Was working great and now won't authorise on 3456

Any thoughts or any similar experiences?
thanks,
Irwin

I have the same problem as of yesterday. I get Authentication failed: “no body”. Occasionally it seems to succeed.

Same here, Authentication failed: “no body” most of the time after Node-Red restart or Re-innitialised.

Same here. Tested with varoius port.
I have compared an old session file and a new, there r differences.
The old on work as normal (second amazon acc on 3457).
With "node-red-contrib-alexa-remote-fork" & "node-red-contrib-alexa-remote2-v2" same problems.
No body

Same problems. I need to reply the process about 15 times until I get ready/success on my init nodes. Appeared two days ago for the first time.

Having the same issue. Have to set my initialize flow on a catch error loop until it starts working. Sometimes it takes several hours before it is successful

@kmorrow429 if you don't want to wait for hours I found that if you edit the account, don't change any setting, just update then redeploy it eventually works again after 5-10 minutes

If it's initialized, you have the cookie in a textfile and everything is ok, how long will it stay in this state? Anyone knows?

@andesse for me it stays initialised unless I restart Node Red, Deploy any of the Alexa Remote2 nodes or Reinitialise (I've got a flow that réinitialises automatically if some speak routines don't work anymore), usually happens every 3 days

@notownblues I had tried that, but when it didn't work immediately I tried deleting the auth file and a couple of restarts. If it happens again, I'll try that and leave it for a while to see if it works

Same problem here (in the UK) for the last couple of days. Authenticates fine after several manual restart flows and manual injected initialise attempts. But the next time it tries to refresh (I have it timed for once an hour) it fails again.
Errors I see are mostly "Authentication failed: "no body"" and separately "failed to load routines: "routines.map is not a function""

Exactly the same Problem in Germany (Service Host: layla.amazon.de)

Question:
Does it appear maybe when you run two alexa accounts in node red? I just added a second one to Node-Red one day before this problem happened. I am not at home since three days, so I can't try it out. Btw, I'm from Germany.

Question:
Does it appear maybe when you run two alexa accounts in node red? I just added a second one to Node-Red one day before this problem happened. I am not at home since three days, so I can't try it out. Btw, I'm from Germany.

No, I am only using one account and have the same problem. I am from germany, too.

Question:
Does it appear maybe when you run two alexa accounts in node red?

No, I have only one alexa account. Same Error after Deactivation of 2fa in Alexa. Setting "Auto Init" to off in Node-RED-Alexa Configuration-Node and Using Node "Alexa init" solves the problem only one times.

Updating the alexa-remote2 dependency to v3.8 should do the trick.

Which contrib is it?

Updating the alexa-remote2 dependency to v3.8 should do the trick.

Which contrib is it?

Updating the alexa-remote2 dependency to v3.8 should do the trick.

Wich contrib do you use?

Updating the alexa-remote2 dependency to v3.8 should do the trick.

I'm using "node-red-contrib-alexa-cakebaked" V. 4.0.2. On GitHub this Version is commented with "Updates dependency alexa-remote2 to v3.7.1". I alredy searched for newer Versions, but I didn't found one. Where can I get v3.8?

Thank you, andesse. If no one will find a workaround, I wait and hope, the developer resolves the problem.

Are you sure 3.8 fixes it?  I've been running it over a week have been experiencing the same "Authenication Failed: No Body" errors.

I tried "3.8" today without success.

So I've debugged the Authentication HTTP Requests and they suddenly respond with 503 'Service Unavailable' on /api/bootstrap?version=0.
Not sure if this is because they've changed something in their API or because it really is unavailable, but I'm afraid it's the former.

Found the issue. The Accept header is not sent in the request. As suspected, the issue is in alexa-remote2 not here. I'll make a PR there shortly.
If you don't want to wait find this file .node-red/node_modules/alexa-remote2/alexa-remote.js and add 'Accept': 'application/json', to the headers. That would be in line 797. After adding this and restarting node-red (so that it picks up the changes) it works again for me.
Example:
let options = {
            host: flags.host || this.baseUrl,
            path: '',
            method: 'GET',
            timeout: flags.timeout || 10000,
            headers: {
                'User-Agent' : this._options.userAgent,
                'Content-Type': 'application/json; charset=UTF-8',
		'Accept': 'application/json',
                'Referer': `https://alexa.${this._options.amazonPage}/spa/index.html`,
                'Origin': `https://alexa.${this._options.amazonPage}`,
                //'Content-Type': 'application/json',
                //'Connection': 'keep-alive',
                'csrf' : this.csrf,
                'Cookie' : this.cookie,
                'Accept-Encoding': 'gzip,deflate'
            }
        };

@bbindreiter thanks! Awesome you figured it out!

Found the issue. The Accept header is not sent in the request. As suspected, the issue is in alexa-remote2 not here. I'll make a PR there shortly.
If you don't want to wait find this file .node-red/node_modules/alexa-remote2/alexa-remote.js and add 'Accept': 'application/json', to the headers. That would be in line 797. After adding this and restarting node-red (so that it picks up the changes) it works again for me.
Example:
let options = {
            host: flags.host || this.baseUrl,
            path: '',
            method: 'GET',
            timeout: flags.timeout || 10000,
            headers: {
                'User-Agent' : this._options.userAgent,
                'Content-Type': 'application/json; charset=UTF-8',
		'Accept': 'application/json',
                'Referer': `https://alexa.${this._options.amazonPage}/spa/index.html`,
                'Origin': `https://alexa.${this._options.amazonPage}`,
                //'Content-Type': 'application/json',
                //'Connection': 'keep-alive',
                'csrf' : this.csrf,
                'Cookie' : this.cookie,
                'Accept-Encoding': 'gzip,deflate'
            }
        };

Just did the above and it now works perfect again. Thank you so much @bbindreiter!

@bbindreiter thanks

Confirm working with above Accept header change here too.  Cheers @bbindreiter

What I am really curious about is, why did it worked for a quiet long time and now was suddenly broken...

I'd guess it'll be down to Amazon changing their services breaking the requests the remote2 lib makes.

Hmm, think I was too quick to say the header change works for me. It may have just worked once.
Will look at doing a clean install in the next few days to see if that helps.

@bbindreiter Thank you so much!

@bbindreiter Thank you!

@bbindreiter Thank you so much, been fighting with this for a few days :-)

@bbindreiter thanks a lot my man, If it weren't for you guys I wouldn't have a smart home, ty really

Thank you, it works like a charm!

@bbindreiter you are a hero!

alexa-remote 3.8.1 is coming to npm just now. Have fun and thank you @bbindreiter

@bbindreiter  Großen Dank auch von mir!
Gruß Matten Matten

Thank you very much everyone. Let's hope for an updated version soon.

Unfortunately, for me it's not working.
I still get the Authentication failed: "No body" message.
After I go to the IP:3456 to authenticate with my credentials, it seems that it does not create the cookie file and after Initialise, I get again the message to go the IP:3456 page

@woody4165
Nodered restartet?

Yes, I have NR in a Proxmox Container and I did first a service nodered restart and also a reboot after.

strange, you are also sure that the files (3) have also been overwritten?
Gruß
Matten Matten

Ops.....
I was modifying a copy of the alexa-remote.js file and not the one in the .node-red/node_modules/alexa-remote2
So, now all is working fine!

I also have the same problem Accaunt Alexa Italia
in addition to me when I restart even before it does not keep me authenticating I have Domoticz and red node on a raspberry
and as a path I went to /home/pi/cookie/alexa.cookie

I also have the same problem Accaunt Alexa Italia
in addition to me when I restart even before it does not keep me authenticating I have Domoticz and red node on a raspberry
and as a path I went to /home/pi/cookie/alexa.cookie

Have you followed the instructions here ?
https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/22#issuecomment-853171093

Have you followed the instructions here ?

No sorry I'm Italian and I'm using google translator to understand
and maybe I missed something
I don't use alexa-remote2
but node-red-contrib-alexa-cakebaked 4.0.2 i believed that solution was for remote2 not cakebaked

@saviothecnic follow the instructions, I'm using cakebaked and it's worked for me

ok i removed
node-red-contrib-alexa-cakebaked 4.0.2
and installed node-red-contrib-alexa-remote2-v2
and modified as you suggested it now works again Only that at every restart it always asks me to re-authenticate but only if I restart raspberry my cookie path is this
/home/pi/cookie/alexa.cookie

I am to stupid to find the file.
My system is Raspberrymatic based Redmatic. Can someone help me and comment the path that I need to use in ssh to find It?
Thanks in advance

It might be
/usr/local/addons/redmatic/var/node_modules/node-red-contrib-opcua/node_modules
I did Google Redmatic "path" to "node-red" modules   (Did you try that?)
and found this
https://github.com/mikakaraila/node-red-contrib-opcua/issues/193
Can't help you otherwise.

My system is Raspberrymatic based Redmatic. Can someone help me and
comment the path that I need to use in ssh to find It?
Thanks in advance
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/22#issuecomment-855255298,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENIQ2JM4WNTC2PPMHZMLITTRI6VNANCNFSM45ACHLFQ
.

@cakebake hasn't been active since the beginning of February. I'm not sure if he's still using this node at all otherwise he'd have written something in here 🤷♂
Even though I want to avoid it if somehow possible, maybe it's time to fork this node once again. I'm sure there are people out there not finding their way to github and are getting frustrated.

@cakebake hasn't been active since the beginning of February. I'm not sure if he's still using this node at all otherwise he'd have written something in here 🤷♂
Even though I want to avoid it if somehow possible, maybe it's time to fork this node once again. I'm sure there are people out there not finding their way to github and are getting frustrated.

I already said you were a hero! 🙂

@bwims thanks, found it at the end... Not the best in console using 🤣

@bbindreiter just fork it.
I personally, as an "end consumer" am just happy when I have a contrib that runs stable and gets a new update if not so :)

Sad to say but it needs to be forked (again).
It needs a maintainer who has the time/attention to up version when the key dependency (alexa-remote) gets updates.
Unfortunately @cakebake mustn't have this time/attention, evidenced by the multiple releases of alexa-remote since 18 April v3.7.2 with no version update here.  I'd really rather be getting updates via the node red palette manager than hacking at node modules.

ditto!
On Sat, 5 Jun 2021 at 21:19, Peter Stevenson @.***>
wrote:

Sad to say but it needs to be forked (again).
It needs a maintainer who has the time/attention to up version when the
key dependency (alexa-remote) gets updates.
Unfortunately @cakebake https://github.com/cakebake mustn't have this
time/attention, evidenced by the multiple releases of alexa-remote since 18
April v3.7.2 with no version update here. I'd really rather be getting
updates via the node red palette manager than hacking at node modules.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/22#issuecomment-855290713,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AENIQ2KKB3LFGW4SAALOES3TRKBGLANCNFSM45ACHLFQ
.

And it is true there are 4 versions that are photocopies of each other
and it just creates confusion I see that some are updated for 11 months others for 4 months others for 2 months another for 1 month
we all automation enthusiasts have alexa and being able to plagiarize it for our purposes thanks to the red knot is very nice
but you need a knot that always stays in step with adj
by Amazon Alexa

this is pretty much one of the most-important (for me - and others?) node-red modules - alexa has gained imho dominance as an intelligent UI for smart-homes and hence strong and reliable integration with node-red is essential.  I'd be happy to pay a suitable maintainer (or even offer my services if all else fails!!!)

@bbindreiter Vielen Dank Bernd, tolle Arbeit!!
I've added the accept property in line 797 and restarted node-red, everything works fine again. I wish I had found this issue and your solution a bit earlier. I was getting frustrated, because redeploying, reinitializing, restarting did not help since a few day.

Maybe we should then create a community node together.
Because many are very attentive here and also able to create a development like this.
In my opinion it is always difficult for one person to keep the node up to date (time, implementation, etc.)
Recently, the most common cause of bugs is the cookie thing, because of that I have subscribed the topic "alexa-remote / releases"  by @Apollon77, so I can implement innovations in my system.
At this point I have to say, that @Apollon7 does a first class job. Biggest thanks!

Good, I'll fork it. Maintainers and contributors welcome. Will post the link here shortly.

Hi! Sorry for the late reply. I had forked the project mainly for myself and hadn't used it in the last few weeks.
I think it's great that the community proves itself here once again and that people help each other.
If I can help with the new fork, please let me know.
Otherwise I can also include other developers here. That would save many having to reinstall the node.
I'm happy to report. I am subscribed.

Hi @cakebake. Glad you're back! I absolutely agree that it would be best if we can just keep this fork here alive. Reinstalling is a pain. But eventually, that'd still mean that you're the one who has to do the builds and uploads to npmjs and nodered. Do you have the time and energy for it?

But eventually, that'd still mean that you're the one who has to do the builds and uploads to npmjs and nodered. Do you have the time and energy for it?

Hi @bbindreiter,
That's right ... time is always a problem for me...
It would be incredibly helpful if you would check the functionality and if you can also resolve the merge requests. In terms of quality, it generally makes sense for one or two persons to do the "final acceptance" and publish the release. I can also hand over / share this process after a short time.
I am currently no longer using the node myself. But that can change again. :)
So if I have support on GitHub, I would be very helpful. This concerns issues, upstream keep an eye on, merge requests...

@bbindreiter @cakebake
Jens, if you don't use the node anymore and time is short, hand it directly over to Bernd, he can create a new name for the contrib and is able to publish new releases.
You can still participate if time is available, or helping with the final acceptance.
Changing the contrib in node red isn't that complicated at all.
Just came into my mind. Good idea?

@andesse, but this would imply that all users will have to remove cakebaked
module, reinstall and configure a new one.
On Mon, Jun 7, 2021 at 11:23 AM andesse @.***> wrote:

@bbindreiter https://github.com/bbindreiter @cakebake
https://github.com/cakebake
Jens, if you don't use the node anymore and time is short, hand it
directly over to Bernd, he can create a new name for the contrib and is
able to publish new releases.
You can still participate if time is available, or helping with the final
acceptance.
Changing the contrib in node red isn't that complicated at all.
Just came into my mind. Good idea?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cakebake/node-red-contrib-alexa-remote-cakebaked/issues/22#issuecomment-855765030,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACBCQ3XV4XVOV3K37364KBLTRSFZ3ANCNFSM45ACHLFQ
.

@fmarzocca thats so easy.
Backup all flows, delete everything, delete the contrib, install the new one, import everything. Takes 3 minutes.
But you are right, I get your point, it might be annoying for some users.

Don't forget the little wrinkle where deleting and reimporting a flow loses the authentication unless you fiddle with credential encryption etc.
I'd much rather keep the same fork if at all possible, but also happy to move to another if necessary.
This is the missing software that Amazon should provide.  It turns a pretty useless voice automation system into something really powerful.

Now that users can update cakebaked and find a working environment again there's no need to fork and migrate all users to a new node. I did create a fork here https://github.com/bbindreiter/node-red-contrib-alexa-remote2-applestrudel which I intend to use for myself, as I'm eager to add more functionality, e.g. https://github.com/586837r/node-red-contrib-alexa-remote2/pull/181 . If something breaks I will always try to fix it upstream and support @cakebake, so everyone benefits from it.
Cheers!

hmmm... of course first of all thank you very much for your efforts!
You write "as I'm eager to add more functionality" - and how will the rest of us users get this new functionality?
Wouldn't it make more sense to have several developers like you working together on just one fork? Maybe also with a new name for the common project?
Maybe it would also be possible to work together to fix bugs that have been there for a long time.
For example, Alexa still stops talking after some time (only for some users? Why?). In the meantime, the error can be detected and the module reinitialized; other software that works similarly (FHEM) or even uses the same module from Apollon77 (iobroker) do not have this error.
In its current form, despite the updates, this module is not reliable and actually not usable.
We still hope...
Thanks and regards
Achim

I've been using this node for quite a while and found it very reliable actually. The only problem we all had was that it stopped working a while ago due to the authentication error, which is fixed now.
We all depend from alexa-remote2 and @Apollon77 is responsive. It was a matter of 24 hours to get the fix merged and published. Then it's up to the maintainers. Like previously pointed out, it doesn't help having multiple developers when only the owner is able to publish a new version to the repository. @cakebake stated that he's currently not using the node, therefore I have forked his repository so I can add new functionality and can independently publish to npmjs. The latter is important to me as I'm using this node heavily and rely on it (Doorbell, etc.. ). If there's something to fix I'll be the first to open a PR so users of cakebaked won't be left out.

therefore I have forked his repository so I can add new functionality and can independently publish to npmjs

This also seems to me to be the best solution. Thank you for your good work and help here.
I am very much looking forward to the fact that with the help of your project the textCommand will be available soon. This will allow any dynamic requests to be made to Alexa - this is the biggest step forward in a long time in my eyes.

Text to command is even a problem solver for me. Because I also set the alarm clock via the node, but unfortunately I have not yet succeeded, no matter how I format the input, to set an alarm clock longer than 24 hours and I think that is still a bug in the node.
Since I manually inserted the text to command in my system, I was already able to test it and also solve my problem with the alarm clock.

@Matten-Matten is there a documentation how text-to-command is used?

is there a documentation how text-to-command is used?
to operate? that's easy you can enter what you can ask alexa too.
if you want to add the function in your node you have to do this manually in the files or wait until it appears here as an update.
greeting

@Matten-Matten gotcha! There is a workaround for doing this already. In the alexa app you can define a routine, where the trigger is what you actually would have asked alexa.

I've been using this node for quite a while and found it very reliable actually. The only problem we all had was that it stopped working a while ago due to the authentication error, which is fixed now.
We all depend from alexa-remote2 and @Apollon77 is responsive. It was a matter of 24 hours to get the fix merged and published. Then it's up to the maintainers. Like previously pointed out, it doesn't help having multiple developers when only the owner is able to publish a new version to the repository. @cakebake stated that he's currently not using the node, therefore I have forked his repository so I can add new functionality and can independently publish to npmjs. The latter is important to me as I'm using this node heavily and rely on it (Doorbell, etc.. ). If there's something to fix I'll be the first to open a PR so users of cakebaked won't be left out.

Hi @bbindreiter,
I think you misunderstood me. I wanted to share this project with other developers so that "normal users" don't have to put in a lot of effort to redo their flow. That was very difficult for many of them the last time they made the switch.
If you have now made the decision to continue the project in a different repo, then syncing both projects makes absolutely no sense, as I then no longer see the purpose of keeping this project alive. Or am I seeing something wrong here? Nobody can benefit from it.
I can then rather write a simple guide on how everyone can "simply" create their fork in order to be able to be independent. The basic idea of community is then no longer really given. Although it would certainly be instructive for many to know the code in connection with their Amazon account. No NPM repos or the Node-Red repository are required to install a node. This can also be done "simply" via the package.json of the Node-Red installation via Git.
Your decision. I'll just have a look here again soon and I'm happy to give authorizations to the source code or support another project if there is time and help is needed.

I have updated to the latest version, but still encounter a 'unexpected end of JSON input'
I believe this is because i use an Australian account

The problem came back to me. The fault Authentication Failure: "no body" appears after I restart the NR.
When I log into amazon everything looks OK but after deploy or restart NR the error message appears.
I'm already using the latest version.

@vbenhur after a restart it's always necessary to make a fresh auth. Don't deploy full Flows, is that maybe the problem? If the auth and Init nodes get deployed, they cause the problems.
I changed my deploys to changed nodes, and never had a problem since.
important is also that you run all automations in a routine node. There choose the option "node" and Run all stuff that you need. you can choose serial to run several automations after another.
if you trigger two alexa nodes in a flow simultaneously, the no json error usually appears in one or both.
can these tips solve your issue?
maybe you're right and we have another problem yet, since when did it appear? I played with big automation today, used the routine nodes like described and had zero issues. I can't reproduce.
Greetings

Wenn du den Cookie in einer datei auf dem speicher speicherst und in der Konfiguration von node angibst. Ist nach einem Neustart keine Notwendigkeit das ganze zu Authentifizieren.
EN: If you save the cookie in a file on the memory and specify it in the configuration of node. After a restart there is no need to authenticate the whole thing.
Gruß
matten matten

@Matten-Matten @vbenhur
oh sorry, I meant an initialize after reboot, my bad.
but all main problems disappeared not deploying the nodes anymore.
deploying just changed nodes was a lifechanger.
and important, don't trigger two nodes at the same time.
fun fact: as I use Spotify in my bathroom, when the door closes, I hab it on one Spotify account all the time. so the music everywhere else stopped all the time when in use.
first I contacted Amazon, asked if it's fine to make a second account on my name for the automation reason, they said: you can create as much accounts as you want.
then I contacted Spotify, explained the reason, and upgraded to a family account.
now I have two Amazon account, feedet with different Spotify accounts. I can trigger these two account simultaneously in node red. no issue :)
I have one Spotify connected to the bathroom, one to the Livingroom. bathroom runs completely on its own play my Playlist, thst have really Stange names, so the dot can find it and I can add new songs when I want. the second my Echo-dot, that is normally connected to my main account can be controlled with my ipad when it plays music. all very conviniet.

In addition to Auto-Init with the cookie file I am running the Initialize node every hour because I also had issues in the past.

Guys to me for a few days is not working
is it just my problem or is it not working for you too?

Thanks I didn't know about the new fork
I switched to Applestrude but I still have it
the same problem ie it works to feel
but it doesn't work for me to talk about alexa

I have never used this option
you can post me an example so I try


Application pagination

Merged with master so tests should pass now.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@37a6fd5). Click here to learn what that means.
The diff coverage is 31.7%.

@@            Coverage Diff            @@
##             master      #29   +/-   ##
=========================================
  Coverage          ?   62.27%
=========================================
  Files             ?       37
  Lines             ?      835
  Branches          ?      105
=========================================
  Hits              ?      520
  Misses            ?      306
  Partials          ?        9

Impacted Files
Coverage Δ

src/types.ts
100% <ø> (ø)

src/util/index.ts
100% <100%> (ø)

src/inversify.config.ts
100% <100%> (ø)

src/util/fs/index.ts
100% <100%> (ø)

src/routes/applicationRouter.ts
91.66% <100%> (ø)

src/routes/adminRouter.ts
100% <100%> (ø)

src/services/applications/applicantService.ts
90.9% <100%> (ø)

src/routes/inviteRouter.ts
100% <100%> (ø)

src/routes/dashboardRouter.ts
100% <100%> (ø)

src/controllers/adminController.ts
21.25% <11.42%> (ø)

... and 5 more

Continue to review full report at Codecov.

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


Create OpenShift IaC Landing Zones repo

Type of repository request
Create new repo
Requested name for the repository
openshift-iac-landing-zones
Repository Description
This repository shows a few examples of the declarative configuration, using the OpenShift IaC framework, for clusters such as Virt landing zones, AI workloads, general purpose, etc....
Associated CoP
The CoP this repository is associated with.
Admin Access
@rgoodson-redhat
@selrahal
@pkliczewski
Write Access
@machacekondra
@ddreggors
@bmarlow
@raffaelespazzoli

Review request:
cc: @redhat-cop/container-cop-core

Resolved by #934


Implement emission distribution #284, #233, #252

Inflation and reward pools settings removed from ctrl #233
Emission contract uses new parameters mechanism #252
Emission distributes according to new params (flexible pools) #284, witness rewards distribution added in #235
updated auths required to emit actions
emit no more depends on ctrl
fixed params singletons and related tables naming
updated emission tests

resolves #233, resolves #252, resolves #284

Review comments fixed in 7614eac


Minimum selectable range

As mentioned in #6 RangeSliders should have a minimum selectable range option.

I am using your sliders package for some sliders in my app, but I am having trouble figuring out how to make a small configuration change to the slider. The slider I am using is just the basic horizontal slider. The default slider has a range of 0.0...1.0 but I really need to alter the range slightly to avoid a divide by 0 error. My understanding is that this is easily done but I can quite figure out how.
I have:
HSlider(value: self.$model.currentScale,  configuration: .init( thumbSize: CGSize(width: 8, height: 8))

And my understanding is that I can add a ClosedRange as part of the init(). I tried to make a ClosedRange:
var range: ClosedRange = 0.0...1.0

But can't figure out how to add it. The errors I get are completely unhelpful showing errors after and before that have nothing to do with the problem. Thanks!

@fracturedsoftware
HSlider(
    value: self.$model.currentScale,
    in: .leastNonzeroMagnitude...1.0,
    configuration: .init( thumbSize: CGSize(width: 8, height: 8)
)

This should work. Your currentScale type should be the same as in range's types.
Let me know if it works for you.

Hi Alex,
Thank you for your quick reply. I can see now how it works, but I am still getting problems. I am sure it is really minor but Swift seems to be really strict with everything ( which is good ). Assuming my self.$model.currentScale is a CGFloat, how would I write the range? Alternatively I tried a local @State variable for the currentScale and Double or Float types caused the same errors. Of course at the moment the errors in SwiftUI are really unhelpful..
I usually find if I manage to get a working example I can ‘work backwards’ and solve the problem.
Thanks again for your quick help and kind regards,
Peter

On 22 Mar 2020, at 10:10 am, Alex Young<EMAIL_ADDRESS>wrote:
@fracturedsoftware https://github.com/fracturedsoftware
HSlider(
value: self.$model.currentScale,
in: .leastNonzeroMagnitude...1.0,
configuration: .init( thumbSize: CGSize(width: 8, height: 8)
)
This should work. Your currentScale type should be the same as in range's types.
Let me know if it works for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/spacenation/swiftui-sliders/issues/8#issuecomment-602117356, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIM5O6U4GUMLBHNSTP5TD5DRIVCMXANCNFSM4LGFXUSA.

Sent via Migadu.com, world's easiest email hosting

Hi Again,
Problem solved I think.  Everything is fine.
Thanks again,
Peter

On 22 Mar 2020, at 10:36 am, Peter<EMAIL_ADDRESS>wrote:
Hi Alex,
Thank you for your quick reply. I can see now how it works, but I am still getting problems. I am sure it is really minor but Swift seems to be really strict with everything ( which is good ). Assuming my self.$model.currentScale is a CGFloat, how would I write the range? Alternatively I tried a local @State variable for the currentScale and Double or Float types caused the same errors. Of course at the moment the errors in SwiftUI are really unhelpful..
I usually find if I manage to get a working example I can ‘work backwards’ and solve the problem.
Thanks again for your quick help and kind regards,
Peter

On 22 Mar 2020, at 10:10 am, Alex Young<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
@fracturedsoftware https://github.com/fracturedsoftware
HSlider(
value: self.$model.currentScale,
in: .leastNonzeroMagnitude...1.0,
configuration: .init( thumbSize: CGSize(width: 8, height: 8)
)
This should work. Your currentScale type should be the same as in range's types.
Let me know if it works for you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/spacenation/swiftui-sliders/issues/8#issuecomment-602117356, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIM5O6U4GUMLBHNSTP5TD5DRIVCMXANCNFSM4LGFXUSA.

Sent via Migadu.com, world's easiest email hosting


Data Labels for Stacked bar chart have wrong position and value

How to reproduce
Make a bar chart with a single series and a merge mode of Stacked, and data labels set to a position of Top.
I initially saw this problem with a 2-series Stacked bar chart, but found that the labels were the exact same if I replaced them with a single series of their sum.
Attached below is a code snippet that produces the attached graphs with vico 2.0.0 alpha 12
CodeSnippet.txt
Observed behavior
Labels are displayed overlapping the bars, and showing values that do not match the vertical axis.

Expected behavior
The data labels for a single series should have the same position as a Grouped bar chart.

Vico version(s)
Latest unstable version
Android version(s)
SDK 30
Additional information
No response

Hello! Thanks for the report. We’ll look into it.

Vico 2.0.0 Alpha 13 fixes this. Cheers!

Vico 1.15.0 Alpha 1 addresses this.

Vico 1.15.0 is now available.


Spike: Explore PatternFly usage with Backstage

Goal
Study how PatternFly and existing PatternFly components can be used with Backstage. Find capabilities, limitations and document them.
What problem does this solve? Please describe.
Existing OpenShift console components such as the topology and pipelines views rely heavily on PatternFly. Backstage on the other hand uses Material UI. To evaluate whether we can reuse existing code, we need to determine if it's possible to use PatternFly in a plugin.
Use cases
As a plugin developer, I want to use PatternFly components in a Backstage plugin so that I can reuse existing code from OpenShift console.
Acceptance criteria
Explore answers the following questions:

Can I use @patternfly/react-core components in a Backstage plugin?
Can PatternFly CSS be contributed from a plugin, or does it have to be added to the root Backstage app?
Does PatternFly CSS break the display of Material UI / Backstage components or layout?
Does Material CSS break display of PatternFly components?
Do the styles clash? Can we theme either PatternFly or Backstage to mitigate the different look and feel?
Can I use the @patternfly/react-topology?
Can I use the @patternfly/react-table?
Can I use the @patternfly/react-charts?

Document the findings.
Additional context
Designing for Backstage: https://backstage.io/docs/dls/design
Backstage plugins: https://backstage.io/docs/plugins/
Customizing Backstage look and feel: https://backstage.io/docs/getting-started/app-custom-theme
PatternFly React docs: https://patternfly-react-main.surge.sh/

@spadgett Can you possibly update this one with an Acceptance criteria and  other information?

@gorkem Happy to, although it looks like I don't have permission to edit issues

@spadgett note we have a separate issue for Topology

How PatternFly components look when used in Backstage:

@spadgett does PF component update here based on the dark/light theme? or this is something that needs to be handled/looked into separately

@invincibleJai Let me add it to the list... IIRC this requires manually adding a pf-theme-dark class to the root element for PF to update. Presumably we can key off of the Backstage setting and add the class.

Moving this one as a task under the Topology epic, and closing as this work is complete.

Adding link to Sam's doc here


How do I create a new transaction on my Gnosis Safe wallet programmatically?

Currently I have a React app which connects to a Metamask wallet. On clicking a 'Transfer' button, it transfers some ethers from the connected Metamask wallet to the one input by the user. All of this works fine and is pretty straightforward. It looks something like this (I am using ethers.js):
// fetch signer from connected metamask account
const signer = new ethers.providers.Web3Provider(ethereum).getSigner()
const contract = new ethers.Contract(contractAddress, ERC20ABI, signer)

// create a new transaction - that's it! so simple!
const txResponse = await contract.transfer(_recipientWalletAddress, utils.parseUnits(_userinput).toString())

Now, I want the same functionality but instead of transferring from the connected Metamask wallet, I want to connect to an existing Gnosis Safe and transfer funds from the safe to a recipient. I already have a test Gnosis Safe set up on gnosis-safe.io over Goerli Testnet with 3 owners. I have the Safe address. I have the addresses of the owners.
In my app, I have connected my app to the test Gnosis Safe using WalletConnect.
Now, I want that I click a button, enter a recipient address and submit the form. This should create a new transaction on the test Gnosis Safe. And then on the Gnosis Safe, the owners can approve/reject the created transaction. I am struggling with this part.
This is what I've tried
import Safe from<EMAIL_ADDRESS>import { ethers, utils } from 'ethers'
import EthersAdapter from<EMAIL_ADDRESS>

// have all addresses here
const gnosisSafeAddress = '0xsafexaddress'
const gnosisSafeOwners = ['0xsafexownerx1', '0xsafexownerx2', '0xsafexownerx3']

// create a ethers provider over goerli network
const provider = new ethers.providers.JsonRpcProvider(`https://goerli.infura.io/v3/${infuraAPIKey}`);

// create signer using the provider and private key of the one of the gnosis safe owner
const signer = new ethers.Wallet(PRIVATE_KEY_OF_SAFE_OWNER_1, provider);

// create connection to safe using the gnosis safe address
const ethAdapter = new EthersAdapter({ ethers, signer });
const safeSdk = await Safe.create({ ethAdapter, safeAddress: gnosisSafeAddress });

// create a transaction
const transaction = {
   to: _recipientWalletAddress,
   value: utils.parseUnits(_userinput).toString(),
   data: '0x',
};

const safeTransaction = await safeSdk.createTransaction(transaction);

This does not work at all. Kindly help me understand what I am doing wrong. I am extremely confused reading the Gnosis SDK repos.
I don't want to deploy a test Gnosis Safe programmatically. I don't want to create a Safe app. I just want to create a transaction, programmatically, on Gnosis Safe (a wallet) to transfer funds, like I do for metamask.

Hello @rajat-sr
The code provided looks good, but you are missing to propose the transaction to the service, so the other owners can access it to sign it and execute it.
Please check this guide: https://github.com/safe-global/safe-core-sdk/blob/main/guides/integrating-the-safe-core-sdk.md#5-propose-the-transaction-to-the-service
You completed the first 4 steps, but step 5 is the one you need. There you will need a safeService instance. See how to instantiate it here: https://github.com/safe-global/safe-core-sdk/blob/main/guides/integrating-the-safe-core-sdk.md#initialize-the-safe-service-client
In case you also want to execute it programatically, if the script contains all the required private keys from the signers, follow the guide until the end. Otherwise you can just submit the transaction to the service and let the owners sign it in the UI

Thanks @germartinez :D

I would also recomment updating to the Safe Core SDK v3.0.0.
This requires updating this: https://github.com/safe-global/safe-core-sdk/tree/main/packages/safe-core-sdk#3-create-a-safe-transaction
const safeTransaction = await safeSdk.createTransaction({ safeTransactionData: transaction });


in this doc shared Image Gallery is not updated with new name Azure compute Gallery

[in this doc shared Image Gallery is not updated with new name Azure compute Gallery ]

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

ID: b4c09d03-24b1-f376-34fd-cbfd8d29d3d7
Version Independent ID: 763073bf-734e-e079-2d4c-97c097eb7c88
Content: Share gallery images across tenants in Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/windows/share-images-across-tenants.md
Service: virtual-machines
Sub-service: gallery
GitHub Login: @sandeepraichura
Microsoft Alias: saraic

@akn9050 Thank you for catching this . We will investigate and update the thread.

@akn9050 We have initiated a change request and this will be updated once the authors approve the change.


train error

myubuntu@myubuntu-Precision-WorkStation-T5500:~/Music/pytorch-pil$ sh run_train.sh
Human Pose Estimation with Parsing Induced Learner: [Train and Val Phase]
Loading training json file: dataset/lip/jsons/LIP_SP_TRAIN_annotations.json...
Finished loading training json file
Loading evaluation json file: dataset/lip/jsons/LIP_SP_VAL_annotations.json...
Finished loading evaluation json file
Traceback (most recent call last):
File "main.py", line 394, in
main()
File "main.py", line 166, in main
train(train_loader, hpe_with_pil_net, pose_criterion, parsing_criterion, optimizer, epoch)
File "main.py", line 222, in train
for i, (im, pose_target, parsing_target) in enumerate(train_loader):
File "/home/myubuntu/anaconda3/envs/pytorch-PIL/lib/python3.5/site-packages/torch/utils/data/dataloader.py", line 201, in next
return self._process_next_batch(batch)
File "/home/myubuntu/anaconda3/envs/pytorch-PIL/lib/python3.5/site-packages/torch/utils/data/dataloader.py", line 221, in _process_next_batch
raise batch.exc_type(batch.exc_msg)
TypeError: Traceback (most recent call last):
File "/home/myubuntu/anaconda3/envs/pytorch-PIL/lib/python3.5/site-packages/torch/utils/data/dataloader.py", line 40, in _worker_loop
samples = collate_fn([dataset[i] for i in batch_indices])
File "/home/myubuntu/anaconda3/envs/pytorch-PIL/lib/python3.5/site-packages/torch/utils/data/dataloader.py", line 40, in
samples = collate_fn([dataset[i] for i in batch_indices])
File "/home/myubuntu/Music/pytorch-pil/utils/data_loader.py", line 136, in getitem
pose_target = target_gen.gen_pose_target(flipped_joints, visibility, self.pose_net_stride, grid_x, grid_y, self.sigma)
File "/home/myubuntu/Music/pytorch-pil/utils/target_generation.py", line 48, in gen_pose_target
gaussian_maps = np.zeros((joint_num + 1, grid_y, grid_x))
TypeError: 'float' object cannot be interpreted as an integer
should I ｍodify ｉｔ in the source code？ how to solve this problem?

grid_y and grid_x are float numbers,so you must transform them into integer by int().You can use pdb.set_trace() to verify it.


How to compute the REL+ F1(strict)

Hi Zexuan,
Is there any script for computing the REL+(strict), which mesures the correction of entity type and relation prediction.
In the run_relation.py,  the output f1 seems to be REL F1.
Best,
Deming

Hi Deming,
Yes. Please check run_eval.py.
You can run the evaluation script to output the end-to-end performance (Ent, Rel, and Rel+) of the predictions.
python run_eval.py --prediction_file {path to output_dir}/predictions.json

Best,
Zexuan

Thanks!


Upgrade Debian Bullseye to Bookworm

Bookworm is the new Debian stable release (https://www.debian.org/releases/stable/) and has a much smaller vulnerability footprint (and is smaller!)
Bullseye
Size: 55.06 mb
Vulnerabilities: 25

Bookworm
Size: 49.58 mb
Vulnerabilities: 17

Beam playground build fail: https://storage.googleapis.com/playground-cloudbuild-logs-public/CI_PR29721_2dc825be4b6f57f496aa0a2a1ce7f140ebfb90ca_63a5f4a1-e8fc-4704-b2b2-8f953823bcce.txt
The error was not obvious. Ran locally I reproduced the error:
#19 2.344 is only available from another source
#19 2.344
#19 2.348 E: Package 'openjdk-11-jre-headless' has no installation candidate
#19 ERROR: executor failed running [/bin/sh -c apt-get update && apt-get install -y openjdk-11-jre-headless]: exit code: 100
------
 > [15/18] RUN apt-get update && apt-get install -y openjdk-11-jre-headless:
------
executor failed running [/bin/sh -c apt-get update && apt-get install -y openjdk-11-jre-headless]: exit code: 100

This was due to openjdk-11 removed from debian bookworm: https://www.reddit.com/r/debian/comments/14fjgus/need_help_installing_openjdk11_on_debian_12/

Thanks Yi! I'll keep playground untouched for now, and we can revisit this later.
Perhaps it should use the Temurin images and not rely on apt-getting the JDK, but it's a bit outside of the my scope here (reducing vulnerability footprint)

Perhaps it should use the Temurin images and not rely on apt-getting the JDK

Yeah that could be an approach. Though from my observation Temurin image does not help much for reducing vulneribility

Run Java PreCommit


PERF-#5586: Precompute resulting '.merge' partitioning based on the arguments

Signed-off-by: Dmitry Chigarev<EMAIL_ADDRESS>
What do these changes do?
The PR extends the capabilities of using the keep_partitioning parameter by replacing it with the num_splits parameter, allowing to extra-specify the desired number of splits for the result of a full-axis function.
This allows us to precompute and specify the desired partitioning of the .merge() and .join() results thus avoiding the generation of an excessive amount of partitions caused by split_result_of_axis_func(num_splits=NPartitions.get())   most of which are empty ones.

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #5586
[x] tests added and passing
[x] module layout described at docs/development/architecture.rst is up-to-date

@dchigarev I like that these changes will avoid creating empty partitions. Do you have any numbers showing the impact on performance?

@anmyachev
Here are the ASV results: (I didn't run TimeMerge and TimeMergeCategorical as they both seem to default to pandas):
MODIN_TEST_DATASET_SIZE="Big" asv continuous origin/master HEAD --launch-method=spawn -b TimeMergeDefault
       before           after         ratio
     [a4504a0e]       [b1f99bc7]
     <issue_5590~2^2>       <merge_filter_empties>
-       2.75±0.1s       2.13±0.05s     0.77  benchmarks.TimeMergeDefault.time_merge([[500000, 20], [1000000, 10]], 'inner', False)
-      2.84±0.06s       2.11±0.06s     0.74  benchmarks.TimeMergeDefault.time_merge([[500000, 20], [1000000, 10]], 'inner', True)
-      3.59±0.04s       2.16±0.01s     0.60  benchmarks.TimeMergeDefault.time_merge([[500000, 20], [1000000, 10]], 'left', False)
-      3.74±0.04s       2.10±0.05s     0.56  benchmarks.TimeMergeDefault.time_merge([[500000, 20], [1000000, 10]], 'left', True)

SOME BENCHMARKS HAVE CHANGED SIGNIFICANTLY.
PERFORMANCE INCREASED.

We can see the speed up because we now not wasting time neither on creating Ncores * (Ncores - 1) amount of empty partitions nor then on filtering them out.

@YarShev @anmyachev ready for review

@YarShev I've reworked approach according with your suggestion

@anmyachev, do you have any other comments regarding the changes?


Bump cluster-standup-teardown to v1.27.3 to update CAPV cluster values for the new vSphere provider

What this PR does
towards https://github.com/giantswarm/giantswarm/issues/32054
Checklist

[x] Update changelog in CHANGELOG.md.

Trigger e2e tests

/run cluster-test-suites

let's re-run the fun
/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

last try for tonight
/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

/run cluster-test-suites TARGET_SUITES=./providers/capv/standard

the e2e tests will fail because we need a new Release to fix issues with kube-vip. I'm going to merge this PR as the changes have been tested locally.


Update command.md

Seems there is a small mistake in the import statement of the usage example of the command component.
It imports from collapsible instead of command.

Whoops, thanks for this!


feat: expose hooks

Todo: add some examples
(currently untested)

We could also add a hook for changing tabs, similar to useNavigation from react-navigation. This would make it easier to navigate to other tabs from within tabs.


ELIFECYCLE  Command failed with exit code 2.

server                                   |  WARN  The field "pnpm" was found in /www/wwwroot/msgbyte/tailchat/server/package.json. This will not take effect. You
should configure "pnpm" at the root of the workspace instead.
Scope: all 76 workspace projects
Lockfile is up to date, resolution step is skipped
Already up to date
 WARN  Failed to create bin at /www/wwwroot/msgbyte/tailchat/server/plugins/com.msgbyte.getui/node_modules/.bin/tailchat-runner. ENOENT: no such file or director
y, open '/www/wwwroot/msgbyte/tailchat/server/packages/sdk/dist/runner/cli.js'
 WARN  Failed to create bin at /www/wwwroot/msgbyte/tailchat/server/plugins/com.msgbyte.prettyinvite/node_modules/.bin/tailchat-runner. ENOENT: no such file or d
irectory, open '/www/wwwroot/msgbyte/tailchat/server/packages/sdk/dist/runner/cli.js'
 WARN  Failed to create bin at /www/wwwroot/msgbyte/tailchat/server/node_modules/.bin/tailchat-service-openapi-generator. ENOENT: no such file or directory, open
'/www/wwwroot/msgbyte/tailchat/server/packages/openapi-generator/dist/index.js'
 WARN  Failed to create bin at /www/wwwroot/msgbyte/tailchat/server/node_modules/.bin/tailchat-service-swagger-generator. ENOENT: no such file or directory, open
'/www/wwwroot/msgbyte/tailchat/server/packages/swagger-jsdoc-generator/dist/index.js'
 WARN  12 other warnings
client/packages/tailchat-client-sdk prepare$ tsc
│ src/openapi/client/ws.ts(4,34): error TS2307: Cannot find module 'tailchat-types' or its corresponding type declarations.
└─ Failed in 3.4s at /www/wwwroot/msgbyte/tailchat/client/packages/tailchat-client-sdk
apps/github-app prepare$ tsc
└─ Running...
.../plugin-declaration-generator prepare$ tsc
└─ Running...
packages/types prepare$ pnpm build
│ ><EMAIL_ADDRESS>build /www/wwwroot/msgbyte/tailchat/packages/types
│ > concurrently npm:build-cjs npm:build-esm
│ [build-cjs]
│ [build-cjs] ><EMAIL_ADDRESS>build-cjs
│ [build-cjs] > rimraf ./dist/cjs && tsc --outDir dist/cjs
│ [build-cjs]
└─ Running...
server/packages/swagger-jsdoc-generator prepare$ tsc
└─ Running...
 ELIFECYCLE  Command failed with exit code 2.

did you use pnpm@8?

Cannot find module 'tailchat-types' or its

I was using pnpm@9 and confirm using pnpm@8 solved the problem

ok cool


Content usage wrapper

It would be nice to have a wrapper that lets me get content usage regardless of the content is Shiny or not. Currently we have /v1/instrumentation/shiny/usage for shiny usage and /v1/instrumentation/content/visits for everything else. They contain much of the same information (though there isn't complete overlap!), but it looks like enough that we could return a combined list that has the fields when they are relevant and either doesn't have them or they are marked as NULL when they are not relevant.
See: https://github.com/rstudio/connectapi/issues/218

I believe this will involve https://github.com/posit-dev/posit-sdk-py/issues/75.


Support multiple deployments per module

Currently a module can be deployed to completion once. It can be rerun if only partially executed or errored; but while display the results of the previous run if rerun on a successful deploy.
To support using a module multiple time we could introduce the concept of a deployment id. So a module could have multiple deployments, each with a unique module id.
This raises design questions about composing sections of the module that refer to singleton instances of contracts on a deploy relative to contracts which are redeployed as new instances each run.

I think we can have a "global" deployment id, so that we scope everything by it. That is, the journal files, deployment artifacts, or whatever we want to store.
We should default de deployment id to something like "network-${chainId}".

This is something we want to support. Right now there is one journal file per module. We want to switch it to a folder structure that supports different deployment ids and chains and whatever other feature the journal needs scoped by.
The next step is to confirm the list of features to scope by (currently chainId and deploymentId) and design a folder layout that will support them.


Forward /api requests to PyBossa backend

This is actually a bit too much of a hassle for something that won't be used much, closing

Reopening as I found a way to do this with nuxt, coming up in v1.0.0-beta.3


feat: sociable unit test functionality

@soryy708 up to review?

Relates to: https://github.com/automock/automock/issues/230


Find a table based on the position of a paragraph

I have a document with the following format:
Unknown content
Paragraph with unique name
Table
Unknown content
Paragraph with unique name
Table
Unknown content
I know the unique names and would like to get the tables following them. Something like a method: def GetTableFromName(paragraphName: str) -> Table:
Is this possible with python-docx?
I know I can iterate through document.paragraphs to find the paragraphs but I have no idea how to guess a position in document.tables based on this information.

have a Google on python-docx iter_block_items and you'll see some prior art on accessing document "block" items (paragraphs and tables) in document order. This should give you the ability to detect the right tables.

Looks like it will do the trick. Thank you!

I used the method you gave here and it worked fine.

Glad to hear it @FredEPr :)


Update README.md to add Contributors

Issue Description
I would like to update the README.md to include the list of Contributors to this project. I'm in GSSoC '23
Topic or Category
Updating README file
Benefits of Adding this Resource
A major benefit of adding this resource would be to encourage people to contribute to this project as well as display the profiles of those who have already contributed.

Yes you can add

The list is not updated as new contributors are added, can you make it such that it automatically adds new contributors?
Your name is also not showing.


cannot download package

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
pyproject.toml file
[project]
name = "project"
version = "0.1.0"
description = "test"
authors = []
requires-python = ">=3.9"

[tool.pixi.pypi-dependencies]
pytoda = { git =<EMAIL_ADDRESS>
[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"

[tool.setuptools]
py-modules = ["bmfm_inference_service"]

Issue description
error:
pixi install
  ⠙ default:linux-64     [00:00:00] resolving guacamol==0.5.5                                                                                × failed to solve the pypi requirements of 'default' 'linux-64'
  ├─▶ failed to resolve pypi dependencies
  ├─▶ Failed to download and build `pytoda<EMAIL_ADDRESS>  ├─▶ Git operation failed
  ├─▶ failed to fetch into: /home/dev/.cache/rattler/cache/uv-cache/git-v0/db/d06a38293fe867f4
  ╰─▶ process didn't exit successfully: `git fetch --force --update-head-ok<EMAIL_ADDRESS>'+HEAD:refs/remotes/origin/HEAD'` (exit status: 128)
      --- stderr
      remote: Not Found
      fatal: repository<EMAIL_ADDRESS>not found

I used to be able to install this, but now i cant plus a few other packages. i can install the package without the tags at the end but i need them.
Expected behavior
pytoda installed

downgrading pixi to pixi 0.24.2 from 0.26.1 fixes my issue....

Hi @brian316, thats very unfortuanate.
I assume this has to do with the update to the latest uv in pixi which might have altered this behavior.
As a workaround you could use the tag = "0.2.5" in the toml file which did work for me:
[project]
name = "project"
version = "0.1.0"
description = "test"
authors = []
requires-python = ">=3.9"

[tool.pixi.project]
channels = ["conda-forge"]
platforms = ["linux-64"]

[tool.pixi.pypi-dependencies]
pytoda = { git = "https://github.com/PaccMann/paccmann_datasets", tag = "0.2.5" }

[build-system]
requires = ["setuptools"]
build-backend = "setuptools.build_meta"

[tool.setuptools]
py-modules = ["bmfm_inference_service"]

We need to decide if we want to support the pip like url style for a git dependency.

We're not supporting it right now, feel free to reopen when needed.


MTCH missing data after Jun 30

https://robintrack.net/symbol/MTCH
The stock is still actively traded as of today.

This is due to MTCH having a split on July 1st; this causes Robinhood to produce a new internal ID for the stock, and the data becomes disassociated in my database.
This would be solved by #72, which is a high priority issue for me.  Note that Robintrack is recording this data and I'll be able to correct the problem and join it with the pre-split data, I just have to create an automated solution to do that.


Update travelperk-tutorial.md

Updating the correct steps now that the platform is self-serve

@marko-travelperk : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@jeevansd
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"

@marko-travelperk @Court72 We have reviewed and made suggested changes in another PR from our private repo. So closing this PR for now. #please-close


how to compile?

Hi Rajeshwar,
thanks for your great Ionic module! :)
I did some modifications to the raw code (in the src folder), but now I don't know how to compile it into the minified version and include the HTML templates like you did. Could you elaborate please?
What I mean: how do I get from the contents of the src folder to the content of the dist folder?
Thanks a bunch in advance,
Florian

Just run gulp build command. It will do serve the purpose.


Specify the specific API and resource for owners

Describe the feature
This should change:
...
spec:
  owners:
    - name<EMAIL_ADDRESS>      kind: Group

A kind is not sufficient to definitively identify which API group we mean here. Instead, we should specify owners more like:
...
spec:
  owners:
    - name<EMAIL_ADDRESS>      apiGroup:  rbac.authorization.k8s.io
      apiResources: groups # yes, the lowercase plural form that you see at the HTTP layer
    - name<EMAIL_ADDRESS>      apiGroup:  some.other.example
      apiResources: externalserviceaccounts # for this example, it could be an aggregated API
    - name<EMAIL_ADDRESS>      apiGroup:  avatars.some.other.example
      apiResources: users # ambiguous name, disambiguated by API group

We also shouldn't assume that Kubernetes RBAC is the only game in town. You can have a conformant Kubernetes cluster that uses a different access control mechanism and runs with RBAC disabled.
Expected behavior
There's never ambiguity about how we refer to owners.

@sftim Thank you for your proposition.
Actually, the owners spec is a list of Subject []v1.Subject that contains already the APIGroup and Kind.
// Subject contains a reference to the object or user identities a role binding applies to.  This can either hold a direct API object reference,
// or a value for non-objects such as user and group names.
// +structType=atomic
type Subject struct {
	// Kind of object being referenced. Values defined by this API group are "User", "Group", and "ServiceAccount".
	// If the Authorizer does not recognized the kind value, the Authorizer should report an error.
	Kind string `json:"kind" protobuf:"bytes,1,opt,name=kind"`
	// APIGroup holds the API group of the referenced subject.
	// Defaults to "" for ServiceAccount subjects.
	// Defaults to "rbac.authorization.k8s.io" for User and Group subjects.
	// +optional
	APIGroup string `json:"apiGroup,omitempty" protobuf:"bytes,2,opt.name=apiGroup"`
	// Name of the object being referenced.
	Name string `json:"name" protobuf:"bytes,3,opt,name=name"`
	// Namespace of the referenced object.  If the object kind is non-namespace, such as "User" or "Group", and this value is not empty
	// the Authorizer should report an error.
	// +optional
	Namespace string `json:"namespace,omitempty" protobuf:"bytes,4,opt,name=namespace"`
}

You can as well refer to the api reference.

Although, I think that we need to update the documentation and samples to add explicitly the APIGroup.

https://nauticus.edixos.com/0.1.0/crds-apis/#spacespecownersindex doesn't mention an API group.
I don't recommend allowing even optional references to a kind, as these can be ambiguous with CRDs. They shouldn't be but they can.

// APIGroup holds the API group of the referenced subject.
// Defaults to "" for ServiceAccount subjects.
// Defaults to "rbac.authorization.k8s.io" for User and Group subjects.
// +optional
APIGroup string json:"apiGroup,omitempty" protobuf:"bytes,2,opt.name=apiGroup"

That defaulting is hard-coding implementation details of Kubernetes RBAC. Watch out for compatibility issues with Kubernetes clusters that use an alternative mechanism (RBAC is not part of certified Kubernetes, and some clusters use different mechanisms).
Defaulting via a MutatingAdmissionWebhook works better if it's essential, because then someone can omit deploying the webhook or replace it with their own.

Yeah I agree, this can be managed by a MutatingWebhook if you omit it.
@sftim Do you have examples of Kubernetes distributions that does not use RBAC by default ?

Distributions? No. Although OpenShift has its own User and Group APIs that aren't the ones from RBAC.


Highlight notifications of issues/PRs were you were mentioned

Currently the notifications view shows notifications for every issue/PR that you are subscribed to, with no visual feedback about mentions to you.  There is a "Participating" tab, but that's a click away and easy to miss.
It would be really nice to have a visual indicator of the importance of the notification.  In my mind they would have this order of importance:

Issues/PRs that I opened.
Issues/PRs where I was mentioned in the conversation or marked as a reviewer.
Issues/PRs that I explicitly subscribed to.
Issues/PRs that I implicitly subscribed to (i.e. because I subscribe to the organization or the project).

Not really sure if all this is doable with github's API, though.
Just to give an example, it would convey the information as I show here (but probably with a nicer design):

It's possible but I don't think it's useful to show such info for all notifications.

Those 4 level I mention are just an idea.  What I think is useful is to have some sort of visual indication of how important the notification is.
And if that can be configurable that would be even better (for instance the ability to configure a color for each type of notification reasons).

There is an online tool available that filters the notifications in different reasons:

comment
author
state change
assign
subscribed
team mention
security alert

Octobox

I wish GitHub auto-sorted notifications based on importance. "Importance" being calculated based on what I usually prioritize and other hints, using machine learning. One can dream though.

The available information is incomplete and not particularly useful. Each notification could hide multiple comments and actions, but GitHub will only choose one of them. We can’t trust that it will choose the one you’re looking for so we shouldn’t show this info.

It's coming from GitHub: https://github.blog/2019-11-13-universe-day-one/#notifications

Necro!
I feel like the current situation is inadequate, as this is filtering (without not statements¹), not highlighting.
¹ With not statements you could have a few tabs/buttons/bookmarks for gh notifications. For example, 1 for mentions, 1 for repos you own, 1 for everything else. The 'everything else' is the notable part here, no not statements.


Rasa Core via docker

Hi, I'm pretty new to all of this so this might be a dumb question...
I think I got rasa-ui to work with rasa-nlu via the docker container.
Is there a reason that there isn't a public docker file for rasa core?
Every example I see needs you to build it yourself and pass in a path to some models. Is this a spacy model?
If anyone has an example docker compose file that handles all this setup, that would help a lot.
Thanks!

Doh.. I didn't see the official docker file for rasa core

@jlkalberer

Every example I see needs you to build it yourself and pass in a path to some models. Is this a spacy model?

RasaCore is a stateful container. So it needs training data and model to be created before starting server. Rasa UI has some instruction on how to start the rasa core as a python process in Training page.


SAMZA-2462 : Adding metric for container thread pool size

Adding metric for container thread pool size.
Symptom: Currently it is not possible to track the container-thread-pool size using metrics, even though its possible to configure it similar to container-memory-mb, vcore, etc.
Cause: No metric for this configurable
Fix: Added metric for container thread pool size, updated metrics reference sheet.

Please include API changes etc. sections for the PR description. This way it's easy to collect them in the changelog during a release.


Bidirectional RPC

Hey!
Please, is it possible to both serve a service and consume a service on the other side, on the same TCP transport? I mean, both the client (initiator of the connection) and the server consuming a service on a full-duplex TCP connection?
Thanks!

Hi, thanks for the question! Yes, this is possible. There was a similar question, with some example code, on https://github.com/google/tarpc/issues/300.

Awesome, thank you @tikue!

You're welcome :) closing this now, but feel free to reopen later if you want!


Brazilian Portuguese translation of Claim Your Front End Development Certificate

[ ] Claim Your Front End Development Certificate

work on it!

finish

Closed in favor of https://github.com/FreeCodeCamp/TranslationExpansion/issues/45, @Janainaf @yesroh please continue discussion there, on that note is this already complete?


Modify our-projects selection

Update selection of projects:

Remove Skywallet :disappointed_relieved:
Add Iperia, Accorlocal, Sirac

Hrm, we should also probably add Save.co... We crafted their MVP/prototype during (before?) their first skyrocket-growth rally :thinking:


[BUG] Dependencies with ignored scopes don't appear in the pom-debloated.xml

Describe the bug
The ignoreScope parameter in DepClean is used to filter out from the analysis dependencies with some specific scopes (e.g., test or provide). Thus, dependencies with ignored scopes should be always considered as used and remain untouched by DepClean. However, this parameter is not working for the pom-debloated.xml because dependencies with ignored scopes are not there.
To Reproduce

Get a project with an unused dependency X with scope test.
Run DepClean with ignoreScopes=test and createPomDebloated=true
Look at the generated pom-debloated.xml, the dependency X should be in the debloated-pom.xml, but it isn't.

Expected behavior
Dependencies with ignored scopes should be always considered as used.

Fixed with #153


Error messages

The default error messages aren't good..we can modify it further with css modules

hii @ppfeiler can u assign me this

@kmahesh18 i want to work on this


Add security policy

Uh oh, looks like the tests failed due to wrong.host.badssl.com failing for the wrong reason (expired cert?)

Yeah, checked the certificate and it expired yesterday, unfortunate! I'm okay to merge this one regardless if you are.


Reports I would like (and changes)

Let me know if you want me to make separate issues for each
Add camper type to "all campers" report and remove chore and lodging
Add camper type to "registration payments" report
Add camp (ie 1,2,3) and attendance (full or 1/2) to "lodging" report and sort by camp and lodging type
Add lodging report by sorted by alpha (last name) with same attributes as above
Add registration date to "registration payments" report (not really needed at this point)
Add lodging report sorted by entry date (ie. Thursday entry, Friday Entry, 1/2 camp-Tuesday entry) include name, type, camp, lodging

All Campers Report
Proposed Template
TEST All Campers Update
Report Here

Changes

[x] Add camper type (this was already added)
[x] Remove chore (this was already removed)
[x] Remove lodging

@willfulbard, would you mind signing off of this?

Registration Payments Report
Proposed Template
Report Here
Changes

[x] Add camper type

Please let me know if you would like the Type column to the right of the $ columns!
@willfulbard

Yes please...put the Type column to the right of the $ columns.
Thank you!!!

Camper Lodging by Alpha Report
Proposed Template
TEST Camper Lodging by Alpha
Report Here
Changes

[ ] Add camp
[ ] Add attendance (full or half camp)
[ ] Sort by alpha last name

This report is waiting on a camp lookup helper that will return a campers camp, lodging type, and site number.

Camper Lodging by Lodging Report
Proposed Template
TEST Camper Lodging by Lodging
Report Here
Changes

[ ] Add camp, lodging type, lodging site
[ ] Sort by lodging

Like the other camper lodging report, this one is waiting on a camp lookup helper that will return a campers camp, lodging type, and site number.

Camper Lodging by Entry Date
Proposed Template
TEST Camper Lodging by Entry Date
Report Here
Changes

[ ]  Add camp, lodging type, lodging site
[ ] Add entry date
[ ] Sort by entry date

Like the other camper lodging reports, this one is waiting on a camp lookup helper that will return a campers camp, lodging type, and site number.


New re-frame set up / Clean slate

not wiping history until past implementations are ported over into new setup

@oconn @dehli

What would be the reasoning for ever wiping the history?

it's outdated and once the logic is ported over it's not of much use. just clutter


not working with ng serve --aot

What I did was

clone https://github.com/ngrx/example-app
did a npm install
did a ng serve
navigate to http://localhost:4200/#/book/find and did a quick search

Everything is working from step 1 - 4. :+1:
Then i proceed to stop the service and did a ng serve --aot
everything builds successfully but when i navigate to http://localhost:4200/#/book/find to do another  search , it just keep spininng.
What i found out is that its not hitting the effects when run on AOT mode.
So am i actually doing it correctly if i were to try the AOT mode?
Thanks!
C:\temp\example-app>ng --version
angular-cli: 1.0.0-beta.17
node: 6.9.1
os: win32 x64

C:\temp\example-app>node --version
v6.9.1

This is a known issue with the CLI. See https://github.com/angular/angular-cli/issues/2799


Install fails

On npm -g install auto-changelog I get this. I also tried clone and install from folder. Same.
npm ERR! code ENOENT
npm ERR! syscall chmod
npm ERR! path /home/roland/.local/var/lib/npm/lib/node_modules/auto-changelog/lib/index.js
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, chmod '/home/roland/.local/var/lib/npm/lib/node_modules/auto-changelog/lib/index.js'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

Any hints appreciated.

Sounds like something wrong with NPM on your machine.. /lib/index.js does indeed exist in the package<EMAIL_ADDRESS>Do other globally installed modules work? Are they in /home/roland/.local/var/lib/npm/lib/node_modules/ too?

You need sudo to install things globally in most cases; it seems like a permissions error.

npm install auto-changelog would install under the current folder.
npm -g install auto-changelog, for me, installs to my home directory.
I have set things up like that via the ~/.local/etc/npm/npmrc.
When I do npm config edit that file is opened.
All my local installation, also from other languages, go to ~/.local.

Here "local" means within my home directory.
Nodejs "local" means in the current folder.

I have write permission to ~/.local,
therefore I do not expect permission errors with npm -g install.
So far I did not have any permission errors with other npm packages.
Today npm install auto-changelog worked without sudo.
Could it have been a timing issue?
I noticed that my $PATH did not contain /home/roland/.local/var/lib/npm/bin.
That is no good, but even so npm install auto-changelog worked without sudo.
sudo npm install  is a bad idea.

It's very atypical to override where global modules are stored that way; generally folks use nvm if they want global modules inside their home dir instead of overriding the prefix.
The local install should always work without sudo; the global one will often require it.


Use interruptGuard in VThreadScheduler

A simple solution to this double scheduling. Allocate AtomicBoolean vs a new virtual thread.
Happy New Year! 🎉

@m8nmueller @He-Pin I implemented the VarHandle approach, please have a look.


[FEATURE] Add default security values

I'm adding a Security schema to OpenAPI, but it seems there's no way to add defaults, everything is lost on reload.
    let open_api = OpenApi::new("test api", "0.0.1")
        .merge_router(&router)
        .add_security_scheme(
            "device-id",
            SecurityScheme::ApiKey(ApiKey::Header(ApiKeyValue::with_description(
                "device-id",
                &"test".to_string(),
            ))),
        )
        .add_security_scheme(
            "authorization",
            SecurityScheme::ApiKey(ApiKey::Header(ApiKeyValue::new("authorization"))),
        );

Would be nice to add defaults.

Also, for some reason the authentication isn't working, the headers never get sent.
        let _ = match headers.get("device-id") {
            Some(device_id) => device_id,
            None => {
                eprintln!("device-id header is required, headers are: {:?}", headers);
                // Throw API error
                let api_error = ApiError {
                    message: "device-id header is required".to_string(),
                    status: "no-device-id".to_string(),
                };
                res.render(api_error);
                return;
            }
        };

Please give a minimum reproducible example.

@chrislearn it's the basic OpenAPI example with these add_security_scheme added. The headers are ignored from the Swagger docs

I ask your example because you said "for some reason the authentication isn't working, the headers never get sent.", I'm not very clear about the specific situation on your end. I can't understand what's going on just by posting a piece of code.

@chrislearn here you go, is this ok, or do you want a Github?
#[handler]
async fn hello(req: &mut Request) {
    // There's no device id
    let _ = match headers.get("device-id") {
        Some(device_id) => device_id,
        None => {
            eprintln!("device-id header is required, headers are: {:?}", headers);
        }
    };
    Ok("---")
}

#[tokio::main]
async fn main() {
    tracing_subscriber::fmt().init();

    let api_subrouter = Router::with_path("api")
        .get(hello);

    let router = Router::new()
        .hoop(logger::logger_middleware)
        .push(api_subrouter);

    // Get the cargo version
    let version = env!("CARGO_PKG_VERSION");

    // OpenAPI with secruity headers
    let open_api = OpenApi::new("test api", version)
        .merge_router(&router)
        .add_security_scheme(
            "device-id",
            SecurityScheme::ApiKey(ApiKey::Header(ApiKeyValue::with_description(
                "device-id",
                &"The device id, from the device".to_string(),
            ))),
        )
        .add_security_scheme(
            "authorization",
            SecurityScheme::ApiKey(ApiKey::Header(ApiKeyValue::with_description(
                "authorization",
                &"The JWT token, optional".to_string(),
            ))),
        );

    let router = router
        .push(open_api.into_router("/api-doc/openapi.json"))
        .push(SwaggerUi::new("/api-doc/openapi.json").into_router("ui"));

    let acceptor = TcpListener::new("<IP_ADDRESS>:5800").bind().await;
    Server::new(acceptor).serve(router).await;
}

You need to add security setting to endpoint:
#[endpoint(security(("device-id" = [], "authorization" = [])))]
async fn hello(req: &mut Request) {
    // There's no device id
    let id = req.header::<String>("device-id");
    println!("device-id: {:?}", id);
}

If you want your authorization data persisted, you can use persist_authorization

@chrislearn I have to add this to every endpoint, what if we have 700 that are all under the same authorization schema? This should be a route setting?

After branch oapi-router merged.
You can use router.oapi_security or router.oapi_securitys to set securities.
All endpoints in the router and it's descents will inherit these security requirements.

@chrislearn I mean how are we supposed to read this?
This line for example
 pub fn new<N: Into<String>, S: IntoIterator<Item = I>, I: Into<String>>(name: N, scopes: S) -> Self {
It's really difficult to read, part of mpl SecurityRequirement
We used to do this? How would do the same?
    let open_api = OpenApi::new(app_name, version)
        .merge_router(&router)
        .add_server(salvo::oapi::Server::new(env_vars().api_url.to_string()).description("API Url"))
        .add_security_scheme(
            "device-id",
            SecurityScheme::ApiKey(ApiKey::Header(ApiKeyValue::with_description(
                "device-id",
                &"The device id, from the device".to_string(),
            ))),
        )
        .add_security_scheme(
            "authorization",
            SecurityScheme::ApiKey(ApiKey::Header(ApiKeyValue::with_description(
                "authorization",
                &"The JWT token, optional".to_string(),
            ))),
        );

@chrislearn For example, it says the field is private here
    let mut security_req = SecurityRequirement {
        value: BTreeMap::new(),
    };
    security_req
        .value
        .insert("authorization".to_string(), Vec::new());

    // The API routes
    let mut api_subrouter = Router::with_path("api")
        .hoop(auth_middleware)
        .push(auth_routes())
        .push(file_routes())
        .push(notification_routes())
        .push(admin_routes())
        .oapi_securities(security);

SecurityRequirement

Use it's add function.
https://docs.rs/salvo-oapi/latest/salvo_oapi/struct.SecurityRequirement.html#method.add


Wrong flag on "Add a member to an organization using the influx CLI"

The example in step 2 reads:
influx org members add -n <org-name> -o <user-ID>
but that gives the error:
"Error: unknown shorthand flag: 'o' in -o"
The example should read
influx org members add -n <org-name> -m <user-ID>
according to influx org members add -h
Relevant URLs
https://v2.docs.influxdata.com/v2.0/organizations/members/add-member/

Thanks for this, @andersekbom!


Animating Area's collision shape causes non detection for signal

Godot version:
3.2 beta 4
OS/device including version:
ubuntu 18.04
Issue description:
The title describes the bug
Steps to reproduce:
create an spatial node, insert area + collision shape as sphere, create a animationplayer
animate the sphere radius to expand from 0.1 to 3 in about 0.3secs setup the signal to detect some rigidbody and voila! doesnt work :(
Minimal reproduction project:
https://github.com/nonunknown/crashcreator/tree/alpha -> check for resources/explosion.res
**There's a workaround? **
yes there is, just setup the sphere radius to the size you want and then disable it after some time, i.e:
_ready():
    yield(get_tree().create_timer(1,false),"timeout")
    queue_free()

Might be duplicate of #33369

Duplicate of #33369.


Postman POST Creation

When using Postman to send POST requests, be sure to use the same port number as when you began running the web app.

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

ID: 583ae3e7-5915-f22b-e54c-6c100cf2a7da
Version Independent ID: 95f2549e-29f9-e31a-b4d0-432b971643ff
Content: Tutorial: Create a web API with ASP.NET Core
Content Source: aspnetcore/tutorials/first-web-api.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Hopefully that's obvious.


[DO NOT MERGE] Deprecate nested routes with absolute paths

From @ryanflorence on https://github.com/reactjs/react-router/pull/3246#issuecomment-210139897:

Added the 3.0 milestone. We don't want to release this until we have features/improvements that depend on it, otherwise it's just annoying to our users. If we get those going we can move this to an earlier release.

@taion, mind enumerating the feature(s) that depend on this?

So I think at the end of it all, it looks like nothing strictly depends on this. It just makes a lot of things simpler, like relative link support, and lets us further optimize checking whether links are active.
So there's nothing strictly requiring this any more, but we should still do it sooner or later.

From @ryanflorence on https://github.com/reactjs/react-router/pull/3246#issuecomment-210139897:

Added the 3.0 milestone. We don't want to release this until we have features/improvements that depend on it, otherwise it's just annoying to our users. If we get those going we can move this to an earlier release.

@taion, mind enumerating the feature(s) that depend on this?

So I think at the end of it all, it looks like nothing strictly depends on this. It just makes a lot of things simpler, like relative link support, and lets us further optimize checking whether links are active.
So there's nothing strictly requiring this any more, but we should still do it sooner or later.

This is useful for making:

our matching algorithm simpler
route configs clearer to humans
simpler for integrations that need to work with paths (like named routes, relative routes, whatever else)

All previous UI + url combinations are still possible but with some extra route config--that's really the only trade-off (and JSF*).
<Route path="inbox" component={Inbox}>
  <IndexRoute component={Dashboard}/>
  <Route path="/message/:id" component={Message}/>
</Route>

// becomes

<Route path="inbox" component={Inbox}>
  <IndexRoute component={Dashboard}/>
</Route>
<Route component={Inbox}>
  <Route path="/message/:id" component={Message}/>
</Route>

Worth it?
(*) JavaScript Fatigue

route configs clearer to humans

I find the opposite true.
In this example, I have to manually concat 3 strings in my head to understand what the URL looks like
<Route path="/" component={App}>
  <Route path="about" component={About} />
  <Route path="inbox" component={Inbox}>
    <Route path="messages/:id" component={Message} />
  </Route>
</Route>

Whereas if you use absolute paths exclusively (we do) it's way clearer, especially in a sufficiently large route config.
<Route path="/" component={App}>
  <Route path="/about" component={About} />
  <Route path="/inbox" component={Inbox}>
    <Route path="/inbox/messages/:id" component={Message} />
  </Route>
</Route>

Mixing absolute & relative feels weird, but I'd miss being able to go exclusively absolute.

You can put a comment in there:
<Route path="/" component={App}>
  <Route path="about" component={About} />
  <Route path="inbox" component={Inbox}>
    <Route {/* path=/inbox/messages/:id */} path="messages/:id" component={Message} />
  </Route>
</Route>

That being said, it would be cool if there was some utility similar to rake routes in Rails to list out the full route tree.

@bensmithett I had thought about that use case a bit, and I'm not totally sure what to do there. The case we're worried about is less what you're doing, and more something like:
<Route path="/inbox" component={Inbox}>
  <Route path="/not-inbox" component={SomethingElse} />
</Route>

IMO this is quite confusing.

@taion is that necessarily a bad thing? I didn't think component nesting necessarily needed to dictate URL structure (via docs)
<Route path="/inbox" component={Inbox}>
  <Route path="/inbox/settings" component={InboxSettings} />
  <Route path="/message/:id" component={Message} />
</Route>

@timdorr yeeeah, but self-documenting code > comments!
(feel free to point me at other discussions, totally jumping in from the sidelines here 😄)

@bensmithett See #3172 for reference. I think the contributing team is all sold on this, so it's going to happen. Personally, I even think it's dangerous to support nested absolute routes, as it's more likely to lead to error-prone behavior, pain, and sadness for all involved.

I'm not against them, I <3 that the urls and component nesting are not coupled. I've seen quite a few people who prefer to do absolute routes everywhere ... wonder what it would look like if we allowed absolute urls as long as they matched their parent perfectly.

Though I'd be slightly :sadface: (it's a feature I like & get value from, haven't experienced any pain) if this PR shipped I'd survive. Trade-offs gonna trade-off 😄.
Is there a good story around iterating on a layout without needing to change URLs?
// Designer: I want the sidebar visible on the change password screen
// URL: /inbox/change-password

<Route path="/" component={App}>
  <Route path="inbox" component={Inbox}>
    <Route path="change-password" component={ChangePassword} />
    <Route path="message/:id" component={Message} />
  </Route>
</Route>

// Designer: No wait, it should appear without the sidebar
// URL: /change-password

<Route path="/" component={App}>
  <Route path="inbox" component={Inbox}>
    <Route path="message/:id" component={Message} />
  </Route>
  <Route path="change-password" component={ChangePassword} />
</Route>

// Designer: No wait, bring the sidebar back, but our product is growing
// so we need new additional settings screens & let's split them over tabs
// URL: /inbox/settings/change-password

<Route path="/" component={App}>
  <Route path="inbox" component={Inbox}>
    <Route path="settings" component={SettingsTabLayout}>
      <Route path="change-password" component={ChangePassword} />
      <Route path="avatar" component={Avatar} />
      <Route path="billing" component={Billing} />
    </Route>
    <Route path="message/:id" component={Message} />
  </Route>
</Route>

Maybe <Redirect> could handle this, but could get a bit gnarly on a larger app with a year's worth of design iterations.
(Also ❤ 🎁 🍺  core team for all your work!)

@bensmithett mind cut/pasting that question into a new issue since it's not related, I can answer it over there.

@ryanflorence done #3320

This PR is pending an update to not drop support for https://github.com/reactjs/react-router/pull/3319#issuecomment-210257142.
There's one other benefit to dropping nested absolute &c. support – it's that we can make <Link> (isActive) faster.
In other words, if we take out this feature, and we want to see if whether /foo is active, we can immediately say no whenever the current pathname doesn't start with /foo/ (and is not /foo). In cases where there are lots of links, likely most of them will fail the isActive check immediately on this prefix thing, which should speed things up quite a bit.

So sounds like here's where we're at:

Stuff can get faster
Implementation can be simpler
Sync and Async route configs are no longer inconsistent (assuming we do also #3326)
People can still do super clear absolute paths as long as they match their parent route perfectly

I'd say for (2), if we keep support for non-conflicting absolute paths, the bigger change is that things become simpler conceptually. The implementation ends up looking almost the same, it's just that we know that if a parent route doesn't match, then it's "cleaner" to say that child routes won't match either.

I'm thinking that we should actually move the matching logic into the route classes entirely.

As for the performance gains and simpler implementation, couldn't we also achieve this by transforming absolute routes during initialization, similar to how JSX is resolved?

I don't think so... we actually do need to look at the parent routes. I don't know – it's maybe not such a big deal in practice.

Not much point keeping this open. Need a better plan before it makes sense to merge this.


Game FPS goes down when there are too many XP orbs in the game

The game still had low fps when I moved away from the xp orbs. I thought that would increase my FPS but I guess not.
Video showing the FPS drops https://youtu.be/R0kOxmvTHFg
Partial Solution

Merge other xp orbs in close proximity with each other for increased xp value

Haven't tested myself but it looks like the issue lies in spawninig the enemies(which is resource heavy) and as xpOrbs lie on the ground with time they become heavier to take care of by engine. Test this amount of Orbs without spawning enemies or make orbs disapear over time. (Also I think it's common among bigger games(see btd battles))
As I said it's only a guess.

I see two solutions

XP orbs are not a thing
XP orbs disappear after X seconds

I think I like the former because with the latter the player will be missing XP orbs and that does not seem fun.

I've never digged into that but what about multi-threading?

I've only used multi-threading when doing multiplayer so I wouldn't know.
If a game requires multi-threading for a simple mechanic like this then it is probably better to not add it at all.


Fix for when 'trailer' is indented

Pull request
Thanks for improving pdfminer.six! Please include the following information to
help us discuss and merge this PR:
Fix a bug where trailer being indented caused a bug. Thanks to @pietermarsman for suggesting the fix.
Closes #214
How Has This Been Tested?
There is an example script and PDF in #214.
Checklist

[x] I have added tests that prove my fix is effective or that my feature
works  (N/A -> we don't really want to add this PDF to our test suite, correct?)
[X] I have added docstrings to newly created methods and classes  (N/A)
[X] I have optimized the code at least one time after creating the initial
version
[X] I have updated the README.md or I am verified that this
is not necessary
[X] I have updated the readthedocs documentation or I
verified that this is not necessary
[X] I have added a consice human-readable description of the change to
CHANGELOG.md

@pietermarsman I just pushed a new commit addressing your code review :+1:

Oops! Merged this while it was broken...


Refactored code to enable reuse, added code for generating changes over time directly into notebook

This merge was intended for the forked repository, rather than upstream.


Server Response Auto load

Hy,
After loading the page, my spreadsheet is empty, but when I perform an operation (scrolling, searching) I get a server response.
How can I make the server response run automatically after the page loads?
Maybe an idea? Or a sample code?
My source code and structure:
datalist.php =>Data from the database
"deferLoading" Is this parameter required?
index.php

Name
Status
Modify
Delete

let table = new JSTable("#recordlist", {
	serverSide : true,
	addQueryParams: false,
	deferLoading: 5,
	ajax : "datalist.php"
});

Yes, this is correct, the first rendering needs to be done when creating the table.

Very good. Thank you very much. Are you planning any new features or fixes in the script in the future?

Actually there is currently nothing specific planned. Do you have a feature request?

I would be interested for the server to respond automatically after the page loads (html and javascript code should be php free).

Great. Thank you ;)

Hy Trekky12! Did you manage to look it up?

Could you please test the version in the development branch? When the option deferLoading is not set the table should be loaded from the server.

Success. The server data is downloaded without entering the php code (In Javascript code without specifying a deferLoading value).

Great! I've published the changes in the new version.
This update is free ;-) You can of course buy me a coffee if you like at https://www.buymeacoffee.com/YXln3gCkm

Great! I've published the changes in the new version. This update is free ;-) You can of course buy me a coffee if you like at https://www.buymeacoffee.com/YXln3gCkm

Thank you very much for your help. I invited you to coffee. :)

Great! Thank you! ☺


CASMPET-7238: /etc/target/saveconfig.json exists as a dir instead of file

Summary and Scope
The iscsi configuration is saved in /etc/target/saveconfig.json. But on some systems this exists as directory and actual file is inside this directory as /etc/target/saveconfig.json/saveconfig.json.temp Hence this case needs to handled in SBPS Marshal agent, else SBPS Marshal agent will fail. This code fix is addressing this issue.
Issues and Related PRs
None.
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.

Resolves [issue id](issue link): - CASMPET-7238
Change will also be needed in <insert branch name here>: N/A
Future work required by [issue id](issue link):  N/A
Documentation changes required in [issue id](issue link): N/A
Merge with/before/after <insert PR URL here>: N/A

Testing
Tested on Starlord where 1.6.0-alpha.67 was installed and issue was reproduced.
Tested on:
Starlord.
Test description:
The issue was reproduced on w002 and w003 of starlord where /etc/target/saveconfig.json existed as directory instead of file. So after applying the code fix. Restarted the SBPS marshal agent (systemd service), then Marshal agent successfuly ran fine.

Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)?: yes
Were continuous integration tests run? If not, why?
Was upgrade tested? If not, why?: TBD
Was downgrade tested? If not, why?: N/A
Were new tests (or test issues/Jiras) created for this change?; No

Risks and Mitigations
None
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] CHANGELOG.md updated
[x] Testing is appropriate and complete, if applicable

This feels like patching the symptom, and not fixing the underlying problem that something is creating /etc/target/saveconfig.json as a directory.  Have you tried to find where this is happening?

This is the wrong change, it is addressing the symptom and not the underlying problem.
I think I've found the underlying issue:
ncn-w002:/var/log # kubectl exec -it -n sysmgmt-health cray-sysmgmt-health-node-exporter-iscsi-s7qvn -- sh
/ # ps axl
PID   USER     TIME  COMMAND
    1 root      0:02 bash /scripts/iscsi_entrypoint.sh
40741 root      0:00 sh
40777 root      0:00 sleep 28
40778 root      0:00 ps axl
/ # ls /etc/target
saveconfig.json
/ # ls -l /etc/target
total 0
drwxr-xr-x    0 root     root             6 Sep 24 12:06 saveconfig.json

the yaml for this has:
     - name: saveconfig
       hostPath:
         path: /etc/target/saveconfig.json

and when it doesn't exist, I believe this is creating it as a directory.  See https://kubernetes.io/docs/concepts/storage/volumes/#hostpath.  There are a few possible fixes, these are in the cray-sysmgmt-health repository:

Mount the parent directory, not the file:

diff --git a/kubernetes/cray-sysmgmt-health/templates/iscsi/iscsi_daemon.yaml b/kubernetes/cray-sysmgmt-health/templates/iscsi/iscsi_daemon.yaml
index acb1317..52a2adf 100644
--- a/kubernetes/cray-sysmgmt-health/templates/iscsi/iscsi_daemon.yaml
+++ b/kubernetes/cray-sysmgmt-health/templates/iscsi/iscsi_daemon.yaml
@@ -30,7 +30,7 @@ spec:
         - mountPath: /iscsi
           name: sysfs
           readOnly: true
-        - mountPath: /etc/target/saveconfig.json
+        - mountPath: /etc/target
           name: saveconfig
           readOnly: true
         - mountPath: /var/lib/node_exporter
@@ -45,7 +45,7 @@ spec:
           path: /sys/kernel/config/target/iscsi/
       - name: saveconfig
         hostPath:
-          path: /etc/target/saveconfig.json
+          path: /etc/target
       - name: host-textfile
         hostPath:
           path: /var/lib/node_exporter

Set the type to FileOrCreate:

diff --git a/kubernetes/cray-sysmgmt-health/templates/iscsi/iscsi_daemon.yaml b/kubernetes/cray-sysmgmt-health/templates/iscsi/iscsi_daemon.yaml
index acb1317..fc9c66b 100644
--- a/kubernetes/cray-sysmgmt-health/templates/iscsi/iscsi_daemon.yaml
+++ b/kubernetes/cray-sysmgmt-health/templates/iscsi/iscsi_daemon.yaml
@@ -32,6 +32,7 @@ spec:
           readOnly: true
         - mountPath: /etc/target/saveconfig.json
           name: saveconfig
+          type: "FileOrCreate"
           readOnly: true
         - mountPath: /var/lib/node_exporter
           name: host-textfile

This will cause the file to be created if it doesn't exist.  If it is set to type: "File", then it will fail if the file doesn't already exist.  I'm thinking the best solution is the first option, mount /etc/target.

I tested the first option on starlord by manually editing the daemonset to mount /etc/target, and the container now shows:
ncn-w002:/var/log # kubectl exec -it -n sysmgmt-health   cray-sysmgmt-health-node-exporter-iscsi-czvxj -- sh
/ # ls /etc/target
alua             backup           pr               saveconfig.json

Please open a new PR for the cray-sysmgmt-health repository and fix the underlying issue there.


Add deprecation notices to Dask chart

We are migrating the Dask community helm charts over to our own repository that will be registered on Helm Hub as per the instructions https://helm.sh/blog/intro-helm-hub/.
This PR adds deprecation notices to the chart in stable and points users to the new repository.
Please let me know if there is anything else I need to change here.
cc @mrocklin

@jacobtomlinson
Could you sign DCO and bump the chart version to latest for one last time please?

/ok-to-test

/lgtm

/lgtm cancel

Done @davidkarlsen. I hadn't seen that process in the docs, I think I've followed it correctly now.

/retest

Yeah seems a bit weird. I've updated to reflect that anyway.

Changes have been made @davidkarlsen. Can I get another review on this?

We've moved over to developing on our own hosted chart so please could we get this reviewed and merged so that folks know this one is deprecated?

Thanks @scottrigby. Changes made.

/test pull-charts-e2e

/lgtm

🎉