Word wrap disabled when switching between plaintext and markdown tabs, have to toggle word wrap twice to re-enable it.

VSCode Version: Code 1.14.1 (2648980a697a4c8fb5777dcfb2ab110cec8a2f58, 2017-07-13T19:08:57.197Z)
OS Version: Darwin x64 16.6.0
Extensions:

Extension
Author (truncated)
Version

Go
luk
0.6.62

latex
ms-
0.1.3

Steps to Reproduce:

Create two tabs, called Tab1 and Tab2 for reference.
Set Tab1 language mode to Markdown.
Switch to Tab2, in plaintext mode, write a line that extends past the width of window, enable Word Wrap, works as expected.
Switch to Tab1 (Markdown).
Switch to Tab2 (Plaintext). Word Wrap no longer applied.
Enable Word Wrap on Tab2. No effect.
Enable Word Wrap on Tab2 for second time. Word Wrap applied.

Reproduces without extensions: Yes

Closing due to duplicate issue: https://github.com/Microsoft/vscode/issues/30360


Fixes

This branch includes various small fixes for the pre-requisite deployment.

This looks like it is merging two repos together.

If I am renaming @StuartCD's repo content to terraform-morpheus-bootstrap then it looks like that should be the 1.0.0 area. This will be run by either a PS consultant or by the customer. Therefore we don't want the 2.0.0 content in a public repo.

Hi @richeney I have updated the code to remove the various layers and only include the "first layer" terraform module. I have also made some amendments to the variable naming.

Will merge in the PR and then we can look at the GitHub provider resources - e.g. data for the repo, which should be copied from a template repo. We can then have the fine grained PAT created for that repo, and push up the required files once the GitHub Actions have been configured for the workload identity.


Fixed grammar in TaskNameAsyncAnalyzer #839

Fixes #839
Update grammar in TaskNameAsyncAnalyzer.cs #839

Coverage remained the same at 91.511% when pulling 5c769f3431f3fbd1e867069b87fc1409d6877292 on sdygert:TaskNameAsyncAnalyzer into c5976810750cee9a76e7104c5ca9ba58ba58bebe on code-cracker:v1.0.x.


adding deviations

Added deviations and made below changes.

Cisco's implementation toggles allow-multiple-as at the global level, but enables multipath and max-paths at the global/afi/safi level.  Hence added deviation.
Cisco is not doing load balance with just one flow, so had to create multiple flows for load balance to work.

Pull Request Functional Test Report for #3006 / 46ed07da05d68ee97621bf4be58ae8f675998913
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-1.51: BGP multipath ECMP
b475082e
Log

Cisco 8000E

RT-1.51: BGP multipath ECMP
95b9869a
Log

Cisco XRd

RT-1.51: BGP multipath ECMP
3cf2a4d3
Log

Juniper ncPTX

RT-1.51: BGP multipath ECMP
eba93bd8
Log

Nokia SR Linux

RT-1.51: BGP multipath ECMP
876f9881
Log

Openconfig Lemming

RT-1.51: BGP multipath ECMP
01d547b8
Log

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-1.51: BGP multipath ECMP

Cisco 8808

RT-1.51: BGP multipath ECMP

Juniper PTX10008

RT-1.51: BGP multipath ECMP

Nokia 7250 IXR-10e

RT-1.51: BGP multipath ECMP

Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.859%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1983

Relevant Lines:
3550

💛  - Coveralls


Issue 8894 - Regression with property lookup error message.

http://d.puremagic.com/issues/show_bug.cgi?id=8894
Previous Pull #1274 was abandoned since there were heavy merge conflicts. As per Walter's comment I've tried to create a single function for the gagging workarounds, but I've only managed to do this for two cases (TOKdotti and TOKdot).
Two distinct cases remain which are hardcoded, I think it would be too hard to force it all into one function. Anyway this should all be temporary until we have a good system for lookups which doesn't depend on gagging and global state.

This pull request introduced a regression:
https://issues.dlang.org/show_bug.cgi?id=14987


CAMEL-12004 Add isDebugEnabled() guard for debug level logs

I added the debug level guards to the one that I found with my script in the latest revision of source code.

Thanks for the pull request.
Imho it would be better to convert the statements to parametrized log messages (where possible). That also saves the cost of the string concatenation (I do not see any potentially costly parameter creation) and does not add the complexity of an additional if statement to the code.

I think the best way to deal with this problem is to use slf4j. But I don't know how costly the migration will be. I can look into the changes and try to parameterize them if its possible if this is the best solution in your opinion.


Try to split longer functions into smaller "coherent" ones (clean code);

@ArielMAJ Can I get an elaboration on what to do here?

The functions are really long and hard to understand. The aim here was refactoring in such a way that the functionality wouldn't change, but there would be more readable functions doing a small amount of work each. This requires understanding the code and thinking of good ways of splitting/naming it. It's not exactly beginner friendly, but feel free to work on it. I might try to find some time next weekend to explain this a little bit better, if you need more elaboration.


Add plugin group versioning and description

What this PR does / why we need it
This PR includes multiple improvements.  I normally would have split this into multiple PRs, but since the changes affected the same code, I decided to make one PR to save time.
Note that this PR remains in draft because it should not be merged until the different central repositories have been migrated to the new DB schema (see below).
The changes are:

Add a description to plugin groups
Add versioning to plugin groups like we have for plugins
If different versions of the same group are provided by different discoveries, merge them (like we do for plugins)
If the same version of a group is provided by different discoveries, keep the first one found only (like we do for plugins)
Allow installing from the latest plugin group when no version is specified by the user

Backwards-compatibility
Backwards-compatibility with alpha.0 and alpha.1 is NOT preserved for plugin groups.
The reason for the break is that the alpha.[01] CLIs expect to find a group by looking for vendor-publisher/name (e.g., vmware-tkg/default:v2.1.0, but the new repos will have the name only be default, so it will not match for older CLIs.
I think we should take the hit and go ahead with this break, but notify the teams using the alpha.[01] releases.
Since backwards-compatibility is not respected anyway, I broke it also by changing the column name Version to PluginVersion for plugin groups.  This new name will avoid confusion.
The UX changes this PR brings:
1- Publishing plugins
We no longer publish a "plugin group" but we publish a "plugin group version".  This means that each time a team publishes, they must specify which version of the plugin group they are publishing; the same goes for activating/deactivating a plugin group version.
The dev also needs to publish a description when a brand new plugin group is created.
tanzu builder inventory plugin-group add , tanzu builder inventory plugin-group activate and tanzu builder inventory plugin-group deactivate take a new mandatory flags: --version
make inventory-plugin-group-add, make inventory-plugin-group-activate and make inventory-plugin-group-deactivate still take $PLUGIN_GROUP_NAME_VERSION and split it into name:version automatically.  As an alternative, a publisher can also use $PLUGIN_GROUP_NAME and $PLUGIN_GROUP_VERSION as two variables instead of one.
tanzu builder inventory plugin-group add also takes an optional new --description flag.  This flag does not need to be used if the plugin group already exists in the DB (since the description is already there).  If the plugin group is a completely new group, then if --description is not specified, the publication will fail.
make inventory-plugin-group-add takes an extra optional variable PLUGIN_GROUP_DESCRIPTION
A new plugin project will get the same modified make targets as described above (through the modified cmd/plugin/builder/template/plugintemplates/plugin-tooling.mk.tmpl)
As expected the --override flag for builder inventory plugin-group add now applies to overwriting a single version of a plugin group.
2- Installing plugins using a group
The format to install plugins from a group uses the notation groupname:groupversion.  For example tanzu plugin install --group vmware-tkg/default:v2.1.0.  I chose this option for two reasons:
a) This is how the command looks currently since a version is part of the group name field
b) There is already a --version flag for the plugin install command so using another flag seemed like it could make things confusing.
If a plugin group version is not specified, the latest plugin group version will be used, like we do for plugins: tanzu plugin install --group vmware-tkg/default
I have added Example to the plugin install command to show the different ways it can be used.
3- Searching for groups
tanzu plugin group search now has a --show-details flag and behaves like tanzu plugin search in its output.  A description column is also added.
Note that the content of a plugin group version is still not accessible.  A new plugin group get command will be done in another PR.
4- Air-gapped
No real change: the version of the group can be specified using the name:version format.  For example: tz plugin download-bundle --to-tar plugin_bundle.tar --group vmware-tkg/default:v2.1.0
If a group version is not specified, the latest version will be used, similarly to how plugin install --group now behaves.  This is up for discussion; maybe for air-gapped we want to require the version of the group to be specified?
Some implementation details:

There are new columns in the inventory tables:

PluginGroups has a new GroupVersion column which is a primary key
PluginGroups has a new Description column
AvailablePluginGroups has a new GroupVersion column which is a primary key to properly identify a plugin group version used for air-gap
A script will be written to migrate old repositories to this new format
This PR cannot be merged until the repositories have been migrated or else the new CLI won't be able to read from those repositories

the local docker test repos have been updated with the new DB schemas
the alpha.0 and alpha.1 CLIs will no longer work with these new repos when dealing with plugin groups

Which issue(s) this PR fixes
Fixes # N/A
Describe testing done for PR
1- Testing searching and using plugin groups:
# Setup CLI
$ \rm -rf hack/central-repo/registry-content
$ rm ~/.config/tanzu/config*
$ rm ~/.cache/tanzu/plugin_inventory
$ tz ceip-participation set false
$ make start-test-central-repo
[...]
$ tz plugin source update default -u localhost:9876/tanzu-cli/plugins/central:small
[ok] updated discovery source default
$ tz config set env.TANZU_CLI_PLUGIN_DISCOVERY_IMAGE_SIGNATURE_PUBLIC_KEY_PATH $tc/hack/central-repo/cosign-key-pair/cosign.pub
# Add additional discoveries which provide extra versions of the same plugin groups
$ tz config set env.TANZU_CLI_ADDITIONAL_PLUGIN_DISCOVERY_IMAGES_TEST_ONLY localhost:9876/tanzu-cli/plugins/sandbox1:small,localhost:9876/tanzu-cli/plugins/sandbox2:small
$ tz config set env.TANZU_CLI_PLUGIN_DISCOVERY_IMAGE_SIGNATURE_VERIFICATION_SKIP_LIST localhost:9876/tanzu-cli/plugins/sandbox1:small,localhost:9876/tanzu-cli/plugins/sandbox2:small

$ # New "plugin group search" output with "lastest" and "description"
$ tz plugin group search
[i] Reading plugin inventory for "localhost:9876/tanzu-cli/plugins/central:small", this will take a few seconds.
[i] Reading plugin inventory for "localhost:9876/tanzu-cli/plugins/sandbox1:small", this will take a few seconds.
[!] Skipping the plugins discovery image signature verification for "localhost:9876/tanzu-cli/plugins/sandbox1:small"

[i] Reading plugin inventory for "localhost:9876/tanzu-cli/plugins/sandbox2:small", this will take a few seconds.
[!] Skipping the plugins discovery image signature verification for "localhost:9876/tanzu-cli/plugins/sandbox2:small"

  GROUP                DESCRIPTION                   LATEST
  vmware-tkg/default   Desc for vmware-tkg/default   v22.22.22
  vmware-tmc/tmc-user  Desc for vmware-tmc/tmc-user  v22.22.22

# Filter by name
$ tz plugin group search --name default
[x] : incorrect plugin group "default" specified
$ tz plugin group search --name vmware-tkg/default
  GROUP               DESCRIPTION                  LATEST
  vmware-tkg/default  Desc for vmware-tkg/default  v22.22.22
$ tz plugin group search --name vmware-tkg/default -o yaml
- description: Desc for vmware-tkg/default
  group: vmware-tkg/default
  latest: v22.22.22

# New "--show-details" to list all group versions
$ tz plugin group search --name vmware-tkg/default --show-details
name: vmware-tkg/default
description: Desc for vmware-tkg/default
latest: v22.22.22
versions:
    - v0.0.1
    - v9.9.9
    - v11.11.11
    - v22.22.22
$ tz plugin group search --name vmware-tkg/default --show-details -o yaml
- name: vmware-tkg/default
  description: Desc for vmware-tkg/default
  latest: v22.22.22
  versions:
    - v0.0.1
    - v9.9.9
    - v11.11.11
    - v22.22.22

# Show details about all groups
# Notice how the plugin group of the same name coming from different discoveries are merged
# with all version shown properly
$ tz plugin group search --show-details
name: vmware-tkg/default
description: Desc for vmware-tkg/default
latest: v22.22.22
versions:
    - v0.0.1
    - v9.9.9
    - v11.11.11
    - v22.22.22

name: vmware-tmc/tmc-user
description: Desc for vmware-tmc/tmc-user
latest: v22.22.22
versions:
    - v0.0.1
    - v9.9.9
    - v11.11.11
    - v22.22.22

$ tz plugin group search --show-details -o yaml
- name: vmware-tkg/default
  description: Desc for vmware-tkg/default
  latest: v22.22.22
  versions:
    - v0.0.1
    - v9.9.9
    - v11.11.11
    - v22.22.22
- name: vmware-tmc/tmc-user
  description: Desc for vmware-tmc/tmc-user
  latest: v22.22.22
  versions:
    - v0.0.1
    - v9.9.9
    - v11.11.11
    - v22.22.22

# Plugin installation from a group VERSION
$ tz plugin install --group vmware-tmc/tmc-user:v9.9.9
[i] Installing plugin 'account:v9.9.9' with target 'mission-control'
[i] Installing plugin 'apply:v9.9.9' with target 'mission-control'
[...]

$ tz plugin install --group vmware-tmc/tmc-user:v0.0.0
[x] : unable to find plugin group vmware-tmc/tmc-user:v0.0.0
$ tz plugin install --group vmware-tmc/tmc-user:v0.0.1
[i] Installing plugin 'account:v0.0.1' with target 'mission-control'
[i] Installing plugin 'apply:v0.0.1' with target 'mission-control'
[i] Installing plugin 'audit:v0.0.1' with target 'mission-control'
[...]

# If no version is specified, the latest one is used, like for plugins
$ tz plugin install --group vmware-tmc/tmc-user
[i] Installing plugin 'account:v22.22.22' with target 'mission-control'
[i] Installing plugin 'apply:v22.22.22' with target 'mission-control'
[...]

2- Publishing plugin:
WILL BE ADDED
3- Air-gapped:
WILL BE ADDED
Release note

Plugin groups are now versioned.  This affects their publishing and their usage.  A description is now also supported for plugin groups.

Additional information
Special notes for your reviewer
A DB migration script will be provided in a separate PR.
Questions:

For air-gapped, do we want to require the version of the group to be specified in plugin download-bundle --group?
Should we allow a different description per group version (instead of one per group)?  We don't allow this for plugins.

For air-gapped, do we want to require the version of the group to be specified in the plugin download-bundle --group?

I think it should be fine to use the latest available. However, we should log which plugin-group version we are using to download the plugin bundle. Showing something like Downloading plugins from plugin-group vmware-tkg/default:v9.9.9 ... would be useful for the user. WDYT?

Should we allow a different description per group version (instead of one per group)? We don't allow this for plugins.

I think the current implementation of not allowing different plugin group descriptions is fine. That way we will also have a consistent naming scheme between plugin and plugin-groups.

Rebased but still missing the manual testing steps for air-gapped and plugin publishing.  Will get to add that soon.

Thanks for the review @anujc25.
Since the DB schema changes, I will first prepare a new version of the plugin DB before merging the PR.


core: Fix issue-331 memo value is being dropped when generating SEP-24 interactive URL JWT and more_info_url JWT

Closes #331
https://github.com/stellar/java-stellar-anchor-sdk/issues/331

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
paymentservice.stellar, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.

What
Fixed the memo value is being dropped when generating SEP-24 interactive URL JWT and more_info_url JWT
Why
Bug
Known limitations
N/A

Reference Server Preview is available here:https://anchor-ref-pr333.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr333.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr333.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr333.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr333.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr333.previews.kube001.services.stellar-ops.com/

Reference Server Preview is available here:https://anchor-ref-pr333.previews.kube001.services.stellar-ops.com/SEP Server Preview is available here:https://anchor-sep-pr333.previews.kube001.services.stellar-ops.com/


hw 5

How did you use the SAM optimizer? SAM doesn't work with just using optimizer.step()!

Please also add the tensorboard files with the experiments, and the README.md file as requested in the Assignment.

How did you use the SAM optimizer? SAM doesn't work with just using optimizer.step()!

No, it does not. I have attempted to run SAM by providing a closure that returns the loss value as param to optimizer.step() like this:
def get_loss():
                self.__optimizer__.zero_grad()
                loss = self.__criterion__(outputs, targets)
                loss.backward()
                return loss

Doing so, I ran into this error:
RuntimeError: Trying to backward through the graph a second time (or directly access saved tensors after they have already been freed). Saved intermediate
values of the graph are freed when you call .backward() or autograd.grad(). Specify retain_graph=True if you need to backward through the graph a second time or if you need to access saved tensors after calling backward.

After trying a few things (inlcuding setting retain_grapth to true, as suggested) and running into different errors which I cannot recall, I dropped using SAM at all, due to time constraint.


Page Link is Inaccurate

The link, Save to OneDrive is not accurate.  What is displayed and demonstrated here is how to save to SharePoint.  The original mixed reality video on YouTube on this topic demonstrates how to save to OneDrive in the demo and references this page to copy and paste the code in for the dynamic file content (to properly format the file contents from Power Apps to OneDrive).  The code doesn't exist.  I reached and out the author of the mixed reality video on Twitter and she responded the code doesn't exist here anymore but try SharePoint demo here.  I have been unable to find anyone that has successfully taken a mixed reality photo in Power Apps and upload it to OneDrive.  Having the steps here would be great.

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

ID: be6dda1c-852e-7f8b-48b5-e0c2a6e6711a
Version Independent ID: 19b9ed6c-04dc-5e44-48a6-75ef12f91028
Content: How do I find and run apps in Power Apps? - Power Apps
Content Source: powerapps-docs/user/index.md
Service: powerapps
Sub-service: end-user
GitHub Login: @mduelae
Microsoft Alias: mkaur

@gotoreports Thank you for the feedback. The topic that you sent feedback on is this: https://docs.microsoft.com/powerapps/user/. However, from your comments, it seems you're actually referring to a different topic. Which topic are you referring to?
Thanks,
Mints
Power Apps Docs Teams

@gotoreports since I haven't heard back I'm going to close this issue.
Thanks,
Mints


fix check for timeout

Signed-off-by: zhangyue<EMAIL_ADDRESS>fix #520

/ok-to-test
/lgtm
/approve


Add read both lag and correlation value from linear correlation vmp

Hi Faruk,
I would like to read both lag and correlation value from a vmp file from linear correlation analysis.
Currently, when I read the vmp file, I get only a matrix of lag value.
However, I would like to get correlation map as well to mask my ROI.
Thank you so much in advance.
Kenshu

@kenshukoiso thanks for opening this issue. It turns out that the data was read correctly. However, the key detail was that the floating numbers were encoding the lags and correlation values at the same time. For instance a map read with value 15.3632 contains both lag information 15 and correlation coefficient 0.3632.
After discovering this, I have now modified the VMP reader to spit out two maps instead of one only if the VMP map is a lag correlation map.
So, please update your bvbabel and try again.

Thanks a lot, Faruk for your investigation and for updating the script super fast!!


Client doesn't receive rows if those rows existed on the table prior to electrification

Setup:

Create a simple table (no FK, etc.)
Add a row to the table
Electrify the table
Sync the table on the client (const shape = await db.{table}.sync(); await shape.synced;)
Query the table on the client (const { results } = useLiveQuery(db.{table}.liveMany());)

Expected results: results contains the row.
Actual results: results doesn't. If you modify the row in any way, it will.
Also in Discord https://discordapp.com/channels/933657521581858818/1221983203812835328

@ondrej Thanks for the report.
We've identified the root cause of the bug and are working on a fix.


Added - [Basically any No Starch Press books] to the end

[ ] I have read freeCodeCamp's contribution guidelines.
[ ] My pull request has a descriptive title (not a vague title like Update index.md)
[ ] My pull request targets the master branch of freeCodeCamp.
[ ] None of my changes are plagiarized from another source without proper attribution.
[ ] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thank you for your contribution.  At this time we have decided not to merge your pull request.  In future PRs please try to include at a minimum a link to the resource and optionally an explanation of why it is useful.
Happy Coding!


Fixed errors when not using physics and navmesh

Which branch your pull-request should merge into?

2.1: BugFixes and Improvements for Current LTS branch

Describe your changes
Remove lua_ax_base_AnimationCache_constructor function.
and fixed errors when not using physics and navmesh.
Issue ticket number and link
Checklist before requesting a review
For each PR

[ ] Add Copyright if it missed:
- "Copyright (c) 2019-present Axmol Engine contributors (see AUTHORS.md)."

[ ] I have performed a self-review of my code.
Optional:

[ ] I have checked readme and add important infos to this PR.
[ ] I have added/adapted some tests too.

For core/new feature PR

[ ] I have checked readme and add important infos to this PR.
[ ] I have added thorough tests.

Any modifications on auto generated code file will overwrite by genbindings ci


Given GPM Shutdown, GPMDP should default to YTM

As we all know, the shutdown of GPM is complete. But the show goes on for GPMDP, thanks to the YouTube Music Beta feature.
Unfortunately, if you had GPM mode enabled after the shutdown, the only way to switch back is via the tray icon - not easily discoverable.
I'd like to make a feature request - have the app open in YTM mode by default, and make the switch to YTM button always appear in GPM mode.
Checklist:

[X] I have checked that there are no issues with similar or the same content
YOU SHOULD CHECK CLOSED ISSUES AS WELL

[X] I have checked the FAQ (https://github.com/MarshallOfSound/Google-Play-Music-Desktop-Player-UNOFFICIAL-/wiki/FAQ) and the answer I am looking for is not there

[X] I have double checked and can reproduce the issue

OS: Windows (though feature request is universal)
GPMDP Version: 4.7.1
Issue Descriptions:
Steps to Reproduce: N/A

This would be great. I recently reinstalled my OS and with it, GPM desktop player, and since the settings do not show (for Linux at least, I don't know about other OSes) on the tranfer screen, I have to hit:
Transfer to YouTube Music -> Explore
every time to access YouTube Music. Something doesn't seem to be initialized properly when this happens, so I can't access GPM settings via the app settings after the "transfer", and things like forward and back (hotkeys) do not properly work.

Time to rename the app & remove GPM completely. Simple.

Hey @DarrienG if you have a systray somewhere(like in polybar) then you can switch to YTM from there. That is what I depend on right now essentially.

Hey @DarrienG if you have a systray somewhere(like in polybar) then you can switch to YTM from there. That is what I depend on right now essentially.

Defaulting back to GPM and having to get back to YTM mode in a round about way every time is an issue that is probably best solved by just removing GPM mode at this point. After the 31. December the GPM mode has no point anymore as the transfer function is disabled.

Defaulting back to GPM and having to get back to YTM mode in a round about way every time is an issue that is probably best solved by just removing GPM mode at this point. After the 31. December the GPM mode has no point anymore as the transfer function is disabled.

Curious, since last release was over 1 year ago, has development on this project honestly been abandoned?

Curious, since last release was over 1 year ago, has development on this project honestly been abandoned?

This would be a great step forward for this application. Getting it updated to work with YTM only.
Looking forward to some update on this.

I've started using YouTube Music Desktop instead


Clarify the behavior of Encoding.RegisterProvider with respect to multiple providers and defaults

Note: Currently, only the Framework docs at https://msdn.microsoft.com/en-us/library/system.text.encoding.registerprovider(v=vs.110).aspx have a description of the method (quoted below), but I expect that to become the content at https://docs.microsoft.com/en-us/dotnet/core/api/system.text.encoding

It seems that calling Encoding.RegisterProvider not only makes additional code pages available, but also changes the default code page, as reported by Encoding.GetEncoding(0). This important aspect should be stated explicitly. Currently, the docs only say:

makes character encodings available on a platform that does not otherwise support them. Once the encoding provider is registered, the encodings that it supports can be retrieved by calling any Encoding.GetEncoding overload.

While you could argue that the above also implies that  Encoding.GetEncoding(0)  will be provider-specific, I suggest making that more obvious.

It seems that only one provider can be registered at the time (last one registered wins), but that is not entirely clear:

If the RegisterProvider method is called to register multiple providers that handle the same encoding, the last registered provider is the used for all encoding and decoding operations. Any previously registered providers are ignored.

I find the first half of that sentence confusing (you cannot actually register multiple providers, as the second half states, and what does "the same encoding" refer to, and why does it matter, if the newly registered provider replaces the previous one?), and if my interpretation is correct, I suggest simply trimming down the sentence to:

The last registered provider is the used for all encoding and decoding operations. Any previously registered providers are ignored.

@tarekgh Could you review this, please?

For Encoding.GetEncoding(0) we need to clarify that when there is no registered provider, we return UTF8 encoding. when a provider is register, the provider can return different Encoding than UTF8. I would avoid mentioning the word "Default" because this will confuse it with the property Encoding.Default. Also it is worth mentioning when using the provider from System.Text.Encoding.Codepages, Encoding.GetEncoding(0) will return the encoding matching the system ACP when running on Windows OS.
For registering multiple providers, I am seeing trimming the sentence as suggested is not enough. we can have a provider that provide some encodings but not all encodings. at that case if the caller requested an encoding which is not supported by last registered provider would results to try the previous registered provider and so on till we find a provider can return the specified encoding. Personally I am seeing the current sentence is not confusing but it looks not clear to @mklement0 so we may think in rephrasing it.
@rpetrusha please let me know if you have any more questions

Thanks @tarekgh. And thanks, @mklement0, for opening this issue. I've assigned it to myself, and will update the docs.

Thanks, @rpetrusha.
Honestly, even after reading this I'm slightly confused, so I'll try to summarize the rules here - please tell me if that covers all aspects:

By default, Encoding.GetEncoding(0) -  code page ID 0 signifying a default value of sorts -
reports the same value as Encoding.Default.

Once an encoding provider has been registered, Encoding.GetEncoding(0) reports that provider's notion of the default encoding.

Does every encoding provider invariably redefine the default? Or can a provider choose to leave the then-effective default in place?

Registering the System.Text.Encoding.CodePages NuGet package adds all legacy Windows code pages (encodings) and additionally makes Encoding.GetEncoding(0) return the active "ANSI" code page (the encoding of the code page associated with the legacy system locale on Windows, which, on Unix systems, will be inferred from the active locale (in Core 2)).

It is possible to register multiple encoding providers, but the following rules apply:

The provider registered last determines the value of Encoding.GetEncoding(0) (see above).  This means that you have no access to the default encoding as defined by previously registered providers, correct?

Multiple providers can (and typically will) register distinct encodings, but for any given  encoding registered by more than one provider the definition of the provider registered last is in effect.

By default, Encoding.GetEncoding(0) - code page ID 0 signifying a default value of sorts -
reports the same value as Encoding.Default.

This is no true any more after registering the providers. this is why I mentioned try to avoid the word default. initially we didn't expose Encoding.Default because of the confusion but we had to expose it after the change in the plans to cover all desktop APIs in the net core. so please don't tie Encoding.GetEncoding(0) with Encoding.Default

Does every encoding provider invariably redefine the default? Or can a provider choose to leave the then-effective default in place?

it is up to the provider to decide if need to return something for Encoding.GetEncoding(0) or not.

The provider registered last determines the value of Encoding.GetEncoding(0) (see above). This means that you have no access to the default encoding as defined by previously registered providers, correct?

As I mention please split the concept of Encoding.Default from Encoding.GetEncoding(0) and everything would be clear. treat Encoding.GetEncoding(0) as any other encoding code page

That clears it all up; thanks, @tarekgh.
As a result:

other places in the documentation need updating (see below)

it raises the question how to reframe code-page identifier 0 in the docs - effectively, it is the last registered encoding provider's  default (definition of of 0). As stated, however, that concept loses its usefulness with multiple registered providers.
Perhaps 0 should be called deprecated?

Additional places in the current docs that need updating.

"0 (zero), to use the default encoding."

https://docs.microsoft.com/en-us/dotnet/core/api/system.text.encoding#System_Text_Encoding_GetEncoding_System_Int32_

https://msdn.microsoft.com/en-us/library/wzsz3bk3(v=vs.110).aspx

@mklement0 I agree and thanks for your feedback. it is useful to reduce the confusion to the users.

@rpetrusha should we change the milestone on this one?

@mairaw, yes, I'll move it to June.


Add Okta SSO to list of IDP providers from One CLI

Add Okta SSO related features to One CLI:
Proposed Changes
- Associate new docker image dnxsolutions/aws-okta-auth
- Create new command **one auth okta** for authentication with new IDP
- Create new command under **one auth configure** for Okta IDP parameters configuration

Overall everything looks good. Just a small fix and I think It's ready.
Also, the lint is not passing. Could you please fix It?
./one/prompt/idp.py:61:2: W292 no newline at end of file
./one/commands/auth.py:13:128: E501 line too long (141 > 127 characters)
1     E501 line too long (141 > 127 characters)
1     W292 no newline at end of file

Nice job!

@arthurbdiniz The lint issues are fixed now.


real column pruning

Hello!
I'm using your example with hidden query_col_name and pred_XX params to build connectors to other storages (clickhouse,orc,mysql,mongodb,...). I succeed in pruing columns while reading from the source, but I still have to pass them filled with nulls through the Vertica SDK. And in my case, it is very time-consuming too. If I query a single column out of external table with 20 columns, it can be 10 times slower than fetching a single column out of external table with only one column.
I saw there is a getParserReturnType method, but it is only a column precision that can be changed from there. I also saw a RLETuple type and guess it is possible to avoid passing nulls by encoding them into RLE, but SDK does not support RLETuple as a type for UDx developers. So for now, I came up with using RLE-like groupping inside UDx with an extra column for count. Another thought is to use arrays to prune columns.
Can you please guide me on whether it is possible to remove null columns from the UDParser output to get better perfomance?

Does a query like 'SELECT column1 FROM <table with 20 columns>' take 10 times longer than a query like 'SELECT column1 FROM <table with 1 column>' even if the data volume returned by both queries is the same? I would like to know how long both queries take to send all data to ODBC-Loader.
It needs to read all rows to know the column has only NULL value. If it can know it beforehand, it removes the column from the query or it uses FILLER option in COPY statement to ignore the column.


feat: RunAggregationQuery Trace Instrumentation

Added test for Datastore runAggregationQuery method.

Fixes #1428 ☕

This PR is against jimit/lookup-trace-1 branch.  Once #1441 is merged, I'll rebase this on tracing-main.

Abandoned.


Cannot send chat messages on Windows client

On the Windows client on Windows 11, I cannot send a message. I get this error:
This messge failed to send. Api network error: get "http://api-0.core.keybaseapi.com/_/api/1.0/merkle/root.json?c=1&last=25285882&skip_last=1": x509: certificate signed by unknown authority. Retry or Cancel.

https://github.com/keybase/client/issues/26102#issuecomment-1874506305

Confirmed that this was resolved by re-installing from the website. See https://github.com/keybase/client/issues/26102#issuecomment-1874506305


 When evaluating an expression interactively (such as in the try-box on https://runarberg.github.io/ascii2mathml) it is not uncommon to see dozens of error outputs in the browser console before the expression is ready. By fixing this not only means appeasing the clients console, but genuine bugs will more likely be detected by monitoring the console output.
on many occasions we could easily fall back to rendering incomplete expressions. Such as for an open fence without a closing fence we could render the opening fence as an operator, for incomplete fractions or sub- or superscript we could simply display the notation symbols as operators as well, so ascii2mathml(x^) ⇒ <math><mi>x</mi><mo>^</mo></math> and incomplete roots could render as series a of identifiers (sqrt ↦ <math><mi>s</mi><mi>q</mi><mi>r</mi><mi>t</mi></math>).

Another solution would be to return an empty <mrow> when applying an operation on nothing.

Closing now, possible revisit in the future.


Request to change wordings in the Remarks section.

In the Remarks section of CreateTimer<T>(DateTime, T, CancellationToken) the current wording says.
All durable timers created using this method must either expire or be cancelled using the cancelToken before the orchestrator function completes. Otherwise the underlying framework will keep the instance alive until the timer expires
Suggested change.
All durable timers created using this method must either expire or be cancelled using the cancelToken before an orchestration instance can transition to the "Completed" state. Otherwise the underlying framework will keep the instance in the "Running" state even after the orchestrator function has completed
Please refer to this issue (https://github.com/MicrosoftDocs/azure-docs/issues/78334#issuecomment-881591472) for additional details.

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

ID: e8baac8e-b591-9ce4-5afd-9ce3e3f17966
Version Independent ID: e86f7868-fc74-28d9-28da-6d8b7e24337d
Content: IDurableOrchestrationContext.CreateTimer Method (Microsoft.Azure.WebJobs.Extensions.DurableTask) - Azure for .NET Developers
Content Source: xml/Microsoft.Azure.WebJobs.Extensions.DurableTask/IDurableOrchestrationContext.xml
Service: azure-functions
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Issue moved to Azure/azure-functions-durable-extension #1893 via ZenHub

This issue has been transferred to the repository where the Microsoft.Azure.WebJobs.Extensions.DurableTask package is maintained as #1893.


[WIP] Add extension dtype support to set_index

Still very much a WIP, but wanted to push up for early feedback
Closes https://github.com/dask/dask/issues/5720, closes https://github.com/dask/dask/issues/8011, closes https://github.com/dask/dask/issues/9118

Woo 🎉

Alright, I think this PR is good to go (or at least ready for another review). @ian-r-rose would you mind taking a look whenever you get a chance?


Allow different branch to support legacy repos

Problem being solved
When I'm running on a repo that doesn't have main branch but instead have the legacy master  or even uses other branch as main, I can't use it.
Proposal
Create an arg to allow it, like --branch=

Such a option already exists. Try to add --branch.
Use gitwho [command] --help for a complete list of available options.


paired data issue

Hey everyone.
I am trying to use this tutorial (https://immunarch.com/articles/web_only/v21_singlecell.html) in order to load my 10x TCR data in order to track clonotypes across seurat clusters (as shown at the very bottom of the tutorial)
However I face specific problems, I provide here my code (seu_all is my seurat object and the idents of the object are set as clusters):
barcode_cluster<-Seurat::Idents(seu_all)
immdata_10x <- repLoad("~/sc_repertoire/scRepertoire_c57bl6j/bl6_tcr_data",.mode = "paired")
== Step 1/3: loading repertoire files... ==

Processing "~/sc_repertoire/scRepertoire_c57bl6j/bl6_tcr_data" ...
  -- [1/2] Parsing "/home/testuser11/sc_repertoire/scRepertoire_c57bl6j/bl6_tcr_data/all_contig_annotations.csv" -- 10x (filt.contigs)
  [!] Removed 16155 clonotypes with no nucleotide and amino acid CDR3 sequence.
  -- [2/2] Parsing "/home/testuser11/sc_repertoire/scRepertoire_c57bl6j/bl6_tcr_data/clonotypes.csv" -- unsupported format, skipping

== Step 2/3: checking metadata files and merging files... ==

Processing "~/sc_repertoire/scRepertoire_c57bl6j/bl6_tcr_data" ...
  -- Metadata file not found; creating a dummy metadata...

== Step 3/3: processing paired chain data... ==

Done!

Warning message:
The following named parsers don't match the column names: barcode,is_cell,contig_id,high_confidence,length,chain,v_gene,d_gene,j_gene,c_gene,full_length,productive,fwr1,fwr1_nt,cdr1,cdr1_nt,fwr2,fwr2_nt,cdr2,cdr2_nt,fwr3,fwr3_nt,cdr3,cdr3_nt,fwr4,fwr4_nt,reads,umis,raw_clonotype_id,raw_consensus_id,exact_subclonotype_id

scdata_cl <- select_clusters(immdata_10x$data$all_contig_annotations, barcode_cluster, "Cluster")
Error in select_clusters(immdata_10x$data[[1]], barcode_cluster, "Cluster") :
  Please provide a list with both 'data' and 'meta' elements.

Any input would be appreciated, thanks a lot!

Hi @christoforos-dimitropoulos!
My name is Maria Volobueva, I am the developer of Immunarch.
Thank you for using the package! Could you provide an example of the file you try to load, as we will be able to quickly identify the issues.

Hi @christoforos-dimitropoulos!
My name is Maria Volobueva, I am the developer of Immunarch. Thank you for using the package! Could you provide an example of the file you try to load, as we will be able to quickly identify the issues.

As an input I give the folder with the output of the 10x cellranger vdj pipeline.

@christoforos-dimitropoulos,

Hi I am having a similar issue, the headers look the same to me though in the attached file.
`>immdata<-repLoad("~/TCR/")
== Step 1/3: loading repertoire files... ==
Processing "~/TCR/" ...
-- [1/7] Parsing "C:/Users/Maggie/Documents/TCR/d0_43F_PBMC_20211209_filtered_contig_annotations.csv" -- 10x (filt.contigs)
-- [2/7] Parsing "C:/Users/Maggie/Documents/TCR/d11_13F_PBMC_20220106_filtered_contig_annotations.csv" -- 10x (filt.contigs)
-- [3/7] Parsing "C:/Users/Maggie/Documents/TCR/d168_13F_LN_20220128_filtered_contig_annotations.csv" -- 10x (filt.contigs)
0s  -- [4/7] Parsing "C:/Users/Maggie/Documents/TCR/d168_13F_PBMC_20211209_filtered_contig_annotations.csv" -- 10x (filt.contigs)
-- [5/7] Parsing "C:/Users/Maggie/Documents/TCR/d168_13F_PBMC_filtered_contig_annotations.csv" -- 10x (filt.contigs)
-- [6/7] Parsing "C:/Users/Maggie/Documents/TCR/d176_43F_LN_20211209_filtered_contig_annotations.csv" -- 10x (filt.contigs)
-- [7/7] Parsing "C:/Users/Maggie/Documents/TCR/d43_13F_PBMC_20211209_filtered_contig_annotations.csv" -- 10x (filt.contigs)
== Step 2/3: checking metadata files and merging files... ==
Processing "~/TCR/" ...
-- Metadata file not found; creating a dummy metadata...
== Step 3/3: processing paired chain data... ==
Done!
Warning messages:
1: The following named parsers don't match the column names: barcode,is_cell,contig_id,high_confidence,length,chain,v_gene,d_gene,j_gene,c_gene,full_length,productive,fwr1,fwr1_nt,cdr1,cdr1_nt,fwr2,fwr2_nt,cdr2,cdr2_nt,fwr3,fwr3_nt,cdr3,cdr3_nt,fwr4,fwr4_nt,reads,umis,raw_clonotype_id,raw_consensus_id,exact_subclonotype_id
2: The following named parsers don't match the column names: barcode,is_cell,contig_id,high_confidence,length,chain,v_gene,d_gene,j_gene,c_gene,full_length,productive,fwr1,fwr1_nt,cdr1,cdr1_nt,fwr2,fwr2_nt,cdr2,cdr2_nt,fwr3,fwr3_nt,cdr3,cdr3_nt,fwr4,fwr4_nt,reads,umis,raw_clonotype_id,raw_consensus_id,exact_subclonotype_id
3: The following named parsers don't match the column names: barcode,is_cell,contig_id,high_confidence,length,chain,v_gene,d_gene,j_gene,c_gene,full_length,productive,fwr1,fwr1_nt,cdr1,cdr1_nt,fwr2,fwr2_nt,cdr2,cdr2_nt,fwr3,fwr3_nt,cdr3,cdr3_nt,fwr4,fwr4_nt,reads,umis,raw_clonotype_id,raw_consensus_id,exact_subclonotype_id
4: The following named parsers don't match the column names: barcode,is_cell,contig_id,high_confidence,length,chain,v_gene,d_gene,j_gene,c_gene,full_length,productive,fwr1,fwr1_nt,cdr1,cdr1_nt,fwr2,fwr2_nt,cdr2,cdr2_nt,fwr3,fwr3_nt,cdr3,cdr3_nt,fwr4,fwr4_nt,reads,umis,raw_clonotype_id,raw_consensus_id,exact_subclonotype_id
5: The following named parsers don't match the column names: barcode,is_cell,contig_id,high_confidence,length,chain,v_gene,d_gene,j_gene,c_gene,full_length,productive,fwr1,fwr1_nt,cdr1,cdr1_nt,fwr2,fwr2_nt,cdr2,cdr2_nt,fwr3,fwr3_nt,cdr3,cdr3_nt,fwr4,fwr4_nt,reads,umis,raw_clonotype_id,raw_consensus_id,exact_subclonotype_id
6: The following named parsers don't match the column names: barcode,is_cell,contig_id,high_confidence,length,chain,v_gene,d_gene,j_gene,c_gene,full_length,productive,fwr1,fwr1_nt,cdr1,cdr1_nt,fwr2,fwr2_nt,cdr2,cdr2_nt,fwr3,fwr3_nt,cdr3,cdr3_nt,fwr4,fwr4_nt,reads,umis,raw_clonotype_id,raw_consensus_id,exact_subclonotype_id
7: The following named parsers don't match the column names: barcode,is_cell,contig_id,high_confidence,length,chain,v_gene,d_gene,j_gene,c_gene,full_length,productive,fwr1,fwr1_nt,cdr1,cdr1_nt,fwr2,fwr2_nt,cdr2,cdr2_nt,fwr3,fwr3_nt,cdr3,cdr3_nt,fwr4,fwr4_nt,reads,umis,raw_clonotype_id,raw_consensus_id,exact_subclonotype_id `
d0_43F_PBMC_20211209_filtered_contig_annotations.csv

Hi, @mbartl13!
Thank you very much for providing the data! Looks like this format of column names is unknown to the parser. I will work to add the support for this format in the future versions of Immunarch.
Best regards,
Aleksandr

Closing this issue for now. It will be implemented in the next version of Immunarch.
More details on the next version of Immunarch are here: https://b-t.cr/t/immunarch-will-significantly-evolve-but-it-will-break-things-and-we-need-your-help/1123


bug(cast): abi-encode / abi-decode with nested structs that contain arrays does not work as expected

Component
Cast
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (be451fb 2024-09-11T00:20:35.367236373Z)
What command(s) is the bug in?
cast abi-encode
cast abi-decode
Operating System
None
Describe the bug
Question relates to how to correctly pass arguments to cast abi-encode when it has multiple parameters with one of them being an array.
Context: https://gist.github.com/pcaversaccio/0ef8fb8034594e012a4903dfa992369e
Basic example (yields incorrect output):
cast abi-encode "UpgradeProposal((uint256)[],uint256)" "[(1)]" "123"

versus (does not work)
cast abi-encode "UpgradeProposal((uint256)[],uint256)" "([(1)],123)"

yields
Could not ABI encode the function and arguments. Did you pass in the right types?
Error
parser error:
([(1)],123)
^
expected `[

Notes
Command:
#!/bin/bash

# Define the parameters for the `UpgradeProposal` struct.
CALLS="[(0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB,0,0x79ba5097),(0x303a465B659cBB0ab36eE643eA362c509EEb5213,0,0x79ba5097),(0xc2eE6b6af7d616f6e27ce7F4A451Aedc2b0F5f5C,0,0x79ba5097),(0x5D8ba173Dc6C3c90C8f7C04C9288BeF5FDbAd06E,0,0x79ba5097)]"

EXECUTOR="0x8f7a9912416e8AdC4D9c21FAe1415D3318A11897"

# Salt value ("decentralization is not optional") as a hex string.
SALT="0x646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c"

# Encode the `UpgradeProposal` struct.
ENCODED_PROPOSAL=$(cast abi-encode "UpgradeProposal((address,uint256,bytes)[],address,bytes32)" $CALLS $EXECUTOR $SALT)

# Compute the `keccak256` hash of the encoded proposal.
PROPOSAL_ID=$(cast keccak "$ENCODED_PROPOSAL")

# Save the proposal ID to a file.
echo "$PROPOSAL_ID" > proposal_id.txt

# Output the result.
echo "Encoded UpgradeProposal: $ENCODED_PROPOSAL"
echo "Proposal ID: $PROPOSAL_ID"

Correct:
0x00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000060000000000000000000000000defd1edee3e8c5965216bd59c866f7f5307c9b29646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c00000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001c00000000000000000000000000000000000000000000000000000000000000260000000000000000000000000d7f9f54194c633f36ccd5f3da84ad4a1c38cb2cb00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000000000000000000000000000303a465b659cbb0ab36ee643ea362c509eeb521300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000000000000000000000000000c2ee6b6af7d616f6e27ce7f4a451aedc2b0f5f5c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba5097000000000000000000000000000000000000000000000000000000000000000000000000000000005d8ba173dc6c3c90c8f7c04c9288bef5fdbad06e00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000

versus encoding by cast
0x00000000000000000000000000000000000000000000000000000000000000600000000000000000000000008f7a9912416e8adc4d9c21fae1415d3318a11897646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c00000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001c00000000000000000000000000000000000000000000000000000000000000260000000000000000000000000d7f9f54194c633f36ccd5f3da84ad4a1c38cb2cb00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000000000000000000000000000303a465b659cbb0ab36ee643ea362c509eeb521300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000000000000000000000000000c2ee6b6af7d616f6e27ce7f4a451aedc2b0f5f5c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba5097000000000000000000000000000000000000000000000000000000000000000000000000000000005d8ba173dc6c3c90c8f7c04c9288bef5fdbad06e00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000

Actionable items

[ ] Clarify and document what the correct way to pass arguments is in this situation
[ ] Identify if there is a bug here

Fwiw, the issue is related to how cast abi-encode works with nested structs that also contain arrays (see my above linked gist). Also, when I try to decode the correct payload it fails:
cast abi-decode -i "UpgradeProposal((address,uint256,bytes)[],address,bytes32)" 0x00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000060000000000000000000000000defd1edee3e8c5965216bd59c866f7f5307c9b29646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c00000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001c00000000000000000000000000000000000000000000000000000000000000260000000000000000000000000d7f9f54194c633f36ccd5f3da84ad4a1c38cb2cb00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000000000000000000000000000303a465b659cbb0ab36ee643ea362c509eeb521300000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000000000000000000000000000c2ee6b6af7d616f6e27ce7f4a451aedc2b0f5f5c00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba5097000000000000000000000000000000000000000000000000000000000000000000000000000000005d8ba173dc6c3c90c8f7c04c9288bef5fdbad06e00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000

The syntax is correct for the first block, not the second

The syntax is correct for the first block, not the second

can you elaborate? Not sure I can follow.

In OP "Basic example" is correct, each parameter corresponds to a CLI argument; the "versus (does not work)" block is not correct

In OP "Basic example" is correct, each parameter corresponds to a CLI argument; the "versus (does not work)" block is not correct

correct - as background this example is coming from me since I literally played around with this for an hour yesterday. The syntax ([(1)],123) would make much more sense as it's a nested struct that I represent here.
Also, more importantly, please check my bash script and the encoding of the complex struct. It's not correct even with the given syntax:
cast abi-encode "UpgradeProposal((address,uint256,bytes)[],address,bytes32)" "[(0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB,0,0x79ba5097),(0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB,0,0x79ba5097)]" "0x8f7a9912416e8AdC4D9c21FAe1415D3318A11897" "0x646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c"

They're 2 different encodings, cast abi-encode encodes for function arguments, not a single struct.
Essentially you're comparing the encoding of (cast abi-encode):
function f( (address,uint256,bytes)[] arg1, address arg2, bytes32 arg3 )

to (expected):
function g( ((address,uint256,bytes)[],address,bytes32) arg1)

You're looking for the second one, so the correct command is achieved by wrapping the struct fields in another pair of parentheses:
cast abi-encode "f(((address,uint256,bytes)[],address,bytes32))" "([(0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB,0,0x79ba5097),(0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB,0,0x79ba5097)],0x8f7a9912416e8AdC4D9c21FAe1415D3318A11897,0x646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c)"

The examples in OP:
$ cast abi-encode "UpgradeProposal((uint256)[],uint256)" "[(1)]" "123"
0x0000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000007b00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001
$ cast abi-encode "UpgradeProposal(((uint256)[],uint256))" "([(1)],123)"
0x00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000000000000000000040000000000000000000000000000000000000000000000000000000000000007b00000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001

Note the extra 0x00..20 at the start

Hmm I see, but:
cast abi-encode "UpgradeProposal(((address,uint256,bytes)[],address,bytes32))" "([(0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB,0,0x79ba5097),(0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB,0,0x79ba5097)],0x8f7a9912416e8AdC4D9c21FAe1415D3318A11897,0x646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c)"

produce the following:
0x000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000600000000000000000000000008f7a9912416e8adc4d9c21fae1415d3318a11897646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c0000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000e0000000000000000000000000d7f9f54194c633f36ccd5f3da84ad4a1c38cb2cb00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000000000000000000000000000d7f9f54194c633f36ccd5f3da84ad4a1c38cb2cb00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060000000000000000000000000000000000000000000000000000000000000000479ba509700000000000000000000000000000000000000000000000000000000

If you want to replicate, use this:
// SPDX-License-Identifier: WTFPL
pragma solidity ^0.8.19;

contract ProposalId {
    struct Call {
        address target;
        uint256 value;
        bytes data;
    }

    struct UpgradeProposal {
        Call[] calls;
        address executor;
        bytes32 salt;
    }

    function computeProposalId() external pure returns (bytes memory) {
        Call[] memory calls = new Call[](4);
        calls[0] = Call({target: 0xD7f9f54194C633F36CCD5F3da84ad4a1c38cB2cB, value: 0, data: hex"79ba5097"});
        calls[1] = Call({target: 0x303a465B659cBB0ab36eE643eA362c509EEb5213, value: 0, data: hex"79ba5097"});
        calls[2] = Call({target: 0xc2eE6b6af7d616f6e27ce7F4A451Aedc2b0F5f5C, value: 0, data: hex"79ba5097"});
        calls[3] = Call({target: 0x5D8ba173Dc6C3c90C8f7C04C9288BeF5FDbAd06E, value: 0, data: hex"79ba5097"});

        address executor = 0xdEFd1eDEE3E8c5965216bd59C866f7f5307C9b29;
        bytes32 salt = hex"646563656e7472616c697a6174696f6e206973206e6f74206f7074696f6e616c";

        UpgradeProposal memory upgradeProposal = UpgradeProposal({calls: calls, executor: executor, salt: salt});

        return abi.encode(upgradeProposal);
    }
}

the arguments are not the same as in the solidity script, calls is length 2 in cast and 4 in your "expected"

the arguments are not the same as in the solidity script: calls is length 2 in cast and 4 in your "correct encoding"

I'm stupid - wrong executor address in the above example. Now everything works well. Can we please have as actionable item that we document how to do such nested structs correctly in the docs?

Thanks @DaniPopes!
Moving this to foundry-rs/book as the actionable item is related to the documentation and confirmed to not be a bug


Make Integer#pow almost spec-compliant

This takes it most of the way - just some BigInt fun-stuff to fix.

Minus the NATFIXME specs (related to rationals), this is now spec-compliant.

Sorry @ryangjchandler, I chose to merge @richardboehme's PR first, so now this PR has some conflicts. :grimacing:

All good, will resolve later!

@seven1m All rebased and updated :)


Fix csg bunny

Set precise={false} on Center. Not sure why this fixes the error, might be related to
https://github.com/mrdoob/three.js/pull/26919 and a combination of csg mesh, it works fine on other meshes.

On further analysis the regression does appear in r158 of threejs where this change was made. Not sure if this counts as an edge case which was missed.
Default value in drei Center is precise = true

Fix AccumulativeShadows alphaTest and RandomizedLight intensity
Change Environment blur to backgroundBluriness

[ ] ready to merge

is this one also ready?

I'm not sure if this is an introduced bug in three in how it handles precise Box3.setFromObject calculations, or a bug in three-bvh-csg. But yeah the example is no longer broken if that's all that matters.


The Naming of "custom_objects"

Hi, about the source code of "siren.py",
tf.keras.utils.get_custom_objects().update({
    'sine': Sine,
    'siren_uniform': SIRENInitializer,
    'siren_first_uniform': SIRENFirstLayerInitializer,
    'SinusodialRepresentationDense': SinusodialRepresentationDense,
    'ScaledSinusodialRepresentationDense': ScaledSinusodialRepresentationDense,
})

I think the purpose of the code is to make custom object available by calling "tf.keras.utils.get_custom_objects()".
Therefore I would like to ask why the name declared be like
"sine" but not "Sine";
"siren_uniform" but not "SIRENInitializer";
"siren_first_uniform" but not "SIRENFirstLayerInitializer"?
I think it should be like
tf.keras.utils.get_custom_objects().update({
    'Sine': Sine,
    'SIRENInitializer': SIRENInitializer,
    'SIRENFirstLayerInitializer': SIRENFirstLayerInitializer,
    'SinusodialRepresentationDense': SinusodialRepresentationDense,
    'ScaledSinusodialRepresentationDense': ScaledSinusodialRepresentationDense,
})

And loading model can be achieved by utilizing
load_model =
keras.models.load_model('./weight_model.h5',custom_objects=tf.keras.utils.get_custom_objects())

Cuz the native name of the class usually be like: Sine.__name__ = "Sine"
Is there other purpose intended to be done, so that we cannot use the origin class name directly?
Thank you!

You are confusing a few things. Names for custom objects are not exactly important, as long as they are called with the current name always in your own code.
Look at how the activation functions are defined, they are all lower case in Keras, so sine is more appropriate than Sine when passing to Activation().
Same with initializers. The actual class of the model or layer that needs to be resolved however just have the same name, so that Keras can resolve it during class creation. Look at custom activation functions for this example.

You are confusing a few things. Names for custom objects are not exactly important, as long as they are called with the current name always in your own code.
Look at how the activation functions are defined, they are all lower case in Keras, so sine is more appropriate than Sine when passing to Activation().
Same with initializers. The actual class of the model or layer that needs to be resolved however just have the same name, so that Keras can resolve it during class creation. Look at custom activation functions for this example.

I get it! Thanks a lot!


Rename the ops file to avoid install.

The client will install all .h files so rename to avoid install the ops files.

Does it affect the use of storage here?

Does it affect the use of storage here?

No affect to graph or storage.


[VS Code] [Audio] Request failed with status code 502

Error:
Request failed with status code 502
Steps to Reproduce:

Version Data

extensionName
VSLS-Audio

extensionVersion
0.1.48

applicationName
VSCode

applicationVersion
1.32.3

platformName
Windows

platformVersion
17.7.0

Closing as a duplicate of #1829.


L3 C-Test code - device settings - dsFPD

Implement L3 C code test suite for dsFPD
Acceptance criteria:

Implement all functionality.
Identify External dependency

merged to develop


mention skipITs

Local development
With Maven you can locally install a SNAPSHOT version of the code, to use from other projects
directly without having to wait for the Maven repository. Use:
mvn install

to run the full tests and do a local install. You can also use
mvn install -DskipITs

to run only the unit tests and do a local install. This is faster.

thanks!


announcements - clickable links

What would you like to be added:
For our announcements banners, make it "clickable" when there's a URL present on the announcement item.  Add a caret when the banner is clickable
Why is this needed:
If we put a message that, "an update is needed", it should be able to redirect to app stores.

Acceptance Criteria: Announcement  clickable links to be added on top Balances
Android:

[ ]  Balances > Check clickable link on Top for new build release

iOS:

[ ]  Balances > Check clickable link on Top for new build release

Whenever a new build is published an announcement link should be displayed on the top of Balances


Modelzoo

Great paper!
Where can I find the trained models?
Thanks

Thanks! You can find them in the README, you can expand the sections by clicking on the little black triangle link


Merge

Coverage remained the same at 84.927% when pulling f90a5d807efa3e8b82a91b1f16358f85bd7c0d89 on strehle:master into 69fc38968ecf6d0748acbfec7aac9ca32cf4ed3d on cloudfoundry:master.


Request for more illustration on the usage of Power Automate Web API to Create Flows using code

Only minimal information is available in configuring clientData property in the article https://docs.microsoft.com/en-us/power-automate/web-api. It would be helpful if you can illustrate in details of how to create a flow and add different type of actions with examples and demos.

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

ID: eecc2503-eee7-8779-2445-d6cd6968a0bd
Version Independent ID: 532be787-8be9-c9b5-37a2-88841c5b8118
Content: Flows are now stored in Common Data Service and use the rich Web API - Power Automate
Content Source: articles/web-api.md
Service: business-applications
Product: ****
Technology: ****
GitHub Login: @stepsic-microsoft-com
Microsoft Alias: stepsic

@radioblazer Could you please evaluate this feedback & work with me or @MSFTMan if doc updates are needed? Thanks.

@radioblazer  The details of the client data field are documented here https://docs.microsoft.com/en-us/azure/logic-apps/logic-apps-workflow-definition-language
Thank you.


fix readme bug

PR types
Bug fixes
PR changes
Docs
Describe
fix readme bug of install shell

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.root seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


chore:  fix group node spacing

Summary | Résumé
Small updating to fix spacing + truncating text.

Fixes issue where text was not truncating properly and was covered by arrows

Updated width for section titles


Enhancement cross chain contract

Index multi parent chain blocks at one time.
Add transaction  for indexing side chain.


Tap View signer to search email

When we tap "View Signer" in the dialog showing the encryption status, the user is taken to Openkeychain to search for the send using the key id. How can I change it email instead of key id?
I cant seem to find the intent which sends the extra "EXTRA_KEY_ID", as this is the string thats getting sent to Openkeychain

From reading the code OpenKeychain provides the Intent that then get's called by us to request the data. So it's like a callback.
How this works is as follows:
We request decryption:
We are returned a CryptoResultAnnotation
The CryptoResultAnnotation contains an Intent
We call that here: https://github.com/k9mail/k-9/blob/231b46f27839f599d95ef3f62cd66f4a20e0e62e/k9mail/src/main/java/com/fsck/k9/ui/messageview/MessageCryptoPresenter.java#L228
That launches OpenKeychain.
So you'd have to modify the intent that open keychain provides us.
I can only assume that this is this intent: https://github.com/open-keychain/open-keychain/blob/b328c9785382857afdcdd1010b29fcb3476a0687/OpenKeychain/src/main/java/org/sufficientlysecure/keychain/remote/ApiPendingIntentFactory.java#L103

Going through the code I did find these but need someone to explain how exactly it was working.
Thanks!

Feel free to ask specific questions via these communication channels: https://github.com/k9mail/k-9#communication


[WIP] cmake minimize module list

As a very small part of an ongoing effort to improve the extensibility and modularity of PX4 this PR updates the build system to reduce the per config module list. Components needed for a particular platform are automatically included. Libraries aren't listed at all anymore, but instead are automatically included and only built + linked if added by a PX4 module's DEPENDS.

all libraries included automatically
only the ones listed by a module's DEPENDS are built and linked

Initially started here. https://github.com/PX4/Firmware/pull/8139

In the process I stumbled upon many circular dependencies. These need to be identified and handled appropriately. The system dependencies should be clear and shouldn't depend on system wide include paths and linking everything together. Having to link with –start-group –end-group to resolve the circular dependencies is usually a bad sign.


The code properly reverses the array but doesn't allow me to proceed. (claims I'm not using the reverse method)

Challenge Waypoint: Reverse Arrays with reverse has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11) AppleWebKit/601.1.56 (KHTML, like Gecko) Version/9.0 Safari/601.1.56.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:
var array = [1,2,3,4,5,6,7];

// Only change code below this line.

array.reverse(function(a,b){
        return b - a;
});

// Only change code above this line.

(function() {return array;})();

it appears that, while my solution indeed reverses the array - the proper way to do so is simply
array.reverse();

The code  array.reverse();   does not work for this waypoint.

@asauce99  It does work.

Yeah, it does. I must have been a character off. Maybe semicolon
On Nov 9, 2015 1:54 AM, "Faizaan"<EMAIL_ADDRESS>wrote:

@asauce99 https://github.com/asauce99 It does work.
—
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/4224#issuecomment-154999396
.


ULTRA Remove start/end offsets

Minor update: Remove ego vehicle's start and end offsets from the simple level.
Note: By default levels from tasks 1 & 2 would be not be constrained by any destination/arrival positions (start/end offsets)

Cool change. I like how it homogenizes Task 1 and Task 2 levels. I thought we had added the offset so that the ego vehicle could have a better change of colliding with the social vehicles, is it okay if we remove the offset now because we aren't using the "___-interaction" distributions? Or is there another reason?

So previously we had the offsets specifically for the _-interaction distributions, and now that we have revert back with the _-density distribution in the simple level the offsets must return to its default values. So yeah, answering your question: We are removing the start/end offsets because we are no longer using the _-interactions.
The _-interaction distributions will used in creating sub-tasks for curriculum learning experiments, or even create a separate task which contain only those types of distributions. However, for now **task1 and **task2 should only contain {low,mid,high}-density or no-traffic distributions.


Gen 9

Hello, will you update this parser with Teracrystalisation ?

Thank you very much ! I'm using this great repo for the website I developed : https://www.coupcritique.fr, and I was afraid to do a fork of this, aside to other development I have to do for 9th gen.
I put it like the url like this you can see a usation of your work.

That's a very cool website! Thank you for mentioning this library :)
I am planning to rewrite it in TypeScript and bringing more compatibility with original Showdown team builder.


Write release notes for 0.28

So much new stuff!
https://github.com/simonw/datasette/compare/0.27...master

https://datasette.readthedocs.io/en/latest/changelog.html#v0-28


AWS Provider for OCI Does not account for disconnected AWS partitions

oci/auth/aws/auth.go::40
var registryPartRe = regexp.MustCompile(`([0-9+]*).dkr.ecr(?:-fips)?\.([^/.]*)\.(amazonaws\.com[.cn]*)`)

This regular expression is used to determine if flux should try to authenticate to the AWS API when pulling an OCI resource. However, this regex does not support some other AWS regions, notably disconnected AWS partitions.
Thus, flux does not detect that it is in AWS and fails due to missing username/password.
Why is this implemented as such? If the user is already forced to specify provider: aws on helmrepositories for example, why does flux still parse the URL instead of de-facto authenticating?
I recommend removing this check and assuming the OCI endpoint requires AWS authentication if the user specifies provider: aws regardless of the URL. If the user in error specifies provider: aws for a non-AWS-backed OCI repo, then flux should fail.

I understand that an alternative path to implementing this would be to expand the regex to include these disconnected regions, but it seems like there is a bigger discussion that should happen around this.

After further investigation, it looks like this happens because the regex tries to pull the region out of the URL.


Blob de-duplication breaks for identical content with different mime types

Demonstrated at https://github.com/getodk/central-backend/pull/1073

We've started filing issues that are potentially user-facing in the central repo, so I just transferred the issue. We're mostly using central-backend and central-frontend just for refactor/testing/development issues.


su -c option

I have an error related too "su invalid -c", as some emulators are not using a su binary with "-c" option, an adaptation is needed.

Solved, waiting for commit confirmation.

As per the original code, it will check for su, if the application doesn't have that then it will start running the command with normal adb command-line utility.
However, I added the su checks due to the following issues raised
"https://github.com/NotSoSecure/android_application_analyzer/issues/1"
For this particular test case, your suggested changes fail.

Error message for the reference

Ok, you are correct. However, this implementation does not work on non-production builds. Tested by me the other day.


Remove cache

This is possibly causing a build problem

Looks like this is a bug with the nightly #8351


Shapes of inputs and output in entry.py

Hello, I wanted to check with you if the shapes of my inputs and the output I get are correct (using the entry.py). For a single example whose tokenized sentence length is 30, the shape of input_ids, input_mask and segment_ids is (1,30) and the image features (features and boxes) both have (1,36,2048). As the cross-modal output, I get (1,768). Would these be correct? How can I get un-pooled outputs?
Best regards

You could take lang_output  / visn_outputs.

Thank you for the response. I have just found that I can use the 'mode' argument in the init of LXRTFeatureExtraction.


istio 1.5 prometheus target errors

Bug description
Prometheus target errors in 1.5 Prometheus installation
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[x ] User Experience
[ ] Developer Infrastructure
Expected behavior
There should be no target errors
Steps to reproduce the bug
Install demo profile and go to the Prometheus UI target.this seems harmless though it is a terrible experience.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
How was Istio installed?
istioctl demo profile installation
Environment where bug was observed (cloud vendor, OS, etc)
KOPS AWS

I think the issue is somewhere else

can confirm after further investigation it is related to istio prometheus

Yeah I think its trying to scrape prometheus itself at :15090 which isn't valid

@prageethw May I close this?

This is a duplicate of https://github.com/istio/istio/issues/21720 so I will close, I think its still an issue in 1.6 though


Web vitals onINP reporting elements that do not have any click functionality or handlers attached

In order to improve INP of my application, I integrated<EMAIL_ADDRESS>to get field data and work on actual interactions causing poor INP score. However in my data I see a lot of elements reported actually dont have click functionality/handlers attached. For instance there are many div/span/p elements reported in the report. What is the reason behind such a behaviour. This basically makes improvement exercise very ineffective and lengthy. I am collecting attribution.eventTarget for the elements on which interactions happen.
function sendToAnalytics({name, value, rating, attribution}) {
  // here I am creating req payload with element as attribution.eventTarget
}

onINP(sendToAnalytics);

Web vitals js integrated<EMAIL_ADDRESS>

There's a few reasons why seemingly non-interactive targets can be marked as the INP target, the two most common of which are:

In Chrome 125 - 128 we stopped reporting scroll start elements, which was a common reason for this—particularly on mobile. That's fully rolled out now but, as it's a fairly recent change, you may still be getting reports from those who haven't upgraded their browsers or other Chromium-based browsers which haven't incorporated this change yet. Check if this is falling over time and/or which browsers are still reporting this.

Global event handlers that run on all elements at body level are quite common, often because the framework used registers them at a high level and then acts upon the element affected. Similarly, some tools like Google Tag Manager or the like can also register global event handlers. Check to ensure your div/span/p elements don't actually have inherited event handlers

I also note you're using v3 of the library and would strongly recommend upgrading to v4 (and v5 soon!) so ensure you have the latest improvements to the library.

Barry @tunetheweb, Thanks for the detailed and insightful answer to my question. One more thing I would like to clarify, does adding a background-color on an element's active and focus state help improve INP? There are times when the click handler is just a trivial function with not much to improve but the slow hardware/network is making app slow. In such cases if we add a touch/click state to element does it help improve INP?


fix(oauth2): add missing scopes to unauthorized error message

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


conan: Add OpenGL/OpenGLES toggle through "gles" option

I'm currently waiting for a conan-package-tools pull request to allow custom docker containers so it builds & pushes with actual video support on Travis. Is it okay to wait until that patch is merged and on pip before I merge this one?

Yep, there's no hurry.


Tracker status field not writable.

Closes OSIDB-1780

@RedHatProductSecurity/osidb-devs I'm not sure about the changes in openapi.yml and its potential knock-on effects in projects that use the API definition. In this PR I tried going the usual route of marking the field as readonly in the serializer and as blankable in the model (without blank=True no POST/PUT can succeed because the field can't be blank because well it's read only and thus not provided in the request). If it's a problem, I think we can make it blank=False and just fake-fill it in TrackerSerializer.create() and TrackerSerializer.update() I guess (but that didn't seem right unless we agree it is)?


Prepare draft of UI for advanced queries

I've done it, but after discussion we decided, that everything can be done by adding some functionalities to basic search.


Show dependents

The graph today is walked backs to the dependencies, but does not show dependents directly, as this involves walking backlinks, or other references.

See original designs
There's some discussion here: https://github.com/jbenet/depviz/issues/17#issuecomment-263379305

Basically:

we want to have it
but it's tricky to do right (given some links will automatically backlink and some wont)
we may have workarounds meanwhile (see user or whole project issues)

On Mon, Nov 28, 2016 at 01:18:06PM -0800, Juan Benet wrote:

but it's tricky to do right (given some links will automatically
backlink and some wont)

This doesn't help with cross-host back-references (e.g. a GitLab issue
referencing a GitHub issue), but within GitHub you can discover these
somewhat efficiently (an extra API call or two per rendered node)
using the timeline API preview 1:
$ curl -sH 'Accept: application/vnd.github.mockingbird-preview' https://api.github.com/repos/jbenet/depviz/issues/15/timeline |

jq '[.[] | select(.event == "cross-referenced") | {"source": {"html_url": .source.issue.html_url, "body": .source.issue.body}}]'
[
{
"source": {
"html_url": "https://github.com/jbenet/depviz/issues/22",
"body": "We don't do this at the moment (there's a FIXME in the GitHub module).  Screenshot for the designed display in #9.  Related but (I think?) distinct idea in #15."
}
}
]


Issue credits to Matt.

Issue 120,192 credits to @anoanoano.

 Follow up
On Wednesday, 28-Feb-24 17:40:41 UTC by Gov4Git dev
Your directive cannot be parsed.


(Maint) Update releases and snapshots repositories

The old repositories URLS were incorrect, which caused an error message when trying to start a REPL. The REPL now starts successfully.

For future reference we conventionally have ticket ids in all caps (eg SERVER-2172) and "maint" in all lowercase.


Language problem

My meteoalarm card is in english , while my HA instance is set to dutch ?
How do i change the language of the card ?

Please file a full bug repport.


Add card Twitter account and get the VC fro Tezosprofile

we are going to use another issuer
https://api.tzprofiles.com/tz1LMChSoDrZK8fFYmewVYnYe7q6tn43zFQs
process :+1: user clic on the card in the discover. wallet asks user to select an account, wallet call api and store the VC as it has alreday been issued by anothere issuer
If the VC is not available, wallet inform the user

the credentialSubject.id will be a did:pkh example -> did:pkh:tz:tz1LMChSoDrZK8fFYmewVYnYe7q6tn43zFQs
Check the corralation with the blockchain account


app.UseRouting() should be after UseAuthentication and UseAuthorization?

.NET 3.0 documentation
If the app uses authentication/authorization features such as AuthorizePage or [Authorize],
place the call to UseAuthentication and UseAuthorization: after, UseRouting and UseCors,
but before UseEndpoints:

This doesn't appear to be correct for an API project? However I have a few other Middleware extensions being used: Swagger,  ForwardedHeaders, JsonExceptions.
The variations I've tried:
Working
app.UseAuthentication();
app.UseAuthorization();
app.UseRouting();

app.UseAuthorization();
app.UseAuthentication();
app.UseRouting();

Not working
(Putting UseRouting first)

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

ID: 76f39eec-9dd1-6167-56ec-47b26e0b5063
Version Independent ID: f9f2b0f3-01eb-cf58-8767-194fe0fc0e44
Content: Migrate from ASP.NET Core 2.2 to 3.0
Content Source: aspnetcore/migration/22-to-30.md
Product: aspnet-core
Technology: aspnetcore-migration
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Can you share a complete Configure method?

// You can add these parameters to this method: IHostingEnvironment env, ILoggerFactory loggerFactory
		public override void Configure(IApplicationBuilder app)
		{
			app.UseAuthentication();
			app.UseAuthorization();

			app.UseSwaggerWithReverseProxySupport();
			app.UseRouting();

			app.UseEndpoints(endPoints =>
			{
				endPoints.MapControllers();
			});

			app.UseJsonExceptionHandler(_hostingEnvironment);
			app.UseForwardedHeaders(new ForwardedHeadersOptions
			{
				ForwardedHeaders = ForwardedHeaders.All
			});
			app.UseJsonHealthChecks();
		}

The version that doesn't work puts UseRouting first

I see a few quirks in the setup you've got. Does the following work?
app.UseRouting();
app.UseAuthentication();
// app.UseAuthorization();
app.UseEndpoints(...);

I see a few quirks in the setup you've got. Does the following work?
app.UseRouting();
app.UseAuthentication();
// app.UseAuthorization();
app.UseEndpoints(...);

No it needs Authorization, or the Controller I am testing (which just creates a user) has this error:
Failed on thread 48. Endpoint Roadkill.Api.Controllers.UsersController.CreateEditor (Roadkill.Api) contains authorization metadata, but a middleware was not found that supports authorization.

I'm not a "Swagger guy" but just curious @yetanotherchris if you tried to set the middlewares in the following order ...
public override void Configure(IApplicationBuilder app)
{
    app.UseSwaggerWithReverseProxySupport();
    app.UseRouting();
    app.UseAuthentication();
    app.UseAuthorization();
    ...
}

How confident are you that you're providing a token and that it's valid, etc? If you do what you're doing with the authz stuff before UseRouting, it looks like you're really just disabling authz in a roundabout fashion. Have you tried calling the endpoint when it works, but without providing a token?

The code (actually a soak test, calling the controller 50 times concurrently to test ASP.NET Identity on Marten with Postgres) works prior to the .NET 3.0 upgrade. I haven't delved into the internals of the authz and authentication middleware, so I'm not sure if this is from another Middleware interfering - but from what I can tell it could only be Swagger.
I'll try removing Swagger from the project and see if the order matters then - but I think Swagger (NSwag) is a fairly common use case for a web api project.

Just for the record:
public static IApplicationBuilder UseSwaggerWithReverseProxySupport(this IApplicationBuilder app)
{
    app.UseSwagger(config => config.PostProcess = (document, request) =>
    {
        string pathBase = request.Headers["X-Forwarded-PathBase"].FirstOrDefault();
        document.BasePath = pathBase;
        document.Host = request.Headers["X-Forwarded-Host"].FirstOrDefault();
    });

    app.UseSwaggerUi3(settings =>
    {
        settings.TransformToExternalPath = (route, request) =>
        {
            string pathBase = request.Headers["X-Forwarded-PathBase"].FirstOrDefault();

            if (!string.IsNullOrEmpty(pathBase))
                return $"{pathBase}{route}";

            return route;
        };
    });

    return app;
}

I tried Startup.cs with //app.UseSwaggerWithReverseProxySupport(); and the same error persists.

With the correct middleware ordering, your JWT (or whatever) is being rejected (it's either invalid or perhaps there's a missing role). When you reorder the middleware as described, I doubt that the token is even being checked, so the request flows through to the endpoint unauthenticated.
This isn't an issue with the docs page.

Thanks for contacting us. We believe that the question you've raised have been answered. If you still feel a need to continue the discussion, feel free to reopen it and add your comments.

Thank you all for your help, it was indeed some bad being sent, and also being interpreted which a custom IAuthorizationRequirement solved (really good docs can be found here on the subject).
I realise it's not a docs-related issue, but if app.UseAuthentication();app.UseAuthorization(); had a way of knowing if EndPointRoutingMiddleware was registered, and throw that would be a nice addition - i'll possibly suggest it in a different PR or issue.

had a way of knowing if EndPointRoutingMiddleware was registered, and throw

It does, there's just a very unfortunate bug in the current 3.0 that only catches a completely missing UseAuthorization call. It's been fixed but hasn't been released yet.


Code for implementing into new RazorPages project shows "app.UseMvc" in Configure section

Should show app.UseEndpoints instead

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

ID: 804e24dd-7e30-8cf5-2c99-1ffacb4582f6
Version Independent ID: 3e25547b-e2c9-6634-2c38-2a77207f17d4
Content: Scaffold Identity in ASP.NET Core projects
Content Source: aspnetcore/security/authentication/scaffold-identity.md
Product: aspnet-core
Technology: aspnetcore-security
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Dup of #10159


Fixing repo issues from Switch azure-docs-powershell to SDP pipeline …

…(248646)
As these are invalid file links, the build pipeline has no knowledge about the correct file links and how to fix it, so it can hardly be fixed from the build pipeline's side.
Take the same example I mentioned below, the source markdown Add-AzApiManagementRegion.md contains one file link at the last line:
Update-AzApiManagementDeployment
However, Update-AzApiManagementDeployment.md doesn't exist in the same folder, so it will lead to 404 page.
Personally, I would suggest to fix this kind of content issue before we switch to the new SDP build pipeline, otherwise you'll always see lots of build warnings after every OPS build. However, the final decision is up to your team.
....
request to raise the priority for this ask. This is the predecessor of docfx v3 migration and we are targeting to switch the pipeline before the end of Aug. If we can not make this done, this will block docfx v3 migration, which will improve the build performance huge, which target to make that happen before the end of Nov.

Docs Build status updates of commit 3d01162:
:clock10: Full build: the average full build time is 29 min(s) 16 sec(s), this is based on the last 480 build(s) for this repository.

Docs Build status updates of commit 3d01162:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

azps-0.10.0/Az.Compute/New-AzVMSqlServerAutoBackupConfig.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Compute/New-AzVMSqlServerAutoPatchingConfig.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Compute/Set-AzVMSqlServerExtension.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.KeyVault/Get-AzKeyVaultCertificate.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.KeyVault/Undo-AzKeyVaultSecretRemoval.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/Get-AzActivityLogAlert.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/Get-AzAlertHistory.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/Get-AzAlertRule.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/New-AzAlertRuleEmail.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Monitor/New-AzAlertRuleWebhook.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Network/Add-AzRouteFilterRuleConfig.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Export-AzResourceGroup.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADApplication.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADServicePrincipal.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Get-AzResource.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Move-AzResource.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/New-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/New-AzResource.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADApplication.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADServicePrincipal.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzADUser.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Remove-AzResource.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-0.10.0/Az.Resources/Set-AzResource.md
:white_check_mark:Succeeded
View (azps-0.10.0)

azps-1.8.0/Az.ApiManagement/Add-AzApiManagementRegion.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/Get-AzApiManagementApiRelease.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/New-AzApiManagementApiRelease.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/New-AzApiManagementBackend.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/New-AzApiManagementBackendCredential.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/New-AzApiManagementBackendProxy.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/New-AzApiManagementBackendServiceFabric.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/New-AzApiManagementVirtualNetwork.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/Remove-AzApiManagementApiRelease.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/Remove-AzApiManagementBackend.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/Set-AzApiManagementBackend.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.ApiManagement/Update-AzApiManagementRegion.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Disable-AzBatchComputeNodeScheduling.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Disable-AzBatchJob.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Disable-AzBatchJobSchedule.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Enable-AzBatchJobSchedule.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Enable-AzBatchTask.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchCertificate.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchJob.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchJobSchedule.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchJobStatistic.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchNodeAgentSku.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchNodeFile.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchNodeFileContent.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchPool.md
:white_check_mark:Succeeded
View (azps-1.8.0)

azps-1.8.0/Az.Batch/Get-AzBatchPoolStatistic.md
:white_check_mark:Succeeded
View (azps-1.8.0)

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Revert test framework back to xunit

I've reverted the tests back to xunit and merged with the latest changes.
After some discussions and investigations into xunit vs nunit Dan and me have decided to revert the test framework back to what it was.
It turns out my issue with visual studio was a known one already.
See: https://github.com/dotnet/project-system/issues/826
I have updated to the pre-release versions of the xunit and test sdk nugets and that solved all my problems.
I have made one additional change and that is removing the program.cs from the integration test project as well. I had previously removed it from the unit test project and that worked fine. When trying to debug the integration tests I noticed that the main method on the program.cs does not get called at all so I removed program.cs entirely.

@detroitpro