Add catalog and metadata vulnerability details

Updates the docs to cover both the catalog and registration metadata inclusions for package vulnerabilities.

Docs Build status updates of commit 5adc768:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/catalog-resource.md
:bulb:Suggestion
View
Details

docs/api/registration-base-url-resource.md
:bulb:Suggestion
View
Details

docs/api/_data/catalog-package-details.json
:white_check_mark:Succeeded
View

docs/api/_data/package-registration-index.json
:white_check_mark:Succeeded
View

docs/api/catalog-resource.md

Line 62, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 99, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 161, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

docs/api/registration-base-url-resource.md

Line 91, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 265, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 302, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 340, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Docs Build status updates of commit f3389cd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/catalog-resource.md
:bulb:Suggestion
View
Details

docs/api/registration-base-url-resource.md
:bulb:Suggestion
View
Details

docs/api/_data/catalog-package-details.json
:white_check_mark:Succeeded
View

docs/api/_data/package-registration-index.json
:white_check_mark:Succeeded
View

docs/api/catalog-resource.md

Line 62, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 99, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 161, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

docs/api/registration-base-url-resource.md

Line 91, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 265, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 302, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 340, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Docs Build status updates of commit 0faee29:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/catalog-resource.md
:bulb:Suggestion
View
Details

docs/api/registration-base-url-resource.md
:bulb:Suggestion
View
Details

docs/api/_data/catalog-package-details.json
:white_check_mark:Succeeded
View

docs/api/_data/package-registration-index.json
:white_check_mark:Succeeded
View

docs/api/catalog-resource.md

Line 62, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 99, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 161, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

docs/api/registration-base-url-resource.md

Line 91, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 265, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 302, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 340, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

IMO we should wait on merging this PR until the client experience is confidently implemented and even shipped. For the package types case, we waited until a .NET CLI preview had shipped with search by package type functionality.
Essentially we should only commit to the protocol in the docs when the E2E experience is pretty much done.

@zivkan

Has this feature gone through a design spec? (was client team involved? maybe I just missed it) That should be agreed on before updating our official docs for how the protocol is changed.

Yes, it has (before my time on team though)--here are:

the dotnet CLI spec, and
the PM UI spec

@joelverhagen

Essentially we should only commit to the protocol in the docs when the E2E experience is pretty much done.

Okay, that sounds good to me. I'll leave the PR up thought if that works.

Docs Build status updates of commit 42fdd26:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/catalog-resource.md
:bulb:Suggestion
View
Details

docs/api/registration-base-url-resource.md
:bulb:Suggestion
View
Details

docs/api/_data/catalog-package-details.json
:white_check_mark:Succeeded
View

docs/api/_data/package-registration-index.json
:white_check_mark:Succeeded
View

docs/api/catalog-resource.md

Line 62, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 99, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 161, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

docs/api/registration-base-url-resource.md

Line 91, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 265, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 302, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.
Line 340, Column 0: [Suggestion-code-block-indented] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```). NOTE: This Suggestion will become a Warning in late September, 2020.

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

Relies on https://github.com/NuGet/NuGetGallery/issues/8084 & Client experience work.

Docs Build status updates of commit 175a91a:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 175a91a:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 175a91a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/_data/catalog-package-details.json
:white_check_mark:Succeeded
View

docs/api/_data/package-registration-index.json
:white_check_mark:Succeeded
View

docs/api/catalog-resource.md
:white_check_mark:Succeeded
View

docs/api/registration-base-url-resource.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 175a91a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/_data/catalog-package-details.json
:white_check_mark:Succeeded
View

docs/api/_data/package-registration-index.json
:white_check_mark:Succeeded
View

docs/api/catalog-resource.md
:white_check_mark:Succeeded
View

docs/api/registration-base-url-resource.md
:white_check_mark:Succeeded
View

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

@JonDouglas I just rebased this on master to prepare it, so let's merge it when other pieces drop.

@JonDouglas I just rebased this on master to prepare it, so let's merge it when other pieces drop.

Docs Build status updates of commit 6d1e252:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6d1e252:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6d1e252:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/_data/catalog-package-details.json
:white_check_mark:Succeeded
View

docs/api/_data/package-registration-index.json
:white_check_mark:Succeeded
View

docs/api/catalog-resource.md
:white_check_mark:Succeeded
View

docs/api/registration-base-url-resource.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 6d1e252:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/api/_data/catalog-package-details.json
:white_check_mark:Succeeded
View

docs/api/_data/package-registration-index.json
:white_check_mark:Succeeded
View

docs/api/catalog-resource.md
:white_check_mark:Succeeded
View

docs/api/registration-base-url-resource.md
:white_check_mark:Succeeded
View

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


Release v0.5?

@bmorris3 or anyone - would it be possible to release a new stable version of astroplan now or soon?
I got a question about some issue from a user, and it turned out, it was already fixed in master.
The last release is v0.4 from Oct 2017:
https://pypi.org/project/astroplan/#history
Maybe close the v0.3 milestone, and introduce milestones for 0.5 and 0.6?
https://github.com/astropy/astroplan/milestones
I find using milestones is helpful for devs, but it's also useful for outsiders like me to see if / when a new release is planned.

@cdeil You got it! Sorry for the delay 😄

Released on pypi! @mwcraig – may I trouble you for a reminder on how to update the conda-forge correctly for astroplan v0.5?

@bmorris3 - awesome, thanks!
pip install and running tests works for me on on macOS for the new v0.5.

@bmorris3 the conda forge bot already opened this: https://github.com/conda-forge/astroplan-feedstock/pull/5


tests: replace flake8 checks with ruff

ruff is faster and easier to setup.
Depends-on: #473

The commits in this PR are stacked on top of #473. Once that PR is merged this PR can be rebased.

Thanks! Rebased


FIX: do not mutate the set message

Missed this when fixing the other cases

Tests passed on 3.4 and then Travis hung. Connection problems plagued 3.5.


Adds 'V' attributes

Description
Provides "V" attributes for css-builder
Fixes #32
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Verified that added/modified attribues are properly loading on browsing
[x] Verified that added/modified attribues editing templates are properly rendered
[x] Verified the output on changes
[x] Verified the deployment

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas. If applicable.
[x] I have made corresponding changes to the documentation. If applicable.
[x] My changes generate no new warnings

Hi @eemike07 , could you please resolve the conflicts?

Hi @eemike07 , could you please resolve the conflicts?

I can but currently out of town - won't have access to PC until Monday.  I'll push it on Monday


Globalnet Healthcheck support

Currently, Globalnet only supports Pod to remoteService connectivity.
Submariner healthcheck uses ping/icmp to verify the tunnel status to
remoteClusters. In this PR, Globalnet is enhanced to support ping to
the globalIP allocated to the GatewayNodes, so that health-check can
be performed even for Globalnet deployments.
In a subsequent PR, endpoint info will be updated to use globalIPs as
health-check IPs.
Depends On: https://github.com/submariner-io/submariner-operator/pull/1015
Related to: https://github.com/submariner-io/submariner/issues/970
Signed-Off-by: Sridhar Gaddam<EMAIL_ADDRESS>

Marked this PR as draft because it depends on the Operator/Submariner-Charts PRs to be merged.
https://github.com/submariner-io/submariner-operator/pull/1015
https://github.com/submariner-io/submariner-charts/pull/103
Otherwise, the PR is good for review. I manually applied the required changes in my local repo and verified this PR.

Just for info: All Globalnet jobs will fail until the dependent PRs are merged.

[cluster3] Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(DaemonSet.spec.template.spec.containers[0].env[3]): unknown field "fieldRef" in io.k8s.api.core.v1.EnvVar

means the chart PR was broken :-(.

means the chart PR was broken :-(.

This should fix it - https://github.com/submariner-io/submariner-charts/pull/104

@sridhargaddam can you please update the "known issues" docs: https://submariner.io/operations/known-issues/#globalnet

@sridhargaddam can you please update the "known issues" docs: https://submariner.io/operations/known-issues/#globalnet

@sridhargaddam can you please update the "known issues" docs: https://submariner.io/operations/known-issues/#globalnet

Sure @nyechiel. Once the PR https://github.com/submariner-io/submariner/pull/1069 gets merged, I'll update the website. Thanks.

@sridhargaddam can you please update the "known issues" docs: https://submariner.io/operations/known-issues/#globalnet

Sure @nyechiel. Once the PR https://github.com/submariner-io/submariner/pull/1069 gets merged, I'll update the website. Thanks.


Reboot / Shutdown, standardised

This PR enables the power off and reboot buttons in the settings page, in normal mode.
We could already power off and reboot from recovery mode.
This PR adds

youSure helper function, that produces an x-confirmation-prompt
instruction helper function that produces a non-closable dialog.

Prompts look like:

Instructions look like:

Changed merge target to main as recovery-fix has been merged.


Create C# code snippets for streams

The redis.io webpage for streams needs the c# example as well. The python equivalent can be used to copy the setup and can be found here
The first line of the file needs to be the ID for the example - # EXAMPLE: stream_tutorial
Each separate section is delimited with a tag that you will need to copy exactly for it to appear in the correct place, ie.
# STEP_START xadd
{code}
# STEP_END

# HIDE_START, # HIDE_END, # REMOVE_START, and # REMOVE_END can be used for debugging and deleting keys. Hide will hide until a user expands the example, remove will only be seen in the source code and will never appear on the webpage.

Examples should live in this folder
@dwdougherty and I will be reviewing and tracking these issues - feel free to tag us with any questions

Done


For pull req

Marton,
I made some changes here to:

Use different genetic codes (so it works on bacteria) [set in config.txt]
Always uses the mitochondrial genetic code for variants on chrM or chrMT (also M or MT)
Dynamically determine the chromosome names so they don't have to be hard-coded [see config.txt]

Thanks very much Steven!
We are now going to look at the changes and get back to you soon!

Hi Steven,
Thank you for your suggestions! We plan to do the following if you are agreeable:
Could you please give us permission to commit to your forked pull request branch so that we can make the modifications?
https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/
Regarding the @codon_usage option you have proposed:

We are very happy to hard-code the use of the mitochondrial code for all genes with chromosome M or MT, while using the standard code for all other genes, as we cannot imagine a situation where a user would want to use the standard code for mitochondrial genes, or vice versa. Thanks very much for drawing our attention to the proper usage of the mitochondrial code!

Usage of the 3 letter amino acid code in the p. portion of the annotation is a mandatory requirement of CSN, so unfortunately we cannot allow this flexibility to be added to the CAVA codebase. Of note, if you would like to use the 1 letter amino acid code, this is now possible (though more indirect) in version 1.2.0 of CAVA using the new PROTREF and PROTALT fields.

As you know there are complexities around bacterial codes and it is not an area that we have personal expertise in. We therefore don’t feel comfortable with adding this feature to the codebase at this time, but are of course happy for you to continue using your implementation in your personal version of CAVA. We are seeking additional input and will keep in contact with you about this.

With the above changes we think a @codon_usage option is not currently required.
For future reference, if you are introducing a new flag in the config file, please use the Options class in core.py. The constructor of the Options class is the place to define all configuration option flags. You can define a new flag by simply adding a new key to the self.defs dictionary:
self.defs['flagname'] = (type, defaultvalue)
Note that type can either be 'string' or 'boolean'.
This will create a new flag called @flagname with the specified default value.
For example, the @chrom flag you introduced in the config file can be defined this way:
self.defs['chrom'] = ('string', '1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,18,20,21,22,X,Y,MT')
The Options class will do all the parsing, so you don't need to open and parse the config file every time you need to access an option. You can simply access the value of your config option by:
options.args['chrom']
Note that options is an instance of Options and is initialized at the beginning of running CAVA. See the line:
options = Options(copts.conf)
This reads the configuration file into the options object.
Since the options object is accessible in the constructor of the SingleJob class, all we need for creating self.chroms is the following line:
self.chroms = options.args['chrom'].strip().split(',')
Therefore the parsing of the config file can be removed from the constructor of SingleJob.
Thanks a lot!

Unfortunately, I already have a use case that is using CAVA for tuberculosis annotations - so I need to leave that one in there.  For more information, I used the bacterial code here.
You should have write access to this pull request already (I have the box checked).  Can you verify?
Thanks

Hi Steven. I can confirm that I have write access to this pull request as I have now successfully pushed a commit to your forPullReq branch. The changes should automatically appear in the GitHub pull request code. I'm going to accept the pull request now and merge it into our develop branch. Thanks very much!


DynamicPlayerTextDrawSetString: An item with this ID (0) could not be found.

Pls help

You need to share your game mode for me to fix the issue.

Dc id

@nexquery

benburakya

a.gfx


dotnet deb install failed

Just tried to use your utility.
dotnet tool install --global dotnet-deb command was successful.
But now  I am stuck at:
C:\GIT\ProjectFolder>dotnet deb install
Unhandled exception. System.InvalidOperationException: No instances of MSBuild could be detected.
Try calling RegisterInstance or RegisterMSBuildPath to manually register one.
at Microsoft.Build.Locator.MSBuildLocator.RegisterDefaults()
at Dotnet.Packaging.PackagingRunner..ctor(String outputName, String msbuildTarget, String commandName) in /__w/1/s/dotnet-rpm/PackagingRunner.cs:line 29
at Dotnet.Packaging.Program.Main(String[] args) in /__w/1/s/dotnet-deb/Program.cs:line 9
I tried to figure out what's happenning but failed.
Defintely I have both Microsoft Visual Studio 2022 with MSBuild installed.
Could anyone help me wth this issue?   Thanks!

I made some additional investigation and found, that .NET SDK 6.0 should be installed as a separate installation to use this package. Visual Studio installation isn't sufficient (ir maybe I missed some additional component).
I suggest that it should be explicitely noted in readme/manual.

Hello, I have also encountered this issue. Have you solved it? thank you

I can confirm that Visual Studio 2019 with separately installed .NET SDK 6.0 can work with dotnet-packaging (old Windows & Visual Studio versions are not barriers to work on .NET 6 apps). How about Win10/11 & default installation of VS2022 I'm don't know at this moment.

I can confirm that Visual Studio 2019 with separately installed .NET SDK 6.0 can work with dotnet-packaging (old Windows & Visual Studio versions are not barriers to work on .NET 6 apps) without problems. How about Win10/11 & default installation of VS2022 I'm don't know at this moment.

The same on VS2022.

Hello, I have also encountered this issue. Have you solved it? thank you

Have you solved it? Same situation，Same error


Add RGB LCD display support

Add support for "raw" rgb lcd displays (no frame buffer, and hsync/vsync requirements)

Initial support added in b298d4b7dd9d089a133cf46628c810a0bb4d4b54


IIS hanging on app pool recycle in version React.NET 3.X

I am consistently seeing an issue where anything that causes IIS to recycle the app pool after an initial load is resulting in no response. The only way to recover it is by killing the IIS worker process. I have only found one other person experiencing this issue via a bug filed at ClearScript's project page: https://clearscript.codeplex.com/workitem/119
I downgraded back to React.NET 2.5 and more importantly the previous version of JSEnginerSwitcher (1.5.X) and the issue is gone. I don't really think this has anything to do with React.NET directly, but I wanted to file this issue so other people experiencing this issue after upgrade to 3.X have a place to start.

Having the same problem. Anyone found a solution for this yet?

The bug I linked to was closed as fixed. Upgrading to JavaScriptEnginerSwitcher 2.4.X seems to have resolved the issue, though I still get more IIS crashing than I used to. It is not hanging anymore though, so it may be an unrelated memory issue. I'm closing this, since it has bee fixed.

I haven't got a single crash since I downgraded. It does not sound like a great fix if it still hangs...

Well, previously I was getting a hang that required me to kill IIS express worker process manually using task manager. That isn't happening anymore. Just occasional (1/20?) IIS crashes during development work.

Hmmm...  I guess it's an issue with newer JavaScriptEngineSwitcher versions. I'm not too sure though.


Remove duplicate servlet that was not needed.

We had 2 copies of the Jersey Application starting up, this was so that one could have basic auth in front of it.
Also removed commented out sections and added a few comments.

This is just the kind of thing that automated tests are really useful for - you just remove the code, run your tests and can be pretty confident that you haven't broken anything, rather than looking through the code and thinking you might have missed something. It's still good to look through the code through!


Fixes detection of AppVeyor

Simple change to fix detection of AppVeyor on Linux.

Fixed the test, but I don’t think these tests are passing for anyone right now

@blueyed as a fellow Appveyor user, can I ask you to review that this won't break anything?

Fixes #125


DscResource.LocalizationHelper Module is misnamed

Having the Exception helper functions in the DscResource.LocalizationHelper module is misleading. These functions are not related to localization (and can be used without). I don't think users would expect to find exception functions in there.
I think this module should be renamed to something more generalized such as 'DscResource.ResourceHelper'.
This also relates to this issue: https://github.com/PowerShell/DscResources/issues/476
Another alternative would be to move the exception functions into DscResource.Common.

We could just move all the functions to DscResource.Common instead. Only draw back is that loading localization strings for the Common module needs to be done right after the Get-LocalizedData function is defined.
The names DscResource.ResourceHelper and DscResource.Common is the same thing. How should contributors know what would go where? Better to just have one DscResource.Common?

I did consider that option, but wasn't sure it was a good idea because of the problem you mention.
I too have the exact same thoughts as you - there seems to be two places to put generic shared functions and it doesn't make a whole lot of sense.
I'd much prefer to have a single 'DscResource.Common'.
Any other options? @gaelcolas ?

Actually, just ran into an issue with the Common Tests - Validate Localization that relates to this. Because the DSCResource.LocalizationHelper itself does not have an en-US folder it actually fails these tests: https://ci.appveyor.com/project/PlagueHO/iscsidsc/builds/24298674#L529
I'm going to work around this in the resources I maintain by combining the all the common modules into the DscResource.Common module, but we probably need to come up with a solution to this over in DSCResources.Tests as well (I'll raise the issue over there too).

Because the DSCResource.LocalizationHelper itself does not have an en-US folder it actually fails these tests

Yes, a string resource file with no keys is the minimum that is required. I didn't want to override (filter out) that in the DscResource.Test. Until there was a better solution I thought the best override was to add a string resource file with no keys.

we probably need to come up with a solution to this over in DSCResources.Tests as well

I think the solution we discuss here will see if we need to make changes to DscResource.Tests.

That is what I did. But I actually think in the case of DscResource.Localization it is just better to merge it to Common (which is what I'm starting to do).

Sounds good. Let's do that.

Ok. I'll submit a PR.


Adding ArcAssay/ArcStudy API

Hit >300 unit tests 🎉 ✅
JS tests not yet run ❌

@HLWeil please have a look!

Renamed "Set" CRUD api functions to "Updated"; SetColumn --> UpdateColumn
Renamed UpdateTableAt functions on ArcAssay and ArcStudy to MapTableAt
member this.MapTableAt(index: int, updateFun: ArcTable -> unit) = ArcTables(this.Tables).MapTableAt(index, updateFun)

Great work!
I will merge this, so I can start using these functions in the FsSpreadsheet IO. If we decide on additional changes feel free to open up a new PR.


Run the full test suite on 32-bit platforms

This commit switches to running the full test suite in its entirety (./ci/run-tests.sh) on 32-bit platforms in CI in addition to 64-bit platforms. This notably adds i686 and armv7 as architectures that are tested in CI.
Lots of little fixes here and there were applied to a number of tests. Many tests just don't run on 32-bit platforms or a platform without Cranelift support, and they've been annotated as such where necessary. Other tests were adjusted to run on all platforms a few minor bug fixes are here as well.

Ok I've been thinking about how to clean this up. For the tests that @cfallin flagged I added logic to them all to check cranelift_native::builder() and see whether that's an error. That indicates whether the native platform is supported by Cranelift and tests will early-return if that's an error.
@fitzgen for your points though I'm not sure how to make it better. I'll note that the cargo:rustc-cfg in the build script is not enabling the pulley feature, it's just affecting the --cfg flags to the compiler. Accurately reflecting Cranelift's supported architecture would mean having:
[target.'cfg(not(any(target_arch = "x86_64", target_arch = "aarch64", target_arch = "s390x", target_arch = "riscv64")))'.dependencies]
pulley-interpreter = { workspace = true }

And then reflecting that same condition into build.rs
This feels "zoomed out" enough to me that leaving target_pointer_width = "32" as a proxy there for now is probably sufficient, but I want to confirm with you and/or see if you know of a way to simplify this.

That cfg is certainly annoying but seems like it is probably better than baking in new assumptions that we know are unlikely to be true for too long?

To clarify though the precise assumption here is that 32-bit platforms don't have a Cranelift backend so pulley is pulled in as a dependency. This doesn't actually change any logic internally within Cranelift or Wasmtime, it just compiles in Pulley by default without a way to turn that off. That's only a problem with respect to binary size.
If all of Cranelift's currently supported architectures are listed out here then that's duplicated in two places in Wasmtime (not counting the ones in Cranelift) and they're just going to get blindly added to in the future. Alternatively if Cranelift gets a 32-bit backend then that would be added as an exception to the cfg as-is when binary size becomes a problem.
To me this is six-to-one-half-dozen-or-the-other where I have a preference for what's as-is as it's a managable cfg that's by-default workable for most platforms (it doesn't work for 64-bit platforms without a Cranelift backend). Listing out architectures individually feels "just as bad" to me basically.
The main alternative to me is that we leave pulley disabled by default on all platforms, regardless of Cranelift support. That feels like a worse experience to me though because it means that Wasmtime only works by default on Cranelift-supported platforms, which if someone's new to Wasmtime they might not understand to enable the Pulley backend.

ping @fitzgen on ^


Race when reading messages using Sender + Receiver pair

We are using mio + tokio-core + futures + futures-cpupool to implement some network protocol (basically - sending and responding to messages).
To read incoming messages, we use simple future, based on tokio_core::io::read_exact - first we read message header, then - message payload.
We spawn this future on CpuPool && on event loop (tokio_core::reactor::Core). After reading header + payload is completed => future is spawned again.
This works for some time, but eventually our futures stop spawning on event loop => no messages are read from network.
I've invested some time trying to understand - what's going on there && here are my thoughts:

we are spawning our future on event loop using tokio_core::reactor::Remote handle
Remote::spawn function sends message to the 'event loop thread' using tokio_core::reactor::channel::Sender:
https://github.com/tokio-rs/tokio-core/blob/master/src/reactor/mod.rs#L578
https://github.com/tokio-rs/tokio-core/blob/master/src/reactor/channel.rs#L47
sender uses custom lock-free Queue to store messages:
https://github.com/tokio-rs/tokio-core/blob/master/src/mpsc_queue.rs
and pair of mio::channel::{SenderCtl, ReceiverCtl} for signalling that queue is not-empty:
https://github.com/carllerche/mio/blob/master/src/channel.rs
when message is sent, it is pushed to the queue, and then SenderCtl::inc is called:
https://github.com/carllerche/mio/blob/master/src/channel.rs#L196
inc method first checks if number of pending messages is 0 && then calls set_readingess(Ready) to awake the Poll.
This is important, because when second message is sent via the same Sender/Receiver pair, readiness is not set again.
when Poll receives notification that message is ready, control is transferred back to tokio_core::reactor::Core:
https://github.com/tokio-rs/tokio-core/blob/master/src/reactor/mod.rs#L282
and it starts processing incoming messages queue:
https://github.com/tokio-rs/tokio-core/blob/master/src/reactor/mod.rs#L385
here's second important part - Receiver::recv method:
https://github.com/tokio-rs/tokio-core/blob/master/src/reactor/channel.rs#L55
here you can see that in case when Queue::pop returns PopResult::Inconsistent, recv returns None && no messages are processed (Core::consume_queue stops processing messages).
Please bear in mind that mio::ReceiverCtl::dec is called only when item is 'popped' out of Queue:
https://github.com/tokio-rs/tokio-core/blob/master/src/reactor/channel.rs#L62
So if queue was in inconsistent state during pop, then SenderCtl.inner.pending is not decreased => next time message is sent using Sender::send, message won't be read, because receiver is notified only when first message is sent (see (4) above).

What has fixed this issue for our project is removal of 'if 0 == cnt' condition here:
https://github.com/carllerche/mio/blob/master/src/channel.rs#L198
So that readiness flag is set even when message is not the first one in the queue. But:

as I understand this can lead to spurious wakeups of Poll (because the whole queue can be read on previous wakeup)
the problem is not with the SenderCtl+ReceiverCtl pair itself, but with ther usage along with lock-free Queue in tokio-core
So maybe this should be fixed in some other way, but if you think this fix is OK - I can try to create PR in mio repository.

Thanks for the detailed report @svyatonik! Out of curiosity, do you have a reproduction for this failure? (sporadically failing is fine). I'd love to check in a unit test and explore this further.
I haven't heavily scrutinized the ctl bits from mio yet but this reminds me that I've been intending to rip out reactor::channel in favor of the channels in the futures crate itself. I did that in https://github.com/alexcrichton/tokio-core/commit/2caad85d44c7a52bf470018ea98fe8b61c13059c, and could you test that out to see if it fixes your problems?

@alexcrichton Not yet, unfortunately - will try to make a small test for this a bit later && check your branch.

Repository with small utility which you can use as a basis for unit test:
https://github.com/svyatonik/tokio_core_race
I've also changed mio && tokio-core source a bit, just to illustrate what's going when meeting the race, but haven't committed my changes - these are described in readme.md

About testing with your branch - I have a problems with compiling our project after switching to your code:
    |      ^^^^^^^^ the trait `std::marker::Sync` is not implemented for `std::cell::RefCell<futures::sync::mpsc::UnboundedSender<tokio_core::reactor::Message>>`
    |
    = note: `std::cell::RefCell<futures::sync::mpsc::UnboundedSender<tokio_core::reactor::Message>>` cannot be shared between threads safely
    = note: required because it appears within the type `tokio_core::reactor::Remote`

So maybe this should be fixed in your branch somehow (as I understand, Remote is now not Sync)? Or should we change our code to make Remote usable again?

Oh yeah that's a property of Remote which I lost on that temporary branch, and we definitely want to keep Remote as Sync. I'll work on updating that.

@svyatonik ok want to test out this commit? https://github.com/alexcrichton/tokio-core/commit/5979a6d59d5a20b7517a6c7b96a87eee9ce0696b

@alexcrichton tested this commit. And I have two news:

positive - looks like race issue is fixed;
not-so-positive - mio poll now returns instantly here:
https://github.com/alexcrichton/tokio-core/commit/5979a6d59d5a20b7517a6c7b96a87eee9ce0696b#diff-245f7d251f7503191c63a5d19b4aae18R263
When starting with RUST_LOG=trace, I can see that when app is running, poll returns ~20000-22000 times per second, thus consuming the whole single CPU. So app is working very slow && I can't be 100% sure that race is gone (but I suppose so, as previously it was because this thread was sleeping when it shouldn't && now it never sleeps). Some stats:

svyatonik@xwnotebook:~/dev/myapp.test/myapp$ grep -rn "loop time - Instant { tv_sec: 238513" start_trace.log | wc -l
20266
svyatonik@xwnotebook:~/dev/myapp.test/myapp$ grep -rn "loop time - Instant { tv_sec: 238512" start_trace.log | wc -l
21870

During most of wakeups, this queue is empty (checked with trace in Async::Ready branch):
https://github.com/alexcrichton/tokio-core/commit/5979a6d59d5a20b7517a6c7b96a87eee9ce0696b#diff-245f7d251f7503191c63a5d19b4aae18R391
So I think that maybe rx_readiness is never reset? However, I do not know in details, how mpsc channel from futures-rs works, but it looks so that it constantly Ready(Read).

Oops, indeed! How about https://github.com/alexcrichton/tokio-core/commit/5979a6d59d5a20b7517a6c7b96a87eee9ce0696b?

Er, I mean https://github.com/alexcrichton/tokio-core/commit/ed9037a73c10fb3521d1b0599e13994de5eb8fb0

@alexcrichton checked - looks like it works now :1st_place_medal: Thank you very much! :)

Awesome, thanks for testing @svyatonik!


BaseFilterSet not using multiple choice filters for CharFields with choices

Environment

Nautobot version (Docker tag too if applicable): 2.0.0a1
Python version: 3.10
Database platform, version:
Middleware(s):

Steps to Reproduce

from nbshell inspect the filter for Interface.mode:

from nautobot.dcim.filters import InterfaceFilterSet
InterfaceFilterSet.get_filters().get("mode")
# returns <django_filters.filters.ChoiceFilter object at 0x7ff8f8a57e80>

Expected Behavior
This should be a MultipleChoiceFilter

Observed Behavior
The filter is being set to ChoiceFilter

In the same family as #1889 and #1483

Issues like cause PRs like this: https://github.com/nautobot/nautobot/pull/2754#issuecomment-1311199557 when trying to adhere to standards defined here: https://github.com/nautobot/nautobot/issues/1606

Closed via #3342


Make textarea component

Issue #100 Extract textarea from index file and make own component in styled folder

Looks mostly good for me. We need to change the imports/exports of types and then we can merge this Pull Request :)

Sure, my linter was complaining like crazy about the exports so I removed them while I was working on it and forgot to add them back in. Will fix it then let you know when it’s done

I added back in the imports/exports so this should be ready to go.

@all-contributors please add @emmalearnscode for code


Select All Sites should be a button

There's a checkbox called "Select All Sites" under Chart Options, but it seems like this should be a button instead. This is because it's a single operation the user would like to perform rather than a setting. Also, the box doesn't seem to check itself when all residues are selected manually (not to say that this would be better).
This issue is part of https://github.com/openjournals/joss-reviews/issues/6129

Good point. I turned it into a button!
#77


wxGTK32: 3.2.3 -> 3.2.4

Description of changes
https://github.com/wxWidgets/wxWidgets/releases/tag/v3.2.4
https://github.com/wxWidgets/wxWidgets/compare/v3.2.3...v3.2.4
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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

[x] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[x] (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
1 package marked as broken and skipped:
springLobby

9 packages failed to build:
audacity displaycal displaycal.dist erlang-ls klipper-firmware klipper-flash slade sladeUnstable tenacity

195 packages built:
abracadabra aegisub akkoma amule amule-daemon amule-gui amule-web asc bochs boinc bossa bossa-arduino cemu chirp chirp.dist cl codeblocks codeblocksFull comical couchdb3 cqrlog cubicsdr diff-pdf digikam dump1090 dvdstyler easyabc ejabberd electricsheep elixir elixir-ls elixir_1_10 elixir_1_11 elixir_1_12 elixir_1_13 elixir_1_14 elvis-erlang erlang erlang_24 erlang_26 erlang_javac erlang_odbc erlang_odbc_javac erlfmt espanso espanso-wayland espeakedit far2l filezilla fityk flamerobin freedv freefilesync freqtweak fsg gnudatalanguage gnuradio3_8Packages.ais gnuradio3_8Packages.limesdr gnuradio3_8Packages.osmosdr gnuradio3_8Packages.osmosdr.dev gnuradio3_9Packages.osmosdr gnuradio3_9Packages.osmosdr.dev gnuradioPackages.osmosdr gnuradioPackages.osmosdr.dev golly gqrx gqrx-gr-audio gqrx-portaudio grandorgue grass hugin indi-full kicad kicad-small kicad-unstable kicad-unstable-small kstars lenmus lfe limesuite livebook loxodo loxodo.dist mavproxy mavproxy.dist mediainfo-gui meerk40t meerk40t.dist megaglest mercury metamorphose2 mix2nix mmex mobilizon mymcplus mymcplus.dist notmuch-bower odamex opencpn openwebrx openwebrx.dist pcem perl536Packages.AlienWxWidgets perl536Packages.AlienWxWidgets.devdoc perl536Packages.AppMusicChordPro perl536Packages.AppMusicChordPro.devdoc perl536Packages.Wx perl536Packages.Wx.devdoc perl536Packages.WxGLCanvas perl536Packages.WxGLCanvas.devdoc perl538Packages.AlienWxWidgets perl538Packages.AlienWxWidgets.devdoc perl538Packages.AppMusicChordPro perl538Packages.AppMusicChordPro.devdoc perl538Packages.Wx perl538Packages.Wx.devdoc perl538Packages.WxGLCanvas perl538Packages.WxGLCanvas.devdoc phd2 plausible playonlinux pleroma poedit pothos printrun printrun.dist pwsafe python310Packages.humblewx python310Packages.humblewx.dist python310Packages.kicad python310Packages.soapysdr-with-plugins python310Packages.wxPython_4_2 python311Packages.humblewx python311Packages.humblewx.dist python311Packages.kicad python311Packages.soapysdr-with-plugins python311Packages.wxPython_4_2 qgis qgis-ltr qradiolink quisk quisk.dist rabbitmq-server rabbitmq-server.doc rabbitmq-server.man radiotray-ng rapidsvn rebar rebar3 rehex rtl_433 saga scorched3d sdrangel sigdigger slic3r soapysdr-with-plugins sonic-pi sooperlooper sound-of-sorting spatialite_gui spek srsran survex suscan therion timeline tqsl treesheets tsung tunnelx urbackup-client urh urh.dist vbam veracrypt welle-io wings woeusb-ng woeusb-ng.dist wxGTK32 wxSVG wxformbuilder wxhexeditor wxmacmolplt wxmaxima wxsqlite3 wxsqliteplus xchm xmlcopyeditor xylib yaws zeroad zeroadPackages.zeroad-unwrapped zod

kicad seems to work with this update, but
pinging maintainers of packages broken by this change:
audacity: @lheckemann @veprbl @wegank (note: nix-update to 3.4.1 didn't fix it)
erlang-ls: none available, @dlesl authored and erlang maintainer @happysalada seems involved (note: doesn't fail on my branch based on nixos-unstable)
slade: @ertes
tenacity: @IreneKnapp @lheckemann
displaycal and klipper-firmware currently fail on master anyway
but pinging their maintainers to make sure they're aware of that:
displaycal: @toastal
klipper-firmware: @vtuan10 (note: updating to 0.12.0 didn't fix it)

Thanks, I'm taking a look at the tenacity issue. According to wxGTK upstream this shouldn't be a breaking change, so perhaps tenacity's build system has something hardcoded.

https://github.com/wxWidgets/wxWidgets/commit/425d9455e8307c1267a79d47d77e3dafeb4d86de must be reverted for Audacity to build. Something like this should work:
diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index e120ee67b902..be39c88bbea6 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -30467,6 +30467,16 @@ with pkgs;

   audacity = callPackage ../applications/audio/audacity {
     inherit (darwin.apple_sdk.frameworks) AppKit CoreAudioKit;
+    wxGTK32 = wxGTK32.overrideAttrs {
+      patches = [
+        (fetchpatch {
+          url = "https://github.com/wxWidgets/wxWidgets/commit/425d9455e8307c1267a79d47d77e3dafeb4d86de.patch";
+          excludes = [ "docs/changes.txt" ];
+          revert = true;
+          hash = "sha256-6LOYLDLtVCHxNdHAWv3zhlCsljIpi//RJb9XVLGD5hM=";
+        })
+      ];
+    };
   };

   audio-recorder = callPackage ../applications/audio/audio-recorder { };

in the case of Tenacity, the problem is caused by wxGTK having implemented initializer_list support for wxArrayString. this caused a few bits of code that were written on the assumption it didn't exist to misbehave.
I have prepared a two-line patch to the Tenacity code. I am happy to add that patch to the nix Tenacity package, and to drive the process of getting it upstreamed. Fortunately, it's a backwards-compatible fix, so there's nothing stopping it from being applied either before or after the wxGTK update.
This is my first time getting a notification about breakage in one of my packages. What's the procedure here, do you want to add my changes to your PR or should they be their own?

i opened this PR as a draft because we're in ZHF and this introduces failures
which i guess means my intend is to have this merged after the 23.11 branch-off (in 8 days)
unless all the breakages can be fixed and the changes reviewed before then

What's the procedure here, do you want to add my changes to your PR or should they be their own?

i don't think there's a set procedure
if you were to open a separate PR i'd probably add your change to this PR and mark this one as closing yours
so a separate PR is probably only useful if you want to separate discussion of the tenacity/audacity failure from the slade and erlang-ls one

Thanks for notifying!
With the updated config for klipper-firmware (https://github.com/NixOS/nixpkgs/pull/267070) it should build again. I also tested it with wxGTK 3.2.4 and it builds fine as well.

Hello everyone!
This issue has already been fixed in Tenacity. We will be releasing 1.3.3 soon that will contain a fix.

oh how lovely, thanks @generic-pers0n ! it sounds like the timeframe works out such that we can just wait for that
here's my changes, in case they're useful just in moving up the timeline or anything like that. I don't think they're particularly idiomatic, I only ever intended them to be temporary
diff --git a/src/Tags.cpp b/src/Tags.cpp
index 50c940bcd..1833307fe 100644
--- a/src/Tags.cpp
+++ b/src/Tags.cpp
@@ -631,7 +631,7 @@ class ComboEditor final : public wxGridCellChoiceEditor
public:
ComboEditor(const wxArrayString& choices, bool allowOthers = false)
:  wxGridCellChoiceEditor(choices, allowOthers)

,  m_choices{ choices }

,  m_choices(choices)
,  m_allowOthers{ allowOthers }
{
}
diff --git a/src/prefs/GUIPrefs.cpp b/src/prefs/GUIPrefs.cpp
index 1e6a93e56..36a73ee3b 100644
--- a/src/prefs/GUIPrefs.cpp
+++ b/src/prefs/GUIPrefs.cpp
@@ -80,7 +80,7 @@ void GUIPrefs::GetRangeChoices(
wxT("145") ,
};
if (pCodes)

 *pCodes = sCodes;

 *pCodes = static_cast<const wxArrayStringEx&>(sCodes);

static const std::initializer_list sChoices = {
XO("-36 dB (shallow range for high-amplitude editing)") ,
--

@IreneKnapp I created a small PR here: https://codeberg.org/tenacityteam/tenacity/pulls/325. If you approve, I'll merge it ASAP.

@06kellyjac just so you know, there's discussion over on https://github.com/wxWidgets/wxWidgets/pull/23309 of making sure to announce this kind of thing in advance going forward, so it can be tested. since you're the maintainer for the nix wxGTK package I thought you might want to be involved.
(if you got @'d for this twice, sorry, I have a bunch of PRs open in tabs and got the wrong one...)

no double ping, though the email i got had a different name tagged there
i'm not actually the wxGTK package maintainer, but the KiCad package maintainer
and there's been a bunch of stuff happening with wxWidgets and KiCad related to wayland support, so i updated this to keep an eye on that

Tenacity 1.3.3 has just been released with improved compatibility with wxWidgets 3.2.4.

Thanks for the heads up, erlang-ls built fine, just tested it on linux-x86_64. So all good on that this.

added wegank's workaround to audacity and slade (thanks!)
waiting for nixpkgs-review to finish before undrafting this

with #267070 it's down to just diplaycal, which is also a preexisting failure
1 package marked as broken and skipped:
springLobby

2 packages failed to build:
displaycal displaycal.dist

203 packages built:
abracadabra aegisub akkoma amule amule-daemon amule-gui amule-web asc audacity bochs boinc bossa bossa-arduino cemu chirp chirp.dist cl codeblocks codeblocksFull comical couchdb3 cqrlog cubicsdr diff-pdf digikam dump1090 dvdstyler easyabc ejabberd electricsheep elixir elixir-ls elixir_1_10 elixir_1_11 elixir_1_12 elixir_1_13 elixir_1_14 elvis-erlang erlang erlang-ls erlang_24 erlang_26 erlang_javac erlang_odbc erlang_odbc_javac erlfmt espanso espanso-wayland espeakedit far2l filezilla fityk flamerobin freedv freefilesync freqtweak fsg gnudatalanguage gnuradio3_8Packages.ais gnuradio3_8Packages.limesdr gnuradio3_8Packages.osmosdr gnuradio3_8Packages.osmosdr.dev gnuradio3_9Packages.osmosdr gnuradio3_9Packages.osmosdr.dev gnuradioPackages.osmosdr gnuradioPackages.osmosdr.dev golly gqrx gqrx-gr-audio gqrx-portaudio grandorgue grass hugin indi-full kicad kicad-small kicad-unstable kicad-unstable-small klipper-firmware klipper-flash kstars lenmus lfe limesuite livebook loxodo loxodo.dist mavproxy mavproxy.dist mediainfo-gui meerk40t meerk40t.dist megaglest mercury metamorphose2 mix2nix mmex mobilizon mymcplus mymcplus.dist notmuch-bower odamex opencpn openwebrx openwebrx.dist pcem perl536Packages.AlienWxWidgets perl536Packages.AlienWxWidgets.devdoc perl536Packages.AppMusicChordPro perl536Packages.AppMusicChordPro.devdoc perl536Packages.Wx perl536Packages.Wx.devdoc perl536Packages.WxGLCanvas perl536Packages.WxGLCanvas.devdoc perl538Packages.AlienWxWidgets perl538Packages.AlienWxWidgets.devdoc perl538Packages.AppMusicChordPro perl538Packages.AppMusicChordPro.devdoc perl538Packages.Wx perl538Packages.Wx.devdoc perl538Packages.WxGLCanvas perl538Packages.WxGLCanvas.devdoc phd2 plausible playonlinux pleroma poedit pothos printrun printrun.dist pterm pwsafe python310Packages.humblewx python310Packages.humblewx.dist python310Packages.kicad python310Packages.soapysdr-with-plugins python310Packages.wxPython_4_2 python311Packages.humblewx python311Packages.humblewx.dist python311Packages.kicad python311Packages.soapysdr-with-plugins python311Packages.wxPython_4_2 qgis qgis-ltr qradiolink quisk quisk.dist rabbitmq-server rabbitmq-server.doc rabbitmq-server.man radiotray-ng rapidsvn rebar rebar3 rehex rtl_433 saga scorched3d sdrangel sigdigger slade sladeUnstable slic3r soapysdr-with-plugins sonic-pi sooperlooper sound-of-sorting spatialite_gui spek srsran survex suscan tenacity therion timeline tqsl treesheets tsung tunnelx urbackup-client urh urh.dist vbam veracrypt welle-io wings woeusb-ng woeusb-ng.dist wxGTK32 wxSVG wxformbuilder wxhexeditor wxmacmolplt wxmaxima wxsqlite3 wxsqliteplus xchm xmlcopyeditor xylib yaws zeroad zeroadPackages.zeroad-unwrapped zod

ok, i just confirmed this resolves an issue i've been having with kicad-unstable on sway (wayland) where my GPU would double its power usage if i had an EGL canvas window hidden / in a non-visible WM tab
so if anyone wants to review or merge this, please do!


Compiler crash: error: expected: !is_optimizing() || !instr->HasUnmatchedInputRepresentations()

Wanted to use an old library of mine and noticed that it cannot be compiler with any dart version after 2.15.0 (stable).
Repro:
git clone https://github.com/knaeckeKami/barbecue.git
cd barbecue
dart pub get
dart compile exe test/table_border_test.dart

Output:
https://gist.github.com/knaeckeKami/bc202626e87171616e629606d55e9e28 (too long for github)

Dart SDK Version: tested various, any after 2.15.0 will fail. newest tested one: 3.0.0-75.0.dev (dev) (Thu Dec 29 16:50:26 2022 -0800) on "macos_arm64"
OS: MacOS, Arm64

@alexmarkov Could you take a look at this? Seems like rogue unboxing being applied to an already unboxed value. Probably we modified the graph after the last select representation was already performed. Maybe load forwarding or canonicalizer broke the graph?

AllocationSinking_Sink pass propagated load and replaced v1563 with v33:
    v33 <- StaticCall:114<EMAIL_ADDRESS>v26, v32, v5, result_type = T{_List}) T{_List}
    StoreField(v16 . rowHeights = v33)
...
    v1563 <- LoadField:1048(v16 . rowHeights {final}) T{List<int>?}
    v1573 <- LoadField:1048(v1563 . Array.length {final}) [0,<PHONE_NUMBER>03423487] T{_Smi}
    v1792 <- UnboxInt64:1048([non-speculative], v1573) [0,<PHONE_NUMBER>03423487] T{int}

=>
    v1573 <- LoadField:1048(v33 . Array.length {final}) [0,<PHONE_NUMBER>03423487] T{_Smi}
    v1792 <- UnboxInt64:1048([non-speculative], v1573) [0,<PHONE_NUMBER>03423487] T{int}

After that, the next Canonicalize happened only after SelectRepresentations_Final and replaced v1573 with v32 which apparently has a different representation:
    v1792 <- UnboxInt64:1048([non-speculative], v32 T{_Smi}) [0,<PHONE_NUMBER>03423487] T{int}

This made UnboxInt64 instruction incorrect and caused crash during code generation.
There are a few things to fix and improve here:

Canonicalize should not replace a value if it has a different representation and flow_graph->unmatched_representations_allowed() is false. It is set to false after SelectRepresentations_Final.
It could be beneficial to have an additional Canonicalize between AllocationSinking_Sink and SelectRepresentations_Final so it could cleanup the IL before representations are frozen.
Canonicalization of boxing and unboxing instructions can check if their input has a desired representation already and eliminate boxing/unboxing if that's the case.

@alexmarkov the list you have above I presume is recommendatations to make the code more robust, should we file issues to track those?

@a-siva I'm working on the follow-up CL https://dart-review.googlesource.com/c/sdk/+/279274 which would fix items 2 and 3 from the list above. The CL points to this issue, so there's no need to file separate issue(s) for those improvements.


[DOCS] Replace pip to python3 -m pip

Replace pip to python3 -m pip

Why?

Not a bug really, just perfectionism.
Same with pyvenv:
Note The pyvenv script has been deprecated as of Python 3.6 in favor of using python3 -m venv to help prevent any potential confusion as to which Python interpreter a virtual environment will be based on.
https://docs.python.org/3/library/venv.html
All examples from https://docs.python.org/3/installing/index.html#basic-usage follow same scheme.

Change it where exactly?

While python3 -m pip is more precise and removes ambiguity about which python version is used, pip is much shorter to type and makes a better candidate for user facing docs for example. I'd still use python3 -m pip in scripts that can run in multiple environments.
We are moving to a world where py3 is the only supported version given that py2 is end of life 1st January 2020, because of this python version ambiguity is a lot less of an issue going forward.

Thanks everyone for the discussion!
The preference of pip install, python -m pip install, python3 -m pip install, pip3 install, etc, is quite subjective and varies a lot depending on personal/team taste.
So, I prefer to leave the simplest version (pip install), and let everyone chose from that what to use.
That's the same reason why I don't suggest Pipenv, Poetry, venv, etc.
...Also, agree with @purificant 😅

I'll close this now, but feel free to add more comments or create new issues.


Updated question schema

See #8

[x] Multiple correct answers in task_text -> @mp4096
[x] Implement text chunks that are shown only on the results screen -> @mp4096
[ ] Case insensitive comparison for task_text -> @syxolk Can we convert the correct answers to lowercase server-side? Probably in prerender.js.

:dolphin:

Coverage remained the same at 87.85% when pulling 49daea1fcdd0ed4f8ca5504afbd5385d787059be on dev-new-question-schema into f159e6a4e5db59aa2d80b26e77152efd7c2dd27b on master.

Coverage remained the same at 87.963% when pulling ce3299efda4a2c05bae807fedaea7b19b1f55f31 on dev-new-question-schema into 2df444894a57f9d1854a35971d6e7c2c43d2c40d on master.

Coverage remained the same at 87.963% when pulling 11ab7120c6e04234a4453646f1cfeb92e7c8a7d8 on dev-new-question-schema into 2df444894a57f9d1854a35971d6e7c2c43d2c40d on master.

Coverage remained the same at 87.963% when pulling def5f6b4b295157aa166534a060ea43d8e1f7509 on dev-new-question-schema into 2df444894a57f9d1854a35971d6e7c2c43d2c40d on master.

Coverage remained the same at 87.963% when pulling 82768fc85f57b478d8fda504bb038c28d7530d72 on dev-new-question-schema into 55f5274b6a71e42c4d54e112502902655897bfbe on master.

Coverage remained the same at 86.957% when pulling 4dda184c3331ba4efb05af03a4c5d81d2784a2d9 on dev-new-question-schema into 551d5dd9404c29882e5f2182b0bf7f43006832c0 on master.

Coverage remained the same at 86.957% when pulling 4dda184c3331ba4efb05af03a4c5d81d2784a2d9 on dev-new-question-schema into 551d5dd9404c29882e5f2182b0bf7f43006832c0 on master.

Coverage remained the same at 86.957% when pulling 4dda184c3331ba4efb05af03a4c5d81d2784a2d9 on dev-new-question-schema into 551d5dd9404c29882e5f2182b0bf7f43006832c0 on master.

Coverage remained the same at 86.325% when pulling 5857576a1dbb4c450798fc7320c098d07da7416e on dev-new-question-schema into 2fef5e4ad5e7b1af299377117ac7650db9df84c4 on master.

Coverage remained the same at 86.957% when pulling 554b5bc9348ec9f1030bcf7ada9e7a37a8d83138 on dev-new-question-schema into e5a8ba06b2d076cd71a312ce2da8da2ee1eb0931 on master.

Coverage remained the same at 86.957% when pulling c8e8b39786158c8a9133e3f908c908b1881e4132 on dev-new-question-schema into d76866a949629f813352bb71d2c61d303f275017 on master.

Coverage remained the same at 86.957% when pulling 611821de636656aba710c33b7ac84d3b0511f1e5 on dev-new-question-schema into d76866a949629f813352bb71d2c61d303f275017 on master.

Coverage remained the same at 86.957% when pulling 453903df5b3e5cf72a8450518da2d76238acd1b4 on dev-new-question-schema into d76866a949629f813352bb71d2c61d303f275017 on master.


any plan to add preact boilerplates?

Description
No response

Not for now, but contribution welcome to create a vike-preact package.


Update Ollama Version to 0.1.32

Ollama supports OpenAI API since 0.1.24. OpenAI API support is quite important for us. Could we update ollama version in ipex-llm[cpp] package to latest release like 0.1.32? I'm interested in windows platform.

Hi @Quallyjiang, ipex-llm ollama has been updated into v0.1.32.

thanks!


fix Enums toUtf8Bytes errors

What this PR does / why we need it?
一个对象中如果有属性是枚举类型，且枚举值为中文命名，对其进行toJSONBytes序列化时，并不能得到期望的值。测试代码如下所示：
@Test
public void testEnum() {
     Bean bean = new Bean();
     bean.setTestEnum(TestEnum.第二);
     bean.setName("zhangsan");
     byte[] bytes = JSON.toJSONBytes(bean, JSONWriter.Feature.WriteEnumsUsingName);
     System.out.println(new String(bytes, StandardCharsets.UTF_8));
}

@Data
static class Bean {
    private TestEnum testEnum;
    private String name;
}

@SuppressWarnings("all")
enum TestEnum {
    第一,
    第二,
}

期望的结果：{"name":"zhangsan","testEnum":"第二"}
实际的结果：{"name":"zhangsan","testEnum":",�"}
经排查，com.alibaba.fastjson2.writer.FieldWriterEnum中使用了过时的getBytes方法复制bytes导致，此方法并不能真正意义上的对字节数组进行复制
Summary of your change
Please indicate you've done the following:

[ ] Made sure tests are passing and test coverage is added if needed.
[ ] Made sure commit message follow the rule of Conventional Commits specification.
[ ] Considered the docs impact and opened a new docs issue or PR with docs changes if needed.

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


Backports 0.15 pr17

tests currently fail
FAIL: qt/test/test_dash-qt
********* Start testing of WalletTests *********
Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 static release build; by GCC 7.3.0)
PASS   : WalletTests::initTestCase()
QDEBUG : WalletTests::walletTests() TransactionTablePriv::refreshWallet
FAIL!  : WalletTests::walletTests() Compared values are not the same
   Actual   (transactionTableModel->rowCount({})): 101
   Expected (103)                                : 103
   Loc: [qt/test/wallettests.cpp(113)]
PASS   : WalletTests::cleanupTestCase()
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 174ms
********* Finished testing of WalletTests *********

https://github.com/dashpay/dash/pull/3007/commits/e706d060e35edfc62663d0902c2b35a6212f3d60 should've fixed the problems with AvailableCoins

tests passing locally :) let's see what travis thinks

Looks like depends step failed, pls force-push the latest commit again.

tests fail https://travis-ci.org/dashpay/dash/jobs/554917322#L3678

Yep, I don't see why though and can't reproduce it in my branch either (restarted linux32/64 builds on Travis several times already, all green all the time).

As of the logs, the first block is generated before the verack from test_node was processed by node0, which results in no INV being sent to test_node. This should fix it: 45d48a0480c58706173d8bd39e3fd2fa20581496

Cherry-picked


changed the way we cycle through sources. from map to for loop with b…

https://user-images.githubusercontent.com/57504257/129986482-e8734cba-db6c-430f-b93a-745c603d3a51.mov

Codecov Report

Merging #2098 (1a4b1d2) into master (c5237df) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           master    #2098    +/-   ##
========================================
  Coverage   70.58%   70.58%
========================================
  Files         407      407
  Lines        7374     7374
  Branches     1576     1444   -132
========================================
  Hits         5205     5205
- Misses       2143     2145     +2
+ Partials       26       24     -2

Impacted Files
Coverage Δ

src/components/charts/costChart/costChart.tsx
9.37% <0.00%> (ø)

...omponents/charts/dailyCostChart/dailyCostChart.tsx
7.89% <0.00%> (ø)

Continue to review full report at Codecov.

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


[tobiko] install tox version from RPM

Stop installing tox with pip and install tox from an RPM instead.
The tox version installed via RPM is valid for tobiko, since it's higher
than 3.8.
With this change a vulnerability issue affecting the tobiko image is
resolved:
https://github.com/advisories/GHSA-w596-4wvx-j9j6
OSPRH-5225

trying to figure out why I pushed changes to [1], but this PR was not updated...
[1] https://github.com/eduolivares/tcib/tree/tobiko-upgrade-tox

moved to https://github.com/openstack-k8s-operators/tcib/pull/145 because this PR was not updated


Eventhub podidentity

This PR adds support for Pod Identity for Event Hub. Users will be able to use Pod Identity instead of depending on supplying a connection string. But this also means that they have to supply EventHubNamespace and EventHubName explicitly.
Checklist

[ ✅] Commits are signed with Developer Certificate of Origin (DCO)
[ ✅] Tests have been added
[ ✅] A PR is opened to update the documentation on https://github.com/kedacore/keda-docs
[ ✅] Changelog has been updated

Looking good, bug I keep the proper review for someone Azure related.
Let's hold merging this PR open for a while, once we are clear that the next release will be 2.1 and not 2.0.1 or something similar.

@eashi I am very sorry, we have changed the Changelog a little bit, could you please update your PR and add this feature to the Unreleased section, thanks!

@eashi I am very sorry, we have changed the Changelog a little bit, could you please update your PR and add this feature to the Unreleased section, thanks!

No problem, done.


maelstrom: init at 3.0.7

Motivation for this change
Add maelstrom to nixpkgs.
Things done

Built on platform(s)

[X] macOS
[X] other Linux distributions

[X] Tested execution of all binary files (usually in ./result/bin/)
[X ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 114179 at eb62f66a run on aarch64-linux 1

1 package built:

maelstrom

2 suggestions:

warning: missing-patch-comment
Please add a comment on the line above, explaining the purpose of this patch.
Near pkgs/games/maelstrom/default.nix:12:15:
   |
12 |   patches = [ ./fix-compilation.patch ];
   |               ^

warning: unclear-gpl
gpl2 is a deprecated license, check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/games/maelstrom/default.nix:34:5:
   |
34 |     license = licenses.gpl2;
   |     ^


Silent audio

Q
A

Bug?
no

New Feature?
no

Version Used
Specific tag or commit sha

FFmpeg Version
FFmpeg 2.8.15

OS
Centos 7

Hi,
It's possible to add a silent audio track to a video that doesn't have audio track?
I found a way with ffmpeg:
ffmpeg -i video.mp4 -f lavfi -i anullsrc=channel_layout=stereo:sample_rate=44100 -strict -2 -c:v copy -shortest video_with_silent.mp4
Could you help me with that please?

+1


[PREVIEW] Remove "window.rollexIntervals"

Fixes #19

The performance on low-end mobile devices is terrible. Tested on iPhone 4S with just 11 counters on a single page (5 static, 5 animated, 1 frozen). We'll need to find what's causing this.
tick() might perform too slow, and setInterval just keeps calling it again and again, even if it did not execute yet. This might completely freeze the tab on low-end devices.
Also, the instant zero reset hack is not working on iPhone 4. Did not test it on a single counter though, so it might just be because of overall poor performance.

The performance on low-end mobile devices is terrible. Tested on iPhone 4S with just 11 counters on a single page (5 static, 5 animated, 1 frozen). We'll need to find what's causing this.

have you checked it with different easing functions?

have you checked it with different easing functions?

Yes. But it seems that it's the easing duration, not function, that matters the most. If easing duration is bigger, the timer is more prone to glitching.

The performance problem described above is a separate issue. I haven't yet managed to find the source of it. We'll need some more elaborate testing to fix it.


Fix tabs style conflict with bootstrap

By default, tab contents not visible due to conflict with bootstrap styles.

Fixed and tested.


Fix handling of dirty flag

Document is started out as dirty.
Reverting is not clearing the dirty flag.

This was a problem in jupyter-js-notebook, solved in https://github.com/jupyter/jupyter-js-notebook/pull/66.


fix: update to eye v3.17.1

fix: update to eye v3.17.1

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

npm package (@latest dist-tag)
GitHub release
v4.16.1

Your semantic-release bot :package::rocket:


update sample links

Fixes #4821
All links to samples have moved to a new "dotnet/samples" repo.

@BillWagner it seems that this PR was also touching one of the api files. can you rebase to fix the conflict? The api folder is now gone from master.

Thanks Ron. I also did a global search for blob/master/sample and found a few more that needed to be fixed.


Resolve TODO in Dockerfile

Proposed changes
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request.
If it fixes a bug or resolves a feature request, be sure to link to
that issue.
Types of changes
What types of changes does your code introduce to the project?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Maintenance (update of libraries or other dependences)

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

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have run all the existing tests locally (not just those related to my feature) and there are no errors
[x] After the last push to the PR branch, I have run the lint script locally and there are no changes to the code base
[x] I have updated the RELEASE NOTES
[x] I have added necessary documentation (if appropriate)
[x] Any dependent changes have been merged and published in downstream modules

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

#680

@NEC-Vishal thanks for this! If you could please rebase on master so we can merge your change. Thanks alot!

Hi @c0c0n3
Yes I rebase the PR.
Can You Please merge it.
Thanks


New package: CubeSoft.CubePDFUtility version 1.6.3

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[X] Does your manifest conform to the 1.0 schema?

Resolves #40956

Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers Add Validation-Domain


Update version to 1.1.7-0 on staging

Update version to 1.1.7-0

🚀 Deployed to staging by @OSBotify in version: 1.1.7-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by @AndrewGable in version: 1.1.7-24 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Juntylpromicrochip1 patch 2

Looks like this was created by accident, closing. If needed, feel free to reopen with more details, thank you!


VMWare vSphere OpenSDS Storage Plugin

What this PR does / why we need it:
With reference to opensds/design-specs#38, This PR is to
support VMware vSphere web client plugin  for OpenSDS storage and third party storage.
Special notes for your reviewer:
This is a work in progress PR, which includes

NGC Plugin: Which is the module to communicate with vSphere components.
Adapter Manager : This is the adapter implementation of opensds and thirdparty storage.

compilation guide can be seen in /vmware/ngc/doc
known limitations:

text  formatting of some files.
opensds adapter for taking default(first) network adapter for picking Initiator IP.

Testing notes:

Tested register module.
Tested device addition
Tested OpenSDS login/ Adding OpenSDS storage device.
Tested stoarge pool listing.
Tested Volume Creation.
Tested Volume Attachment to the ESXI host.

Release note:

@littlehotcx @skdwriting @wisererik @shanu04 Please review.

I have tested this PR by integrating changes in #251  .
Steps to test.

Clone PR #252 (C:/nbp)
clone PR #251 . Copy NGC_Register folder to  c:/nbp/vmware\ngc
Run ngc_package.bat (this should create a zip file (/release/NGC-Register-1.0.0)
4.unzip NGC-Register-1.0.0
5.run \NGC-Register-1.0.0\bin\run.bat
launch https://localhost:8088/homePage
Give vcenter credential and register.
8 login to vcenter server appliance.
stop and atart vsphere-client service ( service-control --stop vsphere-client
service-control --start vsphere-client)
launch vsphere web client.
OpenSDS Storage plugin should be listed in Home page.
12 use plugin to register opensds.
13 provison volume from opensds using volume.


Use an InternalClient pool

Instantiating an InternalClient takes ~300 ms in my measurements. We should not instantiate it on every iteration, but rather use a pool of InternalClient objects. This could be done either by passing an internal client to the handler or by maintaining a dictionary of handlers (so that on subsequent calls, the internal client is already instantiated).

Closed via 7f519c7ce98d9ea04c2b4a27b9ee7f25c0cb6dc6


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v5.10 to before v5.10.44",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e81a7018d93a7de31a3f121c9a7eecd0a5ec58b0",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=851dee5a5da56564a70290713aee665403bb0b24"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "e81a7018d93a7de31a3f121c9a7eecd0a5ec58b0",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "851dee5a5da56564a70290713aee665403bb0b24",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "usb: dwc3: gadget: Bail from dwc3_gadget_exit() if dwc->gadget is NULL\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.10.44 by commit 851dee5a5da56564a70290713aee665403bb0b24, it was introduced in version v5.10 by commit e81a7018d93a7de31a3f121c9a7eecd0a5ec58b0. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1000954


When adding numeric fields, only a small number of numeric fields can be added

HI, @stockbal
In the SQL console, it works when wog001 is added to wog009 but it gives an error when wog001 is added to wog010 or even wog016,
Is there a solution?

Best wishs,
Cooper

Hi @COOPER-DENG ,
This is an error returned by the database and appears in all places in the SAP system where you can execute a select statement ( ADT SQL Console, ABAP Report ). The reason for the error is that summing up so many amounts with a length of 23 places and 2 decimals may exceed the maximum length for a numeric field 31 places and 14 decimals.
A possible workaround would be to add a cast in the selection, assuming the summed up amount does not have more than 31 places and 14 decimals.

For reference you can find here the discussion in the sap comunity: https://community.sap.com/t5/application-development-discussions/syntax-issue-in-advacne-sql/td-p/508018
Kind regards,
Renata

Hi @COOPER-DENG ,
This is an error returned by the database and appears in all places in the SAP system where you can execute a select statement ( ADT SQL Console, ABAP Report ). The reason for the error is that summing up so many amounts with a length of 23 places and 2 decimals may exceed the maximum length for a numeric field 31 places and 14 decimals.
A possible workaround would be to add a cast in the selection, assuming the summed up amount does not have more than 31 places and 14 decimals.

For reference you can find here the discussion in the sap comunity: https://community.sap.com/t5/application-development-discussions/syntax-issue-in-advacne-sql/td-p/508018
Kind regards, Renata

HI,@
You are right, I have solved the problem according to the method you provided, thank you!

Hi @COOPER-DENG ,
This is an error returned by the database and appears in all places in the SAP system where you can execute a select statement ( ADT SQL Console, ABAP Report ). The reason for the error is that summing up so many amounts with a length of 23 places and 2 decimals may exceed the maximum length for a numeric field 31 places and 14 decimals.
A possible workaround would be to add a cast in the selection, assuming the summed up amount does not have more than 31 places and 14 decimals.

For reference you can find here the discussion in the sap comunity: https://community.sap.com/t5/application-development-discussions/syntax-issue-in-advacne-sql/td-p/508018
Kind regards, Renata

Hi, @reichr-dev ,
You are right, I have solved the problem according to the method you provided, thank you!
Best regards,
Cooper


Question ?

Thanks for this library  its been the most flexible and user friendly one I have found so far.  My question is does this support FTPS ?  if so could what modes implicit/explicit ?  could you provide a small example
Thanks

Thanks for using it.
It is an old source code, so I have already forgotten some parts.
Regarding FTPS, unfortunately, we do not support explicit mode.
For implicit mode, please refer to the ftpclient_test.go file, which is commented, but has the code to run it.

Thank you.


Fixes duplicate tree view add button for closed Controlled Vocabularies

References
Fixes https://github.com/DSpace/dspace-angular/issues/3325
Description
The Controlled Vocabulary tree view was displaying two "Add" buttons, one enabled and one disabled, for closed Controlled Vocabularies.
You can read more here.
Instructions for Reviewers
Minor change. I just removed one of the excess buttons and moved the conditional logic to the [disabled] parameter in the button class.
To test it, try opening up a closed Controlled Vocabulary tree view and observing the "Add" button to make sure it's disabled and that there's only one of them.
Checklist
This checklist provides a reminder of what we are going to look for when reviewing your PR. You do not need to complete this checklist prior creating your PR (draft PRs are always welcome).
However, reviewers may request that you complete any actions in this list if you have not done so. If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

[x] My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
[ ] My PR passes ESLint validation using npm run lint
[ ] My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
[ ] My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
[ ] My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
[ ] My PR aligns with Accessibility guidelines if it makes changes to the user interface.
[ ] My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
[ ] My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
[ ] If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[ ] If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
[ ] If my PR fixes an issue ticket, I've linked them together.

@tdonohue I can port this change if it gets approved, unless I need to port it first, in which case, I will do that.

@aseyedia : You do not need to port this PR prior to review.  In fact, we have an automated porting process which is triggered if we merge a PR with a port to [branch] label.  This automated process usually works well for small PRs (like this one), but will sometimes fail.  So, we'd only ask you to port this PR yourself if we find that automated process fails.


Add new Windows 10 updates to dism++

Hi, this is the new WIndows 10 Update to new compilation but dism++ is not detected or you don´t has it.
This is de new Windows 10 Important update: windows10.0-kb4054517

Update now~
Best


[BugFix][Cherry-Pick] Fix bug show full column does not display default value

Fixes #27727
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 2 / 2 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/catalog/Column.java
2
2
100.00%
[]


Give Share Button in Popup Menu an Action

TODO :

[x]  Adding new libarary (React-Native-Share).
[x] Adding function to share button in popup menu to share the content's URL to user's supported app

Thanks

Hey, @TheJackTenor  Thanks for the PR, looks good. please make the requested change.

@kiok46 Oh, i'm really sorry about that. Wait a minute.

Hey, @TheJackTenor  This doesn't seem to work on Android. (Pixel2)

@kiok46 Is this done or can i pick this up ?


chore: release v1.4.0

v1.4.0 deployment should be hold on for mainnet until all draining validator have been withdrawn, and testnet testing is completed


@MastanSayyad The Badge ID QR code redirects to the Github profile ?

@MastanSayyad Hello,this is Stuti Tyagi.I am not able to download my contributor badge....this is my email<EMAIL_ADDRESS>,I used this to register for Gssoc.

@Stutityagi-18  it is working fine please enter your correct details once try with page refreshing

@Stutityagi-18 it is working fine please enter your correct details once try with page refreshing

It's not working


Added support for using a HTTP Proxy when fetching documents from Figma

On AAOS:
Set HTTP Proxy: adb shell settings put global http_proxy "<host>:<port>"
Unset: adb shell settings put global http_proxy ":0"

I thought when we first learned that some OEMs needed proxy support, there was some issue that made it difficult for us to implement. Did you find a way around that? Was it that we just thought ureq didn't have proper proxy support but it does?

ureq has HTTP proxy support.  The changes are to basically pass the HTTP Proxy setting from Android down to LiveUpdate code in Rust.

I've just committed the documentation in #127 and I'd like this to go in with it's usage documented. Can you rebase this and add documentation for setting the proxy?

Done.  Updated live-update/index.md


Expanding definition for d3f:SourceCode

I am just proposing an expanded definition for d3f:SourceCode...
:SourceCode a owl:Class,
        owl:NamedIndividual,
        :ReferenceType ;
    rdfs:label "Source Code" ;
    skos:altLabel "Code", "Source" ;
    :definition "Source code is written using a programming language and usually stored as plain text. This source is often transformed by a compiler, assembler, or interpreter into machine code to be executed by user programs. Source code is commonly designed by computer programmers but increasingly may be generated using automation including generative AI and refactoring software. Source code is vulnerable to supply chain attacks, where an adversary modifies the code to compromise the integrity and security of the software." ;
    rdfs:comment "With regard to software licensing as defined by the Free Software Foundation, the source code of a work means the preferred form of the work for making modifications to it." ;
    rdfs:seeAlso <http://dbpedia.org/resource/Source_code> ;
    rdfs:subClassOf :InformationContentEntity,
            [ a owl:Restriction ;
              owl:onProperty :may-be-modified-by ;
              owl:someValuesFrom :Agent ] .

We probably want to put that restriction on ICE.
Please send a pull.

Does this restriction look okay for the PR?
:SourceCodeAnalyzerTool a owl:Class ;
    rdfs:label "Source Code Analyzer Tool" ;
    rdfs:subClassOf :StaticAnalysisTool,
        [ a owl:Restriction ;
            owl:onProperty :analyzes ;
            owl:someValuesFrom :SourceCode ] ;
    :definition "A source code analyzer tool is a static analysis tool that operates specifically on source code, but not object code." ;
    rdfs:seeAlso <http://dbpedia.org/resource/Static_program_analysis> .
    ```


webview not show in full screen.

In My project webview is not show in full screen
 Device Samsung
 OS Version: 11

Code
import 'dart:io';
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';
import 'package:webview_flutter/webview_flutter.dart';
class WebviewFlutterTest extends StatefulWidget {
@override
State createState() => _WebviewFlutterTest();
}
class _WebviewFlutterTest extends State {
@override
void initState() {
if (Platform.isAndroid) WebView.platform = SurfaceAndroidWebView();
super.initState();
}
@override
Widget build(BuildContext context) {
return Scaffold(
body: WebView(
initialUrl:
"https://github.com/"),
);
}
}

@dharmeshapptrait
What plugin version are you using ?
Can you try by removing hybrid composition to see if it works full screen after that ?
if (Platform.isAndroid) WebView.platform = SurfaceAndroidWebView();

@dharmeshapptrait
What plugin version are you using ?
Can you try by removing hybrid composition to see if it works full screen after that ?
if (Platform.isAndroid) WebView.platform = SurfaceAndroidWebView();

i'm already try it...

What plugin version are you using ?

@dharmeshapptrait

What plugin version are you using ?

@dharmeshapptrait

flutter_inappwebview: ^5.3.2
&&
webview_flutter: ^2.0.8

@dharmeshapptrait
Can you try the plugin example on same device and see if you still get same behavior ?

@dharmeshapptrait
Can you try the plugin example on same device and see if you still get same behavior ?

yes

Thanks for confirming. I see the same behavior on S10 device.

 flutter doctor -v
[✓] Flutter (Channel stable, 2.2.2, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.2.2 at /Users/dhs/documents/fluttersdk/flutter
    • Framework revision d79295af24 (11 days ago), 2021-06-11 08:56:01 -0700
    • Engine revision 91c9fc8fe0
    • Dart version 2.13.3

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.56.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (4 available)
    • SM G975F (mobile) • RZ8M802WY0X • android-arm64 • Android 10 (API 29)
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 91.0.4472.106

• No issues found!

Any suggestion? We are having the same issue, particularly in Samsung devices only, for the rest devices works just fine. We tried different Samsung devices with Android 10 and 11 same issue.

Has anyone come up with a solution?
having similar problems


the generated mapper is an application-scoped CDI bean

the generated mapper is an application-scoped CDI bean and can be retrieved via @Inject

This causes a buffer overflow on openjdk6 can you investigate this issue ?

ignore modified travis.sh file


Syntax of pattern constraint

What's the syntax of the pattern constraint? Is this using Ruby regexps or something more platform neutral such as those specified in XML Schema?

Given pattern is still using ruby regex, and the mentioned issue has been closed, does this mean pattern will likely stay with ruby regex and not change to XSD style?


(build): update docs after publish

this adds ghpagesPushSite to the release step

upgrade sbt-paradox (was throwing errors on makeSite with Java 17)

not :100: this works out with the matrix and the github token as it, but since there is only one Scala/Java defined and GITHUB_TOKEN is in env, I think it could work like that

On a related note, updating sbt-paradox to v0.10.3 appears to have eliminated the need to explicitly "unlock" packages for reflection.  This was required for successful sbt-paradox execution using v0.9.2 and JDK 17+ thusly:
JAVA_OPTS="--add-opens java.base/java.lang=ALL-UNNAMED" sbt paradox

See here for details.
👍

FWIW, the current ci.yml definition updates the docs whenever a build is initiated.  This causes the displayed version to be a "pre-tagged" version, such as 0.13.1+0-ea2eae21+20221210-1443.
I'm not sure if the Github Actions needs: [build] property can be made conditional or not.  Perhaps an on: section introduced into the publish: job could achieve this?  (I don't know if that is supported BTW)
If the above is not easy to specify, then it's a small discrepancy and not a blocker IMHO.

Modifying githubWorkflowPublish should only affect the publish job which is only executed on tags, so I think your points are already addressed.  There is no way to configure permissions right now (but https://github.com/sbt/sbt-github-actions/pull/105 looks promising). Will look into working around that or maybe just wait for that to be merged.

Modifying githubWorkflowPublish should only affect the publish job which is only executed on tags, so I think your points are already addressed. There is no way to configure permissions right now (but sbt/sbt-github-actions#105 looks promising). Will look into working around that or maybe just wait for that to be merged.

Alles gut, alles klar 👍 .

@adrobisch ,
This PR has had no activity for quite some time and, since it is an edge case regarding a minor documentation generation detail, perhaps it could be closed?


Concurrency - can't set non-public fields in constructor

Laravel Version
11.23.5
PHP Version
8.3.10
Database Driver & Version

Description
Laravel's Concurrency facade throws a serialization exception if I want to set a non-public (private or protected) field in a class' constructor.
It does not have any issue with public properties though. See the steps to reproduce below.
Is this something that can be resolved, or are we required to implement alternative methods, such as assigning values from other methods rather than directly from the constructor?
Steps To Reproduce
Create a class that like this:
class Foo
{
    // Create a protected or private property
    private string $expensive;

    public function __construct()
    {
        // Try to set the value in the constructor
        $this->expensive = 'hello world';
    }

    public function bar(): string
    {
        return $this->expensive;
    }
}

Use the class:
$foo = new Foo;

[$bar] = Concurrency::run([
    fn () => $foo->bar(),
]);

Instead of getting back the string "hello world" in $bar, you will get a serialization exception, something like this: unserialize(): Error at offset 157 of 277 bytes.

You should implement Serializable the handle this: https://www.php.net/manual/en/class.serializable.php

Thanks!
If anyone else comes across this issue in the future, note that starting from PHP 8.1, the Serializable interface has been deprecated. It is recommended to implement the __serialize and __unserialize methods instead.


rpmalloc crashs

I created a dll for windows which contains rpmalloc.c and exports the rpmalloc functions.
The global operators new and delete were overwritten and contains the following code:
//********************************************************
void * operator new(size_t size)
{
return rpmalloc(size);
}
//********************************************************
void operator delete(void * const p) noexcept
{
rpfree(p);
}
//********************************************************
void * operator new[](size_t size)
{
return rpmalloc(size);
}
//********************************************************
void operator delete[](void * const p)
{
rpfree(p);
}
When I start our application it runs for about 10s and then crashes.
I attached a picture which shows the crash and the content of the variables in rpmalloc.

Using a custom memory allocator with DLLs in Windows is tricky, you have to make sure all allocations are routed to the correct allocator.
For example, calling a function in foo.dll which allocates memory internally (probably using the C/C++ runtime) and passing this pointer to another module which deallocates it using rpmalloc will cause this crash, since rpmalloc will assume the pointer passed to rpfree is a valid memory segment which was allocated by a call to rpmalloc.
Either you have to make sure all allocations are handled by rpmalloc (which will probably be impossible unless you can recompile all third party DLLs used, or runtime patch the symbol table in all loaded modules), or that you never pass a pointer to rpfree which was not allocated by rpmalloc