DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_20c5216b-316d-4807-9955-c0ae99af8150/pull/1 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-target_20c5216b-316d-4807-9955-c0ae99af8150.git

Docs Build status updates of commit 67a9dc9:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-RepositoryUnauthorizedWithSourceCommit] Git data access to 'https://github.com/VSC-Service-Account/docs-archive-test-source' (branch: Release_Archive_master_2020-06-01-03-43-53) is not authorized.. It looks like this might be the first time you’ve submitted a pull request to this repo. Before you can run builds in a pull request, you have to enable your GitHub account in Docs by visiting https://opportal-sandbox.azurewebsites.net. After you enable your account, close and then reopen this pull request to start another build.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[Proof of Concept] Run snyk scans as part of rakefile

Example of how we could run snyk as part of our test suite local and as part of CI
If it was configured correctly it would show:

Scanning Dependencies for vulnerabilities via Snyk.io

Testing /Users/waldofouche/dev/saml-service...

Tested 134 dependencies for known issues, found 10 issues, 371 vulnerable paths.

Issues to fix by upgrading:

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ Information Exposure [High Severity][https://snyk.io/vuln/SNYK-RUBY-ACTIONPACK-2400638] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>and 12 other path(s)
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ HTTP Request Smuggling (new) [Critical Severity][https://snyk.io/vuln/SNYK-RUBY-PUMA-2437090] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>
  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ Arbitrary Code Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-ACTIVESTORAGE-2420035] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>  ✗ Information Exposure [High Severity][https://snyk.io/vuln/SNYK-RUBY-ACTIONPACK-2400638] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>and 12 other path(s)
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ Information Exposure [High Severity][https://snyk.io/vuln/SNYK-RUBY-ACTIONPACK-2400638] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>and 12 other path(s)
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ Information Exposure [High Severity][https://snyk.io/vuln/SNYK-RUBY-ACTIONPACK-2400638] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>and 12 other path(s)
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ Information Exposure [High Severity][https://snyk.io/vuln/SNYK-RUBY-ACTIONPACK-2400638] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>and 12 other path(s)
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ Information Exposure [High Severity][https://snyk.io/vuln/SNYK-RUBY-ACTIONPACK-2400638] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>and 12 other path(s)
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

  Upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>to fix
  ✗ XML External Entity (XXE) Injection [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-1726792] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Use After Free [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2413994] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Regular Expression Denial of Service (ReDoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2620374] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Out-of-bounds Write (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630623] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)
  ✗ Denial of Service (DoS) (new) [High Severity][https://snyk.io/vuln/SNYK-RUBY-NOKOGIRI-2630898] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>and 62 other path(s)

Issues with no direct upgrade or patch:
  ✗ Information Exposure [Medium Severity][https://snyk.io/vuln/SNYK-RUBY-ACTIONCABLE-20338] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>  No upgrade or patch available
  ✗ Web Cache Poisoning [Medium Severity][https://snyk.io/vuln/SNYK-RUBY-RACK-1061917] in<EMAIL_ADDRESS>    introduced by<EMAIL_ADDRESS>><EMAIL_ADDRESS>and 39 other path(s)
  No upgrade or patch available

Organization:      waldo.fouche
Package manager:   rubygems
Target file:       Gemfile
Project name:      saml-service
Open source:       no
Project path:      /Users/waldofouche/dev/saml-service
Licenses:          enabled


Debug Mode is not working in laravel on different environment

Laravel Version: 6.2.0
PHP Version: 7.2.4
Apache 2.4

Description:
If I use the below-given lines in the .env file, debugging is working
APP_ENV=local
APP_DEBUG=true

But if I use
APP_ENV=test
APP_DEBUG=true

debugging is not working
If I change the App_Env value from local to any other value debugging is not working, I can't use local as App_Env value at all times, because I use this same application in more than one system for dev, test, and production. some functionalities in the application are differs based on the environment.
I want to debug on both dev and test application systems.

Pretty sure your config is being cached somewhere.
Or a server configuration.
Can't reproduce.

Try clearing your application cache with -
php artisan cache:clear php artisan config:cache
Then give it a try..

Yes I did even though it's not working

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

Thank You very much

I used
php artisan cache:clear
php artisan config:cache
and it solved the issue.

this issue occurred to me in laravel 10 ...any solutiuon yet?


Graphics issue

I used bloxstrap and when i uninstalled it,it bugged my graphics and collors

it bugged my graphics and collors

Like, in Roblox?

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.


Missing thumbnail images for (older) showcase contributions

99 out of 1398 (~14%) showcase contributions do not have an accompanying image. Just dumping this here in case someone wants to take screenshots and help close this gap.
It's not breaking the site, but we are displaying a placeholder that doesn't give information about the featured work so it would be a nice low priority improvement. Low-hanging fruit for first-time GitHub contributions maybe?

Reminder on the image specs (from the contribution guide):

While any aspect ratio is fine (the site will resize and crop as necessary), the images will be displayed at 16:9 aspect ratio. We suggest you upload a "landscape" image. The file format should be JPG or PNG, with a maximum width of 800px and file size of 500 kb. Name your thumbnail image with the same filename as your showcase submission (contribution1.png, contribution2.jpg, etc.).

And the list:

[ ] content/videos/challenges/1-starfield/showcase/contribution2.json
[ ] content/videos/challenges/1-starfield/showcase/contribution5.json
[ ] content/videos/challenges/10-dfs-maze-generator/showcase/contribution7.json
[ ] content/videos/challenges/100-neuroevolution-flappy-bird/showcase/contribution11.json
[ ] content/videos/challenges/101-may-the-4th-scrolling-text/showcase/contribution1.json
[ ] content/videos/challenges/103-fire-effect/showcase/contribution4.json
[ ] content/videos/challenges/108-barnsley-fern/showcase/contribution6.json
[ ] content/videos/challenges/111-animated-sprites/showcase/contribution1.json
[ ] content/videos/challenges/113-4d-hypercube-aka-tesseract/showcase/contribution6.json
[ ] content/videos/challenges/114-bubble-sort-visualization/showcase/contribution10.json
[ ] content/videos/challenges/114-bubble-sort-visualization/showcase/contribution15.json
[ ] content/videos/challenges/115-snake-game-redux/showcase/contribution8.json
[ ] content/videos/challenges/116-lissajous-curve-table/showcase/contribution11.json
[ ] content/videos/challenges/117-seven-segment-display/showcase/contribution7.json
[ ] content/videos/challenges/121-logo-interpreter/showcase/contribution3.json
[ ] content/videos/challenges/122-quick-draw/showcase/contribution1.json
[ ] content/videos/challenges/124-flocking-simulation/showcase/contribution12.json
[ ] content/videos/challenges/13-reaction-diffusion/showcase/contribution4.json
[ ] content/videos/challenges/13-reaction-diffusion/showcase/contribution6.json
[ ] content/videos/challenges/130-drawing-with-fourier-transform-and-epicycles/showcase/contribution7.json
[ ] content/videos/challenges/130-drawing-with-fourier-transform-and-epicycles/showcase/contribution8.json
[ ] content/videos/challenges/132-fluid-simulation/showcase/contribution3.json
[ ] content/videos/challenges/134-heart-curve/showcase/contribution7.json
[ ] content/videos/challenges/134-heart-curve/showcase/contribution9.json
[ ] content/videos/challenges/138-angry-birds-with-matterjs/showcase/contribution3.json
[ ] content/videos/challenges/14-fractal-trees-recursive/showcase/contribution4.json
[ ] content/videos/challenges/142-rubiks-cube/showcase/contribution5.json
[ ] content/videos/challenges/145-ray-casting-2d/showcase/contribution14.json
[ ] content/videos/challenges/145-ray-casting-2d/showcase/contribution20.json
[ ] content/videos/challenges/145-ray-casting-2d/showcase/contribution21.json
[ ] content/videos/challenges/145-ray-casting-2d/showcase/contribution23.json
[ ] content/videos/challenges/145-ray-casting-2d/showcase/contribution5.json
[ ] content/videos/challenges/146-rendering-ray-casting/showcase/contribution4.json
[ ] content/videos/challenges/147-chrome-dinosaur-game/showcase/contribution8.json
[ ] content/videos/challenges/148-gift-wrapping/showcase/contribution9.json
[ ] content/videos/challenges/149-tic-tac-toe/showcase/contribution30.json
[ ] content/videos/challenges/155-kaleidoscope-snowflake/showcase/contribution8.json
[ ] content/videos/challenges/158-shape-classifier/showcase/contribution1.json
[ ] content/videos/challenges/159-simple-pendulum/showcase/contribution3.json
[ ] content/videos/challenges/2-menger-sponge/showcase/contribution1.json
[ ] content/videos/challenges/2-menger-sponge/showcase/contribution5.json
[ ] content/videos/challenges/21-mandelbrot-set-with-p5js/showcase/contribution7.json
[ ] content/videos/challenges/21-mandelbrot-set-with-p5js/showcase/contribution9.json
[ ] content/videos/challenges/22-julia-set/showcase/contribution3.json
[ ] content/videos/challenges/29-smart-rockets-in-p5js/showcase/contribution1.json
[ ] content/videos/challenges/3-snake-game/showcase/contribution11.json
[ ] content/videos/challenges/3-snake-game/showcase/contribution18.json
[ ] content/videos/challenges/3-snake-game/showcase/contribution23.json
[ ] content/videos/challenges/3-snake-game/showcase/contribution5.json
[ ] content/videos/challenges/30-phyllotaxis/showcase/contribution9.json
[ ] content/videos/challenges/35-traveling-salesperson/showcase/contribution10.json
[ ] content/videos/challenges/35-traveling-salesperson/showcase/contribution8.json
[ ] content/videos/challenges/4-purple-rain/showcase/contribution5.json
[ ] content/videos/challenges/42-markov-chain-name-generator/showcase/contribution1.json
[ ] content/videos/challenges/46-asteroids/showcase/contribution2.json
[ ] content/videos/challenges/46-asteroids/showcase/contribution3.json
[ ] content/videos/challenges/46-asteroids/showcase/contribution4.json
[ ] content/videos/challenges/46-asteroids/showcase/contribution7.json
[ ] content/videos/challenges/58-3d-earthquake-data-visualization/showcase/contribution1.json
[ ] content/videos/challenges/58-3d-earthquake-data-visualization/showcase/contribution3.json
[ ] content/videos/challenges/60-butterfly-generator/showcase/contribution1.json
[ ] content/videos/challenges/64-kinematics/showcase/contribution3.json
[ ] content/videos/challenges/66-javascript-countdown-timer/showcase/contribution1.json
[ ] content/videos/challenges/67-pong/showcase/contribution9.json
[ ] content/videos/challenges/68-breadth-first-search/showcase/contribution1.json
[ ] content/videos/challenges/68-breadth-first-search/showcase/contribution2.json
[ ] content/videos/challenges/69-evolutionary-steering-behaviors/showcase/contribution6.json
[ ] content/videos/challenges/69-evolutionary-steering-behaviors/showcase/contribution9.json
[ ] content/videos/challenges/71-minesweeper/showcase/contribution1.json
[ ] content/videos/challenges/78-simple-particle-system/showcase/contribution12.json
[ ] content/videos/challenges/78-simple-particle-system/showcase/contribution7.json
[ ] content/videos/challenges/83-p5-sketch-chrome-extension/showcase/contribution1.json
[ ] content/videos/challenges/85-the-game-of-life/showcase/contribution5.json
[ ] content/videos/challenges/86-cube-wave-by-bees-and-bombs/showcase/contribution5.json
[ ] content/videos/challenges/90-dithering/showcase/contribution5.json
[ ] content/videos/challenges/91-snakes-and-ladders/showcase/contribution2.json
[ ] content/videos/challenges/92-xor-problem/showcase/contribution3.json
[ ] content/videos/challenges/93-double-pendulum/showcase/contribution7.json
[ ] content/videos/challenges/98-quadtree/showcase/contribution1.json
[ ] content/videos/challenges/98-quadtree/showcase/contribution5.json
[ ] content/videos/challenges/c2-collatz-conjecture/showcase/contribution8.json
[x] content/videos/challenges/c3-hilbert-curve/showcase/contribution16.json
[x] content/videos/challenges/c3-hilbert-curve/showcase/contribution5.json
[ ] content/videos/challenges/c4-worley-noise/showcase/contribution13.json
[x] content/videos/challenges/c5-marching-squares/showcase/contribution1.json
[ ] content/videos/challenges/c5-marching-squares/showcase/contribution13.json
[x] content/videos/challenges/c5-marching-squares/showcase/contribution3.json
[ ] content/videos/data/1-client-side/2-tabular-data/showcase/contribution1.json
[ ] content/videos/data/1-client-side/2-tabular-data/showcase/contribution2.json
[ ] content/videos/data/1-client-side/3-graphing/showcase/contribution1.json
[ ] content/videos/ml5/5-knn-classification/1-build-the-image-classifier/showcase/contribution1.json
[ ] content/videos/ml5/6-train-your-own-neural-network/1-train-the-model/showcase/contribution1.json
[ ] content/videos/ml5/6-train-your-own-neural-network/1-train-the-model/showcase/contribution4.json
[ ] content/videos/ml5/7-posenet/1-finding-keypoints/showcase/contribution1.json
[ ] content/videos/ml5/7-posenet/1-finding-keypoints/showcase/contribution2.json
[ ] content/videos/ml5/7-posenet/1-finding-keypoints/showcase/contribution4.json
[ ] content/videos/ml5/7-posenet/1-finding-keypoints/showcase/contribution5.json
[ ] content/videos/ml5/8-convolutional-neural-network/1-pixels-as-input/showcase/contribution1.json
[ ] content/videos/noc/5-autonomous-agents/2-seeking-a-target/showcase/contribution1.json

Wow, thanks for making this list! I'll also note that the passenger showcase image pulls from the video's index.jpg if it has one. For example, if you look at the showcase projects missing a thumbnail for the Marching Squares challenge you'll see the example image applied.

We never made placeholder thumbs for videos associated with tracks (not challenges) but that might be worth considering as well, possibly even building it in as a requirement for tests to pass (though we'd have to fill in all the missing ones first.)

Some of the showcases were ports to a different language which made it more time-consuming  to grab the image (a consideration when you are adding a ton of them).

I'm doing a pass over all the issues today, is this one still relevant should we work on updating thumbs for more old showcase project or are we covered enough now?

There are still a lot of showcases that were ported from old site that do not have images.  I think the ones that were relatively easy to grab are done and the ones that are left are more time-consuming /  harder (different languages or platforms) to obtain.   It is a judgement call about whether to close.


global modifier in regex pattern

Using numbered wildcards consecutively like so: '%1$s enabled %2$s %3$s' occasionally causes a match to miss, this results in the actual wildcard being displayed in the UI. After logging just about everything in the library, I decided to omit the 'global' modifier in the regex pattern on line 71 and viola, problem solved.
I can't find too much information on when it's ok to NOT use the global modifier, but this guy (http://stackoverflow.com/a/1222089) thinks it's ok.
This is my first time reporting an issue on github so I apologize in advance if it's not by the books.

@johnnysainz I'm going to close this - feel free to re-open it if you are still having problems.


[Feature request] Post to multiple profiles with a single website

Hello,
As discussed in the chat, it would be awesome to have the possibility to post to different profiles.
Example use case: on an internationalised website, it could be great to post to have multiple accounts, one for each language, e.g<EMAIL_ADDRESS>for entries in French, and<EMAIL_ADDRESS>for entries in English.
Potential conditions:
a) Possibility to specify which profile to post to either via the website URL (if the page routes are prefixed with /en/ or /fr/ for example),
or, even more flexible
b) add a Microformat-like tag to specify the name of the profile to post to.
Thank you for this very interesting project 👍🏻

Thanks for filing! Happy to track this feature request. This would be doable, but nontrivial. For example, we'd need a way for users to define all of their accounts, specify which account they want to federate a given post on their site to, etc.

Thanks for filing! Happy to track this feature request. This would be doable, but nontrivial. For example, we'd need a way for users to define all of their accounts, specify which account they want to federate a given post on their site to, etc.

Maybe by declaring several h-cards, and have a unique ID (I.e., the account name) declared in a tag inside the h-card and, then, for each entry, refer to that unique ID via a tag?

Something like that!


Update to broccoli-funnel 1.0.2 to avoid minimatch vulnerability

See here:
https://nodesecurity.io/advisories/118

Thank you for opening this! Any chance you'd have time to throw this in a PR?

et voilà

0ef17266ef490d69bbdac2a80252d1a05917d1cb closes
Thanks ! :heart:


test: add explicit 10s timeouts for most of the tests

Previously the tests could block forever, particularly infuriating as
this locks the appveyor CI slot for 1hr. All the tests should execute
within 10s, except the max connections one which has been given a 4
minute maximum.
Signed-off-by: David Scott<EMAIL_ADDRESS>

10s was too short for the CI machines -- let's try 60s.

OK, both CIs seem happy with this now.


how to run simpleWebRTC?

I have download and run "node server.js". then visit "http://localhost:8001" via chrome.
type number, then click "create id", but Nothing ever happens。
so have a guide for how to install and run simpleWebRTC?
thanks.

are you running the latest version? This sounds like you can't contact the signaling sandbox server


Add support for security opts on containers

- What I did
Once, a long long time ago, we had aspirations of including a more structured way to handle security permissions in Swarmkit.
Unfortunately, this never panned out. Rather than continuing to stagnate on a might-be, this change simply add in support for the --security-opt flag and its API equivalents directly. Perfect shouldn't be the enemy of good enough.
- How I did it
Adds a security_opt field to the protobuf definition of ContainerSpec. There aren't actually any other changes needed in Swarmkit. This field will get passed into Swarmkit, then passed from Swarmkit to the executor (which lives in the engine). Swarmkit never needs to care about it.
- How to test it
Not needed.

Codecov Report

Merging #3149 (aa1585b) into master (b98a45d) will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3149      +/-   ##
==========================================
- Coverage   61.75%   61.71%   -0.04%
==========================================
  Files         155      155
  Lines       31145    31145
==========================================
- Hits        19234    19222      -12
- Misses      10361    10384      +23
+ Partials     1550     1539      -11

looks related to

https://github.com/moby/moby/issues/41371

@dperny are there changes needed on the moby side to punch this through?

also related: implementation of a security-spec (which was only partial, so selinux, but not apparmor); https://github.com/moby/swarmkit/pull/2075


Unable to resolve security vulnerability in mat-table-exporter using npm

Cannot resolve vulnerability detailed here: https://github.com/advisories/GHSA-4r6h-8v6p-xvw6
mat-table-exporter 15.0.0 (newest version?) depending on xlsx ^0.18.5 and patched version (0.19.3) is not available through npm as detailed here: https://docs.sheetjs.com/docs/getting-started/installation/nodejs/

Looks like the project is not maintained on GitHub anymore (see: https://github.com/SheetJS/sheetjs/issues/2822#issuecomment-1532922059) not sure why the npm page wasn't updated.
In the meantime, this project could update its package.json with the new xlsx version/source, that is https://cdn.sheetjs.com/xlsx-0.19.3/xlsx-0.19.3.tgz

It would be nice if the author could use the tarball instead of the npm package in the package.json!

It would be nice if the author could use the tarball instead of the npm package in the package.json!

or switch to another package that is maintained in npm repo

Any solution to this, guys?

Same story for me. Adding
"xlsx": https://cdn.sheetjs.com/xlsx-0.19.3/xlsx-0.19.3.tgz in resolutions does not help. After build it throws the following error "Error: Module not found: Error: Can't resolve 'xlsx/dist/xlsx.mini.min' in 'node_modules/cdk-table-exporter/fesm2020'"
Any ideas how to resolve ? I even try to move xlsx to my project and modify package json there but no success

I don't know if the owner of the repo is doing anything about this, but I wrote a little Node.js script to remedy the situation a while back:
const fs = require('fs/promises');
async function run() {
  let packageJson = await fs.readFile('./node_modules/xlsx/package.json', { encoding: 'utf-8' });
  const package = JSON.parse(packageJson);
  if (('./dist/xlsx.mini.min' in package.exports)) {
    console.log('xlsx already exports xlsx.mini.min');
    return;
  }
  package.exports = {
    ...package.exports,
    './dist/xlsx.mini.min': {
      "import": "./dist/xlsx.mini.min.js",
      "types": "./dist/zahl.d.ts"
    }
  };
  packageJson = JSON.stringify(package);
  await fs.writeFile('./node_modules/xlsx/package.json', packageJson, 'utf-8');
  console.log('xlsx now exports xlsx.mini.min');
}
run();

Save that as Add-xlsx-mini-min-export.cjs in your project folder and add the following to your scripts node in package.json:
    "postinstall": "node Add-xlsx-mini-min-export.cjs",

That, with the ..."overrides": { "xlsx": "https://cdn.sheetjs.com/xlsx-0.20.2/xlsx-0.20.2.tgz",... line works for me... (and I've upgraded since the last message here, obv).


Feature request - [New German Data Set Thorsten – 2022.10 Available for Re-Training

Are there any plans to re-train and provide new models based on the new German data set Thorsten 2022.10
which can be found here https://www.thorsten-voice.de/en/datasets-2/)
Thanks.

We are currently working on a multi-speaker TTS model that includes Thorsten voice data. Maybe we will also update our Thorsten voice single speaker model, but there is a good one already available
https://www.thorsten-voice.de/einfach-loslegen/
I recommend Thorsten-VITS.

Thanks for the issue @eqikkwkp25-cyber and your response @renepeinl 😊.
If i can support your work, please let me know.


Can't Configure Settings - Dialog Box empty/bugged

Describe the bug
Dialog to enter export settings doesn't work. Allow path, etc. to be entered in plugin settings area?
Operating System
Windows 10
To Reproduce

open command pallete.
Choose set export HTML settings

Screenshots

Are there any odd files in your vault? One person ad this problem and had a node_modules directory in their vault: #355

Can you also take a screenshot of the console after this happens? Thanks

Can you please test out the new beta 1.8.1-0b and let me know if this fixes the issue? Please also let me know if you find any new issues. Thanks!

This root cause is:
titleFromFrontmatter may be a number type. (ex. 20240203.md)

I fixed in https://github.com/KosmosisDire/obsidian-webpage-export/pull/401


Model Freezing

@ElliottKasoar Originally commented in #103:

Model freezing
No changes are currently included, and less directly applicable to the main FTorch library, although there are still interactions e.g. freezing the model can allow InferenceMode to be enabled when loading the model.
Freezing is currently the "default" when tracing in pt2ts.py, but not for scripting, despite potentially improving performance.
Freezing appears to (sometimes) introduce numerical errors when saving the reloading (differences ~10^-6), and can seem to lead to issues loading with Forpy too.

Questions for @ElliottKasoar:

Is there any reason not to freeze the scripted models in the same way we do the traced ones?
Do you feel we should make this an option for the user to set?
Do you feel it is better to have frozen (for performance, but with a warning to check accuracy in Fortran) or unfrozen (to ensure reproducibility) as a default?

Copying @ElliottKasoar's original comment from #81

Model freezing

See: torch.jit.freeze
Applies system-independent optimization, as opposed to the system-dependent optimize_for_inference (which is currently broken, unfortunately)
Can give up to 50% speedup
From our benchmarking (see FTorch with/without gradients and/or frozen models sections), freezing the model can make more modest, but not insignificant, improvements (in most cases)

Tests were carried out by replacing scripted_model.save(filename) with  frozen_model = torch.jit.freeze(scripted_model), and then frozen_model.save(filename) in pt2ts.py

While not a problem for the use of FTorch, it's also worth noting that running the same TorchScript via Forpy (on CPU or GPU) seemed to give a similar errors to what optimize_for_inference can gives e.g. AttributeError: 'RecursiveScriptModule' object has no attribute 'training'
Freezing the model appears to lead to numerical errors (~10^-6) for the ResNet benchmark, raising a RuntimeError when saving, but this doesn't seem to be the case for the cgdrag benchmark, and it is unclear why
The guidance part of the title is perhaps most relevant here, as this is less about the main FTorch library, and more about how we enable users to use tools like pt2ts.py as part of a workflow involving FTorch

This is somewhat dependent on the typical familiarity of potential FTorch users with the processes involved in saving to TorchScript
Note: trace_to_torchscript currently uses model freezing. It would be preferable to have a shared setting and/or behaviour, unless there is a clear reason to use freezing in only one of the functions
Any guidelines on trace_to_torchscript compared with script_to_torchscript may also be useful, as currently there is no clear motivation not to use the "default" script_to_torchscript

Is there any reason not to freeze the scripted models in the same way we do the traced ones?
Do you feel we should make this an option for the user to set?
Do you feel it is better to have frozen (for performance, but with a warning to check accuracy in Fortran) or unfrozen (to ensure reproducibility) as a default?

I think generally we need to understand its behaviour a little better before answering most of this definitively, but my initial thoughts:

Probably not, if it works
Yes, I think so
Probably unfrozen

My feeling is there are probably enough caveats/complications that unfrozen would be best as the default, so more or less anything a user throws at the library can work.
Ideally we'd probably then strongly encourage users looking to optimise inference to freeze their models, either via pt2ts, which is what I mostly used, or our interface (C++ docs are limited, and I'm not sure I tested that at all) - having the option built into FTorch seems like a useful thing to add.
There definitely seems to be some strange behaviour e.g. trying to change the model device (see discussion/linked issue here and note at the end of this), the errors I had using the model with forpy, the numerical differences etc.
Some of those issues may be related, and none so far seem to be too challenging:

There is a work-around for moving the model, and it may not be a problem for FTorch anyway
If it works for FTorch, we don't necessarily need to worry about forpy
Floating point arithmetic etc. shouldn't be expected to be exact

So arguably most of what we need do is confirm and document these potential issues.
Once we have a handle on the limitations, I think generally we should be able to say that there's no reason not to freeze the model for inference.


[5.6] Fix *scan methods on PhpRedis connections

This adds the adapter methods to properly utilize PhpRedis commands for scan, sscan, hscan, and zscan.  fixes #24222
I do know there is 2 failing tests but those are a by product of another bug which most likely needs to be addressed and is opened in issue:  #24257

Your doc blocks are incorrect.

I can't tell what is going on (if anything) with the test class changes.

Please try to organize where you are putting your new methods into logical places within the existing class.

Tests fail on my machine:

Feel free to re-submit when this is cleaned up.


1.0.4 patch train updates

Will need to coordinate with @dougbu for https://github.com/aspnet/Mvc/pull/5782

@JunTaoLuo I'm just waiting for @pranavkm on #5782.
But, why are we calling this 1.0.4? Thought MVC was on the high end with the latest patch branch being rel/1.0.3.

It's the 1.0.4 patch train but the MVC packages will be 1.0.3.

Will need to coordinate with @dougbu for #5782

All done. @JunTaoLuo that PR is now in the rel/1.0.3 branch.

@JunTaoLuo you need to rebase this branch. No need to re-add the SDK version to global.json for example.


feat: Support pypy and pkg change metadata

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (9a28820) 95.65% compared to head (4e17093) 95.65%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #28   +/-   ##
=======================================
  Coverage   95.65%   95.65%
=======================================
  Files           7        7
  Lines         184      184
=======================================
  Hits          176      176
  Misses          8        8

Flag
Coverage Δ

unittests
95.65% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Increase timeouts

This increases our HTTP response timeout to 1 minute, and decreases retry frequency for API calls from once every 1 second to once every 5 seconds.
This means the agent will now wait 10 seconds for a http connection, 60 seconds for a response, and then it'll wait 5 seconds before retrying. For network situations, or downtime, this means things will attempting to retry every 5 seconds instead of every second.

@keithpitt given you chose the initial values, I'll need your eyes on this. I don't see many user-facing problems with the increases?

Once this is merged I'll also backport to stable

:+1:


Power platform solution checker fails with "Exceeded the max wait"

Since v0.0.77 (and still in 0.0.85) we often (not always) are getting the following error in the output logs
##[error]Exceeded the max wait. Try running again with an increased SecondsBetweenChecks and MaxStatusChecks.
There is no option for the task to extend the wait time, except the default timeout built into any devops task (which has no affect). The timeout seems to be locked at 5min, which is probably fine since when the check works on the same solution it takes about 30seconds. The logs saved in the output folder do not indicate any other error.
I've attached the an image showing output of unsuccessful check and successful next to each other. Both checking the same solution

I'm not sure extending the timeout is going to resolve all the issues though. The example I show above, in this case if it works it takes 30seconds, and if it doesn't it's just hanging there. As of today the timeout has been extended for the task, but we just hit the built in timeout of any task in devops.

The initial issue here was with the Checker task, which indeed had an issue with a fixed 5min task timeout.
If you see timeout issues in other tasks, please do open separate issues


Fix validation for ddoc and _local id

Because binary match treats end of binary as <<>> we are validating "_design/" and "_local/" as proper ids.
COUCHDB-3114

+1

hm, there must be a better way. we now have two bits of special logic in the same function for the same reason.

try
 <<"_design/", Rest/binary>> when byte_size(Rest) > 0 -> ok

That way we only say the _design and _local rule once each. anything else beginning _ will hit the general prohibition clause.

@rnewson I did it at first, but then decided to go with less confusing error message for the users sake. If you think it's not a problem here then sure, I'll use guards.

hrm, fair enough. I can't see a tidier way to say it once but still give good error messages.
+1.


highlightModifiedTabs and pinned tabs issue

Env:
Version: 1.51.1 (system setup)
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:34:32.027Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Steps to Reproduce:
As you can see, the blue stripe overlaps the pinned tabs

Does this issue occur when all extensions are disabled?:
All disabled except GitGraph, but I don't think this addon is involved in this issue

This is due to our various z-index being used in tabs, I am a bit afraid to change this so late in endgame, will revisit next month.

/verified


Broken Body/ Prefab

So I had some issues with the models in unity. I dont know how to solve this my friend told me that I have exported the file wrong. No Idea tho how to solve it. https://imgur.com/mBdRsLc Thx in advance! :)

Please upload game file so I can reproduce this issue

https://api.vrchat.cloud/api/1/file/file_6d310a72-6a31-4a9b-a57d-309e0634b457/8/file so this is the vrca file i tried to export. I had no issue while exporting but after i imported it into unity, the model was glitched

Wow. This one is tough. I've found only one tool that can properly export such kind of meshes. I will try to fix this issue but can not guarantee it.

The avatar isn't glitched per say. It's meant to be that way to prevent unwanted "theft". It can also be fixed in blender and exported back out into unity.

Are you sure that it was done intentionally? I'm not going to do anything about this issue in that case but I just want to be sure about it. Few weeks ago I saw exactly same weird mesh among one of asset studio issues. And uabe's dau plugin is able to export such mesh properly. Does it some common anti thief tool or what?

@mafaca Yea, It was intentionally. A lot of people have been forced to do it lately to avoid unwanted distribution of their work. A lot of assets used for most of these "Avatars" are freely distributed and/or can be downloaded in many places , however with people that do commissions or make it from scratch, they end up doing this to the mesh in order to somewhat protect it. The game doesn't provide anti-theft, so they ended up doing their own ,lol.
I did end up talking to the creator of that mesh which Kagan posted and although she doesn't mind it because she's helping give ideas to others(her words). It does sadden her when someone tries to pass off her work as their own.

ohh, I see

Ok. I close this issue in this case, because the ripper only supports official assets.

Since it looked very suspicious I decided to checked this mesh myself just to be sure.
I don't know why @Xiuetsu decided that it is somehow protected and was so confident about that. It isn't protected. I just missed a flag that determine index format and, since this model is huge, default 16bit format doesn't suit it well.
Fixed in 5e74211c6710a5ce750b35c25f4bf16a03b4dd15

@mafaca I believe you might have misunderstood what I said. I said that some people have had to implement their own sort of protection since there is no "real" way of doing it via where they are uploaded to. However their way of protecting it is seeing what programs like yours, asset studio, and uabe can't extract. Gotta be creative these days.

@Xiuetsu, oh, ok i got it


[FEAT] Add Title to the page

Is your feature request related to a problem? Please describe.
The navbar looks dull without the title of the page.
Describe the solution you'd like
-Add a draw-it-out title to the page we can make attractive and simple.
Add the logo beside the title.
please assign @pa

@jayanththalla Kindly add a screenshot of what the app will look after adding your changes.

@jayanththalla there's already a Title, could you elaborate your motive?

beside of the draw it out

@jayanththalla That will not enhance the app, thanks for raising the issue, Kindly explore other issues.


TypeScript error 'Property 'hiddenLabel' missing' in KeyboardDatePicker

Environment

Tech
Version

@material-ui/pickers
^3.2.2

material-ui
^4.2.1

React
^16.8.6

Browser
Version 76.0.3809.100

Peer library
date-fns ^2.0.0-beta.4

Steps to reproduce

Including hiddenLabel prop

      margin="normal"
      id="mui-pickers-date"
      label={label}
      value={selectedDate}
      onChange={onDateChange}
      KeyboardButtonProps={{
        'aria-label': 'change date'
      }}
      hiddenLabel="change date"
    />

leads to React console warning:
Warning: React does not recognize the `hiddenLabel` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `hiddenlabel` instead. If you accidentally passed it from a parent component, remove it from the DOM element.

Removing hiddenLabel prop leads to TypeScript compilation error:

TypeScript error in /Users/sophie.fiset/magnet-fe/magnet-dashboard/src/components/shared/DatePicker.tsx(14,6):
Property 'hiddenLabel' is missing in type '{ margin: "normal"; id: string; label: string | undefined; value: Date | null; onChange: (date: Date | null) => void; KeyboardButtonProps: { 'aria-label': string; }; }' but required in type 'Pick<KeyboardDateInputProps, "label" | "children" | "ref" | "select" | "style" | "title" | "mask" | "defaultChecked" | "defaultValue" | "suppressContentEditableWarning" | "suppressHydrationWarning" | ... 273 more ... | "rifmFormatter">'.  TS2741

Expected behavior
If passing the prop hiddenLabel that is expected by TS, there should be no React warning. If omitting the prop, app should still compile.
Actual behavior
I can't include or exclude :( Seems like a "me" problem with my version of Typescript perhaps?

I am not seeing hiddenLabel in allowed text-field props

Having the same issue. Looks like hiddenLabel was introduced in Material UI 4.3.0 (if I upgrade Material UI, the warning goes away). hiddenLabel is in the Props of FormControl: https://material-ui.com/api/form-control/#props

Upgrading @material-ui/core fixed this for me too

So closing this issue

Awesome - thanks a lot @dmtrKovalenko @alex-scown-checkit @AdamBeddoe!

Upgrading @material-ui/core fixed this for me too

it is necessary to update material-ui / pickers


WebView - no information about WebNavigationEvent and WebNavigationResult

In the article about WebView there is no information about WebNavigationEvent and WebNavigationResult. Especially WebNavigationResult should be described in details because it is not obvious how these navigation results are triggered, i.e. what exactly causes "Failure" navigation result.

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

ID: ef31dc71-3610-6c18-2bda-d0bb70804c92
Version Independent ID: 02f7dc7b-541b-4b82-b33c-4e974fb94d8c
Content: Xamarin.Forms WebView - Xamarin
Content Source: docs/xamarin-forms/user-interface/webview.md
Product: xamarin
GitHub Login: @davidbritch
Microsoft Alias: dabritch

Hi @Mikilll94
I've updated the doc with some information about the events, which is in a PR that will go out later.
With regards to what triggers navigation results, this is internal implementation detail of the native controls (e.g. WkWebView on iOS). For example, if a WkWebView fails to load a Url, the Xamarin.Forms WebViewRenderer on iOS sets a Failure result. The reason for the failure is internal implementation details of the WkWebView.


Make an official website.

From @GoogleCodeExporter on May 31, 2015 11:31
This project looks promising. An official website for this project would
greatly improve it's visibility.

Original issue reported on code.google.com by TruSktr on 9 Sep 2012 at 8:58
Copied from original issue: damonkohler/android-scripting#657

This issue was moved to damonkohler/sl4a#62


[Snyk] Security upgrade yeoman-environment from 3.6.0 to 3.7.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

packages/jmix-front-generator/package.json
packages/jmix-front-generator/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

696/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Regular Expression Denial of Service (ReDoS) SNYK-JS-ANSIREGEX-1583908
No
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: yeoman-environment
    The new version differs by 19 commits.

370fd14 3.7.0
8e83811 Bump mocha from 8.3.0 to 9.1.3 (#362)
9609b00 Bump pacote from 11.3.5 to 12.0.2 (#355)
e7a21c2 Bump yeoman-test from 5.1.0 to 6.2.0 (#357)
c19fbf3 Add concurrency (#359)
c1486de Bump sinon from 9.2.4 to 12.0.1 (#353)
9331475 Bump are-we-there-yet from 1.1.5 to 2.0.0 (#352)
2184ca5 Bump fs-extra from 9.1.0 to 10.0.0 (#350)
f00b8c3 Update only major versions. (#348)
fa9f355 Fix dependabot. (#337)
7ca6a46 Bump arborist. (#335)
8aead6b Enable dependabot monthly for major updates. (#336)
8833c47 Implement conflicterStatus. (#334)
cb46b68 Format using new standards. (#333)
7017557 Fix Node 16 transform behavior change. (#330)
06c2c9b Force write .yo-resolve files.
810b0bd Add ignore to conflicter action.
a6071e1 ESM generator fix.
cc90fd9 fix: error message when generator not found

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Write all text at once

Did you test the new function on any of the previous datasets and compare the outputs?

Yes just test it on hundreds of notes. The outputs are identical before and after the change.


Debugging with Chrome as described in Documentation does not work

Is this a bug report?
Yes.
Can you also reproduce the problem with npm 4.x?
Yes.
Which terms did you search for in User Guide?
Debugging in the Editor
Environment
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>windows 10
<EMAIL_ADDRESS><EMAIL_ADDRESS>Steps to Reproduce

create-react-app chromeDebuggingTest
cd chromeDebuggingTest
npm i
npm run start
open Visual Studio Code
add a .vscode folder with a launch.json according to the a
set a breakpoint in Visual Studio Code (red dot on the left of a line of source code)
select the debugging Panel in Visual Studio Code, press the play/start button labeled "Chrome"
see the breakpoint not being hit when the app is executed in Chrome

Expected Behavior
Breakpoint being hit in Chrome
Actual Behavior

breakpoint is not hit
breakpoint color turns grey in Visual Studio Code
it has something to do with sourcemaps not matching

@codepunkt I might be looking for something like this:
https://developers.google.com/web/tools/chrome-devtools/javascript/
You must use the sources tab from devtools, once in there, you can find for files (cmd + p) to debug and set breakpoints.

@marcelorl Thanks for the advice! There's quite a few ways to debug my application - the one outlined in your answer is one of them. My problem is not debugging in general, but explicitly debugging in VSCode using the VSCode Chrome Debugger extension as described in the User Guide.

@codepunkt I just followed your instructions and set a breakpoint in App.js on line 9 and my breakpoint is hit using Chrome 62. You need to refresh the page in Chrome to get have your breakpoint hit in your React render code, as it's being executed before VS Code is able to attach to Chrome. Similar to how you sometimes need to refresh after Chrome DevTools has opened.

I know this can be confusing, but it's a simple timing problem, as our debugger attaches after Chrome has executed the code. We are working on enabling "break-on-load" breakpoints in https://github.com/Microsoft/vscode-chrome-debug/issues/445, which will make this timing issue transparent.
(cc @gaearon)

I know this can be confusing, but it's a simple timing problem, as our debugger attaches after Chrome has executed the code. We are working on enabling "break-on-load" breakpoints in Microsoft/vscode-chrome-debug#445, which will make this timing issue transparent.

Can we also add a sentence to our docs about this?

I've added a section about this in our README, and I don't want to replicate general FAQs into framework specific docs, but we could update the react docs to have a pointer?

Opened here https://github.com/facebookincubator/create-react-app/pull/3399


HSEARCH-1033 Verify compatibility with Jackson 1.9.2

No version conflicts, no code changes needed and distribution directory contains them as expected.
Shall I push it directly?

I have a few questions:

Are these specific versions used for test only or are they dragged along by users depending on Hibernate Search?
What can we do to track the version change on the AS side?
Using this version means we use and "impose" an older version to our users?

1# They are the suggested version to use at runtime, and included in the distribution assemblies. Of course they are used for testing as well.
2# We could introduce a dependency to  AS7 BOM if they make one (being discussed).. I'd avoid that anyway as hopefully the AS will fix this dependency leak so we will be allowed to use independent versions. In other words,I hope this is a temporary need we have.
3# No it's newer than what we would otherwise bundle.

Applied.


Installed turicreate on Mac with Python 3.7 unable to use it in Jupyter NB

I downloaded the turicreate package and I can also see it in conda list. However, when I try and import turicreate in my jupyter NB it throws the following error.

ModuleNotFoundError                       Traceback (most recent call last)
 in
----> 1 import turicreate
ModuleNotFoundError: No module named 'turicreate'

You have most likely installed turicreate in a different environment than the environment you are using to run Jupyter.
The easiest way to make sure things get installed in the right environment is to install them using Jupyter Notebook. You can run system commands from inside of Jupyter Notebook by starting them with a !. So in a Jupyter code cell, run this command:
! pip install turicreate.
Let us know if that works.

I tried that, it says "requirement already satisfies". It even shows up in "pip list" but still I am not able to import it in jupyter notebook or even in terminal. Can it be a cython problem?
This is the import error:

ImportError                               Traceback (most recent call last)
 in
----> 1 import turicreate
~/.local/lib/python3.7/site-packages/turicreate/init.py in
17 from turicreate.version_info import version
18
---> 19 from turicreate.data_structures.sgraph import Vertex, Edge
20 from turicreate.data_structures.sgraph import SGraph
21 from turicreate.data_structures.sarray import SArray
~/.local/lib/python3.7/site-packages/turicreate/data_structures/init.py in
16
17 from . import image
---> 18 from . import sframe
19 from . import sarray
20 from . import sgraph
~/.local/lib/python3.7/site-packages/turicreate/data_structures/sframe.py in
14 from future import division as _
15 from future import absolute_import as _
---> 16 from .._connect import main as glconnect
17 from .._cython.cy_flexible_type import infer_type_of_list
18 from .._cython.context import debug_trace as cython_context
~/.local/lib/python3.7/site-packages/turicreate/_connect/main.py in
11 from future import absolute_import as _
12
---> 13 from .._cython.cy_unity import UnityGlobalProxy
14 from .._cython.cy_server import EmbeddedServer
15
ImportError: libnsl.so.1: cannot open shared object file: No such file or directory

Ok, this does look like a bug.
It looks like you're using Python 3.7. What version of macOS are you using? Also what version of Jupyter Notebook are you using?

Mac OS Mohave 10.14.16.
NB version = 5.7.6
On Thu, May 14, 2020 at 2:04 AM Toby Roseman<EMAIL_ADDRESS>wrote:

Ok, this does look like a bug.
It looks like you're using Python 3.7. What version of macOS are you
using? Also what version of Jupyter Notebook are you using?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apple/turicreate/issues/3184#issuecomment-628231157,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJSMUL4VGKBYW25V4YVGZXTRRL75RANCNFSM4M5WPNPQ
.

I am having the same problem on Fedora 30
python 3.7
pip3 20.0.2
Jupyter-Notebook 6.0.3

@PriyankaMalhotra26 and @shriaas2898 - What specific python package are you installing to get Jupyter Notebook?
I believe jupyterlab is the Python package for getting Jupyter Notebook. However that package doesn't have a 5.7.6 or a 6.0.3 version.
Using the most recent version of jupyterlab and turicreate, everything works for me. I'm on macOS 10.15.15. I was using Safari and Python 3.7.

I have 'jupyter-lab' version 1.2.6.
However, I have installed notebook directly by command:
'pip install notebook'
And the 'jupyter-notebook' version is 6.0.3

@shriaas2898 - When I run pip install notebook from a fresh virtual environment. I do get jupyter-notebook version 6.0.3. However that does not cause jupyter-lab to get installed. I do get:
jupyter-client==6.1.3
jupyter-core==4.6.3
From a new virtual environment, if I run:
pip install notebook turicreate
everything seems to work fine. From the notebook, I can import turicreate and use it.
Please try using TuriCreate with Jupyter Notebook from a new virtual environment.

Solved:
Turicreate requires libnsl shared object which used to come bundled with glibc in earlier versions of fedora but turns out it got discontinued for some reason.
Installed libnsl with command:
sudo dnf install libnsl
and now turicreate is working.
What I didn't understand that pip should've checked libnsl dependency before installing but I did not get any error during installation.


update docs; add CI badge

update documentation to reflect changes made.  Old documentation kept as well, since it still works.  (Listed as "legacy")

Looking good. Thanks a lot!


Windows autostart feature

Feature request

What problem does this feature solve?
Start Hyperion manually every time
What does the proposed API look like?
The installer (NSIS) should write a registry key for the current user or for all users
How should this be implemented in your opinion?
https://docs.microsoft.com/en-us/windows/win32/setupapi/run-and-runonce-registry-keys
https://nsis.sourceforge.io/Reference/WriteRegStr
Are you willing to work on this yourself?
Maybe 😄

Cool idea, should this be a one time decision (install) or an option for Hyperion to enable/disable the entry whenever wanted?

Ideally the second variant

Hm, regedit needs admin. There is another possible solution to use %appdata%\Microsoft\Windows\Startmenü\Programme\Autostart and place a link to hyperiond. But the path seems to be lang specific, at least on Win 7.

Forget what i said, 'HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run' should be always accessible.

Or Manifest
https://docs.microsoft.com/en-us/previous-versions/bb756929(v=msdn.10)?redirectedfrom=MSDN#requested-execution-levels

The registry should be able to be described in Hyperion mode with the help of QSettings.
https://doc.qt.io/qt-5/qsettings.html

For my second attempt there is another region independent pathC:\Users\%USERNAME%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
Upgrading the manifest to admin is probably a little heavy :)
At least we have now enough hints :)

UAC is really simple with Cmake.
https://prnt.sc/t80kce
https://prnt.sc/t80kxb


Feature/live params

use this branch for testing the live-params feature. see boilerplate pr for more infos.
TODO

Run param syncronisation through parameter constraints

I introduced a new context, the RuntimeContext to handle any state related to the runtime of a project (hash, minter address, params, params definition, etc...). Previously, the state was scattered in 2 different contexts (ParamsContext and MainContext), resulting in a few issues:

The results of application-level operation relying on the entirety of the runtime state could not be exposed next to the state (we had to create a new context, or repeat the operation). This issue became apparent when I tried to compute if the auto-refresh option should have triggered when a parameter with "update: sync" was updated.
Adding new runtime variables (such as execution context, or iteration number) would become ambiguous and would drastically complexify operations described in (1) - now everything is centralized in the Runtime context.
The MainContext also served other purposes, resulting in it becoming bloated

Implementation details:

a soft/hard hash of the runtime context are computed in the RuntimeContext, this is used to know if a change was applied on soft (any params) or hard (only runtime parts requiring a hard refresh of the iframe), very easy to consume elsewhere.

Note (@maerzhase):

By removing the ParamsContext, there will probably be some refacto to do on the main front-end as well to replicate this change. I believe this is for the best as we would have faced similar issues there.

@ciphrd looks good and sure anticipated that. will take care of the changes on the website


ModuleNotFoundError: No module named 'libtmux'

Hi,
When I install and run "python3 icebreaker.py -l targets.txt" I get "ModuleNotFoundError: No module named 'libtmux'" . Anyone had experience of this and know what I'm doing wrong?
Thanks.

Did you run './setup.sh' then 'pipenv shell' before running the tool?
You're just missing the libtmux library which should be installed by the
./setup.sh command. My guess is you're running the tool outside the pipenv
environment or the 'pipenv install --three' command failed when you ran
./setup.sh.
On Wed, Mar 7, 2018 at 8:37 AM, simonj-smith<EMAIL_ADDRESS>wrote:

Hi,
When I install and run "python3 icebreaker.py -l targets.txt" I get
"ModuleNotFoundError: No module named 'libtmux'" . Anyone had experience of
this and know what I'm doing wrong?
Thanks.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/DanMcInerney/icebreaker/issues/5, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABuspeSb2RyYN6RSEkCTanN29bB6q9VQks5tb_6egaJpZM4SgqUs
.

Hi Dan,
Thanks for the quick response, looks like it is 'pipenv install --three' that is having problems. Checking back I can see the below:
Running: pipenv install --three
Creating a virtualenv for this project…
Using /usr/bin/python3 to create virtualenv…
⠋usage: main.py [-h] [-p PYTHON] [-i PACKAGES] [-r REQUIREMENTS] [-d]
[-a PROJECT]
envname
main.py: error: too few arguments
Virtualenv location:
Creating a Pipfile for this project…
Traceback (most recent call last):
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/bin/pipenv", line 11, in
sys.exit(cli())
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/lib/python2.7/site-packages/pipenv/vendor/click/core.py", line 722, in call
return self.main(args, **kwargs)
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/lib/python2.7/site-packages/pipenv/vendor/click/core.py", line 697, in main
rv = self.invoke(ctx)
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/lib/python2.7/site-packages/pipenv/vendor/click/core.py", line 1066, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/lib/python2.7/site-packages/pipenv/vendor/click/core.py", line 895, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/lib/python2.7/site-packages/pipenv/vendor/click/core.py", line 535, in invoke
return callback(args, **kwargs)
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/local/lib/python2.7/site-packages/pipenv/cli.py", line 197, in install
selective_upgrade=selective_upgrade
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/local/lib/python2.7/site-packages/pipenv/core.py", line 1731, in do_install
ensure_project(three=three, python=python, system=system, warn=True, deploy=deploy, skip_requirements=skip_requirements)
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/local/lib/python2.7/site-packages/pipenv/core.py", line 652, in ensure_project
ensure_pipfile(validate=validate, skip_requirements=skip_requirements)
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/local/lib/python2.7/site-packages/pipenv/core.py", line 342, in ensure_pipfile
project.create_pipfile(python=python)
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/local/lib/python2.7/site-packages/pipenv/project.py", line 410, in create_pipfile
config_parser = ConfigOptionParser(name=self.name)
File "/root/.local/share/virtualenvs/icebreaker-2FivyZWy/local/lib/python2.7/site-packages/pipenv/patched/pip/baseparser.py", line 149, in init
assert self.name
AssertionError
/root/.local/share/virtualenvs/icebreaker-2FivyZWy/local/lib/python2.7/site-packages/pipenv/utils.py:1147: ResourceWarning: Implicitly cleaning up <TemporaryDirectory '/tmp/pipenv-CuZOA2-requirements'>
warnings.warn(warn_message, ResourceWarning)
[] Run "pipenv shell" before running icebreaker
[] Example usage: ./icebreaker.py -l targets.txt
Previously I thought I was good after seeing the last 2 lines but it looks like something is causing a fail in that install. I tried an apt update and apt upgrade and total removal and re-clone of the git but still no joy. I am running in Kali Linux if that makes any difference.

I've been having a lot of weird issues with pipenv lately but that one is new. One way I solved my previous issue was to do 'pipenv install --two' then 'pipenv install --three' and it worked normally which is bizarre but worth a try.

Did a clean install and followed your advice about doing the installs separately and manually and it's all working fine now.
Thanks for your help and a cool project.


fix(meta): LSM/SST metrics is stale when there is no alive compactor

I hereby agree to the terms of the Singularity Data, Inc. Contributor License Agreement.
What's changed and what's your intention?
As described in #4380, syncing sstable metrics is done by report_compact_task which is only triggered by compact_done context. The absent alive compactor will cause stale data. The PR changes include:

[x] refactor trigger_sst_metrics to allow update without compaction status
[x] update sst metrics for modified compaction groups upon commit_epoch

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation
If your pull request contains user-facing changes, please specify the types of the changes, and create a release note. Otherwise, please feel free to remove this section.
Types of user-facing changes
sstable metrics are now synced every commit_epoch as well as  compact_done
Release note
Refer to a related PR or issue link (optional)
#4380

PTAL @hzxa21 @wenym1

why is ths PR merged?

Is it the bug of github? The files changed of this PR becomes zero too 🤣


fluxsort comparison behavior

Hi, I've recently been doing some research on sort implementations and noticed that in my tests that fluxsort is not stable. The test and benchmark suite is written in Rust, the following test fails for fluxsort but passes for other stable sorts such as Rust slice::sort and C++ std::stable_sort but not for fluxsort. You can find the test code here https://github.com/Voultapher/sort-research-rs/blob/2642b98dc60cb6c9a6dbdec706a71ebdfbdf89e1/tests/main.rs#L219. In essence it packs two i32 into one u64 and extracts in the comparison function the two i32 again and only uses the first one as comparison and then later checks that the order of the ascending second elements remains in order.
Also on a sidenote, I'm seeing rather different benchmark results, where fluxsort pretty much never beats pdqsort.

Fluxsort passes my own stability tests.
Do you have the cmp macro defined for primitive comparisons, or are you using a comparison function? Things can get a bit finicky since fluxsort uses the C interface for sorts by default.

Indeed I incorrectly supplied the comparison value.
Here is a reproducer:
#include <fluxsort.h>

#include <stdint.h>
#include <string.h>

// This is demo code and will only work on little-endian systems.

void print_i32_slice(int32_t *vals, size_t len)
{
    printf("[");
    for (size_t i = 0; i < len; i += 2)
    {
        printf("(%d, %d)", vals[i], vals[i + 1]);
    }
    printf("]\n");
}

int cmp_unpack_u64_to_i32(const void *a_ptr, const void *b_ptr)
{
    int32_t a = *(int32_t *)(a_ptr);
    int32_t b = *(int32_t *)(b_ptr);

    printf("comparing a: %d b: %d\n", a, b);

    // if (a < b)
    // {
    //     return -1;
    // }
    // else if (a > b)
    // {
    //     return 1;
    // }

    // return 0;

    if (a < b)
    {
        return -1;
    }

    return 1;
}

int main()
{
    uint64_t original[2] = {4294967296,<PHONE_NUMBER>};
    uint64_t v[2] = {};
    memcpy(v, original, sizeof(original));

    printf("original: ");
    print_i32_slice((int32_t *)original, 4);

    fluxsort((void *)v, 2, sizeof(uint64_t), cmp_unpack_u64_to_i32);

    printf("sorted: ");
    print_i32_slice((int32_t *)v, 4);

    return 0;
}

Rust internally and C++ externally use the is_less contract where a function returns a bool. I had incorrectly mapped this concept into the glue code, that uses a Rust closure as comparison function. When I supply the full values it passes the test.
Arguably this could be avoided by limiting comparisons to is_less ie. x = cmp(pta + 1, pta) < 0; instead of x = cmp(pta, pta + 1) > 0;. This ties into the theme of how to specify the comparison function. In your benchmarks you use a  - b which can invoke UB, which for example manifests itself when sorting int32_t v[2] = {-2147483644, 5}; for example by yielding an incorrect sort result. Fundamentally this is the shortcoming of the qsort interface, by limiting yourself to is_less one could do:
if (a < b)
{
    return -1;
}

return 1;

And still retain the stability guarantee, while losing some performance but not the 50% extra of using the fully correct comparison function. Or bite the bullet and change the comparison interface to use is_less instead of an int.

Internally my sorts only require the (a > b)  comparison, which is the right way to go about it as that translates to both greater than and not stable, as well as being compatible with the qsort interface.
C++ messed up by not being compatible with C in this regard, and less than doesn't translate to stable since that would be (a <= b). So it should be c++ and rust biting the bullet, but I doubt that's going to happen.
a - b indeed has an issue with large numbers, I'm forced to use it however in the benchmark since it calls qsort, and qsort doesn't perform proper stability checks and uses a mix of <, <=, and >.

I'm not sure this is the right place to talk about standard library API design, to clarify Rust uses Ord as their interface and is_less is an internal detail.
Indeed you seem to have done what I suggested but biased towards is_more instead of is_less.

a - b indeed has an issue with large numbers, I'm forced to use it however in the benchmark since it calls qsort, and qsort doesn't perform proper stability checks and uses a mix of <, <=, and >.

So what you are saying is, look at my stable algorithm and how it performs against this unstable sort, while making your sort unstable and both sorts broken? There is saying that writing fast code is easy, and writing correct code is hard. Looking at the documentation of qsort https://en.cppreference.com/w/c/algorithm/qsort it tells you to do:
int compare_ints(const void* a, const void* b)
{
    int arg1 = *(const int*)a;
    int arg2 = *(const int*)b;

    if (arg1 < arg2) return -1;
    if (arg1 > arg2) return 1;
    return 0;

    // return (arg1 > arg2) - (arg1 < arg2); // possible shortcut
    // return arg1 - arg2; // erroneous shortcut (fails if INT_MIN is present)
}

Imo if you want a fair comparison you ought to use the correct comparison function for both qsort and fluxsort, and if you want the fastest absolute performance and comparison to languages with faster comparison function abstractions like C++ and Rust changing the signature seem inevitable.

Not quite, in the benchmark against pdqsort the #define cmp(a,b) (*(a) > *(b)) macro is enabled for fluxsort and no comparison functions are involved.
In the case of qsort it doesn't particularly matter for the benchmark I'm running, but admittedly arg1 - arg2 is slightly favorable for fluxsort.

Ah good to know, I'll look into benchmarking with that.

I just came across your presentation and wanted to leave a few remarks for you, figured doing so here might be the best place.
Fluxsort does work on non-integers, but what I'm doing (probably in one of the more atrocious C programming practices) is treating pointers as either 32 or 64 bit integers. The code works out of the box for 32 and 64 bit systems if sizeof(char *) is used for C strings when calling fluxsort(). In the case of 64 bit pointers the pointers are copied as long long, which isn't an issue in C, and each long long is passed as a void type to the comparison function, which can correctly cast it to the pointer it actually is. The benchmark itself performs a test using C strings.
As for stability, some kind of definite proof would be useful. One possible issue when porting is that unguarded insert requires the first 2 elements to be sorted, which the tail_swap() function that calls it takes care of.
Testing for stability is pretty rigorous in the benchmark using a dedicated method for integers, and since identical strings have different pointers, it's also detected during the string test.
Anyways, a cool presentation, and good luck with the porting effort.

Thanks for feedback and kind words :)
You are correct that it works for some user types, however because it allocates memory with malloc void* it would underalign user types with larger than pointer alignment, which would be UB. So it's support for user defined types is limited. Plus there are two other properties it doesn't have that make a port without modifications unsuitable as general purpose sort in Rust. For one, a user may see diverging observations of what value was passed into the comparison function. If in a horribly malicious but legal way the user was sorting a Mutex<Option<Box<...>>> a Mutex holding either a null-pointer or a valid pointer, and would swap the content during a comparison from owned pointer to null-pointer freeing the allocation, when the user drops the slice after sorting it would free the allocation again -> double free UB. The other one would be a panic/exception during comparison, leaving the slice with potential duplicate elements, which again could lead to double free UB. Of course C has neither scope based destructors (RAII) nor unwinding, so for C it's perfectly fine for user provided types as long as their type has fundamental alignment.

I don't think I use malloc void* in fluxsort. The general idea in C would be to create a custom structure in fluxsort.h for each custom size needed. It is a bit obnoxious, but writing typeless code in C is even more so.
@Voultapher
I published a simplified version of quadsort with decent performance that might be useful to your porting effort. It's around 150 lines of code. It should be some orders of magnitude easier to create a formal proof for it as well.
https://github.com/scandum/piposort

Not sure if we're talking about the same thing. In fluxsort.h you'd define:
typedef struct {char bytes[20];} struct160;
#define VAR struct160
#define FUNC(NAME) NAME##160
#define STRUCT(NAME) struct NAME##160

#include "fluxsort.c"

That should allow sorting any 20 byte custom structure. Would also need to add a case 20 in void fluxsort()

I'm talking about types with custom alignment:
#include <stdalign.h>
#include <stdlib.h>

struct {
    alignas(64) char bytes[8];
} CustomType;

void* x(size_t count) {
    // wrong
    // return malloc(sizeof(CustomType) * count);

    // correct
    return aligned_alloc(alignof(CustomType), sizeof(CustomType) * count);
}

Here the malloc call as done by fluxsort would under-align CustomType.

Thanks, that's not something I've had to deal with often. I'll look into it.

I think it's fine to leave it as is, while adding a note to the documentation. My understanding is, that for certain types such as SIMD registers it's UB to allocate and them use them if they are under-aligned.


Remove test classes from module jar files

For some reason, test classes are packaged into module jar files. I figure that this should not be the case.

This is probably in part coming from how test classes in the engine can be extended from modules. I don't recall if any of those classes were in the Core module at some point.
Doesn't look like they are right now, so yeah, we could probably toss those. Unless there is a use case for making modules with test template classes at some point, maybe? Although perhaps in that case we can add some tweak to only include those if needed.

It seems as if this issue was caused by outdated build.gradle files in the module folders. I copied the latest version from Core and that fixed it.


Fix spacing in linode_sd_config

Fix spacing in linode_sd_config causing "credentials not found in type linode.plain"
Signed-off-by: Ryan Lonergan<EMAIL_ADDRESS>

Thanks!


Refactor to make testing easier

Codecov Report

Merging #90 (3e77775) into master (616fa81) will increase coverage by 1.27%.
The diff coverage is 5.12%.

@@            Coverage Diff            @@
##           master     #90      +/-   ##
=========================================
+ Coverage    1.38%   2.66%   +1.27%
=========================================
  Files           2       3       +1
  Lines         144     150       +6
  Branches       48      50       +2
=========================================
+ Hits            2       4       +2
- Misses        131     134       +3
- Partials       11      12       +1


added workflow as per issue #63

Related Issue
Fixes #63
Description
This feature aims to solve the problem of inconsistent and delayed communication following the merging of PRs. By automating the commenting process, it ensures that contributors receive timely feedback and acknowledgments. It also reduces the administrative burden on maintainers, allowing them to focus more on code reviews and other critical tasks.
Type of PR

[ ] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Checklist:

[X] I have performed a self-review of my code
[X] I have read and followed the Contribution Guidelines.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ ] I have commented my code, particularly in hard-to-understand areas.

@Bhanu-code please review and merge this PR


Add 3rd party bgp support from Isovalent/Cilium for EKS-A

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/ok-to-test

@amitmavgupta Could you add a comment to each of the PRs in this stack indicating which PR comes before it - it greatly helps with navigability.

We are going to hold this PR pending @csplinter 's review.

Hi All- could you let us know how we can move ahead with this PR?


CREATE> IMPORT> Unclear result of the import on the Create page

From @julieopla on June 12, 2018 7:7
CURRENTLY
Once you import your file (json or csv) in the Create part, when you come back to the page, the "Empty" section gets highlighted, so you might think that you're going to start your chatbot empty

SHOULD BE
A message should tell the user that the import was correctly made, moreover, maybe an other icon could appear named "Your import" or with the file's name
Copied from original issue: Opla/community-edition#30

SHOULD BE
When you click on import card the import function should be launch


youtube-dl issue

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://youtu.be/wyNnCJLGK5A']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.10.11 (CPython) - Windows-10-10.0.19045-SP0
[debug] exe versions: none
[debug] Proxy map: {}
[youtube] wyNnCJLGK5A: Downloading webpage
ERROR: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\usuario\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\youtube_dl\YoutubeDL.py", line 815, in wrapper
return func(self, *args, **kwargs)
File "C:\Users\usuario\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\youtube_dl\YoutubeDL.py", line 836, in __extract_info
ie_result = ie.extract(url)
File "C:\Users\usuario\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\youtube_dl\extractor\common.py", line 534, in extract
ie_result = self._real_extract(url)
File "C:\Users\usuario\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\youtube_dl\extractor\youtube.py", line 1794, in _real_extract
'uploader_id': self._search_regex(r'/(?:channel|user)/([^/?&#]+)', owner_profile_url, 'uploader id') if owner_profile_url else None,
File "C:\Users\usuario\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\youtube_dl\extractor\common.py", line 1012, in _search_regex
raise RegexNotFoundError('Unable to extract %s' % _name)
youtube_dl.utils.RegexNotFoundError: Unable to extract uploader id; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Checklist

[x] I'm reporting a broken site support issue
[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 bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

PASTE VERBOSE LOG HERE

Description

WRITE DESCRIPTION HERE

[x] I've searched the bugtracker for similar bug reports including closed ones

Learn how by reading #30839 (again?).

[x] I've read bugs section in FAQ

Apply this.


nltools.stats.downsample returns 1-indexed dataframe

This is a confusing and made me thing something wrong was happening in the downsampling making it seem off. @ljchang is there any reason not to use the groupby trick starting from 0 instead of 1 in this line?
Alternatively we could just to a .reset_index(drop=True) in this line and the .median() line

For some reason I thought we fixed it because it threw an error but looks like it was coded to start from 1 from the start. Think it's fine to reset index before returning.

@ejolly Is this fixed now in PR #149

Fixed in PR #149


Need to score at least 70% on the EPUB Test Suite

Test suite is located at http://www.epubtest.org/.  Need to test the candidate build and log the results on the website.

Very stale.  CLosing.


gtest error

How to slove？

Hello,
You should still be able to use the main library since only the unit tests failed to build, which are not required for the main functionality.

how to solve this problem?


Fragment in fullscreen mode not possible

Inside my fragment I'm using Google Places search and creating new markers from results. Everything is working fine, but I need to customize this fragment.Is it possible to customize appearance of fragment without using intent and Activity.I need to open places search in full screen and with black background
Here is my XML :
<fragment
  android:id="@+id/place_autocomplete_fragment"
  android:layout_width="0dp"
  android:layout_height="0dp"
  app:layout_constraintTop_toTopOf="@+id/gl_h_0p"
  app:layout_constraintBottom_toTopOf="@+id/gl_h_100p"
  app:layout_constraintRight_toRightOf="@+id/gl_v_980p"
  app:layout_constraintLeft_toLeftOf="@+id/gl_v_900p"
android:name="com.google.android.gms.location.places.ui.PlaceAutocompleteFragment"
  />

Here is fragment:
@Override public void onViewCreated(View view, Bundle savedInstanceState) {
super.onViewCreated(view, savedInstanceState);
autocompleteFragment  = (PlaceAutocompleteFragment)getActivity().
getFragmentManager().findFragmentById(R.id.place_autocomplete_fragment);
autocompleteFragment.setOnPlaceSelectedListener(this);
}
@Override
 public void onPlaceSelected(Place place) {
   Log.d("Place","selected");
 }

 @Override public void onError(Status status) {
   Log.d("Place","error");

 }

This sample has been deprecated/archived (check README for more information on newer samples related to this technology).
As recommended by GitHub, we are closing all issues and pull requests.


Updates SLN file and README regarding NuGet→Paket switch.

Any objections?

None - just waiting for the tests to pass :-)


Monitoring funding tx mining

This PR add steps to monitoring transactions confirmations.
Used in open channel operation.

Codecov Report

Merging #78 (b61bcd2) into master (b6b6128) will decrease coverage by 0.0%.
The diff coverage is 0.0%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@           Coverage Diff           @@
##           master    #78     +/-   ##
=======================================
- Coverage     0.1%   0.1%   -0.0%
=======================================
  Files          41     41
  Lines        3343   3377     +34
=======================================
  Hits            3      3
- Misses       3340   3374     +34

Impacted Files
Coverage Δ

src/bus/ctl.rs
0.0% <0.0%> (ø)

src/channeld/automata/accept.rs
0.0% <0.0%> (ø)

src/channeld/automata/propose.rs
0.0% <0.0%> (ø)

src/watchd/runtime.rs
0.0% <0.0%> (ø)

src/watchd/worker.rs
0.0% <0.0%> (ø)

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


utils/git_repository: add ::git_branch and ::git_commit_message

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

This PR adds two helper functions for Git repos:

Utils::git_branch, which can used instead of:

shell_output("git log -1")
shell_output("git log --format=%B -n 1 HEAD")

Utils::git_commit_message, which can used instead of:

shell_output("git symbolic-ref --short HEAD").chomp
shell_output("git rev-parse --abbrev-ref HEAD").strip

Review period will end on 2021-01-22 at 01:32:37 UTC.

Review period will end on 2021-01-22 at 01:32:37 UTC.

Review period ended.

Review period ended.


結果位置加入計算平均時間的儀表板

計算平均時間，記得要除以job數
然後根據某個時間範圍給予評語

https://www.nngroup.com/articles/response-times-3-important-limits/
0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result.
1.0 second is about the limit for the user's flow of thought to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data.
10 seconds is about the limit for keeping the user's attention focused on the dialogue. For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback indicating when the computer expects to be done. Feedback during the delay is especially important if the response time is likely to be highly variable, since users will then not know what to expect.


Change parse logic In accordance with open close principle

Change parse logic In accordance with open close principle
Description

change valid check from if to guard
in parse function not change code when add other parce function, just append at parserArchiver
Motivation and Context

If modify or add more parse function, now parse add code like if else, but In accordance OCP not change
parse code, just implement

How Has This Been Tested?

print and check data correctly parsed
import KituraNet
import KituraSys

let router = Router()
router.use(BodyParser())
router.post("/json") {
    request, response, next in
    response.status(HttpStatusCode.OK).send("Hello, World!")
    next()
}

router.post("/text") {
    request, response, next in
    print("text")
    if let body = request.body{
        print(body.asText())
        response.status(HttpStatusCode.OK).send("Hello, World! \n")
    }
    next()
}

router.post("/urlencoded") {
    request, response, next in
    print("urlencoded")
    if let body = request.body {
        var result = ""
        for (k,v) in body.asUrlEncoded()! {
            result += "\(k)=\(v)&"
        }
        response.status(HttpStatusCode.OK).send("Hello, World! \n" + result)
    }
    next()
}

let server = HttpServer.listen(8989, delegate: router)
Server.run()

It is Test code able to parse

Checklist:

[o] I have submitted a CLA form
[o] If applicable, I have updated the documentation accordingly.
[o ] If applicable, I have added tests to cover my changes.

Hey sorry about the delay. Can you fix the merge conflicts that this PR now has?

That's ok. I'm just waiting your response, will fixed comfilcts this problem

Now fixed conflicts, please review

Looks OK to me.

Can you undo your changes to README.md? We can accept after that.

Not long after the start . It's hard , and thank you.


Ensure type correctness when using EmailStr

Change Summary
Hi,
Currently EmailStr is always converted to a str which leads to false-negatives during type checking, e.g. using mypy, and may cause non-obvious bugs when using isinstance, which is useful in combination with Union-types, e.g.:
import pydantic as pyd

class Model(pyd.BaseModel):
  v: pyd.EmailStr

m = Model(v=pyd.EmailStr("test@example.com"))
# reveal_type(m.v) == `'pydantic.networks.EmailStr`
assert isinstance(m.v, pyd.EmailStr)  # this raises

This change always makes EmailStr an EmailStr and should be fully backward-compatible, as EmailStr is still an instance of str.
Related issue number
None that I know of
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

I disagree with this approach for performance and flexibility the current performance is preferable.
To fix mypy, instead do
if TYPE_CHECKING:
    EmailStr = str
else:
    class EmailStr:
        ...

please update.

@samuelcolvin I quite agree with @gherx. I don't think the impact on performance is a problem.
For consistency I find it quite disturbing to have
from pydantic import AnyUrl, BaseModel, EmailStr

class M(BaseModel):
    x: AnyUrl
    y: EmailStr

m = M(x='http://test.com'<EMAIL_ADDRESS>assert isinstance(m.x, AnyUrl) is True
assert isinstance(m.y, EmailStr) is False

I let you answer

Okay, I agree with this but to avoid any breaking changes, let's defer this until V2.

As per #4516, EmailStr has become a true str in typing terms in V2.
We're using
if TYPE_CHECKING:
    EmailStr = typing_extensions.Annotated[str, ...]
else:
    ....

Hence I'm closing this.


Setup DB and Add Pagination to Conform to OGC Specs

This PR makes changes to the app that were required to comply with the pagination requirements of OGC specs: '/req/job-list/limit-definitionand/req/core/pl-limit-definition`. The solution implemented also overcame the shortcoming of the cache (as discussed in the paper).
The following enhancements have been implemented:

/jobs and processes routes now support offset and limit parameters and include links to previous and next pages. This was a requirement of OGC Specs.

Add GitHub Actions like symbols to job statuses

Update HTML pages to be sync with recent code changes

Update tests to reduce testing time from ~5 min to ~4 min

Make echo logs colorful to easily identify requests that were failed or bad

Use of SQLite database in place of snapshots to persist job records.

Get rid of the JobsCache hashmap and introduce the ActiveJobs hashmap. ActiveJobs keep a record of currently active jobs. As soon as a job reaches a terminated state (SUCCESSFUL, FAILED, DISMISSED). The job is being removed from the ActiveJobs and status, logs, etc are updated in the database.

Introduce a hit and miss strategy in handlers. A job id is first checked in ActiveJobs, if it is there (hit) then return a response immediately without checking the database, else if job is not in ActiveJobs (miss) then look in the database. This is similar to the cache hit-and-miss concept.

System design before and after:

Benefits achieved with this PR:

Use of the database allows easy pagination, before we were using hashmap to store jobs which has no particular order.

SQLite is a file-based database and will be in sync with the system all the time. Hence it solves the issue of losing data if the server crashes in between snapshots without adding the complexity of standing up a new database server.

SQLite file can be viewed and updated by software such as DBeaver previously the only way to look at jobs was through API, providing no control over raw data.

JobsCache was never a cache, to begin with, it was serving as a data store.

No need to calculate and track the size of jobs in memory as only active jobs are stored in memory. The remaining jobs are in the database (disk).

Fix #37 Fix  #27 Fix #18

I see there is mutex lock/unlock going on and have some questions:

Does the current Mutex behavior protect the sqlite file or only the in-memory job lists?
Are deadlocks possible with the current Mutexes?
Are deadlocks possible with the current sqlite interactions?
Should we add timeouts?

I see there is mutex lock/unlock going on and have some questions:

Does the current Mutex behavior protect the sqlite file or only the in-memory job lists?
Are deadlocks possible with the current Mutexes?
Are deadlocks possible with the current sqlite interactions?
Should we add timeouts?

@mxkpp I will make this an issue to research later.

I see there is mutex lock/unlock going on and have some questions:

Does the current Mutex behavior protect the sqlite file or only the in-memory job lists?
Are deadlocks possible with the current Mutexes?
Are deadlocks possible with the current sqlite interactions?
Should we add timeouts?

@mxkpp I will make this an issue to research later.

@ar-siddiqui was this resolved, or an issue opened to track?


Is there a CLI tool

I am looking for something like:
$ showdown -o foo one.md two.md three.md

and it would output to a folder:
foo/
  one.html
  two.html
  three.html

I think it might be easier to actually just script this and then you can start opening up how you wish to interact with showdown.
For example, say you create a script called makehtml
#! /bin/bash
# makehtml: create html folder of converted md files

files=$(ls $1)
mkdir $1"/html"

for file in $files; do
  showdown makehtml -i $file -o $1"/html/"$file".html"
done

if you had a directory named md with all your md files, then you could call the script like this
./makehtml /path/to/folder/md

You can go nuts with customising this as well.