Moving the service file

Can you move the service file to /lib/systemd/system/?
/etc/systemd/system/ is used for local system configurations, while packages should install their service files in /lib/systemd/system/.
This allows users to override the provided service file if needed.
See systemd.unit(5)
quoted from here: https://aur.archlinux.org/packages/betterlockscreen/
comment by twouters
Wanted to let you know, seems like a legit reason. Can't change the aur package until the weekend tho

Yeah that would be good, go ahead

done


solc: handle conflicting / pairs properly

as highlighted here https://github.com/foundry-rs/foundry/issues/1488
when emitting duplicated file + contract name pairs we end up overwriting them.
This is a scenario I did not anticipate when implementing the output handler and a limitation of the current layout file/contract-name.sol
we handle multiple versions with a version suffix in the file name.
if there are multiple file+name pairs it's guaranteed that the file is in another folder, meaning parent(file) is always unique. so perhaps if there are conflicts, we add the parent(file)|project roo to the output path.
either has out/parent(file)/file/contract.sol

I would have expected this to be an anti pattern..agree it's an edge case we hadn't considered. When does this happen?

Artifacts are in out/<filename>/<contract>.json, so if you have something like:
src/a/Token.sol
src/b/Token.sol

and both of them have a similar named contract, then you'd have a conflict in the out directory


feat: new classes for result and multiple new related functions

New Result Classes.

Wrap up the results from evaluation functions to classes;
3 classes: CumulativeResults, WindowedResults, PrequentialResults;
Multiple manners to access the results, e.g., results.accuracy() or results.cumulative.accuracy() or results['cumulative'].accuracy();
Fix the windowed results: now it does not only return the last window's results, it returns an array;
Suit all (existing) learning tasks. if the metrics that have been called is not available, shows {metric name} not exist;
New function to write the results into file(s). For cumulative and windowed results, create one csv file for them, for prequential results, create a folder and two csv files, one for cumulative, one for windowed.

Update the impacted test files.

Hi @YibinSun , let's have a meeting on Monday to finalise this PR

Hi @YibinSun , let's have a meeting on Monday to finalise this PR

Hi @hmgomes, Great, I will try to change it based on the discussion during Thursday's meeting before this meeting!


Prevent crashes when loading tensor slices with unsupported types.

Also fix the Tensor(const TensorShape&) constructor swapping the LOG(FATAL)
messages for the unset and unsupported types.
PiperOrigin-RevId: 392695027
Change-Id: I4beda7db950db951d273e3259a7c8534ece49354

@pranve Can you please sign CLA. Thanks!


Tracing for Index Space Launches with Postconditions

Support for tracing with index space launches with postconditions is incomplete.
https://gitlab.com/StanfordLegion/legion/blob/master/runtime/legion/legion_tasks.cc#L7618-7627

This should be fixed by commit 152886f4.

The CI seems happy now. Closing the issue.


Update test files (in.txt, expected_dos.txt, etc.) - part deux

Merged into master, closing

Need to add seek, trade and set.

Pushed to master.  Closed.


[WIP] Moved prombench to subdirectory prombench

See #257

cc @VladMasarik

@krasi-georgiev make build is working and docker images are getting built, why do we need to have a separate Makefile for every tool then?


Modify command for installing CLI

When I tried to install the Stellar CLI based on the instructions (https://developers.stellar.org/docs/build/smart-contracts/getting-started/setup), I found the below command did not work:
cargo install --locked stellar-cli --version v22.0.1 --features opt
I could successfully install the package 'stellar-cli v22.0.1' with the below command, simply removing 'v' from 'v22.0.1':
cargo install --locked stellar-cli --version 22.0.1 --features opt

Thanks for reporting! Fix is in progress here:

https://github.com/stellar/stellar-docs/pulls/1116


Use latest version of notary server in trust sandbox docs

cc @cyli @endophage : I'm fine with just pointing to the latest build off master but we might want to wait until we cut v0.4.0 (scheduled for this week) and point to that tag instead.
Points the trust sandbox to use the latest version of notary server, which has refreshed certificates and new server functionality.  I went through the content trust sandbox docs with this change and everything worked as expected.
Fixes https://github.com/docker/notary/issues/949
- A picture of a cute animal (not mandatory but encouraged)

Signed-off-by: Riyaz Faizullabhoy<EMAIL_ADDRESS>

LGTM, thanks!

LGTM!

@riyazdf so do you want to merge or wait for 0.4?

@justincormack good to merge :)


docs: Add shadcn UI example

I've tested a few, so far so good 🙌

@edmundhung I am running into some issues implementing CheckboxGroup locally (node v18.19.0):

'Control' cannot be used as a JSX component.
Its return type 'ReactNode' is not a valid JSX element.
Type 'undefined' is not assignable to type 'Element | null'.

Have you seen this error elsewhere? I have not seen anyone report it on the Conform project

Do you see the same error running the example? It could be issue with your react type package version or the tsconfig


Update Alibi Anchor Text Example

Provides an improved example
Shows use of custom config to change the explanation algorithm settings for Anchor Text

This change is

/assign @yuzisun

/lgtm
/approve


PDFs do not build

Tried on both Ubuntu and Mac. Same (unclear) error in _main.log
! Extra alignment tab has been changed to \cr.
 \endtemplate
l.1800 &
= &
Here is how much of TeX's memory you used:
13684 strings out of 492649
194607 string characters out of 6129622
303592 words of memory out of 5000000
17170 multiletter control sequences out of 15000+600000
87392 words of font info for 153 fonts, out of 8000000 for 9000
1141 hyphenation exceptions out of 8191
45i,13n,45p,601b,461s stack positions out of 5000i,500n,10000p,200000b,80000s
!  ==> Fatal error occurred, no output PDF file produced!

Same here (except for the numbers).

Thanks.  That was just the tip of the iceberg.  bookdown is happy formatting html with all kinds of errors in it, but LaTeX is pickier.  I'm fixing all this so it'll compile.


Backport "Make apply proxies work with overloaded ctors" to LTS

Backports #19464 to the LTS branch.
PR submitted by the release tooling.
[skip ci]

No regressions detected in the community build up to lts-19605.
Reference


NodeAffinity in  Pixie operator configs

Hello! Is it possible to add nodeAffinity support to operator configs like this?
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:

matchExpressions:
key: beta.kubernetes.io/os
operator: In
values:
linux

This can be useful if Windows nodes are olso present in kubernetes cluster. This will prevent Pixie pods to be scheduled on Windows nodes.
Thank you!

Thanks for the suggestion! We've gone ahead and applied them to our operator configs, and also our vizier YAMLs.

@aimichelle you said you applied this to your operator configs but can I ask where exactly?
Having problem with vizier-pem DS trying to run on Fargate but I don't see anywhere to set the affinity rules:
https://github.com/pixie-io/pixie/blob/main/k8s/operator/helm/values.yaml

@cdenneen would the nodeSelector nested within the pod: key work for you use case?
Can you explain more on the environment you are deploying Pixie to? EKS Fargate still does not support eBPF to my knowledge, so I don't believe your environment is supported.

You can have mixed environments with Fargate, Windows and EC2 Linux so the affinity is necessary. NodeSelectors I don’t believe will work properly in this case


asciimath template literal

This only occurred to me because because #7 said:

Since the Viz.js dependency is lazily loaded this would be a very small addition to the stdlib

Asciimath is pretty great when I'm typing quick math and I don't feel like going all-in on Latex.  It's roughly, "type math the way you would in your code or your TI-83 calculator".
asciimath = {
   const amToTex = await require('https://wzrd.in/standalone/asciimath-to-latex/');
   return function(strings, ...args) {
       return tex(strings.map(amToTex), ...args.map(amToTex));
   };
}

Then again, Viz.js is surely a much more stable dependency than asciimath-to-latex, and dot\`` adds a totally new dimension of functionality whereas this is just a variation, so understood if you simply close with prejudice.

https://beta.observablehq.com/@anandthakker/ascii-math

Thanks for the suggestion, Anand. Our current plan is to try to keep the stdlib small, so we’re going to stick with KaTeX/LaTeX for now. But as you discovered you can always require/import from npm or another notebook to use something outside of stdlib as you prefer.


GC stress

Mode that triggers GC on every N-th allocation and/or PInvoke transition.

Hi I've changed the code as suggested:GetGCgen0size () const { return 64 * 1024; }

Hello, I have managed to reproduce the issue in an isolated code set. The code works for 'dotnet run' on linux but fails in the way mentioned in #4676 for native compilation after a short time (running on Ubuntu 14.04.5 LTS). I've zipped up C/C++ the share object code and the C# code to get the issue to happen and attached them to this post. The zip file contains:
\arc-lib\ - run build.sh to produce libarc.so and set up your LD_LIBRARY_PATH to point at this shared object. I used g++ 4.8.4 to build this.
ConsoleApp2 - build it as native code and run and pretty soon you  should get the following Segmentation fault:
Process 12773 stopped

thread #3: tid = 12777, 0x00000000004161ec ConsoleApp2EEType::get_BaseSize(this=0x0000000000317fe8) + 12 at eetype.h:365, name = 'ConsoleApp2', stop reason = signal SIGSEGV: invalid address (fault address: 0x317fec)   frame #0: 0x00000000004161ec ConsoleApp2EEType::get_BaseSize(this=0x0000000000317fe8) + 12 at eetype.h:365
362
363 	#ifndef RHDUMP
364 	    UInt32 get_BaseSize()
-> 365 	        { return m_uBaseSize; }
366
367 	    UInt16 get_ComponentSize()
368 	        { return m_usComponentSize; }
(lldb) bt
thread #3: tid = 12777, 0x00000000004161ec ConsoleApp2`EEType::get_BaseSize(this=0x0000000000317fe8) + 12 at eetype.h:365, name = 'ConsoleApp2', stop reason = signal SIGSEGV: invalid address (fault address: 0x317fec)

frame #0: 0x00000000004161ec ConsoleApp2EEType::get_BaseSize(this=0x0000000000317fe8) + 12 at eetype.h:365 frame #1: 0x00000000004ec7e5 ConsoleApp2MethodTable::GetBaseSize(this=0x0000000000317fe8) + 21 at gcenv.h:91
frame #2: 0x00000000004936a9 ConsoleApp2WKS::gc_heap::mark_object_simple(unsigned char**) [inlined] WKS::my_get_size(ob=0x00007fffdf199c68) + 34 at gc.cpp:8897 frame #3: 0x0000000000493687 ConsoleApp2WKS::gc_heap::mark_object_simple(po=0x00007fffeec59450) + 535 at gc.cpp:18171
frame #4: 0x00000000004a1d32 ConsoleApp2WKS::gc_heap::mark_through_cards_for_large_objects(void (*)(unsigned char**), unsigned int) [inlined] WKS::gc_heap::mark_through_cards_helper(poo=0x00007fffeec59450, n_gen=0x00007fffddfb3cc0, cg_pointers_found=0x00007fffddfb3cd0, fn=(ConsoleApp2WKS::gc_heap::mark_object_simple(unsigned char**) at gc.cpp:18157), nhigh="\xa0q���, next_boundary="p\x01�)(unsigned char**), unsigned char*, unsigned char*) + 79 at gc.cpp:27545
frame #5: 0x00000000004a1ce3 ConsoleApp2WKS::gc_heap::mark_through_cards_for_large_objects(fn=(ConsoleApp2WKS::gc_heap::mark_object_simple(unsigned char**) at gc.cpp:18157), relocating=NO)(unsigned char**), unsigned int) + 7539 at gc.cpp:31857
frame #6: 0x000000000047887f ConsoleApp2WKS::gc_heap::mark_phase(condemned_gen_number=0, mark_only_p=NO) + 3631 at gc.cpp:19662 frame #7: 0x000000000046fbe7 ConsoleApp2WKS::gc_heap::gc1() + 519 at gc.cpp:15262
frame #8: 0x000000000048cbe3 ConsoleApp2WKS::gc_heap::garbage_collect(n=0) + 3395 at gc.cpp:16853 frame #9: 0x0000000000461861 ConsoleApp2WKS::GCHeap::GarbageCollectGeneration(this=0x0000000000dfb1e0, gen=0, reason=reason_alloc_soh) + 2049 at gc.cpp:35188
frame #10: 0x0000000000466a0f ConsoleApp2WKS::gc_heap::try_allocate_more_space(acontext=0x00007fffddfb55e8, size=56, gen_number=0) + 1503 at gc.cpp:13066 frame #11: 0x0000000000466b83 ConsoleApp2WKS::gc_heap::allocate_more_space(acontext=0x00007fffddfb55e8, size=56, alloc_generation_number=0) + 35 at gc.cpp:13362
frame #12: 0x00000000004e0295 ConsoleApp2WKS::GCHeap::Alloc(gc_alloc_context*, unsigned long, unsigned int) + 277 at gc.cpp:13393 frame #13: 0x00000000004e0180 ConsoleApp2WKS::GCHeap::Alloc(this=0x0000000000dfb1e0, context=0x00007fffddfb55e8, size=56, flags=0) + 96 at gc.cpp:34534
frame #14: 0x0000000000413f63 ConsoleApp2::RhpGcAlloc(pEEType=0x0000000000d48088, uFlags=0, cbSize=56, pTransitionFrame=0x00007fffddfb4940) + 211 at gcrhenv.cpp:273 frame #15: 0x00000000005e31e0 ConsoleApp2RhpNewArrayRare + 58 at unixasmmacrosamd64.inc:650
frame #16: 0x00000000006074a5 ConsoleApp2String__FastAllocateString + 77 at String.cs:632 frame #17: 0x000000000063f870 ConsoleApp2String__CreateStringFromEncoding + 204 at String.cs:606
frame #18: 0x000000000061f083 ConsoleApp2S_P_CoreLib_System_Text_Encoding__GetString + 215 at Encoding.cs:1084 frame #19: 0x0000000000619d3f ConsoleApp2String__CreateStringForSByteConstructor + 147 at String.cs:294
frame #20: 0x000000000060deaf ConsoleApp2String__Ctor_3 + 183 at String.cs:256 frame #21: 0x0000000000640651 ConsoleApp2ConsoleApp2_RecordUpdate__get_Field + 69 at Program.cs:47
frame #22: 0x00000000006313a9 ConsoleApp2ConsoleApp2_ConsoleApp2_CallbackProcessors__OnFeedUpdated + 157 at Program.cs:101 frame #23: 0x000000000064040a ConsoleApp2 at ThrowHelper.cs:74 frame #24: 0x00007fffddfbfdbf libarc.soProcessCallbacks + 63
frame #25: 0x00007fffddfc1bf7 libarc.sovoid std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) + 37 frame #26: 0x00007fffddfc1b51 libarc.sostd::_Bind_simple<void (*())()>::operator()() + 27
frame #27: 0x00007fffddfc1aea libarc.sostd::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() + 28 frame #28: 0x00007ffff7b87a60 libstdc++.so.6___lldb_unnamed_symbol191$$libstdc++.so.6 + 32
frame #29: 0x00007ffff6d93184 libpthread.so.0start_thread(arg=0x00007fffddfb5700) + 196 at pthread_create.c:312 frame #30: 0x00007ffff6ac037d libc.so.6__clone + 109 at clone.S:111

If I can help any further just let me know.
GCIssue.zip

Seen (maybe 1 out of 5 runs) a slight different callstack, not sure if this helps in term of debugging:
(lldb) bt

thread #3: tid = 13711, 0x00007ffff69fcc37 libc.so.6`__GI_raise(sig=6) + 55 at raise.c:56, name = 'ConsoleApp2', stop reason = signal SIGABRT

frame #0: 0x00007ffff69fcc37 libc.so.6__GI_raise(sig=6) + 55 at raise.c:56 frame #1: 0x00007ffff6a00028 libc.so.6__GI_abort + 328 at abort.c:89
frame #2: 0x00007ffff69f5bf6 libc.so.6__assert_fail_base(fmt=<unavailable>, assertion=<unavailable>, file=<unavailable>, line=<unavailable>, function=<unavailable>) + 294 at assert.c:92 frame #3: 0x00007ffff69f5ca2 libc.so.6__GI___assert_fail(assertion=, file=, line=, function=) + 66 at assert.c:101
frame #4: 0x000000000047b79c ConsoleApp2WKS::gc_heap::plan_phase(condemned_gen_number=0) + 9980 at gc.cpp:21793 frame #5: 0x000000000046fbf9 ConsoleApp2WKS::gc_heap::gc1() + 537 at gc.cpp:15265
frame #6: 0x000000000048cbe3 ConsoleApp2WKS::gc_heap::garbage_collect(n=0) + 3395 at gc.cpp:16853 frame #7: 0x0000000000461861 ConsoleApp2WKS::GCHeap::GarbageCollectGeneration(this=0x0000000000dfb1e0, gen=0, reason=reason_alloc_soh) + 2049 at gc.cpp:35188
frame #8: 0x0000000000466a0f ConsoleApp2WKS::gc_heap::try_allocate_more_space(acontext=0x00007fffddfb55e8, size=56, gen_number=0) + 1503 at gc.cpp:13066 frame #9: 0x0000000000466b83 ConsoleApp2WKS::gc_heap::allocate_more_space(acontext=0x00007fffddfb55e8, size=56, alloc_generation_number=0) + 35 at gc.cpp:13362
frame #10: 0x00000000004e0295 ConsoleApp2WKS::GCHeap::Alloc(gc_alloc_context*, unsigned long, unsigned int) + 277 at gc.cpp:13393 frame #11: 0x00000000004e0180 ConsoleApp2WKS::GCHeap::Alloc(this=0x0000000000dfb1e0, context=0x00007fffddfb55e8, size=56, flags=0) + 96 at gc.cpp:34534
frame #12: 0x0000000000413f63 ConsoleApp2::RhpGcAlloc(pEEType=0x0000000000d48088, uFlags=0, cbSize=56, pTransitionFrame=0x00007fffddfb4940) + 211 at gcrhenv.cpp:273 frame #13: 0x00000000005e31e0 ConsoleApp2RhpNewArrayRare + 58 at unixasmmacrosamd64.inc:650
frame #14: 0x00000000006074a5 ConsoleApp2String__FastAllocateString + 77 at String.cs:632 frame #15: 0x000000000063f870 ConsoleApp2String__CreateStringFromEncoding + 204 at String.cs:606
frame #16: 0x000000000061f083 ConsoleApp2S_P_CoreLib_System_Text_Encoding__GetString + 215 at Encoding.cs:1084 frame #17: 0x0000000000619d3f ConsoleApp2String__CreateStringForSByteConstructor + 147 at String.cs:294
frame #18: 0x000000000060deaf ConsoleApp2String__Ctor_3 + 183 at String.cs:256 frame #19: 0x00000000006406b1 ConsoleApp2ConsoleApp2_RecordUpdate__get_Value + 69 at Program.cs:58
frame #20: 0x00000000006313b6 ConsoleApp2ConsoleApp2_ConsoleApp2_CallbackProcessors__OnFeedUpdated + 170 at Program.cs:101 frame #21: 0x000000000064040a ConsoleApp2 at ThrowHelper.cs:74 frame #22: 0x00007fffddfbfdbf libarc.soProcessCallbacks + 63
frame #23: 0x00007fffddfc1bf7 libarc.sovoid std::_Bind_simple<void (*())()>::_M_invoke<>(std::_Index_tuple<>) + 37 frame #24: 0x00007fffddfc1b51 libarc.sostd::_Bind_simple<void (*())()>::operator()() + 27
frame #25: 0x00007fffddfc1aea libarc.sostd::thread::_Impl<std::_Bind_simple<void (*())()> >::_M_run() + 28 frame #26: 0x00007ffff7b87a60 libstdc++.so.6___lldb_unnamed_symbol191$$libstdc++.so.6 + 32
frame #27: 0x00007ffff6d93184 libpthread.so.0start_thread(arg=0x00007fffddfb5700) + 196 at pthread_create.c:312 frame #28: 0x00007ffff6ac037d libc.so.6__clone + 109 at clone.S:111

Thank you! We will take a look.

No problems, I have been trying out the test code and initially I was getting it to fail within the first 5-10 seconds every time (a good 20+ runs), I currently have a run going that has survived around a minute of running and no crash as of yet. Depending on your hardware (I'm running linux on a VM on windows on a pretty recent i7) it could be a little bit more difficult to recreate but hopefully the test will hit it the issue for you. I'll try change some of the parameters in the testing code see if I can increase the chances of it happening.

After that one successful run that I killed in the end and a bit of playing around, it seems what I sent is a pretty good attempt at recreating the issue, the next 5 runs all crashed in a few seconds.

Here is the minimal repro:
using System;
using System.Collections.Generic;

internal class Program
{
    static public void Main()
    {
        for (;;)
        {
            List<KeyValuePair<string, string>> fields = new List<KeyValuePair<string, string>>();

            for (int i = 0; i < 50000; i++)
            {
                fields.Add(new KeyValuePair<string,string>(new string('x', 10), new string('y', 10)));
            }
         }
     }
 }

Hi Jkotas, I've tried the code here and it's crashing every time, so nothing to do with the PInvoke! I was wondering if it's too early in the project to ask about optimisation? I found the issue while running some of our system stress tests on the natively compiled output. If I reduce the iterations in stress test to a very small number so the gc issue isn't always hit, I'm seeing a big different in the time the test takes to complete for native against JIT, here are the results from 3 runs of the same test on various frameworks/operating systems:
Framework                            Run 1 (ms)  Run 2 (ms)  Run 3 (ms)  Average (ms)
.Net Framework 2.0                      978            976             969             974
.Net Framework 4.0                      910            895             870             892
.Net Core 2.0 Window 7               882            883             869             878
.Net Core 2.0 Ubuntu 14.04         878            885             858             874
.Net Corert Ubuntu 14.04          2483          2464            2461           2469   *
The .Net code is calling a tcpip unmanaged protocol handling .dll/.so, then in .Net there are basically several dispatching threads and lots of collection/string based operations. I'm not sure if at this stage such a discrepancy is expected with Corert or not?

@dlewis-arcontech Could you open another issue for the perf findings? Some slowdown is expected because of known perf issues (such as #2640, #2393, or #2394), but providing a profile could help us rule out if this is known or unknown. Just to make sure - this is from a Release build of CoreRT, right? (The repo was built as Release, and the project was published as Release.)

@MichalStrehovsky good spot this was indeed a debug build! I did note a difference initially when I started to run the tests in Release build but then I quickly moved to Debug build to help investigate the issue we are discussing here and didn't change back when I took the above results. I've re-run the last 2 columns above in Release build and managed to increase the iterations count in the tests before hitting any issues:

Framework
Run 1 (ms)
Run 2 (ms)
Run 3 (ms)
Average (ms)

.Net Core 2.0 Ubuntu 14.04
1470
1458
1457
1462

.Net CoreRT Ubuntu 14.04
1773
1792
1779
1781

CoreRT a little higher but not dramatically, could well be one of the issues you have already noted. How should I proceed, should I still create an issue?

I forgot to mention, just to check in case there are any optimizations I'm missing, to build CoreRT I am running:
.\build.sh Release
Then reference IlcPath to the release build, then my console app is using a dependent .Net dll, so as well as having in the main csproj:
<ItemGroup>     <IlcReference = "xxx\dll.csproj" />
I also have:
<ItemGroup>     <IlcReference Include="[release build path].dll />
Then I run:
dotnet build /t:LinkNative --configuration Release
Or for the JIT run above I use:
dotnet run Release
Regards.

Given stacktraces for some of the crashes reported by @dlewis-arcontech (e.g. https://github.com/dotnet/corert/issues/4676#issuecomment-339628519), the perf bottlenect is likely in the un-optimized comparers (https://github.com/dotnet/corert/issues/763). We should have all parts required to implement the optimization now. @MichalStrehovsky feel free to take it if you have some time - I am unlikely to find time for it soon.

@dlewis-arcontech, thank you so much for all the data that you provided and your help with diagnosing the issues! :)

@sergiy-k my pleasure. As things progress with CoreRT and WebAssembly I'll be committing more of our resource to porting our .Net code, Unit/System tests to .Net Standard/.Net Core and getting it natively compiled and running under Windows and Linux. If I encounter any problems I'll raise an issue and I'm always happy to help to investigate.

@dlewis-arcontech #4907 should fix the GC crash.

@MichalStrehovsky feel free to take it if you have some time - I am unlikely to find time for it soon.

OK, I'll have a look

I have updated and re-run the problem test and can confirm it now passes, thanks! I'll move on to attempting to run the entire test suite.


Closing a Pull Request Sends Back Validation Errors Related to Base Branch of PR

Closing a pull request via the "Update a Pull Request" end point https://docs.github.com/en/rest/reference/pulls#update-a-pull-request
Sending in a request body that only alters state yields an error message:
422 Unprocessable Entity: [{"message":"Validation Failed","errors":[{"message":"Ref must be a string","resource":"PullRequest","field":"base","code":"invalid"}],"documentation_url":"https://docs.github.com/rest/reference/pulls#update-a-pull-request"}]
So, I went ahead and altered the flow to retrieve the pull request I am trying to close via the "Get a Pull Request" API call: https://docs.github.com/en/rest/reference/pulls#get-a-pull-request
Then, I made another attempt to close the PR, using a base value of the base.ref field in the response from the get-a-pull-request end point. Request body looked as follows:
{
"state": "closed",
"base": "main"
}
And the API again returned an error, informing me that I cannot update the base value of a closed PR. Error message:
422 Unprocessable Entity: [{"message":"Validation Failed","errors":[{"message":"Cannot change the base branch of a closed pull request.","resource":"PullRequest","field":"base","code":"invalid"}],"documentation_url":"https://docs.github.com/rest/reference/pulls#update-a-pull-request"}]
In both cases, the pull request I was trying to close does actually close. The API call is successfully updating the PR that I am asking it to update.
This feels to me like a bug with the validation on the update pull request end point of the API.
Please let me know if you are able to recreate the scenario/if there is any other helpful information I can provide.
Thank you!

Correct me if I'm wrong, but reading through your report and looking at the documentation of the used endpoints makes me think that this really should be a bug report filed against the GitHub v3 API itself, and that this is explicitly not a bug of this Go client library.
If you agree, then please contact GitHub tech support with your bug report and we can leave this issue open until you hear back and update this issue with their response.
If you disagree, then please help me understand how this is truly a bug of this client library and not a bug of the GitHub v3 API.
Thanks.

Thanks for the quick response Glenn. I do agree that this relates to the v3 API itself, not the Go client library. I have opened this issue in the incorrect place. I have no objection to this issue being closed....I will find the right avenue to report the issue to the API owners themselves.
Thanks again and apologies for the misunderstanding!

Thanks again and apologies for the misunderstanding!

No problem!  Thanks for reporting this to GitHub tech support.
I'll go ahead and close this, but still please feel free to report back your findings here to help others who are facing the same issue.

Sounds good - I've got a ticket open with support (looks like it's a personal ticket so I don't think I can share the link). I will share the results of what is found on this issue when more information comes to light.


Doesn't accept whitespace in file names

Creating chains from files with spaces (e.g. "Kick 01.wav") in the name doesn't work, files also can't be played back in Octachainer.

I have thoroughly tested that the current release (v1.3.1) handles white spaces. Whatever the issue was, it appears fixed now. So closing this.


Possibility to specifiy backup folder

Is your enhancement request related to a problem? Please describe.
The Auto-Backup settings should include a way to specify a folder on the lokal drive.
Describe the solution you'd like.
A simple input field where we put in the exact folder path should do it.

I think this would be how to define the path, maybe utilizing a user defined variable containing the data. Maybe a variation of get*path() would also be needed.

I guess here's a few solutions: https://stackoverflow.com/a/20889432


proto validation: Cluster message should require "connect_timeout" field be set

Cluster message should require "connect_timeout" instead of only checking the duration is greater-than 0.
Description
I'm not sure if this belongs here or in https://github.com/envoyproxy/protoc-gen-validate. Feel free to redirect me there if it's more appropriate
The Cluster message in cluster.proto does not require the connect_timeout field as part of the proto validation. It only requires it to be greater than the default duration (which I assume is 0):
https://github.com/envoyproxy/envoy/blob/main/api/envoy/config/cluster/v3/cluster.proto#L712
When dealing with Go-compiled Cluster messages that don't have the connect_timeout field set, we can call Validate() on them without error. This is because the generated code only cares so validate if the field has been set. It doesn't consider the default value since the duration is nil:
	if d := m.GetConnectTimeout(); d != nil {
		dur, err := ptypes.Duration(d)
		if err != nil {
			return ClusterValidationError{
				field:  "ConnectTimeout",
				reason: "value is not a valid duration",
				cause:  err,
			}
		}

		gt := time.Duration(0*time.Second + 0*time.Nanosecond)

		if dur <= gt {
			return ClusterValidationError{
				field:  "ConnectTimeout",
				reason: "value must be greater than 0s",
			}
		}

	}

This would be trivial to fix and I'm more than happy to just fire off the PR. I'm just not clear on the API implications and whether it would break anything.
Repro steps
I'm running a fairly recent main build:
./envoy_static  version: 2026543d30272e816bd1b46d1e99d50b2212d80f/1.19.0-dev/Modified/DEBUG/BoringSSL
I can successfully validate the following static configuration with that binary:
static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 10000
    filter_chains:
    - filters:

  clusters:
  - name: testing123
    type: LOGICAL_DNS
    connect_timeout: 1s
    load_assignment:
      cluster_name: service_envoyproxy_io
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: www.envoyproxy.io
                port_value: 443

With the following output:
[2021-05-19 21:13:03.586][124567][info][main] [source/server/server.cc:667] runtime: layers:
  - name: base
    static_layer:
      {}
  - name: admin
    admin_layer:
      {}
[2021-05-19 21:13:03.586][124567][info][config] [source/server/configuration_impl.cc:128] loading tracing configuration
[2021-05-19 21:13:03.586][124567][info][config] [source/server/configuration_impl.cc:88] loading 0 static secret(s)
[2021-05-19 21:13:03.586][124567][info][config] [source/server/configuration_impl.cc:94] loading 1 cluster(s)
[2021-05-19 21:13:03.592][124567][info][config] [source/server/configuration_impl.cc:98] loading 1 listener(s)
[2021-05-19 21:13:03.594][124567][info][config] [source/server/configuration_impl.cc:110] loading stats configuration
configuration 'good.yaml' OK

However, removing the connect_timeout field results in a failure to validate.
[txallen@dev-dsk-txallen-2a-95bb9472 ~]$ diff -u3 good.yaml bad.yaml
--- good.yaml	2021-05-19 21:13:00.416024933 +0000
+++ bad.yaml	2021-05-19 21:13:19.331503991 +0000
@@ -11,7 +11,6 @@
   clusters:
   - name: testing123
     type: LOGICAL_DNS
-    connect_timeout: 1s
     load_assignment:
       cluster_name: service_envoyproxy_io
       endpoints:

[txallen@dev-dsk-txallen-2a-95bb9472 ~]$ ./envoy_static --mode validate -c bad.yaml
[2021-05-19 21:21:03.242][128680][info][main] [source/server/server.cc:667] runtime: layers:
  - name: base
    static_layer:
      {}
  - name: admin
    admin_layer:
      {}
[2021-05-19 21:21:03.243][128680][info][config] [source/server/configuration_impl.cc:128] loading tracing configuration
[2021-05-19 21:21:03.243][128680][info][config] [source/server/configuration_impl.cc:88] loading 0 static secret(s)
[2021-05-19 21:21:03.243][128680][info][config] [source/server/configuration_impl.cc:94] loading 1 cluster(s)
[2021-05-19 21:21:03.246][128680][critical][main] [source/server/config_validation/server.cc:62] error initializing configuration 'bad.yaml': Field 'connect_timeout' is missing in: name: "testing123"
type: LOGICAL_DNS
load_assignment {
  cluster_name: "service_envoyproxy_io"
  endpoints {
    lb_endpoints {
      endpoint {
        address {
          socket_address {
            address: "www.envoyproxy.io"
            port_value: 443
          }
        }
      }
    }
  }
}
183412668: "envoy.api.v2.Cluster"

related #16453

The proposed fix is to add a default value.  Previously reported in https://github.com/envoyproxy/envoy/issues/16439


Merge pull request #5 from absolute8511/fix-response-timeout-in-nsqad…

hourly pubsize hover & reverse
fix regression in topic producer info & add NSQd host info

Why copy the rpcstats and errstats to topic? They should be in node stats (not related to a single topic).

remove RPC stats & Err stats.
hourly pub size refine.
statistics rank API test case.


Add some sort of "whyareyourunning" functionality

Proguard has a "whyareyoukeeping" flag which lets devs figure why something is happening. It would be super helpful to learn about why a task is being run, aka its dependencies. Maybe provide this in --scan?

--info and --scan does this.

If outputs were removed, we report that the outputs are missing.
If the inputs have changed, we report that the inputs have changed down to the property level (for non-FileCollection types).
If the input files have changed, we report a subset of the changes to the input files (removed, changed, added).

This is visible in build scans and when comparing builds.  This build failed:
https://enterprise-samples.gradle.com/s/htmj5xe4uxl3k/timeline?task=3scflzwkg4yxw
And we can see compileJava runs because Input property 'classpath' file repos/repo2/com/acme/utils/1.6/utils-1.6.jar has changed.
In the build comparison (with a working build), we can see the successful build has a different classpath for compileJava:
https://enterprise-samples.gradle.com/c/b5hkvdpvrqinu/htmj5xe4uxl3k/task-inputs
--info shows a subset of this information right before the task in question is executed.

No, sorry for not being clearer: I'm asking to be able to see which task dependencies caused it to run. Example: I run assemble, but task x runs. I'd want to see that x ran because assemble depends on it.


Update repositories.txt

A comprehensive Arduino library for interfacing with the IPS-7100 Intelligent Particle Sensor over I2C communication.

@ArduinoBot


Add support for IN predicate with REAL types

previously, REAL is handled thru DOUBLE code path. This PR explicitly support REAL type
To preserve precision, when Input is REAL typed, they are converted to DOUBLE for creating filter and later for comparison.
E2E Testing is blocked due to local presto native setup, but would like to open the PR for early review/feedback.

Thanks for the test case!


Add support for PKCS#8-encoded private keys

Rancher | v2.0.2
User Interface | v2.0.48
I've upgraded our version of Rancher and still having the issue of "Private Key is invalid" when trying to add a certificate.

Temp solution: https://forums.rancher.com/t/adding-certificates-fail-with-private-key-is-invalid-solved/10585

When adding support for PKCS8 when mounting certificates for Rancher, I was already modifying the API for certs. See https://github.com/rancher/rancher/pull/14384 and https://github.com/rancher/rancher/issues/14383.


Create dataset demo does not work

https://freme-project.github.io/tutorials/entity-recognition-against-custom-dataset.html

fixed through https://github.com/freme-project/freme-ner/issues/157


[Question]How to use FindElementByXPath to locate the element on UWP APP

I am writing automation codes to test the UWP APP with WinAppDriver latest version, and use inspect.exe tool to check the element attribute, find the ancestors of this button are:
"System Update" list item
"" list
"" pane
"Lenovo Companion" window
"Lenovo Companion" window
"Desktop 1" pane
[ No Parent]
my locating element code like this:
driver.FindElementByXPath("/pane[@name='Desktop 1']/window[@name='Lenovo Companion']/window[@name='Lenovo Companion']/list[3]/list item[@name='System Update']/button[@name='Check for updates']");
after running, the Exception is invalid XPath expression /pane[@name='Desktop 1']/window[@name='Lenovo Companion']/window[@name='Lenovo Companion']/list[3]/list item[@name='System Update']/button[@name='Check for updates'].
Is this absolute path right?how to locate element with XPath ? and is there any examples to learn?

In line with your issue, I have proposed an enhancement on XPath interpretation #218
I understand that you are looking at Inspect.exe and trying to build the XPath based on the Object names and attribute names present in Inspect.exe
The first letter of the Object name is mostly caps
E.g.
driver.FindElementByXPath("/Pane[@Name='Desktop 1']
Best way is to look at page source!

Hi @questions555,
Yes, @dhapolapankaj is absolutely correct--page source is the way to go, and do look for casing difference on the elements ("pane" vs "Pane").

Hello @dhapolapankaj
I have tried to export Page Source of my UWP, and I want to make sure if I use FindElementByXpath to locate the element , the Absolute path of to located element is based on Page Source or based on Inspect tool, shown as attachments.  I have tried with absolute path in inspect.exe, it doesn't work.  and I also have tried with method like this: driver.FindElementByXPath("/Window[@Name="Lenovo Companion"] //List Item[@Name="System Health"] //Button[@Name="Hardware scan"]") ,this method also doesn't work. Does my method have some problem?

@

@dhapolapankaj I use System.IO.File.AppendAllText(@"D:\pagesource.xml",driver.PageSource) to export page source, and what XML reader tool do you use to view the xml, I read xml with notepad , but the format is disorderly, then I change to html format ,and open with browser.

hi @dhapolapankaj
Thank you very much, I have located the element successfully using FindElementByXPath with absolute path, and know more about difference between the element path with inspect.exe and with pagesource. and thank you again.

Casing being followed in issue #218, closing this ticket.

@questions555 Yes. I was able to make it work..I did this
I did some trial and error and I removed the 1st token of the above XPATH.
Changed /Pane[@Name='Desktop 1']/Window[@Name='FusionReg-MockUI']/Window[@Name='FusionReg-MockUI']/RadioButton[@Name='QA']
to
/Window[@Name='FusionReg-MockUI']/Window[@Name='FusionReg-MockUI']/RadioButton[@Name='QA']
and it worked.

Hello Gentlemen,
I have recently started exploration and coding for automation framework using WinAppDriver (previously working for Automation using Selenium C# for almost 3 years). I came across some issues. Can someone help me with the solution for the following querries I am facing?
(I am using Visual Studio 2019)

Can we use keywords like child, following, sibling, etc. which we use to find XPaths of web-elements for window-elements?
When we get only one attribute value for an window-element as name in Inspect tool and receive error as An element could not be located on the page using the given search parameters, how to deal with the situation?

Thanks in advance :)


KNOX-2806 - Implement a new DoS security provider

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?

@smolnar82 @zeroflag

@zeroflag - please review this one when you have time; thanks!


submitForm should accept an #id as well and the button text

Not sure if this should be the id of the form, or the id of the submit button. What do you think?
Where possible we prefer to hook our tests to page ids, as these are unique and do not change on different locales.

+1


ToSignal(GetTree().CreateTimer(1.0f),"timeout") looks not release memory after timeout

Godot version
Godot_v4.1.2-stable_mono_win64
System information
Windows 11 Godot_v4.1.2-stable_mono_win64
Issue description
in the manual
https://docs.godotengine.org/en/stable/classes/class_scenetree.html#class-scenetree-method-create-timer
GetTree().CreateTimer
after timeout ,it will not release memory
Steps to reproduce
just write this function and keep calling
public async void TEST()
{
await ToSignal(GetTree().CreateTimer(0.2f), SceneTreeTimer.SignalName.Timeout);
}
and you can see the memory and object keep growing
Minimal reproduction project
Bugreport.zip

I'm just curious but since you are on mono how long were your tests? GC takes quite a while to kick in, maybe that's what you see?

you don't need to use createTimer() to create a new Timer every times
instead,You can use a Timer that has already been created in Godot editor, so that just a Timer can do what you want
oneshot and autostart --->false
for example:
Timer timer = GetNode("Timer");
timer.Start();
await ToSignal(timer, "timeout");
I use Godot C# but it's the same in GDscript


MDX-NET models produce a very distinct buzzing sound

I have got better vocal results using MDX-NET compared to other methods. However, I'm getting a persistent buzzing sound in the output generated by this model, irrespective of the input provided and MDX-NET models used. Is there any possible solution to resolve this issue?

I'm getting this too. Just after running it on my clip i use audacity to remove the noise and its completely gone with seemingly no effect on the quality of the audio.

I'm getting this too. Just after running it on my clip i use audacity to remove the noise and its completely gone with seemingly no effect on the quality of the audio.

Yea it's completely gone with denoise effect in adobe audition. (human ears at least) But I'm more concerned about putting those into the dataset, is it going to cause problems

I tried the noise removal in Audacity but didn't work for me


Bin/gust

It would be nice to have our index script executable from the bin directory

I think we can close this now?

Totally!


Memory leak in keras.backend preventing graphs from being GC'ed

In some situations (i.e. when outside of an eager execution context) a Tensor value will be inserted into _GRAPH_LEARNING_PHASES. This is a problem because the Tensor value itself references the graph which is suppose to be weakly held in memory by this dictionary. With the implementation of weakref.WeakKeyDictionary a value that strongly references its key will forever prevent the key from being reclaimed. This means the entire graph is permanently stuck in memory unless the entry is explicitly deleted.
This issue is present in tf 2.3.0
Simple repro code
import gc

import psutil
import tensorflow as tf

FIX_LEAK = False

def _get_rss():
    return psutil.Process().memory_info().rss

def _test_iteration():
    with tf.Graph().as_default() as graph:
        inputs = tf.keras.Input(shape=(8,), dtype="int32")
        embedding_layer = tf.keras.layers.Embedding(
            input_dim=128,
            output_dim=128,
            input_length=8,
        )(inputs)
        tf.keras.layers.LSTM(
            256,
            dropout=0.5,
        )(embedding_layer)

    if FIX_LEAK:
        import tensorflow.python.keras.backend as backend
        backend._GRAPH_LEARNING_PHASES.pop(graph, None)

for _ in range(128):
    _test_iteration()

    gc.collect()
    print("RSS", _get_rss())

With FIX_LEAK as False the memory usage grows forever (about 8MB or so for me each iteration). If FIX_LEAK is True the memory stays stable. I'm not super familiar with TF/keras, there may be a more bare bones example. In particular it seems that the dropout parameter was needed to trigger the learning_phrase Tensor to be created.

This could be the cause for the leak in this issue as well https://github.com/tensorflow/tensorflow/issues/41718
I enabled eager execution via tf.config.experimental_run_functions_eagerly(True) and the memory usage seems quite stable around 1GB, compared to ~7GB+ that I was getting without eager mode.

@msg555,
Could you please provide a minimal working example to reproduce the issue reported here. Thanks!

@msg555,
Could you please provide a minimal working example to reproduce the issue reported here. Thanks!

Added an example

@msg555,
Thank you for the update.
I was able to reproduce the issue with TF v2.3, please find the gist of it here. Thanks!

This could be the cause for the leak in this issue as well #41718
I enabled eager execution via tf.config.experimental_run_functions_eagerly(True) and the memory usage seems quite stable around 1GB, compared to ~7GB+ that I was getting without eager mode. FWIW, I noticed that CPU usage maxes out at 1 core only, compared to multiple cores when using graph mode.
The example code in that issue could be used to reproduce and check this behavior.

@jammm You can test if it's the same issue by examining tensorflow.python.keras.backend._GRAPH_LEARNING_PHASES. If it continues to grow over time with more elements than it's likely the same issue.

Sorry for the delayed response here! The backend graph (& backend learning phases) have been historically prone to memory leaks, and we have put a lot of focus into getting rid of the global backend graph entirely in 2.4 to fix these leaks.
That said, the specific code snippet in this github issue enters a v1 tf.Graph.as_default() explicitly which is a legacy v1 graph compatibility mode. It will not benefit from these improvements, and will not receive performance improvements in the future. If you use eager execution, with tf.function to create/enter graphs as needed, the specific memory leak reported here will not be an issue in 2.4.
As such, closing this issue but happy to answer any follow-on questions.

@tomerk  Thanks a lot for your reply! I'm currently using tf.function in many places. How do I make sure that it's running in eager mode in code outside of tf.function?

If you're using tf2 and haven't explicitly used the tf.compat.v1.disable_eager_execution() command it should be eager. If you're not sure and you want to check it programmatically, you can use tf.executing_eagerly(): https://www.tensorflow.org/api_docs/python/tf/executing_eagerly
It will return True when running eagerly, and False when tracing a tf.function into a graph.

I'm not sure if your issue #41718 is related to this though, that one will necessitate a closer look

Hi @saikumarchalla is there a specific reason you re-opened this issue?


fix: 500s uniqueness issue on updates

SUMMARY

Users would intermittently get Fatal Error 500 errors when trying to update datasets from SQLLab. The issue is happening
with if history.has_changes() coming back as true and DatasetDAO.validate_uniqueness failing. Users should be able to overwrite
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

#16859


MAPREDUCE-7458. Race condition in TaskReportPBImpl#getProto when generating task reports process in concurrency scenarios.

Description of PR
Please refer to the description in MAPREDUCE-7458
How was this patch tested?
No, the exception scenario is hard to reproduce, and the patch is a tiny fix and has the same pattern with others.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 28s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
34m 27s

trunk passed

+1 :green_heart:
compile
0m 28s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
compile
0m 27s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 25s

trunk passed

+1 :green_heart:
mvnsite
0m 30s

trunk passed

+1 :green_heart:
javadoc
0m 33s

trunk passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 27s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
0m 50s

trunk passed

+1 :green_heart:
shadedclient
20m 43s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 20s

the patch passed

+1 :green_heart:
compile
0m 21s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javac
0m 21s

the patch passed

+1 :green_heart:
compile
0m 19s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 19s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 13s

the patch passed

+1 :green_heart:
mvnsite
0m 20s

the patch passed

+1 :green_heart:
javadoc
0m 20s

the patch passed with JDK Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04

+1 :green_heart:
javadoc
0m 19s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
0m 45s

the patch passed

+1 :green_heart:
shadedclient
20m 19s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 56s

hadoop-mapreduce-client-common in the patch passed.

+1 :green_heart:
asflicense
0m 30s

The patch does not generate ASF License warnings.

86m 30s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6172/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6172

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 92e5f5ee015a 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 774f08a23d0c05da0214d1522b248993cff10b76

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.20+8-post-Ubuntu-1ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6172/1/testReport/

Max. process+thread count
752 (vs. ulimit of 5500)

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6172/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
17m 30s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
46m 45s

trunk passed

+1 :green_heart:
compile
0m 33s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 29s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
checkstyle
0m 27s

trunk passed

+1 :green_heart:
mvnsite
0m 36s

trunk passed

+1 :green_heart:
javadoc
0m 38s

trunk passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 31s

trunk passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m  8s

trunk passed

+1 :green_heart:
shadedclient
36m 25s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s

the patch passed

+1 :green_heart:
compile
0m 25s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 25s

the patch passed

+1 :green_heart:
compile
0m 23s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
javac
0m 23s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 16s

the patch passed

+1 :green_heart:
mvnsite
0m 26s

the patch passed

+1 :green_heart:
javadoc
0m 25s

the patch passed with JDK Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 24s

the patch passed with JDK Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

+1 :green_heart:
spotbugs
1m  5s

the patch passed

+1 :green_heart:
shadedclient
34m 38s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
1m 11s

hadoop-mapreduce-client-common in the patch passed.

+1 :green_heart:
asflicense
0m 39s

The patch does not generate ASF License warnings.

149m 39s

Subsystem
Report/Notes

Docker
ClientAPI=1.43 ServerAPI=1.43 base: https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6172/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6172

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux d8f65a3d4ba0 4.15.0-213-generic #224-Ubuntu SMP Mon Jun 19 13:30:12 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 774f08a23d0c05da0214d1522b248993cff10b76

Default Java
Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-<IP_ADDRESS>+1-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_382-8u382-ga-1~20.04.1-b05

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6172/1/testReport/

Max. process+thread count
748 (vs. ulimit of 5500)

modules
C: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common U: hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch-windows-10/job/PR-6172/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@steveloughran can you please help to review this RP or tag relevant folks if possible? Thanks.

Not code I am safe to go anywhere near I'm afraid. Ask on the mapreduce-dev email group


Localization "Soulshape Journal" title

Can you please localize the "Soulshape Journal" title?

Hello, I wasn't sure I really needed to translate it as it's verbatim the name of the addon, but that might not be great for russian users or (upcoming chinese users). I'll try to see whan the consensus is for popular addon and will update accordingly.

It's been added as a translation key, although it's pretty much optional. I'll leave it to translator's preference for their own locales.


Enable more than one devcontainer to use Docker at a time

I bumped into this issue when running two different VS Code devcontainers.
See also:

https://github.com/devcontainers/spec/issues/62
https://bytemeta.vip/repo/microsoft/vscode-dev-containers/issues/1249

Added to Blocked. According to https://github.com/microsoft/vscode-remote-release/issues/5679 there may be an updated in August.

TODO
Update the version of docker-in-docker to v2 (see above post)

We are already using version 2.0.0, which was released 2 month ago. That version should already include the fix.
See all versions: https://github.com/devcontainers/features/pkgs/container/features%2Fdocker-in-docker

I have not bumped into a case where I need more than one dev container to run on an instance since the creation of this ticket. The issue should be fixed according to the post referenced in this ticket.


🏭 Productionise Catalogue

Brief summary of what this Epic is
Complete the Buildout of the OpenMetaData in Modernisation Platform including an upgrade to the latest version, monitoring and alerting, AzureAD authentication and DNS that complies with MOJ standards.
Definition of Done:

Complete buildout or prerequesities
Complete SPIKE on using MWAA for scheduling
Deploy Airflow solution for scheduling
Define and implement solution for AWS authentication
Deploy latest version of OpenMetadata
Test ingestion

List of issues in this epic

[ ]
[ ]

Other information
No response

[ ] #1715
[ ] #1717
[x] #1191
[x] #1824
[x] #2179
[x] #2454

Work completed. Moved to Catalogue team.


deployer: Implement Strategies

The deployer app needs to support multiple strategies for performing deployments.
@archSeer started this work but it seems to have been lost from the deploy-strategy branch.
Features to implement:

[x] A Strategy interface (e.g. type Strategy interface { Perform(*Deployment) error })
[x] A Strategy object which performs a "one-by-one" deployment
[x] A Strategy object which performs an "all-at-once" deployment
[x] A lookup function to determine which strategy to use for a given Deployment (probably make Deployment.Strategy an enum)
[x] Update the handleJob function to call Perform on the relevant Strategy
[x] Emit events throughout the deployment (e.g. start / end of deployment, start / end of formation change, job status changes)
[x] Add integration test for each strategy which does deployment and checks events (partially implemented here)
[x] Restore original formation state if a deployment fails
[x] Handle crashed formations / processes (depends on a fix for #610)
[x] Add a releaseID constraint so that only one deployment operating on a single release might be working at once
[ ] Make sure strategies are idempotent

Part of #536.

I have opened #799 to track idempotent strategies.


[BUG] Macros that call User scripts do not work on Obsidian mobile app.

Describe the bug
I created a user script and assigned it to Macro that shows several suggesters in turn to select a note type, input the file name, and finally create it. I referred to the example below, especially the function called "getBooks".
https://github.com/chhoumann/quickadd/blob/master/docs/Examples/Template_AutomaticBookNotesFromReadwise.md
But nothing happens on mobile app after having called the command despite that it successfully works on desktop.
Just in case, I tried the same process with another simpler script that only has a function to show a suggester. And again, it works on desktop but not on mobile app.
To Reproduce
Steps to reproduce the behavior:

Add a macro that calls your original script that returns a suggester. (User Scripts)
Make it available by setting it to the command or enabling Run on plugin load.
Call it on mobile app.
Get nothing.

Screenshots
These are some captures of reproducing on desktop. The first suggester does not appear in the first place on mobile.

Desktop (please complete the following information):

OS: Windows 10

Smartphone (please complete the following information):

Device: iPhoneXR
OS: iOS14.5

Hey @brkwtnh!
I've made a fix that, from my tests, make scripts work on mobile as they do on desktop. I'll push the fix in the next update.

Hey @brkwtnh! I've made a fix that, from my tests, make scripts work on mobile as they do on desktop. I'll push the fix in the next update.

Thank you very much @chhoumann for your quick response and fix!
I have just confirmed that it works on mobile.


error in evaluation -- connection

when i run evaluation
get LLM outputs
python instance_generation/generation.py
-api ./data/eval_simulated.json
-out ./eval
-llm ./outputs/model1
--agent_prompt test_v1 \
I get an error: ConnectionError: HTTPConnectionPool(host='<IP_ADDRESS>', port=5678): Max retries exceeded with url: /Axolotl/random (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f635fb4c5b0>: Failed to establish a
new connection: [Errno 111] Connection refused'))
Can you help me with this please, thanks!

Hi, you should start the API simulator first.
python instance_generation/simulator.py -api ./data/eval_simulated.json


pip install -e . not working

It seems I cannot install the package with pip in an editable mode.
pip install -e . results in successful installation of the package.  pip install -e . output:

Details
Obtaining file:///home/hubo/Projects/em_alignment/packages/gfriedri-em-alignment
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: numpy in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from em-alignment==0.1.dev18+ga8d7480) (1.22.3)
Requirement already satisfied: scikit-image in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from em-alignment==0.1.dev18+ga8d7480) (0.19.2)
Requirement already satisfied: sofima in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from em-alignment==0.1.dev18+ga8d7480) (0.2.dev4+g2160f05)
Requirement already satisfied: tqdm in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from em-alignment==0.1.dev18+ga8d7480) (4.64.0)
Requirement already satisfied: pandas in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from em-alignment==0.1.dev18+ga8d7480) (1.4.2)
Requirement already satisfied: python-dateutil>=2.8.1 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from pandas->em-alignment==0.1.dev18+ga8d7480) (2.8.2)
Requirement already satisfied: pytz>=2020.1 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from pandas->em-alignment==0.1.dev18+ga8d7480) (2022.1)
Requirement already satisfied: imageio>=2.4.1 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from scikit-image->em-alignment==0.1.dev18+ga8d7480) (2.16.1)
Requirement already satisfied: pillow!=7.1.0,!=7.1.1,!=8.3.0,>=6.1.0 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from scikit-image->em-alignment==0.1.dev18+ga8d7480) (9.0.1)
Requirement already satisfied: packaging>=20.0 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from scikit-image->em-alignment==0.1.dev18+ga8d7480) (21.3)
Requirement already satisfied: PyWavelets>=1.1.1 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from scikit-image->em-alignment==0.1.dev18+ga8d7480) (1.3.0)
Requirement already satisfied: networkx>=2.2 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from scikit-image->em-alignment==0.1.dev18+ga8d7480) (2.7.1)
Requirement already satisfied: scipy>=1.4.1 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from scikit-image->em-alignment==0.1.dev18+ga8d7480) (1.8.0)
Requirement already satisfied: tifffile>=2019.7.26 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from scikit-image->em-alignment==0.1.dev18+ga8d7480) (2022.3.25)
Requirement already satisfied: opencv-python>=<IP_ADDRESS> in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from sofima->em-alignment==0.1.dev18+ga8d7480) (<IP_ADDRESS>)
Requirement already satisfied: connectomics in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from sofima->em-alignment==0.1.dev18+ga8d7480) (0.0.1.dev3)
Requirement already satisfied: absl-py>=0.9.0 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from sofima->em-alignment==0.1.dev18+ga8d7480) (1.0.0)
Requirement already satisfied: jax>=0.2.25 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from sofima->em-alignment==0.1.dev18+ga8d7480) (0.3.7)
Requirement already satisfied: dataclasses-json>=0.5.6 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from sofima->em-alignment==0.1.dev18+ga8d7480) (0.5.7)
Requirement already satisfied: six in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from absl-py>=0.9.0->sofima->em-alignment==0.1.dev18+ga8d7480) (1.16.0)
Requirement already satisfied: marshmallow-enum<2.0.0,>=1.5.1 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from dataclasses-json>=0.5.6->sofima->em-alignment==0.1.dev18+ga8d7480) (1.5.1)
Requirement already satisfied: typing-inspect>=0.4.0 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from dataclasses-json>=0.5.6->sofima->em-alignment==0.1.dev18+ga8d7480) (0.7.1)
Requirement already satisfied: marshmallow<4.0.0,>=3.3.0 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from dataclasses-json>=0.5.6->sofima->em-alignment==0.1.dev18+ga8d7480) (3.15.0)
Requirement already satisfied: typing-extensions in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from jax>=0.2.25->sofima->em-alignment==0.1.dev18+ga8d7480) (4.1.1)
Requirement already satisfied: opt-einsum in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from jax>=0.2.25->sofima->em-alignment==0.1.dev18+ga8d7480) (3.3.0)
Requirement already satisfied: pyparsing!=3.0.5,>=2.0.2 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from packaging>=20.0->scikit-image->em-alignment==0.1.dev18+ga8d7480) (3.0.7)
Requirement already satisfied: mypy-extensions>=0.3.0 in /home/hubo/Software/miniconda3/envs/sofima/lib/python3.9/site-packages (from typing-inspect>=0.4.0->dataclasses-json>=0.5.6->sofima->em-alignment==0.1.dev18+ga8d7480) (0.4.3)
Installing collected packages: em-alignment
  Running setup.py develop for em-alignment
Successfully installed em-alignment-0.1.dev18+ga8d7480

However, python could only find the sbem package but not the em_alignment package.
$ cd ..
$ python -c "import sbem"
$ python -c "import em_alignment"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ModuleNotFoundError: No module named 'em_alignment'

Could this be related to this issue pypa/pip#7953 ?

Is this still relevant?


Can't retrieve from the translation arrays and objects

I'm submitting a...

[ x ] Regression (a behavior that used to work and stopped working in a new release)
[ x ] Bug report
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior
Getting Missing translation for 'roles' while trying to retrieve an array/object from the translation.
Expected behavior
Should return the expected object without triggering any error.
Minimal reproduction of the problem with instructions
en.json:
{
  "title": "It works",
  "roles": ["But", "this", "does", "not", "work"]
}

template.component.html:

<ng-container *transloco="let t">

{{ t('title') }}

{{ t('roles').join(' ') }}

</ng-container>

Environment

Angular version: 9.0.0-next.9

Browser:
- [ x ] Chrome (desktop) version 77
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:
- Node version: XX  10.11.0
- Platform:  win32 x64

Others:
When I updated the package without using the schematics,
I got the same error until I found out I had to change
to `selectTranslateObject` in my services, so my guess is that `t()` is
using `selectTranslate` event when it's an object.

Maybe you should internally determine if to use `selectTranslate` or `selectTranslateObject`.
Or at least throw a different error, since the value does exists :)

@Newbie012 Thanks for the report, I have fixed the issue and it will be up in the next couple of hours

@Newbie012
Fixed in #113.
Published in v2.0.3.
If you are using the messageformat plugin you will also need to upgrade to v1.1.1.
If you are using the optimize plugin you will also need to upgrade to v1.0.1.

I can confirm it has been solved for arrays, but not for objects.
      "links2": [], // <-- Will work
      "links": { <-- getting "Missing translation for 'app.footer.links'"
        "key": "value",
        "...": "...",
      },
``

@Newbie012 the translations are being flattened in runtime, so if you need to select a translation key as object you will have to use selectTranslationObject or getTranslationObject from the service.
take a look at the docs:
https://app.gitbook.com/@netbasal/s/transloco/service-api/translation-api

@itayod thanks for the fast response.
I'm aware of the following methods you mentioned. Although, I was hoping to accomplish it using directives. Either way, I eventually solved it using t('links.' + link.text).


fix(website): update github actions files

Motivation
This PR solves the issue https://github.com/facebook/docusaurus/issues/6775.

This PR also solves the issue, Error: Dependencies lock file is not found in /home/runner/work/docusaurus/docusaurus. Supported file patterns: yarn.lock which is mentioned here. Can I change the action files to solve this?

Error: Dependencies lock file is not found in /home/runner/work/docusaurus/docusaurus.

The actions file works for me without any configuration: https://github.com/jc-verse/docusaurus-template/blob/master/.github/workflows/deploy.yml
It doesn't work for you, because your yarn.lock is not at the root of the repo, which is a bad pattern. You can run setup-node in the website folder instead.

@arifszn The actions files are working for most repos. Even if it doesn't work out-of-the-box for all, modification is trivial. For example, here's a working example for a website in the website/ folder: https://github.com/yanivam/react-svg-worldmap/blob/main/.github/workflows/deploy.yml
The yarn build executes build in all workspaces: https://github.com/yanivam/react-svg-worldmap/blob/main/package.json#L10
If you have a repo with multiple projects and multiple package.jsons, you'd better use a workspace management tool like Nx or Yarn, but for any tool, you would end up with yarn.lock at the root of the repo.


Getting error in new-sample on Android app

System information

OS Platform and Distribution - MacOS BigSur
Target Platform:
Mobile Device (if the target is Android or iOS): Android 11 Xiaomi note 10
MediaPipeUnityPlugin version or commit id: new-sample

Describe the current behavior
All scenes working good in unity but in android camera working but all graphs not working and getting
09-16 14:05:50.212  6808  6832 E Unity   : FileNotFoundException: jar:file:///data/app/~~aQzDfWXS4HchzzvhOPC8ow==/com.rgbkod.shoesCal-smsV_PqGmkGZq1u_IkWGFg==/base.apk!/assets/face_detection_short_range.bytes is not found 09-16 14:05:50.212  6808  6832 E Unity   :   at Mediapipe.Unity.FileSystemResourceManager.PrepareAsset (System.String name, System.String uniqueKey, System.Boolean overwrite) [0x00000] in <00000000000000000000000000000000>:0  09-16 14:05:50.212  6808  6832 E Unity   :   at Mediapipe.Unity.FaceDetection.FaceDetectionGraph.PrepareDependentAssets () [0x00000] in <00000000000000000000000000000000>:0  09-16 14:05:50.212  6808  6832 E Unity   :   at Mediapipe.Unity.GraphRunner.Start () [0x00000] in <00000000000000000000000000000000>:0  09-16 14:05:50.212  6808  6832 E Unity   :  09-16 14:05:50.497  6808  6832 E Unity   : Unsupported destination format in Graphics.ConvertTexture (59). This is likely because the device does not support this format as a rendertarget format. 09-16 14:05:50.497  6808  6832 E Unity   : Mediapipe.Unity.FaceDetection.<Run>d__16:MoveNext() 09-16 14:05:50.497  6808  6832 E Unity   : UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr) 09-16 14:05:50.497  6808  6832 E Unity   :  09-16 14:05:50.497  6808  6832 E Unity   : [ line<PHONE_NUMBER>] 09-16 14:05:50.497  6808  6832 E Unity   :  09-16 14:05:50.508  6808  6832 E Unity   : MediaPipeException: INTERNAL: Graph has errors:  09-16 14:05:50.508  6808  6832 E Unity   : Calculator::Open() for node "facedetectionshortrangegpu__inferencecalculator__facedetectionshortrangegpu__InferenceCalculator" failed: ; (resolved_path)!=(nullptr)pe_api/util/resource_util_custom.cc:18)  09-16 14:05:50.508  6808  6832 E Unity   : Calculator::Open() for node "facedetectionfullrangegpu__inferencecalculator__facedetectionfullrangegpu__InferenceCalculator" failed: ; (resolved_path)!=(nullptr)pe_api/util/resource_util_custom.cc:18)  09-16 14:05:50.508  6808  6832 E Unity   :   at Mediapipe.Status.AssertOk () [0x00000] in <00000000000000000000000000000000>:0  09-16 14:05:50.508  6808  6832 E Unity   :   at Mediapipe.Unity.FaceDetection.FaceDetectionSolution+<Run>d__16.MoveNext () [0x00000] in <00000000000000000000000000000000>:0  09-16 14:05:50.508  6808  6832 E Unity   :   at UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) [0x00000] in <00000000000000000000000000000000>:0
What should I do?

Could you help to solve problem please?

What should I do?

I think you should wait for the next release, since this is a working branch (well, actually, I just pushed the fixed commit yesterday).

can not download new-sample again. Github only download master files. @homuler can you fix the link please?

From where do I get sample apk any know ?


fix(chips): unable to tab out of chip list with input on firefox

Fixes user focus being wrapped back to the first chip, when trying to tab out of a chip list that has an input, on Firefox.
Note: the Browserstack failure seems to unrelated.
Fixes #15011.

I don't quite follow why the focus is trapped- what's going on there?

If I remember correctly, the problem was on Firefox where if you tabbed from a chip, your focus would land on the chip list because it has a tabindex of zero, which would then revert it to one of the chips. A while ago we had the same issue for Chrome, but only happened when you were shift-tabbing.

@crisbeto this passes presubmit, just needs a rebase

Rebased.


Fix: make contentToOption totally optional

Brief Information
This pull request is in the type of:

[x] bug fixing
[ ] new feature
[ ] others

What does this PR do?

Fix #13031 and #13086
Fixed issues
#13031 has described such a situation that user has provided optionToContent function while has not provided the corresponding contentToOption function.
If we think echarts should also work well in this situation, we need to make contentToOption function totally optional. (In other words, if user hasn't provided it, bugs like missing series data or showing a list of undefined should not happen.)
Details
Before: What was the problem?
If user provide optionToContent function but has not provided contentToOption function, press 'refresh' will lose data and make a list of undefined displayed.
After: How is it fixed in this PR?
Even user has not provided contentToOption function, by pressing 'refresh' button also works well.
Usage
Are there any API changes?

[ ] The API has been changed.

No
Related test cases or examples to use the new APIs
NA.
Others
Merging options

[x] Please squash the commits into a single one when merge.

Other information

In #13086 @pissang has raised an issue. He says that PR will make option not refreshed if user didn't provide optionToContent or contentToOption function and changed the default text area. This PR also fix that bug.
The key point here is:

If user has provided optionToContent function but missed contentToOption function, the system tried to parse the content in textarea. But actually textarea is not appended to the document in this case. So the content we need to parse is a user-provided HTML what optionToContent returned, rather than the default textarea.
Futhermore, if user provided a complicated HTML structure (such as a table described in #13031), it is difficult (or saying impossible) for us to parse it and get the right data we want.
By contrast, let's image the opposite situation that user has provided contentToOption function but missed optionToContent function. In this case, the default textarea will show but the parsing function is overwritten by user, which is totally unnecessary.
Given these facts, in my opinion user should still use optionToContent along with contentToOption together. Thus this PR gives warning when user missed one of these two. If he did, a warning message will be shown and all data will remain the same.

Hi @easonyq, thanks for the detailed explanation. I think the scenario you described is complete enough.

Thanks for @pissang 's review. I've applied another patch.


support more various manifest file names.

currently, we have 2 hardcoded filenames for manifest and for deployment files (i.e., manifest.yaml and .yml and deployment.yaml and .yml respectively (declared in "shared.go"). These names appear "lowercased". We need to find a way such that we can match any mixed base name such as "Manifest.yaml" or "manifest.YAML" etc. I would be happy if you want to open this as a lower priority issue to fix later.

We do support various manifest and deployment file names, outside of most used manifest.yaml and deployment.yaml.


ENH: Load ruler annotations

Load in ruler annotations. Resolves #118
Other changes:

Write out ruler annotation metadata to json
Use the metadata to reinitialize the state of the onsd and rainbow metadata generators, so the user can pick up where they left off after reading in annotations

TODO:

[ ] Should we always show the ruler annotations when viewing overlay data? Similar to https://github.com/KitwareMedical/ImageViewer/pull/101/commits/4956c6882e0825293181fb861a8e29fa646031fb. What if the user shows ruler and box annotations at the same time?

@brad-t-moore @aylward This is all set. Would one of you please take a look at your earliest convenience? Thank you.

LGTM after the review comment about status is addressed.  I think we probably need to add an issue to make rulers render even if ruler mode isn't selected.

I think we probably need to add an issue to make rulers render even if ruler mode isn't selected.

This change is a one-liner. I can push it to this branch, if you want?

@tao558 Sure, if you want to add it I can test it within the hour.
-Brad

@tao558 Sure, if you want to add it I can test it within the hour.

All set whenever you're ready.

@tao558 Great! LGTM!

@tao558 Great! LGTM!

Great. I cant merge as I don't have the permissions, but I'm all set with this PR. Likewise with #122


Unable to use more than 5 GPU cards

What is being built is a kata environment. The host has 8 GPU cards. If 1-5 GPU cards are used to create a pod, nvidia-container-cli will run normally, but problems will occur if 6 GPUs are used. After locating, the main reason is that the code calls ns_enter, switches to the rootfs of the container, and cannot find the corresponding directory when mounting_procfs. The environment version information is as follows:
nvidia-container-toolkit version
root@ubuntu-dev:/# dpkg -l | grep nvidia-container-toolkit
ii  nvidia-container-toolkit          1.14.3-1              amd64        NVIDIA Container toolkit
ii  nvidia-container-toolkit-base     1.14.3-1          amd64        NVIDIA Container Toolkit Base
nvidia-container-cli，The running log information is as follows：
`
-- WARNING, the following logs are for debugging purposes only --
I0111 10:30:12.940268 149 nvc.c:376] initializing library context (version=1.14.1, build=1eb5a30a6ad0415550a9df632ac8832bf7e2bbba)
I0111 10:30:12.940332 149 nvc.c:350] using root /
I0111 10:30:12.940334 149 nvc.c:351] using ldcache /etc/ld.so.cache
I0111 10:30:12.940336 149 nvc.c:352] using unprivileged user 65534:65534
I0111 10:30:12.940347 149 nvc.c:393] attempting to load dxcore to see if we are running under Windows Subsystem for Linux (WSL)
I0111 10:30:12.940484 149 nvc.c:395] dxcore initialization failed, continuing assuming a non-WSL environment
I0111 10:30:12.943220 179 nvc.c:278] loading kernel module nvidia
I0111 10:30:12.943338 179 nvc.c:282] running mknod for /dev/nvidiactl
I0111 10:30:12.943362 179 nvc.c:286] running mknod for /dev/nvidia0
I0111 10:30:12.943374 179 nvc.c:286] running mknod for /dev/nvidia1
I0111 10:30:12.943382 179 nvc.c:286] running mknod for /dev/nvidia2
I0111 10:30:12.943390 179 nvc.c:286] running mknod for /dev/nvidia3
I0111 10:30:12.943399 179 nvc.c:286] running mknod for /dev/nvidia4
I0111 10:30:12.943407 179 nvc.c:286] running mknod for /dev/nvidia5
I0111 10:30:12.943415 179 nvc.c:290] running mknod for all nvcaps in /dev/nvidia-caps
I0111 10:30:12.947452 179 nvc.c:218] running mknod for /dev/nvidia-caps/nvidia-cap1 from /proc/driver/nvidia/capabilities/mig/config
I0111 10:30:12.947504 179 nvc.c:218] running mknod for /dev/nvidia-caps/nvidia-cap2 from /proc/driver/nvidia/capabilities/mig/monitor
I0111 10:30:12.949693 179 nvc.c:296] loading kernel module nvidia_uvm
I0111 10:30:12.949702 179 nvc.c:300] running mknod for /dev/nvidia-uvm
I0111 10:30:12.949735 179 nvc.c:305] loading kernel module nvidia_modeset
I0111 10:30:12.955489 179 nvc.c:309] running mknod for /dev/nvidia-modeset
I0111 10:30:12.955701 183 rpc.c:71] starting driver rpc service
I0111 10:30:19.067427 229 rpc.c:71] starting nvcgo rpc service
I0111 10:30:19.072896 149 nvc_container.c:246] configuring container with 'compute utility supervised'
I0111 10:30:19.077084 149 nvc_container.c:88] selecting /run/kata-containers/ae1f8199611632c96d7e2ef8a5d5f51894d377259f062f6336911d02f67474d0/rootfs/usr/local/cuda-12.3/compat/libcuda.so.545.23.08
I0111 10:30:19.077456 149 nvc_container.c:88] selecting /run/kata-containers/ae1f8199611632c96d7e2ef8a5d5f51894d377259f062f6336911d02f67474d0/rootfs/usr/local/cuda-12.3/compat/libcudadebugger.so.545.23.08
I0111 10:30:19.077803 149 nvc_container.c:88] selecting /run/kata-containers/ae1f8199611632c96d7e2ef8a5d5f51894d377259f062f6336911d02f67474d0/rootfs/usr/local/cuda-12.3/compat/libnvidia-nvvm.so.545.23.08
I0111 10:30:19.078148 149 nvc_container.c:88] selecting /run/kata-containers/ae1f8199611632c96d7e2ef8a5d5f51894d377259f062f6336911d02f67474d0/rootfs/usr/local/cuda-12.3/compat/libnvidia-ptxjitcompiler.so.545.23.08
I0111 10:30:19.079973 149 nvc_container.c:268] setting pid to 147
I0111 10:30:19.080003 149 nvc_container.c:269] setting rootfs to /run/kata-containers/ae1f8199611632c96d7e2ef8a5d5f51894d377259f062f6336911d02f67474d0/rootfs
I0111 10:30:19.080011 149 nvc_container.c:270] setting owner to 0:0
I0111 10:30:19.080018 149 nvc_container.c:271] setting bins directory to /usr/bin
I0111 10:30:19.080038 149 nvc_container.c:272] setting libs directory to /usr/lib/x86_64-linux-gnu
I0111 10:30:19.080045 149 nvc_container.c:273] setting libs32 directory to /usr/lib/i386-linux-gnu
I0111 10:30:19.080052 149 nvc_container.c:274] setting cudart directory to /usr/local/cuda
I0111 10:30:19.080058 149 nvc_container.c:275] setting ldconfig to @/sbin/ldconfig.real (host relative)
I0111 10:30:19.080064 149 nvc_container.c:276] setting mount namespace to /proc/147/ns/mnt
I0111 10:30:19.080070 149 nvc_container.c:278] detected cgroupv1
I0111 10:30:19.080077 149 nvc_container.c:279] setting devices cgroup to /sys/fs/cgroup/devices/663e4a00_6864_4e19_8a5f_15d850583969/ae1f8199611632c96d7e2ef8a5d5f51894d377259f062f6336911d02f67474d0
I0111 10:30:19.080134 149 nvc_info.c:798] requesting driver information with ''
I0111 10:30:19.083496 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/vdpau/libvdpau_nvidia.so.535.146.02
I0111 10:30:19.083715 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-ptxjitcompiler.so.535.146.02
I0111 10:30:19.083826 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-pkcs11.so.535.146.02
I0111 10:30:19.083920 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.146.02
I0111 10:30:19.084025 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-opticalflow.so.535.146.02
I0111 10:30:19.084159 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-opencl.so.535.146.02
I0111 10:30:19.084254 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-nvvm.so.535.146.02
I0111 10:30:19.084412 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.535.146.02
I0111 10:30:19.084542 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-fbc.so.535.146.02
I0111 10:30:19.084657 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-encode.so.535.146.02
I0111 10:30:19.084783 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-cfg.so.535.146.02
I0111 10:30:19.084883 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvidia-allocator.so.535.146.02
I0111 10:30:19.084963 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libnvcuvid.so.535.146.02
I0111 10:30:19.085071 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libcudadebugger.so.535.146.02
I0111 10:30:19.085101 149 nvc_info.c:176] selecting /usr/lib/x86_64-linux-gnu/libcuda.so.535.146.02
W0111 10:30:19.085145 149 nvc_info.c:402] missing library libnvidia-nscq.so
W0111 10:30:19.085150 149 nvc_info.c:402] missing library libnvidia-gpucomp.so
W0111 10:30:19.085152 149 nvc_info.c:402] missing library libnvidia-fatbinaryloader.so
W0111 10:30:19.085155 149 nvc_info.c:402] missing library libnvidia-compiler.so
W0111 10:30:19.085158 149 nvc_info.c:402] missing library libnvidia-ngx.so
W0111 10:30:19.085160 149 nvc_info.c:402] missing library libnvidia-eglcore.so
W0111 10:30:19.085163 149 nvc_info.c:402] missing library libnvidia-glcore.so
W0111 10:30:19.085165 149 nvc_info.c:402] missing library libnvidia-tls.so
W0111 10:30:19.085167 149 nvc_info.c:402] missing library libnvidia-glsi.so
W0111 10:30:19.085170 149 nvc_info.c:402] missing library libnvidia-ifr.so
W0111 10:30:19.085172 149 nvc_info.c:402] missing library libnvidia-rtcore.so
W0111 10:30:19.085175 149 nvc_info.c:402] missing library libnvoptix.so
W0111 10:30:19.085177 149 nvc_info.c:402] missing library libGLX_nvidia.so
W0111 10:30:19.085180 149 nvc_info.c:402] missing library libEGL_nvidia.so
W0111 10:30:19.085182 149 nvc_info.c:402] missing library libGLESv2_nvidia.so
W0111 10:30:19.085184 149 nvc_info.c:402] missing library libGLESv1_CM_nvidia.so
W0111 10:30:19.085187 149 nvc_info.c:402] missing library libnvidia-glvkspirv.so
W0111 10:30:19.085189 149 nvc_info.c:402] missing library libnvidia-cbl.so
W0111 10:30:19.085192 149 nvc_info.c:406] missing compat32 library libnvidia-ml.so
W0111 10:30:19.085194 149 nvc_info.c:406] missing compat32 library libnvidia-cfg.so
W0111 10:30:19.085197 149 nvc_info.c:406] missing compat32 library libnvidia-nscq.so
W0111 10:30:19.085199 149 nvc_info.c:406] missing compat32 library libcuda.so
W0111 10:30:19.085202 149 nvc_info.c:406] missing compat32 library libcudadebugger.so
W0111 10:30:19.085204 149 nvc_info.c:406] missing compat32 library libnvidia-opencl.so
W0111 10:30:19.085206 149 nvc_info.c:406] missing compat32 library libnvidia-gpucomp.so
W0111 10:30:19.085209 149 nvc_info.c:406] missing compat32 library libnvidia-ptxjitcompiler.so
W0111 10:30:19.085211 149 nvc_info.c:406] missing compat32 library libnvidia-fatbinaryloader.so
W0111 10:30:19.085214 149 nvc_info.c:406] missing compat32 library libnvidia-allocator.so
W0111 10:30:19.085216 149 nvc_info.c:406] missing compat32 library libnvidia-compiler.so
W0111 10:30:19.085219 149 nvc_info.c:406] missing compat32 library libnvidia-pkcs11.so
W0111 10:30:19.085221 149 nvc_info.c:406] missing compat32 library libnvidia-pkcs11-openssl3.so
W0111 10:30:19.085230 149 nvc_info.c:406] missing compat32 library libnvidia-nvvm.so
W0111 10:30:19.085233 149 nvc_info.c:406] missing compat32 library libnvidia-ngx.so
W0111 10:30:19.085235 149 nvc_info.c:406] missing compat32 library libvdpau_nvidia.so
W0111 10:30:19.085238 149 nvc_info.c:406] missing compat32 library libnvidia-encode.so
W0111 10:30:19.085241 149 nvc_info.c:406] missing compat32 library libnvidia-opticalflow.so
W0111 10:30:19.085243 149 nvc_info.c:406] missing compat32 library libnvcuvid.so
W0111 10:30:19.085246 149 nvc_info.c:406] missing compat32 library libnvidia-eglcore.so
W0111 10:30:19.085249 149 nvc_info.c:406] missing compat32 library libnvidia-glcore.so
W0111 10:30:19.085251 149 nvc_info.c:406] missing compat32 library libnvidia-tls.so
W0111 10:30:19.085254 149 nvc_info.c:406] missing compat32 library libnvidia-glsi.so
W0111 10:30:19.085256 149 nvc_info.c:406] missing compat32 library libnvidia-fbc.so
W0111 10:30:19.085259 149 nvc_info.c:406] missing compat32 library libnvidia-ifr.so
W0111 10:30:19.085262 149 nvc_info.c:406] missing compat32 library libnvidia-rtcore.so
W0111 10:30:19.085264 149 nvc_info.c:406] missing compat32 library libnvoptix.so
W0111 10:30:19.085267 149 nvc_info.c:406] missing compat32 library libGLX_nvidia.so
W0111 10:30:19.085270 149 nvc_info.c:406] missing compat32 library libEGL_nvidia.so
W0111 10:30:19.085272 149 nvc_info.c:406] missing compat32 library libGLESv2_nvidia.so
W0111 10:30:19.085275 149 nvc_info.c:406] missing compat32 library libGLESv1_CM_nvidia.so
W0111 10:30:19.085277 149 nvc_info.c:406] missing compat32 library libnvidia-glvkspirv.so
W0111 10:30:19.085280 149 nvc_info.c:406] missing compat32 library libnvidia-cbl.so
I0111 10:30:19.085495 149 nvc_info.c:302] selecting /usr/bin/nvidia-smi
I0111 10:30:19.085511 149 nvc_info.c:302] selecting /usr/bin/nvidia-debugdump
I0111 10:30:19.085525 149 nvc_info.c:302] selecting /usr/bin/nvidia-persistenced
I0111 10:30:19.085549 149 nvc_info.c:302] selecting /usr/bin/nvidia-cuda-mps-control
I0111 10:30:19.085563 149 nvc_info.c:302] selecting /usr/bin/nvidia-cuda-mps-server
W0111 10:30:19.085591 149 nvc_info.c:428] missing binary nv-fabricmanager
I0111 10:30:19.085667 149 nvc_info.c:488] listing firmware path /lib/firmware/nvidia/535.146.02/gsp_ga10x.bin
I0111 10:30:19.085671 149 nvc_info.c:488] listing firmware path /lib/firmware/nvidia/535.146.02/gsp_tu10x.bin
I0111 10:30:19.085688 149 nvc_info.c:561] listing device /dev/nvidiactl
I0111 10:30:19.085691 149 nvc_info.c:561] listing device /dev/nvidia-uvm
I0111 10:30:19.085693 149 nvc_info.c:561] listing device /dev/nvidia-uvm-tools
I0111 10:30:19.085696 149 nvc_info.c:561] listing device /dev/nvidia-modeset
W0111 10:30:19.085712 149 nvc_info.c:352] missing ipc path /var/run/nvidia-persistenced/socket
W0111 10:30:19.085724 149 nvc_info.c:352] missing ipc path /var/run/nvidia-fabricmanager/socket
W0111 10:30:19.085735 149 nvc_info.c:352] missing ipc path /tmp/nvidia-mps
I0111 10:30:19.085739 149 nvc_info.c:854] requesting device information with ''
I0111 10:30:19.093013 149 nvc_info.c:745] listing device /dev/nvidia0 (GPU-15dd6db0-ca52-31f5-3daf-2019882683b0 at 00000000:02:00.0)
I0111 10:30:19.101035 149 nvc_info.c:745] listing device /dev/nvidia1 (GPU-2f4bb339-fc05-e25d-512c-05c7eefd99e1 at 00000000:04:00.0)
I0111 10:30:19.109848 149 nvc_info.c:745] listing device /dev/nvidia2 (GPU-23e7b85e-0792-0721-9d22-ac2a0e9bac2b at 00000000:06:00.0)
I0111 10:30:19.118514 149 nvc_info.c:745] listing device /dev/nvidia3 (GPU-d78a3ff1-47b6-80be-95a5-ffe77853335f at 00000000:08:00.0)
I0111 10:30:19.126998 149 nvc_info.c:745] listing device /dev/nvidia4 (GPU-3dbafd65-2a6e-1445-9569-a70fa746902d at 00000000:0a:00.0)
I0111 10:30:19.135642 149 nvc_info.c:745] listing device /dev/nvidia5 (GPU-d9bc47e7-fd6d-f1dc-ff31-d9675bb73087 at 00000000:0c:00.0)
`
nvidia-container-cli，code positioning analysis is as follows：【src/nvc_mount.c 】
`
int
nvc_driver_mount(struct nvc_context *ctx, const struct nvc_container *cnt, const struct nvc_driver_info *info)
{
const char **mnt, **ptr, **tmp;
size_t nmnt;
int rv = -1;
    if (validate_context(ctx) < 0)
            return (-1);
    if (validate_args(ctx, cnt != NULL && info != NULL) < 0)
            return (-1);

    if (ns_enter(&ctx->err, cnt->mnt_ns, CLONE_NEWNS) < 0)
            return (-1);

    nmnt = 2 + info->nbins + info->nlibs + cnt->nlibs + info->nlibs32 + info->nipcs + info->ndevs + info->nfirmwares;
    mnt = ptr = (const char **)array_new(&ctx->err, nmnt);
    if (mnt == NULL)
            goto fail;

    /* Procfs mount */
    if (ctx->dxcore.initialized)
            log_warn("skipping procfs mount on WSL");
    else if ((*ptr++ = mount_procfs(&ctx->err, ctx->cfg.root, cnt)) == NULL)
            goto fail;

`
After locating, it was found that the problem occurred on ns_enter func. Under normal circumstances during the test, even if the ns_enter interface was called, the file system path inside the virtual machine could be viewed, and then it could be mounted normally. [The mounting path is: /run/kata -Containers/AE1F1999611632C96D7EF8A5D5F51894D377259F06336911d02F67474D0/ROOTFS/Prive/Driver/Nvidia], for example, the abnormal scene used 6 GPU cards and called ns_enter, will directly enter the ROOTFS of the container as the root directory, so mount [/run/kata- containers/ae1f8199611632c96d7e2ef8a5d5f51894d377259f062f6336911d02f67474d0/rootfs/proc/driver/nvidia], the path cannot be found. I don’t understand the reason here. I don’t know how to solve this problem.

The nvidia-container-cli  process never exited
root@localhost:/# ps -ef | grep con
root          82       2  0 10:30 ?        00:00:00 [ipv6_addrconf]
root         103       2  0 10:30 ?        00:00:00 [ext4-rsv-conver]
nobody       183     123  0 10:30 ?        00:00:05 /usr/bin/nvidia-container-cli --load-kmods --debug=/run/nvidia-container-toolkit.log configure<EMAIL_ADDRESS>--device=all --compute --utility --require=cuda>=12.3 brand=tesla,driver>=470,driver<471 brand=unknown,driver>=470,driver<471 brand=nvidia,driver>=470,driver<471 brand=nvidiartx,driver>=470,driver<471 brand=geforce,driver>=470,driver<471 brand=geforcertx,driver>=470,driver<471 brand=quadro,driver>=470,driver<471 brand=quadrortx,driver>=470,driver<471 brand=titan,driver>=470,driver<471 brand=titanrtx,driver>=470,driver<471 brand=tesla,driver>=525,driver<526 brand=unknown,driver>=525,driver<526 brand=nvidia,driver>=525,driver<526 brand=nvidiartx,driver>=525,driver<526 brand=geforce,driver>=525,driver<526 brand=geforcertx,driver>=525,driver<526 brand=quadro,driver>=525,driver<526 brand=quadrortx,driver>=525,driver<526 brand=titan,driver>=525,driver<526 brand=titanrtx,driver>=525,driver<526 brand=tesla,driver>=535,driver<536 brand=unknown,driver>=535,driver<536 brand=nvidia,driver>=535,driver<536 brand=nvidiartx,driver>=535,driver<536 brand=geforce,driver>=535,driver<536 brand=geforcertx,driver>=535,driver<536 brand=quadro,driver>=535,driver<536 brand=quadrortx,driver>=535,driver<536 brand=titan,driver>=535,driver<536 brand=titanrtx,driver>=535,driver<536 --pid=147 /run/kata-containers/ae1f8199611632c96d7e2ef8a5d5f51894d377259f062f6336911d02f67474d0/rootfs


[FEATURE] Add checkpoint strategy for the dataset

Is your feature request related to a problem? Please describe.
I would like to save the dataset to disk during the generation process, it can be handy for long running pipelines to not loose the already generated data.
Describe the solution you'd like
A way to save every N generations the dataset to disk automatically.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Closed with #194