fix(readme): CI badges

## Overview
Fixes the CI badges in the readme

#190  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @clabby and the rest of your teammates on  Graphite


ensure soft-forks (e.g. multi-sigs) could make use of the time lock system

Currently I don't think it allows for such expansion of logic.

If we don't allow for soft-forks in conditions/fulfillments, and instead force hard-forks, it will be possible. See: https://github.com/rivine/rivine/issues/293#issuecomment-385256422


dataset

Hi，how can i  download the image dataset? I mean i couldn't find your email on the README page

I found the email link of the author<EMAIL_ADDRESS>and sent the email address of the requested data set to the author. The author has replied to me. You can also try sending an email to the author. Good luck

Hi，how can i download the image dataset? I mean i couldn't find your email on the README page

Did you get the author's reply?

Hello, could you please send me a copy of the dataset? Thank you very much, here is my email<EMAIL_ADDRESS>

I found the email link of the author<EMAIL_ADDRESS>and sent the email address of the requested data set to the author. The author has replied to me. You can also try sending an email to the author. Good luck

Can you share a copy with me? I also sent an email to the author, but I haven't received a response for a long<EMAIL_ADDRESS>  thank u

Hello. Could you please share a copy of the dataset with me? I need it now badly.  This is my email<EMAIL_ADDRESS>Thank you.

I found the email link of the author<EMAIL_ADDRESS>and sent the email address of the requested data set to the author. The author has replied to me. You can also try sending an email to the author. Good luck

Hi. Could you please share a copy of the dataset with me? I need it now badly. This is my email<EMAIL_ADDRESS>Thank you.

I found the email link of the author<EMAIL_ADDRESS>and sent the email address of the requested data set to the author. The author has replied to me. You can also try sending an email to the author. Good luck

Hi,could u share a copy with me? i really need the dataset.This is my<EMAIL_ADDRESS>

I found the email link of the author<EMAIL_ADDRESS>and sent the email address of the requested data set to the author. The author has replied to me. You can also try sending an email to the author. Good luck

Hi. Could you please share a copy of the dataset with me? I need it now badly. This is my email<EMAIL_ADDRESS>Thank you.

<EMAIL_ADDRESS>

Please refer to this thread
https://github.com/wondonghyeon/protest-detection-violence-estimation/issues/10#issuecomment-2011074183


Update NEWS.md

Last release note was for 0.5.3. Last release is 0.5.9.

Closed by 9fa97dac7be06f9753d922cf4e8ec3e2124ee7b2


Access task logs in luigid

It would be really nice if luigi intercepted logger.XXX calls & sent them somewhere to be viewed with luigid (up to some reasonable limit). It would help a lot in debugging broken tasks or checking that a task is actually doing something without finding which actual process is running it.
For bonus points, intercept sys.stdout/sys.stderr entirely :)

Duplicate of #1008

Thanks for the triaging work @knassiri. I'm closing this as it's a (much better worded) duplicate of #1008.


Use template-literal instead of EJS

Template Literal is fastest, smallest and simplest template engine, because it use JS's literal template feature.
It's  55 times faster than EJS, and it also use less CPU and RAM ressources, so it may be a good idea to use it instead of EJS 😀

Hello @Drulac  :)
Thank you for the update! I will look into having multiple template engines available in the platform.


Markdown Preview screen does not respond to keyboard shortcuts

VSCode Version: 1.51.1
OS Version: Linux x64 5.4.0

Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:31:29.624Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-48-generic
Steps to Reproduce:

Open a file with Markdown in it
Open the Markdown preview pane to the right side of your Markdown file
Click the Markdown preview pane to focus it
Press ctrl+shift+p to open the Show All Commands bar
Execute the command View: Navigate to the View on the Left
Notice that nothing happens

Does this issue occur when all extensions are disabled?: Yes
Expectation: The commands from the Show All Commands bar should work in the Markdown Preview window (and also the keyboard shortcuts of those commands).

/confirm also in 1.52.0-insider
You might have more success with the commands named View: Focus Right Editor Group and View: Focus Left Editor Group. However the default keybindings for these use a chord, i.e. they both begin with Ctrl+K. It seems that the Markdown Preview doesn't handle chords properly. Watch the status bar for the message reporting about waiting for the second key of the chord. When on Markdown Preview this message disappears prematurely, leaving no opportunity for me to press the second key. In contrast, entering the Ctrl+K, Ctrl+RightArrow chord when on the raw markdown editor in the left group works correctly.

I'm working on this issue

I am no longer able to reproduce this with VS Code insiders on MacOS and windows . I think it is potentially a duplicate of #119076


Cleanup Disclaimer page

There are too many information in the disclaimer page right now we should reduce this to

Disclaimer
Intellectual Property

Blocked by #96

done.


USHIFT-535: Remove dns configurable option from MicroShift config

Cluster DNS is set to the 10th IP of Service CIDR
Signed-off-by: Vu Dinh<EMAIL_ADDRESS>
Which issue(s) this PR addresses:

Closes #

@benluddy PTAL

There are some mentions of this config field in packaging/microshift/config.yaml and the config docs, too.

Do we know why dns option was added before?

Do we know why dns user-configurable option was added before?

I do not know. This was added before my time. Maybe @fzdarsky knows.

/retitle USHIFT-535: Remove dns configurable option from MicroShift config
Created a JIRA issue for this work.

Do we know why dns user-configurable option was added before?

I would suspect that we just didn't know the .10 was a hard default?

/retest

Do we know why dns user-configurable option was added before?

I would suspect that we just didn't know the .10 was a hard default?

It's configurable on other K8s distros, so we probably just thought it should be configurable here, too.

some nits

/retest

@dhellmann Addressed your feedback. Looking for a lgtm and approve. Thanks.

/test e2e-openshift-conformance-sig-auth

/approve

/lgtm

/test e2e-openshift-conformance-sig-network

/test e2e-openshift-conformance-sig-network

/test e2e-openshift-conformance-sig-network

/test e2e-openshift-conformance-sig-network

/retest

/test e2e-openshift-conformance-sig-network

/test e2e-openshift-conformance-sig-network

/retest

/hold

/hold cancel


Earn dashboard rewards

Overview
Seems like we are having some issues with the new grouping earn dashboard rewards.

Cosmos rewards aren't showing up correctly
Thorchain savers should not have claimable rewards

References and additional details
Most likely inside the combined selector
Acceptance Criteria
Shows the correct reward amounts and claimable rewards.
Need By Date
No response
Screenshots/Mockups
No response
Estimated effort
No response

Closed by https://github.com/shapeshift/web/pull/4072


Revert "Ensure that flutter run/drive/test/update_packages only downloads required artifacts"

Reverts flutter/flutter#30075

Landing to fix build


Update Homebrew release version to latest

Triggering Homebrew update for EKS-A release v0.18.5.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick release-0.18

/lgtm
/approve

/woof
/meow


Fix controller init

There was an error when I was using non localized routes in other scopes.
I just added the default init/1 from phoenix as a fallback (https://github.com/phoenixframework/phoenix/blob/master/lib/phoenix/controller/pipeline.ex#L18) that, if I understand well, was overridden (https://github.com/phoenixframework/phoenix/blob/master/lib/phoenix/controller/pipeline.ex#L37)

That makes sense!
thanks for the contribution


fix: Sensor to apply exclude pattern for rootfs enumeration

Mounting a huge folder from the host filesystem can make sensor (almost?) stuck. Most of the time, you'd probably want the host mounts excluded from the minified image, however StartMonitor.Excludes wouldn't really help solving the slowness of the sensor's startup logic caused by such mounts. Hence, the fix.

Was merged as part of #407


Add Documentation for Cloning a Linked List with Random and Next Pointers

📥 Pull Request
Description
This pull request introduces detailed documentation for cloning a linked list that includes both random and next pointers. The new documentation aims to clarify the process and provide a comprehensive guide for developers.
Fixes #1528
Type of change

[x] Added new document

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works

Okay I will make changes then update


Reorganize the classes in grpc-protocol

Motivation:
Realized that both client and server classes in grpc-protocol are
placed under common.grpc.protocol.
Modifications:

Move the client and server side classes to client.grpc.protocol and
server.grpc.protocol respectively.
Miscellaneous:

Add @anuraaga to the owners of /grpc-protocol/

Result:
Consistency

Thanks for reviewing :-)


Setting path to dbt project

Hi,
I'm using dbt in a git repo.
Dbt is thus part of the project, and the whole dbt project is stored under a subfolder.
I'm using dbt in different envs as well.
Workflow:
Source env file (this defines where dbt can find the profiles)
and then go to the dbt subfolder, and run dbt from there.

Is there a way for this extension to set the folder where the dbt project can be found?

Project discovery should work automatically, the extension searches your project to find any dbt_project.yml and registers the projects automatically.
The env part can be handled in the following way (.env files are not supported at the moment, definitely open for PR's)
Just set the environment variables within .vscode config for the project (config.terminal.integrated.env).
env: A map defining environment variables and their values, set the variable to null to delete it from the environment. This can be configured for all profiles using the terminal.integrated.env. setting.
See https://code.visualstudio.com/docs/editor/integrated-terminal
https://github.com/innoverio/vscode-dbt-power-user/blob/1be0a0a8a31f99d8a0b26e03f3bf8490ae5fdaac/src/dbt_client/index.ts#L178-L184


Jekyll serve --incremental is very slow, making a live edit workflow very difficult

It takes over 30 seconds to see one edit to a page go live.  This is slow enough that it makes the incremental "write-and-check, write-and-check" style of working very difficult and frustrating.
Running as:
bundle exec jekyll serve --port 4000 --incremental --trace --config _config_base.yml,_config_cockroachdb.yml

The performance on a brand new MBP with 1TB SSD and 16 GB RAM is ... very bad.  As shown below I am making small edits to one file and it takes 30+ seconds to show me the changes.
      Regenerating: 1 file(s) changed at 2021-03-04 10:36:24
                    v21.1/set-locality.md
                    ...done in 32.932964 seconds.

      Regenerating: 1 file(s) changed at 2021-03-04 10:36:57
                    v21.1/set-locality.md
                    ...done in 32.305148 seconds.

      Regenerating: 2 file(s) changed at 2021-03-04 10:39:43
                    v21.1/set-locality.md
                    v21.1/.#set-locality.md
                    ...done in 33.882001 seconds.

      Regenerating: 1 file(s) changed at 2021-03-04 10:40:17
                    v21.1/set-locality.md
                    ...done in 33.165183 seconds.

      Regenerating: 2 file(s) changed at 2021-03-04 10:41:10
                    v21.1/set-locality.md
                    v21.1/.#set-locality.md
                    ...done in 31.34292 seconds.

Possibly related old issues:

#1716
#2941

Seems like it would be fixed by:

#4959

This surprised me, @rmloveland. If you use make standard, that uses https://github.com/cockroachdb/docs/blob/master/_config_cockroachdb_local.yml, which excludes everything for the stable and dev versions from getting build, and that should keep it pretty fast. Are you not using make standard? Also, it's important to rm -rf _site every so often. The build is slower right after doing that, but it can often improve things thereafter. Can you try that?

Sure!
Just did the following:
rm -rf _site
make standard

Long output pasted below.  tl;dr: on a single edit of one file it's taking about 18 seconds to reload.
I think the other day when I created this issue I had multiple files (about 10) in various states of edited-ness, and hadn't deleted _site in a while.  I wouldn't be surprised if this creeps back up into the near 30s range if I were to work on multiple edits for a couple hours tho without restarting Jekyll.
Maybe I'm the only one experiencing it? But maybe folks are just used to it - Not sure.  Could be something in my setup as well.  I'll ask in the chat.
make standard
bundle install
Using public_suffix 4.0.6
Using addressable 2.7.0
Using json 2.5.1
Using racc 1.5.2
Using nokogiri 1.11.1 (x86_64-darwin)
Using algolia_html_extractor 2.6.4
Using httpclient 2.8.3
Using algoliasearch 1.27.5
Using bundler 2.2.11
Using colorator 1.1.0
Using concurrent-ruby 1.1.8
Using eventmachine 1.2.7
Using http_parser.rb 0.6.0
Using em-websocket 0.5.2
Using ffi 1.14.2
Using filesize 0.2.0
Using forwardable-extended 2.6.0
Using i18n 1.8.9
Using sassc 2.4.0
Using jekyll-sass-converter 2.1.0
Using rb-fsevent 0.10.4
Using rb-inotify 0.10.1
Using listen 3.4.1
Using jekyll-watch 2.2.1
Using rexml 3.2.4
Using kramdown 2.3.0
Using kramdown-parser-gfm 1.1.0
Using liquid 4.0.3
Using mercenary 0.4.0
Using pathutil 0.16.2
Using rouge 3.26.0
Using safe_yaml 1.0.5
Using unicode-display_width 1.7.0
Using terminal-table 2.0.0
Using jekyll 4.2.0
Using progressbar 1.11.0
Using verbal_expressions 0.1.5
Using jekyll-algolia 1.6.0 from source at `jekyll-algolia-dev`
Using jekyll-redirect-from 0.16.0
Using jekyll-remote-include 1.1.3 from https://github.com/ianjevans/jekyll-remote-include.git
Using jekyll-sitemap 1.3.1
Using liquid-c 4.0.0
Using redcarpet 3.5.1
Using rss 0.2.9
Using webrick 1.7.0
Updating files in vendor/cache
Bundle complete! 10 Gemfile dependencies, 45 gems now installed.
Use `bundle info [gemname]` to see where a bundled gem is installed.
touch bootstrap
bundle exec jekyll serve --port 4000 --incremental --trace --config _config_base.yml,_config_cockroachdb.yml,_config_cockroachdb_local.yml
Configuration file: /Users/rloveland/work/code/docs/_config_base.yml
Configuration file: /Users/rloveland/work/code/docs/_config_cockroachdb.yml
Configuration file: /Users/rloveland/work/code/docs/_config_cockroachdb_local.yml
            Source: /Users/rloveland/work/code/docs
       Destination: /Users/rloveland/work/code/docs/_site/docs
 Incremental build: enabled
      Generating...
                    done in 34.659 seconds.
 Auto-regeneration: enabled for '/Users/rloveland/work/code/docs'
    Server address: http://<IP_ADDRESS>:4000/docs/
  Server running... press ctrl-c to stop.
      Regenerating: 2 file(s) changed at 2021-03-08 11:20:50
                    v21.1/add-region.md
                    v21.1/.#add-region.md
                    ...done in 18.482852 seconds.

[2021-03-08 11:21:10] ERROR `/apple-touch-icon-precomposed.png' not found.
[2021-03-08 11:21:10] ERROR `/apple-touch-icon.png' not found.
      Regenerating: 2 file(s) changed at 2021-03-08 11:21:26
                    v21.1/add-region.md
                    v21.1/.#add-region.md
                    ...done in 18.792359 seconds.

Just a heads up that resetting your local Jekyll environment is now easier with make clean.
make clean && make standard

I, too, have noticed the longer regeneration times.

According to this SO question, there's --profile option for Jekyll that shows what is taking the time.
So you could edit your Makefile thusly:
.PHONY: cockroachdb
cockroachdb: jekyll-action := serve --port 4000
cockroachdb: bootstrap
	bundle exec jekyll $(jekyll-action) --incremental --trace --config --profile _config_base.yml,_config_cockroachdb.yml,_config_cockroachdb_local.yml$(extra-config) $(JEKYLLFLAGS)

thanks, I'll take a look at that Ian!

I have also discovered that my editor was creating "auto-save" backup files in these directories, adding to the number of files it has to scan.  I will run the profile and check back

Hi Rich! I am (slowly) taking a look at this. Can you please help answer a few questions?

What is your base build time? (i.e. when you don't make any changes and just rebuild what was previously generated)
What is your Ruby version?
Can you paste your --profile output as discussed with Ian above?
Do you see an improvement if you swap out v20.2 for another version from local builds?

For me, 4. is "yes." If that is also the case for you, then a next step might be to understand what's special about that version. Meanwhile I am also looking into other ways we might be able to speed up the build in general.

It looks like remote_include may be slowing down the build. In a few quick tests, not using remote_include shaves up to 6 seconds (from 13-ish secs to 7-ish secs). Replications welcome!

Hi Rich! I am (slowly) taking a look at this. Can you please help answer a few questions?

Yes! and thanks!

What is your base build time? (i.e. when you don't make any changes and just rebuild what was previously generated)

make cockroachdb-build
touch bootstrap
bundle exec jekyll build --incremental --trace --config _config_base.yml,_config_cockroachdb.yml
Configuration file: /Users/rloveland/work/code/docs/_config_base.yml
Configuration file: /Users/rloveland/work/code/docs/_config_cockroachdb.yml
            Source: /Users/rloveland/work/code/docs
       Destination: /Users/rloveland/work/code/docs/_site/docs
 Incremental build: enabled
      Generating...
                    done in 64.448 seconds.
 Auto-regeneration: disabled. Use --watch to enable.

What is your Ruby version?

ruby 3.0.0p0 (2020-12-25 revision 95aff21468) [x86_64-darwin19]

Can you paste your --profile output as discussed with Ian above?

I edited the Makefile to use Ian's text for the cockroachdb Makefile target and it throws an error as shown below.
(I also got a new laptop recently and Homebrew defaulted me to Ruby 3.0.0 so I've been running with some stashed changes to the Gemfile* files to "get things working", which may be affecting things)
make standard
bundle exec jekyll serve --port 4000 --incremental --trace --config --profile _config_base.yml,_config_cockroachdb.yml,_config_cockroachdb_local.yml
           WARNING: Error reading configuration. Using defaults (and options).
No parser for '/Users/rloveland/work/code/docs/--profile' is available. Use a .y(a)ml or .toml file instead.
bundler: failed to load command: jekyll (/usr/local/lib/ruby/gems/3.0.0/bin/jekyll)
/Users/rloveland/work/code/docs/_plugins/versions/config.rb:7:in `block in initialize': Config missing `versions` key (RuntimeError)
	from /Users/rloveland/work/code/docs/_plugins/versions/config.rb:6:in `each'
	from /Users/rloveland/work/code/docs/_plugins/versions/config.rb:6:in `initialize'
	from /Users/rloveland/work/code/docs/_plugins/versions/generator.rb:11:in `new'
	from /Users/rloveland/work/code/docs/_plugins/versions/generator.rb:11:in `initialize'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/site.rb:321:in `new'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/site.rb:321:in `block (2 levels) in instantiate_subclasses'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/site.rb:321:in `map!'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/site.rb:321:in `block in instantiate_subclasses'
	from <internal:kernel>:90:in `tap'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/site.rb:319:in `instantiate_subclasses'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/site.rb:134:in `setup'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/site.rb:36:in `initialize'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/commands/build.rb:30:in `new'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/commands/build.rb:30:in `process'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/command.rb:91:in `block in process_with_graceful_fail'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/command.rb:91:in `each'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/command.rb:91:in `process_with_graceful_fail'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/lib/jekyll/commands/serve.rb:86:in `block (2 levels) in init_with_program'
	from /usr/local/lib/ruby/gems/3.0.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `block in execute'
	from /usr/local/lib/ruby/gems/3.0.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `each'
	from /usr/local/lib/ruby/gems/3.0.0/gems/mercenary-0.4.0/lib/mercenary/command.rb:221:in `execute'
	from /usr/local/lib/ruby/gems/3.0.0/gems/mercenary-0.4.0/lib/mercenary/program.rb:44:in `go'
	from /usr/local/lib/ruby/gems/3.0.0/gems/mercenary-0.4.0/lib/mercenary.rb:21:in `program'
	from /usr/local/lib/ruby/gems/3.0.0/gems/jekyll-4.2.0/exe/jekyll:15:in `<top (required)>'
	from /usr/local/lib/ruby/gems/3.0.0/bin/jekyll:23:in `load'
	from /usr/local/lib/ruby/gems/3.0.0/bin/jekyll:23:in `<top (required)>'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/cli/exec.rb:63:in `load'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/cli/exec.rb:63:in `kernel_load'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/cli/exec.rb:28:in `run'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/cli.rb:494:in `exec'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/vendor/thor/lib/thor/command.rb:27:in `run'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/vendor/thor/lib/thor/invocation.rb:127:in `invoke_command'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/vendor/thor/lib/thor.rb:392:in `dispatch'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/cli.rb:30:in `dispatch'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/vendor/thor/lib/thor/base.rb:485:in `start'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/cli.rb:24:in `start'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/exe/bundle:49:in `block in <top (required)>'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/lib/bundler/friendly_errors.rb:130:in `with_friendly_errors'
	from /usr/local/lib/ruby/gems/3.0.0/gems/bundler-2.2.11/exe/bundle:37:in `<top (required)>'
	from /usr/local/lib/ruby/gems/3.0.0/bin/bundle:23:in `load'
	from /usr/local/lib/ruby/gems/3.0.0/bin/bundle:23:in `<main>'
make: *** [cockroachdb] Error 1

Do you see an improvement if you swap out v20.2 for another version from local builds?

By "swap out" do you mean I add v20.2 to the list of things we don't build in _config_cockroachdb_local.yml?
If so, here is the output when I add v20.2 to the list of "ignored things":
make cockroachdb-build
bundle exec jekyll build --incremental --trace --config _config_base.yml,_config_cockroachdb.yml
Configuration file: /Users/rloveland/work/code/docs/_config_base.yml
Configuration file: /Users/rloveland/work/code/docs/_config_cockroachdb.yml
            Source: /Users/rloveland/work/code/docs
       Destination: /Users/rloveland/work/code/docs/_site/docs
 Incremental build: enabled
      Generating...
                    done in 62.191 seconds.
 Auto-regeneration: disabled. Use --watch to enable.

For me, 4. is "yes." If that is also the case for you, then a next step might be to understand what's special about that version. Meanwhile I am also looking into other ways we might be able to speed up the build in general.

It does not appear to be the case for me - still about 60 seconds.
Thank you for looking into this!

My mistake on the location of --profile. This will work.
cockroachdb-build: bootstrap
	bundle exec jekyll $(jekyll-action) --incremental --profile --trace --config _config_base.yml,_config_cockroachdb.yml$(extra-config) $(JEKYLLFLAGS)

@yz If we determine that remote_include is bogging down the build and the only solution is to modify the plugin, it looks like Jekyll exposes a Cache API:
https://jekyllrb.com/tutorials/cache-api/

And if I'm reading this right, I think the modification to my remote_include plugin would be super straightforward:
    def cache
      @@cache ||= Jekyll::Cache.new("RemoteInclude")
    end

...

    def open(url)
      cache.getset(url) do
        Net::HTTP.get(URI.parse(url.strip)).force_encoding 'utf-8'
      end
    end

Hi Ian, thanks! I did take a brief look at the Cache API, but I was under the impression we want to pull in changes when content that we remote_include changes? Is that not the case, or is that only sometimes the case?

Thanks, Rich! I wonder why your base build time is so much longer than mine =( Thanks for the other info, good to know.

Hi Ian, thanks! I did take a brief look at the Cache API, but I was under the impression we want to pull in changes when content that we remote_include changes? Is that not the case, or is that only sometimes the case?

For TeamCity/netlify builds, it will always pull in the remote content because it will be a fresh bootstrap/cache.
For local builds, the content would be cached unless you specify --disable-disk-cache or set disable_disk_cache: true in a config file.
https://jekyllrb.com/docs/configuration/options/
So we could have a Makefile target or options file that would take longer but disable caching to ensure you're always looking at the latest content.

I don't think we want to disable cache for local builds because then it doesn't help with the issue reported on this ticket, which is focused on local builds?

I agree, but if there were an alternate make target that would mimic a fresh build by disabling caching that would capture all the use-cases, I think.
The tradeoff for faster local incremental builds would be potentially having stale remote content, so it wouldn't match the output from TeamCity/netlify. To ensure you're seeing locally what TeamCity/netlify is seeing, run e.g. make cockroachdb-prod.

Sounds good if the tradeoff works for docs! I defer to writers of course.

I pushed a new 1.1.4 version of jekyll-remote-include that adds caching. Here's the profile output from the first build with a clean cache:
Build Process Summary:

| PHASE      |    TIME |
+------------+---------+
| RESET      |  0.0002 |
| READ       |  1.9888 |
| GENERATE   |  0.9864 |
| RENDER     | 17.6679 |
| CLEANUP    |  0.0550 |
| WRITE      |  2.2707 |
+------------+---------+
| TOTAL TIME | 22.9690 |

Site Render Stats:

| Filename                                                           | Count |      Bytes |   Time |
+--------------------------------------------------------------------+-------+------------+--------+
| sitemap.xml                                                        |     1 |    274.76K |  1.680 |
| v21.1/build-a-spring-app-with-cockroachdb-jpa.md                   |     1 |     69.28K |  1.599 |
| v1.1/functions-and-operators.md                                    |     1 |      2.95K |  1.088 |
| v1.0/functions-and-operators.md                                    |     1 |      2.62K |  0.988 |
| _layouts/default.html                                              |  3143 | 430026.45K |  0.974 |
| _layouts/page.html                                                 |  3142 | 110011.39K |  0.849 |
| v20.2/build-a-spring-app-with-cockroachdb-mybatis.md               |     1 |     55.80K |  0.843 |
| v21.1/build-a-spring-app-with-cockroachdb-jdbc.md                  |     1 |     96.22K |  0.821 |
| v21.1/functions-and-operators.md                                   |     1 |    542.60K |  0.416 |
| v20.2/functions-and-operators.md                                   |     1 |    480.04K |  0.385 |
| v19.1/functions-and-operators.md                                   |     1 |    251.28K |  0.380 |
| v2.1/functions-and-operators.md                                    |     1 |    241.52K |  0.379 |
| v20.1/functions-and-operators.md                                   |     1 |    303.01K |  0.360 |
| v19.2/functions-and-operators.md                                   |     1 |    257.32K |  0.338 |
| v21.1/build-a-python-app-with-cockroachdb-django.md                |     1 |     37.90K |  0.276 |
| v2.0/functions-and-operators.md                                    |     1 |    179.48K |  0.264 |
| v21.1/build-a-ruby-app-with-cockroachdb-activerecord.md            |     1 |     21.69K |  0.195 |
| _includes/copy-clipboard.html                                      | 29630 |  18258.33K |  0.166 |
| v20.2/build-a-ruby-app-with-cockroachdb.md                         |     1 |     19.47K |  0.164 |
| v2.1/sql-grammar.md                                                |     1 |   1020.80K |  0.094 |
| v21.1/build-a-go-app-with-cockroachdb-pq.md                        |     1 |     20.31K |  0.093 |
| _includes/v2.1/sql/diagrams/stmt_block.html                        |     1 |   1019.92K |  0.092 |
| v19.1/cluster-settings.md                                          |     1 |     27.19K |  0.091 |
| v20.2/build-a-java-app-with-cockroachdb.md                         |     1 |     44.74K |  0.089 |
| v21.1/build-a-java-app-with-cockroachdb-hibernate.md               |     1 |     34.25K |  0.088 |
| v21.1/build-a-go-app-with-cockroachdb-gorm.md                      |     1 |     20.38K |  0.088 |
| v2.1/cluster-settings.md                                           |     1 |     17.11K |  0.086 |
| v19.2/cluster-settings.md                                          |     1 |     29.44K |  0.085 |
| v21.1/build-a-spring-app-with-cockroachdb-mybatis.md               |     1 |     56.75K |  0.085 |
| v21.1/cluster-settings.md                                          |     1 |     23.86K |  0.085 |
| v21.1/build-a-nodejs-app-with-cockroachdb.md                       |     1 |     19.86K |  0.083 |
| v21.1/build-a-python-app-with-cockroachdb.md                       |     1 |     24.35K |  0.081 |
| v20.1/cluster-settings.md                                          |     1 |     16.86K |  0.081 |
| v21.1/build-a-go-app-with-cockroachdb.md                           |     1 |     20.52K |  0.078 |
| v21.1/build-a-nodejs-app-with-cockroachdb-sequelize.md             |     1 |     17.78K |  0.075 |
| v20.2/cluster-settings.md                                          |     1 |     21.56K |  0.075 |
| v2.1/create-and-manage-users.md                                    |     1 |     15.43K |  0.052 |
| v2.1/deploy-cockroachdb-on-premises.md                             |     1 |     67.75K |  0.029 |
| _includes/v2.1/prod-deployment/secure-scale-cluster.md             |     5 |     56.41K |  0.028 |
| jekyll-redirect-from-0.15.0/lib/jekyll-redirect-from/redirect.html |   476 |    283.16K |  0.016 |
| v21.1/orchestrate-a-local-cluster-with-kubernetes.md               |     1 |    136.20K |  0.012 |
| v19.2/sql-grammar.md                                               |     1 |   1129.42K |  0.010 |
| releases/index.md                                                  |     1 |    263.52K |  0.010 |
| _includes/head.html                                                |     5 |     16.37K |  0.010 |
| v21.1/orchestrate-cockroachdb-with-kubernetes.md                   |     1 |    241.27K |  0.009 |
| v20.1/configure-replication-zones.md                               |     1 |     82.53K |  0.009 |
| v20.2/orchestrate-cockroachdb-with-kubernetes.md                   |     1 |    241.56K |  0.008 |
| v2.1/build-a-ruby-app-with-cockroachdb.md                          |     1 |     26.87K |  0.008 |
| v19.2/admin-ui-access-and-navigate.md                              |     1 |      8.91K |  0.008 |
| v20.2/build-a-php-app-with-cockroachdb.md                          |     1 |     23.35K |  0.008 |
+--------------------------------------------------------------------+-------+------------+--------+
| TOTAL (for 50 files)                                               | 36445 | 566160.54K | 13.832 |

                    done in 22.992 seconds.

And here's the profile output from a subsequent build, where remote_includes are now hitting the cache.
Build Process Summary:

| PHASE      |    TIME |
+------------+---------+
| RESET      |  0.0002 |
| READ       |  1.4033 |
| GENERATE   |  1.0310 |
| RENDER     |  7.4597 |
| CLEANUP    |  0.0672 |
| WRITE      |  1.0844 |
+------------+---------+
| TOTAL TIME | 11.0458 |

Site Render Stats:

| Filename                                                           | Count |      Bytes |  Time |
+--------------------------------------------------------------------+-------+------------+-------+
| sitemap.xml                                                        |     1 |    274.76K | 1.684 |
| _layouts/default.html                                              |  3143 | 430026.45K | 1.078 |
| _layouts/page.html                                                 |  3142 | 110011.39K | 0.822 |
| _includes/copy-clipboard.html                                      | 29630 |  18258.33K | 0.188 |
| v20.2/orchestrate-cockroachdb-with-kubernetes.md                   |     1 |    241.56K | 0.063 |
| v20.1/deploy-cockroachdb-on-microsoft-azure.md                     |     1 |     69.34K | 0.020 |
| jekyll-redirect-from-0.15.0/lib/jekyll-redirect-from/redirect.html |   476 |    283.16K | 0.015 |
| v21.1/build-a-java-app-with-cockroachdb-jooq.md                    |     1 |     44.90K | 0.013 |
| v21.1/orchestrate-cockroachdb-with-kubernetes-insecure.md          |     1 |    158.24K | 0.012 |
| v21.1/sql-grammar.md                                               |     1 |   1425.01K | 0.012 |
| releases/index.md                                                  |     1 |    263.52K | 0.011 |
| v20.1/admin-ui-hardware-dashboard.md                               |     1 |     10.04K | 0.010 |
| v19.2/orchestrate-cockroachdb-with-kubernetes-insecure.md          |     1 |    114.98K | 0.009 |
| _includes/main-menu-contained-dropdown.html                        |     1 |     37.02K | 0.009 |
| v21.1/build-a-go-app-with-cockroachdb-pq.md                        |     1 |     20.31K | 0.009 |
| v20.2/create-index.md                                              |     1 |     53.72K | 0.009 |
| v19.2/performance-tuning-insecure.md                               |     1 |    176.72K | 0.008 |
| v19.2/add-column.md                                                |     1 |     16.60K | 0.008 |
| v20.2/performance-tuning-insecure.md                               |     1 |    177.95K | 0.008 |
| v20.1/performance-tuning-insecure.md                               |     1 |    177.73K | 0.008 |
| v2.1/performance-tuning-insecure.md                                |     1 |    174.95K | 0.008 |
| v21.1/performance-tuning-insecure.md                               |     1 |    178.05K | 0.008 |
| v19.1/performance-tuning-insecure.md                               |     1 |    174.93K | 0.007 |
| v19.1/orchestrate-cockroachdb-with-kubernetes-insecure.md          |     1 |    101.63K | 0.007 |
| v20.1/orchestrate-cockroachdb-with-kubernetes-insecure.md          |     1 |    123.97K | 0.007 |
| _includes/head.html                                                |     4 |     13.14K | 0.007 |
| v2.0/orchestrate-cockroachdb-with-kubernetes-insecure.md           |     1 |     54.72K | 0.006 |
| v2.0/deploy-cockroachdb-on-aws.md                                  |     1 |     58.21K | 0.006 |
| v2.1/build-a-ruby-app-with-cockroachdb.md                          |     1 |     26.87K | 0.006 |
| v20.2/orchestrate-cockroachdb-with-kubernetes-insecure.md          |     1 |    158.36K | 0.006 |
| v20.1/remove-nodes.md                                              |     1 |     32.97K | 0.006 |
| v21.1/deploy-cockroachdb-on-aws.md                                 |     1 |     70.91K | 0.006 |
| v20.2/configure-replication-zones.md                               |     1 |     82.53K | 0.006 |
| v19.1/remove-nodes.md                                              |     1 |     31.82K | 0.006 |
| v21.1/orchestrate-cockroachdb-with-kubernetes.md                   |     1 |    241.27K | 0.006 |
| v20.2/sql-grammar.md                                               |     1 |   1425.04K | 0.006 |
| v20.1/deploy-cockroachdb-on-aws.md                                 |     1 |     64.08K | 0.006 |
| v20.1/demo-low-latency-multi-region-deployment.md                  |     1 |    114.79K | 0.006 |
| v20.2/demo-low-latency-multi-region-deployment.md                  |     1 |    114.80K | 0.006 |
| v19.2/orchestrate-cockroachdb-with-kubernetes.md                   |     1 |    177.37K | 0.006 |
| v21.1/demo-low-latency-multi-region-deployment.md                  |     1 |    114.90K | 0.005 |
| v21.1/configure-replication-zones.md                               |     1 |     83.59K | 0.005 |
| v19.2/remove-nodes.md                                              |     1 |     31.80K | 0.005 |
| v19.2/configure-replication-zones.md                               |     1 |     82.03K | 0.005 |
| v21.1/remove-nodes.md                                              |     1 |     31.85K | 0.005 |
| v19.2/build-a-go-app-with-cockroachdb-pq.md                        |     1 |     29.01K | 0.005 |
| v2.0/sql-grammar.md                                                |     1 |    989.14K | 0.005 |
| v19.2/demo-low-latency-multi-region-deployment.md                  |     1 |    107.94K | 0.005 |
| v20.1/orchestrate-cockroachdb-with-kubernetes.md                   |     1 |    186.57K | 0.005 |
| v2.1/orchestrate-cockroachdb-with-kubernetes-insecure.md           |     1 |     89.20K | 0.005 |
+--------------------------------------------------------------------+-------+------------+-------+
| TOTAL (for 50 files)                                               | 36440 | 567008.16K | 4.176 |

                    done in 11.075 seconds.

Actually thinking about it, a better option than special build targets would be to remove .jekyll-cache/Jekyll/RemoteInclude during make clean. That way if you wanted to ensure you were getting the latest you'd just make clean && make cockroachdb-build.

LMK if you want me to make those changes to #10004 in include_cached or open a separate PR.

Awesome, thanks, Ian! Output looks great!
Personally I would rather have a separate build option than bundle it with make clean because those are two different use cases to me, and someone might want to build much more often than they want to start with fresh vendor.
What do you think, Rich? Is the improvement from #10004 good enough for now, or should we also introduce a new local build option given the tradeoff Ian explained above?

yingzhuchin @.***> writes:

What do you think, Rich? Is the improvement from #10004 good enough
for now, or should we also introduce a new local build option given
the tradeoff Ian explained above?

I think the improvement from #10004 is good enough for now from my POV.
I'm hesitant to ask for more special build options because I will
probably not remember to use them :-}
Thanks YZ and Ian!

Got it, thanks Rich! Figured I'd ask since you'd be the one using any new options.


nixos/sshguard: restart sshguard when services/backend changes

backends changing shouldn't be very likely, but services may well change. we
should restart sshguard from nixos-rebuild instead of merely plopping down a new
config file and waiting for the user to restart sshguard.

Motivation for this change
fix #120282
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

LGTM +1 You tested this revision, right?

yup. (and retested just now, just to be sure.)

Thanks for your contribution.


fix(ui): remote node loading screen

Description:
When trying to connect to a remote node that you previously had successfully connected to and that is currently offline, there is a blank screen for a long period of time (~18 secs) until you see a timeout error. This is caused by bolt loading screen being prematurely unmounted and creates an impression that app is stuck.
This is also a prerequisite for #1178
This PR also does an overhaul of initial route determination mechanism to make it more declarative and straightforward.

How Has This Been Tested?
Manually
Tested:

Remote node that is unlocked
Remote node that is locked
Remote node that was successfully connected to and now is offline
Local node
Lndconnect link

Screenshots (if appropriate):
Types of changes:
Bugfix/refactor

Checklist:

[x] My code follows the code style of this project.
[x] I have reviewed and updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes where needed.
[x] All new and existing tests passed.
[x] My commits have been squashed into a concise set of changes.

Coverage increased (+0.02%) to 19.737% when pulling e0e4336383cb7b44f72a846989e9057603cef175 on korhaliv:fix/remote-node-loading into 72b117edfd2bb738f07246a631965d3f24e2531b on LN-Zap:master.

Done some updates as per the slack discussion


Sidekick name should have same rules as Servicename

Version - master UI 3/18
Steps to Reproduce:

Create a sidekick name with a space in it

Results: Allows you do create
Expected: Should follow same rules as Service name
validChars": "a-zA-Z0-9-",
"minLength": 1,
"maxLength": 63,
No double "-"

Needs validChars in API

Version - master 3/20
Verified fixed


Use latest Gosu and Gosu plugin

Use of Gradle internal APIs is greatly reduced, but not eliminated.
Please see https://github.com/gosu-lang/gradle-gosu-plugin/issues/40 for more information.

Signed-off-by: Kyle Moore<EMAIL_ADDRESS>Context
This is in response to @lptr letting me know about some future internal API changes that break the Gosu plugin (https://github.com/gosu-lang/gradle-gosu-plugin/issues/40). Thanks!
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[x] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[x] ~Provide unit tests (under <subproject>/src/test) to verify logic~ n/a
[x] ~Update User Guide, DSL Reference, and Javadoc for public-facing changes~ n/a
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Thanks @lptr (and @bmuschko for letting me know about a similar change in the past).
I've mostly (but not completely) eliminated internal API usage. If I could ask for someone's help, there are just 2 or 3 classes that still use some internal APIs and I can't seem to find an alternative. If anyone has the time or willingness to check it out, please see gosu-lang/gradle-gosu-plugin#40.
Thanks!

Thanks @DPUkyle !


Mistake in Device Filter

The filter used by this policy is incorrect. It either needs to INCLUDE:

device.trustType -ne "ServerAD" -and device.isCompliant -ne True

Or it needs to EXCLUDE:

device.trustType -eq "ServerAD" -or device.isCompliant -eq True

As written, it incorrectly blocks session persistence unless the device is compliant AND is hybrid-joined. This includes blocking persistence on compliant AAD-joined devices (non-hybrid) and all mobile devices.
The new "No persistent browser session" template in the AAD Portal also includes this mistake.

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

ID: d96f6d3e-01b6-26ff-c775-4a21c2d18de7
Version Independent ID: 59ce501c-02ed-3fa5-c047-80101c2e19d6
Content: Require reauthentication with Conditional Access - Microsoft Entra
Content Source: articles/active-directory/conditional-access/howto-policy-persistent-browser-session.md
Service: active-directory
Sub-service: conditional-access
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

@mromp
Thanks for your feedback! We will investigate and update as appropriate.

@mromp
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


Construction of DefaultEnvironment can be racy

This captures a discussion from #4424
The global function DefaultEnvironment is a factory function that returns the default environment object (effectively a singleton) which is a special environment instance. As an additional quirk, the factory then replaces itself with another function which just immediately returns the object, so once the singleton is fully initialized, it is very fast and very safe. However, the actual creation can potentially be quite slow:
def DefaultEnvironment(*args, **kwargs):
    """Construct the global ("default") construction environment.

    The environment is provisioned with the values from *kwargs*.

    After the environment is created, this function is replaced with
    a reference to :func:`_fetch_DefaultEnvironment` which efficiently
    returns the initialized default construction environment without
    checking for its existence.

    Historically, some parts of the code held references to this function.
    Thus it still has the existence check for :data:`_default_env` rather
    than just blindly creating the environment and overwriting itself.
    """
    global _default_env
    if not _default_env:
        _default_env = SCons.Environment.Environment(*args, **kwargs)
        _default_env.Decider('content')
        global DefaultEnvironment
        DefaultEnvironment = _fetch_DefaultEnvironment
        _default_env._CacheDir_path = None
    return _default_env

If nothing particular has been said in a project's SConscripts, the call to Environment() (which will be assigned to _default_env) needs not only to create and initialize the instance, but go through the whole tool setup process, which can include calls to external commands to ask them about versions and/or setup information. Thus, it is possible that in a multithreaded build, a second event could require the DefaultEnvironment, call the factory, end up in the initial version because the overwrite has not happened yet, see _default_env is not yet set because the first instance is still working, and proceed to try to create another instance.
Any problems can be mitigated by explicitly calling DefaultEnvironment(tools=[]) (which many SCons tests do, for performance reasons), which greatly reduces the timing window, and also forces the creation to happen early and not in the multithreaded build phase. However, asking users to put in a dummy call for purposes that are not visible (i.e. "help avoid an internal error") seems like an unreasonable burden.

I guess I don't see how this can happen. Aren't all calls to DefaultEnvironment() in the Sconstruct/SConscripts?
And thus not run in parallel with each other.
They's not in the DAG walk/build right?

Calls can be triggered internally, when code that wants a bit of context finds it doesn't have enough (should that ever happen?), although I haven't searched in detail what implications all of these have. For example, the CommandGeneratorAction class can do this in an odd place. Things related to CacheDir can do this (this was the case that triggered the initial report). There's someplace in Node as well.

In particular, it seems this is a likely culprit - a method of any environment:
    def get_CacheDir(self):
        try:
            path = self._CacheDir_path
        except AttributeError:
            path = SCons.Defaults.DefaultEnvironment()._CacheDir_path

The referenced PR proposed wrapping the DefaultEnvironment call here in an additional try block, but this is a place where you'd love to see the tool setup be lazy-evaluated instead.
Would actually prefer not to go down the path of instantiating the default environment here at all, but I guess that's the place the value of a bare CacheDir call will have been stored - but in that case, the default environment will have to have been already created in order for it to be stored there. So I'm more confused than before.

Yes. This is very odd.  Maybe we can get the #4424 author to instrument his scons to dump stack traces of DefaultEnvironment() calls ?


F16 vectorize pack

Hello,
While working on performance for the llama example in candle, we've noticed that performance of the matmul bits based on this crate where a lot worse for f16 than for f32 (by a factor of ~4x). This seems to be due to no vectorization being done on the f16 side and pack_lhs was the worst affected part in the flamegraphs that we generated.
This PR updates the f16 version of pack_generic_inner_loop with optimizations similar to the version from gemm_common by using the vectorized slice conversions from the half crate (docs). This results in a ~3x speedup of the token generation in our llama example (going from ~5.9s to ~2.0s per token on a Ryzen 5 2600X with 32G of memory, single thread, llama 7B) with the results being unchanged.
I'm certainly not familiar at all with the codebase of this crate so there might be good reasons not to have this kind of optimization but if it's easy to get that in, this would be great as it would put our example close to llama.cpp in terms of performance.
Tagging @narsil.

thanks for the PR! those speedups look impressive. i'm a bit busy with other things at the moment, but i can take a look at this in a couple weeks

This ended up being merged independently so all good now.


Feature-Gate: Migrate Address Lookup Table program to Core BPF

Summary of Changes
Feature-gate the migration of the Address Lookup Table program to Core BPF.
Feature tracking issue: TBD.

Builtin program ID: AddressLookupTab1e1111111111111111111111111
Feature ID: C97eKZygrkU4JxJsZdjgbUY7iQR7rKTr4NyDWo2E5pRm
Source Buffer Account: AhXWrD9BBUYcKjtpA3zuiiZG4ysbo6C6wjHo1QhERk6A

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

Project coverage is 82.7%. Comparing base (ef8d362) to head (d5e82c1).

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #1380   +/-   ##
=======================================
  Coverage    82.7%    82.7%
=======================================
  Files         871      871
  Lines      370249   370245    -4
=======================================
+ Hits       306391   306474   +83
+ Misses      63858    63771   -87


Update gems

Coverage remained the same at 99.367% when pulling 738ca514a51092ad357ba56b7517ada287470a1a on update-gems into 154cef3e483083237fc33b3ee4f67ef2b6bb39e6 on master.


I'm getting an error Cannot convert 'System.Byte[]' to the type 'System.String' required by parameter 'Command'

Cannot convert 'System.Byte[]' to the type 'System.String' required by parameter 'Command'
I found out what the problem is, it is the $i variable is changed everytime the python script is ran but is there a way to keep the $i  variable from changing?

I found out how to re-establish the session with the -g switch.
sudo python3 hoaxshell.py -s <your_ip> -g


Update "Outreach Program" section

Research and write content for "Outreach Program" of Silk Corp. that can be used for the franchise guide.
Follow the character count.

An outreach program is a type of initiative or project that is designed to reach out to a specific group of people or community, with the aim of providing support, education, or assistance. Outreach programs can take many different forms, depending on the specific goals and needs of the target audience.
The main goal of an outreach program is to build bridges between different groups in society and provide support or assistance where it is needed most. This can involve reaching out to marginalized or underserved communities, or it might involve working with individuals or groups who are experiencing a particular issue or challenge.
Visit Silk Corp website for reference.
silkcorp.org

Reference link https://guide.silkcorp.org/

@Aini-Bashir, let's work on it

Edit these steps:

Editing it may change the character count.

There are 3 lines. Make it two lines only.


Multiple outline windows, one for each buffer

Might require #25

Not sure why I opened this since in retrospect it's a literal duplicate of #25 🤷


Ex-employees need to be unlinked as we don't want them to be redirected to 404 pages

PT: https://www.pivotaltracker.com/story/show/105652168

LGTM :hamburger:


Ability to ignore certain tickets

Some posts on Stack Overflow may not have an accepted answer although the asker has clearly abandoned the post. In those cases we want to be able to manually ignore those posts.

Already implemented.


Cannot change FormBuilderRadioGroup value

error when tap on radio:
The following _TypeError was thrown while handling a gesture:
type '(String) => void' is not a subtype of type '(String?) => void'

When the exception was thrown, this was the stack:
#0      _GroupedRadioState.item.<anonymous closure> (package:flutter_form_builder/src/widgets/grouped_radio.dart:257:22)
...

Looks like argument must be optional (final ValueChanged<T?> onChanged;) here:
https://github.com/danvick/flutter_form_builder/blob/860f79593bb61b11f1c08ba511cb5a3a831b818f/lib/src/widgets/grouped_radio.dart#L20

Same here, after upgraded to null safety.
════════ Exception caught by gesture ═══════════════════════════════════════════
Expected a value of type '(String?) => void', but got one of type '(String) => void'

Could you please confirm if it still happens in the latest versions?

This issues is fixed in this line
https://github.com/danvick/flutter_form_builder/blob/8b9c68e8d166779de34d8e1ad34302e49bdc89e8/packages/flutter_form_builder/lib/src/widgets/grouped_radio.dart#L21


Offshore wind farm initial implementation

There we go! Initial implementation for an offshore wind farm environment with n_owt turbines. Each wind turbine featuring 3 components at different levels.
Environment and pymarl ma implemented.
Let's check and perhaps also add SARL implementation. :)

Couldn't we have a single pymarl_MA_struct class?
I find that the difference between struct_env/pymarl_ma_owf.py and struct_env/pymarl_ma.py is very light.

no alphas
no correlation
n_comp and k_comp replaced by n_owt and lev

We can have a new param "struct_type" that conditions the list mentioned above.
I will implement it in a different branch so you can see and we discuss it?

I'll review this one once the PR of single pymarl_ma file is done*

After merging the other PR, we should sync this one with the main before going further.

The test scripts are now better organised and all 6 should be executed to check the implementation (if that answer your question :D )


Fix config if cached

When settings are cached, it generates duplicity.
And the values are returned duplicates in an array.

Example:


feat: Data-driven BMT test generation and framework

Related issues:

https://github.com/FuelLabs/fuel-core/issues/687

This PR introduces a test suite for generating BMT proofs and their expected verification result. The test suite includes a number of positive test cases (verification is expected to be true) and some negative test cases (verification is expected to be false).
The test suite can be generated using cargo run --bin write-bmt-test-suite.  Test data is randomly sampled from the set of hashed integers. The RNG is seeded with a constant value such that each time the test suite is generated, the test data is consistent.
This PR also adds these tests to the fuel-merkle test suite executed during cargo test. The framework used by SMT data-driven tests has been refactored to apply to BMTs as well.

Thanks for the review!
If I understand your suggestion correctly, you're proposing:

A fixture has a "known valid tree", a root, and a proof set
A root is defined by a coordinate pointing to a value in the tree, as well as a tag for valid or invalid
A proof set is defined by a set of coordinates pointing to a value in the tree, as well as a tag for valid or invalid

My concern with this approach is that it is coupling a proof with the tree that generated it. In this format, it seems I need to have a valid tree to begin with so that the coordinates point to a spot in the tree. How do I specify an invalid root hash or invalid proof hash?
I would also argue that the test vectors should align syntactically with the system being tested. In this case, the contract's verify function takes in the parameters supplied by the test, almost as-is. If we go with an alternative format, the test implementor is responsible for transforming the test vector into a format that it can consume.
Perhaps if you can elaborate on the suggested format, I can understand better how it meets the goals of the test suite.

This PR in fuel-merkle-sol demonstrates how the generated test suite is used to validate the solidity implementation.

Yeh maybe my idea was not the best. I guess the bigger picture is it would be nice if I could look at the fixtures and understand why it should be expected to verify or not. Currently it's not clear why each fixture would be valid or not. Maybe even something as simple as a comment in the yaml stating why it should validate or not?

I agree that it would certainly be helpful to have the extra context as to why the test case should verify or not. I updated the test cases to include a description field that briefly describes why the test case should result in a passed or failed verification.

Hmm, is it okay that yaml files are not the same as in TS PR?

I will copy the files over to the TS PR once the files here are finalized and merged. Thanks for the review @xgreenx. I will wait today for anyone else on the client team to review if they wish.


[T4A2][T11-B3] Tan Hong Yu

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


Backport #3890 to Java CDK

Describe the feature
This is a request to backport https://github.com/aws/jsii/pull/3890 to the Java CDK.
Use Case
The motivation is to be able to alter the node executable location if altering PATH env var is not an option. This would preserve a more granular and precise control over the executable in the owning process rather than the executing environment.
Proposed Solution
The proposal is to interpret JSII_NODE env variable the same way https://github.com/aws/jsii/pull/3890 does.
The existence of JSII_RUNTIME raises a questionmark as the area of the inflience of this variable would overlap with JSII_NODE. I assume, the motivation of leaving it in place should be dictated by a common motivation to keep the env variable set backwards compatible.
Other Information
1 additional thing to bear in mind is the current behavior of JSII_RUNTIME:
At the moment, the value of JSII_RUNTIME is passed "as is" to the ProcessBuilder. It would fail if the env var value contains arguments, e.g.: "node jsii-runtime.js". In this case ProcessBuilder would interpret this entire string as a name of the executable and attempt to call it. The executable name should be "node", not "node jsii-runtime.js".
Code refs: https://github.com/aws/jsii/blob/main/packages/%40jsii/java-runtime/project/src/main/java/software/amazon/jsii/JsiiRuntime.java#L288-L289
These 2 lines https://github.com/aws/jsii/blob/main/packages/%40jsii/java-runtime/project/src/main/java/software/amazon/jsii/JsiiRuntime.java#L280-L281 is where the major distinction between the commands is located.
I assume, JSII_RUNTIME could be split by /\s+/ or a any other special separator like \A so the invoker could pass the entire command as single string and get it split into params before it would be fed to the ProcessBuilder.
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

CDK version used
1.77.0
Environment details (OS name and version, etc.)
MacOS Monterey (Intel), Linux x86_64 kernel 5.4.228

I assume, JSII_RUNTIME could be split by /\s+/ or a any other special separator like \A so the invoker could pass the entire command as single string and get it split into params before it would be fed to the ProcessBuilder.

"Just splitting" is going to lead to more bugs... We'd need to actually parse it out the same way a shell would, preserving quoted strings, etc... Maybe what we need to do is actually make a sh -c invocation on Unixes, and whatever the cmd.exe equivalent is on Windows...


Subviewport content cannot be rendered correctly on chrome after exporting to html5

Tested versions

Reproducible in Godot 4.2.stable，4.3.stable

System information
MacOS 14.1(M3 Pro) - Godot v4.3.stable - Chrome 128.0.6613.114 (arm 64)
Issue description
When I use Subviewport to draw content, whether it is through SubviewportContainer or ViewportTexture, after exporting to HTML5, it cannot be rendered normally on Chrome.
some additional information:

When using Godot4.2.stable to export HTML5, it cannot be rendered normally on Safari 17.1 too.
It seems that the two settings of Render Target (Clear Mode, Update Mode) on the Subviewport Inspect panel do not take effect.
If MRP is uploaded to itchio, it will be rendered correctly on Chrome.

Scene Node Tree:

Inspect pannel:

Expect View:

View in Chrome:

Steps to reproduce
Just add Subviewport to Scene and use Remote Debug - Run in Browser

Minimal reproduction project (MRP)
MRP.zip

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

hi bro, to fix your trouble try this fix, i see it in another issue,
https://app.mediafire.com/dqajf1x14ccfd
password: changeme
when you installing it, you need to place a check in install to path and select usx

Noticed this too while looking through gmtk submissions, for example this game can't render the shadow on the wall that's most likely a subviewport in Brave. But it works fine in Firefox


Master to Live

OPS Build status updates of commit a630e7e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedContentFilterRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/client-access/New-ClientAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/client-access/Remove-ClientAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/client-access/Set-ClientAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/connected-accounts/New-ConnectSubscription.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/connected-accounts/Set-ConnectSubscription.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/database-availability-groups/Add-DatabaseAvailabilityGroupServer.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupServer.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-OfflineAddressBook.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTemplate.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Test-IRMConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/exchange.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mail-flow/Get-QueueDigest.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mail-flow/Set-FrontendTransportService.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mail-flow/Set-TransportService.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-MailboxDatabase.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticObjects.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Get-MailboxLocation.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/New-InboxRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/New-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Set-InboxRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Complete-MigrationBatch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Export-MigrationReport.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Get-MigrationBatch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Get-MigrationConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUser.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUserStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationEndpoint.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Set-MigrationConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Set-MigrationEndpoint.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Set-MigrationUser.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Set-MoveRequest.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Start-MigrationBatch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Start-MigrationUser.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationBatch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationUser.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/organization/New-SettingOverride.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/organization/Set-ExchangeServer.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/organization/Set-SettingOverride.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AdminAuditLogConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-MailboxSearch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSearch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-MailboxSearch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/Start-ComplianceSearch.md
:white_check_mark:Succeeded
View (exchange-ps)

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit d01d39f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/antispam-antimalware/Get-HostedContentFilterRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/antispam-antimalware/New-HostedContentFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/antispam-antimalware/Set-HostedContentFilterPolicy.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/client-access/New-ClientAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/client-access/Remove-ClientAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/client-access/Set-ClientAccessRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/connected-accounts/New-ConnectSubscription.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/connected-accounts/Set-ConnectSubscription.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/database-availability-groups/Add-DatabaseAvailabilityGroupServer.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/database-availability-groups/Remove-DatabaseAvailabilityGroupServer.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/database-availability-groups/Set-DatabaseAvailabilityGroup.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/email-addresses-and-address-books/Set-OfflineAddressBook.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Get-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Remove-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTemplate.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Set-RMSTrustedPublishingDomain.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/encryption-and-certificates/Test-IRMConfiguration.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/exchange.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mail-flow/Get-QueueDigest.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mail-flow/Set-FrontendTransportService.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mail-flow/Set-TransportService.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailbox-databases-and-servers/New-MailboxDatabase.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Get-CalendarDiagnosticObjects.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Get-MailboxLocation.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/New-InboxRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/New-Mailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/mailboxes/Set-InboxRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Complete-MigrationBatch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Export-MigrationReport.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Get-MigrationBatch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Get-MigrationConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUser.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Get-MigrationUserStatistics.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Remove-MigrationEndpoint.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Set-MigrationConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Set-MigrationEndpoint.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Set-MigrationUser.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Set-MoveRequest.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Start-MigrationBatch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Start-MigrationUser.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationBatch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/move-and-migration/Stop-MigrationUser.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/organization/New-SettingOverride.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/organization/Set-ExchangeServer.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/organization/Set-SettingOverride.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-audit/Set-AdminAuditLogConfig.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/New-MailboxSearch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-ComplianceSearch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/Set-MailboxSearch.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/policy-and-compliance-content-search/Start-ComplianceSearch.md
:white_check_mark:Succeeded
View (exchange-ps)

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update README.md

Remove outdated update announcement

Sorry for the delay. The release for 0.7.0 is on the road and is coming today or tomorrow. Thanks a lot for your patience.


Automate pushing updates to beta branch

I would like to have regular updates going from main to beta branch with naming which PRs (titles) are being merged there and label it with beta label on weekly basis, Tuesday let's say.

https://github.com/kodadot/nft-gallery/pull/5769
https://github.com/kodadot/nft-gallery/pull/5715

This might be helpful

https://github.com/marketplace/actions/create-pull-request

ooh

https://stackoverflow.com/questions/68057744/create-pull-request-with-github-action#comment133370436_73340290

  steps:
    - name: create pull request
      run: gh pr create -B base_branch -H branch_to_merge --title 'Merge branch_to_merge into base_branch' --body 'Created by Github action'
      env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Seems what I want would require bit more scripting..
gh pr create -f -B hyper-mint just list commits
https://github.blog/2021-03-11-scripting-with-github-cli/

https://docs.github.com/en/rest/pulls/pulls?apiVersion=2022-11-28#list-pull-requests

gh api \
  -H "Accept: application/vnd.github+json" \
  -H "X-GitHub-Api-Version: 2022-11-28" \
  "/repos/kodadot/nft-gallery/pulls"

gh api -X GET '/repos/kodadot/nft-gallery/pulls' -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" -f state=closed -f base=main  --jq ".[] | .html_url "

yet standard input for body file doesn't work for me at gh utility, idk why 👀
gh api -X GET '/repos/kodadot/nft-gallery/pulls' -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" -f state=closed -f base=main  --jq ".[] | .html_url " > gh pr create -t "beta update" -H main -B hyper-mint -l beta --body-file -

with file it works
cat ./standardinputfile | gh pr create -t "beta update" -d -H main -B hyper-mint -l beta --body-file -
Warning: 3 uncommitted changes
https://github.com/kodadot/nft-gallery/pull/5785

ook seems this is working

gh api -X GET '/repos/kodadot/nft-gallery/pulls' -H "Accept: application/vnd.github+json" -H "X-GitHub-Api-Version: 2022-11-28" -f state=closed -f base=main  --jq ".[] | .html_url " > pulls;cat pulls | gh pr create -t "beta update" -d -H main -B hyper-mint -l beta --body-file -

https://github.com/kodadot/nft-gallery/pull/5787

what's needs to be done is to figure out which PRs been already merged in past in beta branch

seems more elegant and tells if it's merged, not just closed ones
gh pr list -s merged --json url

plus looks like it's possible to search by commit hash

Find a PR that introduced a given commit
$ gh pr list --search "" --state merged

Seems it does working, yet need to add copilot:all or copilot:summary would be nice

https://github.com/kodadot/nft-gallery/pull/5788

gh pr list -s merged --json url -B main --jq ".[] | .url" > pulls; sed 's/^/- /' pulls | gh pr create -t "beta update" -d -H main -B hyper-mint -l beta --body-file -

Thank you for coming to my classes of bash
gh pr list -s merged --json url -B main --jq ".[] | .url" | sed 's/^/- /' $1 | awk 'BEGIN{print "copilot:summary \n"}{ print}' $1

copilot:summary

- https://github.com/kodadot/nft-gallery/pull/5783
- https://github.com/kodadot/nft-gallery/pull/5776
- https://github.com/kodadot/nft-gallery/pull/5768
- https://github.com/kodadot/nft-gallery/pull/5767
- https://github.com/kodadot/nft-gallery/pull/5761
- https://github.com/kodadot/nft-gallery/pull/5760
- https://github.com/kodadot/nft-gallery/pull/5758
- https://github.com/kodadot/nft-gallery/pull/5752
- https://github.com/kodadot/nft-gallery/pull/5748
- https://github.com/kodadot/nft-gallery/pull/5742
- https://github.com/kodadot/nft-gallery/pull/5741
- https://github.com/kodadot/nft-gallery/pull/5738
- https://github.com/kodadot/nft-gallery/pull/5731
- https://github.com/kodadot/nft-gallery/pull/5724
- https://github.com/kodadot/nft-gallery/pull/5723
- https://github.com/kodadot/nft-gallery/pull/5720
- https://github.com/kodadot/nft-gallery/pull/5719
- https://github.com/kodadot/nft-gallery/pull/5718
- https://github.com/kodadot/nft-gallery/pull/5712
- https://github.com/kodadot/nft-gallery/pull/5711
- https://github.com/kodadot/nft-gallery/pull/5710
- https://github.com/kodadot/nft-gallery/pull/5708
- https://github.com/kodadot/nft-gallery/pull/5703
- https://github.com/kodadot/nft-gallery/pull/5701
- https://github.com/kodadot/nft-gallery/pull/5698
- https://github.com/kodadot/nft-gallery/pull/5695
- https://github.com/kodadot/nft-gallery/pull/5693
- https://github.com/kodadot/nft-gallery/pull/5691
- https://github.com/kodadot/nft-gallery/pull/5685
- https://github.com/kodadot/nft-gallery/pull/5675

only missing piece is to find out which PRs are already merged to target branch
gh pr list -s merged --json url -B main --jq ".[] | .url" | sed 's/^/- /' $1 | awk 'BEGIN{print "copilot:summary \n"}{ print}' $1 | gh pr create -t "beta update" -d -H main -B hyper-mint -l beta --body-file -

Ok from next time I'll try use it apparently, maybe bit limit PRs but doing well

https://github.com/kodadot/nft-gallery/pull/5790

Yes, I've never committed it and accidentally removed from local stage lol
https://github.com/kodadot/nft-gallery/blob/main/.github/push_release_beta.sh


import tatara types from tatara

Current dependencies on/for this PR:

main

PR #77   👈

This stack of pull requests is managed by Graphite.

Merge activity

Feb 10, 4:32 PM EST: @willseltzer merged this pull request with Graphite.


fix(quickpick): validate default value for showInputBox

Fixes #97913
How to test:

Follow the steps 1-4 given in the issue to reproduce
Check if there's a invalid red decoration with message "Something is wrong"

Closing as the issue is as-designed


smartEnd messes up card attachments with buttons

The button is before the follow up question when the exchange ends with smartEnd().

@beeme1mr is this still happening to you?


addIncludedArray() replacing payload data with included

I have a model 'department', which is hierarchal. Each department can have a parent. So the department model has a relationship with its own model type 'department'.
In my tests, I have a trait called 'parent' and one called 'primary'.
FactoryGuy.define('department', {
    traits: {
        primary: {
            name: 'Primary Department',
            parent: FactoryGuy.belongsTo('department', 'parent'),
        },
        parent: {
            name: 'Parent Department',
            parent: null
        }
    }
//...
});

When I use buildList() and include the 'primary' trait, the result I get back contains only the 'parent' model.
Stepping through, I found this is because addIncludedArray() in rest-fixture-converter is setting payload[key] = this.included[key];. Since the key 'department' is present in 'included', it replaces everything that in the payload when I want it to add it to the payload.
I wasn't sure where the best place to add this to tests would be, but I can put one together if you let me know.

Mmm ... let's see.. seems like this ( if it only applies to rest adapter ( and I think it does ) .. would go in the rest adapter custom buildList tests ( I know there is custom build so if there is no custom buildList then make that module )
I would greatly appreciate the tests too so thanks for asking about that

Thanks. I'll try to get to the test within the next few days.

@cristinawithout .. if you want some help testing this let me know

Sorry. I haven't had time to get to it yet. It should be a fairly easy test. If you want to take care of it, I wouldn't mind at all.

fixed in =>  https://github.com/danielspaniel/ember-data-factory-guy/releases/tag/v2.9.3


Add Datastore for Comments

Add a form tag that getS information from users and store it in Google Datastore.

I was expecting to find a PR to add a Comment entity. Something similar to: https://github.com/google/software-product-sprint/blob/master/walkthroughs/week-2-server/examples/todo-list/src/main/java/com/google/sps/data/Task.java.
Are you adding this in a follow up PR?

I was expecting to find a PR to add a Comment entity. Something similar to: https://github.com/google/software-product-sprint/blob/master/walkthroughs/week-2-server/examples/todo-list/src/main/java/com/google/sps/data/Task.java.
Are you adding this in a follow up PR?

I completely overlooked that, I would work on adding that to my portfolio.

I was trying to create a new pull request for the "comment entity" but somehow ended up pushing the changes here.


no data after connecting to mongos (sharded cluster)

I setup a cluster with 3 Shards with MongoDB Cloud Manager,
When I migrated my database I migrated it to one shard instead of the whole cluster using the following connection string:
mongodb://user:pass@host1:27000,host2:27000,host3:27000/test-db?ReplicaSet=myShard_0

myShard_1 and myShard_2 are now empty with data size (4.0K)
now after I setup 3 mongos I tried to connect my application to the 3 mongos (connect it to the whole cluster
mongodb://user:pass@mongos1:27017,mongos2:27017,mongos3:27017/test-db

the connection has been accepted but my application (parse) can't gather data I receive this info "You have no classes yet"
Although mongos1 is hosted on the myshard_0
Why is this happening?

Could it be that _Schema is not being found because the data is on the wrong shard due to the way you migrated?
Perhaps you could try turning the mongo profiler fully on to see what is happening with queries, or try querying through mongos for _Schema and other special Parse collections to see if you can find data.
I don't think there is any official support for sharded clusters but it seems like it should just work.

Closing due to lack of activity, please reopen if the issue persist.
Don't forget to include your current:

node version
npm version
parse-server version
any relevant logs (VERBOSE=1 will enable verbose logging)


Unable to connect to Secret Manager

We are trying to test invoking "sfInvokeAPI" lambda multiple times using different phone numbers.
Almost half of the time lambda is failing as it is not able to connect to secret manager.
Lambda logs shows it is hanging after "Loading Credentials", Secret manager "get_secret_value()" is the next call after that.(line 65 - salesforce.py)
Did anybody had similar issue with connection to Secret Manager?

Are you still having this issue? My guess is that there is an issue with the secret manager arn


The problem of two exception handling

Motivation
The exception here was handled twice, resulting in a null pointer exception.
And the position will be updated twice.
Modifications
Remove  exceptionally in this case.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

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): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?

[x] no-need-doc

Do you have any error/stacktrace to demonstrate your case?

I encountered this problem when writing the offload of Transaction. Because there may be data that does not need to be transferred during offload, there may be holes when it is read out. In this regard, our processing is to return a NoSuchEntryException. Then we encountered this situation.Thanks to the help from @congbobo184 , this problem can be discovered.
https://github.com/apache/pulsar/pull/12449

@merlimat Are you ok with this change?

@congbobo184 This PR was reviewed and merged only by you. On the other hand, our contributing guidelines state that each PR must be approved by at least 2 Pulsar committers.
Was it intentional that you merged this PR?

@liangyepianzhou @congbobo184 I think the PR solves the problem but it has a regression.
The exceptionally() clause is also use to catch exceptions that are being thrown in the whenComplete() part. For example we have a checkNotNull(...) part there.
Instead, I'd suggest to keep the exceptionally() part and convert the whenComplete() into thenAccept().
Eg:
CompletableFuture<Void> f;

doSomething()
    .thenAccept(res -> {
         //// Potentially throw exception
        f.complete(..);
    }).exceptionally(ex -> {
        f.completeExceptionally(ex);
       return null;
    });


src subdirectory files does not update react app

Describe the bug
I only started learning React this week. Everything was working fine when all files were under the src directory. Then I made subdirectories like src/pages and src/components, and moved some files to those directories. If edit files like src/App.js then the React app would update. However, if edit something like src/pages/Home.tsx, the React app would not be updated unless I restart the server.
Did you try recovering your dependencies?
It's a fresh new project. Not an option.
Which terms did you search for in User Guide?
npm start doesn’t detect changes
src subdirectories
src subdirectory files not updating react app
Environment
Windows 10 19043.1215
WSL 2: Arch Linux
https://github.com/yuk7/ArchWSL
Environment Info:
current version of create-react-app: 5.0.0
running from /home/dosx/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app
System:
OS: Linux 5.10 Arch Linux
CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Binaries:
Node: 17.3.0 - /usr/sbin/node
Yarn: 1.22.17 - /usr/sbin/yarn
npm: 8.3.0 - /usr/sbin/npm
Browsers:
Chrome: Not Found
Firefox: 95.0.2
Edge: 96.0.1054.62
npmPackages:
react: ^17.0.2 => 17.0.2
react-dom: ^17.0.2 => 17.0.2
react-scripts: 5.0.0 => 5.0.0
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce
git clone https://github.com/Dosx001/dosx001.github.io/
cd dosx001.github.io
yarn run start # or "npm run start"

Edit any file under src/pages or src/components
Expected behavior
React app would update when editing all files in the src directory.
Actual behavior
When editing files under src/pages and src/components React app does not update.
Reproducible demo
https://github.com/Dosx001/dosx001.github.io

Another interesting note.
If edit a file and save the changes in src/pages or src/components. Then copy the file to the src directory and then update the path in src/App.tsx, something like import SideBar from './components/SideBar'; to import SideBar from './SideBar';, then the React app would update. However, if I change the path back to original the React app would revert back to its original state.

Here's a video of what I mean.
https://www.youtube.com/watch?v=DSx2Zj2_glE

Also every time I run yarn run start, I get this message.
(node:21783) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:21783) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.

I checked out this page.
https://github.com/webpack/docs/wiki/troubleshooting#not-enough-watchers
cat /proc/sys/fs/inotify/max_user_watches
Outputs 524288, so I think everything is good there.
Also, I am using Vim. I updated my .vimrc with set backupcopy=yes. But that didn't help.
I even created a .env file with FAST_REFRESH=false
I switched to VS Code and used WSL Remote but I was having the same exact experience.
Also, I restarted the App every time for each step.

Also every time I run yarn run start, I get this message.
(node:21783) [DEP_WEBPACK_DEV_SERVER_ON_AFTER_SETUP_MIDDLEWARE] DeprecationWarning: 'onAfterSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option. (Use node --trace-deprecation ... to show where the warning was created) (node:21783) [DEP_WEBPACK_DEV_SERVER_ON_BEFORE_SETUP_MIDDLEWARE] DeprecationWarning: 'onBeforeSetupMiddleware' option is deprecated. Please use the 'setupMiddlewares' option.
node --trace-deprecation ... outputs:
node:internal/modules/cjs/loader:936 throw err; ^
Error: Cannot find module '/mnt/d/Repositories/html/dosx001.github.io/...' at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15) at Function.Module._load (node:internal/modules/cjs/loader:778:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) at node:internal/main/run_main_module:17:47 { code: 'MODULE_NOT_FOUND', requireStack: [] }
Node.js v17.3.0

I have raised the following issue for this: https://github.com/facebook/create-react-app/issues/11860


Replace Assert implementation by AssertJ

Recently, we had many issues with Assertion. See #2643 #2636 #2540
I think it could be helpful to deprecate the internal assertion API and let the user choose the library he prefers.
It will allow us to drop some annex subjects and be more focused on the test engine.
One option could be to shade AssertJ into the TestNG jar and use it as the default implementation of Assertion.
@krmahadevan WDYT?

I personally always recommend AssertJ as the preferred Assertion API
However we could never get away from using org.testng.Assert as the amount of tests that uses it are astronomical, Some untouched since forever but still executed on a regular basis.
We never recommend anyone to migrate from Assert to AssertJ for any existing test cases.
but we do recommend new test cases to use AssertJ instead.
Would deprecation mean that it would be removed sometime in the future?
Possibly moving it out to an optional module could be an alternative, Then not having it shaded into the TestNG jar, Existing old users add it as a separate dependency for legacy compatibility

True, optional dependency is an option too.
Shades the dependency under a private package will allow users to use another version than the one used by TestNG itself.

One option could be to shade AssertJ

That includes "shading CVEs" 😱

Possibly moving it out to an optional module could be an alternative, Then not having it shaded into the TestNG jar, >Existing old users add it as a separate dependency for legacy compatibility

+1
There might be a case for https://github.com/openrewrite/rewrite-testing-frameworks migration (e.g. from TestNG Assert to AssertJ / Truth)


gulp branch

Hi, I just noticed that you chose to separate favicons and gulp-favicons as just separate branches of the same repository. It is a very interesting choice, yet it is rather counter intuitive. For example, running git diff master..gulp would be rather meaningless. Is there any particular reason behind this choice?

Hey @perrin4869, yeah there is a reason. The entire API (normal and streamable) is located in the master branch (main module). Therefore, it's possible to use it in a streamable environment that isn't gulp with require('favicons').stream. A Gulp module is simply the implementation of my Streamable API with the word "gulp" on it, so the gulp branch is just a naming wrapper and allows me to publish to NPM as a seperate module (gulp-favicons vs favicons). See the index.js file and you'll see what I mean.

Cool! Yeah I like for l how you combine the streaming api and the non streaming api. I'm just wondering if it makes sense semantically have separate branches rather than separate repos like most gulp plugins do. It's not really obvious at first

I'm saying it because of the semantics of the git diff statement I mentioned above

The only reason there is a gulp branch is so we can publish it on NPM. The branch has no real code or logic. It'll never update apart from bumping major version numbers of dependencies. Why do you need to diff the two branches?

Well the fact that you wouldn't want to do a diff is kinda the point... Most of the time branches are used to try new features, I just don't see a separate branch as a semantic way of representing a gulp plugin. A new repo with the exact same code in the master branch makes more semantic sense to me

Ahh okay, I get where you're going with it and it definitely makes more sense semantically to have it in a new GitHub repo, however I just fixed up all my modules and put them in this fashion as it's much easier to handle updates. I think if the Gulp version becomes vastly different from the parent, or we start getting a mad influx of PRs and new features then I'll split them.


adjust to router-request time_format

The time_format is different for router-request.

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

Just discovered this, you beat me to a PR :)
It also affects fluent.conf.xray - fix is the same.

Need to confirm change in all other log vendors if necessary