Submit COPASI 4.28.226

id: copasi
version: 4.28.226
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_COPASI/432e2b2083f7b84b8b9ff6ce88c70c004d484d17/biosimulators.json
specificationsPatch:
version: 4.28.226
image:
url: ghcr.io/biosimulators/biosimulators_copasi/copasi:4.28.226
validateImage: true
commitSimulator: true

Thank you @biosimulators-daemon 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 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 from the "Artifacts" section at the bottom of this page.

The specifications of your simulator is valid!

Summary of tests

Executed 60 test cases

Passed 47 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
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
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-discrete-NRM
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesLinear2DPlots
sedml.SimulatorProducesLogarithmic2DPlots
sedml.SimulatorProducesMultiplePlots
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsAddReplaceRemoveModelElementChanges
sedml.SimulatorSupportsAlgorithmParameters
sedml.SimulatorSupportsComputeModelChanges
sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes
sedml.SimulatorSupportsDataSetsWithDifferentShapes
sedml.SimulatorSupportsModelAttributeChanges
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsRepeatedTasksWithChanges
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRangeVariables
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 13 test cases:

published_project.SimulatorCanExecutePublishedProject:bngl/Dolan-PLoS-Comput-Biol-2015-NHEJ
published_project.SimulatorCanExecutePublishedProject:bngl/test-bngl
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-continuous
published_project.SimulatorCanExecutePublishedProject:sbml-core/Edelstein-Biol-Cybern-1996-Nicotinic-excitation
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/Vilar-PNAS-2002-minimal-circardian-clock
published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-continuous
published_project.SimulatorCanExecutePublishedProject:sbml-fbc/Escherichia-coli-core-metabolism
published_project.SimulatorCanExecutePublishedProject:sbml-qual/Chaouiya-BMC-Syst-Biol-2013-EGF-TNFa-signaling
sedml.SimulatorProducesLinear3DPlots
sedml.SimulatorProducesLogarithmic3DPlots

Warnings
cli.CliDescribesSupportedEnvironmentVariablesInline (5.4 s)
Test that the inline help for a command-line interface describes the environment variables that the simulator supports.
Warnings:
The inline help for a command-line interface for a simulation tool should describe the environment variables that the simulation tool supports.

The command-line interface does not describe the following standard environment variables recognized by BioSimulators:
  - 'ALGORITHM_SUBSTITUTION_POLICY'

If the simulation tool implements these variables, they should be described in the inline help for its command-line interface.

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

Log:

docker_image.HasBioContainersLabels (0.5 s)
Test that a Docker image has BioContainers labels with metadata about the image
Warnings:
The Docker image should have the following BioContainers labels:
  extra.identifiers.biotools

Log:

published_project.SimulatorCanExecutePublishedProject:sbml-core/Tomida-EMBO-J-2003-NFAT-translocation (4.3 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000560

Warnings:
Unexpected reports were produced:
  BIOMD0000000678_sim.sedml/Figure_3c

Plots were not produced:
  simulation.sedml/Figure_3c

Extra plots were produced:
  BIOMD0000000678_sim.sedml/Figure_3c

Log:
Archive contains 1 SED-ML documents with 1 models, 1 simulations, 1 tasks, 1 reports, and 1 plots:

  BIOMD0000000678_sim.sedml:

    Tasks (1):

      BIOMD0000000678_task

    Reports (1):

      report: 5 data sets

    Plots (1):

      Figure_3c: 2 curves

Executing SED-ML file 0: BIOMD0000000678_sim.sedml ...

Bundling outputs ...

Cleaning up ...

============= SUMMARY =============

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 1

    Skipped: 0

    Failed: 0

  Tasks (1):

    Succeeded: 1

    Skipped: 0

    Failed: 0

  Outputs (2):

    Succeeded: 2

    Skipped: 0

    Failed: 0

published_project.SimulatorCanExecutePublishedProject:sbml-core/Varusai-Sci-Rep-2018-mTOR-signaling-LSODA-LSODAR-SBML (4.5 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000560

Warnings:
Unexpected reports were produced:
  LSODA.sedml/Figure_2c

Log:
Archive contains 1 SED-ML documents with 1 models, 1 simulations, 1 tasks, 1 reports, and 1 plots:

  LSODA.sedml:

    Tasks (1):

      task1

    Reports (1):

      report: 16 data sets

    Plots (1):

      Figure_2c: 1 curves

Executing SED-ML file 0: LSODA.sedml ...

Bundling outputs ...

Cleaning up ...

============= SUMMARY =============

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 1

    Skipped: 0

    Failed: 0

  Tasks (1):

    Succeeded: 1

    Skipped: 0

    Failed: 0

  Outputs (2):

    Succeeded: 2

    Skipped: 0

    Failed: 0

published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-NRM (16.3 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000027

Warnings:
Unexpected reports were produced:
  simulation.sedml/plot2d_Fig_1_c
  simulation.sedml/plot2d_low_delta_R_stoch

Log:
Archive contains 1 SED-ML documents with 2 models, 2 simulations, 2 tasks, 2 reports, and 2 plots:

  simulation.sedml:

    Tasks (2):

      tsk_1_0

      tsk_1_1

    Reports (2):

      report_Fig_1_c: 10 data sets

      report_low_delta_R_stoch: 10 data sets

    Plots (2):

      plot2d_Fig_1_c: 9 curves

      plot2d_low_delta_R_stoch: 9 curves

Executing SED-ML file 0: simulation.sedml ...

Bundling outputs ...

Cleaning up ...

============= SUMMARY =============

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 1

    Skipped: 0

    Failed: 0

  Tasks (2):

    Succeeded: 2

    Skipped: 0

    Failed: 0

  Outputs (4):

    Succeeded: 4

    Skipped: 0

    Failed: 0

published_project.SimulatorCanExecutePublishedProject:sbml-core/Vilar-PNAS-2002-minimal-circardian-clock-discrete-SSA (5.4 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000029

Warnings:
Unexpected reports were produced:
  simulation.sedml/plot2d_Fig_1_c
  simulation.sedml/plot2d_low_delta_R_stoch

Log:
Archive contains 1 SED-ML documents with 2 models, 2 simulations, 2 tasks, 2 reports, and 2 plots:

  simulation.sedml:

    Tasks (2):

      tsk_1_0

      tsk_1_1

    Reports (2):

      report_Fig_1_c: 10 data sets

      report_low_delta_R_stoch: 10 data sets

    Plots (2):

      plot2d_Fig_1_c: 9 curves

      plot2d_low_delta_R_stoch: 9 curves

Executing SED-ML file 0: simulation.sedml ...

Bundling outputs ...

Cleaning up ...

============= SUMMARY =============

Executed 1 SED documents:

  SED documents (1):

    Succeeded: 1

    Skipped: 0

    Failed: 0

  Tasks (2):

    Succeeded: 2

    Skipped: 0

    Failed: 0

  Outputs (4):

    Succeeded: 4

    Skipped: 0

    Failed: 0

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:

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:

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:

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:

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:

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:

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:

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
Format: format_2585
Algorithm: KISAO_0000030

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

Log:

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
Format: format_2585
Algorithm: KISAO_0000030

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

Log:

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:

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:

sedml.SimulatorProducesLinear3DPlots (0.2 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:

sedml.SimulatorProducesLogarithmic3DPlots (0.1 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:

The image for your simulator is valid!

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


How to handle loading states and requests?

Im still having some issues understanding restartableLatestCache.
I have an class that is handling network access and caching. So it has a method getData(boolean forceFromNetwork) returning a Single<Data>. That forceFromNetwork is called when the user pressed a button for retry.
When I enter the view the first time, getData(forceFromNetwork=false) should be called.
When the Single<Data> starts I want to display a loading state to the view, and when it returns I want to show the data or an error state.
When the user pressed reload, the getData(forceFromNetwork=true) should be called with the same behavior.
How can I archive that using nucleus? I experimented with restartableLatestCache and restartable and using two restartableId but I'm a little unsure how to handle it properly.
Till now I was just extending Presenter and added a CompositeSubscription between onTakeView and onDropView to which I was adding and removing the two Singles. But it seems like this library is exactly build so I do not have to worry about this manual starting / stopping.
Maybe it would also be useful to add the Loading-View-Error flow to the examples as its one of the most common requirements.

I would always set the loading state during onCreate/onCreateView, and your restartableLatestCache will remove the loading state. It's safe to do it like this because the data won't be delivered until onResume.
View (pseudocode):
onCreate(boolean savedState) {
    if (savedState == null) {
        presenter.getData(false)
    }
    progressBar.setVisibility(View.VISIBLE)
    retryButton.setOnClickListener { retryData() }
}

onNextData(List<Data> items) {
    progressBar.setVisibility(View.GONE)
    adapter.setItems(items)
}

onDataError(Throwable error) {
    progressBar.setVisibility(View.GONE)
    retryButton.setVisibility(View.VISIBLE)
}

retryData() {
    progressBar.setVisibility(View.VISIBLE)
    retryButton.setVisibility(View.GONE)
    presenter.getData(true)
}

Hope it helps

This is how I do it:
@State boolean isLoading ;

onCreate
   if isLoading
      showProgressBar

   if savedState == null
     showProgreessBar
     isLoading = true
     presenter.getData(forceFromNetwork=false)

onUserRequestedFreshData
     showProgreessBar
     isLoading = true
     presenter.getData(forceFromNetwork=true)

onDataReceived
   hideProgressBar
   showData
   isLoading = false

onNetworkError
   hideProgressBar
   showErrorRetryView
   isLoading = false

There is also isShowingErrorRetryView flag that need to be saved.
I have PlaceholderView class above each screen, it contains sub-screens for loading/network_error_retry_button/empty_result and manages isLoading, isShowingErrorRetryView flags, so the main view logic is not bloated.

But I also liked the @inorichi's answer, it seems valid and shorter.


Use intercepting routes for EventGroup modals.

Closed by https://github.com/one-zero-eight/InNoHassle-Website/commit/e2b6e299c1efda327f3236a6bf57da0e64113002


Is there a command to restart the plot window in the new version of spyder?

Problem Description
Hello!
I am plotting several figures using matplotlib in spyder. With the new version (4.1.3) the plots are now shown inside a the IDE like is done in R for example (which is awesome!), but now I want to close all the windows plotted with just a simple command or pressing any shortcut.
Is there a way to do that?
What steps reproduce the problem?

import matplotlib.pyplot as plt

for i in range(0,7):
    x=list(range(i,i+10))
    y=list(range(i,i+10))
    plt.figure()
    plt.plot(x,y,linewidth=2, markersize=12)

What is the expected output? What do you see instead?
This is what I expect:

Versions

Spyder version: 4.1.3
Python version:  3.7.5 64-bit
Qt version: 5.12.4
PyQt version: 5.12.3
Operating System name/version: Ubuntu 19

Thanks in advance

Hi @hdnh2006,
I'm glad that you like our plots feature, it is great! If you want to erase all the plots you generated, you can go ahead and click the highlighted icon in red,

For further information please note that two weeks ago we released the new documentation site where you can find a lot of guidance of how to use each pane of Spyder. For instance, this is the site of the plots pane, https://docs.spyder-ide.org/current/plots.html
Thanks for reporting!

Is there a way to do this programmatically? Like how you can clear the consol with:
from IPython import get_ipython
get_ipython().magic('clear')
get_ipython().magic('reset -sf')

No, there isn't.


Update the game over message

Update the game over message so people know how to play again!

perhaps through here?


Update _responsive-embed.scss

The var in the mixin currently doesn't exist and as such including it without a set $ratio var results in build failure.

@ncoden Good point and agreed.

Ack! Sorry I missed this when I created Responsive Embed. @ncoden, I think your solution works. Let's just make sure to include a comment that the $responsive-embed-ratio var will be removed in v6.4, along with the other deprecated functions.

@mheward it looks like there were some questions/changes requested, can you take a look so we can get this merged?  Thanks

Can you:

pass the $ratio parameter to @mixin responsive-embed in @mixin flex-video.

hey @andycochran @mheward @ncoden what is the status of this? The current PR doesn't appear to update anything... we're trying to wrap up 6.3.1 by next week, and would like to get this in.

I've updated the mixin to use the $ratio parameter as requested

we're trying to wrap up 6.3.1 by next week

Sweet :+1:

OK the one additional thing we need to do on this is make sure the default variable definition is in _responsive-embed.scss as _settings.scss is autogenerated upon build (I know it's confusing - it should be in dist, we'll probably move it there for 6.4)

@kball I've moved the var as requested.

Thanks @mheward! Merged!


Use admin account as payer on all outgoing transactions

We expect the admin account to contain enough FLOW to compensate for all custodial accounts' transactions.
Some endpoints (like FT withdrawal) use the user account as the payer, thus running into problems when transactions fail and the storage falls below the minimum.
All outgoing transactions from wallet-api should use the admin account as payer.

@tehranifar
It looks to me that all transactions send by hand are paid by user. Flow are taken from account after each transaction. Am I correct?

Yes, designating the admin account as payer will automatically make it pay for user transactions.

@uhbif19 I am not sure what you mean. 'designating the admin account as payer' - is that something possible in Wallet API? Or your answer is about situation when working with a regular Flow client libruary?

Hey @tehranifar, I've moved this issue to the new upstream repository here: https://github.com/flow-hydraulics/flow-wallet-api/issues/152


Fix Broken Links

Fixes various broken links.

:tada: This PR is included in version 6.11.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[proposal] Add annotation to controller to support immutable workspaces

What does this PR do?
Add annotation org.eclipse.che.workspace/immutable to signify that workspace should not allow further modification, to make secure configuration more persistent.
Once added, further modifications to workspaces are rejected by existing webhooks. If added to a workspace when webhooks are disabled, startup is failed.
What issues does this PR fix or reference?
We'll likely run into situations where modifications to an existing workspace can be used to extract a user's OpenShift token. This is a first step in preventing that without impacting other flows.
Is it tested? How?
Tested on crc

Rebased on master and added exception for started field, to allow starting/stopping immutable workspaces.

Marked as ready for review so we can assess whether this feature is useful.


reorganized Sublime Text extensions, added some

Moved extensions that were in JSON to JavaScript, as comments are allowed in the Sublime files, and were being incorrectly highlighted as errors (see this file, for example). Added several more extensions to JavaScript that hadn't been included previously. Finally, added 2 extensions to XML.

Update - the Travis build is now passing!

Thanks @MattDMo!


(PUP-7390) Prefer minitar for PMT when available

For platforms that ship a minitar gem (currently Windows, about to
include Solaris, and will eventually be all platforms), prefer
that to a local tar binary.
Solaris 10 currently doesn't work properly with the tar binary
and will be soon bundled with the minitar gem.  However, to use
the minitar gem, the priority ordering needs to be adjusted.

Currently only Windows ships the minitar gem (as it has a platform
specific gem), but eventually all platforms will reference the
minitar gem for the same reason - consistency and robustness.

👍

We'll probably want to validate this on a few platforms via acceptance / manual testing prior to merge given there aren't any real tests.

CLA signed by all contributors.

Should this retarget master since PUP-7390 is scheduled for 5.y?

I was thinking we'd be targeting the Solaris PMT install bugfix at the LTS release, hence stable @joshcooper

Looks like needs a spec fixup. Can we retarget PUP-7390 to 4.10.0 if going for LTS? 👍  pending acceptance run

@joshcooper / @MosesMendoza / @McdonaldSeanp are we shooting for next 4.10 series release on this one?

If we make this change in 4.x, then it means minitar must be able to unpack any module that has previously been built using native tar (except for Windows which has only ever supported minitar). Do we know if minitar can handle it? The PAX header thing comes to mind (which we fixed), but I don't know if there are other issues like that. Unless we're sure, I'd suggest targeting puppet 5 instead.

It's my understanding that for packages, we only ship minitar to Windows, and we haven't enabled minitar (yet) on Solaris packages.  For gems, only the Windows platform-specific gems refer to minitar (i.e. https://rubygems.org/gems/puppet/versions/4.9.4-x64-mingw32).
To answer the question about "native tar" - there isn't really such a thing.  There are various flavors of the file format (see https://en.wikipedia.org/wiki/Tar_(computing)#File_format or the notes from myself and Glenn on https://tickets.puppetlabs.com/browse/MODULES-3135).  We have had no guarantees previously in the forge about what format a given module tarball is in - even with Puppet modules, old modules prepared / shipped from local dev boxes will have been tar'd in a different format (OSX uses bsdtar) than ones shipped from jobs running on Linux.  The only tarball that I'm aware of that caused an issue was the one for DSC due to long filenames and the originating tar format - as you've noted, this has been fixed.
Given Windows has already been using minitar for a long time and we don't have reports of failures AND given that I don't believe we actually ship minitar anywhere else yet - I think we're OK on merging this PR.

The reason I'm eager to get this in is so that we can make PMT on Solaris functional - see PA-1019 Vendor minitar gem for Solaris packages - this is currently targeted at agnet 1.10.1 and has a corresponding PE ticket / escalation (PE-19583).

we only ship minitar to Windows, and we haven't enabled minitar (yet) on Solaris packages

Ah right, forgot about that: https://github.com/puppetlabs/puppet-agent/blob/a0cbf6ff51c3c78caa7b59b6e80f08429d6602ac/configs/projects/puppet-agent.rb#L233

To answer the question about "native tar" - there isn't really such a thing.

Yeah, I was using "native tar" to mean gnu tar, bsd tar, etc whatever tar happens to be in the PATH, with it's platform specific behaviors. There's a reason Java uses Jar files!


Blazor template impossible to get up and running

Issue Type: Bug
I use VS Code, and would like to use  Blazor Webassembly, so i downloaded the latest Framework (I am developing on a Mac) and created a solution. My intention are to make a client that's calling a backend API. I succeeded in calling the API, but the response did not contain the http headers from my API. With Postman the headers are all there. So I tried borrowing a Windows 10 PC and generating the solution, but to my supprise, the solution would not build, something with missing *.json files. Ok, Then I tried using Visual Studio 2019 community, and created the solution from the default template, but it actually got worse, nothing seem to work. now i ask for an explanation, Is this a new standard from Microsoft, I have developed c++/c# solutions for 30 years, and never seen the like, are Blazor a hobby project or something that Microsoft want the community to take serius? / Niels
VS Code version: Code 1.47.3 (91899dcef7b8110878ea59626991a18c8a6a1b3e, 2020-07-23T13:12:49.994Z)
OS version: Windows_NT x64 10.0.14393

System Info

Item
Value

CPUs
Intel(R) Pentium(R) CPU G840 @ 2.80GHz (2 x 2794)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: disabled_offoop_rasterization: unavailable_offprotected_video_decode: unavailable_offrasterization: unavailable_offskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: unavailable_off

Load (avg)
undefined

Memory (System)
3.83GB (0.54GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (9)

Extension
Author (truncated)
Version

npm-intellisense
chr
1.3.0

vscode-npm-script
eg2
0.3.13

vscode-npm
fkn
3.3.0

csharpextensions
jch
1.3.1

csharp
ms-
1.22.1

cpptools
ms-
0.29.0

qub-msbuild
qub
0.6.3

arduino-snippets
ron
1.0.2

vscode-arduino
vsc
0.3.1

/needsMoreInfo
Please update this issue after reading https://github.com/Microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions#writing-good-bug-reports-and-feature-requests. Thanks.


Provide a default fallback audio for when an audio file cannot be found.

@imsickofmaps & @gsvr one to review for when you're back online tomorrow.

doh, im was not defined within the scope. Adding in separate commit.

:+1:


Possible to auto-add firewall rules when a dependent roles is included?

Currently I'm using global rule definitions in group_vars and host_vars, but would it be possible to add iptables rules when adding a dependent role, and specifying the rules inside the directory for that role?

Can you give me an example with the dependency tree of what your are trying to do?

would it be possible to add iptables rules when adding a dependent role

@raarts What you describe is absolutely possible: set mikegleasonjr.firewall as a dependency in meta/main.yml, then specify your custom firewall rules in vars/main.yml. Note that you cannot use defaults/main.yml to override the firewall rules—that behavior changed in Ansible v2, IIRC.
If you provide more info about the services you're trying to configure, I'd be happy to put together a more explicit example of directory structure and variable overrides.

Thanks for jumping in @conorsch!

Since we haven't heard anything after a month I will assume OP found a solution!

I'm sorry, got distracted, but yes. @conosch 's solution works for me. Thanks!


TextField - New appendText method

Appending text should be a standard feature for TextField

@NathanSweet what do you think about this?


Update WCAG link for contrast

Update WCAG link for contrast from WCAG 2.0 to WCAG 2.1
My linter also seem to have removed a space on save, can put it back if it was intended.

You can preview this change here:
Built with commit d51fa77326d14acb228f0b4ef5dba49ce4574d27
https://deploy-preview-1005--govuk-design-system-preview.netlify.com

You can preview this change here:
Built with commit d51fa77326d14acb228f0b4ef5dba49ce4574d27
https://deploy-preview-1005--govuk-design-system-preview.netlify.com


Example for catalog dcat:themeTaxonomy

Do you have an example for dcat:themeTaxonomy, so I have an idea of how this could be populated?

http://ns.thedatatank.com/dcat/themes :-)

So http://eurovoc.europa.eu/5463 for biodiversity?

yes!

Great, done in e2cab624d794f948b39981449b1dd2f56619e8ac


.text and .partition_table range overlap on latest nightly

On Windows 10, using Nightly 11/29/2022, the .text and .partition_table range overlap, preventing bootloader from building:
    = note: rust-lld: error: section .text file range overlaps with .partition_table
            >>> .text range is [0xC5C, 0xDE1]
            >>> .partition_table range is [0xDBE, 0xDFD]

            rust-lld: error: section .text virtual address range overlaps with .partition_table
            >>> .text range is [0x7C5C, 0x7DE1]
            >>> .partition_table range is [0x7DBE, 0x7DFD]

            rust-lld: error: section .text load address range overlaps with .partition_table
            >>> .text range is [0x7C5C, 0x7DE1]
            >>> .partition_table range is [0x7DBE, 0x7DFD]

  error: could not compile `bootloader-x86_64-bios-boot-sector` due to previous error

I pulled commit 2ac7140 to make sure the issue is caused by an update in the toolchain, and previous versions failed to compile as well. The build passed on another Windows 10 pc running a Nightly from earlier this month, I will update on it as well to confirm the issue isn't device-specific.

Thanks for reporting! I think we fixed this error as part of https://github.com/rust-osdev/bootloader/pull/283, which is not merged yet. Could you try the release branch? The fixed version is also available on crates.io as  v0.11.0-beta.4.

Ah, it was even in with the fundy error, release branch compiles fine. I guess this issue will work for documenting the bug at least.

Thanks for testing! Yeah, this issue is definitely useful until we merge #283, thanks! I pinned it to the top of the issues list.

Thanks! Glad I can help some, still trying to learn more OS dev to directly contribute


feat(design): add quantity field component

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/graycoreio/daffodil/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?
Fixes: #295
What is the new behavior?
Created a component that will switch from a select element to an input element if the quantity selected is 10+.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

should be g2g now. The major changes are:

creates example components in design package
field and input components inherit the NgControl from the parent field instead of creating their own

@griest024 I put 70 in for the Custom Range Limits section and it's not throwing an error or defaulting to the max?

Fixed

@xelaint fixed


synchronize schema spec

What
APM agent json schema automatic sync
Why
Changeset

https://github.com/elastic/apm-server/commit/72d58a75c Allow indexing of empty service.type (https://github.com/elastic/apm-server/pull/8155)

:green_heart: Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-05-23T05:36:05.210+0000

Duration: 52 min 2 sec

Test stats :test_tube:

Test
Results

Failed
0

Passed
2891

Skipped
22

Total
2913

:green_heart: Flaky test report
Tests succeeded.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


CSV profile: null or empty?

While reading the data from file nbi is reading as empty.But when there is an empty without any delimiter it is reading as null.how to make the nbi to read null as well as empty string as null

Indeed, in a CSV file, when the content of the cell is empty NBi interprets it as (empty) but when the column is missing it interorets it as (null).
If you want to read (empty) or (null) values you should explicitely use these values in your CSV file. Check http://www.nbi.io/docs/compare-special-generic-values/ for more info.
You could also be interested by https://github.com/Seddryck/NBi/issues/216 but it's not implemented at this moment.
You could also request an upgrade of the CSV profile http://www.nbi.io/docs/config-profile-csv/ to take into account two additional attributes empty-cell and missing-cell with possible values (null) and (empty) (and (blank)).

The feature is implemented in #275
If interested/feedback please comment on this issue.


Correction of skipAssignment command that had wrong behaviour

Fixes #19
In SindarinDebugger, when you wanted to skip an assignment with the skip method; it was assigning nil to the variable that was supposed to be assigned, while you'd expect it to completely skip the assignment so that the assigned variable keep the same value as before the assignment.
Furthermore, to go over the assignment, the skipAssignmentNodeWith: was skipping an arbitrary number of bytes. As a result, sometimes, too many pc were skipped and some arguments were missing on the stack. In other cases, the replacement value that should have been assigned to the variable wasn't actually assigned.
To fix this, now, I've made a version skipAssignmentNodeCompletely that completely goes over the assignment by skipping the exact number of bytes there are in the bytecode that does the assignment. This version is used by default in the skip method.
I've also fixed the skipAssignmentNodeWith: so that the assignment is really made but with a replacement value pushed on the stack instead of the value that should have been assigned.

Now that the skip command actually works, I think it could be integrated again to the StDebugger advanced steps toolbar. What do you think?

@MarcusDenker @estebanlm
We do not have tests running for Sindarin?
How can I configure them?


Method longest_match

There is is_match that checks if there is a match for the given string, there is shortest_match that checks if there is a match and returns the length of the shortest match, but no method that checks if there is a match and returns the length of the longest match.
Re-using the shortest_match example, we would have:
let text = "aaaaa";
let pos = Regex::new(r"a+").unwrap().longest_match(text);
assert_eq!(pos, Some(5));

That's what find does.
(Well, technically find is "leftmost-first" or "preference-first." This crate doesn't implement POSIX "leftmost longest" semantics.)

And note also that shortest_match is perhaps not the best name: https://github.com/rust-lang/regex/issues/747

I was confused about what shortest_match did, sorry. I thought it stopped if the first character of the string didn't match the regex (and I thought the same about is_match). I suggest to change the example of shortest_match and have text be "baaaa" to illustrate that it's not the case. That would help clear the confusion for noobs like me who just discovered the crate.
Again sorry for the useless issue and thanks for the precision.


Revert Node.js update

See https://github.com/tibdex/github-app-token/pull/81#issuecomment-1701581938. I need more time to assess this change. Projects willing to use Node.js 20 can use 1.8.1.

You could consider releasing this as a breaking change?

I'm adding it back in #83, see https://github.com/tibdex/github-app-token/pull/81#issuecomment-1712289748.


enhancement/epoch-struct

suggested changes from @mandrigin not sure how resourceful it is since our refactoring. @mandrigin any opinions?

ping @mandrigin @adambabik


feat: new types added to widgets

Description
This Pull Request adds new types to the widgets.ts file, enhancing the usability of Deco Widgets for developers. With these changes, users can directly import the types into their code, simplifying widget development and maintenance.
Main Changes

Addition of new types with specific formatting:

TextArea: Represents a text area.
RichText: Represents formatted text.
ColorInput: Represents a color input, with a default value of #000000.
CSSCode: Represents CSS code.
TypescriptCode: Represents TypeScript code.
JSONCode: Represents JSON code.

Along with the existing types:

ImageWidget: Represents an image URI.
HTMLWidget: Represents an HTML string.
VideoWidget: Represents a video URI.
SiteRoute: Represents a dynamic route with options loaded from website/loaders/options/routes.ts.
MapWidget: Represents a map.

Justification
Importing these new types significantly improves the usability of Deco Widgets by:

Standardizing how different types of data are represented and manipulated.
Facilitating code maintenance and expansion, allowing developers to use specific types with predefined formatting.
Increasing code readability and clarity, helping new developers quickly understand how data is structured and used.

Usage Example:
If the user wants to import any Widget present in the documentation, they can simply import it through widgets.ts:

Expected Benefits

Improved Developer Experience: Directly importing types into the code simplifies developers' daily work.
Consistency and Maintenance: Standardized types make the code easier to maintain and expand.
Greater Code Clarity: Specific types make the code more readable and clear, aiding in quick understanding and onboarding of new developers.

Checklist

[x] Added new types to the widgets.ts file.
[x] Updated documentation with usage examples for each new type.
[x] Conducted tests to ensure the new types are functioning as expected.

If you need any changes or adjustments, feel free to let me know!

Awesome contribution @yuriassuncx <3

Awesome contribution @yuriassuncx <3

thx candeia <3
Is there any other type of widget that you find convenient to add? I saw that the date picker widget was recently launched

Is there any other type of widget that you find convenient to add? I saw that the date picker widget was recently launched
Thats a good question, I'll also take the opportunity to kindly ask you to contribute in our docs page: https://deco.cx/docs/en/developing-capabilities/section-properties/widgets#65830370-000

Here are the respective MD files:
en: https://github.com/deco-sites/starting/blob/main/docs/developing-capabilities/section-properties/widgets/en.md
pt: https://github.com/deco-sites/starting/blob/main/docs/developing-capabilities/section-properties/widgets/pt.md
Could you please update the docs page with the new widgets you've created?


scratchPercent attribute of view corrupts

UIView+Extensions.swift class line 47
// The alpha value is the last 8 bits of the data
let alphaValue = imageDataPointer[pixelDataPosition + 3]
Error: Thread 1: EXC_BAD_ACCESS (code=1, address=0x115668003)
Phone: Iphone 11
IOS Version: 13.2

Hi, will take a look in free time, was very busy this week. If you happen to find a fix earlier don't hesitate to open a PR :)

Hi,
when i changed the boundary points of for loop to
for x in 0...(width-1) {
for y in 0...(height-1) {
}}
it works fine since there is an bad access;
I will share the values of attributes when code corrupts;
width = 680
height = 524
x = 4
y = 524
Also I realize that performance of scratching is dramatically become worse, even iPhone 11, when I test in iPhone 6 scratching is very slow and scratch animation stuck

Any news on this one?


Install dependencies on import

Current Situation
When using pip install ucimlrepo and trying to interact with the dataset, the following libraries needed to be manually installed:

pandas
certifi

How it should be
When calling pip install ucimlrepo the dependencies should be installed with the repo.
How to fix
List the dependencies in the pyproject.toml file. Ideally, fix the installed version, so updates in the libraries don't break the behaviour of the repo.``

Thanks, it's been fixed

Thank you very much! This helps a ton as I try using ucimlrepo for my projects


Option to Specify Line Height as a Multiple of Font Size

Small usability tweak request:
It'd be really nice to be able to specify editor line height as a multiple of font size.
Pitch for why it's worth considering:

It'd be more consistent with the other line height settings in VSCode. (markdown.preview.lineHeight and terminal.integrated.lineHeight are both multipliers--only editor.lineHeight is absolute).
It would also unbreak dynamically resizing code on the fly, which is often important while communicating, like in teaching.
Seems like lots of people change this setting, since VSCode's spacing default is significantly bigger than most editors and people like seeing lots of code on the page. And this leads to confusion because most line spacing settings are a multiplier, in VSCode and elsewhere.

Being able to (optionally) specify the value in ems would solve the problem, while remaining backwards compatible. To give concrete examples, "15" could remain a valid value (implicitly in pixels), but 1.25em could also be a valid value that would rescale properly if the text size were changed.
Thank you for your consideration--and a truly excellent piece of software!

Good folk of #33968 (@smtnsk, @yume-chan, @luangong), if you still believe in VSCode line height being expressible as a ratio, is there any chance we could get your upvote here to get it over the finish line?
I think we've got a clean, backwards compatible way to do it, and just a few more days to get those last few votes.
(commenting here and tagging bc #33968 is locked)

One other really great idea from @appetite-j in #105888: Just autodetect and do the right thing for whichever the user enters. If line height is less than 4, assume it's a multiple of font size, otherwise assume it's an absolute size in pixels.

It might not be a perfect solution, but this feature can still be implemented using the existing setting:
"editor.lineHeight": 0, // Default - relative to fontSize 1.35
"editor.lineHeight": 1.5,// > 0 <= 3 - Relative line number (too small to be a viable absolute)
"editor.lineHeight": 25,// > 3 - Absolute value

To verify, configure editor.lineHeight to a value <8. The line height will be interpreted as a multiplier for editor.fontSize. For values above 8, the editor.lineHeight will be interpreted as the literal value of the line height.

It seems that setting editor.lineHeight to 8 results in it being interpreted in px. Can that be added to the setting description? I thought only values strictly above 8 would end up that way.


Unable to get sender in context function

If a function is passed to the context I would expect to be able to access all the values available in a context like sent. I think currently that function is only called once initial on startup of the api

Updating the title on this to be more specific to the bug.


Insights promoted item (Full width teaser)

I've updated the tests to use staticfiles.finders.find to check for the existence of the referenced static file.
I've also included a migration to create the initial categories.


Update ocp-buildconfigs.yaml

@kamillipka could you please restrict this PR scope to the changes directly contributing to Decision Service inclusion into the repository?
I see a lot of good changes (Dedupification, etc.). Similar changes were/are being introduced already and would cause conflicts.
Let's make this PR all about Decision Service.

Closed with https://github.com/karol-brejna-i/retailstoreofthefuture/commit/e0b77925ed5f5c2bb535ffdd4291574d1842297d
(manual conflict resolution and merge)


Updated strings

@yaichenbaum I think building and running the app to check for missing/corrupt strings would be beneficial here which I cannot do due to Microsoft pushing updates to VS indiscriminately without running proper unit tests nor checking if everything works properly... Could you assign someone that can actually build the app and run it who's not on v16.11.3?


Electron tests: project creation

The test should:

Click on the new Project button
Check the name is in the format project-nnn
Check 1 file and 1 folder are created (both for-real and the UI).
If it's the N+1 project, check that it's the proper numbered project (project-001, project-002, etc).
Repeat 10 times

This is basically the example test I created, I tweak it a little to match this better.

Will be closed by https://github.com/KittyCAD/modeling-app/pull/3315/commits/c17f0ab04fb50ffcdda92f258567eee7144c659a once we merge the electron branch


Composer install --no-dev failing with sf4 + flex

I fixed this here,
https://github.com/EasyCorp/easy-deploy-bundle/commit/45da26d38d1281ea9ff201bfaa03e854fbb5f64a
messed up the fork though, so can't create clean pullrequest (or at least I dunno  know how)
To make ti nice you woud replace the 'prod' with the symfony-env

this one hast it cleaner:
https://github.com/Wunderdata/easy-deploy-bundle-wunderfork/commit/35a3a31325e84d9e961723ab2779ab6df468add0

It is not bundle problem. You can move symfony/dotenv from dev deps, or just set env vars properly.
http://symfony.com/doc/current/best_practices/configuration.html

yep but you still have pass app_env manually to the "composer install"-call, otherwise the call will fail with
"symfony-cmd handling the auto-scripts event returned with error code 127"

You can set it (and other vars like APP_DEBUG) in ~/.profile or ~/.bashrc for user which doing deploy for example export APP_ENV=prod
Or just
set -a
. /path/to/project/.env
set +a

https://unix.stackexchange.com/questions/79064/how-to-export-variables-from-a-file

Yep true, thanks for the hint. I'm switching between prod and debug on
staging server though, so adding this directly to import command, using
value from symfony env, still makes sense for me, (and keeps config in one
place centralized, and makes composer use the env chosen in deploy-config,
regardless from server config) but I agree, this is no bug/issue of the
module then.
Am 06.12.2017 00:59 schrieb "zorn-v"<EMAIL_ADDRESS>You can set it (and other vars like APP_DEBUG) in ~/.profile or ~/.bashrc
for user which doing deploy for example export APP_ENV=prod
Or just
set -a. /path/to/project/.envset +a
https://unix.stackexchange.com/questions/79064/how-to-
export-variables-from-a-file
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/EasyCorp/easy-deploy-bundle/issues/35#issuecomment-349482489,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE3dLrUQ-s5bCYb4XpbDrFgCFnPs435eks5s9djHgaJpZM4QzK8D
.

I also have problems with Symfony 4 and .env file

@cve Have you found the solution to this problem? I have the same problem with Symfony 4.

@MSDATDE not yet

Does anyone has an example how to using this bundle with Symfony 4?

I ran into the same issue. Since #86 has not been merged yet I solved it by adding a command to the beforePreparing() hook as such:
public function beforePreparing()
{
   $this->runRemote(sprintf('cp {{ deploy_dir }}/repo/.env {{ project_dir }} 2>/dev/null'));
}

@PtrTn  I have made the same but still having an error afer composer install:
[KO]
  Script cache:clear returned with error code 1
  !!
  !!  In EnvVarProcessor.php line 162:
  !!
  !!    Environment variable not found: "APP_SERVER".


Manually calling React.PropTypes

I'm periodically seeing the following warning in my Chrome DevTools console:
warning.js:44 Warning: You are manually calling a React.PropTypes validation function for the `itemProps` prop on `Autowhatever`.
This is deprecated and will not work in the next major version.
You may be seeing this warning due to a third-party PropTypes library.
See https://fb.me/react-warning-dont-call-proptypes for details.

Whenever this happens, it happens a lot (like, slaughtered a goat in my console -- basically for all the props that use PropTypes). I looked at the react-autowhatever code and it didn't look like you were manually calling PropTypes. I wonder if it's static format that's throwing things off and instead PropTyes should move to a property on the constructor? (see https://facebook.github.io/react/docs/reusable-components.html#es6-classes )
I'm using:
react-autosuggest: 3.9.0
react: 0.14.8
webpack: 1.13.1
babel-core: 6.13.2
babel-preset-es2015: 6.13.2
babel-preset-react: 6.11.1

Bleh, ignore this: we had a bad shrinkwrap file that was inadvertently pulling in two versions of react (the other reason you can see this error message). Sorry for the bother.


Broken on React 18

Dependencies do not allow for React 18 and also require statement is used causing complete failure to compile in a standard create react app setup.

Hi @scott-cornwel, thanks for creating this issue.
As you could imagine, Yummygum is an agency where we're fully focussing on our client projects at this moment. We do not have any expecting plans in Q1 right now to revive the Flagpack project. We suppose to pickup the project in Q2 again and come with a solution to let Flagpack also work on React 18 versions!

Any update?

Any... Updates... ?

any updates?


small changes to services to work with spacy 1.6

There were a couple of small errors in the implementation of the /models and {model_name}/schema paths, a mistake in file naming for app.py (had displacy.server, needed displacy_service.server). Also a systematic problem with falcon and header strings, which work for me if provided as '...' but not if provided as b'....' .
The schema detection implementation still doesn't work, but returns a better error

Hi Chris,
Thanks a lot for this --- sorry I hadn't had a chance to look at your earlier questions.
About the header strings: I've had a lot of Python 2/3 trouble with this. Lately I've been using hug for our internals, which is only Python 3. It's hard to get all the details correct with just Falcon.
I'll have a look at the schema endpoint.
Best,
Matt


Add more tools

We already have some new tools available. They are still work in progress but already usable:

CSAF trusted provider => csaf_provider + csaf_uploader
Provider checker => csaf_checker
CVRF CSAF converter

@santosomar Could you please add them to the list?

@santosomar
We can also add CSAF Full Validator library and service and CSAF content management system.


Editor button tooltips

I have found that it is difficult to tell what some editor buttons do even after reading the manual because you forget :) Because there are no tooltips.
I have added the 'title' attribute to most of the buttons (I am not sure what clean markdown does?).
Of course they can't be translated this way (and it is cumbersome to translate text in JS so I wont bother). But it is still better to have some text than nothing. I copy/paste down the code from translations.js (only added title="" fields)
    $.fn.editableform.buttons = '' +
        '<button type="submit" title="Save changes" id="x-submit" class="editable-submit btn btn-sm btn-success"></button>' +
        ' <button type="button" title="Cancel changes" id="x-cancel" class="editable-cancel btn btn-sm btn-danger"></button>' +
        '  <button id="x-translate"  type="button" class="editable-translate btn btn-sm btn-warning hidden"></button>' +
        '<button id="x-nodash" type="button" title="Convert translation key to text" class="editable-translate btn btn-sm btn-warning hidden">❉  Ab</button>' +
        '  <button id="x-plurals" type="button" title="Generate plural forms" class="editable-translate btn btn-sm btn-warning hidden">|</button>' +
        '<button id="x-clean-markdown" type="button" class="editable-translate btn btn-sm btn-warning hidden"></button>' +
        '  <button id="x-capitalize" type="button" title="Uppercase the first character of each word in the string" class="editable-translate btn btn-sm btn-info">ab  Ab</button>' +
        '<button id="x-lowercase" type="button" title="Make the string lowercase" class="editable-translate btn btn-sm btn-info">AB  ab</button>' +
        '<button id="x-propcap" type="button" title="Make the string\'s first character uppercase" class="editable-translate btn btn-sm btn-info">A B  A b</button>' +
        '  <button id="x-copy" type="button" title="Copy text to simulated clipboard (page refresh clears contents)" class="editable-translate btn btn-sm btn-primary"></button>' +
        '<button id="x-paste" type="button" title="Paste text from simulated clipboard" class="editable-translate btn btn-sm btn-primary"></button>' +
        '  <button id="x-reset-open" type="button" title="Reset editor contents" class="editable-translate btn btn-sm btn-success"></button>' +
        '<button id="x-reset-saved" type="button" title="Load last published/imported value" class="editable-translate btn btn-sm btn-success"></button>' +
        '
 ';

@yurtesen, thank you. I will add these changes to the next release.

You should probably add something to "x-clean-markdown" button also. For now we wont be using translator much so I will be silent :) but I will make issues when I encounter more :p

Added translation pass-through from PHP to JS so that title strings could be translated into the selected interface language in Version 2.3.6


Can't filter out nests with mons/h > 100

Currently nests filter allows to filter in range 0-100 only. Even if set eg. 0-500 in default filter it still allows to filter out max 100 so I can't filter out eg. 100-500

What am I missing here?

How did you do that? I can't go beyond 100

    "nests": {
      "enabled": false,
      "polygons": false,
      "pokemon": false,
      "avgFilter": [
        0,
        500
      ]
    },

No idea why I had these ranges in config in one line and proly that's why it didin't work for me 🤔 Thanks


0.8.0 rc rebase 1

Modulus Pull Request
Description
First rebase after 0.8.0 release
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[ ] An issue is linked to this pull request.

Dependencies

/blossom-ci


Support overriding the default response

mountebank post-processes all responses in a protocol-specific way to ensure a valid default response in all cases, which includes the Connection: close header for http/s. Allow overriding the default response for an imposter.

closed as of 9821cdd


TypeScript drops inline comments on simple assignment expressions

TypeScript Version:  2.0.3 / nightly (2.1.0-dev.201xxxxx)
$ tsc --version
Version 2.0.8
Code
let x = /* foo */ (1);
let y = /* foo */ 1;
let z = 1 /* foo */;

Expected behavior:
var x = /* foo */ (1);
var y = /* foo */ 1;
var z = 1 /* foo */;

Actual behavior:
var x = (1);
var y = 1;
var z = 1;

This is not a huge problem for most user code, but in tsickle we're adding comments that represent Closure Compiler casts for type assertions, e.g.:
let x = /** @type {string} */ (someExpr);

Which this behaviour breaks.

Actually a duplicate of #9873


My-Calc-App: Milestone-1

I set up the initial files for milestone one of the calculator project with React.
In Milestone 1, we are supposed to set up the basic project structure including:

Use create-react-app to initialize a new React app
Delete any unnecessary file or asset
Add prop-types
Add big.js
Run the application with npm start and make sure that everything works correctly.
deploy the app to Heroku following the instructions in create-react-app-buildpack
Initialize a git repo
Create a Heroku app
Commit and deploy to Heroku and make sure the Heroku app works correctly
Push everything to Github

I resolved conflicts in order to follow the TSE comments, but it means that this branch was automatically merged.


New files added to a folder do not show up in the generated templates

Describe the bug
From Marisol R at Vanderbilt:
I can generate the metadata spreadsheet now, but the spreadsheet only shows the older files, not the ones uploaded on 08/2021. The recently uploaded file names should be in the metadata spreadsheet for us to fill out, correct?

One of the folders that contains the old (February) files and new (August) files are here: https://www.synapse.org/#!Synapse:syn23564801
To Reproduce
Steps to reproduce the behavior:

Go to Data Curator App
Select "Project":"HTAN Vanderbilt", "Folder":"single_cell_RNAseq_level_1", "Template":"scRNA-seq Level 1"
Click the three arrows to go to the generate template page
Click the purple "Click to Generate Google Sheets Template" button
Click on the link it generates
Template doesn't contain the newest files uploaded in August

Expected behavior
The generated template should contain both the older and newer files that were uploaded for centers to annotate.
Additional Notes
Ideally have this fix in place by early October 2021

schematic should handle the generation of a google sheet when there is no manifest present and when there is a manifest present in a given dataset folder. schematic will return a url to the resulting google sheet. The DCA should only need to call schematic's populate manifest function, w/o having logic to decide whether an empty or pre-populated google sheet has to be generated.

@rrchai you can take a look at the updated PR 523  in schematic.
Instead of calling populateModelManifest, you should be able to call getModelManifest the same way as you do here.
The new files should be appended at the end of the manifest. Currently all fields other than filename and entityId are left blank (i.e. empty string).
To test in schematic for the dataset referenced above in this issue:
schematic manifest -v INFO --config ./config-htan.yml get --data_type ScRNA-seqLevel1 --title scRNA-seqLevel1 -d syn23520241 --oauth --sheet_url
Output here:
https://docs.google.com/spreadsheets/d/19BH8yUc8AtmVVPaYajdwUDMkVPOR-jmuNPm8WGP4TVs/edit#gid=0

@ychae thank you for the detailed bug description across these issues (e.g. #190, #192 and #193) :)

@milen-sage @rong I just tested and I see a lot blank rows and then once I scroll down I see the old file names. If I scroll over to the right though, I can see all of the SynapseIDs.
Blank file names to filled in old file names:

Filled in columns, including Synapse IDs for all files:

@ychae I see the biospecimen component there. Aren't these files single cell?
If the files are single cell, could you try selecting single cell RNA seq in the template dropdown?
Biospecimen is not a file-based data type, and the expected behavior is different wrt to pulling updated list of files (i.e. files do not apply to Biospecimen data; e.g. the data model doesn't include the attribute Filename for Biospecimen).

@milen-sage it's really odd, but I selected the correct scRNA-seq Level 1 template and that's what it generated. Here's the screenshot of the dropdown values

:

@rrchai has accidentally submitted a Biospecimen manifest for the Vanderbilt folder while testing today. I restored Vanderbilt's manifest. @ychae could you test the app again?

Whoo-hoo! Looks good! Love it when it's an easy fix 😁
I can see the annotated old files and the filenames of the new files, with no annotations. Looks good to share with Marisol.
Thanks Rong! 🎉  Thanks Milen! 🙌

@ychae Good catch!! And thank you @milen-sage for a quick fix.
I realized when I was testing submission function, I accidentally submitted some files from other project to the Vanderbilt scRNA_seq_level1. If I remember correctly, it only originally contains synapse_storage_manifest.csv and FASTQ_raw.
@milen-sage Is it possible to restore the folder/delete other extra files?
Sorry about the mistake!

Yes, we can delete the unneeded entities.

closes the issue since it's been fixed. Feel free to reopen if the issue remains


Update how-to-auto-train-nlp-models.md

Changed enable long range text feature to show that default is true, and to label as false as needed

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

#sign-off

@ssalgadodev: I'm sorry - only the author of this article, @wenxwei, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@wenxwei
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
#assign:@MicrosoftDocs/public-repo-pr-review-team

The following users don't have valid GitHub IDs, or are not collaborators on this repo: microsoftdocs/public-repo-pr-review-team

#sign-off


Do you happen to achieve real time answers ?

Hey really great project !
Right now for my project I'm using this tool because it's handy. However it takes a bit time to get the answer from OpenAI, I don't know how to speed up things. on OpenAi playground the answers are real-time, the same for the chatGPT website.
I understand it their tech and it is hosted on their website, so there is nothing we can do.
OR maybe I'm doing something really bad and unoptimized and that's why I don't get real time answers.

Funnily enough I just came here to check if this code supported "streaming", the ChatGPT API allows you to parse a boolean called "stream" which then streams the results back to you rather than waiting for the entire chat to complete which really speeds things up. I just checked the code and this doesn't currently have streaming implemented.

Hey thank you for the information !
I hope this repo will add the streaming functionality.
@SeanBannister another repo/code that allows streaming ?

Sorry @tony-wolff, I'm not actively updating this repo currently. It might be hard for me to find time to add streaming support.

I did do a little research to see what else was out there but haven't had a chance to test anything, this one supports streaming according to its changelog https://github.com/mochi-neko/ChatGPT-API-unity


Remove unused file VcfHeaderUtils.scala

Fixes #428

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/1116/
Test PASSed.

Thanks @heuermh! Merged as https://github.com/bigdatagenomics/adam/commit/2e843de7d1c0a3185fd0e7a9a3c65eef07ae4ad3.


TileProviders with Json sources instead of directly to pbf/image files

What should be done with a Map Style like this, which link to sources that are Json files too, which show the correct way to access the data (pbf/image) files (example)?
I tried using the urlTemplates given in the secondary Json sources (such as in the above example: https://israelhiking.osm.org.il/vector/data/IHM/{z}/{x}/{y}.pbf) instead of the Json files, but I get an InvalidProtocolBufferException: Protocol message tag had invalid wire type..
Any ideas? Am I doing something wrong? (Thanks a lot for this great plugin, by the way)

If you open the json file in a web browser, you'll find the URL template to use for vector tiles.
e.g.
    "IHM": {
      "type": "vector",
      "url": "https://israelhiking.osm.org.il/vector/data/IHM.json"
    },

if you look at https://israelhiking.osm.org.il/vector/data/TerrainRGB.json you'll find:
"tiles":["https://israelhiking.osm.org.il/vector/data/IHM/{z}/{x}/{y}.pbf"]

From there the urlTemplate is https://israelhiking.osm.org.il/vector/data/IHM/{z}/{x}/{y}.pbf
good luck!


Support loading of files from USB

From #199

Also i can't load the m3u from my usb storage key, your program tell me that it don't find the file after i have selected it, i have to copy and paste it to internal memory to get it(file loading) working

The USB storage issue is probably due to Android-specific issues around external storage devices. I'd say that's a low priority fix.

maybe i can run adb on my box to see what happened in logcat ? would it help ?

I imagine it'll give some File Not Found problem. USB support would require some more complex file I/O implementation that I'd prefer to avoid doing myself.


If not then when you will be finished it with?

Did you get a chance to reply?

Hi @abhisheka1993
The ETA for updating QRDA-III to 2023 is around end the October to early November this year.

Are you done with qpp conversion tool 2023 updates?
If not then when you will be finished it with?

Are we closer to a date for the qpp conversion tool 2023 updates?

Any updates ?


Parse and dump typed-stack DW_OPs

Firefox libxul.so built optimized by gcc 7.2.1 contains some of these, using the GNU opcodes but AFAIK the GNU versions are identical to what's specified in DWARF5.
The DWARF5 spec is a bit vague about how typed values work. Looking at the examples in libxul, they are all computing values for optimized-away floating point variables; the base_type is always double. Apparently evaluation of these expressions is supposed to use floating-point arithmetic.
I haven't added evaluation support for these opcodes because we haven't needed it yet. For now I would like to be able to dump libxul's DWARF data without warnings about unknown opcodes. Later on we will probably need to add support for floating point evaluation (assuming IEEE754 non-exception semantics I suppose). How things are supposed to work for non-floating-point types is anyone's guess.

How things are supposed to work for non-floating-point types is anyone's guess

2.5.1 discusses it briefly.  Basically operations can either be done in one of the base types, or they can be done in the "generic type", which basically means "what DWARF 4 did".
I started working on this here https://github.com/tromey/gimli/commits/dwarf-5-eval but never finished.  I have no recollection if anything there is useful.  It certainly doesn't work nor even compile.

I just spotted section <IP_ADDRESS> saying

Operations other than DW_OP_abs, DW_OP_div, DW_OP_minus, DW_OP_mul, DW_OP_neg and DW_OP_plus require integral types of the operand (either integral base type or the generic type).
Unfortunately the set of base types is rather large; implementing typed evaluation in full generality would require for example supporting scaled encodings and decimal string encodings.

Coverage increased (+0.07%) to 92.592% when pulling 5d3d5c1a6fd04ac0ed5b114cb6131d423ebff035 on rocallahan:typed-stack into 3f82ff29f7c6bbfdc8e2529e0657b1364cb0af89 on gimli-rs:master.

Collapsing TypedLiteral into Literal has quite far-reaching consequences.
It means that the value part of Literal becomes a Vec<u8>, so every parsed Literal has a heap allocation.
It also means that every time we construct a Literal we have to pass in an address_size and a Reader (or at least an Endianity) so that we can convert the literal value into a Vec<u8> whose size and endianness matches the target architecture.
And of course when evaluating a Literal we have to parse the Vec<u8> back into a u64 (or whatever we end up using to handle arbitrary base types).
Please confirm that this is all OK.

This also means that Operation is no longer Copy. With TypedLiteral it was still Copy because the TypedLiteral payload was a Reader reference, not a Vec.
I guess we could avoid a lot of these problems by making Literal's payload be either a Reader reference or a u64. Is that really better than separating Literal and TypedLiteral, though?

Please give me some guidance.

Definitely don't want a Vec in Operation, and I don't think it's a good idea to artificially munge values just so that they have a common representation. If TypedLiteral's value was only a u64 then collapsing them would be great, but I don't think we can do that.

The compromise option is to make Literal be
    Literal {
        /// The DIE of the base type (0 meaning 'generic type')
        base_type: UnitOffset<Offset>,
        /// The value to push.
        value: LiteralValue<R, Offset>,
    },

#[derive(Debug, Clone, Copy, PartialEq, Eq)]
pub enum LiteralValue<R, Offset = usize>
where
    R: Reader<Offset = Offset>,
    Offset: ReaderOffset,
{
    U(u64),
    Bytes(R),
}

Is that better than what I have in the PR, or not?

The goal of collapsing them should be to make the evaluator code simpler, and I don't think doing that helps (it even makes it worse because it adds some base_type/value combinations that aren't possible in practice). I think what you have in the PR is fine. It can be changed later if needed when the evaluation is implemented.

Thanks.
I should still collapse TypedDeref and TypedRegister, right?

Even there I'm not sure that helps the evaluation code, but I don't feel strongly either way. At some point in the evaluation, all of these operations need to result in a typed value, but my gut feeling is that doing this in the operation parsing is too early. Maybe @tromey has a better idea though.

I've pushed an update that collapses TypedDeref and TypedRegister into Deref and Register.
It won't help evaluation much but I think it does make thing slightly simpler.


Building DIDs list...
Error occurred somewhere, it was caught! TypeError: this.module.newOnchain is not a function
at DIDModule.createNewOnchainTx (/Users/xxxxx/Downloads/sdk-master/src/modules/did/did.js:143:24)
at DIDModule.new (/Users/xxxxx/Downloads/sdk-master/src/modules/did/did.js:167:12)
at registerNewDIDUsingPair (/Users/xxxxx/Downloads/sdk-master/tests/integration/helpers.js:25:25)
at createDockDID (/Users/xxxxx/Downloads/sdk-master/example/resolver.js:55:32)
at main (/Users/xxxxx/Downloads/sdk-master/example/resolver.js:78:25)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
error Command failed with exit code 1.

Can you share your docker image id and SDK version because this.module.newOnchain is not a function  suggests an old docker image?

Creating DID resolvers...
Building DIDs list

The output logs suggest you're running yarn did-resolver-example and not yarn dock-did-example. Secondly using the mainnet tagged docker images to run examples and tests isn't a good idea as it will cost you real tokens.

SDK version: master
dock-substrate: version 0.22.0

Can you share the most recent block on your node? The TypeError might be because your local node doesn't have the recent blocks (last few months) and as per your local state, newOnchain is not an extrinsic as it was only introduced a few months ago.

i also have this problem on mainnet, docker image log is:

then i run connect command:
docker run -p 9944:9944 -p 30333:30333 docknetwork/dock-substrate:mainnet --chain ./cspec/knox_raw.json --ws-external --enable-offchain-indexing=true

then run yarn dock-did-example that throws this.module.newOnchain is not a function error. But not throw this error on testnet.


https://saltpack.org has been down a day

Returns 502 to Cloudflare.

Looks ok to me

Seems to be a problem for ip6 only.
w$ curl -v -6 https://saltpack.org
*   Trying [2406:da00:ff00::3405:3b03]:443...
* Connected to saltpack.org (2406:da00:ff00::3405:3b03) port 443
* ALPN: curl offers h2,http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
*  CAfile: /opt/local/share/curl/curl-ca-bundle.crt
*  CApath: none
* OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to saltpack.org:443
* Closing connection
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to saltpack.org:443

...whereas
$ curl -v -4 https://saltpack.org succeeds.


InvalidCastException randomly thrown in WinHttpHandler

I haven't been able to repro this since it occured, but am looking into seeing what caused this.
fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[0]
      An unhandled exception has occurred while executing the request
System.InvalidCastException: [A]<>f__AnonymousType0`3[System.Net.Http.HttpRequestMessage,System.Guid,System.Int64] cannot be cast to [B]<>f__AnonymousType0`3[System.Net.Http.HttpRequestMessage,System.Guid,System.Int64]. Type A originates from 'System.Net.Http.WinHttpHandler, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' in the context 'Default' at location 'C:\Users\hugh\.nuget\packages\system.net.http.winhttphandler\4.3.0\runtimes\win\lib\netstandard1.3\System.Net.Http.WinHttpHandler.dll'. Type B originates from 'System.Net.Http, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' in the context 'Default' at location 'C:\Program Files\dotnet\shared\Microsoft.NETCore.App\1.1.2\System.Net.Http.dll'.
   at Microsoft.ApplicationInsights.DependencyCollector.Implementation.PropertyFetcher.PropertyFetch.TypedFetchProperty`2.Fetch(Object obj)
   at Microsoft.ApplicationInsights.DependencyCollector.Implementation.HttpCoreDiagnosticSourceListener.OnNext(KeyValuePair`2 evnt)
   at System.Diagnostics.DiagnosticListener.Write(String name, Object value)
   at System.Net.Http.HttpHandlerDiagnosticListenerExtensions.LogHttpRequestCore(DiagnosticListener diagnosticListener, HttpRequestMessage request)
   at System.Net.Http.WinHttpHandler.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpMessageInvoker.SendAsync(HttpRequestMessage request, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.SendAsync(HttpRequestMessage request, HttpCompletionOption completionOption, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.GetAsync(Uri requestUri, HttpCompletionOption completionOption, CancellationToken cancellationToken)
   at System.Net.Http.HttpClient.GetStringAsync(Uri requestUri)
   at System.Net.Http.HttpClient.GetStringAsync(String requestUri)
   at Facebook.GraphClient.<ExecuteRequest>d__20`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Facebook.GraphClient.<GetPage>d__18`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at AsiaChat.Controllers.PageController.<VerifyFacebookPage>d__19.MoveNext() in C:\Users\hugh\Documents\GitHub\asia-chat\src\backend\AsiaChat.WebAPI\Controllers\PageController.cs:line 232
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at AsiaChat.Controllers.PageController.<Update>d__16.MoveNext() in C:\Users\hugh\Documents\GitHub\asia-chat\src\backend\AsiaChat.WebAPI\Controllers\PageController.cs:line 176
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeActionMethodAsync>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextActionFilterAsync>d__25.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextExceptionFilterAsync>d__24.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ExceptionContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResourceFilter>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ResourceExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.<Invoke>d__7.MoveNext()
info: Microsoft.AspNetCore.Hosting.Internal.WebHost[2]
      Request finished in 1851.0059ms 500 text/html; charset=utf-8

This is actually an issue in HttpClient - see https://github.com/dotnet/corefx/issues/22251


Skytrix123 get set improvements

@skytrix123 I don't think this is good approach, because it creates ambiguous behaviour in get by giving it two responsibilities. What if an ID is also an attribute? It's better to keep multiple responsibility to a minimum.
You can also achieve this with find, eg collection.find({id: 1}), which returns the first it can find that matches the given attributes.

@rtheunissen I woke up now and released the same thing, totally forgot about find, but you were faster and you respond to request before i removed it :/

@skytrix123 no problem at all, thanks for putting in the time to suggest a change. 👍


Stlye of dashboardv3 is out of date

Changes need to be pull in to spacing, borders and a few other things.
Remove border under the header: http://bit.ly/AAJJjS
Add spacing to header and left nav: http://bit.ly/xEuU1p vs http://bit.ly/A7ouVf
Add gradient to app cards (large and small): http://bit.ly/xOKv0G --> http://bit.ly/zQuNGp

This is fixed.


Fira Code font symbols missing in vscode windows 10

{
    "terminal.integrated.shell.windows": "C:\\msys64\\usr\\bin\\fish.exe",
    "terminal.integrated.env.windows": {
        "MSYSTEM": "MSYS"
    },
    "terminal.integrated.fontSize": 16,
    "terminal.integrated.fontFamily":"Fira Code",
    "editor.fontSize": 16,
    "editor.fontLigatures": true,
    "editor.fontFamily":"Fira Code",
    "git.path": "C:\\git\\bin\\git.exe",
}

Also tried Fira Mono for Powerline but I can't seem to figure out how to display the last character in my case golang symbol
Second, In PowerShell terminal the arrow doesn't seem rendered correctly

Fira Code was used for git branch symbol, Which is correctly rendered on VS Code. Go lang section use emoji and that's the one displayed as boxes. Windows have terrible support for Unicode symbols.
I don't use Windows, So until any fellow Windows users are able to help, You could customize it with SPACEFISH_GOLANG_SYMBOL.

Ok thx, what about the arrow in Powershell is it also a emoji?

The arrow isn't an emoji, though it is in the UTF-8 character set. It looks like you have to enable UTF-8 explicitly in Powershell with chcp 65001 (details here).

Can't believe windows still doesn't use UTF-8 by default...
Now I can see UTF-8 chracters that I type but arrow still seem to go trough something else.

Are you using a powerline font as well in Powershell?

Heya! :rainbow::sparkles:
This doesn't exactly seem like an Spacefish-specific issue and I don't believe anyone here will be able to help other than upstream. (Best of luck with the issue you've replied to above!)
As @salmanulfarzy said earlier, if you have another symbol that works in the meantime that you'd like to use, you can add set SPACEFISH_GOLANG_SYMBOL 🌮 to your ~/.config/fish/config.fish to override the default arrow icon with a taco.
If you have any further topic-related questions, feel free to ask, but this issue should be closed and I'll add the appropriate tags. :two_hearts:


Program to check a string a pangram or not issue#925

issue #925
I have added the code in Code/Python check pangram.
Please review it!
Thanks!!

Kindly review my PR @raksha009 .
Thanks!

Plz link yr code with respective folder :). Go through the guidelines and the pinned messages

@raksha009 I have linked the code. Kindly review !
Thanks:)

@raksha009 Made all the required changes! Please review!
Thank You!


[Test Automation] - Jenkins job for automated release testing

Jenkins job for automated release testing

Jenkins job for running release tests has been implemented.


Fibers and Helidon

Investigate Fibers in Java and see what could be done with Helidon SE and Helidon MP in that area.

Main areas of interest:

Sockets integration (HTTP server, gRPC server)
File system integration (file I/O)
Database drivers

We are talking about project Loom
Overview: https://www.youtube.com/watch?v=vbGbXUjlRyQ
Demo: https://youtu.be/Csc2JRs6470?t=1699
Update: https://www.youtube.com/watch?v=z_tus_m-6FI

Assigning to @ljnelson as you already work on this issue


Typo fix sonarqube/README.md

Some sentences miss the "." at the end.
This PR is a recreation of PR #4958 .

/assign @rjkernick

/ok-to-test

/lgtm

Sorry, gotta merge in master one more time

@rjkernick
Some PR changed the yaml 2 minutes earlier to your proving to this PR.
I've create it again to PR #5045. Let's close this one. :)


[ui] Make message for custom cluster requiring all three roles more visible

Currently the text is grey in a grey box, enhance the message and make it more visible that rancher requires all three roles to be assigned in the cluster before rancher will finish provisioning the cluster.

This should be quick & easy.

on 2.5-head commit id: 42f722b79 and master-head commit id: a2fc4555


Please add admin .waifureset command

Please add the ability for an admin to manually reset the waifuinfo of an individual.  The only commands I can find right now is to either purge all data, or have the person reset it themselves.
Story goes that my clanmates were talking about how no one would ever be able to afford a spaceship.  I bragged that I could, and bought a spaceship (by giving myself currency) for our old clan leader who has and will be gone for the military for some time.  Didn't even think at the time that it would mess with the leaderboards, and now my clanmates are pissed at me ><

http://feathub.com/Kwoth/NadekoBot :thinking:

I'll make a post on there.  Thanks, shivaco.

You can close the issue fam :P


Nexus 9 - Bug Report

Reported Bugs

[ ] I had the app crash after install using the following steps on my Nexus 9:
Install APK
Launch App
Go to Configuration Screen

Now it seems fine. Maybe a timeout issue on pulling the JSON files?

Include JSON file with APK

File was already included with APK. The long update time comes from creating a SQL database using the JSON file. The settings page therefore needs to be modified to use the JSON directly.


PR checking for forks triggered by a comment

Acceptance Criteria

ability to trigger tests for a PR from a fork using a comment from a person that has write access to the repo (approval from someone with write access could work too)
PRs without approval or a comment must not be automatically checked

Blocked by #1144

https://github.community/t/github-actions-manual-trigger-approvals/16233/64 has a thing for triggering on approval

Let's use the solution linked by @mook-as

@viovanov isn't this done when using the pr-request label?

implemented


can't be running

on OS X version 10.11.3 Beta can't be running

@dragon-del we are fixing an issue where Code will not start with a non-US keyboard layout like Japanese. If you set it to english, then launch Code and then switch back, you can workaround. Fix will be available soon.


Kaban

Added Kaban images
Added Kaban boss translations
Added Kaban boss data
Fix boss with no health data

Also:

Filter null values from containsItems array

.deploy

.deploy


CMake __BUILD_FOR_R fails to find R source files

The CMake build has an option to build for R which was working some versions ago, at least under windows:
https://github.com/microsoft/LightGBM/blob/6e78e697f8e27d4bbf493a0ebd9134c3254a2ecd/CMakeLists.txt#L23
Building with this option by calling cmake directly with -D__BUILD_FOR_R=1 -DCMAKE_R_VERSION=<version> without using the build_r.R script is not working anymore, since it assumes that the R package files are under the same directory as the rest of the source files:
CMake Error at CMakeLists.txt:358 (add_library):
  Cannot find source file:

    src/lightgbm_R.cpp

  Tried extensions .c .C .c++ .cc .cpp .cxx .cu .mpp .m .M .mm .ixx .cppm
  .ccm .cxxm .c++m .h .hh .h++ .hm .hpp .hxx .in .txx .f .F .for .f77 .f90
  .f95 .f03 .hip .ispc

CMake Error at CMakeLists.txt:358 (add_library):
  No SOURCES given to target: _lightgbm

CMake Generate step failed.  Build files cannot be regenerated correctly.

Building with the latest MSVC using the CI script build_r.R under the VS developer console is not working either, since it doesn't recognize all the installed versions - for example, if I use vs2022 in windows 10, I get this error as it tries to look for a windows 8.1 version (note that this doesn't happen when calling cmake directly):
installing via 'install.libs.R' to C:/Users/david/AppData/Local/R/win-library/4.3/00LOCK-lightgbm/00new/lightgbm
Trying 'Visual Studio 16 2019'
-- Configuring incomplete, errors occurred!
CMake Error at CMakeLists.txt:33 (PROJECT):
See also "C:/Users/david/AppData/Local/Temp/Rtmpk3gflg/R.INSTALLafc1e183436/lightgbm/src/build/CMakeFiles/CMakeOutput.log".
  Generator

    Visual Studio 16 2019

  could not find any instance of Visual Studio.

Trying 'Visual Studio 15 2017'
-- Configuring incomplete, errors occurred!
CMake Error at CMakeLists.txt:33 (PROJECT):
See also "C:/Users/david/AppData/Local/Temp/Rtmpk3gflg/R.INSTALLafc1e183436/lightgbm/src/build/CMakeFiles/CMakeOutput.log".
  Generator

    Visual Studio 15 2017

  could not find any instance of Visual Studio.

Trying 'Visual Studio 14 2015'
-- Configuring incomplete, errors occurred!
CMake Error at CMakeLists.txt:33 (PROJECT):
See also "C:/Users/david/AppData/Local/Temp/Rtmpk3gflg/R.INSTALLafc1e183436/lightgbm/src/build/CMakeFiles/CMakeOutput.log".
  Failed to run MSBuild command:

    MSBuild.exe

  to get the value of VCTargetsPath:

    MSBuild version 17.9.8+b34f75857 for .NET Framework
    Build started 5/6/2024 7:21:50 PM.

    Project "C:\Users\david\AppData\Local\Temp\Rtmpk3gflg\R.INSTALLafc1e183436\lightgbm\src\build\CMakeFiles\3.24.3\VCTargetsPath.vcxproj" on node 1 (default targets).
    C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\x64\PlatformToolsets\v140\Toolset.targets(36,5): error MSB8036: The Windows SDK version 8.1 was not found. Install the required version of Windows SDK or change the SDK version in the project property pages or by right-clicking the solution and selecting "Retarget solution". [C:\Users\david\AppData\Local\Temp\Rtmpk3gflg\R.INSTALLafc1e183436\lightgbm\src\build\CMakeFiles\3.24.3\VCTargetsPath.vcxproj]
    Done Building Project "C:\Users\david\AppData\Local\Temp\Rtmpk3gflg\R.INSTALLafc1e183436\lightgbm\src\build\CMakeFiles\3.24.3\VCTargetsPath.vcxproj" (default targets) -- FAILED.

    Build FAILED.

    "C:\Users\david\AppData\Local\Temp\Rtmpk3gflg\R.INSTALLafc1e183436\lightgbm\src\build\CMakeFiles\3.24.3\VCTargetsPath.vcxproj" (default target) (1) ->
    (Desktop_PlatformPrepareForBuild target) ->
      C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Platforms\x64\PlatformToolsets\v140\Toolset.targets(36,5): error MSB8036: The Windows SDK version 8.1 was not found. Install the required version of Windows SDK or change the SDK version in the project property pages or by right-clicking the solution and selecting "Retarget solution". [C:\Users\david\AppData\Local\Temp\Rtmpk3gflg\R.INSTALLafc1e183436\lightgbm\src\build\CMakeFiles\3.24.3\VCTargetsPath.vcxproj]

        0 Warning(s)
        1 Error(s)

    Time Elapsed 00:00:00Warning in eval(ei, envir) :.15

  Exit code: 1

  Building with Visual Studio failed. Attempting with MSYS2
CMake Error: Error: generator : MSYS Makefiles
Does not match the generator used previously: Visual Studio 14 2015
Either remove the CMakeCache.txt file and CMakeFiles directory or choose a different binary directory.
CMake Error: Error: generator : MSYS Makefiles
Does not match the generator used previously: Visual Studio 14 2015
Either remove the CMakeCache.txt file and CMakeFiles directory or choose a different binary directory.
Error in .run_shell_command("cmake", c(cmake_args, "..")) :
  Command failed with exit code: 1
* removing 'C:/Users/david/AppData/Local/R/win-library/4.3/lightgbm'
Error in .run_shell_command(install_cmd, install_args) :
  Command failed with exit code: 1
Execution halted

Thanks for reporting this.

Building with this option by calling cmake directly with -D__BUILD_FOR_R=1 -DCMAKE_R_VERSION= without using the build_r.R script is not working anymore

If that ever worked before, it was by accident.
__BUILD_FOR_R is not intended to be part of the public API of this project's CMake build. It's intended only for use by the build_r.R script.
Use build_r.R to drive CMake-based builds of this project's R package.

Building with the latest MSVC using the CI script build_r.R under the VS developer console is not working either

Could you clarify what "using ... build_r.R under the VS developer console" means specifically? Does that just mean running Rscript build_r.R from a terminal inside Visual Studio, or something else? I'm sorry if that's a silly question, I personally am very unfamiliar with the Visual Studio IDE on Windows.

I get this error as it tries to look for a windows 8.1 version

I wonder if this is a difference between the cmake that's bundled with RTools and the one that you are using outside of R stuff? I'd observed some similar issue when working on #6213 and the related things a few days ago. Don't have logs available right now, will try to chare them when I can.

By "VS developer console", I mean the start menu entry named "Developer Command Prompt" which is added after installing some msvc tool such as "visual studio build tools", which consists of the regular windows command prompt with all msvc-related environment variables pre-loaded.

__BUILD_FOR_R is not intended to be part of the public API of this project's CMake build. It's intended only for use by the build_r.R script.

From what I can tell the build_r.R script doesn't use this option.

I wonder if this is a difference between the cmake that's bundled with RTools and the one that you are using outside of R stuff? I'd observed some similar issue when working on #6213 and the related things a few days ago. Don't have logs available right now, will try to share them when I can.

I get the same error when using the cmake that comes bundled in RTools 4.3.

Thanks for that explanation of Visual Studio and for checking the cmake bundled in RTools, much appreciated!

From what I can tell the build_r.R script doesn't use this option.

This one is very subtle/complex, I can explain!
build_r.R creates a lightgbm_{version}.tar.gz source distribution of the R package which includes src/install.libs.R.
https://github.com/microsoft/LightGBM/blob/f539536073f49dd2d266d8bd5cf7bbed6441a862/build_r.R#L193-L197
That src/install.libs.R then formats a CMake configure command and includes -D__BUILD_FOR_R.
https://github.com/microsoft/LightGBM/blob/f539536073f49dd2d266d8bd5cf7bbed6441a862/R-package/src/install.libs.R#L177
That install.libs.R is a rarely-used but supported alternative to using CMake or autotools directly in an R package. See https://cran.r-project.org/doc/manuals/R-exts.html#Package-subdirectories.