[BUG] Credentials Not Persisting in Flowwise AI on Google Cloud Setup

We are experiencing an issue with Flowwise AI where API credentials for services like OpenAPI and Pinecode are not being persistently saved. These credentials seem to disappear after a certain period, requiring re-entry. This problem is occurring in a setup where Flowwise AI is deployed on Google Cloud using Cloud Run and Cloud SQL.
Steps to Reproduce:

Deploy Flowwise AI on Google Cloud using Cloud Run and Cloud SQL.
Add API credentials for services such as OpenAPI and Pinecode through the Flowwise AI interface.
Verify that the credentials are saved and operational - run a Flow.
Wait for a period (exact duration unknown, typically observed within a few minutes/hours).
Re-check the API credentials in the Flowwise AI interface.

Expected Behavior:
Credentials should remain saved and persist indefinitely unless explicitly removed or changed by the user.
Actual Behavior:
Credentials disappear after a certain period, and users must re-enter them to continue using the respective APIs.
Environment:

Flowwise AI Version:** 1.7.2
Deployment Platform: Google Cloud

Cloud Run
Cloud SQL
Like described here: https://medium.com/google-cloud-jp/securing-flowise-on-cloud-run-6ff0e1a70447

Additional Information:

There are no error messages or logs indicating why the credentials are not being saved persistently.
This issue affects the usability of the application as users need to re-enter credentials frequently.

Workaround:
Currently, there is no known workaround other than repeatedly re-entering the credentials.
Potential Causes:

Possible misconfiguration in the Google Cloud setup.
Issues with the Flowwise AI's credential storage mechanism - where their are stored?

Request for Assistance:
We would appreciate any guidance on resolving this issue to ensure that API credentials are saved persistently. If further information is needed, please let us know.
THX and best Sebastian

Likely the container is cycling and when it does the folder containing the encryption key is lost.
You need to store the encryption key on a persistent volume not in the container.


Sensor not found!

utmp-cli for Linux could for some devices output
Error, serial port does not exist!

This bug was fixed in f2e6f919552382ec6de5e1b12f53cc9295fd0500.


If the internet is down (or the library fails to update for some other reason) it seems that the library update task stops

Screenshot:

The failure above is from nearly an hour ago and the library update task is supposed to check every 5 minutes. Clearly the library update task "crashed" with the failure and is no longer running

I think this was my own fault in my own hooks. Hooks should probably have a "catch" around them as well


attributes: How to access [[deprecated(str)]]?

Is it possible to access [[deprecated(str)]], without using __attribute__((gccxml(”...”)))?
From the current docs, it looks like it only exposes the custom attributes?
https://pygccxml.readthedocs.io/en/master/apidocs/pygccxml.declarations.declaration.html#pygccxml.declarations.declaration.declaration_t.attributes

Part of https://github.com/RobotLocomotion/drake/issues/13670
Example:
https://github.com/RobotLocomotion/drake/blob/0d219dbc2642ce6f9c8120cb5839ac87a5bc637d/tools/workspace/pybind11/test/sample_header.h#L260
https://github.com/RobotLocomotion/drake/blob/0d219dbc2642ce6f9c8120cb5839ac87a5bc637d/common/drake_deprecated.h#L59-L63
\cc @jamiesnape @josephsnyder

Upon inspection, at least some of the info is exposed:
https://gist.github.com/EricCousineau-TRI/8da1ad7963fa58315db5852488e18922#file-drake_issue13670_pygccxml_mkdoc_output-txt-L591-L599
class_t: 'DrakeDeprecatedClass'

    location: [bazel-out/k8-opt/bin/tools/workspace/pybind11/_virtual_includes/sample_header/drake/tools/workspace/pybind11/test/sample_header.h]:261
    artificial: 'False'
    attributes: deprecated
    class type: 'class'
    size: 1
    align: 1
    public:

Will see if it includes the information contained within the deprecation too.
That being said, seems like the docs are stale?

I see that attributes are tested here:
https://github.com/CastXML/CastXML/blob/8625aed52c8e2e0b94cfd65767a7564a36ce4c96/test/input/Class-deprecated.cxx
https://github.com/CastXML/CastXML/blob/8625aed52c8e2e0b94cfd65767a7564a36ce4c96/test/expect/castxml1.any.Class-deprecated.xml.txt#L3
However, it doesn't test for text (but the test doesn't even show it, so that's understandable)...

Will upstream this issue to CastXML when it makes sense.

Resolved by #138


CVXPY 1.0: Non-symmetric solutions in SDPs

Consider the following problem:

import cvxpy as cvx
import numpy as np

# A very simple feasibility problem
M = cvx.Variable((3, 3), PSD=True)
C1 = np.array([[0, 0, 1/2], [0, 0, 0], [1/2, 0, 1]])
C2 = np.array([[0, 0, 0], [0, 0, 1/2], [0, 1/2, 1]])
constraints = [M + C1 == cvx.Variable((3,3), PSD=True)]
constraints += [M + C2 == cvx.Variable((3,3), PSD=True)]
objective = cvx.Minimize(cvx.trace(M))
prob = cvx.Problem(objective, constraints)
opt_val = prob.solve()

# Check solution is symmetric
assert (M.value.T == M.value).all()

The above generates non symmetric solutions.
CVXPY 1.0 (9d0e961), Python 3.6.3 (via Ananconda), macOS Sierra, solvers tried MOSEK==8.1.33, SCS==2.0.2.

Closing, as I've realised that this does not occur on this on a clean environment. Sorry for the confusion.

I don't have that version right now and therefore i don't know if you indeed observe wrong results or if you are just disregarding floating-point math.
(M.value.T == M.value)  # will do a comparison of fp-values without any tolerance!

So, how exactly are you defining non symmetric?
Demo (with numpy-arrays here; should transfer to cvxpy):
import numpy as np
np.random.seed(1)

a = np.random.random((3,3))
M = a.dot(a.T)/2
print(M)
print('1: assert: ' + str((M.T == M).all()))

M[0,1] += 1e-15                                       # precision typically not achieved by solvers
print(M)
print('2: assert: ' + str((M.T == M).all()))

print('3: assert: ' + str((np.allclose(M.T, M))))     # good-practice fp-comparison

[[0.34638737 0.11590088 0.16331792]
 [0.11590088 0.06073435 0.07183128]
 [0.16331792 0.07183128 0.15576476]]
1: assert: True
[[0.34638737 0.11590088 0.16331792]
 [0.11590088 0.06073435 0.07183128]
 [0.16331792 0.07183128 0.15576476]]
2: assert: False
3: assert: True

Thanks for the reply @sschnug. Sorry for the confusion, I should have used np.allclose. But, I indeed get visually different results:
print(M)
[[ 0.1740965  -0.01455408 -0.07117049]
 [-0.01455408 -0.07117049 -0.07117049]
 [ 0.1740965  -0.07117049  0.06349708]]

I could also try installing a commit that you have/prefer.

There is indeed a bug here. I've fixed it on the latest 1.0 commit.


New CSRF cookie when previous one is not expired yet and csrf_regenerate is set to false

I am seeing an issue on CI 3.1.13 with PHP 7.4 where a new CSRF cookie with a different token gets set when the previous one has not expired yet and csrf_regenerate is set to false.
This is causing an issue in my app and because of it I have downgraded to 3.1.11, which doesn't have the issue. I looked at the differences between 3.1.13 and 3.1.11, but didn't see an obvious place that could explain this behavior. I am also not sure yet after how long this happens either.
Please let me know if you need any other details or what I can do to help solve this.

I cannot reproduce this anymore. Will reopen if I can figure out the issue.


Add EC2 permission for VPC access

Description of changes:
Add ec2:DescribeVpcs to the list of permissions required for Lambda functions configured within a VPC.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks! Adding this to the VPC topic.


Implement Email Connector

Purpose
Implement Email Connector
Fixes #21179
Check List

[ ] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[x] API documentation
[x] Module documentation in Module.md files
[ ] Ballerina By Examples

We need to remove these files from the PR.

Codecov Report

Merging #21346 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #21346      +/-   ##
==========================================
+ Coverage   14.64%   14.72%   +0.08%
==========================================
  Files          51       51
  Lines        1400     1399       -1
  Branches      214      214
==========================================
+ Hits          205      206       +1
+ Misses       1179     1177       -2
  Partials       16       16

Impacted Files
Coverage Δ

tool-plugins/vscode/src/extension.ts
0% <ø> (ø)
:arrow_up:

tool-plugins/vscode/src/core/extension.ts
28.37% <ø> (+0.33%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 5b1f4ac...7a8f366. Read the comment docs.


Re-design swap-in using a proof of payment

When implementing swaps, we need to generate a preimage and a payment_hash for each swap-in request.
This allows us to store it instantly in the DB while we're waiting for it to complete, otherwise we're losing data if the wallet restarts before the swap completes.
The preimage should be sent back to the swap server when the swap completes, to act as a proof of payment.
This doesn't prevent swap aggregation at the swap server: the server simply needs to explicitly say "this channel I'm opening to you completes swaps <payment_hash1>, <payment_hash2>, etc" for proper accounting.

This is superseded by the dual funding work, we won't need this mechanism anymore.


Improvements to astmodel object heirarchy

Not all of these have to be done, just a list of ideas to help simplify our lives:

Move RelatedDefinitions() to the Definition interface
Should DefinitionName really implement Type?
Improve Function/FunctionDefinition relationship with the rest of the astmodel types (This may partially be accomplished by 1 and 2 above)

#1: included in PR #101 - was part of some cleanup I did to fix the generated files.

Resolving this as George suggested that having Definition work for Function was a bad idea to begin with, updated #80 to implement his suggestion, and @theunrepentantgeek already has item 1 in a PR.


new metadb table Holdings statements supplements

create new metadb table holdings_statement_supplement

[] Query runs
[x] Data output makes sense
[x] Data types look correct
[x] Query logic seems correct
[x] Column names make sense and are spelled correctly
[] Query syntax and style are appropriate (e.g., correct use of double quotes, lower case for data types)

For derived tables:

[x] query has indexes on columns
[x] vacuum analyze has been added to the bottom
[x] table appears in runlist.txt at an appropriate point

I just noticed that on line 11, 23, and 39 statement has double quotes. I was able to run the query when I removed the quotes. I realize that sometimes DBeaver will have the warning for some words. If you want, you could have holdings_statement instead of just using the word statement which will then avoid any warnings.


[Docs]: Email Landing Page

Is there an existing issue for this?

[X] I have searched the existing issues

Documentation Link
https://docs.appsmith.com/getting-started/setup/instance-configuration/email
Discord/slack/intercom Link
No response
Describe the problem and improvement.
Rehaul the landing page.

Based on discussion with @danciaclara - This page will not serve as a landing page anymore, but will be a guide that helps user to configure any email service provider.
Based on scope change - re-estimating the ticket.


New Token submission

ioTube Token submission
Please read the token submission guide here: https://docs.iotube.org/introduction/token-submission
Team / Developer name
...
Token Symbol
...
Token Decimals
...
Token Name in full
...
Link to the token icon
https://...
Short description of your project
Descrie your project here
What is the blockchain (source blockchain) that your token is issued on

[ ] Ethereum
[ ] Binance Smart Chain
[ ] Polygon
[x] IoTeX

What blockchains (destination blockchain) would you like your token is bridged to

[x] Ethereum
[ ] Binance Smart Chain
[ ] Polygon
[ ] IoTeX

(Please check https://docs.iotube.org/introduction/token-submission#integration-fee for integration fees of different blockchains)
Token native contract address explorer link
Address:
Your project websites

https://...

Your social channels

Telegram:
Twitter:
Discord:

Verification of the token
Please provide the verification of your token in one of the following ways.

[ ] Token address on your website. Please specify the link.
[ ] CMC / Coingecko profile link with token contract address and link to website/social

Send test tokens
Please send a few test tokens ($1-$10 worth) to our wallet address: 0x571e603e3B5c82Bd40998C538603dF4fb42bB051.
Integration fee
Please send the payment to 0x571e603e3B5c82Bd40998C538603dF4fb42bB051 or io12u0xq03mtjpt6sye33fcvq7lf76zhvz3yvt8q0 and post your txn link here.

Good

Content is not filled.


Generate type for variables

I'm trying to improve the apollo graphql client to use a functor module to create a query fetching component and the last piece missing is the type of the variables of the query, similar to the one added for the return type.
The api I'm going for would look like:
module AppQuery = [%graphql {| ... |}];

module QueryRenderer = Client.Query.Create(AppQuery);

<QueryRenderer variables={"a": a}>...</Query>

This would allow to type the variables prop easily.

Just ran into this too.
solved it by nesting my mutation in the module I pass as argument to the functor like below:
module type MutationType = {
  type t;
  type variables;

  module Mutation: {
    let makeWithVariables:
      variables =>
      {
        .
        "parse": Js.Json.t => t,
        "query": string,
        "variables": Js.Json.t,
      };
  };
};


Add numerical identifiers to LLVM label syntax

Fixes #1874
Implicitly-named labels of the form \d+: are valid as well as the
explicitly-identified ones already supported using the identifier
syntax.
This PR extends the LLVM lexer to include the numbered syntax.

LGTM, thanks!


Update slacker

This PR introduces the following changes

Update the slacker to version 0.13.0 which handles messaging when the rate limit is
Catch HTTPErrors
Group the tasks unstaffed slack reminder by step

Coverage decreased (-0.05%) to 93.782% when pulling 4b4fefa8dba0ec35f8e49550afa5d592d8784461 on update-slacker into c2248cc0807288880bf6d08dc97043acedbe810f on master.


Easy to fix bug due to wrong redirection link.

Bug description.
In the getting started page of api-inference docs. Users get redirected to this non-existing page instead of this parameters url.
Easy fix
Just replacing the link with the correct link should fix the issue.

Thanks a lot @bhanu-pm! Would you like to submit a PR to fix it, so you are credited with the resolution? You'd need to change this line. No worries if you don't have time; we'll do it next week instead.

Wow @pcuenca that is such a kind gesture. I would love to do that!


Issue from website page 起步: 体验

From URL: https://www.flutterchina.club/get-started/test-drive.md
TAB switching is not available on these pages

Hi @volitantlv, the flutterchina website is community maintained. Kindly report this issue on their repo over https://github.com/flutterchina/website/issues.
Closing this as it is a community maintained project


Annotate generated files

Add a comment near the top of the generated file indicating that:

it is a generate file
what file it was generated from
the tool that generated it

Respect:

build tags
packages

Comments ahead of the package declaration are actually fine.

Same with go generate comments.

Comments can also be ahead of build tags

Going to not add the file it was generated from for now.


[Question] docker-compose up: exec format error?

My experience with docker has usually been using the docker create command, I'm not super familiar with docker-compose, so this is probably user error, but this is what I get when I run docker-compose up.
sudo docker-compose up Recreating mango ... done Attaching to mango mango    | standard_init_linux.go:219: exec user process caused: exec format error mango exited with code 1
This is my docker-compose.yml

version: '3'

services:
mango:
image: hkalexling/mango
container_name: mango
expose:
- 9070
ports:
- 9070:9070
volumes:
- /home/pi/docker/mango:/home/pi/docker/mango
- /home/pi/docker/mango/config:/home/pi/docker/mango/config

Realized I'm trying to run it on my raspberry pi, which is ARM, and Mango only supports amd64/x86-64.

Realized I'm trying to run it on my raspberry pi, which is ARM, and Mango only supports amd64/x86-64.

Mango does support ARM. Please check the wiki.

Mango does support ARM. Please check the wiki.

Also for the ports field, you probably want - 9070:9000

Also for the ports field, you probably want - 9070:9000

Mango does support ARM. Please check the wiki.

Ohhh, I had no idea. So I just went ahead and followed all the steps and compiled it with port 9070. It starts up, but I get this error.

Mango - Manga Server and Web Reader. Version 0.17.1,

[ERROR]   2021/01/10 03:44:46 | Error when checking tables in DB: database is locked,
Unhandled exception: database is locked (SQLite3::Exception),
  from __w/Mango/Mango/lib/sqlite3/src/sqlite3/connection.cr:91:11 in 'close',
  from __w/Mango/Mango/lib/db/src/db/pool.cr:50:21 in 'close',
  from __w/Mango/Mango/lib/db/src/db.cr:123:7 in '->',
  from __w/Mango/Mango/src/queue.cr:112:3 in 'default',
  from __w/Mango/Mango/src/queue.cr:11:7 in 'default',
  from __w/Mango/Mango/src/mango.cr:47:3 in '->',
  from usr/share/crystal/src/mutex.cr:47:9 in '__crystal_main',
  from usr/share/crystal/src/crystal/main.cr:39:9 in 'main',
  from __libc_start_main

Mango does support ARM. Please check the wiki.

Ohhh, I had no idea. So I just went ahead and followed all the steps and compiled it with port 9070. It starts up, but I get this error.

Mango - Manga Server and Web Reader. Version 0.17.1,

[ERROR]   2021/01/10 03:44:46 | Error when checking tables in DB: database is locked,
Unhandled exception: database is locked (SQLite3::Exception),
  from __w/Mango/Mango/lib/sqlite3/src/sqlite3/connection.cr:91:11 in 'close',
  from __w/Mango/Mango/lib/db/src/db/pool.cr:50:21 in 'close',
  from __w/Mango/Mango/lib/db/src/db.cr:123:7 in '->',
  from __w/Mango/Mango/src/queue.cr:112:3 in 'default',
  from __w/Mango/Mango/src/queue.cr:11:7 in 'default',
  from __w/Mango/Mango/src/mango.cr:47:3 in '->',
  from usr/share/crystal/src/mutex.cr:47:9 in '__crystal_main',
  from usr/share/crystal/src/crystal/main.cr:39:9 in 'main',
  from __libc_start_main

I guess your DB files are in a network mounted drive? In that case, you would need to edit the config file and point them to local paths. Please see https://github.com/hkalexling/Mango/issues/138#issuecomment-756037848.

I guess your DB files are in a network mounted drive? In that case, you would need to edit the config file and point them to local paths. Please see https://github.com/hkalexling/Mango/issues/138#issuecomment-756037848.

I guess your DB files are in a network mounted drive? In that case, you would need to edit the config file and point them to local paths. Please see #138 (comment).

Yeah they're all on a NAS Drive. I redirected the db file configs, and changed a couple docker config settings and it's all working now, thanks for all the help!

I guess your DB files are in a network mounted drive? In that case, you would need to edit the config file and point them to local paths. Please see #138 (comment).

Yeah they're all on a NAS Drive. I redirected the db file configs, and changed a couple docker config settings and it's all working now, thanks for all the help!


How to add custom errors to?

Hi,
I've been trying for a while to setup so I can post a custom errormessage ith the validationErrors but I can't seem to get it to work. I'm not sure what I'm doing wrong. Is there any examples of this?
Import everything;
const { Validator } = require('express-json-validator-middleware');
const { validate } = new Validator();

Create the scheme to validate against,
exports.test = {
	type: 'object',
	required: ['name'],
	properties: {
		name: {
			type: 'string',
		},
	},
	errorMessage: 'This is the message I want to pass on and overwrite the standard one..',
};

Set it up as a middleware
router.get('/test', validate({ body: userValidator.test }), userController.test);
And this is the response,
"error": {
    "name": "JsonSchemaValidationError",
    "validationErrors": {
      "body": [
        {
          "keyword": "required",
          "dataPath": "",
          "schemaPath": "#/required",
          "params": {
            "missingProperty": "name"
          },
          "message": "should have required property 'name'"
        }
      ]
    },

I tried following this: https://github.com/simonplend/express-json-validator-middleware#ajv-instance, but that didn't solve it (honestly the ajv-instance just crashes the server.
Running a node server (v14.15.4), with express(v4.17.1)
Most likely I'm missing out some really basic part but an anyone help me out with how to get this package working with a custom errormessage?
Thanks in advance!

Have you figured it out?
I've done some researches I'm afraid in order to do this we need https://github.com/ajv-validator/ajv-errors but it depends on ajv@^8 while express-json-validator-middleware depends on<EMAIL_ADDRESS>So I guess the best way at the moment is to add another middleware (in your express application) and do validation manually. From there you can throw a ValidationError (or any other error) with the message you want to show, like so:
router.post(
  '/test',
  validate({ // AJV validation
    body: {
      type: 'array',
      items: {
        type: 'string',
        uniqueItems: true,
      },
      minItems: 1,
    },
  }),
  (req, res, next) => { // Manual validation
    req.body.forEach((item, i) => {
      if (!isValid(item)) {
        throw new ValidationError({
          body: [{
            keyword: 'format',
            dataPath: `[${i}]`,
            schemaPath: '#/items/format',
            params: {
              format: 'test_format',
            },
            message: `${item} is invalid`,
          }],
        });
      }
    });

    next();
  },
);

There are two approaches you can take:

Install ajv-errors v2.0.1 (npm install<EMAIL_ADDRESS>— you won't lose any functionality, and it's compatible with Ajv v6, which v2.2.1 of express-json-validator-middleware uses.
Try the v3.0.0-beta.0 release of express-json-validator-middleware, which upgrades Ajv to v8. This should be compatible with the latest version of ajv-errors (v3.0.0.


[Event Request]Table 352 "Default Dimension" - OnUpdateWorkCenterGlobalDimCodeOnCaseElse

Request a new event in procedure UpdateWorkCenterGlobalDimCode in table 352 "Default Dimension":
    local procedure UpdateWorkCenterGlobalDimCode(GlobalDimCodeNo: Integer; WorkCenterNo: Code[20]; NewDimValue: Code[20])
    var
        WorkCenter: Record "Work Center";
    begin
        if WorkCenter.Get(WorkCenterNo) then begin
            case GlobalDimCodeNo of
                1:
                    WorkCenter."Global Dimension 1 Code" := NewDimValue;
                2:
                    WorkCenter."Global Dimension 2 Code" := NewDimValue;
                //<NEW>
                else
                    OnUpdateWorkCenterGlobalDimCodeOnCaseElse(GlobalDimCodeNo, WorkCenterNo, NewDimValue);
                //</NEW>
            end;
            WorkCenter.Modify(true);
        end;
    end;

    //<NEW>
    [IntegrationEvent(false, false)]
    local procedure OnUpdateWorkCenterGlobalDimCodeOnCaseElse(GlobalDimCodeNo: Integer; WorkCenterNo: Code[20]; NewDimValue: Code[20])
    begin
    end;

Realized later that this procedure is only called for Global Dimensions 1 and 2.  By using the DimMgt.DefaultDimOn... calls, this request is unnecessary.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Bump phf to 0.11 series

string_cache is still using phf_shared 0.10.0 though.

Last time I remember seeing an error like this, it was caused by an update to one of the runners github uses. This time though, it seems like only this PR causes the failure since others seem to go through without a hitch. Not sure what's causing it here.

@DimitrisJim Hm, strange! I gave this a rebase, so the workflow needs to be reapproved...


Can't find "config/config.yaml" file

what is your launch cmd?
ros2 run pcl_object_detection pcl_object_detection --ros-args --param-file config/config.yaml

your code did not contain config file

@klintan  your code did not contain config file.


send regular updates for traffic density and/or speed

For a defined area or for the whole simulation?
use the existing message schema in https://github.com/DRIVER-EU/python-test-bed-adapter/blob/master/data/schemas/sumo/sumo_AggregatedOutput-value.avsc
Needs to be runtime configurable (area / frequency) or fixed for the whole simulation?

@erikvullings could you please comment on the questions in the description?


Inconsistent status updates

Hi,
Im using homebridge-zway in combination with a razberry. It works pretty awesome 👍
There is one little issue i cannot figure out; When i dim a light in the Home app after changing the slider it jumps back to the old value. Then it usually jumps back again to the set value. Sometimes this happens 2 times in a row. I tried changing the polling rate but it doenst seem to make a difference. It looks like it polls before the command is executed. Sometimes this also happens with on/off actions. Any way to make it more stable? Let me know if you need any logs.

Yes, I've noticed this. I think it's a race condition where the 2-second poll information is coming back as the new value gets sent out...or at least that's one of the ways. I want to get rid of polling eventually with #25 and I hope this will improve this issue.

Guys, is there any workaround for this? I'm having this issue, too.

+1

Did anyone find a workaround or something to fix this issue?
I found something interesting;
I have a configuration with two different types of dimmers.
The Everspring AD146: http://www.everspring.com/portfolio-item/ad146-2-wire3-wire-in-wall-dimmer-module/
Fibaro Dimmer 2: https://manuals.fibaro.com/dimmer-2/
In regards to this issue, the everspring dimmer works flawlessly, while the Fibaro dimmer keeps jumping between the new and the previous setting while adjusting the slider.
I wondered  if the issue might be with the zway-server itself, but all dimmers work fine when using the Z-Wave Smart Home UI. I have not tried adjusting with any other plugins.
I did however test a Z-Way App called 'Dimmable Scene', and that fixed it. But it's not ideal since it doesn't have a status feedback (goes back to 0% after adjustment). It also seems to dim a little bit down first before dimming up.
The app 'Group devices' did not help.

I'm having this issue with an Aeotec Z-Wave Plus RGB Bulb 5
RGB colour control works perfectly through Z-Way web interface, but through homebridge-zway / Apple Home on phone or Mac the colour I pick from the wheel is initially set and then it jumps back to another colour
Wish I could entirely disable polling for the current value, I care more about the control simply working correctly for setting a new colour than reflecting the currently set device value in the UI


Bump Ember CLI to 3.8 and update other dependencies

This looks larger than it is as it includes lint fixes for both js and hbs.
We're just upgrading to ember 3.8 (most recent LTS) and bumping the versions of other dependencies including any revisions to the dummy app where required (e.g. ember-mirage).

Waiting for #698 so travis will start passing.

@alexander-alvarez I believe this one is ready to go now.


S2I templates use hardcoded version 4.4.0

Presume we're talking about the BUILDER_VERSION parameter here? If so, what should this default to?
IMO It can only ever be latest or the last WFC release tag.
Leaving it blank is not ideal because it then forces folks to manually discover what the value should be.

Ideally, this would follow ${project.version} and for SNAPSHOTS be latest - I think.

With the demise of the template, this is only impacts the wildfly-camel-imagestream.json.
Isn't this just a release process task to update the image stream tags to the new release version?

@tdiesler what do we want to do with this?
Automating this is tricky because having the version replaced at build time will result in a dirty workspace when we come to do releases (i.e the updated imagestream.json wont be committed with the release tag).
So either we:

Default the image tag to latest so that we never have to change it (not recommended for production use cases)

Or

Just make it part of the release procedure to update wildfly-camel-imagestream.json when its copied over to the gh-pages branch

Reopening - We still have this problem in the 4.5.0 release.

It should not show up except in the changelog
[tdiesler@macbook wildfly-camel]$ git grep 4.4.0
README.md:$ asciidoctor -a version=4.4.0-SNAPSHOT docs/guide/index.adoc
docs/Changelog.md:* [#1518][1518] Update s2i docs to wildfly-camel-4.4.0
docs/Changelog.md:* [#1510][1510] S2I templates use hardcoded version 4.4.0
docs/Changelog.md:#### WildFly-Camel 4.4.0
docs/Changelog.md:For details see [4.4.0 features](https://github.com/wildfly-extras/wildfly-camel/issues?q=milestone%3A"4.4.0"+label%3Afeature)
docs/Changelog.md:For details see [4.4.0 tasks](https://github.com/wildfly-extras/wildfly-camel/issues?q=milestone%3A"4.4.0"+label%3Atask)
docs/Changelog.md:For details see [4.4.0 bugs](https://github.com/wildfly-extras/wildfly-camel/issues?q=milestone%3A"4.4.0"+label%3Abug)
docs/guide/cloud/openshift-s2i.adoc:$ s2i build https://github.com/wildfly-extras/wildfly-camel-examples.git -r 4.4.0 --context-dir camel-cdi wildflyext/s2i-wildfly-camel:4.4.0 wildfly-camel-example-cdi
docs/guide/cloud/openshift-s2i.adoc:|**Git Reference**| 4.4.0
docs/guide/sources/wildfly-camel-imagestream.json:        "version": "4.4.0"
docs/guide/sources/wildfly-camel-imagestream.json:              "name": "4.4.0"
docs/guide/sources/wildfly-camel-imagestream.json:            "name": "4.4.0",
docs/guide/sources/wildfly-camel-imagestream.json:              "version": "4.4.0",
docs/guide/sources/wildfly-camel-imagestream.json:              "name": "wildflyext/s2i-wildfly-camel:4.4.0"
docs/guide/start/index.adoc:                       -DarchetypeVersion=4.4.0 \
docs/guide/start/index.adoc:                       -DarchetypeVersion=4.4.0 \


Considering that you wrote the code to be more readable than other emulators, it skips along very nicely and the fact that it only  implements the features I want is a major plus (no disk images or folder structures).
Thank you.
However on Debian Linux when I noticed that if I attempted to invoke the Macro-80 the assembler without providing any arguments it prompted me for a command  line as expected.  However, while pressing Ctrl-C at this point would normally return you to the command prompt this doesn't work when using ntvcm.
$ ntvcm -l macro.cpm

*

Expected result.
$ ntvcm -l macro.cpm

*^C
$

Interestingly if I press Ctrl-C and then press Enter, instead of just prompting me again I get an error.
$ ntvcm -l macro.cpm

*
?Command error
*

The same thing happens with one of my own programs that prompts for a file name if none is given and reads the user input from the command line using the BDOS Read String Function (00AH).
$ ntvcm -l type
*

As with Macro-80- if I press Ctrl-C and press enter I get an error message.  This suggests that the Ctrl-C character is being passed to the program and is not being intercepted by the BDOS.
*
?Invalid filename
*

Thank you for reporting this bug! I'm taking a look.

This should be fixed now. BDOS read console buffer still doesn't handle some control keystrokes, but it does now handle ^c.
I validated on Windows and Ubuntu. Hopefully it works on Debian :)

That was quick !!
I can confirm that entering Ctrl-C always exits.  Which fixes the problem of not being able to get back to the command prompt without killing the process from another window.
However, having experimented a bit I have discovered that the expected behaviour on CP/M is a bit more subtle, Ctrl-C only exits if it is the first character entered (or if you delete any characters previously entered and then enter Ctrl-C), otherwise it is passed to input buffer and '^C' is displayed...
As a future enhancement you might want consider implementing the CP/M control character sequences when reading a string using the BDOS.  Although authentic this would be just as painful to use as the original, so it might be better to use something like readline() or an equivalent to give the same kind of command line editing features as the host OS...

Good find! I've fixed that too. Now read console buffer only special-cases ^c in the first position.
Also I really liked reading your CP/M assembler utility functions. They brought me back to high school days!

This has unfortunately seemingly returned. Attached is a 2-byte CP/M executable (it's not a CSV, rename to COM), padded to 128 bytes, that just loops infinitely and it won't break with Ctrl+C in Windows Terminal or VSCode.
loop.csv

CP/M 2.2 does not respond to ^C in infinite loops, and I've replicated that behavior. There are a handful of cases in BDOS and BIOS calls where ^C is treated special, and I've replicated some of them. CTRL+BREAK will end NTVCM in Windows. In WSL it'll kill NTVCM and the shell, forcing you to start the shell over again at the root. I've thought about adding specialized ^C behavior, but it hasn't been enough of a problem (at least for me) to do anything. Modern operating systems have plenty of ways to kill NTVCM :)

My understanding is not complete, but assuming if execution is not currently inside a BDOS call that allows for input, then Ctrl+C should break the program. That is, if CP/M is awaiting console input, then Ctrl+C acts as CP/M expects, but if execution is outside of BDOS/BIOS then Ctrl+C should break?

That's not how CP/M 2.2 works. I remember resetting my Kaypro II whenever I had an infinite loop while writing assignments for CS 307 :)
I validated again just now on the Altair simulator and my physical Z80 CP/M 2.2 machine.
I did have to make a new loop.com though since yours executed uninitialized memory at address 0x00ff assuming there was a NOP there :)
Also, CP/M has no mechanism for an app to change ^C behavior. MS-DOS, for example, lets apps hook int 0x23 so apps weren't terminated by default on a ^C. When an app like Turbo Pascal starts it hooks that interrupt so that when a user presses ^C it means Page Down in the text editor (same for WordStar and many other apps). On CP/M there are no such hooks. The CP/M versions of those apps need ^C to page down, not exit. So the default has to be to not terminate the app.
That said, NTVCM should check for ^C on BDOS 2: console output and exit the app if detected.


Changing the chompfile.toml while watching via chomp -w does not invalidate

I modified the chompfile while using chomp -ws and I was expecting it to re-build targets affected by the task whose options I modified:
[[task]]
  name = "build:html"
  template = "jspm"
  target = "lib/index.html"
  deps = ["src/index.html", ":build:svelte", ":build:typescript"]
  [task.template-options]
    env = ["browser", "production"]
    preload = true
    integrity = true

I added whitespace = false to the template-options, expecting index.html's import map to be formatted differently.

Changes to the Chompfile is quite tricky to support, because it means modifying the in-place task graph based on a chompfile diff. So we would effectively need to implement a diffing algorithm which can be translated from a diff on the chompfile into a diff on the task graph, and then also make allowance for irreconcilable diffs to cause a complete reload. Definitely agreed this would be a good goal, will leave this up to track.

Would it be easier to exec/replace the running chomp process if the chompfile is modified?
Mar 14, 2022 10:29:47 PM Guy Bedford @.***>:

Changes to the Chompfile is quite tricky to support, because it means modifying the in-place task graph based on a chompfile diff. So we would effectively need to implement a diffing algorithm which can be translated from a diff on the chompfile into a diff on the task graph, and then also make allowance for irreconcilable diffs to cause a complete reload. Definitely agreed this would be a good goal, will leave this up to track.
—
Reply to this email directly, view it on GitHub[https://github.com/guybedford/chomp/issues/92#issuecomment-1067552395], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAAABAPHKVT4H2G6UORFDOLVAAG3HANCNFSM5QW7LCYA].
Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].
You are receiving this because you authored the thread. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAADwAAAA8CAYAAAA6/NlyAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAkSURBVGiB7cExAQAAAMKg9U/taQmgAAAAAAAAAAAAAAAAAABuOHwAAW17XWMAAAAASUVORK5CYII=###24x24:true###][Tracking image][https://github.com/notifications/beacon/AAAABAPINLUFBZ4TE4F63IDVAAG3HA5CNFSM5QW7LCYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH6QY5CY.gif]

I don't think I've ever written anything to replace the current process with a new invocation of itself? I would need to do more careful book-keeping to multi-instance the application lifecycle unfortunately :(

(but yes you are right that's the way to do it)


Provide a path forward for existing Jira Cloud connections, while switching to use OAuth approach

In order to migrate an existing MM instance currently using Jira Cloud to use the OAuth approach, we need to add a way to simultaneously support both instance types from the same Jira URL. This is so webhooks/subscriptions etc. can continue to function properly, and existing connected users can continue to interact with the plugin, as the user base is in the process of migrating connections to OAuth.
Issue created from a Mattermost message by @mickmister.

I'm thinking this should not block the 4.0.0 release. Giving the current state of the code to a new customer is a good idea, but not to an existing system that wants to migrate over. Since the admin would need to explicitly run /jira instance uninstall to get them into a bad state, I think this can wait for next release. Though this is a particularly important thing to follow up on.

@mickmister I am a bit confused about what exactly are you expecting here:

If you are asking that the user's old channel subscriptions still work after switching to OAuth, then I think that will still work with the current code as the URL on which Jira sends the webhook is the same for both. So, we will continue to get the webhook notification from Jira even after switching to OAuth.
If you are asking that the user not have to uninstall the JWT instance to switch to the OAuth instance, then also I think it with work with the current code. I tried to install the instance with both JWT and Oauth and when I uninstalled the OAuth one, the other one was uninstalled too. I think currently we are treating them as a single instance as the URL is the same.

Can you please explain a bit more about the issue here?

If you are asking that the user's old channel subscriptions still work after switching to OAuth, then I think that will still work with the current code as the URL on which Jira sends the webhook is the same for both. So, we will continue to get the webhook notification from Jira even after switching to OAuth.

@raghavaggarwal2308 Something that comes to mind here, is are channel subscriptions still active when you uninstall and reinstall a Jira Cloud instance?

I tried to install the instance with both JWT and Oauth and when I uninstalled the OAuth one, the other one was uninstalled too.

Are you saying that both can be installed at the same time already?
The main issue I'm thinking of is:

I'm a user connected to JWT instance
My admin wants to migrate to OAuth
Admin uninstalls JWT, and installs OAuth
I can't interact with Jira until I reconnect my account. Can't receive notifications etc.

I'm not sure if that's how it would work, but bringing it up as we may need to have a migration plan if that's the case

@mickmister

@raghavaggarwal2308 Something that comes to mind here, is are channel subscriptions still active when you uninstall and reinstall a Jira Cloud instance?

Yes, the subscriptions are still valid.

Are you saying that both can be installed at the same time already?

Not at the same time but the OAuth instance overrides the JWT instance if we install a OAuth instance without uninstalling the JWT instance. The reason for this is a check added in the code for installing OAuth instance.

Because of this condition, the code ignores that an instance with the same URL existed before and continues with the setup.

The main issue I'm thinking of is:
I'm a user connected to JWT instance
My admin wants to migrate to OAuth
Admin uninstalls JWT, and installs OAuth
I can't interact with Jira until I reconnect my account. Can't receive notifications etc.
I'm not sure if that's how it would work, but bringing it up as we may need to have a migration plan if that's the case

What do you mean by migration plan here? Are you suggesting that when an admin installs the OAuth instance, all the users who were connected with JWT earlier should be auto-connected to OAuth now?

Are you suggesting that when an admin installs the OAuth instance, all the users who were connected with JWT earlier should be auto-connected to OAuth now?

@raghavaggarwal2308 No I don't think that's possible. By "plan" I mean having a clear path forward for what the MM admin should do when moving off of the JWT app and onto the OAuth version.
Currently there are working deployments of the Jira Cloud JWT app in production (including the MM community server). It works correctly for all cases except for creating new user connections. If we were to run /jira instance install cloud-oauth ... on an existing deployment, what are the implications of this?

Can I still receive DM notifications from the Jira bot, before reconnecting my account via OAuth?
Can I still create issues within the MM UI, before reconnecting my account via OAuth?
Do comment subscriptions still work that rely on the JWT "bot" account approach?

Essentially, we want the least amount of impact on existing functionality that users depend on, during the process of switching to the OAuth instance type. If possible, we should be able to support both instance types simultaneously, so that there is no disruption in working functionality. What are your thoughts on this?

@raghavaggarwal2308 @Kshitij-Katiyar Note that this issue is being escalated due to issues occurring on the community server with the Jira plugin. We're trying to diagnose an issue with subscriptions, and some sysadmins are unable to help since they can't connect their Jira accounts. I would link to the thread on the discussion but it's in a private team.
What are your thoughts on my previous comment?

@mickmister The best solution we could think of here is:

We update the enterprise check for this particular situation to consider instances with the same URL as a single instance but storing them separately in the KV store.
We need to update the key for storing the oauth instance something like instaceID_oauth in the KV store because if we don't, it will override the JWT instance. Note: This might cause some issues for users who have already installed oauth using the 4.0.0 release as they will already have an oauth instance stored with a different key in the KV store.

The code will keep using the JWT instance until the user has connected to the oauth instance.

This might cause some issues for users who have already installed oauth using the 4.0.0 release as they will already have an oauth instance stored with a different key in the KV store.

We definitely want to avoid that breaking change

The code will keep using the JWT instance until the user has connected to the oauth instance.

I'm not sure I understand this. The plugin will continue to use the JWT connected token? So if I understand correctly, the user will be able to continue using their account. This would also take care of the subscription situation where need to fetch the comment body using the commenter's token.
@raghavaggarwal2308 @Kshitij-Katiyar

I'm not sure I understand this. The plugin will continue to use the JWT connected token? So if I understand correctly, the user will be able to continue using their account. This would also take care of the subscription situation where need to fetch the comment body using the commenter's token.

@mickmister Yes, we will be using the JWT connected token. Please share your views if we are not using this approach.

Link to the community thread regarding this issue:
https://community.mattermost.com/core/pl/rj5ewcdo4ig73p8mk3ekkbbx4y


Switch to latest prerelease

Description

Update to latest prerelease to have latest bug fixes in the app.
Motivation and Context

Keep app up to date and fixes #440
How Has This Been Tested?

Running steps in issue #440
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

@ranjeshj The 2.4.2 release still results in the app crashing. Is this intended? It seems that the fix is not in that version which is a bit confusing.

@ranjeshj The 2.4.2 release still results in the app crashing. Is this intended? It seems that the fix is not in that version which is a bit confusing.

I just checked this morning and it seemed to not crash. Can you verify that you have the correct version of the package ?

Okay, so it did not work the first time I switched after your comment, purging the complete folder fixed the issue. Does clean solution not get rid of the nuget packages? Shouldn't installing a new version  WinUI version handle the necessary logic?

Okay, so it did not work the first time I switched after your comment, purging the complete folder fixed the issue. Does clean solution not get rid of the nuget packages? Shouldn't installing a new version WinUI version handle the necessary logic? Both times it reported that it is using version 2.4.2, but only the second time apparently it actually did.

Probably not. I would have expected the nuget restore in the next build/rebuild to have identified the update in version and restored the appropriate version though.

Closing this as #470 does the same.


[snapd 2.57.4] Snap Suddenly Stop Working on SystemD Enabled WSL2

cmd /c ver
Microsoft Windows [Version 10.0.22621.674]
wsl --status
Default Distribution: AlmaLinux-8
Default Version: 2
Did the problem occur during installation?

[ ] Yes

What happened?
Even when previously able to install microk8s using sudo snap install microk8s --classic it's now suddenly stopped working. This render microk8s stop command unable to execute and emit
Interacting with snapd is not yet supported on Windows Subsystem for Linux.
This command has been left available for documentation purposes only.

messages.
What was expected?
Able to install, start, stop. and uninstall using Snap when systemd is enabled on WSL2.
Steps to reproduce

Enable systemd support on WSL2 /etc/wsl.conf[boot]
systemd=true

Restart using wsl --shutdown
Install microk8s
Run microk8s start
Run microk8s stop (usually works fine, this time it stops working)

Additional information
wsl --version
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>
WSLg version: 1.0.45
MSRDC version: 1.2.3575
Direct3D version: 1.606.4
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.674

cat /etc/wsl.conf
[boot]
systemd=true

[automount]
options = ro

Additional screenshot

Hi, thanks for your report.
This is a known issue (https://bugs.launchpad.net/snapd/+bug/1991826). A fix has already been comited here https://github.com/snapcore/snapd/pull/12179 but it hasn't reached users yet. We're also working on a work-around.
May I ask what release you're running? ($ lsb_release -a).

Judging from past releases it should be in the next couple of weeks.
Here is a temporary fix. Note that this will uninstall all your snaps, so be sure to make any necessary backups.
First, make sure your install is indeed broken:
$ sudo snap refresh
Interacting with snapd is not yet supported on Windows Subsystem for Linux.
This command has been left available for documentation purposes only.

If so, apply the fix:
$ sudo apt -y remove snapd --purge # This is the destructive action
$ sudo apt install -y snapd=2.55.3+22.04
$ sudo snap install snapd --beta   # Should install snapd (beta) 2.57.5
$ sudo snap refresh                # Validation: should print "All snaps up to date."
$ sudo apt upgrade snapd          # No need to stay in old version

Here is a temporary fix. First, make sure your install is indeed broken:
$ sudo snap refresh
Interacting with snapd is not yet supported on Windows Subsystem for Linux.
This command has been left available for documentation purposes only.

If so, apply the fix. Go into powershell:
# Check the name of the distro you want to fix (in you case it'll be Ubuntu or Ubuntu-22.04).
wsl -l -v
  NAME              STATE           VERSION
* Ubuntu-20.04      Running         2
  Ubuntu-Preview    Stopped         2
  Ubuntu-18.04      Stopped         2
  Ubuntu            Stopped         2
  Ubuntu-22.04      Running         2

# Use the name of the distro that you want to fix:
wsl -d NAME -u root

This will start a shell as root:
echo -1 >> /proc/sys/fs/binfmt_misc/WSLInterop
systemctl restart snapd
snap refresh snapd --beta
exit

You'll be back in powershell. Restart wsl:
wsl --shutdown

Go into WSL the usual way and test that it worked:
sudo snap refresh
# Should print something other that the previous message

Can confirm the latest workaround works, thank you. Any way I can return to snap release once the fix is there?

Hi, thanks for your report.
This is a known issue (https://bugs.launchpad.net/snapd/+bug/1991826). A fix has already been comited here snapcore/snapd#12179 but it hasn't reached users yet. We're also working on a work-around.
May I ask what release you're running? ($ lsb_release -a).

Also, here's my lsb_release -a in case it's still needed.
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.04.1 LTS
Release:        22.04
Codename:       jammy

Thanks, I've checked and this afects every distro from 18.04 to 22.10.

Any way I can return to snap release once the fix is there?

Yes, once the fix is available you'll be able to return to release. I'll mention it in this thread and close the issue once that is the case.

Workaround:
Ensure you have systemd-binfmt.service installed in your distro (in Ubuntu that means having the binfmt-support package installed via apt), then execute the following:
echo ":windowsexe:M::\x4d\x5a::/init:PF" | sudo tee -a /proc/sys/fs/binfmt_misc/register

This will replace the WSLInterop binfmt support with an identical configuration under a different name. To activate this, leave WSL and run wsl --shutdown in a PowerShell or CMD window. Next time you restart your distro it should replace the WSLInterop binfmt configuration with this renamed copy so that snapd can't tell that it's on WSL.

This fix Fix works for:

Ubuntu 22.04 (Microsoft Store names: Ubuntu and Ubuntu 22.04 LTS)
Soon to come for other versions. In the meanwhile look around this thread for various temporary workarounds.

This is the fix:
sudo apt-get -y update
sudo apt-get -y upgrade snapd

If you had switched to the beta channel as a temporary fix, you can undo it via:
sudo snap refresh snapd --channel=stable

Workaround:
Ensure you have systemd-binfmt.service installed in your distro (in Ubuntu that means having the binfmt-support package installed via apt), then execute the following:
echo ":windowsexe:M::\x4d\x5a::/init:PF" | sudo tee -a /etc/binfmt.d/windowsexe.conf

This will replace the WSLInterop binfmt support with an identical configuration under a different name. To activate this, leave WSL and run wsl --shutdown in a PowerShell or CMD window. Next time you restart your distro it should replace the WSLInterop binfmt configuration with this renamed copy so that snapd can't tell that it's on WSL.
Edit: fix the path to the configuration file.

It triggers some errors when I run jupyter lab:
grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory
WSL Interopability is disabled. Please enable it before using WSL.
grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory
[error] WSL Interoperability is disabled. Please enable it before using WSL.
Parameter format not correct - ""
tcgetpgrp failed: Not a tty

This is the official, permanent fix. It works for all versions except for Ubuntu Preview (Ubuntu 22.10), which will be fixed soon.
This is the fix:
sudo apt-get -y update
sudo apt-get -y upgrade snapd

@EduardGomezEscandell I did the above and then removed/reinstalled the snaps (b/c snap list reported them as broken) and then tried to build something and I'm getting this:

$ snapcraft --use-lxd
Launching a container.
Waiting for container to be ready
Waiting for network to be ready...
Interacting with snapd is not yet supported on Windows Subsystem for Linux 1.
This command has been left available for documentation purposes only.
An error occurred when trying to execute 'snap set system experimental.snapd-snap=true' with 'LXD': returned exit code 1.

Thanks for the report, @micahl
This seems to be a separate issue. Snapd detects it is running on WSL but fails to detect it is WSL2, so it falls back to assuming it is WSL1. See here:
https://github.com/snapcore/snapd/blob/3c05e535e5cff4b64e4427e38494795fbbfd5122/release/release.go#L131
Please open an issue in snapd repository (https://github.com/snapcore/snapd) to get this fixed.

Hi, I'm still facing issues with it even after the upgrade. I did try some of the workaround fixes for it before I saw the new release, not sure if that's the reason this is happening. I did try purge method mentioned at the top of this thread too.
Result of snap version

Result of snap refresh:

@isonlaxman
This error is different and probably not related to snap. Are you sure your systemd is enabled properly? Use systemctl is-system-running and ensure it returns online or degraded.

@isonlaxman
This error is different and probably not related to snap. Are you sure your systemd is enabled properly? Use systemctl is-system-running and ensure it returns online or degraded.

What should I do if the message returns "degraded"?

Then you're good, that's normal and snap should work. If you want to see exactly which services fail you can use systemctl --failed.
It happens because of some incompatibilities between these services and WSL that we have not yet addressed. Do you have the same issue as the one reported in the previous screenshot, or is it something else?

I also have the same issue as the @isonlaxman in regards to snap version but snap refresh seems to work. systemctl is-system-running shows degraded and systemctl --failed shows systemd-sysusers.service failing

What version of Ubuntu are you running? lsb_release -a

If the error message is the same as  @isonlaxman, then please file a new issue (under this same repo) because it seems to have a diferent origin as the original report. You can tag me there if you want.
In that issue please provide your $HOME\.wslconfig (in Windows) and /etc/wsl.conf, it could be some network thing but let's discuss it elsewhere, this thread is long and disjointed enough as-is.

Closing because this issue only affects Kinetic, which is no longer supported on WSL (This or next week Ubuntu-Preview will start shipping with Lunar Lobster :lobster: )

snapd with version 2.57.5 is currently available on Ubuntu 22.10 with source kinetic-updates, while kinetic source is still at 2.57.4+22.10ubuntu1.

Console Outputs
π lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 22.10
Release:        22.10
Codename:       kinetic

π apt list snapd -a
正在列表... 完成
snapd/kinetic-updates,now 2.57.5+22.10 amd64 [已安装]
snapd/kinetic 2.57.4+22.10ubuntu1 amd64

π snap --version
snap                         2.57.6
snapd                        不可用
series                       16
Windows Subsystem for Linux  -
kernel                       <IP_ADDRESS>-microsoft-standard-WSL2 (amd64)

π snap list
名称      版本             修订版本   追踪             发布者         注记
core20  20221027       1695   latest/stable  canonical✓  base
lxd     4.0.9-eb5e237  23991  4.0/stable/…   canonical✓  -
snapd   2.57.6         17883  latest/stable  canonical✓  snapd

It's also available to install and run Snap Packages with snap and snapd! (Some logs are folded)

Install & Run & Remove logs
π sudo snap install hello-world
确保 "hello-world" 的先决条件可用
......
确保 "core" 的先决条件可用
下载 snap "core" (14399)，来自频道 "stable"
......
获取并检查 snap "core" (14399) 的断言
挂载 snap "core" (14399)
......
复制 snap "core" 的数据
设置 snap "core" (14399) 的安全配置
使 snap "core" (14399) 可用于系统
自动连接 snap "core" 的符合条件的插头和插槽
如果存在，则运行 "core" snap 的配置挂钩
下载 snap "hello-world" (29)，来自频道 "stable"
......
获取并检查 snap "hello-world" (29) 的断言
挂载 snap "hello-world" (29)
......
 Are you sure your systemd is enabled properly? Use systemctl is-system-running and ensure it returns online or degraded.

What should I do if the message returns "degraded"?

what if it showing offline?

@isonlaxman
This error is different and probably not related to snap. Are you sure your systemd is enabled properly? Use systemctl is-system-running and ensure it returns online or degraded.

what if it is showing offline?


"ArrowInvalid: Can't unify schema with duplicate field names" read parquet files from s3 using dask;

using a query I dump data from redshift to parquet
UNLOAD
('
SELECT
     delivered_at
    , flow_name
    , variant_name
    , user_id
') TO
            's3://data/raw/redshift/all_campaigns'
            IAM_ROLE 'arn:aws:iam::XYZ:role/redshift'
            FORMAT AS PARQUET
            maxfilesize 96 mb
            ALLOWOVERWRITE
            MANIFEST;

from the other end using dask I try to read a chunk of this data
df = dd.read_parquet('s3://data/raw/redshift/all_campaigns0079_part_00.parquet')

/Users/fanbuch/Devel/NyRec/EDA.ipynb Cell 7' in <cell line: 1>()
----> 1 df = dd.read_parquet('s3://data/raw/redshift/crm/was_clicked/all_campaigns0079_part_00.parquet')
File ~/opt/miniconda3/envs/deeprec/lib/python3.9/site-packages/dask/dataframe/io/parquet/core.py:460, in read_parquet(path, columns, filters, categories, index, storage_options, engine, calculate_divisions, ignore_metadata_file, metadata_task_size, split_row_groups, chunksize, aggregate_files, parquet_file_extension, **kwargs)
    457 if index and isinstance(index, str):
    458     index = [index]
--> 460 read_metadata_result = engine.read_metadata(
    461     fs,
    462     paths,
    463     categories=categories,
    464     index=index,
    465     gather_statistics=calculate_divisions,
    466     filters=filters,
    467     split_row_groups=split_row_groups,
    468     chunksize=chunksize,
    469     aggregate_files=aggregate_files,
    470     ignore_metadata_file=ignore_metadata_file,
    471     metadata_task_size=metadata_task_size,
    472     parquet_file_extension=parquet_file_extension,
    473     **kwargs,
    474 )
    476 # In the future, we may want to give the engine the
    477 # option to return a dedicated element for `common_kwargs`.
...
File ~/opt/miniconda3/envs/deeprec/lib/python3.9/site-packages/pyarrow/error.pxi:144, in pyarrow.lib.pyarrow_internal_check_status()

File ~/opt/miniconda3/envs/deeprec/lib/python3.9/site-packages/pyarrow/error.pxi:100, in pyarrow.lib.check_status()

ArrowInvalid: Can't unify schema with duplicate field names.

I am sure I don't have identical columns. Please help me improve the question quality if it is not clear.

Hi @naarkhoo, the error seems to be coming from arrow. Are you able to read the parquet file with only arrow or only pandas?
That is to say, if you do something like
import pandas
df = pandas.read_parquet('s3://data/raw/redshift/all_campaigns0079_part_00.parquet')

do you get the same error? That would help determine whether this is a problem with dask or if it lies elsewhere.

Thanks for your reply
it is not the same error but very similar, right ?
[image: image.png]
On Thu, Jul 7, 2022 at 11:33 PM Ian Rose @.***> wrote:

Hi @naarkhoo https://github.com/naarkhoo, the error seems to be coming
from arrow. Are you able to read the parquet file with only arrow or only
pandas?
That is to say, if you do something like
import pandasdf = pandas.read_parquet('s3://data/raw/redshift/all_campaigns0079_part_00.parquet')
do you get the same error? That would help determine whether this is a
problem with dask or if it lies elsewhere.
—
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/9251#issuecomment-1178252367, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABWWO76AYEZ2BFQM4GBR6DVS5EJDANCNFSM525REUJQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Oh, I believe this is the same error
Output exceeds the [size limit](command:workbench.action.openSettings?[). Open the full output data [in a text editor](command:workbench.action.openLargeOutput?9f3139d5-cc3d-4ff3-a115-8127dd8e7a8b)
---------------------------------------------------------------------------
ArrowInvalid                              Traceback (most recent call last)
/Users/fanbuch/Devel/NyRec/EDA.ipynb Cell 9' in <cell line: 2>()
      [1](vscode-notebook-cell:/Users/fanbuch/Devel/NyRec/EDA.ipynb#ch0000031?line=0) import pandas
----> [2](vscode-notebook-cell:/Users/fanbuch/Devel/NyRec/EDA.ipynb#ch0000031?line=1) df = pandas.read_parquet('s3://data/raw/redshift/crm/was_clicked/all_campaigns0079_part_00.parquet')

File ~/opt/miniconda3/envs/deeprec/lib/python3.9/site-packages/pandas/io/parquet.py:493, in read_parquet(path, engine, columns, storage_options, use_nullable_dtypes, **kwargs)
    446 """
    447 Load a parquet object from the file path, returning a DataFrame.
    448
   (...)
    489 DataFrame
    490 """
    491 impl = get_engine(engine)
--> 493 return impl.read(
    494     path,
    495     columns=columns,
    496     storage_options=storage_options,
    497     use_nullable_dtypes=use_nullable_dtypes,
    498     **kwargs,
    499 )

File ~/opt/miniconda3/envs/deeprec/lib/python3.9/site-packages/pandas/io/parquet.py:240, in PyArrowImpl.read(self, path, columns, use_nullable_dtypes, storage_options, **kwargs)
    233 path_or_handle, handles, kwargs["filesystem"] = _get_path_or_handle(
    234     path,
...
session_minutes: int64
__fragment_index: int32
__batch_index: int32
__last_in_fragment: bool
__filename: string

These are the versions

dask version        : '2022.6.0'
pyarrow version     : '8.0.0'
fastparquet version : '0.8.1'

I also have asked the question on stackoverflow

it turned out indeed there were two columns with identical col_names; I wish the library was smarter than that.


[ENH] Add "fMRIPrep" template, with new boldref template

This might be a good train for @ihashi3 to hop on. We would need to add the pediatric atlas here to use it in fMRIPrep. (Doesn't have to be this PR, but just to draw attention to how this is done.)

This should be merged after #256

Under test in https://github.com/poldracklab/fmriprep/pull/1321


Question: How to get it to work in a Nuxt 3 app?

Sorry for asking, but I've tried everything I can think of, and I can't get it to work in my Nuxt 3 app.
I added the plugin to the nuxt.config.ts and the path to tsconfig.json
The Playground is working correctly in my VS Code with Volar, but in my Nuxt 3 project it says "This expression is not callable" whenever I try to call a ref to get its value.

Demo: https://github.com/sxzz/nuxt-functional-ref
It doesn't support SSR/SSG at the moment.

Thank you!!

If you're using pnpm, try pnpm.overrides. It works perfectly!
https://github.com/sxzz/nuxt-functional-ref/commit/01cd6d84ad1994d7a0e0eb335b08b1aa99f970f7


fix BacalhauError call limitation, and some other tiny fix.

The issue this PR will close: #11
Also, fixes the log message not printed issue.

@binocarlos – can you take a look at this change to onlyOwner?


torrential: init at 1.1.0

Motivation for this change
Add a torrent client which is well integrated with the Pantheon Desktop.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Thanks @Kjuvi  :smile:


Port logging Serial Port via USB with USB expander

Port logging with node > serialport is not picking up all the ports connected through a USB expander. I have a 1:4 USB expander with a Prolific RS232->USB plugged into each USB port. The Linux OS sees all of the ports:
  $ sudo setserial -g /dev/ttyUSB*
  /dev/ttyUSB0, UART: 16654, Port: 0x0000, IRQ: 0
  /dev/ttyUSB1, UART: 16654, Port: 0x0000, IRQ: 0
  /dev/ttyUSB2, UART: 16654, Port: 0x0000, IRQ: 0
  /dev/ttyUSB3, UART: 16654, Port: 0x0000, IRQ: 0
  /dev/ttyUSB4, UART: 16654, Port: 0x0000, IRQ: 0

However the serialport code only sees one of them:
  com.list(function (err, ports){
   ports.forEach(function(port){
	console.log(port.comName);
	console.log(port.pnpId);
	console.log(port.manufacturer);
   });
   console.log("Finished Port Logging\n\n");
  });

The port it sees changes if I move them around on the expander module. This is a bit of a road block for me right now.

Tracking similar issue at https://github.com/voodootikigod/node-serialport/issues/610


display rotation configuration does not work on dual-screen displays

When testing DirectMode on dual-screen display setup that receives portrait video, I wasn't able to rotate the displays to show landscape picture.
I modified "rotation" setting to "90" and "270" with no visible effect
"display": {
"rotation": 0,
"bitsPerColor": 8
},
CC @russell-taylor

With the attached config file, I was able to render to two displays using the D3D spinning-cube demo.  When I switched rotation from 0 to 90, the windows changed their aspect ratios and the images rotated by 90 degrees (cubes spinning up rather than left).  When I changed to 270, the images flipped and the cubes spun down.  This is behaving as expected .
nondirectmode_dual_window.zip

I'll try to reproduce this on a pair of DirectMode displays, rather than using the two on-screen displays, but these both follow the same rendering path as far as image orientation is concerned.

The trick is that when you rotate the display with the "rotation" parameter above, you also need to swap the requested display resolution, because the rendering happens in the un-rotated display resolution and then RenderManager rotates it (swapping aspect ratio) when rendering.  If the viewer will see a landscape image (1920x1080) but the display scans out in portrait (1080x1920), you set the display resolution to 1920x1080 and then rotate by 90 (or 270).


How to trace an executed workflow?

I am executing XAML Workflows inside the Activity. When a workflow fails, I would like to access the trace of the whole workflow.
In my Tests for the Workflows, I use the WorkflowTestApplication class from https://www.nuget.org/packages/Microsoft.Activities.UnitTesting
calling this.WorkflowApplicationTest.Tracking.Trace(); outputs the following (shortened):
7: Activity [1.60] "Flowchart" scheduled child activity [1.2542] "WaitForInitializeInput"
8: Activity [1.2542] "WaitForInitializeInput" is Executing
9: Activity [1.2542] "WaitForInitializeInput" scheduled child activity [1.2542.1] "Flowchart"
10: Activity [1.2542.1] "Flowchart" is Executing
14: Activity [1.2542.2] "Wait<IDictionary<String,String>>" is Closed
15: Activity [1.2542.1] "Flowchart" is Closed
16: Activity [1.2542] "WaitForInitializeInput" is Closed
Would be cool if you could push me in the right direction. Right now, we cannot access the workflow Host object becaus it is internal.

I just found there is already a tracking Provider that writes to ActivityActorEventSource
https://github.com/wasabii/Cogito.ServiceFabric/blob/master/Cogito.ServiceFabric.Activities/ActivityActorEventSource.cs
The second eye opener is the fact, that i can easily add a custom TrackingParticipant by providing it as WorkflowExtension.

Ahh, yup. Glad you found those!


EnableHotLoading + use external config file

To start, I'd like to say that I'm quite excited about your project.
I have create a project using Angular 2 and Aspnet core MVC.  I have quite an elaborate webpack.config.js that works well with your plugin.  My only problem is that I want to also enable hot loading.  The pull request currently queued seems to handle what I'm looking for.
Any chance we could get this configuration supported?

By way of an update, I have downloaded the latest source and it is mostly working in this configuration.  I have been unable to make the browser auto reload (I have to hit refresh to see changes), but webpack is repacking the files when they are modified.


Message payloads - contents in system messages

This issue is based on this discussion
Core of the problem:

Most system messages use data property on message (string), not contents.
All client messages use contents property, and it's string
But summary ack/nack use contents, and it's an object. I.e. above two rules are broken,

We should make system consistent and uniform.
I see two possible directions:

System messages (including summary ack/nack) to use data property only
Move all messages (including system) to use contents (and only as a string).

I think we prefer # 1, mostly because service is not supposed to even crack contents (that's client payload), but does crack data property. I find this argument not strong, as someone needs to make determination if it's Ok to crack some payload, and it's based on op type, so one way or another service knows when it's Ok to crack payload (and controls who can send ops with specific type / payload).
Copying Gary's reply from the thread:
ClientJoin & ClientLeave messages use data. Control messages also use it, but clients will never see those since they are not sequenced.
Relevant code is here and here.
The summary ack and nack case is odd. Scribe will set both the contents and data property for it (code). However the summaryAck & nack type are missing from deli's extractDataContent method so the data property is essentially ignored. Maybe someone meant to migrate those 2 types to use data instead of contents but didn't finish? That seems to be the case based on this PR

@vladsud For going with # 1 - Does the client already support parsing data from a summaryAck/summaryNack?
Trying to see how we would sequence the changes. I'm guessing the server should continue filling out contents but also add data, and clients can eventually start reading data instead.

No, client only parses data for join/leave messages.
We can easily add have extra code to get data from either content or data (whatever present) and get it in. Depending on which direction we talk about, it may take weeks (# 1 approach) vs. months (# 2 approach) - it's difference between where parsing happens (container runtime vs. protocol/loader layer).
As for sequencing, we can go in multiple directions. I think the easiest one would be to have least amount of synchronization - i.e. service starts duplicating data and client can work with either formats. Alternatives are also Ok


Update crypto-js dependency

Hi, can you upgrade your version of crypto-js to 4.0.0? Snyk is reporting a vulnerability when I include gocardless-nodejs in my project. I believe the only change to crypto-js is to use native randomness generators that won't work in IE 10 or React Native, so it should be fine for a NodeJS library.

Thank you for reporting it and sorry for the lack of activity. This has been fixed in #122


Unwanted characters

Hello
There is appearing unwanted "␍" characters

There is my write code:
Sub WriteLine(a As String)
        a = uncolor(a)
        Dim lines As List(Of String) = chatlog.Text.ToString.Split(vbLf).ToList
        If lines.Count > 17 Then
            lines.RemoveAt(0)
        End If
        lines.Add(a)
        chatlog.Text = String.Join(vbLf, lines)
End Sub

I tried to use Environment.NewLine and vbLf, vbCrLf
But "␍"characters not disappereared

Okay, I solved this by adding
For i = 0 To lines.Count - 1
        lines(i) = lines(i).Replace(vbCr, "").Replace(vbLf, "")
Next

In the preview version this is already fixed.

In the preview version this is already fixed.

okay thanks


Hotkey to reply to last

Issue
There should be a hotkey to allow you to reply to last message(s).
Alt + R for replying sender and all receivers.
Alt + Shift + R for replying to only the sender.
Notes

This should affect whispers, messages, and addresses.

Resolved in PR #185


Update postman.go

After breaking change update in uuid package (https://github.com/hlandau/acmetool/issues/293), postman.go should be updated.

the package manager should avoid this kind of problem...
I'd rather migrate the package to go modules before updating any dependency


All new CircuitSimulator

Correct handling of measurements in circuits

If circuit has measurements and classical bits, only these are returned
If circuit has no measurements, all qubits are measured (as before)

Removed reordering from code base
Smaller changes to the README

Fixes #8

LGTM 👍🏼


AIs?

would be nice to have some AIs to play against

Sounds good! Though I'm very short for time, happy to accept a PR though
On Thu, Aug 13, 2015 at 11:35 AM, Juan Benet<EMAIL_ADDRESS>wrote:

would be nice to have some AIs to play against
—
Reply to this email directly or view it on GitHub
https://github.com/jpillora/ssh-tron/issues/4.

Cool


services.xserver.desktopManager.gnome3.enable fails with "Detected unsafe path transition"

Describe the bug
nixos-rebuild fails when services.xserver.desktopManager.gnome3.enable is set to true.
To Reproduce
Steps to reproduce the behavior:
  services.xserver.desktopManager.gnome3.enable = true;

Output from sudo nixos-rebuild switch
...
Detected unsafe path transition /etc → /etc/NetworkManager during canonicalization of /etc/NetworkManager.
reloading the following units: dbus.service, firewall.service
restarting the following units: polkit.service
starting the following units: accounts-daemon.service, systemd-udevd-control.socket, systemd-udevd-kernel.socket
the following new units were started: NetworkManager-dispatcher.service, NetworkManager-wait-online.service, NetworkManager.service, avahi-daemon.service, avahi-daemon.socket, colord.service, cups-browsed.service, cups.service, systemd-hostnamed.service
warning: error(s) occurred while switching to the new configuration

Notify maintainers
Not sure where "services.xserver.desktopManager.gnome3" is defined...
Metadata
nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.87, NixOS, 20.09.2538.0cfd08f4881 (Nightingale)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.10`
 - channels(root): `"nixos-20.09.2538.0cfd08f4881, nixos-2003-20.03.3324.929768261a3, nixos2003-20.03, nixos2009-20.09.2538.0cfd08f4881, unstable-21.03pre262186.e49e3a756b3"`
 - channels(chris): `"nixos-20.09.2538.0cfd08f4881, nixos-2003-20.03.3324.929768261a3, nixos-latest-2003-20.03, nixos2003-20.03.3324.929768261a3, nixos2009-20.09.2538.0cfd08f4881, unstable2-21.03pre262186.e49e3a756b3"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Is anything broken for you though? I have a feeling that this error might be safe to ignore. While these errors happened I don't think they prevent the switch to the new generation.

Is anything broken for you though? I have a feeling that this error might be safe to ignore. While these errors happened I don't think they prevent the switch to the new generation.

Hmm you seem to be correct, though the actual command does return a non success exit code as well as the warning: error(s) occurred while switching to the new configuration message.
In other words:
sudo nixos-rebuild switch
building Nix...
building the system configuration...
updating GRUB 2 menu...
lsblk: /dev/mapper/no*[0-9]: not a block device
lsblk: /dev/mapper/raid*[0-9]: not a block device
lsblk: /dev/mapper/disks*[0-9]: not a block device
activating the configuration...
setting up /etc...
reloading user units for chris...
setting up tmpfiles
Detected unsafe path transition /etc → /etc/NetworkManager during canonicalization of /etc/NetworkManager.
warning: error(s) occurred while switching to the new configuration

Return:
echo $?
1

Hmm you seem to be correct, though the actual command does return a non success exit code as well as the warning: error(s) occurred while switching to the new configuration message.
In other words:
sudo nixos-rebuild switch
building Nix...
building the system configuration...
updating GRUB 2 menu...
lsblk: /dev/mapper/no*[0-9]: not a block device
lsblk: /dev/mapper/raid*[0-9]: not a block device
lsblk: /dev/mapper/disks*[0-9]: not a block device
activating the configuration...
setting up /etc...
reloading user units for chris...
setting up tmpfiles
Detected unsafe path transition /etc → /etc/NetworkManager during canonicalization of /etc/NetworkManager.
warning: error(s) occurred while switching to the new configuration

Return:
echo $?
1

Yes this is frankly not uncommon for some nixos configurations. It means that rebuild succeeded but there were some errors when starting new services because the transition from the old to the new configuration involved some complex state. From my experience it's usually not a problem but you can just reboot the computer at which point everything will start again from clean state.
While it would be nice to see these issues resolved I don't see that being done any time soon give the complexity of moving from one arbitrary configuration to another and the fact that there seems to be more pressing issues all the time.

Yes this is frankly not uncommon for some nixos configurations. It means that rebuild succeeded but there were some errors when starting new services because the transition from the old to the new configuration involved some complex state. From my experience it's usually not a problem but you can just reboot the computer at which point everything will start again from clean state.
While it would be nice to see these issues resolved I don't see that being done any time soon give the complexity of moving from one arbitrary configuration to another and the fact that there seems to be more pressing issues all the time.

Please show permissions and ownership of /etc, /etc/NetworkManager, /etc/NetworkManager/system-connections, and every file inside /etc/NetworkManager (ls -altr /etc/NetworkManager).
This is likely a bug due to incorrect configuration of systemd.tmpfiles.rules that we should fix.

Please show permissions and ownership of /etc, /etc/NetworkManager, /etc/NetworkManager/system-connections, and every file inside /etc/NetworkManager (ls -altr /etc/NetworkManager).
This is likely a bug due to incorrect configuration of systemd.tmpfiles.rules that we should fix.

tmpfiles rules btw https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/networking/networkmanager.nix#L429.

tmpfiles rules btw https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/networking/networkmanager.nix#L429.


Cannot control the lock status

Hi
Thank you very much for developing this piece of software :-)
I have installed the docker variant and I can run all the GET commands just fine.
However if I try to change the lock state on one of my flaps, I receive an http/422 error:
Request: {{baseUrl}}/devices/:device_id/control?lock_mode=out
Response
{
"detail": "{'success':false,'error':{}}"
}
Performing a GET on the device_id returns a result as expected.
Thank you for any help.
Holger

Hey @Vandroiy78,
thank you for your contribution. I suspect that your SurePetCare User doesn't have the "Control Permissions" required for updating the lock state. Nevertheless, the HTTP status code would be misleading in this case.
I'll take a closer look tomorrow and share my findings.
Kind regards
Fabian

Thank you for your response, Fabian.
I am able to control the locking state via the app or website with this user. However this is not the main user of the system, but granted administrator privilege.
I will see if it works when using the main user.
Holger

I could reproduce the issue on my own SureFlap device. It has nothing to do with permissions.
I just want to let you know that I am working on a fix.

Hey @Vandroiy78
The issue should be resolved with Release 4.2.4. The docker images are available.
Just let me know, if you can control the lock state now.
Kind regards
Fabian

Hello Fabian
Thank you so much for taking care about this issue. I have updated to the latest version.
At this moment, I still get valid results for all the GET commands. When trying to set the lock mode I have:
{   "detail": "\r\n<title>504 Gateway Time-out</title>\r\n\r\n
504 Gateway Time-out
\r\n\r\n\r\n" }
I will retry tomorrow, maybe there is a problem with their servers.
Regards
Holger

It seems that they indeed had outage on their system yesterday.
I re-tried today and I still get the error above sometimes, but in other tries I receive an error 500 while the lock state is set correctly. Maybe they are still recovering from the outage and are receiving lots of loads on their servers.
I think that the initial problem has been solved. Thank you, @fabieu

I sometimes experience the described behavior via the official SureFlap Android app as well.
Unfortunately, there is nothing I can do to prevent this, so I will close this issue as resolved.

Hi @fabieu thank you for this project! I've been looking for a way to add a additional curfew modes for our cats (like lock-outside curfew which is supported on the non-connected flaps!) and this would be perfect.
After a quick test it looks like my GET /device/<id> returns invalid/incomplete data and setting a lock_mode doesn't work on my device either.
I did a GET /devices/<id> when the device was set to "Locked both ways" in the app:
{
  "control": {
    "curfew": null,
    "fast_polling": null,
    "locking": null
  },
  "created_at": "2019-09-03TXX:XX:XXZ",
  "household_id": 0.0,
  "id": 0.0,
  "index": null,
  "mac_adress": null,
  "name": "Hub",
  "pairing_at": null,
  "parent": null,
  "parent_device_id": null,
  "product_id": 1.0,
  "status": {
    "battery": null,
    "learn_mode": null,
    "locking": null,
    "online": true,
    "signal": null,
    "version": {
      "lcd": null,
      "rf": null
    }
  },
  "updated_at": "2024-06-13T05:49:05.498102Z",
  "version": 38829.0
}

And after this
curl -X PATCH http://localhost:8080/devices/<id>/control?lock_mode=none
{"curfew":null,"fast_polling":null,"locking":null}

Nothing in the output changes.


Why data binding only works one-way at top level?

I have tried using the crate-builder-component in a new simple Vue app and managed to get it running and displaying the crate data.
However I just found out that the crate data is bound only at top level.
For example, if you have data.crate = { ... } and pass it to :crate="data.crate", you can't do for example
<EMAIL_ADDRESS>= 'abc' to update a value from outside of the compenent. And neither<EMAIL_ADDRESS>is updated when the value in the text box is changed.
I know that we can use the @save:crate event to get the current/modified data.
But, is there a reason for not properly bound each nested property to its corresponding ui component?
It seems to be counterintuitive to how Vue component generally works.

You’ve asked two different questions whose answer is related.

To the first: why is the modified crate data not being reflected in the crate object outside the component.
The way it operates is by design. The component is intended to be a black box that has a defined  interface to send data in and one to get data out. It is designed to completely encapsulate crate data handling internal to itself without needing to worry about side effects coming from outside.

To the second: why aren’t properties directly bound to UI elements.
With regard to the implementation; when the component ingests the crate it pulls it apart into an entities array and a properties array. Each entry in the properties array is an object with entityId, propertyId, property name, value and targetEntityId properties. When the crate is rendered to the UI each of these rows is passed into a component that knows how to handle it. For example, if it's a value and the profile says it should be a date then the date component is given the object to render a date picker.

When a user interacts with a data component (eg a text component or date or select) the new value is emitted and passed back up the tree to be patched into the internal structure. Or if a property is added, a placeholder is emitted and patched in to the properties array.
So the data always flows from the parent component to the relevant child component as properties (vue props which are immutable) and changes inside those components (at the edge) are emitted as a patch to the relevant object which is then handled at the top of the component tree.  This is very much how vue (and other spa frameworks) data flow is supposed to work.
The design itself came from an earlier iteration of describo which used a database backend (with an entity table and a linked properties table) to store the crate and which worked exceedingly well with very large crates. Indeed this design also allows me to use the internals of this component in another product I’m working on that is database backed because in that case, the patch events can be sent to the db instead of the internal representation.
What you’ve described sounds a lot like what all of the frameworks stopped doing; namely, allowing changes to data in multiple places. In your description, if I’ve understood it correctly, changes could be happening far away from where the data is being handled and by the magic of JS pass by reference and two way data binding everything would remain in sync. That’s not the done thing nowadays.
Why do you want to pass in a crate and then manipulate it from the outer environment?

Thanks for explaining it. There is no use case for manipulating a crate from the outer environment yet.
It's just that from the user (of the Vue compoment) perspective, the convention is that a v-model binding to a component is usually two-ways. The one-say binding is normally done via {{ xxx }} and v-once. All the exisiting Vue component's library conforms to that convention, eg: element plus, naive ui, etc.
An example of the more complex component is an editable table such as: https://b-editable-table.muhimasri.com/guide/basic-usage.html
A user would expect that an object bound via a v-model will get an update from any changes to a cell and vice versa.

https://vuejs.org/guide/components/props.html#one-way-data-flow


15 php cs fixer issues

#15 Adding php-cs-fixer config, and changes from running said config

@stelgenhof I think I'm happy with this now :)
To summarize the changes in this PR

I adjusted the list to only include PSR based fixers
I've also added a shortcut command to composer composer php-cs-fixer which runs the fixers.
I've php-cs-fixer now also runs on the CI server, meaning PRs will need to be PSR2 compliant before they can be merged.

Also, a note about the tests directory and namespaces, it appears to be part of PSR4

The contiguous sub-namespace names after the "namespace prefix" correspond to a subdirectory within a "base directory", in which the namespace separators represent directory separators. The subdirectory name MUST match the case of the sub-namespace names.

Which is a requirement of PSR2 as far as I understand it

I think the contiguous sub-namespace requirements was the culprit I believe. Let me check once more and merge your PR

Would you mind changing the "tests" folder back to uppercase? I prefer the sub-namespaces to be consistent. If not, I can do it after merging the PR :)
As for - ./vendor/bin/php-cs-fixer --diff --dry-run -v fix, you said it will run on the CI server however this is just a dry-run. Any reason for that?

@stelgenhof would you want to change the actual directory from tests to Tests?  at least that way it does align still align with PSR4

Ah indeed. Then I would leave it as you did. No need to change. I will merge it

Alright, go ahead. I'll need to update my other pull request to meet the new CS requirements :)


Error thrown when no recording file exist but test uses a recorded variable is confusing

Fixed in https://github.com/Azure/azure-sdk-for-net/pull/34790


Responses

Currently we send IBIS commands in a fire-and-forget fashion and do not check for responses.
We should read up on how responses are formatted and what information they convey. When appropriate, we should notify users about errors we receive from the IBIS devices.

We do have responses now for the status command and for flashing.
We do not yet consider responses for the destination command because it is not known how they should look like. It's also possible that no response should be expected. We will have to gather more data to also fix this for the destination command.


⚠ Samsung has degraded performance

In d858d6e, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2593 ms

Resolved: Samsung performance has improved in bbdf393.


[Android BUG] On real android devices execution fails

Environment
Environment:
OS: Windows 10
Node: 8.11.3
Yarn: 1.6.0
npm: 6.4.1
Watchman: Not Found
Xcode: N/A
Android Studio: Version  <IP_ADDRESS> AI-181.55<IP_ADDRESS>56338
Packages: (wanted => installed)
react: 16.3.1 => 16.3.1
react-native: 0.55.4 => 0.55.4
React Native Environment Info:
System:
OS: Windows 10
CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Memory: 2.84 GB / 7.91 GB
Binaries:
Yarn: 1.6.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.4.1 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-181.55<IP_ADDRESS>56338
Description
When I run react-native run-android on an Android Studio's simulator (Nexus 5x Android version 6.0) it works fine as expected. When I connect my real device (Asus ZOOLD Android version 6.0.1) and try to open my app the folowing exception is thrown:
"undefined is not an object (evaluating 'c.Aspect.fill')"
I can't identify the module which is causing this and why it is causing this just on real devices.
Can anyone help me out with that?
Thank you in advance.
 Include a code sample, share a project, or     share an app that reproduces the issue using https://snack.expo.io/. Please follow the guidelines for providing a MCVE: https://stackoverflow.com/help/mcve

@react-native-bot now it throws the error:
React Native version mismatch
JavaScript version: 0.55.4
Native version: 0.57.7
I've looked for that Exception on other issues but none of them help me out.

How did you upgrade your project? It looks like there is a mismatch.

@hramos @react-native-bot I got my project back to the point where I first asked for help, before upgrading.
Now I just tried to upgrade again as @react-native-bot suggested, that is how I did it:
I followed these instructions: https://facebook.github.io/react-native/docs/upgrading
When running  react-native-git-upgrade I get the following output:

The file will have its original line endings in your working directory
git-upgrade info Commit old version template
git-upgrade info Install the new version
error Command failed.
Exit code: 1
Command: git
Arguments: pull
Directory: C:\Users\Caio\AppData\Local\Yarn\Cache\v4.tmp\8e3ea0e4ce65ad4695e1b94666353714
Output:
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=<remote>/<branch> master

git-upgrade ERR! An error occurred during upgrade:
git-upgrade ERR! Error: Command 'yarn add<EMAIL_ADDRESS><EMAIL_ADDRESS>exited with code 1:
stderr: undefinederror Command failed.
Exit code: 1
Command: git
Arguments: pull
Directory: C:\Users\Caio\AppData\Local\Yarn\Cache\v4.tmp\8e3ea0e4ce65ad4695e1b94666353714
Output:
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.
git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:
git branch --set-upstream-to=<remote>/<branch> master

stdout: yarn add v1.12.3
[1/4] Resolving packages...
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
at ChildProcess.child.on.code (C:/Users/Caio/AppData/Roaming/npm/node_modules/react-native-git-upgrade/cliEntry.js:58:18)
at ChildProcess.emit (events.js:182:13)
at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)

git-upgrade ERR! Restore initial sources
Note: checking out 'project-snapshot'.
You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.
If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:
git checkout -b
HEAD is now at 0468ca9 Project snapshot

Should not  react-native-git-upgrade itself take care of tracking the remote repository?
How do I fix it?
Thanks