vmat_c Error decoplile

Describe the bug
Failed to extract Features file for 'csgo_environment' does not contain a parameter named 'g_tAmbientOcclusion'
Expected behavior
Decompile .vmat_c to vmat
Relevant log output or exception with stacktrace
18:48:24.508] [ExtractProgressForm] Failed to extract 'gris_1024_shiny.vmat_c': System.IO.InvalidDataException: Features file for 'csgo_environment' does not contain a parameter named 'g_tAmbientOcclusion'
   at ValveResourceFormat.IO.ShaderDataProvider.GetInputsForTexture_Internal(String textureType, Material material) in /_/ValveResourceFormat/IO/ShaderDataProvider.cs:line 165
   at ValveResourceFormat.IO.ShaderDataProvider.GetInputsForTexture(String textureType, Material material) in /_/ValveResourceFormat/IO/ShaderDataProvider.cs:line 31
   at ValveResourceFormat.IO.MaterialExtract.GetTextureUnpackInfos(String textureType, String texturePath, Boolean omitDefaults, Boolean omitUniforms)+MoveNext() in /_/ValveResourceFormat/IO/MaterialExtract.cs:line 138
   at ValveResourceFormat.IO.MaterialExtract.ToValveMaterial() in /_/ValveResourceFormat/IO/MaterialExtract.cs:line 200
   at ValveResourceFormat.IO.MaterialExtract.ToContentFile() in /_/ValveResourceFormat/IO/MaterialExtract.cs:line 49
   at ValveResourceFormat.IO.FileExtract.Extract(Resource resource, IFileLoader fileLoader, IProgress`1 progress) in /_/ValveResourceFormat/IO/FileExtract.cs:line 174
   at GUI.Forms.ExtractProgressForm.ExtractFile(Resource resource, String inFilePath, String outFilePath, Boolean flatSubfiles) in /_/GUI/Forms/ExtractProgressForm.cs:line 406

What game does this happen in
CS2
Reference file in a Source 2 game
materials/lego/gris_1024_shiny_color.vmat_c
What version of VRF are you using?
10.2.3935 b817e1d47010c8ef0a41e359965d9d28a81dce66 on Microsoft Windows NT 10.0.19045.0 (GPU: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2, Driver: 4.6.0 NVIDIA 566.03)

Did csgo_environment remove support for amient occlusion in one of the recent updates?

No

Did csgo_environment remove support for amient occlusion in one of the recent updates?

No

I think it packs the textures differently then. (This can be seen in compiled textures tab)

I think it packs the textures differently then. (This can be seen in compiled textures tab)


gnomeExtensions.dash-to-dock: v61 -> v62

Motivation for this change
A new version is out. Changelog here. Manually tested.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

@GrahamcOfBorg build gnomeExtensions.dash-to-dock

Success on aarch64-linux (full log)
Partial log (click to expand)
rm -fR _build
echo done
done
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/4b9vgpy7wvlnlvpapdm7gs6kjvsri32c-gnome-shell-dash-to-dock-v62
strip is /nix/store/skd6ix5ipkyhxzq7naylj4digawakl4j-binutils-2.28.1/bin/strip
patching script interpreter paths in /nix/store/4b9vgpy7wvlnlvpapdm7gs6kjvsri32c-gnome-shell-dash-to-dock-v62
checking for references to /build in /nix/store/4b9vgpy7wvlnlvpapdm7gs6kjvsri32c-gnome-shell-dash-to-dock-v62...
/nix/store/4b9vgpy7wvlnlvpapdm7gs6kjvsri32c-gnome-shell-dash-to-dock-v62

Success on x86_64-linux (full log)
Partial log (click to expand)
rm -fR _build
echo done
done
glibPreFixupPhase
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/d19qnq6jajrxc7yr2ag5901zrc5hbsaz-gnome-shell-dash-to-dock-v62
strip is /nix/store/adidfx4pa7vmvby0gjqqmiwg2x49yr27-binutils-2.28.1/bin/strip
patching script interpreter paths in /nix/store/d19qnq6jajrxc7yr2ag5901zrc5hbsaz-gnome-shell-dash-to-dock-v62
checking for references to /tmp/nix-build-gnome-shell-dash-to-dock-v62.drv-0 in /nix/store/d19qnq6jajrxc7yr2ag5901zrc5hbsaz-gnome-shell-dash-to-dock-v62...
/nix/store/d19qnq6jajrxc7yr2ag5901zrc5hbsaz-gnome-shell-dash-to-dock-v62

Success on x86_64-darwin (full log)
Partial log (click to expand)
mkdir -p<EMAIL_ADDRESS>cp -r ./_build/*<EMAIL_ADDRESS>rm -fR _build
echo done
done
glibPreFixupPhase
post-installation fixup
strip is /nix/store/v8ifq0hapblpr2z0hx4wvwg02w4aczqy-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/hmszbn3r6x64g0ia8731kzfmv9p5w24i-gnome-shell-dash-to-dock-v62
/nix/store/hmszbn3r6x64g0ia8731kzfmv9p5w24i-gnome-shell-dash-to-dock-v62


Edit contact always remove match

This is strictly incorrect behavior, edit a contact's email should not cause them to lose their job, therefore this is a functionality bug.

Linked to #357

Duplicate issue


when should I add Defender Antivirus Antimalware updates?

https://www.catalog.update.microsoft.com/Search.aspx?q=defender antivirus antimalware
[Enter feedback here]

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

ID: c7734ca5-0770-5bbd-7da5-dda4c1cf5ae0
Version Independent ID: cb98ef23-d0c6-e62e-b72b-9b5f5d724e8e
Content: Update Windows 10 media with Dynamic Update - Windows Deployment
Content Source: windows/deployment/update/media-dynamic-update.md
Product: w10
Technology: windows
GitHub Login: @SteveDiAcetis
Microsoft Alias: jaimeo

@anwarmahmood1 .  You must add  .cab file or .msu file to operating system .wim file  via offline dism commands.
or you may add  .cab file or .msu file to the running windows 10 OS via online dism command.
DISM.exe /Online /Add-Package /PackagePath:C:\defender-dism-x64.cab

no @RAJU2529  that won't work.  You must use the supplied PowerShell script to integrate Microsoft Defender updates.
I know what to do, and I know how to do it; but this page should mention it so that IT Pros can incorporate Defender.

Hello @anwarmahmood1 ,
the article is about dynamic updates, adding of defender updates is out of its scope.
Thank you


refactor(BasePointer): mark deprecated classes

Conflicts:
Assets/VRTK/Scripts/Pointers/VRTK_PlayAreaCursor.cs

You already get deprecation warnings due to the System.Obsolete keyword


[FLINK-7563] [cep] Fix watermark semantics in cep and related tests.

What is the purpose of the change
Correct the watermark semantics in cep.
Brief change log

use the logic that (timestamp <= watermark) is considered late.

Verifying this change
This change is already covered by existing tests, such as testCEPOperatorCleanupEventTime(), and testCEPOperatorSerializationWRocksDB() in CEPOperatorTest.java
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Hi @yestinchen,
Thanks for working on this issue. Unfortunately your changes do not fix the semantics. Have a look at this failing test:
@Test
public void testCEPWatermarkSemantic() throws Exception {
	Event startEvent = new Event(42, "start", 1.0);
	SubEvent middleEvent = new SubEvent(42, "foo2", 2.0, 10.0);
	Event endEvent = new Event(42, "end", 1.0);

	SelectCepOperator<Event, Integer, Map<String, List<Event>>> operator = getKeyedCepOperatorWithComparator(false);

	try (OneInputStreamOperatorTestHarness<Event, Map<String, List<Event>>> harness = CepOperatorTestUtilities.getCepTestHarness(operator)) {
		harness.open();

		harness.processWatermark(0L);
		verifyWatermark(harness.getOutput().poll(), 0L);

		harness.processElement(new StreamRecord<>(startEvent, 1L));
		harness.processElement(new StreamRecord<>(middleEvent, 2L));
		harness.processElement(new StreamRecord<>(endEvent, 3L));

		assertTrue(operator.hasNonEmptyPQ(42));
		assertTrue(!operator.hasNonEmptyNFA(42));

		harness.processWatermark(3L);
		verifyWatermark(harness.getOutput().poll(), 3L);

		assertTrue(operator.hasNonEmptyPQ(42));
		assertTrue(operator.hasNonEmptyNFA(42));

		harness.processWatermark(4L);
		assertTrue(!operator.hasNonEmptyPQ(42));

		verifyPattern(harness.getOutput().poll(), startEvent, middleEvent, endEvent);
		verifyWatermark(harness.getOutput().poll(), 4L);
	}
}

To fix it you also have to fix the condition in AbstractKeyedCEPPatternOperator::onEventTime:232. Instead of:
while (!sortedTimestamps.isEmpty() && sortedTimestamps.peek() <= timerService.currentWatermark()) {

it should be
while (!sortedTimestamps.isEmpty() && sortedTimestamps.peek() < timerService.currentWatermark()) {

I added the test case to the CEP Operator and addressed the line. Thanks so much.

In fact you were right @yestinchen  in the first commit. I was mistaken with my comment :( Sorry for that. I am merging your first version.


Exception during upload_stream causes hang

This hangs:
from aioftp import ClientSession
import asyncio

async def main():
    async with ClientSession("localhost") as client:
        async with client.upload_stream("/foo/bar") as stream:
            raise RuntimeError()

asyncio.get_event_loop().run_until_complete(main())

This does not:
from aioftp import ClientSession
import asyncio

async def main():
    async with ClientSession("localhost") as client:
        async with client.upload_stream("/foo/bar") as stream:
            try:
                raise RuntimeError()
            finally:
                stream.writer.write_eof()

asyncio.get_event_loop().run_until_complete(main())

Apparently, without the write_eof, the data connection doesn't get closed.
In ClientSession.__aexit__ aioftp sends a QUIT but there's no reaction from the server until the data connection has been closed.
My guess is you should add the write_eof to DataConnectionThrottleStreamIO.__aexit__.
Tested against a local vsftpd.

Interestingly, if you pass instead of raise, it works fine.
I wonder what's going on. The code paths seem to be the same since neither __aexit__ is actually interested in the exception.

@heftig, probably something differs at flushing quit, so on raise there is no real data transfer.

add the write_eof to DataConnectionThrottleStreamIO.__aexit__

This definitely should be there, thanks! :+1:

The code paths seem to be the same since neither aexit is actually interested in the exception.

Strike that; DataConnectionThrottleStreamIO.__aexit__ doesn't call finish if there's an exception. As a result, close doesn't get called either, and the connection stays open.
So write_eof was a red herring, and it was really the missing close.
I guess since every write on the stream does a drain, write_eof isn't needed?

AFAIK normally to close a connection you write_eof, then await drain and then close, to ensure all bytes have been sent.

It looks like writer.close() is enough here. Since write_eof closing only writing, but you can still read (as documentation said). Also, not all transports support write_eof.
Is it enough?
async def __aexit__(self, exc_type, exc, tb):

        if exc is None:

            await self.finish()

        else:

            self.close()

Yes, that works too, thanks.


floats: deflake Round test

@btracey Please take a look.
This takes the table from TestRoundEven and changes the relevant want fields. Changed that differ between the two are
x: 454.4445, prec: 3
x: 454.44445, prec: 4
x: 0.425, prec: 2
x: 123.4245, prec: 3
x: 454.45, prec: 1
x: 454.445, prec: 2
x: 500, prec: -3

Fixes #114.
These tests are simpler and (as I discovered a couple of days ago - strconv.FormatFloat uses round half to even) actually correct.

LGTM


Report coverage from Cygwin jobs

Summary of changes
$sbj
Pull Request Checklist

[x] Changes have tests
[ ] News fragment added in changelog.d/.
(See documentation for details)

@abravalheri you merged this too soon. It's not harmful, but looking at https://github.com/pypa/setuptools/actions/runs/3286201257/jobs/5414056076#step:7:25, it still doesn't report anything. This is why I was keeping it as a draft. It probably needs a fix upstream. FYI.

Sorry for that.
I agree that it looks like it needs a fix upstream. Probably the coveralls action is not getting the correct file on cygwin.
We probably need to report this to them (or just give up and use the CLI client)

The upstream issue is already linked in the last comment before the merge.


pipelines: sample pipeline with multiple dependent stages and fixed runtime

It was brought up that this pipeline might be useful for testing. It has 4 parallel pipelines, each 3 interdependent stages. Each stage should take 2 minutes and generate CPU load during that time by repeatedly taking square roots.

/test pipelines-light load_aware pipeline_timed_multistage

@kpouget I've tried to get this working in the past and it isn't straight forward. Tekton does some of its own parsing so it can clearly tell which stages depend on which and how to construct the DAG. So from what I can tell you are a bit limited as to what type of control flow you use when creating the pipeline. Tekton didn't like compiling for loops or putting the results of pipelines in arrays.
I can look into it and see if Tekton has a way to officially support this though!

ack, I'm not surprised!
there's one way do to what I suggested, it's called code generation :D
write what you want to do in a Python file, and get it executed ;-) But that might be going a bit too far, as we're not even sure to be able to use Pipelines with the load-aware scheduler!

/lgtm
/approve
/hold
@drewrip , you can merge it when you're ready with /hold cancel

/hold cancel
/lgtm


Add View Transitions API support

The View Transitions API is available behind a flag in Chrome at chrome://flags/#view-transition. You can use it to animate transitions between elements on the page across HTTP requests.
The View Transitions API is still an experimental feature, but there seems to be a lot excitement around it; it degrades nicely in browsers without support, so I'm considering enabling it as the new default when elements are changed via x-target.
The video below demonstrates the Inline Edit example on the Alpine AJAX site using a slide-in/out animation. The only code added to the page was this CSS:
/* Setup animations */
@keyframes fade-in {
  from { opacity: 0; }
}

@keyframes fade-out {
  to { opacity: 0; }
}

@keyframes slide-from-right {
  from { transform: translateX(25%); }
}

@keyframes slide-to-left {
  to { transform: translateX(25%); }
}

/* Define animations for the old and new content */
::view-transition-old(slide-fade) {
  animation: 200ms ease 150ms both fade-out, 200ms ease 150ms both slide-to-left;
}
::view-transition-new(slide-fade) {
  animation: 300ms ease 50ms both fade-in, 300ms ease 50ms both slide-from-right;
}

/* Make the magic happen */
form {
  background: #fff;
  view-transition-name: slide-fade;
}

https://github.com/imacrayon/alpine-ajax/assets/3410149/f93d2c31-310b-4446-a18d-959688ea90d2

This looks wonderful!

I noticed a few small rendering bugs in Chrome when enabling this by default. I think it'll be best to make this functionality opt-in and then we can re-evaluate things when it becomes more widely adopted.
To that end I've added a transition modifier to x-merge. Using x-merge.transition on an element will enable View Transitions when the element changes. There's also a global config so that transitions can be enabled for all content changes: ajax.configure({transitions: true}).


fix: 修复黑暗模式下一些样式问题

General

✏ Mark the necessary items without changing the structure of the PR template.

[ ] Pull request template structure not broken

Type

ℹ What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉 Put an x in the boxes that apply.

[ ] My code follows the style guidelines of this project
[ ] Is the code format correct
[ ] Is the git submission information standard?
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

http://localhost:5173/#/dashboard/workbench 黑暗模式下文字为黑色看不见，我修复了
顺便重构了下dark.less


User UUIDs instead of user names

Better for these days, when users tend to update their names in-game. You wouldn't want your donors losing their custom cape then.
Simply enter the formatted UUID instead of the username in the json file.
Formatted user UUIDs can be pulled out manually through MCUUID.NET, or through a json file using MCAPI.
As this project no longer maintained, I don't expect it to be merged, but you users can just use my fork.

Could you also change the documentation?

https://github.com/jadar/DeveloperCapes/pull/44


Breakpoint zone widget should support code coloring

Add a brekapoint, right click on it to Edit Condition -> write some condition -> there is no coloring.

This should now work nicely

This should now work nicely


Fail to load Semantic-UI minified CSS in offline mode

When in offline mode (OFFLINE_MODE set to True), Puppetboard seems to fail to load the Semantic-UI CSS.
The browser is trying to load the path /offline/Semantic-UI-2.1.8/semantic.min.css and it seems to not find a template for it, the logged exception is:
ERROR in app: Exception on /offline/Semantic-UI-2.1.8/semantic.min.css [GET]
Traceback (most recent call last):
  File "./venv/lib/python3.5/site-packages/flask/app.py", line 1982, in wsgi_app
    response = self.full_dispatch_request()
  File "./venv/lib/python3.5/site-packages/flask/app.py", line 1614, in full_dispatch_request
    rv = self.handle_user_exception(e)
  File "./venv/lib/python3.5/site-packages/flask/app.py", line 1517, in handle_user_exception
    reraise(exc_type, exc_value, tb)
  File "./venv/lib/python3.5/site-packages/flask/_compat.py", line 33, in reraise
    raise value
  File "./venv/lib/python3.5/site-packages/flask/app.py", line 1612, in full_dispatch_request
    rv = self.dispatch_request()
  File "./venv/lib/python3.5/site-packages/flask/app.py", line 1598, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "./venv/lib/python3.5/site-packages/puppetboard/app.py", line 1105, in offline_static
    return Response(response=render_template('static/%s' % filename),
  File "./venv/lib/python3.5/site-packages/flask/templating.py", line 133, in render_template
    return _render(ctx.app.jinja_env.get_or_select_template(template_name_or_list),
  File "./venv/lib/python3.5/site-packages/jinja2/environment.py", line 869, in get_or_select_template
    return self.get_template(template_name_or_list, parent, globals)
  File "./venv/lib/python3.5/site-packages/jinja2/environment.py", line 830, in get_template
    return self._load_template(name, self.make_globals(globals))
  File "./venv/lib/python3.5/site-packages/jinja2/environment.py", line 804, in _load_template
    template = self.loader.load(self, name, globals)
  File "./venv/lib/python3.5/site-packages/jinja2/loaders.py", line 113, in load
    source, filename, uptodate = self.get_source(environment, name)
  File "./venv/lib/python3.5/site-packages/flask/templating.py", line 57, in get_source
    return self._get_source_fast(environment, template)
  File "./venv/lib/python3.5/site-packages/flask/templating.py", line 85, in _get_source_fast
    raise TemplateNotFound(template)
jinja2.exceptions.TemplateNotFound: static/Semantic-UI-2.1.8/semantic.min.css

From a quick look at the code it's not fully clear to me why only the Semantic-UI minified CSS is calling the offline_static url handler instead of the standard static one like all the other resources.
Installation details
Puppetboard version: 0.3.0 (from PyPI)
Python version: 3.5.3
OS: Debian GNU/Linux 9.4 (stretch)
Served via uwsgi and Apache with mod_proxy in front of it.

I've noticed that this was resolved in https://github.com/voxpupuli/puppetboard/commit/28566b351f84bc2d8016ffd5ccc9bd9106cba837, hence I'm resolving it as I guess that the next PyPI release will resolve the issue.
By any chance do you have any time estimation for the next release of Puppetboard?


Property test failure BlockSizeTooLargeCHAIN

On a very rare occasion it looks like generator is producing blocks that are too large in the test suite. This needs some investigation and a fix:
https://github.com/input-output-hk/cardano-ledger/actions/runs/6761700112/job/18376844168?pr=3848
GHC-8.10.7
Reproducer: 457bdfa1ff7d15868856e67c95e80870983fd625
Branch: test-reproducer-BlockSizeTooLargeCHAIN-PR-3848
[RealChainPredicateFailure (BlockSizeTooLargeCHAIN 54282 51453)])
      Use --quickcheck-replay=3285 to reproduce.
      Use -p '/Only valid CHAIN STS signals are generated/' to rerun this test only.

....
1 out of 181 tests failed (1267.58s)
Test suite cardano-ledger-shelley-ma-test: FAIL

BlockSizeTooLarge.logs_13079.zip

I confirmed that #3853 fixes the issue


Unexpected Logger output location

Environment

Elixir & Erlang/OTP versions (elixir --version): 1.14.2 Erlang/OTP 24
Operating system: Fly.io Livebook Docker Image Linux
How have you started Livebook (mix phx.server, livebook CLI, Docker, etc): Docker
Livebook version (use git rev-parse HEAD if running with mix): v0.8.0
Browsers that reproduce this bug (the more the merrier): Chrome

Current behavior
When outputting a cell only containing multiple Logger messages they are separated in different Kino frames.
In this example, the first Logger output is listed in the top frame with the remaining Logger outputs in the second frame. If there is an expression above the Logger outputs, they all appear in the same frame.
https://user-images.githubusercontent.com/454563/209405622-044cdeac-2501-407f-a88a-fd9c84f0756b.mov
It didn't happen during recording, but I had an instance where the output changed if there was a new line between the 1 + 1 and the Logger statement, requiring a blank line between the two for the Logger output to move to the end frame.
Expected behavior
I would expect all Logger outputs to be grouped, regardless of their placement in the cell/other codes presence.

Hey @zolrath! Logger works asynchronously, so this is not exactly deterministic. You could do Logger.configure(sync_threshold: 0) to make sure every log is synchronous.

Hey @zolrath! Logger works asynchronously, so this is not exactly deterministic. You could do Logger.configure(sync_threshold: 0) to make sure every log is synchronous.

Ahh, that makes sense.
This was for a specific example Livebook, so that option works perfectly, thanks!


Add custom SQL field for Views

My use case here is that I have a huge table with billions of entries. To improve a bit performance I want a view with let say the data since two years only. By allowing a custom field where I can add a custom SQL I would be able to do that.
Hope that's clear enough ^^ or let me know

So would a custom additional field to the SELECT portion of the query enough or do you want to du custom joins also?

So for my specific use case it would be more a WHERE clause.
Example, currently we have this generated:
CREATE VIEW fake_models_view AS
SELECT "fake_models".*
FROM "fake_models"
WHERE '_#07c2fe9ce829535a5eed01abe7b2eaa32ac021cb#_' IS NOT NULL;

I would like to be able to do something like:
CREATE VIEW fake_models_view AS
SELECT "fake_models".*
FROM "fake_models"
WHERE '_#07c2fe9ce829535a5eed01abe7b2eaa32ac021cb#_' IS NOT NULL
 AND created > DATEADD(yy,-2,GETDATE());

Something like this.
Transformers looks interesting also :D

But cant you do the where using the QueryParams object?

I can but I'll have to think of adding it in all QueryParams of the projects where by doing it here it's once for the all project and all queryparam I'll do would be about business logic and not about making the date lighter

Fixed in 0.9.2


Floats are interpreted wrongly as ints for muon JSON

@nsmith-
I have some problems extracting muon SFs from a JSON if I use it with real values from a test nanoAOD instead of dummy values. It is related to the datatype, but I am very confused because he interprets floats as ints, as you can see in this MWE:
from coffea.nanoevents import NanoEventsFactory, NanoAODSchema
import warnings
warnings.filterwarnings("ignore", module="coffea.*")
import awkward as ak
import gzip
from correctionlib import _core
import rich

fname = "https://raw.githubusercontent.com/CoffeaTeam/coffea/master/tests/samples/nano_dy.root"
events = NanoEventsFactory.from_root(
    {fname: "Events"},
    schemaclass=NanoAODSchema,
    metadata={"dataset": "DYJets"},
    delayed=False,
).events()

events = events[ak.num(events.Muon) >= 1]

fname_json = "/cvmfs/cms.cern.ch/rsync/cms-nanoAOD/jsonpog-integration/POG/MUO/2017_UL/muon_Z_v2.json.gz"
with gzip.open(fname_json,'rt') as file:
    data = file.read().strip()
    evaluator = _core.CorrectionSet.from_string(data)

valsf_lead_muon = evaluator["NUM_GlobalMuons_DEN_genTracks"].evaluate("2017_UL", 1.1, 30., "sf")
print(valsf_lead_muon) # 0.9892860877591372
print(events.Muon[0,0].eta) # 0.713501
print(events.Muon[0,0].pt) # 76.75332
valsf_lead_muon = evaluator["NUM_GlobalMuons_DEN_genTracks"].evaluate("2017_UL", float(events.Muon[0,0].eta), float(events.Muon[0,0].pt), "sf") # works
print(valsf_lead_muon) # 0.9931737081746256
valsf_lead_muon = evaluator["NUM_GlobalMuons_DEN_genTracks"].evaluate("2017_UL", events.Muon[0,0].eta, events.Muon[0,0].pt, "sf") # fails: RuntimeError: Input abseta has wrong type: got int expected real
# This is really concerning because 0.713501 and 76.75332 are obviously not integers!

We need to socialize not using from correctionlib import _core. It was unfortunately necessary for python2-based clients in e.g. CMSSW 10_X release series but is not generally necessary/desired anywhere with python3. Rather, one should be using:
from correctionlib import CorrectionSet
fname_json = "/cvmfs/cms.cern.ch/rsync/cms-nanoAOD/jsonpog-integration/POG/MUO/2017_UL/muon_Z_v2.json.gz"
evaluator = CorrectionSet.from_file(fname_json)

Using this construction, the above example works correctly.
That said, it is worth investigating why the _core module is not casting the data correctly, this may be a pybind11 problem. I'm still looking into it but wanted to mention the above concern to help unblock you.

Hi @nsmith-, thanks so much for this quick help! I confirm that it works with your recipe. Indeed, it would be great to spread the information that _core is not encouraged anymore. Many examples in jsonpog-integration still have this older syntax: https://gitlab.cern.ch/search?search=_core&nav_source=navbar&project_id=112114&group_id=12475&search_code=true&repository_ref=master
I will make sure to advocate the newer way whenever possible but perhaps somebody can also address this for the examples that CMS provides...


Fix race condition around supervisor's Commander

From what I'd see under normal circumstances (and also the example), starting up the supervisor which also launches the commander would happen in a separate goroutine than the one that inspects its state or calls Stop.
The current implementation has a race condition on the cmd *exec.Cmd field, using it both for figuring out whether the commander is running and also actually executing a new Agent process, which could potentially lead to a panic.
This PR fixes a small race condition around the supervisor's Commander by utilizing an existing running field and turning it into a atomic.Bool to store the commander's state.
Fixes #290

@tpaschalis @srikanthccv is this still in progress?

@tpaschalis @srikanthccv is this still in progress?

Srikanth had suggested using more explicit synchronization to avoid potentially leaving a dangling process; if the Shutdown method of the supervisor is called, then the isStoppingFlag will be set and the call to the commander's Start will abort before starting the new process.
I'm looking forward to feedback!

@tpaschalis @srikanthccv I assume you are working on this PR. Please ping me when it is ready.


[FX-2286] Implements show2 click tracking

Re: FX-2286
This takes care of: clickedViewingRoomCard,clickedFairCard, and clickedPartnerCard
Is there anything that has to happen for the artwork grid events or are those just included with the component? Ditto re: pageView?

Artwork grid tracking should be okay, but I would verify.
Re: pageviews, it's possible that they're happening twice (can also be verified in the console). I think we'll need to update this file (but will have to make sure to not silence existing page views until we've launched).

Nice, we can always incrementally add more analytics.
I think for artwork grid tracking, that does need to be passed in to the component via onArtworkBrickClick from the calling code.


Revert web requirements checker filename change

Revert web requirements checker filename change after Composer install/update command execution

This looks wrong to me as the check file is not the one from the SE. It has been customized to have a display consistent with the demo.

Do you mean to change the file name in app/check.php is wrong because this file should be refered only to the original Symfony SE file, not customized one for this project?

So in this case we couldn't rename our web/check.php to web/config.php back too to be consistent with Symfony SE because we change its content.

@bocharsky-bw which is exactly what I commented previously

Then it looks the best solution in this case is to revert web requirements checker filename and keep app/check.php refers to the non-exist web/config.php file.
I change this PR.

@bocharsky-bw I'm sorry but I don't understand this pull request. My question to you is: what do you think if we rename web/check.php file back to web/config.php?

There is another good solution to rename web/check.php file back to web/config.php. But it's not the one from the SE, we did some changes to it to have a display consistent with the demo application.
Anyway, I think it'll be better to rename this file to web/config.php to be consistent with SE naming if @stof is not opposed.

The current content of this pull request is:
-echo_style('yellow', 'web/check.php');
+echo_style('yellow', 'web/config.php');

But I'm confused because we do have a web/check.php file but we don't have a web/config.php. Should we also rename web/check.php to web/config.php?

Xabbuh said that's the best solution in https://github.com/symfony/symfony-demo/pull/124#issuecomment-127053916 and now I agree with him.
I'm also interesting what does @stof think about to rename web/check.php to web/config.php.

Well, I renamed to web/config.php and it's a bad idea. After this renaming Symfony replace our web/config.php with its own when I do $ composer install/update. So we should avoid config.php name anyway.
I suggest to revert changes to https://github.com/bocharsky-bw/symfony-demo/commit/3e8e6e81f21fe7082b7d69cd20bcb4a52bd47601 (left this file name as check.php and also left echo_style('yellow', 'web/config.php'); string in app/check.php as is).
@javiereguiluz What do you think?

@bocharsky-bw I agree with your last solution. If there are problems with Symfony overwriting this file, we'll deal with that when the time comes. Thanks!


Refs #32355 -- Used addClassCleanup() in SimpleTestCase and SerializeMixin.

https://docs.python.org/3/library/unittest.html#unittest.TestCase.addClassCleanup
Inspired by Adam Johnson talk on DjangoCon Europe 2021.
ticket-32355

We could probably get rid of TestCase.tearDownClass() as well but it's more complicated.

@adamchainz Thanks for the review :1st_place_medal:


[docs] Update ThemeProvider API link

close #29504

[x] I have followed (at least) the PR section of the contributing guide.

Preview: https://deploy-preview-29573--material-ui.netlify.app/customization/theming/#theme-provider

Looks good.
While we fix this specific instance of the problem, and it's great. It seems to surface a future improvement opportunity. We have a duplication of content "mess" to manage. From what I understand, we need:

The documentation of the system to have all the imports from @mui/system
The documentation of Material to cover again all the content of the system but with imports from @mui/material/styles.
The documentation of Joy to cover again all the content of the system but with imports from @mui/joy/styles.

My hope is that we can manage this by linking as much as possible to 1. explaining that the import path should be different, and duplicating content in 2. and 3. to the strict minimum.

We can focus on that in the next quarter.


[Bug] [connector-v2] [Eleasticsearch] document description error #4370

Purpose of this pull request

Check list

[ ] Code changed are covered with tests, or it does not need tests for reason:
[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/incubator-seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

close :
https://github.com/apache/incubator-seatunnel/issues/4370


Checkov-action started failing after the recent update in the docker image

Earlier it used to work fine
Pipeline
checkov_scan:
    runs-on: ubuntu-latest
    steps:

      - name: "Checkout"
        uses: actions/checkout@master
      - name: Run Checkov action
        id: checkov
        uses: bridgecrewio/checkov-action@master
        with:
          directory: azure/
          quiet: true # optional: display only failed checks
          soft_fail: true # optional: do not return an error code if there are failed checks
          framework: terraform # optional: run only on a specific infrastructure {cloudformation,terraform,kubernetes,all}
          output_format: sarif # optional: the output format, one of: cli, json, junitxml, github_failed_only, or sarif. Default: sarif
          download_external_modules: true # optional: download external terraform modules from public git repositories and terraform registry
          log_level: WARNING # optional: set log level. Default WARNING

Output
2023-05-09 14:50:13,078 [MainThread  ] [DEBUG]  Hard fail severity threshold: None
2023-05-09 14:50:13,078 [MainThread  ] [DEBUG]  Hard fail checks: []
2023-05-09 14:50:13,079 [MainThread  ] [DEBUG]  Use enforcement rules is FALSE
2023-05-09 14:50:13,079 [MainThread  ] [DEBUG]  In get_exit_code; exit code thresholds: {'soft_fail': True, 'soft_fail_checks': [], 'soft_fail_threshold': None, 'hard_fail_checks': [], 'hard_fail_threshold': None}, hard_fail_on_parsing_errors: False
2023-05-09 14:50:13,079 [MainThread  ] [DEBUG]  Soft_fail is True and soft_fail_on and hard_fail_on are empty - returning 0
Error: -09 14:50:13,081 [MainThread  ] [ERROR]  Exception traceback:
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/checkov/main.py", line 490, in run
    exit_codes.append(self.print_results(
  File "/usr/local/lib/python3.10/site-packages/checkov/main.py", line 638, in print_results
    return runner_registry.print_reports(
  File "/usr/local/lib/python3.10/site-packages/checkov/common/runners/runner_registry.py", line 394, in print_reports
    sarif = Sarif(reports=sarif_reports, tool=self.tool)
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 31, in __init__
    self.json = self.create_json()
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 37, in create_json
    "runs": self._create_runs(),
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 43, in _create_runs
    results = self._create_results()
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 192, in _create_results
    "startLine": int(record.file_line_range[0]) or 1,
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'
Traceback (most recent call last):
  File "/usr/local/bin/checkov", line 9, in <module>
    sys.exit(Checkov().run())
  File "/usr/local/lib/python3.10/site-packages/checkov/main.py", line 490, in run
    exit_codes.append(self.print_results(
  File "/usr/local/lib/python3.10/site-packages/checkov/main.py", line 638, in print_results
    return runner_registry.print_reports(
  File "/usr/local/lib/python3.10/site-packages/checkov/common/runners/runner_registry.py", line 394, in print_reports
    sarif = Sarif(reports=sarif_reports, tool=self.tool)
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 31, in __init__
    self.json = self.create_json()
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 37, in create_json
    "runs": self._create_runs(),
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 43, in _create_runs
    results = self._create_results()
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 192, in _create_results
    "startLine": int(record.file_line_range[0]) or 1,
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'

Cleaning up azure//.external_modules directory

I don't know if it's the same issue but checkov is hanging my workflow since the upgrade from v2.3.214.
If I pin back to the commit for v2.3.214 it works.

checkov -d .    --quiet    --output sarif      --download-external-modules true
Error: -16 04:53:06,712 [MainThread  ] [ERROR]  Exception traceback:
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/checkov/main.py", line 501, in run
    exit_codes.append(self.print_results(
  File "/usr/local/lib/python3.10/site-packages/checkov/main.py", line 690, in print_results
    return runner_registry.print_reports(
  File "/usr/local/lib/python3.10/site-packages/checkov/common/runners/runner_registry.py", line 428, in print_reports
    sarif = Sarif(reports=sarif_reports, tool=self.tool)
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 40, in __init__
    self.json = self.create_json()
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 46, in create_json
    "runs": self._create_runs(),
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 52, in _create_runs
    results = self._create_results()
  File "/usr/local/lib/python3.10/site-packages/checkov/common/output/sarif.py", line 226, in _create_results
    "startLine": int(record.file_line_range[0]) or 1,
TypeError: int() argument must be a string, a bytes-like object or a real number, not 'NoneType'
Traceback (most recent call last):

Same issue here

@aclarkot how did you switch the version back the mentioned version?


Embed famous library without cloud service

Can you include the famous library into your page directly and declare the JS in there? If not—why not?
Would love to post this question on slack, but the links to slack are broken.
Cheers.

hey nikkwong.
You can still npm install famous
https://github.com/famous/engine-seed is an example project working without the cli.
You can also use a link from our CDN
http://code.famo.us/famous/0.5/famous.min.js

Thanks for the help thus far. Is it possible to embed famous onto a page without using any back end node packages—i.e. only having the CDN as a dependency?

if you include that cdn link you will be able to reference the famous global object.

Sweet! Thanks!


Initial import of the galera reconciler

Let the mariadb operator reconcile galera resources, and update the way it reconciles mariadbdatabases, based on whether mariadb or galera is currently in use in the cluster.
It is assumed that either mariadb or galera is instantiated, you can't run both at the same time and reconcile mariadbdatabases.
As the galera reconciler becomes more mature, we may want to deprecate the mariadb reconciler and only support galera, as it can be deployed as a 1-node statefulset.

I'm proposing to move the galera reconciler in this repo rather than to keep it in the galera-operator repo.
The reason being that the mariadbdatabase reconciler is currently duplicated in the galera-operator codebase, as it is necessary to deploy the openstack services without deploying the mariadb-operator. Technically, the only difference between mariadb-operator and galera-operator is that the latter implements the galera reconcilier. So for transitioning to using galera only, it looks simpler in the long run to backport it in the mariadb-operator and deprecate galera-operator.
As a proof of concept, with this PR and a modified openstack-operator [1], one can decide to deploy a control plane with either a simple MariaDB or Galera as a backing database. With the accompanying modified install_yamls [2] one can replace mariadb with a 1-node galera by running:
DBSERVICE=galera make openstack_deploy

One can also deploy a 3-node galera cluster as the database service with:
DBSERVICE=galera REPLICAS=3 make openstack_deploy

[1] https://github.com/openstack-k8s-operators/openstack-operator/compare/master...dciabrin:openstack-operator:galera-reconciler
[2] https://github.com/openstack-k8s-operators/install_yamls/compare/master...dciabrin:install_yamls:galera-reconciler

The reason being that the mariadbdatabase reconciler is currently duplicated in the galera-operator codebase, as it is necessary to deploy the openstack services without deploying the mariadb-operator. Technically, the only difference between mariadb-operator and galera-operator is that the latter implements the galera reconcilier. So for transitioning to using galera only, it looks simpler in the long run to backport it in the mariadb-operator and deprecate galera-operator.

Please note that the mariadb-operator was a stopgap solution until the galera-operator is implemented. And as so it might not be designed for the long run. So by re-using parts of it this way you inherit a bag of shortcuts from this prototype. Here is the list of limitations I know about the prototype, but there can be a lot more:

The database user cannot be influenced it is hardcoded to the name of the DB schema: #36
Even though the service operators define a database password per service, the mariadb-operator uses a global password for each service by not selecting for the service specific password

Therefore I think it would be better not to bring this shortcuts forward but design something for the long run on the mariadbdatabase side too.

I think the general functionality of mariadb-operator is something we still want to have, I mean the split in maraidb and mariadbdatabases. The mentioned limitations are valid and a must have feature/functionality. We only did not add this to mariadb-databases due to the galera development. While I think the two mentioned limitations are easy to be fixed/enhanced, I agree that if we see that there are disadvantages in the current architecture that we should change and break it now instead of a later time.

Apologies for the late PR update, I had difficulties testing the new version with openstack-operator selectivitely enabling/disabling services..


visit logger server - V1

🍏
Iteration 1: server remembers visits only when it's running

Good stuff.

Thank you for true comments 🙇🏻♂


Chromium blocks this completely, Firefox does not

Hi,
The developer console is blank when I load the demo. It also doesn't return any IPs. Firefox returns both the local and external IPs (disturbing!).
Do you know if Chrome fixed this in some way? Can anyone else with a recent Chrome confirm similar behavior?
Thank you,
Teran

it still works in chrome (v48)

Still does, v52.


Submit RBApy 1.0.2

id: rbapy
version: "1.0.2"
specificationsUrl: https://raw.githubusercontent.com/biosimulators/Biosimulators_RBApy/da52fa170ccfe38279078de0c840239ded8fd74a/biosimulators.json
specificationsPatch:
version: "1.0.2"
image:
url: ghcr.io/biosimulators/biosimulators_rbapy/rbapy:1.0.2
validateImage: true
commitSimulator: true

Changelog:

HPC connection restored

Summary of tests

Executed 73 test cases

Passed 31 test cases:

cli.CliDescribesSupportedEnvironmentVariablesInline
cli.CliDisplaysHelpInline
cli.CliDisplaysVersionInformationInline
combine_archive.CombineArchiveHasSedDocumentsInNestedDirectories
combine_archive.CombineArchiveHasSedDocumentsWithSameNamesInDifferentInNestedDirectories
combine_archive.WhenACombineArchiveHasAMasterFileSimulatorOnlyExecutesThisFile
combine_archive.WhenACombineArchiveHasNoMasterFileSimulatorExecutesAllSedDocuments
docker_image.DeclaresSupportedEnvironmentVariables
docker_image.DefaultUserIsRoot
docker_image.HasBioContainersLabels
docker_image.HasOciLabels
docker_image.SingularityImageExecutesSimulationsSuccessfully
log.SimulatorReportsTheStatusOfTheExecutionOfCombineArchives
log.SimulatorReportsTheStatusOfTheExecutionOfSedDocuments
log.SimulatorReportsTheStatusOfTheExecutionOfSedOutputs
log.SimulatorReportsTheStatusOfTheExecutionOfSedTasks
published_project.SimulatorCanExecutePublishedProject:rba/Escherichia-coli-K12-WT
results_report.SimulatorGeneratesReportsOfSimulationResults
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragments
sedml.SimulatorCanResolveModelSourcesDefinedByUriFragmentsAndInheritChanges
sedml.SimulatorProducesReportsWithCuratedNumberOfDimensions
sedml.SimulatorSupportsModelsSimulationsTasksDataGeneratorsAndReports
sedml.SimulatorSupportsMultipleReportsPerSedDocument
sedml.SimulatorSupportsMultipleTasksPerSedDocument
sedml.SimulatorSupportsRepeatedTasksWithFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithLinearUniformRanges
sedml.SimulatorSupportsRepeatedTasksWithLogarithmicUniformRanges
sedml.SimulatorSupportsRepeatedTasksWithMultipleSubTasks
sedml.SimulatorSupportsRepeatedTasksWithNestedFunctionalRanges
sedml.SimulatorSupportsRepeatedTasksWithNestedRepeatedTasks
sedml.SimulatorSupportsRepeatedTasksWithVectorRanges

Failed 0 test cases

Skipped 42 test cases:

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

Warnings
cli.CliDescribesSupportedEnvironmentVariablesInline (4.7 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'
  - 'BUNDLE_OUTPUTS'
  - 'COLLECT_COMBINE_ARCHIVE_RESULTS'
  - 'COLLECT_SED_DOCUMENT_RESULTS'
  - 'DEBUG'
  - 'H5_REPORTS_PATH'
  - 'KEEP_INDIVIDUAL_OUTPUTS'
  - 'LOG_PATH'
  - 'PLOTS_PATH'
  - 'REPORTS_PATH'
  - 'REPORT_FORMATS'
  - 'SAVE_PLOT_DATA'
  - 'VALIDATE_IMAGES'
  - 'VALIDATE_OMEX_MANIFESTS'
  - 'VALIDATE_OMEX_METADATA'
  - 'VALIDATE_RESULTS'
  - 'VALIDATE_SEDML'
  - 'VALIDATE_SEDML_MODELS'
  - 'VERBOSE'
  - 'VIZ_FORMATS'

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.DeclaresSupportedEnvironmentVariables (0.5 s)
Test if a Docker image declares the environment variables that is supports
Warnings:
Docker images for simulation tools should declare the environment variables that they support.

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

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

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

Log:

docker_image.HasBioContainersLabels (0.2 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:

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:cellml/Elowitz-Nature-2000-Repressilator (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_3240
Algorithm: KISAO_0000019

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

Log:

published_project.SimulatorCanExecutePublishedProject:cellml/Lorenz-system (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_3240
Algorithm: KISAO_0000019

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

Log:

published_project.SimulatorCanExecutePublishedProject:mass/Bordbar-Cell-Syst-2015-RBC-metabolism (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000019

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

Log:

published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-CVODE (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_9004
Algorithm: KISAO_0000019

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

Log:

published_project.SimulatorCanExecutePublishedProject:neuroml-lems/Hodgkin-Huxley-cell-Euler (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_9004
Algorithm: KISAO_0000030

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

Log:

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-Fehlberg (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000086

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

Log:

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/Elowitz-Nature-2000-Repressilator (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000019

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

Log:

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/Tomida-EMBO-J-2003-NFAT-translocation (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000560

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

Log:

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

Format: format_2585
Algorithm: KISAO_0000560

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

Log:

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

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

Log:

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

Format: format_2585
Algorithm: KISAO_0000027

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

Log:

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

Format: format_2585
Algorithm: KISAO_0000029

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

Log:

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:

published_project.SimulatorCanExecutePublishedProject:sbml-qual/Irons-J-Theor-Biol-2009-yeast-cell-cycle (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_2585
Algorithm: KISAO_0000449

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

Log:

published_project.SimulatorCanExecutePublishedProject:smoldyn/Lotka-Volterra (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_9001
Algorithm: KISAO_0000057

Reason for skip:
Case requires model formats format_9001 and simulation algorithms KISAO_0000057

Log:

published_project.SimulatorCanExecutePublishedProject:xpp/Wu-Biochem-Pharmacol-2006-pituitary-GH3-cells (0.0 s)
Required model formats and simulation algorithms for SED tasks:

Format: format_9010
Algorithm: KISAO_0000019

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

Log:

sedml.SimulatorProducesLinear2DPlots (4.8 s)
Test that a simulator produces linear 2D plots
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

sedml.SimulatorProducesLinear3DPlots (4.5 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.SimulatorProducesLogarithmic2DPlots (4.4 s)
Test that a simulator produces logarithmic 2D plots
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

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

sedml.SimulatorProducesMultiplePlots (4.5 s)
Test that a simulator produces multiple plots
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

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

Log:

sedml.SimulatorSupportsAlgorithmParameters (4.4 s)
Test that a simulator supports setting the values of parameters of algorithms
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

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

Log:

sedml.SimulatorSupportsDataGeneratorsWithDifferentShapes (4.2 s)
Test that a simulator supports data generators with different shapes
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

sedml.SimulatorSupportsDataSetsWithDifferentShapes (4.3 s)
Test that a simulator supports data generators with different shapes
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

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

Log:

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

Log:

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

Log:

sedml.SimulatorSupportsRepeatedTasksWithSubTasksOfMixedTypes (974.6 s)
Test that a simulator supports repeated tasks whose sub-tasks have mixed types. Also tests that sub-types executed in order of the values of their order attributes and that reports of the results of repeated tasks handle sub-tasks to produce results of different shapes.
Reason for skip:
The image 'ghcr.io/biosimulators/biosimulators_rbapy/rbapy:1.0.2' could not execute the archive:

  [Errno 1] Operation not permitted

Log:
/usr/local/lib/python3.8/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: The SED document is potentially incorrect.

  - Task `__repeated_task_1` may be invalid.

    - The outputs of the sub-tasks have different shapes.

  - Output `__repeated_task_report` may be invalid.

    - Some simulation tools will not be able to generate this output because it uses data from repeated tasks. Output for repeated tasks is an experimental feature of SED-ML, which is not officially supported.

  warnings.warn(termcolor.colored(message, Colors.warning.value), category)

/usr/local/lib/python3.8/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: The COMBINE/OMEX archive may be invalid.

  - The SED-ML file at location `simulation.sedml` may be invalid.

    - Task `__repeated_task_1` may be invalid.

      - The outputs of the sub-tasks have different shapes.

    - Output `__repeated_task_report` may be invalid.

      - Some simulation tools will not be able to generate this output because it uses data from repeated tasks. Output for repeated tasks is an experimental feature of SED-ML, which is not officially supported.

  warnings.warn(termcolor.colored(message, Colors.warning.value), category)

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

  simulation.sedml:

    Tasks (3):

      __repeated_task_0

      __repeated_task_1

      task

    Reports (2):

      __repeated_task_report: 1 data sets

      task_report: 1 data sets

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 (3):

    Succeeded: 3

    Skipped: 0

    Failed: 0

  Outputs (2):

    Succeeded: 2

    Skipped: 0

    Failed: 0

/usr/local/lib/python3.8/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: The SED document is potentially incorrect.

  - Task `__repeated_task_1` may be invalid.

    - The outputs of the sub-tasks have different shapes.

  - Output `__repeated_task_report` may be invalid.

    - Some simulation tools will not be able to generate this output because it uses data from repeated tasks. Output for repeated tasks is an experimental feature of SED-ML, which is not officially supported.

  warnings.warn(termcolor.colored(message, Colors.warning.value), category)

/usr/local/lib/python3.8/site-packages/biosimulators_utils/warnings.py:31: BioSimulatorsWarning: The COMBINE/OMEX archive may be invalid.

  - The SED-ML file at location `simulation.sedml` may be invalid.

    - Task `__repeated_task_1` may be invalid.

      - The outputs of the sub-tasks have different shapes.

    - Output `__repeated_task_report` may be invalid.

      - Some simulation tools will not be able to generate this output because it uses data from repeated tasks. Output for repeated tasks is an experimental feature of SED-ML, which is not officially supported.

  warnings.warn(termcolor.colored(message, Colors.warning.value), category)

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

  simulation.sedml:

    Tasks (3):

      __repeated_task_0

      __repeated_task_1

      task

    Reports (2):

      __repeated_task_report: 1 data sets

      task_report: 1 data sets

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 (3):

    Succeeded: 3

    Skipped: 0

    Failed: 0

  Outputs (2):

    Succeeded: 2

    Skipped: 0

    Failed: 0

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

Log:

sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroInitialTimes (4.1 s)
Test that a simulator supports multiple time courses with non-zero initial times
Reason for skip:
No curated COMBINE/OMEX archives are available to generate archives for testing

Log:

sedml.SimulatorSupportsUniformTimeCoursesWithNonZeroOutputStartTimes (4.5 s)
Test that a simulator supports time courses with non-zero output start times
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 rbapy to the BioSimulators registry will be automatically validated. These submissions will not require manual review by the BioSimulators Team.


feat: add design kit schema

Closes #376
This is a continuation of https://github.com/carbon-design-system/carbon-platform/pull/585 but as a fresh PR to avoid merge conflicts.
Changelog
New

Adds design kits as a third resource type
Library designKits key so we can associate design kits that are the design counterpart to assets in the library
web-app/data/carbon.yml to index resources that don't have their own GitHub repos (design kits)

Changed

Documentation for "asset status" was moved to "status" as a shared schema, with wording not specific to assets so assets and design kits can share the status schema (status key, or an object that contains a key and a note).

Removed

N/A

Testing / reviewing
New design kit resource: https://github.com/carbon-design-system/carbon-platform/blob/91b5b69da979edaf6bf4ce6cf09351634f99fb58/docs/resource-schemas.md#resource-schema-keys
Design kit schema description: https://github.com/carbon-design-system/carbon-platform/blob/91b5b69da979edaf6bf4ce6cf09351634f99fb58/docs/resource-schemas.md#design-kit-schema
Design kit keys: https://github.com/carbon-design-system/carbon-platform/blob/91b5b69da979edaf6bf4ce6cf09351634f99fb58/docs/resource-schemas.md#design-kit-keys
Design kit type: https://github.com/carbon-design-system/carbon-platform/blob/91b5b69da979edaf6bf4ce6cf09351634f99fb58/docs/resource-schemas.md#design-kit-type
Initial indexing: https://github.com/carbon-design-system/carbon-platform/blob/91b5b69da979edaf6bf4ce6cf09351634f99fb58/services/web-app/data/carbon.yml
Design:

[ ] Is there a need to mark certain kits as "primary" or "canonical"? If so, we'll have to either reflect that in the schema or in our JavaScript logic to register design kits to index. Or, can that just be explained in the design getting started page content?
[ ] Do we have all kits indexed? What about IBM Products kits? IBM.com kits?
[ ] We need descriptions for all indexed kits here: https://github.com/carbon-design-system/carbon-platform/blob/91b5b69da979edaf6bf4ce6cf09351634f99fb58/services/web-app/data/carbon.yml

Development:

[ ] Schema validation once design approves the design kits keys and descriptions
[ ] Create issues to update indexed libraries according to the new schema (add designKits to indexed libraries)

@carbon-design-system/carbon-platform-designers to review questions in this PR description - thanks!

@mattrosno @andreancardona @francinelucca
Here is a yaml file with additional kits for IBM Product, Cloud Pal, and IBM.com.

Dotcom has 8 additional sketch kits I have excluded here. From our conversations, they are phasing out support of sketch and prefer it to not be indexed.
IBM Products and Cloud PAL each have 1 kit in Figma. They had aimed to have more by April 27 but I haven't seen them yet: https://pages.github.ibm.com/cdai-design/pal/design-kits/figma/
You will also see Dotcom's figma kits are deprecated. I suggest we catalog those because it sounds like designers are using those kits while they prepare a new release.
I filled in what I could in the yaml file but I wasn't certain about naming convention: i.e. Carbon for IBM Products Gray 10 theme is very long. In Figma it tends to be Gray 10 - IBM Products

https://ibm.ent.box.com/file/968109797345?s=3hd291a2glvptmlss1wcxze1foyucdhm

"Is there a need to mark certain kits as "primary" or "canonical"? If so, we'll have to either reflect that in the schema or in our JavaScript logic to register design kits to index. Or, can that just be explained in the design getting started page content?"
I believe our getting started content covers this well and we don't need to mark 'primary' right now. Dotcom, Cloud PAL, and IBM Product are all working to make Figma kits primary. I think over time it will be clear that sketch is being phased out as those teams don't renew licenses.

Outstanding questions for @mattrosno:

[ ] Library (or asset too) associations with design kits?
[ ] Design kits indexing location?
[ ] Design and dev tasks in description

@mattrosno to look at library designKit inheritance.

@francinelucca just pushed those changes, which work well:
# yaml-language-server: $schema=https://gist.githubusercontent.com/mattrosno/db8f7f672828d484154e3e4e33e8e4e2/raw/bf256274723ac78acc1fb00b2ea25219dbdeb076/carbon-resources.schema.json
library:
  id: carbon-react
  name: Carbon React
  description: React implementation of Carbon Components
  demoLinks:
    - type: storybook
      name: Storybook
      action: link
      url: https://react.carbondesignsystem.com
  designKits:
    carbon-white-sketch:
      $ref: '#/designKits/carbon-white-sketch'
    carbon-g10-sketch:
      $ref<EMAIL_ADDRESS>    carbon-g90-sketch:
      name: Sketch gray 90 theme
      tool: sketch
      type: ui
      status: stable
      url: sketch://add-library/cloud/a324c6dd-df97-435e-b79f-3a29e04922fc
      action: link
  navData:
    - title: A page
      path: '/a-page.mdx'
    - title: Another page
      items:
        - title: Sub page
          path: '/another-page/sub-page.mdx'
          hidden: true
        - title: Another sub page
          path: 'https://github.com/carbon-design-system/carbon-website/blob/main/src/pages/developing/react-tutorial/step-1.mdx'
assets:
  accordion:
    name: Accordion
    description:
      An accordion is a vertically stacked list of headers that reveal or hide associated sections
      of content.
    status: stable
    type: component
    tags:
      - content-element
      - data-display
    framework: react
    platform: web
    docs:
      usagePath: 'https://github.com/carbon-design-system/carbon-website/blob/main/src/pages/components/accordion/usage.mdx'
      stylePath: './components/accordion/styles.mdx'
      codePath: './components/accordion/code.mdx'
      accessibilityPath: './components/accordion/accessibility.mdx'
designKits:
  carbon-white-sketch:
    name: Sketch white theme
    tool: sketch
    type: ui
    status: stable
    url: sketch://add-library/cloud/557b75ff-67d3-41ab-ada5-fa25447218c1
    action: link


Problem

I have a problem when I create a folder from brackets and a file in the folder and I want to show the location in another file include ('include / functions.php') the software does not recognize the folder + file

Could you clarify what you mean with "recognize the folder + file" ?

Assuming this is about add code hint for the location of the file, retargeting as an Extension Idea.


feat(settings): add warning to pull config

Codecov Report

Merging #2102 (47bda15) into main (4a00963) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main    #2102   +/-   ##
=======================================
  Coverage   87.11%   87.11%
=======================================
  Files          85       85
  Lines        9312     9312
  Branches      492      492
=======================================
  Hits         8112     8112
  Misses       1200     1200


docs: arch: Inventory

The knowledge graph

References

https://github.com/w3c-ccg/traceability-interop

Didn't mean to close this

https://github.com/anthonyharrison/sbom-manager

Related: #596

AI/LLM Agent Tool Catalog: https://github.com/scitt-community/scitt-api-emulator/blob/f52fb3c4316c3edc3abe456d1f8f8a891c59e65a/scitt_emulator/policy_engine.py#L8-L20


726Z / Khalil Bsaibes / https://github.com/khalilbsaibesisae

https://github.com/orgs/projets2017cl/teams/nfp103/members


Opens new window with new file

When I create a new file with advanced-new-file, it opens a new window with the file. Is it possible to have the new file created in the current window?

It might be helpful if I tell you exactly what I'm running. :smile:
I'm on OSX 10.10.1 with Atom 0.177.0 and advanced-new-file 0.2.1. I've bound the command to Cmd-N since I want to replace the default new file behavior with it, but it seems to do the same thing if I use the default keybinding.

Hi @raddevon :) this is bit tricky and I've posted issue to atom about that. I do use atom.open functions which has newWindow settings and I set it to false, but sometimes it opens in new window. Will take a closer look at it this weekend :)

Thanks for the reply, @Trudko. I dug a bit deeper and found the newWindow option wasn't getting into the ipc.send call. Pretty sure that's because the call down on line 158 is passing two arguments to atom.open instead of passing the options object.
However, even after explicitly wrapping the options in curly braces, it still opens in a new window. I can verify that the whole object is getting through now, but it doesn't seem to help.
Here's my line 158:
atom.open {pathsToOpen: [pathToCreate], newWindow: false}

Thanks for taking your time, yeah I need to take a closer look at atom.open during the weekend it is bit confusing imho at least documentation is.

@raddevon I've published new version where I used atom.workspace.open instead of atom.open. For me it seems to work. Please try it and let me know.

@Trudko That seems to be working perfectly. Thanks for the fix!

@raddevon thanks for creating an issue and the help!


Version numbering - still 9.0.0 despite all these merges?

I am finding it quite hard to keep track of version numbering.
I see lots of conversations get started and discussed. They hang around for a long time.
Eventually as circumstances permit a huge amount of actions are performed with merging etc etc. (like yesterday).
Yet, when I look at the master source code header it still says version 9.0.0 and that is the version I already have.
Why are code changes being implemented and version numbers not changing?
Why is there not a clearly defined changelog?
I am not complaining as I appreciate this excellent API is provided without charge. It just is hard for me to make a decision as to when to download the latest code and to realise it is been upgraded.

+1 for a new tagged version soon.
I totally understand that updates to a solid, stable project like tinyxml2 happen rarely and in batches. Makes total sense. Just don't forget to release the version when you're done 😉
As a side note, if you need any help testing recent changes, we're happy to help 🙂

10 coming soon.


calibrate function interpretes gravity as error

Hi again,
In calibrate the accelerometer values read are automatically set as error (axe,aye,aze). However if you have the MPU flat on a table then it should read az=1. So now aze will be set to 1 even if there is absolutely no error in the MPU.
If you are only interested in relative accelerometer readings, this might be exactly what you would want. But for roll/pitch/yaw calculation which is also based on those measurements you get a lot of noise/drift, and the accelerometer angles become completely unusable.
To reproduce:

put MPU flat on the table
run calibrate
read getAngleX/getAngleY/getAngleZ

Now for comparison:

put MPU flat on the table
run calibrate
set sensor.aze-=1;
read getAngleX/getAngleY/getAngleZ

The easiest way I can think of handling this is: The calibrate function itself would need an argument that says, eg. ORIENTATION_X_IS_DOWN, ORIENTATION_Y_IS_DOWN, ORIENTATION_Z_IS_DOWN (this should be default) and then you would subtract 1 from the error which matches with the given orientation.
However, this would limit the calibrate function, to be only allowed to be called when the MPU is perfectly aligned on an axis.
Maik

Thanks for this explanation, appreciated

(sorry for late reaction, too busy with other things).
You're right the Z should read 1 in case of a flat sensor.
I like the idea of the parameter to indicate the orientation.
It should ideally support any angle, so the API should look like:
calibrate(x_angle = 0, y_angle = 0);

From these two angles the Z angle and the gravity vector are calculatable.
This gravity vector should be "subtracted" from the error, like the Z = 1 you said but now in 3 dimensions.
Think that is a step too much for now, first step is to get it right for a flat lying sensor.
(I will have a look at your PR now)

Looked at the PR and it made 100% sense, so I merged it into the develop branch.
Thanks again!
Are you OK to be mentioned as I want to give credits where they should be?

Are you OK to be mentioned as I want to give credits where they should be?
Yeah, why not.

I'll try changing the calibrate function as you suggested.

A first version with AZE -= 1 and reset of the gyro integration is preferred.  That would give a minimal correct release as reference.

@mycosd
Did you have time to run some tests with the new calibrate function?
results?

@mycosd Did you have time to run some tests with the new calibrate function? results?

I've been using it in my project, in just X=0, Y=0 orientation. It does the job. Only tested few other orientations when implementing it.
It gets rid of the major drift, however there is still a smaller drift which appears to come from the internal gyro integration (_gyx, _gyy, _gyz).

Thanks for the update,

it gets rid of the major drift, however there is still a smaller drift which appears to come from the internal gyro integration

The smaller drift is probably related to https://github.com/RobTillaart/GY521/issues/47
Will merge the new calibrate into develop, and get it into master asap.

Merged into develop
created a PR for the develop branch.

@mycosd
Engineered the calibrate() function a bit

only sum successful reads, ==> samples counter.
return false if there are no good reads (zero samples)

@mycosd
Merged the improved calibrate() into master, will release 0.6.1 later today.
In the mean time, I got about 15 new issues (other repos as well) so I need to attend some of them too.
So it will take some time to investigate the drift of the sensor (gyroscope integration) which is possibly related to #47.


Request to implement tweet_mode=extended

Hello, edited, cheers

From what I can see, tweet_mode=extended can be easily sent via extra kwargs to most of the method calls. The only exception is the statuses_lookup method where extra kwargs are strictly limited to a few of them. Sending tweet_mode=extended would require changing the signature of the tweepy.api.API.statuses_lookup method, since for some reason, this particular method is not implemented directly as a property.

@arijeetmkh how can these be sent easily via kwargs?

Hello guys,
I am trying to download tweets using tweepy with tweet_mode=extended and my query looks like this:
tweepy.Cursor(api.search,q='to%3ANASA&tweet_mode=extended').items(limit)
, but I keep getting zero results. As soon as I remove the &tweet_mode=extended part from the query, I get plenty of results:
tweepy.Cursor(api.search,q='to%3ANASA').items(limit)
Is it still the right way to form a query? Any idea why am I not getting anything with extended mode?  Hope you can help!
Thanks so much,
Lindsey

The keyword argument for extended_mode needs to be added to the service call (in this case search service). In you case, since you are using a cursor, the keyword argument will be a part of the tweepy.Cursor constructor.
ie,
tweepy.Cursor(api.search, q='to:3NASA', tweet_mode='extended').items(limit)
This should give you a result where each tweet contains a property called full_text instead of the usual text.

Thanks for such a prompt answer! It's working now!

Using the following code snip but getting an error:
Code Snip:
for tweet in tweepy.Cursor(api.search,q=q,rpp=100,result_type='recent',include_entities=True,lang='en',tweet_mode= 'extended').items(i):
Error:
AttributeError: 'Status' object has no attribute 'text'


Looks great, but doesn't update

I tried this and the previous code. Both look great, but seem to only snapshot the background at initialisation. When you move something new behind it, the blurred background doesn't update.

Morning, i found this library via random . Search for blureffect like UWP. Change   ACCENT_ENABLE_ACRYLICBLURBEHIND
to  ACCENT_ENABLE_BLURBEHIND . Works for me really great. Doesnt lag and most important, change or move to another window, doesnt drop blur effect.
Best regards.


RUMM-1268 let user enable/disable background RUM events

What does this PR do?
Let customers enable/disable tracking of background (view-less) events.

Codecov Report

Merging #652 (1580348) into master (04e3dc6) will decrease coverage by 0.18%.
The diff coverage is 94.44%.

@@             Coverage Diff              @@
##             master     #652      +/-   ##
============================================
- Coverage     88.31%   88.13%   -0.18%
+ Complexity     1637     1635       -2
============================================
  Files           182      182
  Lines          5363     5376      +13
  Branches        665      666       +1
============================================
+ Hits           4736     4738       +2
- Misses          399      403       +4
- Partials        228      235       +7

Impacted Files
Coverage Δ

...droid/rum/internal/domain/scope/RumSessionScope.kt
97.67% <66.67%> (+0.06%)
:arrow_up:

...atadog/android/core/configuration/Configuration.kt
96.06% <100.00%> (+0.08%)
:arrow_up:

.../main/kotlin/com/datadog/android/rum/RumMonitor.kt
77.78% <100.00%> (+0.85%)
:arrow_up:

...lin/com/datadog/android/rum/internal/RumFeature.kt
94.29% <100.00%> (+0.08%)
:arrow_up:

...d/rum/internal/domain/scope/RumApplicationScope.kt
100.00% <100.00%> (ø)

.../android/rum/internal/monitor/DatadogRumMonitor.kt
95.61% <100.00%> (+0.08%)
:arrow_up:

...g/internal/domain/event/DdSpanToSpanEventMapper.kt
91.84% <0.00%> (-6.12%)
:arrow_down:

...m/internal/domain/scope/ExternalResourceTimings.kt
73.53% <0.00%> (-5.88%)
:arrow_down:

...nternal/tracking/OreoFragmentLifecycleCallbacks.kt
89.74% <0.00%> (-5.13%)
:arrow_down:

...nal/tracking/AndroidXFragmentLifecycleCallbacks.kt
87.80% <0.00%> (-4.88%)
:arrow_down:

... and 7 more


[SDK Automation - JS] Support and enable breaking change detection for Modular

We will keep the same contract using in MPG to detect/present the breaking changes in the SDK automation CI framework.
@MaryGao @qiaozha
### Parity with existing tooling in Track2
- [ ] https://github.com/Azure/azure-sdk-tools/issues/8303
- [ ] https://github.com/Azure/azure-sdk-tools/issues/8307

### New functionality
- [ ] https://github.com/Azure/azure-sdk-tools/issues/8305
- [ ] https://github.com/Azure/azure-sdk-tools/issues/8301
- [ ] https://github.com/Azure/azure-sdk-tools/issues/8304
- [ ] https://github.com/Azure/azure-sdk-tools/issues/8306
- [ ] https://github.com/Azure/azure-sdk-tools/issues/8317

fix #8303 in #8332

Add a dashboard for other issues related to JS SDK Automation.
Please link new issue to the new dashboard for other issue except for modular support

Related issue: #8580

We will start the testing with beta package of the release tool.

No sub-layer for modular needs to detect now


xinput controller not working with Felix.

I check the video game controller properties (using Windows 10 64bit) and all the buttons are working. But in the emulator when I try to map the controls the emulator does not recognize the button presses.

I use Autohotkey to map joystick buttons to keyboard keys.
For example Jaguar pad:
; Jag-A
Joy1::
Send {y down}  ; Hold down the left-arrow key.
KeyWait Joy2  ; Wait for the user to release the controller button.
Send {y up}  ; Release the left-arrow key.
return
; Jag-b
Joy2::
Send {x down}  ; Hold down the left-arrow key.
KeyWait Joy2  ; Wait for the user to release the controller button.
Send {x up}  ; Release the left-arrow key.
return


UX: Speed-up checkpoint submission logic

Placeholder as a reminder

No longer applies since we deprecated Lotus.


HTML emails getting rejected due to No attachments allowed

Is it possible to enable attachments?

I have resolved the issue.
Big shout out to @faust64 for keeping up with his repo and having some hotfixes to get to a working state


build an integration page which can show all of OpenSDS's documents.

What this PR does / why we need it:
build an integration page which can show all of OpenSDS's documents. when I update info on opensds's official website(https://www.opensds.io/), there is a requirement for a URL to show all the opensds documents, we haven't one, so I did it.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
you can reviewer the demo on this page: http://opensds-mxr.readthedocs.io/en/latest/
Release note:

Coverage remained the same at 59.012% when pulling bf3f28896e569ee6312233dbac1d9fedb3b67ff5 on xiangrumei:master into 7b65ae5fd9f113ab562fb697b58b00f3fc49e30b on opensds:development.

Coverage remained the same at 59.012% when pulling bf3f28896e569ee6312233dbac1d9fedb3b67ff5 on xiangrumei:master into 7b65ae5fd9f113ab562fb697b58b00f3fc49e30b on opensds:development.

Coverage remained the same at 59.012% when pulling bf3f28896e569ee6312233dbac1d9fedb3b67ff5 on xiangrumei:master into 7b65ae5fd9f113ab562fb697b58b00f3fc49e30b on opensds:development.

Coverage remained the same at 59.012% when pulling bf3f28896e569ee6312233dbac1d9fedb3b67ff5 on xiangrumei:master into 7b65ae5fd9f113ab562fb697b58b00f3fc49e30b on opensds:development.

LGTM


Fix parse token expiration

Solves #2649 issue without breaking API changes.

Fixed date parsing and allow 24-hour format :smile:
Add support for tokens that include the timezone offset instead of the timezone, we found both in our logs :man_shrugging:

If you prefer I could also make it optional (TokenExpiration *Timestamp) so that it's not required to check for "is timestamp equals 0001-01-01)
Or by adding a new type TokenExpiration time.Time with a func IsValid for a token that has no expiration header?!
But both would change the public API and for my first PR here I focused on fixing just the bug without an API change.

nice one, thanks

@gmlewis thanks for the feedback, updated the PR. I took everything. :+1:

Thank you, @valbeat !
Merging.


favicon is not showing in wagtail admin.

Make sure to follow one of the issue templates we've got, otherwise the issue might be closed immeditely

Not exactly sure what you mean. Maybe the Wagtail docs about replacing the favicon can help.


Can Linux also be supported?

Hi @yosemiteyss,
thanks again for your work on Windows!
I want to ask you if it is possible to add compatibility for linux too.
Thanks in advance and have a nice day!

Hi, I will look into it once I'm free.

Hi, I has added Linux support in version 1.2.0. This issue can be closed.


Identation

Indentation with 4 spaces works for underdone list but not when using 2 spaces.
This is related to the lack of #851 https://spec.commonmark.org/0.29/#lists

This is by design, as Python-Markdown follows the original Markdown rules (which require 4 spaces), not CommonMark.
This is documented in https://python-markdown.github.io/#differences.

The syntax rules clearly state that when a list item consists of multiple paragraphs, “each subsequent paragraph in a list item must be indented by either 4 spaces or one tab” (emphasis added). However, many implementations do not enforce this rule and allow less than 4 spaces of indentation. The implementers of Python-Markdown consider it a bug to not enforce this rule.


update readme formats

@all-contributors
please add @ekmanib for documentation.
please add @CtJiao for documentation.

https://github.com/all-contributors
please add @ekmanib for documentation.
please add @CtJiao for documentation.

@all-contributors
please add @ekmanib for documentation.
please add @CtJiao for documentation.

@all-contributors
please add @CtJiao for documentation.


The code expands automatically

var_ = ()
if True:
    pass
if False:
    pass
if True:
    pass
....

If var_ = () is mistakenly converted to var_ = ( all subsequent ifs are expanded
And this is very annoying. Is there no way to prevent this from happening?

duplicate of https://github.com/microsoft/vscode/issues/137890


Egress Lockdown: Enable and Toggle

Which issue this PR addresses:

Fixes https://msazure.visualstudio.com/AzureRedHatOpenShift/_workitems/edit/13137954/
What this PR does / why we need it:

This feature will enable the egress lockdown feature by default on new clusters while also allowing current clusters to be admin-upgraded with the new feature.
Test plan for issue:

[x] Update unit test for default cluster features
[x] Update unit test for bi-directional toggling of the feature in admin update
[x] Write new e2e test for internal container registry, since that takes a path from node -> gateway -> storageaccount of the registry
[x] Manual testing in int-like env for:

[x] Current cluster upgrade:

[x] Creating cluster w/o egress lockdown
[x] Admin patch that cluster with the feature
[x] Make sure all is well

[x] New default behavior:

[x] Creating cluster w/ default (egress lockdown)
[x] Make sure all is well

[x] Ensure only admins can update the Egress flag

Is there any documentation that needs to be updated for this PR?

/azp run e2e


AppCacheBuster not used to get Component-preload.js

OpenUI5 version: 1.44.6
Browser/version (+device/version): Chrome latest
Any other tested browsers/devices(OK/FAIL): None
URL (minimal example if possible):
User/password (if required and possible - do not post any confidential information here):
Steps to reproduce the problem:

Set up a project which uses the AppCacheBuster mechanism
Generate a Component-preload.js for the project
Load the project in the browser and watch the network requests in dev tools

What is the expected result?
I expect that the AppCacheBuster would change the request URL to get Component-preload.js with the timestamp which it got from sap-ui-cachebuster-info.json
What happens instead?
The Component-preload.js is requested without injecting the Cachebuster timestamp into the URL. Thus, after an update of the application the old Component-preload.js file is loaded from the browser cache instead of requesting the new one from the server.
Any other information? (attach screenshot if possible)

Hi @Frank683,
it will be really help full if you provide and example where processors can easily reproduce the issue.
Thanks and kind regards,
Petyo (openUI5 Dispatcher)

@PetyoKostakov I have created a small example on plnkr:
http://embed.plnkr.co/GxRaclAZAeONS80ysXSg/
In the dev tools you will see that for Component-preload.js the app cachebuster timestamp is not inserted into the request URL whereas this will be done for other files (like Component.js) in my example.

Dear all,
Any update here?
This is an urgent error for us since updates to the application are not visible at the clients unless they manually clear their browser cache.
I can't tell hundreds of users to clear their browser cache. Most of them don't even know what that is!
Please remove the "author action" badge and provide a solution.
Since we're a SAP customer do you think it would speed up the issue if I opened an error report on SAP OSS platform directly?
Best regards,
Frank

Dear Frank683!
"Since we're a SAP customer do you think it would speed up the issue if I opened an error report on SAP OSS platform directly?" I fear the answer is yes.
Best regards,
Thomas

What a pity!
I have just opened incident "149264 / 2017 UI5 Application Cachebuster doesn't work for Component-preload.js" on SAP support portal
ID:002075129500001492642017

Dear Frank, as replied in the ticket: the AppCacheBuster as of today doesn't consider the asynchronous Component preload. Those URLs will just not get prefixed. If you use the synchronous preload, then the AppCacheBuster should work. I know this is not a solution but at least a workaround for the caching problem which is IMO more critical than the performance for loading the component. Let's follow-up in the ticket.


Update llamacpp.ipynb

Replaced Callbackmanager with BaseCallbackManager since Callbackamanager throws error in Llama-cpp loading docs

thanks for flagging @aksj98!