Melody streams

What changed in this PR:
Adding new core package melody-streams.
This package aims to reduce the API surface and the amount of technologies an engineer has to know to be productive with Melody to a single one: Rx.js
It is based on the simplicity concept of hooks, while it works without any hooks and abstracts data handling and component updating completely to streams.

Let's also address this issue directly: https://github.com/trivago/melody/issues/76
i.e. let's add a render method so that we won't have to teach melody-component just to render a component.


User Contributions Demo App

A sample app that uses MediaWiki Action API:Usercontribs allows you to see the latest top 50 edits made by a user. This app uses Flask framework as backend.

@srish Sorry, The GitHub environment is new for me. I was contributing to Gerrit since 2017. On Gerrit, Everything is related to patch number. By patch number, we can download the patch, resolve the merge conflict etc. But here scenario is Pull Request. So during the resolve the merge conflict, I lost my branch. That is why a pull new request. you can see "Jayprakash-SE wants to merge 2 commits into wikimedia:master from unknown repository". I am sorry about this. Will take care in future. My humble request to you. Please review once again.

If a username is not found, you can maybe show some error to the user
Ans:- Done

For the sake of demo app, might not be a good idea to link to an external css file that lives on Toolforge..
Ans:- Done

May be you don't need to mention Bootstrap here, as you are not really using the framework.
Ans:- Done

I think we don't need to send username data as we already have it in the response object.
Ans:- But we need it, because when username is not found then response object will be empty. So we need to display the error message.


Allow editing and viewing the personal comment field on someone else's profile

Edit with POST /api/v2/user/profile/:username/personal_comment
View with comment field from GET /api/v2/user/profile/:username

See also https://github.com/seamonkeysocial/cruisemonkey/issues/131


switch turned ON by service switch.turn_OFF

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within ZWaveJS2MQTT?
NO, my problem is NOT within ZWaveJS2MQTT
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
When I issue a command to turn_off a switch, the switch (light) doesn't turn off. When I issue a command to turn_on, it doesn't turn on.
In the logs, when it receives a turn_off command, it logs turning off and then ON again... and vice versa.
I opened a ticket in HA Core
https://github.com/home-assistant/core/issues/77051
and they looked at the logs, and recommended opening it here instead.
This is happening specifically with three Minoston zwave outdoor plugs, and no other devices. All three plugs have been on my network for months and working just fine; and all three started misbehaving around the same time, about a week to 10 days ago(?). The bug doesn't happen every time, but anecdotally it seems like about 50% of the time.
I can easily reproduce it simply by clicking the on/off switch in the Device page in HA.
When I click On, right there on the Device page it says:
Switch1 was turned ON by service switch.turn_ON
Switch1 was turned OFF by service switch.turn_ON
and vice versa.
I tried switching from zwaveJS to zwaveJSMQTT (I wanted to do that anyway), and the problem persists.
I noticed that this same issue was reported a couple of years ago here:
https://github.com/home-assistant/core/issues/42798
In the old ticket, it was another device/manufacturer. In my case, the "switches" are Minoston zwave outdoor smart plugs.
https://minoston.com/product/z-wave-plus-smart-plug-outdoor-on-off-outlet-switch-mp22z/
I wrote to Minoston several days ago for any info, but no response yet. (But like I said, they worked fine for months, and I have not updated their firmware.)
In the attached log, Node 26 is the switch that I used to recreate the problem.
THANK YOU
Device information
Minoston zwave outdoor smart plugs.
https://minoston.com/product/z-wave-plus-smart-plug-outdoor-on-off-outlet-switch-mp22z/
How are you using node-zwave-js?

[X] zwavejs2mqtt Docker image (latest)
[ ] zwavejs2mqtt Docker image (dev)
[ ] zwavejs2mqtt Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
zwavejs2mqtt: 6.15.2
zwave-js: 9.6.2
Did you change anything?
no
If yes, what did you change?
No response
Did this work before?
Yes (please describe)
If yes, where did it work?

Attach Driver Logfile
zwavejs_2022-08-19.log

I have been facing this same issue for awhile as well.  Random devices, whether triggered via automations, scenes, manually through HA entity or via zwavejs2mqtt control panel, will frequently change state, then revert a second later.  If you try again, the operation succeeds.  I suspect it may have something to do with the optimistic update logic (maybe a race condition?), but I don't have any data to support that.  No failures of operations shows in logs, it appears as if I had initiated a toggle on the entity.
I can't easily reproduce it, but a period of idle time seems to potentially be a factor as well.  Happy to provide more information, I just hadn't opened an issue yet because I didn't have any good data.  Interested in theories though.

@knwpsk I'm not sure what exactly is going on with the device, but it seems to frequently forget the shared S2 encryption state:
node -> zwave-js: Here's my status, did you get it?
zwave-js -> node: I got it.
(radio silence, meaning node understood the response)

seconds later, no:
zwave-js -> node: Turn on
node -> zwave-js: I don't understand.

The radio silence could also mean that the response, or the node's "I don't understand", was lost.
I expect this to become better in the upcoming v10 release where I overhauled the S2&Supervision communication. For now you can try eliminating connectivity issues as the source of the issue:
https://zwave-js.github.io/node-zwave-js/#/troubleshooting/connectivity-issues?id=general-troubleshooting
and https://zwave-js.github.io/node-zwave-js/#/troubleshooting/network-health?id=testing-the-connection-strength

@AlCalzone thanks for this.
Pls make sure you see the part where this is happening on three devices of same make/model, and that they all started doing this around the same time, and that there was no firmware change. It suggests that there was a change in HA (they say no) or the zwave driver (??) that triggered the problem.
Based on nothing at all, just gut, I'll assume that the Minoston devices were doing something odd all along, but that some recent change on "our" side (HA or driver?) became less tolerant of it...??
Connectivity Issues page:
I read the connectivity issues page, and none of that seems likely.
Two of the three Minoston devices are within a few feet of several more zwave nodes. The third is a bit farther away from the core of my network, but it's also still only a few feet from one other node.
Network health...
This is interesting. I have hurricane-proof glass windows. I have wondered if they cause any kind of radio issues (but there are a number of other things going on that suggest not). Also have "lots of stuff" using radio in various ranges, so I wonder if any kind of signal interference is relevant. I just switched from native zwavejs to zwave-mqtt, so I will definitely try out the health check and see what that offers. If I find anything I'll post here. (Thanks!)

The only thing that did change in the driver in this regard was on July 5th (9.6.0), where the driver stopped requesting an acknowledgement for supervision reports. So we no longer notice if the devices didn't get this report. We didn't do anything with this information before, but this could block the send queue for several seconds if there were issues reaching the devices.
The change shouldn't have an though, unless the devices ignore these commands.

Making sure I understand what you described:
Before the July 5 change, if the driver didn't get an ack from the device, that could block the send queue for a few seconds. After the change, the driver no longer stopped looking for an ack, so the block should no longer happen. So, logically, that change couldn't have been what started my problem; if anything, that change would have fixed my problem (if it was related at all). Is that your point?
(I have a pretty thorough understanding of messaging protocols in general, but very little experience with zwave, and I'm fairly new to HA.)

Yeah that's my point. That change is the only change that could be somewhat relevant, but I wouldn't expect any effect like you describe. I wonder if it still reproduces when you downgrade to whatever the setup was before this started happening.
I don't have a contact at Minoston sadly.

I tried to run HealthCheck the way it's described here,
https://zwave-js.github.io/zwavejs2mqtt/#/guide/healthcheck
but I get Connection Refused.
I'm groping here -- any tips?
I tried running from Console on the HA; and I tried running it from command prompt on a local PC. Same both times.

Wrong health check :) I don't think there's user documentation for the one you should use though.
Go on the network map in z2m, click the node you want to check. A gray panel opens with some routing information and a button "check health". Click that one.

OK would be great if the "improving network health" page actually gave those instructions!  (Thanks again)
Ran health check on Plug2 (the one that most often exhibits the problem), tested it connecting to Node1, my control stick, because the map says it uses a direct connection to the stick. Got some iffy results, attached.
There are several other nodes that are closer to Plug2, in between it and the stick. Is there a way to tell it to try using those instead? I wonder if that would help it. (I've healed the network several times in the past.)
healthCheck_26-1.zip

Also tested Node26 to Node23 (a peer, closer than the controller stick), and it gets 10 out of 10 on every test.

Ran full network Heal.
Now the map no longer shows Plug2 (node26) with a direct connection to control stick (node1).
Ran Health Check from 26 to 1, and now it all comes up 9 out of 10.
Hoping this helps. Will play with it and see.

It failed to turn off, bounced back to on, and then went "unavailable".

Got a driver log of this? This smells a lot like physical connectivity issues though.

Didn't log it first time, but just did it again and recreated it.
This time I used an Automation triggered by a wall switch, to turn on (or off) Plug1 and Plug2 at the same time. Both plugs acted ok for several on/off iterations, and then Plug2 failed the last time.
Log attached.
zwavejs_2022-08-22.log

Please disable any log filters and the the loglevel to "debug". Then try again. The log you posted is missing a lot of information.

Dangit.
OK will re-do in a little while. Wife just yelled at me for turning the lights on/off from remote... :)

OK ran it again, with proper logging this time.
Simply:
Started with Plug 2 (Node 26) off, clicked the On switch on lovelace.
The plug turned on, then off again.
Log attached.
zwavejs_2022-08-23.log
(BTW I just updated HA to 2.6.)

Ok, so part of this may see improvement in the v10 release, but something is really not right in your network:
2022-08-23T13:17:48.502Z SERIAL « 0x011c00a800011a139f038f0076e769c69070706d0ac69760b37bb800be66      (30 bytes)
2022-08-23T13:17:48.505Z SERIAL » [ACK]                                                                   (0x06)
2022-08-23T13:17:48.506Z DRIVER « [Node 026] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -66 dBm
                                  └─[Security2CCMessageEncapsulation] [INVALID]
                                      error: Security2CC_CannotDecode
2022-08-23T13:17:48.507Z CNTRLR » [Node 026] Message authentication failed, cannot decode command.  I usually see this when there is interference or some other connectivity issue - not necessarily with the node itself, this can also be caused by repeaters.
This is the same command, re-transmitted over and over. Only the RSSI changes, but if you look closely, this wildly fluctuates between -66 and -85 dBm.

Interestingly, the same happens with other nodes too:
2022-08-23T13:17:51.420Z SERIAL « 0x010c00a80001080326030000b2c6                                      (14 bytes)
2022-08-23T13:17:51.422Z CNTRLR   [Node 008] [~] [Multilevel Switch] currentValue: 0 => 0           [Endpoint 0]
2022-08-23T13:17:51.425Z SERIAL » [ACK]                                                                   (0x06)
2022-08-23T13:17:51.429Z DRIVER « [Node 008] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -78 dBm
                                  └─[MultilevelSwitchCCReport]
                                      current value: 0
2022-08-23T13:17:51.480Z SERIAL « 0x010c00a80001080326030000b3c7                                      (14 bytes)
2022-08-23T13:17:51.481Z CNTRLR   [Node 008] [~] [Multilevel Switch] currentValue: 0 => 0           [Endpoint 0]
2022-08-23T13:17:51.485Z SERIAL » [ACK]                                                                   (0x06)
2022-08-23T13:17:51.487Z DRIVER « [Node 008] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -77 dBm
                                  └─[MultilevelSwitchCCReport]
                                      current value: 0
2022-08-23T13:17:51.576Z SERIAL « 0x010c00a80001080326030000b1c5                                      (14 bytes)
2022-08-23T13:17:51.578Z CNTRLR   [Node 008] [~] [Multilevel Switch] currentValue: 0 => 0           [Endpoint 0]
2022-08-23T13:17:51.580Z SERIAL » [ACK]                                                                   (0x06)
2022-08-23T13:17:51.581Z DRIVER « [Node 008] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -79 dBm
                                  └─[MultilevelSwitchCCReport]
                                      current value: 0
2022-08-23T13:17:51.605Z SERIAL « 0x010c00a80001080326030000b0c4                                      (14 bytes)
2022-08-23T13:17:51.606Z CNTRLR   [Node 008] [~] [Multilevel Switch] currentValue: 0 => 0           [Endpoint 0]
2022-08-23T13:17:51.608Z SERIAL » [ACK]                                                                   (0x06)
2022-08-23T13:17:51.609Z DRIVER « [Node 008] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -80 dBm
                                  └─[MultilevelSwitchCCReport]
                                      current value: 0
2022-08-23T13:17:51.692Z SERIAL « 0x010c00a80001080326030000b1c5                                      (14 bytes)
2022-08-23T13:17:51.693Z CNTRLR   [Node 008] [~] [Multilevel Switch] currentValue: 0 => 0           [Endpoint 0]
2022-08-23T13:17:51.695Z SERIAL » [ACK]                                                                   (0x06)
2022-08-23T13:17:51.696Z DRIVER « [Node 008] [REQ] [BridgeApplicationCommand]
                                  │ RSSI: -79 dBm
                                  └─[MultilevelSwitchCCReport]
                                      current value: 0

Sending messages to Node 26 frequently takes more than one attempt:
2022-08-23T13:17:52.661Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            33
                                    transmit status:        OK, took 1290 ms
                                    repeater node IDs:      49
                                    routing attempts:       2
                                    protocol & route speed: Z-Wave, 100 kbit/s
                                    ACK RSSI:               -86 dBm
                                    ACK RSSI on repeaters:  -81 dBm

...

2022-08-23T13:17:53.936Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            34
                                    transmit status:        OK, took 540 ms
                                    repeater node IDs:      43, 25
                                    routing attempts:       4
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -66 dBm
                                    ACK RSSI on repeaters:  -61 dBm, -66 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1

...

2022-08-23T13:17:54.655Z DRIVER « [REQ] [SendDataBridge]
                                    callback id:            35
                                    transmit status:        OK, took 600 ms
                                    repeater node IDs:      43, 25
                                    routing attempts:       3
                                    protocol & route speed: Z-Wave, 40 kbit/s
                                    ACK RSSI:               -66 dBm
                                    ACK RSSI on repeaters:  -63 dBm, -66 dBm
                                    ACK channel no.:        1
                                    TX channel no.:         1

...
etc

so it is very likely that the node has similar troubles reaching the controller. I'd suggest taking a good look at the used repeaters nodes here.
Luckily your controller and nodes offer a lot of insight, as long as you are reading the driver logs. Here's an example trying to reach node 7:
transmit status:        OK, took 70 ms
repeater node IDs:      24, 27, 52
routing attempts:       1
protocol & route speed: Z-Wave, 40 kbit/s
ACK RSSI:               -68 dBm
ACK RSSI on repeaters:  -94 dBm, No signal detected, -66 dBm

70ms with 3 hops and 1 attempt is a good number, but if you correlate the repeaters node IDs and the ACK RSSI on repeaters, you'll see that the controller and node 52 have almost the same RSSI. Node 24's value is really low (probably very close to the background noise) and 27 didn't even detect signal.
I'd go through the logs, search for OK, took to get these reports and check if any have more than 1 routing attempt and which repeaters are taken with which RSSI. If any stand out, physically moving them or adding more repeaters around them may help.
You may also see route failed between: X -> Y which can give you an indication of bad links, but I don't see that right now.

OK super great help, thank you!
On gut, I agree with you that this feels like some kind of interference or "network storm" kind of problem. I just needed this kind of help to learn to troubleshoot.
Will be back when I have some time.  FYI going on vacation for a couple of weeks starting Friday, so it may take me a bit to use all your good advice and progress this.

Have a nice vacation then, and feel free to reopen this issue if the bot closes it in the meantime due to lack of activity.

Hey @AlCalzone, in the meantime -- what will I do when I further digest these logs?
For example: You pointed out that Node 24 has low signal strength. That's a keypad back in my master bedroom. It's pretty far from the outdoor plug (Plug 2, Node 26) we've been talking about. I can't fathom why Plug 2 would try to use that keypad as a relay -- especially when there are several nodes much closer to it, and in a more direct path between it and my controller.
So, is there a way I can tell Plug2/Node 26: "Please stop trying to use Node 24 as a relay" ? Or, "Node 26, you are only allowed to use these following nodes as relays" ?

Making notes for later ref.
I did a whole bunch of cleanup this afternoon.
I excluded and re-included 7-8 devices that were not secure, and got them all on S2 authentication.
Then I cleaned up everything that was logging errors (broken automations etc, mostly resulting from either my convertion to mqtt or my exclude/include cleanup).
Gave proper names to all the zwave devices so I can identify them easily for tshooting.
So far my zwave outdoor plugs "seem" to be acting better. Will give it some time and come back here with any updates.

If I "heal the network", that tells the controller and nodes to re-evaluate all of those mappings/routes, right?
Or do I need to do something more fundamental than that to get my network to a state of 'strong mesh" ?
What you're saying makes a lot of sense. I'm new to HA and zwave, and have been learning as I go. I've installed and uninstalled and re-installed a bunch of stuff multiple times as I figure it all out -- not just learning the tech, but also learning how I want to use it, and then observing the weaknesses in my house geography. So... I'm sure there are a number of "bad routes" buried in my devices' knowledge.

More curious-ness.
I just started a network heal. Already I see some strange stuff. Pls see the end of this log: there seem to be multiple nodes that don't reply to the controller's request for a list of neighbors after 5 attempts, and then report "healing failed."
But then, those same devices do show a list of nodes in "get routing info"-- but the list of node numbers looks crazy! I only have about 25 devices; and the highest node id is 75. So what are all those other numbers?
zwavejs_2022-08-24.zip

If I "heal the network", that tells the controller and nodes to re-evaluate all of those mappings/routes, right?

Correct.

Or do I need to do something more fundamental than that to get my network to a state of 'strong mesh" ?

That might require physical layout changes, to improve the physical connection strength between neighbors and reduce interference / wireless reflections near the nodes.

but the list of node numbers looks crazy!

That list comes from the controller memory. I've seen instances before where this was messed up. Refreshing the list of neighbors from nodes should be able to correct that, but as you noticed, those are failing.
Something is definitely fishy there - disabling and enabling the radio before/after showing the network map didn't work either. Try doing this:

shut down z2m
pull the stick
wait 5 seconds
put it back in
start z2m again
retry the heal

Might also be worth to try out a different USB extension cable - not that yours is bad and causes a heap of issues.

Will do... and I'm gonna send this log to Zooz, too (it's their brand controller stick)

Wow... I did all that, and the results look way, way different!
No more fails in the heal process. :)
zwavejs_2022-08-24 1429pm.zip


Release <IP_ADDRESS>

Coverage remained the same at 72.131% when pulling 138b8aa03f7371079cc7a47f6cb7f3ab81f4ce4e on dev into bb5b33a8ed72647882d9c563ae526822088be749 on master.


Parent rotations mess with edge curves and Road Lanes

Discovered while trying to implement intersections with a more dynamic scene, we seem to not have a great parent inverse relationship
Example instanced RoadContainer scene with no rotation, and then with some rotation added:

This is present on the dev branch, unsure if the released addon has this issue. FYI @bdog2112 on this task

Per a parallel post in our wheel steal repo, I had to do something similar with the RoadPoints at one point to invert one parent level of transform (not exactly our scenario here, but this code could be useful).

Worked a little to come up with a fix, indeed going to local-only operations is what we needed. Will create a PR soon for both 4.x and 3.x

With both dev (godot 3.5) and godot4 branches being updated, this is good to be called done - fix will go live in the next asset library update.


Read-the-docs documentation

RTD should be the place that we dig into the details of configurable options

addressed by https://github.com/emccode/polly/pull/58


Introduce buffer in WAL append

WAL append writing cost too much, we can introduce a buffer to cache some data.
I think there could be two kind of mode:

buffer one record and write all at once
buffer multiple records

It is closed by #196


Getting Started doc assumes puppetlabs-package is builtin

Add a 'bolt module add puppetlabs-package' to the docs
Maybe it's the 3.0.0 macOS version, but the 'package' task isn't in the builtins. After some digging, I discovered bolt modules and installing them. Honestly, it was a great lesson to learn, but adding it to the lesson would have made it much much easier.

@cringdahl Are you installing the Bolt gem or the Bolt package? The gem does not ship with any modules and we do not recommend running Bolt as a gem.

At first the bolt gem that presumably came with some other Puppet package I had (1.4.x), but even the 3.0.0 package via direct download, or via Homebrew, exhibited this problem.
Get Outlook for Androidhttps://aka.ms/ghei36

From: beechtom<EMAIL_ADDRESS>Sent: Friday, February 5, 2021 5:04:54 PM
To: puppetlabs/bolt<EMAIL_ADDRESS>Cc: Cory Ringdahl<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [puppetlabs/bolt] Getting Started doc assumes puppetlabs-package is builtin (#2627)
CAUTION: This message originated externally, please use caution when clicking on links or opening attachments!
@cringdahlhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcringdahl&data=04|01|Cory.Ringdahl%40rackspace.com|fcd915c8274641f6c63708d8ca2a73c3|570057f473ef41c8bcbb08db2fc15c2b|0|0|637481630983236764|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=xU0Sxnstq3Gu5tsSwbiTTAqRUZOmaZcDDyfTzDSTnNI%3D&reserved=0 Are you installing the Bolt gem or the Bolt package? The gem does not ship with any modules and we do not recommend running Bolt as a gem.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpuppetlabs%2Fbolt%2Fissues%2F2627%23issuecomment-774335254&data=04|01|Cory.Ringdahl%40rackspace.com|fcd915c8274641f6c63708d8ca2a73c3|570057f473ef41c8bcbb08db2fc15c2b|0|0|637481630983246718|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=U8sJnaOfu8xKGz%2BL3Dbv8mStKE2nKYtTx%2FozTIKGq2s%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADDTAXLCUAZLZS6QUF4W5SDS5R2RNANCNFSM4XFRQ2MA&data=04|01|Cory.Ringdahl%40rackspace.com|fcd915c8274641f6c63708d8ca2a73c3|570057f473ef41c8bcbb08db2fc15c2b|0|0|637481630983246718|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=GxWBXntX0s1YX8BnucLIDVWINfWYn%2B%2FQX%2BkHaN%2BJTBA%3D&reserved=0.

Is 'package' the only builtin module that's missing? For example, is service available? That would be especially weird, since everything just gets installed from the same Puppetfile and the version looks correct. I'd try a gem uninstall bolt (which shouldn't affect the package-installed Bolt) just to be safe, but I haven't been able to reproduce this issue with a freshly installed 3.0.0 on OSX 15.

service isn't available. I'm not sure what's default, but here's what I have:
✔ ~/Code/bolt_test
13:19 $ bolt module show
Plan Language Modules
  boltlib   (built-in)
  ctrl      (built-in)
  dir       (built-in)
  file      (built-in)
  out       (built-in)
  prompt    (built-in)
  system    (built-in)

/Users/cory2388/Code/bolt_test/modules
  apache   (no metadata)

Project Dependencies
  puppetlabs/package   1.4.0

Packaged Modules
  aggregate        (built-in)
  canary           (built-in)
  puppet_connect   (built-in)
  puppetdb_fact    (built-in)

I've got quite the hodgepodge of packages installed, including a PDK that's been pdk bundle updated a number of times. Could this have pulled in an incomplete 1.x bolt on principle?

Ah ok, that packaged_modules is definitely too short, and indicates to me you're using a Gem install of Bolt. Did you try gem uninstall bolt? You might also try which bolt and make sure it's pointing to /opt/puppetlabs/bin/bolt:
lucy ~/githubs/bolt (main) $ which bolt
/usr/local/bin/bolt
lucy ~/githubs/bolt (main) $ ls /usr/local/bin/bolt -l
lrwxrwxrwx 1 root root 24 Feb  4 10:02 /usr/local/bin/bolt -> /opt/puppetlabs/bin/bolt

gem uninstall bolt did it, I'm seeing a pile of puppetlabs/* packages when I do bolt module show.
One thing, though: it takes about 3 seconds to run bolt, and about 10 seconds to run bolt module show, whereas before it was instantaneous. Is this normal? Could it be the new module list? Could the "Project Dependencies" puppetlabs/package be somehow conflicting with the "Packaged Modules" puppetlabs/package?

I suspect that has more to do with loading the package as opposed to the gem than the specific modules. Are other commands slow, or just bolt module show? What OS and Ruby version are you on?

Hm, I think this might be a duplicate of https://github.com/puppetlabs/bolt/issues/2625 - is it ok if I close?

Actually, I think one thing we could do here is provide instructions on our '


redhat.java fails to install on macOS

As said in the title, redhat.java upon trying to install with the UI just says installing forever and over the CLI simply says Failed to install extension redhat.java
I am currently running nightly build at commit: #5f6d1cd2
I'll add more information if necessary.

Hi @brukberhane ,
Thank you for logging the issue!
Some extra information that might be useful:

What OS are you using?
Are other extensions able to be installed?

Also, there are occasionally some intermittent connectivity issues with https://open-vsx.org - might be worth retrying just to see if that was the case.

I'm runnning macOS 11.4, I've tried installing tomi.xajssnippets as just any random extension and that installs perfectly fine. Is there any way I can get logs for why the install for redhat.java failed?

I've managed to get the redhat.java extension installed by downloading the file first and then passing it to oni2 --install-extension. I see no repercussions from that yet.

Upon trying to install it using the GUI of Onivim, It waits for a long time and errors out giving me:

Installing it with a different (and slower) internet source somehow got it to work with the GUI installation... I am going to close this issue for now and assume it was a problem with the internet


HW accelerated Tunarr containers do not exist

I'm trying to change the image tag for my Tunarr container in the Synology Docker client, but neither ghcr.io/chrisbenincasa/tunarr:latest-vaapi nor chrisbenincasa/tunarr:latest-vaapi seem to exist in the repos. Only the vanilla software-only images seem to exist. Were these images removed?

I see them:
https://hub.docker.com/layers/chrisbenincasa/tunarr/latest-vaapi/images/sha256-96e25b4dae008805a7c61c14fccabc6ecd561352cadaa05688788f8ad3cd1f94?context=explore
https://github.com/chrisbenincasa/tunarr/pkgs/container/tunarr/292642394?tag=latest-vaapi

I see them:
https://hub.docker.com/layers/chrisbenincasa/tunarr/latest-vaapi/images/sha256-96e25b4dae008805a7c61c14fccabc6ecd561352cadaa05688788f8ad3cd1f94?context=explore
https://github.com/chrisbenincasa/tunarr/pkgs/container/tunarr/292642394?tag=latest-vaapi

I still see an error saying that it doesn't exist, I'm not sure what the issue might be:

Are you running an ARM based machine?
Also if you are on macOS do you need vaapi?
On Tue, Oct 22, 2024 at 12:26 PM Victoria Dominowski <
@.***> wrote:

I see them:
https://hub.docker.com/layers/chrisbenincasa/tunarr/latest-vaapi/images/sha256-96e25b4dae008805a7c61c14fccabc6ecd561352cadaa05688788f8ad3cd1f94?context=explore
https://github.com/chrisbenincasa/tunarr/pkgs/container/tunarr/292642394?tag=latest-vaapi
I still see an error saying that it doesn't exist, I'm not sure what the
issue might be:
image.png (view on web)
https://github.com/user-attachments/assets/4415eb03-1ea8-4049-b41c-88ef4d1d1885
—
Reply to this email directly, view it on GitHub
https://github.com/chrisbenincasa/tunarr/issues/886#issuecomment-2429732722,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMQRX5HBNPNPUOZH4COUL3Z4Z4CVAVCNFSM6AAAAABQELQP2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRZG4ZTENZSGI
.
You are receiving this because you commented.Message ID:
@.***>

(Just judging from the UI could be wrong)

Gotcha. Maybe an explicit pull is needed somehow? Not familiar with Synology's interface or nuances... i've successfully pulled both the docker hub and ghcr images to confirm that they're available (just now)

@ameturpoet you might just need to add the repository (e.g. https://hub.docker.com/r/chrisbenincasa/tunarr)...

Ah thanks for chiming in @hcooper - that looks probable!

Going to close this since I think it is stale. If adding the repository doesn't work, you can reopen and we can explore further.


Add Luis Fernando Robles to Contributors.md

Hi  @lfr4704, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

Hi Roshan,
The tutorial was very straight forward. I'm looking forward to begin contributing to other open source projects.
Thanks a lot for this exercise. It help me big time!

I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://goo.gl/PM1Jdh


Test that including stdsimd as a submodule in libstd succeeds

So I'm not sure how thorough this test is - cc @alexcrichton is ./x.py check enough? it doesn't appear to catch the issue that @jethrogb ran into, but AFAICT the stdsimd submodule is being appropriately replaced and ./x.py succeeds =/
I haven't enabled this for mipsel and the thumb targets, but for all other targets this appears to work.

I personally feel like this is a bit overboard on the CI budget/complexity, I'm fine discovering these issues after the fact, they don't really come up all that often I think

I personally feel like this is a bit overboard on the CI budget/complexity, I'm fine discovering these issues after the fact, they don't really come up all that often I think

I don't agree with this. In fact, I think that any flow that gates landing things in rust master that could possibly be influenced by stdsimd should also be tested in stdsimd CI.
stdsimd's main purpose is to be a submodule of core/std. However, because stdsimd PRs are not tested in this combination, the chances are high that something will land that will break building core/std. This puts a large burden on the person who requires updates of stdsimd in core/std (because they need some bug fix or new feature to be included upstream): their upstream changes are potentially now blocked by changes made in stdsimd that have nothing to do with the stdsimd changes they want to include upstream.
As for this not happening "all that often", two different core/std-breaking bugs (#599 and #603) were introduced in just the 3 weeks since stdsimd was last updated upstream.

@jethrogb I'm basically personally the architect of CI for crates like libc and rust-lang/rust. It's great to test things, and believe me when I say I don't undervalue it. I have had lots of experience with things like this, and this sort of integration is practically guaranteed to be far more work to keep running than it would be to fix regressions and not acutally effective at preventing all regressions. Preventing regressions like this sort of integration is just being vigilant and not refactoring every few weeks.
Updating any submodule in rust-lang/rust is a PITA because it turns out there's a lot of vectors to introduce subtle bugs. We just do the best we can with the resources we have.

I have the same opinion as Alex, if this turns out to take too much CI time
or be a pain to maintain then it’s probably not worth it.
In my tests running x.py check against libst adds 3 minutes to each build
bot, most of which run now for ~10 minutes.
It doesn’t really make much sense to enable this on all of them, but
depending on how painful this ends up being, it might be worth it to add it
to one or two of them.
On Fri 23. Nov 2018 at 20:38, Alex Crichton<EMAIL_ADDRESS>wrote:

@jethrogb https://github.com/jethrogb I'm basically personally the
architect of CI for crates like libc and rust-lang/rust. It's great to test
things, and believe me when I say I don't undervalue it. I have had lots of
experience with things like this, and this sort of integration is
practically guaranteed to be far more work to keep running than it would be
to fix regressions and not acutally effective at preventing all
regressions. Preventing regressions like this sort of integration is just
being vigilant and not refactoring every few weeks.
Updating any submodule in rust-lang/rust is a PITA because it turns out
there's a lot of vectors to introduce subtle bugs. We just do the best we
can with the resources we have.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang-nursery/stdsimd/pull/602#issuecomment-441308605,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA3Npkp1LQszh33-jGMmaBsdOR6o7fEGks5uyE7DgaJpZM4Yvo9g
.

As another example of why we should not do this, I believe the motivational factor of https://github.com/rust-lang-nursery/stdsimd/issues/603 wouldn't have been caught by this. The bug there is in documentation, not in the standard library itself.
I'm gonna go ahead and close this as I feel relatively strongly this won't end up pulling its weight in the meantime, but we can always reconsider later!


⚠ Bofrost.at has degraded performance

In 267189f, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1125 ms

Resolved: Bofrost.at performance has improved in 343ca6b after 35 minutes.


Fix/#60 links

closes #60

Did a second review, going to merge to start on the Contributor section. Minor link changes will be expected in the last few PRs!


compute.VirtualMachineImagesClient#ListSkusLocation in request URI 'canadacentral,' does not match location of the service 'CanadaCentral'

Bug Report
Got the following error trying to list VM image SKUs with location "canadacentral".
compute.VirtualMachineImagesClient#ListSkus: Failure responding to request: StatusCode=400 -- Original Error: autorest/azure: Service returned an error. Status=400 Code="InvalidLocationInRequestUri" Message="Location in request URI 'canadacentral,' does not match location of the service 'CanadaCentral'"

I would expect the location to not be case sensitive and for "canadacentral" to be equivalient to "CanadaCentral". What's interesting is that this does not happen in any other location (all our regions are lowercase in code and we always use the same API call without any issue). Adding a new region "canadacentral" is what introduced the issue.

import path: `"github.com/Azure/azure-sdk-for-go/profiles/2020-09-01/compute/mgmt/compute"``
SDK version: v63.4.0

import path of package in question, e.g. .../services/compute/mgmt/2018-06-01/compute
SDK version e.g. master, latest, 18.1.0

Specify the exact commit if possible; one way to get this is the REVISION
column output by dep status "github.com/Azure/azure-sdk-for-go.

output of go version

What happened?
What did you expect or want to happen?
How can we reproduce it?
Anything we should know about your environment.

First observed in https://github.com/kubernetes-sigs/cluster-api-provider-azure/pull/2399

@bganapa,  as this is the ask for azurestack, could you help to check whether this behaviour is expected? Thanks

@lirenhe this is not azurestack related. This error occurred in Azure Public Cloud.

Here is the HTTP response if it helps:
<autorest.DetailedError>: {
          Original: <*azure.RequestError | 0xc0001a2240>{
              DetailedError: {
                  Original: nil,
                  PackageType: "",
                  Method: "",
                  StatusCode: <int>400,
                  Message: "",
                  ServiceError: nil,
                  Response: {
                      Status: "400 Bad Request",
                      StatusCode: 400,
                      Proto: "HTTP/2.0",
                      ProtoMajor: 2,
                      ProtoMinor: 0,
                      Header: {
                          "Cache-Control": ["no-cache"],
                          "Strict-Transport-Security": [
                              "max-age=31536000; includeSubDomains",
                          ],
                          "X-Ms-Correlation-Request-Id": [
                              "48ad403d-3ce0-4366-aac1-8d764da6a4a5",
                          ],
                          "Pragma": ["no-cache"],
                          "Content-Length": ["181"],
                          "Content-Type": [
                              "application/json; charset=utf-8",
                          ],
                          "X-Ms-Ratelimit-Remaining-Resource": [
                              "Microsoft.Compute/ListVMImageSkusFromLocation3Min;9999,Microsoft.Compute/ListVMImageSkusFromLocation30Min;29999",
                          ],
                          "Date": [
                              "Fri, 17 Jun 2022 20:01:38 GMT",
                          ],
                          "Expires": ["-1"],
                          "X-Ms-Served-By": [
                              "e371295f-4375-464c-ac6f-1f4a1942c743_13254[498](https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api-provider-azure/2399/pull-cluster-api-provider-azure-e2e/1537886801086124032#1:build-log.txt%3A498)2080877915",
                          ],
                          "Server": [
                              "Microsoft-HTTPAPI/2.0",
                              "Microsoft-HTTPAPI/2.0",
                          ],
                          "X-Ms-Routing-Request-Id": [
                              "CENTRALUS:20220617T200138Z:48ad403d-3ce0-4366-aac1-8d764da6a4a5",
                          ],
                          "X-Ms-Request-Id": [
                              "0b90801f-3308-4f74-ab53-c9e4eedf0e7c",
                          ],
                          "X-Ms-Ratelimit-Remaining-Subscription-Reads": ["11995"],
                          "X-Content-Type-Options": ["nosniff"],
                      },
                      Body: <io.nopCloser>{
                          Reader: <*bytes.Buffer | 0xc00056ac30>{
                              buf: [123, 13, 10, 32, 32, 34, 101, 114, 114, 111, 114, 34, 58, 32, 123, 13, 10, 32, 32, 32, 32, 34, 99, 111, 100, 101, 34, 58, 32, 34, 73, 110, 118, 97, 108, 105, 100, 76, 111, 99, 97, 116, 105, 111, 110, 73, 110, 82, 101, 113, 117, 101, 115, 116, 85, 114, 105, 34, 44, 13, 10, 32, 32, 32, 32, 34, 109, 101, 115, 115, 97, 103, 101, 34, 58, 32, 34, 76, 111, 99, 97, 116, 105, 111, 110, 32, 105, 110, 32, 114, 101, 113, 117, 101, 115, 116, 32, 85, 82, 73, 32, 39, 99, 97, 110, 97, 100, 97, 99, 101, 110, 116, 114, 97, 108, 44, 39, 32, 100, 111, 101, 115, 32, 110, 111, 116, 32, 109, 97, 116, 99, 104, 32, 108, 111, 99, 97, 116, 105, 111, 110, 32, 111, 102, 32, 116, 104, 101, 32, 115, 101, 114, 118, 105, 99, 101, 32, 39, 67, 97, 110, 97, 100, 97, 67, 101, 110, 116, 114, 97, 108, 39, 34, 13, 10, 32, 32, 125, 13, 10, 125],
                              off: 0,
                              lastRead: 0,
                          },
                      },
                      ContentLength: 181,
                      TransferEncoding: nil,
                      Close: false,
                      Uncompressed: false,
                      Trailer: nil,
                      Request: {
                          Method: "GET",
                          URL: {
                              Scheme: "https",
                              Opaque: "",
                              User: nil,
                              Host: "management.azure.com",
                              Path: "/subscriptions/0e46bd28-a80f-4d3a-8200-d9eb8d80cb2e/providers/Microsoft.Compute...

@tadelesh, could you follow up on this?
@bganapa, could you help to check whether 'compute.VirtualMachineImagesClient.ListSkus' is a valid API for AzureStack?
We are released track2 GO SDK and all track 1 libraries except azure stack are now deprecated. https://github.com/Azure/azure-sdk-for-go/tree/main/sdk/resourcemanager/compute/armcompute is the latest library.

Thanks @CecileRobertMichon. We'll involve service team to see whether only location canadacentral is case-sensitive. BTW, is there any other API which has the same location problem?

Adding Service team to look into this.
@Drewm3, @avirishuv, @Vaibhav-Agar, @amjads1 Could you please look into this issue ?

@CecileRobertMichon This seems like a typo
"Location in request URI 'canadacentral,' does not match location of the service 'CanadaCentral'"
Try removing the trailing comma and attempt deployment again. The other issue seems to concur with this.

Oh wow, you're right, I completely missed that... sorry for the noise!


export-installation returning unexpected response

export-installation with opsman <IP_ADDRESS> is returning unexpected response
om-linux --target https://ops-man.net --skip-ssl-validation --username user --password 'PW' --request-timeout 6000 export-installation --output-file /tmp/build/0f36ad4e/pcf-pipelines/tasks/export-opsmgr-settings/opsmgr-settings/installation.zip
exporting installation
30m1s elapsed, waiting for response from Ops Manager...
could not execute "export-installation": failed to export installation: request failed: unexpected response

real    30m1.270s
user    0m39.648s
sys     1m44.332s

Can export from opsman gui successfully without issue.

Closing for not but should probably be noted OPS man appears to have a 30 minute time out for api calls. I went in and modified the tempest-web configuration in this file:
/home/tempest-web/tempest/web/config/thin.production.yml
from its default setting of 30min (1800 sec) to
socket: /tmp/tempest-web.sock
rackup: config.ru
threaded: true
timeout: 60000 (just to ensure we didnt hit anything)

Restarted ops man and the export succeded.

Hi Brandon,
Thanks for sharing your workaround for this issue.
Can you give us some more detail about the size of the generated installation file and the approximate length of time it eventually took for your export to succeed?
Thanks,
@acrmp && @kkallday

using <IP_ADDRESS> file size was around 10.6GB and took roughly 33 to 35min. So right out side the timeout window basically.

As a note I have the following tiles deployed in my test system

ERT 1.11.1
Redis 1.7.5
RabbitMQ 1.7.21
Metrics 1.3.7
MySQL for PCF 1.8.10
JMX Bridge 1.8.22

Unfortunately, since this constraint is on the Ops Manager server side there's nothing we can do from the perspective of om. We have given this feedback to the Ops Manager team and they are going to consider bumping the timeout. Thanks for letting us know about this!
Kevin & @joshzarrabi


Minimal repository (current size very large)

I want to use "json" as a submodule to my project, because:

I want to be transparent is ownership, to give credits where they are due.
To facilitate updating from source.

However, the current repository is extremely large, due to the tests and benchmarks. This hinders again the distribution of my code. Therefore it would be great if a minimal repository can be maintained.
Thanks!
Tom

Duplicate: #96, #482


PHP Debugbar is not working

Hi All,
Sorry, My English is not good.
I have add phalcon-debugbar from this link: https://github.com/snowair/phalcon-debugbar.
but it is not working.
When I run, In my console is display:

I found error:
dashboard:449 GET http://dashboard.somo.local_debugbar/assets/stylesheets?1445331526 net::ERR_NAME_NOT_RESOLVED
dashboard:450 GET http://dashboard.somo.local_debugbar/assets/javascript?1445331525 net::ERR_NAME_NOT_RESOLVED
dashboard:453 Uncaught ReferenceError: PhpDebugBar is not defined(anonymous function) @ dashboard:453
sb-admin-2.js:2 Uncaught TypeError: $ is not a function
How to I can fix it ?

Config the uri service currectly:
$di->set('url', function() use (){
	$url = new Phalcon\Mvc\Url();
	$url->setBaseUri('/');  // here
	return $url;
});

https://github.com/snowair/phalcon-debugbar#about-baseuri

thank you. But my config the uri service:
$di->set('url', function () use ($config) {
$url = new UrlResolver();
$url->setBaseUri($config->application->baseUri);
return $url;
});
In config file : 'baseUri'        => 'http://dashboard.somo.local/'
I can not change 'baseUri'        => '/' . because this affects config my website.
have other solution to this issue ?

You should find out a way, to render the route /_debugbar/assets/stylesheets
from the wrong result:
 http://dashboard.somo.local_debugbar/assets/stylesheets

to the right:
 http://dashboard.somo.local/_debugbar/assets/stylesheets

in phalcon simple-service-provider ind .htaccess

ExpiresActive On
ExpiresByType image/jpg "access 1 year"
ExpiresByType image/jpeg "access 1 year"
ExpiresByType image/gif "access 1 year"
ExpiresByType image/png "access 1 year"
ExpiresByType text/css "access 1 month"
ExpiresByType text/html "access 1 month"
ExpiresByType application/pdf "access 1 month"
ExpiresByType text/x-javascript "access 1 month"
ExpiresByType application/x-shockwave-flash "access 1 month"
ExpiresByType image/x-icon "access 1 year"
ExpiresDefault "access plus 1 month"

    Options -MultiViews
    RewriteEngine On
    RewriteRule ^$ public/     [L]
    RewriteRule ^((?s).*)$ public/$1 [QSA,L]
 # Handle Authorization Header
RewriteCond %{HTTP:Authorization} .
RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]

and add in app\Bootstrap.php function getOutput()
(new \Snowair\Debugbar\ServiceProvider(MYPATH.'config/debugbar.php'))->start();
in


Tune GPU performance for AMIP simulations

The Climate Modeling Alliance
Software Design Issue 📜
Purpose

Cost/Benefits/Risks

People and Personnel

Lead: @sriharshakandala
Collaborators: @charleskawczynski @simonbyrne @szy21
Reviewers: --> @simonbyrne

Components

Inputs

Results and Deliverables

SDI Revision Log

CC
### `ClimaAtmos.jl`
- [ ] Move model-cache variables to fully typed structs
- [ ] Add grid-dependent hyperviscosity specification
- [ ] Balance model-cache recomputation and computing on-the-fly cache
- [ ] Asynchronous kernel launches using CUDA streams
- [ ] Explore CUDA graphs for hiding latency
- [ ] Add QA benchmarks for target AMIP simulations

### `ClimaCore.jl`
- [ ] https://github.com/CliMA/ClimaCore.jl/issues/1428

Focus on RRTMGP


Web UI sync endpoint page

Adressed issue #275, improving the webUI for the sync-endpoint landing page.

I made changes to HTML and css files relating to top_menu_layout and whoami.
Minor unresolved problems:
The file for the landing page is still called whoami.html and whoami.css, I did not change the name of the file because I am not sure what calls whoami.html after the login is successful.
The groups and roles are simply called group/role, it is probably too complicated to separate them into groups and roles

@toadmengo I switched the branch to the development branch, which is the testing area before a release. Can you resolve the merge conflict?

Fixes #https://github.com/odk-x/tool-suite-X/issues/275

@wbrunette Resolved the conflict.


Fix Build Status URI

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Looks like this got fixed in https://github.com/mesosphere/marathon-lb/pull/548.


S3 Asset Ingestor not appearing

Please help me out with this issue
Thanks in advance
Required Information

[ ] AEM 6.5, Service Pack 6.5.9
[ ] ACS AEM Commons Version: 5.0.2
[ ] Reproducible on Latest? yes

Expected Behavior
_Accessing Tools -> ACS AEM COMMONS -> Manage Controlled Processes -> Start Process, The option 'S3 Asset Ingestor'
should appear between the rest of tools.
The tool 'S3 Asset Ingestor' does not appear
Links
Documentation

is the S3 connector installed?

That is where the issue lies, such that I am getting this when trying to resolve it using maven
Could not find artifact com.adobe.granite:com.adobe.granite.oak.s3connector:jar:1.10.10 in adobe (https://repo.adobe.com/nexus/content/groups/public/)

@isosatl this seems like an issue to bring up with Adobe Support since this project doesn't actually distribute the S3 connector.

I just created an adobe ticket; - i appreciate your quick response. Thanks


Reduce minimum required dart version

The package current needs flutter dart sdk version to be >=3.5.3 which is latest at the moment of writing, but the plugin doesn't use any dart or flutter feature that it needs 3.5.3 as the minimum version. Can it be lowered so we can use it in our project?
Here's the result of flutter pub get:
Resolving dependencies...
The current Dart SDK version is 3.5.1.

Because mime_flutter depends on saf_util >=0.0.2 which requires SDK version >=3.5.3 <4.0.0, version solving failed.

You can try the following suggestion to make the pubspec resolve:
* Try using the Flutter SDK version: 3.24.3.

And flutter version
Flutter 3.24.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 5874a72aa4 (8 weeks ago) • 2024-08-20 16:46:00 -0500
Engine • revision c9b9d5780d
Tools • Dart 3.5.1 • DevTools 2.37.2

@Chiggy-Playz Makes sense! Didn't know newly created Flutter project has this aggressive min SDK version settings. Published v0.4.0 with relaxed min Dart and Flutter settings.


controller -> loadData function not called

Inside my HTML
https://github.com/zopyx/zopyx.plone.persistentlogger/blob/master/zopyx/plone/persistentlogger/browser/logger.pt#L84-L102
I am initializing my grid with a custom loadData method.
The grid is being initialized however the load_data() method
https://github.com/zopyx/zopyx.plone.persistentlogger/blob/master/zopyx/plone/persistentlogger/browser/logger.pt#L36-L62
is not called.
(Using jsgrid 1.4.1 with jQuery 1.7.2).

Are you sure load_data was not called?
It feels like it was called but since DATA is null doing grep on it brings to unexpected results.
I do believe you should use Promise which will be returned from the function and resolved with the result of filtering if data already loaded or in success of ajax request if not.

You are ignoring the JS error that you can see in the screenshot.
Please do not close issues too fast without reading and understanding the problem.

In particular the error occurs when you set paging=true.

The error persists with jsGrid 1.5.3

I'm sorry, but I could not manage to reproduce the bug: https://jsfiddle.net/tabalinas/dhu4zjwn/
Please, feel free to update the fiddle to demonstrate it.
Indeed, I didn't look attentively at the exception posted, because the code itself seemed incorrect to me: I expected ajax call filling DATA is async, so grep on DATA being null should fail on the first run. The expected exception seemed obvious, I could not imagine another one
Closing the issue with an answer is a common practice for many support teams. Keeping all the issues opened causes flooding. Once a problem (not necessarily all the problems) is found and we come up with an answer, closing the issue. Absolutely normal is to reopen it once proposed solution doesn't solve the problem. So just feel free to reopen an issue if solution doesn't work.

Cannot reproduce, no answer from the author, closing.

Moved on to DataTables due to the broken architecture and implementation.

Could you please be more specific about "broken architecture and implementation"?
What is exactly meant here?
Thank you very much in advance!


Empty or wrong response when running from within Xcode

Steps to reproduce:

Run the vapor-example from within Xcode (I'm using Xcode 7.3.1 with the 20161-06-06 Swift snapshot)
Browse to http://localhost:8080

Expected Behaviour:

The welcome.html page is shown

Actual Behaviour:

An empty HTML page is shown

In addition other routes such as  http://localhost:8080/mustache and http://localhost:8080/localization/es do not work.

Note for those coming here, add the following to your main.swift file:
#if os(Linux)
let workDir = "./"
#else
var workDir: String {
    let parent = #file.characters.split(separator: "/").map(String.init).dropLast().joined(separator: "/")
    let path = "/\(parent)/.."
    return path
    }
#endif

let app = Application(workDir: workDir)

The issue is that Xcode runs in random folder structures, but we can use this workaround.

This should be in latest 👍


Section on "what is not part of the data space" - e.g. Enterprise Data Management

Trusted Data Sharing requires an end-to-end solution, managing permissions, GDPR consent, managing data as it flows through the enterprise. Those are not part of the data space functionality, but still necessary for building an end to end trusted system.
We need to create a section on where the boundary between the data space functionality and the rest of the participants data systems is.
E.g. Once a data contract gets executed and data assets are transferred usage policies need to be persisted with the data as it is being managed in the enterprise data warehouse or other systems.
E.g. GDPR consent or the handling of PII data needs to be managed in the participants data management system before data is being offered to be shared in a data space. Once it is being shared appropriate policies of the contract need to indicate the need for continued GDPR consent management and PII data handling in the target system. However, the proper handling of PII data is NOT a functionality of the data space, rather of the enterprise data management systems of the individual participant.
We need to introduce a chapter in the rulebook that describes where this boundary lies and provides examples of data management that happens outside of the data space context, but is required for successful and trusted data sharing.

Should be merged with #57


docs: update the link to upgrade DDEV in faq.md

The Issue
For someone who has very little knowledge on Linux, I end up trying to install DDEV by following the installation instructions (from docker desktop and so on) only to realize it's unnecessary.
How This PR Solves The Issue
It should help DDEV users like me.

Thanks so much for pointing this out. I added another commit removing the duplicated instructions in the FAQ.


Text in "Create embed code" dialog now looks differently

Please, update bullet 2 and 3
https://docs.microsoft.com/en-us/power-bi/service-publish-to-web#how-to-use-publish-to-web

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: bc005634-24c6-15c4-4352-e1455d63f4f3
Version Independent ID: 577c460a-08cc-892e-c5f9-e6106958f856
Content: Publish to web from Power BI - Power BI
Content Source: powerbi-docs/service-publish-to-web.md
Service: powerbi
GitHub Login: @markingmyname
Microsoft Alias: maghan

@SychevIgor Thank you for your feedback! We will investigate and review if we need to change/add the information suggested.

@SychevIgor Thanks for the feedback. I updated the screenshots to be more current.  The changes should be posted live in a day or so.

So this feature has been removed from free users?  That makes SELLING your product so much more difficult well done.  As you do not indicate in the documentation that this feature is NOT available to a free user.


Any idea how to compile in dll?

Good day! Who knows how to compile this plugin under windows?

Greetings to all,
I am also searching for the windows DLL file. OS Windows10
pecl install Mosquitto-alpha
error
No releases available for package "pecl.php.net/Mosquitto" install failed


Repo sync for protected CLA branch

The pull request is created from main638061193294620083sync_temp to main to fix git push error for protected CLA branch

Learn Build status updates of commit c96bdad:
:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


How does SingleVarianceNetwork participate in network training?

i have some questions i want to ask you. There is only one parameter of variance in this network. How does it participate in the training of the loss function? Why does the network converge when 1/s approaches 0? Many Thanks  to you!

anyone who can help me answer these questions？

The network converges when 1/s approaches 0 because at that point the parameterized sigmoid function becomes a step function. Essentially, the step function should take on the value 0 outside the surface and 1 inside the surface (I might be getting this flipped).

Thank you very much, but I still don't get it. Registering a parameter 'variance' in SingleVarianceNetwork, self. register_parameter('variance', nn.Parameter(torch.tensor(init_val))). But I don't see anywhere else where the parameter 'variance' is changed and how it participates in the network training.

the variance parameter participates in the forward pass during the alpha calculation.


fix service in project

I changed DB names (and services on the Dockerfile):
[pg_siro]
dbname=siro
user=postgres
password=postgres
host=localhost
[pg_siro_demo]
dbname=siro_demo
user=postgres
password=postgres
host=localhost

I did the change locally. For me it's okay


Use Pure JS gRPC

See https://github.com/wechaty/grpc/issues/126

Done.
Published as<EMAIL_ADDRESS>


Fix: hamburger menu and logo overlap on smaller screens

This pull request addresses the issue where the hamburger menu and logo were overlapping on smaller screens. I have made the necessary changes to fix this bug and ensure proper alignment and display of the elements.
Changes made:

Added responsive classes to adjust the layout of the hamburger menu and logo on smaller screens.

Bhai @sudip57 , there are conflicts please solve them first


The memory in bytes is not readable

I the system consumes considerable amount of memory representing it in bytes is not handy.

Thank you for your feedback. We're working on new frontend so we will address this issue :)


Future idea: Remix Experiments

One thing I've always wanted to be able to do easily is to run experiments (like A/B tests) on stuff that I build.  The base requirements for something like this would be to:

identify the user
load + run some custom code based on who they are
track some success metric

We already have the ability to identify the user and establish a session. And we have the ability to load/run code dynamically. It might be as simple as just loading some custom js/css in the links function or rendering custom markup based on the session data.
Just spitballing some sample code here:
export function loader({ request }) {
  let user = await getUser(request);
  return {
    runSomeExperiment: shouldRunExperiment(user)
  };
}

// Load a custom stylesheet if the user is enrolled in the experiment...
export function links({ data }) {
  let links = [];
  if (data.runSomeExperiment) {
    links.push({ rel: 'stylesheet', href: 'experimental.css' });
  }
  return links;
}

// Render some custom markup if the user is enrolled in the experiment...
export default function MyPage() {
  let data = useRouteData();
  return (
    <div>
      {data.runSomeExperiment && <Experiment />}
    </div>
  );
}

Related: apparently it's difficult to run experiments on Twitter web right now because of the way they do bundling, see https://twitter.com/paularmstrong/status/1399805454663008258. We could show how Remix makes this really easy to do.

added a ticket in linear

Did you guys ever end up putting together any content on this? Would love to check that out!


How to remove 'No Options' option in autocomplete ?

Is there way to remove 'No Options' element from autocomplete when there are no any matching options ?
Check on the documentation and couldn't find anything but rename it

<Autocomplete noOptionsText="" />

@oliviertassinari  still shows the empty option:

In this case, you want to customize the style of the element or you might want to use the freeSolo mode.

Oli

@oliviertassinari  that's the only option I guess, Thanks :)

Still a couple of years on it's not easy to customise. Many of us want to hide the "No options" element when the field is empty ... switching freesolo on and off dynamically won't work with the TS types and not designed to do that. We can't get an easy hook into the no options dom element using css selectors, despite the .MuiAutocomplete-noOptions definition, because this is added to root of DOM.
Be nice if there was an easier way to disable this for an empty field, or dynamically without relying on freeSolo.

The only way I can reliably achieve this is to manage the open state, hold state of the field locally and have a useEffect
const [open, setOpen] = useState(false);

// Use form provider here instead if you want ... or also add some debounce handling ... either way this is your input state
const [fieldValue, setFieldValue] = useState<string>();

  useEffect(() => {
    if (open !== !!fieldValue) {
      setOpen(!!fieldValue);
    }
  }, [open, fieldValue]);

  ...
  <Autocomplete
     ...
     open={open}
     onInputChange={(_evt, val) => setFieldValue(val)}
     onClose={() => setFieldValue(undefined)}
  />

You could easily do this by setting the element to display none.
.MuiAutocomplete-noOptions{
  display: none;
}

note that this element is inside the Popper (MuiPopper-root)

Hiding noOptions as a child of your element won’t work because the popper is added to the root of the DOM and not a child element (you can see by inspecting when it opens), which is why I just prevented it opening.
Not sure why this was closed. A simple api option would be best here.

@tiavina-mika your class path is wrong. As @mbyrne00 said the noOption is not a child of the Autocomplete control. use only the .MuiPopper-root .MuiAutocomplete-noOptions part.

I tried to do it using emotion styled?
export const PopperStyle = styled(Popper)(() => ({
    popperRoot: {
        [`& .MuiAutocomplete-noOptions`]: {
            // display: 'none'
            backgroundColor: 'pink',
        }
    }
}));

and in Autocomplete:
PopperComponent={(props) =>
      <PopperStyle {...props} placement="bottom"/>
  }
   ```
 it  not works, can you help, please?


Prevent log file not found error before any outputs

Kept getting this error no matter what, even running the script locally.
Error server log file not found /root/.vscodium-server/.21b1e2955ddda36eeba3a94e643128e465285b93.log
Added one line to fix.

The server logfile needs to be created from the started server - and if it isn't there, then the connection does not have the info on the ports used... so if I'm not wrong then before this adjustment you got a clear error message (may should include the "did  the server started correctly" note from the other condition though) and afterwards you have no error message but not a working connection - do you?
The main question is: why did the server process started does not create a log file (or how is that named, if different)?


Show message id from transaction inputs

Description
For inputs it displays the transaction id, index and the address, because one can't search for the transaction id it would be nice to get the message id, that had this transaction as payload.
Todo that we need to get the metadata from the output, and from there the message id
Motivation
Makes it easier to find out from where funds were sent
Are you planning to do it yourself in a pull request?
No.

This commit 2a6c56a437df73f5882fd4f20b89f054a64a4128 links the transaction id to the message it comes from.


Non Steam Deck Arch support?

I really like your GUI on the steam deck and I wanted to use it on my main desktop, will you eventually release a script for regular Arch Linux users?

Time permitting this may be something that I olook into in the future, even though my own personal use cases tend to favor Fedora based distros.
The source code is here for others to compile and use however they want, and I welcome quality pull requests to fix or add things like this.


Map concourse https port when using docker-cpi

Telling the docker-cpi to map port 443 will make concourse accessible from the host

force pushed changes

@bodymindarts thanks!


training failed on cloud.annotations.ai

I followed instructions on https://cloud.annotations.ai/workshops/classification/index.html
but when I run 'cacli train', I get error msg (from cacli logs) like this:
'urllib.error.URLError: <urlopen error [Errno 101] Network is unreachable>'
can anybody help me? I don't find any document about it.
thanks.
the full log is as blow:
~ % cacli logs model-wd5wf7ey
training-I5_hf_RGR: Training with training/test data at:
training-I5_hf_RGR:   DATA_DIR: /mnt/data/gesture-detect
training-I5_hf_RGR:   MODEL_DIR: /job/model-code
training-I5_hf_RGR:   TRAINING_JOB:
training-I5_hf_RGR:   TRAINING_COMMAND: cd "$(dirname "$(find . -name "start.sh" -maxdepth 2 | head -1)")" && chmod 777 ./start.sh && ./start.sh 1000
training-I5_hf_RGR: Wed May 20 01:47:20 UTC 2020: Running Tensorflow job
training-I5_hf_RGR: Collecting Cython
training-I5_hf_RGR:   Downloading Cython-0.29.18-cp36-cp36m-manylinux1_x86_64.whl (2.0 MB)
training-I5_hf_RGR: Collecting contextlib2
training-I5_hf_RGR:   Downloading contextlib2-0.6.0.post1-py2.py3-none-any.whl (9.8 kB)
training-I5_hf_RGR: Collecting matplotlib
training-I5_hf_RGR:   Downloading matplotlib-3.2.1-cp36-cp36m-manylinux1_x86_64.whl (12.4 MB)
training-I5_hf_RGR: Requirement already satisfied: pyparsing!=2.0.4,!=2.1.2,!=2.1.6,>=2.0.1 in /opt/anaconda/envs/wmlce/lib/python3.6/site-packages (from matplotlib) (2.4.7)
training-I5_hf_RGR: Collecting cycler>=0.10
training-I5_hf_RGR:   Downloading cycler-0.10.0-py2.py3-none-any.whl (6.5 kB)
training-I5_hf_RGR: Requirement already satisfied: numpy>=1.11 in /opt/anaconda/envs/wmlce/lib/python3.6/site-packages (from matplotlib) (1.16.6)
training-I5_hf_RGR: Requirement already satisfied: python-dateutil>=2.1 in /opt/anaconda/envs/wmlce/lib/python3.6/site-packages (from matplotlib) (2.8.1)
training-I5_hf_RGR: Collecting kiwisolver>=1.0.1
training-I5_hf_RGR:   Downloading kiwisolver-1.2.0-cp36-cp36m-manylinux1_x86_64.whl (88 kB)
training-I5_hf_RGR: Requirement already satisfied: six in /opt/anaconda/envs/wmlce/lib/python3.6/site-packages (from cycler>=0.10->matplotlib) (1.12.0)
training-I5_hf_RGR: Installing collected packages: Cython, contextlib2, cycler, kiwisolver, matplotlib
training-I5_hf_RGR:   WARNING: The scripts cygdb, cython and cythonize are installed in '/home/pwrai/.local/bin' which is not on PATH.
training-I5_hf_RGR:   Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
training-I5_hf_RGR: Successfully installed Cython-0.29.18 contextlib2-0.6.0.post1 cycler-0.10.0 kiwisolver-1.2.0 matplotlib-3.2.1
training-I5_hf_RGR: Collecting pycocotools==2.0.0
training-I5_hf_RGR:   Downloading pycocotools-2.0.0.tar.gz (1.5 MB)
training-I5_hf_RGR: Collecting coremltools==3.3
training-I5_hf_RGR:   Downloading coremltools-3.3-cp36-none-manylinux1_x86_64.whl (3.4 MB)
training-I5_hf_RGR: Collecting tfcoreml==1.1
training-I5_hf_RGR:   Downloading tfcoreml-1.1-py3-none-any.whl (44 kB)
training-I5_hf_RGR: Collecting tensorflowjs==1.4.0
training-I5_hf_RGR:   Downloading tensorflowjs-1.4.0-py3-none-any.whl (56 kB)
training-I5_hf_RGR: Collecting tensorflow-hub==0.3.0
training-I5_hf_RGR:   Downloading tensorflow_hub-0.3.0-py2.py3-none-any.whl (73 kB)
training-I5_hf_RGR: Collecting h5py==2.8.0
training-I5_hf_RGR:   Downloading h5py-2.8.0-cp36-cp36m-manylinux1_x86_64.whl (2.8 MB)
training-I5_hf_RGR: Collecting numpy==1.17.5
training-I5_hf_RGR:   Downloading numpy-1.17.5-cp36-cp36m-manylinux1_x86_64.whl (20.0 MB)
training-I5_hf_RGR: Collecting sympy==1.5.1
training-I5_hf_RGR:   Downloading sympy-1.5.1-py2.py3-none-any.whl (5.6 MB)
training-I5_hf_RGR: Collecting mpmath==1.1.0
training-I5_hf_RGR:   Downloading mpmath-1.1.0.tar.gz (512 kB)
training-I5_hf_RGR: Building wheels for collected packages: pycocotools, mpmath
training-I5_hf_RGR:   Building wheel for pycocotools (setup.py): started
training-I5_hf_RGR:   Building wheel for pycocotools (setup.py): finished with status 'done'
training-I5_hf_RGR:   Created wheel for pycocotools: filename=pycocotools-2.0.0-cp36-cp36m-linux_x86_64.whl size=274278 sha256=6cc972c4dd4231bc7443bcad0252c5ab76859eb0fdec39f6b547856878b69e20
training-I5_hf_RGR:   Stored in directory: /home/pwrai/.cache/pip/wheels/64/7a/c0/ac8f633d11a5f1a6902c72acb9fa828a2bb3639afba4e94a6c
training-I5_hf_RGR:   Building wheel for mpmath (setup.py): started
training-I5_hf_RGR:   Building wheel for mpmath (setup.py): finished with status 'done'
training-I5_hf_RGR:   Created wheel for mpmath: filename=mpmath-1.1.0-py3-none-any.whl size=532239 sha256=0e82a58ce4c6d8eec8f1f1a72b6fff85b612f06714d710a34577468815b84446
training-I5_hf_RGR:   Stored in directory: /home/pwrai/.cache/pip/wheels/e8/38/69/aa17553ad31f09ff5fa44c8a1a6c5b47e7c9261e9c7c16b9fb
training-I5_hf_RGR: Successfully built pycocotools mpmath
training-I5_hf_RGR: Installing collected packages: pycocotools, coremltools, tfcoreml, tensorflowjs, tensorflow-hub, h5py, numpy, sympy, mpmath
training-I5_hf_RGR:   WARNING: The script coremlconverter is installed in '/home/pwrai/.local/bin' which is not on PATH.
training-I5_hf_RGR:   Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
training-I5_hf_RGR:   WARNING: The scripts tensorflowjs_converter and tensorflowjs_wizard are installed in '/home/pwrai/.local/bin' which is not on PATH.
training-I5_hf_RGR:   Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
training-I5_hf_RGR:   WARNING: The scripts f2py, f2py3 and f2py3.6 are installed in '/home/pwrai/.local/bin' which is not on PATH.
training-I5_hf_RGR:   Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
training-I5_hf_RGR:   WARNING: The script isympy is installed in '/home/pwrai/.local/bin' which is not on PATH.
training-I5_hf_RGR:   Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
training-I5_hf_RGR: Successfully installed coremltools-3.3 h5py-2.8.0 mpmath-1.1.0 numpy-1.17.5 pycocotools-2.0.0 sympy-1.5.1 tensorflow-hub-0.3.0 tensorflowjs-1.4.0 tfcoreml-1.1
training-I5_hf_RGR: /////////////////////////////
training-I5_hf_RGR: // Training classification //
training-I5_hf_RGR: /////////////////////////////
training-I5_hf_RGR: 2020-05-20 01:47:57.573861: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcudart.so.10.1
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR: WARNING: Logging before flag parsing goes to stderr.
training-I5_hf_RGR: W0520 01:47:59.027134<PHONE_NUMBER>67648 module_wrapper.py:139] From /job/model-code/src/classification/retrain.py:1313: The name tf.app.run is deprecated. Please use tf.compat.v1.app.run instead.
training-I5_hf_RGR:
training-I5_hf_RGR: W0520 01:47:59.027679<PHONE_NUMBER>67648 module_wrapper.py:139] From /job/model-code/src/classification/retrain.py:970: The name tf.logging.set_verbosity is deprecated. Please use tf.compat.v1.logging.set_verbosity instead.
training-I5_hf_RGR:
training-I5_hf_RGR: W0520 01:47:59.027797<PHONE_NUMBER>67648 module_wrapper.py:139] From /job/model-code/src/classification/retrain.py:970: The name tf.logging.INFO is deprecated. Please use tf.compat.v1.logging.INFO instead.
training-I5_hf_RGR:
training-I5_hf_RGR: W0520 01:47:59.027885<PHONE_NUMBER>67648 module_wrapper.py:139] From /job/model-code/src/classification/retrain.py:914: The name tf.gfile.Exists is deprecated. Please use tf.io.gfile.exists instead.
training-I5_hf_RGR:
training-I5_hf_RGR: W0520 01:47:59.028026<PHONE_NUMBER>67648 module_wrapper.py:139] From /job/model-code/src/classification/retrain.py:916: The name tf.gfile.MakeDirs is deprecated. Please use tf.io.gfile.makedirs instead.
training-I5_hf_RGR:
training-I5_hf_RGR: W0520 01:47:59.028207<PHONE_NUMBER>67648 module_wrapper.py:139] From /job/model-code/src/classification/retrain.py:168: The name tf.gfile.Walk is deprecated. Please use tf.io.gfile.walk instead.
training-I5_hf_RGR:
training-I5_hf_RGR: W0520 01:47:59.032017<PHONE_NUMBER>67648 module_wrapper.py:139] From /job/model-code/src/classification/retrain.py:181: The name tf.logging.info is deprecated. Please use tf.compat.v1.logging.info instead.
training-I5_hf_RGR:
training-I5_hf_RGR: I0520 01:47:59.032114<PHONE_NUMBER>67648 retrain.py:181] Looking for images in 'coffee'
training-I5_hf_RGR: W0520 01:47:59.032187<PHONE_NUMBER>67648 module_wrapper.py:139] From /job/model-code/src/classification/retrain.py:184: The name tf.gfile.Glob is deprecated. Please use tf.io.gfile.glob instead.
training-I5_hf_RGR:
training-I5_hf_RGR: I0520 01:47:59.039404<PHONE_NUMBER>67648 retrain.py:181] Looking for images in 'victory'
training-I5_hf_RGR: I0520 01:47:59.046477<PHONE_NUMBER>67648 resolver.py:79] Using /tmp/tfhub_modules to cache modules.
training-I5_hf_RGR: I0520 01:47:59.047822<PHONE_NUMBER>67648 resolver.py:398] Downloading TF-Hub Module 'https://tfhub.dev/google/imagenet/mobilenet_v1_100_224/feature_vector/1'.
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR:
training-I5_hf_RGR: Traceback (most recent call last):
training-I5_hf_RGR:     encode_chunked=req.has_header('Transfer-encoding'))
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/http/client.py", line 1262, in request
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/http/client.py", line 1308, in _send_request
training-I5_hf_RGR:     self.endheaders(body, encode_chunked=encode_chunked)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/http/client.py", line 1257, in endheaders
training-I5_hf_RGR:     self._send_output(message_body, encode_chunked=encode_chunked)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/http/client.py", line 1036, in _send_output
training-I5_hf_RGR:     self.send(msg)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/http/client.py", line 974, in send
training-I5_hf_RGR:     self.connect()
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/http/client.py", line 1415, in connect
training-I5_hf_RGR:     super().connect()
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/http/client.py", line 946, in connect
training-I5_hf_RGR:     (self.host,self.port), self.timeout, self.source_address)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/socket.py", line 724, in create_connection
training-I5_hf_RGR:     raise err
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/socket.py", line 713, in create_connection
training-I5_hf_RGR:     sock.connect(sa)
training-I5_hf_RGR: OSError: [Errno 101] Network is unreachable
training-I5_hf_RGR:
training-I5_hf_RGR: During handling of the above exception, another exception occurred:
training-I5_hf_RGR:
training-I5_hf_RGR: Traceback (most recent call last):
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/runpy.py", line 193, in _run_module_as_main
training-I5_hf_RGR:     "main", mod_spec)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/runpy.py", line 85, in _run_code
training-I5_hf_RGR:     exec(code, run_globals)
training-I5_hf_RGR:   File "/job/model-code/src/classification/retrain.py", line 1313, in
training-I5_hf_RGR:     tf.app.run(main=main, argv=[sys.argv[0]] + unparsed)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/site-packages/tensorflow_core/python/platform/app.py", line 40, in run
training-I5_hf_RGR:     _run(main=main, argv=argv, flags_parser=_parse_flags_tolerate_undef)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/site-packages/absl/app.py", line 300, in run
training-I5_hf_RGR:     _run_main(main, args)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/site-packages/absl/app.py", line 251, in _run_main
training-I5_hf_RGR:     sys.exit(main(argv))
training-I5_hf_RGR:   File "/job/model-code/src/classification/retrain.py", line 998, in main
training-I5_hf_RGR:     module_spec = hub.load_module_spec(FLAGS.tfhub_module)
training-I5_hf_RGR:   File "/home/pwrai/.local/lib/python3.6/site-packages/tensorflow_hub/module.py", line 60, in load_module_spec
training-I5_hf_RGR:     path = registry.resolver(path)
training-I5_hf_RGR:   File "/home/pwrai/.local/lib/python3.6/site-packages/tensorflow_hub/registry.py", line 42, in call
training-I5_hf_RGR:     return impl(*args, **kwargs)
training-I5_hf_RGR:   File "/home/pwrai/.local/lib/python3.6/site-packages/tensorflow_hub/compressed_module_resolver.py", line 103, in call
training-I5_hf_RGR:     self._lock_file_timeout_sec())
training-I5_hf_RGR:   File "/home/pwrai/.local/lib/python3.6/site-packages/tensorflow_hub/resolver.py", line 400, in atomic_download
training-I5_hf_RGR:     download_fn(handle, tmp_dir)
training-I5_hf_RGR:   File "/home/pwrai/.local/lib/python3.6/site-packages/tensorflow_hub/compressed_module_resolver.py", line 98, in download
training-I5_hf_RGR:     response = url_opener.open(request)
training-I5_hf_RGR:
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/urllib/request.py", line 526, in open
training-I5_hf_RGR:     response = self._open(req, data)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/urllib/request.py", line 544, in _open
training-I5_hf_RGR:     '_open', req)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/urllib/request.py", line 504, in _call_chain
training-I5_hf_RGR:     result = func(*args)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/urllib/request.py", line 1361, in https_open
training-I5_hf_RGR:     context=self._context, check_hostname=self._check_hostname)
training-I5_hf_RGR:   File "/opt/anaconda/envs/wmlce/lib/python3.6/urllib/request.py", line 1320, in do_open
training-I5_hf_RGR:     raise URLError(err)
training-I5_hf_RGR: urllib.error.URLError: <urlopen error [Errno 101] Network is unreachable>
training-I5_hf_RGR: CACLI-TRAINING-FAILED
training-I5_hf_RGR: Training exited with error code 1
training-I5_hf_RGR: Failed: learner_exit_code: 1

This is a known issue that popped up yesterday, it seems like it only happens on classification when trying to download from tfhub, and only fails ~60% of the time. Im looking into whether it’s an issue with tfhub or a connection problem on WML’s end.
It seems to be able to download all the python packages and load images from the bucket just fine

@softwind9 If you’re comfortable with using jupyter notebooks, you could use the “export notebook” feature as a temporary workaround.
You can run the notebook locally or import it into Watson studio/ google collab to run on a gpu

@bourdakos1   Thanks for your reply.
I'm not an expert on "Jupyter notebook", but I will try it.
Thanks a lot.

@softwind9 WML issued a fix, so training should work now. Feel free to reopen if you’re still having problems


fix(create-vite): fix broken vite logo in react when base changed

Description
After using create-vite to generate a React project, in a production build the Vite logo will break when setting the base URL to anything except the default /. This came up for me when trying to build GitHub Pages in a repo of mine, which requires the base to match the repo name.
For example, this build process will result in a broken Vite logo:
# To replicate the issue
npm run build -- --base /test
npm run preview -- --base /test

This occurs because the img src directly refers to the generated /vite.svg and React does not preprocess src attributes to add the configured base.
As suggested in #7358 (found via #10601), the solution is to import vite.svg in the same way as react.svg already is. This MR implements that solution in to the templates to prevent confusion in the future.
Note: This may also apply to the preact templates. However, I've not modified them as I'm not currently familiar with preact.
Without the fix, using a modified base:

With the fix, using a modified base:

Additional context
If using npm run dev from the generated package.json, the issue will not show up. However, the issue will show up when using npm run build followed by npm run preview.
# This will replicate the issue
npm run build -- --base /test
npm run preview -- --base /test

# This will NOT replicate the issue
npm run dev -- --base /test

I've tested this by modifying a generated project to verify the results of a fix. However, I've not tested this using npm create vite... as I'm unsure how to perform a representative test via that method.

What is the purpose of this pull request?

[X] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the PR Title Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Ideally, include relevant tests that fail without this PR but pass with it.

This seems to affect all templates (except Vue because it auto imports it), maybe we should update them all at once.

I'll take a look at the other templates @bluwy. 👍
It's been a few years since I last did any serious front-end dev (my experience is in backend DevEx/Platforms engineering) and I only started trying out Vite today on a whim, but this is a good excuse to brush up. I'll let you know if I have any issues.
I'll mark this as draft in the meantime.

I've pushed fixes for all of the other templates that needed them. I've added further info below in case they help anyone.
Since I copied the changed files from my generated test projects back to the templates, there are a couple of whitespace differences. I've left them in since that means that the templates will now be closer to the files they generate. I'm happy to remove the whitespace changes if they're not desired.
Yep, they're all broken (except Vue)
Sure enough, I can confirm it is broken in the other templates:

(Lit doesn't have a preview as it generates only a component -- I checked the generated source code for the component manually.)
For completeness, I checked Vue as well -- as expected, it works without further modification (both JS and TS variants):

Minimising human error
I cooked up a script to create and run all of the different templated projects one by one:
#!/usr/bin/env bash
trap '' INT # Allow interrupting `npm run preview` servers with Ctrl-C without terminating the whole loop

echo No Base
for template in lit lit-ts preact preact-ts svelte svelte-ts vanilla vanilla-ts vue vue-ts; do
	echo "$template"
	if [ ! -d "$template" ]; then
		echo Creating project for ${template}...
		npm create vite@latest "$template" -- --template "$template"
		( cd "$template" && npm install )
	fi

	echo "${template}: Default base"
	( cd "$template" && npm run build )
	# lit only generates a component, so it has no preview
	if [[ "$template" != lit* ]]; then
		( cd "$template" && npm run preview -- --open )
	fi

	echo "${template}: Configured base"
	( cd "$template" && npm run build -- --base /test )
	# lit only generates a component, so it has no preview
	if [[ "$template" != lit* ]]; then
		( cd "$template" && npm run preview -- --open --base /test )
	fi
done

trap INT # Reset interrupt capture back to default

The script uses create-vite to generate a project using each template and installs its dependencies. It then builds and previews each project twice: once with the default base, and once with a configured /test base.
I ran this script twice. Once without any fixes. Then once more after I applied the fixes. This made it very easy to see which projects worked without changes (Vue) and which required fixes (the rest).
To minimise the chance for mistakes, since I don't know a way to generate a new project from an updated template that hasn't been merged upstream, I instead each fixed file from the generated project back to the template. For example:
file=vanilla-ts/src/main.ts ; cp $file ../vite/packages/create-vite/template-$file

As noted above, this resulted in minor whitespace changes in two cases, svelte and svelte-ts, which I've left in as that brings the templates closer to the files they generate.

Re-opened for review.


Attributes with type datetime casts to str after reboot on persistent sensors

I have a sensor in the pyscript domain with a dict with a number of elements as attributes in the form:
<class 'datetime.datetime'>: <class 'float'>
<class 'datetime.datetime'>: <class 'float'>
e.g.:
2023-04-05T00:00:00+02:00:  2.1957
2023-04-05T01:00:00+02:00:  2.2242
and so on...
After HA reboots, state.persist works fine for the float type but the datetime type is casted as str after reboot. "Looks" the same but is no longer a datetime object.
I expected the type for datetime to be preserved after reboot. I can of course handle this on startup but that's just a nasty workaround :-)
HA Supervised, Docker on Debian 11.
Home Assistant 2023.3.6
Supervisor 2023.03.3
Frontend 20230309.1

Issue remains (as expected) on pyscript 1.4.0 and Supervisor 2023.04.0

Looking at the code I see that this might be because of how the HA class RestoreStateData works. I don't fully understand what is going on but maybe this isn't even a pyscript issue?


[FALSE-POSITIVE]

Domains or links
https://1040taxbiz.com
1040taxbiz.com
https://www.1040taxbiz.com
More Information
Incorrectly marked as Phishing on Phishtank or OpenPhish?
we found some leftover code from wordpress plugin
Have you requested removal from other sources?
Socradar
cluster25
Cyradar
Additional context
We have moved the site to a new IP Address and Server.
:exclamation:
We understand being listed on a Phishing Database like this can be frustrating and embarrassing for many web site owners. The first step is to remain calm. The second step is to rest assured one of our maintainers will address your issue as soon as possible. Please make sure you have provided as much information as possible to help speed up the process.
Send a Pull Request for faster removal
Users who understand github and creating Pull Requests can assist us with faster removals by sending a PR to mitchellkrogza/phishing repository, on the falsepositive.list file

https://github.com/mitchellkrogza/phishing/blob/main/falsepositive.list
Please include the same above information to help speed up the whitelisting process.

Already whitelisted. Closing.


imgPlaceholder.vue required a loader

Hey, great project!
Have just tried out the basic config and run into this:
./node_modules/tiptap-extension-image-upload/src/imagePlaceholder.ts
Module parse failed: Unexpected token (5:7)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
| import imgPlaceholder from './imgPlaceholder.vue'
|
> export interface ImagePlaceholderOptions {
|   inline: boolean
|   HTMLAttributes: Record<string, any>

I'm using nextjs and not vue.
Are there any prerequisites of using this extension?

Same issue here! I'm trying to use with react

Same issue here!


loader: assorted fixes

Depends on https://github.com/bytecodealliance/wasmtime-py/pull/221.
This is an incremental but substantial improvement, to the point where I'd say I consider this implementation correct, or very close to correct, according to my understanding of the importlib hooks involved.
It is however still not thread-safe, I will likely address that after adding component support.

@alexcrichton I have a prototype of an importlib loader for components that builds on top of these fixes but I'll probably hold off submitting it until you've had a chance to review #221 and #222.

Rebased.

Thank you very much for this! All looks great to me and I'm glad this has a better pair of eyes on it than my own "not very Python trained" eyes.

I'm glad this has a better pair of eyes on it than my own "not very Python trained" eyes.

Honestly, this particular bit of the Python library has almost nobody trained in it, and it's definitely one of the most advanced of advanced topics any Python programmer will ever explore, save for perhaps the more obscure FFI-related ones. It was really quite difficult for me to get my head around it, partly due to how obscure it is, partly due to the peculiar state of the docs, and I've spent basically a workday or two reading sources of the Python internals and comparing them across versions.

IIRC the initial bits here were copy/pasted from assorted blogs/stack overflow posts, so I suspect you've done much more studying already than I initially did!


Some performance enhancements to model.py

Most of the enhancements are the result of removing extra dictionary copies/creations.

Improve dictionary handling in .from_dict() methods. If passing kwargs to method, the new methods are faster.
Remove dictionary unpackings where they are unnecessary.
Create a _GEO_TYPES dictionary to avoid the creation of a list in decode()

A comparison of the new/old approaches in .from_dict(), where m is a mapping of length 8.
In [50]: %timeit from_dict2(**m)  # new
695 ns ± 11 ns per loop (mean ± std. dev. of 7 runs, 1,000,000 loops each)

In [51]: %timeit from_dict(**m)  # old
1.15 µs ± 6.93 ns per loop (mean ± std. dev. of 7 runs, 1,000,000 loops each)

I'm going to merge this and cherry pick for 1.9.4.


ImportError: Could not import 'boss.authentication.TokenAuthentication' for API setting 'DEFAULT_AUTHENTICATION_CLASSES'. ModuleNotFoundError: No module named 'boss'.

I am getting ImportError: Could not import 'boss.authentication.TokenAuthentication' for API setting 'DEFAULT_AUTHENTICATION_CLASSES'. ModuleNotFoundError: No module named 'boss'. when trying to run my server

Are you running a Boss DB? If you're not, you probably don't want to use this package. This package's intended use is for connecting Boss with Keycloak.

Are you running a Boss DB? If you're not, you probably don't want to use this package. This package's intended use is for connecting Boss with Keycloak.

Noo am not, am trying to use django withkeycloak authentication. I followed
your tutorial but I keep getting either template not found
/openid/callback/code=134323....
On Thu, Jan 7, 2021 at 4:39 PM Tim Gion<EMAIL_ADDRESS>wrote:

Are you running a Boss DB? If you're not, you probably don't want to use
this package. This package's intended use is for connecting Boss with
Keycloak.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jhuapl-boss/boss-oidc2/issues/1#issuecomment-756121983,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUT5PQI7S6CK4RGCP7FXR3SYW2RZANCNFSM4VYUCY3A
.

--
Kind Regards,
Daniel Karama,
Information Technologiy Consultant

Noo am not, am trying to use django withkeycloak authentication. I followed
your tutorial but I keep getting either template not found
/openid/callback/code=134323....
On Thu, Jan 7, 2021 at 4:39 PM Tim Gion<EMAIL_ADDRESS>wrote:

Are you running a Boss DB? If you're not, you probably don't want to use
this package. This package's intended use is for connecting Boss with
Keycloak.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jhuapl-boss/boss-oidc2/issues/1#issuecomment-756121983,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUT5PQI7S6CK4RGCP7FXR3SYW2RZANCNFSM4VYUCY3A
.

--
Kind Regards,
Daniel Karama,
Information Technologiy Consultant

Noo am not, am trying to use django withkeycloak authentication. I followed your tutorial but I keep getting either template not found /openid/callback/code=134323....

We make no guarantees that this work with a generic Django setup. You can see how our Django is setup here: https://github.com/jhuapl-boss/boss
This will have boss.authentication.TokenAuthentication but I have no idea if that's appropriate for your configuration.

Noo am not, am trying to use django withkeycloak authentication. I followed your tutorial but I keep getting either template not found /openid/callback/code=134323....

We make no guarantees that this work with a generic Django setup. You can see how our Django is setup here: https://github.com/jhuapl-boss/boss
This will have boss.authentication.TokenAuthentication but I have no idea if that's appropriate for your configuration.