Basic Javascript in beta- correct code won't pass without refresh on some challenges

Challenge passing-values-to-functions-with-arguments has an issue.
User Agent is:  Chrome/58.0.3029.110
Please describe how to reproduce this issue, and include links to screenshots if possible.
// Example
function ourFunctionWithArgs(a, b) {
  console.log(a - b);
}
ourFunctionWithArgs(10, 5); // Outputs 5

// Only change code below this line.
function functionWithArgs(par1, par2) {
  console.log(par1 + par2);
}

functionWithArgs(1, 2);

This challenge as well as others (shopping list, write reusable javascript with functions, and a few other earlier ones I can't specifically name) all have an issue where I write the correct answer and try to run, and the tests all fail, regardless of it outputting the correct answer from my code. If I reload the page and then, using the code it saved for me, run the tests, it passes and goes on. This might be something that's already been solved but I didn't see anything specifically about this so I wanted to share in case it was an issue for anyone else.
Using Chrome 58.0.3029.110 (64-bit), Windows 10 creator update, on an HP laptop. Happy to give any other details needed. I've attached a gif I made showing the issue.

@lindakatcodes thanks for the issue. That is quite odd. I'm unfortunately unable to reproduce this bug.
cc/ @freeCodeCamp/moderators anyone else can replicate this? Or know if this is an existing issue?

Using the link provided above, I run the code and passed.
Ubuntu 17.04, Chromium 56.0.2924.76.
I was wondering why the output of my console is just "//running test" and "//tests completed". Your output has more specific tests output which can be seen from your gif.

I can replicate it. @erictleung try doing the challenge before this one and then this one.

Having the same issue with almost every other challenge.
Using Chrome 58.0.3029.110 (64-bit), Ubuntu 16.04.2 LTS , on a Lenovo laptop.
My code is fine, refreshing the challenge page passes the tests.  It started for me with "Divide one Decimal by Another with JavaScript" - #14635

Okay thanks... Will move to a PC
-----Original Message-----
From: "uijaz"<EMAIL_ADDRESS>Sent: 28/05/2017 12:11
To: "freeCodeCamp/freeCodeCamp"<EMAIL_ADDRESS>Cc: "Subscribed"<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Basic Javascript in beta- correctcode won't pass without refresh on some challenges (#15024)
Having the same issue with almost every other challenge.
Using Chrome 58.0.3029.110 (64-bit), Ubuntu 16.04.2 LTS , on a Lenovo laptop.
My code is fine, refreshing the challenge page passes the tests. It started for me with "Divide one Decimal by Another with JavaScript" - #14635
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi @all, Is it taken by anyone. Can i take up to fix if anything that i can help with ?

@valishah feel free to tackle the issue! I personally don't have the knowledge to solve this, but you can take a look at the comment above for a starting place.

Having the same issue as mentioned by @uijaz but on a mac using chrome 58.0.3029.110 (64-bit)

I can help out with this issue if @valishah can't figure it out.

I'd say go for it @CodingPower472. It's been a bit of time.

why are you sending me emails for luke @codecamp.com????? why
On Jul 3, 2017 1:00 PM, "Dylan"<EMAIL_ADDRESS>wrote:

I'd say go for it @CodingPower472 https://github.com/codingpower472.
It's been a bit of time.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/freeCodeCamp/freeCodeCamp/issues/15024#issuecomment-312714804,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AM4VTDVMKsFF7iD84BMS8MIDw23B6K5xks5sKTpggaJpZM4NklPP
.

@pigtails21
looks like you may have accidentally subscribed to all notifications for the FreeCodeCamp repository. To stop receiving notifications please visit the subscriptions page and select "Not watching". Additionally, you can visit the GitHub Help page on managing notification delivery methods for more help.
We are sorry for your inconvenience!

Unable to reproduce.

Google Chrome is up to date
Version 63.0.3239.84 (Official Build) (64-bit)

I'm unable to reproduce as well. Using Chrome (62.0.x). This behavior also appears in #14211

Unable to reproduce using Google Chrome Version 62.0.3202.94 (Official Build) (64-bit)

Thanks everyone, I am closing this as not reproducible any more. Please log a fresh issue, if you happen to come across this.


Patch release-0.8: Remove image GC.

Fix #3617,#3611, and #3393.

cc/ @brendandburns

Since it is a patch to an official release, I am going to run e2e test before merge. Will do a self-merge for this one.

sgtm.
thanks

e2e passed:
2015/01/20 15:43:40 Passed tests: basic.sh[1/1] certs.sh[1/1] goe2e.sh[1/1] guestbook.sh[1/1] liveness.sh[1/1] monitoring.sh[1/1] pd.sh[1/1] private.sh[1/1] services.sh[1/1] update.sh[1/1]
2015/01/20 15:43:40 Flaky tests:
2015/01/20 15:43:40 Failed tests:
2015/01/20 15:43:40 Success!


[IOS/Android] Changing camera on the Pose Detection graph a few times causes a crash - stop start of graph issue

System information
Platform and Distribution: IOS 14 - Tested on iPhone 7 and current Gen iPad. Android 10 on Sony Xperia XZ3
MediaPipeUnityPlugin version or commit id: a754416
Android NDK version (if the target platform is Android): r21d bundled with Unity 2021.1.17f1
Xcode version (if the target platform is iOS): 12.5.1 (12E507)
Describe the current behavior
Using just the Pose tracking graph in the Desktop Demo build to run on IOS/Android in builds we are noticing consistently the app is prone to crashing when changing the camera device using the dropdown. Xcode/Logcat give us no crash logs and don't even register it as a crash. To the logs it just thinks the app is still running but it is frozen.
I found this issue when trying to find ways to compensate for the latency that creeps in on the Pose detection graph when using the latest repo from around https://github.com/homuler/MediaPipeUnityPlugin/commit/a754416741d4a16ce8b49c2adee77196bd762a47
I also tried using this fix but it caused an occasional crash on mobile devices too https://github.com/homuler/MediaPipeUnityPlugin/issues/244#issuecomment-900315679
This is not reproducible in the Editor on Windows or mac which makes me suspect this behaviour is mobile only, as well as this I noticed most people on the github issues here aren't doing much on-device testing anyway so I would assume to most it appears that mediapipe pose detection is running fine always because it does so in the Editor, but not on device when deployed.
Describe the expected behavior
The pose detection graph should run as expected on mobile and run without any crashing like it does in Editor.
Steps to reproduce the issue

Build mediapipe for android on windows docker and build mediapipe for ios on Mac

Build and run the Desktopdemo scene on IOS iphone or an Android phone, choose the pose detection graph, switch between front and back camera at least 10-15 times to see a crash.

This crash can also be reproduced if you call the stop / start graph functions yourself programmatically - I had this running in an invokeRepeating  function every 30 seconds or so which is where I noticed that crash.

I am happy to share the example project we are using privately with you if this helps.

Close this issue for lack of activities.

Apologies, I am looking into this issue now - we are using Mediapipe 0.8.4, is there a way for us to backport this patch there or will we need to move ahead into using Mediapipe 0.8.8?

I recommend you use the latest version, but if you want to use an older version, apply a patch as follows:

Create a patch file and place it under third_party/.
Update WORKSPACE (append the patch file path under the below line).
https://github.com/homuler/MediaPipeUnityPlugin/blob/4d90ac44627dd0996792e56fdc0817a7b15ada4a/WORKSPACE#L60

See also https://github.com/homuler/MediaPipeUnityPlugin/issues/242#issuecomment-900249401.


[youtube] Cannot identify player

tony@Macintosh:~/Music$ youtube-dl -U
Updating to version 2015.07.28 ...
Updated youtube-dl. Restart youtube-dl to use the new version.
tony@Macintosh:~/Music$ youtube-dl HFWKJ2FUiAQ
[youtube] HFWKJ2FUiAQ: Downloading webpage
[youtube] HFWKJ2FUiAQ: Downloading video info webpage
[youtube] HFWKJ2FUiAQ: Extracting video information
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 700, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 592, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfliLjLvh/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfliLjLvh/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
tony@Macintosh:~/Music$ youtube-dl https://www.youtube.com/watch?v=HFWKJ2FUiAQ
[youtube] HFWKJ2FUiAQ: Downloading webpage
[youtube] HFWKJ2FUiAQ: Downloading video info webpage
[youtube] HFWKJ2FUiAQ: Extracting video information
[youtube] HFWKJ2FUiAQ: Downloading js player en_US-vflGx3XCd
[youtube] HFWKJ2FUiAQ: Downloading DASH manifest
[download] Destination: This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f135.mp4
[download] 100% of 12.49MiB in 00:08
[download] Destination: This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f141.m4a
[download] 100% of 6.35MiB in 00:04
[ffmpeg] Merging formats into "This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.mp4"
Deleting original file This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f135.mp4 (pass -k to keep)
Deleting original file This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f141.m4a (pass -k to keep)
tony@Macintosh:~/Music$

After this downloading the full http address for the same video worked fine.

@keevee09 use verbose mode '-v'
it worked fine to me:
youtube-dl -v HFWKJ2FUiAQ
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'HFWKJ2FUiAQ']
[debug] Encodings: locale cp1252, fs mbcs, out None, pref cp1252
[debug] youtube-dl version 2015.07.28
[debug] Python version 2.7.8 - Windows-7-6.1.7600
[debug] exe versions: ffmpeg N-74199-gb27d4fd, ffprobe N-60274-gdce9321
[debug] Proxy map: {}
[youtube] HFWKJ2FUiAQ: Downloading webpage
[youtube] HFWKJ2FUiAQ: Downloading video info webpage
[youtube] HFWKJ2FUiAQ: Extracting video information
[youtube] {43} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {18} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {5} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {36} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {17} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {135} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {244} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {134} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {243} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {133} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {242} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {160} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {140} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] {171} signature length 40.40, html5 player en_US-vflGx3XCd
[youtube] HFWKJ2FUiAQ: Downloading DASH manifest
[debug] Invoking downloader on 'https://r1---sn-cg51pauxax-4aol.googlevideo.com/videoplayback?id=1c558a2761548804&itag=135&source=youtube&requiressl=yes&pl=19&ms=au&mv=m&mn=sn-cg51pauxax-4aol&mm=31&pcm2cms=yes&ratebypass=yes&mime=video/mp4&gir=yes&clen=13093473&lmt=1417229274194488&dur=208.720&sver=3&signature=6AE521E6B3F383F48589D78F3137C2E6E865C560.7D420A71BDA0F4EACF64B71CBB1203B6B5634C63&upn=gSZtApNwZ4c&key=dg_yt0&mt=1438534298&fexp=9407538,9408497,9408710,9409171,9413148,9415089,9415365,9415485,9416126,9416729,9417206,9417911,9418204,9418427&ip=<IP_ADDRESS>&ipbits=0&expire=1438556020&sparams=ip,ipbits,expire,id,itag,source,requiressl,pl,ms,mv,mn,mm,pcm2cms,ratebypass,mime,gir,clen,lmt,dur'
[download] Destination: This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f135.mp4
[download] 100% of 12.49MiB in 04:29
[debug] Invoking downloader on 'https://r1---sn-cg51pauxax-4aol.googlevideo.com/videoplayback?id=1c558a2761548804&itag=141&source=youtube&requiressl=yes&pl=19&ms=au&mv=m&mn=sn-cg51pauxax-4aol&mm=31&pcm2cms=yes&ratebypass=yes&mime=audio/mp4&gir=yes&clen=6658191&lmt=1417229246853289&dur=208.817&sver=3&signature=7F6DDE0A7A240A9AA41841A06A552A0D8E50E940.752FDB54FB8330DAF19972665FB23B50BD83B212&upn=gSZtApNwZ4c&key=dg_yt0&mt=1438534298&fexp=9407538,9408497,9408710,9409171,9413148,9415089,9415365,9415485,9416126,9416729,9417206,9417911,9418204,9418427&ip=<IP_ADDRESS>&ipbits=0&expire=1438556020&sparams=ip,ipbits,expire,id,itag,source,requiressl,pl,ms,mv,mn,mm,pcm2cms,ratebypass,mime,gir,clen,lmt,dur'
[download] Destination: This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f141.m4a
[download] 100% of 6.35MiB in 01:58
[ffmpeg] Merging formats into "This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.mp4"
[debug] ffmpeg command line: ffmpeg -y -i 'This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f135.mp4' -i 'This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f141.m4a' -c copy -map 0:v:0 -map 1:a:0 'This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.temp.mp4'
Deleting original file This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f135.mp4 (pass -k to keep)
Deleting original file This Mortal Coil - Song To The Siren (Official Video)-HFWKJ2FUiAQ.f141.m4a (pass -k to keep)

Hi to all. I believe I have the same issue, can somebody try to reproduce it, please. Thx.
[debug] System config: []
[debug] User config: [u'--rate-limit', u'450K', u'--download-archive', u'/home/mama/.config/youtube-dl/archive', u'--prefer-ffmpeg']
[debug] Command-line args: [u'--verbose', u'-x', u'--audio-format', u'mp3', u'https://www.youtube.com/watch?v=iij6Wr8uP-w']
[debug] Encodings: locale UTF-8, fs UTF-8, out None, pref UTF-8
[debug] youtube-dl version 2015.11.02
[debug] Python version 2.7.3 - Linux-3.13.0-67-generic-x86_64-with-Ubuntu-12.04-precise
[debug] exe versions: avconv 0.8.17-4, avprobe 0.8.17-4, ffmpeg 2.5.3-, ffprobe 2.5.3-
[debug] Proxy map: {}
[youtube] iij6Wr8uP-w: Downloading webpage
[youtube] iij6Wr8uP-w: Downloading video info webpage
[youtube] iij6Wr8uP-w: Extracting video information
WARNING: unable to extract html5 player; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[youtube] {43} signature length 40.44, html5 player None
ERROR: Signature extraction failed: Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 (caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 661, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 290, in extract
    return self._real_extract(url)
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1345, in _real_extract
    encrypted_sig, video_id, player_url, age_gate)
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 827, in _decrypt_signature
    'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 (caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

I do have this issue with just a few youtube links
youtube-dl https://www.youtube.com/watch\?v\=i0A3-wc0rpw\&list\=PLKPi39tTpkdpjBVQZo5oFLWjFjlOMkd2A -v
[debug] System config: []
[debug] User config: [u'-f', u'138+141/138+140/138+139/266+141/266+140/266+139/264+141/264+140/264+139/137+141/137+140/137+139/136+141/136+140/136+139/22+141/22+140/22+139/135+141/135+140/135+139/134+141/134+140/134+139/133+141/133+140/133+139/best']
[debug] Command-line args: [u'https://www.youtube.com/watch?v=i0A3-wc0rpw&list=PLKPi39tTpkdpjBVQZo5oFLWjFjlOMkd2A', u'-v']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.11.02
[debug] Python version 2.7.10 - Darwin-15.0.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 2.8, ffprobe 2.8, rtmpdump 2.4
[debug] Proxy map: {}
[youtube:playlist] Downloading playlist PLKPi39tTpkdpjBVQZo5oFLWjFjlOMkd2A - add --no-playlist to just download video i0A3-wc0rpw
[youtube:playlist] PLKPi39tTpkdpjBVQZo5oFLWjFjlOMkd2A: Downloading webpage
[download] Downloading playlist: 24 Hours of Happy
[youtube:playlist] playlist 24 Hours of Happy: Downloading 24 videos
[download] Downloading video 1 of 24
[youtube] i0A3-wc0rpw: Downloading webpage
[youtube] i0A3-wc0rpw: Downloading video info webpage
[youtube] i0A3-wc0rpw: Extracting video information
WARNING: unable to extract html5 player; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[youtube] {22} signature length 40.44, html5 player None
ERROR: Signature extraction failed: Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 (caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 661, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 290, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1345, in _real_extract
    encrypted_sig, video_id, player_url, age_gate)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 827, in _decrypt_signature
    'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
    video_id, player_url, s
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
    raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
 (caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Here it's about the 24hrs-of-happy Playlist from Pharell Williams (can be found here https://www.youtube.com/watch?v=i0A3-wc0rpw&list=PLOOFL6Fjn-oK91hhbNXkbN186WAs-3Cjs)
I already updated to the latest version and also tried to download the video online – always the same issue. Even tried to remove the https:// from the main url, while I'm not sure if it afffects the URL within the scraped player as well.
willing to help test
Best,
Rico

Yes, I forgot to mention, it only happens (at least for now) for specific videos, some other URLs that don't work:
https://www.youtube.com/watch?v=XeckmmNPwc8
https://www.youtube.com/watch?v=H7SeOai_DOo
https://www.youtube.com/watch?v=VqOaJZdhlUM

Willing to help also however I can.

The problem is fixed in version 2015.11.10. Have a look at update instructions if you have any problem.

:+1: :bow: :-)

It works like a charm, thanks a lot!

Hi, this issue has just reappeared for me. It worked this morning, no longer now. Any clue?

youtube-dl -v HFWKJ2FUiAQ
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-v', u'HFWKJ2FUiAQ']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.02.24
[debug] Python version 2.7.10 - Darwin-16.1.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.0.2, ffprobe 3.0.2
[debug] Proxy map: {}
[youtube] HFWKJ2FUiAQ: Downloading webpage
[youtube] HFWKJ2FUiAQ: Downloading video info webpage
[youtube] HFWKJ2FUiAQ: Extracting video information
WARNING: unable to extract html5 player; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[youtube] {43} signature length 40.40, html5 player None
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/youtube.py", line 1064, in _decrypt_signature
video_id, player_url, s
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/youtube.py", line 952, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://www.youtube.com/yts/jsbin/player-vflppxuSE/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Cannot identify player u'https://www.youtube.com/yts/jsbin/player-vflppxuSE/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/youtube.py", line 1064, in _decrypt_signature
video_id, player_url, s
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/youtube.py", line 952, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://www.youtube.com/yts/jsbin/player-vflppxuSE/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/Library/Python/2.7/site-packages/youtube_dl/YoutubeDL.py", line 761, in extract_info
ie_result = ie.extract(url)
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/common.py", line 427, in extract
ie_result = self._real_extract(url)
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/youtube.py", line 1653, in _real_extract
encrypted_sig, video_id, player_url, age_gate)
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/youtube.py", line 1074, in _decrypt_signature
'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/youtube.py", line 1064, in _decrypt_signature
video_id, player_url, s
File "/Library/Python/2.7/site-packages/youtube_dl/extractor/youtube.py", line 952, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://www.youtube.com/yts/jsbin/player-vflppxuSE/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Cannot identify player u'https://www.youtube.com/yts/jsbin/player-vflppxuSE/en_US/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

@bjmrey update.


Separate concmd/convar permissions

Only check IsConCommandBlocked when validating concmds (not convars)
Convars have their own whitelist and toggle now (Open for discussion on whether to remove this and have no whitelist, or share concmd's whitelist.
Better @strict error messages

Fixes #2346

Nvm, I guess the convar whitelist is for reading convar info while the concmd whitelist is executing commands.


python3Packages.slicer: disable failing tests

Description of changes
ZHF: #172160
Disabling failing tests indicated by Hydra
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build.python310Packages.slicer

@ofborg build python310Packages.slicer

Result of nixpkgs-review pr 172260 run on x86_64-linux 1

1 package marked as broken and skipped:

python39Packages.shap

2 packages built:

python310Packages.slicer
python39Packages.slicer


ci: merge staging to master

This is an automatic PR generated by the pipeline CI/CD. This will be automatically fast-forward merged if successful.

Pipeline Attempt 546547845 - https://gitlab.com/MatrixAI/open-source/typescript-demo-lib-native/-/pipelines/546547845


License required for running this command

We have found that unless the (admin) account running this command has a SharePoint license provisioned, the command silently continues and OneDrive's are not provisioned. Adding a license to the admin account fixed our issue.
I recommend including this in the documentation.

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

ID: 6f61076b-1d49-4f87-b400-fff52d067ea8
Version Independent ID: 8173ce51-c1ef-50be-2069-1ccd3d0ab5b3
Content: Request-SPOPersonalSite (sharepoint-online)
Content Source: sharepoint/sharepoint-ps/sharepoint-online/Request-SPOPersonalSite.md
Service: sharepoint-powershell
GitHub Login: @techwriter40
Microsoft Alias: kirks

Ok, reading it again, I have found it in the text. Closing issue.


Support standard WARC file format

WARC is a standardized file format used for storing web crawl data. It's widely used for storing large scale web data collections such as CommonCrawl and ClueWeb12.
WARC ISO 28500 draft is available at: http://bibnum.bnf.fr/warc/WARC_ISO_28500_version1_latestdraft.pdf

@aecio I have a very good friend who works at Internet Archive if you want to connect. He's all about WARCing :wink:

@VickySteeves Thanks! I'll let you know if I have any questions!

Fixed in PR #117.


Wrong/outdated statements about message encoding

The last section "Note" of Send an event to your custom topic mentions that:

"Event Grid sends messages to a storage queue in a plain text format" which is not the case anymore (see steps to reproduce below). It will be good to have an explicit mention about what is the default encoding in this scenario and if there's a way to change it.
"it's not possible to configure the queue trigger for Azure Functions to accept plain text", which also seems to be outdated following the introduction of a new host.json setting extensions.queues.messageEncoding

Steps to reproduce -

Follow the instructions as described in Quickstart: Send custom events to storage queue - Event Grid, Azure CLI - Azure Event Grid
Inspect the message encoding of the items in the Storage queue (for e.g. with Storage Explorer)
See that messages pushed by EventGrid are base64 encoded

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

ID: 282ef2a3-efcd-7e70-6ba6-673e8ae17599
Version Independent ID: 8b553ac1-2d4e-3473-5da4-ad5dca2d582b
Content: Quickstart: Send custom events to storage queue - Event Grid, Azure CLI - Azure Event Grid
Content Source: articles/event-grid/custom-event-to-queue-storage.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

@mkeskes - Thank you for bringing the issue to our attention. I tested and verified that you are correct. I will update the article to reflect the behavior. Thanks.

Removed the note and checked the file in. The updated article should go live around 3 PM PST.

#please-close

Thanks for the update.
There is one question though that is still not addressed: Is there a way to set the encoding to none when publishing events from event grid to storage queues?


Add F1-F12 key support

Description
As we are short on keybinding options support the F\d-keys as well
Tests
Make sure you've run and fixed any issues with these commands:

[x] cargo fmt --all -- --check to check standard code formatting (cargo fmt --all applies these changes)
[x] cargo clippy --all --all-features -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect to check that you're using the standard code style
[ ] cargo build; cargo test --all --all-features to check that all the tests pass

oh, nice!

Found some stuff in the error handling to fix as well

@sholderbach - should we land this or should we wait for the error handling? I'm fine if we want to do error handling as a second PR

That was referring to the last two commits. Let me know if I should rebase them to a separate PR

This looks good


feat(scap-open): check btf support using scap-open

The scap-open binary is used to check if a given distro supports the modern bpf probe.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: d7ec0a4df2e952471900c8b37e2efd306bbf90ba

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, FedeDP
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP,alacuku]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Cancellation invoice: Gross amount with wrong sign

Description:
If you create a cancellation invoice, on the document the gross amount have the wrong sign (plus instead of minus). The cancellation invoice is therefore incorrect and will be rejected by the tax advisor.
Revive of this issue which "timed out": https://issues.shopware.com/issues/NEXT-30464
Environment:
SW <IP_ADDRESS>
Steps to reproduce:
Create an order
Create a storno document and check the displayed gross value.
Expected result:
The value should be negative "-".
Actual result:
The value is positive (no "-" sign).

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-37262.
[created from NEXT-37262, comment 486736]


Download not working on unix based systems

The download does not work on unix based systems as the downloaded tools (ffmpeg & youtube-dl) are not made excecutable

added unix support in version 0.1.11


Change the login method of hdpost to log in with a password instead of a cookie to prevent the login from expiring quickly.

不是，已作出修改


[Release v2.8.2] Merge into Master

Release Notes: v2.8.2 (1)
This release is due to a requirement to App Store to remove references to donations.  In it’s replacement, a reference to the Litecoin Foundation support page where the user can elect to send LTC if they so choose.

[Warmfix] Issue:146 Remove direct donation: support litecoin foundati…

Other Improvements

Fix crash in Amount formatter (#140)
[Bugfix] Renamed enum from State (#147) (#150)

Bugfixes

Renaming the enum caused a conflict with SwiftUI @State

Authors
Kerry Washington<EMAIL_ADDRESS>Mohamed Barry<EMAIL_ADDRESS>

Create a PR to merge release/v2.8.2 into develop

Create a PR to merge release/v2.8.2 into develop

@kcw-grunt you didn't create it yet! Create it now otherwise we will forget


Can't get ondragend to fire when dragging nodes from the list onto the editor

I need to detect the cancellation of dragging a new node onto the editor. I'd usually use the ondragend event for this; however, it just won't fire when using with Drawflow.
You can see it in action here: https://jsfiddle.net/wd7r81yz/1/
I've added a console log on drag start and end for the "Facebook" node in line 25 of the html. Any idea on how to get the dragend firing or why it is not firing? My only guess would be some intersection with the onmouseup event but I couldn't quite figure it out.

Nevermind, overseen something on my end. AND in the example. 🤦♂


showsMyLocationButton,showsScale property not working

   <MapView
     style={styles.map}
    onPress={(e) => this.onMapPress(e)}
   provider="google"
     zoomEnabled={true}
      scrollEnabled={true}
      showsScale={true}
      mapType='satellite'
      showsMyLocationButton={true}
      showsScale={true}
      showsCompass={true}
      loadingIndicatorColor="#228B22"
     onRegionChange={()=>this.onRegionChange()}
     region={this.state.region}
   >
   </MapView>

Same :(
Any solution?

same case showsMyLocationButton has no effect, should it put something on the map?

Yeah none of the toolBar control properties seem to work my side either.

+1 Same issue

+1

showsMyLocationButton is not implemented for google provider on iOS. You're welcome to make a PR to add the feature.

@gilbox they aren't working on Android either.

on Android: This is a stretch, but make sure the showsMyLocationButton isn't caught behind an overlaying element i.e. navigationBar. Also, the event wasn't working on my emulator for whatever reason, but worked on a device.

For the button to be visible you must set showsUserLocation={true} because the default is false.
Afterwards, please follow the issue on #1033.

Duplicate of #1033


[PDF] Using different margin bottom on first page doesn't work

Steps to reproduce
Environment:

Puppeteer version: 1.3.0
Platform / OS version: Ubuntu 14.04
Node.js version: 7.6.0

Code:
const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto('https://github.com/GoogleChrome/puppeteer', {waitUntil: 'networkidle2'});
await page.addStyleTag({
    content: '@page:first {margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px;}'
});
await page.pdf({
    path: 'test.pdf',
    format: 'A4',
    displayHeaderFooter: true,
    headerTemplate: '
HEADER
',
    footerTemplate: '
FOOTER
',
    margin: {top: '50px', right: '10px', bottom: '50px', left: '10px', }}
);
await browser.close();

Expected result:
The first page should have no margins (and therefore hide the header and footer), while all following pages should have the specified margin and display the header and footer.
Actual result:
The header is properly displayed on all pages except the first one. The footer, however, is only displayed on the last page. It seems that the margin bottom isn't applied properly.

@spiritix does the same occur if you do "save as pdf" through headful chrome? Most likely, this is a chromium issue; please report upstream to the https://crbug.com/new.

@aslushnikov I am not sure how to test this in headful mode since page.pdf() is only available in headless mode.
Protocol error (Page.printToPDF): PrintToPDF is not implemented

@spiritix
Try the following:
Print -> Destination: Save as PDF -> Margins: Custom

@hakimio This does 'work', however, the CSS seems to have no effect at all, probably because manually set margins in Chromium PDF export aren't the same as CSS margins.

@spiritix Maybe then you should add the margins for all the pages the same way? If you are using CSS for the first, use CSS for the rest. Honestly, I don't think those two options should be linked in any way.

Have you tried the preferCSSPageSize ? This allows you to specify the margin's for page in the CSS and it will take priority:
@page {
  size: A4 landscape;
  margin: 0;
}

@garygreen Has no effect, unfortunately. The result is exactly the same as with the initial configuration.

I believe it's related to this bug: https://bugs.chromium.org/p/chromium/issues/detail?id=355116

I also experience this bug (tried it with puppeteer version 1.14.0 and 1.17.0).
In the HTML page I have:
@page:first{margin:0;}@page:first {margin:4cm;}
It works as expected, as long as you do not set displayHeaderFooter to true. In that case the fist page gets no margins as expected, but the next pages have no margins on the right and bottom.
When trying to print this in the chrome browser you will not experience this problem, this makes sense because we do not get to set the displayHeaderFooter property.
HTML to reproduce this: https://jsfiddle.net/prya18Lw/

This is upstream issue.

But is it upstream? I have only been able to reproduce it with puppeteer, not just chromium.

Original issue mentioned by @destan 355116 got merged into that one.

Any updates on this?

Issue still exists, but it's in chromium. There is actual bug related to the issue.


Multiple cursors (cursor block)?

Simply allowing to insert the same thing in different places (as in multi-cursor text editors such as VS Code or Kakoune) won't be fun. However, adding the support for a cursor block seems like an... interesting idea, even though it'd make the language even more obscure (how far can we go though, huh?)
Making |to "collapse" the cursors will keep most of existing code compatible with this new feature; at least compatible with the engine which would otherwise be bamboozled by multiple cursors. Some other cursor words such as |swap, |+, <| can support multiple cursors out-of-the-box.
We can then add |to* which can be used like so: [ 1 2 3 4 ] [ 1 4 ] |to* leaves: [ [ 1 | 2 3 4 | ] ] (note multiple cursor literals => multiple cursors added). Then we can have for instance [ 1 | 2 3 | 4 ] swap which will result in [ 3 | 2 1 | 4 ] (i.e. 1 3 swap => 3 1, then "plug" both back into the block). If there aren't enough arguments, they're taken before the leftmost cursor, as in: [ 1 2 | 3 4 | 5 ] rot => 1 2 "..." 4 rot =>  2 4 "..." 1 => "plug" back in [ 2 4 | 3 1 | 5 ].
Uhm... This does create a lot of problems, for instance what shove-order should the thing have, what cherry-order should the thing have? This issue doesn't answer these questions; instead it swaps answers to them here and there, which doesn't help, but who cares?
Nevertheless, since I don't like making "ultimate" decisions, I think we should rather expose the cursor block to the runtime (what did ya think I'd do huh :smiling_imp:). The latter will make the language obscure², but again, who cares, really? So something like |to* can be implemented in Novika itself, assuming |block leaves the cursor block:
[ dup |block resub ] @: |to*

For instance, in the following block [ 2 3 | 4 5 | 6 7 | 8 9 ] the cursor block will be [ 2 4 6 | ]. If we then do |: drop (drop everything before cursorS), we'll get [ 2 | 4 | 6 | 8 9 ], the cursor block [ 1 3 5 | ] as expected.
Of course to not make things slow we should use integer-cursor or a thin, protocol-conforming integer wrapper instead of spinning up a whole new block for every cursor. Only when multiple cursors are needed should we "actually do the thing". Some object ballet, why not!
And remember blocks are stacks, so you can operate on a stack with multiple cursors! Wouldn't that be fun?
So, the biggest problem now is the following. How do we manage the cursor block?  What if someone holds on to it and then we empty it by e.g. collapsing with |to? On this we can say |block is as dynamic as stack or conts, for instance, so why would you not expect it to disappear right from underneath you? This is less of an issue for me.
As for the management part, I think each block may (optionally!) have its own, personal cursor block. It's only ever created once (when multiple cursors are requested) and then used appropriately, emptied and whatnot, until the block that is its owner is GCd, or until whoever keeps a reference to the cursor block is GCd.

Well, first, we must understand that the cursor in the cursor block is in some sense second-order. The interpreter could use it (and move it!) to find the current insertion point — to keep state. Then there is always an active cursor to tell us where we should do an insertion. And after insertion this second-order cursor will move forward, somewhat reminiscent of the stuff that is happening in stack & code blocks: in stack block the cursor is moved forward after insertion, and in code it is moved forward by magic (by the engine, actually). So with the second-order cursor block cursor, it's moved after insertion but by magic, because no actual insertion is happening but rather there is "remote" insertion, to the block that is the cursor block's owner.
[ 100 | 200 | 300 | ] $: withCursorsAfterEachItem

withCursorsAfterEachItem |block leaves:  [[ 1 2 3 | ]]
withCursorsAfterEachItem 'Didn\'t expect this did you?' shove

withCursorsAfterEachItem leaves: [[ 100 | 200 | 300 'Didn\'t expect this did you?' | ]]
withCursorsAfterEachItem |block leaves:  [[ 1 2 4 | ]]

"swap [ 1 2 4 | ] => swapping(4) [ 1 2 | ] => swapping(4) swapping(2) [ 1 | ]"
withCursorsAfterEachItem swap leaves: [[ 100 | 'Didn\'t expect this did you?' 300 200 ]]

With such solution though, it's hard to keep the cursors intact as I've shown in the examples above, we have to pop them or else consistency will go nuts (as if it already didn't). So this definitely something to think about.
Also, we can go third-order and have multiple cursors in the cursor block. The fact that this should be possible hints at an implementation that recurses somewhere, but it'll recurse somewhere anyway — it's Novika we're talking about. This gives us an opportunity to implement multiple cursors as discussed in the very beginning:
[ 100 200 300 ] $: items

items [ 1 2 3 ] |to*                "Cursor block of items is:  [ 1 2 3 | ]"

items |block [ 1 2 3 ] |to*   "Cursor block of items is:  [ 1 | 2 | 3 | ]"

items 'Heya!' shove               "Cursor block of items is: [ 2 | 3 | 4 | ]"

items leaves: [[ 100 'Heya!' | 200 'Heya!' | 300 'Heya!' | ]]

Note that this example is incompatible with the example above. Again, what'll happen in the cursor block during insertion (and deletion too, frankly) is unclear. Whatever the implementation will be, it should allow terse usage, most of these examples to work, and also multiple orders as I've demonstrated.
Implementing all of this somehow, will make it possible to add something to the "is a block" list: not only are stack, code, array, object, dictionary, continuation, "call stack" aka continuation stack, block friend list — blocks, but block's cursor is a block, too! That can get anyone's head to spin, and I like that.

And for the dessert you can think about a block that is its own cursor block :)


improve README

Changes:

Improve grammar
Monospace font some terms
Capitalize term Markdown
Captalize term URL
Prettify explanation of Markdown AST abbreviation
Expand terms MD and MD AST

Context:
Here are some small changes to improve your README.
Let me know if you like/hate the changes. 😉

Thanks for merging my changes! 😄 ✨

Thank you for spending time going through all the explanations I threw there! I didn't expect anyone to actually ready it 😅


Add Android Learning Resources

https://github.com/androiddevnotes/awesome-android-learning-resources/
Awesome Android Learning Resources aims to be the starting point for Android App Developers to find the finest learning content for Android App Development.
The content is Android Kotlin App development focused. Android Java content which can be of benefit to developers is listed and tagged with [JAVA]
Content in languages other than English is tagged according to ISO 639-2 codes.
Disclaimer: I have added the Awesome Badge along with the other badges to maintain consistency.
PR reviewed:

1876

1848

By submitting this pull request I confirm I've read and complied with the below requirements 🖖
Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.
Requirements for your pull request

Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List.

✅ Add Swift
✅ Add Software Architecture
❌ Update readme.md
❌ Add Awesome Swift
❌ Add swift
❌ Adding Swift
❌ Added Swift

Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.

✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
✅ - [Framer](…) - Prototyping interactive UI designs.
❌ - [iOS](…) - Resources and tools for iOS development.
❌ - [Framer](…)
❌ - [Framer](…) - prototyping interactive UI designs

Your entry should be added at the bottom of the appropriate category.
The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

Has been around for at least 30 days.That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
The default branch should be named main, not master.
Includes a succinct description of the project/theme at the top of the readme. (Example)

✅ Mobile operating system for Apple phones and tablets.
✅ Prototyping interactive UI designs.
❌ Resources and tools for iOS development.
❌ Awesome Framer packages and tools.

It's the result of hard work and the best I could possibly produce.
If you have not put in considerable effort into your list, your pull request will be immediately closed.
The repo name of your list should be in lowercase slug format: awesome-name-of-list.

✅ awesome-swift
✅ awesome-web-typography
❌ awesome-Swift
❌ AwesomeWebTypography

The heading title of your list should be in title case format: # Awesome Name of List.

✅ # Awesome Swift
✅ # Awesome Web Typography
❌ # awesome-swift
❌ # AwesomeSwift

Non-generated Markdown file in a GitHub repo.
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate. Please search for existing submissions.
Only has awesome items. Awesome lists are curations of the best, not everything.
Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
Includes a project logo/illustration whenever possible.

Either centered, fullwidth, or placed at the top-right of the readme. (Example)
The image should link to the project website or any relevant website.
The image should be high-DPI. Set it to maximum half the width of the original image.

Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
Includes the Awesome badge.

Should be placed on the right side of the readme heading.

Can be placed centered if the list has a centered graphics header.

Should link back to this list.

Has a Table of Contents section.

Should be named Contents, not Table of Contents.
Should be the first section in the list.
Should only have one level of nested lists, preferably none.

Has an appropriate license.

We strongly recommend the CC0 license, but any Creative Commons license will work.

Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0 (replace <user> and <repo> accordingly).

A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
Place a file named license or LICENSE in the repo root with the license text.
Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.
To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

Has contribution guidelines.

The file should be named contributing.md. Casing is up to you.

Has consistent formatting and proper spelling/grammar.

The link and description are separated by a dash. Example: - [AVA](…) - JavaScript test runner.
The description starts with an uppercase character and ends with a period.
Consistent and correct naming. For example, Node.js, not NodeJS or node.js.

Doesn't use hard-wrapping.
Doesn't include a Travis badge.You can still use Travis for list linting, but the badge has no value in the readme.
Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

Did you run the linter? It shows 155 errors for me...
See: https://github.com/sindresorhus/awesome-lint

@wernerkrauss Hi. Due to the nature of the list. There are errors related to github should be written as GitHub. BUT the linter cannot identify the github word is part of the link and not standalone.
The linter also shows errors for duplicate links. BUT the linter again cannot identify that those duplicate links are justified in this context.
The linter also mentions separating link and description with -. BUT due to the multiline description, it looks better to me to put the description in a nested bullet point to maintain readability.
I understand the linter shows error but those said errors lack context. If you do manually check the list, it should be according to guidelines.

@androiddevnotes I know, a linter can drive one crazy...
But if you pass correct markdown syntax, the linter can see if it's a link or not. It does't complain at my currently WIP list https://github.com/wernerkrauss/awesome-silverstripe
as an example:
- [Markdown Field](https://github.com/Silverstripers/markdownfield) -  Can replace your HTMLEditorFields (using TinyMCE) so you can utilise Markdown syntax.

This way also the URL is hidden from the list and the link has a "title" (Markdown Field) and an additional description.

@wernerkrauss Hey. I adjusted the README accordingly. If the issues still exist, please let me know.

Thanks for making an Awesome list! 🙌
It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it. I spent a lot of time creating the guidelines so I wouldn't have to comment on common mistakes, and rather spend my time improving Awesome.

unicorn

Made appropriate changes according to guidelines.

The list looks much better now. Might I annoy you with some remarks...?
The linter still throws some errors. Only four are left:
 README.md:268:5
  ×    1:1  Missing main list heading                                                           remark-lint:awesome-heading
  ×   55:1  ToC item "Contributing" does not match corresponding heading ":memo: Contributing"  remark-lint:awesome-toc
  ×  268:5  https://www.raywenderlich.com/                                                      remark-lint:double-link
  ×  577:3  https://www.raywenderlich.com/                                                      remark-lint:double-link

Elements of Android Room - This book explores Room.
What is Room?

Kotlin for Android Developers - Kotlin for Android Developers.
...and others: the name of the link and the description are the same. This doesn't make sense to me. You might summarize the book in one sentence (e.g. for beginners or experienced devs)

Other book descriptions are on the other side too long for my taste, but @sindresorhus might have another opinion on that. Don't just copy/paste the book summary.

@wernerkrauss I used H1 align center to center the heading and not #. The linter probably is complaining because of that. The error is unnecessary IMO as the H1 is also a heading and the linter fails to identify it.
ToC item "Contributing" does not match the corresponding heading ":memo: Contributing": This error looks like a linter issue. If you go to the contents section, the hyperlink works as intended.
https://www.raywenderlich.com/ for this duplicate link, the linter lacks context. The raywenderlich produces courses, books, youtube, blogs, so I need to duplicate the link to have it multiple times throughout the README.
I believe all the 4 errors are justified and are due to the lack of context given to linter.
About book descriptions, that is subjective. I like more details.

unicorn

👍

👍

It looks like you didn't read the guidelines closely enough. I noticed multiple things that are not followed. Try going through the list point for point to ensure you follow it.

Still many guidelines not followed.


Requesting undefined post thread

At some points beta tries to pull up /v0/posts/undefined/thread. It's not clear when or why.

example: https://beta.pnut.io/@ludolphus/posts/328572

Fixed in 1.8.1.


fix: DEV-1947: Fixed tabs randomly mixed after label stream

Description of the proposed changes
Tabs are being randomly mixed after label stream. It's not guaranteed that backend will always return in the expected order.
These changes add an ASC ID ordering in the view class to avoid this issue.
Jira Ticket
https://heartex.atlassian.net/browse/DEV-1947

/git merge develop


Lazy captured evaluation

After fixing the bug I have run the dra example. Theses are the results (the optimized is 4 (!) times faster):
This speed-up is due to lazy evaluation (as implemented in this pull request).
Without lazy evaluation the optimized runs a little slower than the original in the dra example.
Original:
Parsing time:   5.29 seconds
Queries time: 116.80 seconds
Total time: 122.10 seconds
Total run time: 122.18 seconds
Optimized:
Parsing time:   5.27 seconds
Queries time:  24.85 seconds
Total time:  30.11 seconds
Total run time:  30.18 seconds

another general comment: please arrange the PR so that it only shows commits and changed files from the relevant changes


k3s on external mysql db is stuck, no scheduling works, no new pods

Environmental Info:
K3s Version:
root@brixone:~# k3s -v
k3s version v1.20.5+k3s1 (355fff30)
go version go1.15.10
root@kube1-worker:~# k3s -v
k3s version v1.20.6+k3s1 (8d043282)
go version go1.15.10
Node(s) CPU architecture, OS, and Version:
x86, 5x debian 10.9
root@brixone:~# kubectl get nodes -o wide
NAME           STATUS   ROLES                  AGE   VERSION        INTERNAL-IP      EXTERNAL-IP   OS-IMAGE                       KERNEL-VERSION    CONTAINER-RUNTIME
kube1-worker   Ready    <none>                 27m   v1.20.6+k3s1   <IP_ADDRESS>     <none>        Debian GNU/Linux 10 (buster)   4.19.0-16-amd64   containerd://1.4.4-k3s1
kube2-worker   Ready    <none>                 22m   v1.20.6+k3s1   <IP_ADDRESS>     <none>        Debian GNU/Linux 10 (buster)   4.19.0-16-amd64   containerd://1.4.4-k3s1
msi55          Ready    control-plane,master   25h   v1.20.6+k3s1   <IP_ADDRESS>    <none>        Debian GNU/Linux 10 (buster)   5.4.106-1-pve     containerd://1.4.4-k3s1
brixone        Ready    control-plane,master   28d   v1.20.5+k3s1   <IP_ADDRESS>   <none>        Debian GNU/Linux 10 (buster)   5.4.106-1-pve     containerd://1.4.4-k3s1
corosync       Ready    control-plane,master   28d   v1.20.5+k3s1   <IP_ADDRESS>   <none>        Debian GNU/Linux 10 (buster)   5.4.106-1-pve     containerd://1.4.4-k3s1

Cluster Configuration:
currently 3 masters ,2 workers,
Describe the bug:
Problem is that cluster reports 3 masters and 2 workers as Ready, but no schedling of pods works, problem appear after 1 master drop, 2 others just start to not work, but reports as Ready.
Steps To Reproduce:
Hard to say, I have k3s with 3 masters and 3 workers, after 1 master was restarted , cluster start to not scheduling new pods. We tried to restart whole cluster , but then all 3 workers ends in NonReady status, so we removed them and added 2 others that are in Ready, but non pods are created on them.
Expected behavior:
Cluster to work
Actual behavior:
no new pods are creating in masters or workers
Additional context / logs:
kubectl get nodes
NAME           STATUS   ROLES                  AGE   VERSION
kube1-worker   Ready                     26m   v1.20.6+k3s1
kube2-worker   Ready                     20m   v1.20.6+k3s1
msi55          Ready    control-plane,master   25h   v1.20.6+k3s1
brixone        Ready    control-plane,master   28d   v1.20.5+k3s1
corosync       Ready    control-plane,master   28d   v1.20.5+k3s1

Can you attack k3s service logs from one of all of the K3s servers? Kinda hard to tell what's going on from just a list of nodes.

Hello,
yes sure,
k3s.log


When games api will be added?

When games api will be added?

PR #201 is addressing this. Watch it...

Some of the Game API methods have been added. Specifically, TelegramBot#sendGame() and TelegramBot#setGameScore(). Thanks to @jishnu7!
Also, @jishnu7 promised us to implement the remaining methods. :smile:
Will keep this issue open until the remaining methods are implemented and published.

This has been added in v0.25.0!
Thanks @highfeed for your interest in this library!


Fix for issue 701

This is an attempt to fix #701.

Automated message from Dropbox CLA bot
@sharmaeklavya2, it looks like you've already signed the Dropbox CLA. Thanks!

Looks good, merged!  Thanks @sharmaeklavya2!

Oh, I guess one comment -- b4009c28d0d28ecf490d8fc17129a4bbd1410446 should have contained a "Fixes: #701." line at the end of the commit message so it would automatically close the GitHub issue.

Oh, I guess maybe there's still part of #701 open (the docs piece), so maybe it's OK that this left that open.

There is something left to be done. I haven't updated the docs. See #701.


Update usage string to include code-exploration client.

Support for code-exploration client was added #6766 in but the usage string wasn't updated.

Sorry for missing this in #6766.

bors r+


MIGraphx node example for resnet50 model

Uses the MIVisionX extension node to create a test case for resnet50
Modifies the mnist example to take user input for model

@kiritigowda Ready to be merged. Removed both models


Unable to connect to the port

The sample run successfully but the console shows these error. To my assumption, the latest OS(Mac OS Sierra/ Openframework 9.8) no longer support the port. Any one have the solution to fix this problem?
[ error ] SerialDevice::setup: IO Exception (2): No such file or directory, file /Users/hoyin1994/Documents/of_v0.9.8_osx_release/addons/ofxSerial/libs/serial/src/impl/unix.cc, line 151.
[ error ] ofApp::setup: Unable to connect to: /dev/tty.usbmodem411

If it printed successfully, then I'm not sure why you got these errors.  It looks like you tried to connect to a USB serial devices (looks like an arduino uno?).


Return reconcile error if node state is not updated

NetFilter selector depends on PCI address of NICs from the node state. After PR #487 is merged we need to check if node state is updated or return an reconcile error to render device plugin config faster.

@zeeke PTAL


soc: atmel_sam0: Add GCLK Reset

Fixes an issue with mcuboot where the SoC will freeze when the dpll is
disabled since atmel_samd_init was already run in the bootloader.
Signed-off-by: Abram Early<EMAIL_ADDRESS>

@nvlsianpu and @ioannisg could you please review this, as it is part of the MCUboot hardware cleanup that you worked on?

@nandojve

If I'm right, you can create a gclks_init and refact gclk_connect methods.

Not really. The problem occurs when the dpll is initialized, since the core is running on that clock when it hits that function if the bootloader ran. The first thing dpll_init does is disable the clock which then bricks the core. And the reset can't be put in the same place as the gclk connect since the dpll has to be initialized before connecting it.

Ok, understood!

Dividers care attention. I think the more secure way is configure it with a well know low freq oscillator as main source.

I don't really agree since this reset is practically the same as a power on reset, which necessitates a well known oscillator. I wouldn't be totally averse to explicitly connecting the core to a different oscillator before entering dpll_init, but I personally see the reset as a better solution because it puts the entire GCLK peripheral into a known state before configuration. (Which probably means that this should be included on the samd21 as well.)

I understand what you are saying but it is not clear to me what is Main clock between glkc reset and new first gclk_connect. If when you reset gclk system switch to another clock source, what is that clock source, frequency?

I understand what you are saying but it is not clear to me what is Main clock between glkc reset and new first gclk_connect. If when you reset gclk system switch to another clock source, what is that clock source, frequency?

On any reset, generic clock 0 (which provides the core clock) is reset to be sourced from the DFLL48M which is factory calibrated for 48MHz from an RC oscillator.
I do need to add a minor correction: If any of the peripheral clocks are write locked, their respective generic clock source will not be reset on a software reset. Generic clock 0 is exempt from this rule, and will be reset anyway even if peripheral clocks using this as a source are write locked.

@stephanosio not sure if you'd like to take a look here.


Workspace/AccessModeType has no null option

It's xsd definition allows it not to be set:
<xs:element name="accessMode" type="bom:accessModeEnum" minOccurs="0" maxOccurs="1">
But in the code we have neither a null enum option or a nullable option
        [ProtoContract]
        public enum AccessModeType
        {
            [XmlEnum(Name = "read-only")]
            Read_Only,
            [XmlEnum(Name = "read-write")]
            Read_Write,
            [XmlEnum(Name = "read-write-once")]
            Read_Write_Once,
            [XmlEnum(Name = "write-once")]
            Write_Once,
            [XmlEnum(Name = "write-only")]
            Write_Only,
        }

If it's not set, it will be set to read-only after deserialization and serialization.

I guess AccessMode should be changed to a nullable type.


[Feature] Renaming

Keep the current name for the v2.0.0 update, and then change the name to discoauth and DiscoAuth, and replace the api token
Checklist:

[x] Before Async-DisOAuth release:

[x] Check versions in:

[x] docs/conf.py
[x] pyproject.toml
[x] src/__version__.py
[x] src/__main__.py

[x] Change the changelog's Unreleased to 2.0.0

[x] After Async-DisOAuth release:

[x] Change the README
[x] Change PyPI API token
[x] Name changed on pyproject.toml
[x] Name changed on docs/conf.py
[x] Disable webhook for Async-DisOAuth on rtd
[x] Enable new docs webhook for rtd
[x] Move all files in src/DisOAuth to src/discoauth
[x] Double check all documentation for any mention of Async-DisOAuth and DisOAuth, and replace with discoauth and DiscoAuth
[x] Rename the cli to discoauth
[x] Change the docs in the source code

Checklist:

[ ] Before Async-DisOAuth release:

[ ] Check versions in:

[ ] docs/conf.py
[ ] pyproject.toml
[ ] src/__version__.py
[ ] src/__main__.py

[ ] After Async-DisOAuth release:

[ ] Change PyPI API token
[ ] Name changed on pyproject.toml
[ ] Name changed on docs/conf.py
[ ] Disable webhook for Async-DisOAuth on rtd
[ ] Move all files in src/DisOAuth to src/discoauth
[ ] Double check all documentation for any mention of Async-DisOAuth and DisOAuth, and replace the with discoauth and DiscoAuth

Ready to update, and then I will take a break for a while


Advanced Indexing Support #1

This PR refactors the fancy index selection of of NumPy array, which fixes the following cases:

When an integer index is just before or just after an array index, the case is supported by our current advanced indexing logic, however is blocked at typing level.

import numba
import numpy as np

@numba.njit
def func(x, idx):
    return x[:, 2, idx, :, :]

a = np.random.random_integers(0, 100, (10, 11, 12, 13, 14))
b = np.random.random_integers(0, 10, (4,))

print(np.allclose(func(a, b), func.py_func(a, b)))
# Before PR: Error, but we have the support
# After PR: True

When an integer index is after an array index with slices in between (multiple indexing subspaces), the case is not supported by  our current advanced indexing logic, however is not being blocked at typing level.

import numba
import numpy as np

@numba.njit
def func(x, idx):
    return x[:, :, idx, :, 4]

a = np.random.random_integers(0, 100, (10, 11, 12, 13, 14))
b = np.random.random_integers(0, 10, (4,))

print(np.allclose(func(a, b), func.py_func(a, b)))
# Before PR: False, but runs so it's a bug
# After PR: raises Error correctly

This also clearly separates out the various limitations of advanced indexing in Numba so that we can add support/remove the limitation one at a time.

Going to use the checklist again for this PR too:
I have checked that:

[ ] There is no other Pull Request proposing the same change. (If there is
please highlight this and one of the core developers will pick it up.)
[ ] The proposed additional NumPy functionality is not deprecated by
NumPy.
[ ] Public CI is passing.
[ ] The patch does not touch files in numba.core.
[ ] The patch is implemented using the high-level extension API only
(https://numba.readthedocs.io/en/stable/extending/high-level.html).
[ ] The patch updates the documentation to reflect the new functionality.
(https://github.com/numba/numba/blob/main/docs/source/reference/numpysupported.rst)
[ ] The patch is line wrapped to 80 characters.
[ ] Changes to Python source in the patch are flake8 compliant.
[ ] The implementation of the NumPy function reflects that present in the
NumPy implementation itself (look in the NumPy repository:
https://github.com/numpy/numpy)...

[ ] The implementation has references to the region of the NumPy code
base that provides the same functionality. The references are URLs
of the form:
https://github.com/numpy/numpy/tree/<SHA>/path/to/file.py:#<lines>
[ ] The code "looks" reasonably similar to the NumPy implementation.
[ ] The code uses the same algorithm as the NumPy implementation, if
it does not it explains why and this justification is reasonable.
[ ] The type inference part of the Numba implementation restricts the
types to those declared in the NumPy docs (or if not present, what
is accepted in the NumPy implementation itself).
[ ] The Numba implementation uses the same variable names for
arguments as in the NumPy implementation.
[ ] The Numba code has commentary present for anything not-obvious by
inspection.
[ ] The Numba code accommodates differences that might occur across
different NumPy versions in a clear fashion and uses
numba.np.numpy_support.numpy_version to separate the difference
in implementations.

[ ] The unit tests for the implementation:

[ ] Use the same test inputs as the NumPy unit tests for the same
functionality. If this is not the case there are comments which
explain why and this justification is reasonable.
[ ] The NumPy unit test inputs have reference URLs associated with
them to track their origin. The references are URLs of the form:
https://github.com/numpy/numpy/tree/<SHA>/path/to/file.py:#<lines>
[ ] Use unittest style assertions (not pytest style!).
[ ] Check that unsupported/invalid input types are handled as expected
using the with self.assertRaises() pattern.
[ ] Explicitly check custom error messages are raised appropriately.
[ ] Hit all the branches of the proprosed change (both at type
inference and run time).
[ ] Check that numerically awkward values work as expected e.g.
NaN, +/-Inf, 0, INT_MAX, INT_MIN etc.
[ ] Check that types which can be converted to arrays (assuming NumPy
accepts this behaviour) work as expected.
[ ] Check that passing empty versions of containers e.g. empty tuple
or 0d array works as expected.

[ ] The patch works in a simple manual test in my local checkout.
[ ] I cannot break the code in the patch in my local checkout after
trying to do so for a minimum of 10 minutes. The error messages seem
reasonable and there are no "incorrect" results.
[ ] I think the code introduced in this change is easy to maintain.
[ ] I understand all the code in this PR.

After doing some manual flake8 checking, I would like to suggest the following patch so as not to introduce more flake8. violations:
diff --git i/numba/core/typing/arraydecl.py w/numba/core/typing/arraydecl.py
index 6099af40ea..24c5b2591c 100644
--- i/numba/core/typing/arraydecl.py
+++ w/numba/core/typing/arraydecl.py
@@ -45,8 +45,9 @@ def get_array_index_type(ary, idx):
     for ty in idx:
         if ty is types.ellipsis:
             if ellipsis_met:
-                raise NumbaTypeError("Only one ellipsis allowed in array indices "
-                                     "(got %s)" % (idx,))
+                raise NumbaTypeError(
+                    "Only one ellipsis allowed in array indices "
+                    "(got %s)" % (idx,))
             ellipsis_met = True
             in_subspace = False
         elif isinstance(ty, types.SliceType):
@@ -70,7 +71,8 @@ def get_array_index_type(ary, idx):
               and isinstance(ty.dtype, (types.Integer, types.Boolean))):
             if ty.ndim > 1:
                 # Advanced indexing limitation # 1
-                raise NumbaTypeError("Multi-dimensional indices are not supported.")
+                raise NumbaTypeError(
+                    "Multi-dimensional indices are not supported.")
             array_indices += 1
             advanced = True
             if not in_subspace:

@kc611 this looks good so far. Regarding the flake8 cleanliness, I noticed that several of the files that you have touched in this PR are still being excluded with our .flake8 config, but I did check manually and the files are flake8 compliant. Maybe you could include the following patch, so as to automate flake8 checking for these files in furture:
diff --git i/.flake8 w/.flake8
index 0e63904d41..c5b40bb90a 100644
--- i/.flake8
+++ w/.flake8
@@ -98,7 +98,6 @@ exclude =
     numba/tests/test_builtins.py
     numba/tests/test_jitmethod.py
     numba/tests/test_inlining.py
-    numba/tests/test_array_manipulation.py
     numba/tests/test_dummyarray.py
     numba/tests/test_smart_array.py
     numba/tests/test_linalg.py
@@ -110,7 +109,6 @@ exclude =
     numba/tests/test_typeinfer.py
     numba/tests/test_return_values.py
     numba/tests/test_npdatetime.py
-    numba/tests/test_fancy_indexing.py
     numba/tests/support.py
     numba/tests/test_print.py
     numba/tests/test_debug.py
@@ -222,7 +220,6 @@ exclude =
     numba/core/typing/randomdecl.py
     numba/core/typing/setdecl.py
     numba/core/typing/npydecl.py
-    numba/core/typing/arraydecl.py
     numba/core/typing/collections.py
     numba/core/typing/ctypes_utils.py
     numba/core/typing/enumdecl.py

@kc611 this looks good so far. Regarding the flake8 cleanliness, I noticed that several of the files that you have touched in this PR are still being excluded with our .flake8 config, but I did check manually and the files are flake8 compliant. Maybe you could include the following patch, so as to automate flake8 checking for these files in furture:
diff --git i/.flake8 w/.flake8
index 0e63904d41..c5b40bb90a 100644
--- i/.flake8
+++ w/.flake8
@@ -98,7 +98,6 @@ exclude =
     numba/tests/test_builtins.py
     numba/tests/test_jitmethod.py
     numba/tests/test_inlining.py
-    numba/tests/test_array_manipulation.py
     numba/tests/test_dummyarray.py
     numba/tests/test_smart_array.py
     numba/tests/test_linalg.py
@@ -110,7 +109,6 @@ exclude =
     numba/tests/test_typeinfer.py
     numba/tests/test_return_values.py
     numba/tests/test_npdatetime.py
-    numba/tests/test_fancy_indexing.py
     numba/tests/support.py
     numba/tests/test_print.py
     numba/tests/test_debug.py
@@ -222,7 +220,6 @@ exclude =
     numba/core/typing/randomdecl.py
     numba/core/typing/setdecl.py
     numba/core/typing/npydecl.py
-    numba/core/typing/arraydecl.py
     numba/core/typing/collections.py
     numba/core/typing/ctypes_utils.py
     numba/core/typing/enumdecl.py

I took another look at this, and it seems like my vscode may have been misconfigured. Perhaps the only file touched in this PR that is flake clean is:
numba/tests/test_record_dtype.py?

@kc611, OOB @esc recalled from previously that there might be some significant CI runtime increases coming from somewhere in these changes. It's hard to tell from public CI as the CPUs used to run the tests are not consistent. Please could you take a look at the performance of the changed test module before/after this patch and report back? Many thanks. (Am going to mark this as waiting on author again whilst this check is performed).

Locally I see about a ~40 seconds increase. For the changed test module test_fancy_indexing;
On current main before the patch, running pytest numba/numba/tests/test_fancy_indexing.py gives  10 passed, 5 warnings in 40.04s
After the patch, running pytest numba/numba/tests/test_fancy_indexing.py gives 13 passed, 201 warnings in 83.21s (0:01:23)
This is due to the extra tests we have added for multidimensional testing. (Running only the TestFancyIndexingMultiDim gives  3 passed, 196 warnings in 44.40s ).

Locally I see about a ~40 seconds increase. For the changed test module test_fancy_indexing;
On current main before the patch, running pytest numba/numba/tests/test_fancy_indexing.py gives  10 passed, 5 warnings in 40.04s After the patch, running pytest numba/numba/tests/test_fancy_indexing.py gives 13 passed, 201 warnings in 83.21s (0:01:23)
This is due to the extra tests we have added for multidimensional testing. (Running only the TestFancyIndexingMultiDim gives  3 passed, 196 warnings in 44.40s ).

Thanks for doing this @kc611, seems like it is adding a small amount of additional load to the test suite. Maybe the K value for the number of random tests could be reduced? I'm also testing this patch locally to try and see the impact on the code base as a whole.

Running this command: time ./runtests.py -m 4 --random=0.1.

main branch runs 1161 tests in 286s. real: 4m49, user: 14m18, sys: 0m19
this branch runs 1161 tests in 478s. real: 8m1, user: 18m44, sys: 0m25

which suggests there may be an issue, will keep looking.

Running this command: time ./runtests.py -m 4 --random=0.1.
* `main` branch runs 1161 tests in 286s. real: 4m49, user: 14m18, sys: 0m19

* this branch runs 1161 tests in 478s. real: 8m1, user: 18m44, sys: 0m25

which suggests there may be an issue, will keep looking.

Turns out that this was a mistake in the basis of comparison due to branches containing a slight variation in the tests present, apologies @kc611. Having retested this independently there was no observable performance impact on existing tests.


Remove code used to support h5py<2.10.0

It seems that the relevant issue was fixed in 2.10.0 https://github.com/h5py/h5py/commit/466181b178c1b8a5bfa6fb8f217319e021f647e0
I'm not sure how far back you want to fix things. I'm hoping to test this on the CI.
I found this since I've been auditing slowdowns in our codebase, which has caused me to review much of the reading pipeline.
Do you want to add a test for h5py>=2.10.0? Or can we assume that users won't install things together.
https://pypi.org/project/h5py/2.10.0/
I could for example set the backend to not be available if a version of h5py that is too old is detected.
One could alternatively, just keep the code here.

[ ] Closes #xxxx
[ ] Tests added
[ ] User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ] New functions/methods are listed in api.rst

I think this is good. It seems like 3.6 is the min-version we support (https://github.com/pydata/xarray/actions/runs/3577424529/jobs/6016410891)


Put hotMiddleware before proxyMiddleware in dev server

Hot reload breaks when there are entries in the proxy table in config/index.js.  In the dev server, using the hot reload middleware before the proxy middleware fixes the problem.

Thanks for this. is there any info/docs that I can read up on this behaviour?

Not that I know of.  I've never used webpack-hot-middleware or webpack-proxy-middleware.  When looking for documentation, I could only find this tutorial.  He also puts the hot-middleware before the proxy middleware.  I've used react-hot-loader, and I know it is fickle about it's placement in the webpack setup, so I tried changing the order as a fix and it worked.

Thanks for the background info. Will try this!


Fpdf: add WriteAligned.

WriteAligned allows a user to write a single string and align it.
Previously, Write() would only write with Left alignment. Sometimes, you
want to align a specific text string to the center or the right.
HTMLBasic: add <center> tag.
This allows a user to center text within the HTML block. This way they
do not have to split up their input.
A new line will be created automatically before and after the centered
text.

Nice feature -- thanks!


Can I use pretrained model to get disparity map on Pascal VOC dataset?

Is it possible using the pretrained model to get disparity map on Pascal VOC dataset?

Yes, you can have a try.


max-width

it not have max-width or fit-content
when I add a div have inline content long, the overflow can't auto, it crash styles

Hi, it doesn't appear to be a problem with the template or the max-width utility classes. It will happen anywhere unless you break the word in CSS:
https://blog.logrocket.com/guide-css-word-wrap-overflow-wrap-word-break/


Signing up for a new service (ie adding into the sidebar), causes the new service to always get added at index 2

Bug description:
Adding a new service (beyond the 2nd service) keeps adding the service only at position #2.
Steps to reproduce:

Open Ferdi
Make sure that you already have 3 configured services
Click Cmd+N
In the new 'Services' dialog, add any random service
Upon clicking 'save' button, the new service is always added as the 3rd service.

Expected behavior
The new service should always be added to the end of the existing list of services.
Screenshots

Environment:

Operating System: macOS Big Sur

Ferdi Version: Latest GIT SHA: cda77aa3 from the develop branch

Server: Ferdi

Debug information:

I can reproduce this in production mode. However, it doesn't happen for in debug mode, which is especially infuriating and makes debugging it pretty difficult.


[SE-0313] isolated parameters ABI

Explanation:  Implements the core type checker, runtime, and ABI aspects of isolated parameters for SE-0313, so we can lock in the mangling and runtime representation for this feature.
Scope: Affects the modeling of actors in the type system, but should not change the semantics.
Radar/SR Issue: rdar://75389492
Risk: Low.
Testing: PR testing and CI on main.
Original PR: https://github.com/apple/swift/pull/37794

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 0e1638d161639536636feb5e24907bc4daa352c3

Grrr. Unrelated failure on Linux

@swift-ci please test Linux

@swift-ci please nominate


Fix several issues in Public Report Schedules Create Method

Several issues were discovered when testing:

The first Report event time was always set to be event start. This makes sense for daily frequency, but not for weekly or monthly. The first Report event time is now set to the first occurrence of the specified day of the week if it is weekly frequency and the first occurrence of the day of the month if it is monthly frequency.

The api key metadata was not set for calls to the kingdom event groups service and data providers service.

The helper function for the Report lookback window didn't work if utc offset was used instead of time zone.

This change is

Could you provide some context about the issues?

src/main/kotlin/org/wfanet/measurement/reporting/service/api/v2alpha/ReportSchedulesService.kt line 356 at r2 (raw file):

    val nextReportCreationTime: Timestamp =
      if (source.eventStart.hasUtcOffset()) {

Sorry could you remind me again if eventStart gets incremented when a report is created? If so, could you point me to where it happens?
Code quote:
source.eventStart


ENH: Remove unused parameter from method prototype

Remove unused parameter from method prototype: PET images do not have a b0 image.

Not sure whether this was put intentionally to make the interface the same as for DWI but in that case a base class would be more appropriate, or to use kwargs.

This is intentional, perhaps a bad way of defining an API, but all methods need to have that argument :)
How would you go about it?

My first thought is that it should not be there if it is not common to all classes :-S
Thoughts:

Could be a passed as kwargs and do insert_b0 = kwargs['insert_b0'] for the DWI case.
Other solutions:

Mark as  # pylint: disable=unused-argument or # noqa: F841 (less preferable than the below)
Do _ = (insert_b0) as the first statement in the method in the PET case
Do del insert_b0 as the first statement in the method in the PET case
Declare the method as def to_nifti(self, filename, *_): in the PET case
Declare the method as def to_nifti(self, filename, *insert_b0): in the PET case

Do _ = (insert_b0) as the first statement in the method in the PET case

This argument is strong - why PET has to have insert_b0 in first place. Your solution of using kwargs seems the right choice.
Thanks for point out this issue.

Done in 102a820.


RHOARDOC-1455: Fixed the version.wildfly.swarm property in app howto POM

Resolves RHOARDOC-1455

[x] Have you followed the guidelines in our Contributing document?
[x] [v2] Have you created a JIRA and used it in the commit message?
[ ] [v4] Have you created a GitHub Issue and used it in the commit message?
[x] Have you checked to ensure there aren't other open Pull Requests for the same issue?
[x] Have you built the project locally prior to submission with mvn clean install?

The identical PR will be filed in prod and synced to Launcher.

I don't know why the check wasn't updated, but the PR job finished OK: https://ci.wildfly-swarm.io/view/Pull Requests/job/thorntail-pull-request-linux/712/


underutilized nodes are not detectable

What version of descheduler are you using?
descheduler version: v0.25.1
Does this issue reproduce with the latest release? yes
Which descheduler CLI options are you using?
descheduler-64cfdf7f6c-n2xq5.log
No
Please provide a copy of your descheduler policy config file
apiVersion: "descheduler/v1alpha1"
kind: "DeschedulerPolicy"
strategies:
"RemoveDuplicates":
enabled: true
"RemovePodsViolatingInterPodAntiAffinity":
enabled: true
"LowNodeUtilization":
enabled: true
params:
nodeResourceUtilizationThresholds:
thresholds:
"cpu" : 60
"memory": 60
"pods": 10
targetThresholds:
"cpu" : 80
"memory": 80
"pods": 28
What k8s version are you using (kubectl version)?
kubectl version Output
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.2", GitCommit:"faecb196815e248d3ecfb03c680a4507229c2a56", GitTreeState:"clean", BuildDate:"2021-01-13T13:28:09Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"windows/amd64"}

What did you do?
I copied the git repo and run the command to deploy it as deployment.

What did you expect to see?
it should have shown the nodes which is having resources less than 60% should consider as underutilized but it show as appropriate utilized
What did you see instead?
I0318 08:31:10.369732       1 nodeutilization.go:202] "Node is appropriately utilized" node="ip-10-0-1-10.ec2.internal" usage=map[cpu:1310m memory:8448Mi pods:6] usagePercentage=map[cpu:33.41836734693877 memory:27.47757580038873 pods:10.344827586206897]
I0318 08:31:10.369991       1 nodeutilization.go:199] "Node is overutilized" node="ip-10-0-1-23.ec2.internal" usage=map[cpu:1510m memory:1706Mi pods:19] usagePercentage=map[cpu:78.23834196891191 memory:11.310234594863086 pods:65.51724137931035]
I0318 08:31:10.370166       1 nodeutilization.go:199] "Node is overutilized" node="ip-10-0-1-239.ec2.internal" usage=map[cpu:1510m memory:1786Mi pods:19] usagePercentage=map[cpu:78.23834196891191 memory:11.840609019006724 pods:65.51724137931035]
I0318 08:31:10.370359       1 nodeutilization.go:199] "Node is overutilized" node="ip-10-0-1-40.ec2.internal" usage=map[cpu:1820m memory:1764Mi pods:19] usagePercentage=map[cpu:94.30051813471502 memory:11.694756052367223 pods:65.51724137931035]
I0318 08:31:10.370522       1 nodeutilization.go:199] "Node is overutilized" node="ip-10-0-2-188.ec2.internal" usage=map[cpu:1510m memory:1706Mi pods:20] usagePercentage=map[cpu:78.23834196891191 memory:11.310234594863086 pods:68.96551724137932]
I0318 08:31:10.370716       1 nodeutilization.go:199] "Node is overutilized" node="ip-10-0-2-197.ec2.internal" usage=map[cpu:1410m memory:1636Mi pods:18] usagePercentage=map[cpu:73.05699481865285 memory:10.846156973737402 pods:62.06896551724138]
I0318 08:31:10.370897       1 nodeutilization.go:199] "Node is overutilized" node="ip-10-0-2-214.ec2.internal" usage=map[cpu:1410m memory:3044Mi pods:13] usagePercentage=map[cpu:73.05699481865285 memory:20.180746838665435 pods:44.827586206896555]
I0318 08:31:10.371066       1 lownodeutilization.go:135] "Criteria for a node under utilization" CPU=70 Mem=60 Pods=10
I0318 08:31:10.371214       1 lownodeutilization.go:136] "Number of underutilized nodes" totalNumber=0
I0318 08:31:10.371366       1 lownodeutilization.go:149] "Criteria for a node above target utilization" CPU=80 Mem=80 Pods=28
I0318 08:31:10.371515       1 lownodeutilization.go:150] "Number of overutilized nodes" totalNumber=6

I did the changes suggested by you and it worked and getting the node underutilized but still pods are not being moved. Following is logs please have a look and suggest a fix for it
Uploading descheduler-7d8b9cb5b-7h25t.log…

@deenu7724 for some reason the link you shared doesn't work for me
It's possible that the pods might not be evictable for some reason (see https://github.com/kubernetes-sigs/descheduler#pod-evictions). If you run at log level v=4 it will print any reasons for that


opt let keywords list same with legacy planner

check from master
PR: #23632
commit id: b93a1a83a51c6bd9b31947106ad140f43deee0fb
Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Graphviz docker fix

Summary by CodeRabbit

New Features

Enhanced build process for the Python application with additional package support.
Introduced environment variables for improved configuration related to Graphviz.
Added installation of the pygraphviz library from GitHub for specific version control.

Bug Fixes

Updated version of the langchain-groq package to ensure compatibility and access to new features.

lgtm @mdmohsin7 🚀


Update docker images

What does this PR do?
Updates docker image to use latest CUDA version.
cc @pacman100 still one test failure:
FAILED tests/deepspeed/test_deepspeed.py::DeepSpeedConfigIntegration::test_prepare_deepspeed_custom_optimizer_custom_scheduler - AssertionError: False is not true

Fixes # (issue)
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[x] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@SunMarc

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


BINARY MIN TPP

We need to add a binary min TPP

@egeor : I think this was implemented, wasn't it?

Yes


Navigation layouts, Menu Icon

Why is the material design menu icon not visible / editable in the HTML, here.  The issue is that when css is applied to vertical align the material design icons, the menu icon is also affected and thrown off of alignment.

for support question use StackOverflow. Using the material-design-lite and any other applicable tags to get the best support in implementing MDL in projects.

I have to agree with @hebbet. This is obviously support as it is working on the demo. The guys over at StackOverflow are really helpful, though. Give them a try :)