adapter doesn't stay active

Hi, unfortunately I do not get the adapter to run. Could you please have a look:
Describe the bug
Starting the adapter works for about 10sec then it turns red
Screenshots & Logfiles
freeathome.0 | 2023-08-01 20:04:18.699 | error | Error: The state contains the forbidden properties type, common, native! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5675:23) at Freeathome.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5758:21) at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2126:16 at new Promise () at Freeathome.setStateAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2125:16) at /opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:279:48 at Array.forEach () at FreeAtHomeApi.addDeviceToioBroker (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:266:74) at runNextTicks (node:internal/process/task_queues:60:5) at process.processImmediate (node:internal/timers:447:9)
freeathome.0 | 2023-08-01 20:04:18.696 | error | unhandled promise rejection: The state contains the forbidden properties type, common, native!
freeathome.0 | 2023-08-01 20:04:18.695 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
freeathome.0 | 2023-08-01 20:04:18.673 | warn | Terminated (UNCAUGHT_EXCEPTION): Without reason
freeathome.0 | 2023-08-01 20:04:18.672 | info | terminating
freeathome.0 | 2023-08-01 20:04:18.669 | info | Stopping free@home API
freeathome.0 | 2023-08-01 20:04:18.638 | error | The state contains the forbidden properties type, common, native!
freeathome.0 | 2023-08-01 20:04:18.638 | error | Error: The state contains the forbidden properties type, common, native! at validateSetStateObjectArgument (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5675:23) at Freeathome.setState (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/build/lib/adapter/adapter.js:5758:21) at /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2126:16 at new Promise () at Freeathome.setStateAsync (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2125:16) at /opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:279:48 at Array.forEach () at FreeAtHomeApi.addDeviceToioBroker (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:266:74)
freeathome.0 | 2023-08-01 20:04:18.634 | error | unhandled promise rejection: The state contains the forbidden properties type, common, native!
freeathome.0 | 2023-08-01 20:04:18.633 | error | Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
As the adapter restarts everytime this going to repeat over and over until I manually stop the adapter
Versions:
•	platform: linux11/bullseye
•	architecture: arm
•	Node.js: v18.17.0
•	NPM: 9.6.7
•	js-controller: 4.0.24
•	adapter version: 0.0.18
•	Sysap v1 version: v2.5.0
Thanks very much in advance.

I have the same problem. Maybe it´s the Node.js version?

I have the same problem after update from 0.11 to 0.18. Did you have an idea?

As AceTecNic already mentioned I'd also guess that's most probably a Node.js version issue

Does anyone know how to downgrade the nodejs?
Would like to try it on my raspi with an older version like 14 or 12
But it every time I check the version with node -v it's 18
bitteeingit @.***> schrieb am Mo., 14. Aug. 2023, 07:49:

As AceTecNic already mentioned I'd also guess that's most probably a
Node.js version issue
—
Reply to this email directly, view it on GitHub
https://github.com/mobilutz/ioBroker.freeathome/issues/654#issuecomment-1676718879,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJPDYNMMQKAAOGPMLFUQ45TXVG37VANCNFSM6AAAAAA3AFEGDA
.
You are receiving this because you commented.Message ID:
@.***>

Does anyone know how to downgrade the nodejs? Would like to try it on my raspi with an older version like 14 or 12 But it every time I check the version with node -v it's 18 bitteeingit @.> schrieb am Mo., 14. Aug. 2023, 07:49:
…
As AceTecNic already mentioned I'd also guess that's most probably a Node.js version issue — Reply to this email directly, view it on GitHub <#654 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJPDYNMMQKAAOGPMLFUQ45TXVG37VANCNFSM6AAAAAA3AFEGDA . You are receiving this because you commented.Message ID: @.>

You can use nvm. Here is a good tutorial: https://www.howtoforge.de/anleitung/wie-man-nvm-unter-debian-11-installiert-und-verwendet/
I have node V14.18.2 and this problem.
Which node version is the right one?

Thanks @daskleinec, i have changed to version 12.22.12 but if i start IOB, it shows me still 18.xx.xx
Whatever, did you tried the f@h adapter with your 14.18.2 and it doesn´t work too?
I think the adapter is broken... hopefully that @mobilutz can fix it. I really want to use it.

I have tested an another f@h adapter.
https://github.com/hohmannc85/ioBroker.bjfreeathome
This adapter works fine :)

I have the same problem.
Node.js: v18.17.1
NPM: 9.6.7
Unfortunately this adapter (https://github.com/hohmannc85/ioBroker.bjfreeathome) has the same issue in my environment, it only takes some more time to disconnect.
Any chance to get this fixed?

I have the same problem. Node.js: v18.17.1 NPM: 9.6.7
I got the same version on my RPi4

Unfortunately this adapter (https://github.com/hohmannc85/ioBroker.bjfreeathome) has the same issue in my environment, it only takes some more time to disconnect.
Any chance to get this fixed?
Did you set up a new profile in f@h with api acces? I´ve created a new profile as root with full acces - then you ned the api login-phase from f@h (generated automatic.) and your login password.

Did you set up a new profile in f@h with api acces? I´ve created a new profile as root with full acces - then you ned the api login-phase from f@h (generated automatic.) and your login password.

That was a good tip. I had already created a new user and used the automatically generated login name. But with that I never got a connection and had then used the installer as user instead. But with this the adapter was not permanently connected.
When I checked again today, I noticed that the newly created user had no API rights. In Sysap quickly given the right, so the other here linked adapter from hohmannc85 was then actually stable.
Then today I was offered an update in Sysap and I updated my Sysap 2.0 to version 3.2.0. I had the hope that it might improve the functionality with the adapter from mobilutz.
Unfortunately, the opposite was the case. With the adapter from mobilutz I now get no connection at all. With the other  adapter from hohmannc85 it looks no better. This now crashes completely after a few seconds.
Error messages:
obj_sub5.replace is not a function
bjfreeathome.0
2023-08-21 13:00:33.478	error	TypeError: obj_sub5.replace is not a function at /opt/iobroker/node_modules/iobroker.bjfreeathome/main.js:350:124 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
bjfreeathome.0
2023-08-21 13:00:33.478	error	unhandled promise rejection: obj_sub5.replace is not a function
bjfreeathome.0
2023-08-21 13:00:33.478	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
With the new Sysap version both adapters do not work anymore.
There is a note in the release notes:
local API availability for System Access Points version 1 and 2
Unfortunately there is no further information about this.

Hello @everyone
I am sorry to hear that the adapter does not work anymore.
My guess right now is, that it has to do with some dependency update.
As I am not running ioBroker anymore at my house, I didn't see the error yet.
I will try to look into this during this week, but as all OpenSource contributors always say: I cannot guarantee it.
Until then, did anyone try to downgrade to a lower version number to see if things work there?

@Deberk pls create an issue at https://github.com/hohmannc85/ioBroker.bjfreeathome too for this problem.
Can you try to downgrade the SysAp to 3.0.1 or so? Don´t know the version from mine but it was a little bit higher than 3.x.x
@mobilutz @daskleinec got a lower version 14.x.x but it doesn´t work too.
If you need someone to try anything with iob and your adapter, feel free to ask me.
Until then: Thanks for your work!

@Deberk pls create an issue at https://github.com/hohmannc85/ioBroker.bjfreeathome too for this problem.
Can you try to downgrade the SysAp to 3.0.1 or so? Don´t know the version from mine but it was a little bit higher than 3.x.x

I`ve opend an issue.
Trying a downgrade tomorrow.
@mobilutz: Awsome, hope ypu can find and fix the issue. :-)
Many Thanks in advance!!

@mobilutz @daskleinec got a lower version 14.x.x but it doesn´t work too.

I don't mean to downgrade node, but this adapter.
But nevertheless, I will try to look at it.

Maybe it is helpful for this issue, too.
hohmannc85 got his adapter fixed today.
Comments: "fixed the first problem; but now the web socket connection is closing after one minutes. I am on it." + "BJ changed something in timeout of Websocket. this is a problem I have to look somewhen. the connection will be lost for 1 sek in a minute, states and everything will be refreshed. "

hi, i have an old SysAp and tried to use the adapter from https://github.com/hohmannc85/ioBroker.bjfreeathome
is this adapter compatible with my SysAp since i can not get it working.
Thanks

@everyone
I finally got the adapter to work, and stumbled over some things which I need to fix.
A couple of them had been quiet easy, but now I am stuck a bit.
I will work on this, and keep you guys updated. But as said before, I don't know when I can fix things.
Next update will hopefully be better.
PS: I am still running the SysAP with Version 2.6.4 and don't plan on updating. So if there is anyone who can support me when there is a new version to test things out would be great.

And now, after writing this comment, I have a working adapter, at least for the SysAP with Version 2.6.4
@bitteeingit (and others as well) could you please try with the newest version v0.0.20:
https://www.npmjs.com/package/iobroker.freeathome
Thanks

hi,
hab grad getestet, bei mir kommt folgender error.
st.raspberrypi
2023-08-27 10:08:08.974	error	instance system.adapter.freeathome.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
freeathome.0
2023-08-27 10:08:08.296	error	Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle
freeathome.0
2023-08-27 10:08:08.295	error	TypeError: Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle at JSON.stringify () at FreeAtHomeApi.broadcastMessage (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:203:60) at Client. (/opt/iobroker/node_modules/freeathome-api/dist/lib/SystemAccessPoint.js:92:29) at Client.emit (node:events:525:35) at /opt/iobroker/node_modules/@xmpp/middleware/index.js:19:30 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
freeathome.0
2023-08-27 10:08:08.291	error	unhandled promise rejection: Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle
freeathome.0
2023-08-27 10:08:08.289	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
host.raspberrypi
2023-08-27 10:07:27.853	error	instance system.adapter.freeathome.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
freeathome.0
2023-08-27 10:07:27.193	error	Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle
freeathome.0
2023-08-27 10:07:27.191	error	TypeError: Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle at JSON.stringify () at FreeAtHomeApi.broadcastMessage (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:203:60) at Client. (/opt/iobroker/node_modules/freeathome-api/dist/lib/SystemAccessPoint.js:92:29) at Client.emit (node:events:525:35) at /opt/iobroker/node_modules/@xmpp/middleware/index.js:19:30 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
freeathome.0
2023-08-27 10:07:27.187	error	unhandled promise rejection: Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle
freeathome.0
2023-08-27 10:07:27.185	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
freeathome.0
2023-08-27 10:06:53.908	error	adapter disabled
host.raspberrypi
2023-08-27 10:06:25.886	error	instance system.adapter.freeathome.0 terminated with code 6 (UNCAUGHT_EXCEPTION)
freeathome.0
2023-08-27 10:06:25.236	error	Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle
freeathome.0
2023-08-27 10:06:25.234	error	TypeError: Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle at JSON.stringify () at FreeAtHomeApi.broadcastMessage (/opt/iobroker/node_modules/iobroker.freeathome/lib/freeathome.js:203:60) at Client. (/opt/iobroker/node_modules/freeathome-api/dist/lib/SystemAccessPoint.js:92:29) at Client.emit (node:events:525:35) at /opt/iobroker/node_modules/@xmpp/middleware/index.js:19:30 at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
freeathome.0
2023-08-27 10:06:25.229	error	unhandled promise rejection: Converting circular structure to JSON --> starting at object with constructor 'Element' | property 'children' -> object with constructor 'Array' | index 0 -> object with constructor 'Element' --- property 'parent' closes the circle
freeathome.0
2023-08-27 10:06:25.227	error	Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

Hi @mobilutz ,
thank you for your support! The update works fine with my configuration node V14.18.2 and npm 9.8.1.
Thank you in advance for help us because you don't use IOB anymore!
Kind regards - Christian

My SysAp is on 3.0.2
Could this be the problem?
Can I somehow downgrade maybe?

And now, after writing this comment, I have a working adapter, at least for the SysAP with Version 2.6.4
@bitteeingit (and others as well) could you please try with the newest version v0.0.20: https://www.npmjs.com/package/iobroker.freeathome
Thanks

Hi @mobilutz,
First, thank you for taking care of my request even though you are not using IOB anymore!
I am not able to test your fix before next week. For sure I will give feedback then.

First of all, thank you very much for the work.
Unfortunately it doesn't work for me either, but my sysap is on 3.2.0.
As I just read, the rollout for version 3.2.0 was probably stopped again by BJ due to bugs.
A downgrade is according to a message from BJ unfortunately probably not possible.
QUOTE:
"UPDATE: Dear Community, Quality is our utmost priority and despite ample testing beforehand, we have received feedback in the last few hours that has caused us to halt the roll-out of the firmware for the moment. We will keep you updated here on the progress and thank you for your valuable input."
"...Unfortunately, a downgrade is not possible...."


IDVA5-496-unincorporated-business-address-manual

Adding unincorporated What is the business address manual screen

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found

CI: No security warnings found


Export string sets in monitoring infos. (#31838)

This is a cherry pick of https://github.com/apache/beam/pull/31838

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

@robertwb is this precommit failure expected? The same failure happened on your original PR, but it looks like master is green afterwards

nevermind, the 6th run seems to have passed. strange flake


GUROBI_LIN

This partially addresses issue #168 by adding a Gurobi interface to solve LPs.  A couple of tests are included.
Still to do (ordering based on my priorities):

Add warm start capability.  After reading the scs_intf.py code, I have a good idea how to do this.  However, I have a couple questions:
A. I see some tests in test_solvers.py, for example test_ecos_options, which set the warm_start option.  I don't see any sort of assertion that warm starting is actually working, though.  Is there a way to assert this?
B. For performance reasons, I would prefer to sparsely update constraints which have changed from the previous run.  Is there a way to get that information through CVXPY somehow?  Or do I need to compute that myself?

Add capability for other classes of problems (this is a much lower priority for me than warm start).  If someone can describe and point me to (or write) tests that should pass with Gurobi for other classes of problems, I can try and write the code in the interface.  I'm definitely open to contributions from other people to get this working.

In terms of Travis integration, I'm not sure what the best thing to do is.  Gurobi does offer free academic licenses.

Coverage decreased (-0.84%) to 95.52% when pulling 63876dc0475b204f001cc00a39e6961a3c79a465 on macklin:gurobi_lin into 5c053d7eb20fa2caf0e47a19438a506a1733b110 on cvxgrp:master.

Coverage decreased (-0.94%) to 95.42% when pulling 38592c32401f3a72b25bea2ff344842bd5e52ac3 on macklin:gurobi_lin into 5c053d7eb20fa2caf0e47a19438a506a1733b110 on cvxgrp:master.

Commit 38592c3 adds a test to catch a bug I had in 63876dc: Gurobi's default lower bound on a decision variable is zero.  The bug is fixed in c6e4f08.

Coverage decreased (-1.19%) to 95.17% when pulling 38592c32401f3a72b25bea2ff344842bd5e52ac3 on macklin:gurobi_lin into 5c053d7eb20fa2caf0e47a19438a506a1733b110 on cvxgrp:master.

Commit e58b969 has warm starting capabilities where I assume that CVXPY does not provide me any information on constraints that have changed.  While I've included some tests for the output (more tests should definitely be written), none of them assert that Gurobi is actually warm starting internally (I'm not timing anything).

Coverage decreased (-2.62%) to 93.74% when pulling e58b969f597d455daa1a5854eb348389e85ee6c1 on macklin:gurobi_lin into 5c053d7eb20fa2caf0e47a19438a506a1733b110 on cvxgrp:master.

This is phenomenal! I emailed the developers of JuMP and mathprogbase to see if they had any ideas about testing Gurobi in travis. I'll look into this myself also.
You're right that warm start isn't really being tested. One idea I had was to see if a solver converges in one iteration when it's warm started with the solution (or less robustly, whether the warm started solve is faster than the original solve). I didn't get too far with this because there's something wrong with how cvxpy is warm starting SCS.
It looks like you found a good solution for sparsely updating the Gurobi constraints. You could potentially use Parameters for this too. Could you give me an example snippet from your code where you're updating constraints at the CVXPY level?
It looks like Gurobi can solve SOCPs and mixed-integer SOCPs, which would also capture QPs and mixed integer QPs:
https://github.com/JuliaOpt/gurobi.jl
That would be really useful!

I have some tests in test_gurobi_lin_warm_start() in test_solvers.py that demonstrate updating constraints at the CVXPY level using Parameters.  Do Parameters provide information about values that have been updated (something that I could use in my code rather than calculating changes myself)?

Right now what Parameters provide is a way for cvxpy to know which values it can cache and which might change across solves. So the assumption is that any values derived from a Parameter may have changed. There's no way right now to see which Parameters in particular have changed. This might be worth adding.
To see if a constraint contains parameters, you can use this snippet:
import cvxpy.lin_ops.lin_utils as lu
len(lu.get_expr_params(constr.expr)) > 0

Do you need the ability to change all parts of your problem efficiently? Or would it be enough to use Parameters to isolate a subset of values that might change and update them on every solve?
I'm not a huge fan of the "update_objective", "update_eq_constr", etc. solver options, since (if I understand correctly) they may cause cvxpy to solve a different problem then is currently stored in the Parameters.
I heard back from the JuMP/mathprogbase developers, and they didn't have any ideas for doing CI with Gurobi. I've emailed Gurobi support to see if we can get a special license.

I could definitely construct my problems to only use Parameters for values which might change.  I agree that that'd be a cleaner approach than the update_* solver options that I currently have.
Using the snippet you provided, I can figure out if a constraint contains Parameters.  But then I need to know where that constraint gets mapped in A, b, G, or h.  Is there a way to do that?

You can currently get the matrix entries associated with parameterized constraints. Here's code to do it:
# Inside the solver interface.
# Get the data relating to the problem matrices.
matrix_data = self.get_matrix_data(objective, constraints, cached_data)

# Check if the objective must change.
if len(lu.get_expr_params(objective)) > 0:
   Redo the objective because it's all parameterized.

# Get the parameterized part of the equality constraints.
eq_cache = matrix_data.get_param_cache(matrix_data.eq_cache)
eq_cache.coo_tup # A (V, I, J) triplet for the parameterized matrix.
eq_cache.const_vec # The parameterized vector offset.

# Get the parameterized part of the inequality constraints.
ineq_cache = matrix_data.get_param_cache(matrix_data.ineq_cache)
ineq_cache.coo_tup # A (V, I, J) triplet for the parameterized matrix.
ineq_cache.const_vec # The parameterized vector offset.

This gives V, I, J triplet for all the parameterized entries in the different matrices. It also gives the parameterized vector offset. The problem is that in the vector offset zero-valued entries could be parameters that evaluated to 0 or from the initialization of the vector. So you can't tell which part of the vector offset was updated by the parameters.
I tried storing the vector offset as a V, I, J triplet, but that made cvxpy substantially slower.

I heard back from Gurobi, and they aren't willing to give a license for us to use on travis CI. Apparently all their licenses are either tied to a machine or a LAN. I'm alright with not testing the Gurobi integration in travis. At least we'll know the Gurobi code doesn't break anything else.
I'm away from Stanford right now, so I can't use Gurobi. I'll test this PR when I get back to campus.

Haven't had a chance to incorporate the Parameters yet. Hopefully by the end of this week.

I merged in the PR by hand. cvxpy now supports gurobi! Thanks for doing such a great job putting this together.
The only thing I changed is that I removed the update_* keywords and instead had cvxpy assume that part of the problem had changed if and only if it contains parameters. Philosophically I'm against telling cvxpy to solve a different problem then you've specified.
I'll work on adding MI and SOCP support through gurobi.

Ok, thanks!  Sorry I didn't get around to implementing those changes myself--haven't had a chance to work on it recently.


IPv6 ping problem

ping for ipv6 assumes addresses z/xx but this is in general not true. In ipv6 we can have also z/xxx addresses. Moreover, I suggest to move the parameters from 'v6Addr' to a more immediate 'ipv6'.
ip, prefixLen = dest.params.get('ipv6', []).split( '/' )
result = node.cmd( 'ping6 -c1 %s -I %s %s' % (opts, node.intfs.get(0), ip))

my bad...QA uses a different version of Mininet

They really shouldn't.


Implement AAE strategy.

Implement an active anti-entropy strategy to repair variables which didn't get updated during quorum operations because of partial failure.

No longer necessary.


Formidable doesn't seem's to close open files uploaded from web workers

Hi,
I have an issue with Node-Formidable but I don’t know if it’s a bug or if it’s related to the way I’m trying to use it. I would need some help to find it out.
I’m using web workers to chunk and upload large file. As FormData() isn’t available in web workers, I have to send the chunk directly inside the xhr command.
Node-Formidable receive and write the chunk to disk but it seem’s to leave the files stream open because I’m hitting the node process ulimit and it crashes throwing the EMFILE error…
On my system I have the error at around 230 chunks as my ulimit is 256. This doesn’t append when I using FormData directly from the .html file but I cannot using it that way because it create others issue related to high CPU usage by the browser after the upload is complete and web workers solve that.
You can reproduce by using this code and a file large enough to generate more chunks that your uLimit :
app.js :
var http = require('http');
var formidable = require('formidable');
var fs = require('fs');
var path = require('path');
var i = 0;

http.createServer(function(req, res){
    if(req.method.toLowerCase() == 'get'){
        if(req.url != '/favicon.ico'){
            res.writeHead(200, {'Content-Type' : resolveType(req)});

            var url = __dirname;

            if(req.url == '/'){
                url += '/views/index.html';
            }
            else {
                url += '/public' + req.url;
            }

            var readStream = fs.createReadStream(url).pipe(res).on('error', function(o_O){
                console.log(o_O);
            });
        }
        else{
            res.end();
        }
    }

    if(req.method.toLowerCase() == 'post' && req.url == '/upload'){
        var form = new formidable.IncomingForm({
            uploadDir: './tmp/'
        });

        form.parse(req, function(err, fields, files){
            if (err){
                console.error(err.message);
                return;
            }

            if (files.file){
                console.log('Upload complete - Chunk '+ i +' file : '+ files.file.path);
                i += 1;
            }

            res.writeHead(200, {'content-type': 'text/plain'});
            res.end('upload complete : chunk #'+ fields.chunk);
        });
    }
}).listen(3000, function(){
    console.log("Express server listening on port 3000");
});

var resolveType = function(req){
    var extension = path.extname(req.url);

    if(extension == 'js'){
        return 'text/javascript';
    }
    else{
        return 'text/html';
    }
};

/views/index.html :
<html xmlns="http://www.w3.org/1999/xhtml">
    <head>
        <meta http-equiv="content-type" content="text/html;charset=ISO-8859-1">
    </head>

    <body>
        <div>
            <input type="file" id="afile" class="button">
        </div>

        <script type="text/javascript">
            var worker = new Worker('/worker.js');

            worker.onmessage = function(e) {
                console.log(e.data);
            };

            worker.onerror = function(e) {
                console.log(JSON.stringify(e));
            };

            document.querySelector('input[type="file"]').addEventListener('change', function(e) {
                worker.postMessage(this.files);
            }, false);
        </script>
    </body>
</html>

/public/worker.js :
var uploaders=[];

self.onmessage = function(e){

    var blob=e.data[0];
    var slice = blob.slice || blob.webkitSlice || blob.mozSlice;

    const BYTES_PER_CHUNK= 131072; //128kb chunk so a 40MB files should trigger the EMFILE error for a uLimit at 256.
    const SIZE=blob.size;

    var start=0;
    var end=BYTES_PER_CHUNK;

    while(start<SIZE){
        upload(slice.call(blob, start,end));

        start=end;
        end=start+BYTES_PER_CHUNK;
    }
}

function upload(blobOrFile){
    var last = 0;
    var newChunk = true;

    var xhr=new XMLHttpRequest();

    xhr.open('POST', '/upload', true);
    xhr.setRequestHeader("Content-Type", "application/octet-stream");

    xhr.onload=function(e){
        uploaders.pop();

        if(!uploaders.length){
            self.postMessage('UPLOAD DONE!!!');
            self.close()
        }
    };

    uploaders.push(xhr);
    xhr.send(blobOrFile);
}

What are my options to have node formidable to close these files after the upload ?
Thank you,
Eric

Hi @Elanouette
Though the question is pretty old, but could you remember whether it got fixed or not, or how you fixed it?Or perhaps it has already been fixed in newer lib versions?
My first guess is that this is a bug in Formidable i.e. not handling ulimit, but your response could help us.
Thanks.

Use 'Content-Type': 'multipart/form-data'  (this is done automatically so don't do anything)
you cannot use xhr.send(blobOrFile); directly, instead use the FormData API
const formData = new FormData();
formData .append("fileField", blobOrFile);
xhr.send(formData);

FormData was added to Web Worker recently


Implement Capybara

I've decided to stick with @david-a-wheeler 's recommendation and forego RSpec, Cucumber, and Factory Girl for the simpler Minitest and fixtures.
I'm still planning to add Capybara to be able to do real browser testing.
https://github.com/blowmage/minitest-rails-capybara

Sam completed this.  Thank you!


taking out comments in grammar

This PR:

un-comments portions of annotated_lambda that increases parsing to 97%.
adds the case where else comes after a newline following the if control body into scanner.cc

To test, run npx tree-sitter test
cc: @aryx

Yes for the get/set I'm not sure it's good enough to do it via scanner.c, because you can also get modifiers
before, so I think it's simpler to do it in an ugly way like I did in my PR.
Regarding 'else', I think we could do what you proposed!

I see, didn't think about the case where you get modifiers before, so makes sense that we do it through grammar.js and not scanner.c.
Cool! I'll add the else case back into scanner.cc with the test cases!

messed up the commit history for this, I'm going to make a new PR!


'each' has deprecated since php 7.2

I used phpcbf check the code compatibility of guzzle/promises.  And it warned me like this:
../PHP_CodeSniffer/bin/phpcs --extensions=php --standard=PHPCompatibility --runtime-set testVersion 7.4 ./vendor/guzzlehttp/

FILE: vendor/guzzlehttp/promises/src/functions.php
-----------------------------------------------------------------------------------------
FOUND 0 ERRORS AND 3 WARNINGS AFFECTING 3 LINES
-----------------------------------------------------------------------------------------
 222 | WARNING | Function each() is deprecated since PHP 7.2; Use a foreach loop instead
 257 | WARNING | Function each() is deprecated since PHP 7.2; Use a foreach loop instead
 313 | WARNING | Function each() is deprecated since PHP 7.2; Use a foreach loop instead
-----------------------------------------------------------------------------------------

Time: 751ms; Memory: 10MB

Thank you for informing us.
We are not using php's each() anywhere =)

Btw, This might be interesting for you #102


ColorManager take 2 (w/ pydantic)

Description
This PR introduces a ColorManager class to manage the color setting behavior on the annotation layers (e.g., Points, Shapes). ColorManager is implemented as a pydantic EventedModel. We will add the ColorManager to the Points layer to demonstrate how it is integrated and then hook it up to other layers in a follow up PR.
Type of change

[x] Bug-fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

References
This PR supersedes #1940 .
How has this been tested?

[x] added tests for ColorManager
[x] all tests pass with my change

Final checklist:

[x] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works

Love this @kevinyamauchi it looks like it is coming along really nicely. I see it is still marked as WIP/ draft, are there more things you want to do with this before review?

Hey @sofroniewn! I think this PR is almost ready for a first review. I'd like to finish hooking ColorManager up to the Points layer to demonstrate how to implement it. I like the EventedModel so far!

Hey @sofroniewn , this is ready for a first round of review. Thanks for your patience with this one. I've been pretty swamped with the job change and I haven't been able to put as much focused effort on this as I'd have liked.
structure
I am curious to hear your thoughts on how I've structured the ColorManager. I found it a bit challenging at first to balance the strictness of dataclasses and pydantic models with the flexibilty of our color API. What I settled on is that the ColorManager itself stores the state of the parameters to set the colors and calculates the colors from those parameters. A lot of the code that turns the user inputs into the ColorManager inputs is in functions outside of ColorManager (e.g., code to determine if a user gives a property name as a color, they want to map the color to that property). For example, see the initialize_color_manager() function in napari/layers/utils/colormanager.py. Doing so allows the ColorManager to just know about the things it needs to determine colors and the abstraction gives us a bit more flexibility in the user facing API than the EventedModel easily allows.
I wasn't really sure if those convenience functions should be on the ColorManager or as separate functions that take the ColorManager object and modify it. For example, initialize_color_manager()function innapari/layers/utils/colormanager.pycould potentially be a class method that serves as an alternative constructor (e.g.,ColorManager.from_layer_kwargs). Similarly, some convenience functions are on ColorManager(e.g.,ColorManager.update_current_color()) that could be separate functions that take both the ColorManager object and the necessary parameters and then just update the `ColorManager. It's a bit of a mixed bag at this point because my thinking changed over the course of writing the PR, but we should probably land on a consistent style.
refresh
Another questions I have is regarding the refresh_colors() method that we had previously used to force an update of the colors. It is no longer  necessary because the EventedModel recalculates the colors each time a color parameter is changed. However, there can be times when I could see a user would want to force a refresh because they've skipped a setter method. For example, if a user updates a property via layer.properties['prop_key] = new_values, this doesn't use the layer.properties setter and thus doesn't trigger an update of the ColorManager.color_properties. I think we should discourage users from manipulating values in this way (this would break any other behavior that depends on the layer properties), but we support it now, it would potentially be a breaking change to remove Points.refresh_colors
general
In any case, there are a few things I am excited about with this version:

JSON serialization works (search for json in the test_color_manager.py for some rounnd trip examples)
we don't really need to break the current API and we will seriously reduce the amount of duplicated code
almost all of the color handling is now off of the layer model.

I was thinking last night @kevinyamauchi that when we do the follow up PR to deprecate old methods and expose this colormanger publicly we could actually do so under layer.edge and layer.face, so we'd get layer.edge.colors, layer.edge.current_color. What's so nice about that (instead of exposing at layer.edge_color) is that we can deprecate everything is a really clean way!!

Thank you for the reviews, @tlambert03 and @sofroniewn ! I agree that it makes sense to move the set_color() onto ColorManager and implement initialize_color_manager() as a from_<stuff> class method. I can also move the __eq__ methods onto the colormaps and see if #2232 fixes the rest of the equality checks. I was slammed with other stuff today, but I should be able to address those points tomorrow.

I was thinking last night @kevinyamauchi that when we do the follow up PR to deprecate old methods and expose this colormanger publicly we could actually do so under layer.edge and layer.face, so we'd get layer.edge.colors, layer.edge.current_color. What's so nice about that (instead of exposing at layer.edge_color) is that we can deprecate everything is a really clean way!!

Nice! I like it.

@sofroniewn , I think I have addressed most of the comments and it would be helpful to get a bit of feedback with regard to moving the ColorManager to the Points.edge and Points.face

Should the Points.face and Points.edge properties have a setter?
I am wondering if we should make some of the ColorManager properties private. For example, current_color and color_properties. ColorManager.current_color shouldn't be directly modified by the user since ColorManager needs to know  if points are selected to properly update the colors (it should be modified by on the layer). Similarly, the user shouldn't be modifying color_properties because that should be handled by the layer. What do you think?

I think the remaining items are:

improve test coverage on the new code
break up some of the larger functions, as suggested by @tlambert03
add deprecation warnings

Very nice @kevinyamauchi!!

Should the Points.face and Points.edge properties have a setter?

No I don't think so

I am wondering if we should make some of the ColorManager properties private. For example, current_color and color_properties. ColorManager.current_color shouldn't be directly modified by the user since ColorManager needs to know if points are selected to properly update the colors (it should be modified by on the layer). Similarly, the user shouldn't be modifying color_properties because that should be handled by the layer. What do you think?

I'd say if in doubt make it private. I'd much rather start with many more private attributes that we slowly expose and have just the bare minimum be public, so making both of those private sounds good to me.

Thanks for the quick feedback, @sofroniewn ! I should be able to make the final changes on Monday and this PR will be ready for review!

@sofroniewn , I have rounded out the test coverage and refactored the code a bit. I am a bit unsure what to do about the private fields. It looks like private attributes get excluded from the model fields, which I don't think we want (e.g., as I understand it, they don't get validated). My thought with making some of the fields private (e.g., current_color) is that we should communicate to the user which fields can safely modify themselves. I think we can set the Config.underscore_attrs_are_private to False and variables with leading underscores will get treated like normal fields. We would then have to wrap fields we want to be private with PrivateAttr. This seems reasonable to me, but it would be something we would want to standardize across napari. Thoughts?
Otherwise, I think this is ready for review. I am looking forward to hearing your thoughts!

Thank you for the reivews, @sofroniewn and @tlambert03 ! I have addressed @sofroniewn 's comments and I will address @tlambert03 's tomorrow.
By the way, @tlambert03 , I think being able to add json encoders and discoverable validators to the EventedModel is really nice!

I have addressed @tlambert03 's comments with the exception of this comment.
I think the next steps outlined by @sofroniew make sense to me. I have updated #1727 with the action items so we can track them. I think we should wait to do the deprecation notices until we've put ColorManager on all layers so that we can make sure a uniform public API works for all layer types that use ColorManager.

Thanks for the reviews and feedback, @sofroniewn and @tlambert03 ! I'm stoked to have this merged!


How to ignore a PR with specific label?

First of all, thanks for this useful Github Actions.
I wonder if able to ignore some PRs from the reminder if if it has some specific labels (for example "Do not remind", "Do no merge"...), or if its PR title contains the WIP keyword?

Hi anticafe, thank you for the feedback. I implemented it in a branch, can you please test it for me?
Edit your yml with
    - uses: davideviolante/pr-reviews-reminder-action@ignorelabel


Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

I am getting this error Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) and app got crashed on some devices like one plus 6 (Android 10) and moto g 10 (Android 11)  . Would you please look into this issue when we are playing exoplayer video .

Issue has resolved , it was due to exoplayer  for playing video.


Add get_user_workspaces to workspace wrapper

Coverage increased (+0.008%) to 97.879% when pulling 5fead43a3d141a9747bdb4397f0819583fa6e05c on MrCreosote:master into 0a480ff102cc655331a8fdd4c3801eab1c7b308e on kbaseIncubator:master.


notify.alexa_media blueprints compatibility

Describe the bug
Using blueprints target selector add entity_id: to line under target: field and target is detected as being blank.
To Reproduce
Create blueprint to use the notify service
Expected behavior
target: to accept a different entity_id: format. The blueprint function has no option that I can find to flatten device list.
Screenshots
None
System details

Home-assistant (core-2021.4.4):
Hassio No
alexa_media  (3.8.6):
alexapy (version from pip show alexapy or HA startup):
Amazon 2FA is enabled (y/n). We will not debug login issues if unanswered: Yes

Logs
Please provide logs. We'll be most likely asking for them anyway.
Additional context
Add any other context about the problem here.

What blueprint are you using?

Garage door open TTS announcer/reminderAuthor: doughecka  Sent from Mail for Windows 10 From: Alan TseSent: Saturday, April 17, 2021 10:14 PMTo: custom-components/alexa_media_playerCc: krestes; AuthorSubject: Re: [custom-components/alexa_media_player] notify.alexa_media blueprints compatibility (#1246) What blueprint are you using?—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.


Update to v1.8.0

In this version

5 packages built with Spack for use on compute nodes:

esmf 8.2.0
moab 5.4.0
nco 5.1.1
tempestextremes 2.2.1
tempestremap 2.1.6

Many packages have been updated.  In addition to moab, nco and tempestremap listed above, notable updates include:

e3sm_to_cmip 1.9.1
geometric_features 0.7.0
mache 1.8.0
mpas-analysis 1.8.0
mpas_tools 0.15.0
xcdat 0.3.3
zppy 2.2.0
zstash 1.3.0

New and improved

e3sm_to_cmip:
E3SM Diags:
MPAS-Analysis: ... More updates can be found here.
NCO:
xcdat:
zppy:
zstash:

Deployment
Deployed on:

[ ] Acme1
[ ] Andes
[ ] Anvil
[ ] Chrysalis
[ ] Compy
[ ] Perlmutter-CPU

Hey @xylar, just a heads up that we released xcdat=0.4.0 yesterday. I don't anticipate another release between now and the release of E3SM-unified 1.8.0.
Can you update the version to 0.4.0 instead? I updated the Confluence page to reflect this as well.

@tomvothecoder, done!


Output synchronized image model with video

This commit will write synchronized image model with output video. This will provide information required to align Shannon video output with lidar and camera data.

Synchronized image models with video frames.


Having trouble creating new K3D local cluster on Intel Mac (v14.6)

Which version of kubefirst are you using?
v2.4.13
Which cloud provider?
k3d (local)
Which DNS?
None specific
Which installation type?
CLI
Which distributed Git provider?
GitHub
Did you use a fork of gitops-template?
No
Which Operating System?
macOS
What is the issue?
Hey team! Having some issues getting k3d up and running on my intel mac (v14.6).
First was getting an error on Installing and configuring Argo CD about being unable to reach argocd.kubefirst.dev . I added it to my hosts file and was able to move on to Configuring Vault, but that's now giving me an error as well:
Error: unable to reach vault over https - this is likely due to the mkcert certificate store missing. please install it via `/Users/kevin/.k1/kubefirst/tools/mkcert -install`

However when I run that, I can see that they are already installed:
The local CA is already installed in the system trust store! 👍
The local CA is already installed in the Firefox trust store! 👍

After troubleshooting with support in Slack, we're hitting a wall with a fresh clean install in trying to create the k3d clusters.
 ERRO[0010] Node k3d-kubefirst-server-0: Failed executing preStartAction 'WriteFileAction': [WriteFileAction] Writing 345 bytes to /tmp/localRe
ERRO[0010] Node k3d-kubefirst-server-0: Failed executing preStartAction 'WriteFileAction': [WriteFileAction] Writing 208 bytes to /etc/rancher/
ERRO[0010] Node k3d-kubefirst-server-0: Failed executing preStartAction 'WriteFileAction': [WriteFileAction] Writing 451 bytes to /bin/k3d-entr
ERRO[0010] Node k3d-kubefirst-server-0: Failed executing preStartAction 'WriteFileAction': [WriteFileAction] Writing 1325 bytes to /bin/k3d-ent
ERRO[0011] Failed Cluster Start: Failed to start server k3d-kubefirst-server-0: Node k3d-kubefirst-server-0 failed to get ready: error waiting
ERRO[0011] Failed to create cluster >>> Rolling Back
WARN[0011] Failed to delete volume 'k3d-kubefirst-images' of cluster 'kubefirst': failed to find volume 'k3d-kubefirst-images': Error: No such
FATA[0011] Cluster creation FAILED, all changes have been rolled back!
 exit status 1

Additional context in Slack: https://kubefirst.slack.com/archives/C03U34WJ7FW/p1722624581373809
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Kcorb95: it seems that you were able to fix your issue by adding the k3d local domains we use in /etc/hosts/ so I'm closing this as resolves.
With that said, I would like to document that in case someone else had this issue, but I need more information. Since we never encountered this, any idea on why your setup require that?
For the docs, here are the domains that needs to be added:
argo.kubefirst.dev
argocd.kubefirst.dev
vault.kubefirst.dev
console.kubefirst.dev
chartmuseum.kubefirst.dev
atlantis.kubefirst.dev
minio.kubefirst.dev
metaphor-development.kubefirst.dev
metaphor-staging.kubefirst.dev
metaphor-production.kubefirst.dev


Ignite 5655

First implementation, uses global level configuration option (in BinaryConfiguration)

The ticket is resolved, closing PR.
Please close PRs for your resolved tickets and other non-needed PRs.
Alternatively, ask a committer

to use GitHub UI (committer can associate accounts here: https://gitbox.apache.org/setup/ )
or https://github.com/apache/ignite/blob/master/scripts/apply-pull-request.sh from Apache Ignite source.
or mention in commit message 'Fixes #(a number of PR)'.

These methods will automatically close PR.
Feel free to reopen this PR if it is anyway actual.


[Enhancement] (nereids)implement showGrantsCommand in nereids

showGrants command is supported in legacy planner but not in nereids(new doris fe planner). you need implement the following showGrants command in nereids:
unsupportedshowGrantsStatement
SHOW ALL? GRANTS

i will pick it


Apply opacity to non focused Items

Describe the solution you'd like
Similar to
.interactive() or rotation3D()
Can you hint me at what level will you create this type of behaviour?

@umwelt , I'd do that by taking into account the page index. So you have your Pager:
@StateObject var currentPage: Page = .first()

var body: some View {
  Pager(...) { index in
    // return a page here based on index
  }
}

You can compare the callback index  to your Page.index and apply some opacity:
Pager(...) { index in
  MyPage(index: index)
    .opacity(opacity(at: index))
}

and then
/// Decrements proportionally the opacity by 0.2 if unfocused
func opacity(at index: Int) -> Double {
  let value = 1 - abs(Double(index - page.index)) * 0.2
  return max(0, min(1, value))
}

Does that make sense?

@fermoya
Thanks, yes this really helps.
If I can add something is that, compared to the other methods, specially "rotation3D()" this will miss the progressiveness of the effect -> drag coordination.
But for me this works, thanks for the expedite help!

@umwelt I know you were happy with my answer but I liked the idea of implementing this if you're interested.
I haven't still decided on a name for the modifier, for now I've chosen faded(_:) but I think I'll deprecate the current interactive(_:) in favor of interactive(scale:) and use interactive(opacity:) instead.
Let me know if you have any suggestions. See it in action here:
https://github.com/fermoya/SwiftUIPager/blob/fix/ios13-issues/

@fermoya
nice, I also agree that extending the interactive modifier to allow opacity feels more natural, based on the current implementation of the Pager.
The links above are broken

@umwelt update the links

@fermoya
that looks perfect to me.
are you going to release it on cocoa pods anytime soon?

I have a PR ready to go, I’d be releasing a beta first. I might deal with
some other issue before making an official release.
Over the weekend I’ll release 2.1.0-beta.1
On Fri, 5 Mar 2021 at 16:44 umwelt<EMAIL_ADDRESS>wrote:

@fermoya https://github.com/fermoya
that looks perfect to me.
are you going to release it on cocoa pods anytime soon?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fermoya/SwiftUIPager/issues/190#issuecomment-791540344,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACWPPPE5CWPZRFBDVKB2ZI3TCEC7TANCNFSM4YA5I2QQ
.

2.1.0-beta.1. You might see more betas coming up over the weekend but it’s not something relevant, just fixes to a new CI/CD workflow. Once a beta is set-up I can’t stop generating new ones till I make an official release 😅

@fermoya
thanks for the hard work!
the new interactive with opacity works perfect!
Also unrelated to this item, the fix you did on the not animate while transitioning gave the gesture that bit of resistance that was needed, I was dealing with some pages skipped on fast drag velocities, but now looks and feels just awesome.

Thanks for your feedback @umwelt , I appreciate it. I’ll let you know when I make an official release 👍

2.1.0 is live @umwelt


Error highlight dissapears on save

When I edit a file, errors are highlighted correctly:

However, after saving :w, they disappear:

If I run :copen, however, the errors are still listed, so they're still reported, just not highlighted:

Re-reading the files makes the error's highlighting appear again (e.g.: :e). This happens only with coc-tsserver (e.g.: Not with coc-jedi, etc).

Could be tsserver slow to response.

Could be tsserver slow to response.

I don't think so.
When I run :w, the highlights disappear and do not appear (even if I wait for a few minutes).
If run :e immediately after the save, the highlights reappear within a couple of seconds.
At no point do the errors disappear from the quickfix window (I display errors via ALE).
I'll try to trim down my nvim config to a be as minimal as possible to repro this.

I don't think so.
When I run :w, the highlights disappear and do not appear (even if I wait for a few minutes).
If run :e immediately after the save, the highlights reappear within a couple of seconds.
At no point do the errors disappear from the quickfix window (I display errors via ALE).
I'll try to trim down my nvim config to a be as minimal as possible to repro this.

I can reproduce this. Another case: highlights disappear after typing K on any (highlighted or not) variables to hover documentation, and then moving cursor to close hovered documentation.

Should be issue with ale


JsonIgnoreProperties not considered while converting groovy class to json

I have a Rest resource with as groovy class as response type.
I used @JsonIgnoreProperties annotation to exclude metaClass property from groovy. But still this property is listed in swagger-ui Response Class model.
http://stackoverflow.com/questions/22763820/exclude-metaclass-properties-for-groovy-model-classes-in-swagger lists the Foo instance.
com.wordnik.swagger.converter.ModelPropertyParser class does not seem to consider the JsonIgnoreProperties annotation. Is this true? How do I make swagger consider my JsonIgnoreProperties  annotation?

@fehguy - is this still an issue for 1.5? Doesn't the Jackson parsing read these annotations now?

Will add tests and close after confirming.

supported and tested in 1.5.x-M1 and greater, see https://github.com/swagger-api/swagger-core/blob/develop_2.0/modules/swagger-core/src/test/scala/1_3/converter/JsonIgnorePropertiesModelTest.scala


Set default AWS Region to us-east-1

Set the default aws region to us-east-1

Could you please expand on the proposal?
For example, why default to eu-east-1 instead of another region and for which component (terraform state, DR, etc.)
Thanks!

The us-east-1 is the default one on AWS SDK

After discussing what @g-iannelli is proposing is that in the generated file by furyctl create config the default example value for the region should be us-east-1.


Add autoload file into custom-theme-load-path

I wanted to load this package using use-package+straight, which meant it needed an autoload.
Additionally, because this is nominally supposed to be a doom-theme, so I updated the naming of the variables to the doom-theme style ie doom-everblush-*. Updating the naming scheme might make this easier to merge into doom-themes if that is still your intent.

👍🏻


Reducing memory used by esp-matter when it is not running (CON-829)

Describe the question/query that you have
A clear and concise description of what you want to ask.
I'm looking for tips and guidance on reducing memory used by esp-matter when it is not running. I switch that enables matter during compilation and I can see that esp-matter uses around 30% of RAM by existing. Is this possible to reduce it or change memory allocation to dynamic and do it after esp_matter::start ?
Per-archive contributions to ELF file:
Archive File DRAM .data & 0.bss IRAM0 .text & 0.vectors ram_st_total Flash .text & .rodata & .rodata_noload & .appdesc flash_total
libmain.a       1142   10375          22           0        11539      187357    139580                0          0      328101
libCHIP.a         64    8913           0           0         8977      138242     16182                0          0      154488
libesp_matter.a         24   30574          27           0        30625      124615     13806                0          0      138472
Matter enabled:
Used static DRAM:   99344 bytes (  25236 remain, 79.7% used)
.data size:   21568 bytes
.bss  size:   77776 bytes
Used static IRAM:  118306 bytes (  12766 remain, 90.3% used)
.text size:  117279 bytes
.vectors size:    1027 bytes
Used Flash size : 1458603 bytes
.text: 1182259 bytes
.rodata:  276088 bytes
Total image size: 1598477 bytes (.bin may be padded larger)
Matter disabled:
Used static DRAM:   59812 bytes (  64768 remain, 48.0% used)
.data size:   21196 bytes
.bss  size:   38616 bytes
Used static IRAM:  122534 bytes (   8538 remain, 93.5% used)
.text size:  121507 bytes
.vectors size:    1027 bytes
Used Flash size : 1383631 bytes
.text: 1047927 bytes
.rodata:  335448 bytes
Total image size: 1527361 bytes (.bin may be padded larger)
Additional context
...

Standalone esp-matter is close to using up all of the on-chip RAM. I gave up on fighting with it over RAM usage and switched to ESP32s with 2MB PSRAM. They don't cost that much more and all of your RAM consumption problems will go away. I only use about 200K of the 2MB but that 200KB makes a HUGE different in the amount of coding effort needed to make things fit. You can use the spare PSRAM for performance optimizations too like shadowing code in PSRAM instead of executing out of flash.


Board Review: Introducing Load Test service

Thank you for starting the process for approval of the client library for your Azure service.  Thorough review of your client library ensures that your APIs are consistent with the guidelines and the consumers of your client library have a consistently good experience when using Azure.
The Architecture Board reviews Track 2 libraries only. If your library does not meet this requirement, please reach out to Architecture Board before creating the issue.
Please reference our review process guidelines to understand what is being asked for in the issue template.
Before submitting, ensure you adjust the title of the issue appropriately.
Note that the required material must be included before a meeting can be scheduled.
Contacts and Timeline

Service team responsible for the client library: Azure Load Testing team
Main contacts: Abhishek Ranjan (@abranj1219), Nikita Nallamothu (@ninallam) Harshan B (@Harshan01)
Expected GA date for this library: To be decided

About the Service

Link to documentation introducing/describing the service: https://docs.microsoft.com/en-us/azure/load-testing/
Link to the service REST APIs: https://github.com/Azure/azure-rest-api-specs/tree/main/specification/loadtestservice
Is the goal to release a Public Preview, Private Preview, or GA?  Public Preview

About the client library

Name of client library: Load Test service
Link to library reference documentation: N/A
Is there an existing SDK library? If yes, provide link:  No

Step 1: Champion Scenarios
Ultimately the library should be easy to use for common scenarios that developers want. Consider the following questions when thinking about champion scenarios:

What is the app the developer is building that uses your client library? Internal automated load testing workflows
Who is the end-user of the application (the developer's customer)? DevOps teams who require Azure Load Testing
What features of the API need to be explained in the sample so that someone could use this API in real app? Creating/updating a Test, and creating/updating a test run and getting test metrics.
How does the authentication workflow look? OAuth2 token-based authentication from Service Principal credentials

See Champion Scenario section here.

Champion scenario 1

Link to library’s sample folder: https://gist.github.com/Harshan01/03d64552dcb7c28b86ebfeb3fc1df953

I feel important to clarify that Azure Load Test team is going through DPG flow, and having some discussion around names in the API.

APIView for .NET: https://apiview.dev/Assemblies/Review/fe482cb7d6b549ee83b36915d9fcd417

Recording (MS INTERNAL ONLY)


How does delayed restoration of variables in tensorflow checkpoint restore work?

I am trying to follow the checkpointing from tensorflow's checkpoint guide. I am failing to understand the exact semantics of how the variable restoration takes place. The issue that i am facing is best shown by the code bit below:
import tensorflow as tf
import numpy as np

#defining a simple subclass of keras model. Just one dense layer is present we will try to restore the kernel and bias of this layer using the `tf.train.Checkpoint`

class Net(tf.keras.Model):
  """A simple linear model."""

  def __init__(self):
    super(Net, self).__init__()
    self.l1 = tf.keras.layers.Dense(5)
  def call(self, x):
    return self.l1(x)

net = Net()

#initializing the net by running it on a demo input
_ = net(np.arange(4).reshape(-1,1)) #model has been initalized

#checking the weights
print(net.l1.bias,net.l1.kernel)

#saving the model parameters
ckpt = tf.train.Checkpoint(netin=net)
mgr = tf.train.CheckpointManager(ckpt,'./tf_ckpt',max_to_keep=1)
mgr.save()

#trying to load just the bias of the net's parameters
initializer = tf.keras.initializers.Constant(value=1.)
restore_bias_here = tf.Variable(initial_value=initializer(shape=(5,)))
ckpt_layer = tf.train.Checkpoint(bias = restore_bias_here)
ckpt_net = tf.train.Checkpoint(l1 = ckpt_layer)
ckpt1 = tf.train.Checkpoint(netin=ckpt_net)
#queing up the restores
ckpt1.restore(tf.train.latest_checkpoint('./tf_ckpt'))

Now, here is the problem. I can restore the kernel in a delayed fashion both from ckpt_net and from ckpt_layer but it seems i can do it only once. And the behavior shifts silently. Code to show the problem:
#and now trying to load just the kernel but from 1. ckpt_net created previously
delayed_restore_kernel_here = tf.Variable(initial_value=initializer(shape=(1,5)))
print(delayed_restore_kernel_here) #all 1's tensor
ckpt_layer.kernel = delayed_restore_kernel_here
print(delayed_restore_kernel_here) #the variable is loaded up perfectly

#2. from #ckpt_layer created previously. But this wont succeed
delayed_restore_kernel_here = tf.Variable(initial_value=initializer(shape=(1,5)))
print(delayed_restore_kernel_here) #all 1's tensor
ckpt_net.l1.kernel = delayed_restore_kernel_here
print(delayed_restore_kernel_here) #all 1's tensor

I can run the last two steps in any order and only the first one will run. Can somebody explain to me the exact semantics of how the delayed restoration of variables in tensorflow works under the hood? Many thanks in advance

@nitinmnsn
Can you please the tensorflow version on which error is faced.

tensorflow 2.2.0
ubuntu 20.04
Normal installation

@nitinmnsn
I ran the code shared and both the spinets mentioned run with an output, can you please refer to this gist and let us know if this confirms your issue.

@nitinmnsn
please update as per above comment


sbt-scalajs, scalajs-compiler, ... 1.16.0 (was 1.15.0)

About this PR
📦 Updates

org.scala-js:sbt-scalajs
org.scala-js:scalajs-compiler
org.scala-js:scalajs-library
org.scala-js:scalajs-library_2.13
org.scala-js:scalajs-test-bridge
org.scala-js:scalajs-test-bridge_2.13

from 1.15.0 to 1.16.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-js" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-js" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

I will not merge this and #753 for now, because according to https://www.scala-js.org/news/2024/03/19/announcing-scalajs-1.16.0/ there might be "Enhancements with compatibility concerns" and also "it is not guaranteed that a codebase will compile as is when upgrading from 1.15.x (in particular in the presence of -Xfatal-warnings)."
We can wait, if people want to have it upgraded, please comment here, thanks!

OK, we have to merge it otherwise we can not upgrade scala-xml (which we should IMHO), see error in #756:
[error] org.scalajs.ir.IRVersionNotSupportedException: Failed to deserialize a file compiled with Scala.js 1.16 (supported up to: 1.13): /home/runner/.cache/coursier/v1/https/repo1.maven.org/maven2/org/scala-js/scalajs-library_2.13/1.16.0/scalajs-library_2.13-1.16.0.jar:/scala/scalajs/LinkingInfo.sjsir
[error] You may need to upgrade the Scala.js sbt plugin to version 1.16 or later.

Hmm... ok, not, I will not merge any of these right now, scala-xml also upgrades scala-native to 0.5.0: https://scala-native.org/en/latest/changelog/0.5.x/0.5.0.html
I just don't want to break anything in a patch release if not absolutely necessary so I will not merge it right now.

@Mergifyio rebase


Bug: Stubs Misbehaving

Describe the bug

Stubs appear to be broken. After some digging it appears something in Vue 3.2.45 is the culpret.
To Reproduce

Create a new vue project with npm init vue@latest and include vitest
Lock vue to version 3.2.44 and npm install
Add a simple component StubMe.vue

<template>

I should not exist

</template>

Import and use your new component in HelloWorld.vue

<template>

{{ msg }}

      You’ve successfully created a project with
      Vite +
      Vue 3.

  <StubMe />
</template>

Update HelloWorld.spec.ts to include a stub

import { describe, it, expect } from 'vitest'

import { mount } from '@vue/test-utils'
import HelloWorld from '../HelloWorld.vue'

describe('HelloWorld', () => {
  it('works on v3.2.44', () => {
    const wrapper = mount(HelloWorld, { props: { msg: 'Hello Vitest' }, global: { stubs: { StubMe: { template: '
I am stubbed
'} } } })
    expect(wrapper.text()).toContain('I am stubbed')
  })
})

Run the tests - they should pass
Now change to vue 3.2.45 and re-run the tests - they will fail

Expected behavior

Stubs should work.
Related information:

@vue/test-utils version: 2.x.x
Vue version: 3.2.45
node version: 16.3.2
npm (or yarn) version: 8.1.2

Additional context

Hi @mmk0083
Are you using the latest VTU version?

I have @vue/test-utils: 2.2.6 in my project where I discovered this. I was also able to reproduce this as described above by simply starting a brand new vue project with npm init vue@latest

One additional point of interest - in my project I do have one set of tests with { stubs: { RouterLink: RouterLinkStub } } that oddly enough is still working.

@mmk0083 I tried to reproduce on Stackblitz, but this looks like it works?
https://stackblitz.com/edit/vitest-dev-vitest-gj33dw?file=package.json
I'm going to close the issue, but feel free to ping me with a repro on Stackblitz if you have a use case that fails and I'll take a look

@cexbrayat Thank you for looking into this. I've tried to reproduce it again myself this morning and now I can't - at least not on a clean vue project. I'm honestly not sure how I managed to break it that way yesterday so I apologize if I've wasted your time.
I do still have a failing stub in my real project, but after further troubleshooting it seems specific to trying to stub a chart from vue-chartjs.
Anyway - thank you again.


Using Gitflow in this project?

From the naming of branches I assume Gitflow is used in this project. But it looks like it's not used correctly / consistently. For example I see no release branches. This might look like overkill it does have a purpose.
For example now the develop branch is never up-to-date with the latest released version number. In a regular Gitflow workflow you bump the version number in a release branch and merge that to master AND develop when it's released.
Also some of the smaller bugfixes should actually be created in a hotfix branch from master and upon release be merged into master AND develop and possibly a release branch if one is active at that moment. I sometimes cheat here by continuing an older release branch and fixing it in that same branch (which is then called for example release/3.6.x) , bumping the patch version number (i.e. the last part of the version, see Semantic Versioning) and release that by merging again to master and develop.
And please set the repository's default branch to develop instead of master as that is the main development branch.

Hi. I appreciate your desire to help.
I do know and follow git flow in many real life projects that deserve this kind of control.
This project is simple enough to justify only two branches in what I call a simplified git flow.
The master branch is the current release, stable and tested code, while the develop branch is the work in progress branch.
We have only a single code file. Ok, we could split each class in its own file, but even then we would have 3 small files.
I got your point, but I can't see this project growing beyond one more class for raw values and this structure seems fine to me.
I'm happy to receive any feedback and contribution.
Thank you.

Yes, sure, I understand. I only found it a bit confusing to see that the version in the develop branch was lower than the currently released version in the master branch.
There's really no need to split the file by class. I would even say that would make it even harder to use. Now it's a single file drop-in library that you can use which makes it much easier to use.

Ok. So I'll make sure to merge back the master branch into develop after releasing and this should avoid that issue.


Snowflake - Backslash escape of single quote breaks syntax highlighting

System information:

Windows 10
DBeaver <IP_ADDRESS>003211804 Community Edition
Git support, Darkest Dark Theme

Connection specification:

Snowflake 4.10.2
Snowflake 3.12.3
No tunnels or proxies

Describe the problem you're observing:
Even though Snowflake supports backslash escaped single quotes in string literals, these break the syntax highlighting in DBeaver.
This is a similar issue to these ones, but for a different connection type:
#6606, #2716, #2969
Steps to reproduce, if exist:

if anyone stumbles on this: while the default might not be correct, one can easily fix this for themselves by setting the Advanced parameters > String escape character to backslash in the driver settings.


support loading js with typescript

escodegen will often break when using babel, enabling the option to make typescript parsing js will make it faster by reducing the time it takes to load the parsers, allow more options, and hopefully fix the issue

Hi, so I've encountered this.... it would work if we could simply provide a glob or pattern for what to pass through to the typescript compiler in the same way that we can for plugins that do other transforms.

this is already solved.
we will close this for now but let us know otherwise :)

@devmondo since when was this solved? is there an example of using ts to compile js when you want it to? by using quantum ensure-es5? links?

@nchanged is this still not solved?

ya i wanna know, too...

@nchanged ping

@xdave it's not that easy, cuz of module resolution. But we could add it to the next milestone

This is fixed now, let us know otherwise.


Feature: If PF2e System Proficiency without Level is set to Use Variant Rule

Can you put a check in for if the system setting "Proficiency without Level" is set to "Use Variant Rule", and recalculate the average check accordingly, otherwise when that setting is in play your suggested default DC is too high.  Or just have a toggle in your settings to use "DC based on average lvl of party" or not

For "Proficiency without Level" Need to calculate average Proficiency Rank of skill and then use DC from table
https://2e.aonprd.com/Rules.aspx?ID=1370
Is it correct?
Example Party

PC A - skill  Untrained - DC 10
PB B -  skill Master - DC 25
PC C - skill Legendary - DC 30
=> (10+25+30)/3 = 21.6666666667~20

Result 20 is it correct?

im not sure any GM uses it like that.
Generally the table on https://2e.aonprd.com/Rules.aspx?ID=1370 is about the Proficiency needed to do the task, not the Proficiencies of the doer.
so, assuming a GM clicked on a party Skill (to open the "DC of Skill Dialog")
if Proficiency without Level is true, or you have a toggle in the Settings for your Module (which again is a variant rule, so i appreciate you looking at this)
you would present a dialog that used either bullets or a drop down for
"What Proficiency would normally be needed for this Activity"
and the options would be Untrained, Trained, Expert, Master, Legendary.
probably defaulting to Trained
changing that setting would change the Input Field of "DC of Check" to one of the numbers found at https://2e.aonprd.com/Rules.aspx?ID=1370, but would allow the GM to edit the number
before pressing "Create DC Template" or "Cancel"

technically you can use this same effect when proficency with level exists also... You would just take the average you already calculated from your current research, you could use a drop down of Easy (-2), Average (+0), Hard (+2), Very Hard (+4)


Add rest end points for search results and search options

Rest end points for the following:

Search options shown on the search page. Description of the returned object is in code comments.
Search results returned based on the query parameters. Description of returned object in code comments.

@akshayrai , @shankar37 , do you have any more comments?

+1


Touch up bad math in run man page

We'd an off by one error in the run man page spotted by @leorochael in
Fixes: #4239
Signed-off-by: TomSweeneyRedHat<EMAIL_ADDRESS>

LGTM
@vrothberg @leorochael @mheon @baude @jwhonce @QiWang19 PTAL

LGTM

/lgtm
/hold

/hold cancel


fix: Hotfix export bug

:tada: This PR is included in version 1.0.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


disable remote file pulling

Asked by @gbe in #25

1/ When starting the Exegol container, we only need to manipulate local files (Exegol's and the user's) and the version 1.4.0 pulls remote files by default. This means that implementing the PR in the current state of bqm still implies to empty temporarily the file query-sets.json as a workaround to disable remote sources. Something we agreed is not a good idea.
Hence my whish: could you add a CLI option to disable the pulling of remote sources ?

It would be easy to do that, but I don't understand why it's an issue to pull remote resources, I mean several tools included in Exegol may do that?

Hi @noraj,
thanks for taking the time to answer my points.
I see several reasons to not pull remote resources when starting an Exegol container:

If the server where the resource is hosted is unresponsive, it may hang the container start
Some remote resources may not interest the end users
In the case of Exegol, not pulling remote resources creates the opportunity to replace entirely the file provided by Exegol. It's actually what led me to create the Exegol's PR in the first place, then it was suggested to also support the merging feature.
but most of all, when doing an engagement at the customer's premises, the auditor may not have internet access as it may require an authentication against the customer's proxy.

For all these reasons, I see a need for your tool to offer the possibiliy to work offline :)

If the server where the resource is hosted is unresponsive, it may hang the container start

Why? Remote resources are fetched at runtime. And even if the test commands are issued when the container starts, the test command for bqm in Exegol is bqm --help which doesn't interact online. So I don't see how bqm could delay the container start. However it's true that an unavailable remote resource prevent to use the tool locally if this is not possible to disable it.

Some remote resources may not interest the end users

True, I'll add an option anyway.

In the case of Exegol, not pulling remote resources creates the opportunity to replace entirely the file provided by Exegol. It's actually what led me to create the Exegol's PR in the first place, then it was suggested to also support the merging feature.

I'm not sure to understand what you mean here.

but most of all, when doing an engagement at the customer's premises, the auditor may not have internet access as it may require an authentication against the customer's proxy.

True, offline use.

Just to clarify the part you did not understand, it means that I could use your tool with Exegol to merge local files, and not necessarily with the one provided by Exegol.
It is not directly your concerned, it was just to give you some context.


⛹ always include outputs with code cells

This always adds an output array to blocks that represent code-cells in the ast, even when the outputs array is empty. This is consistent with ipynb format, where the outputs array is always present.

Nice, looks good.


MINOR: Deprecate LogConfig.Compact

It actually refers to the delete cleanup policy.

Review by @hachikuji

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6607/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6592/
Test PASSed (JDK 8 and Scala 2.12).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6889/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6875/
Test PASSed (JDK 8 and Scala 2.12).

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/6890/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/6876/
Test PASSed (JDK 8 and Scala 2.12).

@hachikuji is this OK?


ROD Hot Fix

All Submissions Basics:

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you checked all Issues to tie the PR to a specific one?

All Submissions Cores:

[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your core changes, as applicable?
[x] Have you successfully ran tests with your changes locally?
[x] Does your submission pass tests, including CircleCI, Travis CI, and AppVeyor?
[x] Does your submission have appropriate code coverage? The cutoff threshold is 95% by Coversall.

New Model Submissions:

[x] Have you lint your code locally prior to submission?

From previous hot fix, MAD median was still left out without being saved after invoking fit(), now it is saved and tested so it is fully compatible with PyOD and Sklearn code convention.

Pull Request Test Coverage Report for Build 2060

33 of 35 (94.29%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.004%) to 95.782%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyod/models/rod.py
29
31
93.55%

Totals

Change from base Build 2052:
0.004%

Covered Lines:
5337

Relevant Lines:
5572

💛  - Coveralls

Hi @yzhao062
This final fix is very important.
Hopefully we will have it in the next release.

Sounds perfect. the next release will be in a few days for sure or sooner!

the new release is out!


Add function for getting the size of a DFS file without calling dfs_open

About
This change implements dfs_rom_size, which returns the size of a file without calling dfs_open.
Rationale
This can be used in conjunction with dfs_rom_addr and dma_read to get ROM data without needing to open a file handle. This can be useful in scenarios where a programmer might want to avoid invoking malloc (eg: after a level has been loaded).

I can amend test_dfs.c to accommodate this function.

I'm usually a bit "meh" about adding APIs to dragonfs.h as I'd like people to use syscalls instead, but in this case you're looking for the lowest possible overhead and in fact you're basically bypassing dfs as well, you just want ROM data. So I guess it's fine.
Please add the test, yes.

Also have a look at https://github.com/DragonMinded/libdragon/pull/607 which I just merged

Thank you Rasky! It's heartening to see this added! <3


[WIP] Improve test subcommands

Closes #130
Closes #129

Strangely, on my machine, test model --max-trace <num> non-deterministically fails on the second generated test(in the loop) with the following error,
ImportError while importing test module '/home/ranadeep/informal/atomkraft/examples/cosmos-sdk/transfer/transfer/tests/test_transfer_2022_09_05T17_17_33_148/test_Ex_violation2.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
/usr/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
E   ModuleNotFoundError: No module named 'test_Ex_violation2'

Not sure what's causing it.

I found this paragraph from pytest invocation documentation.

Calling pytest.main() will result in importing your tests and any modules that they import. Due to the caching mechanism of python’s import system, making subsequent calls to pytest.main() from the same process will not reflect changes to those files between the calls. For this reason, making multiple calls to pytest.main() from the same process (in order to re-run tests, for example) is not recommended.

My bet is this is the reason. Because I have seen some correlation between present __pycache__ directory and the raised error.

The errors are fixed now :slightly_smiling_face:
I group the test files first and then invoke pytest.main only once.


Installation via deb package fails on Ubuntu Linux

Describe the bug
When attempting to install Synectic on Ubuntu Linux, the following error message is observed:
$ sudo apt install ./Downloads/synectic_4.2.0_amd64.deb
[sudo] password for root:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'synectic:amd64' instead of './Downloads/synectic_4.2.0_amd64.deb'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 synectic:amd64 : Depends: libgtk-3-0:amd64 but it is not installable
                  Depends: libnotify4:amd64 but it is not installable
                  Depends: libnss3:amd64 but it is not installable
                  Depends: libxtst6:amd64 but it is not installable
                  Depends: libatspi2.0-0:amd64 but it is not installable
                  Depends: libdrm2:amd64 but it is not installable
                  Depends: libgbm1:amd64 but it is not installable
                  Depends: libxcb-dri3-0:amd64 but it is not installable
E: Unable to correct problems, you have held broken packages.

To Reproduce
Steps to reproduce the behavior:

Download the deb package version of Synectic
Right-click on the deb file and select Open with Other Application
Select Software Install from the list of available applications
Click Install (provide credentials as needed)
See error

Or alternatively, launch Terminal and run the following command:
sudo apt install ./Downloads/synectic_4.2.0_amd64.deb

Expected behavior
A clean installation onto the Ubuntu desktop.
Screenshots

Versions (please complete the following information):

OS: Ubuntu 22.04.02
Synectic Version: 4.2.0

Additional context
This error was observed while attempting to install Synectic onto an Ubuntu Linux VM through Parallels, but it doesn't appear that this environment had any effect on this outcome.

Per an Nvidia developer forums post, Electron App - unmet dependencies for building installer, in which similar errors appear for a user attempting to install a .deb packaged Electron app:

Your “.deb” is for an Intel architecture desktop PC. You need to build the applications for the Nano’s architecture. One of “arm64/aarch64/ARMv8-a” (they’re different abbreviations of the architecture). Any of these will fail and are not a compatible architecture: “x86/x86_64/amd64/i386/i686”. If you see these, then they are not compatible, and are for an older 32-bit version of ARM: “arm/armhf/arm32/ARMv7”.

This reminded me that the .deb package we're bundling for Synectic is targeted at amd64. It's likely that the Ubuntu 22.04.02 image running in Parallels (for MacOS) is an Intel x64 architecture.

Fixed in https://github.com/EPICLab/synectic/issues/1277 as part of the conversion to Hydraulic Conveyor for packaging distributable versions of Synectic; including for Debian Linux and similar distro flavors.


Custom Texture

Hi, I was trying to add a new mesh with new texture on the chris normal model. However, I keep getting this error in blender.

I don't get any errors when adding a new mesh but it must use the existing material in the chris model

a22.png)
Any fixes for this?

Hi, the way of adding new textures is kinda cumbersome, I believe this happened because you added a texture but didn't set a Fake user option for the texture container and it was removed by Blender after saving. Also what version of Albam do you use? I believe I added an error message that shows texture info in this case.


Model Validations & Tests

Inkling Blog App | Model Validations & Tests #3
Project Description
Add validations to User, and Post models. Aslo add tests using rspec-rails to all the Inkling Blog app.
Feature Description

Added the following validations:

For the User model:

@name must not be blank.
@posts_counter must be an integer greater than or equal to zero.

For the Post model:

@title must not be blank.
@title must not exceed 250 characters.
@comments_counter must be an integer greater than or equal to zero.
@likes_counter must be an integer greater than or equal to zero.

Added unit spec tests for all of the Inkling Blog app models methods and validations.

Happy Reviewing!!!!!

Thanks so much @emmanuellekamwa for the amazing review!


fix "Tick values are displayed even if showTicksValues option is set to false (#105)"

Even if the showTicksValues option is set to false, the tick values are displayed.
In slider.component.ts in updateTicksScale()method, on line #1246, Object.assign(this.ticks[i], newTicks[i]) was used to replace existing tick with the new tick at the given index.
Doing so, didn't removed the value of the tick from the old object even when the value was not present in the new tick. Thus, the tick tooltips still appeared.
That line was changed to this.ticks[i] = newTicks[i] instead of using object.assign().

#105

Thanks for opening a PR.
However, I decided to fix it in another way by initialising Tick class fields when constructing the object.
Using Object.assign() in this place has slight performance advantage over reassigning the object with regards to Angular change detection.


training issue when read h5 file

xl@xl-All-Series:~/work/pytorch-vdsr-master$ python main.py
Namespace(batchSize=64, clip=0.4, cuda=False, lr=0.001, momentum=0.9, nEpochs=50, pretrained='', resume='', start_epoch=1, step=10, threads=4, weight_decay=0.0001)
('Random Seed: ', 8148)
===> Loading datasets
===> Building model
===> Setting GPU
===> Setting Optimizer
===> Training
Epoch=1, lr=0.001
===> Epoch1: Loss:<PHONE_NUMBER>402
===> Epoch1: Loss:<PHONE_NUMBER>422
Checkpoint saved to model/model_epoch_1.pth
Epoch=2, lr=0.001
Traceback (most recent call last):
File "main.py", line 126, in
main()
File "main.py", line 81, in main
train(training_data_loader, optimizer, model, criterion, epoch)
File "main.py", line 99, in train
for iteration, batch in enumerate(training_data_loader, 1):
File "/home/xl/anaconda2/lib/python2.7/site-packages/torch/utils/data/dataloader.py", line 198, in next
return self._process_next_batch(batch)
File "/home/xl/anaconda2/lib/python2.7/site-packages/torch/utils/data/dataloader.py", line 239, in _process_next_batch
raise batch.exc_type(batch.exc_msg)
IOError: Traceback (most recent call last):
File "/home/xl/anaconda2/lib/python2.7/site-packages/torch/utils/data/dataloader.py", line 41, in _worker_loop
samples = collate_fn([dataset[i] for i in batch_indices])
File "/home/xl/work/pytorch-vdsr-master/dataset.py", line 13, in getitem
return torch.from_numpy(self.data[index,:,:,:]).float(), torch.from_numpy(self.target[index,:,:,:]).float()
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (/home/ilan/minonda/conda-bld/h5py_1490028130695/work/h5py/_objects.c:2846)
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (/home/ilan/minonda/conda-bld/h5py_1490028130695/work/h5py/_objects.c:2804)
File "/home/xl/anaconda2/lib/python2.7/site-packages/h5py/_hl/dataset.py", line 494, in getitem
self.id.read(mspace, fspace, arr, mtype, dxpl=self._dxpl)
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper (/home/ilan/minonda/conda-bld/h5py_1490028130695/work/h5py/_objects.c:2846)
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper (/home/ilan/minonda/conda-bld/h5py_1490028130695/work/h5py/_objects.c:2804)
File "h5py/h5d.pyx", line 181, in h5py.h5d.DatasetID.read (/home/ilan/minonda/conda-bld/h5py_1490028130695/work/h5py/h5d.c:3413)
File "h5py/_proxy.pyx", line 130, in h5py._proxy.dset_rw (/home/ilan/minonda/conda-bld/h5py_1490028130695/work/h5py/_proxy.c:2008)
File "h5py/_proxy.pyx", line 84, in h5py._proxy.H5PY_H5Dread (/home/ilan/minonda/conda-bld/h5py_1490028130695/work/h5py/_proxy.c:1656)
IOError: Can't read data (Wrong b-tree signature)
do you come across this error?

@leixiang90 can you have a try with threads = 1?

@twtygqyy It works! thanks.
can you provide a parameter settings for train this network, like lr, epoch nums, step or weight initialization？ I use the default settings. The loss does not seems to converge. Thanks!

@leixiang90 How many epochs have you trained? The loss should be able to converge gradually with the defaulting parameters.

@leixiang90  Hi , I met the same problem
Namespace(batchSize=64, cuda=True, lr=0.0001, momentum=0.9, nEpochs=100, pretrained='', resume='', start_epoch=1, step=100, threads=1, weight_decay=0.0001)
True
('Random Seed: ', 6940)
===> Loading datasets
(11712, 1, 32, 32)
===> Building model
===> Setting GPU
===> Setting Optimizer
===> Training
epoch = 1 lr = 0.0001
Traceback (most recent call last):
File "main.py", line 141, in
main()
File "main.py", line 85, in main
train(training_data_loader, optimizer, model, criterion, epoch)
File "main.py", line 103, in train
for iteration, batch in enumerate(training_data_loader, 1):
File "/home/zhangdongyang/tensorflow/local/lib/python2.7/site-packages/torch/utils/data/dataloader.py", line 174, in next
return self._process_next_batch(batch)
File "/home/zhangdongyang/tensorflow/local/lib/python2.7/site-packages/torch/utils/data/dataloader.py", line 198, in _process_next_batch
raise batch.exc_type(batch.exc_msg)
IOError: Traceback (most recent call last):
File "/home/zhangdongyang/tensorflow/local/lib/python2.7/site-packages/torch/utils/data/dataloader.py", line 34, in _worker_loop
samples = collate_fn([dataset[i] for i in batch_indices])
File "/home/zhangdongyang/pytorch-LapSRN-master/dataset.py", line 15, in getitem
print(self.data[index,:,:,:].shape)
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "/home/zhangdongyang/tensorflow/local/lib/python2.7/site-packages/h5py/_hl/dataset.py", line 496, in getitem
self.id.read(mspace, fspace, arr, mtype, dxpl=self._dxpl)
File "h5py/_objects.pyx", line 54, in h5py._objects.with_phil.wrapper
File "h5py/_objects.pyx", line 55, in h5py._objects.with_phil.wrapper
File "h5py/h5d.pyx", line 181, in h5py.h5d.DatasetID.read
File "h5py/_proxy.pyx", line 130, in h5py._proxy.dset_rw
File "h5py/_proxy.pyx", line 84, in h5py._proxy.H5PY_H5Dread
IOError: Can't read data (wrong B-tree signature)
I generated the train data using https://github.com/twtygqyy/pytorch-LapSRN/tree/master/data. But the error disappear when use the provided lap_pry_x4_small.h5. How did you solve the problem. Thanks a lot.

@twtygqyy  thank your work!
I trained the VDSR model  on 91 images augmented by provided generate_train.m.  I use the default settings. but, the loss does not seems to converge after 50 epochs.  Could you give me some advice? Thanks!

#6


feat: add additional set of colours

ST-27
Motivation and context
To achieve the chart below, we need additional colors: teal and anthracite. Sergiu confirmed that it was already discussed with designer and that we should add the whole set of colors for both of them

Before
No teal no anthracite
After
Both set of colors is available

@Marine-Berthier can you share in the designSystem channel this update? please.
Then designers and devs knows about this for future designs and implementations.
Thank you!


[BUG] crash: This application is not allowed to access Photo data.

ios Crash log:
This application is not allowed to access Photo data.
0 CoreFoundation | ___exceptionPreprocess + 228
1 libobjc.A.dylib | objc_exception_throw + 56
2 PhotoLibraryServices | 0x000000021bdc4000 + 177788
3 Photos | 0x000000021ccdd000 + 809144
4 Photos | 0x000000021ccdd000 + 602268
5 Photos | 0x000000021ccdd000 + 687268
6 AssetsLibraryServices | 0x000000021bae9000 + 38308
7 libdispatch.dylib | __dispatch_client_callout + 16
8 libdispatch.dylib | __dispatch_continuation_pop$VARIANT$mp + 412
9 libdispatch.dylib | __dispatch_source_invoke$VARIANT$mp + 1308
10 libdispatch.dylib | __dispatch_root_queue_drain + 372
11 libdispatch.dylib | __dispatch_worker_thread2 + 128
12 libsystem_pthread.dylib | _pthread_wqthread + 464
13 libsystem_pthread.dylib | start_wqthread + 4

I can't find any info in the log.

Same bug
*** Terminating app due to uncaught exception 'NSObjectInaccessibleException', reason: 'This application is not allowed to access Photo data.'

1
CoreFoundation
0x1f87b5000
__exceptionPreprocess (in CoreFoundation) + 228

2
libobjc.A.dylib
0x1f7a9b000
objc_exception_throw (in libobjc.A.dylib) + 56

3
PhotoLibraryServices
0x2065a1000
-[PLPhotoLibrary initWithTransientContext:name:pathManager:] (in PhotoLibraryServices) + 1320

4
Photos
0x20755d000
-[PHPhotoLibrary photoLibrary] (in Photos) + 108

5
Photos
0x20755d000
-[PHCoreImageManager _performPreheatReferenceCountingOperationForAssets:CPLPrefetching:domain:operation:passingTestHandler:] (in Photos) + 128

6
Photos
0x20755d000
__22-[PHImageManager init]_block_invoke (in Photos) + 344

7
AssetsLibraryServices
0x20629a000
__pl_dispatch_source_set_event_handler_block_invoke (in AssetsLibraryServices) + 36

8
libdispatch.dylib
0x1f82a9000
_dispatch_client_callout (in libdispatch.dylib) + 16

9
libdispatch.dylib
0x1f82a9000
_dispatch_continuation_pop$VARIANT$armv81 (in libdispatch.dylib) + 404

10
libdispatch.dylib
0x1f82a9000
_dispatch_source_invoke$VARIANT$armv81 (in libdispatch.dylib) + 1704

11
libdispatch.dylib
0x1f82a9000
_dispatch_root_queue_drain (in libdispatch.dylib) + 344

12
libdispatch.dylib
0x1f82a9000
_dispatch_worker_thread2 (in libdispatch.dylib) + 116

13
libsystem_pthread.dylib
0x1f84e1000
_pthread_wqthread (in libsystem_pthread.dylib) + 472

14
libsystem_pthread.dylib
0x1f84e1000
start_wqthread (in libsystem_pthread.dylib) + 4

Please provide version info including package version, system version, and Flutter verison.

Closing since no further info are provided.


Configure SSH to use smart card

Refs:

https://developers.yubico.com/PIV/Guides/PIV_Walk-Through.html
https://zerowidthjoiner.net/2019/01/12/using-ssh-public-key-authentication-with-a-smart-card
https://medium.com/google-cloud/google-cloud-ssh-with-os-login-with-yubikey-opensc-pkcs11-and-trusted-platform-module-tpm-based-86fa22a30f8d

Closing.  SSH will use the smartcard now.  If ssh-agent needs to be enabled for using the smart card as well, then that will be a new issue.

Closing.  SSH will use the smartcard now.  If ssh-agent needs to be enabled for using the smart card as well, then that will be a new issue.