Add an automatic GCP-BOM dependency upgrader

Command: python scripts/tools/gcpbomupgrader.py 26.30.0
If run python scripts/tools/gcpbomupgrader.py 26.31.0 based on this PR, it would give:
INFO:root:Changed com.google.api:gax: 2.39.0 -> 2.41.0
INFO:root:Changed com.google.cloud:google-cloud-spanner: 6.56.0 -> 6.57.0
INFO:root:Changed io.grpc:grpc-netty: 1.60.0 -> 1.61.0
INFO:root:Unchanged: io.netty:netty-transport:4.1.100.Final
INFO:root:Changed com.google.protobuf:protobuf-java: 3.25.1 -> 3.25.2
INFO:root:Changed org.apache.arrow:arrow-memory-core: 14.0.2 -> 15.0.0

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

CC: @dhruvdua @shunping

The code looks good. I am also wondering if we can use your script to add a presubmit test, so if the version is not right, the update cannot be submitted.
This may need to change your script to support two modes: in-place updating (which is already implemented) and reporting only. Then a new test can be added to call this script in reporting mode and check if there is any version mismatch.
WDYT?

The code looks good. I am also wondering if we can use your script to add a presubmit test, so if the version is not right, the update cannot be submitted.
This may need to change your script to support two modes: in-place updating (which is already implemented) and reporting only. Then a new test can be added to call this script in reporting mode and check if there is any version mismatch.
WDYT?

This sounds good, similar to .github/workflows/update_python_dependencies.yml . We can setup a "test" to generate a PR / or fail like the referred workflow.
However in practice we already have many tests and there are infra related workflow no one cares and red for months. So the actual benefit I am not sure. As of the scope of this PR I am not intend to setup a test.

LGTM!


Possible race condition in definition + use of ResourceClasses

Description
Going into certain resources, I have run into this issue a couple of times where there's a complaint that the ResourceClasses object is not defined. This cannot be reproduced 10/10 but I think it has to do with the event.ts using the ResourceClasses while also being imported by k8s/index.
Here is an error call stack I got:

I haven't seen this in a while and we cannot reproduce it. Let's close for now.


change command in readme.md

change command 'sh' for 'setup_tracker_gcp.sh' to 'source'  in 'readme.md' to be in ../ain-blockchain after setting everything up.
#87

@gmlee329  could you also update sh setup_node_gcp.sh part?

@gmlee329 could you also update sh setup_node_gcp.sh part?

@platfowner I've updated that part!

@gmlee329 thanks!


remove functions marked for 0.7 removal

[x] Closes issue #xxxx
[x] I am familiar with the contributing guidelines.
[x] Fully tested. Added and/or modified tests to ensure correct behavior for all reasonable inputs. Tests (usually) must pass on the TravisCI and Appveyor testing services.
[x] Updates entries to docs/sphinx/source/api.rst for API changes.
[x] Adds description and name entries in the appropriate docs/sphinx/source/whatsnew file for all changes.
[x] Code quality and style is sufficient. Passes LGTM and SticklerCI checks.
[x] New code is fully documented. Includes sphinx/numpydoc compliant docstrings and comments in the code where necessary.
[x] Pull request is nearly complete and ready for detailed review.

There are a couple of deprecations in ModelChain that I will handle in a follow up PR because they are slightly less straightforward.


Submit Smoldyn 2.67.2

id: smoldyn
version: "2.67.2"
specificationsUrl: https://raw.githubusercontent.com/ssandrews/Smoldyn/0bedd3851cf8bd384759f99a0bbb8b57b687a814/biosimulators.json
specificationsPatch:
version: "2.67.2"
image:
url: ghcr.io/ssandrews/smoldyn/biosimulators_smoldyn:2.67.2
digest: "sha256:abc34e2573d90ec5424b141a0a5f3814ac2619c5c0e69a1168b58bda8cace366"
validateImage: true
commitSimulator: true

Thank you @ssandrews for your submission to the BioSimulators simulator validation/submission system!
The BioSimulators validator bot is validating the specifications of your simulator, validating your Docker image, and committing your simulator to the BioSimulators registry.
We will discuss any concerns with your submission in this issue.
A complete log of your simulator submission job will be available for 90 days here. The results of the validation of your tool will also be saved as a JSON file. A link to this file will be available for 90 days from the "Artifacts" section at the bottom of this page.

The specifications of your simulator is valid!

Summary of tests

Executed 73 test cases

Passed 39 test cases:

cli.CliDescribesSupportedEnvironmentVariablesInline
cli.CliDisplaysHelpInline
cli.CliDisplaysVersionInformationInline
combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
docker_image.DeclaresSupportedEnvironmentVariables
docker_image.DefaultUserIsRoot
docker_image.HasBioContainersLabels
docker_image.HasOciLabels
docker_image.SingularityImageExecutesSimulationsSuccessfully
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesLinear2DPlots
sedml.SimulatorProducesLogarithmic2DPlots
sedml.SimulatorProducesMultiplePlots
sedml.SimulatorSupportsAlgorithmParameters
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
sedml.SimulatorSupportsDataSetsWithDifferentShapes
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithLinearUniformRanges
sedml.SimulatorSupportsRepeatedTasksWithLogarithmicUniformRanges
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes
sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes

Failed 0 test cases

Skipped 34 test cases:

published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
published_project.SimulatorCanExecutePublishedProject:cellml/Elowitz-Nature-2000-Repressilator
published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system
published_project.SimulatorCanExecutePublishedProject:mass/Bordbar-Cell-Syst-2015-RBC-metabolism
published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE
published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler
published_project.SimulatorCanExecutePublishedProject:rba/Escherichia-coli-K12-WT
published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-Fehlberg
published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Elowitz-Nature-2000-Repressilator
published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution
published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis
published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation
published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-NRM
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Irons-J-Theor-Biol-2009-yeast-cell-cycle
published_project.SimulatorCanExecutePublishedProject:xpp/Wu-Biochem-Pharmacol-2006-pituitary-GH3-cells
sedml.SimulatorProducesLinear3DPlots
sedml.SimulatorProducesLogarithmic3DPlots
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
sedml.SimulatorSupportsComputeModelChanges
sedml.SimulatorSupportsModelAttributeChanges
sedml.SimulatorSupportsRepeatedTasksWithChanges
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables
sedml.SimulatorSupportsSubstitutingAlgorithms

Warnings
docker_image.DeclaresSupportedEnvironmentVariables (0.3 s)

Test if a Docker image declares the environment variables that is supports
Warnings:
Docker images for simulation tools should declare the environment variables that they support.

The Docker image does not declare the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'
  - 'BUNDLE_OUTPUTS'
  - 'COLLECT_COMBINE_ARCHIVE_RESULTS'
  - 'COLLECT_SED_DOCUMENT_RESULTS'
  - 'DEBUG'
  - 'H5_REPORTS_PATH'
  - 'KEEP_INDIVIDUAL_OUTPUTS'
  - 'LOG_PATH'
  - 'OMEX_METADATA_INPUT_FORMAT'
  - 'OMEX_METADATA_OUTPUT_FORMAT'
  - 'OMEX_METADATA_SCHEMA'
  - 'PLOTS_PATH'
  - 'REPORTS_PATH'
  - 'REPORT_FORMATS'
  - 'SAVE_PLOT_DATA'
  - 'VALIDATE_IMAGES'
  - 'VALIDATE_IMPORTED_MODEL_FILES'
  - 'VALIDATE_OMEX_MANIFESTS'
  - 'VALIDATE_OMEX_METADATA'
  - 'VALIDATE_RESULTS'
  - 'VALIDATE_SEDML'
  - 'VALIDATE_SEDML_MODELS'
  - 'VIZ_FORMATS'

If the simulation tool implements these variables, they should be declared in the Dockerfile for the Docker image for the simulator.

Note, support for these environment variables is optional. Simulation tools are not required to support these variables.

Log: None

Skips
published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_3972
Algorithm: KISAO_0000263

Reason for skip:
Case requires model formats format_3972 and simulation algorithms KISAO_0000263

Log: None

published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_3972
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_3972 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:cellml/Elowitz-Nature-2000-Repressilator (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_3240
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_3240 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_3240
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_3240 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:mass/Bordbar-Cell-Syst-2015-RBC-metabolism (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_9004
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_9004 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_9004
Algorithm: KISAO_0000030

Reason for skip:
Case requires model formats format_9004 and simulation algorithms KISAO_0000030

Log: None

published_project.SimulatorCanExecutePublishedProject:rba/Escherichia-coli-K12-WT (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_9012
Algorithm: KISAO_0000669

Reason for skip:
Case requires model formats format_9012 and simulation algorithms KISAO_0000669

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Caravagna-J-Theor-Biol-2010-tumor-suppressive-oscillations (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-Fehlberg (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000086

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000086

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Ciliberto-J-Cell-Biol-2003-morphogenesis-checkpoint-continuous (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000088

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000088

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Elowitz-Nature-2000-Repressilator (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Parmar-BMC-Syst-Biol-2017-iron-distribution (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_000019

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_000019

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Szymanska-J-Theor-Biol-2009-HSP-synthesis (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000496

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000496

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000560

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000560

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000560

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000560

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000019
Format: format_2585
Algorithm: KISAO_0000027

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000019, KISAO_0000027

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000019

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-NRM (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000027

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000027

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000029

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000029

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000437

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000437

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000449

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000449

Log: None

published_project.SimulatorCanExecutePublishedProject:sbml-qual/Irons-J-Theor-Biol-2009-yeast-cell-cycle (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000449

Reason for skip:
Case requires model formats format_2585 and simulation algorithms KISAO_0000449

Log: None

published_project.SimulatorCanExecutePublishedProject:xpp/Wu-Biochem-Pharmacol-2006-pituitary-GH3-cells (0.0 s)

Required model formats and simulation algorithms for SED tasks:

Format: format_9010
Algorithm: KISAO_0000019

Reason for skip:
Case requires model formats format_9010 and simulation algorithms KISAO_0000019

Log: None

sedml.SimulatorProducesLinear3DPlots (0.1 s)

Test that a simulator produces linear 3D plots
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log: None

sedml.SimulatorProducesLogarithmic3DPlots (0.0 s)

Test that a simulator produces logarithmic 3D plots
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log: None

sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions (0.0 s)

Test that that the curated number of output dimensions matches the actual number of output dimensions
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log: None

sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges (0.0 s)

Test that a simulator supports model changes that involve adding, replacing, and removing model elements.
Reason for skip:
This test is only implemented for XML-based model languages. Please contact the BioSimulators Team to discuss implementing tests for additional languages.

Log: None

sedml.SimulatorSupportsComputeModelChanges (0.0 s)

Test that a simulator supports compute model changes
Reason for skip:
This test is only implemented for XML-based model languages. Please contact the BioSimulators Team to discuss implementing tests for additional languages.

Log: None

sedml.SimulatorSupportsModelAttributeChanges (0.0 s)

Test that a simulator supports changes to the attributes of model elements
Reason for skip:
This test is only implemented for XML-based model languages. Please contact the BioSimulators Team to discuss implementing tests for additional languages.

Log: None

sedml.SimulatorSupportsRepeatedTasksWithChanges (0.1 s)

Test that a simulator supports repeated tasks with multiple subtasks
Reason for skip:
This test is only implemented for XML-based model languages. Please contact the BioSimulators Team to discuss implementing tests for additional languages.

Log: None

sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables (0.0 s)

Test that a simulator supports repeated tasks over nested functional ranges based on model (specification) variables
Reason for skip:
This test is only implemented for XML-based model languages. Please contact the BioSimulators Team to discuss implementing tests for additional languages.

Log: None

sedml.SimulatorSupportsSubstitutingAlgorithms (0.1 s)

Check that a simulator can substitute algorithms that it doesn't implement with similar algorithms when the algorithm substitution policy is less restrictive than :obj:AlgorithmSubstitutionPolicy.SAME_METHOD. Also check that a simulator ignores unsupported algorithm parameters when the algorithm substitution policy is less restrictive than :obj:AlgorithmSubstitutionPolicy.NONE.
Reason for skip:
Algorithm substitution for "Brownian diffusion Smoluchowski method" (http://www.biomodels.net/kisao/KISAO#KISAO_0000057) for policy SIMILAR_VARIABLES is not supported.

Log: None

The image for your simulator is valid!

Your submission was committed to the BioSimulators registry. Thank you!
Future submissions of subsequent versions of smoldyn to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.


Can't change Text FontSize

Is it possible to add a property in this component that can be bound in Xaml and used to set the Font size of the displayed label?

Added this feature in 2.1.3


Reorganize doc categories

Problems:

Need chinese translation of new categories in _config.yml
Can Use Cases page be removed? It was not listed in the overview category
Can Metrics page be removed? It was not listed in the operation category
3 API pages (FS, S3 and POSIX APIs) were kept even though the entire API category was not listed in the new layout. Confirm that they should still remain the same?

Change list:

Overview

Move top level pages into overview/
Renamed Overview.md to Introduction.md
Renamed Architecture-DataFlow.md to Architecture.md

Core services

Moved and renamed corresponding pages into new directory named core-services/
Moved pages under Structured Data into here

Install Alluxio

Renamed from Deploying Alluxio, with directory name install/
Removed page on vagrant
Added page priorities for listing in desired order

Alluxio in the Cloud

Moved AWS EMR and Dataproc pages into new directory named cloud/

Compute Integrations

Renamed from Data applications, with directory name compute/

Storage integrations

Renamed from Ufs, with directory name storage/

Operations

Moved pages from basic and advanced into operations/ directory
Renamed Command-Line-Interface.md to User-CLI.md
Added page priorities for listing in desired order

Fixed links for all the renames and moves

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6921/
Test PASSed.

Why is the metrics page being removed? I don't understand

Please keep Metrics in Operations
Please keep Use Cases in Overview
Keep 3 API pages
I will translate the _config.yml

do the chinese pages need to be reorganized in the same way?

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6942/
Test PASSed.

alluxio-bot, merge this please


[Maint, CI] Update circleci.yml for artifact location to fix redirector

References and relevant issues
In https://github.com/napari/napari/pull/6417/ the CircleCI config was changed to harmonize with napari-docs. This changed the path for the repo clone, which changes where the html artifacts are located so the redirector link in actions doesn't work.
See: https://github.com/napari/napari/pull/6475#issuecomment-1821270543
Description
This PR updates the location of the artifacts generated by CircleCI building docs. This is analogous to the fix in the napari-docs repo: https://github.com/napari/docs/pull/278

Note that this PR won't have the fix working till merged.


🚀 Feature: Allow to edit share info (name, description) after creation

🔖 Feature description
Currently I can only set the name and description, when creating a share. Afterwards I can only add more files, but cannot change these basic settings.
🎤 Pitch
Sometimes you forget to set a name or have a type and want to fix it.

Also if we could add a password after the share has been created.

Throw in ability to edit the reverse-share link would be extremely handy.


Posts page broken in Safari Private browsing

Hi Kelvin,
First off nice theme - I plan on adapting it for my new blog soon.
I noticed you've switched to using localStorage in place of js-cookie. I was wondering what the bug you refer to is in the update?
Unfortunately the switch to store.js means the theme is currently broken when store is not available, which happens for example in Safari Private browsing mode. As someone that uses private browsing quite a lot that seems like a big limitation. Especially as there is no warning, the posts just don't load (see screenshot).

Hi Andrew,
First off, thanks for checking out the theme and I'm glad you're liking it so far! Also, thanks for thoroughly going through multiple user scenarios to help discover these kind of issues!
I switched from js-cookie to store.js because I realized some of the limitations of cookies if I wanted to implement some more advanced features in the future. Potentially in the future I may want to store metadata on the user's browser to help provide them a custom experience without any need for a special backend API or service (trying to keep the theme as lightweight + speedy as possible).
I was not aware of the issue in private mode, and this bug is mostly likely due to bad error handling on my part. I will take a look at it and will implement a patch very soon (hopefully later today).
Thanks!

Thanks again for reporting this issue. It should now be resolved in the latest commit: https://github.com/kelyvin/caffeine-theme/commit/e75490b4633df874ed8bcc7690f9356f8a5bb6e7
This fix will render the posts page correctly and let me know if you still run into any other issues.


[ISSUE][1.2.1-preview.54] Some impediments using CLI version. Is not enough for my needs?

Hey, I just started working with Refitter a couple of days ago. It's a really cool tool, but it seems like a couple of options are not working as expected (or I am missing something), and I do have a problem with creating a proper configuration and parameters for the CLI command to generate contracts and interfaces.
So my case looks like this, I need to build interfaces and contracts after each build of project. I have an ASP.NET WebAPI with two controllers and some models, for now just as simple as possible. So I have created a "refitter.targets" file which I included inside the .csproj of my API. Inside targets I have couple <Exec command> targets where I am calling dotnet tool restore, dotnet tool update and of course this command
dotnet refitter $(OpenApiDocumentation) -o $(RefitterOutputDirectory) -n $(ProjectName).Client --contracts-output $(RefitterContractsOutputDirectory) --contracts-namespace $(ProjectName).Contract --no-accept-headers --use-api-response --cancellation-tokens
As I mentioned I have 2 controllers named: CoolController and WeatherForecastController

This command is generating me only one file for interfaces named RefitInterfaces.cs and Contracts.cs but I would like to see multiple clients with proper names like ICoolClient and IWeatherForecastClient with methods that belong only to these specific controllers. I have used --multiple-interfaces ByTag option and its looks pretty fine, but is there an option to split these interfaces into different files?
About contracts, they are as well only inside one file. I would really like to see multiple files with proper names of classes. Classes are generated fine with all properties, but why it is the single file? I would like to see just files with names of the contract. For example: Error.cs, User.cs, etc.
Inside the Contracts.cs I see a lot of disabled warnings. Is there a way to pass some kind of settings/configuration to the NSwag from Refitter?
Is there a way to pass a summary as well (not only returns) of the method to the generated Refit interface? For now it looks like this

I really appreciate any help you can provide.

@smietanka Thanks for taking the time to report this

This command is generating me only one file for interfaces named RefitInterfaces.cs and Contracts.cs but I would like to see multiple clients with proper names like ICoolClient and IWeatherForecastClient with methods that belong only to these specific controllers. I have used --multiple-interfaces ByTag option and its looks pretty fine, but is there an option to split these interfaces into different files?

From v1.2.1 you can split the output into multiple files, but it's pretty primitive and can only split it into 3 files:

RefitInterfaces.cs
Contracts.cs
DependencyInjection.cs

Technically, it's possible to split up the Refit interfaces into multiple files. I designed the system in a way that I should be able to easily.

About contracts, they are as well only inside one file. I would really like to see multiple files with proper names of classes. Classes are generated fine with all properties, but why it is the single file? I would like to see just files with names of the contract. For example: Error.cs, User.cs, etc.

I piggy-back on NSwag for parsing the OpenAPI spec and generating contracts. I get all contracts generated as a single string and I don't intend to analyze and break that single large string down into multiple files. If I can find a way to use NSwag to generate single contracts at a time then I will in the future add support for generating multiple files for the contracts

Inside the Contracts.cs I see a lot of disabled warnings. Is there a way to pass some kind of settings/configuration to the NSwag from Refitter?

I haven't figured out a way to get NSwag to not disable warnings. This is common practice in code generators as they have to support multiple versions of the framework. Refitter (and NSwag) generates code that is compatible with .NET Framework 4.x -> .NET Standard 2.0 -> .NET Core  9.0
It's probably a personal thing, but I treat generated code like pulling in a third-party library and I don't care much about how to structure code that I didn't write. That said, the way I use Refitter is to generate "Client SDK's" for the API's that I build from the CI/CD platform that I use

Is there a way to pass a summary as well (not only returns) of the method to the generated Refit interface? For now it looks like this

Refitter purely looks at the OpenAPI spec and maps the details in paths to xml docs in the following way:

I'm generally very open to pull requests so if you have ideas or things you want to add to Refitter that you think you can build yourself then I'll make sure that if you create a pull request we get your changes in 😄

Thanks for your response :)
Yeah, splitting files for each client would be really useful not only for readability but also for git history, etc. Basically, all kinds of splitting contracts or interfaces into different files would really help with git history :)

I really would see some kind of option to pass NSwag settings into the NSwag process while the Refitter is running it. I believe it could be done somehow so NSwag probably has an option to split DTOs into different files, I will check first if this CLI has this option.
This topic probably is similar to the second point, so passing configuration into NSwag directly from Refitter would take it into account so warnings could be disabled.
Ok it seems that I have missed generating xmlDocumentation while I am using AddSwaggerGen now summaries are correctly passed into swagger.json :)

Thanks I will try to check the code what could be changed here


feat: new strategy approach

This is a new implementation approach that:

fixes compatibility with Joken 2 (rc3+)
Adds a more resilient way of refetching the cache
Can be customized for more than one JWKS server

It simplifies a lot of code too... less "concepts" to deal with when implementing your own strategy.

Sorry for the delay @bryanjo... I am trying this a bit more... testing is not good enough I guess... We have to provide an easier way to test this like not  trying to fetch the jwks upon application start.
I'll think this through once more...

@bryanjos I'll go ahead and merge this since the changes were mainly ergometric... the strategy is still the same that you reviewed.
I've added some docs and guides and will publish 1.0.0 to hex! :)


python3.pkgs.mypy: disable FPU tests on i686

Without the change x87 FPU tests fail for minor precision difference as:
AssertionError: actual for 1.7976931348623157e+308: 1.3407807929942597e+154,
                expected 1.3407807929942596e+154 (diff)

FAILED mypyc/test/test_run.py::TestRun::run-floats.test::testFloatOps
FAILED mypyc/test/test_run.py::TestRun::run-math.test::testMathOps

Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Oh, it was already dealt with in staging as d9b1d8cfcf8555516ac732e9c8b10c4ed52ffee0


[ZEPPELIN-1889] Fill missing values to grouped data

What is this PR for?
Fix for multiple group in multi-bar chart
If any value is missing under any domain key in stacked multi-bar chart,
it won't get rendered. Fix this bug by adding fillMissingValues flag in
d3DataFromPivot()
What type of PR is it?
[Bug Fix]
What is the Jira issue?

ZEPPELIN-1889

How should this be tested?

Create a paragraph with tabular output
Add multiple groups to input
Render the stacked multi bar chart
Chart should be rendered properly

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Are there any problems in CI?

I checked Jenkins log for last commit 368a50e. And looks like Jenkins build script somehow confused with 'merge' and handling it not very well. :-(

Sorry, it's my mistake, I did a pull instead of rebase


Search autocomplete broken, how to revert

I'm assuming this is Betterfox-related since it used to work, what about:config tweak needs to be changed to revert this?

https://github.com/yokoffing/Betterfox?tab=readme-ov-file#required-reading
https://github.com/yokoffing/Betterfox/wiki/Common-Overrides#instructions
https://github.com/yokoffing/Betterfox/wiki/Common-Overrides#search-settings


International email addresses is not supported at DAO creation

Describe the bug
Any Unicode email is not valid
To Reproduce
Steps to reproduce the behavior:

Go to beta.gamedao.co
Click on "New DAO"
Enter any Unicode email
See that email is not valid.

Expected behavior
According to https://en.wikipedia.org/wiki/International_email
any of
<EMAIL_ADDRESS>             (Chinese, Unicode)
<EMAIL_ADDRESS>             (Hindi, Unicode)
<EMAIL_ADDRESS>        (Ukrainian, Unicode)
<EMAIL_ADDRESS>     (Greek, Unicode)
<EMAIL_ADDRESS>(German, Unicode)
<EMAIL_ADDRESS>            (Russian, Unicode)
are valid emails.
Screenshots

all kind of exotic top level domains as well


Validate double environment variables in the Pod spec

Doubles in the environment variables in the Pod spec will lead to an error during patch creation:
Error: helm upgrade have failed: UPGRADE FAILED: cannot patch "resource" with kind Deployment: The order in patch list:
[map[name:DOCKER_IMAGE_ID "some-id"] map[name:REDIS_PRICE_TRIGGERS_POOL_SIZE value:20] map[name:REDIS_PRICE_TRIGGERS_POOL_SIZE value:40] map[name:REDIS_LOCKS_HOST "host"] map[name:REDIS_LOCKS_PORT value:6379]]
 doesn't match $setElementOrder list:
[map[name:DOCKER_IMAGE_ID] map[name:REDIS_PRICE_TRIGGE...
...

This should be solved by proper generic validation of Kubernetes resources according to their schemas, which we will do as part of #6159
Closing this as duplicate.


Use Located::new over struct initializer

This PR changes the python.lalrpop to use Located::new over the struct initializer syntax.
This change is motivated to ease upstream contribution from Astral's RustPython fork. Astral's fork uses Located::end_location: Location over Located::end_location: Option<Location> [PR].
Using Located::new has the added benefit that it requires slightly less code because the custom field can be omitted, and end_location doesn't need to be wrapped in Some

I wish we can entirely remove Option from end_location, but not sure if it is possible while keeping cpython compatibiltiy.

Thanks for merging this so quickly.

I wish we can entirely remove Option from end_location, but not sure if it is possible while keeping cpython compatibiltiy.

I'm unfamiliar with CPython. Do you know what's the reason in CPython for end_location being optional?

I don't remember well, but one of them was python-side created ast objects issues.
I think a workaround using __dict__ of the python object will work.
I will look in what more issues exist.


configmaps lock is removed, migrate to configmapsleases

CSV group-sync-operator.v0.0.21 install cannot be completed due to the below error:
unable to start manager {"error": "configmaps lock is removed, migrate to configmapsleases"}

ARO version: 4.10.15
Group sync operator: alpha: group-sync-operator.v0.0.21
group-sync-operator image: quay.io/redhat-cop/group-sync-operator@sha256:979acc20b045f1b21c5bb60bc3d95ed5ccb440d93eef9a4cbb19751d8922a83d

Also seeing same issue.
ARO Version: 4.10.30
Group sync operator: alpha: group-sync-operator.v0.0.21
group-sync-operator image: quay.io/redhat-cop/group-sync-operator@sha256:979acc20b045f1b21c5bb60bc3d95ed5ccb440d93eef9a4cbb19751d8922a83d

Issue acknowledged. Investigating....

Hi. When can we expect a new release with a fix?

@vmospan-hub New release was just published and is being processed by the OperatorHub team
Release: https://github.com/redhat-cop/group-sync-operator/releases/tag/v0.0.22
Operator Hub PR: https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/1984

Thanks!

0.0.22 should now be available in Operator Hub

Thanks for the quick turn around.

Thank you @sabre1041, it's working now

Thank you, @sabre104. It's working here using OCP 4.11.18 with RH IDM.

@EirikOpheim , we were in the same situation.
We removed both 0.0.21 and 0.0.20 and after that you can install again from scratch with 0.0.25 version.

Now the pod is running well.
Maybe there is an issue in the upgrade path, we should be able to bypass the 0.0.21 version when upgrading from 0.0.20


SSLSessionContext.getSession(...) must return SSLSession that impleme…

…nt all methods as expected
Motivation:
When we retrieve a SSLSession via SSLSessionContext.getSession(...) we must be able to access all its methods and the return values should reflect what were able to retrieve in the original session.
Modifications:

Change unit test to valide SSLSessions retrieved via the SSLSessionContext.

Result:
Ensure correct behaviour of SSL implementations

This test currently fails for our native implementation... I will work on a fix


Release v0.3.0 Planning

This issue tracks the set of issues that need to be completed and included in the v0.3.0 Release (changes since v0.2.0 on May, 21, 2023):
Features:

[ ] #663
[ ] #670
[ ] #580
[ ] #614
[ ] #630
[x] #635
[x] #658: Includes "aya: allow unsupported maps"
[ ] #521

[x] #600: API Change
[x] #628: API Change

[x] #429

[x] #581: API Change

[x] #320

[x] #570: API Change
[x] #605

[ ] #369 & #564

[x] #556: API Change
[x] #572: API Change
[x] #616: API Change

[x] #459 & #324

[x] Fixed by #529: API Change

[x] #394

[x] Fixed by by #541

[ ] #533

[x] Partial Fix by #539
[x] Partial Fix by #555

[ ] #430

[x] Partial Fix by #530: API Change

[x] #514

[x] Fixed by #515 Includes "Move bpfd images to use tag :latest instead of :main"

[x] #339

[x] Fixed by #342: API Change

Bugs:

[x] #666

[x] Fixed by #667

[x] #640

[x] Fixed by #649

[x] #638 Includes "change kind deployment to a single node"
[x] #613: API Change
[x] #612
[x] #500

[x] Fixed by #523

TODO @astoycos Track in Milestone?

Done in #770


ESP32: I2C broken by c9e0ad2ac21c26820f04f95d42307a3d53e20ebd

At least on ESP32 the mentioned commit ( https://github.com/esp-rs/esp-hal/commit/c9e0ad2ac21c26820f04f95d42307a3d53e20ebd ) breaks I2C
Need to test on other targets

Tested on all the others and it works there - so it's most probably just some issue with the ESP32 SVD

Closed by #1009


[Prototype] Use builder pattern for PipelineOptions

Early prototype to explore using the builder pattern for pipeline configuration.
Advantages:

Solves API discoverability problem - all extension methods are on HttpPipelineOptions and instantly visible to the customer
Separating registrations from instantiation allows reusing the same pipeline options in multiple clients
Allows to plug DI enabled policies easily (pass in a factory that resolves policy from DI)
Allows to hide policy implementation classes and expose only extension methods simplifying future support
Allows to easily extend pipeline sections list just by adding an entry to the enum

I'll clean it up and add tests if we decide that we are willing to pursue this direction.

Use of delegates for policies

Enables policies managed by DI using DI scopes (singleton/transient) in the future.
Simplifies programming model in default case: no need to worry about cross-pipeline state management.

Closing, this served its purpose.


UserDialogs.Instance.Loading - NullReferenceException

This happens on iOS.
               _progress = UserDialogs.Instance.Loading(maskType: MaskType.Black);
throws:
NullReferenceException.
Full Exception:
at BigTed.ProgressHUD.PositionHUD (Foundation.NSNotification notification) [0x000f4] in <filename unknown>:0
at BigTed.ProgressHUD.ShowProgressWorker (Single progress, System.String status, MaskType maskType, Boolean textOnly, ToastPosition toastPosition, System.String cancelCaption, System.Action cancelCallback, Double timeoutMs, Boolean showContinuousProgress, UIKit.UIImage displayContinuousImage) [0x00265] in <filename unknown>:0
at BigTed.ProgressHUD+<Show>c__AnonStorey0.<>m__0 () [0x00000] in <filename unknown>:0
at Foundation.NSActionDispatcher.Apply () [0x00000] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/Foundation/NSAction.cs:57
at (wrapper managed-to-native) ObjCRuntime.Messaging:void_objc_msgSend_IntPtr_IntPtr_bool (intptr,intptr,intptr,intptr,bool)
at Foundation.NSObject.InvokeOnMainThread (System.Action action) [0x00007] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/Foundation/NSObject2.cs:544
at BigTed.ProgressHUD.Show (System.String status, Single progress, MaskType maskType, Double timeoutMs) [0x0002b] in <filename unknown>:0
at BigTed.BTProgressHUD.Show (System.String status, Single progress, MaskType maskType) [0x00006] in <filename unknown>:0
at Acr.UserDialogs.ProgressDialog+<>c__DisplayClass27_0.<Refresh>b__0 () [0x0002e] in <filename unknown>:0
at Foundation.NSActionDispatcher.Apply () [0x00000] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/Foundation/NSAction.cs:57
at (wrapper managed-to-native) ObjCRuntime.Messaging:void_objc_msgSend_IntPtr_IntPtr_bool (intptr,intptr,intptr,intptr,bool)
at Foundation.NSObject.InvokeOnMainThread (System.Action action) [0x00007] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/Foundation/NSObject2.cs:544
at Acr.UserDialogs.ProgressDialog.Refresh () [0x00091] in <filename unknown>:0
at Acr.UserDialogs.ProgressDialog.Show () [0x00007] in <filename unknown>:0
at Acr.UserDialogs.AbstractUserDialogs.Progress (Acr.UserDialogs.ProgressDialogConfig config) [0x0004d] in <filename unknown>:0
at Acr.UserDialogs.AbstractUserDialogs.Loading (System.String title, System.Action onCancel, System.String cancelText, Boolean show, Nullable`1 maskType) [0x0005c] in <filename unknown>:0
at MyApp.Pages.BaseContentPage`1[T]..ctor (MyApp.ViewModels.LandingViewModel viewModel) [0x0001f] in /Users/zeferino/development/git_repositiories/EXTERNAL/appyfans-xamarin/FansApp/FansApp/Pages/BaseContentPage.cs:23

Where are you calling this from?  I see this when the loading is called before the view is ready.

Im calling this in the constructor in my base content page.
But the line _progress = UserDialogs.Instance.Loading(maskType: MaskType.Black); is just to init the dialog.
I just want to initialize the dialog in the constructor and later on call the show and hide:
_progress.Hide();

Loading has an autoshow which defaults to true which is what is causing this issue likely. You should only init the progress when you're ready for it in any case.
using (UserDialogs.Instance.Loading(...)) {
/// do you async stuff here, if anything crashes, the dialog will auto cleanup
}

SOLVED
The problem is that the show param from the Loading() is true by default.
solved it:
           _progress = UserDialogs.Instance.Loading(show: false, maskType: MaskType.Black);


Test function is not working as expected

Hi team. First thing, you are doing a great job.  I thin, I found an issue in the execution phase.
The flow is the next:
async function login(username, password) {
await t
.typeText('#username', username)
.typeText('#password', password)
.click('button'`);
};
test("User should login", async t => {
login("username", "password");
await t.
      expect("true").eql("true");

}) ;
This is working fine, but if we use an anonymous function instead of t , the changes are not applied.  If we add the second function:
async function loginTest() {
await t
.click('button'`);
};
and then, we perform the test as:
test("User should login", async () => {
login("username", "password");
loginTest();
}) ;
The test is marked as pass, no mather what changes you've made.

maybe because you are missing await ?
test("User should login", async () => {
/* --> */ await login("username", "password");
/* --> */await loginTest();
}) ;

I have that await in the helpers, and should not be the problem.
Will give a try. thanks.

Thanks @devmondo . Your approach is working.


goog.require emitted for every complete request

Sorry for posting an image, didn't know how to show it otherwise. Note that I pressed auto-complete a couple of times and each time a goog.require is done. Using the rebel-readline setup.
Seems like something that should only be done once?

(not to mention all the other goog.addDependency stuff but I think that is the REPL doing that because of the require)

Yes, this should be done only once. For repls other than shadow-cljs this is the case, I'll add a load check for shadow in the next version.

That example was from rebel-readline + figwheel. Didn't involve shadow-cljs at all.

OK, thanks, I will look into it.


Migrate diff-sequences to Typescript

Summary
Diff in built code:

diff --git a/packages/diff-sequences/build/index.js b/packages/diff-sequences/build/index.js
index a85f0a1ed..7c696426a 100644
--- a/packages/diff-sequences/build/index.js
+++ b/packages/diff-sequences/build/index.js
@@ -11,7 +11,6 @@ exports.default = void 0;
  * This source code is licensed under the MIT license found in the
  * LICENSE file in the root directory of this source tree.
  *
- *
  */
 // This diff-sequences package implements the linear space variation in
 // An O(ND) Difference Algorithm and Its Variations by Eugene W. Myers
@@ -603,13 +602,33 @@ const findSubsequences = (
     if (transposed && callbacks.length === 1) {
       // Lazily wrap callback functions to swap args if graph is transposed.
       const _callbacks$ = callbacks[0],
-        _foundSubsequence = _callbacks$.foundSubsequence,
-        _isCommon = _callbacks$.isCommon;
+        foundSubsequence = _callbacks$.foundSubsequence,
+        isCommon = _callbacks$.isCommon;
       callbacks[1] = {
-        foundSubsequence: (nCommon, bCommon, aCommon) => {
-          _foundSubsequence(nCommon, aCommon, bCommon);
-        },
-        isCommon: (bIndex, aIndex) => _isCommon(aIndex, bIndex)
+        foundSubsequence: (function(_foundSubsequence) {
+          function foundSubsequence(_x, _x2, _x3) {
+            return _foundSubsequence.apply(this, arguments);
+          }
+
+          foundSubsequence.toString = function() {
+            return _foundSubsequence.toString();
+          };
+
+          return foundSubsequence;
+        })((nCommon, bCommon, aCommon) => {
+          foundSubsequence(nCommon, aCommon, bCommon);
+        }),
+        isCommon: (function(_isCommon) {
+          function isCommon(_x4, _x5) {
+            return _isCommon.apply(this, arguments);
+          }
+
+          isCommon.toString = function() {
+            return _isCommon.toString();
+          };
+
+          return isCommon;
+        })((bIndex, aIndex) => isCommon(aIndex, bIndex))
       };
     }

Test plan
Green CI

Interesting how complicated the build got compared to the baseline

Yeah, seems like it wants to make sure this stays correct in the new version? Not sure why


Shadow banding artefacts

Maybe you can help me. I've got what I think is a quite basic shadowmap setup and I'm getting the following artefacting when I generate a shadow map of any size. I'm using a DirectionalLight and haven't tried the others yet.

Versions:
<EMAIL_ADDRESS><EMAIL_ADDRESS>
Target:
x86_64-apple-darwin

Repro repo here.
If you could critique my code as well that would be much appreciated.

Only the cube should cast shadow, so if you only use the cube when generating the shadow map, it should look better. The problem is that the ground is really big and the 1024x1024 pixel shadow map will be stretched over a large area.

Ah that makes sense. So if I had custom terrain that I'd generated in some third party software and wanted it to cast shadows on itself, I would simply need to choose a larger shadow map?

Using the shadow map technique over large areas is generally not a good idea, you'll have to move the directional light with the camera to only cast shadow close to the camera view where the shadows are visible or maybe make several directional lights.
I came to think about that in the case you present, the artifacts are more visible by the direction of the light being close to parallel to the ground. Also, the shadow has a soft edge which is not looking good in this case.

Ah ok, in that case does a directional light have a some local bounds that it generates shadow maps within? Is there something like a ScissorBox that applies here? I know these are probably quite simple questions, and appreciate your time.

Ah ok, in that case does a directional light have a some local bounds that it generates shadow maps within? Is there something like a ScissorBox that applies here?

Yes, it will position the shadow map camera such that the objects that cast shadow are all within its viewport. That means, if you have a large object or two objects that are far away from each other, the shadow map will cover a large area and the shadows therefore look pixelated.

you'll have to move the directional light with the camera to only cast shadow close to the camera view

This was not a well thought out reply, of course you can't move a directional light. Instead, you could generate the shadow map with only the objects that are just in front of the camera. Also, it's important to note that only the objects that cast shadow, not the ones that receives shadow, should be given as input to generate_shadow_map.

maybe make several directional lights.

I have considered supporting multiple shadow maps on a single directional light, but unfortunately there's more important tasks at the moment.

I know these are probably quite simple questions, and appreciate your time.

I think they're totally valid questions, I'll convert this into a discussion afterwards so others may find answers to the same questions 👍 I should maybe also update the documentation of generate_shadow_map to make it a bit more clear.

Also, it's important to note that only the objects that cast shadow, not the ones that receives shadow, should be given as input to generate_shadow_map.

That's a really helpful point, thanks! Would be great to know when this changes, but no pressure on my side.


XCode task doesn't pass archivePath parameter

I'm using the XCode build task to build my IOS App.  The build output I want is an xcarchive file.  I'm using the action archive. To create the xcarchive file when building the archive action, you need to pass the -archivePath parameter to xcodebuild.
If I execute the xcodebuild command with the archive action and the archivePath parameter from the command line, the xcarchive file does get created as expect.
The Apple documentation says the following about the archivePath parameter:
Excerpt from: https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/xcodebuild.1.html

-archivePath xcarchivepath
Specifies the path for the archive produced by the archive action, or specifies the archive that
should be exported when -exportArchive is passed.

I will try to make a pull request with a fix in the next few days.

I found if I don't pass the -archivePath parameter to the xcodebuild task, the archive file will be generated to the default location (Users\agentUserName\Library\Developer\Xcode\Archives...).
But if I pass the -archivePath parameter, the build agent can actually generate an .xcarchive file at the specified location. However, sadly the size of this archive file is zero... :(

Madhuri, is this foxed now with the rollout of the revamped task?

Addressed in PR: https://github.com/Microsoft/vsts-tasks/pull/2701

@bryanmacfarlane and @madhurig, since PR #2701 is merged, is it safe to close this issue?

@DavidStaheli: I will close the issue once the changes are deployed to Team Services.

Fix has been merged and will be deployed to Team Services starting Oct 16th and should roll out to all accounts in about a week.

Still having this issue with Xcode@5


Dev kmr

if-no-files-found: error --> does it mean "mark this tun as failure" if no files found ?

yes
The way I modified run-ci to create the artifact I would expect the file to be there and if not then something went wrong.


Renaming

After the "mission-critical" issues are addressed, are you okay with me setting up some name cleaning in the generator project?
Example:
public enum NfdresultT
{
    NFD_ERROR = 0,
    NFD_OKAY = 1,
    NFD_CANCEL = 2
}
public enum NfdResult
{
    Error = 0,
    Okay= 1,
    Cancel = 2
}

Sure

Is it still okay if I do this?

I wonder. It's a breaking change. Do I want to go to 2.0.0 already? 🤔

Nvm, the string marshalling fix was already a breaking change and I didn't up the version correctly lol


Layout/HashAlignment: Use table alignment

In the latest modulesync rubocop was auto-correcting:
{
   "foo"    => "bar",
   "forbar" => "bar"
}

Generally in the puppet world we are used to align to the => and a lot of specs are written this way (and I think it's better to stay this way)

is that the old or the new style?

The new, rubocop is currently auto-correcting to:
{
   "foo" => "bar",
   "forbar" => "bar"
}

I do agree we need something for this because it's making huge changes in some modules for (IMHO) no benefit. I'd like a consistent style, whether it's the old or new. Just as long as it doesn't mix styles. Reading https://www.rubydoc.info/gems/rubocop/0.83.0/RuboCop/Cop/Layout/HashAlignment it said:

Alternatively you can specify multiple allowed styles. That's done by passing a list of styles to EnforcedStyles.

Do we have a module where we can test if this works?

Tested here: https://github.com/voxpupuli/puppet-example/pull/21


Expose cuMemcpyDtoH_v2 in cust

In the latest version (0.3.0) of cust cuMemcpyHtoD_v2 was exposed as cust::memory::memcpy_htod. This avoids the need for reaching into cust_raw and allows using cust::error::CudaResult instead of error codes.
Should cuMemcpyDtoH_v2 be exposed in a similar manner to enable the features above for device to host memcpy as well?

Yeah it should be for consistency


Attachments on the global scope are added to every transaction

How do you use Sentry?
Self-hosted/on-premise
Version
1.39.1
Steps to Reproduce
Sentry version 23.10.1 88c7f2d, sentry-sdk==1.39.1
Problem:
Attachments that are added to the global scope are never "flushed" when a transaction is sent in an envelope so any attachments added throughout the lifetime of a process will be added to every subsequent transaction.
I ran into this because there is no way to explicit add an attachment to one transaction...
# This does not exist
with sentry_sdk.start_transaction(op="foo", name="transaction 1") as transaction_1:
        transaction_1.add_attachment(path=attachment_1, add_to_transactions=True)

... so when you are using the context-manager style transactions there does not seem to be a way to avoid this.
Workaround
The workaround I am currently using is to call this code before adding a different transaction.
with sentry_sdk.configure_scope() as scope:
    if attachments := scope._attachments:
        attachments.clear()

Suggestion
Add a hints: dict[str, Any] to the Transaction class so attachments can be added directly to a transaction. Those hints would just have to be passed to the call to hub.capture_event(event) found here https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/tracing.py#L747.
Screenshots
The discover tab.

Transaction 1 attachments.

Transaction 2 attachments.

Reproducer
Run the reproducer below.
import sentry_sdk
from pathlib import Path

dsn = "http://dfc61781f600282e6da8353828f00434@localhost:9003/2"

sentry_sdk.init(
    dsn=dsn,
    traces_sample_rate=1.0,
    debug=True,
)

attachment_1 = Path("/tmp/attachment_1.txt")
attachment_2 = Path("/tmp/attachment_2.txt")

attachment_1.write_text("attachment 1")
attachment_2.write_text("attachment 2")

with sentry_sdk.start_transaction(op="foo", name="transaction 1"):
    with sentry_sdk.configure_scope() as scope:
        scope.add_attachment(path=attachment_1, add_to_transactions=True)
        with sentry_sdk.start_span():
            print("added attachment 1")

with sentry_sdk.start_transaction(op="bar", name="transaction 2"):
    with sentry_sdk.configure_scope() as scope:
        scope.add_attachment(path=attachment_2, add_to_transactions=True)
        with sentry_sdk.start_span():
            print("added attachment 2")

Expected Result
Transaction 1 will have only attachment_1.txt attached.
Transaction 2 will have only attachment_2.txt attached.
Actual Result
Transaction 1 will have only attachment_1.txt attached.
Transaction 2 will have  attachment_1.txt and  attachment_2.txt attached.

Hey @matutter thanks for reporting this!
Internally Sentry manages a stack of scopes. With configure_scope you change the Scope on top of the stack. In your example that is both time the same scope.
You can replace with configure_scope() in your example with with push_scope(). With this change the top scope on the stack will be duplicated and you only change the duplicated one. Leading to the result you want to have.
Some side note: We are working on refactoring Scopes to make it easier for the user to do things like you do without knowing about the internals of how Sentry manages Scopes.

This suggestion results in no attachments being uploaded whatsoever.
I believe you also meant to point out that sentry_sdk.start_transaction must be called within the sentry_sdk.push_scope context manager. In that case it works as initially expected.
Correct usage:
with sentry_sdk.push_scope() as scope:
    with sentry_sdk.start_transaction(op="foo", name="transaction 1"):
        scope.add_attachment(path=attachment_1, add_to_transactions=True)
        with sentry_sdk.start_span():
            print("added attachment 1")

with sentry_sdk.push_scope() as scope:
    with sentry_sdk.start_transaction(op="bar", name="transaction 2"):
        scope.add_attachment(path=attachment_2, add_to_transactions=True)
        with sentry_sdk.start_span():
            print("added attachment 2")

So the issue is user error.
Thank you!


Compiling Arm again

I've fixed some issues compiling for 32-bit as well as re-enabling cross compilation for Arm/Arm64.
The Arm64 bit code does not compile yet as there were quite a few changes in the past few weeks. This will be the subject of another PR.
The only thing that is open to question is the use of the -mcx16 flag for x86 which does not exist when compiling for Arm. Can someone enlighten me to where this is actually needed in the code?

I've made -mcx16 AMD64 specific.


Incorrect script download location

The URL in the comment at the top of install.sh refers to the old self-hosted git repository. It should point to https://raw.githubusercontent.com/electricduck/sodalite/main/install.sh (as per the README).

Fixed by 85c7cee6e45b525979ac42bd929437810a4c88a6


feat: add JsonObject from/to PolicyDefinition transformers

What this PR changes/adds

Implements JsonObject from/to  PolicyDefinition
the process implemented in the new controller is

input: JsonObject -> expansion -> transform to dto -> transform to entity
output: entity -> transform to dto -> compaction -> JsonObject

Why it does that
dataspace protocol
Further notes

registered the json-ld object mapper once in ManagementApiConfigurationExtension
introduced EDC_PREFIX constant
got rid of the *New*Dto classes, as they became useless
I'm not sure why we are keeping two DTOs, one for creation (RequestDto) and one for modification (UpdateDto): they could be the same (this would save us two transformers and a wrapper class). Maybe something for a subsequent PR
I think some additional effort needs to be made for the swagger documentation

Linked Issue(s)
Closes # <-- insert Issue number if one exists
Checklist

[x] added appropriate tests?
[x] performed checkstyle check locally?
[x] added/updated copyright headers?
[x] documented public classes/methods?
[x] added/updated relevant documentation?
[x] assigned appropriate label? (exclude from changelog with label no-changelog)
[x] formatted title correctly? (take a look at the CONTRIBUTING and Etiquette for pull requests for details)

Codecov Report
Patch coverage: 94.64% and project coverage change: +0.06 :tada:

Comparison is base (0ac9755) 66.04% compared to head (7365a98) 66.11%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2863      +/-   ##
==========================================
+ Coverage   66.04%   66.11%   +0.06%
==========================================
  Files        1001      999       -2
  Lines       20216    20200      -16
  Branches     1185     1181       -4
==========================================
+ Hits        13352    13355       +3
+ Misses       6381     6356      -25
- Partials      483      489       +6

Impacted Files
Coverage Δ

...pi/configuration/DspApiConfigurationExtension.java
93.33% <ø> (ø)

.../org/eclipse/edc/web/jersey/JerseyRestService.java
95.00% <ø> (ø)

...n/java/org/eclipse/edc/jsonld/JsonLdExtension.java
0.00% <0.00%> (ø)

...nector/api/management/asset/AssetApiExtension.java
0.00% <ø> (ø)

...i/management/policy/model/PolicyDefinitionDto.java
85.71% <ø> (ø)

...ement/policy/model/PolicyDefinitionRequestDto.java
68.75% <ø> (+6.25%)
:arrow_up:

...ment/policy/model/PolicyDefinitionResponseDto.java
72.22% <ø> (+5.55%)
:arrow_up:

...gement/policy/model/PolicyDefinitionUpdateDto.java
100.00% <ø> (ø)

...policy/model/PolicyDefinitionUpdateWrapperDto.java
100.00% <ø> (ø)

...pse/edc/web/spi/provider/ObjectMapperProvider.java
0.00% <ø> (ø)

... and 7 more

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Just a quick question: we are now converting twice, once from JsonObject to Dto, and then from Dto to the entity. Technically, one single conversion would suffice.
Are we doing that just to have the DTO in the Swagger doc?

regarding multiple DTOs for request/response: if we don't need them we could get rid of them, but AFAIR when we devised them it made sense for multiple reasons e.g. different validation, or the fact that only the ResponseDto has a createdAt field

ResponseDto is different because, as you said, it has the createdAt, I was referring to RequestDto and UpdateDto, the only difference is the latter doesn't have the id but, to be fair, it would make sense to have the id both in the path and in the Dto, this would save us some transformers and the wrapper.

Just a quick question: we are now converting twice, once from JsonObject to Dto, and then from Dto to the entity. Technically, one single conversion would suffice. Are we doing that just to have the DTO in the Swagger doc?

The main reason is to have a convention because, in this case the Dto and the entity map pretty much 1:1, but in other entities the Dto is a stripped down version of the entity. In these case that middle conversion will be mandatory.
Regarding swagger documentation, I think the Dto won't be enough because we'd like to list Json-LD specific properties as @context, @type, @id..., things that for the moment are not listed, I would discuss this topic separately.

ResponseDto is different because, as you said, it has the createdAt, I was referring to RequestDto and UpdateDto, the only difference is the latter doesn't have the id but, to be fair, it would make sense to have the id both in the path and in the Dto, this would save us some transformers and the wrapper.

got it. yep, generally I think that would be fine.

The main reason is to have a convention because, in this case the Dto and the entity map pretty much 1:1, but in other entities the Dto is a stripped down version of the entity. In these case that middle conversion will be mandatory.

But couldn't we just do the "Stripping" in the JsonObjectFrom<ENTITY>Transformer then? Much the same as we are doing with DTOs anyway?

Regarding swagger documentation, I think the Dto won't be enough because we'd like to list Json-LD specific properties as @context, @type, @id..., things that for the moment are not listed, I would discuss this topic separately.

Maybe there is a way to solve this generically, e.g. through something like a DTO base class, that declares those JSON-LD props?


Increment number of sign in and date of sign in after confirmation. S…

I made 3 changes:
. Added pt-PT to rep
. When the user follow the confirmation link, he is automatically logged in. But the login date and login number increment is not updated.  Added sign_in(@resource) to update this information
. When you visit the change password link for the second time (sent by email), you should be redirected to a 404 page instead of get a window with a json message.

Thanks @rmvenancio! Looks like there are some failing tests that would need to be fixed, though. Would you also be able to split this up into 3 separate PRs, as well?

Hi @booleanbetrayal. I'm new to rails and this is my first collaboration. I will try to to find how to make the tests to pass and split this in 3 different PR. BR.

Will create different PRs


Attempted import error: 'BlocksMap' is not exported from 'easy-email-editor'.

I installed this into my react project I was following the documentation but when I tried to run it. I got
Failed to compile.
./src/App.js
Attempted import error: 'BlocksMap' is not exported from 'easy-email-editor'.
I went to node modules and I found easy-email-editor folder inside that I was unable to find it. It's missing from the default exports. Did you guys replaced it with another name?

Sorry, please install<EMAIL_ADDRESS>Due to my mistake, a beta version became the latest version.

@m-Ryan also  transformToMjml is no longer exported in version 2.5  ,  please give alternatives as it is very helpful in exporting html
Thank you so much!

@m-Ryan  are mergeTags supported? if so, since which version?  they seem not to work on @2.2.2 unfortunately the documentation does not state since what version they do ?

Also missing in the usage file at the end:
export default App
and don`t forget to put a semikolon after the last bracket  (like so: .....}; export default App)
Thanks for this great script!

@m-Ryan also transformToMjml is no longer exported in version 2.5 , please give alternatives or re-export, as it is very helpful in exporting html
Thank you so much!

Please not use the latest version, I am still doing more testing for it. It will take about two or three days
https://github.com/m-Ryan/easy-email/tree/mono-repo/packages/easy-email-core
transformToMjml will be rename to JsonToMjml


don't dump the whole document into files

parse5 returns a complete document, we only want the DOM within the body of that doc, prior to this fix content in files was incorrectly wrapped with html and body elements.

Isn't it better to use parse5's parseFragmentI() for this purpose?
Anyways, if we use the suggested approach we won't be able to use this plugin at the end of the metalsmith pipeline; that is where a complete HTML file been prepared. Where as the current implementation we can use only at the end of the pipeline. So I'm not sure, if we should pick this approach.
What is your use case, where the current implementation is giving problems?

I'm using hyphenate after markdown; files[file].contents represents content you want to place within a document via templates, not be the final document itself, therefore I don't believe you want <html><title></title><body> prepended to files[file].contents and as such the PR simple selects the content within <body> to place in the buffer.

Okay, understood the problem. I would suggest to move the hyphenate after template rendering.
I'm closing this PR.


Disable hook prePuller for three communites using the jupyterhub configurator

Since callysto, qcl, and 2i2c/climatematch are all using the configurator, they don't have any benefit from the hook prePuller so this PR disables it for these hubs to reduce unessecary complexity and false expectations from the config.
These are commits extracted from #3341 that as a whole can't be merged short term

Thank you for reviewing @yuvipanda !!


Build the CI on pull request

This may activate the checks on pull requests instead of only pushes.
Pull Request Checklist

[ ] Privileged views and APIs are guarded by proper permission checks.
[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] Database queries are optimized and the number of queries is constant.
[ ] Database migration files are up to date.
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] GraphQL schema and type definitions are up to date.
[ ] Changes are mentioned in the changelog.

After tests it doesn't work properly. GitHub is building on the latest base branch commit instead of the latest fork's branch commit.


Clocking

Instead of having for crystals with non-optimal accuracy, it might be more interesting to have one TCXO and a 1 to 4 clock buffer.

PoC V0.3 definately shows, that the cheap modules frequencies are a bit away from nominal.


Less string comparison in ExpressionActions.

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
Category (leave one):

Improvement

Short description (up to few sentences):
Decreased the number of string comparisons while executing actions on block. Split long_accurate_number_comparison test.

@KochetovNicolai Let's pull master and we'll continue reviewing.

Close for now.


Pipeline job change to support name + version in job output

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

        )

Should we be fetching Name & Version here?

Refers to: sdk/ml/azure-ai-ml/azure/ai/ml/entities/_job/_input_output_helpers.py:354 in 7f5b1f1. [](commit_id = 7f5b1f1f9e23498a25641c59c2a795c985ac77b9, deletion_comment = False)

    self.asset_version = kwargs.pop('asset_version', None)

IIRC, as per Qianqian Nie, we should not accept asset_version if asset_name is not available.

Refers to: sdk/ml/azure-ai-ml/azure/ai/ml/entities/_inputs_outputs/output.py:79 in 7f5b1f1. [](commit_id = 7f5b1f1f9e23498a25641c59c2a795c985ac77b9, deletion_comment = False)

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


Loss is summed over the batch to estimate the distance to the boundary

Hi,
I was trying to implement this nice work into my adversarial library.
However, I noticed something odd in the code. When estimating the distance to the boundary, the loss is summed over all samples in the batch.
This means that the estimate is correct when attacking one sample, but largely overestimated when attacking a batch of samples.
For isntance, attacking one sample of MNIST provides a distance of 2.6314 in the first iteration but attacking two samples (with the same first), gives [5.5989, 5.8717]. This scales indefinitely; with 100 samples in the batch, the distances are: [201.1688, 210.9703, ...] in the first iteration.

Hi @jeromerony,
thanks for testing our code and congrats on your library, it is very good work!
I will fix this bug as soon as possible, it is indeed a very nice catch!

Closed with #2.


determine if domain is valid in 'certs:attach  '

Currently, although certs:attach <cert> <domain> will properly error out if <cert> is bogus/non-existent, it doesn't if <domain> is similarly non-existent.  Consider the following unit test, which is currently failing (err is nil):
if err := Attach(&client, "test-example-com", "non-existent.domain.com"); err == nil {
   t.Fatal("An Error should have resulted from the attempt to attach a valid cert to a non-existent domain")
 }

This issue tracks work on the client side, and deis/workflow#475 tracks server-side work

Does this require any client side work at all? This looks entirely server side to me.


Typing ; replaces ()

Type () to call a method
Type ;
The () are replaced

Any idea what's going on here?

@roblourens Can you share some repo steps in the VS Code repo? I was seeing this pretty often yesterday but no longer seem to hit it

Sorry, it was happening reliably here https://github.com/microsoft/vscode/blob/73e6a7e3d2eeca422018c212e83bcd6bcbdbe7a7/src/vs/workbench/contrib/notebook/test/browser/notebookExecutionStateService.test.ts#L104 and today it is not happening anymore


[WIP] [FEATURE] ES6+ enum destructuring

JIRA: CPOUI5FOUNDATION-503
This PULL request tries to enable ES6+ destructuring for UI5 enums.
There might be different cases and ways to achieve this and with this change, we try to cover the ones we already know. (Note: There might be more we're not aware of).
Here are the cases we try to cover:

Destructuring from fully quantified name

// shortcut for sap.ui.core.TitleLevel
var {TitleLevel} = sap.ui.core;

Destructuring from fully quantified name

// shortcut for sap.ui.core.TitleLevel
var {TitleLevel} = sap.ui.core;

Chained destructuring

const library = {
  MyEnum: {
    Foo: "FooValue",
  },
};

const { MyEnum } = library;
const { Foo } = MyEnum;

Destructuring with a rename

 const { Foo: Bar } = MyEnum;

Destructuring as an argument of an arrow function

sap.ui.define([
	"sap/ui/core/Control",
	"./library"
], (Control, { MyEnumFromLib } ) => {
...
});

Any mixtures from the cases above

Coverage remained the same at 93.843% when pulling 11443413b1bd951ab76a831da478eb368a283724 on es6-enum-destructuring into b2ebd6c57a3399311b65b67077b470fb8133bd06 on next.


Add CI/CD label to Flux

What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Changelog entries must be created for modifications to shipped code
[ ] Add the qa/skip-qa label if the PR doesn't need to be tested during QA.

/merge


Cant build cytoolz

Hi,
I'm trying to install your library on python3.9, but I get bunch of errors.
Though I can easily install cytoolz 0.11.0 version
Seems like updating dependencies will fix it.
Still want to use your library, but don't want to downgrade python version
ERROR: Command errored out with exit status 1: /home/asd/PycharmProjects/project/venv/bin/python -u -c 'import sys,
setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-fogixndl/setup.py'"'"'; __file__='"'"'/tmp/pip-req-build-fogixndl/setup.py'"'"';
f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__,
'"'"'exec'"'"'))' install --record /tmp/pip-record-ewz8g3qj/install-record.txt --single-version-externally-managed --compile --install-
headers /home/asd/PycharmProjects/project/venv/include/site/python3.9/cytoolz Check the logs for full command output.

cytoolz/functoolz.c:17307:45: error: ‘PyTypeObject {aka struct _typeobject}’ has no member named ‘tp_print’; did you mean ‘tp_dict’?
         __pyx_type_7cytoolz_9functoolz_complement.tp_print = 0;
                                                   ^~~~~~~~
                                                   tp_dict

 In file included from /home/asd/.pyenv/versions/3.9.0/include/python3.9/unicodeobject.h:1026:0,
                       from /home/asd/.pyenv/versions/3.9.0/include/python3.9/Python.h:97,
                       from cytoolz/dicttoolz.c:17:
      /home/asd/.pyenv/versions/3.9.0/include/python3.9/cpython/unicodeobject.h:446:26: note: declared here
       static inline Py_ssize_t _PyUnicode_get_wstr_length(PyObject *op) {
                                ^~~~~~~~~~~~~~~~~~~~~~~~~~
      cytoolz/dicttoolz.c:9130:25: warning: ‘_PyUnicode_get_wstr_length’ is deprecated [-Wdeprecated-declarations]
                               (PyUnicode_GET_SIZE(**argname) != PyUnicode_GET_SIZE(key)) ? 1 :
                               ^

This issue can be closed thanks to #12


1.6.1 -- big-merge-503-geographic-feature-res-type-phase-1

Testing coverage report
Name                                       Stmts   Miss  Cover
init                                       0      0   100%
hs_access_control/init                     1      0   100%
hs_access_control/models                     658    188    71%
hs_app_netCDF/init                         0      0   100%
hs_app_netCDF/admin                            4      0   100%
hs_app_netCDF/forms                          121     70    42%
hs_app_netCDF/models                         188    135    28%
hs_app_netCDF/nc_functions/init            0      0   100%
hs_app_netCDF/receivers                      195    184     6%
hs_app_netCDF/serialization                  330    166    50%
hs_app_netCDF/tasks                            0      0   100%
hs_app_timeseries/init                     0      0   100%
hs_app_timeseries/admin                        4      0   100%
hs_app_timeseries/forms                      109     27    75%
hs_app_timeseries/models                     269    169    37%
hs_app_timeseries/receivers                  310    291     6%
hs_app_timeseries/tasks                        0      0   100%
hs_core/init                               0      0   100%
hs_core/admin                                  8      0   100%
hs_core/autocomplete_light_registry           21     14    33%
hs_core/forms                                715    484    32%
hs_core/hydroshare/init                    5      0   100%
hs_core/hydroshare/date_util                  53     34    36%
hs_core/hydroshare/discovery                   8      4    50%
hs_core/hydroshare/hs_bagit                  132     44    67%
hs_core/hydroshare/resource                  228     88    61%
hs_core/hydroshare/social                     77     61    21%
hs_core/hydroshare/users                     215    159    26%
hs_core/hydroshare/utils                     237     76    68%
hs_core/languages_iso                          1      0   100%
hs_core/management/init                    1      0   100%
hs_core/management/commands/init           1      0   100%
hs_core/models                              1298    304    77%
hs_core/receivers                             78     71     9%
hs_core/serialization                        912    680    25%
hs_core/signals                                9      0   100%
hs_core/tasks                                  0      0   100%
hs_core/templatetags/init                  1      0   100%
hs_core/testing                               11      0   100%
hs_core/views/init                       448    375    16%
hs_core/views/pagination                       3      0   100%
hs_core/views/resource_rest_api              169    113    33%
hs_core/views/serializers                     75     15    80%
hs_core/views/user_rest_api                    8      0   100%
hs_core/views/utils                          101     75    26%
hs_geo_raster_resource/init                0      0   100%
hs_geo_raster_resource/admin                   4      0   100%
hs_geo_raster_resource/forms                 154     93    40%
hs_geo_raster_resource/models                177    113    36%
hs_geo_raster_resource/receivers              98     88    10%
hs_geo_raster_resource/serialization         341    210    38%
hs_geo_raster_resource/tasks                   0      0   100%
hs_geographic_feature_resource/init        0      0   100%
hs_geographic_feature_resource/admin           4      0   100%
hs_geographic_feature_resource/forms          66     26    61%
hs_geographic_feature_resource/models        113     24    79%
hs_geographic_feature_resource/parse_lib      76     10    87%
hs_geographic_feature_resource/receivers     358     70    80%
hs_metrics/init                            0      0   100%
hs_metrics/models                              0      0   100%
hs_model_program/init                      0      0   100%
hs_model_program/admin                         4      0   100%
hs_model_program/forms                        39     12    69%
hs_model_program/models                       78     35    55%
hs_model_program/receivers                    27     19    30%
hs_modelinstance/init                      0      0   100%
hs_modelinstance/admin                         4      0   100%
hs_modelinstance/forms                        51     19    63%
hs_modelinstance/models                      115     70    39%
hs_modelinstance/receivers                    22     14    36%
hs_modelinstance/tasks                         0      0   100%
hs_swat_modelinstance/init                 0      0   100%
hs_swat_modelinstance/admin                    5      0   100%
hs_swat_modelinstance/forms                  164     61    63%
hs_swat_modelinstance/models                 402    279    31%
hs_swat_modelinstance/receivers               33     24    27%
hs_swat_modelinstance/tasks                    0      0   100%
hs_tools_resource/init                     0      0   100%
hs_tools_resource/admin                        4      0   100%
hs_tools_resource/forms                       85     30    65%
hs_tools_resource/models                     169    118    30%
hs_tools_resource/receivers                   39     29    26%
hydroshare/init                            2      0   100%
hydroshare/celery                             11      1    91%
hydroshare/local_settings                     62      0   100%
hydroshare/settings                           57      2    96%
irods_browser_app/init                     0      0   100%
irods_browser_app/models                       0      0   100%
manage                                         6      0   100%
ref_ts/init                                0      0   100%
ref_ts/admin                                   3      0   100%
ref_ts/models                                260    191    27%
ref_ts/receivers                              10      5    50%
theme/init                                 0      0   100%
theme/admin                                   12      0   100%
theme/blog_mods/init                       0      0   100%
theme/blog_mods/admin                          7      3    57%
theme/blog_mods/models                         0      0   100%
theme/models                                  91     11    88%
theme/templatetags/init                    0      0   100%
TOTAL                                      10157   5384    47%

Only some minor adjustments requested after the latest changes. Excellent improvements both moving these facilities into the base class and simplifying them greatly, @zhiyuli !

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@zhiyuli The reason that add_metadata_element_to_xml() cannot be called for OriginalCoverage element is that OriginalCoverage is serialized differently than other metadata elements. Specifically, OriginalCoverage is serialized in the same way as Coverage element for science metadata as follows:
<hsterms:spatialReference>
      <hsterms:box>
        <rdf:value>northlimit=4662392.44692; eastlimit=461954.019091; southlimit=4612592.44692; westlimit=432404.019091; units=meter; projection=NAD83 / UTM zone 12N Transverse_Mercator</rdf:value>
      </hsterms:box>
    </hsterms:spatialReference>

which is not handled currently by add_metadata_element_to_xml().

@ironfroggy do you think this branch is ready for merging, thanks

Can one of the admins verify this patch?

@ironfroggy Can you give this branch a +1 if it is ready. We need your approval getting it merged. Thanks

There are two instances of import * still in use in new code here. Please replace those with explicit imports of only the names you actually intend to import and need, and then merge. As long as that is done, I don't need to re-review, but I'm pretty firm on not letting import * in.

@zhiyuli - Once you push the changes for explicit imports the Jenkins PR builder should pick this up and run. If all passes as it did the last time @hyi will merge this into develop.

@mjstealey @hyi  Thanks! The changes has been done locally, and I am running testing code to double check. Will push it in 30 minus.


Annotation based java migration

Codecov Report

Merging #10 into master will increase coverage by 0.49%.
The diff coverage is 78.08%.

@@             Coverage Diff             @@
##             master     #10      +/-   ##
===========================================
+ Coverage        73%   73.5%   +0.49%
- Complexity      186     204      +18
===========================================
  Files            33      36       +3
  Lines           615     687      +72
  Branches         46      52       +6
===========================================
+ Hits            449     505      +56
- Misses          157     170      +13
- Partials          9      12       +3

Impacted Files
Coverage Δ
Complexity Δ

...com/monjam/core/resolve/JavaMigrationResolver.java
92% <ø> (ø)
5 <0> (ø)
:arrow_down:

.../main/java/com/monjam/core/support/ClassUtils.java
20% <ø> (ø)
1 <0> (?)

...src/main/java/com/monjam/core/command/Command.java
85.71% <ø> (ø)
7 <0> (ø)
:arrow_down:

.../com/monjam/core/database/SessionDbCollection.java
56.25% <0%> (-18.75%)
5 <0> (ø)

...va/com/monjam/core/history/DbMigrationHistory.java
100% <100%> (ø)
6 <1> (ø)
:arrow_down:

...njam/core/resolve/AnnotationResolvedMigration.java
100% <100%> (ø)
4 <4> (?)

...a/com/monjam/core/database/LegacyDbCollection.java
66.66% <50%> (-6.07%)
6 <1> (+1)

...main/java/com/monjam/core/database/DbTemplate.java
92.85% <50%> (-7.15%)
13 <1> (+1)

...jam/core/executor/AnnotationMigrationExecutor.java
53.84% <53.84%> (ø)
2 <2> (?)

...njam/core/resolve/AnnotationMigrationResolver.java
94.87% <94.87%> (ø)
10 <10> (?)

... and 3 more

Continue to review full report at Codecov.

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


Utils.git ignores failing commands

For example,
        git obImpl
        [ ["checkout", T.unpack gitBranch]
        , ["pull"]
        ]

If the checkout command fails, this merrily continues on without failing immediately.

Here's why https://github.com/obsidiansystems/obelisk/blob/master/lib/command/src/Obelisk/Command/Utils.hs#L28
We should just get the wrapProgram stuff over so we can stop using the awkward nix-shell at runtime.


Packer version on PackerBuild task is out-of-date

Packer passed their 1.0.0 mark awhile ago, the PackerBuild task should get updated to support multiple (including newer) versions.

A new preview version (1.*) of this task has been released which uses 1.2.4 Packer.


how do i get message id for CentralSystem commands

I'm trying to get message id for central system commands. looks like most doesnt really pass the requestId
<EMAIL_ADDRESS>Is there any way, i can get message id

The message ID is currently abstracted away and not visible in the upper layer. To be more precise, unique request identifiers are part of the ocpp-j spec and not the pure ocpp spec. Request IDs are visible in the logs though, if enabled.
What would you need it for, if I may ask?

Thanks @lorenzodonini for the update.
In OSCP 2.0, (4.4.1. UpdateGroupCapacityForecast & 4.4.3. GroupCapacityComplianceError) :
There is a request to distribute energy to chargers & any request fails or unable to comply, we need to send another error request to energy provider.
(GroupCapacityComplianceError X-Correlation-ID is required which is same as X-Request-ID in UpdateGroupCapacityForecast sent in before.)
The way I tried to achieve, is by sending SetChargingProfile (wait for Accepted/Rejected response).
chargerId & messageId (OCPP message ID) & X-Request-ID (OSCP) is used to map & accumulate all the energy for Rejected/Offline , compile the GroupCapacityComplianceError request & send.


soc: xtensa: ipc: unmask intc for core 0 only

In ACE architecture, only core 0 should receive IPC interrupts from host.
Unmasking secondary core IPC interrupts was causing race condition in ipc irq handler after enabling secondary core.
When secondary core entered ipc irq handler first, it cleared BUSY bit. Then Core0 handler quit the handler without servicing IPC.

@mwasko @marcinszkudlinski @aborisovich please review

@nashif fyi

I approved checks run that were waiting due to first time constibution.

@dcpleung  please verify, you introduced this in e869cff96c5


Topaz Video AI UI Freezes

Using the latest version of Topaz(v4.2.0) and TopazVideoPauser-x64.zip posted 1/16/24 the pause and resume button do work, but once Topaz is paused, the UI freezes. Unpausing it does not unfreeze the UI. If left alone, Topaz will finish generating the video. The UI still does not unfreeze after that, and the only thing that can be done is to kill the process in the Task Manager and restart Topaz. The ability to pause is great, but you no longer know how long it will take to finish with the video.

Thanks for report, what is status of Topaz Video AI.exe process in Task Manager Details tab after you tried to resume it? Running or Suspended?

I just tried this program and while it did cause the UI to freeze when paused, it unfroze when I unpaused it.
Ryzen 7 3800x
Radeon RX 6800 16 GB VRAM

I just tried this program and while it did cause the UI to freeze when paused, it unfroze when I unpaused it.
Ryzen 7 3800x Radeon RX 6800 16 GB VRAM

That's expected, UI will be froze on pause

I just encountered this issue as well on version 5.3.1 of Video AI, and checking in Task Manager for the exe process shows suspended status despite the pauser not paused and high CPU usage from ffmpeg process for which I'm assuming it's actually still processing despite the frozen UI.
Not sure if it might be related due to pause duration or some other factor. When I was initially checking the pause function it worked fine and the UI wasn't freezing. However after freezing for multiple hours and doing other resource intensive tasks on my PC I went back to unpause it and that's when I noticed the UI was still frozen.


Mirror: add repos needed by testsuite

Signed-off-by: Ricardo Mateus<EMAIL_ADDRESS>What does this PR change?
Add repositories need by the test suite to minima configuration file.

This works and I am OK merging it, although it would be even better to change the testsuite so that it does not require very old products and would save mirrors some bandwidth.
This can also be done as a second step.

This works and I am OK merging it, although it would be even better to change the testsuite so that it does not require very old products and would save mirrors some bandwidth.

I totally agree with you. But @Bischoff made a valid point that with this test we check if SCC works correctly with older product versions. For that reason, I didn't change the automatic test.

This can also be done as a second step.

I would prefer not, for the test coverage reasons explained by Ricardo.
Also, please consider there is no cost associated, other than maintaining more complete lists in sumaform: we don't sync those products.

The cost is just minima space and time to do the sync of several extra products. For remote devs or anyone needing a minima server for an on-the-road setup, that could be a couple hours of sync to their mirrors.

The cost is just minima space and time to do the sync of several extra products. For remote devs or anyone needing a minima server for an on-the-road setup, that could be a couple hours of sync to their mirrors.

Hmmm, right. I was focusing on the situation on the server, and overlook the consequences on the mirror.
Devil's advocate: this resync on the mirror is a one-off.
Also, I don't like much twisting the testing logic or scope for infrastructure reasons. We're just doing this too much already, and for example we keep paying over and over again for not doing real resyncs. Latest example: SUSE/spacewalk#10360.
But okay, feel free to reduce the list and to change the test suite accordingly. I don't want @rjmateus to have his remote work hindered by my being intransigent on testing old stuff.

But okay, feel free to reduce the list and to change the test suite accordingly. I don't want @rjmateus to have his remote work hindered by my being intransigent on testing old stuff.

Hey @Bischoff ,
My remote work is not hindered by this, I work without mirror (just take more time to download stuff).
I'm testing how mirror works and make sure everyone that wants to use it is able to (even run the testsuite).
With these changes, which I'm testing again, I think they will be able.
I will add to my list the task of changing the cucumber test, and after that remove the unnecessary repositories from the mirror.

Hey @Bischoff ,
My remote work is not hindered by this, I work without mirror (just take more time to download stuff).
I'm testing how mirror works and make sure everyone that wants to use it is able to (even run the testsuite).
With these changes, which I'm testing again, I think they will be able.
I will add to my list the task of changing the cucumber test, and after that remove the unnecessary repositories from the mirror.

We have a plan @rjmateus :smile_cat: .