Results permissions issue 869

This makes sure that a user has access to requested analysis results files.

Coverage decreased (-0.13%) to 78.56% when pulling 7299e9fe48d3f590e453e35c379a2fd9c0d48ad9 on adamrp:results_permissions-issue-869 into d243968488bdea9cd0bb7fcef4402e79a0c75bf6 on biocore:master.

Coverage decreased (-0.14%) to 78.55% when pulling 467176277b19d5fe27ee1a536016e63b680a8b81 on adamrp:results_permissions-issue-869 into d243968488bdea9cd0bb7fcef4402e79a0c75bf6 on biocore:master.

The user couldn't open it's own results. The issue was that I had a broken study due to some tests and was getting and error.
Have you tested on a machine that has the EMP studies and have some meta-analysis performed with a non admin user? It takes a lot (haven't been able to open one, note that it opens fine for an admin) to open for all the checks it has to do, I believe due to get_accessible_filepath_ids because it uses the object vs. doing a simple query to retrieve what's needed. If we actually deploy this in qiita.server we will bring the server down. Is there a way to make it less expensive?

So if i understand correctly this is no longer an issue.
I tested on only my own machine which has only a few studies, and a
couple meta analyses i used for testing. If we want to use
staticfilehandler, i do not know a cheaper way to do this, since the only
information exposed to the handler is the file path and the user (not even
the analysis id). There are other cheaper ways to do this using regular
handlers, i think. Were you able to test on a system where the expense of
the function caused usability issues?

I'm unable to replicate the issue you are seeing where the user cannot open
an analysis that they have access to. Note that since this is a static file
handler, you have to do a hard refresh to avoid loading from cache; perhaps
that is the issue?
On Feb 19, 2015 6:26 PM, "Antonio Gonzalez"<EMAIL_ADDRESS>wrote:

The user couldn't open it's own results. The issue was that I had a
broken study due to some tests and was getting and error.
Have you tested on a machine that has the EMP studies and have some
meta-analysis performed with a non admin user? It takes a lot (haven't been
able to open one, note that it opens fine for an admin) to open for all the
checks it has to do, I believe due to get_accessible_filepath_ids
because it uses the object vs. doing a simple query to retrieve what's
needed. If we actually deploy this in qiita.server we will bring the server
down. Is there a way to make it less expensive?

—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/pull/873#issuecomment-75174407.

It could be if there are Studies that failed but I think the queue solution that Jose implemented should prevent this.
My "real" case environment is basically the same than qiita: has all the emp studies, with 2 users (mine, regular, and demo, as admin), and when I test a new feature I add new studies.

I tested that and the issue is performance, cause once I try to open a study as a user you can hear my laptop going nuts and you can see an increment of 20% on CPU, 70% on RAM, and heat, without doing anything else + is even worst if you decide to have 2 tabs.

You say study again; do you mean analysis results? Specifically analysis
results from the /results/... URI?
if this is too expensive, then i don't think we can use a static file
handler (or at least i don't know how to implement it).
On Feb 20, 2015 6:14 AM, "Antonio Gonzalez"<EMAIL_ADDRESS>wrote:

It could be if there are Studies that failed but I think the queue
solution that Jose implemented should prevent this.
My "real" case environment is basically the same than qiita: has
all the emp studies, with 2 users (mine, regular, and demo, as admin), and
when I test a new feature I add new studies.

I tested that and the issue is performance, cause once I try to open a
study as a user you can hear my laptop going nuts and you can see an
increment of 20% on CPU, 70% on RAM, and heat, without doing anything else

is even worst if you decide to have 2 tabs.

—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/pull/873#issuecomment-75235914.

Yup, study on the last paragraph really means meta-analysis, sorry for
confusion.
I do not think the issue is how the static handlers perform but how
get_accessible_filepath_ids retrieves the results: get's all the
studies using the Study object, then looks on each of their raw data,
preprocessed data, and process data to retrieve all file paths; then
does the same for analysis. All these is extremely expensive for all
the objects and loops created. I believe that changing this for a
"complex" SQL command will make things way better. Let me know if you
want to chat.

The issue, as I've said, is that you only have a file path and a user.
Let's chat this morning, I'll be in touch soon.
On Feb 20, 2015 7:55 AM, "Antonio Gonzalez"<EMAIL_ADDRESS>wrote:

Yup, study on the last paragraph really means meta-analysis, sorry for
confusion.
I do not think the issue is how the static handlers perform but how
get_accessible_filepath_ids retrieves the results: get's all the
studies using the Study object, then looks on each of their raw data,
preprocessed data, and process data to retrieve all file paths; then
does the same for analysis. All these is extremely expensive for all
the objects and loops created. I believe that changing this for a
"complex" SQL command will make things way better. Let me know if you
want to chat.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/pull/873#issuecomment-75250307.

As Antonio suggested, might this be phrased as a set membership question
against postgres? It likely will still be expensive though, so it might be
worth some thought on either different structures or a more appropriately
structured cache
On Feb 20, 2015 7:58 AM, "adamrp"<EMAIL_ADDRESS>wrote:

The issue, as I've said, is that you only have a file path and a user.
Let's chat this morning, I'll be in touch soon.
On Feb 20, 2015 7:55 AM, "Antonio Gonzalez"<EMAIL_ADDRESS>wrote:

Yup, study on the last paragraph really means meta-analysis, sorry for
confusion.
I do not think the issue is how the static handlers perform but how
get_accessible_filepath_ids retrieves the results: get's all the
studies using the Study object, then looks on each of their raw data,
preprocessed data, and process data to retrieve all file paths; then
does the same for analysis. All these is extremely expensive for all
the objects and loops created. I believe that changing this for a
"complex" SQL command will make things way better. Let me know if you
want to chat.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/pull/873#issuecomment-75250307.

—
Reply to this email directly or view it on GitHub
https://github.com/biocore/qiita/pull/873#issuecomment-75250989.

@antgonza pointed out that the path requested by the user is always either going to be in the BASE_DATA_DIR/job/ directory (or whatever the current mount is), or in a subdirectory of it. Therefore, we can look at the first path element under job/ and just check whether the user has access to that file or directory.
@antgonza can you test this on your database (which is more populated than mine) when you get a chance?

Coverage decreased (-0.11%) to 78.57% when pulling bb10745caf368345c13eed4ff72b29b7ad996ad2 on adamrp:results_permissions-issue-869 into d243968488bdea9cd0bb7fcef4402e79a0c75bf6 on biocore:master.

Thanks @adamrp. This works sooooo much better!
A few comments:

Admins do not have access to all meta-analysis
Raising errors and loging them is fine but it doesn't tell the user
that the meta-analysis doesn't exist or they have not the right
permissions, which might be more useful
I know is not part of this PR but we have discussed a lot on is so
will it be possible to:

Improve speed of opening the main meta-analysis page, this is still
slow compared to opening a job. My guess a lot of object creation.
Improve either how get_accessible_filepath_ids retrieves all ids or
like in this case change it that so it doesn't retrieve all fp ids but
just checking if fileA can be accessed by UserB

For @antgonza comment part 1, you can easily add an if user.admin or user.dev: return True in tehre and get around having to even check admin and dev access.

Admins do not have access to all meta-analysis

Added

Raising errors and loging them is fine but it doesn't tell the user
that the meta-analysis doesn't exist or they have not the right
permissions, which might be more useful

People should never be accessing the /results/ URI directly, so getting a 500 is okay I think.

I know is not part of this PR but we have discussed a lot on is so
will it be possible to:

Improve speed of opening the main meta-analysis page, this is still
slow compared to opening a job. My guess a lot of object creation.
Improve either how get_accessible_filepath_ids retrieves all ids or
like in this case change it that so it doesn't retrieve all fp ids but
just checking if fileA can be accessed by UserB

I think these comments should be addressed in a different PR, as you suggest.
I also addressed @squirrelo's comments, so if/when tests pass, this should be ready for another review. Thanks, guys!

Coverage decreased (-0.2%) to 78.49% when pulling 7705a8b12081c245ca9c52ae0aa214a840e6cfd0 on adamrp:results_permissions-issue-869 into ca1babc6fa1a9fde13b898ae3f8eac15dbfc0043 on biocore:master.

Ready for another review

One philosophical question, but not blocking :+1:

Code looks good to me. @antgonza you've been reviewing this one. Can you check it again and merge if you agree with the code?


Changing entry points for System.Native calls.

Newer version of the CLR uses different names.

We should switch to direct pinvokes on the real target versions I possible.
Sent from my Windows Phone

From: Wiktor<EMAIL_ADDRESS>Sent: 2/4/2016 8:51 PM
To<EMAIL_ADDRESS>Subject: [MIEngine] Changing entry points for System.Native calls. (#171)

Newer version of the CLR uses different names.

You can view, comment on, or merge this pull request online at:
https://github.com/Microsoft/MIEngine/pull/171
Commit Summary

Changing entry points for System.Native calls.

File Changes

M src/MICore/NativeMethods.cshttps://github.com/Microsoft/MIEngine/pull/171/files#diff-0 (6)

Patch Links:

https://github.com/Microsoft/MIEngine/pull/171.patch
https://github.com/Microsoft/MIEngine/pull/171.diff

—
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/MIEngine/pull/171.

Updated to pinvoke directly

:+1:

See my other comment.

I think there's a bigger work item here to make sure this works on all 3 platforms. I will make further changes to the pinvoke once we start that work.

Maybe I am being dumb, but I think in Debugger.cs(488) we are missing a check that we are actually on Linux before we decide to call CmdLinuxBreak instead of the regular async-break processing. Aside from that, looks good.

You are correct, we just check IsLocalGdbAttach. I'm going to test this on OSX and see what happens; assuming attach works with normal exec-interrupt, I can do the OS check. Otherwise, I'll need to make sure the pinvoke works on a mac. Note this must have been an issue before, unless System.Native offered some abstraction around the syscalls.

IsLocalGdbAttach is specific to the Linux local transport isn't it? Regardless of any of this, the wrappers that verify the platform seem like a good idea to me designwise
Sent from my Windows Phone

From: Wiktor<EMAIL_ADDRESS>Sent: 2/5/2016 11:14 PM
To<EMAIL_ADDRESS>Cc: Jackson<EMAIL_ADDRESS>Subject: Re: [MIEngine] Changing entry points for System.Native calls. (#171)
You are correct, we just check IsLocalGdbAttach. I'm going to test this on OSX and see what happens; assuming attach works with normal exec-interrupt, I can do the OS check. Otherwise, I'll need to make sure the pinvoke works on a mac. Note this must have been an issue before, unless System.Native offered some abstraction around the syscalls.
—
Reply to this email directly or view it on GitHubhttps://github.com/Microsoft/MIEngine/pull/171#issuecomment-180711809.

I think IsLocalGdbAttach is agnostic to the transport itself; it's on MICore.Debugger. I think the wrappers are a good idea, but I'd like to unblock Linux debugging support with this change first, and then work on any gaps in OSX support for local gdb.

I think before we would have been okay on OSX, but blow up on Windows.


Option to get all the data

Using a common schema some will inherently lead to some data loss. Add an option to get the complete  source-specific schema.
Another thought is to use the source schema by default and have an option for converting it into a shared schema.

Woops. This is a dup of #3.


Added back UpdatePredictionCache() in updater_gpu_hist.cu.

Added back UpdatePredictionCache() in updater_gpu_hist.cu.

it had been there before, but wasn't ported to the new version
of updater_gpu_hist.cu

Codecov Report

Merging #3120 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #3120   +/-   ##
=========================================
  Coverage     45.27%   45.27%
  Complexity      228      228
=========================================
  Files           166      166
  Lines         12776    12776
  Branches        466      466
=========================================
  Hits           5784     5784
  Misses         6800     6800
  Partials        192      192

Continue to review full report at Codecov.

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

@canonizer any updates?

Working on it.

Were there bug fixes beyond the multi-GPU-ification of the eval_set ?  I see slightly different results in our reproducibility tests with this update, which says this update changed things even for 1 GPU.

This update is about re-introducing UpdatePredictionCache() for the GPU histogram updater, both for single and multiple GPUs. The implementation supports multiple GPUs. Apart from that, there were no other bug fixes.
Regarding reproducibility: could you point me to the tests that produce slightly different results for 1 GPU?


Not able to download big js file e.x: 18MB ??? ( Update: file size is 7 MB )

First very thanks for the tool !!
Is there any limit on the size of the js file to download, I am not able to see any downloaded file in ./downloads when the file is big. Like in my case it was 18 MB.

I haven't tested it with such huge files. I suppose the python requests library might trip up here will have to check. Will get back to this once I have tested it

Thanks, really appreciate this :)

awaiting


Memory leak caused by command probes

TL;DR: K8s command probe executions seem to trigger a memory leak in the containerd-shim-runhcs-v1 process.
In our AKS production systems we're facing memory consumption issues on our Windows Server 2019 nodes where the nodes' memoryWorkingSetBytes steadily (mostly linearly) increases over time.
This increase does not show on the different K8s pod's reported "MEM" values, still on K8s node-level total "MEM" values.
So we took a look at the nodes' process lists and mentioned that the containerd-shim-runhcs-v1.exe processes' working set size increased over time (and this shim's working set size seems to be not part of the K8s pod/container "MEM" values).
We also saw a pattern that not all shim processes increase in memory, just the ones hosting containers with a configured readiness or liveness command probe (in contrast httpGet probes don't seem to trigger the memory leak).
So we created 3 minimal repro K8s deployments with a bare mcr.microsoft.com/windows/servercore:ltsc2019 container with 1, 10, and 60 second interval readiness probes and also these show a steady shim process working set increase. See the attached CommandProbeRepro.zip for the used K8s deployment YAML files.
Mem impact of the repro sample: After 2.7 days the 1 sec interval container shim had ~ 1400 MB, the 10 sec had ~190 MB and the 60 sec had ~50 MB working set size. So we see that the working set size directly correlates to the command probe interval (and container age). Also we see that all of these shims are larger then non-probe shim processes (which are ~5-20 MB).
So we suspect a memory leak in the command probe code (maybe a process handle leak?) ...
Note that this may be the underlying problem of the containerd bug report "Windows Container memory leak with Calico Felix HostProcess container".
Further note that this issue also affects AKS default containers like the csi-azuredisk-node-win daemon set which defines command probes.

I can confirm this issue in our WS2022 clusters

This issue has been fix in hcsshim and changes have been made to upstream containerd release/1.6, release/1.5 with the new shim tag. PR in upstream containerd/main branch has got sign offs and pending merge

For future reference, this seems to be the PR with the fix, if I'm not mistaken: https://github.com/microsoft/hcsshim/pull/1601.

@kiashok Many many thanks for the fix! ❤
If I see it correctly this is fixed with hcsshim 0.9.6 and 0.10.0-rc.3. Right?
And the backport to containerd 1.6 happened in https://github.com/containerd/containerd/commit/ffc16f5562768745965bda11ae61d93e2328f566. Right?
... and this means that this issue is already fixed with containerd 1.6.13. Right?

@kiashok Many many thanks for the fix! ❤
If I see it correctly this is fixed with hcsshim 0.9.6 and 0.10.0-rc.3. Right?
And the backport to containerd 1.6 happened in containerd/containerd@ffc16f5. Right?
... and this means that this issue is already fixed with containerd 1.6.13. Right?

These are the hcsshim tags that have the fix for each of the branches:
release/1.5: v0.8.25
release/1.6: v0.9.6
containerd/main: v0.10.0-rc3
For release/1.6, tags 1.6.13 and 1.6.14 should have the fix

Perfect. Many thanks again @kiashok!


Remove wildcard imports

I think it can be shoud be a good feature.

ArchUnit is primarily designed for analyzing and enforcing architectural rules on Java bytecode. Since it operates on bytecode rather than source code, it does not have direct access to the original import statements, including wildcard imports, which are removed during the compilation process. Bytecode does not retain information about the specific form of import statements used in the source code.


Removed the Payments.Domain dependency from the Administration.Domain…

… project.

Wow, it was a surprise! Thanks @heymega


Publish on Maven

I couldn't find this library on Maven. If it isn't, could you please upload it there?
Alternatively, you could checkout https://jitpack.io/, which is much easier to setup

Any news on publishing a package ?

Thanks for your interest here! But as you can see, it has been years since I worked on this, so I have no idea how well it works - feel free to pick it up though :)


Option to autohide minimap when in Split Editor view

VSCode Version: 1.13.0
OS Version: Windows 10

Steps to Reproduce:

"editor.minimap.enabled": true

Idea: There should be an option when user is in Split Editor the minimap will be hidden automatically.
Especially on smaller resolutions the minimap takes too much space when working in Split Editor view.
For example something like this: "editor.minimap.spliteditorhide": true

I agree that it takes too much space with Split editors, but I also like to look at the minimap sometimes -- maybe a nice solution would be to "auto-hide" the minimap? It would disappear when you edit code, and fade in if you, for example, start scrolling.

As @quezak suggested, auto-hiding the minimap could also be a solution for this problem.
Thanks for providing the link. That plugin looks promising and something like that would be nice to have also on VS Code.

Sublime text 3 also have a plugin for this, which i have used for a long time. The minimap is great when you need it, but often it just takes up way to much space, especially when you have more than one view open.
As @quezak said, the option to only show the minimap on scroll or hoover would be great, which i believe would also cover the case with the minimap taking up to much space when using multiple views.

+1 for auto-hiding and only show on scrolling.

+1

+1

+1

It seems that there are a lot of situations when a user may wish the minimap to be disabled. Perhaps a general solution is called for: editor.minimap.disableIf: ["fileFitsInView", "viewNotInFocus", "notScrolling"]
However it is implemented, it would be very nice if there was support for conditionally disabling the minimap.

Definitely would be a big win for me. I use a plugin to hide the explorer, which is a big win in split view, but the minimap really does take up a ton of space, especially in the (admittedly rare) instances where VS Code isn't maximized. But I definitely do want the minimap - I use highlighted markers to indicate points in files I want to bookmark, and the minimap is a great way to zip between them.


[BUG]

Context
In order to help us troubleshoot issues with this project, you must provide the following details:

ElasticDump version:latest
Elasticsearch version:6.5.1
Node.js version (note that nodejs v10+ is required for this tool):latest from official
Full command you are having issue with (with inputs and outputs)
      elasticdump \       --input=${es_url}/${index} \       --output=${backup_dir}/${time}/${index}/${type}.json \       --type=${type} \       --limit=5000 \       --concurrency=10 \       --fsCompress \       --fileSize=10kb \       --overwrite=true >>${logfile}

Describe the bug
I used --filesize,i don't know how to restore from the spilted files?
can i get any help from here ?

You can use multi-elasticdump to restore all files in a folder or simply restore 1 at a time

You can use multi-elasticdump to restore all files in a folder or simply restore 1 at a time

thanks


Pinning a nightly toolchain version

Hi,
This repo currently doesn't work on latest nightly, and it's hard to keep up with each nightly, so what tools like miri and others do is pin a specific nightly version and bump it as often as they like, that way you batch fixes and don't need to run around fixing it every day.
using bisect-rustc(https://github.com/rust-lang/cargo-bisect-rustc) with rustc-dev enabled(https://github.com/rust-lang/cargo-bisect-rustc/pull/101) I was able to find the latest nightly we can still compile against, from that I looked for the latest one that contains dev tools like clippy, rustfmt, etc. and that's how I got to nightly-2020-06-10:

Bisect output

$ cargo bisect-rustc --preserve --with-dev --start 2020-06-02 -- check
installing nightly-2020-06-02
llvm-tools: 18.76 MB / 18.76 MB [=========================================================================================================================================================================================================================] 100.00 % 10.71 MB/s
testing...
RESULT: nightly-2020-06-02, ===> No

installing nightly-2020-07-11
testing...
RESULT: nightly-2020-07-11, ===> Yes

installing nightly-2020-06-21
llvm-tools: 18.84 MB / 18.84 MB [=========================================================================================================================================================================================================================] 100.00 % 10.12 MB/s
testing...
RESULT: nightly-2020-06-21, ===> Yes

installing nightly-2020-06-11
llvm-tools: 18.77 MB / 18.77 MB [==========================================================================================================================================================================================================================] 100.00 % 6.20 MB/s
testing...
RESULT: nightly-2020-06-11, ===> No

installing nightly-2020-06-16
llvm-tools: 18.84 MB / 18.84 MB [==========================================================================================================================================================================================================================] 100.00 % 5.60 MB/s
testing...
RESULT: nightly-2020-06-16, ===> Yes

installing nightly-2020-06-13
llvm-tools: 18.84 MB / 18.84 MB [==========================================================================================================================================================================================================================] 100.00 % 6.73 MB/s
testing...
RESULT: nightly-2020-06-13, ===> No

installing nightly-2020-06-14
llvm-tools: 18.84 MB / 18.84 MB [==========================================================================================================================================================================================================================] 100.00 % 7.00 MB/s
testing...
RESULT: nightly-2020-06-14, ===> No

installing nightly-2020-06-15
llvm-tools: 18.83 MB / 18.83 MB [=======================================================================================================================================================================================================================] 100.00 % 6.96 MB/s 0s
testing...
RESULT: nightly-2020-06-15, ===> No

searched toolchains nightly-2020-06-02 through nightly-2020-07-11

********************************************************************************
Regression in nightly-2020-06-16
********************************************************************************

$ rustup install nightly-2020-06-16
info: syncing channel updates for 'nightly-2020-06-16-x86_64-unknown-linux-gnu'
info: latest update on 2020-06-16, rust version 1.46.0-nightly (f315c35a7 2020-06-15)
error: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel nightly-2020-06-16
Sometimes not all components are available in any given nightly.

$ rustup install nightly-2020-06-15
info: syncing channel updates for 'nightly-2020-06-15-x86_64-unknown-linux-gnu'
info: latest update on 2020-06-15, rust version 1.46.0-nightly (4fb54ed48 2020-06-14)
error: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel nightly-2020-06-15
Sometimes not all components are available in any given nightly.

$ rustup install nightly-2020-06-14
info: syncing channel updates for 'nightly-2020-06-14-x86_64-unknown-linux-gnu'
info: latest update on 2020-06-14, rust version 1.46.0-nightly (06e47688b 2020-06-13)
error: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel nightly-2020-06-14
Sometimes not all components are available in any given nightly.

$ rustup install nightly-2020-06-13
info: syncing channel updates for 'nightly-2020-06-13-x86_64-unknown-linux-gnu'
info: latest update on 2020-06-13, rust version 1.46.0-nightly (f4fbb9311 2020-06-12)
error: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel nightly-2020-06-13
Sometimes not all components are available in any given nightly.

$ rustup install nightly-2020-06-12
info: syncing channel updates for 'nightly-2020-06-12-x86_64-unknown-linux-gnu'
info: latest update on 2020-06-12, rust version 1.46.0-nightly (a37c32e2d 2020-06-11)
error: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel nightly-2020-06-12
Sometimes not all components are available in any given nightly.

$ rustup install nightly-2020-06-11
info: syncing channel updates for 'nightly-2020-06-11-x86_64-unknown-linux-gnu'
info: latest update on 2020-06-11, rust version 1.46.0-nightly (449e8eaa2 2020-06-10)
error: component 'rustfmt' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel nightly-2020-06-11
Sometimes not all components are available in any given nightly.

$ rustup install nightly-2020-06-10
info: syncing channel updates for 'nightly-2020-06-10-x86_64-unknown-linux-gnu'
info: latest update on 2020-06-10, rust version 1.46.0-nightly (feb3536eb 2020-06-09)
info: downloading component 'cargo'
info: downloading component 'clippy'
info: downloading component 'rust-docs'
 12.2 MiB /  12.2 MiB (100 %)  10.0 MiB/s in  1s ETA:  0s
info: downloading component 'rust-std'
 15.8 MiB /  15.8 MiB (100 %)   9.5 MiB/s in  1s ETA:  0s
info: downloading component 'rustc'
 47.4 MiB /  47.4 MiB (100 %)   9.2 MiB/s in  5s ETA:  0s
info: downloading component 'rustfmt'
info: installing component 'cargo'
info: Defaulting to 500.0 MiB unpack ram
info: installing component 'clippy'
info: installing component 'rust-docs'
info: installing component 'rust-std'
info: installing component 'rustc'
 47.4 MiB /  47.4 MiB (100 %)  16.0 MiB/s in  2s ETA:  0s
info: installing component 'rustfmt'

  nightly-2020-06-10-x86_64-unknown-linux-gnu installed - rustc 1.46.0-nightly (feb3536eb 2020-06-09)

$ rustup component add rustc-dev llvm-tools-preview --toolchain=nightly-2020-06-10
info: downloading component 'rustc-dev'
info: installing component 'rustc-dev'
info: Defaulting to 500.0 MiB unpack ram
 70.4 MiB /  70.4 MiB (100 %)  15.7 MiB/s in  4s ETA:  0s
info: downloading component 'llvm-tools-preview'
 18.8 MiB /  18.8 MiB (100 %)   6.7 MiB/s in  3s ETA:  0s
info: installing component 'llvm-tools-preview'
 18.8 MiB /  18.8 MiB (100 %)  16.2 MiB/s in  1s ETA:  0s

One of the tests is failing though

$ cargo +nightly-2020-06-10 test

    Finished test [unoptimized + debuginfo] target(s) in 0.11s
     Running target/debug/deps/semverver-ba86c08423bfa21d

running 7 tests
test changes::tests::bchange_span_neq ... ok
test changes::tests::pchange_span_neq ... ok
test changes::tests::ord_change_transitive ... ok
test changes::tests::ord_pchange_transitive ... ok
test changes::tests::max_pchange ... ok
test changes::tests::max_change ... ok
test changes::tests::max_pchange_or_change ... ok

test result: ok. 7 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running target/debug/deps/cargo_semver-032bc82a6c7f3a6c

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running target/debug/deps/rust_semver_public-b6122a2748bb056b

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running target/debug/deps/rust_semverver-1e0c5ef1e2a72092

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running target/debug/deps/debug-c9e5a605732cb514

running 1 test
test debug ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running target/debug/deps/examples-74699b1e36997402

running 31 tests
test features::func_local_items ... ok
test features::issue_34 ... ok
test features::enums ... ok
test features::infer_regress ... ok
test features::func ... ok
test features::macros ... ok
test features::issue_50 ... ok
test features::consts ... ok
test features::inherent_impls ... ok
test features::kind_change ... ok
test features::bounds ... ok
test features::infer ... ok
test features::circular ... ok
test features::max_priv ... ok
test features::pathologic_paths ... ok
test features::mix ... ok
test features::removal ... ok
test features::addition ... ok
test features::sealed_traits ... ok
test features::regions ... ok
test features::pub_use ... ok
test features::structs ... ok
test features::removal_use ... ok
test features::removal_path ... ok
test features::addition_use ... ok
test features::swap ... ok
test features::trait_impls ... ok
test features::trait_objects ... ok
test features::addition_path ... ok
test features::ty_alias ... ok
test features::traits ... ok

test result: ok. 31 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out

     Running target/debug/deps/full-3b50b967eb8ab8ee

running 4 tests
test full::log ... FAILED
test full::libc0 ... ok
test full::libc1 ... ok
test full::rmpv ... ok

failures:

---- full::log stdout ----
cargo-semver failed to produce the expected output
For details, try this command:

    diff tests/full_cases/log-0.3.4-0.3.8.linux /home/elichai2/gits/rust-semverver/target/debug/build/semverver-2de39b970bca2114/out/log-0.3.4-0.3.8.linux

thread 'full::log' panicked at 'unexpected output diff', tests/full.rs:143:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

failures:
    full::log

test result: FAILED. 3 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out

error: test failed, to rerun pass '--test full'

Fixed the failing tests

Great work with cargo-bisect-rust, that's helpful! I hope you don't mind me pinning the version first, I wanted to clean up the current state a little bit first.
Could you rebase and skip the CI changes from here? It'd be great if we could get the ball rolling and start incrementally getting sermverver up to speed in terms of latest nightly support. Thank you!

@Xanewok Done

Thank you!


Updating the error message to say node instead of minion

Fixes 2nd part of https://github.com/GoogleCloudPlatform/kubernetes/issues/10156
Change:
$kubectl get nodes asdf

returned
Earlier:
Error from server: minion "asdf" not found
Now:
Error from server: node "asdf" not found

cc @marekbiskup

Note that the endpoint name is used only for error reporting, so this change should not affect anything else other than error messages: https://github.com/GoogleCloudPlatform/kubernetes/blob/4fdcbc3096432692ee27c8d3f7e85580b29f780c/pkg/registry/generic/etcd/etcd.go#L63

lgtm

Can you recommend another reviewer? e2e test passing suggests change is low-risk, but I'm not familiar with the pkg.

LGTM

Risk assessment: very low.
Just an error message change.

@jlowdermilk Can I have a merge?

lgtm


fix 3.3.x ui error

Description

The operation row display function does not work in the table view.
You need to adjust the width of the data source list column.
Administrator> Workspace> Details> Data Source Popup> Top part of the icon is cut off.
Administrator> Workspace Permission> Workspace Permission Details> Workspace Details-Previous icon should be moved to Workspace list.
Toast error exclusions are required when retrieving period dates in Users> Membership Approval.

Related Issue :

How Has This Been Tested?

In the table view, check that the operation row is displayed normally.
Verify that the data source list column width is adjusted.
Verify that Administrator> Workspace> Details> Data Sources Popup> Top of the icon is displayed correctly.
If Administrator> Workspace Permission> Workspace Permission Details> Workspace Details-Previous icon is clicked, check if it moves to Workspace list.
Under Users> Membership Approval, verify that no warnings are displayed when searching for period dates.

Need additional checks?
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.

Additional Context

deploy to 3


Reattaching kernel driver failed

Sorry if this is fixed or mentioned in another place. I have everything updated in HA and my Accurite to HA was working great. Now it only works for a short period (10 min) and then stops reporting.

I get this too.  Units stop reporting and I have to restart acurite2mqtt to  get readings again.
08:12:21] INFO: AUTO_DISCOVERY = true
[08:12:21] INFO: DEBUG = false
::::::::rtl_433 running output::::::::
rtl_433 version v20240329-2644-gd4bd429382d branch master at<PHONE_NUMBER>41 inputs file rtl_tcp RTL-SDR with TLS
MQTT: Publishing MQTT data to <IP_ADDRESS> port 1883
MQTT: Publishing device info to MQTT topic "rv_rtl_433[/model][/id][/channel:A]".
MQTT: Publishing events info to MQTT topic "rv_rtl_433/events".
MQTT: Publishing states info to MQTT topic "rv_rtl_433/states".
Use "-F log" if you want any messages, warnings, and errors in the console.
Detached kernel driver
INFO:Started
Found Rafael Micro R820T tuner
Exact sample rate is:<PHONE_NUMBER>14 Hz
[R82XX] PLL not locked!
cb transfer status: 1, canceling...
Reattaching kernel driver failed!

There isn't anything I can do about that one. That is coming from the RTL_433 program, and based their git hub issue page it is a hardware issue, and not something they can catch in their app and prevent.
Likely a usb port / power issue / or usb dongle chip issue.

Thank you Jeffrey.
George
On Wed, Jul 17, 2024 at 9:32 PM Jeffrey Stone @.***>
wrote:

There isn't anything I can do about that one. That is coming from the
RTL_433 program, and based their git hub issue page it is a hardware issue,
and not something they can catch in their app and prevent.
Likely a usb port / power issue / or usb dongle chip issue.
—
Reply to this email directly, view it on GitHub
https://github.com/thejeffreystone/hassio_addons/issues/61#issuecomment-2235246326,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEITF266ILBPFOM4ARJFSTZM4ZM5AVCNFSM6AAAAABF7H4W7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZVGI2DMMZSGY
.
You are receiving this because you commented.Message ID:
@.***>

--
George Kerr
“Life’s under no obligation to give us what we expect.” ― Margaret
Mitchell
WebPilot
Just Friends Camping
Rocky Mountain High Escapees Chapter 2


Failed to stop service 'gitHubDependencyExtractorService'

I am attempting to use version 3.3.0 in a multi-module project and receive the following exception:
2: Task failed with an exception.

What went wrong:
Failed to stop service 'gitHubDependencyExtractorService'.

The GitHubDependencyGraphPlugin plugin encountered errors while writing the dependency snapshot json file. Please report this issue at: https://github.com/gradle/github-dependency-graph-gradle-plugin/issues

Caused by: org.gradle.api.GradleException: The GitHubDependencyGraphPlugin plugin encountered errors while writing the dependency snapshot json file. Please report this issue at: https://github.com/gradle/github-dependency-graph-gradle-plugin/issues
at org.gradle.github.dependencygraph.internal.DependencyExtractor.close(DependencyExtractor.kt:271)
at org.gradle.api.services.internal.RegisteredBuildServiceProvider.lambda$maybeStop$1(RegisteredBuildServiceProvider.java:168)
... 132 more
Caused by: java.lang.IllegalStateException: The configuration parameter 'GITHUB_JOB_CORRELATOR' must be set: set an environment variable, or use '-DGITHUB_JOB_CORRELATOR=value' on the command-line.
at org.gradle.github.dependencygraph.internal.util.PluginParameters.throwEnvironmentVariableMissingException(PluginParameters.kt:34)
at org.gradle.github.dependencygraph.internal.util.PluginParameters.load(PluginParameters.kt:25)
at org.gradle.github.dependencygraph.internal.util.PluginParameters.load$default(PluginParameters.kt:21)
at org.gradle.github.dependencygraph.internal.DependencyExtractor$gitHubSnapshotParams$2.invoke(DependencyExtractor.kt:55)
at org.gradle.github.dependencygraph.internal.DependencyExtractor$gitHubSnapshotParams$2.invoke(DependencyExtractor.kt:23)
at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
at org.gradle.github.dependencygraph.internal.DependencyExtractor.getGitHubSnapshotParams(DependencyExtractor.kt)
at org.gradle.github.dependencygraph.internal.DependencyExtractor.writeDependencyGraph(DependencyExtractor.kt:242)
at org.gradle.github.dependencygraph.internal.DependencyExtractor.close(DependencyExtractor.kt:269)

How are you using the plugin?
The error message indicates that you aren't setting one of the required inputs:
The configuration parameter 'GITHUB_JOB_CORRELATOR' must be set: set an environment variable, or use '-DGITHUB_JOB_CORRELATOR=value' on the command-line.
If you're using this plugin standalone, please first try getting it working using these instructions: https://github.com/gradle/github-dependency-graph-gradle-plugin?tab=readme-ov-file#using-the-plugin-to-generate-dependency-reports. That way you don't need to provide any GitHub specific context.

Sorry, you shouldn't have been asked to "Please report this issue" in this case.
The exception message identifies the problem and what you need to do to fix it.
I've raised #134 to fix the error message to make this clearer in the future.

I found a cause. On not-ephemeral build like a self-hosted server, init script is left on gradle user home init.d directory.
If you have used<EMAIL_ADDRESS>or earler, the init script still 0.2.0 that is not use GITHUB_JOB_CORRELATOR.
If you want to fix this, try to delete gradle user home's  init script.


path of building don't ignore equipaments that you cannot use

/

Could you give me your build? I can't seem to find any problems with that skill.

nvm .... the path of build don't ignore equipaments that you cannot use .. so the weapon i'm using it's include even if i don't have enough int to use.. this cause my path of build to not load the damage of ancestral warchief.. i'm using facebreaker

There's a very good reason for that. When planning a build, attribute requirements is something that you generally sort out towards the end; so requiring the user to fulfil them even in the earliest stages is counter-productive, and would be horrible to work with.
Of course I could add the option to enable enforcement of requirements; it's not something I'm currently planning to do, but I will at least consider it.

don't worry :D.. but thx for the answer :D


Create Quality and Analysis Categories for the Hub

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/263
Originally created by @tayloramurphy on 2022-05-27 21:07:56

From https://gitlab.com/meltano/hub/-/issues/261#note_962952778 - we're hiding a lot of the value of Meltano by having Great Expectations and Superset behind the generic "Utilities"
On the backend these can still be a utility plugin type, but for the landing page on the Hub we should have these separated into different categories.

View 9 previous comments from the original issue on GitLab

@tayloramurphy if we leave the backend as it is i'll just have to hardcode a data-analysis.html and data-quality.html for folks to land. and they would still show up in utilities and be found at hub/utilities/{plugin_name}. would you rather i change the backend or just hardcode some stuff for now?

@tayloramurphy @alexmarple "elsewhere" was on GitLab fwiw: https://gitlab.com/meltano/hub/-/issues/263#note_963113364

@alexmarple We'd need them to still show up under utilities on the backend because the API uses that information as well. Decoupling the way they're categorized on the website from the way they're actually stored on the backend may be too difficult with the current codebase.

@DouweM thank you for clarifying.
To be clear on the scope:

utility plugins that have either analysis or quality in their keywords list will need to be listed under both under Analysis / Quality categories & Utility Categories
Analysis / Quality are essentially filtered views of the Utility view
The content for the plugins listed under analysis / quality will be the exact same as when a user clicks on them in the Utility view
For the top search, it'd be nice to only have them listed under Analysis / Quality, but perhaps just keeping it under Utility in the dropdown would be best?

Goal is mainly to make the homepage look better!


🛠 Tooling: Find a way to avoid 'as unknown as ESTree.Node' assertions

Bug Report Checklist

[X] I have tried restarting my IDE and the issue persists.
[X] I have pulled the latest main branch of the repository.
[X] I have searched for related issues and found none that matched my issue.

Overview
Following #40 & #59 & https://github.com/ota-meshi/jsonc-eslint-parser/issues/184: the current state of types for AST nodes in this plugin is that we've completely swapped out the built-in ESLint ones. Nodes are instead typed using import type { AST as JsonAST } from "jsonc-eslint-parser"; -> node: JsonAST.JSONProperty and the like.
Unfortunately, ESLint's APIs still expect ESTree nodes. So we end up with assertions any time we need to pass the nodes to ESLint's APIs:
https://github.com/JoshuaKGoldberg/eslint-plugin-package-json/blob/84035c3f2bac376567eef767ba21f354a0d93f54/src/rules/valid-repository-directory.ts#L32-L34
This isn't ideal. One workaround done by eslint-plugin-jsonc is to instead pass loc: node.loc. But I'd ideally like to be able to just pass the node directly.
Additional Info
I don't know a straightforward way to make this better. context.report is typed in @types/eslint as:
report(descriptor: ReportDescriptor): void;

...with:
type ReportDescriptor = ReportDescriptorMessage & ReportDescriptorLocation & ReportDescriptorOptions;
type ReportDescriptorMessage = { message: string } | { messageId: string };
type ReportDescriptorLocation =
    | { node: ESTree.Node }
    | { loc: AST.SourceLocation | { line: number; column: number } };

I suppose @types/eslint could mark the context with a type parameter like <Node = ESTree.Node> 😬... Eww.
Filed https://github.com/ota-meshi/jsonc-eslint-parser/issues/198. Marking as blocked pending discussion there.

Curious if it makes sense to still pursue this if the ultimate direction is to move to @eslint/json (https://github.com/JoshuaKGoldberg/eslint-plugin-package-json/issues/655)?

It'd be great if resolving #655 resolved this too, yes!


Website completely broke after an edit

Describe the bug
The website is broke after an edit because I ask Bolt to NOT EDIT the rest of the file.
And it insert lot of mention like that :

Link to the Bolt URL that caused the error
https://bolt.new/~/bolt-vanilla-vite-rr3bsw
Steps to reproduce
Ask Bolt to not edit the rest of the website
Expected behavior
I expect Bolt to not redo the entire projet on every prompt because every time it break everything and this is a pain
Screen Recording / Screenshot
No response
Platform
Browser name = Chrome
Full version = <IP_ADDRESS>
Major version = 128
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36 OPR/<IP_ADDRESS>
performance.memory = {
  "totalJSHeapSize": 81180106,
  "usedJSHeapSize": 75257666,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Username = RiderFx3
Chat ID = 42113d6fc387

Additional context
No response

If you right-click a file in the Bolt code editor and select "Lock file" this will prevent the AI from making further changes to that file. The Bolt Help Center contains a number of resources on using Bolt most effectively.


Building wipes out scripting define symbols

I have multiple assets (like the post processing stack) that set scripting define symbols in ProjectSettings/ProjectSettings.asset.
Building with this tool always wipes them out. It would be nice if it could just add its own symbols to the list rather than replacing them. I can't really move the symbols into SuperUnityBuild because the assets themselves automatically define these symbols. Many assets seem to do it so it is apparently a common pattern.
This issue is also described here: https://github.com/Chaser324/unity-build/issues/12#issuecomment-293744300
Here's my git diff after running a build:
--- a/ProjectSettings/ProjectSettings.asset
+++ b/ProjectSettings/ProjectSettings.asset
@@ -118,7 +118,7 @@ PlayerSettings:
     16:10: 1
     16:9: 1
     Others: 1
-  bundleVersion: 1010
+  bundleVersion: 1011
   preloadedAssets: []
   metroInputSource: 0
   wsaTransparentSwapchain: 0
@@ -553,7 +553,7 @@ PlayerSettings:
   webGLCompressionFormat: 1
   webGLLinkerTarget: 1
   scriptingDefineSymbols:
-    1: DOTWEEN_TMP;DOTWEEN_TMP;UNITY_POST_PROCESSING_STACK_V2;FIRST_PERSON_CONTROLLER;THIRD_PERSON_CONTROLLER;ULTIMATE_CHARACTER_CONTROLLER_SHOOTER;ULTIMATE_CHARACTER_CONTROLLER_MELEE;AMPLIFY_SHADER_EDITOR;GPU_INSTANCER
+    1: BUILD_TYPE_PRIMARY;BUILD_PLATFORM_PC;BUILD_ARCH_WINDOWSX64
     4: DOTWEEN_TMP
     7: UNITY_POST_PROCESSING_STACK_V1;DOTWEEN_TMP;UNITY_POST_PROCESSING_STACK_V2
     13: UNITY_POST_PROCESSING_STACK_V1;DOTWEEN_TMP;UNITY_POST_PROCESSING_STACK_V2

Ah. I hadn't really accounted for this. #12 is a slightly more specific scenario that I already addressed, but I really should've adopted a more general approach that would've fixed this issue as well.
I should be able to get a fix out for this within the next day or two.

Wow, great! Thanks!

This should now be fixed. Let me know if there's a scenario that this change doesn't address.

FWIW, can confirm this has been working just fine for me in builds I have been producing using Super Unity Build (including ones that set custom defines as part of a release) since this commit, so you could consider closing this issue.


Support for scoped packages

The npm extension breaks when used in a scoped package or when it's used in a package with scoped dependencies.
Details on scope

What folder are these put in? If the package is @foo/bar is the folder node_modules/bar or node_modules/foo/bar ?

Scoped packages are grouped together so if I install @foo/bar and @foo/baz, the structure would be:
/node_modules
    /foo
        /bar
        /baz

I pushed a breaking test to https://github.com/stealjs/system-npm/commit/34b209ec6d137afc9a143002bf9ce7507c3d7f17, if you could take a look and let me know if the file structure is correct, if the two package.jsons are correct and if the main.js is correct that would be helpful.

Yea that will work.
There are two cases that break right now:

Using scoped dependencies
Using steal in a scoped package

The test you've constructured is for 1, but I imagine once the npm plugin can parse the scoped package properly the second case will be solved as well.

ah, so if I change the main package scoped to @scoped/package or something that should cover them both. I'll do that.

Actually scoped packages do get installed with the @ in the folder name.

Hey @ccummings, I think I have a fix for this. It's in the scoped branch.  If you could, would you mind copying this file: https://raw.githubusercontent.com/stealjs/system-npm/scoped/npm-utils.js
into your project's node_modules/steal/ext folder and give it a try? That's the only file needed to fix this (I think, hopefully).


Error: Inference status for the task 14 is failed.

My actions before raising this issue

[x] Read/searched the docs
[x] Searched past issues

I created a new organization.
In this organization, I created a new project.
In the new project,  I created several tasks with images (each task containing ~4k images)

Steps to Reproduce (for bugs)

Create a new organization
Create a new project in the newly created organization
Create several tasks (each with ~4k images)
In the task view select "Actions" -> "Automatic annotation" -> select a model -> "Annotate"

Expected Behaviour

Annotation is running an I see the labeled data when I inspect the tasks.
Current Behaviour

For some tasks I get an error:
Fetching inference status for the task 13
Error: Inference status for the task 13 is failed. FileNotFoundError: [Errno 2] No such file or directory: '/home/django/share/testdata/extraxted_filtered_1/20230129_020645_370151.jpg'
If I open the task and visually inspect the images I am able to verify that this image DOES EXIST in the task.
Let me know if you need further information.

Hi @maecky

DOES EXIST in the task.

Are you sure? They can be just cached on the server.
As I can see, it tries to retrive data from the attached storage, looks like you created a task with data from there. Data are not copied by default to avoid extra disk memory consumption. So, check these data on the shared storage.
If you want to copy data when create a task, use the dedicated option:

Yes, I am 100% sure. My cloud connection isn't working anymore (see other issue: https://github.com/opencv/cvat/issues/5885) and the images are still there. I tried to run the inference task again with the same error.
Here is the CVAT Server log:
2023-03-28 11:25:25 2023-03-28 09:25:25,714 DEBG 'runserver' stderr output:
2023-03-28 11:25:25 [Tue Mar 28 09:25:25.714832 2023] [wsgi:error] [pid 70:tid<PHONE_NUMBER>31872] [remote <IP_ADDRESS>:33036] [2023-03-28 09:25:25,714] WARNING django.request: Not Found: /api/functions/requests/
2023-03-28 11:25:25
2023-03-28 11:25:25 2023-03-28 09:25:25,715 DEBG 'runserver' stderr output:
2023-03-28 11:25:25 [Tue Mar 28 09:25:25.714917 2023] [wsgi:error] [pid 70:tid<PHONE_NUMBER>31872] [remote <IP_ADDRESS>:33036] WARNING:django.request:Not Found: /api/functions/requests/
2023-03-28 11:25:25
2023-03-28 11:25:30 2023-03-28 09:25:30,656 DEBG 'runserver' stderr output:
2023-03-28 11:25:30 [Tue Mar 28 09:25:30.656816 2023] [wsgi:error] [pid 70:tid<PHONE_NUMBER>31872] [remote <IP_ADDRESS>:33076] [2023-03-28 09:25:30,656] INFO cvat.server.task_13: get repository request
2023-03-28 11:25:30
2023-03-28 11:25:30 2023-03-28 09:25:30,658 DEBG 'runserver' stderr output:
2023-03-28 11:25:30 [Tue Mar 28 09:25:30.658153 2023] [wsgi:error] [pid 70:tid<PHONE_NUMBER>31872] [remote <IP_ADDRESS>:33076] INFO:cvat.server.task_13:get repository request
2023-03-28 11:25:30
2023-03-28 11:26:09 2023-03-28 09:26:09,919 DEBG 'runserver' stderr output:
2023-03-28 11:26:09 [Tue Mar 28 09:26:09.918912 2023] [wsgi:error] [pid 70:tid<PHONE_NUMBER>44832] [remote <IP_ADDRESS>:33414] [2023-03-28 09:26:09,918] INFO cvat.server.task_13: get repository request
2023-03-28 11:26:09
2023-03-28 11:26:09 2023-03-28 09:26:09,920 DEBG 'runserver' stderr output:
2023-03-28 11:26:09 [Tue Mar 28 09:26:09.920201 2023] [wsgi:error] [pid 70:tid<PHONE_NUMBER>44832] [remote <IP_ADDRESS>:33414] INFO:cvat.server.task_13:get repository request
2023-03-28 11:26:09

(Apart from that, it would be really nice to run inference on a remote storage - copy on demand, but that's a different topic :)  )

Not sure what the expected behavior is but when creating a task using cloud storage I get a similar error.
Could not create the task on the server. FileNotFoundError: [Errno 2] No such file or directory:

'/home/django/data/data/58/raw/third-party-datasets/coco2017/train2017/000000000009.jpg'.

I have cache data un-checked:

Is this required for cloud storage? My hope was not to have to cache locally.

I have experienced a similar problem but using a fileshare. I am using videos with a resolution of 512x640. For some videos, the annotation will progress for a while before giving a similar error to what is mentioned here. I suspect there is some sort of timeout issue.

I managed to fix my issue by modifying my docker-compose.override.yml where I had specified my fileshare to include the cvat_worker_annotation container to also have access to my mount by adding
  cvat_worker_annotation:
    volumes:
      - cvat_share:/home/django/share:ro```

Probably we need to update our guides, thank you.

I'll also mention that I had to do something similar for the cvat_worker_export container to work. I'm not sure if there are any other containers that would be affected also.


Reverb_HQ_By_FoxJoy.onnx cannot work, I cannot figure out what happened here, please help.

2024-04-11 11:12:16,256 - INFO - separator - Separator version 0.16.4 instantiating with output_dir: \output, output_format: WAV
2024-04-11 11:12:16,256 - INFO - separator - Operating System: Windows 10.0.19045
2024-04-11 11:12:16,256 - INFO - separator - System: Windows Node: NLY-ZJ0015 Release: 10 Machine: AMD64 Proc: Intel64 Family 6 Model 165 Stepping 3, GenuineIntel
2024-04-11 11:12:16,256 - INFO - separator - Python Version: 3.9.13
2024-04-11 11:12:16,256 - INFO - separator - PyTorch Version: 2.2.2+cu118
2024-04-11 11:12:16,269 - INFO - separator - FFmpeg installed: ffmpeg version 6.1.1-essentials_build-www.gyan.dev Copyright (c) 2000-2023 the FFmpeg developers
2024-04-11 11:12:16,273 - INFO - separator - ONNX Runtime GPU package installed with version: 1.17.1
2024-04-11 11:12:16,299 - INFO - separator - CUDA is available in Torch, setting Torch device to CUDA
2024-04-11 11:12:16,299 - INFO - separator - ONNXruntime has CUDAExecutionProvider available, enabling acceleration
2024-04-11 11:12:16,299 - INFO - separator - Loading model Reverb_HQ_By_FoxJoy.onnx...
......
File "\UVR5Tasks.py", line 53, in exec
self.separator.load_model(model_filename=self.model_name)
File "\audio_separator\separator\separator.py", line 639, in load_model
self.model_instance = separator_class(common_config=common_params, arch_config=self.arch_specific_params[model_type])
File "\audio_separator\separator\architectures\mdx_separator.py", line 93, in init
self.load_model()
File "\audio_separator\separator\architectures\mdx_separator.py", line 124, in load_model
self.model_run = onnx2torch.convert(self.model_path)
File ".venv\lib\site-packages\onnx2torch\converter.py", line 72, in convert
onnx_model = safe_shape_inference(onnx_model_or_path)
File ".venv\lib\site-packages\onnx2torch\utils\safe_shape_inference.py", line 46, in safe_shape_inference
return _shape_inference_by_model_path(onnx_model_or_path, output_path=tmp_model_file.name, **kwargs)
File ".venv\lib\site-packages\onnx2torch\utils\safe_shape_inference.py", line 24, in shape_inference_by_model_path
return onnx.load(output_path)
File ".venv\lib\site-packages\onnx_init.py", line 210, in load_model
model = _get_serializer(format, f).deserialize_proto(load_bytes(f), ModelProto())
File ".venv\lib\site-packages\onnx_init.py", line 147, in _load_bytes
with open(f, "rb") as readable:
PermissionError: [Errno 13] Permission denied: '\models\MDX_Net_Models\tmpuxe6y639'
Some body please help me out, thanks a lot.

I align to the update version of uvr-5.6, and now is okay, some files are changed. you may need to revise some code.

Sorry @XeoOuYang I'm not sure what you mean - what code? What was your fix?


Suggestion for Forbidden Lands Support and My Hack Revealed

I noticed that Tokenizer cannot determine diff between PC and NPC with the Forbidden Lands system.
I put a hack in place manually (and probably not in all the places it needs to be, but it works for my immediate purpose).
The sheet for Forbidden Lands have a subtype property that is "npc" is the NPC sheet is chosen, so I updated main.js as shown below.
Any clues as to other places I can/should update it and I'd be glad to submit PR; or if you want to add support for Forbidden Lands good karma awaits! Thanks much!
function tokenizeActor(actor) {
  let sheetType = ["character", "pc"].includes(actor.type) ? "pc" : "npc";
    if(actor.system.subtype?.type == "npc") {
      sheetType = "npc";
  }

  const options = {
    actor: actor,
    name: actor.name,
    type: sheetType,
    disposition: actor.prototypeToken.disposition,
    avatarFilename: getAvatarPath(actor),
    tokenFilename: actor.prototypeToken.texture.src,
    isWildCard: actor.prototypeToken.randomImg,
  };
  launchTokenizer(options, updateActor);
}

Thanks for this, this confused me a little bit, but a fix will be in the next release!


Escape characters with unicode_escape encode

We need to escape characters like \n, \r etc from the source code, otherwise they are parsed as escape characters by ipython and they screw up the executed source code.
This solution is just a proposal, open for discussion.

Changed the escaping to operate line wise instead of block wise, so that the source code maintains its indentation in the generated python script

@elikatsis I updated the comments to reflect the new changes. I think that this is a good enough solution for now for escaping the code, as it maintains the formatting.


Label hover on bar chart

Here are my six labels:
labels: ["Customer Routine Expectations", "Promotional Effectiveness", "NPD Launches", "Inventory and Logistics Deliverables", "S.O.P. / Business Planning", "Add Value to Category"]

It shows the labels correctly under the graph but when hovering over a bar, it shows the wrong label.
Example:
I hover over the first bar, the label should read "Customer Routine Expectations" but instead it says "Promotional Effectiveness". When I hover over the last bar, the label should read "Add Value to Category" but instead says "undefined".

Thank you for this report. Could you please create a JSBIN that include the full code you are using so we can reproduce this issue

http://jsbin.com/cizomexexo/1/
It appears that it only happens when using an object as dataset. Using an array works just fine.


Define PACKAGE and PACKAGE_VERSION before including bfd.h

On ArchLinux at least the bfd.h header errors out early if
PACKAGE or PACKAGE_VERSION have not been set. This patch
makes backward.hpp compile on this platform for me.

Do you mind adding a little comment around the defines to explain what they are used for? because they don't define with any value I fear somebody (likely me) will forget in the future and get rid of it under some cleanup pretext ^^

Sorry for the delay I totally missed the update. Thanks for this!


Solved Issue: Portfolio Website #17 - Created a portfolio website using React

Solved Issue - Portfolio Website #17 : Create a portfolio website using React

update readme

Updated README.md file.

refer to other added project readme for reference

Updated README.md file, please check it.

Done

Is there is any problem in accepting pull request?


remove

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #2

PR #3

PR #4

PR #5

PR #6   👈

This stack of pull requests is managed by Graphite.


androidsrc.dev can not be resolved

Something is wrong, I can't access: https://androidsrc.dev/
And If I ping it I get:
ping: cannot resolve androidsrc.dev: Unknown host

I forgot to renew the domain. I'm honestly hesitant to buy it again, as Google as made noticeable improvements and got a lot more code into cs.android.com . What do you think?

That have sense. I think that as a Readme is good enough. It's true that they improved but you have more information than that. And more when you are not 100% where to start


Integration tests

What
Need to introduce integration tests.
Why
It's really troublesome to test the end behavior of the form/fields. Unit tests are great, but they don't cover the package usage at the required scope.
How.

Prefer Cypress

Roadmap

[ ] Review existing unit tests and get rid of those which can be re-written to integration tests
[ ] Add tests for getErrorMessages functionality in the UI
[x] Add tests for basic interaction with all the fields (touching, changing, serializing and seeing the expected value)

Integration tests re-written to mount the test scenario component only once and reuse it in all the test cases

Field.Group functionality tests were added as integration tests


Add a settings file

Add a settings file that allows the administrators to quickly modify settings.

solved with commit 40e6b23195e79c3ab780eb69bd8d7316e1837e29 / 6ec86efbdc2a3951b2b2a355b122a43de02c6e0b


Issue in Home Screen

An issue in the Home Screen Design and also not a Mobile responsive
Please Assign this issue to solve this bug and make mobile responsive

Hello @chandel-aman
Can this issue be assigned to me for gssoc '24
Regards,
V Meenakshi Iyer


Allow using HIP in BVH benchmark

Only the check for valid backends was incomplete.

I guess HIP wasn't fixed in #392 :( Merging with the "standard" HIP failure.


Diverged metrics in PatchCore: dropping from 0.99 to 0.44 and 0.03 is rather critical?

diverged metrics: dropping from 0.99 to 0.44 and 0.03 is rather critical?
log images: nice :)
Also padim dropped in performance, but not as crazy.
Here's a patchcore result of "good" parts:

this is padim:
DATALOADER:0 TEST RESULTS
{'image_AUROC': 0.7589669823646545,
'image_F1': 0.8787878751754761,
'pixel_AUROC': 0.9781586527824402,
'pixel_F1': 0.22379672527313232}

Originally posted by @sequoiagrove in https://github.com/openvinotoolkit/anomalib/issues/67#issuecomment-1010091154

@sequoiagrove, @blakshma worked on the patchcore results, where he managed to improve the performance to the following:
DATALOADER:0 TEST RESULTS
{'image_AUROC': 0.9524492025375366,
 'image_F1': 0.9551020860671997,
 'pixel_AUROC': 0.9894225597381592,
 'pixel_F1': 0.3562552034854889}

To reproduce the numbers you could use this branch, to be merged to development soon after this PR.
Here are the qualitative results for the ones you shared above. (screw/test/good/009/png)

I get those numbers too now. but I wonder of the computation of the numbers is also wrong, because when I look through the results images, it only detects about 1/4 to 1/2 of the defects in the different categories. The pixel F1 = 0.35 seems to decribe best the actual performance. but I know that it is low due to correctly detected defects dont have to overlap perfectly to still be a good result.

pixel auroc of 0.97 sound like it is good performance, but looking at the masks it is really not useful in a real system, and the auc is a bad metric for quantifying performance.
So I guess I should always look at pixel F1. Think thats about the same as dice, right? I use dice in segmentation tasks.
Too bad this list shows only the unrealistically positive auroc numbers:
https://paperswithcode.com/sota/anomaly-detection-on-mvtec-ad

yeah, AUC is widely used in academia, but usually not a good metric for industrial applications since it could be misleading. Finding the best threshold from the AUC is not so easy even though we implemented adaptive thresholding mechanism. This is the reason why we also added f1 score to our evaluations.
Regarding always looking at the pixel f1 score for evaluation, there is room there for improvement. We haven't optimise our heatmaps from which the predicted masks are generated. Once we do, I agree, pixel f1 would become the standard metric to evaluate the performance.


KAFKA-15867: Should ConsumerNetworkThread wrap the exception and notify the polling thread?

Changes:

Added backgroundEventHandler to ConsumerNetworkThread to handle unexpected exception.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@philipnee, PTAL. Thanks in advance

@kirktrue, I will

Looks like there are some conflicts to resolve as well. Thanks!


Addition: Pull down to refresh in nearby activity

PR for #264
Pull down to refresh feature added in nearby activity.
SwipeRefreshLayout used

Codecov Report

Merging #1164 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #1164      +/-   ##
=========================================
- Coverage    3.96%   3.95%   -0.01%
=========================================
  Files         123     123
  Lines        5604    5610       +6
  Branches      542     542
=========================================
  Hits          222     222
- Misses       5367    5373       +6
  Partials       15      15

Impacted Files
Coverage Δ

...ava/fr/free/nrw/commons/nearby/NearbyActivity.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Sure. I will make the changes and commit ASAP.

Please review the changes

@97balakrishnan Swipe to refresh works fine. The list updates even if the location has not changed.
@misaochan @neslihanturan Is that behaviour fine. If yes, we can go ahead and merge this. Have tested it on a real device.

I just noticed that it exactly replicates the functionality of the refresh button.
Going ahead and merging it. @97balakrishnan congrats for your first contribution. :)

Thanks a lot. My pleasure. I'll make the changes to prevent it from refreshing if the locations not changed ASAP. Thanks again


Fix pointer profile inspector

Overview
This PR has two changes:

The Pointers profile used ReordableList to easily draw the inspector which is awesome...but when drawn as a subprofile, the entire inspector is reallocated every draw. Thus there is no way to save state between renders resulting in the bug #5004 . This PR draws the list manually with our own add/delete buttons similar to speech profile and other similar list inspectors in MRTK

A lot of old code still uses BeginHorizontal/Vertical which is both problematic and harder to read. Switching to EditorGUILayout.VerticalScope() {} clearly defines what is being draw in this horizontal/vertical and allows valid clean up if the logic returns early

The PR looks more deadly than it is. It's largely because of all the tab formating with the new using() { }
Changes

Fixes: #5004

Verification
Navigated all pages and browed basic usage
All tests pass

As a reviewer, it is possible to check out this change locally by using the following
commands (substituting {PR_ID} with the ID of this pull request):
git fetch origin pull/{PR_ID}/head:name_of_local_branch
git checkout name_of_local_branch

@Troy-Ferrel, do you think we should ban usage of BeginHorizontal/indentLevel to reduce mismatched inspector bugs going forward?

@Troy-Ferrell, do you think we should ban usage of BeginHorizontal/indentLevel to reduce mismatched inspector bugs going forward?

Yes, I would say in general. There is one potential edge case. One semi negative thing with the scopes is that you know force variable scope. Generally you can just move things out to be defined top of function or whatever. But of course for some code areas....it can be a jungle to move around with your UI scope definition...but this should be rare


⚠ Bofrost.at has degraded performance

In eebf9d7, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1904 ms

Resolved: Bofrost.at performance has improved in ecca567.


Review 3: Dashboard.jsx

Please review the Dashboard, linked here
Use these guidelines:

Architecture
Design
JS
React

DUE: 9/30 11:30AM

Architecture OK
Design -- 01 - Does look repeatitive, but not sure if there is a way to refactor in a way that would keep the years/data separated? if not this is good, organized and readable
JS and ESLint -- 08 - Could have a comment block at the top detailing what this file does
React OK

Design-01: There are multiple sections in the chartConfigs for 4, 8, and 12 years that could be refactored into a single function to create chart configurations dynamically, reducing code duplication.
Design-05: Some comments could be clearer. For instance, comments like "Use the real financial data" could be more descriptive regarding the expected structure of financialData.
Design-08: The repeated definition of chart configurations for different years indicates a need for DRY principles. Consider creating a function to generate these configurations based on parameters.

REACT-01: Components should be simple.
Should have smaller components, each handling specific aspects of the dashboard ( separate components for each chart configuration).

A block comment at the top of the main function would be helpful to explain what the function actually does.
Otherwise looks good and readable, could refactor to avoid redundancy (although this is better to keep track and debug)

Design-01: Chart configurations do look redundant at first glance, but it's still very readable

Maybe adding more descriptive error handling for staticfinancials.find()

Outcome of review Meeting
New issues
New checklist items


Feat: Kusion server supports async execution of generate/preview/apply/destroy

What would you like to be added?
Asynchronous executions for generate/preview/apply/destroy in Kusion server
Why is this needed?
The executions might take some time and this should not block the user

Dup of #1336


Capacitor 5

Are you going to update the plugin to support Capacitor 5? Capacitor 5 should be released soon.
https://capacitorjs.com/docs/next/updating/plugins/5-0

Yes, when it reaches RC.

https://ionic.io/blog/announcing-capacitor-5
PR created

This week or next.

Just released.


Yi Home 1080p RFUS 12.0.35 reboots over and over

The camera model and firmware line up for the y291ga file. Add the camera in the Yi app, and it works fine. Put the hack on a 16G SD card, the folder changes to Factory.done so it looks like the hack took. But it just boots over and over again with the SD card left in, and you can't see the IP address of the camera on the network or see the camera in the Yi app. If you take the SD card out, the camera goes back to working the same as if the hack was never applied, that is I can see the camera in the Yi app, you can ping the IP address. I followed the wiki to add the sdwifi.tar.gz files in case it was just not getting back on the network, but again, it just reboots over and over as long as the SD card is in. I have tried one other brand of SD card, exactly the same things happens. Any ideas? Thx

More-with the SD card left in, can't ping the IP address of the camera, does not show up when I try to add it in Agent UI for example, with the card left in the camera reboots over and over and does not work in the Yi app and can't be seen on network. Pulling card out lets it be seen again in the Yi app, but you can't ping the IP address or add it in Agent UI, appears like hack never applied. I have tried formatting the SD card using the camera app.

Please, check this issue:
https://github.com/roleoroleo/yi-hack-Allwinner-v2/issues/540#issuecomment-1341109470

Thanks, that did seem to fix it, although I didn't think so at first as it rebooted several times for a few minutes. It would ping, then not ping, then finally settled out working ok.

If the cam continues to reboot, check the faq page in the wiki: snapshots, swap, etc...


Route Animations Extremely slow (1-2 seconds)

I am getting incredible slowness in a data entry app. Averaging 1-2 seconds route load on an iPhone6. We have timed it as slow as 5 seconds for a single route change, same device. These route changes are finding and displaying 7-10 records.
Everything about the app is extremely fast and snappy, feels native, other then route changes. All subscriptions are done at app start so that is not an issue (we have offline support via GroundDB).
Looking at 2098 records totaling 316KB so this should not be a memory issue. We tested with GroundDB off and local storage clean so that also is not an issue. As far as I can tell this is specifically related to route animation, possibly issue #4. Anyone have any ideas?

Actually this may be a pure local memory issue, in chrome window.performance.memory.totalJSHeapSize is returning 33100000.

This is a memory issue, apologies.


PA, USA: Data is incorrect, likely reversed deaths and number of cases

The PA (Pennsylvania) data appears to be incorrect now.   It's now showing a very low number for number of cases (e.g. about 12).    In clicking through to the data source for the scraper, I'm guessing that the scraper (or website) reversed the columns for number of cases and number of deaths.

✅ Data scraped!
   - 0 cities
   - 1 states
   - 67 counties
   - 0 countries
ℹ  Total counts (tracked cases, may contain duplicates):
   - 1703 cases
   - 16441 tested
   - 0 recovered
   - 32 deaths
   - 0 active

can't reproduce locally?

Thanks for the quick response !
This is the PA,USA data object at https://coronadatascraper.com/#timeseries-byLocation.json
Which shows the discrepancy I'm describing.   Is that helpful ?

Yeah I saw the same, that looks totally wrong...

I just tested this locally (yarn start --location "PA, USA"), and logged the values the scraper was getting.  Output:
{ county: 'Adams County', cases: 7, deaths: 0 }
{ county: 'Allegheny County', cases: 133, deaths: 2 }
{ county: 'Armstrong County', cases: 1, deaths: 0 }
... [snip] ...
{ county: 'Wayne County', cases: 6, deaths: 0 }
{ county: 'Westmoreland County', cases: 24, deaths: 0 }
{ county: 'York County', cases: 21, deaths: 0 }

Those numbers match the data currently shown on https://www.health.pa.gov/topics/disease/coronavirus/Pages/Cases.aspx.
In short, it looks ok to me, based on what's currently there.

Interesting, they also have an Archive page which lists several dates, and matches the 6/7/11 numbers @cburkins pointed out in https://github.com/lazd/coronadatascraper/issues/409#issuecomment-604758785:
https://www.health.pa.gov/topics/disease/coronavirus/Pages/Archives.aspx.

Thanks all for looking at this.   I think most of the PA county-level data is correct.  It seems to be the roll-up to PA sum data that feels off.

PA data is out of whack again due to the page https://www.health.pa.gov/topics/disease/coronavirus/Pages/Cases.aspx now including some age ranges with percents, which are getting reported in the data:

Age Range
Percent of Cases

...
...

50-64
28%

65+
18%

data.json:
  {
    "state": "PA",
    "country": "USA",
    "aggregate": "county",
    "url": "https://www.health.pa.gov/topics/disease/coronavirus/Pages/Cases.aspx",
    "county": "65+ County",
    "cases": 18,
    "deaths": 18,
    "rating": 0.47058823529411764
  },

This is a change as of today to the page layout, I'll work on this now.

As a PA resident, many thanks to you!

On Mar 27, 2020, at 7:25 PM, JZ<EMAIL_ADDRESS>wrote:

PA data is out of whack again due to the page https://www.health.pa.gov/topics/disease/coronavirus/Pages/Cases.aspx now including some age ranges with percents, which are getting reported in the data:
Age Range	Percent of Cases
...	...
50-64	28%
65+	18%
data.json:
{
"state": "PA",
"country": "USA",
"aggregate": "county",
"url": "https://www.health.pa.gov/topics/disease/coronavirus/Pages/Cases.aspx",
"county": "65+ County",
"cases": 18,
"deaths": 18,
"rating": 0.47058823529411764
},
This is a change as of today to the page layout, I'll work on this now.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@jzohrab @cburkins was this fixed by #452? Check the data we reported last night and close this issue if it's looking proper.

I'm not sure if this is the same issue but the "like JHU" data also appears to have figures that are too low for the past week or so.
,,PA,USA,41.12951166463159,-77.60961308037935,12801989,https://www.health.pa.gov/topics/disease/coronavirus/Pages/Cases.aspx,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,12,16,,41,47,63,71,96,133,185,268,2,2,6,7,11,16,22

Hmm, didn't pull the repo and deploy myself, as I'm leveraging the data available on https://coronadatascraper.com/#timeseries-byLocation.json
Looking at that data, still shows incorrect values....    Perhaps it will be correct tomorrow when it pulls the new data for today ?

I fixed this last night in https://github.com/lazd/coronadatascraper/commit/392290719e7cb414f890b6a637fb29fa8327ba67, it looks good now

Agreed, PA data looks good now !


Scheduler

Implement scheduler to call get_predictions method to call every 6-hours.
Estimate of hours of work: 5

Closed with successful merge.


Add documentation on How to add Zaraz to a web app/website that has been deployed to CF Pages

Product
Zaraz (or maybe Pages?)
Subject Matter
Adding Zaraz to a web app/website that has been deployed to CF Pages
Content Location
A new section called How To? Just like how we have a similar section for Pages docs
If a new section is a bit too much, we could have it under Advanced Options
Additional information
I did the following:

Set up Proxying (Orange cloud) for my pages website that has a custom domain attached to it. I know this is not relevant to Zaraz, but is an important precursor that has a significant impact on the UX provided by Zaraz.
Resolved SSL issues (TOO_MANY_REDIRECTS). I had to google to figure this out and stumbled upon this https://support.cloudflare.com/hc/en-us/articles/115000219871-Troubleshooting-redirect-loop-errors-

A lot of users will face this, especially if they are migrating from services like Netlify, Vercel, etc to CF Pages.
While having your domain proxied through CF is not mandatory, it is most certainly a huge plus to have it already setup and allows quick onboarding within Zaraz. As a frontend developer, I would want to avoid spending too much time figuring out how to get things to work and this seems like a common scenario that I'd run into if I work on Static/SPA/Server Rendered websites.

Please let me know if I can work on coming up with a short draft document and post it here, or if you prefer I can directly submit a PR for someone from the team to review.

Please let me know if I can work on coming up with a short draft document and post it here, or if you prefer I can directly submit a PR for someone from the team to review.

Hi @omarmosid , would like to review the PR if you can submit one :)

I'll also ping the Zaraz team and see if there's anything we should be aware of for cases like this one

Thank you for your response @deadlypants1973 @marciocloudflare
Will try and see if I can submit a PR by tomorrow
Will be my first contribution here, please feel free to assign this issue to me

We actually assign issues to the writer that works with that product. As this is a Zaraz issue, that will be me. I've also spoken with the Zaraz PM, and we'll be looking into creating something with the Pages PM regarding this. You can still open up a PR if you want or wait until we have a solution in-house :)


Push nuget package to github packages

closed by using the cake.recipe solution.

closed by using the cake.recipe solution.


When importing components and passing them to the h() function, I want to receive type hints.

What problem does this feature solve?

As shown in the image, SvgIcon is written in template form and does not receive type hints when using the h function.
What does the proposed solution look like?
null

Could you provide a complete example?

I've taken a closer look and there are indeed type hints, but I want the props that a component expects to accept, as well as related events, to be prioritized at the top when triggering suggestions in VSCode, rather than being scattered.

This is not related to language tools, it's the feature of typescript itself.

Perhaps you can use jsx.


#14977: conv config to use higher cores.

Ticket
#14977
Problem description
Provide context for the problem.
What's changed
Describe the approach used to solve the problem.
Summarize the changes made and its impact.
Checklist

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] (For models and ops writers) Full new models tests passes
[ ] New/Existing tests provide coverage for changes

Sheet 2 is updated sheet here. https://docs.google.com/spreadsheets/d/1RG01_0QWPFAks9XFVw2StpPr8YSZXvDjf6GBv_-eKb0/edit?gid=208231282#gid=208231282


test cordova

Hi @UniDevCorp, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@UniDevCorp, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Cleaning up old pull requests - sorry for our lack of a response here, but in the future please add a description for your pull request! If you see a change that still needs to be made, we'd love to get another PR from you. Thanks,


Prefer operation name over field name

This updates the logic for determining the operation name displayed in the left column to prefer the API-consumer-provided operation name over the top-level field name. It will still fall back to the top-level field name when no operation name is provided. The use-case here is that, in practice, GraphQL types are often organized into a tree structure where the top-level field is not very descriptive as to what is actually being queried (e.g., the top level field may be something like organization for every query). For mutations, the consumer-provided name will generally be either more descriptive or the same as the mutation field name. In any case, the users of this extension are likely developers that defined the operation names and would be more interested in seeing those names.

@warrenday the action passes on my fork: https://github.com/jamescdavis/graphql-network-inspector/runs/3298839435?check_suite_focus=true
You'll need to update https://github.com/warrenday/graphql-network-inspector/blob/d330d18245b429320cda8906584fc64e3ce9c3cd/.github/workflows/test.yml#L3
to at least
on: [push, pull_request]

for it to trigger for PRs from forks.
But might be better to use something like:
on:
  pull_request:
  push:
    # filtering branches here prevents duplicate builds from pull_request and push
    branches:
      - master
      - 'v*'
    # always run CI for tags
    tags:
      - '*'

@totolicious this has been released in 2.1.1


[InDataSet]

Suggestion to enhance the compiler / "build problems":
When you want to make controls/actions invisible based on some logic, you need to use a Boolean variable. If you want to change the text style, you need to use a text variable. All those variables would be assigned to the appropriate property. This only works when you add [InDataSet] to the variable declaration, which can easily be forgotten.
It might make sense to have the compiler test for any variables used in those property declarations that do not have the flag set. Not sure how difficult it is, but it surely would help.

We are actually already doing it in a lot of cases. If you find scenarios that don't work please let us know.

Specific scenario is that I created a new page in the extension and created a variable controlling the property "StyleExpr".
Here is a test page - this compiles and doesn't show any errors, but you will receive runtime error when executing the page that "NameStrong" not found. Once you add [InDataSet] to variable declaration, it works. Would be great if this would be caught on build time.
`
page 70000000 TestPage
{
PageType = ListPart;
SourceTable = Integer;
layout
{
    area(content)
    {
        group(GroupName)
        {
            field(Name;Number)
            {
                StyleExpr=NameStrong;
            }
        }
    }
}

actions
{
    area(processing)
    {
        action(ActionName)
        {
            trigger OnAction();
            begin
            end;
        }
    }
}

trigger OnAfterGetRecord();
begin
  if Number mod 2 = 0 then
    NameStrong := 'Strong'
  else
    NameStrong := 'Standard';
end;

var
    NameStrong : Text;

}
`

Thanks, we'll have a look.


context  biasing issue

I am  trying to use  the context  biasing feature. I created  a text file context.txt and passed  it to decoder_main like  below:
context_path=context/context.txt
./build/bin/decoder_main
--chunk_size -1
--wav_path $wav_path
--model_path $model_dir/final.zip
--context_path $context_path
--context_score 3
--unit_path $model_dir/units.txt  2>&1 | tee log.txt
cat  context.txt
residence
However, while  running, I get the below messages:
I1118 06:06:01.211375 27316 params.h:169] Reading context context/context.txt
I1118 06:06:01.211447 27316 context_graph.cc:45] Contexts count size: 1
I1118 06:06:01.211453 27316 context_graph.cc:56] JK....context=residence
W1118 06:06:01.211465 27316 string.cc:143] r is oov.
W1118 06:06:01.211470 27316 string.cc:143] e is oov.
W1118 06:06:01.211474 27316 string.cc:143] s is oov.
W1118 06:06:01.211478 27316 string.cc:143] i is oov.
W1118 06:06:01.211481 27316 string.cc:143] d is oov.
W1118 06:06:01.211483 27316 string.cc:143] e is oov.
W1118 06:06:01.211486 27316 string.cc:143] n is oov.
W1118 06:06:01.211489 27316 string.cc:143] c is oov.
W1118 06:06:01.211491 27316 string.cc:143] e is oov.
W1118 06:06:01.211493 27316 context_graph.cc:59] Ignore unknown word found during compilation.
I1118 06:06:01.246717 27321 decoder_main.cc:54] num frames 724
I1118 06:06:01.246994 27321 asr_decoder.cc:104] Required<PHONE_NUMBER> get 724
why is it splitting into chars ?
.

OK, I think  , I have  to specify the context as  a word same as in units.txt. After  changing it to RESIDENCE, the OOV disappears. Still  trying to figure out  how to make use of this  feature.


Handle (ignore) partial uploads on downsampling and apply retention cycles

AC:

Meta files sync should ignore not-complete blocks for downsampling and retention cycle.
Removal of malformed block if any is ONLY on compaction cycle.

We have nice concurrent logic here: https://github.com/improbable-eng/thanos/blob/10f84a7d7f06813fda97e17d609a9969fcda037f/pkg/compact/compact.go#L169
We did not apply it here: https://github.com/improbable-eng/thanos/blob/10f84a7d7f06813fda97e17d609a9969fcda037f/cmd/thanos/downsample.go#L145
And not on retention: https://github.com/improbable-eng/thanos/blob/1d582af96b2cd412ade46dcfa07e6d40ffb3c176/pkg/compact/retention.go#L16

It fixes compactor crashes like
level=error ts=2019-07-15T21:09:56.108249354Z caller=main.go:182 msg="running command failed" err="error executing compaction: first pass of downsampling failed: retrieve bucket block metas: get meta for block 01DFVPYR64AGDW009PF99N2YFY: The specified key does not exist."

This is because when doing sync and sidecar uploading block we might hit block with no meta.json.

Hey @bwplotka I can help with this.

oh yes please @lx223
Essentially we have 3 different sync implementation. I think we should have nice one meta syncer everyone can reuse: compactor for compating/downsampling/retention but also store gateway.

Any progress @lx223 ?

sorry for the delay; have been busy with work. should have something up for review soon.

PR: https://github.com/thanos-io/thanos/pull/1394 PTAL

Still valid I think, ref: https://cloud-native.slack.com/archives/CK5RSSC10/p1572453579422500

It's getting quite important to get this in, another point of failure:

https://github.com/thanos-io/thanos/issues/1655#issuecomment-559068163
FIxes like https://github.com/thanos-io/thanos/pull/1807

https://github.com/thanos-io/thanos/pull/1394 was our first attempt and can be used as a base (: Will get into this in free time, unless there are other volunteers (:


ModuleNotFoundError: No module named 'ruamel'

Environment:

NNI version: 1.9.0
NNI mode (local|remote|pai): Local
Client OS: Ubuntu
Server OS (for remote mode only): Local
Python version: 3.6.0
PyTorch/TensorFlow version: tensorflow==2.3.0
Is conda/virtualenv/venv used?: conda
Is running in Docker?:Yes

Log message:
   /opt/conda/lib/python3.6/site-packages/nni/package_utils.py in <module>
          8 from pathlib import Path
          9 import importlib
    ---> 10 import ruamel.yaml as yaml
         11
         12 from .constants import BuiltinAlgorithms

    ModuleNotFoundError: No module named 'ruamel'

What issue meet, what's expected?:
It seems the conda install ruamel is ruamel_yaml, I expect that if the nni running in docker+conda environment could identify the ruamel path
How to reproduce it?:
Additional information:

change the 'import ruamel.yaml as yaml' to 'import ruamel_yaml as yaml' it works for me

change the 'import ruamel.yaml as yaml' to 'import ruamel_yaml as yaml' it works for me

change the 'import ruamel.yaml as yaml' to 'import ruamel_yaml as yaml' it works for me

Thanks for your solution, maybe @m4rkl1u can try his method.

change the 'import ruamel.yaml as yaml' to 'import ruamel_yaml as yaml' it works for me

Thanks for your solution, maybe @m4rkl1u can try his method.

met this error in Windows :(

windows 10
python 3.8
could install ruamel.yaml to solve this:

pip install --ignore-installed ruamel.yaml

To avoid this issue, NNI substitutes ruamel.yaml with PyYAML in pr #3702, which will be released in v2.3.


demo: snakemake scatter-gather minimal example

Create a minimal scatter-gather Snakemake example to be able to test properly multiple functionalities like DAG complexity estimation and the Snakemake workflow engine.
The goal of the implemented workflow is that multiple (at least two) rules/steps can run in parallel. In the following illustration B and C can run in parallel and the generated outputs feed D to calculate the final result.

We can use the r-d-helloworld repo and create a reana-snakemake-scatter-gather.yaml file with its corresponding Snakefile.
More information about scatter-gather Snakemake workflows can be found here: https://snakemake.readthedocs.io/en/stable/snakefiles/rules.html#defining-scatter-gather-processes.
Snakemake also allows generating DAG visualizations via --dag. This way we can make sure that we have a scatter-gather workflow and also it's handy to enrich the demo documentation.

In addition to the CMS example, and due to its complexity and issues when running it in the REANA cluster (Snakemake Workflow Engine), maybe we can start from a minimal scatter-gather helloworld to verify that jobs can run in parallel with no issues? As it's described in this issue.
What do you think @mariaFernando? You can also try to execute it in the cluster, check logs, etc. in the same way as one can run reana-snakemake.yaml with no issues.

As part of this task, apart from making the cms-h4l example work in parallel, a dummy scatter-gather example was implemented. Maybe this can be stored somewhere for future investigations related to DAG execution in snakemake.


NanoDet to TFLite Conversion

HI Is there any support to convert my custom nanodet trained model to TFLite?

This repository doesn't provide it


Fix wrong info about empty toleration key (#47929)

Description
Updated information about empty toleration key in taint-and-toleration.md to match the API specification.

Issue

Closes: #47929

/sig scheduling docs

/lgtm

Thank you providing the implementation code to refer to
/approve


When epsg.io is accessed via https, the map service cannot be used with the latest Chrome

Mixed Content: The page at 'https://epsg.io/map#srs=3134' was loaded over HTTPS, but requested an insecure script 'http://maps.google.com/maps/api/js?v=3.3&sensor=false'. This request has been blocked; the content must be served over HTTPS.
Uncaught ReferenceError: google is not defined

Regression on latest deploy. All resources in /map and /transcribe must be loaded via https.
@petrsloup could you please fix and redeploy?

@klokan Done, please close this ticket after CDN reset.

CDN flushed. Closing.


Adding Security as one of the approvers for new software

Adding Security as the approver for new software

Merging after 👍  from Tommy O'Donnell


Mailable class seems to over-write same class objects when build() is called.

Laravel Version: 5.6.39
PHP Version: 7.3.1
Database Driver & Version: n/a

Description:
Mailable class seems to over-write same class objects when build() is called.
Steps To Reproduce:
class Foo extends Mailable {
// ...
public $old;
public $new;

public function __construct(Foo $old, Foo $new) {
$this->old = $old;
$this->new = $new;
}
public function build() {
  $this->old // new
  $this->new // new
}
)

Please provide a reproducible example of your problem.

Heya, unfortunately we don't support this version anymore. Please check out our support policy on which versions we are currently supporting. Can you please try to upgrade to the latest version and see if your problem persists? If so feel free to reply and we'll try to have a look.


RFC: Add HLO for Tan(x)

Request description
We would like to propose adding an HLO for computing the tangent "Tan(x) := Sin(x)/Cos(x)" for numeric types.
Adding an HLO for Tan(x) has several advantages.
Pros:

Many backends or system math libraries, including CUDA, XLA:TPU, libc etc., contain optimized implementations of Tan(x) that are not simply computing Sin(x)/Cos(x).  Mapping Sin(x)/Cos(x) to such primitives inherently relies on fast-math semantics and implicit fusing in the backend compiler.
Using an optimized approximations for Tan(x) improves both accuracy and performance/throughput, since the common steps of
a) range reduction,
b) polynomial approximation,
c) special case handling,
need to be computed only once.
Having a Tan(x) HLO, makes the IR slightly more compact.

Cons:

This adds another HLO that must be implemented by all consumers/transforms of HLO.

TanOP is added to StableHLO opset at https://github.com/openxla/stablehlo/pull/2177


Initialization last convolution layer as zeros

I have a problem about your project.
If you initialize the last layer as zeros, the gradients will also be zeros for all layers. Then the model cannot be trained.
Do i understand correctly?

I have a problem about your project.
If you initialize the last layer as zeros, the gradients will also be zeros for all layers. Then the model cannot be trained.
Do i understand correctly?

Hi, I understand what you mean.
When the last layer is set as zeros, the gradients before the last layer will be zero. However, the gradient for the last layer is not zero, so the last layer will be optimized firstly. Other layers will be optimized later.


Link these new materials to instructors

The new folder with the updated Galaxy Zoo materials is here. This should be linked when it says instructor's start here on the classroom.zooniverse page for galaxy zoo instead of the old google folder. This isn't necessarily the most final version, but it's a working version for Fall 2019.
https://drive.google.com/drive/u/1/folders/1Kr3MxJoPxcwOlJN2FMn-gbjNNneOqX5i

@mollysimon I've updated the link with the URL provided. Thanks!