Upgrade cypress test. Login and logout.

Upgrade cypress test. Login and logout.
Add cssSelector for task name element.
Motivation and context

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[x] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage increased (+0.02%) to 62.183% when pulling 3a505c1a33e65d1c66897e51954900730a399931 on DmitriyOparin:upstream/do/upgrade_cypress_test_issue_1810_login_logout into 217a327744a7c2a9601f4ab807972bce67acf99c on openvinotoolkit:develop.


Scroll Forum list

Currently the scrollable forum list is defined with margin top and margin bot.
It is not responsive we have to find a way to improve that.

Done


Website issuing a reload on captcha for a new token

[deleted]

Did you ever manage to fix the issue?


Optimize std::string usage in Dataset

Signed-off-by: yudong.cai<EMAIL_ADDRESS>

/hold

After discussion, it's not safe enough to use sting_view as map key, so close this PR.
/close


pythran hangs on this code (not the c++ compiler)

In the process of debugging https://github.com/serge-sans-paille/pythran/issues/1574, I made this
variant which seems to hang pythran forever.  The single line indicated by <<<<< triggers the hang.
I waited several minutes for pythran to generate the c++ code.
https://gist.github.com/nbecker/d3625706a1f11c1dfabdc06530adebcb

How strange. Using my setup, pythran input.py -P terminates in a few seconds. (using master branch).

I reinstalled master.  Tried again, same result.
Then removed ~/.pythranrc.  Tried again, same result.
Tried manually cleaning site-packages/pythran, reinstall master, same
result.
Are you using python-3.8.3?
On Mon, Jun 29, 2020 at 4:52 PM serge-sans-paille<EMAIL_ADDRESS>wrote:

How strange. Using my setup, pythran input.py -P terminates in a few
seconds. (using master branch).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/serge-sans-paille/pythran/issues/1577#issuecomment-651358271,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA4VUHCMKOVY466OCRCNVDRZD5I3ANCNFSM4OLRLPAQ
.

--
Those who don't understand recursion are doomed to repeat it

Are you using python-3.8.3?

No, that's definitively a possible root cause. I'm currently busy with
https://github.com/serge-sans-paille/pythran/pull/1498 so expect some delay :-/

Just tried again with python-3.5, seems to hang also.
On Mon, Jun 29, 2020 at 5:18 PM serge-sans-paille<EMAIL_ADDRESS>wrote:

Are you using python-3.8.3?

No, that's definitively a possible root cause. I'm currently busy with
https://github.com/serge-sans-paille/pythran/pull/1498 so expect some
delay :-/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/serge-sans-paille/pythran/issues/1577#issuecomment-651372579,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA4VUBEWN6DHDLUOURNBZLRZEAJVANCNFSM4OLRLPAQ
.

--
Those who don't understand recursion are doomed to repeat it

@nbecker can you confirm it's ok with #1608?

I can confirm that pythran completes normally and clang++ compiles the code
for the example gist.
On Mon, Jul 27, 2020 at 5:07 PM serge-sans-paille<EMAIL_ADDRESS>wrote:

@nbecker https://github.com/nbecker can you confirm it's ok with #1608
https://github.com/serge-sans-paille/pythran/pull/1608?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/serge-sans-paille/pythran/issues/1577#issuecomment-664638922,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA4VUDVLWCK5KQXDQMDATDR5XUBDANCNFSM4OLRLPAQ
.

--
Those who don't understand recursion are doomed to repeat it

Great, thanks for confirming and raising the issue. This will make a better release :-)


updating readme file

Update the readme file, new refs. Considering the new updates of the software.

I have reverted the changes to the examples. Following the import convention of #335, TopoNetX should always be imported and used as tnx without explicit imports of classes/functions.


Remove tracked thirdparty/gpgmm in github

[1:30:00] fatal: write error: No space left on device
[1:30:00] fatal: fetch-pack: invalid index-pack output

Looks like there's no enough space left on the CI device.

@huningxin CI can work now, the commit remove tracked thirdparty/gpgmm in github PTAL, thanks.
cc @mingmingtasd @miaobin

@huningxin CI can work now, the commit remove tracked thirdparty/gpgmm in github PTAL, thanks.

Thanks! And it will also fix issue #183 ,right? @fujunwei

@huningxin CI can work now, the commit remove tracked thirdparty/gpgmm in github PTAL, thanks.

Thanks! And it will also fix issue #183 ,right? @fujunwei

Yes, i will close it after merging the commit.

Merge it, thanks for reviewing.


Disabling chart requirement depending on environment

This is a feature request.
It would be great if there is a quick way to enable/disable the installation of a chart requirement depending on which environment it is being deployed.
Normally what we do is to wrap all *.yaml files of a chart inside an if block like so:
{{ if .Values.chartname.enabled }}
...
{{- end }}

and then set the enabled variable to be different in production.yaml and staging.yaml.
This method does not work for dependencies listed in requirements.yaml because there is no standard if enabled block wrapper in the helm create templates.

closing because I just found out about the condition feature in requirements.yaml which does what I need.
condition: subchart1.enabled, global.subchart1.enabled


Clean up working directory

Remove redundant suffix on directories containing theme configuration and out of date examples.
This helps end user to navigate the project easier by removing redundant clutter.
To do:

[x] Use editor name for directory containing the theme configuration
[x] Preserve directory using .gitignore hack

Need to also change the directory in the Javascript and Python script:

[ ] vscToTm.js
[ ] colorSchemeTool.py

Also see #3


Stop pinning uperf pods

Signed-off-by: Raul Sevilla<EMAIL_ADDRESS>Description
Once https://github.com/cloud-bulldozer/benchmark-operator/pull/781 lands, we won't need to pin uperf pods anymore.
Also removing the multi_az implementation, this functionality is useless when we have a fresh deployed cluster, since these cluster usually have 3 or 4 machinesets using different AZs each one.
Removing all this stuff helps in simplifying the benchmark implementation quite a bit.
In case we're interested in providing a pin node feature (which is not available in the orig implementation),  it be addressed in a different PR to keep the original purpose of this one

/rerun all network-perf:GEN_CSV=false ./run.sh

Results for e2e-benchmarking CI Tests

Workload
Test
Result
Runtime

network-perf
GEN_CSV=false ./run.sh
PASS
00:05:13


Info Window

Made info window pop up when clicking on pins. Also added infowindow component.

Thanks for doing this, Mike.


UI bug on Iphone 13 to 15

There is a UI bug on the Platformatic documentation site

I have reattached this image now, should show
@mcollina


Create Asset Link is Broken

Entire wallet disappears and the webpage displays:
Cannot GET /true

duplicate: https://github.com/cryptonomex/graphene-ui/issues/110

A duplicate of itself??


Reverse DSC Abstraction

Pull Request (PR) description
Abstracts all variables into config data
This Pull Request (PR) fixes the following issues
N/A

Codecov Report

Merging #168 into Dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              Dev     #168   +/-   ##
=======================================
  Coverage   90.15%   90.15%
=======================================
  Files          42       42
  Lines        3444     3444
  Branches       13       13
=======================================
  Hits         3105     3105
  Misses        326      326
  Partials       13       13

Impacted Files
Coverage Δ

...SC/DSCResources/MSFT_TeamsUser/MSFT_TeamsUser.psm1
92.3% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Update fails to install

In Obsidian 0.9.13 when I try to update the plugin from the community plugin page from version 0.3.0 to 0.3.2 it fails to update.
Looking at the console, clicking on update throws a 404 error, it doesn't find manifest.json.
In your releases on Github the newest version is 0.3.1

Hmm... That's my bad. I will fix it now. Thank you for alerting me 👍

Everything seems to be working now. Let me know if anything is still broke.


Error out of memory at line 351 in file /home/developer/bitsandbytes/csrc/pythonInterface.c SHOULD BE PLENTY VRAM

Problem allocating RAM on host using managed pointers under the Unified Virtual Memory
and submit this information together with your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
bin /home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/libbitsandbytes_cuda118_nocublaslt.so
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/cuda_setup/main.py:149: UserWarning: /home/developer/mambaforge/envs/Guanaco did not contain ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] as expected! Searching further paths...
warn(msg)
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/usr/local/nccl/lib'), PosixPath('/usr/local/lib/openmpi'), PosixPath('/home/developer/anaconda3/lib'), PosixPath('/usr/local/cuda-11.8/lib')}
warn(msg)
CUDA SETUP: CUDA runtime path found: /usr/local/cuda-11.8/lib64/libcudart.so
CUDA SETUP: Highest compute capability among GPUs detected: 5.2
CUDA SETUP: Detected CUDA version 118
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: Compute capability < 7.5 detected! Only slow 8-bit matmul is supported for your GPU!
warn(msg)
CUDA SETUP: Loading binary /home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/libbitsandbytes_cuda118_nocublaslt.so...
loading base model EleutherAI/pythia-12b...
Loading checkpoint shards: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [01:16<00:00, 25.39s/it]
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/peft/utils/other.py:76: FutureWarning: prepare_model_for_int8_training is deprecated and will be removed in a future version. Use prepare_model_for_kbit_training instead.
warnings.warn(
adding LoRA modules...
trainable params: 188743680 || all params:<PHONE_NUMBER>0 || trainable: 1.5683137988981302
loaded model
Found cached dataset parquet (/home/developer/.cache/huggingface/datasets/tatsu-lab___parquet/tatsu-lab--alpaca-2b32f0433506ef5f/0.0.0/2a3b91fbd88a2c90d1dbbb32b460cf621d31bd5b05b934492fdef7d8d6f236ec)
100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 1/1 [00:00<00:00, 304.84it/s]
Loading cached processed dataset at /home/developer/.cache/huggingface/datasets/tatsu-lab___parquet/tatsu-lab--alpaca-2b32f0433506ef5f/0.0.0/2a3b91fbd88a2c90d1dbbb32b460cf621d31bd5b05b934492fdef7d8d6f236ec/cache-7688172b91a1f6d4.arrow
Loading cached processed dataset at /home/developer/.cache/huggingface/datasets/tatsu-lab___parquet/tatsu-lab--alpaca-2b32f0433506ef5f/0.0.0/2a3b91fbd88a2c90d1dbbb32b460cf621d31bd5b05b934492fdef7d8d6f236ec/cache-0b873bde6329608e.arrow
torch.float32 705996800 0.058683338085652396
torch.int8<PHONE_NUMBER>0 0.9413166619143476
0%|                                                                                | 0/10000 [00:00<?, ?it/s]
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/autograd/_functions.py:318: UserWarning: MatMul8bitLt: inputs will be cast from torch.float32 to float16 during quantization
warnings.warn(f"MatMul8bitLt: inputs will be cast from {A.dtype} to float16 during quantization")
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/transformers/models/gpt_neox/modeling_gpt_neox.py:229: UserWarning: where received a uint8 condition tensor. This behavior is deprecated and will be removed in a future version of PyTorch. Use a boolean condition instead. (Triggered internally at ../aten/src/ATen/native/TensorCompare.cpp:493.)
attn_scores = torch.where(causal_mask, attn_scores, mask_value)
Error out of memory at line 351 in file /home/developer/bitsandbytes/csrc/pythonInterface.c
/arrow/cpp/src/arrow/filesystem/s3fs.cc:2598:  arrow::fs::FinalizeS3 was not called even though S3 was initialized.  This could lead to a segmentation fault at exit

and submit this information together with your error trace to: https://github.com/TimDettmers/bitsandbytes/issues
bin /home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/libbitsandbytes_cuda118_nocublaslt.so
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/cuda_setup/main.py:149: UserWarning: /home/developer/mambaforge/envs/Guanaco did not contain ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0'] as expected! Searching further paths...
warn(msg)
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: The following directories listed in your path were found to be non-existent: {PosixPath('/usr/local/nccl/lib'), PosixPath('/home/developer/anaconda3/lib'), PosixPath('/usr/local/cuda-11.8/lib'), PosixPath('/usr/local/lib/openmpi')}
warn(msg)
CUDA SETUP: CUDA runtime path found: /usr/local/cuda-11.8/lib64/libcudart.so.11.0
CUDA SETUP: Highest compute capability among GPUs detected: 5.2
CUDA SETUP: Detected CUDA version 118
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/cuda_setup/main.py:149: UserWarning: WARNING: Compute capability < 7.5 detected! Only slow 8-bit matmul is supported for your GPU!
warn(msg)
CUDA SETUP: Loading binary /home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/libbitsandbytes_cuda118_nocublaslt.so...
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++ BUG REPORT INFORMATION ++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++ ANACONDA CUDA PATHS ++++++++++++++++++++
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/torch/lib/libtorch_cuda_linalg.so
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/torch/lib/libtorch_cuda.so
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/torch/lib/libc10_cuda.so
/home/developer/mambaforge/envs/Guanaco/lib/python3.10/site-packages/bitsandbytes-0.39.0-py3.10.egg/bitsandbytes/libbitsandbytes_cuda118_nocublaslt.so
++++++++++++++++++ /usr/local CUDA PATHS +++++++++++++++++++
/usr/local/lib/python3.8/dist-packages/torch/lib/libtorch_cuda_linalg.so
/usr/local/lib/python3.8/dist-packages/torch/lib/libtorch_cuda.so
/usr/local/lib/python3.8/dist-packages/torch/lib/libc10_cuda.so
/usr/local/lib/python3.8/dist-packages/torch/lib/libc10d_cuda_test.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libtorch_cuda_linalg.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libtorch_cuda.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libc10_cuda.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libtorch_cuda_cu.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libtorch_cuda_cpp.so
/usr/local/cuda-11.8/targets/x86_64-linux/lib/stubs/libcuda.so
/usr/local/cuda-11.8/targets/x86_64-linux/lib/libcudart.so
/usr/local/cuda-11.8/compat/libcuda.so
/usr/local/cuda-11.8/nsight-compute-2022.3.0/target/linux-desktop-glibc_2_11_3-x64/libcuda-injection.so
/usr/local/cuda-11.8/nsight-compute-2022.3.0/target/linux-desktop-glibc_2_19_0-ppc64le/libcuda-injection.so
/usr/local/cuda-11.8/nsight-compute-2022.3.0/target/linux-desktop-t210-a64/libcuda-injection.so
+++++++++++++++ WORKING DIRECTORY CUDA PATHS +++++++++++++++
++++++++++++++++++ LD_LIBRARY CUDA PATHS +++++++++++++++++++
++++ /usr/local/cuda-11.8/extras/CUPTI/lib64 CUDA PATHS ++++
++++++++++++++++ /usr/local/lib CUDA PATHS +++++++++++++++++
/usr/local/lib/python3.8/dist-packages/torch/lib/libtorch_cuda_linalg.so
/usr/local/lib/python3.8/dist-packages/torch/lib/libtorch_cuda.so
/usr/local/lib/python3.8/dist-packages/torch/lib/libc10_cuda.so
/usr/local/lib/python3.8/dist-packages/torch/lib/libc10d_cuda_test.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libtorch_cuda_linalg.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libtorch_cuda.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libc10_cuda.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libtorch_cuda_cu.so
/usr/local/lib/python3.8/dist-packages/torch-1.13.1-py3.8-linux-x86_64.egg/torch/lib/libtorch_cuda_cpp.so
++++++++++ /usr/local/cuda-11.8/lib64 CUDA PATHS +++++++++++
+++++++++++ /usr/lib/x86_64-linux-gnu CUDA PATHS +++++++++++
/usr/lib/x86_64-linux-gnu/libcuda.so
/usr/lib/x86_64-linux-gnu/libicudata.so
++++++++++++++++++++++++++ OTHER +++++++++++++++++++++++++++
COMPILED_WITH_CUDA = True
COMPUTE_CAPABILITIES_PER_GPU = ['5.2', '5.2', '5.2', '5.2']
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++ DEBUG INFO END ++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Running a quick check that:
+ library is importable
+ CUDA function is callable
WARNING: Please be sure to sanitize sensible info from any such env vars!
SUCCESS!
Installation was successful!

I have the same issue. maybe helpful or not - my observation: the warmup seems to start for maybe 10 seconds. so the GPU (mine RTX3090) runs at 100% using maybe 40% of VRAM (7b modell) before suddenly everything stops as @phalexo mentions.
Planty of RAM and VRAM free.

This is a duplicate of #477. Please find my response there and continue the discussion in that issue. Higher memory usage is expected on Windows.


Some environment variables are not set

I'm working with your level_4 container (thanks for setting this up!) trying to use SPM without matlab. In the Dockerfile you set several environment variables, but when I run the container not all of them are set.
This is the output of docker inspect --format='{{ json .Config.Env }}:
["NB_UID=3602288","PATH=/usr/lib/fsl/5.0:/opt/conda/envs/python2/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","DEBIAN_FRONTEND=noninteractive","CONDA_DIR=/opt/conda","SHELL=/bin/bash","NB_USER=jovyan","HOME=/home/jovyan","LC_ALL=en_US.UTF-8","LANG=en_US.UTF-8","LANGUAGE=en_US.UTF-8","NEURODEBIAN_URL=http://neuro.debian.net/lists/jessie.de-md.full","XDG_CACHE_HOME=/home/jovyan/.cache/","FSLDIR=/usr/share/fsl/5.0","FSLOUTPUTTYPE=NIFTI_GZ","FSLMULTIFILEQUIT=TRUE","POSSUMDIR=/usr/share/fsl/5.0","LD_LIBRARY_PATH=/opt/mcr/v91/runtime/glnxa64:/opt/mcr/v91/bin/glnxa64:/opt/mcr/v91/sys/os/glnxa64:/opt/mcr/v91/sys/opengl/lib/glnxa64:/usr/lib/fsl/5.0:","FSLTCLSH=/usr/bin/tclsh","FSLWISH=/usr/bin/wis","MATLAB_VERSION=R2016b","MCR_VERSION=v91","MCR_INHIBIT_CTF_LOCK=1","SPM_VERSION=12","SPM_REVISION=r6906","SPM_DIR=/opt/spm12","SPM_EXEC=/opt/spm12/spm12"]

You see that for example, none of the variables you set in the level_2 and level_3 Dockerfiles are set, nor it is MATLAB_CMD.
Note also that Ants and AFNI paths are not in PATH.

Hi @iglpdc, thank you for your input. I had the suspicion that it doesn't take over the ENV variables, but I didn't know how to check for it. Thanks to your input, now I know, thanks!
I guess the best thing is to put them all in startup.sh script and have it run at the end of each Dockerfile. What do you recommend?
I'm very sorry for it, but I'm still playing around with the "order of the levels". I want to create a relative small image, to teach people nipype (see https://github.com/miykael/nipype_course) and I guess it makes more sense to move FreeSurfer to level4 and SPM to level2.

Out of curiosity, how did you find this?

Hi @miykael. I'm not sure which is the best way to proceed. I'm pretty new to docker. I made a small PR that I think it fixes one of the issues with the ENV variables, but I'm not sure if this is all. (I don't have a good machine to test it).
Eventually, I think what it'd be really useful would be to have the different apps in different containers and be able to call them from nipype. But I don't know really which is the best way to go.
For example, I'm currently working on a pipeline that I'd like to run with both SPM8 and SPM12, basically to see how switching to the newer version affects the results. It'd be nice if I could use all the same containers and just "switch" the SPM container from version 8 to 12, without having to rebuild a big container with the whole stack.
I found this repo thru your awesome tutorials for nipype (thanks for that too!).

Thanks for your changes. I'm looking into them now and I will test them on my machine to make sure that everything works nicely.
I'm also new to docker, that's why there's still many changes in my files. But yes, your right. It would be great if Nipype could decide which containers to get. But I'm not sure if this can be done, within the container. Also, I think they always have to be stacked on top of each other.
Hmm.. you're right, let me see if I can add SPM8.

@iglpdc, no I mixed everything up a bit, but it hopefully will work. I have to check it on https://hub.docker.com/r/miykael/.
I was looking into SPM8. The problem is that SPM needs to be the standalone version, so that it can work with MCR (MATLAB Compiler Runtime, see https://en.wikibooks.org/wiki/SPM/Standalone). The current SPM12 version is like this. If you can provide me with an SPM8 version, than I'm happy to add it in the Dockerfile.


Limiting upstream crates may add new impl of trait in future versions

Hello,
I've run into this one a few times now when working with generics, and I haven't really found a way to bypass it in most cases.
I completely get why this is here, "be careful, your behaviour may change if you update your crates, it may even stop compiling altogether" seems like a fair thing to warn against.
BUT: most of the time, when this error appears, it's for types that have been stabilised a while ago, and are way more likely never to add new implementations.
Wouldn't it be a good thing to be able to tell Rust "Yes, I know, this might conflict in the future, but with the current version, it's fine, so let me build until there ARE conflicts" ?
Rust's generics through traits and monomorphisation is one of my favourite features, but sometimes, in situations like this, Rust is TOO smart for its own good, and I think there should be ways to temper it.
This would also help with the problems that have been mentioned in the context of specialization and negative reasoning (maybe this could even enable negative reasoning which has the advantage of being more flexible and expressive than the currently selected "default" oriented specialisation), since breaking changes due to new implementations have always been limiting factors for them.

This restriction is really strict, sometimes backward compatibility is not possible, let alone forward compatibility.

Yeah, this shouldn’t be an error, but a (silenceable) warning. I get

note: upstream crates may add a new impl of trait my_crate::ExtraAttributes<Image> for type my_other_crate::Section in future versions

I know that I wont implement this, so I want to be able to tell the compiler that.

You can work around this with macro (impl_xxx!(TypeA, TypeB, ...)) - that way you're not using trait constraints because you are explicit.
But this is something which definitely should be fixed in language. I've seen it so many times already it's obvious that this was bad idea.

I guess it's worth pointing to this tracking issue about negative impls: https://github.com/rust-lang/rust/issues/68318

I'll leave here an example i've found if this "feature" causing problems
pub trait Responseable {
    fn into_stream (self) -> Box<dyn Stream<Item = u8>>;
}

impl<S: 'static + Stream<Item = u8>> Responseable for S {
    #[inline(always)]
    fn into_stream (self) -> Box<dyn Stream<Item = u8>> {
        Box::new(self)
    }
}

// conflicting implementations of trait `server::response::Responseable` for type `()`.
// upstream crates may add a new impl of trait `futures::Stream` for type `()` in future versions
impl Responseable for () {
 #[inline(always)]
    fn into_stream (self) -> Box<dyn Stream<Item = u8>> {
        Box::new(futures::stream::empty())
    }
}

As you see, rust is basically saying me "well, maybe someone sometime tries to do the same as you, so you can't do it".
This causes very problems very often for no reason, and it should probably be a warning, not an error

recent case was using Pod from bytemuck

^^ Exact same thing here, I try to implement a trait to use bytemuck::cast_slice for all Pod + Zeroable type. And the problem appear when I add for Vec

This is bizarre, why is this still a thing? Literally anything can be changed and broken in a future version of a crate why pick this in particular???

I guess it's because new trait implementations are not commonly considered breaking changes (even though they can be).
Suppose your crate b depends on crate a at version 1.0. You implement a trait for a type within a that is not conflicting in the current version. Later on, a releases a breaking change in minor version 1.1 by adding a trait implementation that conflicts with your implementation. If you specified a's version as 1.0 and not ~1.0 or =1.0, a user that depends on your crate would use version 1.1 by default, in which case your crate no longer compiles.
It still feels unnecessarily strict to disallow all implementations that might conflict in the future, though. My use case is that I want my API to work with anything that implements FromStr, but also with time::OffsetDateTime which doesn't implement FromStr, among others. I thought I could solve this with a new trait similar to FromStr, with a blanket implementation for anything that already implements FromStr, along with separate implementations for OffsetDateTime and other types. But that is considered conflicting. As a workaround, I have to make a newtype for OffsetDateTime and implement FromStr for it, which is much less convenient for users of the API.
IMO, a warning that an implementation might conflict in the future would be enough. The warning can be silenced with an annotation, and that annotation would immediately make clear what the problem is if a conflicting implementation is ever added. The warning could also remind you to use a stricter version range for the dependency.

impl<E> From<E> for MyErrorType where E: Into<BaseLibErrorType> {
    fn from(value: E) -> Self {
        Self::BaseError(value.into())
    }
}
impl From<ErrorTypeFrom3rdPartyLib> for MyErrorType {
    // 🚫 ⚠ 🛑 STOP 🛑 ⚠ 🚫
    // BaseLibErrorType might implement From<AnyTypeThatCouldEverExistUntilTheEndOfTime>
    // Shame on you for not considering this possibility
}

smh

+1 here, would love for this to just be a warning. I'm having this issue warning me about stuff that as the OP said is stable:
I want to implement my error context trait for Result<T, E: std::error::Error> and E: std::error::Error generically,
but theoretically they might decide to impl std::error::Error for Result...

+1 this feels very arbitrary. As @SalsaGal  said - there's basically an unlimited number of things a library author could do to break compatibility in existing code, and explicitly preventing this isn't a stated goal of the language (nor should it be). Why is this thing in particular disallowed, but not any of the hundreds of other arbitrary ways someone could break their code for consumers.
I ran into this trying to implement a trait defined in my code on various collection types - was all fine until I tried to add an impl on a <T: ExactSizeIterator> trait bound rather than a concrete type (because there's too many bespoke iterator impls out there for impl-ing on concrete types to be feasible).
pub trait Foo {
    fn foo(&self) -> &'static str;
}

impl<Item> Foo for Vec<Item> {
    fn foo(&self) -> &'static str {
        "I'm a Vec!"
    }
}

impl<K, V> Foo for HashMap<K, V> {
    fn foo(&self) -> &'static str {
        "I'm a HashMap!"
    }
}

impl<Item, T: ExactSizeIterator<Item = Item>> Foo for T {
    fn foo(&self) -> &'static str {
        "I don't compile :("
    }
}

Gives me 'conflicting implementations of trait len::Foo for type std::vec::Vec<_>
upstream crates may add a new impl of trait std::iter::Iterator for type std::vec::Vec<_> in future versions'.
It sounds like the specialization feature might make this problem go away for this specific use case though? Although currently enabling it doesn't change the error.

I agree that this error make little sense in some cases (e.g. Result might implement Error), but I'm betting it's due to some type solver limitation. Besides specialization, chalk might affect this behavior as well.
I'd prefer being able to specify the impls are unsafe and have the compiler "bail" when the type with multiple implementations already exists instead of always doing so proactively. By bail I mean just ignore all traits/implementations when multiple apply when the user is trying to use some trait item and note conflict in the error  - currently the compiler reports when some function/type/trait exists but isn't imported, so something along those lines (with unsafe) would work much better here.
Alternatively, there's #[stable(since = "1.0.0")] annotations on std trait implementations so the compiler can pick the earliest one for std types - which is the most important case IMO because stdlib can't be vendored as easily as other crates, this would preserve backwards compatibility.

This is the single worst design choice in Rust I've ever had the misfortune of encountering. The worst part is the error doesn't even go away if I set the dependency to a specific version.


When proceeding to checkout we shouldn't call action for clearing delivery mode

When user proceeds through checkout but does not complete his order, instead will add additional items to the cart, we shouldn't call clearing action for delivery mode when proceeding to checkout again, as it might create visible confusion to end user.

After investigating and consultation with @marlass the change isn't necessary here, as this clear is intended due to fact, that backend is not clearing user selection for us even when an address was changed,


Fix: Connect Bank account - Crash when completed adding BA manually

Details

https://github.com/Expensify/App/issues/28811
Fixed Issues

$ https://github.com/Expensify/App/issues/28811
PROPOSAL: https://github.com/Expensify/App/issues/28811#issuecomment-1746914377
Tests

Open any workspace and start bank account flow
Reach to step 4 and click next after selecting required checkboxes
Verify console warning isn't shown for testID

[X] Verify that no errors appear in the JS console

Offline tests

Open any workspace and start bank account flow
Reach to step 4 and click next after selecting required checkboxes
Verify console warning isn't shown for testID

QA Steps

Open any workspace and start bank account flow
Reach to step 4 and click next after selecting required checkboxes
Verify console warning isn't shown for testID

[X] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[X] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))

[X] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web
https://github.com/Expensify/App/assets/14358475/44ac6f64-fb17-4037-b27b-abc7a8246464

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@srikarparsi setting displayName for class component failing the lint with
error  Class components must not set the displayName property  rulesdir/display-name-property
So assigned the string value directly to testID in the latest commit.

Closing this PR in favor of https://github.com/Expensify/App/issues/28334 as PR for that issue targeting the same.


Enumerated Values with numeric value 0 are validated as false

Verified on 5.0 and 5.1
When testing an enumerated value that has the numeric value of 0, this will be evaluated as false.
Steps to reproduce
Paste this into the console:
if ([DayOfWeek]::Sunday) { "It Works" }
else { "It doesn't work" }

Expected behavior
Output:
It Works
Actual behavior
Output:
It doesn't work
Environment data

> $PSVersionTable
PSVersion                      5.1.14393.693
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.693
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

This is by design. Enums are simply integer values and In a PowerShell Boolean context, 0 evaluates to false.

No offense, but that's very much a matter of perspective. The system treats them like numbers, yes. But logically they represent a specific thing. A day of week. A color. A mode or type of action.
So yeah, right from the programmatic background it might make sense. But from a human's perspective it's totally counterintuitive.
I haven't been able to explain this to a single admin colleague yet without his scratching his head and calling it insanity.

If we had a better story for breaking changes, I would have changed this behavior years ago because I think the design is wrong.
If we could statically detect code that would be broken by changing this, it would be easier for us to make an informed decision on the trade-offs. As it stands, changing behaviors might be as bad as leaving things as is.

Actually, I was rather surprised you introduced this change in 5.0.
I had lots of failing functions that used these sub-optimal - but previously working - notations to check whether a parameter was bound at all:
if ($DayOfWeek) { }
if ($PSBoundParameters["DayOfWeek"]) {}

Still lots of examples for this lying around the web, all of which will not work properly with most Enums. And especially the first one is one heck of a lot easier to read than always having to use
if ($PSBoundParameters.ContainsKey("DayOfWeek")) {}

In that case, we should revisit this.

@PowerShell/powershell-committee discussed this and this usage is something we agree to support so that enums are not $null and retain the previous behavior

@SteveL-MSFT Should we close "by design"?

@SteveL-MSFT Perhaps we need "Consider-For-Version-7" label for such issues. We could re-review in time of 7.0 version planning.
@FriedrichWeinmann The best way is to open issue in PSScriptAnalyzer repo. This will definitely reduce the number of scripts affected by this problem and allow it to be fixed here as proposed.

@iSazonov the intent is to never have a v7 otherwise we'll end up fragmenting the PowerShell community further between 5.x and 6.  I've added the Breaking-Change label to make it easier to find this later if necessary.


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-extensions/eventing-writers
/assign knative-extensions/eventing-writers
Produced by: knative-extensions/knobots/actions/update-deps

/test build-tests

closing, conflicts


React Fast Refresh broken with reason-react template v0.20.0

I believe the HMR for react is broken with this template.
Whenever I change anything in my source code, the whole page reloads, instead of just updating the parts that need to. I don't know if this is a problem with vite-plugin-react 2.0 or with vite.
Please can you confirm that HMR is indeed broken for react or did it just break with reason ?
Thank you guys so much for your work on vite, it is AWESOME :heart:

Just checked with 0.20.7 and it seems to be working as expected.

@yyx990803 with the react-template ??

My bad I apologize, it is working. Thank you again for the great work on vite :heart:


Crash report - conduit facades

Hello, I recently tried to paint a conduit facade using a TE Hardened Cache... Just to see if I could. It worked, so I attempted to place it on an item conduit. It crashed my game immediately, and now every time I log into the server, I crash before I even see the game beyond the loading screen. My brother was on the server, playing just fine, when he went to attempt to break said conduit. As soon as he looked at it, his game crashed as well.
Here's the crash report: http://pastebin.com/cujhvDBN
Any help or advice would be greatly appreciated!

My mistake, wrong forum.


Usability of usage limit and type

Hi,
Can you please extend the explanation of Usage limit & types - What and How does Channel /customer specific setups work if the coupon needs to be customer specific?

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

ID: 86041e5e-3283-90a8-9f7b-3556106e7293
Version Independent ID: b5b030ba-df8a-4ae9-2a0e-db6dc0e12da4
Content: Set up coupons for retail sales - Finance & Operations | Dynamics 365 | #MSDyn365FO
Content Source: articles/retail/retail-coupons.md
Service: dynamics-365-retail
GitHub Login: @scott-tucker
Microsoft Alias: scotttuc

@scott-tucker, I created work item # 251855 for investigation.

The coupon usage of type ‘Customer’ and ‘Company’ are updated in HQ using the 'Real Time Service' aka RTS call, but, if the call fails, then we update the channel database. This data gets synced to HQ using the pJob.
For the Channel based usage limit, the data is written to the Channel database and synced to HQ using the pJob.

please assign this to @ShalabhjainMSFT .  I couldn't figure out how to re-assign it myself.


Container installation

I have been following a MongoDB guide for deploying PHP with MongoDB client / SDK here. In this guide, they use your composer package.
However, I would like to place this into a Docker container, and was able to get the mongodb/mongodb package installed by replacing the __DIR__ location and hardcoding in a full path to "/usr/bin/vendor/autoload.php" in a PHP page's require_once directive. I simply appended the installation of PHPDotEnv to this same composer command:
RUN cd /usr/bin && composer require mongodb/mongodb vlucas/phpdotenv
I rebuilt the Dockerfile and uploaded to Docker Hub, which was successful, as redswitch/php-mongodb
Now on 1st run, I cannot load the package. I have tried both these commands but errors same each time:
$dotenv = Dotenv\Dotenv::createImmutable("/usr/bin");
$dotenv = Dotenv\Dotenv::createImmutable(__DIR__);
To load the mongodb package, I use:
require_once '/usr/bin/vendor/autoload.php';
(As opposed to __DIR__ . '/vendor/autoload.php';)
My docker-compose.yml moves the /var/www/html/ directory to the same directory, i.e.:
services:
  web:
    image: redswitch/php-mongodb:8.0-1.9.0
    container_name: web
    volumes:
      - ./html:/var/www/html

I cannot find any files or folders inside the container matching "Dotenv".
Can I ask for further troubleshooting / assistance please?

Thanks for getting in touch. Since this is a support request, I'd recommend asking on some forums or emailing me direct if you'd like to buy some paid support.


nixos/kvmgt: fix starting condition

Motivation for this change
Instead of #48640. I've asked on related mailing lists and systemd.path helper was the solution that worked https://www.freedesktop.org/software/systemd/man/systemd.path.html
cc @Mic92
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Have you tested this? (since I don't see any check-marks).
Can this be tested with any modern Intel GPU?

@Mic92

Have you tested this? (since I don't see any check-marks).

It works
$ systemctl status kvmgt-i915-GVTg_V5_8
● kvmgt-i915-GVTg_V5_8.service - KVMGT VGPU i915-GVTg_V5_8
   Loaded: loaded (/nix/store/2ycqbzkrx7bmslykc258hnmyvi2r73a5-unit-kvmgt-i915-GVTg_V5_8.service/kvmgt-i915-GVTg_V5_8.service; linked; vendor preset: enabled)
   Active: active (exited) since Sun 2019-06-16 13:48:57 MSK; 1min 4s ago
  Process: 942 ExecStart=/nix/store/fyxcppddjg7abrand8n10gwzm5gknc48-bash-4.4-p23/bin/bash -c echo a297db4a-f4c2-11e6-90f6-d3b88d6c9525 > /sys/bus/pci/devices/0000:00:02.0/mdev_supported_types/i915-GVTg_V5_8/create (code=exited, status=0/>
 Main PID: 942 (code=exited, status=0/SUCCESS)

июн 16 13:48:57 nixos systemd[1]: Starting KVMGT VGPU i915-GVTg_V5_8...
июн 16 13:48:57 nixos systemd[1]: Started KVMGT VGPU i915-GVTg_V5_8.

Can this be tested with any modern Intel GPU?

I think using 5th to 7th generation. I'm not sure they upstreamed support for 8th+ generations. Perhaps using latest kernel. Here's an instruction https://nixos.wiki/wiki/IGVT-g

@Mic92 Thank you!


Subclassing is hard

Since all the 'static' functions (like concat, wrap, etc) use the ByteBuffer definition itself instead of "this", it's hard to subclass it. By using this.constructor and this (in static) instead of forcefully deriving from ByteBuffer, it can work. I can submit a patch, and I think it won't break anything, but will make it easier to add methods to the class without monkeypatching it

export class BB extends ByteBuffer {

    static allocate( capacity?: number, littleEndian?: number, noAssert?: boolean ): BB {
        var c: BB = <any>super.allocate(capacity, littleEndian, noAssert);
        c.readBytes = this.prototype.readBytes;
        c.refresh = this.prototype.refresh;
        return c;
    }

    static wrap( buffer: ByteBuffer | Buffer | ArrayBuffer | Uint8Array | string | Array<number>, enc?: string | boolean, littleEndian?: boolean, noAssert?: boolean ): BB {
        var c: BB = <any>super.wrap(buffer, enc, littleEndian, noAssert);
        c.readBytes = this.prototype.readBytes;
        c.refresh = this.prototype.refresh;
        return c;
    }

    static concat( buffers: Array<ByteBuffer | Buffer |  ArrayBuffer | Uint8Array | string>, encoding?: string | boolean, litteEndian?: boolean, noAssert?: boolean ): BB {
        var c: BB = <any>super.concat(buffers, encoding, litteEndian, noAssert);
        c.readBytes = this.prototype.readBytes;
        c.refresh = this.prototype.refresh;
        return c;
    }

}

So, what you are proposing basically is to change https://github.com/dcodeIO/bytebuffer.js/blob/master/src/methods/static/allocate.js#L12
to: return new this(capacity, littleEndian, noAssert);
Correct?

Yup, exactly that, so it can be inherited from without those hacks

So, is this pattern safe to use across (not so modern) browsers?

Yup, you can check in built-in classes, like [].constructor, ({}).constructor, (0).constructor,(function(){}).constructor and so on


kubeadm v1.7 documentation updates

@kubernetes/sig-cluster-lifecycle-pr-reviews @jbeda @pipejakob @lukemarsden @roberthbailey @steveperry-53
Will fix quite a lot of docs issues in the kubeadm repo...

This change is

Thanks for the review @dmmcquay @chenopis @fabriziopandini!
May I ask you to take an other look?
Also I'd like @jbeda and @lukemarsden to sign off on this and then we can merge it into the v1.7 branch...
/assign @jbeda @lukemarsden

@jbeda @lukemarsden This PR still requires your tech review.
FYI, all feedback must be addressed and LGTMs given by EOD Tue, June 27th so that this can be merged for the 1.7 release on June 28th.

@luxas BTW, a conflict popped up for docs/admin/kubeadm.md.

@chenopis Yeah, resolving that now...

@chenopis Conflict resolved

@jbeda Look good to you now?

@luxas Looks like this PR just needs one more round of changes, then I can merge it.

@chenopis See the new commit; I addressed Luke's comments

@luxas Ok, great. You can put any additional changes in a patch PR. Thx

LGTM


Is there a reason for SegmentHistory to internally use a Vec vs BTreeMap?

SegmentHistory uses a Vec<(i32, Time)> internally while essentially mandating the interface and structure of a BTreeMap<i32, Time>.
Using a BTreeMap instead would theoretically improve insertion/removal costs to be logarithmic rather than linear, and it would statically guarantee that the list was sorted. It would also prevent mutating the keys when using iter_mut(), rather than only having a warning. (Given the way run data is structured, allowing this currently is probably not a great idea, and I think would virtually always constitute an error, as opposed to removing and inserting with the changed key.)
It would mean that the collection would no longer be contiguous in memory, but unless that severely impacts performance, I propose changing it to use BTreeMap instead of a Vec of tuples. This should be able to be done without changing the public interface, since the internal type is not publicly exposed. I'm willing to submit a pull request.
Edit: After looking into some of the function signatures, true safety for iter_mut would likely require a "breaking" change (the Item would be (&i32, &mut Time) instead of (&mut i32, &mut Time)), but it's only used in one place in the rest of the library, and it's unlikely to be used often in userland code, and will coerce just fine if it's not mutated (like in the core library) so I think it's still worth doing eventually.

Yeah it's a trade-off between iteration performance and insertion / removal performance. I'd say that iteration is the main use case, and insertion / removal rarely happen (and iirc it almost always inserts at the end). If you make any changes, I'd like to see some benchmarks that confirm that it's faster for our use case.

That makes sense. My initial reason for digging into it was trying to build a SoB that only kept track of full splits (and not subsplits,) so when moving through subsplits and finding that a segment didn't complete, it'd be removed from that SegmentHistory. This being a case for regularly removing was what prompted me to look at it. Obviously there are other ways to handle it.
I do have my doubts that iteration speed is a bottleneck at a higher level for any of the operations where it's used, but benchmarks would prove/disprove that as well. I also think using a custom iter_mut that doesn't allow changing the index is something that's worth considering regardless of the backing data structure.
Tangentially, I DO think that using a BTreeMap for segments in Run could improve things like re-ordering splits a great deal. I just had to move segments around, and moving a couple adjacent splits down one spot made the program hang for over a minute, with absolutely no split history or times to deal with. I'm fairly sure this is caused by the inefficiency of array insertion, and I think that's a use case that is common enough to warrant looking at further.

one spot made the program hang for over a minute

Are you talking about the web LSO or the original LiveSplit or what? And if so, how do I reproduce that?

I'll close this for now. I'm fairly strongly convinced that you made the original LiveSplit hang, which this repository does not relate too. If it was indeed an issue with LiveSplit One, please let me know more details and then we can reopen this.


WIP: NCD - Danger Signs and Symptom Review activities

#397
#398

@mariano-dagostino please review


New Array Extension

Arrays Extension
Overview
This repository contains the code for a new Arrays Extension, which will add support for 2D and 3D arrays in TurboWarp.

Features

Create 2D arrays with dimensions
Set and get values in 2D arrays at specific indices
Check if a 2D array exists
Get the row and column count of a 2D array
Duplicate a 2D array
Count occurrences of an item in a 2D array
Create 3D arrays with customizable dimensions
Set and get values in 3D arrays at specific indices
Check if a 3D array exists
Get the row, column, and depth count of a 3D array
Duplicate a 3D array
Count occurrences of an item in a 3D array

Note

Indices start from 1 instead of 0 to coincide better with vanilla Lists
An array of a type (2D, 3D) of the same name as another array of that type will overwrite the name of any preexisting array
2D arrays and 3D arrays of the same name will not overwrite the other type of array of the same name

is it possible for you to make array resizing blocks?

is it possible for you to make array resizing blocks? @SpyroStudios ?

Probably, but what would you want me to do if there already are existing values


style(weave): columns button icon and some styling

Description
https://github.com/user-attachments/assets/9013787f-baf2-4062-abcf-10c66563e347
Changes some styling on the filter bar
Fixes the resizing behavior
changes column icon

It's not taking the parent indicator into account:


MGMT: WS-FED Attribute Release Option checkbox should be removed

Selecting a WS-FED client type somehow presents a checkbox that user must click in order to see attribute release options. The checkbox must be removed and options must be visible immediately

A fix for this has been pushed to mgmt-5.2-bugs


Add options parameter to Date.to_locale_time_string

Fixes #4383

I haven't been able to run the tests for js-sys locally when following the contributing guide, getting a wasm-bindgen-cli mismatch that I can't seem to resolve even when using cargo install -f wasm-bindgen-cli --path ../cli/ --locked to build wasm-bindgen-cli from the repo. The tests build though 🤷

This should be marked as a breaking change since it adds a parameter to an existing function. Looks there's a label for that but I can't add labels if someone can do that for me. I'll get a changelog entry added now.


Support large launches with up to 2^32 threads on OptiX backend

Mitsuba rendering tasks executed using Dr.Jit's OptiX backend are currently limited to 2^30 ≈ 1 billion Monte Carlo samples in total, which sounds like a lot. However, that's just enough to render a full HD image using 512 samples per pixel:
19201080512 = 1'061'683'200 < 1'073'741'824 = 2^32
This commit increases the limit to 4 billion, which corresponds to 2048 samples per pixel at 1080p resolution. This is the absolute maximum wavefront size that Dr.Jit can accommodate due to its 32 bit based indexing.
It's worth mentioning that further increasing that limit by upgrading to 64 bit indexing is not a good idea as this comes with significant costs on modern GPUs that lack 64 bit registers. Instead, multiple rendering passes should be used in the renderer to handle such very large rendering tasks.
What this commit commit enables is to internally run multiple passes without re-tracing when the sample count is between 2^30 and 2^32, which makes it less likely that users would require the n_passes parameter of the renderer (which arguably adds a few complications).

The CI failure is an unrelated issue that's also broken on master. Likely that slipped through while the CI was not getting triggered. My other PR (#32) fixes it.


Attachments 控件问题

[在此处输入反馈]
我想知道Attachments 控件支持上传什么类型文件，不支持什么类型文件
I want to know Attachments  can upload which type file to sharepoint and which type file can not be upload.
I try to upload a .pbix file to sharepoint ,but failed
文档详细信息
⚠ 请勿编辑此部分。 learn.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: c68b4c33-12f9-3b26-5508-7173fe207ada
Version Independent ID: 0451a3c0-7d56-63b3-e8ff-acc33d6c5daf
Content: Power Apps 中的 Attachments 控件 - Power Apps
Content Source: powerapps-docs/maker/canvas-apps/controls/control-attachments.md
Service: powerapps
Sub-service: canvas-maker
GitHub Login: @chmoncay
Microsoft Alias: chmoncay

### Tasks
- [ ] Add a draft title or issue reference here

Thanks for your comment, @WLXcarry. This issue has been assigned to the doc author for review.

@bishalgoswami  this is not a localization issue.  This is a content issue since the user wants to get more information on how to know what type of file the Attachments control supports uploading and what type of file it does not support


Invalid control Bounds when RenderTransform is applied

I think this also affect the input when using pointer event and GetPosition relative to transformed control.

Yes, currently render transforms are just that: they are transforms applied at render time. Hit testing and the diagnostics window aren't currently aware of them.


feat(app): support daemon mode on non-Windows platforms

Added a new command-line flag -daemon to run the application in the background as a daemon. This option is only available for non-Windows operating systems due to platform-specific process handling. When enabled, the application restarts itself with the same arguments except for the -daemon flag, prints the PID of the background process, and then exits the current process.
Simplified replacement for #440

Why doubt?

Why not use simple & symbol?

Why not use simple & symbol?

These are completely different things. & is a shell function, not a kernel.
For example, a background process started by & will not stay alive after the shell session is closed

Thanks!

https://github.com/AlexxIT/go2rtc/releases/tag/v1.9.0


Exclude examples as a package

Hi, currently "examples" is built as a separate package which can pollute a user environment. This should prevent that.
Once merged, would you mind publishing a new version with it as we would need it downstream.
Thanks!
Ref: https://github.com/conda-forge/staged-recipes/pull/19074

This should be fixed in the 0.3.1 release.


Add eth deposit and withdraw trace

ERC20 LINK(10 link) deposit:
l1 chain:
tx hash: 0xd5165d576a728bc5f9a9d4d93c28d975136f83e19ed1b67351680255b1d7eb5d
l2 chain:
LINK contract address: 0x535E8a3E95ADe8d2199562192EFbb060071A55d7
tx hash: 0xd8affc45f31a7dc7c1b5cfc1d54e1b5fbfbd9951bf7d4263f97eb7b855154359
block number: 13174
ERC20 LINK(1 link) withdraw:
l2 chain:
approve:
block number: 13201
tx hash: 0x3a84bc0ffe4ff1b9ec735a52a03801cdc11c7bc8cc1e85ca2a72882de16f7de9
withdraw:
block number: 13205
tx hash: 0xa7a7cf9b07eb2a3dcf337e247cbda4530201f9dc60021ebbcb1be3ec8dee5a38

The deposit traces are not right, correct situation is l1DataFee = 0(deposit tx(type = 126)) and other tx(type = 0) is l1Datafee != 0.
The PR fix it.


camel application property routesUri is not overridden at runtime

Fixes #54

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/234/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/235/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/236/Build result: FAILURE[...truncated 960.60 KB...]    at java.lang.reflect.Method.invoke (Method.java:498)    at hudson.maven.Maven3Builder.call (Maven3Builder.java:139)    at hudson.maven.Maven3Builder.call (Maven3Builder.java:70)    at hudson.remoting.UserRequest.perform (UserRequest.java:212)    at hudson.remoting.UserRequest.perform (UserRequest.java:54)    at hudson.remoting.Request$2.run (Request.java:369)    at hudson.remoting.InterceptingExecutorService$1.call (InterceptingExecutorService.java:72)    at java.util.concurrent.FutureTask.run (FutureTask.java:266)    at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1149)    at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:624)    at java.lang.Thread.run (Thread.java:748)[ERROR] [ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException[ERROR] [ERROR] After correcting the problems, you can resume the build with the command[ERROR]   mvn  -rf :camel-quarkus-integration-test-corechannel stoppedAdding one-line test results to commit status...Setting status of dfee51c97ff684ea962d634c6a1ae7ad1df0c355 to FAILURE with url https://builds.apache.org/job/camel-quarkus-pr/236/ and message: 'FAILURE 54 tests run, 2 skipped, 0 failed.'Using context: default

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/camel-quarkus-pr/238/


Library name change request

Library repository URL
https://github.com/jhagas/ESP32-Supabase

Hi @jhagas. I am confirming your request.
Unlike submissions, this type of request is still handled manually. The Library Manager index maintainer occasionally comes through to clear all the outstanding requests. They will close this issue when it is done. You will get a notification from GitHub at that time.
After that, you can monitor the indexing of the library via its dedicated logs web page.
Information about that here:
https://github.com/arduino/library-registry/blob/main/FAQ.md#can-i-check-on-library-releases-being-added-to-library-manager

Done:
2023/04/19 15:45:06 Loaded 5753 libraries from DB
Removing Supabase ESP32 Library
Success!


SW-5318 Add deleteMany functionality to ParticipantProjectSpeciesStore and controller

SW-5318 Add deleteMany functionality to ParticipantProjectSpeciesStore and controller
Formatting

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

#1935  👈
#1934
#1933
#1932
#1924
#1919
#1918
#1917
#1916
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nickgraz and the rest of your teammates on  Graphite

Merge activity

May 8, 12:09 PM EDT: @nickgraz started a stack merge that includes this pull request via Graphite.


added support for the user and service authentication

Hello Team,
As per the documentation of the openai, we have 3 types of authentication supported for the user and service level auth. as per the documentation, we know that we need to pass the api_key in the header as a Bearer token. i have adde the condition for that.
FYI : For the POST request when you are passing the parameter which is coming to a call_api function i have found that it was not being passed while tested to i have changed those.
I have added the oauth support in my local. it need to be reviewed first let me know once any of you are available. i am happy to discuss.

As I understood the new parameters. url and user_id were not being used, so I just removed them for now. The new functionality fit very well in the already existing functions, which is fantastic. And the examples are great! Thx


Updating to latest hyper/tokio versions

Hello @rousan, I am planning to use this plugin for a production Hyper-based websocket application. Would you be interested in help updating the plugin to use the latest hyper (0.14) and tokio (1.x) versions, and ensuring the best compatibility with routerify 2.1 ? I could help with a PR if you're interested.

Hey @ErwanDL , Thanks for the issue, If you send a PR, that would be a very valuable help. Thanks.

Sounds good, I will start working on it this week. I also have a somewhat unrelated question : is there a way to access State from a websocket handler (like we would with a regular handler by doing req.data::<State>()) ? And similarly, is there a way to access additional metadata (additional headers, authentication token, query params...) that the client may have passed in the handshake request ?
I haven't found a way to do that yet, but if the handler function provided to upgrade_ws could accept a second argument of type Request, both of these could be solved. Do you think this would be technically doable ? If so, can you point me to what changes would be required, and I could also try to help with that ?

this project seems to be dead for long time. I started maintaining an up-to-date version of this library
here

@NikosEfthias I think the Routerify maintainers told me in some other issue to use hyper-websocket instead, and I must say it integrates pretty smootly with hyper and routerify, I've been using it on a project at work for a few months now.

@NikosEfthias @ErwanDL , I just released a latest version with latest versions of hyper/tokio/routerfy: v3.0.0


Implement Repeat Module

Implementation of a new "repeat" module for the Melissa Action Repository.
WORDS for module: repeat, say
Demo:
User: repeat you are awesome
Melissa: you are awesome

The repeat or say word will have to removed and the remaining string will have to be passed on to the tts() function.
Sample format for an action module
Sample module for removing phrase from user speech
Documentation of the WORDS constant

I would like to take up this issue. Can you please guide me further.

Sure, the workflow would be something like this:

Take the user speech.
Remove the keyword.
Pass that to TTS.

I would suggest you go through the codebase and/or study the resources that I have provided above @amanmehta-maniac

Yes, I am already on it. When just trying to make a dummy git push, I was getting permission denied.
Precisely, this : remote: Permission to Melissa-AI/Melissa-Core.git denied to amanmehta-maniac.
fatal: unable to access 'https://github.com/Melissa-AI/Melissa-Core.git/': The requested URL returned error: 403
Am I missing something?

Clone this repo, git clone that, add this as a remote, push to your repo and then open a PR.

Fixed here: https://github.com/Melissa-AI/Melissa-Core/pull/64.


misc: remove executable for MacOS found in the repo

Remove some executables found in this repo, e.g.
$ file app1
app1: Mach-O 64-bit arm64 executable, flags:<|DYLDLINK|PIE>

@jonbodner Please take a look

Thanks!


Refactor: api calls for resources should be fetched when needed

Here's what happens at the moment:

On load/ first render

first page of visited resources are fetched and all resources are fetched concurrently.

clicking "Load 20 more resources" button

another api call for a page of requested resources is fetched.

Heres what should happen instead:

On load/ first render for each of  all, topics, and projects:

first page should be fetched
all resources matching that page(either all, topics, or projects) should also be fetched(to make it easier to search all not just first page)
NOTE: use promise.all syntax(unless you have a reason not to)

clicking the "Load 20 more resources" button should be removed

Can I help to fix the issue?

Yes you can, that would be appreciated. I'll assign it to you now now. Please do let me know if you need me to clarify anything.


Fixed the old broken XSD in the generator

The old XSD link isn't working so I fixed it for you

Thanks!

Welcome!


adding Client sample for retrieving BOM component vulnerability info

Overall looks nice @gsnyder2007, can you make a couple of quick edits and then go ahead an merge it in.


enable gzip compression

I think this project is great!
I was wondering if you were thinking of adding gzip support? (something that I currently do in Nginx but it would be great if it'd work with this project - much smaller docker file size)

afaik thttpd doens't gzip and I doubt they'll add this feature any time soon.

@johnb8005 I just released a new version (2.0.0 or latest) of the image using BusyBox httpd, which comes with gzip support (check the FAQ in the project README). You have to provide the gzipped files yourself but it's better than nothing. On top of that, the image is smaller (154KB) and comes with a significantly lower memory footprint than my 1.0.0 version.


Added tooltips to criteria type and visibility icons

Motivation and Context

In the table showing all of the criteria settings for an assignment in the web UI, there are some icons used to indicate the type of criterion and the visibility. These icons could be made clearer by adding tooltips to them, which would appear when you hover over them. This pull request implements this feature.
Your Changes

Description: In _criterion.html.erb, added adding the title attribute to the icons that require a tooltip.
Type of change (select all that apply):

[X] New feature (non-breaking change which adds functionality)

Testing

Manually tested changes through the web interface.

Questions and Comments (if applicable)

For the visibility icons, I was debating whether to set the value for title as criteria.help_peer_visibility_message and criteria.help_ta_visibility_message or a shorter and more concise message, such as "Graders and Instructors". I chose the latter because the criteria description box to the right of the table showing all the criteria settings already specifies what the visibility icons are, so I thought it'd be redundant to put the same text in the tooltip. However, please let me know if this should be modified.
Checklist

[X] I have performed a self-review of my own code.
[x] I have verified that the pre-commit.ci checks have passed.
[x] I have verified that the CI tests have passed.
[ ] I have reviewed the test coverage changes reported on Coveralls.
[x] I have updated the Changelog.md file.

Pull request to make documentation changes (if applicable)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 91.8%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
38148

Relevant Lines:
40991

💛  - Coveralls


background log content

Now has:
PomBase::Check::_do_query_checks(): DBI Exception: DBD::Pg::st execute failed: ERROR:  function starts_with(character varying, character varying) does not exist
LINE 23:   AND NOT starts_with(allele.name, gene.name)) as sub
^
HINT:  No function matches the given name and argument types. You might need to add explicit type casts. [for Statement "select count(*) from (SELECT array_to_string(array
(SELECT value
FROM featureprop p
WHERE p.feature_id = allele.feature_id
AND p.type_id in
(SELECT cvterm_id
FROM cvterm
WHERE name = 'canto_session')), ',') AS canto_session,
allele.name AS allele_name,
gene.name AS gene_name, gene.uniquename as gene_uniquename
FROM feature allele
JOIN feature_relationship rel ON rel.subject_id = allele.feature_id
JOIN cvterm rel_type ON rel.type_id = rel_type.cvterm_id
JOIN feature gene ON rel.object_id = gene.feature_id
JOIN cvterm allele_type ON allele_type.cvterm_id = allele.type_id
JOIN featureprop allele_type_prop ON allele_type_prop.feature_id = allele.feature_id
JOIN cvterm allele_type_prop_type ON allele_type_prop_type.cvterm_id = allele_type_prop.type_id
WHERE rel_type.name = 'instance_of'
AND allele_type.name = 'allele'
AND allele_type_prop_type.name = 'allele_type'
AND (allele_type_prop.value = 'amino_acid_mutation'
OR allele_type_prop.value = 'nucleotide_mutation')
AND NOT starts_with(allele.name, gene.name)) as sub"] at /local-homes/pbuild/git/pombase-chado/lib/PomBase/Check.pm line 186

I've fixed that for tonight's load.  The query to check that allele names start with a gene name was failing because I used SQL syntax not supported by the (quite old) version of Postgres on the server.  The illegal query was causing the whole Chado checking stage to fail.


changed label for MONDO:0019528

Fixes #4759

@nicolevasilevsky : it means that the 2 new ORDO terms could be children of this term.


ScanCode: Improve the comment about the ScanCode LicenseRef namespace

Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

This change is

Merging without waiting for Travis CI which seems to be stuck.


refactor: Transcript handled through shared_ptr

Please provide a paragraph or two giving a summary of the change, including relevant motivation and context.
Checklist:
Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge.

[ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag.
[ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to relevant issues (if any exist).

Benchmark results
Metrics with a significant change:

circuit_simulation_time_in_ms (private-kernel-init): 399 (-48%)
circuit_simulation_time_in_ms (base-rollup): 3,183 (+81%)
circuit_simulation_time_in_ms (root-rollup): 96.0 (-43%)
circuit_simulation_time_in_ms (public-kernel-private-input): 418 (-27%)
circuit_input_size_in_bytes (private-kernel-init): 43,077 (-30%)
circuit_input_size_in_bytes (private-kernel-inner): 64,484 (-21%)
circuit_input_size_in_bytes (public-kernel-private-input): 25,203 (-39%)
circuit_input_size_in_bytes (public-kernel-non-first-iteration): 25,245 (-39%)
circuit_output_size_in_bytes (private-kernel-ordering): 9,689 (+19%)
tx_size_in_bytes (0): 10,323 (+17%)
l2_block_building_time_in_ms (8): 25,271 (+23%)
l2_block_building_time_in_ms (32): 100,634 (+23%)
l2_block_building_time_in_ms (128): 402,587 (+23%)
l2_block_rollup_simulation_time_in_ms (8): 17,693 (+48%)
l2_block_rollup_simulation_time_in_ms (32): 70,538 (+49%)
l2_block_rollup_simulation_time_in_ms (128): 281,252 (+49%)
note_trial_decrypting_time_in_ms (8): 16.8 (+192%)
note_trial_decrypting_time_in_ms (32): 13.2 (-86%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 2001d474 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
128 txs

l1_rollup_calldata_size_in_bytes
45,444
179,588
716,132

l1_rollup_calldata_gas
222,888
868,268
3,449,564

l1_rollup_execution_gas
841,975
3,595,376
22,204,933

l2_block_processing_time_in_ms
1,969 (-3%)
7,680
30,108

note_successful_decrypting_time_in_ms
311 (+4%)
900 (+2%)
3,300 (+2%)

note_trial_decrypting_time_in_ms
:warning: 16.8 (+192%)
:warning: 13.2 (-86%)
142 (+1%)

l2_block_building_time_in_ms
:warning: 25,271 (+23%)
:warning: 100,634 (+23%)
:warning: 402,587 (+23%)

l2_block_rollup_simulation_time_in_ms
:warning: 17,693 (+48%)
:warning: 70,538 (+49%)
:warning: 281,252 (+49%)

l2_block_public_tx_process_time_in_ms
7,534 (-13%)
29,947 (-13%)
120,784 (-13%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
21,748 (-1%)
42,358

note_history_successful_decrypting_time_in_ms
2,091 (+2%)
4,082 (+2%)

note_history_trial_decrypting_time_in_ms
126
157 (+1%)

node_database_size_in_bytes
1,630,011
1,094,269 (-1%)

pxe_database_size_in_bytes
29,748
59,307

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
:warning: 399 (-48%)
:warning: 43,077 (-30%)
20,441 (+8%)

private-kernel-ordering
126 (-1%)
25,833 (+6%)
:warning: 9,689 (+19%)

base-rollup
:warning: 3,183 (+81%)
659,500
873

root-rollup
:warning: 96.0 (-43%)
4,072
1,097

private-kernel-inner
826 (+4%)
:warning: 64,484 (-21%)
20,441 (+8%)

public-kernel-private-input
:warning: 418 (-27%)
:warning: 25,203 (-39%)
20,441 (+8%)

public-kernel-non-first-iteration
412 (+1%)
:warning: 25,245 (-39%)
20,441 (+8%)

merge-rollup
11.0 (-29%)
2,592
873

Miscellaneous
Transaction sizes based on how many contracts are deployed in the tx.

Metric
0 deployed contracts
1 deployed contracts

tx_size_in_bytes
:warning: 10,323 (+17%)
29,083 (+6%)


Fixed the Navbar for better UX and change the css of logon and register according to the color pallet of Website i Dark mode

Description:

Enhanced the CSS styling of the Login and Registration pages to align with the website's color palette.
Adjusted fonts, buttons, and input fields to create a more cohesive design with the website’s theme.
Fixed issues with the header layout to improve user experience, ensuring better accessibility and responsiveness.
Improved header design by making it more intuitive and easy to navigate.

Related Issues:

Closes #123 (if there's a related issue to link)

Type of Changes:

[ ] Bugfix
[x] Feature
[ ] Documentation
[ ] Refactoring
[ ] Test

Checklist:

[x] I have read the contributing guidelines
[x] I have followed the coding style
[x] My code is tested (if applicable)
[x] My changes are properly documented (if applicable)
[x] I have included screenshots (if applicable)

Comments:

The design changes were made based on the website's color palette and user feedback.
The header fix should resolve previous alignment issues on mobile and desktop views.

After:

please check my all commits and merge it


Simplify Standard Input

Just a suggestion and my personal preference and may be shared with other Rusteceans, but could it be possible to simplify the Standard Input in std::old_io so it would be as 'simple' as like C/C++ ?

Past RFC.
If you want something like this in the stdlib, it might be a good idea to propose an API, And if you have a good API in mind, you should implement it out-of-tree so it can be reviewed and accepted. That was the consensus of the linked RFC.

Thats kinda what I was looking for, thanks!

also this library

Will not be available in 1.0

Not available as a library or in the std of Rust?

Both.

Why not???

It's a compiler plugin and compiler plugins won't be available in 1.0.

Thats ashame :(

Note that you can still use this in the nightly channel, post-1.0, and that solidifying compiler plugins is something that people really want, so hopefully will be focused on post-1.0

Any progress about this in the past 5 years?

AFAIK "what's wrong with a crate?" remains the consensus here.

Although having one in std is better, I can bear with a crate.
Is there any crate you would recommend, since scan is neither on crates.io nor maintained well?


⚗ test x86 implementation: looking for a solution to match x64 def

Ref: #1
Looking for a solution to match the design of the x64 implementation tail.

@wenceslas-sanchez don't try and match my version, I'm trying to improve it. If you come up with a more idiomatic implementation, I will match yours! See #5 .


Support for Active Directory integration

Is there inbuilt support for Active Directory integration in the bot framework ? If not then How to do the custom Active Directory integration in chatbot framework

You might consider https://github.com/MicrosoftDX/AuthBot.

Thanks for reply. I will look into same


chore(cxx): switch to using Abseil flags library over gflags

This does necessitate turning off gflags support the glog for the time being, due to conflicting exported macros between glog and absl. The extant flag-based functionality can also be achieved via environment variables, however.
In theory, there will be absl/logging at some point, but I don't know what the timeline on that is.

It looks like there are some build errors

It looks like there are some build errors

Oh the joy of undeclared dependencies.

I cannot reproduce the clang-format issue from arc lint locally.


Sync OTA from latest AFR 202007 release

Description

Copy the latest OTA code from AFR 202007.00 release.
Test Steps

Tested in aws/amazon-freertos repo
Related Issue

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks


Query about word-region alignment score

Hi,
Thanks for the exciting work. I have a mall query: Does this line produce the region-word alignment scores S_ground mentioned in the paper?
Line: https://github.com/microsoft/GLIP/blob/main/maskrcnn_benchmark/modeling/rpn/vldyhead.py#L843

我觉得应该是的，前者代表的是图像的特征，后者代表文本的特征。

Thank you for your interest in our work. Sorry for the delay in response!
Yes, this line produces the region-word alignment scores.


Allow connection using custom port number other than 3306

The issue is that on our project, we are using other MySQL port, instead of standard 3306, I did a little change on the code, to allow connections using custom port.

@griiettner 👋  It's been a while!
As for this PR, 👍 😻

I'm around my friend... I'm using your node module to kick start a Joomla website migration to node + React... It will be very challenging...
The backend will remain Joomla, but the front-end will be all React, but the requirements is to keep the flexibility of J! modules... so... let's see what we get from it... lol...
Take care...

@griiettner cool! I haven't really sat down with React yet, although I've worked with Angular a bit. Haven't touched J! in over three years. Glad this little module is getting some use :)


Wheeling and moveing content to left side boundary problem

Hello!~
I try setting your plugin scale positionX positionY like below code.
<TransformWrapper minScale={1} maxScale={5} scale={s} positionX={x} positionY={y}>
But problem like below gif.

Thank your help~

Could you post gif one more time? It is not working anymore :/

Fix is on it's way, today will release new version.


DLRM doesn't work with dense_in_features = 0.

I have a dataset where all features are categorical. In theory, DLRM should also work in this special case with output of Interaction layer having size B * (F choose 2), i.e. only sparse features interact with each other.
The code doesn't seem to support this special case. Do you have a plan for that?
Thank you for this awesome repo.

Hey @tiepvupsu, ah that might be an edge case we hadn't covered, let me see if we can support this

Asked around, and we probably want to keep it this way (since DLRM is something that combined dense + sparse features). We recommend just creating your own sparse layer that just processes the embeddings if you need.


epm:install doesn't work

Installed elvish just a day ago, and came across epm.
When I try to install a package, epm says its already installed but when I try to use the package it says the module doesn't exist. The directory for the modules also does not exist.
~> use epm
~> epm:install github.com/zzamboni/elvish-modules
=> Package github.com/zzamboni/elvish-modules is already installed.
~> use github.com/zzamboni/elvish-modules/alias
Exception: no such module: github.com/zzamboni/elvish-modules/alias
[tty 2], line 1: use github.com/zzamboni/elvish-modules/alias

When I try to install a non-existent package it still says the module is already installed
~> epm:install random-non-existent-package
=> Package random-non-existent-package is already installed.

Os - Garuda Linux Soaring
Elvish Version - v0.15.0

Can you paste the output of
echo $-lib-dir
test -e $-lib-dir/random-non-existent-package

~> echo $-lib-dir
compilation error: 5-14 in [tty]: variable $-lib-dir not found
compilation error: variable $-lib-dir not found
[tty 1], line 1: echo $-lib-dir
~> test -e $-lib-dir/random-non-existent-package
compilation error: 8-17 in [tty]: variable $-lib-dir not found
compilation error: variable $-lib-dir not found
[tty 2], line 1: test -e $-lib-dir/random-non-existent-package

Oops. Replace $-lib-dir with $epm:-lib-dir, what's the output?

~> echo $epm:-lib-dir
compilation error: 5-18 in [tty]: variable $epm:-lib-dir not found
compilation error: variable $epm:-lib-dir not found
[tty 3], line 1: echo $epm:-lib-dir

~> test -e $epm:-lib-dir/random-non-existent-package
compilation error: 8-21 in [tty]: variable $epm:-lib-dir not found
compilation error: variable $epm:-lib-dir not found
[tty 4], line 1: test -e $epm:-lib-dir/random-non-existent-package

I'm guessing this should've returned './elvish/lib'? So does this mean I need to explicitly set the value for lib-dir?

Hmm, do "use epm" first before running those commands?

Oh well, my bad.
~> echo $epm:-lib-dir
/home/sid/.elvish/lib

~> test -e $epm:-lib-dir/random-non-existent-package
0.0064

Hmm so the test command on your system seems to be off, it's certainly not the standard UNIX test command and that's the cause of the problem. Maybe you built a test program and put it somewhere in your PATH?
epm should be changed to use https://elv.sh/ref/path.html#pathis-dir though, and that'd also avoid such problems.

sorry about the test command, completely forgot about it. This is with the standard test command
~> test -e $epm:-lib-dir/random-non-existent-package
Exception: test exited with 1
[tty 26], line 1: test -e $epm:-lib-dir/random-non-existent-package

Did you remove your own test command from PATH? If so epm:install should work as expected from now on.

Ah yes. It works now, thank you.


Document that query params are allowed in grafana URL

Depends on https://github.com/kiali/kiali/pull/2687

DNM: to merge only when dependent is merged


Scroll Up Button

Hey @nisha331, I would like to open this issue under JWOC. I'll to add a scroll up button with smooth scrolling on the home page.

ok


Polling khstate from K8s API-server every 5sec for khcheck leading to client side throttling  and high latency

Currently kuberhealthy-operator creates a resource called khstate for every khcheck. It keeps on polling khstate for each khcheck from k8s API server every 5 sec Here. It leads to a lot of requests to K8s API server.
We are seeing a lot of ### Waited for Xs due to client-side throttling, not priority and fairness. message in kuberhealthy-operator pods .

Also We are seeing a lot of latency in request served by kuberhealthy server (P95 ~ 53 sec for 2xx, only 50% request are served under 1sec). These  metrics have been generated using standard metrics exposed by istio sidecar

Note: <50 checks are running in cluster. All above snapshots are for master pod
@integrii What's the motvation behind storing khstate as crd instead in inmemory (maybe as a concurrent hash map)?

This makes sense, and repeatedly polling the API server is not optimal.  It seems like Kuberhealthy needs a refactor to a reflector cache for khstate and khcheck resources.  Then, when a khstate is needed, Kuberhealthy will not even make a call to the API server.
The reason that khstate exists is to provide a persistent store of state that all Kuberhealthy pods can agree on.  This makes Kuberhealthy highly available without complex clustering algorithms.  By default Kuberhealthy comes with two pods in a deployment.  The pod that comes alphabetically first is always the master pod, but either Kuberhealthy pod can service requests for status because they both just return the data from the khstate resources.
Implementing a reflector would stop the API spam, improve the speed of Kuberhealthy, and prevent the issue you are seeing here.

I just did some work on this... I am refactoring this to use the existing cache for khstate resources...  Progress is in the khstate-cache branch.

I just did some work on this... I am refactoring this to use the existing cache for khstate resources... Progress is in the khstate-cache branch.

@integrii When can we expect a release for this? Also I would like to contribute to this change in case anything is pending

Trying to understand the code base. Could the StateReflector be passed into the external.Check either instead of or along with the khstatechlient? Looking at this line. That way the ext.podHasReportedInAfterTime  could use the reflector cache?

@integrii I did a quick and dirty pass of using the state reflector store to alleviate some API requests. It improved the throughput a little bit. Don't have the numbers handy.
https://github.com/kuberhealthy/kuberhealthy/compare/master...jplouis:kuberhealthy:master


The search on documentation page keeps saying initializing search. Never searches really.

The search on documentation page keeps saying initializing search. Never searches really. I have even tried clearing cache, cookies and changing network.

Duplicate of #1448. Could you try in another browser or private/incognito window?


Use fetch to send requests to create issues/comments

Follow #23290
Network error won't make content lost. And this is a much better approach than "loading-button".
The UI is not perfect and there are still some TODOs, they can be done in following PRs, not a must in this PR's scope.

You should check whether the content of issue/comment is empty

You should check whether the content of issue/comment is empty

There was no such check, so I think it's not in this PR's scope.


Revert "fix(menu): keyboard controls not respecting DOM order when it…

…ems are added at a later point (#11720)"
This reverts commit 49e8c593fc5401f1284957bd3f3bbf8a3ec5b12a.
Reverting this because it breaks interactions on menu items (like hover) when using MatMenuContent

@jelbourn did this not need to be merged or was it decided not to revert it?

@jelbourn still waiting for merge... Right now it seems like dynamic menus creation are no longer possible. Or is there another way?


No such file or directory: 'tmp/nn_models'

I tried to run a pipeline search (from tabular_classification.ipynb) and it failed with the error:
Process Process-1:
Traceback (most recent call last):
  File "/opt/conda/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap
    self.run()
  File "/opt/conda/lib/python3.9/multiprocessing/process.py", line 108, in run
    self._target(*self._args, **self._kwargs)
  File "/opt/conda/lib/python3.9/site-packages/alpha_automl/pipeline_synthesis/setup_search.py", line 112, in search_pipelines
    c.learn()
  File "/opt/conda/lib/python3.9/site-packages/alpha_automl/pipeline_search/Coach.py", line 101, in learn
    self.nnet.save_checkpoint(folder=self.args.get('checkpoint'), filename='temp.pth.tar')
  File "/opt/conda/lib/python3.9/site-packages/alpha_automl/pipeline_search/pipeline/NNet.py", line 145, in save_checkpoint
    os.mkdir(folder)
FileNotFoundError: [Errno 2] No such file or directory: 'tmp/nn_models'

To solve it, I had to create the folder tmp manually in the home directory of the JupyterLab installation. Does alpha-automl create this folder automatically?

In addition, the cell running the method fit() does not return when the error happens. It seems to stay blocked running indefinitely until the user interrupts the cell.

Thanks @aecio! Do you mean that it shows that error and gets 'frozen'?

Per discussion, tempfile should be used on this.

In the case that the parameter output_path is provided (as in the linked notebook), I think we should just automatically create the directory if it does not exist.

Yes, output_path will be an optional param (output_path=None), if provided we will use/create it, otherwise use tempfile.


Source code???

Hi! I saw this mod on Modrinth, and thought it looked really neat. But unfortunately I don't use 1.18.2 anymore.
So I did what any normal person would do and decompiled the mod, ported it to Architectury Loom, and updated it for 1.19.2. Now I can use it in my own private modpack :)
Unfortunately that sort of violates the mod's ARR license. I was hoping you'd consider relicensing the code with something more permissible, and maybe even publishing the source code?
(If you're interested in my fork, I can grant complete and total permission to take it and do what you will with it. Not like I had permission to make it in the first place. (rather ask for forgiveness than for permission... or something like that))

Ok so yes this mod will be open source, it's just that in a rush to post before I had to go I didn't push the code and set the license to ARR for now, but you saying "decompile" like a normal person is funny when actual open source projects don't even get pull requests from other users.
As I said in the description under the picture, I don't have that much time to put into this mod, I just made it for fun and experiments, it's also an attempt to get it to some QSMP members or QSMP modpack which itself runs on 1.18.2 as their waystone menu are so messed up.
I posted the mod literally 3 days ago and I didn't expect to have someone like you at 6 downloads lol.
Anyway, I made the addon directly for Forge only because I tried to make a mod with Architectury Loom not so long ago and had problems with it, I don't remember exactly what, but it made me make this mod with Forge gradle only, even the original mod supports both Fabric and Forge, and I've actually made more Fabric mods than Forge lately, so you might have seen some Fabric like named variables.
Also I'm still not finished with the stuff I want to implement so won't update until I'm done with it.
But like I said, since this mod will be open source and you successfully made it work with Architectury, you can contact me on discord so we can talk about it further. (you can find the link on my InGameStats or my ContainerSearcher mods at the bottom)

...but you saying "decompile" like a normal person is funny when actual open source projects don't even get pull requests from other users.

I have a tendency to do things sometimes. Bad habit :p

But like I said, since this mod will be open source and you successfully made it work with Architectury...

Note that I didn't get it working with Architectury API; just Architectury Loom (I'm still only building it for Forge).
Though it shouldn't be too difficult to accomplish the former - but Fabric has fwaystones, which already has a much better GUI, so I don't think it's all that necessary.

...you can contact me on discord so we can talk about it further.

I see you released a new version of this mod the other day, and having access to the source code would make it a lot easier to update my own fork, so yes - will do :)