Errors in the versions 3.6.12 - 3.6.15

How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
Linux
What is the issue affecting?
Other
Expected Behaviour
No response
Actual Behaviour
Versions between 3.6.12 and 3.6.14 doesn't work at all in my VSCodium on Manjaro Linux.
Version 3.6.15 works, but showing broken error message:

Version 3.6.11 works fine.
Reproduction steps
No response
Additional Notes
No response
Log File
No response

Hello, there were a series of issues when implementing the addon manager which completely broke the versions you mention. 3.6.15 should be working. Not sure why the log file wouldn't exist-can you open the Output panel and select Lua Addon Manager from the dropdown and send what you see in there?

Hm, I am not sure if VSCodium supports all the same APIs as VS Code. It looks like it is failing when creating a log file.

Yes, the directory ~/.config/VSCodium/logs/20230302T195814/window1/exthost/sumneko.lua/addonManager is empty.

Here is the content of ~/.config/VSCodium/logs/20230302T195814/window1/exthost/exthost.log:
2023-03-02 19:58:15.745 [info] Extension host with pid 125043 started
2023-03-02 19:58:15.745 [info] Skipping acquiring lock for /home/luarocks/.config/VSCodium/User/workspaceStorage/d40d579047fe53977e033ee74dc61bbc.
2023-03-02 19:58:15.888 [info] ExtensionService#_doActivateExtension JohnnyMorganz.stylua, startup: false, activationEvent: 'onLanguage:lua'
2023-03-02 19:58:15.888 [info] ExtensionService#_doActivateExtension sumneko.lua, startup: false, activationEvent: 'onLanguage:lua'
2023-03-02 19:58:15.888 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2023-03-02 19:58:15.888 [info] ExtensionService#_doActivateExtension vscode.extension-editing, startup: false, activationEvent: 'onLanguage:markdown'
2023-03-02 19:58:15.888 [info] ExtensionService#_doActivateExtension vscode.markdown-language-features, startup: false, activationEvent: 'onLanguage:markdown'
2023-03-02 19:58:15.888 [info] ExtensionService#_doActivateExtension yzhang.markdown-all-in-one, startup: false, activationEvent: 'onLanguage:markdown'
2023-03-02 19:58:15.889 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2023-03-02 19:58:15.889 [info] ExtensionService#_doActivateExtension funkyremi.vscode-google-translate, startup: true, activationEvent: '*'
2023-03-02 19:58:15.889 [info] ExtensionService#_doActivateExtension naumovs.color-highlight, startup: true, activationEvent: '*'
2023-03-02 19:58:16.148 [info] ExtensionService#_doActivateExtension vscode.markdown-math, startup: false, activationEvent: 'api', root cause: yzhang.markdown-all-in-one
2023-03-02 19:58:16.197 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2023-03-02 19:58:16.197 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2023-03-02 19:58:16.270 [info] Eager extensions activated
2023-03-02 19:58:16.278 [error] Error: ENOENT: no such file or directory, open 'home/luarocks/.config/VSCodium/logs/20230302T195814/window1/exthost/sumneko.lua/addonManager/19-58.log'
2023-03-02 19:58:16.318 [info] ExtensionService#_doActivateExtension vscode.debug-auto-launch, startup: false, activationEvent: 'onStartupFinished'
2023-03-02 19:58:16.318 [info] ExtensionService#_doActivateExtension vscode.merge-conflict, startup: false, activationEvent: 'onStartupFinished'
2023-03-02 19:58:16.318 [info] ExtensionService#_doActivateExtension vscode.npm, startup: false, activationEvent: 'onStartupFinished', root cause: esbenp.prettier-vscode
2023-03-02 19:58:16.318 [info] ExtensionService#_doActivateExtension fcrespo82.markdown-table-formatter, startup: false, activationEvent: 'onStartupFinished'
2023-03-02 19:58:16.318 [info] ExtensionService#_doActivateExtension streetsidesoftware.code-spell-checker, startup: false, activationEvent: 'onStartupFinished'
2023-03-02 19:58:16.526 [info] ExtensionService#_doActivateExtension esbenp.prettier-vscode, startup: false, activationEvent: 'onStartupFinished'
2023-03-02 19:58:20.873 [error] EntryNotFound (FileSystemError): Unable to read file '/home/luarocks/.config/VSCodium/logs/20230302T195814/window1/exthost/sumneko.lua/addonManager/19-58.log' (Error: Unable to resolve nonexistent file '/home/luarocks/.config/VSCodium/logs/20230302T195814/window1/exthost/sumneko.lua/addonManager/19-58.log')
	at Yt._handleError (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:30142)
	at Object.readFile (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:98:29026)
	at process.processTicksAndRejections (node:internal/process/task_queues:96:5)
2023-03-02 20:03:22.514 [info] Extension host terminating: received terminate message from renderer
2023-03-02 20:03:22.527 [error] Canceled: Canceled
	at new u (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:92736)
	at l._remoteCall (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:106:13769)
	at $.<computed>.N.charCodeAt.$.<computed> (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:106:10315)
	at s._doExecuteCommand (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:112905)
	at s.executeCommand (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:112216)
	at E.registerCommand.description (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:111443)
	at s._executeContributedCommand (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:113540)
	at s._doExecuteCommand (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:112356)
	at s.executeCommand (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:96:112216)
	at Object.executeCommand (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:117:33764)
	at D (/opt/vscodium-bin/resources/app/extensions/git/dist/main.js:2:2055322)
	at f.invoke (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2559)
	at d.fire (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2137)
	at Object.h [as dispose] (/opt/vscodium-bin/resources/app/extensions/git/dist/main.js:2:2070159)
	at /opt/vscodium-bin/resources/app/extensions/git/dist/main.js:2:2074226
	at Array.forEach (<anonymous>)
	at g.dispose (/opt/vscodium-bin/resources/app/extensions/git/dist/main.js:2:2074212)
	at C.<anonymous> (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:13686)
	at C.dispose (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:13821)
	at C.<anonymous> (/opt/vscodium-bin/resources/app/extensions/git/dist/main.js:2:2057452)
	at C.dispose (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:94:13821)
	at k (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:10:12140)
	at f._deactivate (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:13198)
	at /opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:10372
	at Array.map (<anonymous>)
	at f._deactivateAll (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:10359)
	at f.terminate (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:108:10744)
	at h.terminate (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:112:1565)
	at p (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:122:19074)
	at /opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:122:16964
	at f.invoke (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2559)
	at d.fire (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2137)
	at p.fire (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:72:17066)
	at t._receiveMessage (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:72:23562)
	at /opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:72:20001
	at f.invoke (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:145)
	at g.deliver (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2559)
	at d.fire (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:63:2137)
	at h.acceptChunk (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:72:13890)
	at /opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:72:13020
	at Socket.t (/opt/vscodium-bin/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:72:28756)
	at Socket.emit (node:events:526:28)
	at addChunk (node:internal/streams/readable:315:12)
	at readableAddChunk (node:internal/streams/readable:289:9)
	at Readable.push (node:internal/streams/readable:228:10)
	at Pipe.onStreamRead (node:internal/stream_base_commons:190:23) setContext undefined
2023-03-02 20:03:22.527 [info] Extension host with pid 125043 exiting with code 0

I believe this has been fixed in the commits I have just pushed, thanks for the help debugging!
Hopefully we can get the fix released soon 🙂


No Strong name for dotless.AspNet

Why does the latest version (1.6.2) not have a strong name anymore?
It is technically preventing us from using this library.

That was fast. Awesome! Thank you!


Hide Search Bar from Sidepanel

Hide search bar from side panel until its functional
https://github.com/openshiftio/openshift.io/issues/2293

@SMahil fabric8/fabric8-ui:SNAPSHOT-PR-2455-1 is deployed and available for testing at https://fabric8-ui-fabric8-ui-pr-2455-fabric8-planner.badger.fabric8.io


Update packit status to support monorepos

packit status should report information about all the packages found in a monorepo (downstream PRs, dist-git versions, Bodhi updates, Koji builds, Copr builds, ...).
This means updating packit.api.status() and the related methods and classes to support monorepos.

We decided to implement this through a decorator so that very few changes should be needed.
The changes will be linked to https://github.com/packit/packit/issues/1849.
Ideally we could have just one PR which adds support to the monorepo packages in Packit CLI.


Unable to create ResourceGroupDeployment

Module: 1
Exercise 2: Configure the Azure AD DS domain environment
Task 1: Deploy an Azure VM running Windows 10 by using an Azure Resource Manager QuickStart template
Step: 3: From the PowerShell session in the Cloud Shell pane, run the following to deploy an Azure VM running Windows 10 that will serve as a Azure Virtual Desktop client and join it to the Azure AD DS domain:
Description of issue:  After uploading the "az140-11_azuredeploycl11a.json" and "az140-11_azuredeploycl11a.parameters.json", running the script.  running the commands came back with error
New-AzResourceGroupDeployment: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
Repro steps:

Uploaded both .json files to /Home

When run the script, it came back with error:
New-AzResourceGroupDeployment:
Line |
3 |    -Location $location `
|    ~~~~~~~~~
| A parameter cannot be found that matches parameter name 'Location'.

Tried leaving out the" -Location $location".  error returned:
New-AzResourceGroupDeployment: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.

Pls provide a copy of the template you are using (the one you uploaded)
rgds
Marcin

Thanks Marcin, The templates that i am using are from the Labs\01\ folder:
\Allfiles\Labs\01\az140-11_azuredeploycl11a.json
https://github.com/MicrosoftLearning/AZ-140-Configuring-and-Operating-Microsoft-Azure-Virtual-Desktop/blob/master/Allfiles/Labs/01/az140-11_azuredeploycl11a.json
\Allfiles\Labs\01\az140-11_azuredeploycl11a.parameters.json
https://github.com/MicrosoftLearning/AZ-140-Configuring-and-Operating-Microsoft-Azure-Virtual-Desktop/blob/master/Allfiles/Labs/01/az140-11_azuredeploycl11a.parameters.json
Thanks

I'm aware of their original location.
I'd like to take a look at a copy of the template you are uploading to Cloud Shell (pls copy and paste its content into your response)
rgds
Marcin

Hi Marcin,
I simply downloaded these 2 files from the Lab\01 folder and then uploaded them to cloud shell without making any changes.  So what I uploaded is exactly what is on the repository.  I believe those files are 2000+ lines, so it might be hard to upload them here.   thanks.
wing

Hi Wing,
the first 20 lines might suffice.
rgds
Marcin

Hi Marcin,
Thank you for your suggestion!  I right-click on the .json files, and chose "Save link as".  I thought I was saving the files, but in fact it wasn't.  I uploaded the files with the correct content and I was able to deploy the VM successfully.  thank you for your help.
regards
wing

Hi Wing,
you're welcome
rgds
Marcin


Add double click and long press for GUI Controls

Related forum issue: https://forum.babylonjs.com/t/add-doubleclick-and-longpress-for-a-gui-button/40729
We support these as trigger actions for meshes: https://doc.babylonjs.com/features/featuresDeepDive/events/actions#triggers, so we should extend this support. We need to discuss how to do that, through ActionManager too or through some other mechanism.

No traction. Feel free to re-open


Add Function for validating token

This should work for the Authenticated calls - It does two things

Adds a function for validating the GitHub Token - This function validates the token once each time the script is run so that if additional API calls are needed the token doesn't need to be re-validated each time.
Adds a function for getting the Releases API Response - This is to make it easier to follow the logic of how the API response is fetched - either using gh.exe or by Invoke-RestMethod

Thanks @Trenly, I didn't notified by GitHub about this pull request. Those modifications are already reverted on my master branch ❤
This pull request can be closed.


[Feature Requests] Tri-state filters

Implements negative filters for Download, Unread, Completed
A PR has been made already, if you want to use that PR (or your own if you want)
https://github.com/inorichi/tachiyomi/pull/2127

This has be added as of v0.9.1


[stable/kong] Update Kong role to match users params

Signed-off-by: garland<EMAIL_ADDRESS>What this PR does / why we need it:
The resourceName for the leader election configmap is hardcoded into the Role.  If the kong controller restarts or it was not the one that created the configmap, it is denied on being able to access it.  In turn the kong controller does not update any new items that comes up or changes.
I see the following errors in the Kong controller ingress-controller logs.
E1227 00:07:20.754146       5 leaderelection.go:258] Failed to update lock: configmaps "kong-ingress-controller-leader-kong-kong" is forbidden: User "system:serviceaccount:dev-kong:dev-kong-kong" cannot update configmaps in the namespace "dev-kong"

By setting this to the proper name, I dont get this error in the logs anymore and the routes works as expected after restarts.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md

/assign @hbagdi

/ok-to-test

/lgtm

@sekka1 Thank you!


admin: object link and uuid filtering

Adds support for filtering PIDs by object uuid.

Adds support for linking to record (and other) admin views.

Signed-off-by: Lars Holm Nielsen<EMAIL_ADDRESS>

[ ] update copyright years


Analysis of Large Data Sets

This should be doable with gnuplot and raw statistics can be computed by hand on disk if need be. Data would be read/written via I/O system calls like read() and write().
Graphviz may also be of use, as well as LaTeX.

MatLab has the ability to plot massive (1 billion point) datasets. GNU plot seems easier to use though because we don't need to do much work to set it up. Let's go with GNU plot for now and if they want extra analysis they have enough matlab programmers to build a new plotting system.


Manual xAxis labels implemented

Relates to #503

Need to investigate some of the API docs to simplify the rounding of the intervals.
https://github.com/mbostock/d3/wiki/Time-Intervals

There isn't any overflow stuff included in this, but I have that in progress in the yAxis work.  Might be worth pulling that functionality out into a separate component once both issue are resolved

Noticed some issues with this while rebasing, adding WIP tag for now


Many tests now fail with Invalid_argument("compare: functional value")

Within the last 1-2 days I'm starting to see failures related to comparing functions in tests that haven't triggered such errors before, which haven't been changed recently, and which are not (intentionally!) comparing functions.
Here's an example from Linux 5.1:
https://github.com/ocaml-multicore/multicoretests/actions/runs/4994151783/jobs/8944304277
random seed: 495041348
generated error fail pass / total     time test name

[ ]    0    0    0    0 / 1000     0.0s Lin DSL Queue test with Domain
Fatal error: exception Invalid_argument("compare: functional value")
File "src/queue/dune", line 4, characters 7-20:
4 |  (name lin_tests_dsl)
           ^^^^^^^^^^^^^
(cd _build/default/src/queue && ./lin_tests_dsl.exe --verbose)
Command exited with code 2.

Observations:

spotted on 5.1 and trunk (we only test 5.0 weekly now) and
across Linux, macOS, and Windows
only seen on Lin DSL tests so far
seen on Queue, Dynlink, Weak, Bigarray, Ephemeron, ... tests

It turns out the reason for the failures was an element comparison added to the 0.21 QCheck list shrinker: https://github.com/c-cube/qcheck/pull/280

This is fixed with the release of QCheck 0.21.1


Fixes CVE-2023-49569

Summary
Fixes CVE-2023-49569
Fixed by upgrading go-git:
go get<EMAIL_ADDRESS>
Use Cases

Checklist

[ ] I have viewed, signed, and submitted the Contributor License Agreement.
[ ] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[ ] I have added an integration test, if necessary.
[ ] I have reviewed the styleguide for guidance on my code quality.
[ ] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

Thank you for the review @thitch97 !
I don't think I have the permission to merge this. Please go ahead and do it for me :bow:


Trailingslash has a wrong ranking and creates empty params in array if after a wildcard parameter

Reproduction
https://play.vuejs.org/#eNqtVV1P2zAU/SteNqnt1tqlQzxkoWNDaGzaB2LTXpY9pImbBhLbsh0oivrfd22niQsFXibUNrn33ONzfY9NE1RJwfCVCsKgqASXGjUolTTR9IMQaIOWkldocFPTQcw6gOS1prLLYuICPcTUbnOJENjVx6xjHsJnFDOEcK3o0JW794rXTA8HL6FsMArGQVsO+iJNK1FC/dwAo9XB/JyWJTeLvYgIvNqwsD/woLTkLJ+f1lJSpp1mJBK9CiPS5lDToFc2gZd1WV5AEm02loY4noglN1vCS6vya8GukebHcUDiYP6JwzM65xWNSJ9/tCJZpCSjy75SU6WfqQxtacOSioZoYAomIsnpYAzNyKRSIWowxq4LFzGZHMAz6MVfCN0W0KDJPVgyIttGI2OIXRm/C3qLSItr0xHxpgGvKpWF0EhRXZud66wC47UkvpUmrV3egSE4A11uNscdeDiCFEzJcs7BBK4A6z02/UYrLu/OC6XhZ9wGne59axqxLYOZmm1t69RtoLXr1ssLqNzBdZHO13RtoV43EtrxtQwbs30rJzPcp304GhuIrYah/nEjaJxl0YDAwFMOkhi4OezFb2yVAXoOseZwZaF5H+LX70ev71H0je3l6F32kMikSGi+h3GcvRk9w/wXvjdwvGGS/h6bM+37BpUJy8HrWoFtPQNYg907/LP5lgmO/mzXkLDMzoieWed/enW/1E5NqxV2uvEPrLlzdvU7TZMqEXA3cwYdWP/EbQKEw7F3Q4uDXqYJx8FKa6FCQmomrnMMcyE94uQQv8VTkoHnvCimqposJL9V8HwF7K0h4uAEQHBl3WjOSzVJRPHYEg+AJ0f4CB+QslgQYCcFy+jachtqaHgDbWoFm7os8ntNGisVJZU/hC5g03eaTeDKv/1iY1rWtBOarmh6vSd+pdZO8oWk0N0N9ZrTicypdumzn9/pGp67ZMWzugT0E8lLqnhZG40O9rFmGcj2cFbtZzuzguW/1NlaU6a2TRmhdjcs3g7y9InWe7lv8aG3i0rflVThVJnrEe7xMTKXtKtbcJlRCf8LxBqB2CJDL6fTKVgWAUjmBZssuNa8CtHBVKxtXCRZBmK7CKwSM6BFc5SgN/CxxG11SZdw4H3kauav3NP3AtI09QSEaAp/s5Yh2PwD2IzlHA==
Steps to reproduce the bug

Click on "Go to test"
Notice the route.params is an array with an empty element at the end
Click on "Go to test with page", notice the page has now 2 slashes in it

Expected behavior
Without a trailing slash the ranking is correct, I think the trailingslash should have a lower rank than a regex
https://paths.esm.dev/?p=AAMeJUyB3A7ACAROgDYMTAHuJXIFqHQAUAFACTg_OQA5INikft_qADWgAQVDQMk8w6RBgNwSAIA.&t=/en/brands/abcd/efh/page/2#
Actual behavior
With a trailing slash now the ranking is wrong and the second route can never be matched https://paths.esm.dev/?p=AAMeJUyB3A7ACAROgDYMTAHuJXIFqHQAUAFACTg_OQA5INikft_qADWg4AUBBfMMSSMghySCcrsAAA..&t=/en/brands/abcd/efh/page/2#
Additional information
I think the trailingslash should be discarded from the params list because it's in any case optional with vue router
The ranking should also be changed so that a trailingslash doesn't alter the ranking
Related https://github.com/vuejs/router/issues/1300
https://github.com/vuejs/router/issues/1123

The ranking of a trailing slash is an intended behavior.
Note you can use the strict option too. Also, the page makes more sense as a query param in your case, which fixes the issue. This important when using the wildcard .* which matches anything since they can create redundant paths like this one

Also, the page makes more sense as a query param in your case, which fixes the issue.

Sorry, that's not an option
I'm using the strict and end option but the page is still not being matched if both have a trailingslash
Here are the regex and scores
^/en/product-category(?:/((?:.*)(?:/(?:.*))*))?/$ [ [ 80 ], [ 80 ], [ -8 ], [ 90.7 ] ]
^/en/product-category(?:/((?:.*)(?:/(?:.*))*))?/page(?:/(\d+))?/$ [ [ 80 ], [ 80 ], [ -8 ], [ 80 ], [ 62 ], [ 90.7 ] ]

As you can see the strict option is not working properly in this case
https://paths.esm.dev/?p=ABMMIPQgYAqQdgEjEDgB1jMwBaS3zAWgdABQAUAJJD84ADmgubTh2OsANaCQFQEFeAwz-MpjCYPVCgB5&t=/en/brands/abcd/efh/page/2/#

Having redundant paths will always yield issues in routing and should be avoided. Using .* can easily create these problems too. Using query params should also be your go to solution your pagination. In your case you might need to combine it with server redirects to fully work. In any case, I'm glad you found a workaround (BTW, the ranking difference with .* is not a bug).

Having redundant paths will always yield issues in routing and should be avoided

It shouldn't, that's never been a problem when routing uses the user provided order instead of computing a score, but if it computes a score then it should do so correctly or provide us with the option to change the score of a route manually

Using query params should also be your go to solution your pagination. In your case you might need to combine it with server redirects to fully work

That's suggesting another feature because the core feature of the router is not working properly, I don't see how a server redirect when vue router does client side routing would work properly

I'm glad you found a workaround (BTW, the ranking difference with .* is not a bug)

Thanks, I'm talking about the fact that .*? is not treated as a lazy regex but as a greedy one not about the ranking
For what I gathered it just seems like an oversight there with trailingslashes being considered as another root segment, shouldn't this just happen for the actual root path / (so for the first segment) and not for trailing slashes? Like this a trailing slash would not add any segment score and would have the same behavior as no trailing slash
https://github.com/vuejs/router/blob/a24d55b8de03c3c4a999998cabf49366963a6a7a/packages/router/src/matcher/pathParserRanker.ts#L141

All in all I can submit a PR for bug 1 which is optional or repeated params lazyness is being overwritten by being wrapped (by checking the presence of (+|*|?)? in the regex and appending another ? to the regex in this case
And another PR for the trailingslash issue
I have no problem spending a bit of time for that. But they should be regarded as what they are, which is bugs. I only have a problem spending time on a PR for nothing (that will never be accepted)

I have no problem spending a bit of time for that. But they should be regarded as what they are, which is bugs. I only have a problem spending time on a PR for nothing (that will never be accepted because it is "intended behavior")

That's totally understandable.
If you manage to tweak the scoring while keeping scoring very similar (to avoid unexpected breaking changes outside), not break or change any existing assertions on ranking. I can take a look. To be fully transparent to you, if you open a PR, I will need some time to get it released (probably 2 to 3 months), but I will eventually take a look and address the problem if possible.

From what I gathered it just seems like an oversight there with trailingslashes being considered as another root segment, shouldn't this just happen for the actual root path / (so for the first segment) and not for trailing slashes? Like this a trailing slash would not add any segment score and would have the same behavior as no trailing slash

Maybe there is a differentiation to be made between end and non-end versions. In the future, I doubt the end option will be preserved by default as it creates incoherences in ranking (it seems this is one of them)

I'm talking about the fact that .*? is not treated as a lazy regex when it's wrapped by being marked as optional or repeated, but as a greedy one, not about the ranking (which means the 2 regexes are perfectly equivalent but if this bug is fixed then they wouldn't be perfectly equivalent, but bad example because in this particular case they are not being wrapped)

I see. Unless the current behavior exposes a ranking issue, I doubt any effort will be made to break the current workaround, especially knowing now that it is a workaround. It's great you bring it up thought


[Loc] update to mssql constants and sql-migration

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage remained the same at 41.756%

Files with Coverage Reduction
New Missed Lines
%

extensions/notebook/src/dialog/configurePython/configurePythonWizard.ts
1
46.46%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
30826

Relevant Lines:
69082

💛  - Coveralls


SignaturePacket: fixes typo in signature type switches with T.persona

In openppg/packet/signature.iced are multiple checks against the current signature type. All of them compare against a non existing Type T.personal which seems to be a typo of T.persona
 52   sig_types :  # See RFC 4880 5.2.1. Signature Types
 53     binary_doc : 0x00
 54     canonical_text : 0x01
 55     issuer : 0x10
 56     persona : 0x11

thanks!


Update Raspberry Pi sample

[ ] Add all supported commands
[ ] Implement current height command

@iMicknl Hi this is very interesting. Any updates on this so far? Since I'm planning to work with Raspberry Pi, I'm happy to help contribute on this task.


floyd_warsall.java : Added Floyd Warshall Algorithm [Java]

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Any change needs to be discussed before proceeding.
Description
Please describe what changes you have made.

Added algorithm for Floyd Warshall in Java

Related Issue
Fixes #86
This project only accepts pull requests related to open issues.
If suggesting a new feature or change, please discuss it in an issue first.
If fixing a bug, there should be an issue describing it with steps to reproduce.
Please link to the issue here:
How Has This Been Tested? (Optional)
Please describe in detail how you tested your changes.
You can skip this if you have not added any tests.
Screenshots (Optional)
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (change which fixes an issue with the algorithm)

[x] New Algorithm (non-breaking change which adds functionality)

[ ] Documentation

Checklist:
Go over all the following points, and put an x in all the boxes that apply.
If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x] My code follows the code style of this project.

[x] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[x] I have read the CONTRIBUTING document.

I havent change any files ... perphaps the files were corrupt ... please look into it .. teey weren't downloaded to my computer


Revert "Extend fhmax default (#1877)"

The last PR caused seg faults for prognostic runs with lower physics diagnostics save intervals- they ran out of space in their fdiag arrays. Reverting to the previous default for fhmax, and the issue with physics diags not saving after ~40d will instead be fixed on the fortran side (solution proposed here).
Instead of changing the default, in the meantime if we are saving data for longer than 1024 hr, fhmax can be manually updated to be larger in the user config.

Thanks @AnnaKwa.  I anticipated this issue, yet somehow it didn't occur to me that we output physics diagnostics at every timestep in most of our other workflows.  Perhaps I should prioritize ai2cm/fv3gfs-fortran#301.


compile tf_mesh_renderer

When I use bazel to compile tf_mesh_renderer, I met the problem shown in the following:
MGCNet-master/thirdParty/tf_mesh_renderer/mesh_renderer/kernels/BUILD:8:8: Executing genrule //mesh_renderer/kernels:rasterize_triangles_kernel failed (Exit 1): bash failed: error executing command /bin/bash -c ... (remaining 1 argument(s) skipped)

Are you sure that you follow each cmd provided by us?


hi this is gloatingxennial from tikok

ty for reading my account on your live I would love an access code to statschecklol.com and i can help with the python api and or other stuff. Im a DS... but finance and risk focused.. not super good at javascript

thank you


sportschau.de video not detected

Checklist

[x] I'm reporting a broken site support
[x] I've verified that I'm running youtube-dl version 2021.12.17
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar issues including closed ones

Verbose log

andreas@andreas2:~$ youtube-dl -v https://www.sportschau.de/schach/video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.html
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'https://www.sportschau.de/schach/video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.html']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.9.2 (CPython) - Linux-5.10.0-16-amd64-x86_64-with-glibc2.31
[debug] exe versions: ffmpeg 4.3.4-0, ffprobe 4.3.4-0, rtmpdump 2.4
[debug] Proxy map: {}
[WDRPage] video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100: Downloading webpage
[download] Downloading playlist: video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100
[WDRPage] playlist video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100: Collected 0 video ids (downloading 0 of them)
[download] Finished downloading playlist: video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100

Description

I have checked the issues and found a closed issue that sportschau.de is supported. But the video above cannot be downloaded. I also checked several other videos from sportschau.de and they cannot be downloaded too. I was able to find the same video in the ARD Mediathek (ARDBetaMediathek) and there the download works:
https://www.ardmediathek.de/video/sportschau/spasski-gegen-fischer-das-schachspiel-des-jahrhunderts/das-erste/Y3JpZDovL3Nwb3J0c2NoYXUuZGUvc3BvcnRzY2hhdS1mZm1wZWctdmlkZW8tNTg0MTE4OQ
By the way, the WDR (WDRPage) is part of the ARD (ARDBetaMediathek) and the sportschau.de is driven by the ARD. Maybe there are internal redirects that confuse youtube-dl?

for this link - https://www.sportschau.de/schach/video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.html
try with youtube-dl --force-generic-extractor "https://www.sportschau.de/schach/video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.html"

Yes, this works:
youtube-dl -v --force-generic-extractor "https://www.sportschau.de/schach/video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.html"
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '--force-generic-extractor', 'https://www.sportschau.de/schach/video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.html']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.9.2 (CPython) - Linux-5.10.0-16-amd64-x86_64-with-glibc2.31
[debug] exe versions: ffmpeg 4.3.4-0, ffprobe 4.3.4-0, rtmpdump 2.4
[debug] Proxy map: {}
[generic] video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100: Requesting header
WARNING: Forcing on generic information extractor.
[generic] video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100: Downloading webpage
[generic] video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100: Extracting information
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://sportschau-dd.akamaized.net/weltweit/nfsk/2022/07/11/8e5d597c-cf7a-49f8-b7d0-06ea38c594a0/8e5d597c-cf7a-49f8-b7d0-06ea38c594a0_AVC-1080.mp4'
[download] Destination: Spasski gegen Fischer - das Schachspiel des Jahrhunderts-video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.mp4

So the detection of WDRPage is false?

Apparently:

at some point (before 2016) Sportschau used a common page format with ARD;
later (2016) it used a common page format with WDR, and currently yt-dl expects this and fails;
now it doesn't do either.

In the problem page there is a well populated application/ld+json block including a 1080 contentUrl, which the generic extractor finds. Metadata is also in the og:* <meta> elements. Later there is a <div> with class mediaplayer whose data-v attribute decodes to a JSON object whose .mc.streams.media lists additional media formats.
Possibly, as this is a sports site, there are current pages that are more difficult to extract, but this from yesterday has the same structure

So this regex is the problem?
https://github.com/ytdl-org/youtube-dl/blob/master/youtube_dl/extractor/wdr.py#L132

There are two tests in this file but both links are not valid anymore. I assume the page is completely restructured and WDRPage does not apply to sportschau.de anymore.

Exactly. For the moment you can use the work-around or try to find the show at ARD.
The first stage of fixing this is to direct a Sportschau URL to the generic extractor, either by default, by removing the pattern and associated tests, or explicitly, by forwarding the URL to the generic extractor.
Then, if the resulting formats and metadata prove inadequate, a new extractor could be created, or possibly the generic extractor could be improved.
This is what we get after stage 1, omitting null and default values:
{
  "extractor": "generic",
  "protocol": "https",
  "upload_date": "20220711",
  "duration": 572,
  "id": "video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100",
  "title": "Spasski gegen Fischer - das Schachspiel des Jahrhunderts",
  "timestamp":<PHONE_NUMBER>,
  "thumbnail": "https://images.sportschau.de/image/2e57ae8d-2802-4bde-a179-bdba485a3233/AAABgewgmjQ/AAABgPp7Db4/16x9-1280/spasski-fischer-100.jpg",
  "webpage_url_basename": "video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.html",
  "display_id": "video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100",
  "description": "Inmitten des kalten Krieges trafen vor 50 Jahren Boris Spasski und Bobby Fischer im Finale der Schach-WM aufeinander. Ein Spiel, welches von der gesamten Welt gebannt beobachtet wurde.",
  "format": "0 - unknown",
  "uploader": "Sportschau.de",
  "format_id": "0",
  "url": "https://sportschau-dd.akamaized.net/weltweit/nfsk/2022/07/11/8e5d597c-cf7a-49f8-b7d0-06ea38c594a0/8e5d597c-cf7a-49f8-b7d0-06ea38c594a0_AVC-1080.mp4",
  "ext": "mp4",
  "webpage_url": "https://www.sportschau.de/schach/video-spasski-gegen-fischer-das-schachspiel-des-jahrhunderts-100.html"
}


bower support

Please add this as a bower component.

:+1:

#37 should fix this. But I'm unfamiliar with bower, and I cannot find L.GeoSearch on http://bower.io/search/ like @flakron is saying.
Can one of you help me out?

@smeijer It doesn't look like it was properly registered.

@althaus, thanks. I've seem to have fixed this one. Can you confirm?
bower install leaflet-geosearch


dynamic-crop.lua script causes OSD to bug out in fullscreen

Setup (please complete the following information):

OS: Windows 7 Build 7601 Service Pack 1
Player: mpv
Player Version: v0.36.0
Video Quality: 1080pH.264 /2160p HDR H265 or any song, doesn't matter

Additional context
MPV config:
script="C:\Program Files\MPV\scr\dynamic-crop.lua"
hwdec=no
vo=gpu-next
Log file
output.txt
Describe the bug
When you go fullscreen, the OSD bugs out, pulsates/flickers. OSD doesn't disappear after time, it displays all the time.
Expected behavior
After fullscreen, OSD acts as usual, don't bug out, and disappear after 2 seconds.
Screenshots

Hello, can't reproduce and never had this issue.
The logs are incomplete, doesn't show dynamic crop loading, etc. Example:
[   0.012][d][dynamic_crop] Loading lua script C:\Users\xxxxx\mpv-scripts\dynamic-crop.lua...
[   0.015][d][dynamic_crop] reading options for dynamic_crop
...
[   0.266][i][dynamic_crop] File loaded.

But i see you're using DEL shortcut, which is used to toggle OSC visibility between Never, Auto and Always.
May be it's your issue.

I don't know, I just put in cmd "mpv --log-file=output.txt" and thats it.
What do you mean by "DEL shortcut"? Do you have any suggestions what I can try out to fix this?
I am a noob, I use mvp since 4 days or so.

I don't know, I just put in cmd "mpv --log-file=output.txt" and thats it.

add in mpv.conf instead, to get the logs in any case.
log-file=output.txt

What do you mean by "DEL shortcut"? Do you have any suggestions what I can try out to fix this?

The touch DEL from your keyboard, make sure the settings is never or auto.

I am a noob, I use mpv since 4 days or so.

It's ok, but i don't think the issue is related to the script.

Win 7 / driver, anything.


problem with run on NAS

the problem to create fake display:
this error:
/startup.sh: line 62:     8 Aborted                 /usr/bin/Xvfb :0 -screen 0 "${RESOLUTION}x24" -nolisten tcp -nolisten unix
Starting LXDE
** Message: 13:15:03.462: main.vala:101: Session is LXDE
** Message: 13:15:03.462: main.vala:102: DE is LXDE

(lxsession:10): Gtk-WARNING **: 13:15:03.468: cannot open display: :0
Starting x11vnc
05/04/2023 13:15:05 passing arg to libvncserver: -rfbport
05/04/2023 13:15:05 passing arg to libvncserver: 5901
05/04/2023 13:15:05 x11vnc version: 0.9.16 lastmod: 2019-01-05  pid: 21
05/04/2023 13:15:05 XOpenDisplay(":0") failed.
05/04/2023 13:15:05 Trying again with XAUTHLOCALHOSTNAME=localhost ...

05/04/2023 13:15:05 ***************************************
05/04/2023 13:15:05 *** XOpenDisplay failed (:0)

*** x11vnc was unable to open the X DISPLAY: ":0", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.

Some tips and guidelines:

** An X server (the one you wish to view) must be running before x11vnc is
   started: x11vnc does not start the X server.  (however, see the -create
   option if that is what you really want).

** You must use -display <disp>, -OR- set and export your $DISPLAY
   environment variable to refer to the display of the desired X server.
 - Usually the display is simply ":0" (in fact x11vnc uses this if you forget
   to specify it), but in some multi-user situations it could be ":1", ":2",
   or even ":137".  Ask your administrator or a guru if you are having
   difficulty determining what your X DISPLAY is.

** Next, you need to have sufficient permissions (Xauthority)
   to connect to the X DISPLAY.   Here are some Tips:

 - Often, you just need to run x11vnc as the user logged into the X session.
   So make sure to be that user when you type x11vnc.
 - Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
   file may be accessed.  The cookie file contains the secret key that
   allows x11vnc to connect to the desired X DISPLAY.
 - You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
   by the -auth option, e.g.:
       x11vnc -auth /home/someuser/.Xauthority -display :0
       x11vnc -auth /tmp/.gdmzndVlR -display :0
   you must have read permission for the auth file.
   See also '-auth guess' and '-findauth' discussed below.

** If NO ONE is logged into an X session yet, but there is a greeter login
   program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
   to find and use the raw display manager MIT-MAGIC-COOKIE file.
   Some examples for various display managers:

     gdm:     -auth /var/gdm/:0.Xauth
              -auth /var/lib/gdm/:0.Xauth
     kdm:     -auth /var/lib/kdm/A:0-crWk72
              -auth /var/run/xauth/A:0-crWk72
     xdm:     -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
     dtlogin: -auth /var/dt/A:0-UgaaXa

   Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.

   Starting with x11vnc 0.9.9 you can have it try to guess by using:

              -auth guess

   (see also the x11vnc -findauth option.)

   Only root will have read permission for the file, and so x11vnc must be run
   as root (or copy it).  The random characters in the filenames will of course
   change and the directory the cookie file resides in is system dependent.

See also: http://www.karlrunge.com/x11vnc/faq.html
Starting noVNC
WebSocket server settings:
  - Listen on :6901
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from :6901 to <IP_ADDRESS>:5901
<IP_ADDRESS> - - [05/Apr/2023 13:15:42] <IP_ADDRESS>: Plain non-SSL (ws://) WebSocket connection
<IP_ADDRESS> - - [05/Apr/2023 13:15:42] <IP_ADDRESS>: Path: '/websockify'
<IP_ADDRESS> - - [05/Apr/2023 13:15:42] connecting to: <IP_ADDRESS>:5901
<IP_ADDRESS> - - [05/Apr/2023 13:15:42] Failed to connect to <IP_ADDRESS>:5901

Hey there, thanks for opening this issue and for using this software! May I ask you some more details about the environment (e.g. Docker version, OS) and what is the command / docker-compose file you are using to spin this up?

I have qnap with armv7 procs alpine

Could you please tell me what is the digest of the specific desktainer Docker image you are using?
Thanks :)

I didn't ask you that. Please read carefully. There is no supervisor running in this Docker image :)

Sorry I had tried the same versions and I answered you wrongly about version  ahahah anyway this is the mistake it gives me

Latest

See https://github.com/dmotte/desktainer/issues/7 which is basically the same issue.


Can I use environment variables with it?

Hi.
Is it possible to pass env variables as SCSS vars on build time?

Put it like this (nuxt2):
      loaders: {
        scss: {
          additionalData: `
            $asset-path: "${process.env.PUBLIC_BASE_URL}frontend-assets/";
          `
        }
      },


Enable eslint

Thanks for the review @simonbrunel. I created a new branch on my local machine for the rollup stuff and made this one just turn on eslint for now. There's lots of PRs with lint issues, so hopefully that will help get through the reviews. I turned off the require errors that eslint was causing since they'll get resolved by the switch to rollup after merging the existing PRs


Line Endings fix to force LF line endings for Windows users

Am I crazy or do the initial spaces show up as non-printable characters? Git is also marking it as a binary file.


[BUG] ProtectedRoute.jsx gives Uncaught NS_ERROR_ABORT

This is the error I get in my console, I mainly see this when I am navigated to the main view at the root route '/'
Firefox 116 mentions that it is coming from ProtectedRoute.jsx line #5
 const token = JSON.parse(localStorage.getItem('token'));

Here is the associated error:
Uncaught NS_ERROR_ABORT:
    UserAuthenticated ProtectedRoute.jsx:5
    React 11
    workLoop scheduler.development.js:266
    flushWork scheduler.development.js:239
    performWorkUntilDeadline scheduler.development.js:533
    js scheduler.development.js:571
    js scheduler.development.js:633
    factory react refresh:6
    Webpack 24
        __webpack_require__
        fn
        js
        factory
        __webpack_require__
        fn
        js
        js
        factory
        __webpack_require__
        fn
        js
        factory
        __webpack_require__
        fn
        js
        factory
        __webpack_require__
        fn
        js
        factory
        __webpack_require__
        <anonymous>
        <anonymous>

I think this issue is resolved.  Not sure.
I think this 's a protected route problem.   @LOGESH-B @BlackBond06 etc
I want to go through and eliminate issues etc that are completed.

I think it has. I don't get the error on both Microsoft Edge and Chrome browsers I haven't tested it on FireFox tho.

Ok @BlackBond06.  I have not seen this error lately either.  Just wanted to confirm before I close this as completed.

Closing as completed.


Ability to have diffrent isort configurations for diffrent file extension

With isort 5.0.0 it's now possible to format pyx in addition to the traditional .py files.
my sorting order in .py files is different than my sorting order in .pyx files.
Is there an option to have different configuration for different file extensions?

Currently, no, but i think this would be a great feature for isort to add

This is implemented in develop and will find it's way out in the 5.3.0 release:
isort now has in both the config and CLI arguments, support for setting blocked_extensions and supported_extensions. This allows creating two config files, one that specifies sorting pyx files and another that specifies sorting pyfiles. Then isort would need to be executed per a config defined:
isort --settings-path .isort.cfg .
isort --settings-path .cython.isort.cfg .
Thanks!
~Timothy

This has now been released


Remove docs from istio/istio as they are now in istio/community instead

@geeknoid: Adding do-not-merge/release-note-label-needed because the release note process has not been followed.

One of the following labels is required "release-note", "release-note-action-required", or "release-note-none".
Please see: https://github.com/kubernetes/community/blob/master/contributors/devel/pull-requests.md#write-release-notes-if-needed.
Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@geeknoid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-presubmit.sh
ca17ad2ea86936b3d734a25b70b76692bac4e76f
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


I have found a bug.

import k from "is-odd-and-even";

const l = s => {
    try {
        return k(s);
    } catch (e) {
        return false;
    }
}
for (const i of [
    "", " ", "a", 1, 2, 3, 4, 0, -1, -4, Infinity, -Infinity, NaN, -NaN, Number("-0"), undefined, 10n, 1n, 0n, -1n, 1e8, 2e5,
    true, false, Symbol(), new Error
]) console.log(l(i));

Every single time it logs out false. It doesn't log anything other than false.

yeah this library is pretty useless tbh. its just a glorified "return false" function.


[fix] sys mail_logs decode

Coverage decreased (-12.2%) to 55.243% when pulling 331e8994bd4e8d795a01e28cec2ac829a75e7d34 on itowtips:fix-sys-maillog into 26e7482743a8d21b16dd3a6f6bef1e2c827c3cb8 on shirasagi:master.


kubectl-flame does not take into account the node taints

I tried to profile a pod that runs on a certain type of node that has a taint, e.g.:
taints:
  - effect: NoSchedule
    key: some-key
    value: some-value

The job/pod that is launched by kubectl-flame, however, does not have tolerations for such taints, which makes it impossible to actually run the pod

I see... so specifying nodeName "disables" the taint or make it irrelevant?

it bypasses the k8s scheduler totally and corresponding kubelet on the node will pickup the workload.

Hi @casidiablo @yashbhutwala
This issue is now fixed, if you installed via krew upgrading is as simple as:
kubectl krew upgrade


support to build with VS2022 and sync latest libspdm

Signed-off-by: BinbinLee<EMAIL_ADDRESS>

Would you please remove  /wd4819 ?
See https://github.com/DMTF/libspdm/issues/1116

The new request was submitted in #137 .


The step operation is error when the SW bp is set in a J instruction.

Hi Guys：
I use the Ibex core running a simple test C code.
I set a SW bp before a “jump” instruction,  when the cpu fetched the SW bp instruction, the cpu is halted.
But after that, i use the “step" cmd in telnet,  the PC in CPU is wrong, it's not the correct PC which the JUMP instruction expected , the dpc has been changed.
When I use the HW bp， the dpc has‘t been changed.
So, i think this is a bug
please see the following figure.

@GregAC Could u help me checking this issue？ Thanks

I think this is an issue with Ibex's EBREAK handling, it's setting the depc for the instruction following the EBREAK not the EBREAK itself.
From what I can tell from the waveform you've supplied, Ibex is first fetching the instruction immediately following the jal 0x30000090, which is the instruction at 0x300006c2 (fetches are aligned so it fetches at 0x300006c0). The instruction at that address is a 4-byte EBREAK (0x00100073) which is split across 2 instruction fetches as it's unaligned.
Ibex executes that EBREAK giving you depc = 0x300006c6 which is the address of the instruction after the EBREAK where it should produce depc = 0x300006c2
From a brief look at the RTL this should work correctly and uses the same mechanism as normal exceptions (and indeed it is tested in the verification environment) so there may be something more complex going on that causes it to break. If you could provide a full .vcd of the failure that would be useful in debugging it.

I would guess that enter_debug_mode is set when the core goes to FLUSH as a result of the EBREAK. That causes the core to go to DBG_TAKEN_IF rather than DBG_TAKEN_ID hence it captures the wrong PC.
What debug module are you using? and did you definitely clear the HW breakpoint before setting the SW breakpoint?

@tomroberts-lowrisc
Thanks for your response.
tomroberts-lowrisc:  I would guess that enter_debug_mode is set when the core goes to FLUSH as a result of the EBREAK. That causes the core to go to DBG_TAKEN_IF rather than DBG_TAKEN_ID hence it captures the wrong PC.
apolloJason:  yes, please see the following figure. The SW bp has changed the jal instruction to c.ebreak. So the CPU enter debug_mode and goes to FLUSH, the controller FSM state is DBG_TAKEN_ID, the debug_csr_save is active. But the current PC has been changed in if_stage. The debug_csr_save signal and changed PC caused the wrong dpc in csr register.
tomroberts-lowrisc: What debug module are you using? and did you definitely clear the HW breakpoint before setting the SW breakpoint?
apolloJason: 1. I use the pulp riscv-gdb module, cloned from github.
2. I didn't set any HW bp, just use a SW bp.
3. I think the cpu matched a HW bp function is corrected，i have finished a test, just set a single HW bp in the jal instruction, the same PC.
4. When I set the SW bp，there is not any HW bp in the CPU trigger.

@tomroberts-lowrisc
I set the SW pc in 0x300006c2 ，the J instruction.
That's a while(1){}; test in the C function.

@GregAC @tomroberts-lowrisc
Hi :
the cv32e40p has the same bug. They has fixed the bug for storeing the next instruction PC.
Could you double check again?

From the latest wave you've given Ibex is going into DBG_TAKEN_IF as enter_debug_mode is asserted.
An EBREAK doesn't assert enter_debug_mode so there's something else going on here as well as the EBREAK instruction. Either the debug module has requested to enter debug mode, single stepping is active or there's a hardware breakpoint too.
As I said above a full .vcd would be helpful in debugging (this could be large so gzip it or use .fst which is the GTKWave file format, I think it has a .vcd to .fst conventor available as part of GTKWave).

Single stepping is active, which causes the entry to debug mode. I'm not really sure what the core is supposed to do here (single stepping over an EBREAK instruction), it's probably doing the correct thing and stepping to the "next" instruction.
The debugger should replace the EBREAK with the real instruction before it releases the core to step. I attempted to reproduce this locally but I don't hit this behavior (I get the correct instruction replaced as expected). You might want to try updating your gdb and OpenOCD versions?

Ah had missed the debug_single_step_o signal the bottom there.
From the debug spec's description of single stepping:

If the instruction does not complete due to an exception, the hart will immediately enter Debug Mode before executing the trap handler, with appropriate exception registers set.

EBREAK causes an breakpoint exception (if dcsr.ebreak[m|s|u] isn't set). So EBREAK isn't failing to complete due to an exception, it completes which causes the exception. So I'd argue when single-stepping over an EBREAK you should get a dpc of the next instruction to execute which is the first instruction of the exception handler.
If dcsr.ebreak[m|s|u] are set then I'd argue you'd effectively ignore the single step and enter debug mode as normal for an EBREAK when dcsr.ebreak[m|s|u] are set (executing the instruction enters debug mode, at which point single stepping would take over but you don't single step in debug mode).

Yeah I think that makes sense.
Looking at the issue raised by @apollojason on cv32e40p, they have changed it such that the EBREAK is prioritized here on debug entry rather than the step (thus capturing the ID stage PC rather than the IF stage). We should probably do the same - though only in the ebreakm/u case as you noted.

Hi @apollojason can you try again with the linked fix - if it fixes the problem, we can close this issue

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

thank you for explaining it so fully.
I got sick recently, so i didn't give u a response. Tomorrow, i can get the new version code,try again.
thanks!

@tomroberts-lowrisc @GregAC
Hi :
I have try again with the latest version ibex CPU RTL. It is working correctly.
thank u very much!


Removed generator expression tests

@rultor, release tag is 0.0.20

@rultor, release tag is 0.0.20

@andrewg0r @bugdea1er Invalid release tag 0.0.20 specified. There is already a release 0.0.20 newer than the given release in this repository.

@rultor, release tag is 0.0.20

@andrewg0r I'm sorry, I don't understand you :( Check this page and try again please


Virtus hogs initialize()

If I include Virtus in my class, it adds a method initialize to do it's magic. This is mostly a good thing, but it means that I cannot compute and set non-Virtus instance variables at object creation time. I'd like to be able to do this.

Can you not declare your own #initialize method, call super within it, and then do your own stuff after?

... i swear I tried that and it didn't work, but I just tried it again and you're right. my bad. lousy afternoon :)

No problem. Virtus was designed so that you could override #initialize and supply you're own. You don't even have to call super if you don't care about assigning the args to self.attributes, eg:
def initialize(name, email)
  @name, @email = name, email
end

There are cases where you might want to declare a constructor with positional arguments, and then set the internal state on your own. Or you can delegate to super, eg:
def initialize(name, email)
  super :name => name, :email => email
end

There aren't any rules when it comes to how #initialize should work. The main reason Virtus provides one is to have a sensible default, but you can always override it to do whatever you need.

While we're talking, is there a way to do something like
class Foo; def initialize; @bar = 'baz'; end end
class SubFoo < Foo; include Virtus; end

and have SubFoo.new set @bar?

Right now Virtus' #initialize method doesn't call super. It probably should, even if that's a noop most of the time.
I think we'd accept a patch for that if you're interested in writing one with a spec.

I may do so, in my Copious Free Time ;)

I know this has been closed for quite sometime now but how would I make it possible that I set an initializer and if no options were passed matching the attribute it uses the default set?
def initialize

end

Maybe you could override .new and handle this logic there.


support Windows separators in path_dispatch

While setting up Windows CI for promnesia, the takeout tests failed and had these in logs:
2022-05-09T21:03:56.5877916Z [INFO    2022-05-09 20:58:14 promnesia extract.py:49] extracting via promnesia.sources.takeout:index ...
[W 220509 20:58:14 path_dispatch:270] No function to handle parsing My Activity\Chrome\MyActivity.html
[W 220509 20:58:14 path_dispatch:270] No function to handle parsing My Activity\Chrome\README

I guess it's because in path_dispatch forward slashes are hardcoded. Perhaps the quickest fix would be to do something like .replace(os.sep, '/') here -- paths in takeout shouldn't have either forward or backwards slashes anyway https://github.com/seanbreckenridge/google_takeout_parser/blob/master/google_takeout_parser/path_dispatch.py#L94

Ah right - must've made a mistake not removing the \ escaping from the path strings after converting them to regex strings.
I think would make sense to leave the maps intact (other than fixing the backslash issues), and then modify the string in the _match_handler function? Think that would be easier to read

Yep, agree, easier to keep maps as simple strings (hence the suggestion to just hack during the regex matching)!
Ah yeah -- could be the other way around depending on whether we want to patch the regex or the path. Path felt easier since means less modifications for regex (who knows how it could get in the way of escaping :) ), but don't mind either way

yeah, the promnesia config it's the most up to date  one
https://github.com/karlicoss/promnesia/blob/master/.github/workflows/main.yml
On Tue, May 10, 2022, 17:18 seanbreckenridge @.***>
wrote:

Could you link me to the windows CI -- might as well add a windows CI here
as well so these issues are caught...
—
Reply to this email directly, view it on GitHub
https://github.com/seanbreckenridge/google_takeout_parser/issues/32#issuecomment-1122607884,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHEBPGGESNQPVTR7QSXGTVJKD37ANCNFSM5VPRNH5A
.
You are receiving this because you authored the thread.Message ID:
@.***>

should be resolved @karlicoss , let me know if the CI is still failing

thanks, the takeout tests are working now! 👍
On Thu, May 12, 2022, 23:45 seanbreckenridge @.***>
wrote:

should be resolved @karlicoss https://github.com/karlicoss , let me
know if the CI is still failing
—
Reply to this email directly, view it on GitHub
https://github.com/seanbreckenridge/google_takeout_parser/issues/32#issuecomment-1125484734,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACHEBLYY5HKXGEBKWC2S73VJWCXFANCNFSM5VPRNH5A
.
You are receiving this because you were mentioned.Message ID:
@.***>


f4xx-hal like gpio

Hey, sorry for the delay, I'm pretty busy right now. I hope I'll make progress on this review this week.


bosh-cli bash-completion breaks file bash-completion

brew install bosh-cli
touch bosh-init.yml
bosh2 create-env bo

Nothing happens although there is a file bosh-init.yml

Workaround for now: manually remove /usr/local/etc/bash_completion.d/bosh-cli

FWIW, we had a similar problem with the cf CLI.
Although we addressed it in code (explicitly implement a filepath completer for all relevant arguments), there may also be a one-line fix in the completion file (adding -o default to the complete command?).
Take care with the flags to complete, some are not available on all distributions and Bash versions.

@dkoper Are you aware of -o default not being available somewhere? Why did you decide to implement a filepath completer instead? It is only roughly behaving like regular bash folder and file completion. For instance, completing a folder always adds a space after the slash and one has to delete the space in order to continue completion in the folder.

@friegger We found the -o default flag after we implemented the filepath completer. I can't find the statement anymore about it not being available. Maybe it related to -o bashdefault with pre-4.0 Bash but honestly, no idea..

Closing - seems like this was fixed as part of cloudfoundry/bosh-cli#361.


Ensure text remains visible during webfont load

Font display: https://developers.google.com/web/updates/2016/02/font-display
Would be nice to include this function as service worker in the fast google fonts script streamer?
https://medium.com/@pierluc/supercharge-google-fonts-with-cloudflare-and-service-workers-25c37462fb6a
Repo: https://github.com/Zertz/font-workers
Possibility to also optimize fontawesome v4.7 and v5 to extend the workers to also optimize local font by adding such functions to the worker script.

Right now this is a local solution to it, but would be better to have it in the worker and streamer: https://metabox.io/load-google-fonts-wordpress/
Working good as a snippet
add_action( 'wp_head', 'themeprefix_load_fonts' );
function themeprefix_load_fonts() {
    ?>
<!-- Code snippet to speed up Google Fonts rendering: googlefonts.3perf.com -->
<link rel="dns-prefetch" href="https://fonts.gstatic.com">
<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin="anonymous">
<link rel="preload" href="https://fonts.googleapis.com/css?family=Roboto" as="fetch" crossorigin="anonymous">
<script type="text/javascript">
!function(e,n,t){"use strict";var o="https://fonts.googleapis.com/css?family=Roboto",r="__3perf_googleFontsStylesheet";function c(e){(n.head||n.body).appendChild(e)}function a(){var e=n.createElement("link");e.href=o,e.rel="stylesheet",c(e)}function f(e){if(!n.getElementById(r)){var t=n.createElement("style");t.id=r,c(t)}n.getElementById(r).innerHTML=e}e.FontFace&&e.FontFace.prototype.hasOwnProperty("display")?(t[r]&&f(t[r]),fetch(o).then(function(e){return e.text()}).then(function(e){return e.replace(/@font-face {/g,"@font-face{font-display:swap;")}).then(function(e){return t[r]=e}).then(f).catch(a)):a()}(window,document,localStorage);
</script>
<!-- End of code snippet for Google Fonts -->
    <?php
}

Even preload critical font not only google fonts, all fonts that are used above the fold. Custom fonts, icons etc? just wild card all .woff*?

@alriksson Google has come up with a new query that supports injecting font-display: swap to the @font-face. So I guess it's better to do it from WordPress itself. See https://wpspeedmatters.com/fix-foit-font-in-wordpress/

@gijo-varghese Googlefonts the workers streamer already take care of the issue is icon font packs. And to alter parent code which will be flushed sooner or later, it would be better with a php routing or adding something in the workers for all types of woff's.

@pmeenan could we sort font-display: Swap to the google fonts optimization?
@gijo-varghese if doing manually in wordpress I would like to inject it with a php script to not alter theme or plugin files which are where google fonts come from. Any solution?

@alriksson my plugin only fix Googe Fonts (asynchronously injected won't work). I may create a plugin that will fix both soon

Closing this issue because the initial question was addressed. Also the templates have moved over to the worker-sdk monorepo: https://github.com/cloudflare/workers-sdk/tree/main/templates.
if you're still experiencing issues feel free to open an issue there.


React 16 support

Hi @dtschust, thanks for building redux-bug-reporter! I have one question though. Do you have any plans to support React 16 in order to get rid of the deprecation warning regarding React.createClass in React 15.5?

Hi @akoenig , thanks for asking! Yes, I plan to support React 16 eventually, but I'm not spending a lot of time lately on redux-bug-reporter. I'll probably look into it once React 16 launches. I also accept PRs if you'd like to take a crack at it!

Awesome! :) Now where React 16 landed, do you have time for that? :)

Hi @akoenig , I'll try and get to this in the next few weeks, but am also willing to accept PRs if you need it more urgently :)

@akoenig I've got a rough branch that I think seems to be working fine with React 16, although my unit tests are failing due to some bugs in the newest version of enzyme. The commits are all over the place and I'll tidy them up before merging, but I'd love feedback if you can confirm how it works for you: https://github.com/dtschust/redux-bug-reporter/tree/bump-versions

Ah @dtschust, that is awesome. Thanks for putting time into it and sorry that my request seemed a bit needy. I just hadn‘t the time to compile the PR 😕
I will work on an app that has to be migrated to React 16 and which uses the Redux Bug Reporter in the next week. Will be able to test the branch then.
Thanks a thousand times for your efforts!

@dtschust  Was this ever completed?

@jrball3 sorry, but I'm not actively maintaining this package at the moment. I have an abandoned work in progress branch as listed above that should work with React 16 if you want to try that!


Storybook cleanup part 1

This PR is to cleanup our storybook story.
This main goal is to move existing ones to storybook

[x] deprecate dumb sheet (current: common/dumb)
[x] cleanup hierarchy of stories
[x] fixup profile file naming
~- [ ] placeholders for all storybook components (for part 2)~

@keybase/react-hackers this is ready, next branch coming soon


about the cityscape_generator.py

a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType

Please checkout the path of your data


Epic: Schema parsing and validation

Parse contents of file

Ensure it complies with W3C CSV-W spec

[x] #17 Learn csv-w schema structure

[x] #21 Create PropertyChecker to be used in TableGroup schema load & validate

[x] #18 Create class Csvw::TableGroup with load from json method

[x] #15 Create schema class with function to load from csvw-metadata

[ ] #47 Introduce dependency injection

[x] #51 Ensure that schema file path can work as web urls or files

Done the majority of this, still keeping the DI issue open.


Sarthak815 patch 1

I have added 2 algorithm hackerrank problems

I have added question link at top of both files


disabled obsolete pr-jobs and fixed seed job not to create them any more

the this is part of #754 - so this PR can be closed


feat: add deltatime kwarg to chain.mine

What I did
added deltatime capability to chain.ChainManager.mine
fixes: #569
How I did it
Added the deltatime kwarg to ChainManager.mine
How to verify it
Create test (will do following some back and forth) and test the new mining capability
Checklist

[ ] All changes are completed
[ ] New test cases have been added
[ ] Documentation has been updated

I probably should have left this issue. I thought it was more complicated at first, then realized we have a converter for this, so it was really much simpler than I previously thought

Yeah, maybe try changing the typing and let pydantic handle it for you?

@NotPeopling2day can you give me an example of what you mean

@NotPeopling2day can you give me an example of what you mean

Apologies, when I quickly looked at this I thought it was a part of the BlockAPI we were working on yesterday.

It would be nice to have some context on the ValueError as well.
It looks like it is just raising ValueError with no message, so users may not know what has gone away


[MINOR][SQL][DOCS] Fix some wrong default values in SQL tuning guide's AQE section

What changes were proposed in this pull request?

spark.sql.adaptive.coalescePartitions.initialPartitionNum 200 -> (none)
spark.sql.adaptive.skewJoin.skewedPartitionFactor is 10 -> 5
Why are the changes needed?

the wrong doc misguide people
Does this PR introduce any user-facing change?

no
How was this patch tested?

passing doc

cc @maropu @cloud-fan thanks

Test build #135681 has started for PR 31717 at commit aa2c6a6.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40263/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40263/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40263/

Merged to master, branch-3.1 and branch-3.0.

Test build #135681 has finished for PR 31717 at commit aa2c6a6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/135681/


Helm 3 support

Hello, guys!
Amazing project! Looks like exactly what I’m looking for.
Just some probably weird question for me, if Helm 3 is supported? I know it’s still alpha, but it still works well for us even in this stage, will be happy to use werf with third version of Helm. If not supported yet, pls let me know your roadmap to upgrade to next version of Helm.
Best regards,
Alexey Zhokhov.

Hi! Thanks!
Werf now have built-in helm 2 client and tiller. It works the same way as helm 2 (same release storage, fully compatible, etc.). But the only difference is that tiller process and werf process are the same single process. So to use helm 3 we must compile werf agains new helm 3 codebase.
Werf is not compiled with helm 3 for now. The main reasons are: there should be clear and durable way to migrate from helm 2 installations to helm 3 (https://github.com/helm/helm/issues/5892); it is alpha.
We will certainly update to helm 3 some day.
Public roadmap will also be available at the https://werf.io soon.

@distorhead https://github.com/helm/helm/releases/tag/v3.0.0 just released!

Any plans/ETA here?

👍

Some notes for future implementation:

werf should not auto-purge first failed release, remove this dangerous feature when ported to helm 3;
update masterminds/sprig library;
CTRL-C + wait + atomic release status updates;
3 way merge should solve a problem when a kubernetes cluster has been updated, but there are resources deployed which have outdated api versions definitions in the release.

Any plans/ETA here?

It is not a priority task for now, because it will add nothing new and valuable to the werf. Werf do have all main features that Helm 3 have: three way merge and tillerless architecture.
But we should switch to Helm 3 in v1.2 version.

Good day. Thanks, could you say, when 1.2 is planning?

Update. Happy to announce, that we have "migration to Helm 3" task in the nearest plans of big tasks. I think we will implement usable Helm 3 support in 1 month approximately.

As for now, there is very early alpha version: v1.1.22-alpha4 — which available in the alpha channel. This version embeds all helm-v3 commands into werf helm-v3 subcommand and adds support for kubedog-based waiting for resources. For example:
werf helm-v3 upgrade --namespace myproj myproj . --install --create-namespace --wait

All werf deploy-process related annotations are supported as well: https://werf.io/documentation/reference/deploy_process/deploy_into_kubernetes.html#resource-tracking-configuration.
This can already be useful for someone. But we continue to work on full helm-3 support (secrets, support replicas autoscaler for 3-way-merge managed fields, resources adoption, automatically added annotations and labels to all deployed resources, etc.).

Status update.
As for now Helm 3 is experimentally avaiable in the current v1.1 version when WERF_DEPLOY_HELM_V3=1 variable is set — werf will use helm-v3 for werf deploy/dismiss commands in this case.
Also we are working on werf v1.2 which is in alpha stage now. It use helm-v3 by default. There is unsolved question with automigration from existing helm-v2 installation to helm-v3 now.
Usable v1.2 should be available in october.

Here we go. Alpha and beta channel of v1.2 now contain usable version of werf with Helm 3.4.0.

werf converge command will build images defined in the werf.yaml and deploy chart using helm 3.
v1.2 uses helm 3 only and does not support helm 2.
checkout new documentation articles: https://werf.io/introduction.html, https://werf.io/documentation/quickstart.html and https://werf.io/documentation/using_with_ci_cd_systems.html.
werf helm * commands are available to work directly with helm-chart by lowlevel commands (such as install/upgrade and other), these commands use helm 3 only.

As for automigration and further steps:

Current beta version of werf can be used for new projects which does not need a migration from Helm 2.
We are working on this feature https://github.com/werf/werf/issues/2712 to publish charts bound with correct images by semver into docker registry. This feature will already be available in the v1.2 when v1.2 becomes stable.
Next step after releasing first stable v1.2 is to add automigration existing releases from helm 2 to helm 3: https://github.com/werf/werf/issues/2866.


Create Database Indexes

(closes #24)

Coverage remained the same at 100.0% when pulling 74706bd8a0e1b143a506abc5a8c187a03f85a9e2 on database_indexes into 398d54ab31a3f2e7364cbda39a170c4c9a21f45e on master.


E2e testing utxo snapshot / shared wallet receive transaction

Issue Number

Overview

9149b0a5f58a182e0cd2f3578052aec8a2ad92e8
Sanity e2e check for utxo snapshot

690b0de412a3ea1edcd96c36a217cb7e8d305c31
Test receive funds to shared wallet

Comments

bors r+

bors r+

bors r+


$ git add .

$ git add .
warning: in the working copy of 'package-lock.json', LF will be replaced by CRLF the next time Git touches it
warning: in the working copy of 'package.json', LF will be replaced by CRLF the next time Git touches it

setting the core.autocrlf configuration to false to disable automatic line ending conversion.


Add globals to eslint

Wrong pull request

Coverage remained the same at 66.86% when pulling 35b3511bb6c654e44b1f7f323f6e0d93703199ab on madtaras:add-globals-to-eslint into 989c19f0aac420dce6bb4560c86d8ec1907040f1 on mjhea0:master.


65536 vertices can crash GLES3 driver

Tested versions

Reproducible in Master, 4.3 stable, and 4.22 stable
Not reproducible in 4.1 stable

System information
Ubuntu 22.04 - Godot 4.3 - GLES backend
Issue description
On the GLES3 backend, drawing a mesh with exactly 65536 vertices will read some uninitialized data while building a wireframe in drivers/gles3/storage/mesh_storage.cpp.  In some configurations this can result in a read out of bounds and immediate editor crash, but the invalid reads can reliably be seen in valgrind.
The problem is the wireframe code added between 4.1 and 4.2 in commit  https://github.com/godotengine/godot/commit/bae6f86257ffb9bed915bcd0d6fa41e1da39894a   checks if (new_surface.vertex_count < (1 << 16)) to determine if the index data fits in 2 bytes.  That comparison should actually be a <= to match how the rendering server prepares that index buffer.  To match with the other 5 checks of this in the codebase, in the corresponding pull request I've also changed the (1 << 16) constant to 65536.
In our larger project we're using a workaround of adding one extra vertex, which works (but took a day of effort to find!).
Steps to reproduce
On GLES3 backend (compatibility mode), create a mesh with 65536 vertices and some index data, and display it.  In the attached minimal project on Linux, valgrind displays six read-beyond-end-of-buffer memory accesses when you do this.
Built with "scons dev_build=yes", valgrind will report the bad memory reads like this on 4.2 stable (along with the standard batch of false positives):
==348442== Invalid read of size 4
==348442==    at 0x3D5BA5D: GLES3::MeshStorage::mesh_add_surface(RID, RenderingServer::SurfaceData const&) (mesh_storage.cpp:322)
==348442==    by 0x645E75F: RenderingServerDefault::mesh_add_surface(RID, RenderingServer::SurfaceData const&) (rendering_server_default.h:297)
==348442==    by 0x5C35AA9: ArrayMesh::add_surface(BitField<Mesh::ArrayFormat>, Mesh::PrimitiveType, Vector<unsigned char> const&, Vector<unsigned char> const&, Vector<unsigned char> const&, int, Vector<unsigned char> const&, int, AABB const&, Vector<unsigned char> const&, Vector<AABB> const&, Vector<RenderingServer::SurfaceData::LOD> const&, Vector4) (mesh.cpp:1790)
==348442==    by 0x5C35DD1: ArrayMesh::add_surface_from_arrays(Mesh::PrimitiveType, Array const&, TypedArray<Array> const&, Dictionary const&, BitField<Mesh::ArrayFormat>) (mesh.cpp:1816)
==348442==    by 0x5DEDD20: SurfaceTool::commit(Ref<ArrayMesh> const&, unsigned long) (surface_tool.cpp:740)

In our larger project we reliably got a crash on Windows at this location.
Minimal reproduction project (MRP)
vertex65536demo_pack.zip
This project consists of this minimal gdscript example, in the GLES3 backend:
@tool
extends Node3D

func _ready() -> void:
    var st : SurfaceTool = SurfaceTool.new()
    st.begin(Mesh.PRIMITIVE_TRIANGLES)

    # the bug only shows up with exactly 65536 vertices
    for i in range(65536):
	    st.add_vertex(Vector3(i%256,i%13,i/256))
	    # need some indices for the bug to fire
	    if (i>6):
		    for back in range(6):
			    st.add_index(i-back)

    # draw the mesh
    var am : ArrayMesh = st.commit()
    var m : MeshInstance3D = MeshInstance3D.new()
    m.set_mesh(am)
    add_child(m)

Just tested the minimal example project on my Windows 10 machine, and opening that minimum reproducible test scene reliably crashes the editor on 4.3-stable and 4.2.2-stable.


Getting started example

I had a little more trouble getting everything working on jruby-head.
I have an example here https://github.com/danielhopkins/jruby-rack-benchmark that you might be interested in linking to.
Also, if I'm way off base, i'd love some input :)

JRuby 1.7, especially on Java 7, was still very much in flux last I checked (you should make sure to use at least 7u2). What were the exact problems that you encountered ?

The java 7 stuff wasn't really the problem.
I had to do some tweaking to the basic jetty.rb to get the classpath right and find a proper place to put the jetty executables. It might be helpful to someone trying to do a comparison of different technologies to have either a more full features demo or docs on how to get a complete running instance.
Still very helpful project, thanks!


Add Nanostring paper again

This was somehow lost :-(

Yeah I don't know. I tried reopening it from the original branch but the commit was already in so had to make a new one 🤷♂

Ah, no it was the revert of the astro4 upgrage https://github.com/nf-core/website/commit/7622308f45ccfe2507f15dba931a00dc4e0b8d05#diff-832368a8438a3b4ffefb7592b20dbc8ac150508ec9af96c1bde40c2dd436ae88 Sorry again.


bug: Unable to switch from drizzle-orm/vercel-postgres to drizzle-orm/node-postgres using nodejs runtime

Provide environment information
System:
  OS: macOS 15.1.1
  CPU: (10) arm64 Apple M1 Max
  Memory: 8.57 GB / 64.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 20.18.1 - ~/.nvm/versions/node/v20.18.1/bin/node
  npm: 10.8.2 - ~/.nvm/versions/node/v20.18.1/bin/npm
  pnpm: 9.14.2 - ~/.nvm/versions/node/v20.18.1/bin/pnpm
  Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman

TL;DR
I've hit a wall trying to switch the Postgres driver in the create-t3-turbo template from drizzle-orm/vercel-postgres to drizzle-orm/node-postgres. While database migrations are working fine, the app keeps failing during startup and hydration in different Node.js environments. I'm seeing net.Socket errors and Edge runtime issues with the Node.js crypto module. I've tried several workarounds, but nothing's sticking.
Describe the bug
I've run into some frustrating runtime compatibility issues while trying to swap out the Postgres driver in the create-t3-turbo template. Here's what I'm seeing:

On Node v22.12.0, I'm getting hit with net.Socket constructor errors in the Next.js React Server Components (RSC) environment
On Node v20.18.1, I'm running into Edge runtime issues with the Node.js crypto module and missing pg-native dependencies

The weird part? Database operations like schema migrations using drizzle-kit push work perfectly fine. It's just when the app tries to start up that everything falls apart.
Link to reproduction
https://github.com/LinnJS/t3-turborepo-node-pg-driver/pull/1
To reproduce

Clone the my reproduction repository .
Pull origin git fetch origin main
Switch branch git checkout feat/add-pg-driver
Install pnpm install --filter @acme/nextjs...
Run http://localhost:3000 pnpm dev --filter @acme/nextjs...

Previous Attempted Workarounds
I've thrown quite a few potential solutions at this problem:

Removed all "Edge" exports from the project
Tweaked the Webpack config in next.config.js to exclude problematic Node.js modules
Verified that CLI database operations work (they do!)
Even got it working in a closed-source project by suppressing similar errors, but can't replicate that success in a clean setup

Despite all these attempts, the issue keeps showing up during runtime when using the Node.js runtime.
Additional information
Introduction
Hey there! I've been diving deep into the create-t3-turbo template and hit some pretty significant roadblocks while trying to switch database drivers. My goal was to use the node-postgres driver for better compatibility with self-hosted setups, but I'm running into walls with both RSC and Edge runtime environments.
Description
The problems started when I tried switching from drizzle-orm/vercel-postgres to drizzle-orm/node-postgres in the packages/db and packages/api directories. I'm seeing runtime errors related to Node.js native modules like net and crypto. It seems to be tied to Next.js runtime limitations.
Error Messages
Original Repository (Node v22.12.0)
TypeError: net.Socket is not a constructor
    at getStream (webpack-internal:///(rsc)/../../node_modules/pg/lib/stream.js:23:12)
    at new Connection (webpack-internal:///(rsc)/../../node_modules/pg/lib/connection.js:18:36)
    at new Client (webpack-internal:///(rsc)/../../node_modules/pg/lib/client.js:48:7)

Reproduction Repository (Node v20.18.1)
Error: The edge runtime does not support Node.js 'crypto' module.
Learn More: https://nextjs.org/docs/messages/node-module-in-edge-runtime
    at <unknown> (webpack-internal:///(middleware)/../../node_modules/next/dist/esm/server/web/globals.js:34)

And just to make things more interesting, I'm also seeing this in the reproduction:
Module not found: Can't resolve 'pg-native' in '/Users/.../node_modules/pg/lib/native'

Import trace for requested module:
../../node_modules/pg/lib/native/client.js
../../node_modules/pg/lib/native/index.js
../../node_modules/pg/lib/index.js
../../packages/db/src/client.ts
../../packages/auth/src/config.ts
../../packages/auth/src/index.ts

Reproduction Repository
t3-turborepo-node-pg-driver
Related Discussions
Discord Thread Reference
If you want to join the discussion, I've started a thread in Theo's Typesafe Cult
Additional Context
From what I can tell, these errors are popping up because of how Next.js interacts with Node.js native modules in RSC and Edge runtime environments. This feels more like a fundamental runtime compatibility issue rather than just a configuration problem.
Expected Behavior
In an ideal world, the app should just connect to Postgres using the node-postgres driver without throwing fits about net.Socket, crypto, or pg-native. It should run smoothly on the Node.js runtime like any other normal app.
Questions
I'm still wrestling with these questions:

Is there a "right way" to use node-postgres with Next.js RSC?
Are there known limitations I should be aware of?
How are others handling Node.js native modules in the Edge runtime?

Contributing Back to the Community
Once we crack this, I'd love to give back by:

Writing up a detailed guide on switching from vercel-postgres to node-postgres
Documenting all the configuration changes and workarounds needed
Sharing best practices for using node-postgres in Next.js RSC/Edge environments
Warning others about the pitfalls I've discovered

Thanks in advance for any help or insights you can share! Let's figure this out together.

We've experienced this in the past and this is because the middleware always is set to "edge" and what was done in the past is to use pg-proxy or some other setup that allows you to use something else this can be worked around if you adjust the auth config also explained here: https://authjs.dev/guides/edge-compatibility#middleware

https://github.com/vercel/next.js/discussions/46722


Bugfixes

A few small bug fixes / nits:

Body Stream to use "\r\n" rather than newline UInt8's (it's faster, don't ask me why)
Ensure that if transfer-encoding=chunked content-length is removed and vice versa if content-length is set and transfer-encoding=chunked remove transfer-encoding
Add a bounds check on Buffer

Current coverage is 80.63% (diff: 72.72%)

Merging #169 into master will increase coverage by 0.01%

@@             master       #169   diff @@
==========================================
  Files           178        178
  Lines         13019      13025     +6
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits          10496      10503     +7
+ Misses         2523       2522     -1
  Partials          0          0

Powered by Codecov. Last update 764de8c...801c1e5


make keybase encrypt/decrypt work with teams and per user keys

@maxtaco can you please take a first look?
I still have to address some todos here and there (and add a lot of tests), but wanted to get a quick opinion before you go on vacation.

I am going to start rebasing this (tomorrow morning) on top of https://github.com/keybase/client/pull/12948/ while we wait for that to get merged...

@maxtaco I changed the defaults as agreed. This is good to go on my end. Note the version bump.

OK, let's do it! 👍
(where is the version bump?)

https://github.com/keybase/client/pull/12724/commits/c945d24af494380cf159fb2d2444eda8345d5d76

@cjb would have to weigh in on the version bump

he suggested that I add it to this PR, but let's still wait on a :+1: from him.


Remove enabling Cydia Store purchases in to do list

Since saurik isn't planning to bring Cydia Store back up, this probably won't happen and should be removed from the to-do list.

Nvm - closing for now as I see that you're waiting for info from saurik on what he's gonna do.


TensorFlow Certificate Network - region - australiasia

https://developers.google.com/certification/directory/tensorflow
select australia for region is not available due to incorrect name shown as australiasia.
selecting australiasia shows noting nether australia or Asia.
I just passed Tensorflow exam and want to show my profile correct in australia.

@BrianHwang
Kindly open a tf discussion forum issue for this as it is not a bug or feature request, Please post this kind of support questions at Stackoverflow. There is a big community to support and learn from your questions.
Thanks!


Visual regression testing!

Fixes https://github.com/perseids-tools/treebank-react/issues/10
Use BackstopJS to add visual regression testing. Combined with the unit tests, I think this gives us relatively good test coverage.
The changes within the visual-test/ directory are all Backstop boilerplate except for backstop.json, which specifies the screen size and URL for the test, and test_Treebank_renders_correctly_0_document_0_tablet.png, which is the image used in comparisons.

Thanks @balmas!

Thanks @balmas!


Is there a way to keep moving nodes inside the canvas boundaries?

I am trying to make the moving nodes not go beyond the canvas width and height. I initially thought I can restrict the node position to be in this boundary {-canvas.width/2, canvas.width/2} and {-canvas.height/2, canvas.height/2} but the position of nodes seem different than what I expected.
Can someone please guide me on how should I proceed? I tried using this.vizceral.currentGraph.layoutDimensions, but looks like this is also not the right dimensions for full canvas. Where are the correct the height and width dimension of vizceral stored which can be used to create canvas boundary?
Thanks

Currently this is what I am doing in moveNodeInteraction.js:
This creates a boundary around the canvas but as you resize the vizceral window, its doesnt always takes the shape of resized window. Any suggestions are welcome.
onDocumentMouseMove (event) {
if (this._state === 1) {
if (this._lastMBPress_pressedObj_isDraggable) {
const mouseLocVPSpace = new Vector2(0, 0);
getMouseLocInVPSpace(event, mouseLocVPSpace);
const tx = mouseLocVPSpace.x - this._lastMBPress_mouseLocInVPSpace.x;
const ty = mouseLocVPSpace.y - this._lastMBPress_mouseLocInVPSpace.y;
const t = doubleSqrt((tx * tx) + (ty * ty));
if (t > 10) {
this._onDragStart();
}
}
} else if (this._state === 2) {
this.vizceral.validateRaycaster(event.clientX, event.clientY);
const o = this.vizceral.raycaster.ray.origin;
var layoutWidth  =  this.vizceralthis.vizceral.currentGraph.layoutDimensions.width;
var layoutHeight = this.vizceralthis.vizceral.currentGraph.layoutDimensions.height;
var xBound = {left: -layoutWidth/2, right: layoutWidth/2};
var yBound = {bottom: -layoutHeight/2, top: layoutHeight/2};
var mouseLocX = this._lastMBPress_mouseLocInGraphSpace.x;
var mouseLocY = this._lastMBPress_mouseLocInGraphSpace.y;
const dx = o.x - this._lastMBPress_mouseLocInGraphSpace.x;
const dy = o.y - this._lastMBPress_mouseLocInGraphSpace.y;
var newX = this._lastMBPress_pressedObj_pos.x + dx;
var newY = this._lastMBPress_pressedObj_pos.y + dy;
  if (newX > xBound.right || newX < xBound.left)
  {
	if( newX >= xBound.right){
		newX = xBound.right;
	  }
	  if(newX <= xBound.left){
		newX = xBound.left;
	  }
  }

  if (newY > yBound.top || newY < yBound.bottom)
  {
	  if( newY >= yBound.top){
		newY = yBound.top;
	  }
	  if(newY <= yBound.bottom){
		newY = yBound.bottom;
	  }
  }

  this._setDraggableObjectPosition(this._lastMBPress_pressedObj, newX, newY);
}

}
Thanks a lot for your help!

We do not use the particle positioning physics internally , and since the developer of it, @jbrekelmans, has not been active here for some time, I'm going to close this. However, I will happily review a PR that would modify this behavior.


Issue 32: Add modes to internal systemtest builds

What does this do and can the repetition be avoided?

There is a lookup (modes.xml) file which can be used to turn a 'mode' (e.g. Mode100) into a string of java -X options (e.g. -Xint -Xgcpolicy:gencon).
However, this has the downside of having to look up the mode mnemonic in order to know what the test is actually running with.  It also means that if you want to run with a one-off set of options you still have to create a 'mode', which means the modes.xml file would become very bloated.
So in (offline) discussions we decided to move away from the lookup mechanism, and instead define the full options directly in the variation tag.
Not sure what you mean by 'the repetition'.  A variation is the set of options to be applied when running that particular test - so each test has its own variations. If there are no variation tags the test is simply run with no -X options at all (which may well be fine for many tests).
The playlists for all tests run under the testkitgen mechanism are actually planned to be put together in the openjdk-tests repository (along with those for the jtreg tests etc.), in which case this pull request will not be required (there'll need to be a similar request in openjdk-tests when the directory structure for the playlist files has been determined).

Yes, there are a few notes regarding this change:

We should just proceed with the plan to create a system folder in openjdk-tests that contains a build.xml and a playlist.xml file (where the build.xml file knows what repo (openjdk-systemtests) to clone and how to build the test material, and playlist.xml file indicates which tests you'd like to run (and with what options and against what Java versions and implementations).

My preference for the contents of the variation tags is to put the actual options rather than the less meaningful modeNumbers (that are a carry-over from how things were done in the past).  So as a review comment  Mode687  should be changed to: -XX:+UseCompressedOops -Xjit -Xgcpolicy:gencon -Xaggressive  in which case, is implementation-specific, so that  needs to also be tagged so that its only run against openjdk+openj9 flavours of SDK (as openjdk+hotspot would fail to parse the options).

I haven't looked at all of the options these modes include, but some are implementation-specific, so we need to tag the tests further so they will not be invoked against an implementation that they will not run against.

I will recommend we hold off on this PR, and move this and the build.xml file into the other repo.


CD-NOD outputs directed cycles.

Hi, Thanks for your great work.
When I am using CD-NOD in my private data, I realize the output PDAG contains a directed cycle.
I use KCI test, other settings (e.g. orientation rules) are set exactly as default values in the illustration example.
Any idea why this phonomene shows? How should I solve this bug?

Hi, thanks for the great question. From my perspective, it might not be a bug--sometimes the cycle happens when the data does not meet the faithfulness assumption. The same phenomenon occurs in PC and FCI, too. Could you please try it on simulated data, i.e., the one you are sure faithfulness does not violate, to see if there are any cycles?

Thanks for your answer. The simulation data is just fine. I guess it may be the assumption violation problem.


YARN and Kafka Gateway roles for gateway node

The current version of aws.reference.conf has the two gateway roles in place, so this PR is no longer needed. Thanks for finding them!


Correct test expectations

Correct test expectations

use valid multipart/form-data content type; include a boundary
correct expectations of FormCollection model binder's operation
restore tests actually skipped for either of the above reasons
add more tests with ModelBindingResult.Model==null and both IsModelSet values

Remove test references to Won't Fix bug #2473

restore #2473 tests; update test expectations
expect null composite results whenever binding fails

Restore test skipped due to "#2646"

that issue does not exist; was likely #2466 or similar fixed bug

Rename model binding tests that still mention ReturnsFalse or ReturnsTrue
Minor src changes

remove unused variable and unnecessary nesting in DefaultControllerActionArgumentBinder
remove dangling mention of [DefaultValue] in ComplexModelDtoModelBinder

nits:

remove empty delegates from some GetOperationBindingContext calls; null fine
do some using cleanup
combine two test methods in KeyValuePairModelBinderTest
name a few more arguments

/cc @harshgMSFT @rynowak

Rebased and updated

also changed PR description to match latest overall changes
note additional fixes e.g. restoration of test skipped due to non-existent "#2646" issue and src nits

:watch:

:shipit:

:shipit:

26795bd