MPCS: Rename CommitmentWithData to CommitmentWithWitness & remove unnecessary trait requirement.

The name "CommitmentWithData" is vague, renamed to CommitmentWithWitness to be clearer
It doesn't actually need to be serialized anywhere in the protocol, and never need to create a default instance, remove the unnecessary trait bounds (which doesn't cause any compilation error at all), and to avoid implementing these trait unnecessarily in WHIR wrapper

Thanks for providing a detailed motivation in the PR description.


Add mock function into Timeout Task's process dictionary

Hello! This is a proposal to fix #157.
I followed @stefanchrobot first suggestion and copied the mock inside Task process dictionary.
On the unit tests, I had to define another client since I couldn't figure out a way to reuse the existing one's for this test. Would appreciate any feedback on how to improve it :)

Thanks for the PR!
The reason I did not implement this solution is that it is polluting production code with test-specific code. Please see https://github.com/teamon/tesla/issues/240 (point C) for the proposal on how to fix this issue.

It makes totally sense. I'll take a closer look on #240. Closing for now. Thanks :)


Make sure dropped item updates inventory hilite and selection correctly

It doesn't seem to be a biggie as the selection index is automatically reset whenever dropping an item.


Racket 8.6 broken on aarch64-darwin

Steps To Reproduce
Steps to reproduce the behavior:

nix-env -iA nixpkgs.racket-minimal

Build log
compiler/cm:   start-compile: /private/tmp/nix-build-racket-minimal-8.6.drv-0/racket-8.6/src/mac/codesign.rkt
compiler/cm:   finish-compile: /private/tmp/nix-build-racket-minimal-8.6.drv-0/racket-8.6/src/mac/codesign.rkt
cs/c/racketcs -O info'@'compiler/cm -l- setup --boot ../setup-go.rkt cs/c/compiled ignored cs/c/ignored.d ../cs/known.rkt ../cs/
failed
 in build-one
 in loop
 in module->hash
make: *** [Makefile:13: all] Error 1
error: builder for '/nix/store/ilywy5nllnmjq0lz9xlbd1v7rzrg7axj-racket-minimal-8.6.drv' failed with exit code 2;
       last 10 log lines:
       > compiler/cm:   finish-compile: /private/tmp/nix-build-racket-minimal-8.6.drv-0/racket-8.6/src/cs/c/embed-boot.rkt
       > cs/c/raw_racketcs -O info'@'compiler/cm -l- setup --boot ../setup-go.rkt cs/c/compiled ignored cs/c/ignored.d ../mac/codesign.rkt -s - --entitlements ../mac/entitlements.plist cs/c/racketcs
       > compiler/cm:   start-compile: /private/tmp/nix-build-racket-minimal-8.6.drv-0/racket-8.6/src/mac/codesign.rkt
       > compiler/cm:   finish-compile: /private/tmp/nix-build-racket-minimal-8.6.drv-0/racket-8.6/src/mac/codesign.rkt
       > cs/c/racketcs -O info'@'compiler/cm -l- setup --boot ../setup-go.rkt cs/c/compiled ignored cs/c/ignored.d ../cs/known.rkt ../cs/
       > failed
       >  in build-one
       >  in loop
       >  in module->hash
       > make: *** [Makefile:13: all] Error 1
       For full logs, run 'nix log /nix/store/ilywy5nllnmjq0lz9xlbd1v7rzrg7axj-racket-minimal-8.6.drv'.

Notify maintainers
@henrytill @vrthra
Metadata
~ $ nix-shell -p nix-info --run "nix-info -m"
these 2 paths will be fetched (0.01 MiB download, 0.14 MiB unpacked):
  /nix/store/0gfg84zy171sgpwfbgwji3ybbjh38rh4-nix-info
  /nix/store/yarklbql3fs5b3r38h3w25nax2s8rnd3-DarwinTools-1
copying path '/nix/store/yarklbql3fs5b3r38h3w25nax2s8rnd3-DarwinTools-1' from 'https://cache.nixos.org'...
copying path '/nix/store/0gfg84zy171sgpwfbgwji3ybbjh38rh4-nix-info' from 'https://cache.nixos.org'...
 - system: `"aarch64-darwin"`
 - host os: `Darwin 21.6.0, macOS 12.6`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.8.0`
 - channels(hmih): `""`
 - channels(root): `"nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

Could you elaborate more? I have noticed this posted issue and decided to check, considering I need racket in the near future, and I am on M1 Mac mini.
I was unable to replicate by installing with specified command nix-env -iA nixpkgs.racket-minimal
Outcome is valid /nix/store/nnsgpvag85c5kjhg6ns4ll3nv0vc6kd6-racket-minimal-8.6
My system has numerous differences though:
nix-shell -p nix-info --run "nix-info -m"
these 2 paths will be fetched (0.01 MiB download, 0.14 MiB unpacked):
  /nix/store/vwrmfx47spb7p3241pvgmbzbacvq2fic-DarwinTools-1
  /nix/store/vzmbw94qf0rhimbr5gfrk0cnd10w59fq-nix-info
copying path '/nix/store/vwrmfx47spb7p3241pvgmbzbacvq2fic-DarwinTools-1' from 'https://cache.nixos.org'...
copying path '/nix/store/vzmbw94qf0rhimbr5gfrk0cnd10w59fq-nix-info' from 'https://cache.nixos.org'...
 - system: `"aarch64-darwin"`
 - host os: `Darwin 21.6.0, macOS 12.5`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.11.0`
 - channels(root): `"[REDACTED], nixpkgs"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`

My nix version is higher. Consider updating your channel and nix version. Maybe it is the culprit?
Additionally, I am on previous macOS release. Is this an upstream regression in racket itself related to os update?
In my case software looks like to be working:
racket --version
Welcome to Racket v8.6 [cs].

Additionally, I am on previous macOS release. Is this an upstream regression in racket itself related to os update?

Possibly. I am on version 12.6 and the homebrew package works well. Also, as you see in the log, the failure happens right after compiler/cm:   finish-compile: /private/tmp/nix-build-racket-minimal-8.6.drv-0/racket-8.6/src/mac/codesign.rkt, and in the repo there is a codesign patch. Maybe it's out of date.

FWIW, I'm getting the same error on nix=2.11.0.
 - system: `"aarch64-darwin"`
 - host os: `Darwin 21.6.0, macOS 12.6`
 - multi-user?: `yes`
 - sandbox: `no`
 - version: `nix-env (Nix) 2.11.0`
 - channels(root): `"nixpkgs"`
 - channels ... : `"darwin"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixpkgs`


Add delay between nginx reloads

Added logic in the subscribe function to reload nginx only if >1 second has passed since last nginx reload. Fixes #26. @mhamann @lostinthestory @DavidMGreen PTAL

@alexsong93 It seems that if the first time through, I fail the 1 second check, but then another API update doesn't come in for a long period of time, nginx would not reload to know about the first API for that long period of time. I would think we would almost need to implement it like you implemented the health check. On first request, set a flag that we need to reload and set a timer to reload in one second. On subsequent requests, see if we're already waiting to reload. If so, just update the file mgmt portion. Then just before we reload, set the flag back to false so the next API will trigger another reload in one second.

@lostinthestory I believe that's exactly what the code is doing - the redisUpdated flag is set to true inside the else block when redis is updated, and it is set back to false after the if/else block, if redisUpdated == true and timeDiff >= 1. The 1 second check is done regardless of whether or not redis has been updated.
I think the problem here is that I changed the timeout for redisSubClient to 10 seconds, from 1 second. This means that redisSubClient:read_reply() will block for 10 seconds if it doesn't see any updates. I changed the timeout back to 1 second - it should work as expected now.

Ah, I seem to have blocked the redisUpdated out of my vision altogether when I was looking this over.


Add a Github actions CI flow

I think it's really useful to have CI, github actions is zero dollars and pretty reliable.

Thank you. I will set up GHA now, but I am doing it slightly different to be more in line with what I am used to from other crates I maintain.


Disable python downloads when running notebooks on a SAW. (#11186)

Porting change to release branch.

Coverage increased (+0.0008%) to 36.03% when pulling 41af05e731d6abfcf9b888e6d74a2fc8e0598001 on corivera/portSawChange into 6ecaf97000e6af09fd8e110c00c332e60d3facba on release/1.20.


The speed when evaluating the result using the 'bbox'/'coco' format

I make the dataset with coco format and use 'bbox' format to evaluate the result.
But I find the speed of evaluation is very slow, nearly 3 hours.
I want to know where is the problem and how to boost it?
Following is the results:
Evaluating bbox...
Loading and preparing results...
DONE (t=12.14s)
creating index...
index created!
Running per image evaluation...
Evaluate annotation type *bbox*
DONE (t=8601.13s).
Accumulating evaluation results...
DONE (t=187.50s).

+-----------------------------------------------------------------------------+
| NVIDIA-SMI 450.80.02    Driver Version: 450.80.02    CUDA Version: 11.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce RTX 208...  Off  | 00000000:3B:00.0 Off |                  N/A |
| 51%   78C    P2   240W / 250W |   1161MiB / 11019MiB |     84%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  GeForce RTX 208...  Off  | 00000000:AF:00.0 Off |                  N/A |
| 49%   76C    P2   212W / 250W |   1229MiB / 11019MiB |     85%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

How large is your val dataset? The coco api uses CPU to calculate the mAP so it may be very slow when there are a lot of images and objects.


Child Supervision disable meaning

In openthread stack, by default child supervision is disabled.
So how or when does mtd re-attach process is enabled in case child supervison is disabled.

Closing stale issue.


Confirm Cargo Version matches Tag Version in release CI/CD workflow

Resolves #3
Done:

Find the cargo version from the Cargo.toml file.
Add a v to the version within the workflow.
Cancel the workflow if the two do not match up.

Todo:

Figure out why github.ref is not returning the current tag.
Complete the semi-automation of releases in the CI workflow.

If I can figure out why I cannot get the tag using github.ref, everything else should be pretty much done from there.
Thanks!

P.S. I'll squash the commits if that's easier for you - was annoying to test the workflows out without commiting! :joy:

Thanks for the work on this! I'll test this out later and then merge it in.

Just to clarify - this is still a draft pr. I've been struggling to get the tag name from the CI. I tried with github.ref and it did not work as intended.

If it helps, this is how I do it in my other project: https://github.com/Sleitnick/Knit/blob/main/.github/workflows/release.yaml#L48

So maybe it could look something like this?
      - name: Get the tag of current release
        id: get_version
        run: echo ::set-output name=VERSION::${GITHUB_REF#refs/tags/v}

      - name: Verify package version is equal to tag version
        if: ${{ steps.cargo_version.outputs.value != steps.get_version.outputs.VERSION }}
        run: |
          echo "${{ steps.cargo_version.outputs.value }}"
          echo "${{ steps.get_version.outputs.VERSION }}"
          exit 1

If you wanna make those changes, I'll pull this in!

Hey sorry about that @Sleitnick will get to it ASAP!

No problem; no rush

Hm @Sleitnick... I still could not get it implemented with the changes you requests, you should be able to add a commit re if you want to take a stab at seeing what's wrong here.


Add some fun and entertainment sites/games

Could you also add this one? https://regexcrossword.com/

Added


Johtaylo/issue1410

fixes #1410
This adds the UserAgent for the scenario where the client (specifically the BotFrameworkAdapter) has passed in a custom HttpClient.
Care needs to be take because the headers collection is not thread safe. The Adapter will be a singleton which is why this code is called from the constructor.
Ideally in the (dot net core) future we will be able to use IHttpClientFactory consistently.

Pull Request Test Coverage Report for Build 53651

0 of 0   changed or added relevant lines in 0 files are covered.
145 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.004%) to 76.13%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Microsoft.Bot.Builder/BotFrameworkAdapter.cs
145
22.68%

Totals

Change from base Build 53546:
0.004%

Covered Lines:
4363

Relevant Lines:
5731

💛  - Coveralls

No issues found in Microsoft.Bot.Builder.dll
No issues found in Microsoft.Bot.Builder.AI.Luis.dll
No issues found in Microsoft.Bot.Builder.AI.QnA.dll
No issues found in Microsoft.Bot.Builder.ApplicationInsights.dll
No issues found in Microsoft.Bot.Builder.Azure.dll
No issues found in Microsoft.Bot.Builder.Dialogs.dll
No issues found in Microsoft.Bot.Builder.TemplateManager.dll
No issues found in Microsoft.Bot.Configuration.dll
No issues found in Microsoft.Bot.Connector.dll
No issues found in Microsoft.Bot.Schema.dll


system slow

when i was search something that ai take to much time as compare to other ai platform. so if can approve then i will ok.

Sorry for late response, now it should be resolved.


Dependence update ??

Want to ask if the dependencies we use (netserilizer/mono ...etc) need updates so we should do that to benefit from improvements or any possible bug fixes !

If no one else will, then I'll do that, after fixing tor

https://github.com/quasar/Quasar/releases/tag/v1.4.0


missing dependencies spyder_kernels on startup,but i have this model.

What steps will reproduce the problem?

Error
You have missing dependencies!# Mandatory:spyder_kernels >=2.0.1,<2.1.0 :  2.0.1 (NOK)Please install them to avoid this message.Note: Spyder could work without some of these dependencies, however to have a smooth experience when using Spyder we strongly recommend you to install all the listed missing dependencies.Failing to install these dependencies might result in bugs. Please be sure that any found bugs are not the direct result of missing dependencies, prior to reporting a new issue.
OK

Hey @cailongli, thanks for reporting. This is a duplicate of issue #15091 and it'll be fixed in our next version.


Documents in rest of world?

When will the functions related to document collaboration open up for the rest of the world?

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

ID: 3aa25441-0531-504f-580e-3ad586081bbe
Version Independent ID: c6c702b5-5e68-b2e6-ee32-ead9eac98ec5
Content: Collaborate with Teams
Content Source: ce/basics/teams-collaboration.md
Service: crm-online
GitHub Login: @mduelae
Microsoft Alias: mkaur

@thomassandsor General availability is planned for End of April 2019.
Thanks,
Mints


TD-2691 Create React UI Part Selector Component

Closes TD-2691
Changes

This PR introduces a new component, PartSelector to the library. The PartSelector is a user interface component that allows users to select a part from a list of parts. It is designed to be flexible and reusable in different parts of the application.
Features:

Part Name Selection: The component provides an autocomplete dropdown that lists all the unique part names. Users can select a part name from this dropdown.

Part Number Selection: Based on the selected part name, the component provides a second autocomplete dropdown that lists all the part numbers associated with the selected part name. This dropdown is disabled until a part name is selected.

Flexible Layout: The component can be displayed in a row or column layout, controlled by the flexDirection prop. It also controls the wrapping of items with the flexWrap prop.

Controlled Component: The PartSelector is a controlled component. It accepts a value prop that represents the currently selected part (both name and number), and an onChange callback that is called whenever the selection changes.

Utility Function Integration: The component uses a utility function uniqueSortedArray to sort and get unique part names.

The initial use case for this component will be in VIRTO.DATA > Search > SELECT PART (tab)
Other changes:

Autocomplete.tsx

New prop added for no options text, made us of noOptionsText prop of MuiAutocomplete

utils/common.ts

Added uniqueSortedArray function (moved from VehicleSelector.tsx)

VehicleSelector

New story added for custom size variant in VehicleSelector.stories.tsx
Use of the uniqueSortedArray from the utils/common function, removed uniqueSortedArray function from VehicleSelector.tsx
New size prop added in VehicleSelector.types.ts and implemented use of size in VehicleSelector.tsx

UI/UX

Initial light mode

Initial dark mode

Part Name selected

Filled
size: small
flexDirection: row

Testing notes

Part Name Selection:

Start by testing the part name selection. Click on the "Part Name" dropdown.
Select a part name from the list. The selected part name should be displayed in the "Part Name" field.

Part Number Selection:

Once a part name is selected, the "Part Number" dropdown should become enabled.
Click on it and you should see a list of part numbers associated with the selected part name.
Select a part number from the list.
The selected part number should be displayed in the "Part Number" field.

Layout:

The component should be displayed in a column layout by default. If the flexDirection prop is set to "row", the component should be displayed in a row layout.
The flexWrap prop controls whether the items should wrap onto multiple lines.

Clearing Selection:

Clear the selection in the "Part Name" field.
The "Part Number" field should become disabled and its selection should be cleared as well.

Size:

The size of the component can be controlled by the size prop.
Try changing the size prop to "small" or "medium" and observe the changes in the component's size.

Unique Part Names:

The "Part Name" dropdown should only display unique part names.
If there are duplicate part names in the parts prop, they should only appear once in the dropdown.

Sorting:

The part names in the "Part Name" dropdown should be sorted in ascending order.

PLEASE NOTE:

After approval the component will be tested in VIRTO via pre-release.

Failed end-to-end are a known issue.

Author checklist before assigning a reviewer

[x] Reviewed my own code-diff.
- [ ] Branch has been run in docker.
[x] PR assigned to me or an appropriate delegate.
[x] Relevant labels added to the PR.
[x] Appropriate tests have been added.
[x] Lint and test workflows pass.

I have left some comments within the code outlining issues I have found while testing. Here I will outline a couple more.
nowrap seems to do nothing:

The flexWrap does take affect, if you have more fields:

I have left some comments within the code outlining issues I have found while testing. Here I will outline a couple more.
nowrap seems to do nothing:

The flexWrap does take affect, if you have more fields:

Apologies, I misunderstood the function of the flexWrap prop.


router: auto_host_rewrite_header support

Description: Make it possible to substitute upstream's request host/:authority header with value of any (downstream or custom) header. This allows for efficient implementation of more involving deployments with specially configured downstream load balancers.
Risk Level: Low, does not change default behaviour
Testing: Unit tests added
Docs Changes: Description in proto file
Release Notes: Updated
Fixes #6486

@zuercher, thanks for the review!


Added new Vehicle hashes and Weapon components from 757 update

Btw. There is no good reason in having VehicleHash, PedHash and WeaponHash in the Native namespace when most other enums aren't. We should move them out of there.

@crosire I just moved the hash enums into the GTA Namespace, makes more sense in there

@Fireboyd78 @zorg93
Also Xls and Xls2 should be XLS and XLS2. Aaaaaannnnnddddd, the car's name is BestiaGTS not BestiaGT.

I realised about BestiaGT a couple of hours ago when I searched through the decompiled scripts for its hash and couldnt find it.(for some reason a few seconds after spawning the cars on 757 they get deleted) That issue should go soon though(hopefully) if not we found a work around

Fixed in #501


[HW] Hari G

Name: Hari G
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/hari-g-12582812b/
Attach the homework screenshots below for both step II and step III:

Looks great Hari, here's your badge -> https://api.badgr.io/public/assertions/eABpUz05RYSyu-O5CqtBCg?identity__email=itsmeharig%40gmail.com

Hey Hari G, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/5HbMI5gWQ2iNStBE73qGKw


Add REDO_THREAD_PENDING_WORK to ignorable wait types in reports

https://github.com/microsoft/SqlNexus/blob/7a86cbf3a1ea46de7c834a51d2fb74a63ac5d12e/sqlnexus/PerfStatsAnalysis.sql#L577

This wait type would be high if no log records coming on the primary.
Confirmed in https://www.sqlskills.com/help/waits/redo_thread_pending_work/ can be ignored

Before the fix

After the fix (same data set)


Make it clear that "Python (python, py, etc)" in Code Playground has a "catch multiple" semantic

The typeahead suggestion for Code Playground's language field will suggest entries like "Python (python, py, etc)". These suggested entries are special. They will be applicable to "python", "py" and everything mentioned in the bracket. Another example is the "Rust (rust, rs)" one and many others.
Once user selects the typeahead suggestion, the string before the brackets are used to populate the text field. E.g. "Python"
Users are still able to edit what's in the text field to anything.
This points to 3 problems:

It appears that "Python" with a capital P means something special to the system. It appears to be a hack in that specific strings mean certain things.
Users still being able to edit what's in the text field makes it unclear that it's special.
After selecting the suggestion and the text becomes "Python" without the information in the brackets also makes it unclear that it's special.

AFAIK there's no special logic around "Python" with a capital P -- my guess is what you're seeing is just an emergent behavior. We canonicalize aliases with the following server-side logic in zerver/lib/markdown/fenced_code.py:
# To support our "view in playground" feature, the frontend
# needs to know what Pygments language was used for
# highlighting this code block.  We record this in a data
# attribute attached to the outer `pre` element.
# Unfortunately, the pygments API doesn't offer a way to add
# this, so we need to do it in a post-processing step.
if lang:
    div_tag = lxml.html.fromstring(code)

    # For the value of our data element, we get the lexer
    # subclass name instead of directly using the language,
    # since that canonicalizes aliases (Eg: `js` and
    # `javascript` will be mapped to `JavaScript`).
    try:
        code_language = find_lexer_class_by_name(lang).name
    except ClassNotFound:
        # If there isn't a Pygments lexer by this name, we
        # still tag it with the user's data-code-language
        # value, since this allows hooking up a "playground"
        # for custom "languages" that aren't known to Pygments.
        code_language = lang

    div_tag.attrib["data-code-language"] = code_language
    code = lxml.html.tostring(div_tag, encoding="unicode")
return code

And I think the bug is that we're not doing similar canonicalization in the Code Playground administrative settings UI.


[REEF-945] Create alias for evaluator configuration

*added NamedparameterAlias
*Updated evaluator.config file for tests
*Added test cases to deserialize evaluator config
*Fixed an issue in ClassHierarchy merge that is touched in the test scenario
*Added overload method for Bind to accept language for alias
*Added overload methods in AvroSerializer to accept ClassHierarchy
JIRA: REEF-945
This closes #

Review comments have addressed and pushed in.

+1

@jwang98052 I've done a pass.

Have addressed review comments and pushed in.

I will test and merge


Support Resource bundle package

closes #11
Support resource bundle.

If a package contains resources, Collect all resources. it uses implementation inside SwiftPM.
Generate {package_name}-Resources target in xcodeproj. it is a resource bundle target.
Add the resource bundle target as a dependency to the framework target
Inject resource-accessor.swift into the framework target. It allows frameworks to use Bundle.module.
Build the framework, then the resource bundle is embedded into the framework.

@mtj0928 @freddi-kit I fixed it. Could you review it again? https://github.com/giginet/Scipio/pull/22/commits/a747ec90f23ee875fad42c64650b3a53e80d2dc9

In further investigation, SKIP_INSTALL can be NO for all targets.
https://github.com/giginet/Scipio/pull/22/commits/399d66060dbd7b08f41a3207b202de5ce6a7b82a
So I specified SKIP_INSTALL=NO always clearly.


python310Packages.pglast: 4.1 -> 5.0

Description of changes
https://github.com/lelit/pglast/releases/tag/v5.0

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 217432 run on x86_64-linux 1

2 packages built:

python310Packages.pglast
python311Packages.pglast


KeyVault swagger file needs to be updated with secret backup permissions.

Azure/azure-cli#2587
Some keyvault SDKs choke on the new secret backup and restore permission as it does not appear in the swagger file.

This permission is already in the swagger def https://github.com/Azure/azure-rest-api-specs/blob/master/arm-keyvault/2015-06-01/swagger/keyvault.json#L310.  The linked issue appears to be due to an out of date version of the azure-cli.


Remove numbers from artifact and package names related to SemanticDB

When we introduced a dedicated artifact for the schema bindings, we weren't sure whether we would want to version Scalameta and schema in lockstep. Therefore, we called the artifact semanticdb3 and the package scala.meta.internal.semanticdb3.
However, over time it's become clear that it's pretty inconvenient to version Scalameta and semanticdb3 differently. Currently, versions are computed automatically from git history, which means that to do something different for semanticdb3, we had to assign versions by hand. That quickly got old, so we reverted to lockstep versioning.
Now when we're about to release Scalameta 4, it's a good time to codify the de-facto convention. I suggest that we call the artifact semanticdb and the package scala.meta.internal.semanticdb.

I'm in favor of this change. We should still keep TextDocument.schema in order to provide a way to programmatically assert against the version of SemanticDB payloads.

Totally. Perhaps, we could change Schema from an enum to a proper data structure that carries the version of the generator, e.g.
message Version {
  string major = 1;
  string minor = 2;
  string patch = 3;
  string sha = 4;
  string timestamp = 5;
}


Rivets formatter when each argument is another formatter

I want to check if table.value is equal to 'Stack' or 'Overflow'.
I would like to do something like this:
rv-if="table.value | eq 'Stack' | or (table.value | eq 'Overflow')"

rivets.formatters.eq = function (value, args)  {
         return value === args;
};

rivets.formatters.or = function (value, args)  {
         return value || args;
};

I would like to use those 2 formatters to achieve this.
I know I can have a specific formatter like this to achieve my functionality.
rivets.formatters.checkIfValueEqualsEitherArg = function (value, arg1, arg2)  {
             return (value === arg1) || (value===arg2);
};

rv-if="table.value | checkIfValueEqualsEitherArg 'Stack' 'Overflow'"

But, I would rather use the above two generic formatters (eq and or).
What is the best way to achieve this

I have encountered same thing once. I have solved this by providing such anyOf formatter:
rivets.formatters.anyOf = (value, arrayAsStr) => {
	return NS.Array.indexOf(arrayAsStr.split(','), value, true) >= 0
}

Usage:
<div class="item-settings-row" rv-if="item.type | anyOf 'Shirt,Jacket,Hoodie'">
</div>

To me this one feels generic enough, it's readable and understandable.

Thanks for the response. It does look better than my solution. But, I would still like a generic way to have a formatter where it has multiple parameters that can be formatters.

RPN
What you want is probably a support for expressions - a hierarchical structure of nesting binary expressions. Formatters are linear, though. So there is no support for nesting. I tried to think of anything like this and it would be possible using https://en.wikipedia.org/wiki/Reverse_Polish_notation underneath. However, the syntax would be a little weird.
Formatter would need to pass some "builder" object instead of just a value. Next formatter would take it, check if it's just a value or instanceof the builder and continue adding to it. However, I'm not sure how to get information which formatter is the latest one. Maybe overriding toString() in prototype would help: https://stackoverflow.com/questions/6307514/is-it-possible-to-override-javascripts-tostring-function-to-provide-meaningfu
Full expressions
Other way is total overkill in terms of size (10 KB). You could take this parser for expressions (there are no statements, just expressions!) https://github.com/Namek/js_expr and implement it as formatter. Then, you could pass expression as text as a first argument and all values to expression as next arguments. Or, play a little more with getting values by names from rivets context but I'm not too experienced in that.
?
I don't see any other option than extending rivets itself. If you achieve anything interesting then please share with us :)

I agree that this is out of scope. You could very easily implement the expression parser as a formatter, as @Namek says. Implementing it in rivets core would increase the size of the package considerably. There could be some mileage with the use of parentheses, but I think it opens a can of worms – in your example, you used or (table.value | eq 'Overflow'), but what if you used or (a-totally-different-variable | eq 'Overflow')? The linear nature of formatters allows rivets to remain simple.
Also, there is no one currently able to spend a lot of time on rivets, so new functionality is not going to come from maintainers. I (I can only speak for myself really) am very happy to look at PRs if I have time, but my personal circumstances mean I don't get a lot of time to look at rivets, and no other maintainers with push access seem to have that time either.


Vulnerability roundup 77: slim-1.3.6: 1 advisory

search, files

[x] CVE-2015-2171 (nixos-19.09)

Scanned versions: nixos-19.09: 5f506b95f9f. May contain false positives.

I believe this is a false positive.
Slim (the login manager) is at version 1.3.6 (the newest release). The linked CVE is referring to "slim framework" (a PHP application).
Can someone double-check? :)

Indeed a false positive.


remove docs link to nowhere

With ea000f57b6f249974293003e97b84741323fadf5 docs folder was removed, therefore the pre-commit hook should go to.

Thank you 👍


fix(keep-alive): if a component has no name just return vnode

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

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

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

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[ ] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[ ] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

The match is first checked on the component’s own name option, then its local registration name (the key in the parent’s components option) if the name option is not available. Anonymous components cannot be matched against.

according to this , if a component has no name (get name by getComponentName(componentOptions)) , it should return vnode . otherwise it will be cached by <keep-alive>

The #6942 fixed this already(also in a better way).

Duplicate of #6492


Unable to set directory

I am unable to type or paste my BeatSaber file directory into the settings box. Opening the "Browse for directory" menu leads to endless loading.
https://github.com/kuba2k2/spicetify-beat-saber/assets/138703198/134ed9e3-eb85-41f1-852e-1906ea899113
Not sure why it didn't show up in the video, but the backend is also connected on version v2.0.1, should it matter

2.0.1 is the correct version for backend. Typing or pasting the path is not supported, you need to use the browser button.
Please enable devtools in spicetify (spicetify enable-devtools IIRC), press Ctrl+Shift+I, navigate to the Console tab and open the directory picker again. Post screenshots of errors, if any occur.

Seems path null left error

But path like e: or c: lists folders and files it the location

Thanks, this should be fixed in extension v2.1.1 and backend v2.0.2.

good to know

Works good now:

Thanks for your time

I installed extension v2.1.1 and backend v2.0.2, but the problem persists for me.
Just after starting spotify:

More errors appeared shortly after:

When trying to set beat saber directory:

do you have backend connected?

These errors are caused by the Marketplace extension, not by the Beat Saber extension. In fact, the only error from this extension is:

which can indicate either outdated backend, or backend not running at all. Did you reboot your PC after installation?

Thank you for being fast and helpful :)
Rebooting worked its magic yet again


feat: Update web template routes and intro animation

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

v1.5.0
GitHub release

Your semantic-release bot :package::rocket:


Getting all cookies?

I am trying to get all of the saved cookies from the webdriver session.
I tried using a run script with a command document.cookie, but i can`t get all of the cookies.
I want to capture the password hash that is stored in a cookie[password_hashSSL], and while selenium itself haves the get/add/delete cookies function it will be realy usable inside node-red too.

Hi @vukmirovic98 ,
Have you tried to run the following script return document.cookie it should work. I agree with you about cookie management, it'll come in a future release (after 0.2.x).
Simon,

Yes i managed to get cookies but haven`t realized that some of them were HTTP only :(


Nees check on refreshFromWindowLevel

If hypeDocument.refresh isn't initialized yet, postpone or handle in …
    function refreshFromWindowLevel(hypeDocument) { …

fixed in upcoming 1.4.0 simple check


Debug module security issue

Hi,
is there any particular reason to stay wtth debug 2.2.0? There a security issue with that version, fixed in 2.6.9

The only reason is missing time :) . Thanks for the hint, I will upgrade that when updating to your feature.


Featcreate table stmt offer default distribution attribute :random distribution and auto bucket

Create table stmt do not need to specify distribution, the default distribution is random distribution and auto bucket.

run buildall


[Add] React Spring - Animation

Site URL
https://www.react-spring.dev/
Description of the above provided site
React Spring is a library for building interactive, data-driven, and animated UI components. It can animate HTML, SVG, Native Elements, Three.js, and more.
Category
Frontend
Sub Category
animations
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)

@haldaranup
I have assigned you the issue. Please proceed with it, and don't hesitate to tag me @Anmol-Baranwal or @CBID2 if you require any assistance.

Very weird landing page. The resource seems helpful.


Add conntrack metrics

What does this PR do?
Add conntrack metrics to the network check that can be found in pyroute2 and {proc_location}/sys/net/netfilter/.
Motivation
Customer and internal request.
Additional Notes
pyroute2 is used for the available metrics. More metrics should be available from here later.
pyroute2.conntrack.Conntrack.conntrack_max_size has some issues for now.
Every file in {proc_location}/sys/net/netfilter/ is read unless count which is available with pyroute2.
Some documentation still need to be done for the different metrics available.
The documentation in the metadata.csv mainly comes from here
cc @lbernail
Review checklist (to be filled by reviewers)

[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] Feature or bugfix must have tests
[ ] Git history must be clean
[ ] If PR adds a configuration option, it must be added to the configuration file.

Went through the PR quickly, looks good. Looking forward to testing it on our cluster
I'm skeptical about the parameters we retrieve as metrics:

booleans
timeouts

Maybe we can reach out to the customer and get more info on their use cases? I'm pretty sure they are mostly interested in stats and just ls in the proc conntrack directory without checking

Thanks @lbernail !
Since pyroute2 needs sudo to get the conntrack information, we get these information with calling the subprocess.  This subprocess is not available by default everywhere, so there is an option to enable it.
For the list of metrics in /${proc}/sys/net/netfilter/, there is now a whitelist/blacklist configuration.


[Segment ingestion job] Multi-threaded segment copy from staging dir to final destination

SparkIngestionJob uses single threaded copy for segments copy from staging dir to final deep store dir(e.g. S3):
https://github.com/apache/pinot/blob/7ce8b756dff2b153151517afd552759e44d46c75/pinot-plugins/pinot-batch-ingestion/pinot-batch-ingestion-spark/src/main/java/org/apache/pinot/plugin/ingestion/batch/spark/SparkSegmentGenerationJobRunner.java#L345
For a few hundred segments being uploaded, it can take forever. In this case, we should consider generating a list of source and destination paths for segment copy then use RDD to parallel this job.

Same is true for Hadoop segment generation job. It would be great to have a generalized threaded copy that can be used by Hadoop and Spark (and maybe Flink in the future)

@xiangfu0
This already happens: https://github.com/apache/pinot/blob/7e9ca6a5a4afe0d4e283ac1307c45430e474cbf2/pinot-plugins/pinot-batch-ingestion/pinot-batch-ingestion-spark/src/main/java/org/apache/pinot/plugin/ingestion/batch/spark/SparkSegmentTarPushJobRunner.java#L112
However, parallel push logic is missing in Hadoop Segment Generation.

Also, the below logic of setting parallelism to number of segments to push does not seem wise. It should be removed or changed to a smaller number.
if (pushParallelism < 1) {
      pushParallelism = segmentsToPush.size();
    }

https://github.com/apache/pinot/blob/7e9ca6a5a4afe0d4e283ac1307c45430e474cbf2/pinot-plugins/pinot-batch-ingestion/pinot-batch-ingestion-spark/src/main/java/org/apache/pinot/plugin/ingestion/batch/spark/SparkSegmentTarPushJobRunner.java#L96


Add queryParamsValues to Request

This method supports URLs like:
http://host/resource?id=foo&id=bar

returning request.getParamsValues("id")as ["foo", "bar"]
It simply delegates to the appropiate method in HttpServletRequest. Without it, the non-intuitive and a bit cumbersome way of getting this result is:
QueryParamsMap paramMap = request.queryMap("id");
if (paramMap.hasValue()) {
    whatever(paramMap.values())
}

I will have a look at this after my vacation (the week after next)

:+1:

:)


enable support for .NET Fx 4.6.1 <-> .NET Standard 2

This should be finished, but I need to do some manual tests.
Let's run CI.

What
This allows users to opt-in to support between .NET Fx 4.6.1 and .NET Standard 2.0.
How
You can set EnableNetFx461NetStandard2Support in the app.config of paket.exe (works both for "normal" paket.exe and magic-mode paket.exe).
If you use Paket.Core as a Library, you can set
DotnetToolingSupport.mode <- ToolingSupportMode.ToolingSupportNetSDK2

Caveats
This is a hacky workaround for a shoddy implementation by Microsoft in the .NET SDK 2.x.
After setting this flag, delete and regenerate your lockfile. Just running install is not enough.
Ensure that the flag is consistently either always on, or always off. Check paket.exe.config into source control.

supersedes https://github.com/fsprojects/Paket/pull/3248
fixes https://github.com/fsprojects/Paket/issues/3004 (it would then add the .NET Standard 2 dll for .NET 4.6.2)
fixes https://github.com/fsprojects/Paket/issues/2986
fixes https://github.com/fsprojects/Paket/issues/2705
ref https://github.com/fsprojects/Paket/pull/2391
and see https://twitter.com/terrajobst/status/1032025428242849793

that error looks unrelated

can you please merge with master?

woud be good to have the setting as a group setting

Hi @forki, sorry for the delay, I've merged latest master and let's see what CI says.

would be good to have the setting as a group setting

when I started with this, i took a look at how a proper implementation could be done, and it was a lot of work, touching almost everything.
You would need to parametrize FrameworkIdentifier.RawSupportedPlatforms by this flag, and pass it everywhere.

After CI is green I'll do another manual test, I think it worked ... almost half a year ago, but just to be sure ...
(And maybe add a test or two)

I wanted to add an end2end integration test, but hit an unexpected issue:
With PR https://github.com/fsprojects/Paket/pull/2664 I made it so that the build doesn't use the local reference assemblies for compilation, but instead from a NuGet package (0x53A.ReferenceAssemblies.Paket).
Currently this package only contains the ref-assemblies for net45, so I can't create a test project with .net461.
Adding the ref-assemblies for net461 into this package would double the package size (from 100MB extracted to 200MB extracted), which i don't think is worth it.
So instead I've create a small unit test which doesn't check compilation, but just resolving.

Manual tests for both direct execution and bootstrapper exection were Ok. If you use the bootstrapper, then you also need the latest paket.exe downloaded, an old one from cache obviously doesn't understand the new flag.

merged master, now build is green again

What's the status of this PR?
I know we have .NET Framework 4.8 now, but some people refuse to install anything newer than 4.6.1 😒

We can't take it as it. We need a group setting for it since it's breaking and even MS admitted it is not correct.

It's not directly breaking, since you would have to enable it in the app.config manually. So if you do nothing, nothing changes.
Can you maybe take a quick look at an implementation strategy?
If you want to make it a group setting, then the hack with the global mutable field isn't enough, you would have to parametrize SupportCalculation.getSupportedPlatforms etc by this flag. It would need to be passed down, and this would touch almost everything.
At least that was my conclusion a year ago, and the reason why I settled on the app.config "hack".

would it work with paket global tool or magic mode?
I feel this should at least be a setting in the deps file

would it work with paket global tool or magic mode?

It should already work with magic mode, just set the app.config of the bootstrapper.

I feel this should at least be a setting in the deps file

I guess that should work - read the setting, then set the global variable before doing any other operations.
It would be treated similar to the "version" global setting.

Yes. That would be great
Lukas Rieger<EMAIL_ADDRESS>schrieb am Fr., 20. Sep. 2019,
18:21:

would it work with paket global tool or magic mode?
It should already work with magic mode, just set the app.config of the
bootstrapper.
I feel this should at least be a setting in the deps file
I guess that should work - read the setting, then set the global variable
before doing any other operations.
It would be treated similar to the "version" global setting.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fsprojects/Paket/pull/3447?email_source=notifications&email_token=AAAOANGGMYLNPGHKE4MQ3HDQKTZ7HA5CNFSM4GIL56J2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7HGQXI#issuecomment-533620829,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAOANHS4QKGP645YGW3FWLQKTZ7HANCNFSM4GIL56JQ
.

@0x53A, where to put

You can set EnableNetFx461NetStandard2Support in the app.config of paket.exe (works both for "normal" paket.exe and magic-mode paket.exe).

What is the structure of app.config? I can't find such a setting anywhere

@0x53A, where to put

You can set EnableNetFx461NetStandard2Support in the app.config of paket.exe (works both for "normal" paket.exe and magic-mode paket.exe).

What is the structure of app.config? I can't find such a setting anywhere

As this PR wasn't merged, there is no such feature.
It wasn't merged because the app settings is more of a hack, and it would have been preferable to add a setting to the paket.dependencies.
Though at that point I didn't have any more time / energy.
Theoretically it would have been in the appSettings:
    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
      <appSettings>
        <add key="EnableNetFx461NetStandard2Support" value="true"/>
      </appSettings>
    </configuration>

As this PR wasn't merged, there is no such feature.
It wasn't merged because the app settings is more of a hack, and it would have been preferable to add a setting to the paket.dependencies.
Though at that point I didn't have any more time / energy.
Theoretically it would have been in the appSettings:
    <?xml version="1.0" encoding="utf-8" ?>
    <configuration>
      <appSettings>
        <add key="EnableNetFx461NetStandard2Support" value="true"/>
      </appSettings>
    </configuration>

any news on this?

@0x53A do we need this or should it be updated?

With .NET 4.6.1 end of life cycle, people had to update the .NET Framework version, where it was possible.
Almost all migrations I've seen were to .NET 4.7.2 and 4.8.0. These support .NET Standard 2 well. I believe that such upgrades are common, which would decrease the importance of this change. However, I've had experience with 4.6.1 -> 4.6.2 bumps too.
The 4.8.1 version looks good, but it's not supported on Windows Server 2019, and we can treat it as 4.8.0.
If you opt for a flag making Paket accept 4.6.1/4.6.2 as .NET Standard 2 compliant, I think that it should be easy to remove as the impact will decrease over time.
Maybe the version match could be delegated and possible to override by an extension?

With .NET 4.6.1 end of life cycle, people had to update the .NET Framework version, where it was possible.
Almost all migrations I've seen were to .NET 4.7.2 and 4.8.0 . These support .NET Standard 2 well. I believe that such upgrades are common, which would decrease the importance of this change. However, I've had experience with 4.6.1 -> 4.6.2 bumps too.
The 4.8.1 version looks good, but it's not supported on Windows Server 2019, and we can treat it as 4.8.0.
If you opt for a flag making Paket accept 4.6.1/4.6.2 as .NET Standard 2 compliant, I think that it should be easy to remove as the impact will decrease over time.
Maybe the version match could be delegated and possible to override by an extension?


"slides: command not found"

Describe the bug
I can't use the CLI command, my system can't find it.
To Reproduce
Steps to reproduce the behavior:

Install or upgrade Go on a Mac using homebrew.
go get github.com/maaslalani/slides
make a basic .md file.
slides basic.md

Expected behavior
I expected the presentation to launch.
Desktop (please complete the following information):

OS: MacOS
Version: 11.2.3

Additional context
I'm using go version go1.16.4 darwin/amd64

follow this guide to add go executables  to your PATH variable: https://sourabhbajaj.com/mac-setup/Go/

Hey! In addition to the solution above, you can also just download the macOS binary and then place it in a place where you have your PATH set.
I think soon I will look into adding slides to homebrew and other package managers so you can just install it without Go.

BTW, you can now install slides with Homebrew
brew install slides

or if you want the latest version
brew install --HEAD slides


bindgen macro: "Use of Undeclared Type HostImports" when WIT world name is host

Problem Description
I created a simple host.wit file to start playing with the component model in an embedded runtime. In this file, I created a world by the name host. I was following the examples in the wasmtime bindgen examples and got an error stating that HostImports did not exist but there was a similar trait named Host_Imports (see build output below). I changed my trait impl to the one shown below and got an error stating that bindgen was creating some code that referenced HostImports.
If I change the world name to anything else, the problem goes away.
Identified Problem Area
I found that there is a function in wasmtime/crates/wit-bindgen/src/rust.rs called to_rust_upper_camel_case that uses Host_ if the provided name is host. This is not being used consistently somewhere.
Project Files
Here are my project files that replicate the issue, along with the cargo expand output that shows the code with an issue (collapsed to improve readability of this ticket).
./Cargo.toml
[package]
name = "host"
version = "0.1.0"
edition = "2021"

[dependencies]
wasmtime = "25.0.1"
wit-bindgen = "0.32.0"

./wit/host.wit
package system:system;

world host {
    import print: func(msg: string);
    export run: func();
}

./src/main.rs
use wasmtime::*;

wasmtime::component::bindgen!("host");

struct State;

impl Host_Imports for State {
    fn print(&mut self, msg: String) {
        println!("{msg}");
    }
}

fn main() {
    println!("Hello, world!");
}

Expanded main.rs

#![feature(prelude_import)]
#[prelude_import]
use std::prelude::rust_2021::*;
#[macro_use]
extern crate std;
use wasmtime::*;
/// Auto-generated bindings for a pre-instantiated version of a
/// component which implements the world `host`.
///
/// This structure is created through [`Host_Pre::new`] which
/// takes a [`InstancePre`](wasmtime::component::InstancePre) that
/// has been created through a [`Linker`](wasmtime::component::Linker).
///
/// For more information see [`Host_`] as well.
pub struct Host_Pre<T> {
    instance_pre: wasmtime::component::InstancePre<T>,
    indices: Host_Indices,
}
impl<T> Clone for Host_Pre<T> {
    fn clone(&self) -> Self {
        Self {
            instance_pre: self.instance_pre.clone(),
            indices: self.indices.clone(),
        }
    }
}
impl<_T> Host_Pre<_T> {
    /// Creates a new copy of `Host_Pre` bindings which can then
    /// be used to instantiate into a particular store.
    ///
    /// This method may fail if the component behind `instance_pre`
    /// does not have the required exports.
    pub fn new(
        instance_pre: wasmtime::component::InstancePre<_T>,
    ) -> wasmtime::Result<Self> {
        let indices = Host_Indices::new(instance_pre.component())?;
        Ok(Self { instance_pre, indices })
    }
    pub fn engine(&self) -> &wasmtime::Engine {
        self.instance_pre.engine()
    }
    pub fn instance_pre(&self) -> &wasmtime::component::InstancePre<_T> {
        &self.instance_pre
    }
    /// Instantiates a new instance of [`Host_`] within the
    /// `store` provided.
    ///
    /// This function will use `self` as the pre-instantiated
    /// instance to perform instantiation. Afterwards the preloaded
    /// indices in `self` are used to lookup all exports on the
    /// resulting instance.
    pub fn instantiate(
        &self,
        mut store: impl wasmtime::AsContextMut<Data = _T>,
    ) -> wasmtime::Result<Host_> {
        let mut store = store.as_context_mut();
        let instance = self.instance_pre.instantiate(&mut store)?;
        self.indices.load(&mut store, &instance)
    }
}
/// Auto-generated bindings for index of the exports of
/// `host`.
///
/// This is an implementation detail of [`Host_Pre`] and can
/// be constructed if needed as well.
///
/// For more information see [`Host_`] as well.
pub struct Host_Indices {
    run: wasmtime::component::ComponentExportIndex,
}
#[automatically_derived]
impl ::core::clone::Clone for Host_Indices {
    #[inline]
    fn clone(&self) -> Host_Indices {
        Host_Indices {
            run: ::core::clone::Clone::clone(&self.run),
        }
    }
}
/// Auto-generated bindings for an instance a component which
/// implements the world `host`.
///
/// This structure can be created through a number of means
/// depending on your requirements and what you have on hand:
///
/// * The most convenient way is to use
///   [`Host_::instantiate`] which only needs a
///   [`Store`], [`Component`], and [`Linker`].
///
/// * Alternatively you can create a [`Host_Pre`] ahead of
///   time with a [`Component`] to front-load string lookups
///   of exports once instead of per-instantiation. This
///   method then uses [`Host_Pre::instantiate`] to
///   create a [`Host_`].
///
/// * If you've instantiated the instance yourself already
///   then you can use [`Host_::new`].
///
/// * You can also access the guts of instantiation through
///   [`Host_Indices::new_instance`] followed
///   by [`Host_Indices::load`] to crate an instance of this
///   type.
///
/// These methods are all equivalent to one another and move
/// around the tradeoff of what work is performed when.
///
/// [`Store`]: wasmtime::Store
/// [`Component`]: wasmtime::component::Component
/// [`Linker`]: wasmtime::component::Linker
pub struct Host_ {
    run: wasmtime::component::Func,
}
pub trait Host_Imports {
    fn print(&mut self, msg: wasmtime::component::__internal::String) -> ();
}
pub trait Host_ImportsGetHost<
    T,
>: Fn(T) -> <Self as Host_ImportsGetHost<T>>::Host + Send + Sync + Copy + 'static {
    type Host: Host_Imports;
}
impl<F, T, O> Host_ImportsGetHost<T> for F
where
    F: Fn(T) -> O + Send + Sync + Copy + 'static,
    O: Host_Imports,
{
    type Host = O;
}
impl<_T: Host_Imports + ?Sized> Host_Imports for &mut _T {
    fn print(&mut self, msg: wasmtime::component::__internal::String) -> () {
        Host_Imports::print(*self, msg)
    }
}
const _: () = {
    #[allow(unused_imports)]
    use wasmtime::component::__internal::anyhow;
    impl Host_Indices {
        /// Creates a new copy of `Host_Indices` bindings which can then
        /// be used to instantiate into a particular store.
        ///
        /// This method may fail if the component does not have the
        /// required exports.
        pub fn new(
            component: &wasmtime::component::Component,
        ) -> wasmtime::Result<Self> {
            let _component = component;
            let run = _component
                .export_index(None, "run")
                .ok_or_else(|| ::anyhow::__private::must_use({
                    let error = ::anyhow::__private::format_err(
                        format_args!("no function export `run` found"),
                    );
                    error
                }))?
                .1;
            Ok(Host_Indices { run })
        }
        /// Creates a new instance of [`Host_Indices`] from an
        /// instantiated component.
        ///
        /// This method of creating a [`Host_`] will perform string
        /// lookups for all exports when this method is called. This
        /// will only succeed if the provided instance matches the
        /// requirements of [`Host_`].
        pub fn new_instance(
            mut store: impl wasmtime::AsContextMut,
            instance: &wasmtime::component::Instance,
        ) -> wasmtime::Result<Self> {
            let _instance = instance;
            let run = _instance
                .get_export(&mut store, None, "run")
                .ok_or_else(|| ::anyhow::__private::must_use({
                    let error = ::anyhow::__private::format_err(
                        format_args!("no function export `run` found"),
                    );
                    error
                }))?;
            Ok(Host_Indices { run })
        }
        /// Uses the indices stored in `self` to load an instance
        /// of [`Host_`] from the instance provided.
        ///
        /// Note that at this time this method will additionally
        /// perform type-checks of all exports.
        pub fn load(
            &self,
            mut store: impl wasmtime::AsContextMut,
            instance: &wasmtime::component::Instance,
        ) -> wasmtime::Result<Host_> {
            let _instance = instance;
            let run = *_instance.get_typed_func::<(), ()>(&mut store, &self.run)?.func();
            Ok(Host_ { run })
        }
    }
    impl Host_ {
        /// Convenience wrapper around [`Host_Pre::new`] and
        /// [`Host_Pre::instantiate`].
        pub fn instantiate<_T>(
            mut store: impl wasmtime::AsContextMut<Data = _T>,
            component: &wasmtime::component::Component,
            linker: &wasmtime::component::Linker<_T>,
        ) -> wasmtime::Result<Host_> {
            let pre = linker.instantiate_pre(component)?;
            Host_Pre::new(pre)?.instantiate(store)
        }
        /// Convenience wrapper around [`Host_Indices::new_instance`] and
        /// [`Host_Indices::load`].
        pub fn new(
            mut store: impl wasmtime::AsContextMut,
            instance: &wasmtime::component::Instance,
        ) -> wasmtime::Result<Host_> {
            let indices = Host_Indices::new_instance(&mut store, instance)?;
            indices.load(store, instance)
        }
        pub fn add_to_linker_imports_get_host<T>(
            linker: &mut wasmtime::component::Linker<T>,
            host_getter: impl for<'a> Host_ImportsGetHost<&'a mut T>,
        ) -> wasmtime::Result<()> {
            let mut linker = linker.root();
            linker
                .func_wrap(
                    "print",
                    move |
                        mut caller: wasmtime::StoreContextMut<'_, T>,
                        (arg0,): (wasmtime::component::__internal::String,)|
                    {
                        let host = &mut host_getter(caller.data_mut());
                        let r = HostImports::print(host, arg0);
                        Ok(r)
                    },
                )?;
            Ok(())
        }
        pub fn add_to_linker<T, U>(
            linker: &mut wasmtime::component::Linker<T>,
            get: impl Fn(&mut T) -> &mut U + Send + Sync + Copy + 'static,
        ) -> wasmtime::Result<()>
        where
            U: Host_Imports,
        {
            Self::add_to_linker_imports_get_host(linker, get)?;
            Ok(())
        }
        pub fn call_run<S: wasmtime::AsContextMut>(
            &self,
            mut store: S,
        ) -> wasmtime::Result<()> {
            let callee = unsafe {
                wasmtime::component::TypedFunc::<(), ()>::new_unchecked(self.run)
            };
            let () = callee.call(store.as_context_mut(), ())?;
            callee.post_return(store.as_context_mut())?;
            Ok(())
        }
    }
};
const _: &str = "package system:system;\n\nworld host {\n    import print: func(msg: string);\n    export run: func();\n}\n";
struct State;
impl Host_Imports for State {
    fn print(&mut self, msg: String) {
        {
            ::std::io::_print(format_args!("{0}\n", msg));
        };
    }
}
fn main() {
    {
        ::std::io::_print(format_args!("Hello, world!\n"));
    };
}

Build Output
error[E0433]: failed to resolve: use of undeclared type `HostImports`
 --> src/main.rs:3:1
  |
3 | wasmtime::component::bindgen!("host");
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ use of undeclared type `HostImports`
  |
  = note: this error originates in the macro `wasmtime::component::bindgen` (in Nightly builds, run with -Z macro-backtrace for more info)

warning: unused import: `wasmtime`
 --> src/main.rs:1:5
  |
1 | use wasmtime::*;
  |     ^^^^^^^^
  |
  = note: `#[warn(unused_imports)]` on by default

For more information about this error, try `rustc --explain E0433`.
warning: `host` (bin "host") generated 1 warning
error: could not compile `host` (bin "host") due to 1 previous error; 1 warning emitted

The issue appears to be in wasmtime/crates/wit-bindgen/src/lib.rs
I'll try making a quick change to see if I can get it to work and then submit a PR.

Fixed in https://github.com/bytecodealliance/wasmtime/pull/9316


Rails Form Not Submitting

I've got a bit of code that is trying to create a forum in Redmine.
  agent.get('http://myredmine/projects/change/boards/new')
  forum = agent.page.form_with(action: '/projects/change/boards')
  button = forum.button_with(value: 'Create')
  forum['board[name]'] = '2484: Setup and Customize Test VPN'
  forum['board[description]'] = 'VPN Forum'
  agent.submit(forum, button)

The code seems to submit correctly, but no forum is created.  I looked at the Rails logs and compared a manual submission from my code to one coming from the browser.
Here is the submission from my code notice the extra "Rendered" lines.  No forum created.
Started POST "/projects/change/boards" for <IP_ADDRESS> at 2015-03-10 15:35:43 -0500
Processing by BoardsController#create as */*
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"TOKEN=", "board"=>{"name"=>"2484: Setup and Customize Test VPN", "description"=>"VPN Forum", "parent_id"=>""}, "commit"=>"Create", "project_id"=>"change"}
  Current user: matt (id=3)
  Rendered boards/_form.html.erb (3.1ms)
  Rendered boards/new.html.erb within layouts/base (114.0ms)
  Rendered plugins/redmine_wiki_extensions/app/views/wiki_extensions/_html_header.html.erb (4.6ms)
  Rendered plugins/redmine_wiki_extensions/app/views/wiki_extensions/_body_bottom.html.erb (2.7ms)
Completed 200 OK in 161.1ms (Views: 148.4ms | ActiveRecord: 5.8ms)

Here is the submission from the browser, which is missing the Rendered erb helpers... but this way works fine.  A forum gets created.....then the browser redirects to the main forums page.
Started POST "/projects/change/boards" for <IP_ADDRESS> at 2015-03-10 15:36:37 -0500
Processing by BoardsController#create as HTML
  Parameters: {"utf8"=>"✓", "authenticity_token"=>"TOKEN", "board"=>{"name"=>"test3", "description"=>"test3", "parent_id"=>""}, "commit"=>"Create", "project_id"=>"change"}
  Current user: matt (id=3)
Redirected to http://myredmine/projects/change/settings/boards
Completed 302 Found in 13.4ms (ActiveRecord: 3.7ms)
Started GET "/projects/change/settings/boards" for <IP_ADDRESS> at 2015-03-10 15:36:37 -0500
Processing by ProjectsController#settings as HTML
  Parameters: {"id"=>"change", "tab"=>"boards"}
  Current user: matt (id=3)
  Rendered projects/_form.html.erb (43.4ms)
  Rendered projects/_edit.html.erb (45.3ms)
  Rendered projects/settings/_modules.html.erb (11.5ms)
  Rendered projects/settings/_members.html.erb (185.4ms)
  Rendered projects/settings/_versions.html.erb (7.3ms)
  Rendered projects/settings/_issue_categories.html.erb (1.3ms)
  Rendered projects/settings/_wiki.html.erb (1.8ms)
  Rendered projects/settings/_repositories.html.erb (1.6ms)
  Rendered projects/settings/_boards.html.erb (12.6ms)
  Rendered projects/settings/_activities.html.erb (18.5ms)
  Rendered plugins/redmine_wiki_extensions/app/views/wiki_extensions_settings/_menu.html.erb (2.5ms)
  Rendered plugins/redmine_wiki_extensions/app/views/wiki_extensions_settings/_show.html.erb (9.8ms)
  Rendered common/_tabs.html.erb (434.3ms)
  Rendered projects/settings.html.erb within layouts/base (435.2ms)
  Rendered plugins/redmine_wiki_extensions/app/views/wiki_extensions/_html_header.html.erb (4.0ms)
  Rendered plugins/redmine_wiki_extensions/app/views/wiki_extensions/_body_bottom.html.erb (0.1ms)
Completed 200 OK in 478.7ms (Views: 447.8ms | ActiveRecord: 20.1ms)

One difference I see is the BoardsController#create as HTML from the browser is working, the BoardsController#create as */* from the code is not.  Not sure if that matters or not.
Anyone have any thoughts or suggestions?
Thanks,
Matt

Hi Matt, sorry I've only just got around to looking at this. Did you figure it out?


Invoke -- malloc for array of struct has wrong bitcast/type identification

Defect
The following C++ allocation is wrongly identified by TypeART as int64 (LLVM 10)
  struct S1 {
    int x;
    virtual ~S1() = default;
  };
  try {
    S1* ss = new S1[2];
  } catch (...) {
  }

LLVM/TypeART Generated Code
  %5 = invoke i8* @_Znam(i64 40) #4
          to label %6 unwind label %16

6:                                                ; preds = %0
  call void @__typeart_alloc(i8* %5, i32 3, i64 5)
  %7 = bitcast i8* %5 to i64*
  store i64 2, i64* %7, align 16
  %8 = getelementptr inbounds i8, i8* %5, i64 8
  %9 = bitcast i8* %8 to %struct.S1*
  %10 = getelementptr inbounds %struct.S1, %struct.S1* %9, i64 2
  br label %11

Two bitcasts are generated.
TypeART erroneously takes the first one as the candidate to extract the type (i32 3 -> i64).

Extended defect
This issue also extends to the way types are allocated with new expressions and the implicit size that is added to the allocation, see generated code example line 7-8 (before the bitcast to S1).
Problem
Which pointer needs to be passed to the TypeART runtime?
We take %5 currently, but %9 may be the correct address (which may have further implications on handling memory addresses and "legal" bounds).
This may spawn an additional issue, which will be referenced here.


new Client() has side-effect of destroying old clients/queries

That means that Query.destroying on old Clients now throw exceptions because they are already cleaned up.
This is okay for systems where lifetime is precisely managed (old query should be cleaned up before client is cleaned up), but this is often not the case in JS frameworks.
As an aside: registering Clients (and having side-effects) in its constructor function seems like a strong a anti-pattern to me. I would never expect code to behave like that.

There is a Client Registry that allows components (and apps) to find a Client by App ID.  Having two Clients share an App ID would break many things.  This has both pros and cons.
Largest Con from my perspective is that it prevents a single app from having two clients allowing someone to authenticate as both an "Admin" user and as a regular user.
Largest Pro is that one needs only an App ID to get a Client, saving both WebSDK Components and your app from having to pass pointers to the Client everywhere. (We do have a task to investigate using some other ID, but that would mean only WebSDK components could do it, and not Apps themselves).  Its much simpler to pass an appId than a Client among Angular Components that will be inspecting that Client for changes, modifying it with tracking properties, etc....
What your calling a side effect and an anti-pattern is to my perspective is a natural part of having a registry and a standard part of working with registries in that 1. all components side effect on being created by registering themselves, and 2. components that are not distinct must either throw errors or destroy the prior component.
If you are explicitly calling query.destroy(), you could instead try:
if (!query.isDestroyed) query.destroy();

Alternatively, you could do:
if (!layer.Client.getClient(appId)) {
   client = new layer.Client({
      appId: appId
   });
}

One thing to keep in mind as well is that any pattern that does NOT cleanup prior Clients, means an app that iterates and recreates the Client a dozen times will now have a dozen live websocket connections... something we would consider harmful.  Alternate suggestions are welcome, but this more than anything else would have to be prevented.

Not much folllow up here.  May at some point replace Client constructor with factory method, but thats a breaking change, and is currently the only solution that still returns a valid Client.  Reopen to discuss further.


emergency equipment (x2 toolbox, x2 hazard vest, x5 oxygen tank, x5 masks) Cost: $2000

Oxygen and masks can be removed from this


[git-sync] Allow random failures

This PR introduces a flag to allow failures in the sync operation
$ docker run -it \
> -e GIT_SYNC_REPO="https://********** repo url **********.git" \
> -e GIT_SYNC_DEST="/git" \
> -e GIT_SYNC_MAX_SYNC_FAILURES="10" \
> gcr.io/google_containers/git-sync
2016/04/21 12:52:17 setting up the git credential cache
2016/04/21 12:52:18 clone "https://********** repo url **********.git": Cloning into '/git'...
2016/04/21 12:52:19 fetch "master": From https://********** repo url **********
 * branch            master     -> FETCH_HEAD
Already up-to-date.
2016/04/21 12:52:19 reset "HEAD": HEAD is now at befa882 feat(*): incorporación de versión 06958961
2016/04/21 12:52:19 wait 10 seconds
2016/04/21 12:52:29 done
2016/04/21 12:52:30 fetch "master": From https://********** repo url **********
 * branch            master     -> FETCH_HEAD
Already up-to-date.
2016/04/21 12:52:30 reset "HEAD": HEAD is now at befa882 feat(*): incorporación de versión 06958961
2016/04/21 12:52:30 wait 10 seconds
2016/04/21 12:52:40 done

after disconnecting internet access
2016/04/21 12:53:20 unexpected error syncing repo: error running command "git pull origin master" : exit status 1: fatal: unable to access 'https://********** repo url **********.git/': Could not resolve host: ********** host **********
2016/04/21 12:53:20 wait 10 seconds before retryng
2016/04/21 12:54:10 unexpected error syncing repo: error running command "git pull origin master" : exit status 1: fatal: unable to access 'https://********** repo url **********.git/': Could not resolve host: ********** host **********
2016/04/21 12:54:10 wait 10 seconds before retryng
2016/04/21 12:55:00 unexpected error syncing repo: error running command "git pull origin master" : exit status 1: fatal: unable to access 'https://********** repo url **********.git/': Could not resolve host: ********** host **********
2016/04/21 12:55:00 wait 10 seconds before retryng
2016/04/21 12:55:50 unexpected error syncing repo: error running command "git pull origin master" : exit status 1: fatal: unable to access 'https://********** repo url **********.git/': Could not resolve host: ********** host **********
2016/04/21 12:55:50 wait 10 seconds before retryng
2016/04/21 12:56:40 unexpected error syncing repo: error running command "git pull origin master" : exit status 1: fatal: unable to access 'https://********** repo url **********.git/': Could not resolve host: ********** host **********
2016/04/21 12:56:40 wait 10 seconds before retryng
2016/04/21 12:57:30 error syncing repo: error running command "git pull origin master" : exit status 1: fatal: unable to access 'https://********** repo url **********.git/': Could not resolve host: ********** host **********

@bprashanth who can review this?

ping @thockin


Add 'copy' to available codecs

Q
A

Bug?
no

New Feature?
Yes

Version Used
Specific tag or commit sha

FFmpeg Version
FFmpeg or AVConv and version

OS
Your OS and version

Is it possible to add 'copy' as an available video/audio codec for X264?
I've tested this by simply adding it to the front of each array in FFMpeg\Format\Video\X264 and seems to work fine
This is helpful when you have a video of the same codec/size etc and you don't care about converting bitrate, you just want to add +faststart, for example, as it doesn't have to re-encode the entire video and completes in only a few seconds.
any reason not to allow this as an option?

Duplicate of #645. The version was just released a few moments ago.


Fix/regex comparator

Fixes

Issue #3

Proposed Changes
Add strict comparison

Thank you @itailulu for the fix and good catch :+1:


CNV-31218: Update "Review and create VM" page title and its breadcrumbs

📝 Description
Fixes:
https://bugzilla.redhat.com/show_bug.cgi?id=2224357
Jira:
https://issues.redhat.com/browse/CNV-31218
Make the following changes in Customize Template parameters page:

change page title to Customize template parameters (small "t")
change the breadcrumb from Customize to Customize template parameters, too
change the Next button text to Customize VirtualMachine parameters

Make the following changes in Review and create VirtualMachine page:

change the title page to Customize and create VirtualMachine
change the breadcrumb from Customize to Customize template parameters (same as in the previous page)
change the breadcrumb from Review to Customize VirtualMachine

Make these text changes according to the doc team suggestions.
🎥 Screenshots
Before:
Customize Template parameters page:

Review and create VirtualMachine page:

After:
Updated Customize template parameters page:

Renamed Customize and create VirtualMachine page:

/lgtm

/retest

I still have a question why do we think the first page is "Customize template parameters" and the second page is "Customize and create VirtualMachine"? Both of these pages are customizing the VirtualMachine's parameters by clicking the customize button just after selecting a template, isn't it?

/retest


fix loading imager after v14 of AIonedge #12

Did you maybe rather mean if (url[:-3] != 'jpg') ?

thanks for advice. No url[-3:] != 'jpg' is correct


Add a FAQ

We need a FAQ section on the docs.
I see a lot of people coming to discussions thread to understand how to use custom scopes etc.
It would be wise to provide some examples and add relevant docs as a FAQ

I came here because I am stuck on scopes :(

We will provide a FAQ section soon(even its out of scope of this library, people often needs it anyway)


npm or yarn?

I see both package-lock.json and yarn.lock files in the repo.
Running npm install modifies both package.json and package-lock.json.
Running yarn install modifies yarn.lock.
The contributing wiki does not indicate a preference.
Seems like one of the lock files should be removed and the other should be updated and committed.
I'm not the most proficient npm/yarn user so I apologize if I am missing something obvious here.
package-lock.json changes after npm install

yarn.lock changes after yarn install (truncated)

ah, thanks for pointing that out. I don't believe I've ever used yarn so it probably came from another contributor and I missed it. I'll remove it in favor of npm.


[Typography] after upgrading @mui/material from 5.x to 6.x the TS type of the color prop changed and shows an error for old implementations

Steps to reproduce
Links to live example:

link to version 5.x without ts error: https://stackblitz.com/edit/vitejs-vite-svnirn?file=src%2FApp.tsx&terminal=dev
link to version 6.x with ts error: https://stackblitz.com/edit/vitejs-vite-svnirn?file=src%2FApp.tsx

Steps:
Just use Typography component like this:
<Typography
     color={(theme) => theme.palette.error.main}
>
     h1. Heading
</Typography>

Since 6.0.0 version, although the code itself works and the color is applied  - TS display 2 errors for this implementation:

No overload matches this call.
  Overload 1 of 2, '(props: { component: ElementType<any, keyof IntrinsicElements>; } & TypographyOwnProps & CommonProps & Omit<any, "children" | ... 112 more ... | "variantMapping">): Element | null', gave the following error.
    Type '(theme: any) => any' is not assignable to type '(string & {}) | OverridableStringUnion<"primary" | "secondary" | "success" | "error" | "info" | "warning" | "textLink" | "textDisabled" | "textPrimary" | "textSecondary", TypographyPropsColorOverrides> | undefined'.
  Overload 2 of 2, '(props: DefaultComponentProps<TypographyTypeMap<{}, "span">>): Element | null', gave the following error.
    Type '(theme: any) => any' is not assignable to type '(string & {}) | OverridableStringUnion<"primary" | "secondary" | "success" | "error" | "info" | "warning" | "textLink" | "textDisabled" | "textPrimary" | "textSecondary", TypographyPropsColorOverrides> | undefined'.

Parameter 'theme' implicitly has an 'any' type.

From reading the declarations files, it seems that you changed the type of color prop.
This is the type in version 5.x:
(property) color?: ResponsiveStyleValue<Property.Color | readonly string[] | undefined> | ((theme: Theme) => ResponsiveStyleValue<AllSystemCSSProperties["color"]>)

And this is the type in version 6.x:
(property) TypographyOwnProps.color?: (string & {}) | OverridableStringUnion<"primary" | "secondary" | "success" | "error" | "info" | "warning" | "textDisabled" | "textPrimary" | "textSecondary", TypographyPropsColorOverrides> | undefined

Current behavior
No response
Expected behavior
No response
Context
No response
Your environment

npx @mui/envinfo
  System:
    OS: Linux 5.0 undefined
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  Browsers:
    Chrome: latest
  npmPackages:
    @emotion/react: ^11.13.3 => 11.13.3
    @emotion/styled: ^11.13.0 => 11.13.0
    @mui/core-downloads-tracker:  6.0.2
    @mui/material: ^6.0.1 => 6.0.2
    @mui/private-theming:  6.0.2
    @mui/styled-engine:  6.0.2
    @mui/system:  6.0.2
    @mui/types:  7.2.16
    @mui/utils:  6.0.2
    @types/react: ^18.3.5 => 18.3.5
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    typescript: ^5.5.3 => 5.5.4

tsconfig
{
  "compilerOptions": {
    "jsx": "react-jsx",
    "useDefineForClassFields": true,
    "lib": ["ES2021", "DOM", "DOM.Iterable"],
    "skipLibCheck": true,

    /* Bundler mode */
    "moduleResolution": "bundler",
    "module": "ESNext",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "moduleDetection": "force",
    "noEmit": true,

    /* Linting */
    "strict": true,
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noFallthroughCasesInSwitch": true,
    "esModuleInterop": true
  },
  "include": ["src/**/*"],
  "exclude": ["dist", "node_modules"]
}

Search keywords: Typography, color prop, typescipt, ts, error

@mnajdova  Thanks for the quick reply 🙂

I hope the explanation help. @siriwatknp to consider if we should improve a bit the migration guide on this one.

Thanks @mnajdova, will do.


add central_limit_theorem

PR Checklist
If you are contributing to Javis.jl, please make sure you are able to check off each item on this list:

[ ] Did I update CHANGELOG.md with whatever changes/features I added with this PR?
[x] Did I make sure to only change the part of the file where I introduced a new change/feature?
[x] Did I cover all corner cases to be close to 100% test coverage (if applicable)?
[ ] Did I properly add Javis dependencies to the Project.toml + set an upper bound of the dependency (if applicable)?
[ ] Did I properly add test dependencies to the test directory (if applicable)?
[ ] Did I check relevant tutorials that may be affected by changes in this PR?
[ ] Did I clearly articulate why this PR was made the way it was and how it was made?

I try to add the central_limit_theorem example. To do so I added central_limit_theorem.jl to the examples folder. central_limit_theorem.gif to the docs/src/assets/ folder and adited docs/src/examples.md to make the new one appear in a similar way to how the others do.

Hi, I was wandering if there is something else I have to do for the pr because I don't understand some of the messages like those from codecov[bot]. Anyway if there is please tell me and I am happy to do it!

I don't know why it didn't run. Sorry I was quite busy over the weekend. Ping @TheCedarPrince if u have time to check this and merge

Thanks for the contribution @gpucce ! Looks really great and a very nice animation! :smile:


fix some links with 404 error

Fix some links with 404 error.
I have checked the validity of all links started with "https://godoc.org"!

/hold
@SataQiu thanks!
please remove the kubeadm* releated changes because it duplicates with my PR here:
https://github.com/kubernetes/website/pull/10283
the minikube changes are fine!

please remove the kubeadm* releated changes because it duplicates with my PR here:
#10283

LGTM, thanks

Thanks！I have removed the kubeadm* releated changes. @neolit123

thanks
/hold cancel

/lgtm

/approve

/assign @chenopis

/assign @bradtopol


Capstone project setup

Hi there 👋
Here's a link to the project.
There are 3 people in this team.

Status: ✔ Project Approved ✔
Hi @laiifuu,
Everything is looking great! Please, start this capstone project :shipit:
Congratulations! 🎉
Cheers and Happy coding!👏👏👏

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think the code review was unfair, you can request a second opinion using this form.


chore: introduce zx, corepack and setup script

Summary

🤖 Generated by Copilot at 2e274e3
This pull request adds a setup script and a doctor script to the project to help developers prepare their environment and tools for working on the project. It also adds some comments to disable TypeScript checking for some JavaScript files that use external modules and features. Additionally, it adds a .gitignore file, a package.json file, and a tsconfig.json file to the scripts folder to manage the dependencies and configuration of the scripts.

Walkthrough

🤖 Generated by Copilot at 2e274e3

Add a setup script and a doctor script to improve the developer workflow and environment (link, link, link)
Run the doctor script automatically before installing dependencies with pnpm (link)
Add TypeScript support and configuration for the scripts folder (link)
Add the zx module as a dependency for writing shell scripts in JavaScript and TypeScript (link)
Disable TypeScript checking for JavaScript files that use Node.js or external modules and functions (link, link, link, link, link, link)
Ignore the node_modules folder in the scripts folder (link)

Related issue (if exists)
#2678

@hyf0 I think we have a chicken and egg problem here, we haven't done npm install here  so zx is undefined ...
rspack  main ❯ node scripts/meta/setup.mjs
node:internal/errors:478
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'zx' imported from /Users/bytedance/github/rspack/scripts/meta/setup.mjs

You are right. It looks like setup.mjs shouldn't rely on any dependency. Yeah, I just realized the reason why I create the folder using the name `meta :(.


community: Use _AstraDBCollectionEnvironment in AstraDB VectorStore (community)

Another PR will be done for the langchain-astradb package.
Note: for future PRs, devs will be done in the partner package only. This one is just to align with the rest of the components in the community package and it fixes a bunch of issues.

@cbornet once the partner package is ready, you could use the @deprecated decorator to ask users to move to the partner package


[Bug]: The getProducts method is causing an unhandled error when loading product without any taxons on a certain product's page.

Expected Behavior
When you go to a certain product's page, the backend uses the getProducts function to the "suggested" products. It should load or skip them them no matter they have any taxons or not.
Actual Behavior
The products without taxons cause unhandled errors because the backend tries to parse the taxons no matter they exist or not.
Possible Solution
It is possible that in the function "buiildBreadcrums" in the file api-client/src/api/serializers/product.ts handling addTaxonToBreadcrumbs conditionally if taxons exist will fix the issue.

Steps to reproduce
Connect a backend with products that don't have any taxons assigned to them and go to any certain product's page. Following error should appear:

What version of Spree integration are you using?
1.2.0
What version of Node.js are you using?
14.17.6
What browser (and version) are you using?
Brave
What operating system (and version) are you using?
macOS
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

I was experiencing the issue identified above on every page load (including homepage). The suggested solution resolved the issue for me. Thanks @witoldkesek


qalculate-gtk: 3.8.0 -> 3.8.0a

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/qalculate-gtk/versions.
meta.description for qalculate-gtk is: "The ultimate desktop calculator"
meta.homepage for qalculate-gtk is: "http://qalculate.github.io"
Updates performed:

Version update

Compare changes on GitHub

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.8.0a with grep in /nix/store/frhlvns6h0m3w2q1gy2gjm5v24lhm106-qalculate-gtk-3.8.0a

directory tree listing: https://gist.github.com/411ccf553a48145eb8d4a62d78c8e23e

du listing: https://gist.github.com/e97ec9bfdc5d32407d96c69ed7fbbc88

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
qalculate-gtk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/frhlvns6h0m3w2q1gy2gjm5v24lhm106-qalculate-gtk-3.8.0a \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A qalculate-gtk https://github.com/r-ryantm/nixpkgs/archive/67ea5a0081f5f55890ca5523ed0782590710aa1d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/frhlvns6h0m3w2q1gy2gjm5v24lhm106-qalculate-gtk-3.8.0a
ls -la /nix/store/frhlvns6h0m3w2q1gy2gjm5v24lhm106-qalculate-gtk-3.8.0a/bin

cc @gebner for testing.

@GrahamcOfBorg eval


Update README.md to add missing dependency

Added some other fixes that I feel are good to have.

Thank you for your contribution!


nCr Modulo Any Mod cpp

I would like to nCr Modulo Any Mod in c++

Adde PR #173 for this issue. Do check it out!


[WFLY-1007] Warnings about missing notification descriptions

check that the notification is described by the resource registry at
the time emit(Notification) is called and buffer the eventual
warnings. These warnings will be logged only at the end of the operation
execution if it actually successful.
JIRA: https://issues.jboss.org/browse/WFCORE-1007

I have manually checked that calling the :migrate operation on the legacy messaging subsystem no longer generate these spurious WFLYCTL0357: Notification of type resource-removed is not described for the resource ... warnings


Problem with Image captured by script

Sorry for the bad title, I'm not sure how to explain what I am seeing 100%.
I've been able to get the script running, and it launches the 4 windows (original, background removed, output, etc.). Upon launching the windows, the "original" has a still frame of the camera's view at that moment. the other 3 are black screens, and I keep getting application non-responsive errors. Eventually the entire machine locks up.
I'm running this on an Ubuntu VM currently, and installing a Windows VM to test next. I had issues running on Mac OS (apple silicon), and decided to move away from that. If I can get it working, I plan to move to dedicated hardware later.
Any Thoughts?

Update: I have exact same behavior on Windows.. application windows all pop up, but I get a still frame on "original" while the others stay blank, and everything freezes.

I actually found a post from 2019 of someone with a similar problem.. and it was the OpenCV version. I think I might be good to go now.


Python3 - updated

this is an updated that is rebased against upstream's master as of today. maybe it's easier if you just fetched the whole branch.

I just merged in a PR that merged master, so I think this rebase is going to conflict now.


Define 99303 and 99304 exit codes in the WMExceptions

Fixes #7268

Can I request when this goes through you let P&R know. What will these exit codes be telling us?
We are working on trying to automate things in production, but we need to know what we are cueing off when work comes out of WMStats

These are not new exit codes Jen, I'm just "defining" them in the usual place.

99303's we have been seeing but not 99304's
https://docs.google.com/spreadsheets/d/1onZky6rW2z7NRvvQaLrBGaS8iFfYSg_EL71F1l3mTWE/edit#gid=0
https://twiki.cern.ch/twiki/bin/view/CMS/CompOpsPRWorkflowTrafficController#Error_Codes_Mapping
and neither are on
https://twiki.cern.ch/twiki/bin/view/CMSPublic/JobExitCodes

@jenimal, Jen in that case those document you are pointing needs to be updated.
99303, 99304 exit code indicates as Alan explained in the patch (No Job report).
99303 is any case we don't have a job report. And 99304 is the specific case we don't even have job cache directory. Looking at the document you pointed it is related site issues, etc. But that is pure coincidence. WMAgent doesn't know which specific issue is since there is no job report.

Thank you!  I will update the documents.  They come from observational looks at what we see in day to day operations.  Any input from developers on the list is welcome!
Thanks,
Jen


(PUP-3750) Support :include: in mailalias type

The mailalias type does not allow the specification of included files,
which contain an alias's elements. Such alias entries are commonly
specified in the an MTA's aliases file through the following syntax.
aliasname: :include: /path/to/file
Specifying the rest of an ":include:" line as a recipient does not
work, because the existing mailalias type will quote the entry.
This change adds a new parameter named "file" to the mailalias type,
which allows the indirect specification of a file containing the
recipients.  The parameter parses and generates ":include:" alias entries.

Can you squash commits to remove the intermediate work?

OK. To avoid rewriting history on a publicly visible repo, I have created a new pull request.

Merged the new request, thanks.


Break es6-shim into smaller, independent submodules

Libraries like prfun (incidentally recommended in the es6-shim README) augment the Promise prototype with additional methods.  Promise.promisify is particularly nice.
I just tried incorporating the es6-shim into my Node 0.11.13 project to get access to the Array polyfills.  Now, I'm getting Promise.promisify cannot be found errors.  A quick skim through the shim source shows that es6-shim completely overwrites the global Promise object with its own polyfill when it isn't satisfied with the present implementation.
I could probably work around this by including es6-shim before prfun, but the library that includes prfun and the one that includes es6-shim have nothing to do with each other.  It'd be a shame to introduce a needless dependency to work around this.

:+1:

Why don't you just use individual shims?

@paulmillr total size and compatibility? For example, Array.from individual shim not supports iterators, which makes it almost useless.
P.S. core-js supports custom build and splitted to commonjs submodules (not fully yet) :)

I'm reluctant to the idea of ES6 shim consisting of 20 npm submodules. maybe something what @appsforartists mentioned

Why does the number of submodules matter? The size of the built JS file used in a browser would be basically equivalent, and "more dependencies" is a good thing :-)

"more dependencies" is a good thing

not when you see npm making 1000 requests to the server on a slow connection. Ask jdalton for his terrible experience with breaking down lodash

As a Webpack user, a monolithic library that touches a bunch of unrelated native prototypes is very unappealing.  I didn't know about core-js when I opened this issue, but now that @zloirock has shared that link, I may go there the next time I need a polyfill because of its modularity.
(FWIW, I think @ljharb is on the right track - if you want to release a single file, just run Webpack over your repo.  There's no reason to have all your code in a single script.  That said, I'm unfamiliar with @jdalton's experience with lodash.)

:heart: modules.

@jdalton where are all github repos for lodash methods?

@paulmillr - think files, not repos

What @appsforartists said.
https://github.com/lodash/lodash/tree/amd
https://github.com/lodash/lodash/tree/es
https://github.com/lodash/lodash/tree/npm
https://github.com/lodash/lodash/tree/npm-packages
https://github.com/lodash/lodash-compat/tree/amd
https://github.com/lodash/lodash-compat/tree/npm
https://github.com/lodash/lodash-node
https://github.com/lodash/lodash-amd

hmm interesting
yeah, maybe that'll work. One repo, many files.

+1

+1

It would be great to have the following bundles
Math
String
Number
Promise
RegExp
Array
Object
Reflect
Collection
Symbol

If and when we do this, you'll be able to import a la Array, Array.prototype, Array.prototype.find - any granularity you wish.