Add missing log levels

I'd like to be able to default to TraceLevel when a tracing feature is enabled in my crate.

Our current assumptions:

Debug and trace by definition are below the threshold for normal operations and we should encourage best practices of defaults being for normal operations
Abnormal cases where debug and trace become normal operations that people can workaround it the above by providing their own LogLevel impl

Is there a reason we should re-think these assumptions?  Otherwise, I lean to closing this with the specified workaround.

This isn't changing the default, it's giving developers the freedom to choose what works for them. I gave you my use case, I want to be able to do this:
#[cfg(not(feature = "trace"))]
type DefaultLevel = clap_verbosity_flag::WarnLevel;
#[cfg(feature = "trace")]
type DefaultLevel = clap_verbosity_flag::TraceLevel;

Your reply is essentially telling me, "I don't like your choice so eff off." Very frustrating.
I understand that I can just make my own TraceLevel struct, but that doesn't make any sense. The library integrates with the log crate, so it should mirror the log crate's levels. And again, the default is error and that's fine. I'm simply asking for the option to choose something else without it being a pain.
Let me put it another way: by your reasoning, if I'm vegetarian and I think being vegetarian is a "best practice", then I'll tell anyone who wants to buy meat to eff off and raise their own cattle. Nonsense.

What's frustrating here is that I get the sense there's nothing I can say that will change your mind. Your reply presents an option to argue against something that clearly isn't refutable. Obviously "Debug and trace by definition are below the threshold for normal operations" so the reply is an insincere pretense of collaboration and that really irks me.
The actual question here is should devs be able to make their own choices? and the answer "no" is insulting.  Making everyone suffer to get the behavior they want because you don't like it is unacceptable.

One option would be to make them doc(hidden).

Apologies for getting pissed off yet again, but I don't think I've EVER had an interaction with you that isn't immediately met with rebuttal/rejection/confrontation. It's maddening.

What's frustrating here is that I get the sense there's nothing I can say that will change your mind. Your reply presents an option to argue against something that clearly isn't refutable.

I gave the base assumptions and opened a dialog for re-evaluating them.   Instead of a good-faith dialog, I am yet again being met with hostility at accepting your contributions at face value.  This type of dialog should be happening in an issue but I let us past here hoping to smooth things out.
This is your warning: if you can't interact with others without hostility, you will be banned from this and related Orgs.  Seeking better understanding is not a hostile act that deserves hostility being returned but is an expected part of being a maintainer.

The actual question here is should devs be able to make their own choices? and the answer "no" is insulting.  Making everyone suffer to get the behavior they want because you don't like it is unacceptable.

The answer is not "no" but "its already supported by implementing LogLevel".  This follows the principle of API design of make the right / safe choice easy while making the exception cases possible.  What I'm trying to understand is why does the impl need to be in here, rather than in your crate.  Bringing up use cases like having a feature flag to control the default is very relevant information that was left out of the PR.  It would be of interest to include more of that use case, how representative that is, and, if its rare, any are extenuating circumstances for why these other impls should be shipped by default.

What I'm trying to understand is why does the impl need to be in here, rather than in your crate.

Simply because I don't want to have to copy that impl in all of my crates.

accepting your contributions at face value

No, I'm asking for two things:

Acknowledging that my request is reasonable. I'm always happy to change the implementation or write code in a way that makes the maintainer happy, but a baseline for collaboration is acknowledging that somebody else needs something you don't.
Compromise: for example, making the structs doc(hidden) is a good path forward. It meets my need for not having to duplicate code everywhere and it meets your need for making it more difficult to go against best practices.

Bringing up use cases like having a feature flag to control the default is very relevant information that was left out of the PR.

Lol no? I'll quote myself: "I'd like to be able to default to TraceLevel when a tracing feature is enabled in my crate."

It would be of interest to include more of that use case, how representative that is, and, if its rare, any are extenuating circumstances for why these other impls should be shipped by default.

This is once again disingenuous because a data driven approach doesn't make sense when the request is as dumb as "plz mirror the log crate's levels so I don't have to duplicate code."

A note: you're the only person I've had issues with like this in what's now going to be almost a decade of being on GitHub.

This follows the principle of API design of make the right / safe choice easy while making the exception cases possible.

This is the part I fundamentally don't understand. Typically one would describe the difference between a high level API and low level API like this: you write low level APIs that are difficult to use correctly but afford complete control (in this case implementing LogLevel) and then you write the common use case high level APIs that are easy to use on top of the low level ones (in this case *Level structs).
Ok, but why do people split the API like this instead of only providing the most flexible API?

Performance: high level APIs typically make fewer assumptions (to keep their use simple) and thus must put in extra work to bring the program into a known state. Thus, low level APIs might be necessary to help devs meet performance targets.
Maintenance burden: trying to provide all the possible high level use cases might be too difficult, so you only provide the common ones and tell people to use the low level API for highly specific needs.
*Convenience/hiding complexity: you might be able to provide high level APIs with no performance loss that meet a common need. The goal is just to hide all the low level boiler plate for the common case.
Changing implementation details: if the low-level API exists but can't be used, then typically the high level API serves as an abstraction barrier to enable changing the low level APIs indiscriminately.
???

In this case, there's nothing performance related and there isn't a maintenance burden (maybe if this was the stdlib you'd need a bit more rational, but the fact that there are already similar APIs for the other log levels should make this a pretty easy argument). There also isn't an issue around getting stuck with an implementation you don't like.
*I'm asking for the convenience and minimal complexity of using a high level API.
I believe you're saying one of the reasons people perform a low/high level API split is because the high level API is supposed to be endorsed by the maintainer while the low level API is the "you're on your own because it's a bad idea" path. I very strongly disagree with this take.
If I'm understanding your reasoning correctly, then again I feel like there's nothing I can do to change your mind, so what's the point? My view is that if something is simple to implement, performant, has no maintenance burden, and is something people want, then it almost always makes sense to implement it. The burden of proof should be on "why not?" and "because I don't want to let people use a default I think is bad for the ecosystem" to be valid reasoning.
Disagreement is fine, but usually people will try to compromise to make progress. Your original reply can be destructed as saying the following:

These are my assumptions.
I made a decision using those assumptions.
Unless you can invalidate my assumptions, I'm sticking with my decision.

How am I supposed to respond? Of course if this was our first interaction, I would elaborate and try to explain my side of things assuming you'd want to help me make progress, but I consistently get these ultimatums from you that leave no room for compromise. What am I supposed to do?

Hey, @epage I saw this got a little heated above, and while I don't want to stir that up again, I'd like to throw a use case into the mix. If you'd prefer me to open another issue rather than continuing this one, or comment in #95 instead, I'm happy to do that.
TL;DR: This got a little long while writing, but I'm not sure what to cut out:

I'd find the extra log levels useful, especially during prototyping and for situations where for a small amount of time setting the default level is an easier approach to debug some  problem at a more verbose default log level.
Not doing this has caused confusing fragmentation that seems worse than the doing it

During prototyping a cli app, it would be nice and let me fall into the pit of success to have a default level of debug available to me. This would make it easy for me to have http requests show up in my logs and various things like that. Once I'm done prototyping this can certainly be switched back to the default.
If I'm writing a few different CLIs for various things, this additional boilerplate code to set a default that is not available seems heavy. It ends up getting duplicated across a few places, and it's effectively throw away code that I want to delete when it's no longer in use. But I also want the ability to turn that back on if needs be.
So given these concerns:

wanting a simple one line setup while prototyping to avoid writing much code for simple things
wanting the ability to change this simply in a symmetric way that aligns with changing from ERROR to INFO as the default
not wanting to have to dig into the implementation of this to work out which parts to implement

I come to the same conclusion that including the other levels is the right thing based on those assumptions.
Right now there are 3 similarly named crates. The changes aren't documented, but I think they're:

clap-verbosity-flag this lib
clap-verbosity a fork which adds serde support
clap-verbosity-flag2 a fork which adds the extra levels

As a consumer looking to simplify a verbosity flag in a cli app, this is a confusing place to be in. I want both of those extra features, but I also want to generally use software which I know will get regularly maintained rather than being a single issue fork.
I think much of what I wrote seems to align with the arguments that @SUPERCILEX was making here.

This follows the principle of API design of make the right / safe choice easy while making the exception cases possible

I think this way to define how an API should choose features has some problems, as it overindexes on what is "correct". I don't think there is a correct universally accepted log level that's most useful for all use cases. For some use cases, that level is DEBUG, for some it's ERROR. I don't particularly know any specific use cases where logging at a TRACE level by default makes sense, but I can see that it's reasonable to want that.
Here, there seems like there's a reasonable default (ERROR) that aligns with a default that's used in many logging frameworks, and that works well enough, but not providing the other levels seems just odd and the sort of thing that only has downside.
Perhaps there's a specific use case that you're thinking of that's unstated here where defaulting the verbosity flag level to DEBUG / TRACE would cause known issues? I wonder if you could expand on those a bit more, because those seem like the more theoretical problems to me (but it's likely I don't have the same perspective as yours, so I'm seeking to understand yours a bit more here too).


Update TADAR5.Rmd

I made all figure the first or only object in their code chunk. This should allow all of them to automatically display in the html document. If that does not work, I've got one more idea to try.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 42.25%.  Consider uploading reports for the commit 06681ff to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #414      +/-   ##
===========================================
+ Coverage    42.16%   42.25%   +0.09%
===========================================
  Files           14       14
  Lines         3323     3323
===========================================
+ Hits          1401     1404       +3
+ Misses        1922     1919       -3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Handle multiple namespaces in mock server

it is not possible to test different status messages for DALC using our mock server because it does not differentiate namespaces while creating the mock DALC: https://github.com/rollkit/rollkit/blob/main/da/celestia/mock/server.go#L47
This means, all namespace data gets stored into a single key-value store and querying for different namespaces would result in the same data.
We need to extend the mock server to create one mock DALC for each namespace.

Related: #829

Duplicate of https://github.com/rollkit/go-da/issues/94


Question on experiment setting

Thanks for the great work!
I have a question regarding the experiment setting. As pred is trained and tested only on text provided by ext, does it mean only the original test data is fed into pred for both training and testing (since supp and ext only extract rationales for original test data)? By original test data, I mean the test set of supp.

Test data is never fed into the pred model while training. The way we train it is 1) Train the supp model training data and then extract rationales for each training data example and 2) Use these rationales as input to pred model and train to predict the final prediction.
At test time, we simply use the supp+ext to extract the rationale for that test point and then feed it to the pred model to get the final prediction.

Thanks for your reply, it's really helpful!
I got another question about the model. I wonder are supp and pred should be the same black box model? Your code seems they are same, but in your paper talk, you use 'black box model' for saliency scorer, 'black box model 2' for classifier, it seems they are different.

You can use any classification model for supp and pred and they can be different. They can also be of same type but have different parameters (in our case, we use BERT for both supp and pred but they don't share parameters; the BERT trained for supp is independent of the BERT trained for pred). Hence we use "black box model" and "black box model 2" in the talk, since they are two different models.

Got it, thanks a lot!


kernel: configs: Add Intel GPU support

The Intel GPU support has been enabled in kata runtime, but the
guest kernel of kata container lacks the support of Intel GPU.
so this commit enables it as default in guest kernel.
CONFIG_DRM, CONFIG_DRM_I915 and CONFIG_DRM_I915_USERPTR are necessary.
Others are obtained by running command "make menuconfig" and selecting
the following options.
Device Drivers
---> Graphics support
---> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support)
Device Drivers
---> Graphics support
---> Intel 8xx/9xx/G3x/G4x/HD Graphics
Fixes #232
Signed-off-by: Zhao Xinda<EMAIL_ADDRESS>

Thanks @xindazhao.
lgtm, but let's get a few more pairs of eyes on it...

/test

Hi @caoruidong, what do you mean by "test"? Could you give me some hints?

Our CI changed to on-demand mode. Need to trigger jenkins by "/test" or "/retest"

hi @caoruidong, could you help to review the commit? Thanks a lot.

LGTM though I'm not expert of kernel config. These configs seems not harmful.


Issue with video display

Hello,
I have gone through the installation process and am trying to run the following command with the GUI:
python iGibson/igibson/examples/behavior/behavior_env_metrics.py
when I run it, I get a lot of print outs (objects are loaded, file sizes are reported, etc.) , but it generates a GUI window that just stays black the entire time. Should I be seeing something when I run this besides a black window, and if I don't see something, what would be causing this issue?
If it helps, the last few lines printed before the program ends is:
Merged vertex data shape:
(3108540, 14)
Enable pbr: True
multidrawcount 481
Segmentation fault (core dumped)

What platform/GPU are you on?

What platform/GPU are you on?

My platform setup is:
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.6 LTS
Release:	16.04
Codename:	xenial
For my GPU setup:
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.130                Driver Version: 384.130                   |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 1070    Off  | 00000000:01:00.0  On |                  N/A |
|  0%   50C    P0    35W / 151W |    589MiB /  8112MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+

Hello,
Is there a solution to this issue? I am facing exactly the same issue in headless mode.

It's hard to debug your individual setups, I would first try to reproduce on an Ubuntu 20.04 workstation with up to date drivers:
This provides the dependencies on a fresh google cloud instance (which I've verified). Note we do test iGibson on Ubuntu 16/18/20.04 and Fedora 34/CentOS 8.
# Add the nvidia ubuntu repositories
apt-get update && apt-get install -y --no-install-recommends \
    gnupg2 curl ca-certificates && \
    curl -fsSL https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/7fa2af80.pub | apt-key add - && \
    echo "deb https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64 /" > /etc/apt/sources.list.d/cuda.list && \
    echo "deb https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu2004/x86_64 /" > /etc/apt/sources.list.d/nvidia-ml.list

# The following cuda libraries are required to compile igibson
apt-get update && apt-get update && apt-get install -y --no-install-recommends \
    xserver-xorg-video-nvidia-470 \
    cuda-cudart-11-1=11.1.74-1 \
    cuda-compat-11-1 \
    cuda-command-line-tools-11-1=11.1.1-1 \
    cuda-libraries-dev-11-1=11.1.1-1 \

# For building and running igibson
apt-get update && apt-get install -y --no-install-recommends \
    cmake \
    git \
    g++ \
    libegl-dev

Actually, we both are on the same team and using the same lab computer. The only difference is I am sshing into the machine and require the headless mode. Our machine is ubuntu 16 and you said you tested on it so this problem so we should not have been faced this, right?
We do have nvidia and cuda libraries for cuda7.5 already installed. Will the version make a difference?

Ah, that makes sense! I can try to find one of our lab computers running 16.04 later and verify.
For reference, this is what you should see (on the latest ig-develop)

I'd recommend upgrading your graphics drivers as they are extremely out of date, and we've run into various issues (most recently a cgroups issue affecting creating egl contexts on the 460.x and 465.x driver series)

I've verified the latest iGibson work on ubuntu 16.04 with the correct dependencies from our  installation guide. Please ensure your nvidia driver and libegl1 are up to date, there are reported issues with EGL context I mentioned before.


Make -Cmetadata consistent across platforms

This commit updates how -Cmetadata is calculated for each unit to optionally exclude the host: ... line that rustc prints for cross-compiled builds. Previously the full verbose_version was hashed for stable builds and the host was explicitly hashed for non-stable builds. For a build using --target, however, that means that the -Cmetadata will be different when producing the same target on different hosts (e.g. producing the binary once on Linux and once on macOS).
This can hinder reproduction of a binary across different platforms even when the --target flag is used. For example in rust-lang/rust#117597 it was seen that a WebAssembly binary produced on different platforms was slightly different and this appears due to the differing -Cmetadata flags. After this commit the -Cmetadata flag is the same for two different platforms meaning that different platforms produce the same binary.
I've tested locally and a simple project produces a different binary before this change but produces the same binary on two platforms after this change. Unfortunately automated testing of this change will be difficult since it requires two different host compilers, though.

Does this fix the same issues in https://github.com/rust-lang/cargo/issues/8140 and https://github.com/rust-lang/cargo/issues/13922?

Ah good catch! I suspect this fixes #13922 but I think there's more concerns brought up in #8140 so while this may fix some of the issues there I don't think it would fix all of them

Thanks! I'm not 100% certain that different host compilers will always produce the exact same output, but I imagine that should be considered a bug in rustc if it does not.
@bors r+

:pushpin: Commit 2db0bab16139d094f689587b73539aae386a1919 has been approved by ehuss
It is now in the queue for this repository.

:hourglass: Testing commit 2db0bab16139d094f689587b73539aae386a1919 with merge 361a4882ae4fe929bdc8f504a3609c0099700b74...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing 361a4882ae4fe929bdc8f504a3609c0099700b74 to master...

A bit off topic, but how does one know when this merge will show up in the stable or nightly release?

I believe cargo gets updated on nightly once a week or so. And from there it will ride the release train to stable, which can take anywhere from 6-12 weeks depending on where in the release cycle a change gets merged.

Thanks! I'm not 100% certain that different host compilers will always produce the exact same output, but I imagine that should be considered a bug in rustc if it does not.

I definitely agree yeah. Getting deterministic output across different host platforms for the same target to me is basically a big game of whack-a-mole. This PR is probably one piece of the puzzle but I also have the same hunch that there are many other pieces for completely full fidelity.

Adding the relnotes label here. Sketch of release notes:
The Rust compiler now uses the same metadata for symbol ABI compatibility regardless of the host the Rust compiler was compiled for. This makes it possible for cross-compiles to the same target from different hosts to produce identical binaries. (There may still be other issues with doing so, which we hope to resolve over time.)


Fix failing EDA Unit Tests that fail only when installed and run from a K12 org.

Critical Changes
Changes
We've updated the way Affiliation Mappings works when EDA orgs are created for new customers. Now, Affiliations Mappings will use API names for Account record types instead of using labels. We've also updated several Affiliations TDTM classes to accommodate this difference. With these changes, EDA unit tests will pass when run on orgs that also have the K-12 Architecture Kit installed.
Issues Closed
#1088
New Metadata
Deleted Metadata
Testing Notes

Tested / Passes QE. @juliesnow please give love to our RN's! Thanks!


link to Chromatic appIds from README #49

Overall this PR looks fantastic:

#113

In this PR, I'm suggesting that we link to our fancy new Chromatic URLs in the README. (I know we can also find the links in PRs and Actions.)
Later we can expand on our use on our use of Chromatic in this issue:

#26.

Ah, this is the problem @GPortas and I have been talking about today:
error during build:
Error: Undefined variable.
   ╷
55 │     "primary": $primary-text-emphasis-dark,
   │                ^^^^^^^^^^^^^^^^^^^^^^^^^^^

See https://github.com/IQSS/dataverse-frontend/actions/runs/5126059350/jobs/9220048062?pr=114#step:5:33
@ekraffmiller definitely unrelated to the README, like you said. I'd say this is safe to merge if you're ok with the content change. Up to you. 😄

Ah, this is the problem @GPortas and I have been talking about today:
error during build:
Error: Undefined variable.
   ╷
55 │     "primary": $primary-text-emphasis-dark,
   │                ^^^^^^^^^^^^^^^^^^^^^^^^^^^

See https://github.com/IQSS/dataverse-frontend/actions/runs/5126059350/jobs/9220048062?pr=114#step:5:33
@ekraffmiller definitely unrelated to the README, like you said. I'd say this is safe to merge if you're ok with the content change. Up to you. 😄

Yes, I saw that in the build. What is the issue that you talked about?  Does it require a change to one of the package.json files? I'd rather not send something to QA that is failing the build.  I tried to recreate it locally by deleting my node_modules files but didn't get the same error.

Oh, I don't mean we have a solution. I just mean we agree that "Undefined variable" was happening on my laptop. And now we see it in GitHub Actions, apparently.

@pdurbin @ekraffmiller
Yesterday @MellyGray and I solved the problem with undefined bootstrap variables by using a fixed version. See: https://github.com/IQSS/dataverse-frontend/pull/112/commits/ebfb2215bdb19541956ed82ec37233cf1c372e23


Add ThreatIntelligencePlatform.com

Add this row below to the category Threat Intelligence:
- [ThreatIntelligencePlatform.com](https://threatintelligenceplatform.com/) - Data, tool, and API provider that specializes in automated threat detection, security analysis and threat intelligence solutions

Hey @edoardottt, Can I work on this ? Could you assign it to me ?

Done @AdityaJ2305 : )

Thanks for your contribution, appreciated! @AdityaJ2305


Decompose cuda

CUDA decompose function passed test.
Added time measurement for Kernel function.

Codecov Report
Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (5155e7e) 96.80% compared to head (e7d7331) 97.10%.
Report is 204 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #257      +/-   ##
==========================================
+ Coverage   96.80%   97.10%   +0.29%
==========================================
  Files          27       27
  Lines        2223     2312      +89
==========================================
+ Hits         2152     2245      +93
+ Misses         71       67       -4

Files
Coverage Δ

include/micm/process/process_set.hpp
99.32% <100.00%> (ø)

include/micm/solver/lu_decomposition.hpp
100.00% <ø> (ø)

include/micm/process/jit_process_set.hpp
98.78% <98.87%> (+2.40%)
:arrow_up:

include/micm/solver/rosenbrock.hpp
96.65% <92.85%> (+0.68%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@qinatan can you resolve the conflicting files in your PR before I test it on Derecho?

@qinatan The following two tests failed with your latest branch:
7 - troe_rate_constant (Failed)
10 - cuda_process_set (SEGFAULT)

@qinatan The troe_rate_constant test still fails somehow with your latest branch.
7 - troe_rate_constant (Failed)

@qinatan we've ran into this failing before, specifically with nvhpc. Does this test happen to pass if you make a release build?

@qinatan The troe_rate_constant test still fails somehow with your latest branch.
7 - troe_rate_constant (Failed)

@qinatan we've ran into this failing before, specifically with nvhpc. Does this test happen to pass if you make a release build?

@sjsprecious - were you building with Debug or Release?

@qinatan The troe_rate_constant test still fails somehow with your latest branch.
7 - troe_rate_constant (Failed)

@qinatan we've ran into this failing before, specifically with nvhpc. Does this test happen to pass if you make a release build?

@sjsprecious - were you building with Debug or Release?

@mattldawson @K20shores @qinatan My bad! Yes, I recalled this issue now and I was using the DEBUG build option before. Switching to the release option passes the troe_rate_constant test. However, it then fails the regression_test_rosenbrock_p_force test somehow.

@qinatan The troe_rate_constant test still fails somehow with your latest branch.
7 - troe_rate_constant (Failed)

@qinatan we've ran into this failing before, specifically with nvhpc. Does this test happen to pass if you make a release build?

@sjsprecious - were you building with Debug or Release?

@mattldawson @K20shores @qinatan My bad! Yes, I recalled this issue now and I was using the DEBUG build option before. Switching to the release option passes the troe_rate_constant test. However, it then fails the regression_test_rosenbrock_p_force test somehow.

@sjsprecious Would you be able to run this test using the main branch? I think it's likely this is unrelated to this particular PR, and just slipped by because we have no automated testing with the NVidia compiler on GPUs. If main fails in the same way, let's create a separate issue for this (and see if we can come up with some solution for automated testing on GPUs, if possible)

@qinatan The troe_rate_constant test still fails somehow with your latest branch.
7 - troe_rate_constant (Failed)

@qinatan we've ran into this failing before, specifically with nvhpc. Does this test happen to pass if you make a release build?

@sjsprecious - were you building with Debug or Release?

@mattldawson @K20shores @qinatan My bad! Yes, I recalled this issue now and I was using the DEBUG build option before. Switching to the release option passes the troe_rate_constant test. However, it then fails the regression_test_rosenbrock_p_force test somehow.

@sjsprecious Would you be able to run this test using the main branch? I think it's likely this is unrelated to this particular PR, and just slipped by because we have no automated testing with the NVidia compiler on GPUs. If main fails in the same way, let's create a separate issue for this (and see if we can come up with some solution for automated testing on GPUs, if possible)

Thanks @mattldawson . Yes, the same test fails for the main branch, either. I agree that this is unrelated to Qina's work here and should be addressed separately. In terms of testing MICM on GPU, we are using a self-hosted runner on Derecho to test another code on the GPU through the GitHub workflow. It is not 100% automatic but it could be a solution temporarily. Happy to chat offline about this idea.


getting a lot of errors

Unable to use this version of binwalk. Getting those errors:
WARNING: Error loading plugin 'lzmamod.py': [Errno 13] Permission denied
The files concerned are:
'zlibvalid.py'
'tar.py'
'cpio.py'
'lzmamod.py'
'compressd.py'

It seems that this problem still exists. It happens on Ubuntu Ubuntu 14.04.4 LTS, both when installed via pip install binwalk and when running sudo python setup.py install from the downloaded tarball from github.
This is what the plugins folder looks like after installation. Note that I am not in the staff group.
$ ll /usr/local/lib/python2.7/dist-packages/binwalk/plugins/
total 120K
-rw-r----- 1 root staff 2,7K Dez 23  2015 arcadyan.py
-rw-r--r-- 1 root staff 2,5K Aug 11 14:48 arcadyan.pyc
-rw-r----- 1 root staff 1,4K Dez 23  2015 compressd.py
-rw-r--r-- 1 root staff  502 Aug 11 14:48 compressd.pyc
-rw-r----- 1 root staff 3,9K Dez 23  2015 cpio.py
-rw-r--r-- 1 root staff 2,9K Aug 11 14:48 cpio.pyc
-rw-r----- 1 root staff 1,5K Dez 23  2015 gzipextract.py
-rw-r--r-- 1 root staff 1,7K Aug 11 14:48 gzipextract.pyc
-rw-r----- 1 root staff 1,8K Dez 23  2015 gzipvalid.py
-rw-r--r-- 1 root staff 1,7K Aug 11 14:48 gzipvalid.pyc
...


Create anyWordNbe, anyWordNle, wordNbe, and wordNle

Provide support for words of various sizes.
Also, small code refactoring and changing deprecated functions to newer ones.

Nice -- thanks for the PR! Will try to get an update pushed to Hackage this evening (will depend on how long it takes to recover my account there, which seems to have bit-rotted).

Thanks! Please note that I didn't change the package version, so it's still at 0.2.


Changes made by setValue don't sync in other users view

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
Declarative list formatting
Developer environment
None
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[X] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

Chrome  125.0.6422.142
Edge 125.0.2535.92
Firefox 124.0

Describe the bug / error
We use a button with setValue to add a person and set a new status to an item with a single click in list view. However, during testing we realised that changes made by setValue action do not sync in other editors views. This leads to problems because the button may be clicked again by other editors and tasks may be worked on by several people.
setValueBug.webm
Steps to reproduce

Add a JSON format to a person field that gives it a button with a customRowAction of type setValue. i.e.

{
"$schema": "https://developer.microsoft.com/json-schemas/sp/v2/column-formatting.schema.json",
"elmType": "div",
"children": [
{
"elmType": "div",
"style": {
"display": "=if(([$Status] == 'To Do' || [$Status] == '' || [$Status] == 'Watch' || [$Status] == 'Idee') && [$Autor] == '', 'flex','none')",
"flex-direction": "row"
},
"children": [
{
"elmType": "div",
"style": {
"width": "95px",
"height": "26px",
"border-radius": "3px",
"cursor": "pointer",
"display": "flex",
"align-items": "center",
"justify-content": "space-evenly",
"margin": "5px"
},
"attributes": {
"class": "ms-bgColor-themePrimary ms-bgColor-themeDark--hover ms-fontColor-white ms-fontSize-12 ms-fontWeight-bold"
},
"customRowAction": {
"action": "setValue",
"actionInput": {
"Status": "In Arbeit",
"Autor": "@me"
}
},
"children": [
{
"elmType": "div",
"txtContent": "Übernehmen"
}
]
}
]
},
{
"elmType": "div",
"children": [
{
"elmType": "span",
"txtContent"<EMAIL_ADDRESS>', ')",
"style": {
"padding-left": "5px",
"word-break": "keep-all"
}
}
]
}
]
}

Use the button and observe in a second browser whether the changes are visible.

Expected behavior
A click on the button in list view should trigger the change of the values and these changes should be immediately visible to other users.

@marcokitzmann Thanks for reporting the bug. We will take a look at this and update on the timelines.


iOS - Send screen analytics for account settings screen and my programs screen

Description
LEARNER-8260
LEARNER-8259
In this PR I added the screen analytics for the Account settings screen and My programs screen

@mumer92 I have fixed the comments

@saeedbashir I have fixed comments.


Update lib to use prices 1.0.0

This PR bumps lib's version to 1.0.0, redoes the api to be function based with functions returning lists of payloads to send to Google's API, and updates codebase to work with TaxedMoney.
TODO

[x] Convert EnhancedItem and EnhancedTransaction to functions
[x] Add **extra_data to all functions
[x] Split __init__ into few smaller packages
[x] Move tests suite to py.test
[x] Update readme

Can we please have all items accept **kwargs and merge them into the the resulting dict? Adding custom fields is a common case and is currently fairly awkward.

@patrys

Question: would it make sense add type information now that we're dropping Python 2?

Most of API is returning dicts, but typing functions params will be big usability win here and not that hard to do (just copy param types from google docs), so I'll do another pass with those.


Images on edit form

In the edit form of one of the resources of my app, that contains images on different nested models, I find that only some images are being shown. the two models on the screenshot are configured exactly the same. Is there a limit of images loaded on the nested forms?
I wouldn´t care but it may be confusing for my client...

With Refile no images are shown for me in the Edit form, just a URL.

In my case some do, others don't...


throw tool exit when chrome fails to connect

Description
If we can't establish a debug connection with chrome, throw a tool exit instead of crashing with a socket exception. Not quite certain why this happens yet or what other steps we can take.

Not the right fix, we already throw an exit


[Bug]: The replica repair process is continuously retried

Contact Details
No response
Is there an existing issue for this?

[X] I have searched all the existing issues

Priority
low (Default)
Environment
- CubeFS version:3.4.0

Current Behavior
Decommission a data node, the repair progress of a replica of a data partition sticks at 98.55%, then regresses to 0, and new replicas are created on other nodes to retry the repair process.
Expected Behavior
The repair progress of the replica will not get stuck and will be able to complete the repair successfully.
Steps To Reproduce
1. Decommission data node
2. Observe the repair progress of replicas through the cli.

CubeFS Log
No response
Anything else? (Additional Context)
No response

closed by #3563


Merging metrics branch into master

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I will merge this PR after Bala creates the release tag.
Just avoiding any merge issue.


print_from_file should take AsRef, not &str

Currently, if you want to pass a Path to viuer::print_from_file, you have to convert it to a &str:
let path = Path::new("some/path/foo.png");
print_from_file(path.to_str().unwrap(), &Default::default());

This isn't very ergonomic, and if your path contains invalid UTF-8, you can't use it all. Since image::io::Reader::open already takes an AsRef<Path>, I don't see any technical reason for this limitation. Additionally, str already implements AsRef<Path>, so I don't think this would be a breaking change. I'm happy to submit a pull request implementing this change, if it's wanted.

Very good point, I don't think there is a specific reason why it is like that. I'll be happy to review/test a PR with such changes :)


Improve code cov

Codecov Report
Patch coverage has no change and project coverage change: -68.19 :warning:

Comparison is base (78fb183) 68.18% compared to head (abf5320) 0.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #26       +/-   ##
==========================================
- Coverage   68.18%   0.00%   -68.19%
==========================================
  Files           7       7
  Lines         484     493        +9
==========================================
- Hits          330       0      -330
- Misses        154     493      +339

Impacted Files
Coverage Δ

src/helpers.jl
0.00% <0.00%> (-77.09%)
:arrow_down:

... and 5 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Getting the pickle analysis data from within Python

Hello, I am trying to obtain the pickle analysis data that is associated with pickled model checkpoints from Python programmatically but is unable to find anything in the docs on how to do this. Is there a clear way to do this?
A screenshot of the example of the analysis information is attached below.

it is not currently supported, but cc'ing @McPatate (and @krampstudio for visibility)
thanks for the feature request!

@Wauplin  Thanks a lot for adding it as a new feature, just tested out the new API and it works very well! I was wondering if in the future a user downloading a potential malicious Pickle file would raise a confirmation warning to make it clear to them the risks before allowing the model to load? This seems like a good addition now that the scan data is available via the API.

I was wondering if in the future a user downloading a potential malicious Pickle file would raise a confirmation warning to make it clear to them the risks before allowing the model to load?

That's actually a pretty good idea. I'll keep it in mind to do it properly. I think that if we do something like that, it will be a warning but without asking confirmation from the user (or at least not by default). Always a balance to find between usability and security :)

I think having an extra option disable_unsafe_download (defaulting to False) could be a nice to have 😄

Yes, I was thinking about an environment variable directly so that users can be sure to disable them globally.

@McPatate before implementing this, what's your take on how to consider a file as "unsafe". I saw that the security scan has 3 levels: innocuous, suspicious and dangerous.
I see four options here:

set HF_HUB_DISABLE_UNSAFE_DOWNLOAD=1 raise an Exception on dangerous files but not suspicious ones
set HF_HUB_DISABLE_UNSAFE_DOWNLOAD=1 raise an Exception on dangerous files AND suspicious ones
set HF_HUB_DISABLE_DANGEROUS_DOWNLOAD=1 and HF_HUB_DISABLE_SUSPICIOUS_DOWNLOAD=1 separately. If "disable suspicious" is True, "disable dangerous" is automatically True as well => more explicit and flexible but it adds two env variables instead of one.
set HF_HUB_UNSAFE_DOWNLOAD_LEVEL (or HF_HUB_SAFETY_LEVEL?) to either "minimal" (default), "intermediate" or "maximal" => as much flexibility as 3. but with only 1 variable

For me it really depends on what suspicious means and when it happens. IMO if a user sets HF_HUB_DISABLE_UNSAFE_DOWNLOAD=1,  I'd rather forbid any non-innocuous download (i.e. option 2). Otherwise if flexibility is important, I'd go for option 4 but with a better naming.
Also cc @JohnnyRacer if you are opinionated on this topic.

@Wauplin
I think it would be a good idea to prevent downloads of  dangerous Pickle checkpoints by default, with  a warning message that can be disabled via an environment variable like you had mentioned above or by calling a function like transformers.env_configs.disable_unsafe_download(True) .  To toggle the ability to allow for unsafe download on or off. I think a way to disable unsafe downloads is needed as it can be used conveniently as a malware dropper, especially when models are loaded onto production environments.  For suspicious models I think a toggle-able  warning will suffice since most do not contain dangerous eval` which would allow for arbitrary code execution.

I think the future-proof way is to emit a warning on any model loading from Pickle, as we default more and more to the safetensors format (and its usage is growing rapidly)

Does it cost a lot to send a request to the hub to check before starting a download if there are dangerous imports?
It could also be done asynchronously, as in no changes in the download logic, except you add a cancellation token to the download job and if the file contains a dangerous import, the asynchronous job cancels the download, wdyt @julien-c?

But that should rather live in libraries

Yes, correct

or even in torch


Fix selector engine blowing with invalid ids

Fixes #1608

This is a weird piece of code, do we have a better way around it? Maybe first check with document.getElementById?
r+wc

This is a weird piece of code, do we have a better way around it? Maybe first check with document.getElementById?

What's weird, my patch or the original code?
The regex just checks what is acceptable as a valid id (in a quite liberal way since HTML5 allows everything that's not spaces [1]). We're not likely doing anything too crazy since the original code is just dealing with opening sections denoted by and id.
The regex ignores things like #id=foo which is what is causing the original problem.
As far as the regex goes - It must start with '#', \w is analogous to [A-Za-z0-9_] and I'm adding - and . to that. Other than that the repetition is one or more.
I suppose the alternative could look like this:
var fragment = window.location.hash;
if (fragment) {
    // If the page URL is pointing directly to an expando section (e.g.
    // external link to that section), make sure the contents are visible.
    // The getElementByID ensures the element exists and doesn't
    // allow us to pass invalid selectors to jQuery.
    var $target = $(document.getElementById(fragment.substr(1)));
    if ($target.hasClass('expando'))
        $target.addClass('expanded');
}

But then I'm not sure how direct that is?
[1] https://mathiasbynens.be/notes/html5-id-class

I was talking about the original code, taking just any fragment, converting it into a jquery node, and then expanding it. Your code is very good ;)
Thinking again about it, and as you explained yourself, making it "sure that it's a proper existing id" doesn't really add anything to it, so let's just leave it as is, thanks!

Thinking again about it, and as you explained yourself, making it "sure that it's a proper existing id" doesn't really add anything to it, so let's just leave it as is, thanks!

Ok! Btw I do like the simplicity of the document.getElementById idea - it's clever and works well in practice since the null when the id doesn't exist just means that jquery does nothing with it and when it returns an element jquery just wraps that with a jquery object.
The only thing there is it looks a bit odd, passing document.getElementById as an arg to $().


Question about the test-time prompt learning procedure

Thanks for your work!
I am wondering that given a single test image and conduct the test-time prompt learning procedure, is this test image immediately evaluated on the optimized prompt?
Furthuremore, once the evaluation of a single test image is finished and the corresponding prompts is optimized, for the next coming test image, the prompts will be re-initialized to "a photo of a" or just using the optimized one from the previous step?

Thanks for your response! My confusion is resolved.

Hi, thank you for your interest in our work. To answer your questions:

Yes, the test image is evaluated immediately on the optimized prompt.
When a new test image comes in, the prompt will be reset to its initial state ("a photo of a" or the initial CoOp weight).

Hi, Thank you for your response! But I’m still curious about the reasoning behind resetting the prompts to their initial state when a new test image is introduced. Could you explain why the previous optimized prompt is not utilized for the next test image?


Add support for a static folder

It is a nice escape hatch, ref: #28
Verified by going through the entire flow (in all three states, i.e. node_modules, development and ejected) with npm start.

Can you please rebase this? I want to take a look this week.

Put it on my todo list, will do this evening!

Rebased!

What happens if I just reference /src/image.png in my HTML? If it works now we need to make sure it doesn’t because that would be confusing.

Don't have time to try it out at the moment I'm afraid!

Interesting thread! I was just experiencing this "short coming" today while testing out create-react-app and I needed to load Apple touch icons. I just happened to solve this the exact same way (only calling it assets which I understand was an unpopular choice), and silly me didn't check to see if there already was an open PR. I think this would be a great addition.
@gaearon I tested out referencing the /src/logo.svg directly from index.html and that didn't work. Neither did creating an arbitrarily file, /bar/foo.svg, and that could not be referenced from the static files either.
As a maybe "happy accident", by calling this static, it works as expected when referencing the files from the index.html it feels natural both in build and start mode as one can refer to the JS, CSS and media files from the same location. I also verified that a folder media in the template/static directory, got merged with the build/static/ directory and not overwritten.
Now it might feel "magical" that you have to create the static directory yourself and users need to confer with documentation by own initiative to check "if something like this just happens to exist". I think the template should have this folder by default by using something like PNG favicons or something.
Having something like this:
static/favicon/favicon-16.png
static/favicon/favicon-32.png

And in index.html:
...
<title>React App</title>
<link rel="icon" href="static/favicon/favicon-16.png" sizes="16x16" type="image/png">
<link rel="icon" href="static/favicon/favicon-32.png" sizes="32x32" type="image/png">
...

This way it would be easy to understand how to use it, and that it even exists. Just wanted to chime in and managed to write an entire essay doing so.

@mikaelbr Haha thanks for feedback on this!

For a Service Worker to control a site, it has to be placed at the root. I.e., a service worker at /static/sw.js could only control pages that started with /static. There are other systems like Google's Website Verification that work by looking for a file at the root of a domain.
Any concern with simply removing the to option from CopyWebpackPlugin(), so that the contents of static are copied directly into the output?

@sco that'd be confusing if you put files into static/image.png but then have to reference /image.png. It might also override over files that are in the root? (imagine putting an index.html into static/…)

copy-webpack-plugin actually won't overwrite any previously staged files, by default.
I can see how it might be a little confusing, but I think @mikaelbr's suggestion of putting the favicons there, and referencing them from index.html, would help to illustrate it pretty clearly.
I suspect putting arbitrary files at the root of a project will be a fairly common need. (robots.txt comes to mind, for instance.)

There might be several files that are required to be in the root, so there might be a need to do this as well. What is the possible downsides of copying files from root to root?
By just copying files it'll be easier to restrict what files to actually copy and reduce the build-directory, but it might be more more confusing; "why do this files work, but I can't find /some-dir/bar.svg." Are there any huge side-effects by transferring all extra static files, except build size?

If you have a backend to your app, serving arbitrary static files from the root url that your webserver serves generally is not a good idea, because then you can't use a regex in your nginx/apache config to decide whether to route things to your static file service mechanism or to your backend. You usually want to special-case a small number of files, like robots.txt, crossdomain.xml, sw.js, and so on. So I suggest we continue serving assets in /static/ from a url containing /static/.
Perhaps you could actually work around this quite easily if you don't have a backend, by proxying to localhost:3000/static. That will proxy localhost:3000/sw.js to localhost:3000/static/sw.js IIUC. If you do have a backend then this won't work, but if you do have a backend then you already have the problem that the default logic will proxy /sw.js to your backend. You might just want to serve a handful of static files from your existing backend in that case.

I don't think proxying like that is a good idea. Having 2 different routes that route to the same assets is needlessly confusing.
I think it's much better to move index.html and favicon.ico into the static file and have everything in there copied into dist.

I think it's much better to move index.html

This would be a much better solution if index.html wasn't passed through webpack with the HTMLWebpackPlugin – but alas, it is. That'd only make things more confusing if suddenly one single file in the static/ folder was passed through webpack but all the others aren't.

Depends on whether the associated images in there would be passed though
webpack as well to have hashes added for cdn cache busting reasons.
I wouldn't mind building a pr for all this but have no clue if it's what
the maintainers want.
On Mon, Aug 29, 2016 at 4:01 AM Max Stoiber<EMAIL_ADDRESS>wrote:

I think it's much better to move index.html
This would be a much better solution if index.html wasn't passed through
webpack with the HTMLWebpackPlugin – but alas, it is. That'd only make
things more confusing if suddenly one single file in the static/ folder
was passed through webpack but all the others aren't.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/pull/226#issuecomment-243057958,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABJ2igg8U4OqFJMyqeGmlDfRTZDG2BGks5qkpHhgaJpZM4JVdxr
.

Depends on whether the associated images in there would be passed though webpack as well to have hashes added for cdn cache busting reasons.

Nope, then they should go into the src folder next to the respective components. The whole point of having a static/ folder is that it's an escape hatch out of all of that behaviour.

Then index.html should be in src
On Mon, Aug 29, 2016 at 8:13 AM Max Stoiber<EMAIL_ADDRESS>wrote:

Depends on whether the associated images in there would be passed though
webpack as well to have hashes added for cdn cache busting reasons.
Nope, then they should go into the src folder next to the respective
components. The whole point of having a static/ folder is that it's an
escape hatch out of all of that behaviour.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/pull/226#issuecomment-243106997,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABJ2rrU9h8qvQRURSbYUVKdWu5MgFoOks5qksz0gaJpZM4JVdxr
.

This is tangential to this PR, but if that's the case then index.html should be inside of src anyways.
And with that context I'd say that having static is a mistake that would lead to more confusion than it would solve. It gives 2 locations for things to be stored rather than just one. For those who need the more advanced  behavior they can always eject and do themselves.

@tal I personally have no useful opinion on layout or even what should or shouldn't go through the webpack transformation.
On the topic of capabilities, though: I do think that it's good to have a fairly ambitious definition of what can be done without ejecting.  So, in particular, serving favicons for all major OSes and as much of the progressive web app feature set as possible (good service workers defaults, etc.), should not require ejecting.
If those capabilities are accessible (but not required) in the default setup, then more people will implement them, and more webapps will be better webapps, which is good for users and good for the web.

What i was meaning was that those favicon or icons of whatever sort for all
the OSes are specified by meta tags. Not convention. That means that they
should be cache busted, this probably means going though webpack in some
way.
On Mon, Aug 29, 2016 at 12:45 PM David Ascher<EMAIL_ADDRESS>wrote:

@tal https://github.com/tal I personally have no useful opinion on
layout or even what should or shouldn't go through the webpack
transformation.
On the topic of capabilities, though: I do think that it's good to have
a fairly ambitious definition of what can be done without ejecting. So, in
particular, serving favicons for all major OSes and as much of the
progressive web app feature set as possible (good service workers defaults,
etc.), should not require ejecting.
If those capabilities are accessible (but not required) in the default
setup, then more people will implement them, and more webapps will be
better webapps, which is good for users and good for the web.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/pull/226#issuecomment-243180755,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABJ2rwYSvWX7TlyHBe3QVKaCxlVFWQUks5qkwyggaJpZM4JVdxr
.

@tal, in that case, maybe a package like webpack-manifest-plugin would be interesting. It works by adding this to your webpack loader config:
{
    test: /manifest.json$/,
    loader: 'file?name=manifest.json!web-app-manifest',
},

Sorry for the long turnaround on this.
I’ve been weighing pros and cons and I’m coming to realization that this is not the approach I want to take.
Instead, #428 should satisfy most use cases, and if not, we can address them on case by case basis (file issues!)
Please see #551 for more comments on this, justification for not supporting this, and additional documentation that I believe adequately explains how #428 works as well as the behavior I ultimately want to have.
Sorry 😥.

We got some more feedback and I know more about the use cases people have for this. I couldn't find any better alternative also let's do it in the next minor.

Thought some more about it. It won't work for non-relative roots (like GH Pages).
People will reference /static in their HTML and it will 404 after hosting.
Any ideas how to solve that?

would love to help with this issue. it relates to the open graph meta tag issue i'm wanting resolve too.
what should i try?

I’m going to close this because I ended up with a different solution that I think addresses these concerns better: https://github.com/facebookincubator/create-react-app/pull/703. Let me know what you think!

This is now supported in 0.5.0.
Read about using the new public folder.
See also migration instructions and breaking changes in 0.5.0.


Error 500 when I try to send an email.

When I try to send an email, I get a 500 error in the F12 console. For some reason, it sends the POST request to <IP_ADDRESS>:465, and I don't know why. Here is my config :
SMTP_HOSTNAME: ssl0.ovh.net
SMTP_PORT: 465
SMTP_USERNAME: "{{ smtp_username }}"
SMTP_PASSWORD: "{{ smtp_password }}"
SMTP_AUTH_TYPE: LOGIN
SMTP_ENCRYPTION: STARTTLS
EMAIL_FROM_ADDRESS: "{{ smtp_username }}"
EMAIL_FROM_NAME: Compte VPN

Bad config of my dnsmasq.


Send DSN with SentryEnvelopeHeader

:scroll: Description
This change injects DSN into the SentryEnvelopeHeader class and serializes it if available.
:bulb: Motivation and Context
This change ensures that the DSN is passed to the server along with events, bringing in consistency with the JavaScript SDK. This gets us one step closer to passing a tunnel that can be used to proxy data to Sentry servers (to fixe #872). Once this change is merged, will create a separate PR that accepts tunnel as a parameter within the SentryConfig and configures the transport accordingly (again, similar to the JS SDK).
:green_heart: How did you test it?
Verified that the dsn was passed within the envelope to the remote server.
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[x] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Hey @marandaneto, why would this require changes to the Java SDK? Isn't the Dart SDK self contained?

Hey, no, the Android SDK has to deserialize and serialize again the event in order to enrich the event with the device context.
The reason is: https://github.com/getsentry/team-mobile/issues/11
On iOS it'd work ootb.

Yikes, I had no idea. I would much rather someone who is familiar with the development environment for the Java SDK make that change. I hope that's okay.

Yikes, I had no idea. I would much rather someone who is familiar with the development environment for the Java SDK make that change. I hope that's okay.

Yep, let me try to get into this latest next week since this is a short week, if that's ok.

Codecov Report
Base: 90.05% // Head: 90.13% // Increases project coverage by +0.08% :tada:

Coverage data is based on head (3502ee4) compared to base (fa7e619).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #873      +/-   ##
==========================================
+ Coverage   90.05%   90.13%   +0.08%
==========================================
  Files         105      107       +2
  Lines        3357     3405      +48
==========================================
+ Hits         3023     3069      +46
- Misses        334      336       +2

Impacted Files
Coverage Δ

dart/lib/src/sentry_envelope.dart
100.00% <ø> (ø)

dart/lib/src/sentry_client.dart
93.43% <100.00%> (+0.04%)
:arrow_up:

dart/lib/src/sentry_envelope_header.dart
100.00% <100.00%> (ø)

logging/lib/src/extension.dart
100.00% <0.00%> (ø)

logging/lib/src/logging_integration.dart
90.47% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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

@ua741 CI is unhappy, also, add a new changelog entry, after that, happy to LGTM.

@ua741 CI is unhappy, also, add a new changelog entry, after that, happy to LGTM.

@ua741 any update here?

Seems like only a lint issue, preferred const over final, otherwise tests are passing.

@ua741 CI is unhappy, also, add a new changelog entry, after that, happy to LGTM.

@ua741 any update here?

Sorry for dropping the ball here, I was on vacation.
Thank you so much for taking it forward and merging it. Really appreciate it.


Iceprog mpsse refactor

These changes move the MPSSE specific functions into it's own module. This should make the code bit less cluttered and also allow for the reuse of the MPSSE specific code for other projects.
I have changed the bank selection to be numeric instead of an enum so that we don't refer to any ftdi internal structures and api in the main header file, this was the only place we would need it otherwise.

Thank you for merging. I was about to fix the things @daveshah1 pointed out. I will send a new cosmetic cleanup PR later. :)

Did that already in 15c9bfd. :)

Ok, awesome! Thank you again for merging this. :D


SNS Topic Does Not Exist Error Message

Describe the bug
After deploying v1.3.1 and running the remediation for CIS 3.x findings, I am receiving an error in the SO0111-SHARR-Orchestrator logs pointing out that a "Topic does not exist". The error references line 264, "publish_to_sns('SO0111-SHARR_Topic', self.severity + ':' + self.message, self.__region)" from sechub_findings.py. Is this the correct topic name or does this need to be adjusted to "SO0111-SHARR-LocalAlarmNotification"?
To Reproduce
Deploy the 1.3.1 solution
Create a subscription for the newly created SO0111-SHARR-LocalAlarmNotification SNS topic
Remediate any one or more of the CIS 3.x Security Hub findings using SHARR
Check the log entry in the SO0111-SHARR-Orchestrator logs
Expected behavior
I would expect to not see any errors in the SO0111-SHARR-Orchestrator logs after a remediation attempt. I would also expect to see a successful remediation message in the SO0111-SHARR log group.

[ ]Version: v1.3.1
[x] Region: us-east-1
[x] Was the solution modified from the version published on this repository? No
[x] Have you checked your service quotas for the sevices this solution uses? Yes
[x] Were there any errors in the CloudWatch Logs? How to enable debug mode? Yes

Screenshots

Additional context
Despite the execution failed message in the log, the remediation did end up setting up the metric and the alarm as expected. Also, the Security Hub finding did resolve at least for 3.2. 3.1 is still not resolving but that is due to the metric being switched around as mentioned here: https://github.com/awslabs/aws-security-hub-automated-response-and-remediation/issues/38

Hello mobri2a, thank you for getting back to me. I reviewed the CloudFormation template output as you suggested and noticed that the SNS topic was created with no issues however when I went to the SNS console, the topic was not there. I'm thinking possibly it was removed manually by a team member and I didn't know. I recreated the topic manually and everything worked as I would expect. I really appreciate your help!


Spotify API Error (unknown): received an empty response

Skipping lyrics for ATSMXN - Disco Phonk: lyrics not available

Not a bug, it's just letting you know there aren't any lyrics to download for that track. The program will still run as expected.
If you don't care about lyrics and just want the warning message to go away, turn off DOWNLOAD_LYRICS in the config or add --download-lyrics=False to your command.


Improve source code style in report

Display def, end, class and module in bold.

Closed because I never needed it


Prevent interest room moderators from modifying widgets

The moderators of interest rooms are not the conference hosts and are
liable to break things. Restrict widget modification in those rooms to
admins.

Rejigged the PR to update existing interest rooms with the correct settings.


Preserve file permission when creating archives

Restoring file permissions on extraction works with #14, however there are no clean mechanisms for reading permissions from a File and setting them in an ArchiveEntry.

@thrau , great lib! Any plans on implementing this feature?

are you on *nix or windows? the problem is really that the java file permissions are very course grained and there's no good way of reading them in a cross-platform way.
for *nix we could maybe just use a similar mechanism as with permission restoring.


pd.Period can't be used as a 1-element coord

With xarray 0.7.2, following this basic example from the docs, but with a modification in the last line to use pd.Period instead of pd.Timestamp:
import numpy as np
import xarray as xr

temp = 15 + 8 * np.random.randn(2, 2, 3)
precip = 10 * np.random.rand(2, 2, 3)
lon = [[-99.83, -99.32], [-99.79, -99.23]]
lat = [[42.25, 42.21], [42.63, 42.59]]

ds = xr.Dataset({'temperature': (['x', 'y', 'time'],  temp),
                 'precipitation': (['x', 'y', 'time'], precip)},
                 coords={'lon': (['x', 'y'], lon),
                         'lat': (['x', 'y'], lat),
                         'time': pd.date_range('2014-09-06', periods=3),
                         'reference_time': pd.Period('2014')})

This raises:
ValueError: dimensions ('reference_time',) must have the same length as the number of data dimensions, ndim=0

I noticed (#645) that there are other issues stemming from pandas' PeriodIndex & company, so if this is not a straightforward fix I will understand!

It doesn't really seem like reference_time is a "coordinate" variable. Being a scalar, you are not going to use it as a coordinate in the same sense as lat/lon/time.  Nevertheless, your example works if  you cast the Period to a DataArray first:
ds = xr.Dataset({'temperature': (['x', 'y', 'time'],  temp),
                 'precipitation': (['x', 'y', 'time'], precip)},
                 coords={'lon': (['x', 'y'], lon),
                         'lat': (['x', 'y'], lat),
                         'time': pd.date_range('2014-09-06', periods=3),
                         'reference_time': xr.DataArray(pd.Period('2014'))})

Thanks for the bug report -- this should definitely work. I'll take a look.

@jhamman — you're right. In truth, I was working with some more complex code using a PeriodIndex and getting errors I couldn't decipher, so I pulled those lines from the docs and played with them to try to understand what was happening. I don't know why it's that way in the docs…maybe because ds['reference_time'] or ds.reference_time is more concise than ds.attrs['reference_time']?
@shoyer — thanks!

This now works, although as an object array rather than PI. Which is probably OK:
In [6]: ds
Out[6]:
<xarray.Dataset>
Dimensions:         (time: 3, x: 2, y: 2)
Coordinates:
    lon             (x, y) float64 -99.83 -99.32 -99.79 -99.23
    lat             (x, y) float64 42.25 42.21 42.63 42.59
  * time            (time) datetime64[ns] 2014-09-06 2014-09-07 2014-09-08
    reference_time  object 2014
  * x               (x) int64 0 1
  * y               (y) int64 0 1
Data variables:
    temperature     (x, y, time) float64 12.29 8.305 10.63 16.6 2.823 16.29 ...
    precipitation   (x, y, time) float64 4.541 3.618 3.336 2.332 7.987 4.197 ...

In [7]: ds.reference_time
Out[7]:
<xarray.DataArray 'reference_time' ()>
array(Period('2014', 'A-DEC'), dtype=object)
Coordinates:
    reference_time  object 2014

@shoyer - to close?

Yep, looks like this works now. There's no period dtype in NumPy, so object dtype is the best we can do.


Strange behaviour with "conditionally required fields"

I've encountered an issue with a schema entry similar to the one below from the documentation:
 {
   field: {
    type: String,
    optional: true,
    custom: function () {
      var customCondition = this.field('saleType').value == 1;
      if (customCondition && !this.isSet && (!this.operator || (this.value === null || this.value === ""))) {
        return "required";
      }
    }
  }
 }

Without !this.isSet, an exception is being thrown with message "Error: field is required"
Though the problem is I don't want to be able to update and remove the field... Will this check be affected by update operations?

isSet means whether the document (for an insert) or the modifier (for an update) is trying to do something to the "field" property.
So the example seems to be for checking on insert only. For an update, I think this would work, but modifiers get tricky because you have to make sure to account for all supported operators for your version of mongo.
function () {
  var shouldBeRequired = this.field('saleType').value == 1;

  if (shouldBeRequired) {
    // inserts
    if (!this.operator) {
      if (!this.isSet || this.value === null || this.value === "") return "required";
    }

    // updates
    else if (this.isSet) {
      if (this.operator === "$set" && this.value === null || this.value === "") return "required";
      if (this.operator === "$unset") return "required";
      if (this.operator === "$rename") return "required";
    }
  }
}


(PUP-10433) Add --no-gpg-checks as global option

This PR updates the global option "--no-gpg-check" to "--no-gpg-checks". "--no-gpg-checks" is the correct flag from the zypper documentation:  https://en.opensuse.org/SDB:Zypper_manual_(plain)
"--no-gpg-check" works because zypper supports unique name abbreviations for flags:
https://github.com/openSUSE/zypper/blob/master/src/utils/flags/zyppflags.cc#L378 but this causes confusion when using this flag in a Puppet manifest.
Zypper also accepts multiple options of the same type, so:
/usr/bin/zypper --no-gpg-check --no-gpg-checks install --auto-agree-with-licenses --no-confirm apache

does the same thing as:
/usr/bin/zypper --no-gpg-checks install --auto-agree-with-licenses --no-confirm apache

jenkins please test this on sles11-64a,sles11-32a,sles12-64a,sles12-POWERa,sles15-64a

CLA signed by all contributors.


Fedora 31 release

Write a spec file and get osbuild-composer into fedora 31. The spec file should be accepted into fedora, work with packit and work with the (possibly adjusted) make-repo.sh tool in the tools directory. Once this is finished, and a first release out (passing minimal manual testing), immediately start the process of inclusion into RHEL8.2.

I don't think this qualifies as a one-cycle issue. The package review process itself is a 2 weeks task because it is blocked on the reviewer and we cannot anticipate his/her response time.

Yeah, but I think we should have it scheduled in the cycle to visibly allocate the time required to manage the process. I am OK with moving it to the next cycle, it's an odd one.

Sure, I'd also like to see the spec file merged, but I think this issue needs to be split in order to fit into a single cycle.

The first version of specfile is already merged, currently we need to do two things:

fix the issue with make-repo.sh (see #53)
start the review process (blocked by first release)

Good point about possibly being blocked. I think we should still try to get this done in a cycle, but if we end up blocked on external people so be it (and we'll just have to let it go over several cycles).
This issue is a bit special as the work is very async (blocked on other things), so hopefully it will be easy to do in parallel with other things.

I now tagged the first release. As to the make-repo.sh issue, will this be made easier by the specfile targeting f31, rather than f30?

I don't think it matters. But as I said I need to investigate it more.

This is close to being done, see: https://bugzilla.redhat.com/show_bug.cgi?id=1768774

I've just sent osbuild-composer to f31 updates-testing: https://bodhi.fedoraproject.org/updates/FEDORA-2019-5ba07c030a
@teg packit is still missing, but I think we should create a separate issue for this task and schedule it for later cycles. If you don't think so, feel free to reopen this issue. :)


Overblocking of Flash content

[This behavior reported by David Bellamy (david29x@gmail.com).  His email to Ed Felten is quoted below.]
The ad blocker blocks anything with flash content. It blocks an ebook( textbook on McGraw Hill's site) as ADCHOICES IDENTIFIED. The same happens on news videos on newspaper websites. The ad blocker identified parts of my Fidelity account as ADCHOICES IDENTIFIED.
It appears that any content using Flash is automatically labeled as ADCHOICES IDENTIFIED.

Can you really overblock flash?  Lol.


start template

Overview

PR Checklist

[ ] Related to designs:
[ ] Related to JIRA ticket: ABC-123
[ ] I have run this code to verify it works
[ ] This PR includes unit tests for the code change

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.e9ed3a.0@codecademy/gamut-labs@31.3.4-alpha.e9ed3a.0@codecademy/gamut@46.1.1-alpha.e9ed3a.0@codecademy/monaco@0.6.33-alpha.e9ed3a.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6254437098dd9a00808ce181--gamut-preview.netlify.appDeploy Logs

📬Published Alpha Packages:@codecademy/gamut-kit@0.6.99-alpha.70be86.0@codecademy/gamut-labs@31.3.4-alpha.70be86.0@codecademy/gamut@46.1.1-alpha.70be86.0@codecademy/monaco@0.6.33-alpha.70be86.0<EMAIL_ADDRESS>
🚀 Styleguide deploy preview ready!https://6254703b78406902c1947b97--gamut-preview.netlify.appDeploy Logs


Lazy loading: Webpack angular-router-loader error.

When I run webpack, I get these errors:
ERROR in ./ClientApp/boot-client.ts     Module build failed: TypeError: loaderUtils.getOptions is not a function         at Object.module.exports (/Volumes/Mac HDD/Documentos/Workspace/AAPB_Web/AAPB_Web/node_modules/angular-router-loader/src/index.js:12:27)
ERROR in ./ClientApp/boot-server.ts     Module build failed: TypeError: loaderUtils.getOptions is not a function         at Object.module.exports (/Volumes/Mac HDD/Documentos/Workspace/AAPB_Web/AAPB_Web/node_modules/angular-router-loader/src/index.js:12:27)
I have added the loader in the sharedConfig from the file webpack.config.js and added a chunkFilename in the output object.
const sharedConfig = {         stats: { modules: false },         context: __dirname,         resolve: { extensions: [ '.js', '.ts' ] },         output: {             filename: '[name].js',             chunkFilename: '[id].chunk.js', // Para que o lazy-loading funcione.             publicPath: '/dist/' // Webpack dev middleware, if enabled, handles requests for this URL prefix         },         module: {             rules: [                 { test: /\.ts$/, include: /ClientApp/, use: ['awesome-typescript-loader?silent=true', 'angular2-template-loader', 'angular-router-loader'] },                 { test: /\.html$/, use: 'html-loader?minimize=false' },                 { test: /\.css$/, use: [ 'to-string-loader', isDevBuild ? 'css-loader' : 'css-loader?minimize' ] },                 { test: /\.(png|jpg|jpeg|gif|svg)$/, use: 'url-loader?limit=25000' }             ]         },         plugins: [new CheckerPlugin()]     };
Do I have to add some typescript compiler configuration so that lazy loading can work?
I also added the loadChildren property in the app.routing.module:
RouterModule.forRoot([             { path: '', redirectTo: 'home', pathMatch: 'full' },             { path: 'login', component: LoginComponent },             { path: 'home', canActivate: [AuthGuardService], component: HomeComponent },             { path: 'manad', canLoad: [AuthGuardService], loadChildren: './components/manad/manad.module#ManadModule' },             { path: '**', redirectTo: 'home' }         ])
What am I doing wrong? The angular-router-loader is running on version 0.6.0. Is it a compatibility issue with the Angular 4.1.2 maybe?

Nevermind. I just found the answer. No one said I have to install the loader-utils package. So, one thing less to achieve lazy loading on Angular + Webpack.

Which version of angular-router-loader and loader-utils you are using. I tried latest versions of both but still getting this error.
"angular-router-loader": "0.6.0",
"loader-utils": "1.1.0"

@naveedahmed1 try using angular2-router-loader. People have updated the Angular template to use this one now. Maybe it's a good idea to pull this Project and compare it with your Project to see what improvements have been made. The latest version has lazy loading enabled.

Yes I tried that and it works but it seems that angular2-router-loader is now angular-router-loader. So, shouldnt we use angular-router-loader now?

@naveedahmed1 did you achieve preloading modules?    If yes, can I check your webpack.config.js that works for preloading modules and this template?
Thanks

I haven't tried preloading but I think this template by Mark has preloading enabled https://github.com/MarkPieszak/aspnetcore-angular2-universal
You might also want to take a look at upcoming template:
https://github.com/aspnet/JavaScriptServices/issues/1288#issuecomment-346003334


Tutorial for migrating from Fieldtrip

We have a tutorial for EEGLAB users. We should have the same for Fieldtrip users, as Fieldtrip is I think the second-largest software platform (and IME a bit more popular amongst MEG people).
I can't do it, I've never really used Fiedltrip.

https://www.martinos.org/mne/stable/manual/migrating.html EEGLAB tutorial here.

I've used FieldTrip mainly for time-frequency and cluster-correction, so I could try creating some examples of migration with respect to this. I wouldn't be able to do this soon however.
Currently the table for migrating from EEGlab should work well also for other migrations - one should just ignore the "EEGLAB function" column.

Related: #3201

Closing for #1495


Zdog[shapeName] is not a constructor

Thanks Alexandre for this, declarative ZDog is awesome :)
Some shapes dont work, for example for ZPath or ZBox this error pops:
[Vue warn]: Error in created hook (Promise/async): "TypeError: Zdog[shapeName] is not a constructor"

You can reproduce here: https://codesandbox.io/s/vue-template-vjc7w
Some other shapes like ZCone seems to render the wrong shape.
Also the peer dependency vue-runtimes-helpers seems required.

Also the peer dependency vue-runtimes-helpers seems required.
This is now fixed in 0.1.0.

Thanks!
As for Zdog[shapeName] error it is fixed via #3 in 0.1.1. You'll have to use ZShape instead of ZPath


Creating an uninitialized CPU-accessible buffer or image should be unsafe

Asking on IRC, it seems that uninitialized memory really is unsafe. It is an undefined behavior to read from it, and the only reason why things work today is that the compiler doesn't realize it's uninitialized.

It looks like the methods in question are already deprecated (e.g. ImmutableImage::new).
Am I correct to say this can be closed after we remove those deprecated methods?

Since the memory is allocated by Vulkan before it's exposed to Rust, from the perspective of the Rust compiler it's the same as if the Vulkan implementation had written random bytes to the memory before handing it over to Rust. I don't think they could be considered "uninitialised" in the compiler UB sense.


[Zed] Duplicate entries when searching

Extension
https://www.raycast.com/ewgenius/zed-recent-projects
Raycast Version
1.74.1
macOS Version
14.4.1
Description
When you search for a project the same project is listed twice:

Also when you search for a project which is pinned the project is listed in the pinned and recent section:

Steps To Reproduce

Open a project with Zed
Open Search Recent Project command
Search the previous opened project

Current Behaviour
The same project is listed twice.
Expected Behaviour
The same project should only be listed once.

Thanks for the report @tmwrnr! I will check that.

@raycastbot assign me


Doesn't work on mac sonoma 14.0

Workflow version
2023.3
Alfred version
5.1.3
macOS version
sonoma 14.0
Debugger output
I've tried to download several YouTube videos using the DV shortcut, and every video does download separate audio and mp4 files. Still, it doesn't stitch them together and eventually, I get the notification 'download failed to try again maybe using DP'. I do have ffmpeg codec and also updated the homebrew using fixed dependencies.

More details
I've tried to download several YouTube videos using the DV shortcut, and every video does download separate audio and mp4 files. Still, it doesn't stitch them together and eventually, I get the notification 'download failed to try again maybe using DP'. I do have ffmpeg codec and also updated the homebrew using fixed dependencies.

Your issue lies somewhere in yt-dlp. The workflow asks it to do the download and whatever you get is 100% dependent on that. Try the download manually in the terminal and report what you get in their issue tracker.
For future issues, please add the correct debugger output. Without that it’s hard to diagnose issues.

Hey Vitora thanks for the amazingly quick reply. How do I try to run the yt-dlp feature manually on the terminal?


npm test: no tests found - watchman?

Is this a bug report?
Yes
As per issue https://github.com/facebook/create-react-app/issues/2889 I'm having the same problem. The solutions in issue 2889 discuss removing the watchman path variable. Where is the path located?
If I install to the same directory where I initially installed watchman I always get the no tests found error but if I specify a new directory npm test works.

Did you try recovering your dependencies?

Yes
Which terms did you search for in User Guide?

The search terms returned the 2889 issue but the solution is not clear.
Environment

Does not work I get below output:
`Please specify the project directory:
create-react-app
For example:
create-react-app my-react-app
Run create-react-app --help to see all options.`
Steps to Reproduce

Install to project directory using npx create-react-app
CD into project
Install watchman
Run npm test and receive no tests found error
CD up 1 directory
rm -rf project
Install to project directory again using npx create-react-app
CD into project and do not install watchman
Run npm test - still no tests found

Expected Behavior

If watchman is interfering with a npx create-react-app then why after I delete the project does the problem persist if I create in the same directory again? I would expect that if watchman is the issue that a fresh create-react-app should be able to run tests. If the watchman var must be removed then where is this path located?
Actual Behavior

No tests will run if watchman has ever been installed to that folder before.
Reproducible Demo

See "Steps to Reproduce"

Did you run your tests as npm test -- --no-watchman? This is a known bug fixed in a future (unreleased) version of Jest.


Add a script to fix missing copyrights on sources and apply it

Adds tools/unix/fix-copyrights.sh which looks for sources where the copyright may have been unintentionally missed.
Noticed we'd missed a few the other day and saw this note about github sources.

Should we add a CI run that fails when this is missing?


change size of axis values

Hi,
I'm new in bqplot and I'd like to change the font size of the X axis values because they are too small (see picture).

Any solution to change it?
Many thanks in advance,
Nicolas

The solution is :
ax_x = Axis(scale=x_ord, orientation="horizontal", color = 'Blue',tick_style= {'font-size': '20px'})
It seems that there is a mistake in the help page about axis:
http://bqplot.readthedocs.io/en/stable/_generate/bqplot.axes.Axis.html
In the paragraph about tick_style, the correct example should be {'font-size': '14px'} and not {'font-size': 14}


jetracer basic motion error

sudo pip3 install --upgrade pip
sudo pip3 uninstall Adafruit-PureIO
sudo pip3 install Adafruit-PureIO
We already tried this, but the error has not solved.
Please help ;n;

Hi~!
I'm using Waveshare JetRacer.
-----Original Message-----
From: "Chitoku<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Sent: 2021-03-10 (수) 16:19:42 (GMT+09:00)
Subject: Re: [NVIDIA-AI-IOT/jetracer] jetracer basic motion error (#94)
Hi jackey42,
Can you tell me what vehicle hardware you are using?
(Latrax? Tamiya? or Waveshare JetRacer? Waveshare JetRacer Pro?)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

use waveshare image，and deploy patches for specific hardware.

Hi jackey42,
As zinwalin suggested, please check out the Waveshare image which they also posted in this issue here.
https://github.com/NVIDIA-AI-IOT/jetracer/issues/96

Hello jackey42
Met same errors with JetRacer Pro. So my conditions are:

JetRacer Pro https://www.waveshare.com/wiki/JetRacer_Pro_AI_Kit

jetcard_nano-4gb-jp451 https://doc-0c-bc-docs.googleusercontent.com/docs/securesc/oca2mgdh5rj4h8hbtk0do6b37cs03g8n/rqmq8oajntfduih3euka329cmkam653k/1619391975000/08570363794112935001/15224068068018828316/1MX-z7ZCPvUzpN3nGhfZMAgENtK6VnBdh?e=download&authuser=0&nonce=4tsnrhoii3rl4&user=15224068068018828316&hash=8me5382sk3s71098iksrdem94gv256n9

Jetson Nano (A02) 4GB

branch ws/pro https://github.com/waveshare/jetracer/tree/ws/pro

With this branch I can get basic motions notebook about fully working execpt backward motion. It can move forward like normal jetracer do, but moves backward with 'donkeycar' scheme 'Reverse on RC cars is a little tricky because the ESC must receive a reverse pulse, zero pulse, reverse pulse to start to go backwards.' as described at https://docs.donkeycar.com/guide/calibrate/
BR, Ed.


Delete the SQLEngine after migrate V1SingleEntryEngine to JDBI

Once we move the V1SingleEntryEngine to use JDBI instead of SQLEngine, we can delete the SQLEngine class.

sql engine is gone, closing


Cleanup unused providers

Cleanup unused providers.
Removes the keycloak module from the addons folder as it is broken. It still contained data references to a structure that no longer exists and is broken. I've not deleted the generic keycloak modules, but the end-user facing add-on only created confusion.
Cleans up a bit the eshop gitops config, leveraging argocd waves to have the files nicely split.
Adds the argocd_include_example_apps variable to allow installing ArgoCD without the example applications. This is very useful to have ArgoCD installed in all the clusters but without applications, so users can just configure their own apps for their own repos (by default example apps will still be installed).

agree, technically we should have keycloak as argocd construct,


browser no response when use igv web

why I click the igv web page  several times, and then the browser no response

Do you mean https://igv.org/app? It's working for me.

Do you mean https://igv.org/app? It's working for me.

Yeah, It's also working for me. But when I use tracks module to view my bam file. It happens when I click the bam area several times.

We can try to help If you give us precise details of what you did and what you see - including what data you loaded and how, and what you did after loading the data, and at what point IGV stopped behaving as expected and how. Screenshots might help too.

We can try to help If you give us precise details of what you did and what you see - including what data you loaded and how, and what you did after loading the data, and at what point IGV stopped behaving as expected and how. Screenshots might help too.

thanks, I will provide them as soon as possible

We can try to help If you give us precise details of what you did and what you see - including what data you loaded and how, and what you did after loading the data, and at what point IGV stopped behaving as expected and how. Screenshots might help too.

thanks, I will provide them as soon as possible

hello，

We can try to help If you give us precise details of what you did and what you see - including what data you loaded and how, and what you did after loading the data, and at what point IGV stopped behaving as expected and how. Screenshots might help too.

hello helgathorv, the detail is when I click this area several times.

then, the browser begin no response

Hmm. I don't know why it's not responding - I can't reproduce it with any of the data I've tried loading.
But first, it will be helpful to know what are you hoping to accomplish by clicking in this area multiple times. Double-clicking would normally zoom in, but you're zoomed in to the max (40 bp). Or are you single clicking to bring up the popup info?
To further debug this, we can try a couple of different things:
If you are familiar with the web browser developer tools, there might be some clues if you open up the console.
Or if your data is available to me via URL, you can share your session with me and I can take look. Click Share, then copy the tinyurl you see in the dialog that pops up and send it to me at<EMAIL_ADDRESS>

Hmm. I don't know why it's not responding - I can't reproduce it with any of the data I've tried loading.
But first, it will be helpful to know what are you hoping to accomplish by clicking in this area multiple times. Double-clicking would normally zoom in, but you're zoomed in to the max (40 bp). Or are you single clicking to bring up the popup info?
To further debug this, we can try a couple of different things:
If you are familiar with the web browser developer tools, there might be some clues if you open up the console.
Or if your data is available to me via URL, you can share your session with me and I can take look. Click Share, then copy the tinyurl you see in the dialog that pops up and send it to me at<EMAIL_ADDRESS>
I probably know what caused this problem. You can try click the base then the browser will no response. I think it has nothing to do with the data.

Hmm. I don't know why it's not responding - I can't reproduce it with any of the data I've tried loading.
But first, it will be helpful to know what are you hoping to accomplish by clicking in this area multiple times. Double-clicking would normally zoom in, but you're zoomed in to the max (40 bp). Or are you single clicking to bring up the popup info?
To further debug this, we can try a couple of different things:
If you are familiar with the web browser developer tools, there might be some clues if you open up the console.
Or if your data is available to me via URL, you can share your session with me and I can take look. Click Share, then copy the tinyurl you see in the dialog that pops up and send it to me at<EMAIL_ADDRESS>
I probably know what caused this problem. You can try click the base then the browser will no response. I think it has nothing to do with the data.

such as

Hmm. I don't know why it's not responding - I can't reproduce it with any of the data I've tried loading.
But first, it will be helpful to know what are you hoping to accomplish by clicking in this area multiple times. Double-clicking would normally zoom in, but you're zoomed in to the max (40 bp). Or are you single clicking to bring up the popup info?
To further debug this, we can try a couple of different things:
If you are familiar with the web browser developer tools, there might be some clues if you open up the console.
Or if your data is available to me via URL, you can share your session with me and I can take look. Click Share, then copy the tinyurl you see in the dialog that pops up and send it to me at<EMAIL_ADDRESS>
I probably know what caused this problem. You can try click the base then the browser will no response. I think it has nothing to do with the data. Because I test a lot of data I have.

I am not able to reproduce the error with any of the data I've tried loading. If you can reproduce it with one of the hosted tracks, or with public data that you can point me to, then I can take a look.

OK，I will share my data by the email which you provided. You can have a try.

Hello, helgathorv. Have you received my data and tested it based on this data.

@transorigin I apologize, there was a typo in the email address I gave you - it should be<EMAIL_ADDRESS>(note the '-'). The other email address does not exist, so I did not receive your email - in fact you should have received a failed delivery notice.
Note that when you send to the corrected address, you will receive an auto-reply about the preferred way to contact the IGV team. Please just ignore that message, but when you see it, you will know that your email was delivered.

@transorigin I apologize, there was a typo in the email address I gave you - it should be<EMAIL_ADDRESS>(note the '-'). The other email address does not exist, so I did not receive your email - in fact you should have received a failed delivery notice.
Note that when you send to the corrected address, you will receive an auto-reply about the preferred way to contact the IGV team. Please just ignore that message, but when you see it, you will know that your email was delivered.

OK, I have resent the data to you. Please check.

We received the test data and can reproduce the issue.   It is specific to this data, or data like this,  and I think is related to array values in the alignment tags.   The fix will require an igv update, we will update this issue when that happens.

We received the test data and can reproduce the issue. It is specific to this data, or data like this, and I think is related to array values in the alignment tags. The fix will require an igv update, we will update this issue when that happens.

If this problem is fixed please let me know, thanks.


Slightly fix coin.cfg.cmake.in

Slightly fixes coin-config support under CMake buildsystem - only paths and features.
Still does not support -DHAVE_MULTIPLE_VERSION=ON
Related to https://github.com/coin3d/coin/issues/131
Also fixes underlinking against X11 which is used in glx_glue but never explicitly declared to be used, hence when it comes implicitly with -lGLX, it's dropped by --as-needed.

Thanks for the patches. I can't merge them right now as I'm away over the next two weeks and won't try to break things. Will check then properly and report back.


ListCarriers() throws 500 error - System.Text.Json.JsonException: A possible object cycle was detected.

Seems like some kind of mapping/serialization issue. I'm using  ShipEngine nuget package v 1.0.1.
Here is my code, using .net6/vs2022:
var shipEngine = new ShipEngine(shipEngineApiKey);
var carriers = await shipEngine.ListCarriers();
"carriers" is returning a JsonException:
System.Text.Json.JsonException: A possible object cycle was detected. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 32. Consider using ReferenceHandler.Preserve on JsonSerializerOptions to support cycles. Path: $.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.MoveNextAction.Target.

So sorry - I was missing the await in the controller using my method.