React to runtime/594 Encoder.Convert change

https://github.com/dotnet/runtime/issues/594 is reverting a 3.1 fix to encoders for compat reasons. That might have side-effects for our use of encoders so we're pre-emptively updating AspNetCore as well.
This change works because we know WriteMultiSegmentEncoded is always called with a complete string, there's no tearing, so we can always flush the encoder.

👀

@aspnet/build we've done away with patchconfig stuff, right?

@GrabYourPitchforks I thought you had detailed two affected locations?

@GrabYourPitchforks I thought you had detailed two affected locations?

@Pilchie we reviewed the other two uses of this API and determined that they were not affected by the change.

@Pilchie I believe this is the only location that would be affected by the 3.1.1 change. I had called out another location that has a buggy call site, but that second call site is buggy regardless of which runtime it's running against. The 3.1.1 change won't affect it.

@aspnet/build we've done away with patchconfig stuff, right?

We've done so in 3.0, but haven't merged that forward to 3.1 yet: https://github.com/aspnet/AspNetCore/blob/9a4ab80f7e068e30da5ea3c819b546b511b64302/Directory.Build.targets#L61-L64
We intend to merge it forward with the rest of https://github.com/aspnet/AspNetCore/pull/17311 (CC @dougbu @JunTaoLuo)

@mmitche Any reason not to merge this?  @GrabYourPitchforks are the other changes ready/merged?

@mmitche Any reason not to merge this? @GrabYourPitchforks are the other changes ready/merged?

They aren't ready yet. I think we should hold those changes for 3.1.2.

@Pilchie is this approved? It still has servicing-consider, so I've put it in 3.1.x since we generally don't put things in a specific patch milestone until they're approved.

Not approved for 3.1.1

It's been conceptually approved at Tactics, but that was before the PR was actually created.  However, as @mmitche says, we'll hold it from 3.1.1 at this point as the base changes aren't going to make 3.1.1.

It's been conceptually approved at Tactics, but that was before the PR was actually created. However, as @mmitche says, we'll hold it from 3.1.1 at this point as the base changes aren't going to make 3.1.1.

I guess my question is this: Does tactics need to further review this change? If no, we can mark servicing-approved and move to 3.1.2 to resolve the confusion (it's clear that it needs no further approval from Tactics, but does need to wait until the branch is open for 3.1.2-approved changes). If yes, we leave it as-is (servicing-consider and 3.1.x) :).

I'm going to bring up the slip to 3.1.2 in Tactics tomorrow to make sure everyone is aware. Once that happens, we'll move to servicing-approved and 3.1.2.

Putting * NO MERGE* (not that it does much) just to make clear that the branch is not open for 3.1.2 changes yet.

Approved for 3.1.2

Moved to Mar as per Tactics. Will need to be explicitly approved for Feb, if required.

@anurse I believe this got bumped back to feb now. Please confirm when you have the chance 😄

Correct, but @Tratcher I believe this is reacting to a change that hasn't actually happened in runtime's 3.1.x branch. Can you check on that?

@GrabYourPitchforks?


Update index.md

Open parenthesis in the wrong place
Proposed changes
Fix the incorrectly located parenthesis

Deploy preview for docsdocker ready!
Built with commit 968300a50630bf6dbdef2f5d968b87a4a007e75a
https://deploy-preview-8508--docsdocker.netlify.com


Update accessing-boards.rst

Added icon for Product Menu based on user feedback.

Thanks, @justinegeffen! Could you add an inline Boards icon image as well for step #2, please, given that there's 2 ways to get to boards and users would benefit from seeing visual examples of both.


refacore: Move all webpack.*.js to .webpack folder

This is cleaner to have .webpack or webpack folder where all the webpack configs will live. Need to change npm scripts too

May I tackle this?

sure 👍

@anikethsaha
Is this issue work in progress or still no one picked?

No one picked as of now. Feel free to take it

Hi! is this issue opened ?

Can I join to this task and contribute with someone more? This will be my first contribution.

Hi, this issue has been fixed now.


ModelManagementBean seems redundant

https://github.com/GLAProject/Auction/blob/master/Auction-ejb/src/main/java/com/ul/session/ModelManagementBean.java
ModelManagementBean just seems like an unnecessary wrapper for Bid, Article and Person. Is there a reason to use/have this?

The goal is to follow the "façade" design pattern - to have a single entry point for any program wishing to interact with the entities.
It was a suggestion by Nicolas, and Armand and I agreed.
The main benefits are:

Calling programs only need to inject the ModelManager instead of a myriad of entity managers.
It hides the implementation of the entity managers from the calling programs.

I think we should keep it.


Komga issue with encoding with s6-supervise

Komga is not working properly under the s6-supervise program. The problem is when adding comics with special character:
java.nio.file.InvalidPathException: Malformed input or input contains unmappable characters:
It seems this is has to do with encoding as launching komga from normal user (appbox or root) is working fine.
I am not familiar with s6-supervice so not sure where to look for this issue.

The problem is in the locale when s6 supervisor is launched. On my box it is POSIX instead of UTF-8 (as my appbox user). So the script should be run with s6-envdir (with a directory of ENV files) but I find it not very elegant. Not sure if you have a better solution for this issue.


Error in invokeChaincode when invoke method in the same chaincode

Environment: fabric release-2.2
My chaincode named vulnerable is as follows:

When I invoke helloworld directly, it gives me responce "helloworld", everything works fine.
When I invoke invokeDirectly, it also gives me responce "helloworld".
But when I invoke invokeSameContract method, it gives me

and chaincode docker container logging is as follows:

Observation of results above:
(1) the statement System.out.printf("\n%s\n", chaincodeName) works fine.
(2) org.hyperledger.fabric.shim.impl.InvocationStubImpl.invokeChaincode has reached the statement final ByteString response = this.handler.invoke(invokeChaincodeMessage);.

Sorry for the interruption. It’s a mistake, the function name should be the first arguments.


Demo Application Crash on Windows 10 Run

No exact replication procedures, as I do not remember all the steps. But the gist of it was that I destroyed the top fish, let the sub take damage, each time hitting the Save button. Move the sub around, saved, crash happened around that point.

I can unfortunately not reproduce this. Also the the screenshot would indicate a problem during loading while you wrote that the problem occurred during saving.  It would really help if you could provide a list of steps to reproduce the issue. Also which branch are you running?


[Fixes #354] fixes CubicFermionicSimulationGate.value_equality_values

The gate actually is periodic, but only when all the weights are shifted by the same amount. This quick fix avoids false positives.


Conflicting Issue!

The conflict is caused by:
docscan 1.0.4 depends on rembg==1.0.10
docscan 1.0.3 depends on rembg==1.0.9
docscan 1.0.2 depends on rembg==1.0.7
To fix this you could try to:

loosen the range of package versions you've specified
remove package versions to allow pip attempt to solve the dependency conflict

And I am not able to install the above version of rembg. @danielgatis  I think the old version rembg has been removed, yet docscan is not updated yet. Need solution for this!

fixed! ;)
try to install it again!


Allow to use the builder with jsdoc

Today if we run:
module.exports = ({ builder }) => {
   // builder. do not have any intellisense
}

Seems interesting, kindly assign me this issue would love to work on it ! @raphaelkieling

To enable IntelliSense support for JSDoc in JavaScript code that uses a builder function, we can provide type information and documentation through JSDoc comments. Here's an example of how we can achieve this:
/**
 * @param {Object} options - The options object.
 * @param {function} options.builder - The builder function.
 */
module.exports = ({ builder }) => {
   // Now, you should have IntelliSense support for 'builder'.
   builder.someMethod(); // IntelliSense should work here.
}

Above, we use @param to describe the parameter options, which is an object. Within this object, we specify that builder is a function. By providing this information, we should get IntelliSense support for the builder function and its methods.

This is very interesting and a very good first step, but i suppose that this @param should make reference for our real Builder to have any king of IntelliSense like:
/**
 * @param {object} params - config params
 * @param {import("../src/index").Builder} params.builder - the builder instance
 */
module.exports = ({ builder }) => {
   // Now, you should have IntelliSense support for 'builder'.
   builder.someMethod(); // IntelliSense should work here.
}

It works perfectly 😄
But we have some small issues here. Today the idea would be to avoid require the user to install the tool locally since we do not have any huge advantage doing it. It means that it will work only for who installed in their dependencies? Since they need to use the flah import("doctorenv-cli") i suppose.
/**
 * @param {object} params - config params
 * @param {import("doctorenv-cli").Builder} params.builder - the builder instance
 */
module.exports = ({ builder }) => {
   // Now, you should have IntelliSense support for 'builder'.
   builder.someMethod(); // IntelliSense should work here.
}

Final thoughts:

Should it be a recommendation? Install locally if you want intellisense?
Is it possible to have remote objects? Like an object from an external URL, with this the dev will not need to install the library to use the intellisense

What do you think?

Recommendation to Install Locally:

It's a good idea to suggest that users install a library locally if they want to have better code suggestions (IntelliSense) while using it. It makes their development experience smoother.

Remote Objects for IntelliSense:

Providing code suggestions for libraries not installed locally can be tricky. Typically, users can install type information separately to enable IntelliSense. There isn't a common way to offer IntelliSense for remote libraries without some local setup. However, some online tools might help with this in specific situations.


Taskbarx losing blur, needs restart to fix

Store or Regular version: Store version
What's your Build of Windows 10: Build 18362.19h1_release.190318-1202
.NET Framework 4.8 installed: Yes
Any Antivirus software: No
Any other third-party taskbar tweakers: No
Is there a way i can reproduce: No
What are your taskbar settings: Only speed change to 100ms
What says the error message if you got any: No error message
Taskbar loses its blur randomly and then I can only get it back after a force quit from configuratorx.

I am also experiencing a similar issue. The blur and acrylic features do not work at all and both function as transparent. I am unable to get them to work even after restart of app and computer. However, if I click on the start button it seems to restore blur and acrylic functions

I can also confirm this, I also had this problem with a rainmeter-transparent taskbar skin as well (I'm no longer using rainmeter-transparent taskbar skin). The blur disappears completely and goes fully transparent sometimes. So far I've fixed it by restarting TaskbarX.
What's your Build of Windows 10: Build 18363.836
.NET Framework 4.8 installed: Yes
Any Antivirus software: Yes
Any other third-party taskbar tweakers: No
Is there a way I can reproduce: No
What are your taskbar settings: Only speed change to 500ms, Animationspeed changed to 250ms
What says the error message if you got any: No error message

You guys should try out 1.5.7. It has fixed this issue for me. https://github.com/ChrisAnd1998/TaskbarX/releases/tag/<IP_ADDRESS>

You guys should try out 1.5.7. It has fixed this issue for me. https://github.com/ChrisAnd1998/TaskbarX/releases/tag/<IP_ADDRESS>

Just uninstalled the old release and installed this, still the same problem. Although I've found a way to possibly reproduce the problem. If windows taskbar settings are set to "Automatically hide the taskbar in desktop mode" = true, then by switching on and off with "Use small taskbar buttons" (note: just spam that switch-button) I was able to make the problem both returning and going away.

@ChrisAnd1998 You can close this imho. For me it's gone since 1.6.10.


npm start command is not working

if you use raspberry pi
use
sudo apt-get install npm
sudo npm install -g npm@latest
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"

Thank you so much..
On Thu, Mar 14, 2019 at 6:43 PM ad7608327<EMAIL_ADDRESS>wrote:

if you use raspberry pi
use
sudo apt-get install npm
sudo npm install -g npm@latest
bash -c "$(curl -sL
https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh
)"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/HackerShackOfficial/AI-Smart-Mirror/issues/68#issuecomment-472847363,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AjNR6lTFw4W4pr95x5ek3uRD8gLk-BBWks5vWkr5gaJpZM4SeEAF
.


gawk is an unspecified dependency

It looks like gawk is utilized explicitly in speedseq, but not currently listed as a prerequisite. I'm seeing errors in a Docker image where I did not explicitly install gawk.

thanks Dave, added it to the README


Fixed bad bindings

Fixes #14532

That only fixes the first two errors in #14532, not the rest, does it?

Nevermind, I tested and all errors are fixed 👍


Updated Julia notebook to run Julia 1.0.

Updated Julia notebook to run Julia 1.0.
Also added a tiny bit more explanation about what PyPlot is.
For https://github.com/binder-examples/multi-language-demo/pull/5.

Oops, I was hoping this package had CI, so I didn't actually run this myself... Sorry, i've broken the build with a typo! Lemme try again...

@betatim I've opened #7 to fix it. Running the tests there now.


Suggestion: replace docker stack deploy

This is more of an architectural suggestion if since you're going down this path.
Can you consider being a replacement for docker stack deploy as well.

For one, if you do you can fix the issue where we have to fix a Docker Compose spec file that's generated from docker compose convert
Second you can probably implement it such that Error response from daemon: rpc error: code = Unknown desc = update out of sequence no longer happens.

I think this issue should be filed against https://github.com/neuroforgede/docker-stack-deploy


Change unsafe_packages

Sounds strage, perhaps something better would be allowed_packages, safe_packages.

Fine for now as this is in line with the safe_licenses setting


5 person limit in happyhours site

Hi,
I've create 6 accounts under my domain name in happyhours.io and I didn't receive any alert for using too many accounts. It is mentioned in your web page that only teams up to 5 persons can use this product freely. I want to know if it is a software bug, or I can use this product with how many users I want.
Also, I deployed this project using heroku button but I couldn't figure out how to signup.
Thanks.

It's not a hard limit, if you have 6 users that's fine, it's not a software bug :)
To set up the first user in Single Tenant mode (which the heroku button uses by default) you can use the rake create_user task.

It's not a hard limit, if you have 6 users that's fine, it's not a software bug :)
To set up the first user in Single Tenant mode (which the heroku button uses by default) you can use the rake create_user task.

Thanks.


rename gitops run objects and add metadata

Fixes #2813

rename objects to run-dev-bucket, and run-dev-ks
add metadata to run-dev-bucket and run-dev-ks
rename dev-bucket server namespace to gitops-run
add a hidden flag --x-session-name to pass down the session name to the sub-process

Signed-off-by: Chanwit Kaewkasi<EMAIL_ADDRESS>


Segmentation fault for Python 3.9 for video

🐛 Bug

To Reproduce
Steps to reproduce the behavior:
Build torchvision for the latest version using python 3.9 with the latest pytorch nightly, run pytest -v test/test_video.py.
Output:
vision39 ❯ pytest -v test/test_video.py
================================================================================ test session starts =================================================================================
platform linux -- Python 3.9.1, pytest-6.2.2, py-1.10.0, pluggy-0.12.0 -- /home/eliuriegas/miniconda3/envs/vision39/bin/python
cachedir: .pytest_cache
rootdir: /home/eliuriegas/work/vision
plugins: cov-2.11.1
collected 3 items

test/test_video.py::TestVideo::test_metadata PASSED                                                                                [ 33%]
test/test_video.py::TestVideo::test_read_video_tensor Fatal Python error: Segmentation fault

Current thread 0x00007f618a834740 (most recent call first):
  File "/home/eliuriegas/work/vision/torchvision/io/__init__.py", line 123 in __next__
  File "/home/eliuriegas/work/vision/test/test_video.py", line 296 in test_read_video_tensor
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/unittest/case.py", line 550 in _callTestMethod
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/unittest/case.py", line 593 in run
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/unittest/case.py", line 653 in __call__
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/unittest.py", line 321 in runtest
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/runner.py", line 162 in pytest_runtest_call
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/manager.py", line 78 in <lambda>
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/manager.py", line 87 in _hookexec
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/hooks.py", line 289 in __call__
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/runner.py", line 255 in <lambda>
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/runner.py", line 311 in from_call
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/runner.py", line 254 in call_runtest_hook
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/runner.py", line 215 in call_and_report
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/runner.py", line 126 in runtestprotocol
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/runner.py", line 109 in pytest_runtest_protocol
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/manager.py", line 78 in <lambda>
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/manager.py", line 87 in _hookexec
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/hooks.py", line 289 in __call__
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/main.py", line 348 in pytest_runtestloop
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/manager.py", line 78 in <lambda>
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/manager.py", line 87 in _hookexec
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/hooks.py", line 289 in __call__
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/main.py", line 323 in _main
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/main.py", line 269 in wrap_session
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/main.py", line 316 in pytest_cmdline_main
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/callers.py", line 187 in _multicall
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/manager.py", line 78 in <lambda>
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/manager.py", line 87 in _hookexec
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/pluggy/hooks.py", line 289 in __call__
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/config/__init__.py", line 162 in main
  File "/home/eliuriegas/miniconda3/envs/vision39/lib/python3.9/site-packages/_pytest/config/__init__.py", line 185 in console_main
  File "/home/eliuriegas/miniconda3/envs/vision39/bin/pytest", line 11 in <module>
zsh: segmentation fault (core dumped)  pytest -v test/test_video.py

Expected behavior

No segmentation fault
Environment
Please copy and paste the output from our
environment collection script
(or fill out the checklist below manually).
You can get the script and run it with:
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

vision39 ❯ python -m torch.utils.collect_env
Collecting environment information...
PyTorch version: 1.8.0
Is debug build: False
CUDA used to build PyTorch: 11.2
ROCM used to build PyTorch: N/A

OS: Fedora release 33 (Thirty Three) (x86_64)
GCC version: (GCC) 10.2.1 20201125 (Red Hat 10.2.1-9)
Clang version: 11.0.0 (Fedora 11.0.0-2.fc33)
CMake version: version 3.18.4

Python version: 3.9 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: Quadro P4000
Nvidia driver version: 460.32.03
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.20.0
[pip3] torch==1.8.0
[pip3] torchvision==0.9.0a0+81d47c3
[conda] blas                      2.108                       mkl    conda-forge
[conda] blas-devel                3.9.0                     8_mkl    conda-forge
[conda] cudatoolkit               11.2.0               h73cb219_7    conda-forge
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] libblas                   3.9.0                     8_mkl    conda-forge
[conda] libcblas                  3.9.0                     8_mkl    conda-forge
[conda] liblapack                 3.9.0                     8_mkl    conda-forge
[conda] liblapacke                3.9.0                     8_mkl    conda-forge
[conda] mkl                       2020.4             h726a3e6_304    conda-forge
[conda] mkl-devel                 2020.4             ha770c72_305    conda-forge
[conda] mkl-include               2020.4             h726a3e6_304    conda-forge
[conda] numpy                     1.20.0           py39hdbf815f_0    conda-forge
[conda] pytorch                   1.8.0           py3.9_cuda112_cudnn8.1.0_0    pytorch-test
[conda] torchvision               0.9.0a0+81d47c3           dev_0    <develop>

Additional context

This was found as part of the effort to introduce Python 3.9 to the main branch here: https://github.com/pytorch/vision/pull/3341
cc @fmassa @andfoy

Which FFmpeg did you use?

Should be this one:
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch

cc @bjuncek as the segmentation fault happens in the new VideoReader implementation

I think @seemethere  installed the faulty 4.3 FFmpeg version

I think that's the issue - I've just build tv with 3.9 and my legacy 4.2 from and it passes for me.
I'll try the one from pytorch channel as well just to make sure

@seemethere for reference, in https://github.com/pytorch/vision/issues/2650#issuecomment-694915626 we found out that the 4.3 version of FFmpeg (which was present in conda unfortunately). Using FFmpeg 4.2 fixes the issue.

If everyone agrees, I'll document this in #3460 and close this issue.

@prabhat00155 should we reopen this? Or create a new issue?
Looks like  #3460 which was supposed to supersede this one hasn't been addressed yet, and it would be nice to have an issue that tracks the 3.9 problems since we deactivated the builds in https://github.com/pytorch/vision/pull/4417

@NicolasHug I think we should either augment the #3460 or start a new issue;
segfault here is 90% due to the broken ffmpeg version. Segfaults we've started seeing now seem altogether different (and am not 100% sure what they're about - I'll be syncing with Prabhat in a bit to double check

@NicolasHug I have created an issue to track it here: https://github.com/pytorch/vision/issues/4430


🐾 Add pods tab to overview page

Forklift operator pod logs:
We ask users to look at the "operator pod" logs, but do not provide an easy to use way to get into the controller pods,
this PR adds a link to the controller pods from the overview page.

addressed by https://github.com/kubev2v/forklift-console-plugin/pull/932


Download script won't work on wsl/windows

Issue: Automated Data Collection and Preparation on WSL/Windows
Problem Description:
I have encountered an issue with my data collection and preparation script, specifically when running it on Windows Subsystem for Linux (WSL)/Windows environment. My project involves downloading datasets from Kaggle and automating data preparation, which works perfectly fine on my local machine and Ubuntu 22.04 VMs. However, when I attempt to execute the download script (setup.py, now renamed to processor.py) on WSL/Windows, it fails to run automatically.
Objective:
My primary goal is to enable seamless data collection and preparation, not only on Ubuntu 22.04 but also on Windows Subsystem for Linux (WSL) and native Windows environments.
Temporary Solution:
As a temporary workaround, I have devised a solution that involves directly downloading the dataset from Kaggle and subsequently running processor.py to validate the data. After this step, users must execute src/validator.py to create a ready-to-use dataset, which can then be utilized in other notebooks within the project.
Request for Assistance:
I am seeking assistance in resolving this issue to ensure that the data collection and preparation process can run smoothly on WSL/Windows, just as it does on other platforms.
Additional Information:

Environment Details:

Operating System: Windows 10 and 11
Python Version: Any
Kaggle Dataset: See dataset here

Temporary Solution: [WARNING] This is a Temporary Solution
Dataset Download
To download the dataset, use the provided download.sh script:
bash src/download.sh

This script simplifies the dataset download process.
Environment Setup
First, let's identify the available Python version:
if command -v python3 &>/dev/null; then
    PYTHON_CMD="python3"
    PIP_CMD="python3 -m pip"
else
    PYTHON_CMD="python"
    PIP_CMD="python -m pip"
fi

Use the $PYTHON_CMD and $PIP_CMD variables for various commands, such as installing required packages:
$PIP_CMD install -r requirements.txt

Dataset Verification and Configuration
Ensure the dataset's integrity and configure it:
$PYTHON_CMD processor.py

Additional Setup (Troubleshooting)
In case of errors:

Download the dataset directly from Kaggle.
Place it in the data/ folder.
Re-run processor.py.

For further troubleshooting, navigate to the src/ folder and execute the following:
cd src
$PYTHON_CMD validator.py

Unsetting Environment Variables
Once the setup is complete:
unset PYTHON_CMD
unset PIP_CMD

Detailed Instructions
For more comprehensive instructions, please consult the prerequisites.md  files available in the project repository.
Important Note:
This solution is temporary and intended for resolving specific issues. It is not the final solution to the underlying problem. Further investigation and improvements are needed for a permanent fix.


Escaping characters in docstring raises DOC103

This is more a question than an issue (I'm sorry for opening my third issue in a week's time...).
I am on the brink of adding pydoclint to my company's codebase (started at 1000 issues.... now down to 1), but the only way I'm able to is by excluding the file via pre-commit.
I have the following class:
class Foo:
    r"""Description

    Args:
        with\_ (dict): Description
        select (str): Description
    """
    def __init__(self, with_: dict, select: str):
        ...

pydoclint imo correctly raises:
    8: DOC103: Method `Foo.__init__`: Docstring arguments are different from function arguments.
(Or could be other formatting issues: https://jsh9.github.io/pydoclint/violation_codes.html#notes-on-doc103 ).
Arguments in the function signature but not in the docstring: [with_: dict]. Arguments in the docstring but
not in the function signature: [with\_: dict].

If I try to remove the \ before the underscore, sphinx complains:
$ .Foo:7: ERROR: Unknown target name: "with".
...and the documentation shows with instead of with_.
Do you have a suggested approach here (outside excluding the entire file?) 🙏

Hi @haakonvt , thanks for raising this issue!
I didn't know that Sphinx requires escaping underscores.  And interestingly, only 1 or 2 trailing underscores need to be escaped.  3 or more trailing underscores and preceding underscores don't seem to need to be escaped.
I've pushed a fix and it will be published as v0.2.2.

That's great! Thanks a lot (again) @jsh9 🙏 👏


override autocompletion bug

Doesn't autocomplete in the current class: https://youtu.be/p3xH3aj35Ls
ST version 3095 on Fedora 22

/OmniSharp/Overrides/OverrideHandler.cs from line 111
should be modified like this:
var firstNode =
typeDeclaration.Children.FIrst();
script.InsertAfter
(     node        :  firstNode
,  newNode :  memberDeclaration);

Closing due to having outdated information.


fix(extra765/776): Add right region to CSV if access is denied

Context
If access is denied on checks extra765 or extra776 currently no region is specified.
In the CSV output those checks then default to a different/wrong region.
Description
Add region parameter to textInfo call.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

thanks @roman-mueller


Reg cocktails apt1.0+preprocessing

Additionally the dropout shape should be funnel

additionally if I am not mistaken for Lucas's code the beta1 and beta2 were also fixed for adam.

True they did not have them in the search space. They were using pytorch defaults


Updates

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

Comparison is base (c705306) 91.90% compared to head (f4de461) 91.90%.

Files
Patch %
Lines

src/fast_scram.erl
0.00%
1 Missing :warning:

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #12   +/-   ##
=======================================
  Coverage   91.90%   91.90%
=======================================
  Files           5        5
  Lines         321      321
=======================================
  Hits          295      295
  Misses         26       26

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


update fastlane

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 1 vulnerabilities in the rubygems dependencies of this project.
Snyk changed the following file(s):

fastlane/Gemfile.lock

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Denial of Service (DoS) SNYK-RUBY-REXML-7462086
  551

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)
Release Note
NONE

No major changes, so looks good. Should we run an iOS build to be certain?

This just updates the scripts platform to build the app


Plaquette circuit expressed as QASM

In the frontend v2, every type of plaquette is associated to the circuit measuring the stabilizer.
The circuit are currently represented via a ASCII art like:
X( 0, 0): ---------X--------------
                   |
Z( 2, 0): ---------|---*----------
                   |   |
A( 1, 1): |0> -H---*---*---H-- D~
          ___ ___ ___ ___ ___ ___
time ruler 0   1   2   3   4   5

As we discussed in the weekly call, it would be great to express the circuit in the QASM language (in substitution of the ASCII art or, even better, in addition to it).
The circuit is drawn by the utility function createCircuitAsciiArt() in <repo>/frontend_v2/src/workspace/circuit.js.
It would be great having a similar one to create the equivalent QASM code.
If QASM and ASCII are complementary, we need functions to keep the representations in sync:

from QASM to ASCII
from ASCII to QASM
The former may be sufficient if we allow the user to modify the QASM code and use the ASCII art as a visual confirmation.

I think the user data (plaquettes/qubits/circuits) can be mastered in JSON, and we can write a custom serializer that maps this JSON to OpenQASM. I don't think that's a bijective mapping, though.

I think the user data (plaquettes/qubits/circuits) can be mastered in JSON, and we can write a custom serializer that maps this JSON to OpenQASM. I don't think that's a bijective mapping, though.

For OpenQASM (2.X or 3.X), the only thing that makes this mapping non-bijective is the fact that OpenQASM has no native support for qubit coordinates. With that exception, and knowing that the detectors will ultimately be computed automatically, I think that it should be fine, but I would need to implement it to be sure there is not a small detail I am missing that would break that.
Also, Stim file format supports natively both qubit coordinates and detectors.

I will work on adding the stim code.

I will work on adding the stim code.

See PR https://github.com/QCHackers/tqec/pull/192


Added Docker 1.13 MAINTAINER deprecation

Coverage increased (+0.002%) to 99.103% when pulling 1cca5fac092006e732092f458b7f6d41d7c42bf2 on sameetn:master into 824fd7543a390b429296895ed881dd3030e308ca on replicatedhq:master.

Coverage increased (+0.002%) to 99.103% when pulling 1cca5fac092006e732092f458b7f6d41d7c42bf2 on sameetn:master into 824fd7543a390b429296895ed881dd3030e308ca on replicatedhq:master.

Never forget to add docs for you work ;)
The README.md like updates ;)

Coverage increased (+0.002%) to 99.103% when pulling a1a1838e23f26aa58550f4ad90aa374c0747dbdb on sameetn:master into 824fd7543a390b429296895ed881dd3030e308ca on replicatedhq:master.


filter out outdated MLE advertisement from old partition

As discussed in spec-660, the outdated MLE advertisement from old partition should be filtered out when the recipient is in new partition.
Resolved 5.1.4 failing when interop with NXP and unstable 9.2.9 found during R2(DEV-1194)

Current coverage is 70.18% (diff: 83.33%)

Merging #1155 into master will decrease coverage by 3.42%

@@             master      #1155   diff @@
==========================================
  Files           128        127      -1
  Lines         17586      18918   +1332
  Methods        2492       2650    +158
  Messages          0          0
  Branches       2124       2307    +183
==========================================
+ Hits          12946      13278    +332
- Misses         3830       4770    +940
- Partials        810        870     +60

Powered by Codecov. Last update ab866ee...80f6ece


Use an AutoResetEvent instead of a Monitor in TestScheduler.WithScheduler

This prevents TestScheduler.WithAsync from throwing a SynchronizationLockExceptionObject exception, because we can't await inside a Monitor

Thanks @flagbug!


Allow comparing locations

The colors are problematic but not quite sure how to make it better. I think I should allow different types of stippling to distinguish, but colors seem nicer. No idea.

Feature level change request.
Would it make sense that when we are in comparison mode. We only allow 1 metric to be compared between places getting compared? Maybe a drop down that selects the metric?

That seems plausible but I don't have the mental capacity to spend time on it

No worries. I’ll take that on.
April Schleck<EMAIL_ADDRESS>2020年5月17日 週日，下午6:38寫道：

That seems plausible but I don't have the mental capacity to spend time on
it
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/xunhuang/covid-19/pull/135#issuecomment-629900299,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFSGF7UQLRATXSQ4WH3HKDRSCGQ7ANCNFSM4NDUCPAQ
.


Causes 'Disable All Installed Extensions' to fail in VS Code (Regular and Insiders)

This extension prevents the option Disable All Installed Extensions in Visual Studio Code because the other, newer extension, (hosted at https://github.com/Microsoft/vscode-node-debug2) "depends" on this extension, and apparently, this extension is attempted to be disabled first.
Actually, perhaps this is more of a bug for VS Code itself? IOW, VS Code should take into account extension dependencies when attempting to disable extensions and ensure that they are disabled in the correct order? (And perhaps even alert the user that "The 'xyz' extension will also be disabled because it depends on this 'abc' extension. Continue: Yes / No?")

@sandy081 I think this is a valid concern. This issue was initially filed against node-debug.

It gets worse. I tried to disable another extension, a plugin to VS Code Test Explorer extension for Python tests. Nope, it depends on Python. Ok, I go to disable Python. Nope, an Azure extension depends on that. Ok, let's disable that, too. Nope, the Azure Extension Pack requires it. Yikes.
This really does seem more of an issue for VS Code rather than the extension itself. VS Code should also treat Extension Packs a bit differently, allowing constituent extensions to be individually disabled. (Barring any dependencies, of course, but that's more about the extension being disabled than about the entire extension pack. IOW, extension packs are just containers, nothing more?)

@fourpastmidnight Node debug extensions are built in extensions are not disabled when you perform the action - Disable all Installed Extensions.
Did you have node-debug extension installed from Marketplace? Can you please open your extensions folder (use command Open Extensions Folder) and check if it contains node-debug extension.


chore(test, pallas): fix deprecated shuffle in pallas test

This has been deprecated from JAX. Fix to supress warnings.

Hello @sharadmv , this may be a minor PR, but could it be merged now (all tests pass)?

Yep will merge today


Movement physics issue

This is your Private Server Pack.

And this is Real agar.io.

Private Server looks like close cell and cell.
But real agar.io looks like regular cell and cell.
But you think, it's not bug, you don't have to fix this.
Thank you for make agar.io private server!
(i'm korean, so i can't use English well.)

I know about it and I want to fix it.

I rewritten collision physics, so this issue is resolved.
With one note. MultiOgar uses single pass collision resolver, so if some cell is under pressure from several other cells, the cell which is under pressure may be clamped and you will see very similar behavior.
I'm not so familiar with physics engines, so I don't know how to fix it with single-pass collision resolving.
On the other hand, multi-pass collision resolving will be too slow.


The word Dynamic is misspelled.

Misspelled word:
"""Processor for dense DynamiceEmbedding."""
"""Processor for dense DynamicEmbedding."""

@googlebot I fixed it.

@googlebot I fixed it.


Standard folder structure/code organisation guidelines for hyper apps

Now that Hyperapp has been out for a while and used by many people, I thought I'd open this issue so that we can all share how we organise our hyper apps.
Maybe we can come up with some sort of standard/supported folder structure together?
Some people have started working on some CLI to setup HA projects, these could potentially benefit from what is discussed in this issue.
PS: I know that HA 2.0 is right around the corner, but I think it is still very valuable to discuss  this now because:

many people will still use HA 1 for some time
from the look of it, the standard app structure for HA 2.0 will should be too different from the standard for HA 1

Looking forward to the discussions down below.

For the record, here is the folder structure that I found works best for me (it's for typescript, but the only typescript specific files are the api.ts):
App folder structure:
dist/       # bundled files
src/        # sources
  module1/     # module folders (detailed below)
  module2/
  common/      # ... common stuff, sometimes I call this lib/
  components   # implementations for simple components (props => VNode)
    Component1.scss
    Component1.tsx
    Component2.scss
    Component2.tsx
    index.ts       # export * from "./Component1"
                   # export * from "./Component2"
  api.ts    # the typescript definitions for the State, Actions, and all relevant types
  state.ts  # the state object
  view.ts   # the view function
  index.ts  # calls app(state, actions, view, element)
  index.html
  # other top level files
package.json
# other files ...

Module folder structure:
submodule1/  # nested modules, same folder structure as this
submodule2/
actions/     # implementations for actions (usage: import * as actions from "./actions")
  action1.ts
  action2.ts
  index.ts      # export * from "./action1"
                # export * from "./action2"
                # import * as submodule1 from "../submodule1/actions"
                # export { submodule1 }
components/  # implementations for simple components (props => VNode)
  Component1.scss
  Component1.tsx
  Component2.scss
  Component2.tsx
  index.ts      # export * from "./Component1"
                # export * from "./Component2"
api.ts    # the typescript definitions for the State, Actions, and all relevant types
state.ts  # the state object
LazyComponent1.scss # these are the lazy components (props => (state, actions) => VNode)
LazyComponent1.tsx
LazyComponent2.scss
LazyComponent2.tsx
index.ts

I guess, for most Web based projects, the tree folder structure can be simplified to this (using JSX).
my-hyperapp-project
├── public
│   └── js
│       └── bundle.js
└── src
    ├── components
    │   ├── about.jsx <-- requires partials/**/*
    │   ├── contact.jsx <-- requires partials/**/*
    │   ├── home.jsx <-- requires partials/**/*
    │   └── partials
    │       ├── footer.jsx
    │       ├── header.jsx
    │       └── main.jsx
    ├── index.html
    ├── index.jsx <-- requires components/*.jsx & utils/**/*
    └── utils
        ├── actions.jsx
        └── state.jsx

In my opinion, it looks cleaner and is safer to scale for small to mid-sized project using Hyperapp 1.x.x. I'm currently working on a Rollup based template for Hyperapp and this is the folder structure I'm currently testing in development to see how convenient it is for all kind of project. Let me know what you think about it!

I feel that an agreed upon folder structure is a great idea. I acknowledge it will be impossible to fit all use cases. This said, I feel that the above example from @aminnairi  is simple, understandable, and a good base to start from.
One thing I would strongly advise against is the uppercase first letter present in the other 2 examples. It seems that this is being used to signify a component file. However these files can be identified in both folder structures as components due to residing in a "components" folder. This is unnecessary duplication of intent.

I also like consistency in the naming convention of all stuff in my application whether it is a component or an exported function. But this is more of a personnal concern than a guideline as it is not impacting the organization.
I guess sometimes, the bundler help in a way that, for instance, with Webpack's alias, we can make a 1-2 level deep folders' structure, and just call things like :
// /app/jsx/app.jsx
import 'SCSS/app.scss'

with a Webpack configured like so :
module.exports = {
  resolve: {
    alias: {
      SCSS: __dirname + '/app/scss/'
    }
  }
}

instead of doing :
// /app/jsx/app.jsx
import '../scss/app.scss'

But this might be just me hating double-dot when we can use aliases in Webpack (not sure how it is done with other bundler though). It has the advantages to be cleaner and easier to understand for newcomers inspecting the source code as every JSX will be in the same directory, every SCSS either etc... But I can see a problem when working in a large-scale application. There might be a perfect spot between aliasing low-level folders and subfolders by theme organization.

@frenzzy @zaceno @lukejacksonn Do you have any opinion on this?

I’m not sure it’s a good idea to promote a “standard and official” folder structure. Everyone does it differently, and as long as everyone does what works for them, why argue with each other who does it better?
But @Mytrill s original suggestion of sharing and explaining the ideas behind it is great. Should be very helpful to newcomers!

Here was a starting point to standardize a directory layout: Folder Structure Conventions
A folder structure mainly depends on the project type and may vary project to project. Only the base (always used files) could be at the same place.
For example the base directory layout of Hyperapp Starter:
.
├── build/                         # Compiled output
├── node_modules/                  # 3rd-party libraries and utilities
├── public/                        # Static files such as favicon.ico etc.
├── src/                           # Application source code
│   ├── app.js                     # Universal (Isomorphic) application entry point
│   ├── index.js                   # Client-side rendering, e.g. app(state, actions, view, container)
│   └── server.js                  # Server-side rendering, e.g. renderToString(view, state, actions)
├── .env                           # Environment variables
├── package.json                   # The list of project dependencies + NPM scripts
└── README.md                      # Getting started guide

The advanced directory layout of a huge project may look like this:
├── .circleci/                     # Continuous integration configuration files
├── .vscode/                       # Project snippets and run/debug configuration for Text Editor/IDE
├── benchmarks/                    # Load and stress tests
├── build/                         # Compiled output
├── configs/                       # Configuration overrides for Babel, Bundler, etc. Example: https://github.com/frenzzy/hyperapp-tools/tree/master/configs
├── docs/                          # Documentation files
├── migrations/                    # Database schema migration files
├── node_modules/                  # 3rd-party libraries and utilities
├── public/                        # Static files such as favicon.ico etc.
├── scripts/                       # Automation scripts (yarn update-schema etc.)
├── seeds/                         # Reference and seed data for the database
├── src/                           # Application source code
│   ├── common/                    # Shared Hyperapp/React components and HOCs
│   │   └── {component}/           # Any component name or reusable block
│   │       ├── {component}.js     # Or {component}.browser.js + {component}.node.js
│   │       ├── {component}.test.js
│   │       ├── {component}.css
│   │       ├── {component}.i18n.json
│   │       ├── {image}.{svg,png,jpg,gif}
│   │       ├── package.json       # Allows to use require('component') instead of require('component/component') and import different files for browser and server when necessary
│   │       └── README.md          # If necessary
│   ├── fonts/                     # Custom web fonts
│   ├── icons/                     # Reusable svg icons
│   ├── pages/                     # Web app pages (/news, /store, /users, /users/:id, /admin, etc)
│   │   └── {page}/                # The same structure as for common/ but the files are not reusable and the whole folder could be deleted safely
│   ├── server/                    # Server-side code (API, authentication, etc.)
│   ├── app.js                     # Universal (Isomorphic) application entry point
│   ├── app.test.js                # Unit tests for app.js
│   ├── app.css                    # Global application styles (for html, body, h1 etc.)
│   ├── index.js                   # Client-side rendering, e.g. app(state, actions, view, container)
│   ├── server.js                  # Server-side rendering, e.g. renderToString(view, state, actions)
│   ├── serviceWorker.js           # Service worker entry point
│   ├── graphql.schema             # GraphQL schema (auto-generated, used by Apollo or Relay)
│   └── theme.js                   # UI theme variables (for example overrides for Material UI default styles)
├── ssl/                           # SSL certificates (for example for connecting to Cloud SQL instance)
├── tests/                         # End-to-end, integration tests
├── .env                           # Environment variables
├── .env.{environment}             # Environment variables overrides for a specific environment
├── docker-compose.yml             # Defines Docker services, networks and volumes
├── docker-compose.override.yml    # Overrides per developer environment (not under source control)
├── Dockerfile                     # Commands for building a Docker image for production
├── package.json                   # The list of project dependencies + NPM scripts
└── README.md                      # Getting started guide


chore: get file signed url

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


Custom primitive creation functions

Added two functions, make_trans_primitive and make_agg_primitive.  Given a function to apply to input features, list of allowed input feature types, and variable type of the resulting feature, these functions will create a new primitive that can be used with DFS.

Codecov Report

Merging #13 into master will increase coverage by 0.42%.
The diff coverage is 95.19%.

@@            Coverage Diff             @@
##           master      #13      +/-   ##
==========================================
+ Coverage   86.44%   86.86%   +0.42%
==========================================
  Files          73       73
  Lines        6549     6778     +229
==========================================
+ Hits         5661     5888     +227
- Misses        888      890       +2

Impacted Files
Coverage Δ

featuretools/demo/mock_customer.py
14.7% <ø> (ø)
:arrow_up:

featuretools/utils/pickle_utils.py
75.86% <100%> (ø)
:arrow_up:

featuretools/primitives/aggregation_primitives.py
92.1% <100%> (+0.85%)
:arrow_up:

...ols/tests/feature_function_tests/test_agg_feats.py
98.35% <100%> (+0.75%)
:arrow_up:

featuretools/primitives/utils.py
93.15% <100%> (+1.48%)
:arrow_up:

featuretools/primitives/primitive_base.py
76.94% <79.16%> (ø)
:arrow_up:

featuretools/synthesis/deep_feature_synthesis.py
92.09% <88.88%> (+0.13%)
:arrow_up:

...turetools/primitives/aggregation_primitive_base.py
95.45% <92.59%> (-4.55%)
:arrow_down:

featuretools/primitives/transform_primitive.py
96.78% <94.44%> (-0.51%)
:arrow_down:

.../feature_function_tests/test_transform_features.py
85.15% <95.65%> (+0.89%)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


CPU support?

In the readme, under "Install the NVIDIA Container Toolkit" it says:

This step [...] is only necessary if you want GPU support.

So if I understand correctly, we can chose to use the CPU instead? If so, I didn't find how to do it.
I tried removing --gpus all from the docker run command but then when launching runGan.py 1 I got :
ImportError: libcuda.so.1: cannot open shared object file: No such file or directory

Failed to load the native TensorFlow runtime.

If using the CPU on the run case 1 is possible, I would like to do it for the following reasons:

the Nvidia Toolkit is not yet supported under the latest stable Ubuntu (20.10)
I have another computer with an AMD GPU which I would also like to run TecoGAN on

The issue might be that the docker base image is build using a gpu base image.
In docker/Dockerfile you could change from tensorflow/tensorflow:1.8.0-gpu-py3 to from tensorflow/tensorflow:1.8.0-py3, execute the docker build step and runGan.py 1 should work on the CPU.

The issue might be that the docker base image is build using a gpu base image.
In docker/Dockerfile you could change from tensorflow/tensorflow:1.8.0-gpu-py3 to from tensorflow/tensorflow:1.8.0-py3, execute the docker build step and runGan.py 1 should work on the CPU.

Thanks, it works great!

Thanks, it works great!


the text of button is not centered.

Why button text is not centered. Why this is happening?

It's actually clearly centered in the screenshot that you give ... There is 118px on both side of the text, and 14px at the top and at the bottom. Can't see issue here :/


cds-button in a form triggers ngSubmit when it shouldn't

Describe the bug
Moving from @clr/angular buttons to , I've noticed that a button with type="button" will call the ngSubmit method bound to the form. This behaviour doesn't happen with regular html buttons.
How to reproduce
https://stackblitz.com/edit/clarity-v5-enter-to-submit?file=src/app/app.component.html

Click the first "Cancel" button and only the Cancel Count increments.
Click the first "Submit" button and only the Submit Count increments.
Click the second "Cancel" button and both counts incorrectly increment.
Click the second "Submit" button and the Submit Count increments.

I'm pretty sure I've got the html correct but I'm happy to be corrected. (I've been trying to figure out why some of our forms won't submit with the Enter key when we swap the buttons over to the  versions).
Expected behavior
Clicking on the Cancel button with the attribute type="button" should not submit the form.
Versions
Clarity project:

[x] Clarity Core
[ ] Clarity Angular/UI

Clarity version:

[ ] v3.x
[ ] v4.x
[x] v5.x

Framework:

[x] Angular
[ ] React
[ ] Vue
[ ] Other:

Framework version:
ie: Angular 11.2

Duplicate of https://github.com/vmware/clarity/issues/6002


createdb for custom fasta header

Is it possible to pass as a parameter position of ID in fasta header on DB creation?
It would be great to have possibility to specify ID field in fasta that are responsible for ID when running MMseqs2 createdb.
As I see in Util.cpp, position of ID is hardcoded in
getFastaHeaderPosition in const struct Databases
for example - { "gi|",   3, 3}  // NCBI GI
For example I might have fastaID like

gi|1123952629 gene_1|GeneMark.hmm|102_aa|-|1375|1683  gb|AAWO01000063| Length: 10023
where ID is the gi|1123952629 or<PHONE_NUMBER>
In the current implementation of Util.cpp ID will be 102_aa

I have workaround for my problem by removing "gi|"
// if we can not find one of the existing database ids,
// we use the first part of the string or the whole string
However it would be nice feature to specify it manually.

Thank you, I already did my workaround (left bare gis: >10000123/n).
My issue was just low priority suggestion for improvement.


Standard rules for pull requests

I propose to roll out the a few more rules to pull requests:

At least one reviewer besides the author must approve the PR
PRs with all checks completed (build + approval) shall be auto-completed
Branches of PRs shall be deleted after merge

Providing default reviewers could be done by creating a CODEOWNERS file

@karstenroethig
See this documentation on protecting branches: https://docs.github.com/de/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule
It should be usable with GitHub Free

Please check this on automatic branch deletion: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/configuring-pull-request-merges/managing-the-automatic-deletion-of-branches

I made the following adjustments via the settings:

Settings > Gerneral > Pull Requests > Allow merge commits: Disabled
Settings > Gerneral > Pull Requests > Automatically delete head branches: Enabled
Settings > Rules > Rulesets > "Basic Ruleset"

Target branch: Default (master)
Rules:

Require linear history: Enabled
Require a pull request before merging: Enabled
Required approvals: 1

In our next meeting we can look at the other options together and activate them if necessary.

For the current active PR, I am unable to merge this without your approval. I'm also unable to workaround by self-approving it. Setup looks good, from my side.

clsd


Bump dependecies jest, @types/jest and ts-jest

I upgraded the jest, @types/jest and ts-jest dependencies to the latest version, because in every pnpm install there was a warning for the ts-jest library and in the future I wanted to upgrade to typescript 5.5.3 in all packages.
In order to update jest it was necessary to update ts-jest and vice versa, although I didn't want to make a PR with both updates they are totally related and you can't update one library without updating the other.
In the packages/turbo-test-utils, I removed the jest, @types/jest and ts-jest dependencies, as they were not used in this package node:test is used.
In order to move from jest to the latest version and keep everything working the same without touching code, I had to update the configuration of jest when doing snapshop to leave the configuration that had before to be able to default, put it url of the documentation, without putting this configuration all the tests failed: https://jestjs.io/docs/upgrading-to-jest29#snapshot-format
In all jest configurations, now InitialOptionsTsJest is marked as deprecated and changed to JestConfigWithTsJest.

Allow CI Workflow Run

[ ] approve CI run for commit: 169bedbb30fee3ec1ba2ef70391d00dafdb2eb85

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

Hi @anthonyshew, I think the auto merge failed

Unfortunate. Looks like it did, indeed. Would you want to fix these conflicts or should we close and work on this some other time?

Hi @anthonyshew,
I have been checking and this has already been implemented: https://github.com/vercel/turborepo/pull/9155
I close this PR.

Very sorry about that. I've encouraged and re-iterated with the team that we need to handle PRs from community members faster and always check for open PRs that have already done the work. Myself included, I've made mistakes on this a number of times.
We'll be better on this in the future and I continue to appreciate all your PRs. 🙏


Quick check - AWS

Need to do following tasks:

[ ] Login into AWS console ☁
[ ] Pass MFA code 📱
[ ] Go to IAM Role ㊙
[ ] Change the password ⏩ to new
[ ] Try to login with new password 🛂

[ ]

[ ]

[ ]

[ ]


Is this library simply geared towards CRYPTO currencies only?

Can't seem anything general to use with Forex  or Stocks

not relevant , found my issue


Fix recursive writing of output files - preserve folder structure

When introducing the output flag, the input folder structure was not used in output.
Fixes https://github.com/GoogleCloudPlatform/proto-gen-md-diagrams/pull/14#issuecomment-2068571626
@chicco785  This fixes your comment

any chance that we can get this merged? Its a bit of a show stopper for us with this otherwise excellent utility :)

@rmcguinness Any chance mergin this fix PR?


Need to update Heroku Multipack

I see this message when installing Heroku Toolbelt on a new box:
remote: -----> Multipack app detected
remote: WARNING: This buildpack is no longer maintained.
remote:
remote: Please choose a different buildpack or go to https://github.com/ddollar/heroku-buildpack-multi
remote: and fork it to your own account.
remote:
remote: This buildpack will cease to function at the stroke of midnight on January 1, 2017.

This has been completed.

@trystant may I ask how you resolved this warning?


Does marzipano support the streaming video?

If I want to play streaming videos, for example, rtmp, rtsp, hls and etc. Does marzipano support them?

I have not tested this, but Marzipano should be able to render any HTML5 Video element.


Security context is broken for 21.3.0 Express

I've been having trouble running the 21.3.0 XE container due to permission issues.
I'm not using Helm, but basically the same manifest and saw the following:
https://github.com/oracle/docker-images/blob/1cd62e6cb0803cd3f76d672f623c201af41caecd/OracleDatabase/SingleInstance/helm-charts/oracle-db/templates/deployment.yaml#L31-L33
I've had to do the following instead:
      securityContext:
        runAsUser: 0   # the scripts are only runnable by root
        fsGroup: 54321 # the scripts `su - oracle` which tries to mkdir on the mounted volume

Thought it might be useful to note here in case anyone else is struggling.

Well that works up until here:
https://github.com/oracle/docker-images/blob/1cd62e6cb0803cd3f76d672f623c201af41caecd/OracleDatabase/SingleInstance/dockerfiles/21.3.0/runUserScripts.sh#L30
Because it's being run as root (due to my securityContext change), but it need to run as oracle.

I think there needs to be a chown (or move the USER statement above the RUN maybe), so that we can go back to running as oracle as intended.
https://github.com/oracle/docker-images/blob/1cd62e6cb0803cd3f76d672f623c201af41caecd/OracleDatabase/SingleInstance/dockerfiles/21.3.0/Dockerfile.xe#L63-L81

I am unable to reproduce this on my setup. Used the following yaml file to deploy 21c XE database:
apiVersion: v1
kind: Namespace
metadata:
  name: ns1
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: oracle-xe-oradata
  namespace: ns1
  labels:
    app: oracle-xe
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 20Gi

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: oracle-xe
  labels:
    app: oracle-xe
  namespace: ns1
spec:
  replicas: 1
  selector:
    matchLabels:
      app: oracle-xe
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: oracle-xe
    spec:
      securityContext:
        runAsUser: 54321
        fsGroup: 54321
      containers:
        - name: xe
          image: <Latest 21c XE image location>
          envFrom:
            - secretRef:
                name: oracle-xe-credentials
          ports:
            - containerPort: 1521
              name: oracle-listener
            - containerPort: 5500
              name: oem-express
          volumeMounts:
          - name: oradata
            mountPath: /opt/oracle/oradata
          readinessProbe:
            initialDelaySeconds: 60
            periodSeconds: 60
            exec:
              command:
                - /bin/sh
                - "-c"
                - $ORACLE_BASE/$CHECK_DB_FILE
      volumes:
        - name: oradata
          persistentVolumeClaim:
            claimName: oracle-xe-oradata
---
apiVersion: v1
kind: Service
metadata:
  name: xe-database
  namespace: ns1
  labels:
    app: oracle-xe
spec:
  ports:
    - name: listener
      port: 1521
      targetPort: oracle-listener
  selector:
    app: oracle-xe

The status after deploying this on k8s cluster:
$: xe-deployment kubectl get all -n ns1
NAME                             READY   STATUS    RESTARTS   AGE
pod/oracle-xe-65fbcd6665-8kbvl   1/1     Running   0          16m

NAME                  TYPE        CLUSTER-IP    EXTERNAL-IP   PORT(S)    AGE
service/xe-database   ClusterIP   <IP_ADDRESS>   <none>        1521/TCP   16m

NAME                        READY   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/oracle-xe   1/1     1            1           16m

NAME                                   DESIRED   CURRENT   READY   AGE
replicaset.apps/oracle-xe-65fbcd6665   1         1         1       16m

Not sure why this error is coming. Can you pls share more info on how you are building the 21c XE image and what deployment yaml is being used for further investigation ?

Sure, the build is as follows:
docker build -f Dockerfile.xe https://github.com/oracle/docker-images.git#main:OracleDatabase/SingleInstance/dockerfiles/21.3.0

My deployment is listed here (which works when privileged mode is enabled): https://github.com/oracle/docker-images/issues/2243#issuecomment-1030811971

Closing this issue as the deployment is working (indicated by previous comment). Please reopen in case of any further issue.


这个后端是不是不可以用在端到端模型上？

这个后端是不是不可以用在端到端模型上？

@von-321 Hi, thanks for following our work. You can jointly train a neural speaker encoder with this back-end model. More details are provided in this paper. Please check it.


AU-service does not send removed logo_$_id-keys anymore

I sent this request to the AU-service:
{
    "collection": "meeting",
    "ids": [
        2
    ],
    "fields": {
        // [...],
        "id": null,
        "logo_$_id": {
            "type": "template"
        },
        "font_$_id": {
            "type": "template"
        },
        "reference_projector_id": null,
        "is_active_in_organization_id": null,
        // [...]
    }
}

I got this response:
{
    // [...]
    "meeting/2/id": 2,
    "meeting/2/is_active_in_organization_id": 1,
    "meeting/2/logo_$_id": [
        "web_header"
    ],
    "meeting/2/logo_$web_header_id": 5,
    // [...]
}

So far, so good...
But then, I remove the logo used as web_header (this request is regardless, but for the completeness):
[
    {
        "action": "meeting.unset_logo",
        "data": [
            {
                "id": 2,
                "place": "web_header"
            }
        ]
    }
]

And I got the following response:
{
    "meeting/2/logo_$_id": []
}

You see, the key web_header is missing. Therefore, the client does not notice, that the logo changed.
Is this a bug or is this a result of previously committed changes (like OpenSlides/openslides-autoupdate-service#337)?

Duplicate of #618

Maybe we could think about changing the type of the field meeting/logo_$_id from a template field to a JSON-field. So you could save all logo-values for one meeting into one database key.

this would be the solution I'd propose. Currently, the client cannot get the required information in any meaningful way.


Problems on newer Androids like Note 3?

Being told that the popup is not resizing and that the "X" to close is not showing up at all...

Could be due to the missing vendor prefixes for positioning (which @spencerbrooks fixed).  I would try out the updated version of the popup with that merge.  If it's still happening, it's most likely due to conflicting CSS on the page (a global div {} declaration may affect the popup div(s))


Repeated bot answers after clicking the "Reset Chatbot" button

I am recording a conversation with my facebook chatbot via fbDirect, but after clicking the "Reset Chatbot" button I get the same answer to my request twice. If I click another time the "Reset Chatbot" button I get the same answer to my request three times and so on.
I faced the same issue by clicking the "Clear Chat" button but I was able to solve it in that case by emptying the vm.messages array in the clearChat function:
vm.clearChat = function() {       vm.messages = [];       vm.messages.length = 0;     };
I tried to do the same in the startDocker() function that, as far as I understand, is the one that is called when a you click on the "Reset Chatbot" button but it doesn't work and I'm not able to understand what could be the problem.
Can you help me?
Thank you.

The emulators have been extracted to another project, Botium CLI.


fixed uncessary line breaks

Pre-Submission Checklist

[x] Your pull request targets the staging branch of FreeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm run test-challenges. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Description

fixed uneccessary line breaks in issue #9554

@dkat90 looks good to me but can you put or edit your PR message's last checkbox to have Closes #9554? This will autoclose the issue when your PR is merged. Thanks!

Hey Eric,
Thanks so much for accepting my pull request!I'll fix it as soon as I get the chance.
Warmest regards,
David Ken
On Tue, Jul 05, 2016 at 10:39 AM, Eric Leung <<EMAIL_ADDRESS><EMAIL_ADDRESS>> wrote:
@dkat90 [https://github.com/dkat90] looks good to me but can you put or edit your PR message's last checkbox to have Closes #9554 ? This will autoclose the issue when your PR is merged. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub [https://github.com/FreeCodeCamp/FreeCodeCamp/pull/9556#issuecomment-230376410] , or mute the thread [https://github.com/notifications/unsubscribe/AP2bxvAH_ZYmkrrRALkwOUiH64zVbTRJks5qScPwgaJpZM4JEuid] .

Done!
On Tue, Jul 5, 2016 at 10:39 AM, Eric Leung<EMAIL_ADDRESS>wrote:

@dkat90 https://github.com/dkat90 looks good to me but can you put or
edit your PR message's last checkbox to have Closes #9554? This will
autoclose the issue when your PR is merged. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/pull/9556#issuecomment-230376410,
or mute the thread
https://github.com/notifications/unsubscribe/AP2bxvAH_ZYmkrrRALkwOUiH64zVbTRJks5qScPwgaJpZM4JEuid
.

@dkat90 thanks for your efforts but I don't see any changes. To make the change of adding Closes #9554, you'll need to visit the GitHub site where your PR is. So you'll need to go to https://github.com/FreeCodeCamp/FreeCodeCamp/pull/9556 and edit your PR commit message where it says

Closes currently open issue (replace XXXX with an issue no): Closes #XXXX

Let me know if you have any questions. Thanks again!

Hey Eric! I think it shows up correctly now! I don't know what happened to my edits, I'm really sorry about that!

:sparkles: :sparkles: LGTM :+1: :sparkles: :sparkles:
:tada: Thanks for contributing @dkat90 and congratulations on your first PR submission to FreeCodeCamp! :tada:


Remove .validation for manifests\i\iA\Writer - Empty directory

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115572&drop=dogfoodAlpha

[Policy] Needs Manual Merge


Create license file acceptance for inspec 4

Tested with chef/inspec/4.0.8/20190412140954
With this change, when the compliance service starts, it creates the ~/.chef/accepted_licenses/inspec empty file that will surpass the inspec 4 chef license prompt.

It works with inspec 3 as well.
No need to track every use of inspec in the codebase to ensure we add the --chef-license option

i know you mentioned that the license acceptance littering the stdout only happens the first time this is run.  what's the plan for handling that littered stdout the first time the license acceptance stuff actually runs?

will this also work for our inspec shim env? https://github.com/chef/automate/blob/master/components/compliance-service/inspec/cli.go#L33

what's the plan for handling that littered stdout the first time the license acceptance stuff actually runs?
By creating the ~/.chef/accepted_licenses/inspec, inspec assumes the license has already been accepted. No confirmation is added to STDOUT

I'll test the inspecShimEnv now...

i'm not 100% convinced this is the right way to go about it. Your service shoudn't really be writing outside of /hab/svc. Maybe there is an environment variable that can be set?

@jaym the possible options for license acceptance are detailed here: https://github.com/chef/automate/issues/83#issue-433394461

An ENV variable is one of the options and the function being modified in this PR is for setting the ENV for our inspec calls. That seems to be a much simpler solution (for this specific case, anyways).

An ENV variable is one of the options
it is? where is that detailed?

Adds a new value that can be passed as a value to --chef-license or as an ENV var: accept-silent.

https://github.com/chef/license-acceptance/pull/26

that command is for silencing the output. it is not for actually accepting the license.
do we know that accepting the license can also be done via env var?

ohh, or did i misunderstand and that will accept the license and silence the output?

ohh, or did i misunderstand and that will accept the license and silence the output?

From the updates to README in that PR that's what it sounds like to me.

I could be misunderstanding this too though.

we should confirm, but ya the readme does seem to imply that will work.

nice catch @phiggins !

CHEF_LICENSE=accept-no-persist worked like a charm, no files written on disk anymore, compatibility with inspec 3 & 4. I updated the code of the PR, title and description.
I tested with the latest unstable inspec 4.1.3 build the scanning, profile operation(inspec json, archive) and the scripts(bash & powershell) we run remotely.


fix shortcode to troubleshoot deploy

Attempt number one to fix Netlify build. Fragile shortcode syntax; this was the only reported error, 🤞 it's the only one ...

/assign @steveperry-53 @zacharysarah @chenopis
apologies for assign spam, but would be good to get this fix in soon ...

/approve
/lgtm


Partial struct validation does not validate child structs

[ X ] I have looked at the documentation here first?
[ X ] I have looked at the examples provided that may showcase my question here?

Package version eg. v9, v10:
v10
Issue, Question or Enhancement:
When using StructPartial(), we should expect all fields specified to be validated. It does not validate struct properties, however, unless you specify the full path to individual fields inside child structs.
Code sample, to showcase or reproduce:

type Order struct {
	Id   string `validate:"required,number"`
	Item Item   `validate:"required"`
}
type Item struct {
	Id string `validate:"required,number"`
}
func TestMain(m *testing.M) {
	v := validator.New(validator.WithRequiredStructEnabled())
	order := Order{
		Id: "123",
		Item: Item{
			Id: "invalid",
		},
	}
	log.Printf("validation full: %+v", v.Struct(order))
	log.Printf("validation partial: %+v", v.StructPartial(order, "Item"))
	log.Printf("validation partial with path: %+v", v.StructPartial(order, "Item.Id"))
	log.Fatalf("done.")
	return
}

Output is as follows:
2024/07/19 15:26:07 validation full: Key: 'Order.Item.Id' Error:Field validation for 'Id' failed on the 'number' tag
2024/07/19 15:26:07 validation partial: <nil>
2024/07/19 15:26:07 validation partial with path: Key: 'Order.Item.Id' Error:Field validation for 'Id' failed on the 'number' tag
2024/07/19 15:26:07 done.

Actually, using StructFiltered() it does validate child structs. The following works:
	log.Printf("validation filtered: %+v", v.StructFiltered(order, func(ns []byte) bool {
		if bytes.Equal(ns, []byte("Item")) {
			return true
		} else {
			return false
		}
	}))

However, this should be implemented for StructPartial() as well.

Using StructFiltered(), it does go into nested structs. However, it's a bit cumbersome to use. This works and validates all child fields in the child struct:
	log.Printf("validation filtered: %+v", v.StructFiltered(order, func(ns []byte) bool {
		if bytes.HasPrefix([]byte("Order.Item"), ns) || bytes.HasPrefix(ns, []byte("Order.Item")) {
			return false
		} else {
			return true
		}
	}))

There should be better support in StructPartial() for nested structs...


User profile

Todo

[x]  add user profile features as per the story (NSA-331)
[ ]  include correct layout file
[ ]  add navigation UI elements
[ ]  cleanup html and css


feat: [typescript-react-query] Able to import useQuery from own-path instead react-query or tanstack/react-query

Description
I would like to propose a new feature to address this issue. I have described the proposed solution in detail on the following GitHub discussion: Link to GitHub Discussion.
In summary, I suggest adding a new configuration field called reactQueryImportFrom. This field will allow users to specify a custom import path for react-query. For example:
reactQueryImportFrom = 'custom-react-query';

With this configuration, the import statements for useQuery, useMutation, UseQueryOptions, and UseMutationOptions will be updated as follows:
import { useQuery, useMutation, UseQueryOptions, UseMutationOptions } from 'custom-react-query';

This feature will provide flexibility and enable developers to centralize the source with some required configuration, making it easier to customize and maintain their projects.
List any dependencies that are required for this change.

typescript-react-query

Related #368 (issue)

Type of change

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Screenshots/Sandbox (if appropriate/relevant):
Adding links to sandbox or providing screenshots can help us understand more about this PR and take
action on it as appropriate
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can
reproduce. Please also list any relevant details for your test configuration

[x] reactQueryImportFrom: custom-path

Test Environment:

OS: Ubuntu
"@graphql-codegen/plugin-helpers": "^3.0.0",
"@graphql-codegen/visitor-plugin-common": "2.13.1",
NodeJS: v16.18.1

Checklist:

[x] I have followed the
CONTRIBUTING doc and the
style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose
the solution you did and what alternatives you considered, etc...

hi @saihaj, could you help to review this PR. please.
Thank you so much

@n1ru4l sorry for bothering you, but could you help review this PR

Hi @n1ru4l, please help me know if I need to do anything else to get merge this PR. Thank you for everything


GlobalStyles using an attribute selector are loaded after regular styles

Environment
System:

OS: macOS 10.15.2
CPU: (8) x64 Intel(R) Core(TM) i7-8559U CPU @ 2.70GHz
Memory: 1.12 GB / 16.00 GB
Shell: 5.7.1 - /bin/zsh

Binaries:

Node: 13.7.0 - ~/.asdf/installs/nodejs/13.7.0/bin/node
Yarn: 1.21.1 - ~/.asdf/installs/nodejs/13.7.0/.npm/bin/yarn
npm: 6.13.6 - ~/.asdf/installs/nodejs/13.7.0/bin/npm

npmPackages:

babel-plugin-styled-components: ^1.10.7 => 1.10.7
styled-components: ^5.0.0 => 5.0.0

Reproduction
v5.0.0: https://codesandbox.io/s/thirsty-kalam-hi5s8
v4.4.1:  https://codesandbox.io/s/strange-mendeleev-pindz
Steps to reproduce

Create a global stylesheet using an attribute selector to set some styles.
Try to overwrite those styles on a component

Expected Behavior
The global styles are overwritten by the component styles, as in v4.4.1
Actual Behavior
The component styles are overwritten

I can confirm that issue. Here is a sandbox where I tried to load the createGlobalStyle component from another file before the "App". But that doesn't help either. https://codesandbox.io/s/crimson-violet-mv5xy
In the <style> tag in devtools here https://mv5xy.csb.app/ you can see that the global styles are coming after the StyledH1 declarations.

We currently don't guarantee an insertion order for global styles. I agree this should be fixed though.

Really hoping that this gets fixed, it's a major bummer for us 🙏

I have just ran into the same issue. Replicated here:
https://codesandbox.io/embed/great-grass-l9y63
Since attribute selector and class selector have the same specificity, and global style is meant to set a base-line for individual components to override, I think the library should gurantee that global styles are inserted first before normal styles.

I am quite disappointed that this isn't getting more recognition. v5 was released with a "no breaking changes!" headline. Well, going from a guaranteed order of stylesheet insertion to not guaranteed is quite literally a breaking change, which wasn't even mentioned anywhere.

Has anyone found a work around for this? I have a large project that can't upgrade until this is fixed or there is a work around that doesn't involve touching a large portion of the code base.

Hi ! Any progress on this ? This is a major issue for us ... We need the v5 to decrease our bundle size and have decent score on lighthouse v6...
Thanks for your help here and your great job !

@asafigan this will be fixed in 5.2!


Host's terminal

When I connect to a live preview session when I press ALT + `, I can have access to the host's terminal, that mean I have access to :

Delete files from the host's terminal
Delete System32
Create files
Shutdown, reboot, the computer

Note: VS Code in Windows

@Andre221 A host's terminal isn't automatically shared with guests, so you wouldn't be able to access the things you mentioned unless you were explicitly given permission to do so. Additionally, when thinking about #41, we plan to make shared terminals read-only by default, since the most common use case for shared terminals is to allow everyone in the session to see the output of commands (e.g. build failures, unit test status), as opposed to allowing guests to directly access the host's machine.

@Andre221 See here for information on security considerations for terminals: https://review.docs.microsoft.com/en-us/visualstudio/liveshare/reference/security?branch=master#sharing-a-terminal

Thanks


StandaloneERC20 symbol shows an address parameter

StandaloneERC20 symbol function shows an address parameter. symbol(account: address)
First reported in the Community Forum: https://forum.openzeppelin.com/t/sdk-testing-getting-invalid-number-of-parameters/1570

💻 Environment

"@openzeppelin/contracts-ethereum-package": "^2.3.0"

$ oz --version
2.5.3

📝 Details

Occurs on version 2.3.0 but not 2.2.3
🔢 Code to reproduce bug

mkdir token
cd token
npm init -y
oz init
oz link @openzeppelin/contracts-ethereum-package

Create token on ganache-cli
$ oz create
No contracts found to compile.
? Pick a contract to instantiate @openzeppelin/contracts-ethereum-package/StandaloneERC20
? Pick a network development
✓ Deploying @openzeppelin/contracts-ethereum-package dependency to network dev-1571358909036
All contracts are up to date
? Do you want to call a function on the instance after creating it? Yes
? Select which function * initialize(name: string, symbol: string, decimals: uint8)
? name (string): Test Token
? symbol (string): TST
? decimals (uint8): 18
✓ Setting everything up to create contract instances
✓ Instance created at 0x4bf749ec68270027C5910220CEAB30Cc284c7BA2
0x4bf749ec68270027C5910220CEAB30Cc284c7BA2

Attempt to call symbol
$ oz call
? Pick a network development
? Pick an instance StandaloneERC20 at 0x4bf749ec68270027C5910220CEAB30Cc284c7BA2
? Select which function symbol(account: address)
? account (address): 0x4bf749ec68270027C5910220CEAB30Cc284c7BA2
✖ Calling: 'symbol' with:
- account (address): "0x4bf749ec68270027C5910220CEAB30Cc284c7BA2"
Error while trying to call 0x4bf749ec68270027C5910220CEAB30Cc284c7BA2#symbol(address). Error: Returned error: VM Exception while processing transaction: revert

Reverting to 2.2.3 resolves the issue
npm uninstall @openzeppelin/contracts-ethereum-package
oz link<EMAIL_ADDRESS>
$ oz create
No contracts found to compile.
? Pick a contract to instantiate @openzeppelin/contracts-ethereum-package/StandaloneERC20
? Pick a network development
✓ Deploying @openzeppelin/contracts-ethereum-package dependency to network dev-1571358909036
All contracts are up to date
? Do you want to call a function on the instance after creating it? Yes
? Select which function * initialize(name: string, symbol: string, decimals: uint8)
? name (string): Test Token
? symbol (string): TST
? decimals (uint8): 18
✓ Setting everything up to create contract instances
✓ Instance created at 0x1b88Bdb8269A1aB1372459F5a4eC3663D6f5cCc4
0x1b88Bdb8269A1aB1372459F5a4eC3663D6f5cCc4

$ oz call
? Pick a network development
? Pick an instance StandaloneERC20 at 0x1b88Bdb8269A1aB1372459F5a4eC3663D6f5cCc4
? Select which function symbol()
✓ Method 'symbol()' returned: TST
TST

I tracked this down to truffle corrupting the abi field on the JSON artifacts: this was fixed on release 5.0.20, but we're still using 5.0.18 here.
We need to update the truffle dependency, recompile, and publish a new version with the artifacts fixed.

Is @openzeppelin/contracts also affected?

Is @openzeppelin/contracts also affected?
I assume only if someone compiles with truffle between 5.0.13 and 5.0.19.

We had a post in the forum about the Truffle issue (though related to OpenZeppelin SDK)
https://forum.openzeppelin.com/t/upgrade-truffle-5-0-13-to-5-0-20/767

Is @openzeppelin/contracts also affected?

v2.3 was compiled using Truffle 5.0.18 (a broken version), so depending on how the release was built, it could be affected. Checking this is not trivial however.

No longer applies.


support multiple architectures (e.g. SSE, AVX) in the same executable…

… via a macro

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

Comparison is base (37fde44) 95.64% compared to head (5426764) 95.08%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #118      +/-   ##
==========================================
- Coverage   95.64%   95.08%   -0.57%
==========================================
  Files          58       41      -17
  Lines        3860     2988     -872
==========================================
- Hits         3692     2841     -851
+ Misses        168      147      -21

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

Awesome, thanks again! Merging now...


Imagery Offset Database support

Description
Please add support for imagery offset database. https://wiki.openstreetmap.org/wiki/Imagery_Offset_Database
Screenshots
No response

Related to #4764

Also related: #1124


The popup menu does not close when the console is open

Step to reproduce:

On the VM list page and detail page
Click console and open a console window

Result:
The popup menu does not close when the console is open

Validated


Containerize the app for python

Have it working a little bit on Podman. Will update the file when it's working well.

Closed with #17


Ensure OpenAPI description contains delete operations for contained collections

We believe this is an issue with OpenAPI.Net.Odata  Related to #191

Tracked with this issue: https://github.com/microsoft/OpenAPI.NET.OData/issues/59


Slider and range input

I see this slider on home page. But I don't know how to make this. Can everyone teach me to to do this?

Please close this issue and ask questions on the Google group or Gitter. Related issue #1331.


Update sharp, remove deprecated max fn call, retrieve image urls and …

…save to firebase rtdb.
Updating the example here on how to better use the sharp node lib to parse and save to the firebase db.
Sorry for the formatting - i'm actually have some minor issue with VSCode on that. If anyone can assist there that'd be great.

Hi @alxvallejo in vscode, you can  "Command + Shift + P" to select a save without formatting, this might help you reduce the amount of whitespace, etc  changes?


read setup requirements in requirements.txt

Let's avoid useless code duplication that can lead to errors :)

@MateoLostanlen actually the duplication is on purpose since this is the only way to build the conda distrib properly :sweat_smile:

good to know :)


fix: Fix text

Description
This PR removes the mention of vault from the lego acme library
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I Have bumped the version of the library

This PR removes the mention of vault from the lego acme library

Vault? I assume you meant Lego. Why do we want to do that?


SEO-2443: Restricted Term Global Settings

SEO-2443: Restricted Term Global Settings

Description

Added new UI and endpoints for adjusting restricted term settings at a global level.
Motivation and Context

See JIRA Ticket SEO-2443.
How Has This Been Tested?

Manual testing of new feature was performed.
Types of changes

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

Checklist:

[ ] I have added tests to cover my changes.

Overall looking good to me, I think just some of the console logs need to be cleaned up and then the settings should be moved to the bottom of the page as discussed.  I'll approve after that.


How to show gaps in line plots (Signal and Scatter)

(Or maybe a different plot type would make more sense - suggestions?)
I am pulling data from a table to be plotted. Each record has a timestamp and associated values. I am able to successful pull this into a PlotSignalXY and have been having all sorts of fun with all the various ScottPlot options - well done!
However, in some cases, I'll have a jump in record times. The plot does draw everything correctly, and the time axis is behaving correctly. However, is there some way to NOT connect data points that are more than X seconds apart?
For instance, if there's a gap of 1 hour in the data, can that appear as a gap in the plotted line?
If not, do you have any guidance as to where to start my search if I wanted to attempt a solution?
Thanks!

Hey @Wyrus,
This is a somewhat common question, so I'll add it to the FAQ (#572) so it's a little easier to figure out.
The short answer is that right now scatter plots and signal plots can only plot a single connected line. Values like double.PositiveInfinity and doube.NaN are not supported. There is active work (#578) which seeks to detect these invalid values and throw exceptions or write error messages to make this more obvious.
If you have a "disconnected" dataset, the best option is to determine individual lines on your end, then place multiple scatter plots as necessary. If you are in a graphical environment where the data changes a lot, every time there is a new set of data you can call plt.Clear() and plot everything again. It's not the most satisfying answer, but it's the best solution given the current state of the project!
Let me know if you have other questions or hit any snags along the way 👍
Scott

I figured out already that I could do this. However, doing this causes duplicates to show up in the Legend. Every time the same Label is plotted it adds another instance of the Label to the Legend.

Following-up, anyone interested in making scatter plots with gaps can now do so:

https://scottplot.net/faq/data-gaps/
https://scottplot.net/cookbook/4.1/category/plottable-scatter-plot/#nan-values-break-the-line

Thanks! I will try to use double.NaN


Bower version mismatch for version 2.0.1

The tag 2.0.1 is place before a40523f (json version update)
bower ionicons#2.0.1 mismatch Version declared in the json (2.0.0) is different than the resolved one (2.0.1)

There's nothing solved since ! @Ionitron Why did you closed it ?


change repo name to nydus

Hi CNCF community operators, we are requesting to change the sub-project repo name image-serivice (https://github.com/dragonflyoss/image-service) of dragonfly (https://github.com/dragonflyoss/Dragonfly2) to nydus.
The meaning of repo name image-service is relatively vague and does not leave a deep impression for users. In fact, we have used nydus as the project name in the docs and some publicity, let's change the repo name now. Please help assess the proposal's feasibility and give a +1 or LGTM in the comment on this issue, and then I will update the repo name in github setting page, thanks!

cc @krook :)

Sounds good to me!

@krook Thanks!
Let's change the repo name to nydus.
cc @jiangliu @bergwolf @changweige @liubogithub @hsiangkao @eryugey @adamqqqplay @sctb512


Implements an ArrayList for the extras

To avoid loosing the cached previous extra when a new one arrives

Hi Team,
Can you please provide a fix for this? I am stuck from past 3 days in this issue.

Hi, guys!
I just created this issue https://github.com/phonegap/phonegap-plugin-push/issues/1271 and then realized there's already a pull request with the fix.
I'm not really an Android programmer so the comments are a little over my head, but it seems like the benefits of the merge (allowing multiple notifications with action buttons to work, at least sometimes) would exceed the risks.
What do you think?
Thanks! :D

@mikepsinn this PR fixes a different issue but it doesn't quite work. Your #1271 issue needs more investigation as clicking an action button should start the app.

Got it. Thanks for the explanation, @macdonst !

Fixed by #1272