refac/ single->double quotes

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

18 of 18 (100.0%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.957%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2628

Relevant Lines:
2635

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

19 of 19 (100.0%)  changed or added relevant lines in 9 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 98.957%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2628

Relevant Lines:
2635

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

69 of 69 (100.0%)  changed or added relevant lines in 18 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0003%) to 98.957%

Totals

Change from base Build<PHONE_NUMBER>:
0.0003%

Covered Lines:
2629

Relevant Lines:
2636

💛  - Coveralls

Codecov Report

Merging #225 (3188628) into main (7b36334) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head 3188628 differs from pull request most recent head b7759ee. Consider uploading reports for the commit b7759ee to get more accurate results

@@           Coverage Diff           @@
##             main     #225   +/-   ##
=======================================
  Coverage   99.74%   99.74%
=======================================
  Files          67       67
  Lines        3138     3139    +1
  Branches      533      533
=======================================
+ Hits         3130     3131    +1
  Misses          8        8

Impacted Files
Coverage Δ

algorithms/sets/knapsack-problem/Knapsack.js
100.00% <ø> (ø)

algorithms/sorting/SortTester.js
100.00% <ø> (ø)

algorithms/sorting/bubble-sort/BubbleSort.js
100.00% <ø> (ø)

algorithms/sorting/counting-sort/CountingSort.js
100.00% <ø> (ø)

algorithms/sorting/heap-sort/HeapSort.js
100.00% <ø> (ø)

algorithms/sorting/insertion-sort/InsertionSort.js
100.00% <ø> (ø)

algorithms/sorting/merge-sort/MergeSort.js
100.00% <ø> (ø)

algorithms/sorting/quick-sort/QuickSort.js
100.00% <ø> (ø)

algorithms/sorting/quick-sort/QuickSortInPlace.js
100.00% <ø> (ø)

algorithms/sorting/radix-sort/RadixSort.js
100.00% <ø> (ø)

... and 46 more

Continue to review full report at Codecov.

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

69 of 69 (100.0%)  changed or added relevant lines in 18 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0003%) to 98.957%

Totals

Change from base Build<PHONE_NUMBER>:
0.0003%

Covered Lines:
2629

Relevant Lines:
2636

💛  - Coveralls


version control: remove .vscode

Dir .vscode is accidentally added to version control, cause annoying prompt.

https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/labring/sealos
this dir is using vscode

https://vscode.dev/redirect?url=vscode://ms-vscode-remote.remote-containers/cloneInVolume?url=https://github.com/labring/sealos
this dir is using vscode

Maybe this link is another request, on main branch .vscode is already been deleted by accidentally added user.


Add string permutations to C++

Description
Recursive string permutation program in C++
Fixes #401
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] I have read the contribution guidelines before making this PR.
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented in my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation (Language folder or any other readme instructed to)
[x] My changes generates no new warnings
[x] I have added tests that prove my fix is effective or that my feature works

@kaustubhgupta sorry about that. This PR does not mess with other READMEs


Is there an option to show move number on top of stones?

... similar to the about diagram. It'll be great if ngGo will support:
  Player.showMoveNumbers(); // show number for all stones
  Player.showMoveNumbers(fromMove, toMove); // for a range of moves
  Player.showMoveNumbersFromLastComment(); // from previous comment to current move

I like how you used an AlphaGo game :)
I will look into this after my holiday.
On Tue, Mar 22, 2016, 20:38 Horace Ho<EMAIL_ADDRESS>wrote:

[image: move_numbers]
https://cloud.githubusercontent.com/assets/6657/13947235/3c05b5dc-f054-11e5-9ad7-812b8033e17b.png
... similar to the about diagram. It'll be great if ngGo will support:
Player.showMoveNumbers(); // show number for all stones
Player.showMoveNumbers(fromMove, toMove); // for a range of moves
Player.showMoveNumbersFromLastComment(); // from previous comment to current move
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/adambuczynski/ngGo/issues/34

@horaceho It appears that this is already implemented.
There exists a method Player.showMoveNumbers(fromMove, toMove)
Defaults to all moves, if no parameters given.
There is no support for showing move numbers from the last comment.
You will have to manually loop the nodes and find the last comment (or remember it) and then supply that value as fromMove.
Let me know if you have further questions. This functionality is also testable in the demo.


Ability to store pre-existing values?

In cases where the up() method performs a static change/overwrite across a dataset there is no great way of knowing how to revert it in the down() method. Exposing an interface for the up() method to store the preexisting values as part of state could prove very useful., but it also substantially increases the risk of misuse and very large state sets.
For example, consider the following:
exports.up = async () => {
  for (user in users) {
    user.lastname = 'Doe'
    await user.save()
  }
}

exports.down = async () => {
  for (user in users) {
    user.lastname = '???' // Whelp. We dont know what the name was prior to the migration
    await user.save()
  }
}

Similarly, it could be useful to store an ID for an ambiguous entity that was created in the migration, e.g.
exports.up = async () => {
  const { id } = await user.create({ name: 'Donald Duck' })
  return id
}

// We don't want to remove ALL users named Donald Duck, just this particular one.
// Now imagine if it were possible to refer to the thing returned by `up()`:
exports.down = async ({ upValue }) => {
  await users.remove(upValue)
}


bundle_libraries.sh: unsetenv LD_PRELOAD

这个 PR 实现什么功能/修复什么问题:
RT
是否需要 backport 到之前的 release 分支:
NONE
/cc @yousong

/area util

Codecov Report

Merging #4469 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #4469      +/-   ##
=========================================
+ Coverage    6.83%   6.84%   +<.01%
=========================================
  Files         521     521
  Lines       88434   88408      -26
=========================================
+ Hits         6048    6050       +2
+ Misses      81880   81853      -27
+ Partials      506     505       -1

Flag
Coverage Δ

#aFlag
6.84% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/networks.go
0.54% <0%> (ø)
:arrow_up:

pkg/compute/models/guestnetworks.go
0.22% <0%> (ø)
:arrow_up:

pkg/appsrv/response.go
69.23% <0%> (+3.07%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm
/approve


Feature/update oracle

The example oracle should include an end to end test in truffle. No need to use a webserver to fulfill the request, but different addresses should be used to model the signing behavior of daemons.

We also want a new base event store which sets addresses for permissions when created, that cannot be altered. We don't trust either of the current event stores.

@OR13 can you be more specific? I tested the contract deployed in migrations with the watcher I set on it - did you see that?


Support Swift 3 Xcode Beta 6

Solves issue #132

I don't have access to my computer right now so I can't parse this but is the Travis CI build failing the result of the tests being written in Swift 1 and 2?

It's weird, I'm kind of busy right now to check, but will do it later today, additionally I will check if everything works ok in Beta 5.

For sure! Share what you find!

I'm going to need some help here, I'm totally ignorant about Travis CI, but it looks like the build is being done with Xcode 7? 🤔... my last commit fixes everything in the project, it compiles good under Xcode Beta 6, including the test, etc.

Hey @ed-mejia. Travis CI (continuous integration) is a tool that facilitates the deployment of safer code. It does this by checking your updated code from your app I'll request against the tests that you have previously  written for your code. One obvious benefit of doing this is that your code is always tested against the tests you have in case you forget to manually run all tests yourself..
Now onto what may be causing the failure. If you look at the travis.yml file that is in the root of SwiftValidator, you'll notice that it's environment uses the Xcode 7.1 osx image. Swift 3 beta 6 isn't available till Xcode 8. I'm guessing that's why it fails.

Travis still failing I see. I'm gonna take a look myself shortly.

Hey @davepatterson thanks for the info about travis 👍 , I was trying to get it work, but I'm done 😫
If you could check it would be nice 👍

Great work @ed-mejia & @davepatterson! Any progress on getting this merged so the library can officially support Swift 3?

Travis keep faling even in this latest PR https://github.com/jpotts18/SwiftValidator/pull/146

Yeah, I've been meaning to look into Travis issue but I've been bombarded with work lately. I'll be sure to take another shot sometime this week.

Hi! I would love to request all Rule classes to be opened with open accessor. Many of us will need create own project specific Rules. It's not possible override classes or inherit them if they are set as public because Swift 3 limit public scope to module only. @ed-mejia


Randomized Walkspeed

Randomizes walk speed between 1% and config.walk_offset_percent_max if config.walk_random = true

#3943 is similar. I would appreciate input.

Haven't looked at the code, but judging by the configuration i would prefer #3943 min/max walk step then using %

@jimmywarting the initial code used a fraction to alter set walking speed. Per a request, I switched to a max and min setup.

Matter of preference I suppose, figured this was the shortest and cleanest way to do it, it would work in either case though the min/max step walk values in #3943 are good as well. In this case 1% is the minimum

You could remove the bool and just have folks set percentage to 0 if they do not want variance - but you'd need to make the minimum variance percentage 0.

I set the minimum to 1% since we are using a switch in the config for true/false ("walk_random", true), if set to false it's back to default (0)

imported the random module since importing just the function wasn't enough (for uniform)

This might not be necessary now that #3943 has been merged. I'll let you guys decide and @BreezeLo, please close this PR if not necessary anymore.

Just saw @TheSavior, will close in about ~4 hours, just want to see if anyone else has any input on this one - I'm satisfied with #3943

@BreezeLo There's more than one way to solve most problems =]
in #3943
walk_min = 2
walk_max = 4
is the same as in here
walk = 200
walk_offset_percent_max = 0.02
Live dangerously I want to set my walk to 200 =P

That's because there is a mistake here, should of been
self.speed = speed + speed * random.uniform(0.01, self.bot.config.walk_offset_percent_max) ;) updated


html p tag being displayed

As you can see, the p tag is being displayed. Should be an easy fix.

I'm working on this now.

This can be solved by casting the HTML content (in Security::lostpassword()) to an HTMLFragment:
'Content' => DBField::create_field('HTMLFragment', '<p>' . _t(... //etc

@kinglozzer This might fix this specific instance of the issue, but as you can see (in e.g. #6537), there are several places thoroughout the cms/framework where the seemingly "same" issue occurs. Do you think all instances of this issue be approached using the same fix, or is there a root cause at a higher level (I haven't had time to dig, but I've been helping those who have).

is this 4.x or 3.x?

If you're sending HTML to the templates then you have to cast it as HTMLText in some way.

The best solution is have the <p> tags in the template and the content sent as plain text.

This was an issue in 4 (dev-master) also. The markup comes from the YML language files themselves and obviously worked in v3. Unless someone is going to repace all markup in language files and modify calling logic everywhere, I'd suggest there's something awry at a higher level.

There isn’t a one-size-fits-all fix here, unfortunately. Stuff that goes through the template engine needs to be cast to HTMLFragment (or HTMLText in 3.x), and stuff that is returned to React for it to render will need some other solution (maybe https://github.com/silverstripe/silverstripe-framework/issues/6537#issuecomment-274036548).
We’ll likely have to fix these one-by-one as they come up. Regressions from 3.x may have been caused by casting API changes (https://docs.silverstripe.org/en/4/changelogs/4.0.0/#explicit-text-casting-is-now-enforced-on-all-template-variables).
Anyway, the bug described in this ticket should be pretty easy to solve. @hoKRa1, do you fancy submitting a PR with this change?

@phptek the template is behaving as expected here. This does need to be fixed one-by-one.
PHP should not be rendering HTML.
@kinglozzer even casting as HTMLFragment is dangerous because the content inside the <p> needs to be HTML encoded in that case.
If we don't have HTML in our strings, then that's the best and safest way to pass things to the template

This is not a problem in SS4.
Unfortunately, Silverstripe CMS 3 has entered limited support in June 2018. This means we'll only be fixing critical bugs and security issues for Silverstripe CMS 3 going forward.
You can read the Silverstripe CMS Roadmap for more information on our support commitments.
If someone is encountering this problem in SS4, please leave some replication steps and we can reopen.


OpenEXR static build not creating libIlmImf.a

Setting BUILD_SHARED_LIBS to OFF seems to create a static library for ilmThread, but not
for IlmImf.
Environment:
	Docker container based on Centos:7
	updated
	'devtoolset-11' installed
	'scl enable devtoolset-11 bash' executed
	OpenSSL 1.1.1l installed  built/installed
	CMake  3.29.5 built/installed
	Freetype 2.11.0 built/installed

Steps to reproduce:
	wget https://github.com/AcademySoftwareFoundation/openexr/releases/download/v3.2.4/openexr-v3.2.4.tar.gz
	mkdir openexr-v3.2.4
	tar zxvf openexr-v3.2.4.tar.gz -C /openexr-v3.2.4
	rm openexr-v3.2.4.tar.gz
	cd /openexr-v3.2.4
	cmake -DCMAKE_CXX_STANDARD=17 -DBUILD_SHARED_LIBS=0 .
	make -j$(nproc)
	make install

If you then execute:
	find / -name "libIlm*"

Returns:
	/usr/lib64/libIlmImf.so
	/usr/lib64/libIlmThread.so.6
	/usr/lib64/libIlmThread.so.6.0.0
	/usr/lib64/libIlmImf.so.7
	/usr/lib64/libIlmImf.so.7.0.0
	/usr/local/lib64/libIlmThread-3_2.a
	/usr/local/lib64/libIlmThread-3_2.so.<IP_ADDRESS>
	/usr/local/lib64/libIlmThread-3_2.so.31
	/usr/local/lib64/libIlmThread-3_2.so
	/usr/local/lib64/libIlmThread.so
	/src/lib/IlmThread/libIlmThread-3_2.a

Expected behavior:
A libIlmImf.a library should be created.
I.e., it creates libIlmThread-3_2.a, but not an ILMImf equivalent.

The libraries in /usr/lib/* appear to be from an older installation. Those should not be generated by your cmake invocation of v3.2.4. Are you picking those up from a base image somewhere?
OpenEXR v3.2.4 does not build any libraries with Imf in the name, that term was retired in the v3.0 release.

The desire to reference IlmImf comes from this error when building an app using OIIO:
/opt/rh/devtoolset-11/root/usr/libexec/gcc/x86_64-redhat-linux/11/ld: /OpenImageIO-<IP_ADDRESS>/dist/lib64/libOpenImageIO.a(imagebufalgo_draw.cpp.o): in function std::_Function_handler<void (OpenImageIO_v2_5::ROI), OpenImageIO_v2_5::noise_uniform_<Imath_3_1::half>(OpenImageIO_v2_5::ImageBuf&, float, float, bool, int, OpenImageIO_v2_5::ROI, int)::{lambda(OpenImageIO_v2_5::ROI)#1}>::_M_invoke(std::_Any_data const&, OpenImageIO_v2_5::ROI&&)': imagebufalgo_draw.cpp:(.text+0xeb4f): undefined reference to imath_half_to_float_table'

The project split Imath (now producing libImath) into a separate project repo at version 3.0, and at that time, also the main OpenEXR library changed to be called libOpenEXR, not libIlmImf.
On Unix-like systems, dynamic libraries understand how to link their own dependencies. Static libraries do not. If you're linking static libOpenImageIO.a, and not using cmake and consuming OIIO's exported cmake config files, you'll need to -lStuff yourself to include the dependency libraries you need. In this case, it's Imath.

Understood.  Thanks, @lgritz, for your helpful response.  I was confused by this line from the OIIO dependency definition:
- OpenEXR/Imath >= 3.1 (tested through 3.2 and main)
I thought it meant that OpenEXR and Imath were both contained together were in fact, it's now necessary to download and build them separately.  Imho, there should be two separate lines in the dependency list for OIIO, not one.

It's only very recently in master (not yet in any official supported release) that we were 3.1+ only. For a very long time, we accepted either 2.x or 3.x. They were the same package in 2.x. So "OpenEXR/Imath" was meant indicate "either both package, if new, or the combined thing, if old."
Sorry, I will clarify the docs. I'm sure there are a few places where the wording is muddied because it used to describe a different situation.


chore: Drop SITES.md for GitHub topic tag

Maybe there is a better topic tag, but I noticed that there are already some using it, and this drops the noise of people trying to update SITES.md
Closes #464

@jdanyow does this make sense to you?

thanks for the PR. Shipped!

No problem, guess you need a boilerplate message to close all the "Update SITE.md" PRs that are still open 😆

Ha, realized it might be good to add the tag on this repo, so it will likely show at the top of the results https://github.com/topics/utterances


Reduce or eliminate implementation singletons

The internal implementation uses singletons fairly extensively.  This increases the difficulty of unit testing.  Replacing the singletons with global state at the API level and references from individual classes would reduce coupling and make it easier to unit test.

Fixed by #204.


Update repo status on each build

@arunagw Do you mind adding a descriptive commit message about why something was done?

@arunagw I've rebased latest master and force pushed.

In this PR we are just updating repo attributes whenever a new build comes in.

:+1:

A few ideas and comments, but this looks good to me

Will merge this in when CI is green. Thanks for reviews.


Memory Leaks -> Upgrade Chartboost SDK

Hello,
There is a memory leak issue on iOS with the ANE in sample directory. I would like to re-build it with the current SDK.
It seems that you forget to commit the "build" directory that should contain extension.xml and platform_ios.xml.
Could you update the repository so we can re-build an up-to-date ANE?
Best Regards
Pierrick

Resolved.  Latest AIR ANE is up to date.


Drop apis_metainfo.views.UriGetOrCreate

The idea of the UriGetOrCreate view was to be able to simply pass an URI to the view and it either returns the existing model instance with that URI attached to it, or it creates a new model instance. But IIRC we discussed later, that it is actually not possible to deduce from the URI, what kind of object to create (this is why there are different import routes for different model - and they do exactly that: create a model instance or return the one that already exists).
So I propose to drop the UriGetOrCreate view

lets drop that view in favour of the entity specific import routes


chore: update capacitor & plugins to v6

Cherry-picked from https://github.com/superhero-com/superhero-wallet/pull/2983 as I think it makes sense to separate the PRs
This is why you can see the scanProgress being set and not being used right now

In general all functionality is working but I found some issues. They are also reproducible on develop, I registered them separately.
Also some visual discrepancies on android app (probably because of the larger font is installed):

The same issues related to android are reproducible on dev branch.


Fix bug with speech streaming speech_context.

I believe this is the correct resolution to

Update SpeechContext in tests. See: #2700.

mentioned in #2522.
Speech streaming wasn't converting the list of hints to an instance of SpeechContext before flight.

Can you add a system test to exercise this fix?

@dhermes added speech_context to the system test.
system-tests runtests: commands[1] | python /Users/daspecster/Documents/google/google-cloud-py/system_tests/attempt_system_tests.py speech
test_async_recognize_gcs_file (speech.TestSpeechClient) ... _operation_complete. Trying again in 1 seconds...
_operation_complete. Trying again in 2 seconds...
_operation_complete. Trying again in 4 seconds...
ok
test_async_recognize_local_file (speech.TestSpeechClient) ... _operation_complete. Trying again in 1 seconds...
_operation_complete. Trying again in 2 seconds...
_operation_complete. Trying again in 4 seconds...
ok
test_stream_recognize (speech.TestSpeechClient) ... ok
test_stream_recognize_interim_results (speech.TestSpeechClient) ... ok
test_stream_recognize_single_utterance (speech.TestSpeechClient) ... ok
test_sync_recognize_gcs_file (speech.TestSpeechClient) ... ok
test_sync_recognize_local_file (speech.TestSpeechClient) ... ok
409 The bucket you tried to delete was not empty. (DELETE https://www.googleapis.com/storage/v1/b/new_1478803671769), Trying again in 1 seconds...

----------------------------------------------------------------------
Ran 7 tests in 33.971s

OK
E1110 13:48:35.789352000<PHONE_NUMBER>21216 network_status_tracker.c:48] Memory leaked as all network endpoints were not shut down
_____________________________________________________ summary _____________________________________________________
  system-tests: commands succeeded
  congratulations :)

LGTM once CIs go green? Did you run
$ tox -e system-tests -- speech
$ GOOGLE_CLOUD_DISABLE_GRPC=true tox -e system-tests -- speech

to verify?

@dhermes the tests would just get skipped since streaming only works with gRPC anyway.


xpra: 4.3.3 -> 4.4.3

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@offlinehacker @numinit @mvnetbiz

Result of nixpkgs-review pr 219371 run on aarch64-linux 1

1 package failed to build:

ib-controller

2 packages built:

run-scaled
xpra

Result of nixpkgs-review pr 219371 run on aarch64-linux 1

1 package failed to build:

ib-controller

2 packages built:

run-scaled
xpra

1 package failed to build:
ib-controller

ib-controller depends on ib-tws which is unfree so I'm guessing that's why it fails to build?


Kylin Oracle aggregation buffer

In order to be properly called an oracle, the system will need to accept inputs from more than one API and
discrimate upon the values it receives to give an accurate estimate of what the value is for that time period
.

First off we need to make a collection of API's that will populate the OCW aggregation buffer

The aggregation done on the OCW is one block behind the Kylin runtime oracle,
so the resolution of the OCW should be 6 seconds while the resolution of the Kylin runtime Oracle is 12 seconds

In the   pub fn submit_price_feed: line 391 there should be  a pool of urls(hard coded at first)
let api_url = str::from_utf8(b"https://api.kylin-node.co.uk/prices?currency_pairs=").unwrap();

https://gnunicorn.github.io/substrate-offchain-cb/

This is an example of an existing oracle system on polkadot
https://github.com/ComposableFi/composable/blob/main/frame/oracle/src/lib.rs#L897

Off-chain Indexing example
https://substrate.recipes/off-chain-workers/indexing.html

At the moment we are calling just one API, if it goes down, the whole system is screwed.
This is a diagram of projected reporter APIs. There is only one in the OCW at the moment, but we could convince parachains to populate the aggregation buffer. Lets set up a meeting when you can to disscuss this, we need to implement an API datastructure that contains all vetting info that will approve this API fpor contribution to the buffer(like a whitelisting or KYC) If the contributing API is a parchain, it should benefit from a graylisting privilege where it does not have as many hoops to jump through to be approved.

Milestone 2 Oracle working flow for data feeding and aggregation buffer calculation


fix(copy button): fix layout on dao grid and notification settings pages

Verified on dev. Fixed

Verified on testnet. Fixed


Improved docstring display support

Environment data
VS Code version:  1.18
Python Extension version:  0.8.0
Python Version:   3.4
OS and version:   Windows 10

There is currently very little support for python docstrings, at least using the reST format that we use in our project. Existing docstrings are displayed in the intellisense dialog, but the parameters aren't interpreted as parameters, meaning that there is no type inference being done off of the documentation.
The two main things that would be helpful are:

Recognize existing docstrings and defined parameters/types
Include the ability to auto-generate docstrings, inferring types from the function signature when possible

Thanks!

Since this was transferred, I'm going to close this; my update above was some 9 months ago and Pylance's docstring handling has been much improved. Any specific issue should be opened as a new issue.


Windows 10 : service install / service start - "the dependency service does not exits or been marked for deletion."

Am trying to install the Logger example,
I can install the service by running main.exe -service install.
but if i try to start the service with main -service start - or if i manually try in services.msc to start it i get this error :

Any idea to whats going on ? note i am running it as administrator and tried to change user from local account to administrator also but no avail.
GIF if i try to start it manually in services.scv :
https://i.imgur.com/AG3xGH0.gifv
And it is this program with no modification im trying to run :
https://github.com/kardianos/service/blob/master/example/logging/main.go

GIF if i try to start it manually in services.scv :
https://i.imgur.com/AG3xGH0.gifv
And it is this program with no modification im trying to run :
https://github.com/kardianos/service/blob/master/example/logging/main.go

@goltvn
Removing this two strings from dependencies and rebuild the source can make it work.
Refer to this issue


Add support for long double

Needed for https://github.com/rust-lang/libc/pull/2565.

ping @JohnTitor

Looks fine, could you also add a test case here? https://github.com/JohnTitor/ctest2/tree/master/testcrate/src

From what I can read, it's supposed to compare the rust equivalent, however long double has no equivalent in Rust. So: how can I add a test for a type which doesn't exist in rust?

I wanted to ensure that it works fine by replicating code from the above libc PR, doesn't it make much sense? If not, I'm fine to merge as-is.

I can give it a try at least.

Let's see how it goes now. :3

@JohnTitor Does the test looks ok to you?

Thanks for the release! :)


Implement RAdam optimizer

System information

Are you willing to contribute it (yes/no): Yes, but would like to see if someone else will
Are you willing to maintain it going forward? (yes/no): Yes, but would like to see if someone else will

Describe the feature and the current behavior/state.
New paper describing RAdam looks like a drop in replacement for Adam optimizer with better results.
https://arxiv.org/abs/1908.03265v1
https://github.com/LiyuanLucasLiu/RAdam

That would be awesome indeed.
For the record, here is a Keras implementation (not official): https://github.com/CyberZHG/keras-radam.

This is going to be a great addon ! For any one who is looking out for another detailed comparison can read through - https://medium.com/@lessw/new-state-of-the-art-ai-optimizer-rectified-adam-radam-5d854730807b

I vote for this as well. Looking for this!

Great addition.
Can I try implementation of this?

@SSaishruthi Sure! I know @sayoojbk has also shared interest in helping with this so if you could make a WIP PR as soon as you get it started that'd be great so we could have a few eyes on this and push it through.

Looking forward to that!

Seems that there is an unofficial implementation for TF/Keras.
https://github.com/CyberZHG/keras-radam

I have found one for TF:

I have found one for TF: https://github.com/taki0112/RAdam-Tensorflow

Thanks for the links. I have marked all the links and planning to kick start with the implementation in 2 days. Will keep posted.

@SSaishruthi it looks like RAdam has already an improvement called 'RAdam+lookahead'. One possible implementation of lookahead:
https://github.com/bojone/keras_lookahead
It's called 'Ranger' (the combination of RAdam + lookahead):
Small article about it: https://medium.com/@lessw/new-deep-learning-optimizer-ranger-synergistic-combination-of-radam-lookahead-for-the-best-of-2dc83f79a48d
Paper: https://arxiv.org/abs/1907.08610v1
Lookahead Pytorch implementation: https://github.com/lonePatient/lookahead_pytorch/blob/master/optimizer.py

@luminoso however, it seems that that repo does not support TensorFlow.

Thanks for the links. I have marked all the links and planning to kick start with the implementation after this weekend. Just done with other priority change. Will keep posted.

Hi @SSaishruthi I know you're working on several different things, including the core migration of F1. Would you be okay with @AakashKumarNain taking a look at this one as he has expressed interest. Would love for you to help review any implementation.

@seanpmorgan Sure. Will collaborate along so that we keep things going.

@seanpmorgan @SSaishruthi To me, the keras implementation as pointed out in the comments LGTM. Also, it is written with Optimizer_v2 api. Take a look
https://github.com/CyberZHG/keras-radam/blob/master/keras_radam/optimizer_v2.py

Ping @CyberZHG. Would it be okay to use your implementation as part of Addons? The license you have on it looks good -- but wanted to get your permission/see if you'd like to contribute it yourself?

Yeah it is fair if @CyberZHG just adds it here. Most of the work is already done in that.

Is available an official implementation now?

Is available an official implementation now?

@Alessiobrini
https://www.tensorflow.org/addons/api_docs/python/tfa/optimizers/RectifiedAdam

Is available an official implementation now?

@Alessiobrini
https://www.tensorflow.org/addons/api_docs/python/tfa/optimizers/RectifiedAdam

Thank you! Anyway, if I set warmup proportion and total steps, the optimizer doesn't seem to do the proper learning rate warmup. I don't know if I'm doing something wrong, but the doc says that is only sufficient to specify parameters to have the warmup schedule.

One question. I've been looking at how weight decay is implemented here, in the original RAdam paper and in the paper originally introducing weight decay for Adam (also known as AdamW and cited by the RAdam paper).
The implementations seem to be pretty much the same, but there's a subtle difference: in AdamW the weight decay can also be scheduled for warm restarts, and in fact they propose a normalized value for those cases. Looking at the TF addons AdamW implementation you can see that both learning rate and weight decay argument support a callable: that is, a LearningRateSchedule. However, the RectifiedAdam implementation only does so for the learning rate.
Looking at the code it looks like this should be relatively trivial to change: instead of using the weight decay as a constant hyperparameter, it would need to be handled in a similar way to how decayed_lr works here.
Was there any reason to not also support weight decay schedulers in this case? I imagine you can get the same result by passing weight decay as a tensor with the scheduling already applied, but by doing so the scheduler state might be lost when serializing and deserializing back.

@leandro-gracia-gil Thanks for your good question, Leandro. Would you mind filing an issue for it?

@facaiy Sure. Here it is: https://github.com/tensorflow/addons/issues/1908


Add ESLint with some simple rules

Is your feature request related to a problem? Please describe.
Nexrender is a great project, I use it internally in my company and sometimes we make some changes and adaptations to our needs.
One thing that makes it harder to contribute back to it is that we use it with a ESLint with some basic rules (like not using semicolons), and pass the code through a CI that enforce all of those rules. This leads to massive conflicts when we want to merge Nexrender code or if we wish to contribute something back.
Adding a basic ESLinting for the project and enforcing some of those rules could help us keep the same code standard as the original project and minimize these conflicts.
Describe the solution you'd like
We could agree in some basic rules under the usage (or not) of semicolon, build a .eslintrc file and add a CI that ensures these rules are being followed through the project.
One thing that the project would also benefit from is that it could lint the code for problems.

Hey @nihey
Actually, I do not see reasons why not. Would you be able to create a PR with needed changes, if that is not too much to ask?
Cheers!

No problems! I'll submit a PR soon.

Thank you @nihey :)


Missing escaping of strings in \MySQLReplication\JsonBinaryDecoder\JsonBinaryDecoderService::parseScalar($type)

Operating System: Debian
PHP Version: 7.2
php-mysql-replication Version: 5.0.5
mysql version (SELECT VERSION();): 5.7.17 Percona

Steps required to reproduce the problem.

Table with field type JSON
Content like ["\"test"]

Expected Result.

RowEvent which contains the JSON-field with value ["\"test"].

Actual Result.

RowEvent which contains the JSON-field with invalid value [""test"].

I'll add a patch that fixes this issue.

Index: src/MySQLReplication/JsonBinaryDecoder/JsonBinaryDecoderService.php
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
--- src/MySQLReplication/JsonBinaryDecoder/JsonBinaryDecoderService.php	(revision f6033e7e4dbe971802a8879e4f85589a0df3a519)
+++ src/MySQLReplication/JsonBinaryDecoder/JsonBinaryDecoderService.php	(date<PHONE_NUMBER>111)
@@ -291,7 +291,10 @@
         } else if (self::DOUBLE === $type) {
             $this->jsonBinaryDecoderFormatter->formatValue($this->binaryDataReader->readDouble());
         } else if (self::STRING === $type) {
-            $this->jsonBinaryDecoderFormatter->formatValue($this->binaryDataReader->read($this->readVariableInt()));
+            $this->jsonBinaryDecoderFormatter->formatValue(strtr(
+                $this->binaryDataReader->read($this->readVariableInt()),
+                ['"' => '\"']
+            ));
         } /**
          * else if (self::OPAQUE === $type)
          * {
@@ -335,4 +338,4 @@

         return $len;
     }
-}
\ No newline at end of file
+}

Hi tx for reporting this I fix this by adding addslashes before creating json also added to integration test you see all in commit

Hi @krowinski i'am not sure if addslashes is the right way? Only " have to be escaped and non of the other characters, covered by addslashes...?

hmm yes you probably correct I think I will add str_replace as I found that more characters need to be escaped.
Backspace is replaced with \b
Form feed is replaced with \f
Newline is replaced with \n
Carriage return is replaced with \r
Tab is replaced with \t
Double quote is replaced with \"
Backslash is replaced with \\


NTR for PTI's

host cell apoplast
standard def, define using GO:0048046    apoplast

xyloglucan-specific endo-beta-1,4-glucanase inhibitor  activity

standard def using (GO:0033946 xyloglucan-specific endo-beta-1,4-glucanase activity)
ref for both:
PMID:28082413

host cell apoplast:
def: The apoplast region surrounding a host plant cell. Plants may be described as having two major compartments: the living symplast and the non-living apoplast. The apoplast is external to the plasma membrane and includes cell walls, intercellular spaces and the lumen of dead structures such as xylem vessels. Water and solutes pass freely through it. The host is defined as the larger of the organisms involved in a symbiotic interaction.
is_a parent: GO:0018995 host cellular component (in generic cellular component branch, it's under extracellular region, but the host branch doesn't have the parallel term)

+[Term]
+id: GO:0140593
+name: host cell apoplast
+def: "The apoplast region surrounding a host plant cell. Plants may be described as having two major compartments: the living symplast and the non-living apoplast. The apoplast is external to the plasma membrane and includes cell walls, intercellular spaces and the lumen of dead structures such as xylem vessels. Water and solutes pass freely through it. The host is defined as the larger of the organisms involved in a symbiotic interaction." [PMID:28082413]
+xref: cellular_component
+is_a: GO:0033643 ! host cell part
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/20814 xsd:anyURI
+created_by: pg
+creation_date: 2021-02-09T18:56:11Z
+
+[Term]
+id: GO:0140594
+name: xyloglucan-specific endo-beta-1,4-glucanase inhibitor activity
+namespace: molecular_function
+def: "Stops, prevents or reduces the activity of xyloglucan-specific endo-beta-1,4-glucanase." [PMID:28082413]
+is_a: GO:0004857 ! enzyme inhibitor activity
+property_value: term_tracker_item https://github.com/geneontology/go-ontology/issues/20814 xsd:anyURI
+created_by: pg
+creation_date: 2021-02-09T18:59:49Z


Windows support

using bash script instead of script, python file.py instead of file.py
forcing slashes as file path separator to produce the same results on Windows and Unix
taking into account different virtualenv directory layout on Windows and Unix
Retrieving executable file location from os.Args instead of calling srclib's toolchain.Lookup
bundling virtualenv 13.1.0 instead of downloading it at request. Using virtualenv in program mode to create temporary environment

Hey thanks for the pull requests.
What's the reason for including virtualenv instead of downloading it? That seems like a separate pull request.
I like the addition of --isolated and disabled version check.
Apart from the few style issues, it looks good. (I didn't test it on Windows, just reading the code).

What's the reason for including virtualenv instead of downloading it? That seems like a separate pull request.

You are right, these changes weren't needed. I reverted them, now virtualenv is downloaded and installed during make install

This fails the test on Travis (https://travis-ci.org/sourcegraph/srclib-python/builds/82000040), because it fails to find the pip command. Not sure what changed in this diff to break that, but you can manually install pip in the .travis.yml file as a step in the before-install stage.

This fails the test on Travis

Sorry, my bad. Fixed now

LGTM, thanks!


restore crnk-example-frontend

the crnk-example-frontend folder was deleted on master with commit 1ea2f56e0518a9c39faa451c15ec0e9383089f1a. Was it on purpose? It's confusing when one tries to find the examples for angular implementation.

Hi. well if it is desired, it can be added again. I noticed there are still some traces left. But it would also have to get an update in various areas.

new plan in the area :-) crnk-ui will get a significant upgrade and show the various techniques in there. This way only one UI has to be maintained and we will show advanced sorting, filtering, facetted search,...

Does it mean that the crnk-ui is already supreme to the angular frontend application, or it is just desired to promote crnk-ui?
 Quite the contrary actually, it still needs some work...
Reason for dropping the frontend example are two-fold: there are many different frameworks out there, each evolving quite rapidly. So it is both maintenance effort and rather impossible to cover a wide spectrum of frameworks. On the otherside, crnk/jsonapi is plain, simple REST, and not something more complex as OData, GraphQL and similar where you also need client tooling to work with it.
but contributions are welcomed if somebody would like to maintain one or help getting crnk-ui a bit more up to date.


Fix base image builds to use consistent name (or make auto-merge)

Bug Description
When the periodic job builds a new base image, it uses a different PR name for each new PR so we end up building new image and PR each day until one of the PRs is merged.
The release-builder code does not use the same pr-creator that automator uses so there isn't a way to verify the existing image exists. Either we need to update to use pr-creator, or add some additional logic.
A second option would be to mark the PRs as auto-merge so they merge automatically preventing multiple PRs.
Version
Releases that automatically build new base images (1.12+).

Additional Information
No response

I don't think we should rely on auto-merge, can we de-dupe the PRs?


Dear PyGui showcase

Hey, dearpygui-map looks like it could be a nice addition to the Dear PyGui showcase. Would you be willing to make a short GIF (<8Mb) of the app?
I'm not familiar with poetry, but I cannot get the app to run on my computer or I'd probably make the GIF myself.

Indeed! I am planning to announce it there and on Discord when I release 0.1.0. Should be within a week or so.

That would be great! For the showcase, I'd prefer high quality and short over lower quality and long. It just needs to provide a good impression of the app.

First release is now made and a notification is posted to Discord showcase. Thanks for the patience!

I just saw it. Looks awesome! Thanks for making and sharing the widget!


Adding new attackmodules

Description
new file:   attack-modules/homoglyph_v2_attack.py
new file:   attack-modules/payload_mask_attack.py
Homoglyphv2 attackmodule: Modfied orginal homoglyph attack now randomly and sequentially increase the amount of replaced letters with a homoglyph.
Payload Mask: To get the LLM to echo back a prompt that would normally be caught by the prompt filter or embeddings.
Motivation and Context
Contribution of potential attackmodules for the moonshot project
Type of Change

other: Add on to existing attackmodules.
Checklist
Please check all the boxes that apply to this pull request using "x":

[x]  I have tested the changes locally and verified that they work as expected.
[ ]  I have added or updated the necessary documentation (README, API docs, etc.).
[ ]  I have added appropriate unit tests or functional tests for the changes made.
[ ]  I have followed the project's coding conventions and style guidelines.
[ ]  I have rebased my branch onto the latest commit of the main branch.
[ ]  I have squashed or reorganized my commits into logical units.
[x]  I have added any necessary dependencies or packages to the project's build configuration.
[x]  I have performed a self-review of my own code.
[x]  I have read, understood and agree to the Developer Certificate of Origin below, which this project utilises.

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
   have the right to submit it under the open source license
   indicated in the file; or

(b) The contribution is based upon previous work that, to the best
   of my knowledge, is covered under an appropriate open source
   license and I have the right under that license to submit that
   work with modifications, whether created in whole or in part
   by me, under the same open source license (unless I am
   permitted to submit under a different license), as indicated
   in the file; or

(c) The contribution was provided directly to me by some other
   person who certified (a), (b) or (c) and I have not modified
   it.

(d) I understand and agree that this project and the contribution
   are public and that a record of the contribution (including all
   personal information I submit with it, including my sign-off) is
   maintained indefinitely and may be redistributed consistent with
   this project or the open source license(s) involved.

@Mungusbean
hello. thanks for your commit and sorry it took a while to get back as we have been swamped lately.
we're currently trying out your attack modules and i noticed that the percentage of characters replaced seems to be appended to the prompt that is sent to the LLM. is this the expected behaviour?

tested the attack modules after the update. everything is working. ready to merge when QA has verified


Program closes after time?

I don't really know if its replicable but I think the program just closes after being left open for a while. I'm not sure if this is an issue on my end.

https://github.com/Merubokkusu/Discord-S.C.U.M/issues/65
this was listed in the current issue. it is an issue with discum they have said that they have made changes to their gateway.py if this issues arises then add onto the issue linked so it helps with the issue on their end

I'll try it out 👍

so far the bot hasn't crashed after 12 hour of use. gonna keep it running for longer but it seems to be okay but hasnt been using multi server watching and stuff so let me know. how yours go so I can let the dev of discum know the status of their changes

Ive been running the bot for 24hours no issues have arose gonna close this issue for now @RecentYogurt feel free to reopen if you still have issues


Error   PA3003: Parse error: Property should be at same indent level

Formatting in vs code drops the indentation in line 350 of the .yaml file.
When packing the source files it throws a PA3003: Parse error
using the command >pac canvas pack ...
348        Text: |-
349            ="Click the blue Save disk in the top left to submit a Rapid Response or to save any changes.
350
351            Incident Classification:
352            Light - <4 hrs
353            Serious - >4 & <24hrs"

unless there is a current repro, the latest canvas libraries in pac CLI do have addressed this error. If anyone still has a repro, please provide a repro with a .msapp that stil shows this error in pac CLI v1.12.2 or the upcoming Feb refresh, v1.13.x


Traits on Basilisk

We are still by default attaching 1 trait (carbonless) to every NFT which I find weird

and it would be perhaps desirable to get rid of it or give user an option to select it voluntarily (I remember talking about this with @roiLeo somewhere)

@vikiival what's the state of the traits on Snek? Is there a reason we are attaching carbonless to every NFT without an option to add more traits / remove this one?

ref #3265


Estimated Earnings Wrong for PPLNS

The calculation for estimated earnings is based on the number of shares since the last block was found.  That's not correct for PPLNS as the number of shares could be prior to when the last block was found, or after the last block was found.
Example using a fixed number of shares from config: $config['pplns']['shares']['default'] = 100000000;
If I found a block 50000000 shares ago, I'm not considering the 50000000 shares from the previous block find in my estimate calculation.  If I found a block 150000000 shares ago, I'm incorrectly including the extra 50000000 shares since the previous block find.
To fix this, we need to understand how many shares need to be fetched - both from the shares and potentially shares_archive tables.  This of course, depends on the PPLNS configuration.  If it's fixed, then you need to get that number of shares.  If it's block average, then you need to get that average.  Pseudocode follows:
if (getSharesToConsider(payout_method) <= getTotalSharesFromShareTable()) {   roundShares = getSharesFromSharesTable(); } else {   roundShares = getSharesFromSharesTable() + getRemainingSharesFromSharesArchiveTable(); }
Once you have the appropriate valid/invalid shares for a true PPLNS round, then the existing code should work just fine to calculate the estimates.

I'll be honest, I haven't done any real in-depth coding on MPOS anymore for a while so I'll trust your analysis on this :-D
Thinking about how this would work, this may have one impact on the system: Performance. We have to gather a lot of data in order to calculate a more appropriate estimate which isn't just based on the current round but includes all shares that need to be looked at. I am not entirely sure this is the case, but that may mean looking at a lot of data to get an estimate.
I'll keep this open for someone to look at and maybe create a pull request that can be tested by others. I will not be able to code this myself due to lack of time.

I am closing all old feature requests and ideas since it doesn't seem that anyone is doing a PR against those anyway. Since I won't have the time, no need to keep these ideas open if they are not eventually being implemented.


Add type declarations for unorm: both importable module and ambient var

unorm has a minimal API.

unorm/unorm.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/unorm
http://bower.io/search/?q=unorm
others?

[ ] has a test file? (unorm/unorm-tests.ts or others)
[ ] pass the Travic-CI test?

This one too, @vvakame. Added standard header to d.ts and test file, unorm-tests.ts. Ready to merge? Thanks!

@chbrown thanks mate!


PeerDependencies are also bundled in lib mode which results in redundant output size

Version
4.3.1
Environment info
System:
  OS: Windows 10
Binaries:
  Node: 12.16.3
  Yarn: 1.22.4
  npm: 6.14.4
npmPackages:
  @vue/babel-helper-vue-jsx-merge-props:  1.0.0
  @vue/babel-plugin-transform-vue-jsx:  1.1.2
  @vue/babel-preset-app:  4.3.1
  @vue/babel-preset-jsx:  1.1.2
  @vue/babel-sugar-functional-vue:  1.1.2
  @vue/babel-sugar-inject-h:  1.1.2
  @vue/babel-sugar-v-model:  1.1.2
  @vue/babel-sugar-v-on:  1.1.2
  @vue/cli-overlay:  4.3.1
  @vue/cli-plugin-babel: ~4.3.0 => 4.3.1
  @vue/cli-plugin-router:  4.3.1
  @vue/cli-plugin-vuex:  4.3.1
  @vue/cli-service: ~4.3.0 => 4.3.1
  @vue/cli-shared-utils:  4.3.1
  @vue/component-compiler-utils:  3.1.1
  @vue/preload-webpack-plugin:  1.1.1
  @vue/web-component-wrapper:  1.2.0
  babel-helper-vue-jsx-merge-props:  2.0.3
  vue: ^2.6.11 => 2.6.11
  vue-hot-reload-api:  2.3.4
  vue-loader:  15.9.1
  vue-style-loader:  4.1.2
  vue-template-compiler: ^2.6.11 => 2.6.11
  vue-template-es2015-compiler:  1.9.1
  vuex:  3.3.0
npmGlobalPackages:
  @vue/cli: Not Found

Steps to reproduce

Add a peerDependency and use it as devDependency as well for development only.
Import this dependency.
Run "vue-cli-service build --target lib --name xxx src/main.js"

What is expected?
"In lib mode, Vue is externalized. This means the bundle will not bundle Vue even if your code imports Vue."
PeerDependencies should be externalized as well.
Or is there a way to do so?
What is actually happening?
PeerDependencies will be bundled into the output files

It seems that you are under the impression that Vue does externalize dependencies for you.
That's. It the case. You will have to tell webpack what to externalize yourself.


[macOS] Switching textfields with IME enabled results in duplicate input

Repro steps:

Create a flutter app with two textfields
Focus the cursor in the first textfield
Switch to Japanese input mode and enter text (e.g. type, one character at a time: n i h o n n g o)
Without committing (Return) or cancelling (Escape) input, focus the curse in the second text field

Expected behaviour: the OS/framework arenotified that the composing (mark) text is committed, and that the OS mark text should be cleared
Actual behaviour: IME state still contains the same composing (mark) text as it had when composing in the first text field. The first textfield behaves as though the compose (mark) text was committed but that's likely because we send compose text inline with the full text string, and compose start/end position separately. The framework still likely thinks the field is composing.

A similar issue was fixed on windows in flutter/engine##29146
SHA: flutter/engine@de0765181f85b93fb4380a66ff97fd67bcdaa572

A fix is out in flutter/engine#31849.

Fixed by flutter/engine#31849 on main branch.


New version: ByteDance.Doubao version 1.10.1

Created by 🥟 Dumplings in workflow run #5865.

Log
Updated: 1.9.7 → 1.10.1
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

Bad installer

Bad installer


Audy db 04

Please look what was changed. You can merge and pull or just add the code to the cloud so that the site is up and running. Didnt really change much other than some code in the JS files and added an HTML file

everytime we weren't logged in, it would open errorlogin.html which had that modal, and it was annoying. so I redirected to our normal login page


Is it possible to use the TAG information on the Pipeline

Can you please clarify if it is possible to capture any TAG information into variables or any other struct that would allow it to be used on the pipeline. Eg, for the command git tag -a 1.0.1 -m "Fixed bug A" -m "Improved performance for use casa X"
I would like to use the version as the package version and possibly the messages as release notes... Is that possible?

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

ID: 8b846aea-82f7-a988-67d8-1b5e74b61ed2
Version Independent ID: 2d632729-bb33-c0a0-c996-e1d8e86c2e23
Content: Build Azure Repos Git repositories - Azure Pipelines
Content Source: docs/pipelines/repos/azure-repos-git.md
Product: devops
Technology: devops-cicd-repos
GitHub Login: @steved0x
Microsoft Alias: sdanie

@Leonardo-Ferreira Thank you for the question.
In something as specific as this it's generally recommended to use REST.  For this instance, please refer to the tags API.


Catalog of My Things

Capstone Project
In This Project, We have done the following:-
Logic

Created class from the UML class diagram in a separate .rb file.

Create Items, Books, MusicAlbum, Games, Author, Label, and Genre.

Implemented associations (1-to-many relationships) and aggregations (parent-child relationships) between classes
Add add_item method (in all classes that have that method)
Add can_be_archived?() in the Item class
Add move_to_archive() in the Item class
Add can_be_archived?() in the Book class
Add can_be_archived?() in the MusicAlbum class
Add can_be_archived?() in the Game class

Tests

Add unit tests for all implemented methods.

User Interface

We have implemented the following  functionality

Add Book, Game, Music Album
List Books, Authors, Games, Music Album, Genre, Label.
Add quit functionality
Implemented functionality for saving data to JSON files.
Implemented functionality for loading data from JSON files.

Database

Created a schema.sql file with tables that will be analogical to the structure of the classes.

Video Recording

This is the Video recording

Thank you for your understanding and patience. If you have any questions or concerns, please don't hesitate to reach out to us  @Lul-Abdifan @Adams-Ghub and @rugwizangoga

@gemmen29 We thank you for the approval


Added Hindi translation for concepts/policy page

Description
This pull request adds the Hindi localization for the Kubernetes "concepts/policy" page. The translation provides Hindi content to explain various Kubernetes policies, including API objects, admission controllers, ValidatingAdmissionPolicy, dynamic admission control, and Kubelet configurations.

Issue

Closes: #48260

Thank you for the valuable suggestions, @utkarsh-singh1! 🙌

I've updated the translation for "namespace" to "नेमस्पेस" in the glossary tooltip as suggested.
The term "छवि" has been replaced with "इमेज" for consistency in the dynamic admission controller section.
I've also rephrased the sentence regarding the dynamic admission controller to clarify the explanation, incorporating your suggestion.

Please let me know if any further changes are required! 😊

@sftim @utkarsh-singh1 @drnic Just wanted to follow up on the PR—everything is looking good on your end, and no further changes are needed. Could you please review it when you have a moment? If all looks good to you, feel free to go ahead and merge.

This is a quick reminder about this PR. If everything looks good, could you please go ahead and merge it? Let me know if there’s anything else you need from me.


Exclude LZA Resources from Config Rules

Is your feature request related to a problem? Please describe.
This feature is related to a problem.
We are currently utilizing the AWS Landing Zone Accelerator (LZA) alongside AWS Security Hub. However, the resources created and managed by the LZA pipeline are adversely affecting our Security Score. To mitigate this issue, our team has implemented several Custom Config Rules to explicitly exclude all LZA-created resources from evaluation. We are seeking a solution that addresses this challenge without the need to establish multiple custom configuration rules to maintain or improve our security score.
Describe the feature you'd like
I would like an option for rules to ignore resources based on regex or LZA resources.
Additional context
Here are some examples of The Custom Config Rules we had to create:
Rule Name: ECRLifecyclePolicyEnforcement
Description: Ensures that all ECR repositories have lifecycle policies attached, excluding LZA-created repositories matching the pattern cdk-accel-container-assets-*.
Rule Replaced: ECR.3
Name: S3BucketLoggingEnabledExclusion
description: Ensures that all S3 buckets have logging enabled, excluding LZA-created buckets matching the pattern aws-accelerator-s3-access-logs-*.
Rule Replaced: S3.9

Another example finding is Lambda.3 which expects functions to run in a VPC. Conveniently excluding LZA resources from findings which they are intentionally in violation of would indeed eliminate a large amount of security noise.
Please count me as a second for this enhancement

Hello @Godtrilla!
Thank you for reaching out. We have an open item in our backlog for this feature request, because as you indicated, this impacts the security score in your environment if you're using SecurityHub as your SIEM. I have added this issue to the aforementioned issue to get more traction. I will keep this issue open and keep you up to date once this is supported for a future release. Please let me know if you have any other questions or concerns in the meantime.


describe differences between bytes and strings

closes #609
@knz Can you take a quick look at this? Hope I didn't butcher your explanation!

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1ded8bdd38ada348efc4cd587bdcc2af3e0a7668/

@rmloveland Can I get a copy edit on this? Same content in each file, thankfully.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/603add4cea1d53c68917d186a20a1e0aac370f76/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/3822fb737c0048c9a445445da967e8e02cc12632/

LGTM
The explanation of the difference of interpretation of \x should link to the page on string and byte literals: https://www.cockroachlabs.com/docs/v2.1/sql-constants.html

@sploiselle, is this ready to merge?

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a07e9e01c8ed0c470675a39c0fd293adb32371c4/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/47b0e0fc7aaaabcc30912fb7b8bd3b5c0d0ad648/


cargo.toml: drop the version range for md-5, sha2

cargo.toml: drop the version range for md-5, sha2
https://github.com/coreos/openssh-keys/issues/89

I guess we should probably do a new release for this, so let's add a changelog entry so we have something to say about it.
Also, please update the commit message prefix to cargo: as requested.


Add project option to log to file.

It's pretty useful to have the PolycodePlayer logging to a file.
There's a new checkbox in the project settings to enable this (by default it is disabled).

rebasing


:robot: Triggering CI on branch 'release-next' after synching to openshift/master

/test 4.4-csv

OCF Webhook is merging this PR


feat(dotnet): handling optional and variadic parameters

Handling optional and variadic parameters in .NET
Emits the =null or params[] keywords when required in constructors or methods.
Ran pack.sh in the CDK with this change, and the S3 construct now looks better:
public Bucket(Amazon.CDK.Construct scope, string id, Amazon.CDK.AWS.S3.IBucketProps props = null): base(new DeputyProps(new object[]{scope, id, props}))         {         }
Making the C# call look like:
 var bucket = new Bucket(this, "bucketName");
Rather than
 var bucket = new Bucket(this, "bucketName", null);
Fixes #153
Fixes #210

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

Should variadic arguments be defaulted to []?

In C#, a parameter array can not have a default value. It is by definition optional because it is passed as an empty array if not specified.
C# spec: http://download.microsoft.com/download/3/8/8/388e7205-bc10-4226-b2a8-75351c669b09/csharp language specification.doc
Section 7.4.1:

In particular, note that an empty array is created when there are zero arguments given for the parameter array.

This means no changes to the runtime should be required, as the parameter will be passed as an empty array.

Have we made sure this works with the current runtime? Have the compliance tests been updated to reflect this change?

Tested with the CDKHello app (the S3 bucket instruction used to require a useless new BucketProps(), not anymore), calling 'cdk-synth' works fine.
Tested with the ported EC2/ECS sample stack, which used to require useless new Ec2TaskDefinitionProps() and useless new RepositoryImageProps(), calling 'cdk-synth' works fine.
Looks like the variadic might need some runtime work. Looking into this and holding off the PR so far.

This is ready to be reviewed/merged. tested with the CDK for Lambda and variadic layers.
Also added a full suite of compliance tests that run with the runtime with all sorts of tests around optionals and variadic params (nulls, empty, one value array, multiple values array etc..).

Looking super good. Love the small enhancements to readability that you brought in there & the comments... Sweet sweet stuff!


[Bug Report]: hot reload is not working when using custom memo function in React

System Info
System:
OS: macOS 13.2.1
CPU: (10) arm64 Apple M2 Pro
Memory: 78.59 MB / 16.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 18.14.2 - ~/Library/Caches/fnm_multishells/41915_1679985898031/bin/node
Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/41915_1679985898031/bin/yarn
npm: 9.5.0 - ~/Library/Caches/fnm_multishells/41915_1679985898031/bin/npm
Browsers:
Safari: 16.3
Details
React hot reload failed when i wrapped a component with custom memo function
function memo(displayName, functionComponent) {
    return React.memo(Object.assign(functionComponent, { displayName }))
}

const UnwrappedApp = memo('App', () => {
    const [count, setCount] = React.useState(0)

    return (

Rspack + React

                <button onClick={() => setCount((count) => count + 1)}>count is {count}</button>

                    Edit src/App.jsx and save to test HMR

Click on the Rspack and React logos to learn more

    )
})

export const App = memo('App', UnwrappedApp)

when i update text in component, rspack did a full reload instead of hot reload. Hot reload works as expected when export App with React.memo. It does not seem to be a issue on webpack or vite.

Reproduce link
https://github.com/Shad02w/rspack-hmr-repro
Reproduce Steps

create project pnpm create rspack@latest
start dev server
update text in App
page get full reload

@Shad02w It already fixed after aligin to react-refresh-webpack-plugin, you can have a try with latest version.I will close this issue, feel free to open a new issue if you have any new issues.


Fix #6660. Created regex to match all uppercase ascii/cyrillic chars

https://github.com/codemirror/CodeMirror/issues/6660
Created a regex that will match  all uppercase ascii/cyrillic characters. This will improve the accuracy of function isUpperCase() and allow vim shortcut "shift + ~" to convert lowerCaseChars => upperCaseChars & upperCaseChars => lowerCaseChars on cyrillic characters.

Some of the browsers supported by the library don't support \p (or /u for that matter) so you'll have to do this conditionally and fall back to the old regexp when it doesn't work.
Also, why new RegExp(/^[\p{Lu}]$/, 'u'), and not just /^[\p{Lu}]$/u?

Some of the browsers supported by the library don't support \p (or /u for that matter) so you'll have to do this conditionally and fall back to the old regexp when it doesn't work.

I should've recognized that as a potential issue beyond the browsers that I tested.
A more accurate solution that does not require a regex may be to bring back the original regex to check for uppercase ascii and also check the indexof the below upperCase cyrillic chars string. Ill make sure im not missing any additional chars in that string.
var upperCaseCyrillicChars = "АбБВГДЕЁЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯ";
upperCaseCyrillicChars.indexOf(k) !== -1

Also, why new RegExp(/^[\p{Lu}]$/, 'u'), and not just /^[\p{Lu}]$/u?
For some reason when running npm test - the later regex would return a SyntaxError: invalid regular expression flag but new Regexp would not.

For some reason when running npm test - the later regex would return a SyntaxError: invalid regular expression flag but new Regexp would not.

That's a symptom of the engine support issue I was talking about.
I'd suggest something like:
var upperCaseChars
try { upperCaseChars = new RegExp("^[\\p{Lu}]$", "u") }
catch (_) { upperCaseChars = /^[A-Z]$/ }

Thanks for the suggestions. Added try/catch to fallback to the original regex.

    return new RegExp(/^[\p{Lu}]$/, "u").test(k);

Could you make the argument a string rather than a regexp? I guess this, due to subtle type conversions, also works, but it's needlessly obscure. (Don't forget to escape the backslash in the string.)

Also since try-catch isn't necessarily cheap I'd really put the regexp in a module-level variable.

The exception occurs on regexp creation, not when calling a method on it, so this doesn't work. Please just follow the structure I showed before.

The exception occurs on regexp creation, not when calling a method on it, so this doesn't work. Please just follow the structure I showed before.

Looks to be set as requested. Apologies on any confusion


[Enhancement] Improve spacing between organization logos in the testimonials section

Description

The space in between organization logos in the testimonials is not very responsive.
The space is insufficient to distinguish the logos clear in mobile view.

How to recreate

Go to the bottom of the website to the testimonials section.
Below the testimonial section look for organization logos.
Now change the screen size to check the responsiveness of the logos.

Proposed Solution

Increase the spacing in between logos to increase the clarity.

Screenshots

/assign


Element id=batch_delete_link not found

I'm getting this error:
[info] Executing: |fireEvent | id=batch_delete_link | click |
[error] Element id=batch_delete_link not found
Am I doing something wrong, or is there something that can be changed to make this work again?

What's your browser location when you got this error?
It should be something like https://YOUR_SUBDOMAIN.slack.com/archives/general

Yep, I was using the wrong URL. Thanks for setting me straight. Worked beautifully, and I will be sharing it with others who misused their #general channel before realizing its special restrictions.

Cool, have a good day! :sparkles:


Notary requires an X509 cert's common name to match the GUN exactly, but the length of a common name is restricted to 64 chars

In order to be valid, Notary requires that any cert must have a common name that matches the GUN.  See https://github.com/docker/notary/blob/master/trustpinning/certs.go#L178
However, RFC3280 imposes a maximum length of 64 characters on the common name of an X509 certificate.  See https://www.ietf.org/rfc/rfc3280.txt (search for ub-common-name).
When using Notary with Docker, it is easy to end up with a GUN that is longer than 64 characters (e.g. "my_docker_registry.somedomain.com/my_docker_repo_part_1/my_docker_repo_part_2")
While Notary's own internal certificate-generating code may not enforce this limit, it is enforced by third-party tools such as openssl.  This is a big problem for anyone planning to generate their own certificates and then import them into Notary (see https://github.com/docker/notary/pull/821)

Thank you @dnwake for pointing this out!  I'm going to link this issue to https://github.com/docker/notary/issues/883 since it's similar in nature, but different

For the benefit of future people running into this problem, I've found that the certtool command (supplied as part of the gnutls-utils package) ignores the 64 character limitation, so can be used as a workaround.

Having merged wildcard CNs and there being workarounds, I'm going to close this. We don't have any specific action items to address GUN name length. Please re-open or file an issue with specific action items if more is needed.


inconsistent trace-indicator formed for rare scenario of /v1/relay-server-replacement

While testing /v1/relay-server-replacement, found one weird scenario, where the trace-indictor was created as per expectation in all cases except the below case.
Case 1 creates same trace-indicator for RO and TAR clients whereas case 2 creates a correct one (unique trace-indicator for each)
Case 1:
{
                        "uuid": "ro-2-0-1-op-fc-is-009",
                        "name": [
                            {
                                "value-name": "ForwardingKind",
                                "value": "core-model-1-4:FORWARDING_KIND_TYPE_SUBSCRIPTION"
                            },
                            {
                                "value-name": "ForwardingName",
                                "value": "ServerReplacementBroadcast"
                            }
                        ],
                        "fc-port": [
                            {
                                "local-id": "000",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_MANAGEMENT",
                                "logical-termination-point": "ro-2-0-1-op-s-is-003"
                            },
                            {
                                "local-id": "001",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_MANAGEMENT",
                                "logical-termination-point": "ro-2-0-1-op-s-is-002"
                            },
                            {
                                "local-id": "100",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_INPUT",
                                "logical-termination-point": "ro-2-0-1-op-s-is-010"
                            },
                            {
                                "local-id": "200",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-ro-2-0-1-001"
                            },
                            {
                                "local-id": "201",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-tar-1-0-0-001"
                            },
                            {
                                "local-id": "202",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-eatl-1-0-0-001"
                            },
                            {
                                "local-id": "203",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-ol-1-0-0-001"
                            },
                            {
                                "local-id": "204",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-aa-1-0-0-001"
                            },
                            {
                                "local-id": "205",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-alt-1-0-0-001"
                            },
                            {
                                "local-id": "206",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-okm-1-0-0-001"
                            },
                            {
                                "local-id": "207",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-cc-1-0-0-001"
                            },
                            {
                                "local-id": "208",
                                "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
                                "logical-termination-point": "ro-2-0-1-op-c-im-dan-2-0-1-001"
                            }
                        ]
                    }

Sample log flow for case 1: where two instances having same trace-indicator 6.1
{
    "x-correlator": "510e5200-e11b-41d4-a716-516655641124",
    "trace-indicator": "6",
    "user": "User Name",
    "originator": "Resolver",
    "application-name": "RegistryOffice",
    "release-number": "2.0.1",
    "operation-name": "/v1/relay-server-replacement",
    "response-code": 204,
    "timestamp": "2023-06-13T14:31:40+02:00",
    "stringified-body": "{\"current-application-name\":\"ApplicationLayerTopology\",\"current-release-number\":\"1.0.0\",\"future-application-name\":\"ApplicationLayerTopology\",\"future-release-number\":\"2.0.1\",\"future-protocol\":\"HTTP\",\"future-address\":{\"ip-address\":{\"ipv-4-address\":\"<IP_ADDRESS>\"}},\"future-port\":3005}"
  },
  {
    "x-correlator": "510e5200-e11b-41d4-a716-516655641124",
    "trace-indicator": "6.1",
    "user": "User Name",
    "originator": "RegistryOffice",
    "application-name": "RegistryOffice",
    "release-number": "2.0.1",
    "operation-name": "/v1/update-client",
    "response-code": 204,
    "timestamp": "2023-06-13T14:31:40+02:00",
    "stringified-body": "{\"current-application-name\":\"ApplicationLayerTopology\",\"current-release-number\":\"1.0.0\",\"future-application-name\":\"ApplicationLayerTopology\",\"future-release-number\":\"2.0.1\",\"future-protocol\":\"HTTP\",\"future-address\":{\"ip-address\":{\"ipv-4-address\":\"<IP_ADDRESS>\"}},\"future-port\":3005}"
  },
  {
    "x-correlator": "510e5200-e11b-41d4-a716-516655641124",
    "trace-indicator": "6.1",
    "user": "User Name",
    "originator": "RegistryOffice",
    "application-name": "TypeApprovalRegister",
    "release-number": "2.0.1",
    "operation-name": "/v1/update-client",
    "response-code": 204,
    "timestamp": "2023-06-13T14:31:40+02:00",
    "stringified-body": "{\"current-application-name\":\"ApplicationLayerTopology\",\"current-release-number\":\"1.0.0\",\"future-application-name\":\"ApplicationLayerTopology\",\"future-release-number\":\"2.0.1\",\"future-protocol\":\"HTTP\",\"future-address\":{\"ip-address\":{\"ipv-4-address\":\"<IP_ADDRESS>\"}},\"future-port\":3005}"
  },
  {
    "x-correlator": "510e5200-e11b-41d4-a716-516655641124",
    "trace-indicator": "6.2",
    "user": "User Name",
    "originator": "RegistryOffice",
    "application-name": "ExecutionAndTraceLog",
    "release-number": "2.0.1",
    "operation-name": "/v1/update-client",
    "response-code": 204,
    "timestamp": "2023-06-13T14:31:40+02:00",
    "stringified-body": "{\"current-application-name\":\"ApplicationLayerTopology\",\"current-release-number\":\"1.0.0\",\"future-application-name\":\"ApplicationLayerTopology\",\"future-release-number\":\"2.0.1\",\"future-protocol\":\"HTTP\",\"future-address\":{\"ip-address\":{\"ipv-4-address\":\"<IP_ADDRESS>\"}},\"future-port\":3005}"
  },

Case 2:
{
    "uuid": "ro-2-0-1-op-fc-is-009",
    "name": [
        {
            "value-name": "ForwardingKind",
            "value": "core-model-1-4:FORWARDING_KIND_TYPE_SUBSCRIPTION"
        },
        {
            "value-name": "ForwardingName",
            "value": "ServerReplacementBroadcast"
        }
    ],
    "fc-port": [
        {
            "local-id": "000",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_MANAGEMENT",
            "logical-termination-point": "ro-2-0-1-op-s-is-003"
        },
        {
            "local-id": "001",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_MANAGEMENT",
            "logical-termination-point": "ro-2-0-1-op-s-is-002"
        },
        {
            "local-id": "100",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_INPUT",
            "logical-termination-point": "ro-2-0-1-op-s-is-010"
        },
        {
            "local-id": "201",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-tar-1-0-0-001"
        },
        {
            "local-id": "202",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-eatl-1-0-0-001"
        },
        {
            "local-id": "203",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-ol-1-0-0-001"
        },
        {
            "local-id": "204",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-aa-1-0-0-001"
        },
        {
            "local-id": "205",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-alt-1-0-0-001"
        },
        {
            "local-id": "206",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-okm-1-0-0-001"
        },
        {
            "local-id": "207",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-cc-1-0-0-001"
        },
        {
            "local-id": "208",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-da-2-0-1-001"
        },
        {
            "local-id": "209",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-dan-2-0-1-001"
        },
        {
            "local-id": "210",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-nr-2-0-1-001"
        },
        {
            "local-id": "211",
            "port-direction": "core-model-1-4:PORT_DIRECTION_TYPE_OUTPUT",
            "logical-termination-point": "ro-2-0-1-op-c-im-ro-2-0-3-001"
        }
    ]
}

Priority:Low;
AffectedFlow:None;

Cause: ROs operation relay-server-replacement sends forwardings to all applications with 'update-client' operation. Since RO is first in the list of forwardings and we are not waiting for response, update-client on RO starts to execute. Update-client has also forwardings. Which means a second call to automateForwardingConstructAsync (within RO, within this one API call) which resets traceIndicatorIncrementer back to 1.


Typo in docstring for classification_summary

There appears to be a typo in the docstring for the "classification_summary" function (located in functions/evaluation/classification_summary.py).
The correct definition for recall is TP / (TP + FN), however the current docstring writes "TN" instead of "FN".
Also, after amending the definition, a few lines later should mention the definition of "FN" alongside "TP", "FP", and "TN".
The actual code seems to make the correct calculation.

Fixed in #6515.


query-engine should support variables

Problem
The query-engine of prisma doesn't support variables.
I'm probably an unusual user of prisma, however, I think my use case is relevant to the future of prisma, as it can dramatically increase performance.
In its current implementation, all variables have to be inlined into the GraphQL query before sending it to the query-engine as it hasn't yet implemented variables.
Suggested solution
The query-engine should support variables as an enabler for "prepared statements".
If you enable variables, the engine can internally prepare all SQL statements against the database and fill in the variables into the prepared statement at runtime. If a query is prepared once, the prepared statement can be re-used. This means the prisma client can prepare all operations and store them with an ID. For subsequent requests, the client only sends the ID and variables. This would allow the engine to completely skip the "graphql layer" and directly call into the SQL connection. This should allow the query engine to be a lot more efficient and use less memory because complex operations like AST transformations only have to run once per operation.

I think we already have have LRU cache of the prepared statement executed which can be controlled by statement_cache_size in the connection string.
cc @pimeys

We indeed have a cache for prepared statements already.
Can you explain a bit more what you are lacking @jensneuse? I am unclear how this related to GraphQL queries, which is an application level concern.

@janpio Hey, thanks for looking into this.
Just in case it's not clear, I'm not using the generated Prisma client as a frontend to the Rust client.
I want to directly interact with the Rust engine via the JSON RPC API.
The problem though is that I always have to inline all variables into the Query.
This makes it impossible for me (and the generated Prisma client) to re-use and cache Queries.
I think it's very inefficient for the prisma client to always build GraphQL queries which have variables inlined.
Wouldn't it make sense for the prisma client to divide the execution into two stages:

"prepare" a GraphQL Query
"execute" a prepared GraphQL Query with variables

The prepare stage would return an ID for the prepared statement.
The execution stage allows the client to execute a prepared statement with an ID and variables.
This would mean that the Rust binary can skip many steps (lexing,parsing,validation) in the hot path, when a statement is prepared.
As an alternative, the Rust binary could also be extended with an API which returns the SQL statement for a given GraphQL Query. This way, any client could use the Rust API to translate a GraphQL query into a SQL statement and cache it for themselves. It could then use the "raw SQL" mode to execute the pre-computed SQL statement.

I want to directly interact with the Rust engine via the JSON RPC API.

Ok, that explains my confusion: That is not a supported way to use Prisma. The Rust Engine API is an internal implementation detail that can change (and will!) change any time, or might even go away in the future for some use cases (see https://github.com/prisma/prisma/issues/6301).
Your suggestion might still be interesting. Is creating these queries such a big deal? It is for a database connection, as sending a prepared statement is almost 2 pieces: preparing and executing and both takes a roundtrip to the database. That does not really exist for the GraphQL queries we are creating though - that is just creating a string that we send over to the Engine.
Your additional suggestion about returning generated SQL is not viable, as many Client Queries are turned into a series of queries that build on each other. You tell the Engine what data you want, and it then returns that data to you - what happens in between is just an implementation detail.

The problem though is that I always have to inline all variables into the Query.
This makes it impossible for me (and the generated Prisma client) to re-use and cache Queries.
I think it's very inefficient for the prisma client to always build GraphQL queries which have variables inlined.

Rereading this 2 years later, I think this is where some information was missing:
The Query Engine indeed expects full GraphQL queries (or today Json payloads). But on the Query Engine side, these are turned into normal named prepared SQL statements that are executed on the database. We have a prepared statement cache for the SQL statements that we look up if a query was prepared before, and use it if we find one.
Now, of course, we could potentially do something similar for the Prisma Client queries (either via GraphQL or Json protocol) that we receive in the engine from a Client, as going from that string to the query to be executed indeed is similar to "planning a query" in a database. The cost of this would be that the current 1-roundtrip to execute a query would need to be replaced with a multi-roundtrip query execution similar to how SQL statements need to be pepared first, and then can be executed (or parse, bind, execute on the extended protocol).
Still interesting suggestion, if that "parse + bind" phase of the queries in the Query Engine indeed is a relevant amount of time for each query.


feat: Zephyr 2.6.0

Based on:

https://docs.zephyrproject.org/2.6.0/getting_started/index.html
https://docs.zephyrproject.org/2.6.0/getting_started/installation_linux.html#install-requirements-and-dependencies

TODO

[ ] Make 2.6-branch
[ ] Change PR base to 2.6-branch

This is probably ready for testing.


[Browser Bookmarks] ...support additional browsers for this extension

Extension
https://www.raycast.com/raycast/browser-bookmarks
Description
I am using the "Prisma Access Browser" but the following extension only supports the Chrome and Safari browsers, it will benefit a add the following support.
Who will benefit from this feature?
No response
Anything else?
No response

Thanks for the feature request. Would you like to work on it? If yes, here's our guide on extension contributions so that you can open up a pull request. Feel free to contact me here or in the Slack community if you need further help.

@thomaslombart I might grab it and make a contribution.
Can you provide any pointer in the right direction? There are multiple chrome-based browsers in the market, and I imagine all interfaces are the same, and the only thing needed is to point to the correct app instead of Chrome [or to an alternative storage location on disk].
If you're familiar with the relevant code, a starting point of where to look would be great.

Sure, here are some PRs that achieved the same for other browsers:

https://github.com/raycast/extensions/pull/9697
https://github.com/raycast/extensions/pull/6354
https://github.com/raycast/extensions/pull/7460

You can probably do something similar 🙂


Distributions not compatible with AD (ForwardDiff/Flux.Tracker)

[ ] MvNormal (not working with Flux), see #511
[x] Poisson, see #614
[x] Binomial, see #600

Three possible solutions:

Define our own version of these functions for ForwardDiff and Flux.Tracker types. These should ideally be in Distributions.jl with Requires.jl to avoid adding extra dependencies there,
Make a pure Julia implementation of these distributions and PR them to Distributions.jl, or
Use finite difference autodiff by default as Optim.jl does using DiffEqDiffTools.jl.

Make a pure Julia implementation of these distributions and PR them to Distributions.jl; Poisson at least seems to use ccall, or

At least for MvNormal, that the implementation isn't pure Julia actually isn't the issue. The implementation in Distributions.jl places very strong type constraints on the mean vector in particular. I made a start on rectifying this for MvNormal, see this PR, but having now dug slightly further into the internals it looks like a reasonable amount of work would be required to properly sort things out without making breaking changes to Distributions.jl, which presumably isn't an option.

Use finite difference autodiff by default as Optim.jl does using DiffEqDiffTools.jl.

I'm not keen on this because it's inaccurate in general, and not well suited to high-dimensional problems.

Define our own version of these functions for ForwardDiff and Flux.Tracker types. These should ideally be in Distributions.jl to avoid type piracy, with Requires.jl to avoid adding extra dependencies there,

We've already got this for Binomial and #614 provides something sensible for Poisson, so if someone turns that into a PR (@cpfiffer ?) that should be straightforward to resolve. MvNormal will remain slightly tricky without some (potentially slightly awkward) refactoring of Distributions.jl though.
@yebai @mohamed82008 what are your thoughts?

I prefer the solution of fixing these issues on the Distributions.jl and DiffRules side, through either pure Julia implementation of logpdf functions or customised gradient rules. This way these changes can also be helpful for other packages such as Mamba and Stheno.
On the short term, we can keep these (temporary) fixes including #600 #614  in the Turing repo and remove them after these issues are addressed in the Distributions and related AD packages.

duplicate of #717 and https://github.com/TuringLang/Turing.jl/issues/615


fix: wrong folder name

The description (in C#) seemed to be incorrect.
https://docs.microsoft.com/en-us/azure/azure-web-pubsub/tutorial-pub-sub-messages?tabs=csharp#set-up-the-subscriber
create a new folder subscribe
-> create a new folder subscriber

@08thse : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

#sign-off


Add support for async pinging with tokio

Adds a future module for support for asynchronous pinging that is disabled by default. Some things are somewhat hacky, like converting to and from std connection types, because tokio doesn't mimic the standard library perfectly.

Following @Cldfire's suggestion I renamed the future module to tokio and de-duplicated the request structs. I did not refactor the sync api to wrap the async module because I believe tokio and async-trait would burden users the the sync api with too many dependencies, but this could be changed.

That's a fair concern. I'm fine with merging this for now and re-visiting that decision later on since the ping protocol is highly unlikely to change much if at all going forward, so we shouldn't be touching this code much anyway.
Let's make sure we update the CLI example as mentioned above and make clippy happy first, though.

I changed the CLI example up a bit to provide both sync and async impls, and I updated the READMEs a bit to mention the new async functionality.
Thanks again for doing this!


Automated Package Upgrade

:tada: This PR is included in version 13.0.54 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix State and charSpec shaping

Prior to this commit the state object would mutate shape once created.
Further more the charSpec passed into the State constructor would be of a different
shape when in reality it does not have to be.

@krisselden when you have a chance can you review?


Not issue: Broadlink RM4C Mini

The plugin is compatible with the new Broadlink RM4C Mini?
Thanks!

Is this a question or a statement - you're saying it is compatible, but you also put a question mark?


Bug #2580: Initialize and load hwloc topology only once, during startup

6.10.0 branch now fails with
cpuaffinity.C: In function 'void CmiInitHwlocTopology()':
cpuaffinity.C:72:99: error: 'HWLOC_TOPOLOGY_FLAG_INCLUDE_DISALLOWED' was not declared in this scope
cmi_hwloc_topology_set_flags(legacy_topology, cmi_hwloc_topology_get_flags(legacy_topology) | HWLOC_TOPOLOGY_FLAG_INCLUDE_DISALLOWED);
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Fatal Error by charmc in directory /tmp/oct2019/charm/netlrts-linux-x86_64/tmp
Command g++ -DCMK_GFORTRAN -I../bin/../include -D__CHARMC__=1 -I. -O3 -U_FORTIFY_SOURCE -fno-stack-protector -fno-lifetime-dse -c cpuaffinity.C -o cpuaffinity.o returned error code 1

6.10.0 branch now fails

Pushed a fix.


Using a separate domain

Just a quick thought:  On my side (I manage my own DNS servers) I did a split between the DNS domain the cert is for and the domain the authorizations are in using CNAMEs (so _acme-challenge.www.example.com IN CNAME www.example.com.acme.example.com).  This allows me to have static DNS entries for everything except one domain that contains all validations.
This allows me to have different ACLs on the account that can create validations and the account that can actually manage the DNS.  And in my case the keys are additionally protected by DANE (so changing the cert by itself would not allow use of arbitrary keys).
Just wondering if route53 can do the same thing (different ACLs for different users managing different domains) and if it's worth it implementing a mapping from the verification name as returned by the API to some other name.

You can use IAM to give different credentials permissions on different hosted zones, I see no reason you couldn't create a hosted zones for just _acme-challenge.<your domains> and that would accomplish what you want. This question is probably better for a general AWS forum though.


Merge fideslib into unified-fides

Is your feature request related to a specific problem?
Now that everything is merged into a single project, the additional friction of updating fideslib is no longer worth it since it is no longer enabling code-sharing. Case in point, PRs like this become more complicated as we end up circumventing fideslib altogether instead of trying to fix it properly and cut another release.
Describe the solution you'd like
Copy/pasta, keeping the git history doesn't seem particularly important here given the additional complexity

@NevilleS @seanpreston FYI this is on my mind. That repo is now devoid of its original purpose and should be folded back in (the arms of unified-fides are ever-open to embrace more code)


make --file argument required

Fix https://github.com/spdx/ntia-conformance-checker/issues/139
Through making the --file argument required.

The build is failing due to an issue with a bot, not due to failing tests. Sorry about that.
Tests pass!
Thank you, @lumjjb!


Add Kairi's Heart Piece As Item

Make this the same as the added Proofs we created. The item name should be KEY_ITEM17. Assigning to Critic since he has the latest item datatable I believe

Kairi's Heart Piece added as KEY_ITEM17.
TresItemData.zip


compile error example/simple

I've tried to run the "simple" example project, got this error:
https://gist.github.com/pouya-abbassi/266d7ab406d4b5001404dc5ff8b479f4
─➤  lein version
Leiningen 2.8.3 on Java 10.0.2 OpenJDK 64-Bit Server VM

I can create re-frame project and run it already, I just can't run this sample code.

Thanks for the heads up, I'll update the dependencies to handle Java 9+.


[Py3-compatibility] fix some iteritems and use of long

More python 3 compatibility fixes

Looks good -- increased test coverage due to removal of unnecessary code! Woohoo! Merging.