Doing my backup I see repeating Error 409 Conflict. What does this error mean and how could I fix it?

2016/01/09 03:00:13 15 boda laura y oscar/foto/1/DCIM/100EOS5D/IMG_2158.CR2: Received error: HTTP code 409: "409 Conflict", reponse body: {"logref":"b8a1c898-b674-11e5-94a1-25dbf54c992b","message":"Node with the name img_2158.cr2 already exists under parentId ErQpIn7aQJyboAPthMpXow conflicting NodeId: PipzSt9OQECDw6-CmJ-c-Q","code":"NAME_ALREADY_EXISTS","info":{"nodeId":"PipzSt9OQECDw6-CmJ-c-Q"}}

retrying 4/10

Thanks!
David

Have you got a file called MG_2158.CR2 and another called img_2158.cr2 would be the first thing to check?  Amazon cloud drive can't have files which differ only in case.
If it does that every time you sync then that is probably the explanation.  If not then retrying the sync will probably clear it up.

Hello Nick, thank you for responding my question.
I retry this same backup today to see if I pass errors but I have no good news to tell you. These are the errors.
Have you any idea for me?
Best regards,
David.
2016/01/12 00:17:23 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"78455be4-b8b9-11e5-a9e1-7b3d3af0708c","message":"Next token is expired"}
2016/01/12 00:17:54
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 1
Checks:                 0
Transferred:            0
Elapsed time:     13m1.8s
2016/01/12 00:18:05 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"9174f55f-b8b9-11e5-89f9-9fa63cc188bd","message":"Next token is expired"}
2016/01/12 00:18:39 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"a5baeeea-b8b9-11e5-8a5c-1dc936022f78","message":"Next token is expired"}
2016/01/12 00:18:54
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 3
Checks:                 0
Transferred:            0
Elapsed time:     14m1.8s
2016/01/12 00:19:13 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"b9c60162-b8b9-11e5-a4b6-1dab780678ad","message":"Next token is expired"}
2016/01/12 00:19:40 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"ca0abd2f-b8b9-11e5-af9a-a35439bbe5ef","message":"Next token is expired"}
2016/01/12 00:19:54
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 5
Checks:                 0
Transferred:            0
Elapsed time:     15m1.8s
2016/01/12 00:20:24 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"e472fdf6-b8b9-11e5-b206-c5271ed18146","message":"Next token is expired"}
2016/01/12 00:20:54
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 6
Checks:                 0
Transferred:            0
Elapsed time:     16m1.8s
2016/01/12 00:20:58 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"f86e32c7-b8b9-11e5-9e59-aff0ed81ea31","message":"Next token is expired"}

And this continues with this:
2016/01/12 00:24:15 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"6e1a192f-b8ba-11e5-b690-2fe169be019f","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"722d30ca-b8ba-11e5-b71b-c9f7a2b1755b","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20150828/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"722d30ca-b8ba-11e5-b71b-c9f7a2b1755b","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"72391714-b8ba-11e5-9baa-bf30e079a361","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20150803/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"72391714-b8ba-11e5-9baa-bf30e079a361","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"7243ec7e-b8ba-11e5-8445-1b2f4ae2e53e","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/android note 2/DCIM/Camera/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"7243ec7e-b8ba-11e5-8445-1b2f4ae2e53e","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/android note 2/DCIM/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"7243ec7e-b8ba-11e5-8445-1b2f4ae2e53e","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/android note 2/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"7243ec7e-b8ba-11e5-8445-1b2f4ae2e53e","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"724af121-b8ba-11e5-995b-c189821f5878","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151127/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"724af121-b8ba-11e5-995b-c189821f5878","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"725467e6-b8ba-11e5-8166-a18906a156dc","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151222/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"725467e6-b8ba-11e5-8166-a18906a156dc","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"72611157-b8ba-11e5-a8c9-e948bfd4d12f","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151210/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"72611157-b8ba-11e5-a8c9-e948bfd4d12f","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"7261ae03-b8ba-11e5-8d80-8f63cdfc2fc5","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151122/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"7261ae03-b8ba-11e5-8d80-8f63cdfc2fc5","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"7263a9bc-b8ba-11e5-af9a-a35439bbe5ef","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151026/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"7263a9bc-b8ba-11e5-af9a-a35439bbe5ef","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"72668f89-b8ba-11e5-8c22-03e2f37f8936","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151202/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"72668f89-b8ba-11e5-8c22-03e2f37f8936","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"725d199f-b8ba-11e5-8fc9-336f8529d06d","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151206/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"725d199f-b8ba-11e5-8fc9-336f8529d06d","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"726fde54-b8ba-11e5-8b33-614e3613c0e9","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151224/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"726fde54-b8ba-11e5-8b33-614e3613c0e9","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"7271dad7-b8ba-11e5-a065-13a227994cb3","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151225/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"7271dad7-b8ba-11e5-a065-13a227994cb3","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"7275ab5a-b8ba-11e5-9794-07a8a8d1b2ba","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151113/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"7275ab5a-b8ba-11e5-9794-07a8a8d1b2ba","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"72784336-b8ba-11e5-bad5-ad2bf291595d","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/copia note2 julio 2014/DCIM/Camera/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"72784336-b8ba-11e5-bad5-ad2bf291595d","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"727de82e-b8ba-11e5-89f9-9fa63cc188bd","message":"Next token is expired"}
2016/01/12 00:24:22 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20160109/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"727de82e-b8ba-11e5-89f9-9fa63cc188bd","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"72875e3d-b8ba-11e5-8e26-8333432c69ae","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Error reading fotos y videos personales/note2 wassap 12nov2015/WhatsApp Images/Sent/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"72875e3d-b8ba-11e5-8e26-8333432c69ae","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"728fe9be-b8ba-11e5-92f4-55012bead4b9","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Error reading fotos y videos personales/copia note2 julio 2014/ACRCallsBackup/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"728fe9be-b8ba-11e5-92f4-55012bead4b9","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"729085a2-b8ba-11e5-95ad-476432104ce0","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Error reading fotos y videos personales/20151102/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"729085a2-b8ba-11e5-95ad-476432104ce0","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Couldn't list files: HTTP code 400: "400 Bad Request", reponse body: {"logref":"729715da-b8ba-11e5-b7ed-73cd3a14c1ba","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Error reading fotos y videos personales/note2 wassap 12nov2015/WhatsApp Images/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"729715da-b8ba-11e5-b7ed-73cd3a14c1ba","message":"Next token is expired"}
2016/01/12 00:24:23 Amazon cloud drive root '9-1': Error reading fotos y videos personales/note2 wassap 12nov2015/:HTTP code 400: "400 Bad Request", reponse body: {"logref":"729715da-b8ba-11e5-b7ed-73cd3a14c1ba","message":"Next token is expired"}

I haven't see `Next token is expired

Does the listing take a really long time?

Well, it is less than 13 minutes. I guess it is because of some server restarts/reconfiguration going on at Amazon.
The failure is in func (s *NodesService) listNodes, but it doesn't do anything else than reading nodes. Concurrent reads are limited by the pacer, so we don't do limit the client in any fashion.
Are you by any chance running multiple simultaneous uploads?
I don't know if writes from another client will invalidate the tokens. Depends on Amazon.

Fortunately, the error "next token is expired" was only that day and today is not present. Less bad.
Responding to your question Nick. Yes, I have many jpg images with same file name, but in different folders. I haven't two images with same file name in same folder.
Let me give you some more extra information. I uploaded the first backup of this usb drive (1.5TB), using the official amazon desktop application, and now I am trying to use rclone to uploading just the new files. At the moment there I haven't added new files to the usb drive, so rclone should check all and tell me, there isn't nothing to copy.
Could you fix rclone to admit having same filename in different folders on ACD or do you think Amazon doesn't admit it?. If you think last option, it extrange for me that I was able to upload the entire usb using official acd desktop app.
Let's see... Kind regards and thank you for your interest in this issue
David

same filename in different folders on ACD

This shouldn't be a problem.
I think the problem might just have been temporary - does the sync work properly now?

Sounds to me like https://github.com/ncw/rclone/issues/263 I'm guessing the directory you're uploading contains a lot of files?
Amazon Cloud Drive has been finicky for the past month or so, and it seems to be mostly Amazon's fault. The sync should eventually work; it depends on the day.

No, it continues giving error in same point. I have tried rclone copy for the full hard disk drive another 4 days more and always gives me the same errors with it reaches this folder:

boda laura y oscar/foto/1/DCIM/100EOS5D/

To discard problems over this folder, I have tried rclone copy for this folder only and it worked well without errors.

Tested again just now and continues giving same error.
lines of error here:
http://pastebin.com/b8bbDccd
It could be any database used by rclone or any configuration file used for rclone to annotate what things to do in this backup, corrupted or broken?. If yes, is there any way to clean or recreate this cache, db or config file in rclone?.

@bunset thank you that log is very useful.
I can see the "Next token is expired" messages.  It is clear to me that these are the cause of the "409 Conflict" messages - rclone didn't read part of the directory listing, so missed out some files.
It would be fairly easy to change the recursion strategy for listing from depth first into width first - that should fix the token expired messages hopefully.
Also I'm concerned that the error in the listing didn't seem to get passed up to the master sync command - it really should have done.
Also rclone spends ages retrying those 409 Conflicts for no gain.

I'm also getting this 409 Conflict (NAME_ALREADY_EXISTS) error. Trying to copy 250GB folder with photos. My camera rolled over its file name counter several times so there a duplicities but never in the same folder. Below is a link to verbose logs and a list of all photos I back up. Each time I run rclone the error appears on different directory and file. I still need to upload most of the photos but the copy get so slow with the 409 error and retries that it would be impossible to finish in reasonable time. I run rclone v1.26 on Synology NAS. First time I ran rclone I managed to copy 100GB of photos without any error. Then we had power outage and since then I encounter this error.
logs and file list of local photo directory
https://www.dropbox.com/sh/8rk42habdvtaf8h/AAC6xdXArxZAtQNrWBhYJ6JCa?dl=0

@avgex Thanks for that - very helpful.
I can see the same "Next token is expired" followed later by the "409 Conflict" errors, so this looks like the same problem.
I note also that your file system appears to be in latin1 instead of UTF-8.  This may mean that some of the names with accents look a bit odd in Amazon's web interface (see the local docs).  You might want to run convmv on the filesystem to make it utf-8 which would be the modern thing to do. (I made myself a ticket to write this up #300)

Hi Nick. Thank you for reviewing the errors.
Let me know if there is anything else I can help you until you can fix it, for example if you need remote connection to my desktop computer to see these errors or debugging them while they are happening. Just tell me.
Thanks and Kind regards!
David

Another log of another try just now. Same error after doing the backup very well along hours. It comes into a loop over same error.
https://www.dropbox.com/s/thn9wiykfcoyqmd/logrclone.txt?dl=0

I'm working on a fix - I'll put a link to a beta release in a day or two.

Thank you Nick!

I've made a beta for you to try: http://pub.rclone.org/v1.26-34-gde3cf5eβ/
Any feedback much appreciated.

tried twice the beta, it got stuck each time
https://www.dropbox.com/sh/8rk42habdvtaf8h/AAC36oI8RTeZtB7pG6CFGM79a/v1.26-34-gde3cf5eß?dl=0

Thank you Nick, I am testing it, running my backup, I tell you soon, how is it going!

Hi Nick, after 53 min. tried I had to kill the process because there was not progression on backup. It is not working well.
Kind regards!
David
Log:
MacBook-Pro-13:bin David$ cat prueba.sh
#!/bin/sh
si se conecta el 9-1 usb
#if [ -d  /Volumes/9-1\ 3TB ]
#then
#si otro proceso rclone no está ejecutandose
#if pgrep rclone;
#then
#/usr/bin/osascript -e 'display notification "Prueba.sh" with title "Otro proceso rclone está todavía ejecutandose"';
#else
#/usr/bin/osascript -e 'display notification "Prueba.sh" with title "9-1 conectado - Haciendo backup del 9-1 en acd"'
#echo "Comenzando rclone del 9-1 en acd" >> /Users/David/bin/cronlog.log;
#echo "/Users/David/bin/rclone --log-file=/Users/David/bin/cronlog.log copy /Volumes/9-1\ 3TB/9-1/ remote:9-1" >> /Users/David/bin/cronlog.log;
#/Users/David/bin/rclone --log-file=/Users/David/bin/cronlog.log copy /Volumes/9-1\ 3TB/9-1/ remote:9-1
#fi
#fi
# rclone -v copy /Volumes/9-1\ 3TB/9-1/trabajo\ fotos\ boda\ laura\ y\ oscar/ remote:9-1/"trabajo fotos boda laura y oscar"

MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$
MacBook-Pro-13:bin David$ /Users/David/bin/rclone -v copy /Volumes/9-1\ 3TB/9-1/ remote:9-1
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Modify window not supported
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Building file list
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Reading ""
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Finished reading ""
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Reading "16 boda elena&alex 13-jun-2015/"
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Reading "trabajo fotos boda virginia sergio/"
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Reading "trabajo fotos de boda elena y alex/"
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Reading "laura fotos embarazada aranjuez 17-jun-2015/"
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Reading "lr5-prebodas-veronica-pilar-laura/"
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Reading "trabajo album boda esther cesar/"
2016/01/21 00:13:45 Amazon cloud drive root '9-1': Reading "slideshow virginia sergio/"
2016/01/21 00:13:46 Amazon cloud drive root '9-1': Finished reading "16 boda elena&alex 13-jun-2015/"
2016/01/21 00:13:46 Amazon cloud drive root '9-1': Finished reading "laura fotos embarazada aranjuez 17-jun-2015/"
2016/01/21 00:13:46 Amazon cloud drive root '9-1': Finished reading "trabajo fotos de boda elena y alex/"
2016/01/21 00:13:46 Amazon cloud drive root '9-1': Finished reading "trabajo fotos boda virginia sergio/"
2016/01/21 00:13:46 Amazon cloud drive root '9-1': Finished reading "lr5-prebodas-veronica-pilar-laura/"
2016/01/21 00:13:46 Amazon cloud drive root '9-1': Finished reading "trabajo album boda esther cesar/"
2016/01/21 00:13:46 Amazon cloud drive root '9-1': Finished reading "slideshow virginia sergio/"
2016/01/21 00:14:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      1m2.1s
2016/01/21 00:15:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      2m2.1s
2016/01/21 00:16:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      3m2.1s
2016/01/21 00:17:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      4m2.1s
2016/01/21 00:18:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      5m2.1s
2016/01/21 00:19:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      6m2.1s
2016/01/21 00:20:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      7m2.1s
2016/01/21 00:21:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      8m2.1s
2016/01/21 00:22:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:      9m2.1s
2016/01/21 00:23:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     10m2.1s
2016/01/21 00:24:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     11m2.1s
2016/01/21 00:25:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     12m2.1s
2016/01/21 00:26:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     13m2.1s
2016/01/21 00:27:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     14m2.1s
2016/01/21 00:28:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     15m2.1s
2016/01/21 00:29:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     16m2.1s
2016/01/21 00:30:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     17m2.1s
2016/01/21 00:31:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     18m2.1s
2016/01/21 00:32:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     19m2.1s
2016/01/21 00:33:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     20m2.1s
2016/01/21 00:34:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     21m2.1s
2016/01/21 00:35:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     22m2.1s
2016/01/21 00:36:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     23m2.1s
2016/01/21 00:37:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     24m2.1s
2016/01/21 00:38:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     25m2.1s
2016/01/21 00:39:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     26m2.1s
2016/01/21 00:40:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     27m2.1s
2016/01/21 00:41:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     28m2.1s
2016/01/21 00:42:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     29m2.1s
2016/01/21 00:43:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     30m2.1s
2016/01/21 00:44:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     31m2.1s
2016/01/21 00:45:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     32m2.1s
2016/01/21 00:46:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     33m2.1s
2016/01/21 00:47:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     34m2.1s
2016/01/21 00:48:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     35m2.1s
2016/01/21 00:49:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     36m2.1s
2016/01/21 00:50:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     37m2.1s
2016/01/21 00:51:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     38m2.1s
2016/01/21 00:52:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     39m2.1s
2016/01/21 00:53:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     40m2.1s
2016/01/21 00:54:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     41m2.1s
2016/01/21 00:55:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     42m2.1s
2016/01/21 00:56:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     43m2.1s
2016/01/21 00:57:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     44m2.1s
2016/01/21 00:58:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     45m2.1s
2016/01/21 00:59:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     46m2.1s
2016/01/21 01:00:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     47m2.1s
2016/01/21 01:01:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     48m2.1s
2016/01/21 01:02:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     49m2.1s
MacBook-Pro-13:bin David$ cat prueba.sh
#!/bin/sh
si se conecta el 9-1 usb
#if 2016/01/21 01:03:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     50m2.1s
2016/01/21 01:04:45
Transferred:            0 Bytes (   0.00 kByte/s)
Errors:                 0
Checks:                 0
Transferred:            0
Elapsed time:     51m2.1s

Hello Nick.
I think you did close this issue by mistake. It is without resolving, may you change it to open?
Kind regards and happy saturday!

the fix will be released in v1.27
@ncw can we test it out in some beta ?

Thanks for your reports.  It looks like there is still a problem :-(  I'll see if I can replicate it.
If you could send me a log with rclone -v --dump-headers of it pausing that would be really helpful. It will be very big and contain sensitive info, so If you could email it to me privately that would be really helpful.
Here is a new beta.  I don't think it will fix the problem, but just so we are testing the same thing!
http://pub.rclone.org/v1.26-39-gc3a0c0cβ/

Actually don't bother sending me a log - I've reproduced the problem!
Will make a new Beta when I've figured out what is going on...

Thank you Nick, I keep waiting for your fix. Will you tell us your progress here on this thread?

This should be fixed in version 1.27 which I've just uploaded :-)

thank you Nick for the fix, I finally managed to upload some new files. However I noticed in log file that the "409 Conflict" error is still there, but it does not get stuck as before. Also the files in error seem to be all backed up already on amazon cloud, so it is not a big deal
here is the log file if you want  to check:
https://dl.dropboxusercontent.com/u/432618/rcopy_/log3.zip

@avgex I see what happened there - that log was really helpful thank you.
The 409 errors are caused by the listing of the files going wrong.  Looks like I have a few more things to retry...
I made an issue here #340 - if you subscribe to that then you'll get updates on it.

Hello Nick!
I have tested it now and it is working well. Awesome.
One thing, please. When I do a copy I can see a resume at the end of copy process, showing me how many errors I had doing my copy, but every error I had was displayed while rclone was doing the copy in the middle of thousand of lines, so it is very difficult for me to get a clean list of just files with error. Is there any way or do you know any trick, so I can get a simple list of files giving error in my copy?
Thank you very much, kind regards,
David

@bunset if you run rclone without the -v flag, it should only tell you about the errors rather than about everything it is copying.

Hi, I'm also getting many 409 errors while syncing a folder, for example:
2016/07/08 13:26:34 avoidthecrowd/www/tmp/cache/sprockets/v3.0/ouIVwmb-ntMxhEoLCci-Im11GMCyKg0vRXAHhhRPaDU.cache: Failed to copy: HTTP code 409: "409 Conflict", reponse body: {"logref":"d37d396e-44fe-11e6-9e80-7576dc88fd3e","message":"Node with the name ouivwmb-ntmxheolcci-im11gmcykg0vrxahhhrpadu.cache already exists under parentId lXvdUqFIQKSGE_-XBRGCow conflicting NodeId: 8IsDNjWQTGmWDvxA4DVi6g","code":"NAME_ALREADY_EXISTS","info":{"nodeId":"8IsDNjWQTGmWDvxA4DVi6g"}} 2016/07/08 13:27:16 avoidthecrowd/www/tmp/cache/sprockets/v3.0/n1esMikxkVncQWoTefSzE79C8RfTVdUWWEo7C2UIQi4.cache: Failed to copy: HTTP code 409: "409 Conflict", reponse body: {"logref":"ec5e656e-44fe-11e6-a6dd-573b84944f90","message":"Node with the name n1esmikxkvncqwotefsze79c8rftvduwweo7c2uiqi4.cache already exists under parentId lXvdUqFIQKSGE_-XBRGCow conflicting NodeId: umkCEev_RT-n8eC6IOrNnQ","code":"NAME_ALREADY_EXISTS","info":{"nodeId":"umkCEev_RT-n8eC6IOrNnQ"}}
The names are not repeated locally (nor with a different case). Isn't rclone supposed to overwrite the remote files?

@fcarreiro are you using the latest version of rclone - 1.30 ?  If not can you try that.  If you get the problems with 1.30 then can you open a new issue with a log of all the errors - 409 errors are caused by the directory listing going wrong earlier which I believe is fixed in 1.30.

I was using version 1.29; I'm now checking with 1.30 and will let you know if it still fails. Thanks.


feat: export initialize stores for Modal, Toast and Drawer

Linked Issue
Closes #{issueNumber}
Description
Export initialize stores for Modal, Toast and Drawer
Changsets
Instructions: Changesets automate our changelog. If you modify files in /packages/skeleton, run pnpm changeset in the root of the monorepo, follow the prompts, then commit the markdown file. Changes that add features should be minor while chores and bugfixes should be patch. Please prefix the changeset message with feat:, bugfix: or chore:.
Checklist
Please read and apply all contribution requirements.

[x] This PR targets the dev branch (NEVER master)
[x] Documentation reflects all relevant changes
[x] Branch is prefixed with: docs/, feat/, chore/, bugfix/
[x] Ensure Svelte and Typescript linting is current - run pnpm check
[x] Ensure Prettier linting is current - run pnpm format
[x] All test cases are passing - run pnpm test
[x] Includes a changeset (if relevant; see above)

@ibilux I reviewed this with @AdrianGonz97 yesterday, who implemented the change to the stores for these features. He confirmed the choice was deliberate not to export the initialize methods. Though I don't know the specifics - perhaps he can elaborate.
Can you maybe explain your goals here? Are you encountering a specific issue that you believe this would help with?

As @endigo9740 mentioned, these functions were purposefully not exposed to simplify the surface area of the API. Rather than having to initialize each store individually, they can all be initialized with initializeStores. If you're concerned about the "overhead" of initializing all of them, I wouldn't worry about them since it's extremely minimal.

@endigo9740 If I don't want to use a store for some case it shouldn't be initial. I want to control what stores to initialize.

@AdrianGonz97 I want to control what stores to initialize and use, in case I want to implement different store or extend one of them.

@ibilux
Sure, I can understand wanting more control over that. But how does exporting the individual store initializers help you achieve "implement different store or extend one of them"?
If anything, it would make more sense to expose their respective services that generates the stores so that you can set them yourself...
Additionally, if you really want to extend our stores, you're free to get them from context and modify them from there.

@ibilux I might suggest we go ahead and close this out. I don't think this something we're going to move forward with. I'd suggest following Adrian's advice above instead.
If you you would like to open a GitHub Discussions thread to discuss further or need additional support, please feel free to tag either of us. Otherwise we're available on Discord in the #contributors channel most weekdays.


update branch 4

Issue #, if available:
Updated with correct working script
Required removing trainingcompiler (which wasn't working)
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Updated with moving docker to prevent testing issues. Works on instances with at least 24GB of ram on GPU.


Prevent Resubmission requests from going through running-open

It makes no sense for them to be running-open although the OpenRunningTimeout value is inherited from the original workflow which makes them go through this.

fixed. running open has different meaning now.


CMake flag and envvar to disable HIP kernels

Added CMake option, MIOPEN_USE_HIP_KERNELS, that can disable HIP kernels.
Added env.var, MIOPEN_DEBUG_HIP_KERNELS, that allows to override the CMake option.
Documentation updated.
Some tests directly use HIP kernels, e.g. handle_test. Those left as is.

All tests passed, ready to go.


Source Control in devcontainers does not auto-refresh; requires manually pressing refresh button

Does this issue occur when all extensions are disabled?: Yes

VS Code Version:

Version: 1.85.1 (user setup)
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:49:37.021Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19045

OS Version:

Edition	Windows 10 Pro
Version	22H2
Installed on	6/4/2023
OS build	19045.3803
Experience	Windows Feature Experience Pack 1000.19053.1000.0

Steps to Reproduce:

open git repo folder in vscode in windows
reopen folder in devcontainer
edit an existing file
source control does not detect this change (git output also shows no activity either)
press refresh button in source control panel and the changes appear (very slow)

I have tried:

https://github.com/microsoft/vscode-remote-release/issues/7628
adding "git.autorefresh": true to settings in devcontainer.json as well as in both default vscode settings.json and user settings.json

I am not using Docker Desktop, but a coworker is and has applied the same attempts above with no success. Everything works fine if I connect to WSL FIRST, then open my repo folder (cloned inside WSL), then open the devcontainer.

It is happening for me and reported here as well https://github.com/microsoft/vscode/issues/200787

the weird thing is it seems to pickup new, untracked, files fine.

open windows-local repo folder
re-open in container
make new file, call it foobar.txt
source control updates automagically

however...

open windows-local repo folder
re-open in container
edit an existing, already tracked, file (ex add a comment) and save
source control does not update automagically
manually press refresh button - the change is identified

dont know if this is related, but drilling down through /mnt/c/ where the windows fs mounts, there are various permissions at various levels. multiple levels without write permissions

I had the same problem. This is related to the filesystem rights. You can configure them:
1. Create/Edit an /etc/wsl.conf file (as sudo) with the following contents:
   [automount]
   options="metadata"
   Exit WSL

2.  Restart WSL via Rebuild Dev Container

More on WSL file system rights: https://www.reddit.com/r/bashonubuntuonwindows/comments/ovmlk3/unable_to_change_permissions_of_a_file_using/

Thanks, thats very informative. unfortunately it doesnt fix it for me...

Finally found a real fix. Problem is that windows file system and WSL does not communicate well together. Problem is also with performance.
Proper fix to all this is that you need to clone repository inside WSL. This means you need to use "Dev Containers: Clone Repository in Container Volume..."
Once repository is inside WSL then everything works properly Git refresh, also e.g. angular hot reload feature ... Performance is superb ...
@robot-ranger sorry, you are right my firsts suggestion is not the proper one.

@PeterStegnar, thank you very much for looking into this and for sharing the solution. The Source Control view refreshes based on file-system events and there are various known issues where file system events are not delivered when files are stored in the Windows file system. Closing the repository in container volume is the correct fix.
@robot-ranger, I will go ahead and close this issue but please feel free to reopen it in case this does not resolve your issue. Thanks!

Yes, I have already discovered that my repos cloned in wsl work fine.
If I connect to wsl first, open my wsl cloned repo, then open my dev container, it works fine.
I'm cool with that, but Its frustrating that this has been a complaint for ~5 years and it's still not documented the way @lszomoru described it
Why is 'reopen in devcontainer' shown as an option in windows? It straight up doesn't work, hasn't for years. Maybe there should be a warning that shows up if a devcontainer is opened without previously connecting to wsl?
"Warning: File system events are commonly non-functional for windows folder mounts in dev containers. This may cause source control to malfunction. Consider cloning your repo in wsl. Then open your dev container from there."
... Or am I just using devcontainers incorrectly? Is the intent to clone repo contents AFTER container creation? If so, this means devcontainer.json is not stored in the repo?

Why is 'reopen in devcontainer' shown as an option in windows? It straight up doesn't work, hasn't for years. Maybe there should be a warning that shows up if a devcontainer is opened without previously connecting to wsl?

"Warning: File system events are commonly non-functional for windows folder mounts in dev containers. This may cause source control to malfunction. Consider cloning your repo in wsl. Then open your dev container from there."

... Or am I just using devcontainers incorrectly? Is the intent to clone repo contents AFTER container creation? If so, this means devcontainer.json is not stored in the repo?

Adding @chrmarti, who owns our remote container extension to chime in here. Thanks for the feedback.


dev_compiler spread collection failure with await.

A control-flow collection compiled with dartdevc fails at runtime, while it succeeds with dart2js.
Using webdev serve --release succeeds, but webdev serve fails at runtime.
This is using dartdevc version 2.6.0-dev.7.0, so I assume it is using CFE.
The reduced code is
void main() {
    TryDataService().runMe();
}

Future foo() => Future.delayed(Duration(seconds:3), () => [null]);

class TryDataService {
    Function foo1 = foo;  // If this is made static, the error disappears
    Future runMe() async {
        return [...(await foo1())];
    }
}

and it gives the error in Chrome:
dart_sdk.js:5145 Uncaught (in promise) Error: NoSuchMethodError: 'foo1'
Dynamic call of null.
Receiver: null
Arguments: []
    at Object.throw_ [as throw] (dart_sdk.js:3870)
    at Object.defaultNoSuchMethod (dart_sdk.js:4285)
    at Object.noSuchMethod (dart_sdk.js:4281)
    at callNSM (dart_sdk.js:4036)
    at Object._checkAndCall (dart_sdk.js:4038)
    at Object.callMethod (dart_sdk.js:4117)
    at Object.dsend (dart_sdk.js:4120)
    at main.dart:27
    at Generator.next (<anonymous>)
    at runBody (dart_sdk.js:32267)
    at Object._async [as async] (dart_sdk.js:32295)
    at main.TryDataService.new.runMe (main.dart:26)
    at runMe.next (<anonymous>)
    at runBody (dart_sdk.js:32267)
    at Object._async [as async] (dart_sdk.js:32295)
    at main.TryDataService.new.runMe (main.dart:25)
    at main$ (main.dart:18)

The JS code that the example was turned into includes:
  const TryDataService_foo1 = dart.privateName(main, "TryDataService.foo1");
  main.TryDataService = class TryDataService extends core.Object {
    get foo1() {
      return this[foo1];
    }
    set foo1(value) {
      this[foo1] = value;
    }
    runMe() {
      return async.async(dart.dynamic, (function* runMe() {
        return yield async.async(core.List, function*() {
          let t0 = [];
          for (let t1 of core.Iterable._check(yield dart.dsend(this, 'foo1', [])))
            t0[$add](t1);
          return t0;
        });
      }).bind(this));
    }
  };
  (main.TryDataService.new = function() {
    this[foo1] = C2 || CT.C2;
    ;
  }).prototype = main.TryDataService.prototype;

The actual case where we found this failure actually had an object member, and called a method on it:
class A {
   B b;
   Future runMe() async {
      return [ ... await b.foo() ];
}

That is the more typical case in which this would happen.

@whesse - thanks for the small repro!
It appears that when there is a ... with an await, we create a new async closure for it, however we didn't bind it to the enclosing this. Adding .bind(this) in the generated code addresses this problem, so I hope it's not a hard fix on our codegen.
Interestingly, you can still cause this problem when the await is separate from the use of this, for example:
void main() async {
  print(await A().run());
}

class A {
    m1() => [1, 2];
    Future run() async {
      return [await null, ...m1()];
    }
}

Also triggers the issue.
The issue occurs both in ddc and ddk.

We may be able to fix this by binding "this" to the generator. E.g., turning:
    return async.async(dart.void, (function* act() {
      core.print(yield async.async(ListOfString(), function*() {
        let t0 = JSArrayOfString().of([]);
        for (let t1 of (yield this[_ids$].serve(prefix)))
          t0[$add](t1);
        return t0;
      }));
    }).bind(this));

to
    return async.async(dart.void, (function* act() {
      core.print(yield async.async(ListOfString(), function*() {
        let t0 = JSArrayOfString().of([]);
        for (let t1 of (yield this[_ids$].serve(prefix)))
          t0[$add](t1);
        return t0;
      }.bind(this)));
    }).bind(this));

Found a few places to add a binding. Thanks @Markzipan, _emitGeneratorFunctionExpression is one of them. Preparing a fix.


activity: follow-up from integration

This goes through and adds everything that was TODO on my previous PR, except activity feed.

[X] Allow notification settings for threads
[X] Remove current "full-info" scry on frontend and wrap unreads into a new init scry
[X] Add migration from old unreads
[X] Add handling for devs who enabled %activity already
[X] Show unread counts based on a setting?
[X] Verify everything is in mark-warmer that needs to be

More follow-up:

[ ] Fix issue where clearing main chat window makes dot go away, but then it comes back because of unread threads
[ ] Fix migrated sort order of "read" channels
[ ] Fix on-init of migration
[ ] TLON-1689
[ ] TLON-1556

PR Checklist

[X] Includes changes to desk files
[ ] Describes how you tested the PR locally (test ship vs livenet)
[ ] If a new feature, includes automated tests
[X] Comments added anywhere logic may be confusing without context

Fixes TLON-1924, TLON-1562, TLON-1414

I can't get this installed on fresh ships. The other agents bump, but activity fails
gall: failed
/sys/vane/gall/hoon:<[2.021 15].[2.021 36]>
/app/activity/hoon:<[31 5].[33 17]>
/app/activity/hoon:<[32 7].[32 20]>
/app/activity/hoon:<[32 12].[32 20]>
/app/activity/hoon:<[73 3].[78 31]>
/app/activity/hoon:<[74 3].[78 31]>
/app/activity/hoon:<[75 3].[78 31]>
/app/activity/hoon:<[75 12].[75 26]>
/app/activity/hoon:<[152 3].[200 23]>
/app/activity/hoon:<[153 3].[200 23]>
/app/activity/hoon:<[154 3].[200 23]>
/app/activity/hoon:<[154 7].[156 7]>
/gx/~ralfyr-sidlyn-rispeg-nocput--fabsel-nacreg-linwyc-marzod/chat/~2024.5.28..15.30.19..8057/full/noun

If I comment out the new ++  on-init logic, it goes through.

@latter-bolden latest push should fix


JSON.stringify replacer

Hello everyone, I am configuring the HttpClient with a replacer to JSON.stringify like this:
let replacer = new JsonStringifyReplacer();   // this is my replace i have built
this.http = this.http.configure(x => {
      x.withBaseUrl(CONSTS.ApiUrlBase);
      x.withHeader('Accept', 'application/json;charset=UTF-8');
      x.withReplacer((key, value) => replacer.stringify(key, value));   // here i am using my replacer
});

JsonStringifyReplacer :
export class JsonStringifyReplacer {
    private cache = [];

    stringify(key, value) {
        if (typeof value === 'object' && value !== null) {
            if (this.cache.indexOf(value) !== -1) {
                // Circular reference found, discard key
                return;
            }
            // Store value in our collection
            this.cache.push(value);
        }
        return value;
    }
}

My problem:
This works once, but the cache array is never emptied for the next time the replacer needs to be used.
I also cannot do this:
 x.withReplacer((key, value) => new new JsonStringifyReplacer().stringify(key, value));

because then the cache will be reinitialized for every member the JSON.stringify method is trying to stringify, which defeats the purpose, since the cache is always new.
Any ideas on how to solve this?I thought up some elaborate solutions in my head, but I think I may be over complicating things.

I think right now you'd need to pass your replacer at request creation time instead of at configuration time so it's not shared by all requests. It'd probably be better if the withReplacer helper took a function that returned a replacer, so we could create a new one for each request. Care to open a PR? :-)

Closing for now. The reviver/replacer can be passed per request instead of as part of the global config.


Added TGRSIint::OpenLibrary and calling it at start of grsisort

Now the path and version of the library get printed whenever grsisort is started with a library provided via command line argument or .grsirc (whether raw data files are processed or not).

This might actually print this twice now if a raw file is processed.


Print Structure Generator argument options as a numbered list

The user can type out the option or the number of the argument from the printed list.
They can even type just the start of an option to select it, down to a single letter if there is only one option that starts with that letter.
The selected option is then printed so the user to visually confirm the right option was selected.
Free form arguments with no options (e.g. FILE) still work the same. They get the user's input and that is it.
i.e.:
STRUCTURE - What kind of structure is being built? >
1: basic_encoder
2: stenodyon_decoder
3: properinglish19_decoder
Type out an option or give its index (1-3):
Typing basic_encoder, 1, bas, or b will all select basic_encoder.

I should have merged this before commiting my changes... oh well. More work for me :)

This is actually a really nice feature btw! the wall of text is a bit messy, but it definitely speeds up the process of getting through the structures arguments

I initially was just going to add the cli arguments but then the number
idea came to me so I added it too.
I thought about adding a verbose flag or something since it does turn in to
a wall of text... feel free to tweak. :)
I wanted to figure out how to make some of the options cli arguments, but
those arguments are determined at run time, so I’m not sure how that could
be done. So I figured making picking the option easier was a good
compromise.
Hmm... maybe add a cli argument that takes a list of arguments and then
passes those along. That could work!
Also, I really like your argument handler. It’s pretty clever.
Bob
On Wed, Mar 10, 2021 at 10:19 PM n00b-asaurus @.***>
wrote:

This is actually a really nice feature btw! the wall of text is a bit
messy, but it definitely speeds up the process of getting through the
structures arguments
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/n00b-asaurus/Redstone-Development-Kit/pull/15#issuecomment-796348464,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATELXU4ZG2LXK7CMAKPENBTTDAEANANCNFSM4YZ2FRRQ
.

I think I can tweak it to add a verbose flag.
Thanks for the complement also :)
I figured it might be a good idea to let the structure register the arguments it needs at run time, since the plan is to have the structure generator handle more than just ROMs, and not all instructions will require the same arguments.
You may be right about passing the arguments as a list. That would probably be easiest.

Yeah, it makes sense why you did the arguments that way. Not every
structure needs the same things.
One thought was to pick out a set of standard arguments that every
structure will need, like facing direction, but if some are still run time
one not sure how much that would help. Now that we’ve had argument list
idea that should work nicely.
Thinking about common arguments gave me another idea though. You probably
already plan on doing this, but new structures should keep what common
arguments they have in the same order so people can remember what order
things go in.
I’m on my phone and won’t be at a computer for about a week, and maybe
won’t be able to really look at the code again until March 22, so I can’t
really work on a working concept, but one idea I had would start something
like this:
parser.add_argument(‘-a’, ‘—arguments’, nargs=‘+’, help=‘Arguments to pass
to the structure generator for the chosen structure.’)
And then pass args.arguments to the argument_handler and have it take each
argument off the list one at a time and use it instead of user input. And
if a structure needs more arguments than were given it asks for the rest.
It would be nice if the arguments were handled the same way as user input,
so people can pass in numbers to short names, just like when typing in
arguments.
I look forward to using the tools myself someday. ;)
On Thu, Mar 11, 2021 at 1:01 AM n00b-asaurus @.***>
wrote:

I think I can tweak it to add a verbose flag.
Thanks for the complement also :)
I figured it might be a good idea to let the structure register the
arguments it needs at run time, since the plan is to have the structure
generator handle more than just ROMs, and not all instructions will require
the same arguments.
You may be right about passing the arguments as a list. That would
probably be easiest.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/n00b-asaurus/Redstone-Development-Kit/pull/15#issuecomment-796428304,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATELXU35IMENFW7HTARIUZDTDAW7BANCNFSM4YZ2FRRQ
.


card changes

created cards

You have not defined pubspec.yml file for card images .Fix that .
Also , design is good but not responsive also fix that .

this this i have used very small device pixel 2 hope this time it will work


How can this be done in a automated way.

From the description on this page and the fact it states

B2C applications should NOT be edited:

On other application management portals such as the Application Registration Portal.
Using Graph API or PowerShell

there appears to be no way to generate new app registrations programmatically. Is that correct and if so is there anything on the near term roadmap that will allow us to do it in a automated way?

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

ID: b1c2ea43-4468-6ce2-c963-6940f5cb1d34
Version Independent ID: e91ad7a8-0dbd-79b4-0f1b-b3c5a66d6d78
Content
Content Source
Service: active-directory-b2c

@leftler  Thank you for the valuable feedback. I forwarded your feedback to the content team.

@leftler Would MS Graph work for you? https://developer.microsoft.com/en-us/graph/docs/api-reference/beta/api/application_post_applications

@PatAltimore Would that work against a B2C Active directory? I already do it for my B2B directory.

@leftler Registration should work the same way for apps in an AD tenant.  I haven't tried it myself. I think it would work.

I tried POST Application, but it did not work.
It is displayed on the "App registrations", but it was not displayed on the "Azure AD B2C - Applications".

@leftler @HiroyukiSako , For AD application registration, Graph API would be the option. I'd suggest posting your question to https://stackoverflow.com/questions/tagged/office365 or microsoft-graph.

#please-close

var applicationConfig = {
clientID: 'e760cab2-b9a1-4c0d-86fb-ff7084abd902',
authority: "https://login.microsoftonline.com/tfp/fabrikamb2c.onmicrosoft.com/b2c_1_susi",
b2cScopes: ["https://fabrikamb2c.onmicrosoft.com/demoapi/demo.read"],
webApi: 'https://fabrikamb2chello.azurewebsites.net/hello',
};
In the above authority & b2cScopes value where can we found when we create our own application in the tenant?

@PatAltimore How can you close this with your last comment stating

@leftler @HiroyukiSako , For AD application registration, Graph API would be the option. I'd suggest posting your question to https://stackoverflow.com/questions/tagged/office365 or microsoft-graph.

While your documentation clearly says the opposite:

B2C applications should NOT be edited:

On other application management portals such as the Application Registration Portal.
Using Graph API or PowerShell

Please reopen and document the proper way to automate this!

@ggirard07 Sorry, I guess I misread the original question.  My mistake.  Thanks for pointing this out. I'll send this along to the product team.
Thanks,
Pat

@ggirard07 @shoeb8997 @leftler @HiroyukiSako, I'm sorry.  I gave some incorrect guidance on the original question.  The correct location for feedback on programmatically registering B2C applications is https://feedback.azure.com/forums/169401-azure-active-directory/suggestions/19975480-programmatically-register-b2c-applications
Please upvote the feature if you are interested.


Fix hipcc lib dir

This fixes various issues around the lib path in hipvars.pm and hipcc.pl:

hipvars.pm: Detect the correct lib directory (i.e. 'lib64' or 'lib')
hipcc.pl: Use the correct lib path in the linker arguments
hipcc.pl: Set the DEVICE_LIB_PATH correctly for system installation (e.g. in /usr/lib64/amdgcn/bitcode/)

Note that this does not yet fix the issues around the include directories, which requires not only changes in HIP, but also ROCm-CompilerSupport.
@raramakr, this addresses some of the issues mentioned in https://github.com/ROCm-Developer-Tools/hipamd/issues/43#issuecomment-1222959814. Could you please have a look and merge those changes as you have been working on updating HIP to use GNUInstallDirs (https://github.com/ROCm-Developer-Tools/hipamd/commit/c92a12faf39210e24d329cc2c7e94dd124e69fed)?

@Mystro256, I would appreciate if you could have a look at this and forward it to the right people to get this fixed.

Neat idea, but something to note about hipinfo is that the Debian packagers actually remove this file in their test packages, since it violates the Linux FHS (I think) and is not strictly required. Since Fedora has this policy too, I would advise against detecting the libdir using this logic, since it would be best to use "%exclude %{_libdir}/.hipInfo" in the spec file.
Alternatively the script can be updated to look for "libhsa-runtime64*" in /usr/lib and /usr/lib64, which should also work for Debian, since they use /usr/lib/x86_64-linux-gnu. I'm not sure how insane of an idea of doing this is:
find /usr/lib /usr/lib64 -name libhsa-runtime64* | grep -m1 -o '^/usr/lib.*/'

Good point about the hidden hipInfo file. Ideally we would get rid of those altogether and set those variables during the build process. By maybe that is another problem.
I was toying around with a similar idea of searching for the actual libraries already earlier. If I find the time I will revise the patches to do that. Also happfor somebody else to take the lead.

@cgmb Do you know how the Debian guys deal with this? I figure it might have come up, but I'm less versed in HIP.

hipcc.pl: Set the DEVICE_LIB_PATH correctly for system installation (e.g. in /usr/lib64/amdgcn/bitcode/)

It would be nice to also handle /usr/lib/x86_64-linux-gnu/amdgcn/bitcode/, which is where the files are currently exist on Debian. Would that be supported by this change?

@Mystro256 I have updated this branch now to adopt your suggestion to look for the HSA runtime library. This works well in my Fedora packages where .hipInfo and .hipVersion are not present anymore.
@cgmb at the moment, this patch does not handle the Debian case for DEVICE_LIB_PATH. With the latest change, I only replace the hardcoded 'lib' to $LIB which corresponds lib*/ without the trailing slash. It does not account for the additional multi-arch directory (i.e. x86_64-linux-gnu) in the Debian case. However, that could be added probably fairly easily, but as I am not really familiar with the Debian filesystem layout, I wasn't even aware of this.
The $LIB directory is also used for setting the search directories for the linker (via -L or -rpath). In the Fedora case, this leads to having -L/usr/lib64 added in various places, which is as far as I can tell not needed at all since that is in the default search path already anyway. I'm at a loss with this in the Debian case.

Thanks for your review and comments @cgmb. I have converted this PR to a draft since I realised that there are still various entangled issues in the perl scripts for hipcc related to an installation in /usr. I previously thought the issues around lib and inlcude paths were somewhat separate, but it's just one big mess there.
I have no a fully working version of all this, and was able to compile and run the HIP examples now using only Fedora packages. But this required some major surgery, and will require local patches either way, as ROCM 5.2 doesn't work with upstream Clang 14 anymore and requires the AMD's Clang.


How to use image/files from shopify as banners

hi,
I see there is an API available to get images - https://help.shopify.com/api/storefront-api/reference/object/image .
I'm assuming this is through the files upload, however I'm not able to get it to work. Can you show an example of how it is supposed to be used ?

Closing because this project is now deprecated.


IRI normalization through core::fmt::Display, with neither allocation nor temporary variable length buffers

This is possible, and I already implemented working code.
I'll replace the internals of the current NormalizationTask's methods using core::fmt::Display.
And at the next release with breaking changes (possibly v0.6.0), I might be able to remove or simplify NormalizationTask trait and usage of task types.

By the commit 793a8768d970c4ca7b48458db8c124f3b91f1cba, normalization is provided through core::fmt::Display internally.
I'll make it public at another branch.

Exposed as normalize::Normalized type.
Alreday merged to develop branch, and waiting for the next release (v0.6.0).


Use latest knative-client dependency for knative services

Purpose

The knative service artifacts were generated using custom spec
definitions. With this PR those custom spec definitions are replaced
with defintions that are provided with knative-client dependency.

Along with the change, the latest of version of kubernetes-client and
knative-client are used.

Resolves https://github.com/ballerinax/kubernetes/issues/517

Codecov Report

Merging #518 into master will increase coverage by 1.32%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master     #518      +/-   ##
============================================
+ Coverage     64.66%   65.98%   +1.32%
+ Complexity      950      919      -31
============================================
  Files            98       94       -4
  Lines          4862     4707     -155
  Branches        503      488      -15
============================================
- Hits           3144     3106      -38
+ Misses         1497     1380     -117
  Partials        221      221

Impacted Files
Coverage Δ
Complexity Δ

...org/ballerinax/kubernetes/handlers/HPAHandler.java
91.83% <100.00%> (+2.36%)
8.00 <1.00> (+1.00)

...ernetes/handlers/PersistentVolumeClaimHandler.java
91.89% <100.00%> (+0.22%)
5.00 <0.00> (ø)

...inax/kubernetes/handlers/ResourceQuotaHandler.java
89.47% <100.00%> (+1.23%)
7.00 <1.00> (ø)

...rnetes/handlers/knative/KnativeServiceHandler.java
66.88% <100.00%> (+0.43%)
13.00 <0.00> (ø)

.../kubernetes/models/PersistentVolumeClaimModel.java
100.00% <100.00%> (ø)
11.00 <4.00> (+2.00)

...tes/processors/VolumeClaimAnnotationProcessor.java
90.19% <100.00%> (+0.61%)
12.00 <0.00> (ø)

...erinax/kubernetes/models/knative/ServiceModel.java
45.31% <0.00%> (+0.78%)
30.00% <0.00%> (+1.00%)

...erinax/kubernetes/models/knative/KnativeModel.java
30.00% <0.00%> (+10.00%)
5.00% <0.00%> (+2.00%)

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 d4f597d...fd9c254. Read the comment docs.


[BUG] After running on monitor with different resolution, configuration window is unusable

After running on monitor #1 with resolution 3840x2160, and then running on monitor #2 at 2560x1440, the settings window is not completely usable.

Hi, @fre-sch, please use the new Windowed Mode feature.

Hi, @fre-sch, please use the new Windowed Mode feature.

As you can see in the screenshot, the tabs aren't reachable. And since the tabs aren't reachable, neither is the checkbox for switching to window mode.

Hi @fre-sch just delete the Settings.json file to reset everything.

Where is this Settings.json file located? Is it this one New World - Aeternum Cartogram\AeternumCartogram_Data\StreamingAssets\Settings.json?
I realize this is most likely a very rare issue, possibly one only I have. I sometimes play on my desk, sometimes I play on a TV. So in the end, no matter how I position the minimap and configuration window, it'll never be right for one of them.  There being a Settings.json, I can switch those out depending on the display I play on. I know Cartogram already supports profiles, but that's just for the game position recognition. Without access to the main configuration window, profiles wouldn't help in this case because they're potentially offscreen.
If this was something I need to fix, I guess I would implement some checks on startup:

Is the configured size (map or configuration window) larger than the screen area? Clamp it, probably even clamp to 50% of area.
Is the configured position (just configuration window) outside the screen area? Clamp it to center of screen area.
possibly save and restore position and size of minimap and configuration window per display hardware identifier.
include map and configuration window sizes in profiles, and have a profile switch keybinding
make configuration window draggable by clicking anywhere, not just the dedicated button in its titlebar

Here's a batch script to enable applying versions of Settings.json. One version of this batch file per Settings.json must be created. INSTALLATION_DIRECTORY must be replaced with actual absolute path to directory of "New World - Aeternum Cartogram".

In AeternumCartogram_Data\StreamingAssets\ create Settings.1.json or create a copy of Settings.json and rename to Settings.1.json.
Create a batch file Start Settings 1.bat with contents below inside New World - Aeternum Cartogram directory to apply Settings.1.json
Starting Start Settings 1.bat will first apply Settings.1.json, then start AeternumCartogram.
Repeat above steps as necessary, by creating additional Settings.X.json files and additional Start Settings X.bat files.

@echo off
cd "INSTALLATION_DIRECTORY"
del "AeternumCartogram_Data\StreamingAssets\Settings.json"
mklink /H "AeternumCartogram_Data\StreamingAssets\Settings.json" "AeternumCartogram_Data\StreamingAssets\Settings.1.json"
start AeternumCartogram.exe


Restore PROD env mapping via plugin

Description
https://github.com/RedHatInsights/acs-ui/pull/72 has apparently dropped a definition of the PROD env var that tells ACS console UI plugin to talk to the prod fleet manager instance instead of the default stage one.
This PR attempts to restore previous behavior in the new, appropriate location.
Checklist (Definition of Done)

[ ] ~Unit and integration tests added~
[ ] Added test description under Test manual
[ ] ~Documentation added if necessary~
[ ] CI and all relevant tests are passing
[ ] Add the ticket number to the PR title if available, i.e. ROX-12345: ...
[x] Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.

Test manual
TODO: Add manual testing efforts
# To run tests locally run:
npm run test

Codecov Report
Patch and project coverage have no change.

Comparison is base (22cdfc7) 11.89% compared to head (c093e28) 11.89%.

:exclamation: Current head c093e28 differs from pull request most recent head 302cb71. Consider uploading reports for the commit 302cb71 to get more accurate results

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #76   +/-   ##
=======================================
  Coverage   11.89%   11.89%
=======================================
  Files          26       26
  Lines         395      395
  Branches       84       84
=======================================
  Hits           47       47
  Misses        322      322
  Partials       26       26

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Internal ticket: https://issues.redhat.com/browse/ROX-16460


Value in [users.name] cannot be blank. Example from official docs does not work.

Issue Summary
I try to create a new post on my blog using node.js
To Reproduce
Here is my code it works, but request gives and error
const GhostAdminAPI = require('@tryghost/admin-api');
const path = require('path');

// Your API config
const api = new GhostAdminAPI({
    url: 'https://citvy.com/blog',
    version: "v3",
    key: 'ADMIN API KEY FROM GHOST PANEL'
});

// Your content
let html = '
My test post content.

My awesome photo

';

return api.posts
    .add(
        { title: 'My Test Post', html },
        { source: 'html' },
        { excerpt: "👋 Welcome, it's great to have you here." },
        { feature_image: "https://static.ghost.org/v3.0.0/images/welcome-to-ghost.png" }
    )
    .then(res => console.log(JSON.stringify(res)))
    .catch(err => console.log(err));

The error:

The example I took exactly from here: https://ghost.org/docs/api/v2/javascript/admin/#publishing-example
Technical details:

Ghost Version: latest (current one), update today
Node Version: v12
Browser/OS: Ghost installed on ubuntu 18.04
Database: default one (no idea), I installed compiled version of Ghost blog via npm

fuck, this is how you must have shown the example in docs:
    .add(
        {
            title: 'My Test Post', html,
            excerpt: "👋 Welcome, it's great to have you here.",
            feature_image: "https://static.ghost.org/v3.0.0/images/welcome-to-ghost.png",
            authors: [
                {
                    id: '5951f5fca366002ebd5dbef7',
                    name: 'Rupesh Narayan',
                    slug: 'rupesh-narayan',
                    email<EMAIL_ADDRESS>                    profile_image: 'https://citvy.com/blog/content/images/2020/07/cG5n.png',
                    cover_image: 'https://citvy.com/blog/content/images/2020/07/Crummock-Water-Road-Lake-District.jpg',
                    bio: 'Технический писатель',
                    website: null,
                    location: 'Киев',
                    facebook: 'citvy',
                    twitter: '@lampgram',
                    accessibility: '{"nightShift":true,"whatsNew":{"lastSeenDate":"2020-06-29T16:11:36.000+00:00"}}',
                    status: 'active',
                    meta_title: null,
                    meta_description: null,
                    tour: '["getting-started","using-the-editor","featured-post","upload-a-theme"]',
                    last_seen: '2020-08-07T21:44:58.000Z',
                    created_at: '2020-04-04T13:57:25.000Z',
                    updated_at: '2020-08-07T21:44:58.000Z',
                    roles: [
                        {
                            "id": "5ddc9063c35e7700383b27e3",
                            "name": "Author",
                            "description": "Authors",
                            "created_at": "2019-11-26T02:39:31.000Z",
                            "updated_at": "2019-11-26T02:39:31.000Z"
                        }
                    ],
                    url: 'https://citvy.com/blog/author/rupesh-narayan/'
                }
            ],
            primary_author: {
                id: '5951f5fca366002ebd5dbef7',
                name: 'Rupesh Narayan',
                slug: 'rupesh-narayan',
                email<EMAIL_ADDRESS>                profile_image: 'https://citvy.com/blog/content/images/2020/07/cG5n.png',
                cover_image: 'https://citvy.com/blog/content/images/2020/07/Crummock-Water-Road-Lake-District.jpg',
                bio: 'Технический писатель',
                website: null,
                location: 'Киев',
                facebook: 'citvy',
                twitter: '@lampgram',
                accessibility: '{"nightShift":true,"whatsNew":{"lastSeenDate":"2020-06-29T16:11:36.000+00:00"}}',
                status: 'active',
                meta_title: null,
                meta_description: null,
                tour: '["getting-started","using-the-editor","featured-post","upload-a-theme"]',
                last_seen: '2020-08-07T21:44:58.000Z',
                created_at: '2020-04-04T13:57:25.000Z',
                updated_at: '2020-08-07T21:44:58.000Z',
                roles: [
                    {
                        "id": "5ddc9063c35e7700383b27e3",
                        "name": "Author",
                        "description": "Authors",
                        "created_at": "2019-11-26T02:39:31.000Z",
                        "updated_at": "2019-11-26T02:39:31.000Z"
                    }
                ],
                url: 'https://citvy.com/blog/author/rupesh-narayan/'
            }
        },
        { source: 'html' }
    )

I think we've fixed whatever issue there was with the docs here, as the example on https://ghost.org/docs/admin-api/javascript/ works fine right now 🙂


Does not run on latest firmware

I can compile the app fine, but it will not run on the latest firmware version, 86.1

Damn, I had similar issue with flizzer tracker. Will check and try to fix soon

I checked on latest dev OFW commit, it works. Please check if you have most recent video player source code version, that's most likely the reason why it does not run for you.

Thank you.


Activating a node driver or cluster driver does not automatically deselect itself after the state changes to Active

Is your feature request related to a problem? Please describe.

When a user goes to activate a node driver that is in a state of Inactive by default, that works as expected. However, after the node driver state changes to Active, that node driver is still selected. To illustrate this behavior, see below:

Seems a bit counterintuitive as from a user's perspective, I would expect the UI to automatically deselect the now active node driver.
Describe the solution you'd like

After a node driver or cluster driver goes from a state of Inactive to Active, the UI should automatically deselect that driver as it is now Active.

This is another page that we should port from Ember to Vue, so we should fix this as part of that new ticket.
@gaktive to file a new one.


SIM300: fix and check are not aligned

using the latest 0.3.2 together with precommit
  - repo: https://github.com/astral-sh/ruff-pre-commit
    rev: v0.3.2
    hooks:
      - id: ruff
        args: ["--fix"]
      - id: ruff-format
      - id: ruff
        args: ["--preview"]

and the code
def test_cloud_compute_binding():
    cloud_compute.ENABLE_MULTIPLE_WORKS_IN_NON_DEFAULT_CONTAINER = True

    assert cloud_compute._CLOUD_COMPUTE_STORE == {}
    flow = FlowCC()
    assert len(cloud_compute._CLOUD_COMPUTE_STORE) == 2

fixed by the first run is not accepted by the last check
ruff.....................................................................Failed
- hook id: ruff
- files were modified by this hook

Found 1 error (1 fixed, 0 remaining).

ruff-format..............................................................Passed
ruff.....................................................................Failed
- hook id: ruff
- exit code: 1

tests/tests_app/core/test_lightning_app.py:1119:12: SIM300 [*] Yoda conditions are discouraged, use `cloud_compute._CLOUD_COMPUTE_STORE == {}` instead
     |
1117 |     cloud_compute.ENABLE_MULTIPLE_WORKS_IN_NON_DEFAULT_CONTAINER = True
1118 |
1119 |     assert {} == cloud_compute._CLOUD_COMPUTE_STORE
     |            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ SIM300
1120 |     flow = FlowCC()
1121 |     assert len(cloud_compute._CLOUD_COMPUTE_STORE) == 2
     |
     = help: Replace Yoda condition with `cloud_compute._CLOUD_COMPUTE_STORE == {}`

Found 1 error.
[*] 1 fixable with the `--fix` option.

It looks like you're using --preview in one invocation but not the other, so this may be expected. Can you try using --preview in both?

Ok, I was aware of preview for formatting to apply some future staff, but though that preview for check is just rich/verbose...


ContinuityAnalyzer class in generator mode may use an algorithm that is too simple

When the ContinuityAnalyzer class is configured to run in generator mode, it uses a simple approach:  it clears all discontinuities and always increases the CC count unless the current packet doesn't have a payload.  This will likely work fine the majority of the time.  But, let's consider a potential case with the ContinuityAnalyzer used in generator mode with the rmsplice plug-in.  Let's say that there is one splice event sequence in an input stream, corresponding to a commercial break.  So, if the fixcc option is enabled, what one would expect the rmsplice plug-in to do in this case is to output all the packets, exactly as they appear in the input stream, until it hits the splice out event.  Then it would drop all packets until getting a splice in command, at which point it would start outputting packets again, but with the CC adjusted appropriately and also time stamps adjusted appropriately if the plug-in has been configured to do so.
However, the expected behavior is not guaranteed to occur due to the way the ContinuityAnalyzer works in generator mode.  Just considering all the packets prior to the splice out command, if any of these packets have the discontinuity indicator turned on, this will be lost.  Further, if there are any duplicate packets, that is, successive packets with the same content and with the CC the same value, this will also be lost, and that's perhaps a more significant issue.
After the splice, there is no choice but to adjust the CC (if fixcc is enabled), but this can be done in a fashion that respects both the discontinuity indicator and duplicate packets.  Let's say that, in generator mode, the ContinuityAnalyzer class did not reset the discontinuity indicator.  In that case, after the splice, the first packet for each monitored PID could have its discontinuity indicator turned on by the rmsplice plug-in.  Then, when the ContinuityAnalyzer sees any packets with the indicator turned on, it would act as a reset, resetting the current fixcc value to that of the packet with the indicator turned on.
To handle duplicate packets, it would be necessary to keep track of the last packet for each PID.  Then, when in generator mode, if it sees that the CC value is the same for the current packet as that of the last packet (the original version of the packet, not the version with its CC value massaged), it would compare the memory of each packet, and if they are the same, it would maintain this by setting the CC value of the current packet to be the same as used for the last packet.  Further, any time a discontinuity packet is observed would reset the duplicate packet checking state.
Anyway, I think the approach that I suggested would properly address the possibility of expected discontinuities and duplicates when the ContinuityAnalyzer class is in generator mode.

Thanks for reporting this. There are a few more corner cases I am thinking about. I will fix this.

Fixed in commit b53e6c751e237040eb54d013fc5ed297fa1dd98a


Support for unescaped newlines

We are migrating our web app from Backbone to React, and hoping to replace marked with react-markedown. The problem it, we need to convert single newlines to broken newlines (
), and I can't seem to find a way to do that in react-markdown.
This is the option we set in marked to enable this functionality: https://github.com/chjj/marked#breaks
We need this support for backwards compatibility in our app, as well as to follow the generally accepted Github style of markdown which is fairly well known to our users. From what I can tell, because react-markdown uses CommonMark, this is not something available as an option.
Any thoughts?

I also have similar problem. It's not convenient to use
 in each place I want to break line.

Have you tried use Hardbreak as prop? I had a similar issue  using Softbreak as the  that creates comes with a margin-top and margin-bottom

This has changed a bit since v3 was released. Please see https://github.com/rexxars/react-markdown/issues/105#issuecomment-346103734


feat: add validate partial command

Description
** Describe what, why and how of the changes clearly and concisely. Add any additional useful context or info, as necessary. **
Todos
** List any todo items necessary before merging, if any. Delete if none. **

[ ] Sample todo item 1
[ ] Sample todo item 2

Tasks
** Link to task(s) or issue(s) which this PR corresponds to. Example: KNO-54 **
Screenshots
** Attach any screenshots or recordings to visually illustrate the changes, as necessary. Delete if not relevant. **

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#388  👈
#387
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @connorlindsey and the rest of your teammates on  Graphite

Merge activity

Jul 30, 1:15 PM EDT: @connorlindsey started a stack merge that includes this pull request via Graphite.


Modal not working when ModalContent is not implemented

When I have a component which does not implement the interface ModalContent, then the ModalDialog cannot send the parameters to the component.
It should be optional.

It could nice to pass the height and width also. Or just specify a css Class for it. Tks.

@rafaelzr this will be treated in the issue #5


[BUG] Home path duplicated on Windows

Please confirm

[x] I am running the latest version of this plugin

Describe the bug
telekasten is looking for daily folder in Home/Home/daily instead of Home/daily
To Reproduce
Steps to reproduce the behavior:

Start nvim

Require Telekasten setup using example in README only changing home directory:
local home = '/Users/[user]/zettelkasten'

Run Telekasten new_note or search_notes

Telekasten says daily directory does not exist and offers to make it in wrong location (see screenshot).

Expected behavior
Telekasten detects existing daily directory or offers to create it in correct location
Screenshots

Operating system (please complete the following information):

OS: Windows 10

Could this be related to #71 an the fix in #76?
Could you try if setting you directory with \Users\[user]\zettelkasten works?

Also, if you accept the creation of the daily dir at that place, does it prompts for weeklies, templates and images as well?

Could you try this fix? https://github.com/lambtho12/telekasten.nvim/tree/fixPath
If it works, I will merge it asap.

Could you try this fix? https://github.com/lambtho12/telekasten.nvim/tree/fixPath If it works, I will merge it asap.

Unfortunately, I still get the same error.

(there is now only one slash between the duplicated home paths now though)

Also, if you accept the creation of the daily dir at that place, does it prompts for weeklies, templates and images as well?

It gives an error when trying to create the daily folder.

Could this be related to #71 an the fix in #76?
Could you try if setting you directory with \Users\[user]\zettelkasten works? It seems like Plenary.Path could be the issue here. Unfortunately I do not have a Windows machine to test it.

Here's the config I currently have; I think the paths should be set up correctly?
  use {'renerocksai/telekasten.nvim',
  disable = false, --https://github.com/renerocksai/telekasten.nvim/issues/106
  config = function() require('telekasten').setup({
     home = '\\Users\\[user]\\zettelkasten',
     dailies = '\\Users\\[user]\\zettelkasten\\daily' }) end}

What about the following
use {'renerocksai/telekasten.nvim',
  disable = false, --https://github.com/renerocksai/telekasten.nvim/issues/106
  config = function() require('telekasten').setup({
  home = '/Users/[user]/zettelkasten',
  dailies = '/Users/[user]/zettelkasten/daily' }) end}

It looks like caused by this piece of code in telekasten.lua:
local function make_config_path_absolute(path)
    local ret = path
    if not (Path:new(path):is_absolute()) and path ~= nil then
        ret = M.Cfg.home .. "/" .. path
    end
    return ret
end

If you look at plenary/path.lua, you will see:
local is_absolute = function(filename, sep)
  if sep == "\\" then
    return string.match(filename, "^[A-Z]:\\.*$")
  end
  return string.sub(filename, 1, 1) == sep
end

On windows, is_absolute() will only return true if the path starts with [drive]:\\.
Therefore, I suggest to not pass in a weird path like Users\[user]\zettelkasten. Pass in the real Windows path. Problem #71 probably needs a revisit.

@yantongl what would be the best solution in your opinion?
Force windows user to specify their home as C:\\.. ? (but then we will have issues with lua and the \stuff I guess.

I am new to nvim plugin development. My gut feeling tells me that we should specify the home as C:\\... on Windows since Plenary seems to expect a Windows path. I could help test the problem on Windows, but I need to understand the previous problems first

I am quite busy atm. But I should have some time next week to finally sort all this out.

thank you! I also need to go to bed now, it is late midnight here. Will follow up tomorrow.

I found two options working for me:

the simplest one:
yes, add C:\\ at path start so that it looks like this:
C:\\Users/%name%/zettelkasten
(you may put \\ everywhere or not, main thing - C:\\ part)
in this case the paths look like mess but works for me.

kind of more correct and cross-platform:
path = vim.fn.expand('~/zettelkasten')
but then you have to do
string.gsub(path, '\\', '\\\\')
that also messy but works too.

tested these 2 variants only within my zettelkasten config,
and didn't change any env vars or whatever outside the plugin


Proposal: Extend authorization scope with the image tag pattern

Problem description
Nowadays GitOps approach become more and more popular. We run on continuous integration pipelines which as a result push docker image into the registry. On the other side, we have processes like flux image updater, which listens for registry changes ( in particular it looks for image tag patterns ) and based on that updates manifests which furthermore results in production/staging/development server update.
Currently, it's not possible to create users with restricted access only to some tag pattern - due to that it's hard to accomplish flow that is fully safe. Let me give some example:
We have repository example-org/backend and we have 2 envs, production and staging. Production is expecting (fluxcd image updater) the following image pattern prod-* (ex. example-orb/backend:prod-132) on registry in order to trigger build and staging is expecting staging-*. Now we have a registry user called deployer-staging which should be able only to push tags that trigger staging - currently, it's not possible and that user would be able to do anything if it have write access to that repository.
Proposition
My proposition is to extend functionality related with scope and leave the option to specify as well tag pattern for a given user

I am curious why you have prod and staging in the same repository? The permissions model is per repository, and it will be very difficult to change. It was designed as a similar model to git, where the repository is basically the permissions object, and per branch permissions are difficult (with a registry branches don't really exist so this is not really possible).

I am curious why you have prod and staging in the same repository? The permissions model is per repository, and it will be very difficult to change. It was designed as a similar model to git, where the repository is basically the permissions object, and per branch permissions are difficult (with a registry branches don't really exist so this is not really possible).

I see your point - I don't like much the approach with separate repositories because you need to manage at least 2 repositories. Let's say that we wanna as well protect our staging environment. It means that we need to have the following repos:
example-orb/backend-prod
example-orb/backend-staging
example-orb/backend
Moreover, if your organization has multiple repositories you end up with the messy solution in my opinion.
I know that with tools like terraform it's possible more efficiently manage that scenario but after all under the hood you have a ton of repos.
If it would be possible to specify access based on the image tag it will result in a reduced number of repositories - only one for a given project

Has anyone figured out a solution to this since its original posting?
I opened a similar question below and just found this open issue.
https://github.com/distribution/distribution/discussions/4279

As I said in the question, authz based on tags rather than repos offers very little security, and risks users thinking something is protected when it is not. When a client pulls a layer (blob) it is not possible to know how they obtained the manifest. Allowing a user access to only one tag still must allow them access to every layer in the repo.

Its more for pushing images.
If we could make roles based on tags it would be possible to create 2 sets: one for dev and second for prod.
Most ci/CD platforms allow to define env vars only for given protected branch


docs: add gpg-tui to the "apps using tui" list

Description
Add gpg-tui to the apps-using-tui list.

Nice 👏


Optionally load client ID, secret and domain from environment

We have multiple environments that we keep in sync with database backups cloned between them. Obviously this confused the Auth0 plugin as it doesn't have the right credentials any more.
Loading the credentials from the environment in a 12-factor app style would make this a lot easier. Perhaps if the values are blank in the database they could be loaded from the env? Another issue here is the user migration token, which could perhaps be generated in a more stable fashion so it doesn't need to be stored in the database?

@Floppy - Thank you for the suggestion on this. We were considering something like this for sensitive data storage like the ones you mentioned. WordPress convention is to define a constant in wp-config.php, rather than a .env file. Would that work for your purposes? Then we don't have to load a separate env-parsing library.

Tracking progress in the add-env-settings-support

Yeah, it's probably best to stick to the wordpress standard. We can always use an env loader inside our wp-config.php to do the next step.

Fixed in #509, merged into dev. Release coming soon!


fix: update dd trace to 4.20 (nice)

Description

Updated dd-trace dependency to ^4.20. We see a lot of spam errors that are related to how Next.js middleware works internally. Should be fixed after dd-trace update, since they fixed the issue in issue linked below.

Related Issue
https://github.com/DataDog/dd-trace-js/issues/3682

How Has This Been Tested?
npm run test
Checklist

This is a breaking change:

[ ] Yes
[x] No

Will this release a new version:

[x] Yes
[ ] No

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Is storing circuits in the circuit handler thread safe?

The singleton circuit handler stores the circuits in a hashset, shouldn't we use a thread safe collection instead?
https://docs.microsoft.com/en-us/aspnet/core/blazor/fundamentals/signalr?view=aspnetcore-6.0#blazor-server-circuit-handler

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

ID: 0969556b-b77e-bdb8-8e20-fd6971be0c25
Version Independent ID: d17e4c28-ea82-0dd8-295d-19f6ada147ea
Content: ASP.NET Core Blazor SignalR guidance
Content Source: aspnetcore/blazor/fundamentals/signalr.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @derth ... This came in directly from the product unit on ...
https://github.com/dotnet/AspNetCore.Docs/pull/16702
You can ask the product unit at ...
https://github.com/dotnet/aspnetcore/issues
If you do, you can let them know that Pranav (not on their team any longer) added the code on that PR ☝ back in 2020. You can give them this link ...
https://github.com/dotnet/AspNetCore.Docs/pull/16702

Also, please add ...
cc: @guardrex https://github.com/dotnet/AspNetCore.Docs/issues/26740

... to the bottom of your opening comment so that I follow along. I might re-open this for doc work depending on what they say.


Question: system_api.c functions

I am porting Wakaama to a new target and wondering about the purpose/intent of the following functions located in system_api.c when LWM2M_EMBEDDED_MODE is defined.
static void prv_value_change(void* context,
                             const char* uriPath,
                             const char * value,
                             size_t valueLength)
{
    lwm2m_uri_t uri;
    if (lwm2m_stringToUri(uriPath, strlen(uriPath), &uri))
    {
        handle_value_changed(context, &uri, value, valueLength);
    }
}

void init_value_change(lwm2m_context_t * lwm2m)
{
    system_setValueChangedHandler(lwm2m, prv_value_change);
}

I actually had LWM2M_EMBEDDED_MODE not defined and my system was working OK. So it appears these definitions may be optional?

I had not noticed that before, and have Wakaama working on our device using our own client code. It looks like the intent is to register a callback that is called when something changes. I would definitely consider it optional.

@JRubis, could we close this issue now ?


simulation: Recamán's Sequence

Proposed Simulation Name: Recamán's Sequence
https://en.wikipedia.org/wiki/Recamán's_sequence
Category Proposed: Mathematics
Additional points/links:

I would like to  go ahead with this as a part of gssoc '21

@soukarsha122 sure! Go ahead :)

Sir,
It will be very kind of you if you clarify whether I have been assigned
this issue as part of gssoc 21.
On Thu, 4 Mar 2021, 14:40 Saksham Arora<EMAIL_ADDRESS>wrote:

@soukarsha122 https://github.com/soukarsha122 sure! Go ahead :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cod-ed/simulate/issues/131#issuecomment-790456696,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASXEMYXF6LNGJIMNQM7A3ELTB5FBFANCNFSM4SLQ562Q
.

@yashugarg I am a gssoc participant 2021.Can I contribute to this issue

@yashugarg I am a gssoc participant 2021.Can I contribute to this issue

Hey please go ahead @Sibasish-Padhy


Still having trouble with internally promiscuous nodes.

See https://github.com/NCATSTranslator/Feedback/issues/427
We have two rules
(Disease)<-[treats]-Chem1<-[decreased]-(Gene)-[decreased]->(chem2)
And a similar one where Gene is a Pathway and the predicate is has_input.
Both rules are producing large numbers of results for the same Gene/Pathways.  So for instance, For Gene=CMAP there are about 20 answers, and they are among the highest ranked.  I have a promiscuity filter ready to go in aragorn, so I will try it out with this result.

Internal promiscuity addressed in Fugu.   Reopen if necessary.


Add uptime command to ci

Fixed in https://github.com/mithro/HDMI2USB-litex-firmware/commit/3892837d63776d06447e125855e082df8c8fb7d5


logs behavior seems odd

Hello guys
I am trying to get the logs from the containers and put them in a queue, but the logs() and streaming_logs() act strange
so right now we have shell scripts that basically do this
curl -s --no-buffer -XGET --unix-socket /var/run/docker.sock "http:/containers/CONTINER_ID/logs?stdout=1&tail=1&follow=1"
so we get one line at a time, that line goes into the queue
with the ruby api we are unable to replicate this behavior
we tried:
container.streaming_logs(stdout: true, tail: 1, follow: true) { |stream, chunk| enqueue_log("#{container_name}:  #{chunk}")  }
but if nothing changes it keeps getting the same message (the last one) over and over.
and also later on we get the Docker::Error::TimeoutError, we cannot increase the timeout as this runs continuously
any ideas about how to achieve that?

Probably related to https://github.com/swipely/docker-api/pull/522

Pretty sure this down to the difference in the format of the streamed logs depending on whether the container is configured as having a TTY or not.  The value of the tty: true/false option passed to #logs/#streaming_logs must match the value of the c.info["Config"]["Tty"] container variable, otherwise all heck breaks loose -- the wrong parser is invoked, and either no logs come through, or all logs come through in one giant string.
It is impossible to overstate the amount of swearing I have done in the last hour or so as I figured that out.