Uncaught TypeError: Cannot read property 'prototype' of undefined

thanks for help
Describe the bug
when i add the fabric module  and  run dev again, this error is occurred.
Reproduction
https://github.com/lvhaohua/fabricjs-react-vite
System Info

vite version: 2.0.0-beta.12
Operating System:  macOS 11.1  20C69
Node version: 14.4.0
Package manager (npm/yarn/pnpm) and version: yarn

Logs
some warning when 'yarn dev':
[plugin:vite:resolve] externalized node built-in "events" to empty module. (imported by: /Users/haohua/Canvas/canvas-hua/node_modules/jsdom/lib/jsdom/virtual-console.js)
[plugin:vite:resolve] externalized node built-in "events" to empty module. (imported by: /Users/haohua/Canvas/canvas-hua/node_modules/jsdom/lib/jsdom/virtual-console.js) (x2)
[plugin:vite:resolve] externalized node built-in "vm" to empty module. (imported by: /Users/haohua/Canvas/canvas-hua/node_modules/jsdom/lib/jsdom/browser/Window.js)
[plugin:vite:resolve] externalized node built-in "vm" to empty module. (imported by: /Users/haohua/Canvas/canvas-hua/node_modules/jsdom/lib/jsdom/browser/Window.js) (x2)
[plugin:vite:resolve] externalized node built-in "fs" to empty module. (imported by: /Users/haohua/Canvas/canvas-hua/node_modules/jsdom/lib/jsdom/browser/resources/resource-loader.js)

Could I get some more info about the fix here? I'm getting similar warnings importing Firepad, so is this the usual for cjs modules?

Could I get some more info about the fix here? I'm getting similar warnings importing Firepad, so is this the usual for cjs modules?

It's the same problem. (fixed in beta.31)

It's the same problem. (fixed in beta.31)

Same error here:

vite version: 2.0.0-beta.36

Operating System: macOS 11.1

Node version: 14.15.4

Package manager (npm/yarn/pnpm) and version: yarn

Logs
[plugin:vite:resolve] externalized node built-in "events" to empty module. (imported by: /Users/eduardoliron/Sites/rxdb-hasura-vue3/node_modules/pouchdb-replication/lib/index.es.js)
[plugin:vite:resolve] externalized node built-in "events" to empty module. (imported by: /Users/eduardoliron/Sites/rxdb-hasura-vue3/node_modules/pouchdb-core/lib/index.es.js)
[plugin:vite:resolve] externalized node built-in "events" to empty module. (imported by: /Users/eduardoliron/Sites/rxdb-hasura-vue3/node_modules/pouchdb-utils/lib/index-browser.es.js)

Same error here:

vite version: 2.0.0-beta.36

Operating System: macOS 11.1

Node version: 14.15.4

Package manager (npm/yarn/pnpm) and version: yarn

Logs
[plugin:vite:resolve] externalized node built-in "events" to empty module. (imported by: /Users/eduardoliron/Sites/rxdb-hasura-vue3/node_modules/pouchdb-replication/lib/index.es.js)
[plugin:vite:resolve] externalized node built-in "events" to empty module. (imported by: /Users/eduardoliron/Sites/rxdb-hasura-vue3/node_modules/pouchdb-core/lib/index.es.js)
[plugin:vite:resolve] externalized node built-in "events" to empty module. (imported by: /Users/eduardoliron/Sites/rxdb-hasura-vue3/node_modules/pouchdb-utils/lib/index-browser.es.js)


feat: added useCursors and maxCacheSizeConfig as config params

PR Checklist

[x] Brief description of changes
[x] Links to any relevant issues
[x] Required status checks are passing
[x] User cases if changes impact the user's experience
[x] @mention a maintainer to request a review

Good point, I can read from that instead of the window

@sedghi ready for your review


Google accounts authorization error

Clicking on the 'Sign in with Google' button to upload images brings up a new window with the error: Error 400: redirect_uri_mismatch and the text:
"The JavaScript origin in the request, https://weed-ai.sydney.edu.au, does not match the ones authorized for the OAuth client. Visit https://console.developers.google.com/apis/credentials/oauthclient/${your_client_id}?project=${your_project_number} to update the authorized JavaScript origins."
Could be due to new URL?

Yes it is. Assigning to Elevn.

Seems to be working now, thanks @ElevnLi


Largest Sum Contiguous Subarray in Java

Largest Sum Contiguous Subarray in Java
Assigned Issue Number?
#119
Language Opted?
Java
Number of files added or updated?
1
Name of these files?
Data_Structures => Array => Largest_Sum_Contiguous_Subarray => Largest Sum Contiguous Subarray.java
Checklist

[x] I was assigned for this otherwise my PR will be rejected.
[x] I've read the contribution guidelines.
[x] I've referred the correct issue number.
[x] I've filled up this entire template correctly.

:star2: this repository and support.

Have to resolve an issue

Have to resolve an issue

@sanskriti0512 👍🏼


youtube video fails. https://www.youtube.com/watch?v=yhXHH2sZlQU

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2019.04.24. If it's not, read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2019.04.24

Before submitting an issue make sure you have:

[x] At least skimmed through the README, most notably the FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones
[x] Checked that provided video/audio/playlist URLs (if any) are alive and playable in a browser

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

youtube-dl -f 140 https://youtu.be/yhXHH2sZlQU --verbose
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'-f', u'140', u'https://youtu.be/yhXHH2sZlQU', u'--verbose']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2019.04.17
[debug] Python version 2.7.15 (CPython) - Linux-4.18.19-100.fc27.x86_64-x86_64-with-fedora-27-Twenty_Seven
[debug] exe versions: ffmpeg 3.3.9, ffprobe 3.3.9
[debug] Proxy map: {}
[youtube] yhXHH2sZlQU: Downloading webpage
[youtube] yhXHH2sZlQU: Downloading video info webpage
ERROR: yhXHH2sZlQU: "token" parameter not in video info for unknown reason; 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 796, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 529, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1693, in _real_extract
    video_id=video_id)
ExtractorError: yhXHH2sZlQU: "token" parameter not in video info for unknown reason; 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.
...
<end of log>

Unable to download this youtube video.

forgot to reopen the terminal...my bad. Thanks!

forgot to reopen the terminal after updating to the last version...my bad. Thanks!


auth module - Intensive blocking

Hello,
I'm trying to use the Tidal Web SDK for the first time, more precisely the "@tidal-music/auth" module. Using the example available in the "/examples" folder (I use pnpm and Vite.js) and taking care to fill in my own "clientId" and "clientSecret", at login time I have to validate a captcha, which I do, then I get blocked for some reason I don't know.

import { finalizeLogin, init, initializeLogin, credentialsProvider, logout } from "@tidal-music/auth";

// In my application, this information is present, and it works well with Tidal's rest api.
const CLIENT_ID = "";
const CLIENT_SECRET = "";

window.addEventListener("load", () => {
	const form = document.getElementById("loginRedirectForm");
	const logoutButton = document.getElementById("logoutBtn");

	form?.addEventListener("submit", (event) => {
		submitHandler(event).catch((error) => console.error(error));
	});

	logoutButton?.addEventListener("click", () => {
		logout();
		window.location.reload();
		localStorage.clear();
	});

	loadHandler().catch((error) => console.error(error));
});

const submitHandler = async (event: SubmitEvent) => {
	event.preventDefault();

	await init({
		clientId: CLIENT_ID,
		clientSecret: CLIENT_SECRET,
		credentialsStorageKey: "tidal",
	});

	const loginUrl = await initializeLogin({ redirectUri: "http://localhost:5173/user.html" });

	window.open(loginUrl);
};

const loadHandler = async () => {
	const clientId = localStorage.getItem("clientId");
	const redirectUri = localStorage.getItem("redirectUri");
	const form = document.getElementById("loginRedirectForm")!;

	if (clientId && redirectUri) {
		form.style.display = "none";

		await init({
			clientId,
			clientSecret: CLIENT_SECRET,
			clientUniqueKey: "test",
			credentialsStorageKey: "loginRedirect",
		});

		if (window.location.search.length > 0) {
			await finalizeLogin(window.location.search);
			window.location.replace("/index.html");
		} else {
			await credentialsProvider.getCredentials();
		}
	}
};

Hey, and thanks for reporting, one possible cause of this can be if you have the browser developer tools open while logging in, our captcha tool is sensitive to that. Hope that helps :-)
If not, we'd need your full IP address to look in the logs if there is more information on why you got blocked.

With or without open development tools, unfortunately the same problem remains.
IP : <IP_ADDRESS>

Hé, et merci pour le signalement, une cause possible de cela peut être si les outils de développement du navigateur sont ouverts lors de la connexion, notre outil captcha y est sensible. J'espère que cela pourra aider :-)
Sinon, nous aurions besoin de votre adresse IP complète pour rechercher dans les journaux s'il y a plus d'informations sur la raison pour laquelle vous avez été bloqué.

Hey, and thanks for reporting, one possible cause of this can be if you have the browser developer tools open while logging in, our captcha tool is sensitive to that. Hope that helps :-)
If not, we'd need your full IP address to look in the logs if there is more information on why you got blocked.

With or without open development tools, unfortunately the same problem remains.
IP : <IP_ADDRESS>

We will need to investigate some more, if we can tweak the rules here a bit, will hopefully know more next week :-)

We will need to investigate some more, if we can tweak the rules here a bit, will hopefully know more next week :-)

any news ?

Sorry for the delay, we are still in discussions with our security partners on how we can best detect traffic like this (and separate it from the bot traffic we want to block). Hope to have better news soon!

Hello, still no news? Do you know what the problem is exactly?

Hey, so the problem is that developer traffic can look suspiciously much like automated bot traffic to our bot-detection system. There is no quick solution to that, but we are looking into ways that should allow us to "allow-list" developers for limited periods of time.
In the meantime, if you try again now it might work better, as the blocking is only temporary. And please ensure you do not have the browser developer tools open while logging in, as that will block you :-)


Why I didn't receive push notification when app is closed?

I didn't receive any push notification when the application is closed.
Did I missed any configuration?
Please kindly advice. Thank you!

Does your APNS message have the content-available flag set?

@madebyais
Is this for Android or for iOS?
For Android a similar issue is discussed in #1, can you please take a look?
For iOS - do you have allowed the alert/banner and the notifications at all for the app?

@vbresults @AntonDobrev
This is for android. Thank you @AntonDobrev , I'll take a look on it.


Adds Serbian language support to the app

Hi Sarah,
Happy New Year!
This PR should add Serbian language support to this great app that you created. The changes are done both in the store and locale, by creating a new folder called /sr for Serbian i18n.
This should be fine for starters, however, if I missed anything, please let me know.
Thanks!

Thank you so much! Happy new year! 🎉


My page is empty!!!

I did all the steps provided and I got the domain working " http://abdelrahman-mahmoud.me/ " but the page has no content. When I run npm start it works on my local machine but when I open the index.html page alone it doesn't work!!!
.
.
Any suggestions ??!!

Opening index.html directly in a browser won't load the scripts - it must be served from a sever.

What about the domain?

Sorry, couldn't say without seeing your code.

The error in the console says  Failed to load resource: the server responded with a status of 404 (Not Found)  and http://abdelrahman-mahmoud.me/build/bundle.js file is not found!!!

Make sure build/bundle.js is committed and pushed to your repository (run $ npm run build to create it). Other than that it could be any number of things. Ask a friend to look at your code.


Feature/GitHub dependency review test

Description

Test #1746 with changes.
Check-List

[ ] All Acceptance criteria of user story are met
[ ] Accessibility was considered and tested (On UI Change)
[ ] JUnit tests are written (60% CodeCov)
[ ] Internal Review is maintained
[ ] Documentations external and internal are completed
[ ] Smoketest successful (Manual E2E-Test depending on Change)
[ ] No waste on Branch left (e.g. console.logs)
[ ] Board is up-to-date
[ ] Internal Services / Artifacts updated (Depending on Change - See Dependency Graph
[ ] Openshift environments are prepared (Secrets, etc.) and release-issue is maintained

Just for test


Showcase how to call public nlm COM APIs

Can you (in this PR or a follow up) update the "LatestBuild" with this new binary?
Or if you are motivated, moving those to an artifact in the "release" section of Github could be even better 😊


(Bug) #1940 FV - Intro screen: when clicking "learn more" button it shows an empty screen

Description
Make FV learn more open in a new tab. Added new optional environment variable.
About #1940
New Environment Variable
Link to open description about face verification usage
Optional
Default value: https://medium.com/gooddollar/gooddollar-identity-pillar-balancing-identity-and-privacy-part-i-face-matching-d6864bcebf54
REACT_APP_FV_LEARN_MORE_URL=
How Has This Been Tested?
FV Learn more button should open new tab with medium.com post about GoodDollar's FV.
Checklist:

[x] PR title matches follow: (Feature|Bug|Chore) Task Name
[x] My code follows the style guidelines of this project
[x] I have followed all the instructions described in the initial task (check Definitions of Done)
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have added reference to a related issue in the repository
[x] I have added a detailed description of the changes proposed in the pull request. I am as descriptive as possible, assisting reviewers as much as possible.
[ ] I have added screenshots related to my pull request (for frontend tasks)
[ ] I have pasted a gif showing the feature.
[x] @mentions of the person or team responsible for reviewing proposed changes

are PrivacyArticle doesn't uses some config variable to display Medium's page ? we should check it and use it too
pls check all PrivacyArticle usage and updage them to openURL
pls check probably we're also showing other medium articles - they also should be opened in a new tabs

the link was hardcoded to the iframe element of the PrivacyArticle screen. There was not config value. So I added env var to have possibility change it when needed.

i've added new env var to the Netlify

pls re check my changes

Everything is ok


Why build in the source dir?

"binaryDir": "${sourceDir}/builds/${presetName}",

Why do you put the build directory inside the source directory instead of doing an out-of-tree build?
I thought best practices recommended out of tree builds.

@LegalizeAdulthood  This template proposes an out-of-tree build (they are indeed side by side), as there is no mixture of CMakeCache.txt (and all the generated build-system files) with source files, e.g. you can delete the builds directory and no source file is going to be deleted.
Let me know your feedback about this, and please create a pull request with the desired approach as new ways of doing things are always welcome.

I'm not sure why you say they are "side by side" when the preset is putting the binary directory as a subdirectory of sourcedir as shown in the snippet I quoted above.  Isn't ${sourceDir} the top-level source directory from my git checkout?

@LegalizeAdulthood CMAKE_SOURCE_DIR and CMAKE_BINARY_DIR are not the same, hence this is not a in-source-build.
It is useful to list the benefits of this solution:

it allows to have multiple binary directories, that is multiple build configurations for a single source tree:

each binary directory gets a different CMakeCache.txt, that is can be configured with totally different values.
each binary directory is completely isolated from the others.

a binary directory could be deleted any time, no harm and no leftover would be there, and it helps to maintain a clean source tree.

And downsides:

the .gitignore file needs to be augmented to ignore the subtree of binary directories.
anything else?

@LegalizeAdulthood I think there are multiple similar ways to solve a problem, so I welcome you to submit a PR with your proposal.

it allows to have multiple binary directories
a binary directory could be deleted any time

These benefits aren't because you've nested the binary directory in the source directory, it's simply because they aren't the same directory.
I've never seen anyone define "out of tree builds" as just saying that CMAKE_SOURCE_DIR and CMAKE_BINARY_DIR don't have the same value.  "Out of tree" means literally that -- the build directory isn't in the source tree, hence no need to modify the .gitignore, etc.
The Getting Started page in cmake docs initially implies that "out of source" is just considered having different values as you say, but if you look at the Makefile generator example at the bottom of the page, they are obviously showing the build directory as a peer to the source directory and not as a child:
# With source code in the directory MyProject
# to build MyProject-debug create that directory, cd into it and
ccmake ../MyProject -DCMAKE_BUILD_TYPE=Debug
# the same idea is used for the release tree MyProject-release
ccmake ../MyProject -DCMAKE_BUILD_TYPE=Release

...which is how I always envisioned "out of source" to literally mean that -- no build artifacts are within the source directory tree whatsoever.  To visualize it more explicitly, it looks like this:
MyProject/
MyProject/CMakeLists.txt
MyProject/main.cpp
MyProject/...
debug/
debug/CMakeCache.txt
debug/main.o
debug/...
release/
release/CMakeCache.txt
release/main.o
release/...

You are then relieved from having to mark these in-source-tree build directories as being ignored by whatever version control system you're using.

@LegalizeAdulthood I see you are not satisfied by my answers and I am still open to discuss this further if you deem so.
As always I am interested in receiving contributions for a better C++ project template, do not hesitate to open a PR on this repository, thank you.

@LegalizeAdulthood closing this stale discussion.


This commit fixes 3 things.

Handle textDocument/completion result when result is CompletionItem[].
Before this commit, it was assumed textDocument/completion result would be type CompletionList or null. See https://microsoft.github.io/language-server-protocol/specification#completion-request-leftwards_arrow_with_hook

Handle null trigger characters for signatureHelp and completion.
Client would error if a language server registered SignatureHelp or Completion with no trigger characters. Example language server response that leads to an error:

Sent: {"id":9,"jsonrpc":"2.0","method":"client/registerCapability","params":{"registrations":[{"id":"43f30805-c2d9-4091-9693-68208feb617d","method":"textDocument/signatureHelp","registerOptions":{"triggerCharacters":null,"documentSelector":[{"pattern":"**/*.cs"},{"pattern":"**/*.csx"}]}}]}}

Some language servers (omnisharp) send a hover result with a null object in the content array. Added a return to handle this case.

Example
Sent: {"jsonrpc":"2.0","id":29,"result":{"contents":[null,null]}}

Hi Elayne! Thanks so much for sending this PR. I’ll take a look over the
weekend or Monday and see if this makes sense :)
On Wed, May 15, 2019 at 18:00 ElayneB<EMAIL_ADDRESS>wrote:

Handle textDocument/completion result when result is CompletionItem[].
Before this commit, it was assumed textDocument/completion result
would be type CompletionList or null. See
https://microsoft.github.io/language-server-protocol/specification#completion-request-leftwards_arrow_with_hook
2.
Handle null trigger characters for signatureHelp and completion.
Client would error if a language server registered SignatureHelp or
Completion with no trigger characters. Example language server response
that leads to an error:

Some language servers (omnisharp) send a hover result with a null
object in the content array. Added a return to handle this case.

Example
Sent: {"jsonrpc":"2.0","id":29,"result":{"contents":[null,null]}}

You can view, comment on, or merge this pull request online at:
https://github.com/wylieconlon/lsp-editor-adapter/pull/19
Commit Summary

This commit fixes 3 things.

File Changes

M src/codemirror-adapter.ts
https://github.com/wylieconlon/lsp-editor-adapter/pull/19/files#diff-0
(2)
M src/ws-connection.ts
https://github.com/wylieconlon/lsp-editor-adapter/pull/19/files#diff-1
(12)

Patch Links:

https://github.com/wylieconlon/lsp-editor-adapter/pull/19.patch
https://github.com/wylieconlon/lsp-editor-adapter/pull/19.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wylieconlon/lsp-editor-adapter/pull/19?email_source=notifications&email_token=AAFCW24DMQRKWMAFNFLP24DPVSBZBA5CNFSM4HNHKH42YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4GUBBN2Q,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFCW2Z7J5QNPPVOYDQQLNTPVSBZBANCNFSM4HNHKH4Q
.


Debug the langchain llms model

/approve

/lgtm

I'm also on investigating on how to make langchain works


Add icons style

Added rules for sizing the icon, icons as black on a light background and icons as white on a dark background.

Hi, sorry for the late response and thanks for the PR. Currently this package only provides the minimum required css to load and render the fonts. Font size and colors are application specific so I don't want to include them in the main css file and currently there are no plans to include them in this package. In future if I decide to include them (in a separate optional file), I will let you know.


Bug in installer - pip install pyjq

In Python 3.7 I get a consistent failure trying to install this package. We've also built a test server to verify that a clean Python image does not resolve the problem
C:\temp>pip install pyjq
Collecting pyjq
  Using cached https://files.pythonhosted.org/packages/66/74/7f5c7789c894a943088040a0c148f7ac5daddf4096cf820e3ff15ae75ea0/pyjq-2.3.1.tar.gz
Requirement already satisfied: six in c:\python\python37-32\lib\site-packages (from pyjq) (1.11.0)
Installing collected packages: pyjq
  Running setup.py install for pyjq ... error
    Complete output from command c:\python\python37-32\python.exe -u -c "import setuptools, tokenize;__file__='C:\\Users\\user\\AppData\\Local\\Temp\\pip-install-5k46zhvg\\pyjq\\setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record C:\Users\user\AppData\Local\Temp\pip-record-d46h9me8\install-record.txt --single-version-externally-managed --compile:
    running install
    running build
    running build_py
    creating build
    creating build\lib.win32-3.7
    copying pyjq.py -> build\lib.win32-3.7
    running build_ext
    error: [WinError 2] The system cannot find the file specified

    ----------------------------------------
Command "c:\python\python37-32\python.exe -u -c "import setuptools, tokenize;__file__='C:\\Users\\user\\AppData\\Local\\Temp\\pip-install-5k46zhvg\\pyjq\\setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record C:\Users\user\AppData\Local\Temp\pip-record-d46h9me8\install-record.txt --single-version-externally-managed --compile" failed with error code 1 in C:\Users\user\AppData\Local\Temp\pip-install-5k46zhvg\pyjq\

C:\temp>

pyjq doesn't work on Windows.
See: https://github.com/doloopwhile/pyjq/issues/9


Using --break-on-reject Kills Parent Processes

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2023.02.17 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
I have a bunch of YoutTube channels that I archive.  Each channel has a dedicated bash script sitting in a directory.  I have a cron job which runs every night that simply executes all .sh files in that directory.  To prevent yt-dlp from cycling through 1000's of videos each night, I have a filter that only looks at now-2 days of videos; and I add the --break-on-reject to stop yt-dlp after it hits that limit.
Unfortunately, for some reason, when using --break-on-reject, the child process (in this case, the cron job) gets killed as well; so only the first script in the directory is ever executed.  As shown in the verbose output, this can be reproduced manually by just trying to execute all shell scripts in the directory.
I would expect that the --break-on-reject argument would only kill yt-dlp and not the parent process as well.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
root@ytdlpbox:~/ytdlpscripts# ./*.sh
*******************************************
DOWNLOADING ANONYMOUS ALLIGATOR
*******************************************
[debug] Command-line config: ['--break-on-reject', '-vU', '--datebefore', 'now', '--dateafter', 'now-2days', 'https://www.youtube.com/@anongator/videos']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2023.02.17 [a0a7c01] (zip)
[debug] Python 3.9.5 (CPython x86_64 64bit) - Linux-5.11.0-49-generic-x86_64-with-glibc2.33 (OpenSSL 1.1.1j  16 Feb 2021, glibc 2.33)
[debug] exe versions: ffmpeg 4.3.2-0, ffprobe 4.3.2-0, phantomjs 2.1.1
[debug] Optional libraries: certifi-2020.06.20, secretstorage-3.3.1, sqlite3-2.6.0
[debug] Proxy map: {}
[debug] Loaded 1782 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2023.02.17, Current version: 2023.02.17
yt-dlp is up to date (2023.02.17)
[youtube:tab] Extracting URL: https://www.youtube.com/@anongator/videos
[youtube:tab] @anongator/videos: Downloading webpage
[debug] [youtube:tab] Selected tab: 'videos' (videos), Requested tab: 'videos'
[download] Downloading playlist: anonymous alligator - Videos
[youtube:tab] UCsLUcgc354xDMBiDIXZzNdg page 1: Downloading API JSON
[youtube:tab] UCsLUcgc354xDMBiDIXZzNdg page 2: Downloading API JSON
[youtube:tab] Playlist anonymous alligator - Videos: Downloading 89 items of 89
[download] Downloading item 1 of 89
[youtube] Extracting URL: https://www.youtube.com/watch?v=FAyT1VfUUlI
[youtube] FAyT1VfUUlI: Downloading webpage
[youtube] FAyT1VfUUlI: Downloading android player API JSON
[debug] Loading youtube-nsig.9419f2ea from cache
[debug] [youtube] Decrypted nsig bSU0PiYYkcatgeAb7 => b6bBnhXwZAeGMw
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[download] 2023-02-19 upload date is not in range 2023-02-22 - 2023-02-24
[info] Encountered a video that did not match filter, stopping due to --break-on-reject
Aborting remaining downloads
[debug] Command-line config: ['--break-on-reject', '-vU', '--datebefore', 'now', '--dateafter', 'now-2days', 'https://www.youtube.com/@anongator/shorts']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2023.02.17 [a0a7c01] (zip)
[debug] Python 3.9.5 (CPython x86_64 64bit) - Linux-5.11.0-49-generic-x86_64-with-glibc2.33 (OpenSSL 1.1.1j  16 Feb 2021, glibc 2.33)
[debug] exe versions: ffmpeg 4.3.2-0, ffprobe 4.3.2-0, phantomjs 2.1.1
[debug] Optional libraries: certifi-2020.06.20, secretstorage-3.3.1, sqlite3-2.6.0
[debug] Proxy map: {}
[debug] Loaded 1782 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2023.02.17, Current version: 2023.02.17
yt-dlp is up to date (2023.02.17)
[youtube:tab] Extracting URL: https://www.youtube.com/@anongator/shorts
[youtube:tab] @anongator/shorts: Downloading webpage
[debug] [youtube:tab] Selected tab: 'shorts' (shorts), Requested tab: 'shorts'
[download] Downloading playlist: anonymous alligator - Shorts
[youtube:tab] Playlist anonymous alligator - Shorts: Downloading 33 items of 33
[download] Downloading item 1 of 33
[youtube] Extracting URL: https://www.youtube.com/shorts/0felMggsm4Y
[youtube] 0felMggsm4Y: Downloading webpage
[youtube] 0felMggsm4Y: Downloading android player API JSON
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[download] 2023-02-18 upload date is not in range 2023-02-22 - 2023-02-24
[info] Encountered a video that did not match filter, stopping due to --break-on-reject
Aborting remaining downloads
[debug] Command-line config: ['--break-on-reject', '-vU', '--datebefore', 'now', '--dateafter', 'now-2days', 'https://www.youtube.com/@anongator/streams']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2023.02.17 [a0a7c01] (zip)
[debug] Python 3.9.5 (CPython x86_64 64bit) - Linux-5.11.0-49-generic-x86_64-with-glibc2.33 (OpenSSL 1.1.1j  16 Feb 2021, glibc 2.33)
[debug] exe versions: ffmpeg 4.3.2-0, ffprobe 4.3.2-0, phantomjs 2.1.1
[debug] Optional libraries: certifi-2020.06.20, secretstorage-3.3.1, sqlite3-2.6.0
[debug] Proxy map: {}
[debug] Loaded 1782 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2023.02.17, Current version: 2023.02.17
yt-dlp is up to date (2023.02.17)
[youtube:tab] Extracting URL: https://www.youtube.com/@anongator/streams
[youtube:tab] @anongator/streams: Downloading webpage
[debug] [youtube:tab] Selected tab: 'streams' (live), Requested tab: 'streams'
[download] Downloading playlist: anonymous alligator - Live
[youtube:tab] Playlist anonymous alligator - Live: Downloading 4 items of 4
[download] Downloading item 1 of 4
[youtube] Extracting URL: https://www.youtube.com/watch?v=2Axu8Bd2FQw
[youtube] 2Axu8Bd2FQw: Downloading webpage
[youtube] 2Axu8Bd2FQw: Downloading android player API JSON
[debug] [youtube] Extracting signature function js_9419f2ea_102
[debug] Loading youtube-sigfuncs.js_9419f2ea_102 from cache
[debug] Loading youtube-nsig.9419f2ea from cache
[debug] [youtube] Decrypted nsig _3Ohb0cw_Mk0Y52nD => eSmr5vKXjrHZZQ
[debug] [youtube] Extracting signature function js_9419f2ea_106
[debug] Loading youtube-sigfuncs.js_9419f2ea_106 from cache
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, vcodec:vp9.2, channels, acodec, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), channels, acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[download] 2023-01-12 upload date is not in range 2023-02-22 - 2023-02-24
[info] Encountered a video that did not match filter, stopping due to --break-on-reject
Aborting remaining downloads
root@ytdlpbox:~/ytdlpscripts#

yt-dlp cannot influence any parent processes. When downloads are aborted, the exit code is non-0. Your script probably has a bug that causes it to crash when that happens

I'm open to suggestions on how to improve this; since I can't find any reason why a sub-process exiting non-0 would cause the parent to stop.  I've put the script below.
#!/bin/bash

echo "*******************************************"
echo "DOWNLOADING ANONYMOUS ALLIGATOR"
echo "*******************************************"

cd "/pineridge/Media/Archived YouTube Content/Anonymous Alligator"
yt-dlp --break-on-reject --datebefore now --dateafter now-2days https://www.youtube.com/@anongator/videos
yt-dlp --break-on-reject --datebefore now --dateafter now-2days https://www.youtube.com/@anongator/shorts
yt-dlp --break-on-reject --datebefore now --dateafter now-2days https://www.youtube.com/@anongator/streams

Moving my upstream script to use a for-loop instead of an *.sh seems to fix this.  I still don't understand it; but whatever - closing this one as "no idea."

root@ytdlpbox:~/ytdlpscripts# ./*.sh

If you are trying to run the scripts with ./*.sh, that is the problem. Using a glob like that will only run the 1st script in the directory, with each subsequent filename passed as an argument to that 1st script


Circular ROI extraction: unexpected behavior

Describe the bug
ROI extraction is different than the definition.
In the first image below the circle ROI is defined very close to the central ring. When extraction, see the second image, we can still a little portion of the second ring what is ununexpected !

Thanks for the feedback.
I was almost tempted to answer that it's a feature, not a bug 😉, but at least this is the intended behavior for now even if it may be seen as inappropriate.
The current behavior of the circular ROI is to be able to do the computations (all features in the "Computation" menu) only in the area of interest (inside the circle). However, when extracting the ROI, we extract the smallest square area around the circle.
Actually, there might be an issue here because at some point we used to keep the circular ROI in the extracted image, but we removed this feature: perhaps we should reimplement it.
An alternative solution could be to replace the pixel values outside the ROI area by a certain value (which would be asked to the user: 0, by default for example).

I just reviewed the associated code and indeed this is a bug! The circular ROI should be kept in the newly created image.

For information, this is happening only when the "Extract all regions of interest into a single image object" is checked.


devshell: add python LSP

Adds required dependencies for using pylsp with a nix devshell in neovim.

I'm not in favour of this. You shouldn't force me to use that LSP, if you want to add that to a nix flake put it somewhere else!

This doesn't force you to use this LSP, if you have a different one configured in your editor, it'll use that. In fact, these packages don't do anything unless you've configured your editor to use this python LSP. Or am I misunderstanding something about your setup here?


Improve deployment process, reduce the time cost

It's a long run task, put it here for tracking.
Will need to break into in detail tasks later.

Converting the issue to Epic, so we can break it down to executable sub issues.

closed and track in #4022


How to make tests being stateless?

💬 Questions and Help
I'm using just via react-scripts (run tests by react-scripts test command) for a TypeScript project. Also I'm using axios library for client http requests and axios-mock-adapter.
So a test looks like this:
import 'jest';
import React from 'react';
import MockAdapter from 'axios-mock-adapter';
// … also "fixtureData" which is just a mocked json
// … also "instance" which is an AxiosInstance

it('should render correctly', () => {
  const mock = new MockAdapter(instance);
  mock.onGet('/some-api-endpoint').reply(200, fixtureData);
  expect(render(smth)).toMatchSnapshot();
});

describe('Foo', () => {
  it('bar', async () => {
    // const mock = new MockAdapter(instance);
    // mock.onGet('/some-api-endpoint').reply(200, fixtureData);
    const foo = render(smth);
    // … further testing
  });
});

As you can see mocking of the axios instance is commented in second test (bar) but the test passes, and if I provide incorrect fixtureData, both tests will fail which means tests environments interfere which each other and the tests aren't pure and are stateful. I've tried to run it with --clearMocks but it doesn't change anything (I assumed this option for internal jest mocking mechanisms only).
Is there any way to run each test with completely new independent and isolated environment?

Use https://jestjs.io/docs/en/configuration#resetmocks-boolean or function equivalent.

@thymikee Sad but it doesn't help, it seems it doesn't change anything. I've added these lines to package.json:
  "jest": {
    "resetMocks": true
  }

I've verified that this option is read by trying to run tests with "resetMocks": 123 and getting type check error.

Just for those who fill find this issue:
This issue is closed but it haven't been resolved.
There's still no environment isolation inside a single test file. At least I haven't found a way to do so.

P.S. In this particular case with that particular library used it could be fixed like this:
const mock = new MockAdapter(instance); // at the top level of scope

beforeAll(() => {
  jest.resetAllMocks();
  mock.reset();
});

‼ But this doesn't solve the problem with stateful tests ‼


SkipIfMentioned.java:25-29: apply SkipIfMentioned too...

The puzzle 85-d5fc9715 from #85 has to be resolved:
https://github.com/tracehubpm/code-review-action/blob/ce2df04b0302c910f05f76e68298764ef0d09d43/src/main/java/git/tracehub/codereview/action/SkipIfMentioned.java#L25-L29
The puzzle was created by @h1alexbel on 09-May-24.
Estimate: 15 minutes,  role: DEV.
If you have any technical questions, don't ask me, submit new tickets instead. The task will be "done" when the problem is fixed and the text of the puzzle is removed from the source code. Here is more about PDD and about me.

@l3r8yJ do you want to take it?

@h1alexbel sure

@l3r8yJ okay, assigned

@0pdd 2 puzzles #109, #110 are still not solved.

@0pdd the puzzle #109 is still not solved; solved: #110.

@0pdd all 2 puzzles are solved here: #109, #110.


Enabling caching on view API

WHAT DOES THIS PR DO?

[x] Upgrades packages
[x] Enables caching and scheduling tasks on the view microservice

HOW DO I TEST OUT THIS PR?
Follow instructions in the readme.md file
WHICH ENDPOINTS SHOULD BE READY FOR TESTING?:
API Docs

@Baalmart @123MwanjeMike any reservations??

@Baalmart @123MwanjeMike any reservations??

None from my end @NoahNsimbe


Add some clarifications to the kubefed doc.

cc @allannaim @kubernetes/sig-federation-pr-reviews

This change is

LGTM, thanks!


Handle ambiguities introduced by stack association

update-buildpack/delete-buildpack now fail if the specified buildpack name is ambiguous
update-buildpack/delete-buildpack now accept [-s STACK] flag to disambiguate
create-buildpack removes stray buildpack records on buildpack-bits upload failure, which will eventually return errors when uploaded buildpack bits specify a stack which is not unique in combination with the buildpack name.

[#153256959]
Signed-off-by: Sam Coward<EMAIL_ADDRESS>Signed-off-by: Jackson Feeny<EMAIL_ADDRESS>Signed-off-by: Victoria Henry<EMAIL_ADDRESS>
What Need Does It Address?
In light of this cloud_controller_ng PR, future versions of CC will support multiple buildpacks with the same name as long as they have different stacks. In the lens of this change, this affects the following buildpack CLI commands:
update-buildpack/delete-buildpack: these operate on a specified buildpack (e.g. update-buildpack/delete-buildpack) because these commands currently accept the buildpack name as the sole means of indicating the specific buildpack.
This change will allow specifying the stack in addition to the buildpack's name with the -s flag, but will only be required if the name is not distinct.
create-buildpack: Since the stack associated with buildpacks is only known by CC after buildpack bits are uploaded, it's possible that the API will fail on the buildpack bits upload if it is discovered that the stack + buildpack name is not unique. This leaves a stray buildpack entry with a stack of unknown which requires manual intervention to delete.
This change will make the CLI clean up the stray record.
Possible Drawbacks
Unaware.
Why Should This Be In Core?
It's related to core commands (*-buildpack)
Description of the Change

BuildpackRepository findByName now returns AmbiguousModelError if it finds more than 1
BuildpackRepository now can findByNameAndStack
Update/DeleteBuildpack commands use findByNameAndStack with stack passed via -s flag
Update/DeleteBuildpack commands fail if findByName returns AmbiguousModelError
CreateBuildpack command now deletes buildpack if the upload fails

Alternate Designs
It's worth noting that UpdateBuildpack and DeleteBuildpack commands both have need to get a Buildpack, and that they do so by means of the specified buildpack name (and now, possible -s flag argument). They do this through different means; DeleteBuildpack interacts with BuildpackRepository directly and UpdateBuildpack is provided one via a BuildpackRequirement.
We initially sought to unify their use of a BuildpackRequirement, however we found that the Requirements mechanism takes away control of handling any errors generated by the requirement (they bubble up and always manifest as a command failure).
This seemed in opposition to what appears to be intentional effort in the DeleteBuildpack command to handle this and exit successfully with a warning instead. In light of this and not wanting to introduce any widespread architectural changes so we have not done said unification and have ensured the exit code behavior is not modified.
Applicable Issues
This change is part of a larger buildpacks story:
https://www.pivotaltracker.com/story/show/153256959
Other open PRs related to this:
https://github.com/cloudfoundry/cloud_controller_ng/pull/1064
https://github.com/cloudfoundry/capi-release/pull/75

Would it make sense for us to make some of these changes (ex. rename-buildpack and better error messages) in a second PR, given that the current PR strictly improves the behavior with the latest version of CAPI?
It seems like we're leaving more stuff broken for longer by blocking this PR on additional functionality.

@sclevine For adding -s to rename-buildpack and updating the text of the error messages, we're okay with a new PR.
For the other issues, we would like to have the changes addressed in order to merge.
I also updated my review comment to include an additional issue - the PR changes the idempotency of create-buildpack; that will also need to be fixed before we can merge this PR, as it is a breaking change.

@abbyachau @tjvman ready to merge

@tjvman I think we've made all the changes requested for this PR.

Apart from the ongoing delete-buildpack updates, the changes in this commit look good.
However, we want to point out that the behavior around attempting to create a buildpack with the same stack when it already exists is weird/pretty confusing, even if it's technically correct.
When attempting to create a buildpack / stack combination that already exists, we see the following warning the first time around:
± |idoru-buildpack-stack-assoc {2} U:2 ✗| → cf create-buildpack test /tmp/test-buildpack.zip 10
Creating buildpack test...
OK

Uploading buildpack test...
Done uploading
OK
Server error, status code: 422, error code: 290000, message: The buildpack name test is already in use for the stack cflinuxfs2
TIP: use 'cf update-buildpack' to update this buildpack

This exits 0, which is the expected behavior (though we prefer that the CC error be wrapped in a nicer warning message without server error).
When attempting to create a buildpack / stack combination that already exists a second time however, we see the following warning:
± |idoru-buildpack-stack-assoc {2} U:2 ✗| → cf create-buildpack test /tmp/test-buildpack.zip 10
Creating buildpack test...
OK
Buildpack test already exists without a stack
TIP: use 'cf delete-buildpack' to delete buildpack test without a stack

This happens because creating a buildpack with a stack is a two step process - per the doc, when buildpack records are first created the stack will be nil. Per the original PR comment, "the API will fail on the buildpack bits upload if it is discovered that the stack + buildpack name is not unique. This leaves a stray buildpack entry with a stack of unknown which requires manual intervention to delete."
It sounds like our team had pushed back on the part where we clean up the stray record, so technically it's true that "Buildpack test already exists without a stack'. But to a user, this message is unclear because they've been attempting to create a buildpack with a stack name this whole time.
Not sure if there's any action to be taken, but just want to call that out for discussion if needed.
cc @abbyachau

We agree that in the case where create-buildpack fails after creating the buildpack record, the best user experience would be for the CLI to remove the stray buildpack record. We had implemented this in the PR, but we were told to remove it. Happy to restore it if you'd prefer.

We have implemented the new delete behavior and added/corrected unit and integration tests for it.


landing page

As a user
I want to have a landing page
So that I know what to expect.

Acceptance criteria (ac)

[ ] there are a introduction with a slide effect
[ ] when the display is tapped(or clicked), the next step is displayed
[ ] there is a button on the page
[ ] when the start button is clicked, you get to the main page

tasks

[ ]  create a branch
[ ]  create a button
[ ]  install react-spring (for the slide effects)
[ ]  position the button on the page

Hi Omer,
I like your user story! I only have one typo: there is an introduction with a slide effect and not are a introduction with a slide effect. Only nit-picking. ;)
Happy hacking! 💪

Hi Mareike, thanks for the feedback. I've changed my mind :D
So I updated my user story again. Please let me know if something is missing

Hi Omer,
I just researched about the parallax effect and I'm looking forward to your implementation. :D
The user story is good! 👍 But the typo is not gone yet. ;)
Happy hacking! 🎶


Added Windows Server 2016 registry value information

Added Windows Server 2016 registry value information
Related to #6678
//cc @vivmishra

I think the best thing to do is to merge this now, @mairaw, and address the issue in a separate PR.


Restrict the start chars SPLIT_PATTERN can match

SPLIT_PATTERN has no preference for the order which it matches against characters when looking for frames. This can lead it to incorrectly matching against non-frame characters when the frames aren't encased in separators. This leads to unexpected behavior
For example
from fileseq import FileSequence
FileSequence("light1-1#.exr") # Succeeds
FileSequence("heavy1-1#.exr") # Fails with exception ParseException
FileSequence("heavy.1-1#.exr") # Succeeds

This patch restricts what SPLIT_PATTERN can start matching on (it has to be a number or negative number) to avoid incorrect matches on colon, comma and especially x and y

Hey thanks for catching this and providing a fix!


Modify how 'override' argument is implemented

The current implementation defines --override as the following:

If *.h or *.cpp file exists,
Compute MD5 of input file and compare with MD5 found in *.cpp file.
If MD5 compare is the same, skip file generation
Else, look for the --override flag for deciding if we should regenerate the output file.

This makes the --override flag useless if the MD5 in the cpp file is not changed while the content of the *.cpp file is changed.
The implementation should be changed as the following:

By default, the application stores the input file 'modified date' into the generated output files header.
If the output files exists and that 'modified date' in the generated files matches the intput files, then skip file regeneration (the resulting files will likely be the same which will trigger Visual Studio to rebuild the project)
If the --override flag is specified, then the application should not look for the 'modified date' value and regenerated the files anyway.

Note that implementing this will let the MD5 computation obsolete. The MD5 implementation may be set as deprecated.
The getMd5() api will also be broken.


fix(http)!: imaga Data URIs need to be a string

Discord expects that Data URIs get send as a string therefore we should take a &str accordingly.

Should a serialization test be added to (some?) of these?


chore: Bump chart and app versions

I wanna check out release workflow triggering and also release a chart with the 153 fix

Gonna abuse the bot here to get this one going 😅

/approve

/merge


Test exemption bot should not run on release branch PRs

See https://github.com/flutter/flutter/pull/100922

This is fixed (base on my latest cherrypicks)


Style: write test to check headers of IMPROVER Python modules

As a StaGE developer, I want an automated test to check the headers of my files so that I can be sure my code has the right license and header information.
Acceptance criteria:

Write automated test that checks for presence of coding utf8 and BSD 3-clause license info for Python modules under lib/improver/

Maybe use conn


adding 2 rebus

Associated Issue: #
Summary of Changes

change 1 Added rebus
change 2 Added rebus

Pull Request Test Coverage Report for Build 1030

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 87.143%

Totals

Change from base Build 937:
0.0%

Covered Lines:
158

Relevant Lines:
180

💛  - Coveralls


Fix issue on Android 8, 9, 10 that made checkNotifications always granted

Summary
There is an issue with android that are on os version < 10, when we call checkNotifications() method, the result is always 'granted'.
Test Plan
What's required for testing (prerequisites)?
Android with os version < 10
What are the steps to reproduce (after prerequisites)?
Call checkNotifications on RN, run on an android device with os version < 10, turn on the push notifs and see the result, turn off and see.
Compatibility
OS    Implemented
iOS          N/A
Android   ✅

[x] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Is it more accurate to say that this fix is just for the Android version range from O (8) to 10? But that it would work correctly from Marshmallow / 7 down and 10 and higher?

@mikehardy Indeed thanks, the fix is from 8 included.
It is working correctly from 10 and higher. I did not test on lower versions than 7 tho

Great - thanks for replying, that was mostly intended to check that I was reading it correctly, code review works best with more than one set of eyes since we humans are so unreliable. From the perspective of fixing a "hole" of versions between 7 and 10 not inclusive, it does seem to make sense


[General] Fil-Crypto datacenter hosts which are unresponsive

What do you need?
The following hosts appear unresponsive to SSH connection:
worker-gpu-3 (<IP_ADDRESS> )
worker-gpu-4 (<IP_ADDRESS>)
worker-gpu-6 (<IP_ADDRESS>)
Why do you need it?
Filecoin-crypto proofs development
Who is the DRI?
nemo, vmx, shawnrader, Artem, Jake
Team and command structure
fil-crypto
Estimated monthly cost
Systems are in-accessible by the team for development, benchmarking, and testing.
What else do we need to know?
This is impairing investigation of high-priority test failure: https://github.com/filecoin-project/rust-fil-proofs/issues/1647

I power-cycled this with IPMI.
@shawnrader you should be able to re-connect to these boxes now!


az cosmosdb database does not work with --key parameter

Describe the bug
The az cosmosdb database commands does works using --key parameter.
az cosmosdb database exists --db-name mydb --key "XXXX" --name mycosmosdb
This just happens after upgrade to azure-cli (2.0.38) or the latest 2.0.41
To Reproduce

Open command prompt
Sign in with Azure CLI 2.0
az login
Run any az cosmosdb database command:
az cosmosdb database exists --db-name mydb --key "XXXX" --name mycosmosdb
An error is displayed:
unsupported operand type(s) for +: 'NoneType' and 'str'
Traceback (most recent call last):
File "/opt/az/lib/python3.6/site-packages/knack/cli.py", line 197, in invoke
cmd_result = self.invocation.execute(args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 334, in execute
cmd.exception_handler(ex)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 96, in generic_exception_handler
chained_handler(ex)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 76, in chained_handler
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 71, in chained_handler
h(ex)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 86, in network_exception_handler
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 71, in chained_handler
h(ex)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 59, in unknown_server_failure_exception_handler
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 71, in chained_handler
h(ex)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 51, in invalid_arg_found_exception_handler
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 71, in chained_handler
h(ex)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 29, in resource_not_found_exception_handler
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 71, in chained_handler
h(ex)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/_exception_handler.py", line 21, in duplicate_resource_exception_handler
raise ex
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 311, in execute
result = cmd(params)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/commands/init.py", line 170, in call
return super(AzCliCommand, self).call(*args, **kwargs)
File "/opt/az/lib/python3.6/site-packages/knack/commands.py", line 109, in call
return self.handler(*args, **kwargs)
File "/opt/az/lib/python3.6/site-packages/azure/cli/core/init.py", line 421, in default_command_handler
result = op(**command_args)
File "/opt/az/lib/python3.6/site-packages/azure/cli/command_modules/cosmosdb/custom.py", line 244, in cli_cosmosdb_database_list
return list(client.ReadDatabases())
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/query_iterable.py", line 112, in next
return next(self._ex_context)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/base_execution_context.py", line 105, in next
return self.next()
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/execution_dispatcher.py", line 64, in next
return next(self._execution_context)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/base_execution_context.py", line 105, in next
return self.next()
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/base_execution_context.py", line 95, in next
results = self.fetch_next_block()
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/base_execution_context.py", line 73, in fetch_next_block
return self._fetch_next_block()
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/base_execution_context.py", line 158, in _fetch_next_block
return self._fetch_items_helper_with_retries(self._fetch_function)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/base_execution_context.py", line 132, in _fetch_items_helper_with_retries
return retry_utility._Execute(self._client, self._client._global_endpoint_manager, callback)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/retry_utility.py", line 56, in _Execute
result = _ExecuteFunction(function, *args, **kwargs)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/retry_utility.py", line 92, in _ExecuteFunction
return function(*args, **kwargs)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/base_execution_context.py", line 130, in callback
return self._fetch_items_helper_no_retries(fetch_function)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/execution_context/base_execution_context.py", line 120, in _fetch_items_helper_no_retries
(fetched_items, response_headers) = fetch_function(self._options)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/document_client.py", line 282, in fetch_fn
options), self.last_response_headers
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/document_client.py", line 2685, in __QueryFeed
url_connection = self._global_endpoint_manager.ReadEndpoint
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/global_endpoint_manager.py", line 48, in ReadEndpoint
self.RefreshEndpointList()
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/global_endpoint_manager.py", line 67, in RefreshEndpointList
database_account = self._GetDatabaseAccount()
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/global_endpoint_manager.py", line 85, in _GetDatabaseAccount
database_account = self._GetDatabaseAccountStub(self.DefaultEndpoint)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/global_endpoint_manager.py", line 105, in _GetDatabaseAccountStub
return self.Client.GetDatabaseAccount(endpoint)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/document_client.py", line 2309, in GetDatabaseAccount
headers)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/document_client.py", line 2546, in __Get
headers)
File "/opt/az/lib/python3.6/site-packages/pydocumentdb/synchronized_request.py", line 210, in SynchronizedRequest
resource_url = base_url + request_options['path']
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'

Expected behavior
A boolean indicating whether the database exists.
Environment summary
azure-cli (2.0.41)
acr (2.0.28)
acs (2.1.3)
advisor (0.5.1)
ams (0.1.1)
appservice (0.1.36)
backup (1.1.2)
batch (3.2.4)
batchai (0.3.1)
billing (0.1.8)
cdn (0.0.14)
cloud (2.0.15)
cognitiveservices (0.1.13)
command-modules-nspkg (2.0.1)
configure (2.0.17)
consumption (0.3.1)
container (0.2.1)
core (2.0.41)
cosmosdb (0.1.21)
dla (0.1.0)
dls (0.0.22)
dms (0.0.1)
eventgrid (0.1.12)
eventhubs (0.1.3)
extension (0.1.0)
feedback (2.1.3)
find (0.2.11)
interactive (0.3.25)
iot (0.1.21)
keyvault (2.0.23)
lab (0.0.22)
maps (0.2.0)
monitor (0.1.8)
network (2.1.5)
nspkg (3.0.2)
policyinsights (0.1.0)
profile (2.0.27)
rdbms (0.2.5)
redis (0.2.14)
reservations (0.2.1)
resource (2.0.32)
role (2.0.26)
servicebus (0.1.2)
servicefabric (0.0.12)
sql (2.0.27)
storage (2.0.35)
vm (2.0.35)
Python location '/opt/az/bin/python3'
Extensions directory '/home/vagrant/.azure/cliextensions'
Python (Linux) 3.6.1 (default, Jul  2 2018, 18:43:15)
[GCC 4.8.4]
Legal docs and information: aka.ms/AzureCliLegal
Additional context
It works in azure-cli (2.0.27)

same error for SHOW as well as EXISTS. Oh and LIST fails too...

https://github.com/Azure/azure-cli/issues/6827

Still experiencing this problem - any news on the resolution?

I'm also having this issue.. any update?

@christopheranderson for comment.

@fercho-ayala thank you for identifying this problem. I have reverted the change that introduced the problem as a part of #7929. It should be working as of CLI version 2.0.53

Closing since this has been fixed. Please open if that is not the case.


Hotfix for pyzmq installation

fixes #2271
pyzmq installation fails due to the latest prerelease.
Fix: removed the --pre argument to use the latest release, which is known to work.

Should we fix it in Docker as well?
https://github.com/MiczFlor/RPi-Jukebox-RFID/blob/c713610ff87fdaa434ff751dfdea118584b3e47f/docker/jukebox.Dockerfile#L53

Done with dont use prereleases (docker)

Reference: this should also fix #2268

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 38.2%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
416

Relevant Lines:
1089

💛  - Coveralls


Quiet flag

Description:
Adds a -q/--quiet flag which logs leaks one line at a time instead of the default "pretty" json. This also sets the log level to errors only. Good for processes that was to injest the output of gitleaks without opening a file.
Checklist:

[x] Does your PR pass tests?
[ ] Have you written new tests for your changes?
[x] Have you lint your code locally prior to submission?

I updated gitleaks and found that the -q/--quiet flag is no longer present. Is there a reason for that, or an alternative?


Add "type": "module" to package.json for Vite resolution

I have a project that uses this datepicker. I'm creating an SSR build of the project using Vite. When trying to run the resulting bundle using node, a Cannot use import statement outside a module error happens. Vite correctly imports the vue-datepicker.es.js file, but then incorrectly treats it as a CommonJS module. This happens because Vite seems to only treat modules as ES modules if the package.json specifies the type as module.
If I manually edit the package.json in my node_modules folder to include "type": "module", everything works as expected.

Hmm, I am aware of this, however, if "type":"module" is set, nuxt will throw an error in the production environment.

Will have to check with vanilla vite setup, since this is the config from the vue-create.

Ok, it will work, I was experimenting with .cjs and .mjs

Thanks for the quick response!