Minor output changes

Makes sense. :+1: from me.
Would you mind updating the cookbook to use this newer version?

@eherot some notes, but I’m gonna merge this in & cut a release. This seems like some nice improvements.


cant add project or users on 0.4.5 (after migration from 0.3.5-rc)

Hi, i migrated from 0.3.5-rc to 0.4.5 (and run the database migration as documented).
 This happens sometimes after an upgrade.

Closing due to no further details provided.


Add error for empty scopes.

Before, a ParamNotFoundError was raised.
This specializes the error to indicate the collection doesn't exist at all.
This should be easier to debug for users.

Codecov Report

Merging #1698 (38498c8) into main (d1fb06e) will decrease coverage by 0.01%.
The diff coverage is 90.90%.

@@            Coverage Diff             @@
##             main    #1698      +/-   ##
==========================================
- Coverage   83.18%   83.17%   -0.02%
==========================================
  Files          69       69
  Lines        5853     5867      +14
==========================================
+ Hits         4869     4880      +11
- Misses        984      987       +3

Impacted Files
Coverage Δ

flax/core/scope.py
92.68% <87.50%> (-0.40%)
:arrow_down:

flax/errors.py
88.23% <100.00%> (+0.54%)
:arrow_up:

flax/linen/stochastic.py
92.00% <0.00%> (-0.31%)
:arrow_down:

flax/jax_utils.py
70.96% <0.00%> (+0.18%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d1fb06e...38498c8. Read the comment docs.


⚠ Bofrost.be has degraded performance

In ad07ef3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1136 ms

Resolved: Bofrost.be performance has improved in 757fa17.


I can't add any images, for some reason it just freeze then nothing are added.

@Georges-SR any error in console ? Whats the size of the image ?


[action] Continue git_commit action execution if there is nothing to commit

Checklist

[x] I've run bundle exec rspec from the root directory to see all new and existing tests pass
[x] I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
[x] I've read the Contribution Guidelines
[x] I've updated the documentation if necessary.

Motivation and Context

git_commit action fails if there's nothing to commit.

closes https://github.com/fastlane/fastlane/issues/14437
Description

Added a new parameter allow_nothing_to_commit.

Tested the changes by adding a new unit test and doing manual testing.

👋 @janpio and @joshdholtz
Thanks for your questions / suggestions. I updated the implementation - now we're checking if there's something to commit via git status --porcelain. If the git index is clean, there's no point of committing changes, so we just early return.
Added one more unit tests 💪
Let me know what you think 🙇

👋 @joshdholtz
PR is ready for another round, thanks for your comments! 💪


Integer literal is too large to be represented in any integer type

Hi,
lt seems that I can not save 128bit integers (actually compile fails with error from title). Even if I save small number in db in uint128_t field, and I copy saved value (for example 0xffa11f4b000000000000000000000000) and I try to assign it with uint128_t tmp = 0xffa11f4b000000000000000000000000 it doesn't compile. Any ideas?
Thanks in advance

uint128_t field = 0xffa11f4b;
field <<= 96;


Inconsistent bounding boxes

Hi,
I tried to repeat https://github.com/AdaRoseCannon/aframe-htmlmesh/issues/4 here but it didn't work. I tried making a bounding box but the geometry was very different from what I expected, namely a square rather than a rectangle.
In the screenshot below I can show one that worked, the lower one, and one that didn't, despite using the same code
el = new THREE.BoxHelper( document.getElementById("locationreload").object3D.children[0], 0x00ff00 ); AFRAME.scenes[0].object3D.add(el)

Is somehow forcing a sync() necessary? Did I miss a step? Note that I did that via the console and seconds after the scene was displayed so I'm relatively confident everything was loaded, at least displayed as it should. I also noticed https://github.com/lojjic/aframe-troika-text/issues/38 before but again, I'm not doing it right after adding the element so not sure it would relevant here.
Anyway, what is the recommended way to add a background behind an entire element or part of it?
PS: I noticed https://protectwise.github.io/troika/troika-three-text/#carets-and-selection-ranges that could later on be useful to highlight words or lines but didn't dive in there before being able to have the entire element.

The AFrame inspector also makes the square bounding boxes on element selection

If I change value from 12345 to 1 the bounding box does seems like it is update properly so... maybe unrelated, maybe a threejs/AFrame boxhelper issue. Leaving this open for now as I still investigate.

Seems it's a boxhelper issue as the boundingbox itself seems fine and creating a boxgeometry from it works as expected. Less convenient but sufficient to add a background.

My suspicion is the BoxHelper was reading the geometry.boundingBox before the text sync() callback is complete and not getting updated afterward? 🤷

I am facing the same issue, the bounding box is not getting properly

@lijualivenow try checking 1000ms after creating the entity and if it does make a difference tried indeed .sync() and check after, iirc worked for me.

@Utopiah, after 1000ms it's working, thank you.


Update Image.cs

Before reading stream for header , position should be changed to 0 if the passed stream were read before

Ah good catch! Cheers! :+1:


docs: translation update

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[x] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:

based on commit #3975


Configure Azure PipelinesCode workflow

This pipeline configuration builds the application and produces a build for the Release configuration.

@microsoft-github-policy-service agree [company="{your company}"]

@microsoft-github-policy-service agree


ci: init release-please

NS-52.
Configure the release-please process (triggers, etc.)

Notification service branch is deployed to platta: https://kuva-notification-service-pr47.api.dev.hel.ninja :rocket::rocket::rocket:


Fixes to workshop article

Category

[x] Content fix
[ ] New article

Docs Build status updates of commit 85051c9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/microsoft365-maturity-model--run-workshop.md
:warning:Warning
View
Details

Community/media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - Content Set.xlsx
:white_check_mark:Succeeded

Community/media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - Hardcore Set.xlsx
:white_check_mark:Succeeded

Community/media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - People Set.xlsx
:white_check_mark:Succeeded

Community/media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - Quick assessment.xlsx
:white_check_mark:Succeeded

Community/media/microsoft365-maturity-model--run-workshop/mm4m365-levels.png
:white_check_mark:Succeeded
View

Community/media/microsoft365-maturity-model--run-workshop/workship-diagram.png
:white_check_mark:Succeeded
View

Community/microsoft365-maturity-model--run-workshop.md

Line 2, Column 1: [Warning-ms-author-missing] Missing required attribute: 'ms.author'. Add the current author's Microsoft alias.
Line 2, Column 1: [Warning-ms-prod-or-service-missing] One of the following attributes is required: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.
Line 105, Column 5: [Warning-link-out-of-scope] File 'media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - Quick assessment.xlsx' referenced by link 'media/microsoft365-maturity-model--run-workshop/Workbook%20-%20MM4M365%20workshop%20tool%20-%20Quick%20assessment.xlsx' will not be built because it is not included in build scope.
Line 135, Column 3: [Warning-link-out-of-scope] File 'media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - Content Set.xlsx' referenced by link 'media/microsoft365-maturity-model--run-workshop/Workbook%20-%20MM4M365%20workshop%20tool%20-%20Content%20Set.xlsx' will not be built because it is not included in build scope.
Line 136, Column 3: [Warning-link-out-of-scope] File 'media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - Hardcore Set.xlsx' referenced by link 'media/microsoft365-maturity-model--run-workshop/Workbook%20-%20MM4M365%20workshop%20tool%20-%20Hardcore%20Set.xlsx' will not be built because it is not included in build scope.
Line 137, Column 3: [Warning-link-out-of-scope] File 'media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - People Set.xlsx' referenced by link 'media/microsoft365-maturity-model--run-workshop/Workbook%20-%20MM4M365%20workshop%20tool%20-%20People%20Set.xlsx' will not be built because it is not included in build scope.
Line 138, Column 3: [Warning-link-out-of-scope] File 'media/microsoft365-maturity-model--run-workshop/Workbook - MM4M365 workshop tool - Quick assessment.xlsx' referenced by link 'media/microsoft365-maturity-model--run-workshop/Workbook%20-%20MM4M365%20workshop%20tool%20-%20Quick%20assessment.xlsx' will not be built because it is not included in build scope.
Line 2, Column 1: [Suggestion-ms-topic-missing] Missing required attribute: 'ms.topic'. Add a valid value to indicate the article type.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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 the docs.microsoft.com contributor guidesPost your question in the Docs support channel


chore: Update/Remove logos in this repo

We've now voted on a logo for the project, so we need to update the README.md to use the new logo. If this logo is being stored in another repo then we should remove the files from here.

@xynydev would you be able to handle this one?

@xynydev would you be able to handle this one?

Sure


fix(argocd): make refreshInterval configuration as optional

Description:
Since we have a fallback value for refreshInterval config, marking it as optional field.

/lgtm


AArch64: temporary patch to allow cross-compiling from non-AArch64

Temporarily disable so the upcoming 1.11 release doesn't require patching, though I don't know that we'll ever bother getting 128-bit floating-point CTFE for AArch64 cross-compilation working. I'll remove the std.outbuffer excisions once we get core.stdc.stdarg.va_arg working on AArch64.
I'll also merge the core.internal.convert commit from dlang/druntime#2257 once I finish the pull and it's merged upstream or before the 1.11 release, whichever comes first, so that no patches will be needed to cross-compile the 1.11 stdlib and its tests for AArch64.

This isn't worth it IMO. Why cheat for AArch64 instead of letting unimplemented stuff fail as expected?


"Build image (repo2docker)" fails with  jupyter-repo2docker: error: argument --image-name:' ... is not a valid docker image name.

Why this happens

image-name should use github.sha (the full commit SHA, containing only [0-9a-f]), rather than inputs.ref (which defaults to github.ref, which depends on the type of trigger and can include invalid characters

Workaround

Specifying jobs.<job_id>.uses.ref: ${{ github.sha }} externally (i.e. in the caller workflow) can bypass this issue since it will cause inputs.ref to be set internally (i.e. inside the called workflow) to a Docker-compatible string

This should be resolved by f45e2be24e6e0a6499ef0497ac38f81a5b4f3316.


Magnifying or minifying a video in Paella on Engange using 🔍 will also start/stop the video

Describe the bug
A clear and concise description of what you see:
When opening a published video on https://stable.opencast.org and clicking the 🔍 with a + or -, the video is magnified or minified but the playback state is also toggled (i.e. a playing video stops and a stopped video starts playing)
To Reproduce
Steps to reproduce the behavior:

Go to https://stable.opencast.org
Click on a published dual-stream video (Published: Yes -> Engange)
Start the video pressing the big play button ▶
Click the magnifying glass 🔍 on one video
The video stops if it was playing, or starts if it was not playing

Expected: Maginifcation/ minification without playback toggle
Environment Information

Browser: Firefox 83.0 (64-Bit)
Opencast 9.0.0.SNAPSHOT - 547d9ef
Paella 6.4.3

This issue is reproducable on https://paellaplayer.upv.es/demos/ and on r/8.x (paella 6.2.7), but on r/8.x the issue occurs only once (i.e. even if you press the magnification glass multiple times after loading the page, the playback state is only toggled once)

A related issue: Pressing the magnifying glass twice may toggle the browser's full-screen state.

Upstream report: https://github.com/polimediaupv/paella/issues/649

Has been fixed in https://github.com/polimediaupv/paella/commit/5d80f3d1fccd94e259f15622da81f69d5ed97d0b (probably Paella 6.4.6)

Has been fixed in https://github.com/polimediaupv/paella/commit/5d80f3d1fccd94e259f15622da81f69d5ed97d0b (probably Paella 6.4.6)

This seems to be fixed, please reopen if you think that is needed


Make nikhita and frank maintainers

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
none

/assign @mrIncompetent

/retest

/lgtm
/approve

/retest


Illegal Characters found in URL

You should not link to proxy pages directly. Illegal Characters found in URL.
Above error I receive if I try to visit old.reddit.com
The website works but why do I receive this error.

Problem with javascript. Add:

$config['js_remove'] = array('reddit.com');

to your config.php file here and that will fix it.
https://github.com/Athlon1600/php-proxy-app/blob/master/config.php

Thanks it works now.


NameError: uninitialized constant Devise

Im using Ruby on rails on Ubuntu for my development and this is the error Im facing when i try to deploy my app on heroku. using the push command
$ git push heroku master
This outputs :
Counting objects: 1023, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (930/930), done.
Writing objects: 100% (1023/1023), 3.56 MiB | 11.00 KiB/s, done.
Total 1023 (delta 31), reused 0 (delta 0)
remote: Compressing source files... done.
remote: Building source:
remote:
remote: -----> Ruby app detected
remote: -----> Compiling Ruby/Rails
remote: -----> Using Ruby version: ruby-2.3.4
remote: -----> Installing dependencies using bundler 1.13.7
remote:        Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
**remote:        Warning: the running version of Bundler (1.13.7) is older than the version that created the lockfile (1.14.6). We suggest you upgrade to the latest version of Bundler by running gem install** bundler.
remote:        Fetching gem metadata from https://rubygems.org/..........
remote:        Fetching version metadata from https://rubygems.org/..
remote:        Fetching dependency metadata from https://rubygems.org/.
remote:        Installing i18n 0.8.1
remote:        Installing rake 12.0.0
remote:        Installing json 1.8.6 with native extensions
remote:        Installing minitest 5.10.1
remote:        Installing thread_safe 0.3.6
remote:        Installing builder 3.2.3
remote:        Installing erubis 2.7.0
remote:        Installing mini_portile2 2.1.0
remote:        Installing rack 1.6.5
remote:        Installing arel 6.0.4
remote:        Installing mime-types-data 3.2016.0521
remote:        Installing coffee-script-source 1.12.2
remote:        Installing execjs 2.7.0
remote:        Installing concurrent-ruby 1.0.5
remote:        Installing thor 0.19.4
remote:        Installing multi_json 1.12.1
remote:        Using bundler 1.13.7
remote:        Installing pg 0.20.0 with native extensions
remote:        Installing rails_serve_static_assets 0.0.5
remote:        Installing rails_stdout_logging 0.0.5
remote:        Installing rdoc 4.3.0
remote:        Installing sass 3.4.23
remote:        Installing tilt 2.0.7
remote:        Installing turbolinks-source 5.0.3
remote:        Installing tzinfo 1.2.3
remote:        Installing nokogiri 1.7.1 with native extensions
remote:        Installing rack-test 0.6.3
remote:        Installing mime-types 3.1
remote:        Installing uglifier 3.2.0
remote:        Installing coffee-script 2.4.1
remote:        Installing sprockets 3.7.1
remote:        Installing rails_12factor 0.0.3
remote:        Installing turbolinks 5.0.1
remote:        Installing mail 2.6.5
remote:        Installing loofah 2.0.3
remote:        Installing rails-html-sanitizer 1.0.3
remote:        Installing sdoc 0.4.2
remote:        Installing activesupport 4.2.0
remote:        Installing globalid 0.4.0
remote:        Installing rails-deprecated_sanitizer 1.0.3
remote:        Installing activemodel 4.2.0
remote:        Installing jbuilder 2.6.3
remote:        Installing activejob 4.2.0
remote:        Installing rails-dom-testing 1.0.8
remote:        Installing actionview 4.2.0
remote:        Installing activerecord 4.2.0
remote:        Installing actionpack 4.2.0
remote:        Installing actionmailer 4.2.0
remote:        Installing sprockets-rails 3.2.0
remote:        Installing railties 4.2.0
remote:        Installing coffee-rails 4.1.1
remote:        Installing sass-rails 5.0.6
remote:        Installing jquery-rails 4.3.1
remote:        Installing rails 4.2.0
remote:        Bundle complete! 15 Gemfile dependencies, 54 gems now installed.
remote:        Gems in the groups development and test were not installed.
remote:        Bundled gems are installed into ./vendor/bundle.
remote:        Bundle completed (21.84s)
remote:        Cleaning up the bundler cache.
remote:        Warning: the running version of Bundler (1.13.7) is older than the version that created the lockfile (1.14.6). We suggest you upgrade to the latest version of Bundler by running gem install bundler.
**remote: -----> Installing node-v6.10.0-linux-x64
remote: -----> Detecting rake tasks
remote: -----> Preparing app for Rails asset pipeline
remote:        Running: rake assets:precompile
remote:        rake aborted!
remote:        NameError: uninitialized constant Devise
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/config/initializers/devise.rb:3:in <top (required)>'** remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/engine.rb:652:in block in load_config_initializer'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.0/lib/active_support/notifications.rb:166:in instrument' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/engine.rb:651:in load_config_initializer'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/engine.rb:616:in block (2 levels) in <class:Engine>' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/engine.rb:615:in each'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/engine.rb:615:in block in <class:Engine>' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/initializable.rb:30:in instance_exec'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/initializable.rb:30:in run' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/initializable.rb:55:in block in run_initializers'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/initializable.rb:44:in each' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/initializable.rb:44:in tsort_each_child'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/initializable.rb:54:in run_initializers' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/application.rb:352:in initialize!'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/config/environment.rb:5:in <top (required)>' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/application.rb:328:in require'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/application.rb:328:in require_environment!' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/railties-4.2.0/lib/rails/application.rb:443:in block in run_tasks_blocks'
remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/sprockets-rails-3.2.0/lib/sprockets/rails/task.rb:62:in block (2 levels) in define' remote:        /tmp/build_36d752abc082d93e1fd0e065635a5768/vendor/bundle/ruby/2.3.0/gems/rake-12.0.0/exe/rake:27:in <top (required)>'
remote:        Tasks: TOP => environment
remote:        (See full trace by running task with --trace)
remote:  !
remote:  !     Precompiling assets failed.
remote:  !
remote:  !     Push rejected, failed to compile Ruby app.
remote:
remote:  !     Push failed
remote: Verifying deploy...
remote:
remote: !	Push rejected to floating-mesa-85213.
remote:
To https://git.heroku.com/floating-mesa-85213.git
! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'https://git.heroku.com/floating-mesa-85213.git'

Thanks for opening this issue.
Could you please provide more information by using the ISSUE_TEMPLATE?
I'm marking this issue as closed for the time being. If you could provide more information through the ISSUE_TEMPLATE, I'd gladly reopen it.


Not working open with chrome on windows Sublime Text 3

Hello,
I have sublime Text 3 and I can't edit the Browser.sublime-settings file. I set chrome as my default browser, but as I couldn't change "%Local AppData%" to my actual route "C:\Program Files (x86)" It isn't working.
How can I go through this?
Thanks in advance.
PS: It's working with the other browsers, and I'm using windows 8.1.

This is a really old post but for anyone trying to get this working, this is how I got around it.  If u want to use chrome then you set up your user preferences file as mentioned above (changing the default path to chrome to be something like C:/Program Files (x86)/Google/Chrome/Application/chrome.exe and the selectedBrowser at the bottom to 'chrome').
In sublime under 'Preferences->PackageSettings->View in Browser->Settings-Default', change the bottom section from "browser": "firefox" to "browser": "chrome64"

Gwad i tried so many things and almost pulled out all the hair on my head but Yay! finally this worked for me... thanks mickeo4.

won't let me edit "Settings-Default", if I browser to the folder where it claims to be stored it's not there / right click > open containing folder takes to c:/.
is this a windows10 thing?

Dangit.. Still not working for me.
I tried everything detailed here.
Made the following 2 files in the Packages\User folder:
Made

@captaininbox Thanks, that solution worked for me :)
{
"browser": "chrome64"
}
in "View In Browser.sublime-settings"-file.

Ctrl + `
I found the following error:

File "C:\Program Files (x86)\sublime\Data\Packages\View In Browser\ViewInBrowserCommand.py", line 137, in getWindowsUserShellFolders
   return_dict[name] = value.encode("ascii")
UnicodeEncodeError: 'ascii' codec can't encode character '\xe1' in position 26: ordinal not in range(128)

I opened the file ViewInBrowserCommand.py line 137, I changed:
value.encode("ascii") for value.encode("utf-8")

It worked!

Using MAC
and I changed the default to firefox, safari, chrome, tried them all nothing happens, it doesn't open a browser any suggestions?


Ignore intermittent tests

Ignore tests which do not reliably pass. Since everyone just restarts until they pass, they don't add much benefit and they waste resources and people's time.
Long-term it would be good to fix these tests, but until somebody does that I think it is better not to run them.

Ironically, there is a test error in one of the Appveyor builds, but it looks like an infra failure rather than anything wrong with this PR.

PTAL @siddontang @BusyJay @overvenus @Hoverbear Does anyone not approve of this approach to the unstable tests?

I worked at some old clients that had this approach and the moment you remove the pain, embarrassment, and reminders, everyone forgets about it and they never get fixed.
So, I'm generally of the opinion that the tests should get fixed (and be stable) or removed completely (because they are superseded with others).

the moment you remove the pain, embarrassment, and reminders, everyone forgets about it and they never get fixed.

I don't want to sound sarcastic, but they are not getting fixed right now, and they are a big dent in development velocity. It seems like wishful thinking to suppose they will get fixed by leaving things unchanged.
The downside of the current situation is that we are so used to re-running tests that tests could change from passing to intermittent without people noticing. If the default is that all tests pass, then that doesn't happen.
I hope that by keeping track of the number of intermittent failures and keeping that number highlighted (e.g., by making a tracking issue and pinning it, or using a dashboard), we can encourage the tests to get fixed, even without the pain.

@Hoverbear Notice that these tests can be seen as completely removed already, but they're only removed for some certain features. Does that sound reasonable enough?

This is too bad that disable the test cases instead of fixing them. It's called 掩耳盗铃 in Chinese that cover one's ears when stealing a bell.
@ice1000 You should not merge a PR when there is only one approval. Ask someone to review the code instead.

@BusyJay I recommend requiring two approvals for merging. There's only on required for this repo atm so I assumed that it's fine to merge with 1 approval.
Btw there are issues for the disabled tests: #305 #306 so what we're doing is treating the disabling of the tests as a "bug" and postpone the fix.
I'm fine with regression, because they're disabled for not blocking some PRs and the blocking PRs are mostly merged now.

I think all repos except some trivial documentation changes have always required 2 approvals in all PingCAP and TiKV repos.
When there are folks who are still actively against the merging of the PR it's probably good form to wait for a second approval.


Node switcher - Checking url sometimes gets stuck on SSL

This got picked up by the UI tests and should be reproducible manually.

Open Block explorer connected to Testnet
Open node switcher and enter url for devnet (as seen in the screenshot)
Click connect
Stuck on Checking SSL

i believe this has been fixed in this PR: https://github.com/vegaprotocol/frontend-monorepo/pull/2357/files#diff-7034b8ddabfe4af427b5bb0d1e8279a37a7bf881d52730c93798386257d70144R75-R80


[BUG] DynamicData throws ambiguous overload exception from the dynamic binder

Library name and version
Azure.Core 1.33.0
Describe the bug
DynamicData throws ambiguous overload exception from the dynamic binder when dynamic json string property passed to Console.WriteLine
Expected behavior
Prints "Hello" to the console
Actual behavior
Exception thrown and prints:
Microsoft.CSharp.RuntimeBinder.RuntimeBinderException: The call is ambiguous between the following methods or properties: 'System.Console.WriteLine(string, params object[])' and 'System.Console.WriteLine(bool)'
at CallSite.Target(Closure, CallSite, Type, Object)
at System.Dynamic.UpdateDelegates.UpdateAndExecuteVoid2[T0,T1](CallSite site, T0 arg0, T1 arg1)
at Program.$(String[] args) in C:\Users\kcwalina\Desktop\ConsoleApp1\ConsoleApp1\Program.cs:line 6
C:\Users\kcwalina\Desktop\ConsoleApp1\ConsoleApp1\bin\Debug\net7.0\ConsoleApp1.exe (process 25144) exited with code 0.
Reproduction Steps
Create console project (I did .NET 7)
Add the following packages:
    <PackageReference Include="Azure.Core" Version="1.33.0" />
    <PackageReference Include="System.Memory.Data" Version="7.0.0" />

Change program.cs to:
using Azure;

try
{
    var json = BinaryData.FromObjectAsJson(new { Text = "Hello!" }).ToDynamicFromJson();
    Console.WriteLine(json.Text);
}
catch (Exception e)
{
    Console.WriteLine(e.ToString());
}

Environment
No response

This can be resolved by releasing the Experimental package.   When we do the Core release this month, let's please include Experimental.
//cc: @christothes, @JoshLove-msft

Resolving; Experimental was released yesterday.


[Rails][React] Add the ability to "pin" a story so it shows up first on the StoryList

The Haudenosaunee community has requested that we add a feature to "pin" a story, so that it shows up first on the StoryList. Let's make it happen!
Let's go about this the following way:

Create a new boolean in the Story model called storyPinned.
In the CMS, for a logged in user with editor or admin permissions, add the ability to "pin" a story by showing a grayed out icon-pushpin from font-awesome to the right of a story title in the story dashboard edit view. Upon being clicked, the pushpin will turn to black, and the story will be set to storyPinned = true; any other story that was previously set to storyPinned = true will then be storyPinned = false.
Once a story is "pinned", the story will have an icon-pushpin from font-awesome in the top right of a Story card upon hover over the card.

Upon hovering over the icon-pushpin, the icon should be highlighted with a box-shadow in the same way that the card is highlighted upon hover.
Users with member permissions are able to see that a story is pinned, but can't themselves pin or unpin any stories. (And they do not see any hover box-shadow behavior.)
Once clicked, the Story card should move to the top of the list (top left in the CMS).
Additionally, on the application front end (/home/), the story should show first in the StoryList in the sidebar, regardless of how the story is sorted, and the icon-pushpin should show up in the top right here, too.

However, if either on the CMS side or the application front end, the stories are filtered in such a way that the pinned story does not meet the criteria, it should disappear from the list.
In the CMS, once a story has been pinned, a user with editor or admin permissions can unpin the story by clicking on the icon-pushpin in the top right, which removes it from being pinned and returns it to its normal order in the list of stories.
Default state is that no stories are pinned.

Bonus if the user can somehow see the "pinned" story move to the top of the list in the CMS (e.g. by briefly fading out from current position, and fading in to top level) -- and vice versa if unpinned -- but not necessary for completion.

Hello, I would like to work in this issue

Thanks @griseduardo - I assigned you

Hello, I opened a pr related to this issue: https://github.com/Terrastories/terrastories/pull/975


Concurrent validation of the same schema

Describe the bug
We have individual tests which check two separate APIs return a result that adheres to the same schema. When these tests are run in parallel, the ValidateSchema() method throws an exception. The exception is either of the below:
System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection. (Parameter 'index')
   at System.Collections.Generic.List`1.RemoveAt(Int32 index)
   at System.Collections.Generic.List`1.Remove(T item)
   at Manatee.Json.Schema.RecursiveRefKeyword.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.AdditionalPropertiesKeyword.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.PropertiesKeyword.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.VocabularyKeyword.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.ValidateSchema(JsonSchemaOptions options)
   at ManateeConcurrencyTests.UnitTest1.<>c.<Test1>b__0_0() in C:\\Users\\Jack.ohara\\source\\repos\\ManateeConcurrencyTests\\ManateeConcurrencyTests\\UnitTest1.cs:line 24\r\n   at ManateeConcurrencyTests.UnitTest1.<>c__DisplayClass0_0.<Test1>b__1(Action action) in C:\\Users\\Jack.ohara\\source\\repos\\ManateeConcurrencyTests\\ManateeConcurrencyTests\\UnitTest1.cs:line 38

System.InvalidOperationException: Collection was modified; enumeration operation may not execute.
   at System.Collections.Generic.List`1.Enumerator.MoveNextRare()
   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
   at Manatee.Json.Schema.RecursiveRefKeyword.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.AdditionalPropertiesKeyword.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.PropertiesKeyword.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.VocabularyKeyword.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.Validate(SchemaValidationContext context)
   at Manatee.Json.Schema.JsonSchema.ValidateSchema(JsonSchemaOptions options)
   at ManateeConcurrencyTests.UnitTest1.<>c.<Test1>b__0_0() in C:\\Users\\Jack.ohara\\source\\repos\\ManateeConcurrencyTests\\ManateeConcurrencyTests\\UnitTest1.cs:line 24\r\n   at ManateeConcurrencyTests.UnitTest1.<>c__DisplayClass0_0.<Test1>b__1(Action action) in C:\\Users\\Jack.ohara\\source\\repos\\ManateeConcurrencyTests\\ManateeConcurrencyTests\\UnitTest1.cs:line 38

To Reproduce
I have written a unit test that reproduces the error:
var validateSchemaAction = new Action(()
{
    var serializer = new JsonSerializer();
    var schemaText = File.ReadAllText($"{AppDomain.CurrentDomain.BaseDirectory}my-schema.json");
    var schemaJson = JsonValue.Parse(schemaText);
    var schema = serializer.Deserialize<JsonSchema>(schemaJson);

    schema.ValidateSchema();
});

var exceptions = new List<Exception>();

Parallel.ForEach(
    new[]
    {
        validateSchemaAction, validateSchemaAction, validateSchemaAction, validateSchemaAction,
        validateSchemaAction
    }, action =>
    {
        try
        {
            action();
        }
        catch (Exception ex)
        {
            exceptions.Add(ex);
        }
    });

Assert.Empty(exceptions);

The schema I was using for this test is:
{
  "description": "API Error",
  "type": "object",
  "required": [ "code", "message" ],
  "properties": {
    "code": { "type": "string" },
    "message": { "type": "string" },
    "correlation_id": { "type": "string" },
    "details": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "property": { "type": "string" },
          "code": { "type": "string" },
          "message": { "type": "string" }
        }
      }
    },
    "links": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "href": { "type": "string" },
          "rel": { "type": "string" },
          "reference": { "type": "string" },
          "type": { "type": "string" }
        }
      }
    }
  }
}

Expected behavior
The schema should be validated successfully on all threads.
Desktop (please complete the following information):

OS: Windows 10 pro version 10.0.18363 Build 18363
.Net core 3.1
Manatee version 13.0.1

Thanks for the report and the sample test. I'll add it to the suite so I can fix the problem.

I find it odd that there's no $recursiveRef in your schema, yet this is the keyword that's throwing.  That leads me to believe it's happening in the meta-schema validation, but that's not pay off the stack trace.

It looks like it is from the MetaSchema Validation. The part of the trace in VocabularyKeyword is line 127. I guess the issue is that the meta schemas are shared and are coming from a static ConcurrentDictionary.

Hm..., yeah it's here: https://github.com/gregsdennis/Manatee.Json/blob/master/Manatee.Json/Schema/Keywords/RecursiveRefKeyword.cs#L72
So this keyword instance is on the metaschema, which is attempting to validate concurrently.  This particular array is used to detect recursive loops in the schema by storing the instance locations that it's already evaluated.
Even if it didn't throw an exception, it's still not thread-safe because it could store a location from evaluating that same location on another instance on another thread.
I have a few solutions in mind.  I'll play with those and see what comes of them.

@gregsdennis thanks for the fix! 👍

Just came across this bug while validating the schema and validating objects in another test case.
Went to file an issue but was delighted to find it already fixed 👍. Thanks!

FWIW -- I've come across similar issues in other JSON Schema evaluators, and have come to the conclusion that storing any sort of state information right in the schema structure is a Bad Idea with the potential to create all kinds of hidden bugs, and so have switched to storing state info in an out-of-band structure that only the current evaluator instance has access to in its own thread.


timescaledb-single: How to restore from specific backup

The documentation specifies how to restore from the latest backup using the backup.pgBackRest value, but it does not specify to restore from a specific backup that is not the latest. Is doing so supported by this chart?

use pgbackrest info to get the Backup informations.
you can use this command to restore to a specified backup:
pgbackrest --stanza=poddb --set=20240108-021507F restore


[Feature Request] Add meta fields to routes

I want to add meta fields to the routes for permissions and authentification.
What is the recommended way to do that?

Hey @Septias, great question.
This isn't currently supported, but I plan to add support soon via a custom Vue SFC block where you'd be able to set route config.
For example, it may look something like:
<page>
{
  "meta": {
    "requiresAuth": true
  }
}
</page>

Let me know what you think about this idea!

And how is this supposed to work with components written in .jsx/.tsx files?

Hi, whilst I'm working on adding that custom SFC block, I thought that it was worth noting that as of release v0.5 you can now supply an extendRoute function in your config that allows you to modify your routes after they have been resolved, so it is possible to add route meta via this method as well 😀

(Unrelated: I've just checked out your plugin and seems nice.)
Regarding the extendRoute function, to me it seems the place for it is not in vite.config. I think a better option would be implement a method like generateRoutes() that takes a config object as argument and returns the route array. This way you don't bloat the vite.config with stuff that should be elsewhere.

(Unrelated: I've just checked out your plugin and seems nice.)
Regarding the extendRoute function, to me it seems the place for it is not in vite.config. I think a better option would be implement a method like generateRoutes() that takes a config object as argument and returns the route array. This way you don't bloat the vite.config with stuff that should be elsewhere.

Funny you should say that, I was considering something similar recently. If I'm understanding your suggestion correctly, we could alter the virtual file returned by the plugin so that instead of directly exporting an array of routes, it instead exports a function which can be called to generate the routes? Something like:
import { generateRoutes } from 'voie-pages';

const routes = generateRoutes();

We could then even go a step further and allow the user to pass in some kind of function to generate parts of the - if not the entire - virtual file, which would allow for generating routes however the user wants. This, in combination with allowing the user to change the module id that voie resolves, could potentially allow for generating routes config for any router -- not just Vue Router.

Funny you should say that, I was considering something similar recently. If I'm understanding your suggestion correctly, we could alter the virtual file returned by the plugin so that instead of directly exporting an array of routes, it instead exports a function which can be called to generate the routes? Something like:
import { generateRoutes } from 'voie-pages';

const routes = generateRoutes();

We could then even go a step further and allow the user to pass in some kind of function to generate parts of the - if not the entire - virtual file, which would allow for generating routes however the user wants. This, in combination with allowing the user to change the module id that voie resolves, could potentially allow for generating routes config for any router -- not just Vue Router.

Yes, that's exactly what I'm talking about. And while thinking about it, this could be expanded further by giving users the ability to use custom properties in file names.
Take this file name as example: pages/users/[id]{user;defined;string}.vue.
At a first look this could get bloated, but having a way of adding some custom metadata to a file would give some nice freedom of movement. What the user does with that data is up to them (layout name, user page, admin page, etc).

Yes, that's exactly what I'm talking about. And while thinking about it, this could be expanded further by giving users the ability to use custom properties in file names.
Take this file name as example: pages/users/[id]{user;defined;string}.vue.
At a first look this could get bloated, but having a way of adding some custom metadata to a file would give some nice freedom of movement. What the user does with that data is up to them (layout name, user page, admin page, etc).

I'm not sure what the relationship is between this and vite-plugin-pages; does this project continue or is it superseded by vite-plugin-pages?
I submitted a PR that was (politely) declined because it wasn't exactly what the owner wanted.  As I need this functionality, and I don't particularly want to maintain a fork, do you have any interest in a PR, if this project continues?
https://github.com/JohnCampionJr/vite-plugin-pages/tree/sfc-meta

Now I'm using https://github.com/ktsn/vue-route-generator#route-custom-block
which can handle this at top of a .vue file:
<route>
{
  "meta": {
    "auth": false
  }
}
</route>
<template>
    <div class="d-flex align-items-center min-vh-100">

Could this also work in voie?


feat: pretty colors, ascii, and helpful intro to the CLI

This PR adds some ASCII art and other helpful color branding to the CLI to help the user know what is going on.
Current state of the world
For context, here is the current version:

New version in this PR

For the ASCII cube, it feels like we can improve on this, but maybe it's better than no cube.


one tiny problem in test_NTURain_synthetic.py

the 25th should be：base_data_path = Path('./testsets/synthetic_NTURain')
Your work is excellent!

Thanks. I had fixed such small typo. @Ced3-han


[Prototype] Tables batch

Initial Prototype for Tables Batch
API Level changes

Adds a createBatch method which returns a TablesBatch object which is used to hold the operations to be performed in the batch.

The TablesBatch object exposes the following methods:

createEntities - Adds an insert operation to the Batch for each of the entities in the array. Does not perform a service call
createEntity - Adds a single insert operation to the Batch. Does not perform a service call
deleteEntity - Adds a delete operation to the Batch. Does not perform a service call
updateEntity - Adds an update operation to the batch. Does not perform a service call
submitBatch - Submits the operations in the batch. Does Perform a service call

Implementation details
Crafting the Batch request

Swagger doesn't define the batch operation so it needs to be hand-crafted
Batch request sends all the operations in the body, each operation is bounded by changeset_<GUID> and the whole Batch is bounded by batch_<GUID>.

Each operation is described with the HTTP request
When building the batch, I create a new internal client with a Pipeline that intercepts the operations and instead of sending them to the service it appends them to the current batch body

Sample Batch
POST https://myaccount.table.core.windows.net/$batch HTTP/1.1
x-ms-version: 2013-08-15
Accept-Charset: UTF-8
DataServiceVersion: 3.0;
MaxDataServiceVersion: 3.0;NetFx
Content-Type: multipart/mixed; boundary=batch_a1e9d677-b28b-435e-a89e-87e6a768a431
x-ms-date: Mon, 14 Oct 2013 18:25:49 GMT
Authorization: SharedKey myaccount:50daR38MtfezvbMdKrGJVN+8sjDSn+AaA=
Host: <IP_ADDRESS>:10002
Content-Length: 1323
Connection: Keep-Alive

--batch_a1e9d677-b28b-435e-a89e-87e6a768a431
Content-Type: multipart/mixed; boundary=changeset_8a28b620-b4bb-458c-a177-0959fb14c977

--changeset_8a28b620-b4bb-458c-a177-0959fb14c977
Content-Type: application/http
Content-Transfer-Encoding: binary

POST https://myaccount.table.core.windows.net/Blogs HTTP/1.1
Content-Type: application/json
Accept: application/json;odata=minimalmetadata
Prefer: return-no-content
DataServiceVersion: 3.0;

{"PartitionKey":"Channel_19", "RowKey":"1", "Rating":9, "Text":".NET..."}
--changeset_8a28b620-b4bb-458c-a177-0959fb14c977
Content-Type: application/http
Content-Transfer-Encoding: binary

POST https://myaccount.table.core.windows.net/Blogs HTTP/1.1
Content-Type: application/json
Accept: application/json;odata=minimalmetadata
Prefer: return-no-content
DataServiceVersion: 3.0;

{"PartitionKey":"Channel_17", "RowKey":"2", "Rating":9, "Text":"Azure..."}
--changeset_8a28b620-b4bb-458c-a177-0959fb14c977
Content-Type: application/http
Content-Transfer-Encoding: binary

MERGE https://myaccount.table.core.windows.net/Blogs(PartitionKey='Channel_17', RowKey='3') HTTP/1.1
Content-Type: application/json
Accept: application/json;odata=minimalmetadata
DataServiceVersion: 3.0;

{"PartitionKey":"Channel_19", "RowKey":"3", "Rating":9, "Text":"PDC 2008..."}

--changeset_8a28b620-b4bb-458c-a177-0959fb14c977--
--batch_a1e9d677-b28b-435e-a89e-87e6a768a431

TODO

[ ]  Batch clean up after submitting

@xirzec, @ellismg thanks a lot for your feedback :smile: I have addressed your comments and made this a real PR. When you get a chance can you please take another look?

/azp run js - tables - tests

/azp run js - tables - tests

/azp run js - tables - tests

/azp run js - tables - tests

/azp run js - tables - tests


Interpretation of old-style Apple Partition Map partitions is incorrect

IM:D gives two partition signatures:

The partition signature. This field should contain the value of the pMapSIG constant ($504D). An earlier but still supported version uses the value $5453.

That's all it says about it, implying that both signatures are used for the same structure.
This isn't true. The new constant was introduced with a new partition structure layout in IM:5. IM:4 gives the old structure:
struct APMPartitionIM4 {
	u_int16_t pdSig; //'ST'
	u_int32_t pdStart; //starting block address
	u_int32_t pdSize; //number of blocks
	OSType pdFSID; //file system ID ('TFS1' for Macintosh Plus)
};

I don't know how likely we are to encounter such a partition, but we should interpret it correctly.

(I also kind of wonder whether Apple's current APM implementation recognizes and understands these partition maps.)

Actually it kind of sounds like the old APM works completely differently, and is all packed into the second physical block (following the DDM, which didn't change):
struct APMPartitionMapIM4 {
	u_int16_t pdSig; //'ST'
	struct APMPartitionIM4 partitions[];
};

struct APMPartitionIM4 {
	u_int32_t pdStart;
	u_int32_t pdSize;
	OSType pdFSID;
};

It's the partition map signature followed by one or more partition records (each having a start, size, and FSID), terminated by a partition record with all zeroes:

Since there's no field in the device partition map for specifying the number of partitions, you need to signal the end of the map with a partition whose pdStart, pdSize, and pdFSID fields are set to 0.

IM4 doesn't specify what happens when there are more partitions than will fit in the second block; presumably they didn't anticipate somebody creating more than 42-and-a-half partitions. (Or maybe the IM5 format was the answer to that question.)
It does say:

The system startup procedure … then reads the device partition map from physical block 1 and checks for the proper signature ($5453).

which sort of implies that the partition map is confined entirely to that block—i.e., the maximum number of partitions an IM4-formatted disk can have is 42 (or 41 if the all-zeroes partition is required).
… I suppose I'll have to create an image with 42 partitions in an IM4 partition map and see what System 6 does.


[doc] Fix broken internal documention links

This fixes broken links in the documentation. Broken links were found using  lychee.
cargo install lychee
lychee . -o /tmp/output.md -f markdown --require-https --exclude-all-private --cache --exclude-path sw/vendor/ --exclude-path hw/vendor/ --exclude-path site/ --exclude-path hw/ip_templates

Note: Currently links between books have to be URLs. Lychee can't check for this.
These changes are split over two PRs to make reviews easier. This PR has the large number of fixes to internal links. The second PR, https://github.com/lowRISC/opentitan/pull/17655, fewer more miscellaneous changes.
Fixes: https://github.com/lowRISC/opentitan/issues/17588

What is your opinion of 'lychee' having used it now? It would be great to have something like this in CI to check links when rebuilding the site. Is it worth pursing a lychee-based solution to do this?

What is your opinion of 'lychee' having used it now? It would be great to have something like this in CI to check links when rebuilding the site. Is it worth pursing a lychee-based solution to do this?

Yeah, I like it. It doesn't check anchors, which would be nice to have for links between markdown files, but this could be contributed upstream in https://github.com/lycheeverse/lychee/issues/185 .
We could have a check only for local links in CI and a full checks (including external links) in the nightlies.

What is your opinion of 'lychee' having used it now? It would be great to have something like this in CI to check links when rebuilding the site. Is it worth pursing a lychee-based solution to do this?

Yeah, I like it. It doesn't check anchors, which would be nice to have for links between markdown files, but this could be contributed upstream in lycheeverse/lychee#185 .
We could have a check only for local links in CI and a full checks (including external links) in the nightlies.

In that case we should create a follow-up issue to consider adding CI jobs using lychee. I think it would be really valuable.

One other comment, when you rebase can you seperate it from any new changes? I try to rebase the old branch, comment 'rebased', then force-push the new changes. It's basically impossible to review otherwise with the GitHub UI. Thanks!

One other comment, when you rebase can you seperate it from any new changes? I try to rebase the old branch, comment 'rebased', then force-push the new changes. It's basically impossible to review otherwise with the GitHub UI. Thanks!

Sorry, I don't quite follow. I'll come and ask you offline


Error opening debugger (alpha client)

Is this a bug report or a feature request?
Bug
Version Info

Version of Majestic: 1.0.0.alpha
Version of Jest: 0.20.4
Version of Node: 8.9.0
Operating System: MacOSX Sierra

Reproduction Repo
Tried running this in the bolt repo. When selecting a test file and hitting debug I get this message in my console
(node:78902) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): FetchError: request to http://localhost:9229/json failed, reason: connectECONNREFUSED <IP_ADDRESS>:9229
(node:78902) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
ps stderr: Debugger listening on ws://<IP_ADDRESS>:9229/5733f978-d2d6-416d-ae8e-d5c81de99bf7
For help see https://nodejs.org/en/docs/inspector

When I hit it a second time, I get this message
ps stderr: Starting inspector on <IP_ADDRESS>:9229 failed: address already in use

But it also opens the flag with the link correctly, interestingly.
I don't believe I have any other debuggers open, I'll investigate a bit more later.
Just raising here as an fyi

We should try to find a free port and use it to open the debugger to be safe I guess

Hey Luke,
With the recent rewrite, I decided to remove the debugger to keep the scope manageable. Sorry about that.


Cannot set GitSCMStatusChecksExtension when GitSCMChecksContext uses BuildData

Description
Default checks are published to GitHub with the name Jenkins when no SCM is configured on the job (CpsFlowDefinition). A valid GitSCMChecksContext is created because the build contains a valid hudson.plugins.git.util.BuildData object.
That is awesome, however, it is not currently possible to skip that check or to configure the name.
Steps to reproduce

Create a new pipeline job
Use the following pipeline script
Run the job

#!/usr/bin/groovy

node {
    stage ('checkout') {
        checkout scm: [
            $class: 'GitSCM',
            branches: [[name: "*/master"]],
            extensions: [
                [$class: 'CleanBeforeCheckout'],
                [$class: 'GitSCMStatusChecksExtension', name: 'Custom Name', skip: false]
            ],
            userRemoteConfigs: [[credentialsId: 'your-github-app-credential', url: 'https://github.com/user/repo.git']]
        ]
    }
}

Current behaviour
[...]
Fetching changes from the remote Git repository
[...]
[GitHub Checks] GitHub check (name: Jenkins, status: IN_PROGRESS) has been published.

Expected behaviour
[...]
Fetching changes from the remote Git repository
[...]
[GitHub Checks] GitHub check (name: Custom Name, status: IN_PROGRESS) has been published.

Implementation suggestion
I am not sure I know where to start with this issue. The configuration are retrieved in BuildStatusChecksPublisher. They could try to retrieve some config persisted in the Run object (like BuildData) to know the check property. At the moment, GitSCMStatusChecksExtension is not persisted in the Run.

There is also BuildStatusChecksPublisher.JobScheduledListener.onEnterWaiting, which calls getChecksName with a Job rather than a Run: https://github.com/jenkinsci/checks-api-plugin/blob/4996cf43478acbd1a3043225af2b9d7849c6c174/src/main/java/io/jenkins/plugins/checks/status/BuildStatusChecksPublisher.java#L127-L129
I don't think that will ever be able to get the checks name defined in a pipeline script… but then again, it does not know the SCM settings defined in the pipeline either, so it won't be posting checks with an incorrect name to that SCM.

You are right. onEnterWaiting does not matter much in this scenario because the SCM is not present on the job so it won't publish anything. However, after the first checkout step, it will start to publish in onCheckout and onCompleted because checkout will add BuildData. But from there, we have access to the run object, so we could, if present, use information in the Run when scm is not defined.

What should happen if the pipeline runs multiple checkout steps, with a GitSCMStatusChecksExtension in each? Should it publish IN_PROGRESS to each repository after the corresponding checkout, and then COMPLETED to every repository when the run completes?

I think these can be 2 different problems. If the GitSCMChecksContext uses the first build data only, then it should respect the associated GitSCMStatusChecksExtension configuration of this build data. If it has a mechanism to loop through all buildData (from different checkout steps), then it should respect their own configuration and publish the completed check for all of them.
I think the first step would be to be able to get the GitSCMStatusChecksExtension for a specific build data first.
When that is working, sending a check for multiple checkout step could be added. I can easily imagine a use case where there are 2 checkouts, but only the second one is in the right repo and should have the check. The user would need to specify in the first checkout to skip the check.


Executor role implementation.

Proposed changes
This pr contains the conversion of Editor role to a new role Executor in Litmus.
The new Executor role can perform following tasks.

ReRunChaosExperiment
StopChaosExperiment

and all the Get, List tasks.
Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[x] New feature (non-breaking change which adds functionality)
[ ] Bugfix (non-breaking change which fixes an issue)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Hello, all.
I believe it is a little late for this question, but I would like to understand what was the motivation for this change.
In our use case, we have several teams that are using litmus and all the projects are owned by the admin (since their creation is via IaC) and the members of each project (some of them has more than 30 members) are responsible for creating/updating their own experiments.
If I understood correctly, with this change, only the onwer can create or modify the experiments. With that, our operation became impossible to handle. So if somebody can help me to understand better what was the rational behind this change, it could be awesome.
Thank you in advance

Hello, all. I believe it is a little late for this question, but I would like to understand what was the motivation for this change. In our use case, we have several teams that are using litmus and all the projects are owned by the admin (since their creation is via IaC) and the members of each project (some of them has more than 30 members) are responsible for creating/updating their own experiments. If I understood correctly, with this change, only the onwer can create or modify the experiments. With that, our operation became impossible to handle. So if somebody can help me to understand better what was the rational behind this change, it would be awesome. Thank you in advance

Hey @vitor-campos thanks for the feedback, @Saranya-jena would be able to answer this correctly. Also we most probably would be having the multiple owner feature in the next release. So I think the issue you are facing now would be solved by that.

Hello, @aryan-bhokare. Thank you for the answer. I have some points to add on top of what you said:

Since it's a breaking change, it shouldn't be applied to a minor version making it incompatible with all the 3.x versions. In this case, if I would like to upgrade my current version (3.6.0) to it, it's gonna break.
I need to upgrade my litmus-agent to the version 3.9.0 because of this fix (https://github.com/litmuschaos/litmus-helm/pull/389) which bug is affecting currently our operation.
I understand the motivation of having an extra role for Executor, but why replace the Editor one? To me, doesn't make any sense

Hi @vitor-campos ,
In the litmus community, we predominantly see a tiered usage of the platform - where an admin/sre-owner persona installs the platform, connects the cluster/namespace targets and invites a set of app developers to run the experiments as desired within a shared environment.
While, in some cases, the developers are given a free hand to execute the experiments as desired, most chaos admins/cluster owners have a requirement for experiments to be fully vetted offline (in the git repos/custom hubs) before they are executed in the project - i.e., have the right folks approve the experiment, the intended targets and its inputs. Also, they would like to prevent any tampering with the experiment spec by developers - in order to
(a) not cause an unintended increase in blast radius
and (b) prevent malicious users from being able to perform disruptive actions. This holds true for both faults as well as probes (specifically, command probes which are highly flexible).
This needs the creation of an executor persona - who is only able to execute the experiment and not perform any other experiment CRUD ops.
Litmus, until the last release supported owners and editors as the role that could run experiments -- and both are highly privileged in terms of the actions they can carry out within the platform. To remediate this situation, we have downgraded the editor to a pure executor and put the ones on the owner to map people with the right role - A co-owner who has all administrative permissions OR a pure executor who can only run approved faults.
The current release introduces the executor and a patch end of July introduces the ability to add co-owners on the project


update donation address in swap tab to new main donation address

since the donation setup changed a bit and we got a new donation .tez address, could we quickly change that in the swap tab alt text?

the new address is:
teiaescrow.tez (tz1Q7fCeswrECCZthfzx2joqkoTdyin8DDg8)
would be cool to bring that in line, thanks!

mel this was another issue, not the added addresses in the collab contract suggested beneficiaries

I don't understand?
https://github.com/teia-community/teia-ui/pull/90/files


Haiku L Series , connects and tiles show, but does not control anything

Fan: Haiku L Series
Firmware: 3.1.0
I am having an issue in which the plugin connects to the Fan and shows all the necessary tiles/accessories in homekit. There are no error messages on Homebridge.
The fan will not do anything when I use the tiles in homebridge or in homekit. It seems to be communicating with the fan since all the correct accessories populate, but it just does not control anything. I just tried clearing the accessory cache and restarted, still nothing. Clicking the tiles does not result in controlling the fan.
Below is the initialization log:
[9/13/2022, 3:55:55 PM] [homebridge-i6-bigassfans] Launched child bridge with PID 3148 [9/13/2022, 3:55:55 PM] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6' [9/13/2022, 3:55:55 PM] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.1 child bridge successfully [9/13/2022, 3:55:56 PM] Loaded 1 cached accessories from cachedAccessories.0E397D7A7D42. [9/13/2022, 3:55:56 PM] [homebridge-i6-bigassfans] Loading accessory from cache: Haiku-Fam [9/13/2022, 3:55:56 PM] [homebridge-i6-bigassfans] Init - initializing devices [9/13/2022, 3:55:56 PM] [homebridge-i6-bigassfans] Restoring existing accessory from cache: Haiku-Fam [9/13/2022, 3:55:56 PM] Homebridge v1.4.0 (HAP v0.10.0) (homebridge-i6-bigassfans) is running on port 56706. [9/13/2022, 3:55:56 PM] [homebridge-i6-bigassfans] Haiku-Fam - current relative humidity out of range: 1000, assuming no humidity sensor for model "Haiku Switch" [9/13/2022, 3:55:56 PM] [homebridge-i6-bigassfans] Haiku-Fam - light detected

Hello.  Can you add this to your fan's configuration and install the latest beta -<EMAIL_ADDRESS>"debugLevels": [
  ["light", 1],
  ["redflags", 1],
  [“network”, 11],
  ["characteristics", 1]
]

Then restart homebridge with debugging turned on (e.g., homebridge -D), give it 1/2 a minute to settle down, then turn your light on and off with the Big Ass Fans app, then try to do the same thing from the Home app and post or mail me<EMAIL_ADDRESS>the log output that comes for the plugin.
Thanks.

Thank you for the reply. I get the log output below, but nothing additional is added when I use the Big Ass Fan App or try to use the home app.
Where should I add the debug levels in the JSON? I just want to make sure I have it in the correct spot.
[9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Launched child bridge with PID 19160 [9/14/2022, 10:41:48 AM] Registering platform 'homebridge-i6-bigassfans.BigAssFans-i6' [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Loaded homebridge-i6-bigassfans v0.5.2-beta2 child bridge successfully [9/14/2022, 10:41:48 AM] Loaded 1 cached accessories from cachedAccessories.0E397D7A7D42. [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Finished initializing platform [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Loading accessory from cache: Haiku-Fam [9/14/2022, 10:41:48 AM] Publishing bridge accessory (name: homebridge-i6-bigassfans, publishInfo: { username: '0E:39:7D:7A:7D:42',   port: 56706,   pincode: '***-**-***',   category: 2,   bind: undefined,   mdns: undefined,   addIdentifyingMaterial: true,   advertiser: undefined }). [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Executed didFinishLaunching callback [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Init - initializing devices [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Restoring existing accessory from cache: Haiku-Fam [9/14/2022, 10:41:48 AM] Homebridge v1.4.0 (HAP v0.10.0) (homebridge-i6-bigassfans) is running on port 56706. [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] dblog progress(0/0) Haiku-Fam - product type: Haiku Switch (0x48, 0x61, 0x69, 0x6b, 0x75, 0x20, 0x53, 0x77, 0x69, 0x74, 0x63, 0x68) [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] dblog progress(0/0) Haiku-Fam - firmware: 3.1.0 [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Haiku-Fam - current relative humidity out of range: 1000, assuming no humidity sensor for model "Haiku Switch" [9/14/2022, 10:41:48 AM] [homebridge-i6-bigassfans] Haiku-Fam - light detected

@bozzy01  add them in within one of the fan sections you have configured. Like this example below.
"fans":[                   {                     "name": "Big Fan i6",                     "mac": "20:F8:5E:00:00:00",                     "ip": "BigFani6.local",                     "showFanAutoSwitch": true,                     "showLightAutoSwitch": true,                     "showWhooshSwitch": false,                      "debugLevels": [                                ["light", 1],                                ["redflags", 1],                                [“network”, 11],                                ["characteristics", 1]                        ]                   },

@pponce , thank you that worked.
So, oddly enough after that the control seems to be working now, but for some reason when controlling from Apple Home I do not hear a beep when I turn the fan on.
Log is below:


Console model errorSumary()

\yii\helpers\Html::errorSummary() does a good job of parsing error data and rendering it for Html rendering,
however there is no similar functionality for console applications, i.e. formatted error Output from model errors in  console application , It would useful addition to the Console helper tools

can you explain in more detail how you use model validation on console?

Typically I write bulk import /file processing operations in my console actions.
It is useful to do this using console application as for large uploads / bulk imports  it is better to do the processing( when it make take  few minutes or more etc) asynchronously rather than while the request is made .

In this scenario Initial request on the web is made , the object is queued for processing and then console action does the actually processing ( via scheduled cron / long running worker process listening to a queue etc ).

Validations are performed when save() ic called as is usual.

All the errors are piped to file and/or sent as an email to the uploading user. Here un-formatted or text formatted output is better than only HTML formatted output.

Another slightly different use case is throwing validation errors in REST actions, HTML validated output just comes in the way of parsing the errors. Array output is required ( Although models->getErrors() is basically an array an custom function has to be written anyway to parse a group of models )
Currently I use couple of hack helpers functions extending HTML::errorSummary to handle this, However it would be nice to have other errorSummary formats like for un-formatted text, formatted for stderr, and  json output etc


[Bug]: No way to handle type discrimination with react/destructuring-assignment

Is there an existing issue for this?

[X] I have searched the existing issues and my issue is unique
[X] My issue appears in the command-line and not only in the text editor

Description Overview
Description
When you accept a props type that is a union of two interfaces which can be discriminated, it is not possible to destructure the items which do not exist on one or more of the interfaces. However, react/destructuring-assignment does not recognize that, and so it fires when attempting to access the value from the props.
Example w/ error
interface P1 {
	a: true;
	b: number;
}

interface P2 {
	a: false;
}

type P = P1 | P2;

export const MyComponent: React.VFC
 = (props) => {
	const { a } = props;

	const b = a ? props.b : undefined;

	return {b};
};

This can't really be worked around if you need b to exist at the top level of the component (e.g., as an input or dependency for a use* call). I think the only real way to work around this is something like:
let b: P1["b"] | undefined;

if (a) {
	const { b: bTemp } = props;
	b = bTemp;
}

But this gets super, super cumbersome when you have more than one prop to handle this way.
Expected Behavior
Ideally: The rule should be able to detect if the property does not exist on the union-ed props type, and in such a case should not fire.
Alternatively: There should be an optional setting to have this rule ignore ternary assignments for this specific use case.
eslint-plugin-react version
v7.32.2
eslint version
v8.44.0
node version
v16.20.1

It’s quite possible; if typescript doesn’t let you do it, typescript is broken.

@ljharb I'm not sure what you mean. This is by design in TypeScript. In the example above, you cannot destructure b out of props because it is not guaranteed to exist on the type unless a === true. At destructure time, TS cannot tell if the object is P1 or P2, you cannot pull out a field that is exclusive to P1.

If necessary, I can find where this is documented in TS, but I can guarantee you it is by design.

It’s JavaScript - every property is always guaranteed to yield undefined when absent. I understand how TS is designed, but the correct thing to do here is unconditionally destructure both properties. TS’s build-time fiction doesn’t change that,.

@ljharb So is the implication here that the linting supported by this library is not intended to be compatible with TypeScript?

Of course it is; but if you happen to have selected a type that typescript doesn't support combined with react patterns, there’s not much we can do about that.
The runtime code should do what the rule suggests, full stop. If TS is telling you to do something subpar, then either TS, or your types, are subpar.
You can always use // @ts-ignore.

This looks to be a difference in opinion where my take is that TypeScript is doing the right thing and protecting the devs/runtime from potentially ending up with a type or value that is unexpected, while—correct me if I'm wrong—your take is that the linter's strict enforcement is favored over the type-checking provided by TypeScript.
The issue I see here is that when working in a code base with other people of differing experience levels, disabling linting rules (which is the approach I've been using to work around this bug/feature ask) might make code less consistent or readable, but disabling TS itself opens the possibility of other developers making mistakes that cause functional runtime issues.
I guess if that's not a concern, then this issue isn't going to see any traction. However, given how many existing ESLint rules—even ones in this repository—have customization that leave it up to the maintainers of a given code base to decide how they want their code to be linted (i.e., tweak the behavior of "what the rule suggests"), I'm not really seeing the reason that such a customization could not exist for this rule.

If a is absent, undefined is expected, so yes, I think that TS isn't doing the right thing here.
There are many customizations offered, but infinitely more that are not offered intentionally - just because someone wants something doesn't make it "not harmful" to have that thing, and lots of people want lots of things that would end up being harmful.
As to this specific request, if you need b at the top level of the component, then b isn't actually a property that can be absent from props, so your types are wrong. The type for the component shouldn't be P1 | P2, it should be P1 | (P2 & { b?: never }) or something like that (i'd have to play with it in a TS context to be sure).
This problem is annoying also because TypeScript fails to differentiate between a component's external props types, and internal props types - externally, P1 | P2 seems perfectly correct, but internally that's not the correct type for your implementation since you need b in every code branch.

For this specific case, this comment actually helped me realize something:

... if you need b at the top level of the component, then b isn't actually a property that can be absent from props, so your types are wrong.

It's definitely the case that b is required at the top level—but only in half of the use cases of the component, which, thinking about it, is probably a React anti-pattern.
I'm thinking now that it's probably better to be explicit about this, where it's actually two separate components such that one takes props: P1 and one takes props: P2—and still allow for logic common to both components to be exercised on props: P. (Example at the bottom of my comment.) It's a little difficult to illustrate in the contrived minimal example, but hopefully if anyone comes across this dilemma in the future, this is enough to show how I think I'll end up handling this (rather than eslint-ignore).
Appreciate the open discussion on this. Cheers.

interface P1 {
	a: true;
	b: number;
}

interface P2 {
	a: false;
}

type P = P1 | P2;

export const MyComponent: React.VFC
 = (props) => {
	const { a } = props;

	// If needed, any common logic between the two forked components can go here, and be
	// passed in as props on the line below.

	return a ? <MyComponentWithATrue {...props} /> : <MyComponentWithAFalse {...props} />;
};

export const MyComponentWithATrue: React.VFC<P1> = (props) => {
	const { b } = props;

	return {b};
};

export const MyComponentWithAFalse: React.VFC<P2> = (props) => {
	return {/* ... */};
};

Splitting it into two components definitely sounds like the best approach here.
I remain open to discussing a change in the rule to allow for exceptions, but to be compelling, I'd need a use case that isn't obviated by finding a better architecture :-)


Update flutter.io's social sharing metadata

Currently, it looks like we're not advertising the right metadata when we're shared. We show this:

We could:

[ ] display an image
[ ] show relevant description

We need this before beta for sure!

cc @sethladd This should be pretty easy to do, right?

We'll likely do this as part of the website upgrades we envision.
cc @maguinis

cc @filiph


watch command: changes to widget flags dooesn't generate models for widget programs

Changes to flags will mean that their respective program models will also change. When using the watch command djelm intercepts flag changes and generates the model for that particular program. This however doesn't function for widget programs.
Proposed solution
Detect flag changes for widgets and generate the respective widget Model.

This was fairly simple to do but I did notice that we get double generations on programs.
I conjecture because we load the flags module and under the hood python modifies the files when it loads the module for it's own caching reasons. Thus the watch process picks up 2 file mods instead of 1.
It's not a huge deal, but we should be able to get around this when we start validating file changes more robustly.

Released in 0.14.0


Disabling LDAP requires editing the node directly

chef-server-core 12.0.5-1.el6
Short version: there  should be a way to remove/unconfigure ldap without editing the node data for the chef server directly.
Long version:
After configuring LDAP per https://docs.chef.io/server_ldap.html, we needed to turn it off. Tried doing so by removing ldap items from /etc/opscode/chef-server.rb and running a chef-server-ctl/opscode-manage-ctl, but the ldap configuration persisted.
Attempted to set to nil, with no joy. Finally was able to remove the ldap configuration by editing the /opt/opscode/embedded/nodes/.json and removing the ldap sections.
Let me know if you'd like any additional information.

I think this bug should have been fixed in the lastest release as we now make sure to delete any existing node data before the reconfiguration.


ci: updates to fix build/package & produce binaries

Description of changes

Issue #, if available

Description of how you validated changes
Checklist

[ ] PR description included
[ ] yarn test passes
[ ] Tests are changed or added
[ ] Relevant documentation is changed or added (and PR referenced)
[ ] New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
[ ] Pull request labels are added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Fixed up the merge conflicts. This looks good to me. Will squash and merge this and checkout on my fork to implement and validate the changes.

Codecov Report

:exclamation: No coverage uploaded for pull request base (cb@285c07c). Click here to learn what that means.
The diff coverage is n/a.

: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          @@
##             cb   #12284   +/-   ##
=====================================
  Coverage      ?   47.05%
=====================================
  Files         ?      836
  Lines         ?    38092
  Branches      ?     7730
=====================================
  Hits          ?    17926
  Misses        ?    18523
  Partials      ?     1643

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


nodejs favicon URL changed?

mdn-anno.css has favicon line as

background-image: url(https://nodejs.org/static/images/favicons/favicon.ico);

but it seems URL has gone and returns 404. I have no idea on new location, so just file an issue here.

Sigh, thanks for the reports. I'll track it down and I guess just download the image directly.

it seems we could replace with https://nodejs.org/favicon.ico


Fix width for hiring banner to avoid safari issue

Changes

[x] Fix width for hiring banner to avoid safari issue

Coverage remained the same at 83.797% when pulling 0ecd03af44cd746e8bd066001d3597b31ec32088 on fix-hiring-banner-sizes into 90bea5f35fc9d0360bf1ede86edff65ea3cd5225 on master.


(PUP-5538) Fix SID::Principal domain_account

Previously, the Puppet::Util::Windows::SID::Principal initializer
didn't understand that an account may be passed in with a domain
prefix that should be parsed off when building the domain_account
value.
When calling:
Puppet::Util::Windows::SID::Principal.lookup_account_name('NT AUTHORITY\SYSTEM')
account was previously set to 'NT AUTHORITY\SYSTEM' and
domain_account to 'NT AUTHORITY\NT AUTHORITY\SYSTEM'
This commit changes account to 'SYSTEM' and
domain_account to 'NT AUTHORITY\SYSTEM' in the above instance

+1

:+1:


🧪 Silence expected errors during unit tests

Description
We see the below errors when running unit tests. These are expected as we are testing error states, however they cause unneeded noise in the console. Mock console.error (or use a different approach) to silence these expected errors. Be sure to not hide real errors if something were to break.
Screenshot

Closed by #1005


Update Okta docs to include SCIM deprovisioning

We're updating our Okta app to support SCIM deprovisioning 💫
Most of the setup is staying the same, and we're adding a piece for folks who want to enable the deprovisioning.
The doc currently starts out with everything in Okta for step 1, then everything in Buildkite for step 2. To get the deprovisioning set up you first need to get some stuff from BK then you have to go back to Okta. I decided to add the new little dance in as a subsection to step 2, but if you'd think that it would be better elsewhere feel free to move it!
New stuff is here: https://docs-review-pr-1094.herokuapp.com/docs/integrations/sso/okta#step-2-create-an-sso-provider-scim-deprovisioning
I also noticed that a couple of the screenshots were sitting funny, and it turns out their width/height numbers were a little off. I've updated the ones I found.

This won't need merging until the Okta app is ready to go, so I'm going to change it back to a draft.

This PR won't need merging until the Okta app is ready.

Thanks @plaindocs! I've just added in some more bits from your review.
I've stuck that note at the top of the deprovisioning section as per the Okta integration guide. It will be removed before this goes live 👍🏻

@harrietgrace , I'm not super clear on the split between folks wanting to use just SSO, and those who want deprovisioning also. Is that something we want to care about?

I'm not super clear on the split between folks wanting to use just SSO, and those who want deprovisioning also. Is that something we want to care about?

@plaindocs yes it is! The Okta folks have taken care of that on their side: https://saml-doc.okta.com/SAML_Docs/How-to-Configure-SAML-2.0-for-Buildkite.html. They link to this doc when you add the application in Okta. The new version of the app is live, so I'll update the note saying that it's not available to say that it's there but not super done yet. Once it's all good and we've flipped the feature flag I'll come back and remove the note.

Given that the new version of the app went live this morning (unexpectedly), I'm going to merge this. We can always go and add/fix things once it's live 😊

🎊🎊🎊
On Fri, 20 Aug 2021, 10:08 Harriet Lawrence, @.***>
wrote:

Merged #1094 https://github.com/buildkite/docs/pull/1094 into main.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/buildkite/docs/pull/1094#event-5184125661, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAB7RBXBWHJ4UOKNHLNIHLT5WMGRANCNFSM5AGCII3Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

Thanks for helping push this over the line @harrietgrace !


Allow EF.Relational.Design to install on UWP projects

Resolves #3681

:shipit: This is consistent with the hacking I did on my package cache to get things to work.


[fix][cursor] Fix enable maxPosition cursor will read in deap loop

Motivation
Now we don't check OpAddEntry can read entry is smaller than maxReadPosition, if readPosition is bigger than maxReadPosition, we only can read an empty list as result. In fact, when maxReadPosition have not been updated, we should put read op in to wait state and when maxReadPosition updated, we can notify it and read continue.
Modifications

Add a field named maxReadPosition inManagedLedgerImpl and if read op enable maxReadPosition, we should check this readPosition is bigger than maxReadPosition, if bigger we should put the op into wait state, if smaller or equals we can  do this op.
Add a field named waitingCursorsByMaxReadPosition in ManagedLedgerImpl, when cursor has read op in wait state, we can put this read op in to this queue. If maxReadPosition updated, we will pool it and notify this this read op.
In topicTransaction buffer, when any updated maxReadposition op we should sync it to ManagedLedgerImpl maxReadPosition.

Verifying this change
add the test
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation

Does this pull request introduce a new feature? (yes)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

This change is a big refactor in ManagedCursor, it is not a transaction only related patch.
Please change the title, otherwise it is possible that this change would not be noticed by people not interested in Transactions.
Also I would say that we cannot cherry-pick this change to old branches, as it is adding breaking changes in the internal interfaces (I am pretty sure that some Protocol Handler won't compile)

I am wondering why this pr do not invoke updateMaxReadPosition in TopicTransactionBuffer#handleTransactionMessage() ?

Since we will start the RC version of 3.0.0 on 2023-04-11, I will change the label/milestone of PR who have not been merged.

The PR of type feature is deferred to 3.1.0
The PR of type fix is deferred to 3.0.1

So drag this PR to 3.0.1

It looks the issue fixed by https://github.com/apache/pulsar/pull/14667, closing... feel free to reopen if this PR still ongoing

It looks the issue fixed by #14667, closing... feel free to reopen if this PR still ongoing

@dao-jun This issue is not fix. I test again in version-3.0.5 and this issue reproduce. This pr still need to be merged.


Created TicTok meric scraper.

Only testing for success and failure in the network data response.
Test instructions are in the README.md.

The instructions reference port 8888 but it seems that by default port 3000 is used. I worked around this by adding "start": "PORT=8888 run-p start:*" to package.json but not sure that's the right thing to do here. Please advise.

The README.md needs to be corrected. I'll update it.

I'm a little confused about the role netlify is playing. I see a lambdas folder that seems to imply the metric parsing logic would be running server side? Ideally we perform metric parsing locally so that our API calls to Tik Tok are distributed across client devices.

Netlify provides a serverless API layer to the thin client. The TikTok library mentioned that there isn't a limit on the number of requests that can be made.

When I follow the instructions I'm seeing attached. Is this expected?
Looks like the ./src/functions files haven't been built. You'll also need to rerun the tests.

rebased and reopened to get PR builder to run.

Keeping commits messages.

Did you follow the directions in the README.md on how to start the project?
Regards,
Bernard T. A. Baker
On Tue, Apr 14, 2020 at 6:21 AM dzx11<EMAIL_ADDRESS>wrote:

@dzx11 commented on this pull request.
In react_front_end/src/tests/services/TikTok.js
https://github.com/un7c0rn/stopthevirus/pull/23#discussion_r407873354:

@@ -0,0 +1,17 @@
+/**

@jest-environment node

*/

+import { metricParser } from "../../services/TikTok";
+
+test("video metadata", async () => {

const url = "https://www.tiktok.com/@tiktok/video/6807491984882765062";
const data = await metricParser(url);
expect(data.id).toBe("6807491984882765062");

@bernardbaker https://github.com/bernardbaker It looks like it's trying
to connect to localhost:8888 for some reason. Are there some config changes
that need to be made to change this? I think I saw some discussion with
Brandon regarding this. Using jest.setTimeout didn't make a difference.
Full trace below.
[image: test2]
https://user-images.githubusercontent.com/13459787/79188856-266ca700-7e5b-11ea-8cb5-43ffc5acc7ea.PNG
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/un7c0rn/stopthevirus/pull/23#discussion_r407873354,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHNTTHIJIAB4DSK2DMNML3RMPXFPANCNFSM4MEYOBGA
.

@bernardbaker I reran the install scripts, changed the port in the test script, and tried running the 'yarn start' script concurrently and still had an error, although the console error messages are different. How are you running the tests? Do you just run the 'yarn test' script or do you have another script or server running at the same time? Since it's trying to connect to localhost, I assume that you're running the 'yarn start' script at the same time as you run the tests

@dzx11 try this...
open three terminal windows.
1st window: cd react_front_end; yarn
2nd window after 1st set of commands have completed: netlify dev
3rd window after 2nd set of commands have completed: yarn test
Regards,
Bernard T. A. Baker
On Tue, Apr 14, 2020 at 5:30 PM dzx11<EMAIL_ADDRESS>wrote:

@bernardbaker https://github.com/bernardbaker I reran the install
scripts, changed the port in the test script, and tried running the 'yarn
start' script concurrently and still had an error, although the console
error messages are different. How are you running the tests? Do you just
run the 'yarn test' script or do you have another script or server running
at the same time? Since it's trying to connect to localhost, I assume that
you're running the 'yarn start' script at the same time as you run the tests
[image: test4]
https://user-images.githubusercontent.com/13459787/79249682-99f0d180-7eb8-11ea-9b3a-5683b1e78234.PNG
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/un7c0rn/stopthevirus/pull/23#issuecomment-613545593,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHNTTGFUCLJ3RMRBXK3SPDRMSFSXANCNFSM4MEYOBGA
.

@bernardbaker that worked, thanks! It may be worth adding those steps to the readme - I was under the impression that netlify was only needed for deployment.

@dzx11 great news. Good job. I'll update the README.md as requested.


mcunet face detection model and code

Hi Team,  I would like to run the mcunet timyengine face detection model on M7 board and looking to find the source code but I see that there is only VWW code captured here. Is there a way to find the face detection code ? Also it would be helpful if you can add face detection benchmarking numbers for detection timings.
Thanks in advance.

Hi @kumarchaitanyab, we have an example for person detection: https://github.com/mit-han-lab/tinyengine/blob/master/examples/detection_fpn.py. Feel free to check it out.

Thanks for your response. Actually I am looking for  C/C++ source code for face detection based application which runs on M7 based microcontroller. Can you please point me to that?

Hi @kumarchaitanyab,
Sorry for the late reply. We are preparing to release the source code and tutorial for the face mask detection demo, so please stay tuned.

Hi @kumarchaitanyab,
We have released the source code for face mask detection. Feel free to check it out and let us know any issues or questions.
Tutorial on openmv cam: https://github.com/mit-han-lab/tinyengine/tree/master/examples/openmv_face_mask_detection
Generated code for the model: https://github.com/mit-han-lab/tinyengine/tree/master/examples/openmv_face_mask_detection/codegen

Sure, will try and let you know. However, can you share your benchmarking numbers for various boards, more specifically am looking for detection timings. I have an M7 (STM32F746G-DISCO) board and hope this code can run on this board.

Hi @meenchen @RaymondWang0
I have arducam, not sure if this code supports this camera interface. Can you please confirm and let me know along with benchmarking numbers for face detection and specially for STM32F746G-DISCO board.

Hi @kumarchaitanyab,
The generated code for Tinyengine is able to run on the STM32F746G-DISCO board, but the application-specific code will need to be edited (refer to tutorial). For face mask detection, the latency is about 140ms on the openmv cam running at 480MHz. On the STM32F746G-DISCO board, the latency will be around 311ms at 216MHz.

Hi @meenchen
Thanks for the input. Just wanted to know that this time (140ms or 311ms) is only for inference or does it includes camera capture and pre, post processing involved?

Hi @meenchen Thanks for the input. Just wanted to know that this time (140ms or 311ms) is only for inference or does it includes camera capture and pre, post processing involved?

That includes post processing as well.

Hi @meenchen, thanks a lot.
It will be very useful for us if you can provide timing breakdown for camera capture, pre-processing, inference and post-processing.


[#59] Add node states

Description
A state has been added to each node. (Whether it was deleted from the hash table or not).
This will help filter events for eviction policy updates in the wrong order to avoid damaging the eviction policy.
Related issue(s)

Fixed #59 by adding node states

:white_check_mark: Checklist for your Pull Request
Related changes (conditional)

Tests

[x] If I added new functionality, I added tests covering it.
[x] If I fixed a bug, I added a regression test to prevent the bug from
silently reappearing again.

Documentation

[x] I checked whether I should update the docs and did so if necessary:

README

Public contracts

[x] My changes doesn't break project license.

Stylistic guide (mandatory)

[x] My code complies with the styles guide.

[x] My commit history is clean (only contains changes relating to my
issue/pull request and no reverted-my-earlier-commit changes) and commit
messages start with identifiers of related issues in square brackets.
Example: [#42] Short commit description
If necessary both of these can be achieved even after the commits have been
made/pushed using rebase and squash.

Before merging (mandatory)

[x] Check target  branch of PR is set correctly

Codecov Report
Attention: Patch coverage is 85.71429% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 95.56%. Comparing base (758caa3) to head (6bb9e32).

Files
Patch %
Lines

internal/core/cache.go
87.50%
1 Missing and 1 partial :warning:

internal/s3fifo/small.go
0.00%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #60      +/-   ##
==========================================
+ Coverage   95.37%   95.56%   +0.18%
==========================================
  Files          22       22
  Lines        1232     1239       +7
==========================================
+ Hits         1175     1184       +9
+ Misses         39       37       -2
  Partials       18       18

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

Damn, it seems like splitting isAlive checks between eviction and expiration policies was a bad idea. It looks like we need to refactor the code.

Yes, it looks better now.


ENH: Enable installation of dependencies on Microsoft Windows

@cooperlab says "Skip. This library is used exclusively on servers."


Google Tasks support not working

I replaced the SSD in my laptop and installed Debian Testing fresh, and now I'm attempting to get Errands to pick up Google Tasks but no dice. I installed the DEB package as well as the Flatpak (one after the other, not simultaneously), and removed and re-added my Google account but I got nothin'. Has Google support been removed or am I missing something?

Errands never supported Google Tasks, or Google Calendar.

Sorry, I think I was getting Errands mixed up with Endeavor.
Sent with Proton Mail secure email.
On Thursday, November 21st, 2024 at 00:18, mrvladus @.***> wrote:

Errands never supported Google Tasks, or Google Calendar.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Always template images are ignored

Setting images that have the rendering mode UIImageRenderingModeAlwaysTemplate are ignored (not shown at all).
The following code has the same result as to setting the image to nil:
UIImage *image = [[UIImage imageNamed:@"some_image"] imageWithRenderingMode:UIImageRenderingModeAlwaysTemplate];
[SVProgressHUD setSuccessImage:image];

When will this be pulled?

Is there any reason this isn't pulled?