Test DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP behavior

Motivation
APMAPI-289
Test tracer behavior when DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP is configured to the empty string and to a valid regex to ensure all tracers modify the http.url tag in the same fashion.
Changes

Adds 2 new test classes for testing the configuration with an empty string value and a valid regex value
Adds a new scenario for testing empty string configurations, to be used by other configurations under the same "Config Consistency" effort.
Enables this test for dd-trace-java and configures a Java spring-boot endpoint to support this test

Workflow

⚠ Create your PR as draft ⚠
Work on you PR until the CI passes (if something not related to your task is failing, you can ignore it)
Mark it as ready for review

Test logic is modified? -> Get a review from RFC owner. We're working on refining the codeowners file quickly.
Framework is modified, or non obvious usage of it -> get a review from R&P team

:rocket: Once your PR is reviewed, you can merge it!
🛟 #apm-shared-testing 🛟
Reviewer checklist

[ ] If PR title starts with [<language>], double-check that only <language> is impacted by the change
[ ] No system-tests internal is modified. Otherwise, I have the approval from R&P team
[ ] CI is green, or failing jobs are not related to this change (and you are 100% sure about this statement)
[ ] A docker base image is modified?

[ ] the relevant build-XXX-image label is present

[ ] A scenario is added (or removed)?

[ ] Get a review from R&P team

I've rebased to fix some CI issues


About dockerfile

We appreciate you go through Apollo documentations and search previous issues before creating an new one. If neither of the sources helped you with your issues, please report the issue using the following form. Please note missing info can delay the response time.
System information

OS Platform and Distribution (e.g., Linux Ubuntu 14.04):
Apollo installed from (source or binary):
Apollo version (1.0, 1.5, 2.0, 2.5, 3.0):

Steps to reproduce the issue:

Please use bullet points and include as much details as possible:

Supporting materials (screenshots, command lines, code/script snippets):
Hello！Where is the dockerfile？Thank you！

dockerfile
apollo\docker\build\dev.x86_64.dockerfile
build
docker

dockerfile
apollo\docker\build\dev.x86_64.dockerfile
build
Here is a doc about build docker here

very nice！Thank you！


Add news on top

It would be nice if the add news form on the admin dashboard was always on top
Instead of having to scroll past all the old news it would be better if the form to add news was always on top and the news items below it.
News items can be long and you might have to scroll a long way down to get to the form.

Additionally having a seperate page for news with pagination (instead of admin dashboard) and editing capability would be nice.

I am also in favor of just moving news to a separate page. Also:

Allow drafts to be saved in a "unpublished" state.
Allow edits to already published articles (this may prevent email spam when there's something left out accidentally, or a spelling mistake)


Positional changes around the Kubevirt logo in the README.md file Signed-off-by: Pritam Saha<EMAIL_ADDRESS>

What this PR does / why we need it:

Shifted the Logo of Kubevirt at the top in the Readme file.
And made the tag lines alignment in the centre.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
#Before

#After

Release note:

none

Thank you for the PR! Would you please update the PR title to be something more descriptive of what this PR is changing?

Thank you for the PR! Would you please update the PR title to be something more descriptive of what this PR is changing?

+1
In addition, if you don't mind:

Change the commit message as well
Fill out "What this PR does / why we need it:" section
under Release note:, Please write NONE

Thanks a lot for your contribution!

Thank you for the PR! Would you please update the PR title to be something more descriptive of what this PR is changing?

+1
In addition, if you don't mind:

Change the commit message as well
Fill out "What this PR does / why we need it:" section
under Release note:, Please write NONE

Thanks a lot for your contribution!

Yeah Sure!

I have one doubt, Should I remove the signed off tag line ?

Yeah Sure!

Thanks!

I have one doubt, Should I remove the signed off tag line ?

You should keep it only at the bottom of the commit message.
See this as an example.
tip: this can be added automatically with git commit --signoff

Yeah Sure!

Thanks!

I have one doubt, Should I remove the signed off tag line ?

You should keep it only at the bottom of the commit message. See this as an example.
tip: this can be added automatically with git commit --signoff

I edited the PR message details & Title. is it ok now ? Let me know if any changes required.

Yeah Sure!

Thanks!

I have one doubt, Should I remove the signed off tag line ?

You should keep it only at the bottom of the commit message. See this as an example.
tip: this can be added automatically with git commit --signoff

I edited the PR message details & Title. is it ok now ? Let me know if any changes required.

Thanks a lot! Appreciate it!
You can also remove Signed-off-by: Pritam Saha<EMAIL_ADDRESS>suffix from the title and replace the commit subject from it to Changes in the Readme.MD file if you don't mind.
/ok-to-test
/lgtm

Changed the PR title & Signed-off-by: Pritam Saha<EMAIL_ADDRESS>section removed. Can you please tell me how to change the commit subject ? I have never done this before.

Changed the PR title & Signed-off-by: Pritam Saha<EMAIL_ADDRESS>section removed. Can you please tell me how to change the commit subject ? I have never done this before.

But that's okay, you can leave it as it is for now and remember it for follow-up PRs :)
Thanks again for you contribution!

1 check to fail is it the reason that this PR is not merged yet?

1 check to fail is it the reason that this PR is not merged yet?

Thank you for the PR @Saha-7.
PRs need to have lgtm and approved tags in order for the automation to merge them.
This PR was not yet approved by one of the maintainers.
You can see who the maintainers are under "approvers" in this docuemnt.

Okay got it.

/approve


fix(vMemo): prevent unexpected render in v-for + v-memo

This PR fixes the unexpected render when v-memo is used in a keyed v-for list. In the past, we just used an array as the renderCache of a list whatever if it is keyed. This PR adds a map that uses nodes.key as key and node as the value to the cache. When updates, if a list is keyed, it will check the cache from the map, so that can prevent unexpected render.
close #10392

/ecosystem-ci run

@baiwusanyu-c could you help to re-run the ecosystem-ci?

Could you please resolve the conflicts?

Could you please resolve the conflicts?

Sure, glad to see this PR finally noticed by others😁

I also added corresponding test case

/ecosystem-ci run

language-tools failed seems not related to this PR

/ecosystem-ci run language-tools


Wallet balance is 0 in Windows build

On OS X the balance is 100 so transactions can be tested. On Windows 10 Home - the balance of a new wallet is 0. Expected it to be 100 just like on OS X.

This is not an issue, the initial state for new account is balance 0. Previously we had 100 SMC but this was fictional and no real balance was issued when creating new account


 I have searched related issues but cannot get the expected help.
[X] 2. The bug has not been fixed in the latest version.
[X] 3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
[X] 4. If the issue you raised is not a bug but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.

Describe the bug
I frequently encounter Watch Dog TimeOut errors when deploying Mistral-123B using 8x A800 80G, which causes the service to stop. This issue occurs whether I send a single request or multiple requests. Below are my startup command and logs.
Command：
python -m sglang.launch_server --model-path /Mistral-Large-Instruct-2/ --host <IP_ADDRESS> --port 9997 --disable-cuda-graph --schedule-conservativeness 0.3 --tp 8 --mem-fraction-static 0.75 --schedule-policy fcfs
Error Log:
[rank5]:[E814 17:27:59.408557873 ProcessGroupNCCL.cpp:607] [Rank 5] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=4476, OpType=_ALLGATHER_BASE, NumelIn=4096, NumelOut=32768, Timeout(ms)
=600000) ran for 600012 milliseconds before timing out.
[rank5]:[E814 17:27:59.414680437 ProcessGroupNCCL.cpp:1664] [PG 3 Rank 5] Exception (either an error or timeout) detected by watchdog at work: 4476, last enqueued NCCL work: 4476, last completed NCCL w
ork: 4475.
[rank5]:[E814 17:27:59.414692410 ProcessGroupNCCL.cpp:1709] [PG 3 Rank 5] Timeout at NCCL work: 4476, last enqueued NCCL work: 4476, last completed NCCL work: 4475.
[rank5]:[E814 17:27:59.414701836 ProcessGroupNCCL.cpp:621] [Rank 5] Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels, subsequent GPU operations might run on
corrupted/incomplete data.
[rank5]:[E814 17:27:59.414708719 ProcessGroupNCCL.cpp:627] [Rank 5] To avoid data inconsistency, we are taking the entire process down.
[rank5]:[E814 17:27:59.417033598 ProcessGroupNCCL.cpp:1515] [PG 3 Rank 5] Process group watchdog thread terminated with exception: [Rank 5] Watchdog caught collective operation timeout: WorkNCCL(SeqNum
=4476, OpType=_ALLGATHER_BASE, NumelIn=4096, NumelOut=32768, Timeout(ms)=600000) ran for 600012 milliseconds before timing out.
Exception raised from checkTimeout at ../torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp:609 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x96 (0x7f1ad52fcf86 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libc10.so)
frame #1: c10d::ProcessGroupNCCL::WorkNCCL::checkTimeout(std::optional<std::chrono::duration<long, std::ratio<1l, 1000l> > >) + 0x1d2 (0x7f1ad654d8d2 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.
12/site-packages/torch/lib/libtorch_cuda.so)
frame #2: c10d::ProcessGroupNCCL::watchdogHandler() + 0x233 (0x7f1ad6554313 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libtorch_cuda.so)
frame #3: c10d::ProcessGroupNCCL::ncclCommWatchdog() + 0x10c (0x7f1ad65566fc in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libtorch_cuda.so)
frame #4:  + 0xdbbf4 (0x7f1b325ccbf4 in /mnt/new_afs/miniconda3/envs/SGLang/bin/../lib/libstdc++.so.6)
frame #5:  + 0x8609 (0x7f1bdd334609 in /usr/lib/x86_64-linux-gnu/libpthread.so.0)
frame #6: clone + 0x43 (0x7f1bdd0ff133 in /usr/lib/x86_64-linux-gnu/libc.so.6)
Reproduction
python -m sglang.launch_server --model-path /Mistral-Large-Instruct-2/ --host <IP_ADDRESS> --port 9997 --disable-cuda-graph --schedule-conservativeness 0.3 --tp 8 --mem-fraction-static 0.75 --schedule-policy fcfs
Environment
aiohappyeyeballs                  2.3.5
aiohttp                           3.10.3
aiosignal                         1.3.1
annotated-types                   0.7.0
anthropic                         0.33.1
anyio                             4.4.0
attrs                             24.2.0
certifi                           2024.7.4
charset-normalizer                3.3.2
click                             8.1.7
cloudpickle                       3.0.0
cmake                             3.30.2
datasets                          2.20.0
dill                              0.3.8
diskcache                         5.6.3
distro                            1.9.0
fastapi                           0.112.0
filelock                          3.15.4
flashinfer                        0.1.4+cu121torch2.4
frozenlist                        1.4.1
fsspec                            2024.5.0
h11                               0.14.0
hf_transfer                       0.1.8
httpcore                          1.0.5
httptools                         0.6.1
httpx                             0.27.0
huggingface-hub                   0.24.5
idna                              3.7
importlib_metadata                8.2.0
interegular                       0.3.3
Jinja2                            3.1.4
jiter                             0.5.0
jsonschema                        4.23.0
jsonschema-specifications         2023.12.1
lark                              1.1.9
litellm                           1.43.7
llvmlite                          0.43.0
lm-format-enforcer                0.10.3
MarkupSafe                        2.1.5
mpmath                            1.3.0
msgpack                           1.0.8
multidict                         6.0.5
multiprocess                      0.70.16
nest-asyncio                      1.6.0
networkx                          3.3
ninja                             <IP_ADDRESS>
numba                             0.60.0
numpy                             1.26.4
nvidia-cublas-cu12                <IP_ADDRESS>
nvidia-cuda-cupti-cu12            12.1.105
nvidia-cuda-nvrtc-cu12            12.1.105
nvidia-cuda-runtime-cu12          12.1.105
nvidia-cudnn-cu12                 <IP_ADDRESS>
nvidia-cufft-cu12                 <IP_ADDRESS>
nvidia-curand-cu12                <IP_ADDRESS>
nvidia-cusolver-cu12              <IP_ADDRESS>
nvidia-cusparse-cu12              <IP_ADDRESS>
nvidia-ml-py                      12.555.43
nvidia-nccl-cu12                  2.20.5
nvidia-nvjitlink-cu12             12.6.20
nvidia-nvtx-cu12                  12.1.105
openai                            1.40.6
outlines                          0.0.46
packaging                         24.1
pandas                            2.2.2
pillow                            10.4.0
pip                               24.2
prometheus_client                 0.20.0
prometheus-fastapi-instrumentator 7.0.0
protobuf                          5.27.3
psutil                            6.0.0
py-cpuinfo                        9.0.0
pyairports                        2.1.1
pyarrow                           17.0.0
pyarrow-hotfix                    0.6
pycountry                         24.6.1
pydantic                          2.8.2
pydantic_core                     2.20.1
python-dateutil                   2.9.0.post0
python-dotenv                     1.0.1
python-multipart                  0.0.9
pytz                              2024.1
PyYAML                            6.0.2
pyzmq                             26.1.0
ray                               2.34.0
referencing                       0.35.1
regex                             2024.7.24
requests                          2.32.3
rpds-py                           0.20.0
safetensors                       0.4.4
sentencepiece                     0.2.0
setuptools                        72.1.0
sglang                            0.2.12
six                               1.16.0
sniffio                           1.3.1
starlette                         0.37.2
sympy                             1.13.2
tiktoken                          0.7.0
tokenizers                        0.19.1
torch                             2.4.0
torchvision                       0.19.0
tqdm                              4.66.5
transformers                      4.44.0
triton                            3.0.0
typing_extensions                 4.12.2
tzdata                            2024.1
urllib3                           2.2.2
uvicorn                           0.30.5
uvloop                            0.19.0
vllm                              0.5.4
vllm-flash-attn                   2.6.1
watchfiles                        0.23.0
websockets                        12.0
wheel                             0.43.0
xformers                          0.0.27.post2
xxhash                            3.4.1
yarl                              1.9.4
zipp                              3.20.0
zmq                               0.0.0

It functions properly on the A100 TP 8.  I have searched related issues but cannot get the expected help.
[x]  2. The bug has not been fixed in the latest version.
[x]  3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
[x]  4. If the issue you raised is not a bug but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.

Describe the bug
I frequently encounter Watch Dog TimeOut errors when deploying Mistral-123B using 8x A800 80G, which causes the service to stop. This issue occurs whether I send a single request or multiple requests. Below are my startup command and logs.
Command： python -m sglang.launch_server --model-path /Mistral-Large-Instruct-2/ --host <IP_ADDRESS> --port 9997 --disable-cuda-graph --schedule-conservativeness 0.3 --tp 8 --mem-fraction-static 0.75 --schedule-policy fcfs
Error Log: [rank5]:[E814 17:27:59.408557873 ProcessGroupNCCL.cpp:607] [Rank 5] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=4476, OpType=_ALLGATHER_BASE, NumelIn=4096, NumelOut=32768, Timeout(ms) =600000) ran for 600012 milliseconds before timing out. [rank5]:[E814 17:27:59.414680437 ProcessGroupNCCL.cpp:1664] [PG 3 Rank 5] Exception (either an error or timeout) detected by watchdog at work: 4476, last enqueued NCCL work: 4476, last completed NCCL w ork: 4475. [rank5]:[E814 17:27:59.414692410 ProcessGroupNCCL.cpp:1709] [PG 3 Rank 5] Timeout at NCCL work: 4476, last enqueued NCCL work: 4476, last completed NCCL work: 4475. [rank5]:[E814 17:27:59.414701836 ProcessGroupNCCL.cpp:621] [Rank 5] Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data. [rank5]:[E814 17:27:59.414708719 ProcessGroupNCCL.cpp:627] [Rank 5] To avoid data inconsistency, we are taking the entire process down. [rank5]:[E814 17:27:59.417033598 ProcessGroupNCCL.cpp:1515] [PG 3 Rank 5] Process group watchdog thread terminated with exception: [Rank 5] Watchdog caught collective operation timeout: WorkNCCL(SeqNum =4476, OpType=_ALLGATHER_BASE, NumelIn=4096, NumelOut=32768, Timeout(ms)=600000) ran for 600012 milliseconds before timing out. Exception raised from checkTimeout at ../torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp:609 (most recent call first): frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x96 (0x7f1ad52fcf86 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libc10.so) frame #1: c10d::ProcessGroupNCCL::WorkNCCL::checkTimeout(std::optional<std::chrono::duration<long, std::ratio<1l, 1000l> > >) + 0x1d2 (0x7f1ad654d8d2 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3. 12/site-packages/torch/lib/libtorch_cuda.so) frame #2: c10d::ProcessGroupNCCL::watchdogHandler() + 0x233 (0x7f1ad6554313 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libtorch_cuda.so) frame #3: c10d::ProcessGroupNCCL::ncclCommWatchdog() + 0x10c (0x7f1ad65566fc in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libtorch_cuda.so) frame #4: + 0xdbbf4 (0x7f1b325ccbf4 in /mnt/new_afs/miniconda3/envs/SGLang/bin/../lib/libstdc++.so.6) frame #5: + 0x8609 (0x7f1bdd334609 in /usr/lib/x86_64-linux-gnu/libpthread.so.0) frame #6: clone + 0x43 (0x7f1bdd0ff133 in /usr/lib/x86_64-linux-gnu/libc.so.6)
Reproduction
python -m sglang.launch_server --model-path /Mistral-Large-Instruct-2/ --host <IP_ADDRESS> --port 9997 --disable-cuda-graph --schedule-conservativeness 0.3 --tp 8 --mem-fraction-static 0.75 --schedule-policy fcfs
Environment
aiohappyeyeballs 2.3.5 aiohttp 3.10.3 aiosignal 1.3.1 annotated-types 0.7.0 anthropic 0.33.1 anyio 4.4.0 attrs 24.2.0 certifi 2024.7.4 charset-normalizer 3.3.2 click 8.1.7 cloudpickle 3.0.0 cmake 3.30.2 datasets 2.20.0 dill 0.3.8 diskcache 5.6.3 distro 1.9.0 fastapi 0.112.0 filelock 3.15.4 flashinfer 0.1.4+cu121torch2.4 frozenlist 1.4.1 fsspec 2024.5.0 h11 0.14.0 hf_transfer 0.1.8 httpcore 1.0.5 httptools 0.6.1 httpx 0.27.0 huggingface-hub 0.24.5 idna 3.7 importlib_metadata 8.2.0 interegular 0.3.3 Jinja2 3.1.4 jiter 0.5.0 jsonschema 4.23.0 jsonschema-specifications 2023.12.1 lark 1.1.9 litellm 1.43.7 llvmlite 0.43.0 lm-format-enforcer 0.10.3 MarkupSafe 2.1.5 mpmath 1.3.0 msgpack 1.0.8 multidict 6.0.5 multiprocess 0.70.16 nest-asyncio 1.6.0 networkx 3.3 ninja <IP_ADDRESS> numba 0.60.0 numpy 1.26.4 nvidia-cublas-cu12 <IP_ADDRESS> nvidia-cuda-cupti-cu12 12.1.105 nvidia-cuda-nvrtc-cu12 12.1.105 nvidia-cuda-runtime-cu12 12.1.105 nvidia-cudnn-cu12 <IP_ADDRESS> nvidia-cufft-cu12 <IP_ADDRESS> nvidia-curand-cu12 <IP_ADDRESS> nvidia-cusolver-cu12 <IP_ADDRESS> nvidia-cusparse-cu12 <IP_ADDRESS> nvidia-ml-py 12.555.43 nvidia-nccl-cu12 2.20.5 nvidia-nvjitlink-cu12 12.6.20 nvidia-nvtx-cu12 12.1.105 openai 1.40.6 outlines 0.0.46 packaging 24.1 pandas 2.2.2 pillow 10.4.0 pip 24.2 prometheus_client 0.20.0 prometheus-fastapi-instrumentator 7.0.0 protobuf 5.27.3 psutil 6.0.0 py-cpuinfo 9.0.0 pyairports 2.1.1 pyarrow 17.0.0 pyarrow-hotfix 0.6 pycountry 24.6.1 pydantic 2.8.2 pydantic_core 2.20.1 python-dateutil 2.9.0.post0 python-dotenv 1.0.1 python-multipart 0.0.9 pytz 2024.1 PyYAML 6.0.2 pyzmq 26.1.0 ray 2.34.0 referencing 0.35.1 regex 2024.7.24 requests 2.32.3 rpds-py 0.20.0 safetensors 0.4.4 sentencepiece 0.2.0 setuptools 72.1.0 sglang 0.2.12 six 1.16.0 sniffio 1.3.1 starlette 0.37.2 sympy 1.13.2 tiktoken 0.7.0 tokenizers 0.19.1 torch 2.4.0 torchvision 0.19.0 tqdm 4.66.5 transformers 4.44.0 triton 3.0.0 typing_extensions 4.12.2 tzdata 2024.1 urllib3 2.2.2 uvicorn 0.30.5 uvloop 0.19.0 vllm 0.5.4 vllm-flash-attn 2.6.1 watchfiles 0.23.0 websockets 12.0 wheel 0.43.0 xformers 0.0.27.post2 xxhash 3.4.1 yarl 1.9.4 zipp 3.20.0 zmq 0.0.0

Has the problem been solved? I have encountered the same problem as you, but it only appears on some machines. I don't find anything special about these machines at present. @

Checklist

[x]   1. I have searched related issues but cannot get the expected help.
[x]   2. The bug has not been fixed in the latest version.
[x]   3. Please note that if the bug-related issue you submitted lacks corresponding environment info and a minimal reproducible demo, it will be challenging for us to reproduce and resolve the issue, reducing the likelihood of receiving feedback.
[x]   4. If the issue you raised is not a bug but a question, please raise a discussion at https://github.com/sgl-project/sglang/discussions/new/choose Otherwise, it will be closed.

Describe the bug
I frequently encounter Watch Dog TimeOut errors when deploying Mistral-123B using 8x A800 80G, which causes the service to stop. This issue occurs whether I send a single request or multiple requests. Below are my startup command and logs.
Command： python -m sglang.launch_server --model-path /Mistral-Large-Instruct-2/ --host <IP_ADDRESS> --port 9997 --disable-cuda-graph --schedule-conservativeness 0.3 --tp 8 --mem-fraction-static 0.75 --schedule-policy fcfs
Error Log: [rank5]:[E814 17:27:59.408557873 ProcessGroupNCCL.cpp:607] [Rank 5] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=4476, OpType=_ALLGATHER_BASE, NumelIn=4096, NumelOut=32768, Timeout(ms) =600000) ran for 600012 milliseconds before timing out. [rank5]:[E814 17:27:59.414680437 ProcessGroupNCCL.cpp:1664] [PG 3 Rank 5] Exception (either an error or timeout) detected by watchdog at work: 4476, last enqueued NCCL work: 4476, last completed NCCL w ork: 4475. [rank5]:[E814 17:27:59.414692410 ProcessGroupNCCL.cpp:1709] [PG 3 Rank 5] Timeout at NCCL work: 4476, last enqueued NCCL work: 4476, last completed NCCL work: 4475. [rank5]:[E814 17:27:59.414701836 ProcessGroupNCCL.cpp:621] [Rank 5] Some NCCL operations have failed or timed out. Due to the asynchronous nature of CUDA kernels, subsequent GPU operations might run on corrupted/incomplete data. [rank5]:[E814 17:27:59.414708719 ProcessGroupNCCL.cpp:627] [Rank 5] To avoid data inconsistency, we are taking the entire process down. [rank5]:[E814 17:27:59.417033598 ProcessGroupNCCL.cpp:1515] [PG 3 Rank 5] Process group watchdog thread terminated with exception: [Rank 5] Watchdog caught collective operation timeout: WorkNCCL(SeqNum =4476, OpType=_ALLGATHER_BASE, NumelIn=4096, NumelOut=32768, Timeout(ms)=600000) ran for 600012 milliseconds before timing out. Exception raised from checkTimeout at ../torch/csrc/distributed/c10d/ProcessGroupNCCL.cpp:609 (most recent call first): frame #0: c10::Error::Error(c10::SourceLocation, std::string) + 0x96 (0x7f1ad52fcf86 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libc10.so) frame #1: c10d::ProcessGroupNCCL::WorkNCCL::checkTimeout(std::optional<std::chrono::duration<long, std::ratio<1l, 1000l> > >) + 0x1d2 (0x7f1ad654d8d2 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3. 12/site-packages/torch/lib/libtorch_cuda.so) frame #2: c10d::ProcessGroupNCCL::watchdogHandler() + 0x233 (0x7f1ad6554313 in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libtorch_cuda.so) frame #3: c10d::ProcessGroupNCCL::ncclCommWatchdog() + 0x10c (0x7f1ad65566fc in /mnt/new_afs/miniconda3/envs/SGLang/lib/python3.12/site-packages/torch/lib/libtorch_cuda.so) frame #4: + 0xdbbf4 (0x7f1b325ccbf4 in /mnt/new_afs/miniconda3/envs/SGLang/bin/../lib/libstdc++.so.6) frame #5: + 0x8609 (0x7f1bdd334609 in /usr/lib/x86_64-linux-gnu/libpthread.so.0) frame #6: clone + 0x43 (0x7f1bdd0ff133 in /usr/lib/x86_64-linux-gnu/libc.so.6)
Reproduction
python -m sglang.launch_server --model-path /Mistral-Large-Instruct-2/ --host <IP_ADDRESS> --port 9997 --disable-cuda-graph --schedule-conservativeness 0.3 --tp 8 --mem-fraction-static 0.75 --schedule-policy fcfs
Environment
aiohappyeyeballs 2.3.5 aiohttp 3.10.3 aiosignal 1.3.1 annotated-types 0.7.0 anthropic 0.33.1 anyio 4.4.0 attrs 24.2.0 certifi 2024.7.4 charset-normalizer 3.3.2 click 8.1.7 cloudpickle 3.0.0 cmake 3.30.2 datasets 2.20.0 dill 0.3.8 diskcache 5.6.3 distro 1.9.0 fastapi 0.112.0 filelock 3.15.4 flashinfer 0.1.4+cu121torch2.4 frozenlist 1.4.1 fsspec 2024.5.0 h11 0.14.0 hf_transfer 0.1.8 httpcore 1.0.5 httptools 0.6.1 httpx 0.27.0 huggingface-hub 0.24.5 idna 3.7 importlib_metadata 8.2.0 interegular 0.3.3 Jinja2 3.1.4 jiter 0.5.0 jsonschema 4.23.0 jsonschema-specifications 2023.12.1 lark 1.1.9 litellm 1.43.7 llvmlite 0.43.0 lm-format-enforcer 0.10.3 MarkupSafe 2.1.5 mpmath 1.3.0 msgpack 1.0.8 multidict 6.0.5 multiprocess 0.70.16 nest-asyncio 1.6.0 networkx 3.3 ninja <IP_ADDRESS> numba 0.60.0 numpy 1.26.4 nvidia-cublas-cu12 <IP_ADDRESS> nvidia-cuda-cupti-cu12 12.1.105 nvidia-cuda-nvrtc-cu12 12.1.105 nvidia-cuda-runtime-cu12 12.1.105 nvidia-cudnn-cu12 <IP_ADDRESS> nvidia-cufft-cu12 <IP_ADDRESS> nvidia-curand-cu12 <IP_ADDRESS> nvidia-cusolver-cu12 <IP_ADDRESS> nvidia-cusparse-cu12 <IP_ADDRESS> nvidia-ml-py 12.555.43 nvidia-nccl-cu12 2.20.5 nvidia-nvjitlink-cu12 12.6.20 nvidia-nvtx-cu12 12.1.105 openai 1.40.6 outlines 0.0.46 packaging 24.1 pandas 2.2.2 pillow 10.4.0 pip 24.2 prometheus_client 0.20.0 prometheus-fastapi-instrumentator 7.0.0 protobuf 5.27.3 psutil 6.0.0 py-cpuinfo 9.0.0 pyairports 2.1.1 pyarrow 17.0.0 pyarrow-hotfix 0.6 pycountry 24.6.1 pydantic 2.8.2 pydantic_core 2.20.1 python-dateutil 2.9.0.post0 python-dotenv 1.0.1 python-multipart 0.0.9 pytz 2024.1 PyYAML 6.0.2 pyzmq 26.1.0 ray 2.34.0 referencing 0.35.1 regex 2024.7.24 requests 2.32.3 rpds-py 0.20.0 safetensors 0.4.4 sentencepiece 0.2.0 setuptools 72.1.0 sglang 0.2.12 six 1.16.0 sniffio 1.3.1 starlette 0.37.2 sympy 1.13.2 tiktoken 0.7.0 tokenizers 0.19.1 torch 2.4.0 torchvision 0.19.0 tqdm 4.66.5 transformers 4.44.0 triton 3.0.0 typing_extensions 4.12.2 tzdata 2024.1 urllib3 2.2.2 uvicorn 0.30.5 uvloop 0.19.0 vllm 0.5.4 vllm-flash-attn 2.6.1 watchfiles 0.23.0 websockets 12.0 wheel 0.43.0 xformers 0.0.27.post2 xxhash 3.4.1 yarl 1.9.4 zipp 3.20.0 zmq 0.0.0

Has the problem been solved? I have encountered the same problem as you, but it only appears on some machines. I don't find anything special about these machines at present. @Rookie-Kai

I updated SGLang and enabled --disable-custom-all-reduce, which seems to have resolved the previous issue. However, I’m now encountering a new problem. After making frequent, long-duration service calls, SGLang throws the following error:
[PG 3 Rank 7] Process group watchdog thread terminated with exception: CUDA error: an illegal memory access was encountered. CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
For debugging, consider passing CUDA_LAUNCH_BLOCKING=1. Compile with TORCH_USE_CUDA_DSA` to enable device-side assertions.
I suspect that this could be due to insufficient GPU memory. However, I’m using 8xA800 GPUs to deploy Qwen2-72B, with only 4 concurrent requests. This issue is still troubling me.

@Rookie-Kai This is unexpected. Could you provide a simple reproducible example with the latest version? We can take a look.

Thank you for your reply. After the last similar issue occurred, I restarted the service, and fortunately, it has been running normally for over a week so far without the problem reoccurring. Maybe it was a sporadic NCCL bug? I will keep monitoring the issue, and if it happens again, I will continue to provide feedback in this issue. Fingers crossed it keeps running smoothly.


Use files property in package.json

+1
test/out.json is over 250kb.

Thanks to both of you (also for #8)!

@fb55 No problem! I'd be glad if you release a new version :)

Apparently @npm has problems with the name again: https://github.com/npm/npm/issues/4665. I can't publish a new version right now, but would be willing to switch the package to a lowercase name (if old references could be redirected).
cc @othiym23 @isaacs

Oh, I didn't know that problem.

@fb55 Existing packages should be fine.  You can push updates to them.  you just can't create NEW packages with uppercase letters in the name, afaik.
If you want to lowecase it, you can soft-redirect with the npm deprecate command.

@isaacs This is the response I get:
feedy at feedy in ~/Documents/node_modules/CSSwhat on master [?]
$ npm pub
npm ERR! Darwin 14.0.0
npm ERR! argv "node" "/usr/local/bin/npm" "pub"
npm ERR! node v0.10.35
npm ERR! npm  v2.2.0

npm ERR! Invalid name: "CSSwhat"
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /Users/feedy/Documents/node_modules/CSSwhat/npm-debug.log

@fb55 Yeah, I get it.  I see, it's validating before sending to the registry.  That feels like a reasonably-motivated idea that is unfortunately causing some unpleasant behavior in this case.  We should be rejecting new package creation with uppercase names, but not updates to existing packages.
I'll bring it up with the team here.

Thanks @isaacs!


Upstream merge

Merge from upstream sync for https://github.com/plotly/dekn/issues/9874

Closing as stale.


Apply peasyCam matrix onto PGraphics3D

At the moment I am working on a multi-pass rendering in processing. There I have to use a new PGraphics3D canvas and I can not use the default g object. After the rendering and shading, I'm just going to "print" it on to the g object again as texture:
cam.beginHUD();
image(canvas, 0, 0);
cam.endHUD();

Now I have the problem that things like peasycam do not work anymore because they are attached to the original g and do not transform the camera matrix of my canvas.
So I tried to use the camera matrix of the original graphics and copy it to my canvas:
PGraphics3D p = (PGraphics3D)this.g;
canvas.camera = p.camera;

This did not work, maybe because peasycam is doing something special and it does not change the original camera matrix. So my next idea was to use the static apply method from peasy cam. I had to copy the function out of the original code and make it public:
import peasy.org.apache.commons.math.geometry.Rotation;
import peasy.org.apache.commons.math.geometry.Vector3D;

Vector3D positionVec = new Vector3D(cam.getPosition()[0], cam.getPosition()[1], cam.getPosition()[2]);
Vector3D rotationVec = new Vector3D(cam.getRotations()[0], cam.getRotations()[1], cam.getRotations()[2]);
apply(canvas, positionVec, new Rotation(rotationVec, 0), cam.getDistance());

Here the apply method:
void apply(final PGraphics g, final Vector3D center, final Rotation rotation,
  final double distance) {
  final Vector3D pos = rotation.applyTo(Vector3D.plusK).scalarMultiply(distance).add(center);
  final Vector3D rup = rotation.applyTo(Vector3D.plusJ);
  g.camera((float)pos.getX(), (float)pos.getY(), (float)pos.getZ(), //
    (float)center.getX(), (float)center.getY(), (float)center.getZ(), //
    (float)rup.getX(), (float)rup.getY(), (float)rup.getZ());
}

There I always have a zero norm for rotation (Arithmetic Exception).
So my final idea was to just copy all the rotations and translation to my camera matrix:
canvas.beginCamera();
canvas.camera();

canvas.rotateX(cam.getRotations()[0]);
canvas.rotateY(cam.getRotations()[1]);
canvas.rotateZ(cam.getRotations()[2]);

canvas.translate(
  cam.getPosition()[0],
  cam.getPosition()[1],
  cam.getPosition()[2]);

canvas.endCamera();

So now I could rotate my cube, but it was not accurate and I think there is something wrong with some axis.
I would like to ask if someone has done this before and if there is a simple method to do this?

I'd guess that instead of canvas.camera = p.camera you'd have to copy the peasycam camera, as in canvas.camera = new PMatrix3D(p.camera).
But this is just a guess.

Found this as solution. Works great!
cam.getState().apply(canvas);

Oh, yeah. That's what that's for. :)


⚠ Bofrost.de has degraded performance

In 81344fc, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1643 ms

Resolved: Bofrost.de performance has improved in 4a36bd9 after 7 minutes.


Improve handling of multi pattern unbound variables

Without this change, errors are only being caught when a variable is bound in exactly one of the patterns.
Closes https://github.com/roc-lang/roc/issues/6279

I'll kick off CI, but his should be reviewed by someone more familiar with this part of the compiler I think.

Looks like GitHub's "Update branch" feature removed the signing info from the commit. Fixed it

Pushed a change to adapt the test to new output format

Ping?


Add c++11 compile flags

As per subject.

I guess so. Got that from here:
error: ‘shared_ptr’ in namespace ‘std’ does not name a template type
   typedef std::shared_ptr<realtime_tools::RealtimePublisher<std_msgs::Float64> > RtPublisherPtr;

Ah, thanks for spotting this. It popped up because you still use kinetic, right?


[encryption-utils] v2.2.2 release

Next time I will merg into main then the release created on npm.


WIP: Check types

closes #14

@ghostdevv recommended this starter config: https://gist.github.com/ghostdevv/36b067835a782f18f094c715a5124f2a


Rework fieldset styling

For the radio-button groups and the checkbox-groups to look like the figma design, the styling of the fieldset has to be adapted. A ticket to add spacing between the legend and the first fieldset item already exists: #3847. In addition a padding on the fieldset should be introduced to adhere to the design.

@schaertim please update ticket description with more infos.

Proposed tokens:
post-legend-font-weight,
post-legend-line-height,
post-legend-large-font-size,
post-legent-margin-end,
post-legend-large-padding-block-start,
post-legend-large-padding-block-end,
post-legend-large-margin-block-end,
post-legend-large-border-bottom,
post-legend-large-border-color,
post-legend-large-border-style,
post-legend-large-border-width

@schaertim please make sure the token are also changed in the components it was used as this produces breaks

@sandra-post ready for Design Review :)
Preview Link: https://preview-4092--swisspost-design-system-next.netlify.app/?path=/docs/61faccd2-de2c-48f0-9a06-c051a56580ef--docs


Overhaul Key API

Key API
The Key API as of now mainly consists of

Key::with_offset(key: Key, offset: u32) -> Key
Key::with_chunk_offset(key: Key, offset: u32) -> Key
Key::store(&mut self, bytes: &[u8])
Key::load(&self) -> Vec<u8>
Key::clear(&mut self)

Especially the Key::with_offset and Key::with_chunk_offset APIs are not intuitive.
A better design would be to use the std::ops::Add and std::ops::AddAssign traits and implement them for u32 (replaces uses of Key::with_offset), u64 (replaces uses of Key::with_chunk_offset) and also some versions for i32 and i64 to go in both directions.
Due to technical implementation issues the unsigned variants could be implemented a bit more efficient.
For completeness one could also think about u128 and i128 support since Key is 256-bit anyway.
Also Key::store, Key::load and Key::clear could be marked unsafe since those operations are normally not safe using the raw Key abstraction and are only made safe by the many alternatives, like SyncCell, Value, Vec, etc.

This commit adds std::ops::{Add, AddAssign} implementations for Key for u32 and u64.

Signed versions will follow.
Concerns about adding another std::ops::Sub and std::ops::SubAssign implementation.
Also we could add something similar to a ptrdiff with std::ops::Sub<Key> for Key impl. However, what return type should it have?

Commits https://github.com/Robbepop/pdsl/commit/888039050152dab25ffe6a5421f12ed0046a7430 and https://github.com/Robbepop/pdsl/commit/10e5f15b33110dab0b00fd220d6214b273bd7a5d remove Key::with_chunk_offset and Key::with_offset in favor of the new core::ops::{Add, AddAssign} implementations.

Commit https://github.com/Robbepop/pdsl/commit/89b0be5fb95f27c094ef311e1082a761210c4515 adds core::ops::Sub impl for Key and the KeyDiff type.
Look at commit https://github.com/Robbepop/pdsl/commit/4509914f92d80bf12a1a2511547a7213bc1acf23 on how to use this new interface.

Missing pieces:

impl core::ops::Sub<{u32, u64, u128}> for Key
impl core::ops::Add<u128> for Key
impl core::ops::Add<{i32, i64, i128}> for Key. Note that this hasn't been made yet since the unsigned variants can be implemented a bit more efficiently. This might not be transparent to users so could lead to a slight performance degradation when using signed instead of unsigned after implementing this. Besides that these trait implementations are for convenience.

Besides other things this commit adds core::ops::{Sub, SubAssign} implementations for Key.
Also during implementation we found out that core::ops::{Add,AddAssign,Sub,SubAssign} implementations for RHS = {i32,i64,i128} do not make sense and are semantically difficult to articulate on Key instances so it is better to leave them away and stay with the unsigned variants that have a semantically clear usage story.


undefined is not an object (evaluating 'RNFetchBlob.DocumentDir')

hey guy i'm getting this error undefined is not an object (evaluating 'RNFetchBlob.DocumentDir') ..
i know this was mentioned before but all the solutions didn't help fix the problem for me
i'm going crazy .. i've been trying 9 hours to fix it with no luck
i tried rnpm and didn't work then tried linking manually and still didn't work
i'm using linux and android
and this is my package file
  "name": "funshare",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start"
  },
  "dependencies": {
    "base-64": "^0.1.0",
    "firebase": "^3.1.0",
    "react": "15.2.1",
    "react-native": "0.29.1",
    "react-native-cli": "^1.0.0",
    "react-native-fbsdk": "^0.2.2",
    "react-native-fbsdkcore": "0.0.8",
    "react-native-fbsdklogin": "0.0.8",
    "react-native-fbsdkshare": "0.0.8",
    "react-native-fetch-blob": "^0.6.4",
    "react-native-gifted-spinner": "0.0.5",
    "react-native-icon-badge": "^1.1.1",
    "react-native-image-picker": "^0.21.1",
    "react-native-swipe-cards": "0.0.7",
    "react-native-swiper": "^1.4.8",
    "reflux": "^0.4.1"
  }
}

Hi @rameramwe , apparently you're getting this error because the library is not linked properly. I've noticed that you might using an very old version of this library (0.6.4). Perhaps you can try the following steps :
First, close the app and packager.
Then upgrade rnpm
$ npm install -g rnpm

Remove the installed package
$ rnpm uninstall react-native-fetch-blob

Re-install the library
$ npm install --save react-native-fetch-blob && rnpm link

And there should be some logs in the terminal

To verify if the library is linked properly, check if these lines exists in settings.gradle
include ':react-native-fetch-blob'
project(':react-native-fetch-blob').projectDir = new File(rootProject.projectDir, '../node_modules/react-native-fetch-blob/android')

Also check MainApplication.java
import com.RNFetchBlob.RNFetchBlobPackage;

@Override
    protected List<ReactPackage> getPackages() {
      return Arrays.<ReactPackage>asList(
+          new RNFetchBlobPackage(),
         new MainReactPackage()
      );
    }

Now, run the app see if it work properly
$ react-native run-android

React Native has changed its Android application template in 0.29 which result in rnpm link not working with RN 0.29.0, and 0.29.1. However we've fixed this problem by adding custom rnpm.

@wkh237 Thanks. Let me try that now.

@wkh237 I am still getting the same. Could it be because I am using it from a worker? It is used alongside with react-native-workers could that be the problem; I doubt it.
Thanks

Thats what I got after running rnpm link

hey @wkh237  thanks a lot for the fast and awesome response
i did exactly like you said and i even got the same results in my terminal but still the same error :(

then i tried deleting the build folder in my android folder and uninstalling the package and then reinstalling it and compiling but still no luck ..

@RichardBoyewa  hey man about the skipped thing i got it too you gotta delete this line   new RNFetchBlobPackage(), in mainapplication.java and it'll work actually it'll just add it again :P  .

@wkh237 i noticed this while compiling ..does it matter ?

@rameramwe I did just that and the error is still there. Are you using it from a worker service? I am using this for a background service.
Worker : react-native-workers

@RichardBoyewa  actually no i'm not using Workers but i'm using other stuff like image picker and Fbsdk  do you think this might  be causing the problem ?

@RichardBoyewa , if you're using react-native-workers did you add
new WorkerPackage(new MyAwesomePackage(), new MyAmazingPackage())

to WorkerPackage constructor (which should located in node_modules/react-native-workers/android/src/main/java/co/apptailor/Worker/WorkerPackage.java line 34) ?

I am not sure. I have been on this for a while... But this is an interesting package, I will fight my way through it :-)

@wkh237 Let me do that.... I missed that line :-(

this package is essential for me cause i'm using firebase and i need firebase storage .

@rameramwe , does the firebase upload sample work on you environment ?

i'll check that and see

Heyyyyyyyyyyyyy! 👍 It works.......... uuuuhhnnnnnnn!!! Dancing..... @rameramwe How far with yours? @wkh237 Thanks a billion. Can we drop this line as a comment in the ReadMe, incase someone else try to use it this way.
Thanks guys. You rock!

@RichardBoyewa  congrats man :D hope  i  can fix it too :P

@rameramwe How can I message you directly... there is something you need to take out of your repo ASAP.... Don't commit that to gitHub

@rameramwe check your dependencies to see that they don't need a special installation like mine.

@RichardBoyewa  i don't know how if you want that's my email<EMAIL_ADDRESS>but i know what you mean :P the firebase thing

:-) Sent you a mail. Have u solved urs ?

no not yet i'm trying to get the firebase upload repo running locally and see what'S going on

ok. Best of luck.

@wkh237  i got the repo running and it works and it gave me 80% result why the hell ain't working with original app ? that'S the package file for the upload repo
{
"name": "RNFirebaseUploadSample",
"version": "0.0.1",
"private": true,
"scripts": {
"start": "react-native start"
},
"dependencies": {
"firebase": "^3.2.0",
"react": "15.2.1",
"react-native": "^0.28.0",
"react-native-fetch-blob": "0.9.1",
"react-native-testkit": "^0.1.1",
"react-timer-mixin": "^0.13.3"
}
}
you can see here i'm using react native v0.28.0

@rameramwe , I've tested the library with 0.29.1 Ubuntu 15 environment and it works fine. Could you provide a simplified sample of your project ?

@wkh237  would you like to see the repo ? it's not that big
thank you very much for the help

Yeah, I'd like to help if it's possible.

@wkh237 Awesome :D that'S the repo https://github.com/rameramwe/funshare

@rameramwe , when I try to run the application but it gives me a totally different error message saying that something is incorrect in SwipeCard.js.

I temporarily removed anything in index.android.js it works now.

great .. it'S not important anyways but you should require the library fetch blob and see if it works

@rameramwe , I've noticed that FacebookSDK uses different Android Build Tool (23.0.2) and React Native uses 23.0.1. When the first time I try to build the project, it shows the following error message.

I'm wondering if your environment missed this build tool too. I fix this error by simply open the Android project with Android Studio and install the build tool. Have you tried build the project using Android Studio ?
There's also a StackOverflow thread about install build tools using command line.

@wkh237  no i didn't use android studio

i never got this error

After upgrade react-native-swipe-cards to 0.8.0 and fix the missing comma in SwipeCards.js the app work properly now. Perhaps try clone the repo and reinstall the npm packages ?

@wkh237  thank you very much i go it to work .. i was testing not on genymotion but on my phone .. the solution was  to uninstall the app from my phone and reinstalling it using run-android .. that'S very weird but now it's working perfectly thank you very much again .

@rameramwe , great to hear that ! Please feel free ask any question when needed 😄

Nice job done here @wkh237 . @rameramwe Glad you finally got it to work.

I'll get this exception if I turn on the "Don't keep activities" setting in android. If I turn it off, I can use this library normally. My version is
"react-native-fetch-blob": "^0.9.6".
Thanks.

I'll get this exception if I turn on the "Don't keep activities" setting in android. If I turn it off, I can use this library normally. My version is
"react-native-fetch-blob": "^0.9.6".
Thanks.

I am trying to install your plugin and having this problem. I've tried starting from scratch twice in the past week and I keep getting this screen. I got it installed after a while the first time but I had to reinstall again can't remember how I got around it.
First off, a couple comments about your installation instructions:

You first mention to install the package with npm via npm install --save react-native-fetch-blob.  That's fine. However, right after that you say:

Or if using CocoaPods, add the pod to your Podfile, for example:

If I'm correct, it's not an "or" but a required 2nd step. By using CocoPods, you get the required iOS files right? Also, there should be a pod install instruction after adding the line to the Podfile right? However, when I run pod install, it hangs on trying to install React (0.11.0):

pod install finally finished but it says React has been deprecated:

And I'm seeing this when trying to run react-native run-ios now:

** BUILD FAILED **

The following build commands failed:
        CompileC /Users/dwilt/Projects/GJS/gjs-app/ios/build/Build/Intermediates/Pods.build/Release-iphonesimulator/react-native-fetch-blob.build/Objects-normal/i386/RNFetchBlob.o /Users/dwilt/Projects/GJS/gjs-app/node_modules/react-native-fetch-blob/ios/RNFetchBlob/RNFetchBlob.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
        CompileC /Users/dwilt/Projects/GJS/gjs-app/ios/build/Build/Intermediates/Pods.build/Release-iphonesimulator/react-native-fetch-blob.build/Objects-normal/i386/RNFetchBlobFS.o /Users/dwilt/Projects/GJS/gjs-app/node_modules/react-native-fetch-blob/ios/RNFetchBlobFS.m normal i386 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(2 failures)

I got a same issue of @dwilt

Two things solved the problem for me:
1- use the react-native link command
2- deploy the app again to the device from android studio ( i think using the package manager (npm start) only packages the new javascript code, not the library native code )

I'm getting the same issue but i'm using expo. How can i fix it without detach the project, please help!!

If you are making a Activity and implementing DefaultHardwareBackBtnHandler,  then in your onCreate(Bundle savedInstanceState),  use addPackage() method like this:
mReactInstanceManager = ReactInstanceManager.builder()                 .setApplication(getApplication())                 .setBundleAssetName("index.android.bundle")                 .setJSMainModulePath("index.android")                 .addPackage(new MainReactPackage())                 .addPackage(new RNFetchBlobPackage())                 .setUseDeveloperSupport(BuildConfig.DEBUG)                 .setInitialLifecycleState(LifecycleState.RESUMED)                 .build();

After linking you need to run
pod update


Green tags do not work in some cases

The green tags are not properly working for https://main--bitdefender--hlxsites.hlx.page/solutions/mobile-security-android

@johan-t

The problem was that there was a line break in the content which lead to a change in the HTML that was not recognised by the regex function. Therefore we must remember to not include line-breaks in the tags in the content


Problem with laravel timezone

First of all, thanks for the amazing package.
When I set app.php's zime zone to my local time zone, the eventsub webhook URL keeps throwing SignatureVerificationException with the message Timestamp outside the tolerance zone, it works when I set it back to Laravel's default though.
Is this perhaps a problem on my side?

That's strange. PHP should always use the UTC timestamps in both time and strototime functions when comparing the header and current timestamps.
Could you try out #97 ? This PR introduces time comparisons via Carbon

Thanks for the response,
I tried the PR, I confirm it works with my time zone.

That's strange. PHP should always use the UTC timestamps in both time and strototime functions when comparing the header and current timestamps.

strototime and time takes the time set in PHP. This can actually cause problems if you have not set your system time to UTC. I can reproduce it by the following example:
<?php

// Europe/Berlin
echo date_default_timezone_get() . PHP_EOL;

//<PHONE_NUMBER>
echo strtotime('2021-04-29 22:53:23') . PHP_EOL;

date_default_timezone_set('America/New_York');

//<PHONE_NUMBER>
echo strtotime('2021-04-29 22:53:23') . PHP_EOL;

//<PHONE_NUMBER> !==<PHONE_NUMBER>


Avoding crashes when broker reconnects

Fixes #18

It seems like this PR does improve the situation, but I feel like there's a more general fix to recover from any crash to Inflight. Skimming the code, it looks like other lines could crash as well. Given the bug report, would it be correct in assuming that those would not be handled either?

It seems like this PR does improve the situation, but I feel like there's a more general fix to recover from any crash to Inflight. Skimming the code, it looks like other lines could crash as well. Given the bug report, would it be correct in assuming that those would not be handled either?

Inflight is meant to stop if an update to a track (a back and forth wth the MQTT server) can not be resolved, i.e. a protocol error occurred.
The one error that is now ignored is when the MQTT server sends a package for a track that is no longer "in flight" because the Inflight was somehow just reset. Crashing the Inflight had the MQTT server retrying, causing another crash, etc.
I can't think of a better solution than to ignore a package directed at a "track" that has vanished, but I am open to one.


[flutter_tools] Fix missing stack trace from daemon

When the daemon throws an exception, the receiving client is unable to surface stack traces from the daemon.
This is because it is sent with the trace key here:
https://github.com/flutter/flutter/blob/1e8dd1e4d6d70c5e06525bea3fb164a03d7a6c1d/packages/flutter_tools/lib/src/daemon.dart#L308
But the client tries to read it with the stackTrace key here:
https://github.com/flutter/flutter/blob/1e8dd1e4d6d70c5e06525bea3fb164a03d7a6c1d/packages/flutter_tools/lib/src/daemon.dart#L343
Thanks to @mraleph for spotting this!
List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.
b/326825892
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[ ] I followed the [breaking change policy] and added [Data Driven Fixes] where supported.
[x] All existing and new tests are passing.

Overwrote the Google Testing status because the failing test was already failing and unrelated to this PR.


doc: add upgrade guide

[skip ci]
@xiang90 @hongchaodeng PTAL to see if this is the format and level of detail expected in the upgrade guide.
For operations like creating and restoring from a backup, I've only given a general description and linked to the other docs where it's explained in more detail. I can be more explicit here if required.

ref: https://github.com/coreos/etcd-operator/issues/1046

Some references:
https://github.com/dropwizard/dropwizard/wiki
https://github.com/gitlabhq/gitlabhq/tree/master/doc/update
Let's follow the same rules and provide upgrade docs between one minor version.

@hongchaodeng I realize we only want to provide the update guide for minor versions but I've tacked on the more general way of upgrading the operator for incompatible clusters via restore from backup at the end.
If you think that's not needed or out of place we can remove that.

@hongchaodeng PTAL. I've tried to keep the Backup Safety Precaution section short with just links to existing docs on how to do backup, and restore. If you want to include more detail on that, I can write more expanded docs on how to backup and restore and then link to them.
The point being I want to keep the main upgrade_guide doc uncluttered and short.
Also with the v0.2.x to v0.3.x section I've kept the title as Noticeable changes instead of Manual.
Lastly the incompatible upgrade guide is its own doc now.

LGTM


Multiple rules

id
username
access
topic

1
userA
1
topicA/#

2
userB
3
topicB/#

3
userB
1
topicA/#

I have the next ACL rules table (also there are columns "allow" filled with 1, "ipaddr" filled with NULLs and "clientid" filled with NULLs that are not shown for simplicity).
userA is able to subscribe to the topicA subtopics, userB is able to subscribe and publish to the topicB subtopics.
Expected result:
userB should be able to subscribe to the topicA subtopics
Actual result:
userB should is not able to subscribe to the topicA subtopics

ACL query is select allow, ipaddr, username, clientid, access, topic from device_acl where username = '%u' or username = '$all' or clientid = '%c' limit 1

my fault, removed "limit 1" and it was fixed


Bump workflow library version to 0.1.0-alpha04

Description
Bump workflow library version to 0.1.0-alpha04
Alternative(s) considered
NA
Type
Releases
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

Ok I'm going to merge this as an admin due to the simple nature of this pr and the time requirements.


How to set DEPTH_NORMALIZER in extended POINT_CLOUD_RANGE?

How should I set
https://github.com/open-mmlab/OpenPCDet/blob/26a16123cf820e29ed565f4ad53964c66f3ea030/tools/cfgs/kitti_models/pointrcnn.yaml#L70
if I set
https://github.com/open-mmlab/OpenPCDet/blob/26a16123cf820e29ed565f4ad53964c66f3ea030/tools/cfgs/dataset_configs/kitti_dataset.yaml#L4
to [0, -40, -3, 80, 40, 1]?

It doesn't matter, ``DEPTH_NORMALIZER'' is just used to normalize depth to around [0, 1]. So a similar value with your max depth should be ok.


0ttl

Fix for issue #860

Yes, I'll change it to call msg_cache_remove. Maybe you can to the other two issues in a separate ticket.


[PARQUET] Segmentation fault when writing empty RecordBatches

I have a curious problem.  I am trying to convert a very sparse dataset to parquet (~3% rows in a range are populated).  The file I am working with spans upto ~63M rows.  I decided to iterate in batches of 500k rows, 127 batches in total.  Each row batch is a RecordBatch.  I create 4 batches at a time, and write to a parquet file incrementally.  Something like this:
batches = [..]  # 4 batches
tbl = pa.Table.from_batches(batches)
# btw, is there a guideline on how to choose row_group_size?
pqwriter.write_table(tbl, row_group_size=15000)
# same issue with pq.write_table(..)

I was getting a segmentation fault, I narrowed it down to a specific iteration.  I noticed that iteration had empty batches; specifically, [0, 0, 2876, 14423].  The number of rows for each RecordBatch for the whole dataset is below:
[14050, 16398, 14080, 14920, 15527, 14288, 15040, 14733, 15345, 15799,
15728, 15942, 14734, 15241, 15721, 15255, 14167, 14009, 13753, 14800,
14554, 14287, 15393, 14766, 16600, 15675, 14072, 13263, 12906, 14167,
14455, 15428, 15129, 16141, 15478, 16257, 14639, 14887, 14919, 15535,
13973, 14334, 13286, 15038, 15951, 17252, 15883, 19903, 16967, 16878,
15845, 12205, 8761, 0, 0, 0, 0, 0, 2876, 14423, 13557, 12723, 14330,
15452, 13551, 12723, 12396, 13531, 13539, 11512, 13175, 13941, 14634,
15515, 14239, 13856, 13873, 14154, 14822, 13543, 14653, 15328, 16171,
15101, 150 55, 15194, 14058, 13706, 14747, 14650, 14694, 15397, 15122,
16055, 16635, 14153, 14665, 14781, 15462, 15426, 16150, 14632, 14532,
15139, 15324, 15279, 16075, 16394, 16834, 15391, 16320, 1650 4, 17248,
15913, 15341, 14754, 16637, 15695, 16642, 18143, 19481, 19072, 15742,
18807, 18789, 14258, 0, 0]

On excluding the empty RecordBatch-es, the segfault goes away, but unfortunately I can't work-up a minimal example; e.g. I tried the following:
import pyarrow as pa
import pyarrow.parquet as pq
import numpy as np

batch1 = [pa.array([], type=pa.int8()),
          pa.array([], type=pa.float32())]
batch2 = [pa.array([i for i in range(10)], type=pa.int8()),
          pa.array(np.random.rand(10), type=pa.float32())]

names = ['i', 'f']
batches = [pa.RecordBatch.from_arrays(batch1, names),
           pa.RecordBatch.from_arrays(batch2, names)]

tbl = pa.Table.from_batches(batches)
pq.write_table(tbl, '/tmp/test.pq')

But this works!
I have tried attaching gdb, the backtrace when the segfault occurs is shown below (maybe it helps, this is how I realised empty batches could be the reason).
(gdb) bt
#0  0x00007f3e7676d670 in parquet::TypedColumnWriter<parquet::DataType<(parquet::Type::type)6> >::WriteMiniBatch(long, short const*, short const*, parquet::ByteArray const*) ()
   from /home/user/miniconda3/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.11
#1  0x00007f3e76733d1e in arrow::Status parquet::arrow::(anonymous namespace)::ArrowColumnWriter::TypedWriteBatch<parquet::DataType<(parquet::Type::type)6>, arrow::BinaryType>(arrow::Array const&, long, short const*, short const*) ()
   from /home/user/miniconda3/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.11
#2  0x00007f3e7673a3d4 in parquet::arrow::(anonymous namespace)::ArrowColumnWriter::Write(arrow::Array const&) ()
   from /home/user/miniconda3/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.11
#3  0x00007f3e7673df09 in parquet::arrow::FileWriter::Impl::WriteColumnChunk(std::shared_ptr<arrow::ChunkedArray> const&, long, long) ()
   from /home/user/miniconda3/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.11
#4  0x00007f3e7673c74d in parquet::arrow::FileWriter::WriteColumnChunk(std::shared_ptr<arrow::ChunkedArray> const&, long, long) ()
   from /home/user/miniconda3/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.11
#5  0x00007f3e7673c8d2 in parquet::arrow::FileWriter::WriteTable(arrow::Table const&, long) ()
   from /home/user/miniconda3/lib/python3.6/site-packages/pyarrow/../../../libparquet.so.11
#6  0x00007f3e731e3a51 in __pyx_pw_7pyarrow_8_parquet_13ParquetWriter_5write_table(_object*, _object*, _object*) ()
   from /home/user/miniconda3/lib/python3.6/site-packages/pyarrow/_parquet.cpython-36m-x86_64-linux-gnu.so

Is this sufficient info to file a bug report?  If reproducing this seems difficult, I can share more details about my environment (both data and code are public).

Can you provide example code that reproduces the failure?

So far I have not managed to replicate this with synthetic data.  The data I am using is from the 1000 Genome project, which has been public for many years, so we can be reasonably sure the data is good.  The following steps should help you replicate the issue.

Download the data file (and index), about 330MB:
$ wget ftp://ftp.1000genomes.ebi.ac.uk/vol1/ftp/release/20130502/ALL.chr20.phase3_shapeit2_mvncall_integrated_v5a.20130502.genotypes.vcf.gz{,.tbi}

Install the Cython library pysam, a thin wrapper around the reference implementation of the VCF file spec.   You will need zlib headers, but that's probably not a problem :)
$ pip3 install --user pysam

Now you can use the following script
#!/bin/env python3

from collections import OrderedDict

import pyarrow as pa
import pyarrow.parquet as pq

from pysam import VariantFile

data = 'ALL.chr20.phase3_shapeit2_mvncall_integrated_v5a.20130502.genotypes.vcf.gz'

cols = OrderedDict(
    CHROM=pa.string(),
    POS=pa.int32(),
    ID=pa.string(),
    REF=pa.string(),
    ALTS=pa.list_(pa.string()),
    QUAL=pa.int8(),
)

def to_arrow(vf_itr, cols):
    """Convert `VariantRecord` batches to Arrow `RecordBatch`es

    vf_itr -- Iterator over `VariantFile` that returns `VariantRecord`s
    cols   -- Record column spec (as returned by get_vcf_cols(..))

    returns list of `RecordBatch`es

    """
    batch = [OrderedDict((k, getattr(vrec, k.lower())) for k in cols.keys())
             for vrec in vf_itr]
    # populate as struct -> flatten
    batch = pa.array(batch, type=pa.struct(cols)).flatten()
    return pa.RecordBatch.from_arrays(batch, pa.schema(cols))

vf = VariantFile(data, mode='r', threads=4)
batches = [to_arrow(vf.fetch("20", i*500_000, (i + 1)*500_000), cols) for i in range(56, 60)]
print('# of rows:', [b.num_rows for b in batches])
tbl = pa.Table.from_batches(batches, pa.schema(cols))
pq.write_table(tbl, 'test.parquet')  # this segfaults

My apologies for not providing a proper minimal example.

Cool, would you mind transferring this to a JIRA issue where we can track this?

Done: ARROW-3792
I opened one here because I wasn't sure if my example was sufficiently minimal :).


reshape() supports contiguous array only

Reporting a bug

[x] I am using the latest released version of Numba (most recent is visible in
the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[ ] I have included below a minimal working reproducer (if you are unsure how
to write one see http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports).

Update2:
Problem solved, one need to use numpy.copy() to create a contiguous array copy of the slice for use, and everything will be fine. Like this:
Q = ions[:,1].copy()
A topic about the contiguous array and non-contiguous array is here:
https://stackoverflow.com/questions/26998223/what-is-the-difference-between-contiguous-and-non-contiguous-arrays
Just in case that anyone would encounter the same problem like me.
Update1:
I've read the issue #4819, I think that I've found where the problem is, but if I really need to extract a column out of a 2-d array for use, what should I do? Thanks for the help!
Problem and code:
if I do something like this:
Q = np.array([1.60217663e-19, 1.60217663e-19, 1.60217663e-19, 1.60217663e-19])
Electric_Potential_Force(n, Q, pos, t)

everyting is fine, but if I try someting below, where the ions[:,1] is exactly the Q mentioned above, and warnings come out, am I doing someting wrong? Is it because of the slice I've made here?
I've tried to use q = ions[:,1] to create a new array, but still don't work.
Q = ions[:,1]
Electric_Potential_Force(n, Q, pos, t)

It seems that the problem raise from a numpy.reshape() function used in the self-defined function Electric_Potential_Force(num, q, r, t)
here is the Electric_Potential_Force(num, q, r, t) function:
@jit
def Electric_Potential_Force(num, q, r, t):
    temp = np.zeros((num, 3))
    for i in range(num):
        r_t_temp = np.append(r[i], np.array(t))
        temp[i] = Electric_Potential_Gradient(r_t_temp)
    return temp * q.reshape(num, 1)

warings:
Compilation is falling back to object mode WITH looplifting enabled because Function "Electric_Potential_Force" failed type inference due to: Internal error at <numba.typeinfer.CallConstraint object at 0x0000024B5DF72288>.
reshape() supports contiguous array only
[1] During: resolving callee type: BoundFunction(array.reshape for array(float64, 1d, A))
[2] During: typing of call at f:/Protomol/MD Simulation/test.py (181)
Enable logging at debug level for details.
File "test.py", line 181:
def Electric_Potential_Force(num, q, r, t):

temp[i] = Electric_Potential_Gradient(r_t_temp)
return temp * q.reshape(num, 1)
^
@jit
f:/Protomol/MD Simulation/test.py:173: NumbaWarning:
Compilation is falling back to object mode WITHOUT looplifting enabled because Function "Electric_Potential_Force" failed type inference due to: cannot determine Numba type of <cla
ss 'numba.dispatcher.LiftedLoop'>
File "test.py", line 178:
def Electric_Potential_Force(num, q, r, t):

temp = np.zeros((num, 3))
for i in range(num):
^
@jit
D:\ProgramData\Anaconda3\lib\site-packages\numba\object_mode_passes.py:178: NumbaWarning: Function "Electric_Potential_Force" was compiled in object mode without forceobj=True, but has
lifted loops.
File "test.py", line 174:
@jit
def Electric_Potential_Force(num, q, r, t):
^
state.func_ir.loc))
D:\ProgramData\Anaconda3\lib\site-packages\numba\object_mode_passes.py:187: NumbaDeprecationWarning:
Fall-back from the nopython compilation path to the object mode compilation path has been detected, this is deprecated behaviour.
For more information visit http://numba.pydata.org/numba-doc/latest/reference/deprecation.html#deprecation-of-object-mode-fall-back-behaviour-when-using-jit
File "test.py", line 174:
@jit
def Electric_Potential_Force(num, q, r, t):
^
warnings.warn(errors.NumbaDeprecationWarning(msg, state.func_ir.loc))

Thanks for opening/closing this! Glad you got something working. In general it's a good idea to try and use @jit(nopython=True) or @njit (they are aliases) so that nopython mode is used as this gives the best performance.
If you are new to Numba, perhaps take a look at the 5 minute guide first and/or click one of the Try Now buttons here http://numba.pydata.org/ to open up an interactive Numba demo in your browser, this one demonstrates the basics.

It seems the copy() or ascontiguous() functions takes considerable amount of time in python or numba, especially if it is a big array; unlike a contiguous one. Is there a way to overcome this performance issue with numba? We usually come up with such issues if we take transpose or views on some arrays and end up with a non-contiguous array.

@anilsathyan7 please could you open a new ticket with a reproducing example to discuss, thanks.


[HUDI-2142] Support setting bucket assign parallelism for flink write…

… task
Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contributing.html before opening a pull request.

What is the purpose of the pull request
Support setting bucket assign parallelism for flink write task.
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

Codecov Report

Merging #3239 (2e5df1f) into master (16e90d3) will decrease coverage by 44.75%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #3239       +/-   ##
============================================
- Coverage     47.62%   2.87%   -44.76%
+ Complexity     5502      82     -5420
============================================
  Files           930     281      -649
  Lines         41268   11619    -29649
  Branches       4137     951     -3186
============================================
- Hits          19655     334    -19321
+ Misses        19865   11259     -8606
+ Partials       1748      26     -1722

Flag
Coverage Δ

hudicli
?

hudiclient
0.00% <ø> (-34.59%)
:arrow_down:

hudicommon
?

hudiflink
?

hudihadoopmr
?

hudisparkdatasource
?

hudisync
5.28% <ø> (-49.20%)
:arrow_down:

huditimelineservice
?

hudiutilities
9.25% <ø> (-49.32%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


wrong types - module:modulename/typename turned into just module

I have jsdocs that look like
    /**
     * Creates a framebuffer and attachments.
     *
     * @param {WebGLRenderingContext} gl the WebGLRenderingContext
     * @param {module:twgl.AttachmentOptions[]} [attachments] which attachments to create.
     * @param {number} [width] the width for the attachments.
     * @param {number} [height] the height for the attachments.r
     * @return {module:twgl.FramebufferInfo} the framebuffer and attachments.
     * @memberOf module:twgl/framebuffers
     */

tsd-jsdoc 2.1.3 generated the correct (or at least useful for me) signature
    function createFramebufferInfo(
        gl: WebGLRenderingContext,
        attachments?: module:twgl.AttachmentOptions[],
        width?: number,
        height?: number): module:twgl.FramebufferInfo;

tsd-jsdoc 2.2.0+ generates an incorrect signature
    function createFramebufferInfo(
        gl: WebGLRenderingContext,
        attachments?: module[],
        width?: number,
        height?: number): module;

attachments?: module:twgl.AttachmentOptions[],

I don't think that is valid Typescript, is it? I definitely get errors on the playground trying to use it.
I agree the new one is incorrect as well. Assuming twgl is a module you have somewhere else in code I'd expect the output to just be twgl.FramebufferInfo. PR welcome!

Yea, I agree the old output was wrong but I had some post process to fix it. Now the output is unusable though.

Well look into PR if someone doesn't beat me to it. For now just moved my deps back to 2.1.2

So, I've been having the same issue and decided to try changing modules to imports, e.g. something like this:
if (/^module:/.test(name)) {
  const [mod, imp] = name.replace(/^module:/, '').split('~');
  return ts.createImportTypeNode(ts.createStringLiteral(mod), ts.createTypeReferenceNode(imp || 'default'));
}

Thoughts?


Tp finish

Pull Request Test Coverage Report for Build 55

2 of 36 (5.56%)  changed or added relevant lines in 3 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-15.5%) to 76.834%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

repository/IngSoft2-Model/RandomBoard.class.st
0
34
0.0%

Files with Coverage Reduction
New Missed Lines
%

repository/IngSoft2-Model/Player.class.st
3
92.86%

Totals

Change from base Build 41:
-15.5%

Covered Lines:
199

Relevant Lines:
259

💛  - Coveralls


Failed to create a MLP Site

Hi Team
Getting an error while provisioning MLP. Please check if there is a bug and resolve asap as customers are also reporting the same.
"Unfortunately your site provisioning at least partially failed!" Screenshot attached[](url

)

Hi,
Thanks for using the Look Book site. We've just refreshed the solution and I invite you to test it now. In case of any problem, please create a new issue and provide the PnP Correlation ID (that you get by email together with the provisioning outcome), so that we can investigate it further. Thanks.


0.8 migration - Units

Check all nodes for inputs and outputs that use units.
Make a list of affected nodes.
Wait & hope that Dynamo's built-in conversion functionality will be exposed...

42c31ad0766768350ce72a239aa2b80295c5b751 added unit conversion functionality so there's no dependency on Dynamo proper anymore


Pushing and pulling parameters.

Do you have any plans/ideas how to implement pushing and pulling parameters between coroutines?
Something like this:

http://www.boost.org/doc/libs/1_58_0/libs/coroutine/doc/html/coroutine/coroutine/asymmetric.html
http://www.boost.org/doc/libs/1_58_0/libs/coroutine/doc/html/coroutine/coroutine/symmetric.html

I have thought about that. But have no idea how to set the lifetime gracefully.

@3Hren Hey, take a look at this, is that meet your requirements?
https://github.com/zonyitoo/coroutine-rs/blob/boost/examples/simple.rs

Looks great, thanks!
I will test it ASAP.

I am still looking for the way to implement symmetric coroutines.

The latest commit have implemented asymmetric coroutines.


Add Beta 1.7.3 Items

Added a list of item IDs to the blocks and items documentation and changed the item names to be accurate to Beta 1.7.3.

Looks good, could you include the shifted ID as well? Or replace the ID with the shifted one since that's the one actually used?

Done that. The shifted IDs make more sense.


EF: Initialization

This is a weak initialization with centroids of planes and PC aligment.
It should be outside the regular solve, so a dedicated method should get this first solution to the problem, otherwise, convergence is not guaranteed if the IC is far from the optimum

Fix at #18


[Feature request] Allowing to manually set the serial path.

Feature request

What problem does this feature solve?
When a serial device changes from /dev/ttyUSB0 to /dev/ttyUSB1 for example, and you have to open the configuration to change the path.
How should this be implemented in your opinion?
Just by letting users manually write the path to the serial device.
Are you willing to work on this yourself?
I would like to but do not understand Hyperion enough to do so.

@philibertc I assume you are reposting this in context of alpha10.
What is not clear for me is the difference of manually updating a path versus selecting it from a top down?
If the path would have changed, the drop-down reflects this, given that hyperion looks for feasible configurations in the background. This helps to avoid "wrong" manual configurations.
What I guess is you are looking for is a "stable" path which does not change over time.
Here the answer is not manual configuration, but to use a udev configuration under unix.
That is already supported out-of the box by alpha10.
see https://github.com/hyperion-project/hyperion.ng/pull/1246
In case I missed you point, maybe you outline your problem and not a potential solution...

Hello,
The problem is when you connect the adalight device and the port /dev/ttyUSB0 is already in use, you have to open the configuration to change the port to /dev/ttyUSB1, and it is annoying.

I created a link /dev/ttyUSB-Adalight which works. But I can't select it via the hyperion web interface.


OCPBUGS-41501: Add status box for error handling

Before
Infinite loading
Error not showing up basically
After

/cherry-pick release-4.17

/jira refresh


Needs way to override path to BFI for situation where we cannot side-by-side install BFI to the project dir.

Needs way to override path to BFI for situation where we cannot side-by-side install BFI to the project dir.
--bfi-dir/-B arg
for situation such as:

$SRC_DIR/project_dir and $SRC_DIR is non-writable
$SRC_DIR/batteries-forking-included/example/* so that we don't need the recursive symlink of $SRC_DIR/batteries-forking-included/example/batteries-forking-included
$SRC_DIR/batteries-forking-included/src/batteries_forking_included b/c we cannot put a recursive symlink at $SRC_DIR/batteries-forking-included/src/batteries-forking-included (and it is AWFUL to have a dashed version AND a underscored version of folder in the same folder)

done


KVS versioning abstraction

The current vault impl uses by default the Fabric RWs versioning protos to capture the version of key-value pairs. As this works well for Fabric, other platforms, such as Orion, may need to adopt that versioning scheme.
This issue proposes an KVS versioning abstraction used by the vault, and thereby, make it independent of the actual platform in use. For instance, the vault could store the version information as bytes and the platform provides a marshaller impl to convert the bytes into the proper format according to the platform.

addressed


Port the usage of already impelemnted HMC sampling in tfp

Link to implementation

Notebook demonstrating the use of HMC. PR will be made soon.

Judging from the merge message, pretty sure they are deprecating the tf contrib distribution: https://github.com/tensorflow/probability/commit/0714da045f8bac5ecbcb7b84f20e743088c1c6a5
They probably already done so in the nightly release - we should pin the version up in the config in both branches.


Update discovery book website to track the latest changes to master.

The source code at https://rust-embedded.github.io/discovery/05-led-roulette/the-led-and-delay-abstractions.html is not compatible with new versions of cortex-m-rt because newer cortex-m-rt uses the #[entry] tag instead of entry!(main).
Also, the Cargo.toml file (discovery/src/05-led-roulette/Cargo.toml) doesn't have cortex-m-rt in it leading to: error[E0463]: can't find crate for `cortex_m_rt`
However, the source code at https://github.com/rust-embedded/discovery/blob/master/src/05-led-roulette/the-led-and-delay-abstractions.md is already updated to work with #[entry] (and doesn't need cargo.toml changes), but the website doesn't seem to be updated with the latest code, i don't know why this is.
So all of this would be fixed by just making the website track the master branch (which has up to date example code)

Thank you for the report.
It seems that the "update the build on each commit" logic broke after transferring this repository to the org but it has been fixed now.


Integrate prebuilt libraries

It would be great to have a pattern for integrating prebuilt static libraries. Sometimes there are libraries where the configuration and build scripts are complex and not easily convertible to gyp. Pointing to them is a problem especially for Android, for which there will be multiple copies of the binary for the different target architectures.

Yes, totally agree.  The gyp documentation shows how to do something similar, but I could add an example.  Do you have a library in mind perhaps?

Microsoft’s cross-platform C++ REST SDK (Casablanca) is probably a good candidate for a monolithic library that could be of use for a number of apps that would benefit from the use of prebuilt binaries.

I'm currently playing with openh264 (https://github.com/cisco/openh264), which has just enough in its Makefile that I don't really want to take on converting it to gyp.
Btw my current solution to this is to point a gyp file at one of the Android architecture library files.  e.g.:
'conditions': [
['OS=="ios"', {
"libraries": [
'../prebuilt/ios/libopenh264.a'
]
},'OS=="mac"', {
"libraries": [
'../prebuilt/osx/libopenh264.a'
]
}, 'OS=="android"', {
# This generates a reference to the lib without referencing the
# architecture. Gyp doesn't support specifying multi-architecture
# files, so are added with a hand-written Android.mk.
"libraries": [
'../prebuilt/android/x86/libopenh264.a'
]
}],
]
This generates a line like: LOCAL_STATIC_LIBRARIES := libopenh264 in target.mk. Then in a hand-written Android.mk I include GypAndroid.mk and specify the real path to the architecture-specific library like:
include $(CLEAR_VARS)
LOCAL_PATH := $(PREBUILTS)/$(TARGET_ARCH_ABI)
LOCAL_MODULE := openh264
LOCAL_SRC_FILES := libopenh264.a
include $(PREBUILT_STATIC_LIBRARY)
It works. Something tells me this pattern could be cleaner, though...
P.S. I'm using fat binaries on darwin to avoid this problem.

^ I've actually seen this pattern for Android several times now - the wrapper "root makefile".  The libraries don't even have to be pre-built, they can even be dependencies that have their own (android) Makefiles.
I think Casablanca would be a more general example than h264 - thanks for the idea @tanaka-de-silva

I am happy that Android and Apple Support C/C++ because I plan to make a Application that helps to prevent the phones that are made by Samsung from overheating.
My Plan: Use C++.
Drawbacks: With me having years of experiance of Visual Basic under windows Only I got no idea what API Headers I need to maske this work. I have some knowlege on C and C++ but that is from places of open source games/code made in C/C++. A perfect Example is Doom or even Duke Nukem 3D.
At least I know namespaces, classes, defines, structs, functions, exports, includes, defines, while loops, for loops, if, else, else if blocks, and breaks for loops.
Although I think there is a lot more things the most funniest thing I found in C and C++ when I first seen them before was things like.
#define WIN32_LEAN_AND_MEAN


AttributeError: module 'cupy' has no attribute 'util'

Thank you for using and contributing to CuPy!
If your issue is a request for support in using CuPy, please post it on Stack Overflow or Google Groups (en / ja).
Developer team members are monitoring questions on these channels.
If it is a bug report, please include the following information:

Conditions (you can just paste the output of python -c 'import cupy; cupy.show_config()')

CuPy version: cupy-cuda112
OS/Platform : Ubuntu18.04
CUDA version: 11.2
cuDNN/NCCL version (if applicable)

Code to reproduce:
@cupy.util.memoize(for_each_device=True)
def cupy_launch(strFunction, strKernel):
return cupy.cuda.compile_with_cache(strKernel).get_function(strFunction)
Error messages, stack traces, or logs:
Traceback (most recent call last):
File "/home/Datasets/UCSD _Pedestrian_dataset/Anomaly_Prediction/train.py", line 16, in
from models.liteFlownet import lite_flownet as lite_flow
File "/home/Datasets/UCSD _Pedestrian_dataset/Anomaly_Prediction/models/liteFlownet/lite_flownet.py", line 5, in
from models.liteFlownet import correlation
File "/home/Datasets/UCSD _Pedestrian_dataset/Anomaly_Prediction/models/liteFlownet/correlation.py", line 281, in
@cupy.util.memoize(for_each_device=True)
AttributeError: module 'cupy' has no attribute 'util'

Don't use @cupy.util.memoize, use @cupy.memoize. The formerly cupy.util module is considered private and is now renamed to cupy._util to reflect this intention.

Hello,
The original verison "@cupy._util.memoize(for_each_device=True)", which has error "AttributeError: module 'cupy' has no attribute '_util'"
When I revised to "@cupy.memoize(for_each_device=True)", the code has "module 'cupy' has no attribute 'memoize'
"
CuPy version: cupy-cuda117
OS/Platform : Ubuntu20.04
CUDA version: 11.7
Thank you in advance for answering.


Remove database connections

Hello,
Just a small thing, is there a way to remove database connections through the interface?
Thank you,
Amelia

There is in fact not anymore. I redesigned this a while ago, and removed that button. Forgot to add it back 😅
Will look into adding it again tomorrow.
You can however edit a connection almost completely freely (except for the id). So maybe you can repurpose it in the meantime 😇

Fixed in #206 :)


Docker Package has moved from lxc-docker to docker-engine

This warrants additional investigation to ensure nothing else breaks once we move to the docker-engine package from lxc-docker. Ensuring all the meta stays the same, has init scripts, etc.

http://blog.docker.com/2015/07/new-apt-and-yum-repos/


Query on not existing time series causes database panic

I'm on 0.9.0. I noticed that my database kept crashing when i performed a certain query. I then realized it was because the timeseries did not exist in the database. The query was done through the UI.
The query I executed through the UI was - select * from lo, which resulted in "Error" being shown as a message. I didn't see anything in the response as far as messages are concerned. When i looked in the logs I saw this: http://pastebin.com/iZzyJLyH

This has been fixed in master and 0.9.1-rc1.
https://influxdb.com/download/index.html

Awesome, thanks.


Angular 14 support

Any timeline available for angular 14 upgrade?

No. But feel free to submit a Pull Request. :)

@MaaxGr
@hcsatoshiwatanabe did create a pull request - any chance that you merge than soon?

can we merge the corresponding pr and update npm packages for angular 14?

Hey together. V14 is now released. Thanks for your merge request :)
<EMAIL_ADDRESS>


ArrayIndexOutOfBoundsException in FileUtils#getPath if called with root of primary external storage

When the Uri content://com.android.externalstorage.documents/tree/primary%3A/document/primary%3A is fed into FileUtils#getPath, an ArrayIndexOutOfBoundsException is raised, because the docId for this URI is "primary:" and thus splitting this id on ":" gives an array with length 1
The following fixes the problem:
    if ("primary".equalsIgnoreCase(type)) {
      String path = Environment.getExternalStorageDirectory().getPath();
      if (split.length > 1) {
        path += "/" + split[1];
      }
      return path;
    }

Probably a pull request would be more appropriate to provide a solution.
Nice find though, I see those exceptions in my crash reports quite often. Thanks!


[teemo] Update to v2.3

Describe the pull request

What does your PR fix?

Update to v2.3 version.

Which triplets are supported/not supported? Have you updated the CI baseline?
<linux, widnows / osx, uwp>,

Does your PR follow the maintainer guide?

If you are still working on the PR, open it as a Draft: https://github.blog/2019-02-14-introducing-draft-pull-requests/

@winsoft666 ,LGTM, plesase run command "./vcpkg x-add-version teemo --overwrite-version" and commit again

Thanks for the version update!


Naming consideration (capitalization)

I've integrated QRCoder into our project and in a few minutes I was up and running with QR codes. You've done a great job, thank you!
I felt immediately at home: I was expecting the two-letter QR acronym to stay as a two-letter upper case name in the source code, as recommended by the Framework Design Guidelines summarized here.
There are, however, a few small glitches where the naming is not OK:
var generator = new QRCoder.QRCodeGenerator ();
var data = generator.CreateQrCode (value, QRCoder.QRCodeGenerator.ECCLevel.Q);
var code = new QRCoder.QRCode (data);
var bitmap = code.GetGraphic (8);

CreateQrCode() should be CreateQRCode() for consistency's sake.
ECCLevel uses the three letter acronym ECC which should therefore be written as EccLevel.

There may be other such glitches in the code base, I did not check.
What do you think? Would it be OK for you to introduce breaking changes to make the library
even easier to consume, by removing these small surprises?

Hi @epsitec ,
thanks for your feedback. In theory this is a good and justifiable proposal. Nevertheless I'm a bit scared of the user's/developer's reactions, when they have to rewrite their code after the next update.
Do you have a strategy or idea in mind, how to switch "softly"? May be we can switch by giving support for old an new naming for a while. (While marking the old named functions as obsolete like explained here: http://stackoverflow.com/a/1759357/251719)

@codebude, sorry for the long silence - I somehow lost track of this issue.
I don't see any other solution than duplicating types to keep current implementations from compiling after such a major change. And who knows if type and enum names have not been persisted under some form or another, and what it would mean to break deserialization...
Obsoleting the misnamed types and methods will certainly be useful, until the next major release where such a braking change would be acceptable.

Doing it all at once might be better that way it is just done otherwise it is just delaying the issue

I think a massive code go-through can be justifiable.

Hi @epsitec , @Mrtops and @Hydroque ,
since you guys argue for renaming, let's try to do so. Before doing such breaking changes, I want to ensure, that we have to do this only one time. So can we bring up a list with all classes/methods/variables which shall be changed together? I just want to ensure that nothing is left behind.

File
Type
Old
New

AbstractQRCode.cs
property
QrCodeData
QRCodeData

PayloadGenerator.cs
method
isHexStyle
IsHexStyle

PayloadGenerator.cs
enum-value (CalendarEvent)
iCalComplete
ICalComplete

PayloadGenerator.cs
enum-value (GeolocationEncoding)
GEO
Geo

PayloadGenerator.cs
enum-value (MailEncoding)
MAILTO
MailTo

PayloadGenerator.cs
enum-value (MailEncoding)
MATMSG
MatMsg

PayloadGenerator.cs
enum-value (MailEncoding)
SMTP
Smtp

PayloadGenerator.cs
class
MMS
Mms

PayloadGenerator.cs
enum
MMSEncoding
MmsEncoding

PayloadGenerator.cs
enum-value (MmsEncoding)
MMS
Mms

PayloadGenerator.cs
enum-value (MmsEncoding)
MMSTO
MmsTo

PayloadGenerator.cs
method
HMACToString
HmacToString

PayloadGenerator.cs
enum-value (OneTimePasswordAuthType)
HOTP
Hotp

PayloadGenerator.cs
enum-value (OneTimePasswordAuthType)
TOTP
Totp

PayloadGenerator.cs
enum
OoneTimePasswordAuthAlgorithm
OneTimePasswordAuthAlgorithm

PayloadGenerator.cs
enum-value (OneTimePasswordAuthAlgorithm)
SHA1
Sha1

PayloadGenerator.cs
enum-value (OneTimePasswordAuthAlgorithm)
SHA256
Sha256

PayloadGenerator.cs
enum-value (OneTimePasswordAuthAlgorithm)
SHA512
Sha512

PayloadGenerator.cs
class
SMS
Sms

PayloadGenerator.cs
enum
SMSEncoding
SmsEncoding

PayloadGenerator.cs
enum-value (SmsEncoding)
SMS
Sms

PayloadGenerator.cs
enum-value (SmsEncoding)
SMS_iOS
SmsIos

PayloadGenerator.cs
enum-value (SmsEncoding)
SMSTO
SmsTo

PayloadGenerator.cs
class
SwissQrCode
SwissQRCode

PayloadGenerator.cs
exception-type
SwissQrCodeException
SwissQRCodeException

PayloadGenerator.cs
enum-value (SwissQRCode.Currency)
CHF
Chf

PayloadGenerator.cs
enum-value (SwissQRCode.Currency)
EUR
Eur

PayloadGenerator.cs
method (SwissQRCode.Iban)
IsQrIban
IsQRIban

PayloadGenerator.cs
enum-value (SwissQRCode.IbanType)
QrIban
QRIban

PayloadGenerator.cs
exception-type
SwissQrCodeIbanException
SwissQRCodeIbanException

PayloadGenerator.cs
enum-value (SwissQRCode.ReferenceTextType)
QrReference
QRReference

PayloadGenerator.cs
enum-value (SwissQRCode.ReferenceType)
NON
Non

PayloadGenerator.cs
enum-value (SwissQRCode.ReferenceType)
QRR
Qrr

PayloadGenerator.cs
enum-value (SwissQRCode.ReferenceType)
SCOR
Scor

PayloadGenerator.cs
exception-type
SwissQrCodeReferenceException
SwissQRCodeReferenceException

PayloadGenerator.cs
exception-type
SwissQrCodeContactException
SwissQRCodeContactException

PayloadGenerator.cs
enum-value (WiFi.Authentication)
nopass
NoPass

PayloadGenerator.cs
enum-value (WiFi.Authentication)
WEP
Wep

PayloadGenerator.cs
enum-value (WiFi.Authentication)
WPA
Wpa

QRCodeGenerator.cs
method
CalculateECCWords
CalculateEccWords

QRCodeGenerator.cs
method
CreateCapacityECCTable
CreateCapacityEccTable

QRCodeGenerator.cs
method
CreateQrCode
CreateQRCode

QRCodeGenerator.cs
method
IsValidISO
IsValidIso

QRCodeGenerator.cs
method
XORPolynoms
XorPolynoms

QRCodeGenerator.cs
enum
ECCLevel
EccLevel

Please add, edit, remove, proof and discuss this list. 👍

Thank you for your proposal. It seems that Microsoft has some difficulty at adhering to their own coding standards. See for instance what they did for SHA or HMAC...
https://msdn.microsoft.com/en-us/library/system.security.cryptography.hmac(v=vs.110).aspx
So, switching all acronyms to the three letter words is probably not the path to least surprise for users of Cryptography namespace.
No I am confused.

Hi @epsitec ,
that's why I initially said, that I don't see a big "benefit". Yes, coding standards are good and everyone should try to met the standards, but it's not possible all the time.
I'm still scared, that we could put happy users off, by doing this breaking changes. On the other hand you and the others said, that the changes would make the lib more intuitive to use. But spoken for myself, when I start using a new lib, I don't know how the methods/properties are named. I have to use Intellisense/autocomplete and/or the wiki/docs to learn what methods are available and how to use them. So does renaming methods really bring the effort, when have to use docs/wiki anyway?

You might be right, after all. Removing the surprise of the Qr spelling by breaking compatibility is probably not worth it.

My intent for proposal would be looking through all the code for formatting and regulation.  Making a new release doesn't mean that people can't rely on the previous instance if they want. They will come to want the more additional features in the mean time. As long as the dev has good documentation over what has changed, it shouldn't be that hard to figure out.

Postponed. Maybe implemented in the next major release.


publish this to bower and npm?

:+1:

I would also love to see this published to npm in particular. I'm currently using the git url in a package.json file as an alternative. However I seem to be unable to link to specific releases and I believe this is due to the fact that the release don't contain the package.json file.

:+1:

ok, it looks like author is not going to do this.
forked https://github.com/stevermeister/tinycon2
and published on npm
npm install tinycon2

I would suggest using the git url instead of npm - both the packages that have been published there are not under my control :information_desk_person:
You can easily point at a tag or commit using the github url.


Access targets during initialization

Hey!
First of all, sorry for using GitHub issues for asking questions but not sure what's the best place to ask for help. I want to ask what's the best way to access targets during the initialization process (according to docs,connectedCallback might be too early to query element from the DOM)? Let's say I'd like to setup / start dropzone on a specific target when component is initialized. When / how should I do it?

Actually I've found html-parsed-element which addresses this problem (it's a nice abstraction based on MutationObserver). Unfortunately, it does not allow to override connectedCallback via regular operator assignment (used by @controller decorator), so I've created a PR to fix it. Hopefully it gets merged, so we can access targets in the parsedCallback like this:
import HTMLParsedElement from 'html-parsed-element';
import { controller, attr, target } from '@github/catalyst'

@controller
export default class TextEditorElement extends HTMLParsedElement {
  @target area: HTMLInputElement

  parsedCallback() {
    this.area.value = 'Hello World!'
  }
}

PR got merged, and new version has been released so parsedCallback can be used with catalyst to initialize targets with the component as shown above.
Should I add info to the guides?