Update Wordpress.gitignore

Reasons for making this change:
This file is missing /* to begin with ignoring everything. I have also added a line to ignore Mac's .DS_Store, several of which appear within the directories that belong to wp-content.
TODO
Links to documentation supporting these rule changes:
TODO
If this is a new template:

Link to application or project’s homepage: TODO

Also, should we close this one in favor of #3282 or #3295?


Cannot find module 'koa'.

When importing as mentioned in docs for an express project:
import { express as voyagerMiddleware } from 'graphql-voyager/middleware';

I get
 node_modules/graphql-voyager/middleware/koa.d.ts:1:25 - error TS2307: Cannot find module 'koa'.

 1 import { Context } from 'koa';

from<EMAIL_ADDRESS>

I realized how make it work:
import voyagerMiddleware =  require('graphql-voyager/middleware/express'); app.use('/voyager', voyagerMiddleware.default({ endpointUrl: '/graphql' }));

this way worked better:
import voyagerMiddleware from  'graphql-voyager/middleware/express'; app.use('/voyager', voyagerMiddleware({ endpointUrl: '/graphql' }));

@anodynos @daniloferreira Just published 1.0.0-rc.26 📦 with a fix included. Can you please try.

this way worked better:
import voyagerMiddleware from 'graphql-voyager/middleware/express'; app.use('/voyager', voyagerMiddleware({ endpointUrl: '/graphql' }));

@daniloferreira It's workaround not a full fix since express middlaware still depends on @types/express. So I just removed all externall types from middlewares to completely solve this problem.

@IvanGoncharov I get TypeError: voyagerMiddleware is not a function with the following imports on  1.0.0-rc.26 :
import { express as voyagerMiddleware } from 'graphql-voyager/middleware';  // => undefined
//or
import voyagerMiddleware  from 'graphql-voyager/middleware/express'; // => { }

@Apollinaire Strange, it works for me when I'm doing:
const { express: voyagerMiddleware } = require('graphql-voyager/middleware');

Can you please test the same code in your setup.
I see you are using ES6 modules, what environment do you using babel, typescript, esm?

I'm using Meteor to build, with the ecmascript package, which uses Babel under the hood. To be more precise, i'm trying to include this to  vulcan.js : https://github.com/vulcanjs/vulcan
Any import on server side returns undefined. On the client it works, but I need the middleware to run serverside only, because that's where I create my express app.

@Apollinaire I'm not familiar with meteor so can you please create GitHub repo with the minimal setup to reproduce this issue?

After further search, it seems related to how I build my project. Something in my config must be wrong because I am able to import and run the middleware in other Vulcan/Meteor projects.
I'll update this when I've found the issue, it might be useful for future people

@Apollinaire I'm closing this issue since the original issue was resolved.
But please post your findings here it will help if other Meteor users will have the same problem.

@IvanGoncharov it was just some bad config from me, other should not have the same problem.

@SachaG If I remember well the problem was that I was doing npm i --save-dev graphql-voyager because I was thinking that I only had to use it on dev environment. But Meteor did not like this, so I just did npm i graphql-voyager and it worked !

Haha exact same issue for me! Thanks!


Multiple Config File Support

SIMBA: This is documented well, I want to merge.
Github: This branch has conflicts that must be resolved

What do I need to do to resolve the conflicts? A bit new to this.

click 'Use the command line'  below this line, many thanks
|
|

Sorry, I'm not seeing anywhere to click that? Can you specify a bit more?

hmm, you can search 'Use this command line' in this page :)

Yeah, still not seeing it. Are you able to see it since you've got more permissions than I?

Step 1: From your project repository, check out a new branch and test the changes.
git checkout -b ColeGreenlee-dev dev
git pull https://github.com/ColeGreenlee/PokemonGo-Bot.git dev
Step 2: Merge the changes and update on GitHub.
git checkout dev
git merge --no-ff ColeGreenlee-dev
git push origin dev

@ColeGreenlee you can also do a quick
git fetch [FROM THE DEV BRANCH]
git pull [FROM THE DEV BRANCH]
then you solve merge issues
commit changes to your branch
push to your branch
This will update automatically the Pull request and should solve merging issues

Okay, I done goofed and killed my local stuff. I'm gonna try this again in a second. Thanks for the help


Unresolved reference: ConnectionInfo

The correct class is called "ConnectionInformation"

also doesnt work "ConnectionInformation"

Worked for me tho

It is indeed ConnectionInformation, the readme has been corrected accordingly.

It is indeed ConnectionInformation, the readme has been corrected accordingly.

That means you could close this issue :D


feat: updating network resolution data model

Added all the values for record_type field as per IANA website for network resolution data model.

:tada: This PR is included in version 5.3.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 5.4.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


rcmpy needs to check if the output file is present or not

if it gets deleted or removed, running rcmpy apply should restore it

added on https://github.com/vkottler/rcmpy/pull/21


[Bug] RuntimeError in ModelTpServer

Checklist

[ ] 1. I have searched related issues but cannot get the expected help.
[ ] 2. The bug has not been fixed in the latest version.
[ ] 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.
[ ] 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.
[ ] 5. Please use English, otherwise it will be closed.

Describe the bug
benchmark serving got error when --num-prompts=5
num-prompts=1 and num-prompts=3 work fine, failed when num-prompts=5
Exception in ModelTpServer:
Traceback (most recent call last):
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/managers/tp_worker.py", line 218, in exposed_step
    self.forward_step()
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/managers/tp_worker.py", line 234, in forward_step
    self.forward_prefill_batch(new_batch)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/managers/tp_worker.py", line 446, in forward_prefill_batch
    output = self.model_runner.forward(batch, ForwardMode.EXTEND)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/model_runner.py", line 430, in forward
    return self.forward_extend(batch)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/model_runner.py", line 399, in forward_extend
    input_metadata = InputMetadata.from_schedule_batch(
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/forward_batch_info.py", line 200, in from_schedule_batch
    ret.init_flashinfer_handlers(
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/forward_batch_info.py", line 225, in init_flashinfer_handlers
    update_flashinfer_indices(
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/forward_batch_info.py", line 315, in update_flashinfer_indices
    model_runner.flashinfer_prefill_wrapper_paged.begin_forward(
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/flashinfer/prefill.py", line 804, in begin_forward
    self._wrapper.begin_forward(
RuntimeError: Failed to allocate memory for batch_prefill_tmp_v with size 450494464 and alignment 16 in AlignedAllocator

Exception in ControllerSingle:
Traceback (most recent call last):
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/managers/controller_single.py", line 166, in start_controller_process
    controller.loop_for_forward()
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/managers/controller_single.py", line 103, in loop_for_forward
    out_pyobjs = self.tp_server.exposed_step(recv_reqs)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/managers/tp_worker.py", line 218, in exposed_step
    self.forward_step()
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/managers/tp_worker.py", line 234, in forward_step
    self.forward_prefill_batch(new_batch)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/managers/tp_worker.py", line 446, in forward_prefill_batch
    output = self.model_runner.forward(batch, ForwardMode.EXTEND)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/model_runner.py", line 430, in forward
    return self.forward_extend(batch)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/torch/utils/_contextlib.py", line 116, in decorate_context
    return func(*args, **kwargs)
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/model_runner.py", line 399, in forward_extend
    input_metadata = InputMetadata.from_schedule_batch(
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/forward_batch_info.py", line 200, in from_schedule_batch
    ret.init_flashinfer_handlers(
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/forward_batch_info.py", line 225, in init_flashinfer_handlers
    update_flashinfer_indices(
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/sglang/srt/model_executor/forward_batch_info.py", line 315, in update_flashinfer_indices
    model_runner.flashinfer_prefill_wrapper_paged.begin_forward(
  File "/data1/nfs15/nfs/bigdata/zhanglei/conda/envs/sglang-0.2.13/lib/python3.10/site-packages/flashinfer/prefill.py", line 804, in begin_forward
    self._wrapper.begin_forward(
RuntimeError: Failed to allocate memory for batch_prefill_tmp_v with size 450494464 and alignment 16 in AlignedAllocator

Reproduction
server:
python -m sglang.launch_server --model-path Qwen/Qwen2-7B-Instruct --tensor-parallel-size 1 --disable-radix-cache --host <IP_ADDRESS> --port 8083  --trust-remote-code --served-model-name Qwen2-7B-Instruct --mem-fraction-static 0.9

benchmark:
python benchmark_serving.py --model Qwen2-7B-Instruct --tokenizer Qwen/Qwen2-7B-Instruct  --host <IP_ADDRESS> --port 8083 --dataset-name random --random-input-len 4096 --random-output-len 256 --save-result --num-prompts 5

Environment
Python: 3.10.14 | packaged by conda-forge | (main, Mar 20 2024, 12:45:18) [GCC 12.3.0]
CUDA available: True
GPU 0,1,2,3,4,5,6,7: NVIDIA A100-SXM4-80GB
GPU 0,1,2,3,4,5,6,7 Compute Capability: 8.0
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 12.1, V12.1.105
CUDA Driver Version: 525.85.12
PyTorch: 2.4.0+cu121
sglang: 0.2.13
flashinfer: 0.1.5+cu121torch2.4
triton: 3.0.0
transformers: 4.44.0
requests: 2.32.3
tqdm: 4.66.5
numpy: 1.26.4
aiohttp: 3.10.5
fastapi: 0.112.1
hf_transfer: 0.1.8
huggingface_hub: 0.24.6
interegular: 0.3.3
packaging: 24.1
PIL: 10.4.0
psutil: 6.0.0
pydantic: 2.8.2
uvicorn: 0.30.6
uvloop: 0.20.0
zmq: 26.1.1
vllm: 0.5.4
multipart: 0.0.9
openai: 1.41.1
anthropic: 0.34.1
NVIDIA Topology:
GPU0    GPU1    GPU2    GPU3    GPU4    GPU5    GPU6    GPU7    NIC0    NIC1NIC2    NIC3    NIC4    NIC5    NIC6    NIC7    NIC8    CPU Affinity    NUMA Affinity
GPU0     X      NV12    NV12    NV12    NV12    NV12    NV12    NV12    PXB     PXBNODE     NODE    SYS     SYS     SYS     SYS     SYS     0-31,64-95      0
GPU1    NV12     X      NV12    NV12    NV12    NV12    NV12    NV12    PXB     PXBNODE     NODE    SYS     SYS     SYS     SYS     SYS     0-31,64-95      0
GPU2    NV12    NV12     X      NV12    NV12    NV12    NV12    NV12    NODE    NODEPXB     PXB     SYS     SYS     SYS     SYS     SYS     0-31,64-95      0
GPU3    NV12    NV12    NV12     X      NV12    NV12    NV12    NV12    NODE    NODEPXB     PXB     SYS     SYS     SYS     SYS     SYS     0-31,64-95      0
GPU4    NV12    NV12    NV12    NV12     X      NV12    NV12    NV12    SYS     SYSSYS      SYS     PXB     PXB     NODE    NODE    NODE    32-63,96-127    1
GPU5    NV12    NV12    NV12    NV12    NV12     X      NV12    NV12    SYS     SYSSYS      SYS     PXB     PXB     NODE    NODE    NODE    32-63,96-127    1
GPU6    NV12    NV12    NV12    NV12    NV12    NV12     X      NV12    SYS     SYSSYS      SYS     NODE    NODE    PXB     PXB     NODE    32-63,96-127    1
GPU7    NV12    NV12    NV12    NV12    NV12    NV12    NV12     X      SYS     SYSSYS      SYS     NODE    NODE    PXB     PXB     NODE    32-63,96-127    1
NIC0    PXB     PXB     NODE    NODE    SYS     SYS     SYS     SYS      X      PIXNODE     NODE    SYS     SYS     SYS     SYS     SYS
NIC1    PXB     PXB     NODE    NODE    SYS     SYS     SYS     SYS     PIX      X NODE     NODE    SYS     SYS     SYS     SYS     SYS
NIC2    NODE    NODE    PXB     PXB     SYS     SYS     SYS     SYS     NODE    NODE X      PIX     SYS     SYS     SYS     SYS     SYS
NIC3    NODE    NODE    PXB     PXB     SYS     SYS     SYS     SYS     NODE    NODEPIX      X      SYS     SYS     SYS     SYS     SYS
NIC4    SYS     SYS     SYS     SYS     PXB     PXB     NODE    NODE    SYS     SYSSYS      SYS      X      PIX     NODE    NODE    NODE
NIC5    SYS     SYS     SYS     SYS     PXB     PXB     NODE    NODE    SYS     SYSSYS      SYS     PIX      X      NODE    NODE    NODE
NIC6    SYS     SYS     SYS     SYS     NODE    NODE    PXB     PXB     SYS     SYSSYS      SYS     NODE    NODE     X      PIX     NODE
NIC7    SYS     SYS     SYS     SYS     NODE    NODE    PXB     PXB     SYS     SYSSYS      SYS     NODE    NODE    PIX      X      NODE
NIC8    SYS     SYS     SYS     SYS     NODE    NODE    NODE    NODE    SYS     SYSSYS      SYS     NODE    NODE    NODE    NODE     X
Legend:
X    = Self
SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
PIX  = Connection traversing at most a single PCIe bridge
NV#  = Connection traversing a bonded set of # NVLinks
NIC Legend:
NIC0: mlx5_0
NIC1: mlx5_1
NIC2: mlx5_2
NIC3: mlx5_3
NIC4: mlx5_6
NIC5: mlx5_7
NIC6: mlx5_8
NIC7: mlx5_9
NIC8: mlx5_bond_0
ulimit soft: 65536

try the latest version 0.3.0

ok

@zhyncs 0.3.0 got same error

Ok I’ll take a look asap.

Python: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
CUDA available: True
GPU 0: NVIDIA A100-SXM4-80GB
GPU 0 Compute Capability: 8.0
CUDA_HOME: /usr/local/cuda
NVCC: Cuda compilation tools, release 12.1, V12.1.105
CUDA Driver Version: 535.104.05
PyTorch: 2.4.0+cu121
flashinfer: 0.1.6+cu121torch2.4
triton: 3.0.0
transformers: 4.44.2
requests: 2.32.3
tqdm: 4.66.5
numpy: 1.26.3
aiohttp: 3.10.5
fastapi: 0.112.2
hf_transfer: 0.1.8
huggingface_hub: 0.24.6
interegular: 0.3.3
packaging: 23.2
PIL: 10.2.0
psutil: 5.9.8
pydantic: 2.8.2
uvicorn: 0.30.6
uvloop: 0.20.0
zmq: 24.0.1
vllm: 0.5.5
multipart: 0.0.9
openai: 1.43.0
anthropic: 0.34.1
NVIDIA Topology:
        GPU0    NIC0    NIC1    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      SYS     PXB     48-63,176-191   3               N/A
NIC0    SYS      X      SYS
NIC1    PXB     SYS      X

Legend:

  X    = Self
  SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
  NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
  PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
  PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
  PIX  = Connection traversing at most a single PCIe bridge
  NV#  = Connection traversing a bonded set of # NVLinks

NIC Legend:

  NIC0: mlx5_bond_0
  NIC1: mlx5_bond_1

ulimit soft: 1048576

python -m sglang.launch_server --model-path Qwen/Qwen2-7B-Instruct --tensor-parallel-size 1 --disable-radix-cache --host <IP_ADDRESS> --port 8083  --trust-remote-code --served-model-name Qwen2-7B-Instruct --mem-fraction-static 0.9

python3 -m sglang.bench_serving --model Qwen2-7B-Instruct --tokenizer Qwen/Qwen2-7B-Instruct  --host <IP_ADDRESS> --port 8083 --dataset-name random --random-input-len 4096 --random-output-len 256 --num-prompts 5

It works well for me and I can't reproduce your issue. Maybe you can try docker https://github.com/sgl-project/sglang/?tab=readme-ov-file#method-3-using-docker

@zhyncs I got same error when use docker images https://github.com/sgl-project/sglang/?tab=readme-ov-file#method-3-using-docker

It's a little wired. May you start a new instance, eliminating the environmental issues of the machine itself. And try this
pip install --upgrade pip
pip install "sglang[all]"

# Install FlashInfer CUDA kernels
pip install flashinfer -i https://flashinfer.ai/whl/cu121/torch2.4/

I am getting the same issue:

I launched the server like this:
python3 -m sglang.launch_server --model-path $model_arg --tp 8 --disable-radix-cache --host <IP_ADDRESS> --port 9942 --log-level debug --file-storage-pth /home/dave.makhervaks/SGl ang_storage --chunked-prefill-size 4096
the model I am using is https://huggingface.co/neuralmagic/Meta-Llama-3.1-405B-Instruct-FP8
I am sending requests as part of the MMLU bench https://github.com/sgl-project/sglang/tree/main/benchmark/mmlu

It may be cuased by seet both --disable-radix-cache and --chunked-prefill-size
I test with  --disable-radix-cache or  --chunked-prefill-size -1,it can be work fine.
There warning log when start server, it seems a experimental feature.
You set both `--disable-radix-cache` and `--chunked-prefill-size`. This combination is an experimental feature and we noticed it can lead to wrong generation results. If you want to use chunked prefill, it is recommended not using `--disable-radix-cache`.

@Lzhang-hub thanks for your reply! I tried with just --disable-radix-cache
i.e. like this python3 -m sglang.launch_server --model-path $model_arg --tp 8 --disable-radix-cache --host <IP_ADDRESS> --port 9942 --log-level debug --file-storage-pth /home/dave.makhervaks/SGl ang_storage
and I still get:

when use --disable-radix-cache ,you should add --chunked-prefill-size -1, because sglang enable chunked-prefill default

@Lzhang-hub thanks for your reply! That seemed to have fix it.
Now I am seeing a discrepancy however in hellaswag results. When I run it with the following command:
python3 bench_sglang.py --host http://<IP_ADDRESS> --port 9942 --num-shot 10 --num-questions 10042
I get:
{"task": "hellaswag", "backend": "srt", "num_gpus": 1, "latency": 3303.519, "accuracy": 0.256, "num_requests": 10042, "other": {"num_questions": 10042, "parallel": 64}}
Which is way lower than what they quote here: https://huggingface.co/neuralmagic/Meta-Llama-3.1-405B-Instruct-FP8#accuracy

Same issue as https://github.com/sgl-project/sglang/pull/1304#issuecomment-2324917521. It seems that the space to allocate for batch_prefill_tmp_v and batch_prefill_tmp_s is too large (exceeds the default flashinfer_workspace_size: 384MB).
https://github.com/flashinfer-ai/flashinfer/blob/46ec89317fb112dfb04bc740e711ccd3cdcf96f8/include/flashinfer/attention/handler.cuh#L797
I'm not sure why the required flashinfer space is too large for some settings.
cc: @zhyncs @yzh119 @hnyls2002

@ispobock thanks for looping this in.
However, I do not think this should have something to do with the very bad results I am getting on Hellaswag right?

@dmakhervaks Did you test it on other datasets? gsm8k or mmlu?

@ispobock These are the results I have gathered for various different models.
MMLU
Model | Nshot | Accuracy
Meta-Llama-3.1-8B-Instruct | 0 | 0.684
Meta-Llama-3.1-8B-Instruct | 5 | 0.682
Meta-Llama-3.1-70B-Instruct | 0 | 0.825
Meta-Llama-3.1-70B-Instruct | 5 | 0.825
Meta-Llama-3.1-405B-Instruct-FP8 | 0 | 0.864
Meta-Llama-3.1-405B-Instruct-FP8 | 5 | 0.865
neuralmagic-Meta-Llama-3.1-405B-Instruct-FP8 | 0 | 0.861
neuralmagic-Meta-Llama-3.1-405B-Instruct-FP8 | 5 | 0.862
GSMK8
MODEL | NSHOT | ACCURACY
Meta-Llama-3.1-8B-Instruct | 0 | 0.36
Meta-Llama-3.1-8B-Instruct | 5 | 0.752
Meta-Llama-3.1-8B-Instruct | 8 | 0.801
Meta-Llama-3.1-70B-Instruct | 0 | 0.810
Meta-Llama-3.1-70B-Instruct | 5 | 0.929
Meta-Llama-3.1-70B-Instruct | 8 | 0.939
Meta-Llama-3-1-405B-Instruct-FP8 | 0 | 0.879
Meta-Llama-3-1-405B-Instruct-FP8 | 5 | 0.956
Meta-Llama-3-1-405B-Instruct-FP8 | 8 | 0.961
neuralmagic-Meta-Llama-3.1-405B-Instruct-FP8 | 0 | 0.88
neuralmagic-Meta-Llama-3.1-405B-Instruct-FP8 | 5 | 0.958
neuralmagic-Meta-Llama-3.1-405B-Instruct-FP8 | 8 | 0.961
Hellaswag
Meta-Llama-3.1-8B-Instruct | 0 | 0.315
Meta-Llama-3.1-8B-Instruct | 10 | 0.396
Meta-Llama-3.1-70B-Instruct | 0 | 0.264
Meta-Llama-3.1-70B-Instruct | 10 | 0.252
Meta-Llama-3-1-405B-Instruct-FP8 | 0 | 0.265
Meta-Llama-3-1-405B-Instruct-FP8 | 10 | 0.248
neuralmagic-Meta-Llama-3.1-405B-Instruct-FP8 | 0 | 0.264
neuralmagic-Meta-Llama-3.1-405B-Instruct-FP8 | 10 | 0.256
None of these results match the quoted results from their HF pages, however Hellaswag achieves very poor results. Any ideas?

@dmakhervaks could you try to remove the --disable-radix-cache when testing Hellaswag?

None of these results match the quoted results from their HF pages, however Hellaswag achieves very poor results.

@dmakhervaks The issue is fixed in https://github.com/sgl-project/sglang/pull/1428.

@ispobock why would disabling radix cache when testing hellaswag fix this issue? Does disabling radix cache somehow compromise integrity of calculations?

@dmakhervaks The issue was fixed without disabling the radix cache. You can check the PR mentioned above for more detail. Pls try the newest SGLang version 0.3.1.


work around webpack build warning with earcut

Pulling in Cesium via webpack produces the following warning...
WARNING in ./~/cesium/Source/ThirdParty/earcut-2.1.1.js
Critical dependencies:
1:479-486 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
 @ ./~/cesium/Source/ThirdParty/earcut-2.1.1.js 1:479-486

This PR strips the boilerplate from earcut so it can be loaded directly like other Cesium modules.

Thanks for the fix, @chris-cooper!
@bagnell instead, is it possible to just use the unminified version of earcut?

While we should always use the unminified version of libraries, if I recall correctly, there was no unminified version of earcut that did not include a bunch of debug code.  @bagnell can you please confirm.

Rather than modify the minified version, I'd rather see us modify an unminified version to not include it's debug code (or use pragmas) if possible.

Thanks @mramato.  A couple of things I forgot to mention:

This was more than just a build warning as it caused an earcut error at runtime
The full source code is in a single CommonJS module.  Has anyone looked into if it's feasible for Cesium to pull in CommonJS third party dependencies directly from source code in node_modules (i.e. the reverse of how Terria pulls in AMD cesium dependencies using a require()?

@chris-cooper I'm seeing the warningin 1.23, too, but I'm not seeing any runtime errors.  When do you see that?  My test case it is admittedly pretty simple: I'm loading a GeoJSON with a polygon.  I would expect that to trigger it, though.

It was working OK locally, but intermittently gives the following error when running from a remote server...
earcut.js:645 An error occurred while rendering.  Rendering has stopped.
undefined
Error: importScripts failed for Workers/createPolylineGeometry at https://(url-changed)/cesium/Workers/createPolylineGeometry.js
http://requirejs.org/docs/errors.html#importscripts
Error: importScripts failed for Workers/createPolylineGeometry at https://(url-changed)/cesium/Workers/createPolylineGeometry.js
http://requirejs.org/docs/errors.html#importscripts
    at makeError (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:1191)
    at Function.req.load (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:16165)
    at Object.load (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:12786)
    at Object.load (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:6357)
    at Object.fetch (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:6296)
    at Object.check (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:7362)
    at Object.enable (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:9429)
    at Object.enable (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:11891)
    at Object.<anonymous> (https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:9286)
    at https://(url-changed)/cesium/Workers/cesiumWorkerBootstrapper.js:29:938

I looked into this some more and I think the easiest thing to do is just remove the source map directive from the submitted file.  The "build" we are using is nothing more than the commonjs source file that @chris-cooper mentioned but with a UMD wrapper, so removing the source map should fix the issue without introducing any problems (or making it hard to maintain).  I'll open a PR for people to try out.

@chris-cooper can you give #4169 a try and confirm it fixes the issue?  Thanks.

There was additional discussion of this in #4169, ultimately it is a webpack issue but there's no reason we can't work around it since we know Cesium sues AMD and there's significant maintenance overhead here.

Thanks @chris-cooper


Issue with spells.

When equipping spell memory, the slots are all occupied by Bless which has a cost of 0 in all slots.  You cannot remove or change the slots as no options are made available.
The spell limit is at 500/500 and this doesn't change, even when equipping a second spell memory in your skill slots.
The spell memory priority also does not fill up.
Edit: The indicator for the spell capacity actually does move when equipping spell memory, in the first screenshot the marker/line is far to the right whereas in screenshot 2 it drops down. It doesn't change when equipping a second spell memory though.

I don't think spells has been implemented yet...


Trying to add IKEA Bulbs LED2002G5/LED1935C3 according to tutorial - Err: cannot find module 'zigbee-...'

Hello,
i am trying to add IKEA Bulb LED2002G5 (TRADFRIbulbE14WSglobeopal470lm) and LED1935C3 (TRADFRIbulbE14WWclear250lm)
to Zigbee2MQTT.
(i also posted this here: https://github.com/Koenkk/zigbee2mqtt/discussions/10411)
The problem happens with V1.6.2 and V1.7.0
After pairing to my existing network (including other IKEA bulbs which work) i get this messages:
Dec 28 15:56:39 homebridge npm[430]: Zigbee2MQTT:info  2021-12-28 15:56:39: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"announce","meta":{"friendly_name":"0x804b50fffece16a6"},"type":"device_announced"}'
Dec 28 15:57:47 homebridge npm[430]: Zigbee2MQTT:warn  2021-12-28 15:57:47: Received message from unsupported device with Zigbee model 'TRADFRIbulbE14WSglobeopal470lm' and manufacturer name 'IKEA of Sweden'
Dec 28 15:57:47 homebridge npm[430]: Zigbee2MQTT:warn  2021-12-28 15:57:47: Please see: https://www.zigbee2mqtt.io/how_tos/how_to_support_new_devices.html.
After carefully following the steps it looks this way as described in the tutorial above:
pi@homebridge:/opt/zigbee2mqtt/data $ ls -all
total 52
drwxr-xr-x  3 pi pi  4096 Dec 28 16:04 .
drwxr-xr-x 11 pi pi  4096 Feb 19  2021 ..
-rwxr-xr-x  1 pi pi  1340 Dec 28 16:04 TRADFRIbulbE14WSglobeopal470lm.js
-rwxrwxrwx  1 pi pi  1340 Nov 20 09:32 TRADFRIbulbE14WWclear250lm.js
-rw-r--r--  1 pi pi  1167 Dec 25 17:11 configuration.yaml
-rw-r--r--  1 pi pi 22595 Dec 28 15:06 database.db
drwxr-xr-x 12 pi pi  4096 Dec 26 17:05 log
-rw-r--r--  1 pi pi  3116 Dec 28 16:00 state.json
This is my configuration.yaml:
homeassistant: false
permit_join: true
mqtt:
base_topic: zigbee2mqtt
server: 'mqtt://localhost:1883'
serial:
port: /dev/ttyACM0
devices:
'0x00124b0022670e7a':
friendly_name: '0x00124b0022670e7a'
'0x0017880109164423':
.
.
.
'0x8cf681fffe46edd9':
friendly_name: '0x8cf681fffe46edd9'
'0x001788010b0967d7':
friendly_name: '0x001788010b0967d7'
advanced:
log_level: debug
external_converters:

TRADFRIbulbE14WSglobeopal470lm.js
TRADFRIbulbE14WWclear250lm.js

Then i get the following error:
pi@homebridge:/opt/zigbee2mqtt/data $ sudo journalctl -u zigbee2mqtt.service -f
-- Logs begin at Sun 2021-12-26 16:17:02 CET. --
Dec 28 16:06:39 homebridge npm[430]: Zigbee2MQTT:info  2021-12-28 16:06:39: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"message":"Update available for '0x001788010b0967d7'","meta":{"device":"0x001788010b0967d7","status":"available"},"type":"ota_update"}'
Dec 28 16:07:22 homebridge systemd[1]: Stopping zigbee2mqtt...
Dec 28 16:07:22 homebridge npm[430]: Zigbee2MQTT:info  2021-12-28 16:07:22: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline'
Dec 28 16:07:22 homebridge npm[430]: Zigbee2MQTT:info  2021-12-28 16:07:22: Disconnecting from MQTT server
Dec 28 16:07:24 homebridge npm[430]: Zigbee2MQTT:info  2021-12-28 16:07:24: zigbee-herdsman stopped
Dec 28 16:07:24 homebridge systemd[1]: zigbee2mqtt.service: Succeeded.
Dec 28 16:07:24 homebridge systemd[1]: Stopped zigbee2mqtt.
Dec 28 16:10:02 homebridge systemd[1]: Started zigbee2mqtt.
Dec 28 16:10:14 homebridge npm[12944]: ><EMAIL_ADDRESS>start /opt/zigbee2mqtt
Dec 28 16:10:14 homebridge npm[12944]: > node index.js
Dec 28 16:10:45 homebridge npm[12944]: internal/modules/cjs/loader.js:905
Dec 28 16:10:45 homebridge npm[12944]:   throw err;
Dec 28 16:10:45 homebridge npm[12944]:   ^
Dec 28 16:10:45 homebridge npm[12944]: Error: Cannot find module 'zigbee-herdsman-converters/lib/extend'
Dec 28 16:10:45 homebridge npm[12944]: Require stack:
Dec 28 16:10:45 homebridge npm[12944]: - /opt/zigbee2mqtt/lib/util/utils.js
Dec 28 16:10:45 homebridge npm[12944]: - /opt/zigbee2mqtt/lib/util/settings.js
Dec 28 16:10:45 homebridge npm[12944]: - /opt/zigbee2mqtt/index.js
Dec 28 16:10:45 homebridge npm[12944]:     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:902:15)
Dec 28 16:10:45 homebridge npm[12944]:     at Function.Module._load (internal/modules/cjs/loader.js:746:27)
Dec 28 16:10:45 homebridge npm[12944]:     at Module.require (internal/modules/cjs/loader.js:974:19)
Dec 28 16:10:45 homebridge npm[12944]:     at require (internal/modules/cjs/helpers.js:93:18)
Dec 28 16:10:45 homebridge npm[12944]:     at evalmachine.:5:16
Dec 28 16:10:45 homebridge npm[12944]:     at Script.runInContext (vm.js:144:12)
Dec 28 16:10:45 homebridge npm[12944]:     at Script.runInNewContext (vm.js:149:17)
Dec 28 16:10:45 homebridge npm[12944]:     at Object.runInNewContext (vm.js:303:38)
Dec 28 16:10:45 homebridge npm[12944]:     at Object.getExternalConvertersDefinitions (/opt/zigbee2mqtt/lib/util/utils.js:159:16)
Dec 28 16:10:45 homebridge npm[12944]:     at getExternalConvertersDefinitions.next () {
Dec 28 16:10:45 homebridge npm[12944]:   code: 'MODULE_NOT_FOUND',
Dec 28 16:10:45 homebridge npm[12944]:   requireStack: [
Dec 28 16:10:45 homebridge npm[12944]:     '/opt/zigbee2mqtt/lib/util/utils.js',
Dec 28 16:10:45 homebridge npm[12944]:     '/opt/zigbee2mqtt/lib/util/settings.js',
Dec 28 16:10:45 homebridge npm[12944]:     '/opt/zigbee2mqtt/index.js'
Dec 28 16:10:45 homebridge npm[12944]:   ]
Dec 28 16:10:45 homebridge npm[12944]: }
Dec 28 16:10:45 homebridge npm[12944]: npm ERR! code ELIFECYCLE
Dec 28 16:10:45 homebridge npm[12944]: npm ERR! errno 1
Dec 28 16:10:46 homebridge npm[12944]: npm ERR<EMAIL_ADDRESS>start: node index.js
Dec 28 16:10:46 homebridge npm[12944]: npm ERR! Exit status 1
Dec 28 16:10:46 homebridge npm[12944]: npm ERR!
Dec 28 16:10:46 homebridge npm[12944]: npm ERR! Failed at the<EMAIL_ADDRESS>start script.
Dec 28 16:10:46 homebridge npm[12944]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Dec 28 16:10:46 homebridge npm[12944]: npm ERR! A complete log of this run can be found in:
Dec 28 16:10:46 homebridge npm[12944]: npm ERR!     /home/pi/.npm/_logs/2021-12-28T15_10_46_137Z-debug.log
Dec 28 16:10:46 homebridge systemd[1]: zigbee2mqtt.service: Main process exited, code=exited, status=1/FAILURE
Dec 28 16:10:46 homebridge systemd[1]: zigbee2mqtt.service: Failed with result 'exit-code'.
Dec 28 16:10:46 homebridge systemd[1]: zigbee2mqtt.service: Service RestartSec=100ms expired, scheduling restart.
Dec 28 16:10:46 homebridge systemd[1]: zigbee2mqtt.service: Scheduled restart job, restart counter is at 1.
Dec 28 16:10:46 homebridge systemd[1]: Stopped zigbee2mqtt.
some details:
pi@homebridge:/opt/zigbee2mqtt/data $ npm -v
6.14.15
pi@homebridge:/opt/zigbee2mqtt/data $ lsb_release -a
No LSB modules are available.
Distributor ID:	Raspbian
Description:	Raspbian GNU/Linux 10 (buster)
Release:	10
Codename:	buster
pi@homebridge:/opt/zigbee2mqtt/data $ cat /etc/issue
Homebridge Raspbian - \n (\r)
Node.js Version	v14.18.0
Npm Version	v6.14.15
Any help appreciated thank you!!

It's really difficult to read the logs without proper formatting.
Also, I would think these devices are supported by the latest version of Zigbee2MQTT. Which version of Zigbee2MQTT are you running?

Hello and thank you for your fast response.
currently i am running Zigbee2MQTT version 1.6.2 according to the web-gui of homebridge:

however according to log it says version 1.17.1 - how is that possible?
Is there a way to upgrade manually?
thank you in advance.
2021-12-28.18-14-00.zip

You are confusing the version of the homebridge-z2m plugin (this repository) with the version of Zigbee2MQTT.
Remember that Zigbee2MQTT is a separate system that runs outside of Homebridge. This plugin only communicates with it via an MQTT message broker.
Given that you are running version 1.17.1, I suggest getting the latest version of zigbee2mqtt. How you can do that depends on how you have installed Zigbee2MQTT (so not this plugin) initially.

thank you for the clarification and the support! i will try to update! regards steve


[PSM Interop] Disable custom_lb test for cpp

The code needed for this test was reverted in https://github.com/grpc/grpc/pull/32769.
Let's uncomment this code in https://github.com/grpc/grpc/pull/32799, once the custom_lb support is brought back.

The code was restored in https://github.com/grpc/grpc/pull/32810. No need to disable the test now.


Hugo's built-in figure shortcode title appears in toc

I couldn't find an easy way for my figure titles not to be in the toc.

Maybe using h5 for figure titles as default ? Or give the opportunity for the user to configure the depth of the toc?
Thank you for your work!
--nick

Hi, thank you for using the Zzo theme. I'll investigate for this

Hey~ I want to know how did you import the image. Did you use the shortcode that this theme provides?

Actually I used the "native" Hugo shotcode,  {{< figure src=
"/media/spf13.jpg" title="Steve Francia" >}}
I saw the custom "img" shortcode but I couldn't manage to get it work... I
will try again soon!
Le ven. 6 déc. 2019 à 13:59, zzossig<EMAIL_ADDRESS>a écrit :

Hey~ I want to know how did you import the image. Did you use the
shortcode that this theme provides?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zzossig/hugo-theme-zzo/issues/26?email_source=notifications&email_token=AABU7XUJUPDIZQGCCRJLFVDQXJEDBA5CNFSM4JWVSV5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGEAHDQ#issuecomment-562561934,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABU7XV5A7SVUJJ7U4JDM2LQXJEDBANCNFSM4JWVSV5A
.

Actually I used the "native" Hugo shotcode: {{< figure src="/media/spf13.jpg" title="Steve Francia" >}}
I saw the custom img shortcode but I couldn't manage to get it work... I will try again soon!

OK, my bad, the following works: {{< img src="../../images/whoami/avatar.jpg" title="Image4" caption="Image description" alt="image alt" >}}.
But not with the absolute path in src, because of my baseURL with a path (baseURL = "https://host.fr/blog/")?
And also I really miss a way to customize the size of the image width/height attribute from the figure shortcode: {{< figure src="/media/spf13.jpg" width="100x" title="Steve Francia" >}}

Do you want to use an absolute path? I don't have a solution right now. I'll think about it why the absolute path is not working. And I'll add width and height property to the image shortcode soon😋

No, it's OK for me for the path ;) Great to hear that you'll add width and height property to the image shortcode soon.
Thanks!

I just added width and height property. You can do like this
{{< img src="../../images/whoami/avatar.jpg" title="Image4" caption="Image description" alt="image alt" width="100px" height="100px" >}}


Selfhealing: 0-ORK

Problem
It is not possible to remotely monitor nodes to prevent them from being DDOS'ed, just because when it really happens you can't access them anymore.
Solution
We will need to run a daemon on each node (can do it in a privileged container) that can execute the self-healing actions locally, and then report to AYS via the pub sub logging infrastructure that it has executed a self healing action eg by disabling a network interface. AYS can then investigate to which vm / container this interface belongs, and subsequently set the vm / container in the "network_killed" status and report via the health-checks what happened. The user can then over the console / core-x api fix the problem, and resume the networking of the vm / container.
Deliverable

0-ORK daemon written in GO, that monitors packets in VxLan interfaces, vm interfaces and GW pub ip interfaces and communicates via the pub sub logging infrastructure if an action was taken, or to notify a warning status.

over 8k packets/second ==> HEALTHCHECK WARNING and add 200ms latency to the NIC
over 10k packets/second ==> HEALTHCHECK ERROR & SELFHEALING action; i.e. shut the NIC down

flist for 0-ORK container (https://github.com/zero-os/0-core/issues/396)
core-0 will spawn the 0-ORK container at boot automatically
"network_killed" status on vm / container
health-check report towards outside world
documentation on the whole system

See also:

https://github.com/0-complexity/selfhealing/blob/master/jumpscripts/healthchecks/vm_network_load.py
https://github.com/0-complexity/selfhealing/blob/master/jumpscripts/maintenance/selfhealing_threashold.py

can this be done as co-routine in main daemon or is this dangerous?

Kristof De Spiegeleer, [07.07.17 02:02]
I believe we should never rely on privileged containers to do anything because this breaks the security concept of zero-os
Kristof De Spiegeleer, [07.07.17 02:02]
the goal is that golang is the master process controlling everything
Kristof De Spiegeleer, [07.07.17 02:03]
from moment you allow privileged containers you break security completely (hacker surface expands x<PHONE_NUMBER>00)
Kristof De Spiegeleer, [07.07.17 02:03]
if we need to do this short term to win some development time, fine by me but for sure not long term
Kristof De Spiegeleer, [07.07.17 02:06]
if we need to run subprocess, we need to make this subprocess part of the building process of our zero-os
Kristof De Spiegeleer, [07.07.17 02:06]
and no-one should be able to remotely spawn privileged container
Kristof De Spiegeleer, [07.07.17 02:06]
it is prob ok that zero-os himself spawns a privileged container to get a predefined flist as a primitive function insize zero-os
Kristof De Spiegeleer, [07.07.17 02:07]
so not generic container driven by ays

I think that the zero-os API should allow the creation of privileged containers, but via the 0-orchestrator API we should not allow it.
Currently we use privileged containers for running

OpenvSwitch (creates devices, needs to be privileged)
NBD & Tlog server (currently runs privileged but host networking should be enough)

Eg for OpenvSwitch we cannot go around running privileged containers.
See also https://github.com/zero-os/0-orchestrator/issues/674

@despiegk

can this be done as co-routine in main daemon or is this dangerous?

The advantage of running it as a separate privileged container is that is more easily to maintain, update, without needing core-0 to be rebooted.

@despiegk we changed the specs according to your recommendations

@FastGeert I assume this is to be added to the current logic of 0-ORK (killing processes/VMs if the cpu usage and/or memory exceeds certain thresholds).
While privileged containers can access system resources, they still run in a separate PID namespace, hence they can not know about processing running on the node or on other containers.
We have 2 options:

Add more options to container creations to refine what namespaces it should use.
Run ORK directly on the node (easier of course) but we will need to include it in the image.

I would prefer we do the second option.
I don't think we should allow container to be more privileged.

See https://github.com/zero-os/0-core/issues/396 for detail about how we are going to spawn/run the 0-ork

Note to QA: This needs to be tested in a production environment.

After some discussions with @grimpy  and @muhamadazmy  we agreed that the status update should be on the nic, not on the container/vm since they may have other reachable nics. I created this ticket for that change https://github.com/zero-os/0-orchestrator/issues/986.

test in be-scale-2 with steps

create container C1  in node1 with vxlan network
create container C2 in node2 with same network  for C1
try to make C1 ping C2 ,but failed to connect to each other due to hardware issue in env

So this Issue blocked till env be available

Software Version
a7ed0d5e0925d86bb95c95726eff3635efca7440


Uses fixed version of node-crypt3

I submitted a PR against node-crypt3, but it looks like the project is dead. I could push it to NPM under a different name?
Also the tests for this in spec/lib/services/encryption-spec.js do not pass on mac before or after this change.
https://hwjiraprd01.corp.emc.com/browse/MON-542
I setup travis-ci for node-crypt3 that builds it for node 0.10, 0.12, 4.0, 4.1 on linux and mac:
https://travis-ci.org/rolandpoulter/node-crypt3

So it's just broken on node 4 right now? I'm leaning towards just closing this rather than introduce Roland's fork as a dependency, and solving the problem when we transition to node 4.

We should be able to remove the dependency and use built in crypto as well.
Some time needs to be put into it though.
On Nov 3, 2015, at 10:52 AM, Ben Broderick Phillips <notifications<EMAIL_ADDRESS>wrote:
So it's just broken on node 4 right now? I'm leaning towards just closing this rather than introduce Roland's fork as a dependency, and solving the problem when we transition to node 4.
—
Reply to this email directly or view it on GitHubhttps://github.com/RackHD/on-core/pull/12#issuecomment-153452472.

Ok, so does that mean I should close this, or is there a reason to keep it open?

If https://hwjiraprd01.corp.emc.com/browse/MAG-248 is resolved, close this PR is OK. Now I still cannot find the solution for MAG-248. Of course, if we have plenty of time before using Node 4.0, close this PR is OK as well, because I agree with @jfrey , use built-in library should be the target.


run_tests_csharp_macos_opt_native fails after all tests passed

Happened in https://grpc-testing.appspot.com/job/gRPC_pull_requests_macos/4493/testReport/junit/(root)/aggregate_tests/run_tests_csharp_macos_opt_native/
2017-04-12 00:51:32,859 SUCCESS: All tests passed
tools/run_tests/helper_scripts/run_tests_in_workspace.sh: line 47: 67916 Alarm clock: 14         python "${WORKSPACE_NAME}/tools/run_tests/run_tests.py" $@

Should be fixed by https://github.com/grpc/grpc/pull/11520.


Simplify Product Form

Issue
Connects N/A
What was done

[x] Simplified the ProductForm by componentizing the location, product tags, start, and end date fields

How to test

Check out the app and ensure that the product form works like it did before. Nothing should have changed visually or functionality wise.

Approved


Automatic dependsOn for child resources using modules

When deploying resources and associated child resources in the same template I can not get automatic dependsOn to work without outputting the parent resource name and passing it as a parameter to the child resource, or adding a manual dependsOn. Since I already have the name of the parent resource I find the additional steps to output a name I already know overly complicated. Might be my mistake as well...
Below is an example deployment of a Firewall Policy and Rule Collection Group.
First I have my Firewall Policy module, FWPolicy.bicep
param location string {
  default: resourceGroup().location
  metadata: {
    description: 'Specifies the Azure location where the key vault should be created.'
  }
}
param policyname string {
  metadata: {
    description: 'Specifies the name to use for the Firewall Policy'
  }
}
param dnsservers array {
  default: [
    '<IP_ADDRESS>'
  ]
  metadata: {
    description: 'Specify custom DNS Servers for Azure Firewall'
  }
}

resource policy 'Microsoft.Network/firewallPolicies@2020-06-01' = {
  name: policyname
  location: location
  properties: {
    threatIntelMode: 'Alert'
    dnsSettings: {
      servers: dnsservers
      enableProxy: true
    }
  }
}

output fwpolicyname string = policy.name
output fwpolicyid string = policy.id

I also have a module for my Rule Collection Group, FwPolicyPlatformRCG.bicep
param fwpolicyname string

resource platformrcgroup 'Microsoft.Network/firewallPolicies/ruleCollectionGroups@2020-06-01' = {
    name: '${fwpolicyname}/Platform-Rules'
    properties: {
        priority: 100
        ruleCollections: [
            {
                ruleCollectionType: 'FirewallPolicyFilterRuleCollection'
                name: 'Allow-Azure-KMS'
                priority: 100
                action: {
                    type: 'Allow'
                }
                rules: [
                    {
                        ruleType: 'NetworkRule'
                        name: 'Azure-KMS-Service'
                        description: 'Allow traffic from all Address Spaces to Azure platform KMS Service'
                        sourceAddresses: [
                            '*'
                        ]
                        sourceIpGroups: []
                        ipProtocols: [
                            'TCP'
                        ]
                        destinationPorts: [
                            '1688'
                        ]
                        destinationIpGroups: []
                        destinationAddresses: []
                        destinationFqdns: [
                            'kms.core.windows.net'
                        ]
                    }
                ]
            }
        ]
    }
}

main.bicep looks like this:
targetScope='subscription'

param location string {
  default: 'westeurope'
  metadata: {
    description: 'Specifies the Azure location where the key vault should be created.'
  }
}

var fwpolicyname = 'fw-${location}-policy'

resource wanrg 'Microsoft.Resources/resourceGroups@2020-06-01' = {
  name: 'policyrg-rg'
  location: location
}

module fwpolicy './FwPolicy.bicep' = {
  name: 'fwpolicydeploy'
  scope: resourceGroup(policyrg.name)
  params: {
    policyname: fwpolicyname
    location: location
  }
}

module rcgroupplatform './FwPolicyPlatformRCG.bicep' = {
  name: 'rcgroupplatformdeploy'
  scope: resourceGroup(policyrg.name)
  params: {
    fwpolicyname: fwpolicy.outputs.fwpolicyname
  }
}

For the dependsOn to be generated for the Microsoft.Network/firewallPolicies/ruleCollectionGroups resource I need to output the resource name from the module deploying the Microsoft.Network/firewallPolicies resource and passing it in as a parameter to the next module. Or specify a manual dependsOn for the Rule Collection Group.
Suggested solution
It would be awesome if bicep build could look at the resource type being deployed, and if it is a child resource add automatic dependsOn based on the child resource name. For example if the first segment of the child resource name matches another resource in the same template add a dependsOn when compiled.
This is how I want to be able to define the main.bicep template.
main.bicep
targetScope='subscription'

param location string {
  default: 'westeurope'
  metadata: {
    description: 'Specifies the Azure location where the key vault should be created.'
  }
}

var fwpolicyname = 'fw-${location}-policy'

resource wanrg 'Microsoft.Resources/resourceGroups@2020-06-01' = {
  name: 'policyrg-rg'
  location: location
}

module fwpolicy './FwPolicy.bicep' = {
  name: 'fwpolicydeploy'
  scope: resourceGroup(policyrg.name)
  params: {
    policyname: fwpolicyname
    location: location
  }
}

module rcgroupplatform './FwPolicyPlatformRCG.bicep' = {
  name: 'rcgroupplatformdeploy'
  scope: resourceGroup(policyrg.name)
  params: {
    fwpolicyname: fwpolicyname
  }
}

The challenge is that we have no easy way of knowing which module should go first. One thing we could potentially expose is the resources that are created in the module is read-only properties, so you could do something like:
module rcgroupplatform './FwPolicyPlatformRCG.bicep' = {
  name: 'rcgroupplatformdeploy'
  scope: resourceGroup(policyrg.name)
  params: {
    fwpolicyname: fwpolicy.resources.policy.name
  }
}

So you wouldn't have to declare the output. Thoughts?

That would be a nice way of solving it! When you're working with multiple module files in large deployments you end up with a lot of outputs in the end. I've started to output the name and id of all resources in my module files by default, because I never know when I need to use them and that is properties that are often used. I created a template the other day where I'm consuming 29 outputs from resources deployed in different modules. There is a lot of jumping back and forth between module files and main when authoring the template. I like your suggested solution since it would solve both the dependsOn issue and make the authoring experience more pleasant with less outputs in the module files.

@StefanIvemo Would it be ok to automatically expose all the resources from the child module to the parent module? Or would you want that to be opt-in?

@majastrz I would be ok with the automatic option.

Automatically exposing all resources from child modules seems like an excellent idea! The whole notion of having to edit a module (adding outputs) based on how I want to consume it feels backwards and this would solve this.

@StefanIvemo and @SimonWahlin The counterpoint to this is that the resources exposed by a module could be considered part of the module contract. Accidental modifications could lead to breaking changes in the parent module. This is likely less of an issue with local modules, but can potentially cause trouble when modules are published to a module registry. (We don't have that ability yet, but we will.)
Thoughts?

@majastrz While I think there is a valid point to be made relating to the module registry my general view would be to document the recommendation and let developers decide how best to handle the situation.  For example, I think that the vast majority of people will either write their own local modules or simply be consumers and therefore this change would massively help the vast majority of people.
A general rule of thumb in my mind is if you own the lot (both creation and consumption) then you can use direct resource referencing however if you are pushing something to the registry then key information should be exported via outputs and should be considered an 'Interface'.  This also enables developers to override this standard by directly referencing resources if they feel they need to however I would consider this generally unsupported by the module owner and you do so at your own risk (like referencing an internal c# interface or equivalent).

@majastrz  I've been thinking this over during the day. And I would say that it doesn't matter if it´s a local module or a module in a module registry. I still want all resources from the child modules exposed. As an author of a module published to a module registry I never know what properties from the resources deployed in the module the consumer of the module want to use in their template.  For a high quality module there will have to be a lot of outputs declared for it to be useful.
Let's say I have authored two modules and published them to a module registry. The first creates a Virtual Network and the second a Virtual Network Gateway.
VNet.bicep
The VNet template looks like this. I have a parameter called subnet of the type array because I can't define the subnets in advance. To allow my consumers to reference the subnets i must output the properties of the subnets created output subnets array = vnet.properties.subnets. I've also added name and id just in case.
param location string
param vnetname string
param addressprefix string
param subnet array

resource vnet 'Microsoft.Network/virtualNetworks@2020-05-01' = {
  name: vnetname
  location: location
  properties: {
    addressSpace: {
      addressPrefixes: [
        addressprefix
      ]
    }
    subnets: subnet
  }
}

output id string = vnet.id
output name string = vnet.name
output subnets array = vnet.properties.subnets

VNetVPNGw.bicep
The module that deploys the VPN Gateway looks like this. I need to define a lot of outputs for all different use cases if someone wants to setup for example a VPN tunnel using the deployed VPN Gateway.
param location string
param vpngwname string
param subnetref string
param asn int {
  default: 65010
}

resource vpngwpip 'Microsoft.Network/publicIPAddresses@2020-06-01' = {
  name: '${vpngwname}-pip'
  location: location
  sku: {
    name: 'Standard'
  }
  properties: {
    publicIPAllocationMethod: 'Static'
  }
}

resource vpngw 'Microsoft.Network/virtualNetworkGateways@2020-06-01' = {
  name: vpngwname
  location: location
  properties: {
      gatewayType: 'Vpn'
      ipConfigurations: [
          {
              name: 'default'
              properties: {
                  privateIPAllocationMethod: 'Dynamic'
                  subnet: {
                      id: subnetref
                  }
                  publicIPAddress: {
                      id: vpngwpip.id
                  }
              }
          }
      ]
      activeActive: false
      enableBgp: true
      bgpSettings: {
          asn: asn
      }
      vpnType: 'RouteBased'
      vpnGatewayGeneration: 'Generation1'
      sku: {
          name: 'VpnGw1AZ'
          tier: 'VpnGw1AZ'
      }
  }
}

output id string = vpngw.id
output name string = vpngw.name
output publicip string = vpngwpip.properties.ipAddress
output bgpaddress string = vpngw.properties.bgpSettings.bgpPeeringAddress
output bgpasn int = vpngw.properties.bgpSettings.asn

main.bicep
An example main.bicep could look like this.
param location string = resourceGroup().location
param vnetname string = 'superduper-vnet'
param addressprefix string = '<IP_ADDRESS>/24'
param subnet array {
  default: [
    {
      name: 'snet-servers'
      properties: {
        addressPrefix: '<IP_ADDRESS>/26'
      }
    }
    {
      name: 'GatewaySubnet'
      properties: {
        addressPrefix: '<IP_ADDRESS>/26'
      }
    }
  ]
}

module vnet './VNet.bicep' = {
  name: 'vnetdeploy'
  params: {
    vnetname: vnetname
    addressprefix: addressprefix
    location: location
    subnet: subnet
  }
}

module vpngw './VNetVPNGw.bicep' = {
  name: 'vpngwdeploy'
  params: {
    location: location
    vpngwname: '${vnetname}-vpngw'
    subnetref: vnet.outputs.subnets[1].id
  }
}

resource wan 'Microsoft.Network/virtualWans@2020-06-01' = {
  name: 'super-wan'
  location: location
  properties: {
      type: 'Standard'
      disableVpnEncryption: false
      allowBranchToBranchTraffic: true
      office365LocalBreakoutCategory: 'None'
  }
}

resource vpnsite 'Microsoft.Network/vpnSites@2020-06-01' = {
  name: 'onprem-vpnsite'
  location: location
  properties: {
      addressSpace :{
          addressPrefixes: [
            addressprefix
          ]
      }
      bgpProperties: {
          asn: vpngw.outputs.bgpasn
          bgpPeeringAddress: vpngw.outputs.bgpaddress
          peerWeight: 0
      }
      deviceProperties: {
          linkSpeedInMbps: 0
      }
      ipAddress: vpngw.outputs.publicip
      virtualWan: {
          id: wan.id
      }
  }
}

It would be really nice if it would work as @alex-frankel suggested. It would improve the authoring experience a lot! Now I need to jump back and forth between modules. I need to make sure that i output properties that I might need later on. And it would also be a lot more clear in the main template what property I'm actually referencing to. With outputs I'm in the hands of the developer of the module to name the outputs in a descriptive way, I want to be able to look at the main template and understand what property from the child module I'm actually using.

Just jumping in to share that the more I think about this thread, the more I think we should do this. This statement is convincing for me:

As an author of a module published to a module registry I never know what properties from the resources deployed in the module the consumer of the module want to use in their template.

It feels like it will either be too hard to know the exact outputs that will be needed, or it will become too noisy with outputs to try to cover all predicted scenarios. It does mean there are more likely to be breaking changes since authors will not know what properties their consumer are depending on, but as long as we have a good versioning story it should be manageable IMO.

what about being able to declare resource as 'public'? adding that keyword would give ability for module developers to expose only significant resources rather than all of them.
Or the opposite - all resources are public by default and developer can close resource to module only using 'private' keyword.

as long as we have a good versioning story it should be manageable IMO.

If someone refactors a module and removes some resource declarations from it, they will disappear from the contract. If the consumer depended on those and was updated to use the latest version of the module, it will no longer compile.
I'm wondering if we should enforce semantic versioning when modules are published to a registry. This would mean we have logic to detect breaking changes and block publishing to the registry unless the publisher increments the major version of the module. With local modules, I wouldn't want to enforce anything.
On the other hand, this sort of breaking changes detection could only really be contract based, but there are ways to introduce module breaking changes in the module implementation as well (setting changes that aren't backwards compatible or cause downtime, for example). But if the detection would be partial, perhaps we shouldn't do it at all and leave it as a responsibility of the module author?
@miqm Yeah, allowing the module author to control visibility is an option as well.

@majastrz problem with api/contract breaking changes affects all software. since bicep is a compiler, if the linked module does not publish resource you're basing anymore, you will get compiler/linker error and it's up to developer, not the tool maker, to fix this issue and keep track of breaking changes in external dependencies.
when you talk about registry, what do you have in mind? are there plans for building something special for bicep or leverage nuget/npm artifactories? if we use the latter, adding another versioning to the file IMHO might result in lots of packages with versions being bumped while file inside package will remain on <IP_ADDRESS>  and I think we don't need such strong linking. Moreover it's going to be static linking, not dynamic (unless we're talking on linking external arm templates but that is not this feature about I think)

+1 on this:

Or the opposite - all resources are public by default and developer can close resource to module only using 'private' keyword.

I like the notion of having all resources output as 'public' by default and being able to declare resources as private to reduce the amount of output. This will make it easy for new authors to not have to think about public/private at all and give more experienced authors a method to make the output less confusing.

+1 on this:

Or the opposite - all resources are public by default and developer can close resource to module only using 'private' keyword.

I like the notion of having all resources output as 'public' by default and being able to declare resources as private to reduce the amount of output. This will make it easy for new authors to not have to think about public/private at all and give more experienced authors a method to make the output less confusing.

Somewhat related to #1170

Linking #1242 as module versions were mentioned in this thread.


ttnn.bitwise_left_shift gives results different from the torch version when the bit used to represent a sign differs from the bit on position 31 - shift_bits

Describe the bug
ttnn.bitwise_left_shift gives results different from the torch version when the bit used to represent a sign differs from the bit on position 31 - shift_bits, where shift_bits is an argument indicating how many bit spots should the binary representations of the input tensor elements be shifted to the left.
To Reproduce

Create a test_bitwise_left_shift.py file.
Copy the lines of code bellow to the created file

from loguru import logger
import random
import pytest
import torch
import ttnn

from tests.ttnn.utils_for_testing import assert_with_pcc
from tests.ttnn.python_api_testing.sweep_tests import ttnn_ops

def run_bitwise_left_shift_tests(input_shape, dtype, dlayout, in_mem_config, output_mem_config, data_seed, shift_bits, device):
    torch.manual_seed(data_seed)

    x = torch.randint(-2147483647,<PHONE_NUMBER>, input_shape[0], dtype=torch.int32)

    changebit = 31 - shift_bits
    exludebit_mask = torch.bitwise_not(torch.tensor(2**changebit).to(torch.int32))
    includebit_mask = torch.tensor(2**changebit).to(torch.int32)

    x = torch.where(x < 0, torch.bitwise_and(x, exludebit_mask), torch.bitwise_or(x, includebit_mask))
    # Uncomment the line bellow and comment the line above for the unit test to pass
    #x = torch.where(x < 0, torch.bitwise_or(x, includebit_mask), torch.bitwise_and(x, exludebit_mask))

    try:
        # get ref result
        ref_value = torch.bitwise_left_shift(x, shift_bits)

        tt_x = ttnn_ops.setup_ttnn_tensor(x, device, dlayout[0], in_mem_config[0], dtype[0])

        tt_result = ttnn.bitwise_left_shift(tt_x, shift_bits)
        tt_result = ttnn_ops.ttnn_tensor_to_torch(tt_result, output_mem_config[0])

    except Exception as e:
        logger.warning(f"Operation execution crashed")
        raise e

    assert len(tt_result.shape) == len(ref_value.shape)
    assert tt_result.shape == ref_value.shape
    assert_with_pcc(ref_value, tt_result, 0.99)

test_sweep_args = [
    (
        [(32, 96)],
        [ttnn.int32],
        [ttnn.TILE_LAYOUT],
        [ttnn.DRAM_MEMORY_CONFIG],
        [ttnn.L1_MEMORY_CONFIG],
        17799073,
        1,
    ),
    (
        [(3, 160, 224)],
        [ttnn.int32],
        [ttnn.TILE_LAYOUT],
        [ttnn.L1_MEMORY_CONFIG],
        [ttnn.DRAM_MEMORY_CONFIG],
        3121221,
        11,
    ),
    (
        [(6, 6, 224, 256)],
        [ttnn.int32],
        [ttnn.TILE_LAYOUT],
        [ttnn.DRAM_MEMORY_CONFIG],
        [ttnn.DRAM_MEMORY_CONFIG],
        10286194,
        23,
    ),
    (
        [(6, 10, 256, 256)],
        [ttnn.int32],
        [ttnn.TILE_LAYOUT],
        [ttnn.L1_MEMORY_CONFIG],
        [ttnn.L1_MEMORY_CONFIG],
        10286194,
        30,
    ),
]

@pytest.mark.parametrize(
    "input_shape, dtype, dlayout, in_mem_config, output_mem_config, data_seed, shift_bits",
    (test_sweep_args),
)
def test_bitwise_left_shift(input_shape, dtype, dlayout, in_mem_config, output_mem_config, data_seed, shift_bits, device):
    run_bitwise_left_shift_tests(input_shape, dtype, dlayout, in_mem_config, output_mem_config, data_seed, shift_bits, device)

Run the test using the command:

pytest path/to/test_bitwise_left_shift.py

Expected behavior
All four test cases should fail with an assertion error.

Issue is with shift operator : #15514

Updated fix here : https://github.com/tenstorrent/tt-metal/pull/15538
Shift operator issue is tracked in #15514


Dual license?

The standard approach in the Rust ecosystem is to dual license
See https://rust-lang.github.io/api-guidelines/necessities.html#c-permissive
Doing so would make it easier to become a more semi-official clap project (even move into the clap org if you want).  If interested, the earlier the done, the easier this is.

Thank you for telling me!


feat(tabbar): use index instead of functions fixes #46

This will add index property for the tabbar. We will only render the new pages and keep the old ones, otherwise this may cause flickering.
@argelius your opinion would be appreciated. I think we might also update the tutorials/docs.

Thanks @philolo1 !


Missing Amcrest motion_detection service

Home Assistant release with the issue:

0.93.1
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Raspbian Stretch on a Pi3B
Amcrest IP2M-841B camera
Component/platform:

https://www.home-assistant.io/components/amcrest/
Description of problem:
Switches are being replaced with services per https://github.com/home-assistant/home-assistant/pull/22949, but there doesn't seem to be a service available for directly enabling/disabling the camera's motion detection feature like the switch did.
Should there be a service like amcrest.enable_motion_detection and amcrest.disable_motion_detection?
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
amcrest:
  - host: <IP_ADDRESS>
    username: !secret amcrest_username
    password: !secret amcrest_password

Traceback (if applicable):

Additional information:

Fair point. Is this something you use? I can work on adding it. I don't plan to remove the deprecated features anytime soon.

I remember now why there aren't amcrest.enable_motion_detection and amcrest.disable_motion_detection services. That's because there already are  camera.enable_motion_detection and camera.disable_motion_detection services (which the amcrest integration supports) to do the job.

Ooooh, great to know!  I'll use those.  Might be worth adding to the docs on the component page too.  Thanks @pnbruckner!

Might be worth adding to the docs on the component page too.

Generally for a component, all services should be in that domain. So, for cameras, they should all be camera.xxx. In the old days, before the Great Migration and the introduction of the integration concept, if a platform wanted to add non-standard services, they would be domain.platform_xxx, so e.g., camera.amcrest_enable_recording. In fact, that's how my custom version of the amcrest component used to work. But now if an "integration" wants to add services, they need to be integration.xxx, like amcrest.enable_recording, which, of course, is no longer obvious what component it works with.
I guess I could have tried to add all the new services I was adding to the camera component (e.g., camera.enable_recording), but I wasn't willing to fight that battle. And none of the reviewers suggested it either. So now the amcrest camera related services are split between the camera domain and the amcrest domain, and hence the documentation for them is also split between doc pages. 🤷♂
I guess the moral of the story is, if you want to know what services are available for an entity, you need to look at its component doc page, and possibly also its platform/integration doc page.
At least, that's the best I can figure it out.


Fix incorrect information about SCIM

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

I checked the results in staging and looks right.
There's only one thing I'd change, but I'm not sure whether it worth it. I've added "If SAML SSO is configured on organisation" languages as I can see that the same data/reusables/saml/about-linked-identities.md templated is used in both org and enterprise account related articles. Ideally we should have two separate templates, but I suspect it'll require a review of all documentation and updating it with either one or another.

@andrekolodochka
Thanks so much for opening a PR! I'll get this triaged for review :zap:


Opening of Ports

Greetings all,
Theses are all the ports that are requested be open for the different service. Please ensure that the ports that you need for either your service and/or application is captured in this list

TCP 22
TCP 80
TCP 443
TCP 3000
TCP 8080
TCP 9090
TCP 9100
UDP 9993
UDP 123
UDP 323

All fine for monitoring.

TCP 22 (SSH)
TCP 80 (not used)
TCP 443 (not used)
TCP 3000 (Grafana)
TCP 8080 (Auxiliary)
TCP 9090 (Node Exporter)
TCP 9100 (Prometheus)
UDP 9993 (WireGuard(
UDP 123 (Inbound NTP - Should not be necessary)
UDP 323 (Inbound Chrony - Should not be necessary)

Final ports list for scc2024_sg
TCP 22 (SSH)
TCP 3000 (Grafana)
TCP 8080 (Auxiliary)
TCP 9090 (Node Exporter)
TCP 9100 (Prometheus)
UDP 9993 (WireGuard)

Please test


CANONICAL_REJECTED

I got following entries in log:
INFO -          DOCUMENT_FETCHED: http://www.site.com/data-policy
INFO -        REJECTED_CANONICAL: http://www.site.com/data-policy
INFO -           REJECTED_IMPORT: http://www.site.com/data-policy

Tell me please why is it rejected, is there appeared a new default configuration entry? Migrated from 2.0.1 to 2.2.0 Snapshot.

This is a new feature introduced in 2.2.0 (from feature request #79) to help reduce crawling duplicate content.  You can read more about it here.  The URL http://www.site.com/data-policy is rejected because in its HTML content, you have this:
<link rel="canonical" href="http://www.salesforce.com/platform/overview/"/>

The authors of that page are telling browsers the authoritative version is http://www.salesforce.com/platform/overview/ and consequently that page should be crawled instead.
This means that canonical page will get crawled instead, unless you have filtering rules forcing to stay on the www.site.com domain.
You can disable this new feature by adding this tag to your crawler:
<canonicalLinkDetector ignore="true" />

Thanks a lot, this feature looks very helpful.

That feature is now officially released.

Hi,
Sorry to reopen an old issue.
In my config file, I have:
  <startURLs stayOnDomain="true" stayOnPort="true" stayOnProtocol="true">
        <url>https://www.researchgate.net/publication/261340078_Introduction_of_sustainable_development_in_engineers%27_curricula_Problematic_and_evaluation_methods</url>
...

When I run the crawler, I get:
ResearchGate: 2016-11-28 15:50:31 INFO - ResearchGate: Crawling references...
ResearchGate: 2016-11-28 15:50:33 INFO -          DOCUMENT_FETCHED: https://www.researchgate.net/publication/261340078_Introduction_of_sustainable_development_in_engineers%27_curricula_Problematic_and_evaluation_methods
ResearchGate: 2016-11-28 15:50:33 INFO -        REJECTED_CANONICAL: https://www.researchgate.net/publication/261340078_Introduction_of_sustainable_development_in_engineers%27_curricula_Problematic_and_evaluation_methods
ResearchGate: 2016-11-28 15:50:42 INFO - ResearchGate: 100% completed (2 processed/2 total)
ResearchGate: 2016-11-28 15:50:42 INFO - ResearchGate: Reprocessing any cached/orphan references...
ResearchGate: 2016-11-28 15:50:42 INFO - ResearchGate: Crawler finishing: committing documents.
ResearchGate: 2016-11-28 15:50:42 INFO - ResearchGate: 2 reference(s) processed.
ResearchGate: 2016-11-28 15:50:42 INFO -          CRAWLER_FINISHED

When I have a look inside the website page code, I see:
 <link rel="canonical" href="https://www.researchgate.net/publication/281917092_Empreinte_ecologique_Comparer_la_demande_et_l'offre_de_ressources_regeneratives_de_la_biosphere" />
This is exactly the start URL, but not encoded (' instead of %27).
Not sure if its a bug in the canonicalLinkDetector (which does not detect that links are the same) or it is in the website that forgot to encode the URL...

It is both.  First there was indeed a bug with the GenericCanonicalLinkDetector.  It was truncating URLs with single quotes in them, thinking the single quote was the closing delimiter for the URL string.   This is now fixed in the latest snapshot release.
Second, the single quote is a reserved characters (sub-delimiter) for URLs as per RFC 3986.  This means if you are keeping the default normalization rules, the rule encodeNonURICharacters has no effect on the quote and it is not escaped (rightfully so).  If the quote is not meant as a delimiter, it should always be encoded on the site.  You can get around this problem by forcing escaping of the single quote, like this:
      <urlNormalizer class="com.norconex.collector.http.url.impl.GenericURLNormalizer">
        <normalizations>
            removeFragment, lowerCaseSchemeHost, upperCaseEscapeSequence,
            decodeUnreservedCharacters, removeDefaultPort,
            encodeNonURICharacters
        </normalizations>
        <replacements>
          <replace>
             <match>'</match>
             <replacement>%27</replacement>
          </replace>
        </replacements>
      </urlNormalizer>

Without that suggested normalization replacement, it will work with the fix, but the non-encoded canonical version will be followed instead of the encoded version.  Depends which one you want.  Please confirm.

Fix is now in 2.6.1.


docker run simply hangs in this step char device redirected to /dev/pts/1 (label charserial0)

Firstly, thanks for this wonderful tool :)
When i run my qcow2 image on centos7 using this command
[root@localhost test]# docker run --name kvm --rm -it --privileged -v /var/test/myimage.qcow2:/image/image -e AUTO_ATTACH=yes -e DEBUG=y bbvainnotech/kvm:latest /bin/sh
The command simply hangs at this point
INFO: Launching qemu-kvm
DEBUG: Launching /usr/libexec/qemu-kvm -drive if=virtio,file=/image/image   -nodefaults   -device virtio-balloon-pci,id=balloon0   -realtime mlock=off   -msg timestamp=on   -chardev pty,id=charserial0   -device isa-serial,chardev=charserial0,id=serial0   -serial stdio    -enable-kvm -machine accel=kvm,usb=off  -vga qxl -display none -m 1024 -smp 4,sockets=4,cores=1,threads=1  /bin/sh  -device virtio-net-pci,netdev=net0,mac=02:42:ac:11:00:02  -netdev tap,id=net0,vhost=on,fd=3 3<>/dev/macvtap1c06f8
char device redirected to /dev/pts/1 (label charserial0)
Is there anything i need to set in my host to have this working?

Hi!

Firstly, thanks for this wonderful tool :)
Glad that you like it!

First, I see you are passing /bin/sh as an argument to docker run ....  If you want to debug the container, pass bash instead.  It is explained here, but the example code is missing the bash keyword at the end.  Ooops.
If you want to use the VM, take into account that the VM's will be accessible only via network.  You must ensure that the VM launches a dhcp client and spawns an ssh server, for instance.
(Correct me if I'm wrong, @methadata).
If all the requirements I mentioned are met, you should be able to reach your VM with a simple ssh<EMAIL_ADDRESS>or whatever IP is assigned by the dnsmasq server that is launched.  That info should be apparent in the logs.
Hope that it helps!

Closing.  @csudharsan, feel free to reopen if you require more clarifications.


approved Skype bot not working because of channel registration problem

Hi, my bot was approved and running fine but I needed to recreate it keeping the same AppID.
The channels for Telegram and Facebook Messenger and Webchat are running normally but when I try to edit the Skype channel I receive the error below that don´t allow me to go ahead. I can´t save nor delete Skype channel configuration.
It was in https://join.skype.com/bot/364ac194-60b8-4959-88ba-6cef784e924b and its name is ZapPrices.
The bot is not working and logs this error: "There was a problem synchronizing your bot to Skype."
Exception: ApsException Create failed. ApsException: Create failed. HttpException: Aps call failed - message: NA reasonPhrase: Conflict request content: {"Description":{"displayName":"ZapPrices BR","description":"Comparador de preços entre diversas lojas. Basta enviar o nome do produto ou o código de barras.","agentId":"364ac194-60b8-4959-88ba-6cef784e924b","developer":"Corporator Servicos de Informatica Ltda","extra":null,"userTileSmallUrl":"https://bot-framework.azureedge.net/bot-icons-v1/botzapprices4_8yBDekFko2GV8GzF735cm4UJ7j74ZnAyn38931XE101Uw2yy.png","userTileMediumUrl":"https://bot-framework.azureedge.net/bot-icons-v1/botzapprices4_8yBDekFko2GV8GzF735cm4UJ7j74ZnAyn38931XE101Uw2yy.png","userTileLargeUrl":"https://bot-framework.azureedge.net/bot-icons-v1/botzapprices4_8yBDekFko2GV8GzF735cm4UJ7j74ZnAyn38931XE101Uw2yy.png","userTileExtraLargeUrl":"https://bot-framework.azureedge.net/bot-icons-v1/botzapprices4_8yBDekFko2GV8GzF735cm4UJ7j74ZnAyn38931XE101Uw2yy.png","userTileStaticUrl":"https://bot-framework.azureedge.net/bot-icons-v1/botzapprices4_8yBDekFko2GV8GzF735cm4UJ7j74ZnAyn38931XE101Uw2yy.png","webpage":"http://botzapprices4.azurewebsites.net/","tos":"http://zapprices.com.br/termodeusozap.html","privacyStatement":"http://zapprices.com.br/politicadeprivacidadezap.html","isTrusted":false,"capabilities":["im.send","im.receive","file.send","moji.send","photo.send"],"disclosures":null,"supportedLocales":[],"agentType":"Participant","starRating":0.0,"categories":null,"keywords":null,"etag":null},"PublishState":"Preview","Disabled":false,"MsaAppId":"364ac194-60b8-4959-88ba-6cef784e924b","BotHandle":"botzapprices4","AppInsightsInstrumentationKey":"00000000-0000-0000-0000-000000000000","Cid":0,"Updated":"0001-01-01T00:00:00","DeveloperId":"deprecated","MessagingApiVersion":"3","MessagesUrl":"https://botzapprices4.azurewebsites.net/api/messages","AugmentedChatMode":false,"Channels":["skype"],"Hashtags":"skypedirect"} , at SkypeAps.ApsAdapter.d__24`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at SkypeAps.ApsAdapter.d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Intercom.Channels.Controllers.Skype.ApsAgentManager.d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Intercom.Channels.Controllers.Skype.SkypeHelper.d__3.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Intercom.Channels.Controllers.SkypeController.d__1.MoveNext()

Hi, I have recreated everything with differente bot handle and appId: https://join.skype.com/bot/ac573e18-18eb-48e7-856a-51ddeb3b6185 . Please review it as soon as possible.

Hi, the bot with the new AppId is already published. Please remove the old one 364ac194-60b8-4959-88ba-6cef784e924b� from the Skype bots directory.

There are two icons of ZapPrices bots in Android add bot screen as shown below.
Please remove the one that is not working anymore (364ac194-60b8-4959-88ba-6cef784e924b).

Hi, please add back the ZapPrices bot with AppId ac573e18-18eb-48e7-856a-51ddeb3b6185 to the Skype bots Directory. I asked to delete only the old one (364ac194-60b8-4959-88ba-6cef784e924b).


Separate installing and updating bindings

To pull the submodule using the fixed commit we only need this command:
git pull --recurse-submodules

If we update the submodule, in order to fetch the newest changes (new commits from the target branch) and point the fixed commit to them, we should do:
git submodule update --remote --recursive --init

For now, both commands are used in the install_cairo_bindings.sh script.
We should separate the process of just installing the bindings from updating the binding repository fixed commit.

Related https://github.com/software-mansion/protostar/pull/1555


Having SSHOperator?

I'd like to kick scripts at remote boxes via ssh. I know I can use ssh command via BashOperator. However current (master) airflow have the SSHHook. I think it is better that using existing eco system.
If it is acceptable, I'll submit code  (WIP).

I like it but I would like to see some tests added and maybe a rename to SSHExecuteOperator?

@bolkedebruin OK. I'm planning to write tests too. Then where can I put them? It seems there are no test directories for contrib packages.
Re renaming:  I see. I'll change the name.


Best fitting hit incorrect

Hi,
I used classificaiton for COI and then ran the program to find the best fitting hit both with the JAMP and the BOLDigger method. I found a case where both BOLDigger and the JAMP method choose a hit even though another publicly available hit with better taxonomic classification and similarity was found.
Please check the entry for ASV308 in the attached file. BOLDigger and JAMP choose a published hit with a classification to class level and a similarity of 95.12. However, in the sheet showing the 20 best hits, there are several published hits with higher similarity and better classification. The top hit has a similarity of >97% and classification down to species level (although given the similarity value, only genus level callsification should be trusted, obviously).
BOLDResults_COI_cluster_reps_curated_no_contam.xlsx
A bug?
Cheers
Nauras

I'm on it.
best Dominik

Thanks Dominik. I have curated some of the entries manually now. Looking forward to using the improved algorithm in the future ;-)
Thanks again for this great tool.

Command-line is also updated now including the API correction.


Reactive kafka commit retry has no backoff

Affects Version(s): <2.3.1>

I am not sure whether here is the right place to issue the bug of reactive kafka.
When kafka client commits failed, client will retry immediately after the failed commit request (Kafka broker is temporally unavailable). And after 100 times retry within 10 ms, the comsumer flux is terminated, the consumer will not poll new messages anymore.
Retry should have backoff, instead of retrying immediately. By checking the log, the consumer thread retried to commit 100 times within 10ms. This time is not enough for Kafka client failover in a clustered environment.

I see you already opened this in the right place.
https://github.com/reactor/reactor-kafka/issues/127


InvoiceItem model has two fields named quantity

I'm not that familiar with Stripe's API, but I believe the one that should remain is the IntegerField and not the PositiveIntegerField ... Am I correct in assuming this?

You're right, django takes the last one listed top to bottom. Looking at the migrations you can also see PositiveIntergerField has never been used

That's good to know ! Thank you!

Thanks for catching this.  We'll remove the extra one.


Update remix-dev dependency, attempt to fix integration tests

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[x] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

The remix-dev dependency was outdated and reflecting a security issue. Not a real issue as its only used in tests, but figured we may as well upgrade anyway. Tried to fix integration tests as well as they do not currently run due to a commented out line.

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Set map->odom transform timestamp to ros::Time::now() to prevent wait issue

As briefly mentioned in #47, not updating the timestamp of the map->odom transform published at fixed rate results in components always waiting till a new SLAM pose estimate is produced. For robots performing online mapping and navigation this clearly can be undesirable (at least when using tools such as ROS navigation or rviz).
To demonstrate, here is a video of running the demo bag file from https://github.com/tu-darmstadt-ros-pkg/cartographer_hector_tracker before the change:

As visible, the robot "jumps" every few seconds as only at these snapshots valid transform data to the world frame is available.
After the change in this PR the robot moves smoothly:

Putting this out here for discussion, perhaps how things are stamped should be configurable.

You could argue that this is a sort of extrapolation where our motion model is "we're standing still." We have an underlying motion model we could be exposing instead that should give better results. Perhaps this is a reasonable first step though? @wohe thoughts?

In principle two approaches make some sense:

Publishing the transform only when a new estimate is generated (as was the case prior to the changes of #47)
Publishing with a fixed rate, updating the transform timestamp so ROS tools do not wait as proposed in this PR.

Current master mixes both, it publishes at fixed rate but with fixed timestamp. As far as tf is concerned republishing same transform with same timestamp repeatedly has no effect, so resulting behavior is the same as just publishing the transform once when a new estimate is generated.
With the changes in this PR, the robot effectively moves according to odometry between SLAM pose estimate updates, which is about the most practical thing one can do barring other information. One could certainly argue that handling odometry, (short term) SLAM pose estimates and graph optimized pose estimates in the ROS world could be improved though :)

With the changes in this PR, the robot effectively moves according to odometry between SLAM pose estimate updates ...

That's only because you're providing your own odom frame. In the case where that's not happening, the robot would be standing still. I think we can extrapolate internally better by combining other sensor data (e.g. odometry and IMU) along with our constant velocity model. We just need to expose the internal pose estimate, used to initialize scan matches, between scan matches.


[Task] Support monitoring of Apache Hbase Master nodes

Description
Support monitoring of Apache Hbase Master nodes
Recommended monitoring Metrics:
Task List

[ ]  Number of abnormal RegionServers
[ ]  Number of active RegionServers
[ ] Average cluster load
[ ] Number of cluster requests
[ ] Count of Regions in transition
[ ] Number of Regions with transition time exceeding the threshold
[ ] Oldest RIT time
[ ] Number of cluster load balancing occurrences
[ ] Count of RPC handles

I can do it. Thank you for assigning it to me. Thank you


Added Hamburger Menu for Small Screen Devices

Description
Added Hamburger menu For small screen devices.
Checklist
✔I am making a proper pull request, not spam.
✔ I've checked the issue list before deciding what to submit.
Related Issues or Pull Requests
Improve navbar UI for small screens #194
https://github.com/wasimreja/book-finder/issues/194
Add relevant screenshot or video (if any)

great work!


Fix a typo in a comment

Change the comment on H2C from "over TLS" to "cleartext".

Thank you @minwoox !


build: Update runtime image, add a guard rail

This was missed out from aa796a2c282e. A check is added
to ensure this doesn't happen again.
Fixes: aa796a2c282e (build: Fix shellcheck linter)

Coverage increased (+0.005%) to 36.942% when pulling 21eefe63d5bc6b95f32f93f407d76f395d64b665 on pr/errordeveloper/update-runtime-image into f4ea3f67145eb5c8c6d14a6087058577e9885322 on master.


Adding Lincoln collaboration projects to SuperCloud description

Jeremy requested adding these Lincoln collaboration projects to the SuperCloud description on orcd.mit.edu, reflecting those changes here as well.

Preview: https://mit-orcd.github.io/orcd-docs-previews/PR/PR45/


Persistent BottomSheet difficult to close using TalkBack

When using TalkBack, the user is instructed to swipe to dismiss the persistent BottomSheet. The swipe must occur within the BottomSheet in order to dismiss it. For users who can't see the screen, figuring out where to swipe could potentially be frustrating.

@michdud is this on a recent version of the gallery? There should be an "actions: dismiss" callout after the label is read, then you can open up the local context menu - swipe up and then to the right by default - to close it


Request: option to only highlight code more than X lines away

Having highlights a line or two before or after the cursor is usually more distracting than helpful.
Could the option to disable highlighting of the current line be extended with a "range" config, to set how far away a highlight needs to be from the cursor to show?

great idea, sorry about the delay!


Add format compatible with COMEBin

We would like to combine fairy with COMEBin which naturally supports bam files. Do you think Bam could be supported ?

@paulzierep this is fundamentally not possible, unfortunately. This is because fairy does not do an alignment, which is why it's so fast.


docs: Move Files and update TOC

Files Deleted

/docs/brief-install-vagrant-dev.md

Files Moved

/docs/code-of-conduct.md -> /docs/contributing/code-of-conduct.md
/docs/migration-renumbering.md -> /docs/subsystems/migration-renumbering.md
/docs/users.md -> /docs/subsystems/users.md

TOC Update

/docs/contributing/index.rst
/docs/production/index.rst
/docs/subsystems/index.rst

Fixes #7417  First Two Parts

@timabbott  Kindly Review it.

@Balaji2198 thanks for working on this!  A few requests:

I suspect this will break some links.  You can check for this with git grep input-pills and ./tools/test-documentation (do both for each article you rename, since test-documentation only checks links in the docs/ files, but we might have some from code as well).
Can you do this as a series of smaller commits that each delete/move one article?  That's a lot easier to review.  Check out our GitHub guide and search for "rebase" for advice on how to do this as rebase.  Our commit guidelines are also helpful reading.

@timabbott  I rebased the commit and separated the commits one per file.
And did a git grep, Fixed the links shown.
Also added the title of users.md. (Because To include in TOC).
Your thoughts on it? Don't know why Travis Fails.

The test failures are because you didn't move everything (e.g. the backend / linter failures are because a linter exclude rule didn't get updated)
(zulip-py3-venv) tabbott@zaset:~/zulip$ git grep migration-renumbering
docs/subsystems/index.rst:   migration-renumbering
docs/subsystems/schema-migrations.md:  manually. There is a tutorial [here](migration-renumbering.html) that
tools/linter_lib/custom_check.py:            "docs/migration-renumbering.md",

How are you testing this?  When I ran tools/build-docs, I got this error:
/home/tabbott/zulip/docs/contributing/code-of-conduct.rst: WARNING: document not readable. Ignored.

which was because you needed to update the code-of-conduct.md symlink after moving it.

Since I think it'll help you learn, I ended up cleaning up most of these commits and merging them.  @Balaji2198 can you look at the 5 commits ending with 489feaf13936092436d0736a2ff800643a0eec5b.  Notice how we do changes atomically together, and explain why each change is correct or desirable in the commit message.

Thanks for your work on this @Balaji2198!

@timabbott  Now I understood. Thanks. :+1:


Adjust Sockets test ports s.t. APM and Async tests do not collide.

@CIPop @davidsh @stephentoub PTAL. In my private testing (e.g. http://dotnet-ci.cloudapp.net/job/dotnet_corefx_linux_debug_tst_prtest/2614/), there have been problems with ports colliding when the APM and async tests run in parallel.

Other than the comment I've made on previous PRs about using dynamically generated port numbers instead (:wink:), LGTM.

LGTM


iam getting the error when i do subscribe my azure account

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az login
Errors:
Paste here the error message you have received. Make sure to remove all sensitive information,
such as user name, password, credential, subscription ID, etc.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az login

Expected Behavior
Environment Summary
Windows-10-10.0.19044-SP0
Python 3.10.10
Installer: MSI

azure-cli 2.47.0

Additional Context

Thank you for opening this issue, we will look into it.

az
Traceback (most recent call last):
File "runpy.py", line 196, in _run_module_as_main
File "runpy.py", line 86, in _run_code
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/main.py", line 14, in
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/telemetry.py", line 19, in
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/telemetry/init.py", line 9, in
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\portalocker/init.py", line 4, in
File "D:\a_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\portalocker/portalocker.py", line 11, in
ImportError: DLL load failed while importing win32file: The specified procedure could not be found.


Support pipeline model

Enhancement
tiflash support pipeline model
todo list

[x] public desgin doc

https://github.com/pingcap/tiflash/pull/7612

[x] pre-refactor

https://github.com/pingcap/tiflash/issues/5900

[ ] pipeline model

[x] support task scheduler and push model operator

[x] support task scheduler and simple operator(limit, projection, filter, mock(_scan/exchange_sender/receiver))

https://github.com/pingcap/tiflash/pull/6520

[x] support complex operator

[x] aggregate

https://github.com/pingcap/tiflash/pull/6855
https://github.com/pingcap/tiflash/pull/7089
https://github.com/pingcap/tiflash/pull/7220
https://github.com/pingcap/tiflash/pull/7318

[x] join

https://github.com/pingcap/tiflash/pull/7333
https://github.com/pingcap/tiflash/pull/7833

[x] sort/window

https://github.com/pingcap/tiflash/pull/6963
https://github.com/pingcap/tiflash/pull/7492

[x] topn

https://github.com/pingcap/tiflash/pull/6805
https://github.com/pingcap/tiflash/pull/7216

[x] support fine grained shuffle

https://github.com/pingcap/tiflash/pull/6934

[x] support io executor

https://github.com/pingcap/tiflash/pull/7195

[x] support exchange / scan async io

[x] async table scan

https://github.com/pingcap/tiflash/pull/6831
https://github.com/pingcap/tiflash/pull/7225
https://github.com/pingcap/tiflash/pull/7474
https://github.com/pingcap/tiflash/pull/7480
https://github.com/pingcap/tiflash/pull/7552
https://github.com/pingcap/tiflash/pull/7723

[x] async exchange sender/receiver

https://github.com/pingcap/tiflash/pull/6835
https://github.com/pingcap/tiflash/pull/6854

[ ] task schedule

[x] Multi-level feedback queue

https://github.com/pingcap/tiflash/pull/7393

[x] io_priority_queue

https://github.com/pingcap/tiflash/pull/7722

[ ] resource group

https://github.com/pingcap/tiflash/issues/7660

[x] other

[x] support explain analyze/mpp tracing

https://github.com/pingcap/tiflash/pull/6995
https://github.com/pingcap/tiflash/pull/7562

[x] improve log

https://github.com/pingcap/tiflash/pull/6921

[x] improve metrics

https://github.com/pingcap/tiflash/pull/7117
https://github.com/pingcap/tiflash/pull/7584

[x] failpoint

https://github.com/pingcap/tiflash/pull/6923

[x] refine assert

https://github.com/pingcap/tiflash/pull/7343

Only resource control is left, which is tracked in other issues