can't install flash attention pre-compiled wheels because of a version mismatch

The following command works with pip directly, but not with uv pip. There are a couple other flash attention issues in the tracker but all of them seem to be building it, not installing a pre-built version. Any idea what might be causing this?
$ uv pip install --verbose https://github.com/Dao-AILab/flash-attention/releases/download/v2.5.8/
flash_attn-2.5.8+cu122torch2.3cxx11abiFALSE-cp310-cp310-linux_x86_64.wh

version=uv 0.1.44

Verbose logs
  ```
INFO Found a virtualenv through VIRTUAL_ENV at: /home/user/.venv
DEBUG Cached interpreter info for Python 3.10.12, skipping probing: .venv/bin/python
DEBUG Using Python 3.10.12 environment at .venv/bin/python
DEBUG Trying to lock if free: .venv/.lock
DEBUG At least one requirement is not satisfied: https://github.com/Dao-AILab/flash-attention/releases/download/v2.5.8/flash_attn-2.5.8+cu122torch2.3cxx11abiFALSE-cp310-cp310-linux_x86_64.whl
DEBUG Using registry request timeout of 30s
DEBUG Found fresh response for: https://github.com/Dao-AILab/flash-attention/releases/download/v2.5.8/flash_attn-2.5.8+cu122torch2.3cxx11abiFALSE-cp310-cp310-linux_x86_64.whl
DEBUG Solving with target Python version 3.10.12
DEBUG Adding direct dependency: flash-attn*
DEBUG Searching for a compatible version of flash-attn @ https://github.com/Dao-AILab/flash-attention/releases/download/v2.5.8/flash_attn-2.5.8+cu122torch2.3cxx11abiFALSE-cp310-cp310-linux_x86_64.whl (*)
DEBUG Adding transitive dependency for flash-attn==2.5.8: torch*
DEBUG Adding transitive dependency for flash-attn==2.5.8: einops*
DEBUG Adding transitive dependency for flash-attn==2.5.8: packaging*
DEBUG Adding transitive dependency for flash-attn==2.5.8: ninja*
DEBUG Found fresh response for: https://pypi.org/simple/torch/
DEBUG Found fresh response for: https://pypi.org/simple/einops/
DEBUG Found fresh response for: https://pypi.org/simple/packaging/
DEBUG Found installed version of torch==2.3.0 that satisfies preference in *
DEBUG Found installed version of einops==0.8.0 that satisfies preference in *
DEBUG Found fresh response for: https://pypi.org/simple/ninja/
DEBUG Found installed version of packaging==24.0 that satisfies preference in *
DEBUG Found installed version of ninja==<IP_ADDRESS> that satisfies preference in *
DEBUG Searching for a compatible version of torch (*)
DEBUG Found installed version of torch==2.3.0 that satisfies preference in *
DEBUG Selecting: torch==2.3.0 (installed)
DEBUG Adding transitive dependency for torch==2.3.0: filelock*
DEBUG Adding transitive dependency for torch==2.3.0: typing-extensions>=4.8.0
DEBUG Adding transitive dependency for torch==2.3.0: sympy*
DEBUG Adding transitive dependency for torch==2.3.0: networkx*
DEBUG Adding transitive dependency for torch==2.3.0: jinja2*
DEBUG Adding transitive dependency for torch==2.3.0: fsspec*
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-cuda-nvrtc-cu12==12.1.105
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-cuda-runtime-cu12==12.1.105
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-cuda-cupti-cu12==12.1.105
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-cudnn-cu12==<IP_ADDRESS>
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-cublas-cu12==<IP_ADDRESS>
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-cufft-cu12==<IP_ADDRESS>
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-curand-cu12==<IP_ADDRESS>
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-cusolver-cu12==<IP_ADDRESS>
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-cusparse-cu12==<IP_ADDRESS>
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-nccl-cu12==2.20.5
DEBUG Adding transitive dependency for torch==2.3.0: nvidia-nvtx-cu12==12.1.105
DEBUG Adding transitive dependency for torch==2.3.0: triton==2.3.0
DEBUG Found fresh response for: https://pypi.org/simple/typing-extensions/
DEBUG Found fresh response for: https://pypi.org/simple/filelock/
DEBUG Found fresh response for: https://pypi.org/simple/sympy/
DEBUG Found fresh response for: https://pypi.org/simple/networkx/
DEBUG Found fresh response for: https://pypi.org/simple/jinja2/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cuda-nvrtc-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/fsspec/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cuda-runtime-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cudnn-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cublas-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cufft-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cusolver-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cusparse-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-nccl-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-nvtx-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-cuda-cupti-cu12/
DEBUG Found installed version of typing-extensions==4.11.0 that satisfies preference in >=4.8.0
DEBUG Found fresh response for: https://pypi.org/simple/triton/
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-curand-cu12/
DEBUG Found installed version of filelock==3.14.0 that satisfies preference in *
DEBUG Found installed version of sympy==1.12 that satisfies preference in *
DEBUG Found installed version of networkx==3.3 that satisfies preference in *
DEBUG Found installed version of jinja2==3.1.4 that satisfies preference in *
DEBUG Found installed version of nvidia-cuda-nvrtc-cu12==12.1.105 that satisfies preference in ==12.1.105
DEBUG Found installed version of fsspec==2024.3.1 that satisfies preference in *
DEBUG Found installed version of nvidia-cuda-runtime-cu12==12.1.105 that satisfies preference in ==12.1.105
DEBUG Found installed version of nvidia-cudnn-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Found installed version of nvidia-cublas-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Found installed version of nvidia-cufft-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Found installed version of nvidia-cusolver-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Found installed version of nvidia-cusparse-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Found installed version of nvidia-nccl-cu12==2.20.5 that satisfies preference in ==2.20.5
DEBUG Found installed version of nvidia-nvtx-cu12==12.1.105 that satisfies preference in ==12.1.105
DEBUG Found installed version of nvidia-cuda-cupti-cu12==12.1.105 that satisfies preference in ==12.1.105
DEBUG Found installed version of triton==2.3.0 that satisfies preference in ==2.3.0
DEBUG Found installed version of nvidia-curand-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Searching for a compatible version of nvidia-cuda-nvrtc-cu12 (==12.1.105)
DEBUG Found installed version of nvidia-cuda-nvrtc-cu12==12.1.105 that satisfies preference in ==12.1.105
DEBUG Selecting: nvidia-cuda-nvrtc-cu12==12.1.105 (installed)
DEBUG Searching for a compatible version of nvidia-cuda-runtime-cu12 (==12.1.105)
DEBUG Found installed version of nvidia-cuda-runtime-cu12==12.1.105 that satisfies preference in ==12.1.105
DEBUG Selecting: nvidia-cuda-runtime-cu12==12.1.105 (installed)
DEBUG Searching for a compatible version of nvidia-cuda-cupti-cu12 (==12.1.105)
DEBUG Found installed version of nvidia-cuda-cupti-cu12==12.1.105 that satisfies preference in ==12.1.105
DEBUG Selecting: nvidia-cuda-cupti-cu12==12.1.105 (installed)
DEBUG Searching for a compatible version of nvidia-cudnn-cu12 (==<IP_ADDRESS>)
DEBUG Found installed version of nvidia-cudnn-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Selecting: nvidia-cudnn-cu12==<IP_ADDRESS> (installed)
DEBUG Adding transitive dependency for nvidia-cudnn-cu12==<IP_ADDRESS>: nvidia-cublas-cu12*
DEBUG Searching for a compatible version of nvidia-cublas-cu12 (==<IP_ADDRESS>)
DEBUG Found installed version of nvidia-cublas-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Selecting: nvidia-cublas-cu12==<IP_ADDRESS> (installed)
DEBUG Searching for a compatible version of nvidia-cufft-cu12 (==<IP_ADDRESS>)
DEBUG Found installed version of nvidia-cufft-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Selecting: nvidia-cufft-cu12==<IP_ADDRESS> (installed)
DEBUG Searching for a compatible version of nvidia-curand-cu12 (==<IP_ADDRESS>)
DEBUG Found installed version of nvidia-curand-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Selecting: nvidia-curand-cu12==<IP_ADDRESS> (installed)
DEBUG Searching for a compatible version of nvidia-cusolver-cu12 (==<IP_ADDRESS>)
DEBUG Found installed version of nvidia-cusolver-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Selecting: nvidia-cusolver-cu12==<IP_ADDRESS> (installed)
DEBUG Adding transitive dependency for nvidia-cusolver-cu12==<IP_ADDRESS>: nvidia-cublas-cu12*
DEBUG Adding transitive dependency for nvidia-cusolver-cu12==<IP_ADDRESS>: nvidia-nvjitlink-cu12*
DEBUG Adding transitive dependency for nvidia-cusolver-cu12==<IP_ADDRESS>: nvidia-cusparse-cu12*
DEBUG Searching for a compatible version of nvidia-cusparse-cu12 (==<IP_ADDRESS>)
DEBUG Found installed version of nvidia-cusparse-cu12==<IP_ADDRESS> that satisfies preference in ==<IP_ADDRESS>
DEBUG Selecting: nvidia-cusparse-cu12==<IP_ADDRESS> (installed)
DEBUG Adding transitive dependency for nvidia-cusparse-cu12==<IP_ADDRESS>: nvidia-nvjitlink-cu12*
DEBUG Searching for a compatible version of nvidia-nccl-cu12 (==2.20.5)
DEBUG Found installed version of nvidia-nccl-cu12==2.20.5 that satisfies preference in ==2.20.5
DEBUG Selecting: nvidia-nccl-cu12==2.20.5 (installed)
DEBUG Searching for a compatible version of nvidia-nvtx-cu12 (==12.1.105)
DEBUG Found installed version of nvidia-nvtx-cu12==12.1.105 that satisfies preference in ==12.1.105
DEBUG Selecting: nvidia-nvtx-cu12==12.1.105 (installed)
DEBUG Searching for a compatible version of triton (==2.3.0)
DEBUG Found installed version of triton==2.3.0 that satisfies preference in ==2.3.0
DEBUG Selecting: triton==2.3.0 (installed)
DEBUG Adding transitive dependency for triton==2.3.0: filelock*
DEBUG Searching for a compatible version of einops (*)
DEBUG Found installed version of einops==0.8.0 that satisfies preference in *
DEBUG Selecting: einops==0.8.0 (installed)
DEBUG Searching for a compatible version of packaging (*)
DEBUG Found installed version of packaging==24.0 that satisfies preference in *
DEBUG Selecting: packaging==24.0 (installed)
DEBUG Searching for a compatible version of ninja (*)
DEBUG Found installed version of ninja==<IP_ADDRESS> that satisfies preference in *
DEBUG Selecting: ninja==<IP_ADDRESS> (installed)
DEBUG Searching for a compatible version of filelock (*)
DEBUG Found installed version of filelock==3.14.0 that satisfies preference in *
DEBUG Selecting: filelock==3.14.0 (installed)
DEBUG Searching for a compatible version of typing-extensions (>=4.8.0)
DEBUG Found installed version of typing-extensions==4.11.0 that satisfies preference in >=4.8.0
DEBUG Selecting: typing-extensions==4.11.0 (installed)
DEBUG Searching for a compatible version of sympy (*)
DEBUG Found installed version of sympy==1.12 that satisfies preference in *
DEBUG Selecting: sympy==1.12 (installed)
DEBUG Adding transitive dependency for sympy==1.12: mpmath>=0.19
DEBUG Searching for a compatible version of networkx (*)
DEBUG Found installed version of networkx==3.3 that satisfies preference in *
DEBUG Selecting: networkx==3.3 (installed)
DEBUG Searching for a compatible version of jinja2 (*)
DEBUG Found installed version of jinja2==3.1.4 that satisfies preference in *
DEBUG Selecting: jinja2==3.1.4 (installed)
DEBUG Adding transitive dependency for jinja2==3.1.4: markupsafe>=2.0
DEBUG Searching for a compatible version of fsspec (*)
DEBUG Found installed version of fsspec==2024.3.1 that satisfies preference in *
DEBUG Selecting: fsspec==2024.3.1 (installed)
DEBUG Found fresh response for: https://pypi.org/simple/nvidia-nvjitlink-cu12/
DEBUG Found fresh response for: https://pypi.org/simple/mpmath/
DEBUG Found installed version of nvidia-nvjitlink-cu12==12.4.127 that satisfies preference in *
DEBUG Found installed version of mpmath==1.3.0 that satisfies preference in >=0.19
DEBUG Searching for a compatible version of nvidia-nvjitlink-cu12 (*)
DEBUG Found installed version of nvidia-nvjitlink-cu12==12.4.127 that satisfies preference in *
DEBUG Selecting: nvidia-nvjitlink-cu12==12.4.127 (installed)
DEBUG Searching for a compatible version of mpmath (>=0.19)
DEBUG Found installed version of mpmath==1.3.0 that satisfies preference in >=0.19
DEBUG Selecting: mpmath==1.3.0 (installed)
DEBUG Found fresh response for: https://pypi.org/simple/markupsafe/
DEBUG Found installed version of markupsafe==2.1.5 that satisfies preference in >=2.0
DEBUG Searching for a compatible version of markupsafe (>=2.0)
DEBUG Found installed version of markupsafe==2.1.5 that satisfies preference in >=2.0
DEBUG Selecting: markupsafe==2.1.5 (installed)
DEBUG Tried 27 versions: einops 1, filelock 1, flash-attn 1, fsspec 1, jinja2 1, markupsafe 1, mpmath 1, networkx 1, ninja 1, nvidia-cublas-cu12 1, nvidia-cuda-cupti-cu12 1, nvidia-cuda-nvrtc-cu12 1, nvidia-cuda-runtime-cu12 1, nvidia-cudnn-cu12 1, nvidia-cufft-cu12 1, nvidia-curand-cu12 1, nvidia-cusolver-cu12 1, nvidia-cusparse-cu12 1, nvidia-nccl-cu12 1, nvidia-nvjitlink-cu12 1, nvidia-nvtx-cu12 1, packaging 1, root 1, sympy 1, torch 1, triton 1, typing-extensions 1
Resolved 26 packages in 8ms
DEBUG Requirement already installed: einops==0.8.0
DEBUG Requirement already installed: filelock==3.14.0
DEBUG URL wheel requirement already cached: flash-attn==2.5.8+cu122torch2.3cxx11abifalse (from https://github.com/Dao-AILab/flash-attention/releases/download/v2.5.8/flash_attn-2.5.8+cu122torch2.3cxx11abiFALSE-cp310-cp310-linux_x86_64.whl)
DEBUG Requirement already installed: fsspec==2024.3.1
DEBUG Requirement already installed: jinja2==3.1.4
DEBUG Requirement already installed: markupsafe==2.1.5
DEBUG Requirement already installed: mpmath==1.3.0
DEBUG Requirement already installed: networkx==3.3
DEBUG Requirement already installed: ninja==<IP_ADDRESS>
DEBUG Requirement already installed: nvidia-cublas-cu12==<IP_ADDRESS>
DEBUG Requirement already installed: nvidia-cuda-cupti-cu12==12.1.105
DEBUG Requirement already installed: nvidia-cuda-nvrtc-cu12==12.1.105
DEBUG Requirement already installed: nvidia-cuda-runtime-cu12==12.1.105
DEBUG Requirement already installed: nvidia-cudnn-cu12==<IP_ADDRESS>
DEBUG Requirement already installed: nvidia-cufft-cu12==<IP_ADDRESS>
DEBUG Requirement already installed: nvidia-curand-cu12==<IP_ADDRESS>
DEBUG Requirement already installed: nvidia-cusolver-cu12==<IP_ADDRESS>
DEBUG Requirement already installed: nvidia-cusparse-cu12==<IP_ADDRESS>
DEBUG Requirement already installed: nvidia-nccl-cu12==2.20.5
DEBUG Requirement already installed: nvidia-nvjitlink-cu12==12.4.127
DEBUG Requirement already installed: nvidia-nvtx-cu12==12.1.105
DEBUG Requirement already installed: packaging==24.0
DEBUG Requirement already installed: sympy==1.12
DEBUG Requirement already installed: torch==2.3.0
DEBUG Requirement already installed: triton==2.3.0
DEBUG Requirement already installed: typing-extensions==4.11.0
DEBUG Unnecessary package: pyyaml==6.0.1
DEBUG Unnecessary package: aiosignal==1.3.1
DEBUG Unnecessary package: argparse==1.4.0
DEBUG Unnecessary package: attrs==23.2.0
DEBUG Unnecessary package: boto3==1.34.105
DEBUG Unnecessary package: botocore==1.34.105
DEBUG Unnecessary package: braceexpand==0.1.7
DEBUG Unnecessary package: certifi==2024.2.2
DEBUG Unnecessary package: charset-normalizer==3.3.2
DEBUG Unnecessary package: click==8.1.7
DEBUG Unnecessary package: frozenlist==1.4.1
DEBUG Unnecessary package: huggingface-hub==0.23.0
DEBUG Unnecessary package: idna==3.7
DEBUG Unnecessary package: jmespath==1.0.1
DEBUG Unnecessary package: jsonschema==4.22.0
DEBUG Unnecessary package: jsonschema-specifications==2023.12.1
DEBUG Unnecessary package: msgpack==1.0.8
DEBUG Unnecessary package: numpy==1.26.4
DEBUG Unnecessary package: pillow==10.3.0
DEBUG Preserving seed package: pip==24.0
DEBUG Unnecessary package: protobuf==5.26.1
DEBUG Unnecessary package: python-dateutil==2.9.0.post0
DEBUG Unnecessary package: ray==2.21.0
DEBUG Unnecessary package: referencing==0.35.1
DEBUG Unnecessary package: regex==2024.5.10
DEBUG Unnecessary package: requests==2.31.0
DEBUG Unnecessary package: rpds-py==0.18.1
DEBUG Unnecessary package: s3transfer==0.10.1
DEBUG Unnecessary package: s5cmd==0.1.0
DEBUG Unnecessary package: safetensors==0.4.3
DEBUG Preserving seed package: setuptools==59.6.0
DEBUG Unnecessary package: six==1.16.0
DEBUG Unnecessary package: tokenizers==0.19.1
DEBUG Unnecessary package: torchvision==0.18.0
DEBUG Unnecessary package: tqdm==4.66.4
DEBUG Unnecessary package: transformers==4.40.2
DEBUG Unnecessary package: urllib3==2.2.1
DEBUG Preserving seed package: uv==0.1.44
DEBUG Unnecessary package: webdataset==0.2.86
DEBUG Preserving seed package: wheel==0.37.1
error: Failed to install: flash_attn-2.5.8+cu122torch2.3cxx11abifalse-cp310-cp310-linux_x86_64.whl (flash-attn==2.5.8+cu122torch2.3cxx11abifalse (from https://github.com/Dao-AILab/flash-attention/releases/download/v2.5.8/flash_attn-2.5.8+cu122torch2.3cxx11abiFALSE-cp310-cp310-linux_x86_64.whl))
  Caused by: Wheel version does not match filename: 2.5.8 != 2.5.8+cu122torch2.3cxx11abifalse
  ```

We might need to ignore local segments in that comparison.

I assume it works if you rename the file to, like, flash_attn-2.5.8-cp310-cp310-linux_x86_64.whl?

wow, you guys fixed it already 🔥


Impersonate http header order fingerprint

Except for http2 fingerprinting, http header orders can be used for fingerprinting as well.
According to Amazon Cloudfront docs:

Amazon CloudFront now supports the “Cloudfront-viewer-header-order” and "Cloudfront-viewer-header-count" headers, enabling customers to track the total number of HTTP headers sent with each request, as well as the order in which the headers were sent. Customers can use the two headers to detect and identify request patterns and compare them to the expected and legitimate patterns. This, used in conjunction with other access control rules, can help customers detect and block any attempts to spoof requests.

Unfortunately, the order of headers is fixed for curl, it does not send headers in the order of being added, and the order can not be changed whatever you like. It was discussed in curl/curl#3282, and has been on the TODO list for a very long time.
As you can see in the curl/lib/http.c:
    Curl_dyn_addf(&req,
                  " HTTP/%s\r\n" /* HTTP version */
                  "%s" /* host */
                  "%s" /* proxyuserpwd */
                  "%s" /* userpwd */
                  "%s" /* range */
                  "%s" /* user agent */
                  "%s" /* accept */
                  "%s" /* TE: */
                  "%s" /* accept-encoding */
                  "%s" /* referer */
                  "%s" /* Proxy-Connection */
                  "%s" /* transfer-encoding */
                  "%s",/* Alt-Used */

It seems unlikely that curl will change this. Could you please consider adding this feature to curl-impersonate? Thanks.

Currently with all the built-in impersonations the headers are sent in the correct order according to my testing. Are you referring to a possible case where the HTTP headers are manually set by the user and in a different order (e.g. Accept-Encoding before User-Agent? Can you share an example where this affects you?

I just checked the header order with a simple echo server, the orders are correct. I was looking at the "source" request headers in Chrome devtools, which is alphabetically ordered, and I was misled by that. Thanks for your explaination and sorry for the bother.

Connection from ('<IP_ADDRESS>', 57396)
GET / HTTP/1.1
Host: localhost:8888
Connection: keep-alive
sec-ch-ua: "Chromium";v="110", "Not A(Brand";v="24", "Google Chrome";v="110"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "macOS"
DNT: 1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Sec-Fetch-Site: none
Sec-Fetch-Mode: navigate
Sec-Fetch-User: ?1
Sec-Fetch-Dest: document
Accept-Encoding: gzip, deflate, br
Accept-Language: en,zh-CN;q=0.9,zh-TW;q=0.8,zh;q=0.7
Cookie: jenkins-timestamper-offset=-28800000

Connection from ('<IP_ADDRESS>', 61000)
GET / HTTP/1.1
Host: localhost:8888
Connection: Upgrade, HTTP2-Settings
Upgrade: h2c
HTTP2-Settings: AAEAAQAAAAIAAAAAAAMAAAPoAAQAYAAAAAYABAAA
sec-ch-ua: "Chromium";v="110", "Not A(Brand";v="24", "Google Chrome";v="110"
sec-ch-ua-mobile: ?0
sec-ch-ua-platform: "Windows"
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Sec-Fetch-Site: none
Sec-Fetch-Mode: navigate
Sec-Fetch-User: ?1
Sec-Fetch-Dest: document
Accept-Encoding: gzip, deflate, br
Accept-Language: en-US,en;q=0.9

Thanks for reporting back @yifeikong, was about to start debugging this issue here as well, to avoid future detection. So I guess we're good.

I was recording some captures today using Wireshark.
I could observe the following behaviour of the normal curl binary:
The order of the specified header fields is respected. It seems that -H 'Host: example.com' is always the first element no matter when it is specified.
curl -XPOST 'http://google.com'  \
  -H 'Host: facebook.com' \
  -H 'Accept: application/json' \
  -H 'User-Agent: yyyy'

indeed produces
POST / HTTP/1.1
Host: facebook.com
Accept: application/json
User-Agent: yyyy

If we switch up Accept and User-Agent this is indeed respected.
curl -XPOST 'http://google.com'  \
  -H 'Host: facebook.com' \
  -H 'User-Agent: yyyy' \
  -H 'Accept: application/json'

produces:
POST / HTTP/1.1
Host: facebook.com
User-Agent: yyyy
Accept: application/json

Interestingly we can specify header fields twice:
curl -XPOST 'http://google.com'  \
  -H 'Host: facebook.com' \
  -H 'User-Agent: yyyy' \
  -H 'Accept: application/json' \
  -H 'User-Agent: xxxx'

POST / HTTP/1.1
Host: facebook.com
User-Agent: yyyy
Accept: application/json
User-Agent: xxxx

Host always first
When we are trying to put the host header field to the last position like so:
curl -XPOST 'http://google.com'  \
  -H 'User-Agent: yyyy' \
  -H 'Accept: application/json' \
  -H 'User-Agent: xxxx' \
  -H 'Host: facebook.com'

it produces the same output as the previous command:
POST / HTTP/1.1
Host: facebook.com
User-Agent: yyyy
Accept: application/json
User-Agent: xxxx

I cannot find any section in the official HTTP RFCs that force you to use it as the first header field, but throughout my career I have never seen something different though.


HHH-15446 - allow Dialect version to be specified separately from the dialect class name

See https://hibernate.atlassian.net/browse/HHH-15446
Signed-off-by: Jan Schatteman<EMAIL_ADDRESS>

Still need to add a test to verify the dialect returned corresponds to what is expected

@beikov It looks a bit different from when we paired, because i didn't want to repeat that stack of nested try-catch in the getMetadataResolutionInfo method we created, when creating the JdbcEnvironment  (HQLTest showed that we need to pass in the dbmd to the JdbcEnvironment when it is allowed, otherwise it fails due to scrollable result sets not being enabled)


update to use new artifact host for artifact

publish failed https://github.com/nrkno/bigquery-scala/actions/runs/11033090579/job/30643663747


feat: improve isNuxtError() type inference

🔗 Linked issue
resolves #28813
📚 Description
This PR will improve the type inference of isNuxtError(), without changing its implementation at all.
The change is a one-liner, very simple, but it offers several advantages:

Wider param type: the runtime code is already resilient to all parameter types, so its type is set to unknown to improve DX and avoid casting.
Always infer type: in this way, the type inference (error is NuxtError<DataT>) will always be applied after being asserted.
Mandatory param: I thought it was good to avoid using isNuxtError() without a param, as it's not particularly meaningful on its own.

Thank you!


fix(spacing): enable 0.5 point in spacing

fix(spacing): enable 0.5 point in spacing

:tada: This PR is included in version 1.40.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Preventing default behavior and event propogation of the a tag

@nodkrot could you resolve the conflicts in your PR and then I'll take a look? I did a recent commit so that may have caused it. Thanks.


Add metadata values to include in the output

This is a guided version of adding metadata.  Specifically, the fields should be specified along with the possible datatypes / values for the fields.

This can be done in the config file.


GPTNeoX: Use static rotary embedding

What does this PR do?
transformers 4.35 removed rotary embeddings from GPTNeoX's weights (link to line diff). This applies the same fix as https://github.com/huggingface/text-generation-inference/pull/793 which generates them on-the-fly using the appropriate value from the config file
Fixes https://github.com/huggingface/text-generation-inference/issues/1460
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[x] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
@OlivierDehaene OR @Narsil

Hi @dwyatte thank you for the contribution, unfortunately this change appears to break the neox tests.
tested locally with:
cd integration-tests/
pytest -s -vv models/test_flash_neox.py

**note you may have to comment out the skip flags for some tests
would you be able to review these changes and ensure they pass the tests. Thank you!!

@drbh thanks for the reply
Any chance there is a guide to developing using TGI's docker image to manage all dependencies when running the integration tests? I've gotten pretty far on compiling everything but it seems like a never ending rabbit hole (on to Flash Attention now and it even recommended using TGI's image)
2024-01-30T00:04:51.061971Z  WARN text_generation_launcher: Could not import Flash Attention enabled models: Flash Attention is not installed.
Use the official Docker image (ghcr.io/huggingface/text-generation-inference:latest) or install flash attention with `cd server && make install install-flash-attention`

I can probably mount my code / integration tests, but I'm probably missing something easy (e.g., just reading through source code, maybe setting the env var DOCKER_IMAGE)

Ok @drbh 871e5e7 fixes the actual rotary embedding logic (thanks for flagging) but I suspect there might still be failures in the local tests due to stale snapshots
Wondering if we should update these as part of the PR

awesome thank you for resolving @dwyatte. I actually think those tests have been flakey for some time now and neox is not a current priority, so we can continue to skip them for now. Overall the PR looks good and has reasonable responses when tested locally but I think we should get a quick second look before approving.
@Narsil what do you think about approving when tests are flakey/skipped?
Thank you both!

Thanks a lot for this contribution.
We' ll take the contribution as-is. It possibly breaks some stuff but overall is more aligned with other modeling code, therefore i' m ok to add it.
Neox non flash is not tested, but this is neox flash


Enable at-least-once delivery for ACK-based input sources via GC callback

Right now, if you want to use ACK-based input sources (e.g. SQS, RabbitMQ), you have to ACK immediately upon message receipt (because otherwise you can never ACK unless you do some very hacky  and input specific things like send the raw message type through the dataflow and ACK on output in a custom connector). This means that those input systems are limited to at-most-once delivery.
A way we could facilitate at-least-once delivery is by adding a StatefulSource.garbage_collect(self, state) callback that is called when an epoch is older than the cluster frontier (meaning all outputs and backups for it have completed) with the snapshot that was taken at the end of that epoch.
Then, a SQS input source could do something like (made up SQS Python API):
class _SQSSource(StatefulSource):
    def __init__(self, queue_name, resume_state):
        self._queue = SQSQueueConsumer(queue_name)
        self._in_flight_msg_ids = resume_state or set()

    def next(self):
        msg = self._queue.poll(0.001)
        if msg is None:
            return
        else:
            self._in_flight_msg_ids.insert(msg.id())
            return msg.payload()

    def snapshot(self):
        return self._in_flight_msg_ids

    def garbage_collect(self, state):
        closed_in_flight_msg_ids = state
        for msg_id in closed_in_flight_msg_ids:
            self._queue.ack(msg_id)
            self._in_flight_msg_ids.remove(msg_id)

    def close(self):
        self._queue.close()

I believe this will work because any messages consumed during an epoch that is "rolled back" during recovery will eventually visibility timeout and be delivered again. This requires some coordination with the SQS visibility timeout value; it'd have to be longer than the epoch interval so that you don't redeliver before GC could even be called.
Returning the snapshot state on GC instead of baking in the concept of message IDs directly is cool because then you can support other input sources that have "dynamic retention". The one that comes to mind is if you wanted to build a Postgres logical replication input. You need to be periodically "ACKing" up to an LSN so the replication slot does not retain changes forever.
Something like (made up Postgres Python API, but inspired by psychopg2's replication API):
class _PGLRSource(StatefulSource):
    def __init__(self, conn, resume_state):
        self._lsn = resume_state
        self._cursor = conn.start_replication(start_lsn=self._lsn)

    def next(self):
        msg = self._cursor.read_message()
        if msg is None:
            return
        else if msg.data_start > self._lsn:  # Skip the msg at the recovery LSN.
            self._lsn = msg.data_start
            return msg.payload

    def snapshot(self):
        return self._lsn

    def garbage_collect(self, state):
        lsn = state
        self._cursor.send_feedback(flush_lsn=lsn)

    def close(self):
        self._queue.close()

This callback might be better called commit? This is effectively a two-phase-commit. Also you could then have an identical API with StatefulSink.commit(self, state) for outputs to get exactly-once output. The same recovery machinery would support both the input and the output functionality.

I'd be interested in participating in the discussion around this.  I'm working on using Bytewax with Memphis.dev.  Like the JMS API, Memphis expects the consumer to acknowledge the message once processed.  For my simple prototype, I do not intend to do aggregations so I was going to pass the message information along the flow so that I can use a dummy output source to acknowledge it after a previous output source writes the transformed message out.  I was also considering if it would be possible to add a hook to the StatelessInputSource or similar that gets called after next().  E.g., next() is called to get the next event and once the flow processes it, the hook (e.g., mark_done()) is called.

E.g. it's possible an input's next is called 3 times in a row, buffering items into internal dataflow queues, but no output was ever emitted. (Although probably you will not practically see this behavior, but Bytewax might change it.)

I didn't realize that.  I thought it worked in lock step.  Yes, I can definitely see that being a problem.
I dug a bit into Memphis.  We have the ability to get the sequence id for each message we receive and set the starting sequencing number when we create consumers.  We can use this to perform Kafka-esque state recovery, so we'll do that.  We still need to acknowledge messages but that's because of some logic on the broker side.


Plugable secret backend

This commit extends SwarmKit secret management with pluggable secret
backends support.
Following previous commits:
docker/swarmkit@eebac27
moby/moby@08f7cf0
Added the following parameters to the plugin request:
- ServiceSpec.TaskSpec.ContainerSpec.Hostname - for use in a x509
certificate
- ServiceSpec.EndpointSpec - has desired DNS domains that might be
suitable for an external x509 certificate
- ServiceSpec.Annotations.Name - name of the service
- ServiceSpec.Annotations.Labels - captures environment names, and other
metadata

Signed-off-by: Liron Levin<EMAIL_ADDRESS>

CC @diogomonica, @aaronlehmann, @riyazdf.
@cpuguy83, currently, the secrets plugin API is:
/SecretProvider.GetSecret

and the plugin capability is:
secretprovider

Should secret be pluralsecretsprovider /SecretsProvider.GetSecret?

Thanks @aaronlehmann, I just thought it will be simpler to maintain long term.
I modified the code according to your suggestion.
Also, what do you think the API should be: secretprovider or secretsprovider?

I think the plural might be better, but do we have any other examples of how the other plugins do it?

Thanks @aaronlehmann, I just thought it will be simpler to maintain long term.
I modified the code according to your suggestion.

Ah, I see now. You were reusing some structures from that package, even though you weren't serializing ServiceSpec itself.
The code looks good to me. I don't have an opinion on the API naming or set of fields to expose. Maybe @diogomonica and @cpuguy83 have thoughts on that.

The code looks fine to me.
I can't think of a reason this would matter, because it will be eventually consistent anyway, but I wanted to mention it in case someone else can think of something:
It's possible the tasks could be created and gathering all the dependencies could start, and immediately after the service was changed, and hence the parameters passed to the external secret service might no longer be accurate.   But if the service spec has changed in such a way as to change some of these parameters anyway, the tasks will probably be stopped/reaped and restarted anyway, and another call to fetch external secrets made, so it'd converge on consistent parameters in the next call.

It's possible the tasks could be created and gathering all the dependencies could start, and immediately after the service was changed, and hence the parameters passed to the external secret service might no longer be accurate.

The task has a copy of the TaskSpec. Anything taken from service.Spec.Task should be taken from task.Spec instead, to avoid this potential inconsistency.

Thanks @cyli @aaronlehmann good idea (I wasn't sure if the fields in api.Task are consistent with api.Service). I've update the review according to your comments.

Makes sense to use []byte @cpuguy83, this is much more consistent.
I also want to add validation that the secret driver exist when adding a new secret to swarmkit, but I need your  change moby/moby#34117 in order to import PluginStore without changing libcontainerd dependency in moby.

@liron-l You should be able to do this lookup with the PluginGetter.

@cpuguy83 in swarmd, PluginGetter is not initialize, I wanted to initialize with with PluginStore.

LGTM

LGTM other than the minor error message nitpick.

Thanks @cyli fixed.


[Bug]: Link does not work in Properties

Bug Description
When clicking a link in Properties (Obsidian version 1.4.2), it sends the URL to an external browser.
Relevant Screenshot
No response
To Reproduce

Put link in Properties
Click link

Obsidian Version
1.4.2
web-browser-only

[X] Did you install only one web browser plugin?

Checklist

[X] I updated to the latest version of the plugin.

fixed.


Android Crash on GalaxyS9, GalaxyS9+, Galaxy Note 9 (Samsung Exynos 9810)

Steps to Reproduce

Crash detected on Google Play Console. (Not detect on Firebase Crashlytics)
Only GalaxyS9, GalaxyS9+, Galaxy Note 9. (But not occurred all devices)
These devices use same chipset = Samsung Exynos 9810

Code sample

Logs

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 2205 >>> com.footsell.app <<<

backtrace:
  #00  pc 0x00000000009ef388  /vendor/lib64/egl/libGLES_mali.so
  #01  pc 0x00000000009f1bc0  /vendor/lib64/egl/libGLES_mali.so
  #02  pc 0x0000000000a044fc  /vendor/lib64/egl/libGLES_mali.so
  #03  pc 0x0000000000a037c0  /vendor/lib64/egl/libGLES_mali.so
  #04  pc 0x000000000002de94  /system/lib64/libEGL.so (android::eglSwapBuffersWithDamageKHRImpl(void*, void*, int*, int)+748)
  #05  pc 0x000000000002a498  /system/lib64/libEGL.so (eglSwapBuffers+80)
  #06  pc 0x000000000032ef84  /data/app/com.footsell.app-tAdyBCW1W1Y9gp2N22Ld1Q==/split_config.arm64_v8a.apk!libflutter.so

   info • A value for optional parameter 'key' isn't ever given • lib/presentation/view/webview/footsell_app_webview.dart:140:11 • unused_element
   info • The value of the local variable 'errorConnectionTimedOut' isn't used • lib/presentation/view/webview/footsell_web_webview.dart:473:31 • unused_local_variable
   info • The private field _isOnError could be 'final' • lib/presentation/widgets/app_text_field.dart:23:8 • prefer_final_fields
   info • The constant name 'SplashView' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:2:16 • constant_identifier_names
   info • The constant name 'SignInView' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:3:16 • constant_identifier_names
   info • The constant name 'HomeView' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:4:16 • constant_identifier_names
   info • The constant name 'PushSettingView' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:5:16 • constant_identifier_names
   info • The constant name 'MyPageView' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:6:16 • constant_identifier_names
   info • The constant name 'SingleWebviewView' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:7:16 • constant_identifier_names
   info • The constant name 'MemoView' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:8:16 • constant_identifier_names
   info • The constant name 'AppWebview' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:9:16 • constant_identifier_names
   info • The constant name 'MyDrawView' isn't a lowerCamelCase identifier • lib/routes/app_routes.dart:10:16 • constant_identifier_names

[✓] Flutter (Channel stable, 3.7.3, on macOS 13.1 22C65 darwin-x64, locale en-KR)
    • Flutter version 3.7.3 on channel stable at /Users/suim/dev/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision<PHONE_NUMBER> (12 days ago), 2023-02-08 15:46:04 -0800
    • Engine revision 248290d6d5
    • Dart version 2.19.2
    • DevTools version 2.20.1

[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
    • Android SDK at /Users/suim/Library/Android/sdk
    • Platform android-33, build-tools 31.0.0
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14C18
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] VS Code (version 1.75.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.58.0

[✓] Connected device (3 available)
    • SM S906N (mobile) • RFCT41N23WJ • android-arm64  • Android 13 (API 33)
    • macOS (desktop)   • macos       • darwin-x64     • macOS 13.1 22C65 darwin-x64
    • Chrome (web)      • chrome      • web-javascript • Google Chrome 109.0.5414.119
    ! Error: tommy의 iPhone has recently restarted. Xcode will continue when tommy의 iPhone is unlocked. (code -14)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

Hi @versatile309
I see there's an open issue addressing the case you described https://github.com/flutter/flutter/issues/117950
Please follow up on that issue, I'm closing the current one as a duplicate.
If you disagree, please write in the comments and I will reopen it.
Thank you


Cow: Watch thekrishinternational.com

Cow requests the watch of the watch_keyword thekrishinternational\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

thekrishinternational\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Update sort.py

Preparing review...

Preparing review...

PR Analysis

🎯 Main theme: Update sort.py
📝 PR summary: This PR updates the merge_sort function in sort.py to fix a bug where the remaining elements in the right half of the array were not being processed.
📌 Type of PR: Bug fix
🧪 Relevant tests added: No
⏱ Estimated effort to review [1-5]: 2, because the changes are localized to a single function and the fix is straightforward.
🔒 Security concerns: No security concerns found

PR Feedback
💡 General suggestions: The code changes look good overall. It would be helpful to add a comment explaining the purpose of the while loop that processes the remaining elements in the right half of the array.
 🤖 Code feedback:relevant filecheck/sort.pysuggestion
Add a comment above the while loop to explain that it processes the remaining elements in the right half of the array. [medium]relevant line# Process the remaining elements in the right half of the arrayrelevant filecheck/sort.pysuggestion
Fix indentation of the line j += 1 to match the surrounding code. [medium]relevant linej += 1relevant filecheck/sort.pysuggestion
Fix indentation of the line k += 1 to match the surrounding code. [medium]relevant linek += 1relevant filecheck/sort.pysuggestion
Fix indentation of the line k += 1 to match the surrounding code. [medium]relevant linek += 1
 ✨ Usage tips:

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To edit any configuration parameter from the configuration.toml, add --config_path=new_value.
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, add a /config comment.


Panic with unexported field

Here is the gist of the panic: https://gist.github.com/dadgar/a78cf8accbc66020f0ea
Problem was created by adding the unexported field:
// Constraints are used to restrict placement options.
type Constraint struct {
	LTarget string // Left-hand target
	RTarget string // Right-hand target
	Operand string // Constraint operand (<=, <, =, !=, >, >=), contains, near
	str     string // Memorized string
}

Which is included in this struct which was being copied during the panic:
type Job struct {
	// Region is the Nomad region that handles scheduling this job
	Region string

	// ID is a unique identifier for the job per region. It can be
	// specified hierarchically like LineOfBiz/OrgName/Team/Project
	ID string

	// ParentID is the unique identifier of the job that spawned this job.
	ParentID string

	// Name is the logical name of the job used to refer to it. This is unique
	// per region, but not unique globally.
	Name string

	// Type is used to control various behaviors about the job. Most jobs
	// are service jobs, meaning they are expected to be long lived.
	// Some jobs are batch oriented meaning they run and then terminate.
	// This can be extended in the future to support custom schedulers.
	Type string

	// Priority is used to control scheduling importance and if this job
	// can preempt other jobs.
	Priority int

	// AllAtOnce is used to control if incremental scheduling of task groups
	// is allowed or if we must do a gang scheduling of the entire job. This
	// can slow down larger jobs if resources are not available.
	AllAtOnce bool `mapstructure:"all_at_once"`

	// Datacenters contains all the datacenters this job is allowed to span
	Datacenters []string

	// Constraints can be specified at a job level and apply to
	// all the task groups and tasks.
	Constraints []*Constraint

	// TaskGroups are the collections of task groups that this job needs
	// to run. Each task group is an atomic unit of scheduling and placement.
	TaskGroups []*TaskGroup

	// Update is used to control the update strategy
	Update UpdateStrategy

	// Periodic is used to define the interval the job is run at.
	Periodic *PeriodicConfig

	// GC is used to mark the job as available for garbage collection after it
	// has no outstanding evaluations or allocations.
	GC bool

	// Meta is used to associate arbitrary metadata with this
	// job. This is opaque to Nomad.
	Meta map[string]string

	// Job status
	Status string

	// StatusDescription is meant to provide more human useful information
	StatusDescription string

	// Raft Indexes
	CreateIndex    uint64
	ModifyIndex    uint64
	JobModifyIndex uint64
}

Fixed!


Unexpected route decision after accessing nodeport across nodes

Bug Report
Type: bug report
What happened
node1: <IP_ADDRESS>
node2: <IP_ADDRESS>
svc: nodePort 30991, only have one pod backend, pod ip: <IP_ADDRESS> on node2
network: vlanid 701
master interface: bond0
test network access: from node1 to node2:30991
#curl <IP_ADDRESS>:30991
404 page not found

tcpdump on interface bond0.701 and got unexpected traffic
#tcpdump -nv -i bond0.701 host <IP_ADDRESS> and host <IP_ADDRESS> and port 30991
tcpdump: listening on bond0.701, link-type EN10MB (Ethernet), capture size 262144 bytes
16:09:03.511036 IP (tos 0x0, ttl 63, id 0, offset 0, flags [DF], proto TCP (6), length 60)
    <IP_ADDRESS>.30991 > <IP_ADDRESS>.37957: Flags [S.], cksum 0xbd97 (incorrect -> 0xcde4), seq<PHONE_NUMBER>, ack<PHONE_NUMBER>, win 28960, options [mss 1460,sackOK,TS val 522611790 ecr<PHONE_NUMBER>,nop,wscale 7], length 0
16:09:03.511207 IP (tos 0x0, ttl 63, id 5047, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.30991 > <IP_ADDRESS>.37957: Flags [.], cksum 0xbd8f (incorrect -> 0x6c9c), ack 83, win 227, options [nop,nop,TS val 522611790 ecr<PHONE_NUMBER>], length 0
16:09:03.511374 IP (tos 0x0, ttl 63, id 5048, offset 0, flags [DF], proto TCP (6), length 228)
    <IP_ADDRESS>.30991 > <IP_ADDRESS>.37957: Flags [P.], cksum 0xbe3f (incorrect -> 0x4865), seq 1:177, ack 83, win 227, options [nop,nop,TS val 522611790 ecr<PHONE_NUMBER>], length 176
16:09:03.511649 IP (tos 0x0, ttl 63, id 5049, offset 0, flags [DF], proto TCP (6), length 52)
    <IP_ADDRESS>.30991 > <IP_ADDRESS>.37957: Flags [F.], cksum 0xbd8f (incorrect -> 0x6be9), seq 177, ack 84, win 227, options [nop,nop,TS val 522611790 ecr<PHONE_NUMBER>], length 0

We can see the reply network packets above, all went into bond0.701 after routing.
But, the packets between nodes are expected to go through bond0.
What you expected to happen
All reply network packets go through bond0, but not bond0.701.
How to reproduce it (as minimally and precisely as possible)
Access nodeport across nodes on underlay network mode.
Anything else we need to know?
Sometimes, although the network traffic is unexpected but it works, because container network router received these network packets and forward to nodes, if rp_filter and source address detection are both disabled.
Environment

hybridnet version: v0.3.2
OS (e.g. cat /etc/os-release):
Kernel (e.g. uname -a):
Kubernetes version:
Install tools:
Others:

This is because kernel will not trigger the rerouting process after traffic is SNATed in netfilter, which is unexpected :)
I'm working on it to adapt to the nodeport svc of kube-proxy.


ci: do not run auto commit in pull requests

This is to avoid failures like the one we saw in #126. The job fails because it is a pull request from a fork and it cannot commit to the source repository. It turns out we don't really need to auto-commit in PR. The job will still run once the PR is merged but now it will run in the context of the actual repo.

I see that the auto-commit job was skipped in the PR but it ran as expected in the main branch on the merge commit.


[bs_parser_hevc] Support for I-slices with enabled IBC

Standard allows I-slices with enabled IBC, which is effectively ignored.
Skip ref-list modification for I-slices to avoid exception.

@eistarov could you please have a look?


Issue with the Release pipeline

While I'm creating a release pipeline In the Command line script task the dual writes are changing to pause mode and then it is moving to next task. But in the background still the some of the  dual write are InProgress of changing to pause mode, can you please provide any suggest on this.

I can add additional functionality to check after the records have been triggered to pause to frequently lookup (like every minute) if maps are now in paused state or not.
Will add it on the next release


Cleanup of installation under windows

Adding alternate install under windows (not using babun)
Using choco to install docker and docker-compose (have cleaned presetup-win.sh)
The new presetup-win.cmd script now check administrator rights and can be used "standalone" for a quick installation

We used to install docker and docker-compose Windows binaries with choco, however that made a dependency on choco projects to be up-to-date and was not very reliable and consistent.
Also, I don't remember if it was possible to specify a particular version.
The current approach is made to be consistent across all platforms:

we define specific version in the scripts, e.g.
DOCKER_VERSION=1.9.1
DOCKER_COMPOSE_VERSION=1.5.2

then pull them directly from github

There are other parts of the project where we rely on a Linux(-like) shell and tools (cygwin/Babun) for cross-platform consistency and support reasons.
I'm open to suggestion and PRs for a full PowerShell support on Windows, but that's, obviously, a major undertaking.

Ok i understand your point.
There is a new version using version support so the version of docker client is now consistent with the docker inside the VM

Hi @willoucom
Thanks for being involved. So your change makes sense if this project was a completely standalone project. However it's part of a bigger initiative called Drude https://github.com/blinkreaction/drude
Majority of lines you remove in your PR are for the needs of further Drude integration. As well as babun installation that is needed to run other Drude routines smoothly. So this pull request as it is now can not be accepted as it would break Drude integration.
I guess if you made new alternative scripts (totally new, without altering existing ones) that would exist here for people who only want boot2docker-vagrant sans rest of Drude then in that case it could be accepted and merged with appropriate instructions if @lmakarov thinks it is appropriate. If you ask me it would work better as a fork of this project.
And if you use Drupal we really encourage you to try Drude.

@willoucom thanks for your input. I'm going to close this PR as we do want to keep things consistent for supportability reasons and thus will stick and require Babun on Windows (at least for now).


Internationalization

The website is currently available in german only.
First we need to find a technical way to have the website translatable, then later add other languages step by step.

If someone is interested in helping here: at the moment the main page index.html is a static page with client side Javascript. We also have a a php page details.php. I think it would be best to find a php way of internationalization and convert all pages to php, so we can share one translation file.
Comment here if you want to help.

The site is now available in german and english. Thanks to @greenhalos.
Translations for other languages are welcome.


Copy address only works on symbols

Video of the behavior
https://youtu.be/qMP6U5dZ21g

Looks like we missed closing this one when it was resolved.


Condition function is ignored

Upon updating this plugin, it stopped recognizing a condition function that I use to check that the cursor is in a math section in Markdown. When I checkout back to commit 99a94cc35ec99bf06263d0346128e908a204575c then it works again. If I checkout one commit after that, it fails, so the problem is likely in f1d81013bccda0b4a84f405976b41de2278054d0 .

Is it possible that it's due to this: https://github.com/iurimateus/luasnip-latex-snippets.nvim/issues/14?

Ah yes it seems likely. Thanks, i'll check that out.


"Hull" and "trimesh" colliders seem broken

Hull and trimesh colliders seem to add a pivot outside the mesh that it moves around
https://user-images.githubusercontent.com/57411488/213877400-7229b7ea-65d4-4162-be54-2cb87153480a.mov
see video with no forces acting on the rigid body ^

It's a bit unclear what's going on here actually...  How are your RigidBodies set up?
A common thing that can happen is that your colliders are not centered within their bodies. It's interesting how it seems to be "heavy" at the bottom.

It's a bit unclear what's going on here actually... How are your RigidBodies set up?
A common thing that can happen is that your colliders are not centered within their bodies. It's interesting how it seems to be "heavy" at the bottom.

Thanks for the info. I'm dynamically creating these RigidBodies and joints based on links and joints from a URDF. But the same thing is actually noted by @brunosimon in his video course when trying to create a hull collider for a hamburger mesh. https://threejs-journey.com/lessons/physics-with-r3f#


Detele file error

if the next change file is a deleted file ,it will show a error like this:
cannot open file:///e%3A/code/flutter_quick_cli/asset/1.webp. Detail: Unable to read file 'e:\code\flutter_quick_cli\asset\1.webp' (Error: Unable to resolve nonexistent file 'e:\code\flutter_quick_cli\asset\1.webp')

Thanks for the report. Made some changes, so it should be fixed in the newest version now ✅

it 's great~ and it work.
but i found another problem,There was no response when I entered alt+z in the deleted file，And in the list view mode, the order of next changes is not as shown in the vs code

Weird, it works for me. I made another change which might fix the problem with no response. Also what operating system are you using?

The operating system I am using is Windows 10 22H2 19045.3693，

Looks like the problem is with the .webp file since it's not a text file. I use vscode.window.activeTextEditor which seems to only work with text files. I will need to look more into it if I can add support for images and other non-textual files.


PKG -- [root] Enter alpha mode

This PR enters alpha mode for the changesets bot.  I've adjusted all of the package versions to match what is currently released for the existing alphas.

bump another patch version for all packages
the first alpha versions has been already published in npm
for example this one:
https://www.npmjs.com/package/@onflow/fcl?activeTab=versions
<EMAIL_ADDRESS>has been published yesterday

Yup, the idea is that the package.json files need to have the current alpha version that is released.
When the bot runs changeset version is run, it will bump these to the next alpha version to prepare for release.
When the bot run changeset publish, it will release any packages whose versions do not exist on NPM (i.e. the ones that just got bumped)
If we were to put these packages to the next version, the changeset bot would bump again and would end up skipping a version.

I see, I thought you're trying to publish the packages manually


[PRW-2.0] New config surface allowing content-type and encoding preferences for both sending and receiving.

TODO(bwplotka):

[ ] Agree if we want what's proposed in the new negotiation proposal https://docs.google.com/document/d/16ivhfAaaezNpB1OVs3p83-_ZZK-8uRgktqtcpYT2Sjc/edit
[ ] Fix the sender part
[ ] Consider util for "preference enum" flags
[ ] Finish the receive part.
[ ] Fix tests

We switched to simpler idea so closing this, will add another one for our current approach (while learning from the comments made here from @cstyan  🤗 )


release the sensitive-info flag

Not 100% happy with the flag name, and am open to suggestions.

Does this PR need a docs update or release note?

[x] :white_check_mark: Yes, it's included

Type of change

[x] :sunflower: Feature
[x] :world_map: Documentation

Test Plan

[x] :muscle: Manual
[x] :zap: Unit test

@ntolia updated and ready for re-review.
Flag display in corso --help
Flags:
      --mask-sensitive-data   anonymize personal data in log output


CRITICAL:

the typescript playground is not opening in the new tab which makes it little bit unconvenient to use.

This most definitely isn't a critical issue, sorry.
Whether or not a link should open in a new tab or not is a hotly debated item, as some people don't want to open a new tab and setting target="_blank" means nobody can have that behavior; you can Ctrl+click or middle click to do that quickly.


Profile page

Add Profile section to app

Profile creation, view, edit
Profile form validation
Wrap app with ProfileContext allowing access from other components

First login with LinkedIn

View profile summary

Updated with Edit profile feature, which now works with latest master.
Do note there is a backend bug : https://github.com/jobsgowhere/jobsgowhere/issues/123


💡[Feature]: In the existing project [apple-stock-predictions-lstm.ipynb] i want to add GRU model and compare LSTM and GRU Results

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
To enhance the existing stock price prediction project by integrating a Gated Recurrent Unit (GRU) model alongside the existing Long Short-Term Memory (LSTM) model. This will allow for a comparative analysis of the performance of both models on the same dataset.
Use Case
Enhanced Predictive Analysis: Integrating a GRU model into the stock price prediction project will significantly enhance predictive analysis capabilities. By comparing GRU with the existing LSTM model, users can identify which model offers better accuracy and performance for predicting stock prices based on historical data. This comparison will allow for more informed decision-making when choosing the appropriate model for similar time-series forecasting tasks
Benefits
Integrating the GRU model will improve prediction accuracy, offer a faster and more efficient alternative to LSTM, and provide users with greater flexibility for model selection. The feature enhances the project's versatility, making it applicable to broader time-series forecasting tasks and fostering community engagement through comparative analysis.
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

its already there

its already there

I noticed that the existing code [ Prediction Models/Apple Stock Price Prediction/Models/apple-stock-predictions-lstm.ipynb ] only implements the LSTM model. I believe adding the GRU model could enhance prediction performance and provide a valuable alternative, given its efficiency and effectiveness in time-series forecasting...


Migration guide and expanded docs

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/90
Originally created by @aaronsteers on 2021-04-02 00:44:25

Now that we have launched 0.1.0, we should expand on the docs and the new user experience.
We should also consider what would be helpful to ease migration from prior versions.
Sample tap migration PR for ref:

https://github.com/dataops-tk/tap-powerbi-metadata/pull/23

View 3 previous comments from the original issue on GitLab


feat(nodes): make it possible to set origin per node

Discussion - https://github.com/wbkd/react-flow/discussions/2871

This PR doesn't cover store actions like

setNodes
setDefaultNodesAndEdges
updateNodeDimensions
triggerNodeChanges

There's probably a couple more places where nodeOrigin would have to be updated to use either the per node origin or the global nodeOrigin.

This PR doesn't cover store actions like

setNodes
setDefaultNodesAndEdges
updateNodeDimensions
triggerNodeChanges

There's probably a couple more places where nodeOrigin would have to be updated to use either the per node origin or the global nodeOrigin.

Thanks for the directions, will look into that

This will be possible with the next major or eventually minor release. It's already implemented in the "feat/packages" branch.

This is part of the v12 release. It's still in beta, but you can already try it out. All details: https://github.com/xyflow/xyflow/discussions/3764


installation error in "Ubuntu 16.04.4 LTS"

python3 -m venv venv && source venv/bin/activate && pip install -r requirements.txt
--editable=git+git@github.com:alexis-mignon/python-flickr-api.git is not the right format; it must have #egg=Package

https://github.com/tobiasandtobias/flask-alembic/issues/2
issue can be solved by   requirements.txt as following
-e git+https://github.com:alexis-mignon/python-flickr-api.git#egg=Package


Add GET_CONTENT and INSERT actions.

This branch adds support for 3rd party app integration/automation using
standard "otpauth://" URIs
(https://github.com/google/google-authenticator/wiki/Key-Uri-Format).
The GET_CONTENT intent action will return the current code for an
existing token. The INSERT action will install a new token and return
the current code (and the token secret to allow stateless operation by
the intent sender). Both actions are subject to user confirmation.
These two actions will allow a 3rd party app to alleviate the cubersome
and error prone user process of being prompted for an OTP code,
switching to FreeOTP, memorizing or copying the code to the clipboard,
switch back to the original app, and finally entering the code. The 3rd
party app should appropriately handle the exception cases of FreeOTP not
being installed or the user denying the requested action.

Please make sure to follow: https://chris.beams.io/posts/git-commit/

So, I understand the purpose of the GET_CONTENT action. But I don't understand the purpose of the INSERT action. Third party apps can already create tokens by simply opening the otpauth:// url.
I'd also be open to a patch which migrates all token access through these intents. In this case, we need to verify the sender of the intent. If the sender is FreeOTP, we can allow the fetching of tokens without confirmation.

Well, it's been almost a year, but if I recall, I didn't want to break the existing functionality, but I had a couple issues with it. First, it is odd to me that an intent action named VIEW results in changes to the state of the apps data. More importantly, I need it to confirm with the user before adding tokens and provide feedback when there are errors. Neither of these happened with the existing ACTION_VIEW code so I implemented them under a different intent action name (INSERT is more appropriate IMHO) providing the functionality I was after while maintaining backward compatibility. Thanks for your attention on this.

@ericatkin It is strange. But, to my knowledge, VIEW is the intent for capturing URLs that are clicked on. In our case, we want to support clicking on otpauth:// URLs in the browser. So that is why we use VIEW. If we can capture those clicks with INSERT, great! But if not, INSERT is probably redundant.

Is it ok to add the confirmation and error reporting to the VIEW code path?

Actually, I think that is a use case for keeping both. VIEW for urls clicked in a browser, and INSERT for explicit intent based IPC where we can assume the client app wants feedback.

@ericatkin We probably need confirmation on VIEW (we don't have it now). What purpose would INSERT serve (besides merely a logical distinction)?

For me, the important thing is that my app needs to know if the token was successfully inserted or not. If we can set the result on the VIEW intent then that will likely work for me and seems it would just be ignored in the case of clicked hyperlink. I would also want to the add the confirmation dialog and alert dialog on errors which breaks backward compatibility. I'd be willing to code that up and test these assumptions if it's something you'll merge, but I don't want to do it if it will go nowhere. What do you think?

@joekir Do you see any reason this proposal is a bad idea?


run 2 parachains for xcm testing

e2e tests all still pass

overhead is minimal/nothing. waiting on @vgeddes to share comments before merging though.

We'll likely want something like this in future. Right now though, I think its a bit premature to add this functionality to our E2E stack.
In the short term (milestone V1), this testing feature will likely not be used at all, as its more straightforward to test simple XCM asset transfers using polkadot-launch parachain/config-xcmp.json. No need to run the relayer, and deploy contracts, etc. It also gives us more flexibility to customize parachain code/config for testing different XCM scenarios, instead of the structure mandated by the E2E stack.
Then in the longer term, as we evolve XCM and bridge messaging, the solution implemented in this PR won't be sufficient. Instead of a running an duplicate of our parachain, we'll need to run a custom parachain with pallets and config that differs from snowbridge.

@vgeddes we need to be able to test xcm e2e, including from the frontend. i don't really see much issue with adding this to our e2e stack. it will be used and the additional is pretty minimal.

can put it in a different script if u prefer but i think an e2e script with both is still important

@vgeddes this is actually needed to test basic functionality of the grandpa light client properly when testing the parachain merkle proofs as the merkle tree should be tested with more than 1 leaf.
i've also updated the script to take an argument "duplicate" such that it will run 1 parachain without the arg and 2 duplicated parachains with it, so should still be compatible with your needs for xcm testing/manually running a second parachain :)

e2e tests all pass in both configurations, with 2 or 3 chains running fine in each configuration, so going to merge

Cool, sounds good. On a related note, in #417 we're also gonna have to run at least 2 collators per parachain due to a change in block authoring logic in Cumulus.


Fix Dependency Check in OpenTelemetry Extensions pom

Description
Adds missing dependency that caused Analyze Dependency semaphore failures

let's merge this once the semaphore build passes. @marcusgreer in the meantime can u push this commit into the other branch?


Add note about passing ES6 arrow functions

This note would have helped me to figure out what's happening. It's also a nice opportunity to evangelize and educate about ES6. :)

Could probably be extended to mention all mocha functions? Since this would apply to TDD interface functions, as well as the other BDD functions like it and hooks like before, etc. For example, you can't do:
it('test', () => {
  this.skip();
});

I tried to keep it short and relevant to the context, right under the this.slow(); snippet. I think people can generalize once you put them on the right track. If you want to make it longer then maybe it should be moved out of the 'Dynamically Generating Tests' -> 'Test duration' section, and become its own little header?

I like that idea :) Maybe a section on ES6?

Are there any other ES6 considerations apart from this one about arrow functions and the one that's already there, Working with Promises? (I can't think of anything that would change because of classes, for instance, or because of let/const)

Not that I'm aware of. And sorry for the trouble!

This note would have helped me to figure out what's happening.

Me too.

Put it in its own section as suggested by reviewer, and rebased.

Thanks!


cmd/compile: runtime error: makeslice: len out of range

Given the following program:
package p

func f() {
	_ = [][]int{1e9: []int{}}
}

go1.8.3 prints
# command-line-arguments
./test.go:3: stack frame too large (>2GB)

On tip, the compiler crashes with an internal error:
# command-line-arguments
panic: runtime error: makeslice: len out of range

goroutine 18 [running]:
cmd/compile/internal/gc.bvalloc(...)
	/home/adonizetti/go/src/cmd/compile/internal/gc/bv.go:21
cmd/compile/internal/gc.livenessemit(0xc4200b4240, 0xc42048c128, 0xc42048c190)
	/home/adonizetti/go/src/cmd/compile/internal/gc/plive.go:1258 +0x167
cmd/compile/internal/gc.liveness(0xc420496000, 0xc420498000, 0x41117d)
	/home/adonizetti/go/src/cmd/compile/internal/gc/plive.go:1302 +0x131
cmd/compile/internal/gc.genssa(0xc420498000, 0xc42007c6e0)
	/home/adonizetti/go/src/cmd/compile/internal/gc/ssa.go:4377 +0xa0
cmd/compile/internal/gc.compileSSA(0xc420314000, 0x1)
	/home/adonizetti/go/src/cmd/compile/internal/gc/pgen.go:240 +0x7e
cmd/compile/internal/gc.compileFunctions.func2(0xc420472780, 0xc42046c0f0, 0x1)
	/home/adonizetti/go/src/cmd/compile/internal/gc/pgen.go:287 +0x49
created by cmd/compile/internal/gc.compileFunctions
	/home/adonizetti/go/src/cmd/compile/internal/gc/pgen.go:285 +0x10e

$ gotip version
go version devel +4c86f7bd49 Tue May 30 01:10:56 2017 +0000 linux/amd64

Should probalby get https://github.com/dvyukov/gosmith working again.

@dgryski In what sense? I fuzz the compiler with gosmith fairly regularly.

Ah, good to know gosmith still works.  I wasn't sure where this bug came from, and if it happened from production code, another round of fuzzing might be worth it.  Nice to know we're still throwing random stuff at it then :)

Introduced in ca33e1097155019d0636a0da805054b4182e9b7d.
cc @josharian


Web analytics - improve tracking on the website

As a ODC product manager
I want to know whether the user is clicking the link/button
So that I know where to prioritise when making improvements on the site
Basic Requirements:

[ ] Can identify which buttons or links on the same page are redundant
[x] Can identify how the user is interacting with the survey form
[x] Can identify what boxes users are stopping and leaving at
[x] Can track the survey form submissions that are actually submitted and not just filled in and abandoned
[x] Can track when the window is scrolled down (to see if anyone is reading before the fold)
[x] Can track the search terms used on site

Also see #888

Not sure how to track redundant buttons but everything else is putting events into Google Analytics.
I've written a summary of all the events.


Second backprop

I think we need second-order backprop for A and for AA - I bet those will be the bottlenecks for trainable radials.

I'm going to declare this as completed by #49 - Any issues will be bugs left over from that PR.


Phalcon Explorer - Powerful Transaction Explorer Designed For DeFi Community

Title of your project
Phalcon Explorer
Short (1-2 sentence) description of your project
Designed specifically for the DeFi community, Phalcon Explorer empowers developers, traders, and security researchers to delve deep into transactions. As of now, Phalcon Explorer boasts over 20,000 monthly active users, analyzing approximately 10,000 transactions daily across 160+ countries. Notably, 75% of our user base hails from major countries including the US, China, and the UK.
Link to your project
https://explorer.phalcon.xyz/
Live on Testnet
No
If your project is live on one of Taiko's testnets, please provide evidence of that here (eg. links, screenshots).
By now, Phalcon Explorer supports ETH, BSC, Arbitrum, OP, Polygon, Fantom, Avalanche
Upload a quality logo to your project

@aleaxu When can we expect Phalcon to be live on Taiko testnet? :)


Convert DelegableAuthInfoDAO to a trait

With this change it would be easier to mix it into other abstract classes.
Fixes: #560

Coverage remained the same at 95.619% when pulling 2e73d2ae22d78de249c1db7835ad4acaaa1c69d5 on akkie:fixes_560 into 0d983cc59e17e1a49bd47e26874a80f3465c4631 on mohiva:master.

Coverage remained the same at 95.619% when pulling 2e73d2ae22d78de249c1db7835ad4acaaa1c69d5 on akkie:fixes_560 into 0d983cc59e17e1a49bd47e26874a80f3465c4631 on mohiva:master.

Coverage remained the same at 95.619% when pulling 2e73d2ae22d78de249c1db7835ad4acaaa1c69d5 on akkie:fixes_560 into 0d983cc59e17e1a49bd47e26874a80f3465c4631 on mohiva:master.

Coverage remained the same at 95.619% when pulling 2e73d2ae22d78de249c1db7835ad4acaaa1c69d5 on akkie:fixes_560 into 0d983cc59e17e1a49bd47e26874a80f3465c4631 on mohiva:master.


Questions about fine-tuning based on small dataset about  picking objects

Hey,
Thanks for your open-source code!! I am trying to fine-tune the vla model using my small dataset but have some questions:
My small dataset for fine-tuning: 120 demons about pick up a yellow or a red object (fake fruits) .
Robot Arm: UR5
Q(1) How to use proprio information of the robot? You mentioned in an other closed issue: “Adding proprio should be a small code change to the RLDSTransform”
Could you maybe describe it more specific about how to make the change?
(This is how I did, and maybe I misunderstood)
I changed  in line 46-48 in
https://github.com/openvla/openvla/blob/f7e891580a2fbd429f5f1cc22a4ccdb3cdb71ad1/prismatic/vla/datasets/datasets.py#L48
from:
 conversation = [
        {"from": "human", "value": f"What action should the robot take to {lang}?"},
        {"from": "gpt", "value": self.action_tokenizer(action)},
    ]

To:
xxxx = proprio_data
 conversation = [
        {"from": "human", "value": f"What action should the robot take to {lang}, given robot proprioception {xxxx} ?"},
        {"from": "gpt", "value": self.action_tokenizer(action)},
    ]

I tried with this, but then overfitting happens, action acc went to 100% and robot can do noting in inference tests.
Q(2) I guess you set image_aug=True when doing fine-tuing.
In my case if I set image_aug=False, Action acc can reach over 95%. But if I set image_aug=True, Action acc will get stuck around 80% can almost not increase anymore. What can be the reason?
Q(3) Can lora_dropout help avoid overfitting, do you use in fine-tuning in your experiment?
Q(4) Since I also have Depth information, It can happen that robot always fail to grasp the object. Because from the camera view, the object is located at middle of gripper and gripper should be able to grasp the object, and in fact, the object is somewhat behind the gripper.
Have you got similar issue during testing? Any ideas?

Hi, thanks for reaching out!
Re proprio: your implementation looks correct, just add it to the prompt! We have anecdotally observed that adding proprio may indeed hurt with small datasets, so maybe it's better to not add it -- do things work better without?
Re image aug: we do usually use image augmentation. i am surprised the model would struggle to fit the data with image aug. Is the robot rollout performance any different between the runs with and without augmentation?
Re lora dropout: we don't use that in our experiments -- we use the finetuning script as provided.
Re depth: this kind of 'early grasping' is a common failure mode. You can make sure that the lighting and camera angle between data collection and robot rollout tests is consistent (since the model may use shadows or distance to frame boundary to determine depth implicitly). You can also try changing the camera angle so it's less ambiguous?
Closing for now -- feel free to reopen if you have more quesitons!


remove unused variable k from ecp_mapit

Very small and little relevant fix.
However I wanted to use this occasion also to ask you if in your opinion is desirable to change the second mapit argument to the curve's BIG type. Right now the argument can be any octet which is not efficient and makes the function's usage error prone.
If it is desirable, I am happy to take care for such an API change.

Coverage increased (+0.02%) to 89.625% when pulling b7ba9f98a037de6c243d1943cc2391c57f9c2501 on jaromil:develop into 372e483916d1dda7c28cd104ff4b3726e579a50c on milagro-crypto:master.

Hi We plan to add another mapit function which will have BIG as a parameter in the near future which will address your concern.


Length check in write_chunk().

cooccur introduces all-0 record(s) if one of the chunks it tries to write is empty; this can happen if the vocabulary is small (17 in my case). This PR fixes that.
Note that I haven't checked if a small vocabulary introduces other errors.

Okay, looks great. Tested it and seems to work well. Thank you for your contribution!


Is support for 1.17 planned?

duplicate of #12, which was closed because "asking for updates" is not appropriate for an issue tracker.
yes, it's planned.


Fix CATS issues

OPS Build status updates of commit ef393a6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/add-in-development-best-practices.md
:white_check_mark:Succeeded

docs/concepts/privacy-and-security.md
:white_check_mark:Succeeded

docs/concepts/resource-limits-and-performance-optimization.md
:white_check_mark:Succeeded

docs/design/accessibility-guidelines.md
:white_check_mark:Succeeded

docs/design/add-in-icons.md
:white_check_mark:Succeeded

docs/design/authentication-patterns.md
:white_check_mark:Succeeded

docs/design/data-visualization-guidelines.md
:white_check_mark:Succeeded

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded

docs/develop/add-ins-with-angular2.md
:white_check_mark:Succeeded

docs/develop/addressing-same-origin-policy-limitations.md
:white_check_mark:Succeeded

docs/develop/auth-external-add-ins.md
:white_check_mark:Succeeded

docs/develop/authorize-to-microsoft-graph.md
:white_check_mark:Succeeded

docs/develop/create-addin-commands.md
:white_check_mark:Succeeded

docs/develop/dialog-api-in-office-add-ins.md
:white_check_mark:Succeeded

docs/develop/loading-the-dom-and-runtime-environment.md
:white_check_mark:Succeeded

docs/develop/localization.md
:white_check_mark:Succeeded

docs/develop/referencing-the-javascript-api-for-office-library-from-its-cdn.md
:white_check_mark:Succeeded

docs/develop/troubleshoot-sso-in-office-add-ins.md
:white_check_mark:Succeeded

docs/develop/update-your-javascript-api-for-office-and-manifest-schema-version.md
:white_check_mark:Succeeded

docs/develop/usability-testing.md
:white_check_mark:Succeeded

docs/docfx.json
:white_check_mark:Succeeded

docs/excel/custom-functions-json.md
:white_check_mark:Succeeded

docs/excel/excel-add-ins-multiple-ranges.md
:white_check_mark:Succeeded

docs/includes/file-tutorial-excel-custom-functions.md
:white_check_mark:Succeeded

docs/project/create-a-project-add-in-that-uses-rest-with-an-on-premises-odata-service.md
:white_check_mark:Succeeded

docs/project/project-add-ins.md
:white_check_mark:Succeeded

docs/reference/objectmodel/preview-requirement-set/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.3/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.4/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.4/outlook-requirement-set-1.4.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.5/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.6/office.context.mailbox.item.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.6/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/objectmodel/requirement-set-1.7/office.context.mailbox.md
:white_check_mark:Succeeded

docs/reference/requirement-sets/excel-api-requirement-sets.md
:white_check_mark:Succeeded

docs/testing/sideload-an-office-add-in-on-ipad-and-mac.md
:white_check_mark:Succeeded

docs/testing/testing-and-troubleshooting.md
:white_check_mark:Succeeded

docs/testing/troubleshoot-manifest.md
:white_check_mark:Succeeded

docs/word/create-better-add-ins-for-word-with-office-open-xml.md
:white_check_mark:Succeeded

docs/word/search-option-guidance.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


accept imports in deno anywidget

This is a rough way to include imports, which could be a general preamble instead.
import { widget } from "./mod.ts";

let model = await widget({
    // shared model between frontend and backend
    state: { data: [4, 8, 15, 16, 23, 42] },
    imports: `
import * as d3 from "https://esm.sh/d3@7";
`,
    // front-end render function
    render: ({ model, el }) => {
        const width = 500;
        const svg = d3.select(el)
          .append("svg")
          .attr("width", width)

        const x = d3.scaleLinear()
          .range([0, width]);

        const updateChart = (data) => {
            // Update scale domain based on new data
            x.domain([0, d3.max(data)!]);

            const bars = svg.selectAll("rect")
                .data(data);

            // Update existing bars
            bars
                .attr("width", x)
                .attr("y", (d, i) => i * 25)
                .attr("height", 20);

            // Add new bars
            bars.enter().append("rect")
                .attr("x", 0)
                .attr("y", (d, i) => i * 25)
                .attr("width", x)
                .attr("height", 20)
                .attr("fill", "#69b3a2");

            // Remove extra bars
            bars.exit().remove();
        };

        // Initial render
        updateChart(model.get('data'));

        model.on("change:data", () => {
            updateChart(model.get('data'));
        });
    }
});

model

On a side note, my editor defaults to using deno fmt. Could we use the builtin deno formatting for the deno project portion?

Made it work with React and https://github.com/denoland/deno/pull/20695. Since createRender relies on variables being defined where the render is run, it has to be called "on the frontend" rather than be created in Deno.

This is too great.

I'm liking this interface for React based anywidgets

Must be a configuration issue on my end. I made sure to keep it consistent with the repo so the change set is small. I'll dig into editor settings.

Must be a configuration issue on my end. I made sure to keep it consistent with the repo so the change set is small. I'll dig into editor settings.

Thank you! I'll try my best to get it so that deno fmt just works too.

Do you have any thoughts on how to publish to denoland the monorepo? We make separate tagged releases for each sub-package. I went through the setup on https://deno.com/add_module, but I think I may have made a mistake with the subpath and not sure how to modify.

Not sure. I haven't tried monorepos with Deno and I don't have any ideas (yet). Might be worth a post to the Deno discord: https://discord.com/servers/deno-684898665143206084

Oh great call. Thank you!


Cadence proxy logging issues

Setting the LogLevel property in CadenceSettings and then connecting to a Cadence cluster via CadenceClient.ConnectAsync() does not alter the InternalLogLevel field.  InternalLogLevel is used to set the LogLevel property in a InitializeRequest sent to the cadence proxy during CadenceClient.ConnectAsync().
The result is that the LogLevel sent to the cadence-proxy during initialization is always None=0, so nothing is getting logged by the cadence-proxy.
The proper behavior is that the user shall be able to alter the LogLevel sent to the cadence-proxy in the CadenceSettings, and the cadence-proxy should then use that as its log level for logging to stdout as well as transmitting messages back to the .NET client.

@johncburns1: I'm working on this.  One potential change for you Jack is that CadenceSettings.LogLevel may now be set to "none" too.  This wasn't documented earlier so the cadence-proxy may not support it.

That's fine, when I deserialize the log level, I set it to all caps when I parse it so case shouldnt matter.

@johncburns1: Never mind.  I'm passing you a LogLevel enum in the message.  I'm not sure why I had the setting be a string back when we first started this project.

FIXED

Sorry I was wrapped up with the wf-sms stuff for the second half of the day.  Will get on it tomorrow.

@johncburns1: The new log format is pretty hard to read.  Would it be possible to write a blank line after every entry logged to the console or perhaps not write as JSON?  Right now, it's pretty much a solid block of text.
As a temporary workaround, I've surrounded the  "---" logged messages for received messages in attempt to make these easier to pick out.  You can remove these.
I've also changed the name of your internal logger from proxy to cadence-proxy.

Yeah I can make it more human readable. I just did the json because it is a little more lightweight. I'll make it look beautiful

Cool thanks.  This will probably pay off whenever we need to debug weird issues.

Add \n line ending as well as replace JSON encoder with a console encoder in the cadence-proxy logger.


Add toNotHaveStyleRule matcher

follow #9

Coverage increased (+0.2%) to 89.595% when pulling e1e0c9e121584e4c3c8c6f94e357b6bc5d28a2d3 on toNotHaveStyleRule into 8bd66d91b30a0ee2d3cc5b407fb8d3812a5fe11c on master.


No product links on pack View page

The links to products have been lost in the UI change.

As a note on the subject, on export / template download the URL field is missing as well


how to config when i want no fallback on some situation

for example,
on 409/400 http status, i don't want to fallback, what can i do?

Do you mean sentinel integration with spring-cloud-gateway or zuul?
pls describe it clearly.

Closing this issue due to no feedback.


Verify that hadoop playbook works

Works after switch to default-jdk and default-jre-headless per #87


Multi-column positive interop placeholder

It would be useful to have the multi-column apps converge on a spec to allow for interoperability.
Lume
Notedeck
Does coracle do multi-column @staab ?

Coracle doesn't do multi-column per se, but it does have custom feeds which is conceptually similar. I have a NIP for custom feeds available on wikifreedia, and a typescript implementation available as part of welshman. I'm interested in seeing adoption of my feeds standard, because it enables a "feed marketplace", which is a huge benefit to users. In Coracle, you can already create, search, and share feeds across your network.


Incompatible with Bitbucket Data Center

The latest UPM update (3.0) marks this plugin is not compatible with the following text:

The currently installed app was a part of the deprecated Data Center program and the app version is now not Data Center compatible. Please update the app to a Data Center version.

According to Atlassian:

The latest UPM update (3.0.0) contains Data Center compatibility messaging, which is why you’re now seeing these messages.
You’re seeing these as Atlassian has launched a new class for marketplace data center to test if the add-ons are DC compatible. This is to ensure that those add-ons are not compromising performance of the instance. Please refer to the full announcement here A new class of Marketplace app has arrived.
As a result, you will encounter situation where the plugins are marked as incompatible. We’re still approving new apps daily as our vendors and partners update their apps to meet our new Data Center standards. Ultimately, Atlassian recommends you contact the vendor to determine compatibility at scale. For the apps released by us, we are currently working on releasing new versions but that could still take some time.
In most cases, the add-ons should still work and you won’t see any problems (as they’ve been working fine so far), but look out for any updates from vendors.

I am seeing the same issue, I am trying to upgrade to Bitbucket 6.1.

No. Due #37 the plugin does not work on Bitbucket Server 6+.

It looks like this project is no longer active, last commit is almost a year ago. Too bad. It was a very handy plugin.

I have a PR open which includes changes for Bitbucket 6.0. Note it only covers the file size plugin, not the file name. It can be compiled with atlas-package from the Atlassian SDK, and then you can upload the resulting jar to Bitbucket.

My free Control Freak plugin might be a good substitute.  Currently it provides the ability to block large files. Compatible with Bitbucket Server and Data Center 6.x.
Example push rejection:
remote: Control Freak: Push rejected. Files larger than 8000000 bytes are not permitted
remote:
remote: Control Freak
remote: -----
remote: Push rejected. Files larger than 8000000 bytes are not permitted
remote: in this repository. The following file is too large:
remote:
remote:   path/to/bigFile.jar (8722752 bytes)
remote:
remote: You can push large files to this repository using 'git lfs':
remote:   git lfs track <path>
remote:


refine SegmentRead streams

What problem does this PR solve?
Issue Number: ref #5900
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/run-all-tests

@ywqzzy please update the branch and get it merged

/merge

@ywqzzy please update the branch and get it merged

Because the fork repo is in group ywqdev, so I can't modify the config.
I will use my own account in future development.


Selenium WebDriver Not able to select DoJo dropdown

Hi there!
I am trying to select a dropdown which is designed in the DOJO Html and when i am performing the "Select" function on this then it is not able to Click on the dropdown nor it is able to select the value from it.Is it the bug in the WebDriver that it is not able to select the value.
Please find the Html code for dropdown below -
Dropdown_Issue.docx
Feature Request

Reasons for adopting new feature
Is this a breaking change? (How will this affect existing functionality)

The temporary solution here is to first click on the dropdown and to next provide the xpath for the element which is present on that dropdown and then perform the Click option.
But if you refer the code above then there is same class name for both the droopdowns so if we are planning to use this property then xpath will be same for both of them and selenium is getting confused and getting an error as "Element Not Found".
Please provide any other solution if someone knows about it . Thanks in advance.

Hi there!
Your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

Thanks!

Ok Nick..Thanks !!!


unique count map

Coverage decreased (-0.2%) to 98.606% when pulling 5b7bc17a40d747ee1e85ac5eac335ee35d86f411 on hllmap into d053f8cdf0d4302d98e3a8127ca03b4a51cec1f4 on master.


Sushy-tool installation failed on RHEL9.1 with OCP 4.13.10

Bug description
Hey Guys,
I think you should change the role of sushy-tool installation because below packages are removed from RHEL9. can you please confirm if my understanding are correct.

python3-virtualenv
libvirt-devel

OpenShift version
other (provide in the description)
Assisted Installer version
v2.12.1
Relevant log output
thentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o 'User="root"' -o ConnectTimeout=10 -o 'ControlPath="/root/.ansible/cp/6e1f01377f"' <IP_ADDRESS> '/bin/sh -c '"'"'rm -f -r /tmp/ansible-tmp-1696565854.5189414-158717-68323237263436/ > /dev/null 2>&1 && sleep 0'"'"''
2023-10-06 13:17:36,602 p=158717 u=root n=ansible | <<IP_ADDRESS>> (0, b'', b'')
2023-10-06 13:17:36,608 p=158374 u=root n=ansible | fatal: [vm_host1]: FAILED! => changed=false
  failures:
  - No package python3-virtualenv available.
  - No package libvirt-devel available.
  invocation:
    module_args

Inventory file
No response
Required statements

[X] I have removed all sensitive details from the attached logs and inventory files.
[X] I acknowledge that Red Hat does not provide commercial support for the content of this repository.
[X] I acknowledge that any assistance is offered purely on a best-effort basis, as resource permits.

I ran into the issues when attempting to run crucible on RHEL 9.


Update lvm driver handler function and add unit test

Coverage increased (+4.0%) to 41.085% when pulling 2b0e57f37c80344d682099cae375da54b42ee31d on leonwanghui:lvm-fixer into 0183dfdd66ca648895aca9f0804a66f9d10b691d on opensds:development.


TCp

Specs

Leon version: 1.0.0-beta.8+dev
OS (or browser) version: Windows
Node.js version: v18.16.0
Complete "leon check" (or "npm run check") output:https://report.getleon.ai/raw/dewiyepiko
(if using Docker) Complete "npm run docker:check" output:
(optional) Leon skill version:

Expected Behavior
It should work correctly
Actual Behavior
It says that Leon is ready, but the web server is refusing the connection.
This is the second time I have installed it, because the previous time it connected but the TCP server never loaded to the console.
Now it loads the TCP server but it is impossible to connect to the localhost.
How Do We Reproduce?
Extra (like a sample repo to reproduce the issue, etc.)

Hi, do you have any anti-virus or firewall that could block any port?
From the report you shared, there is no reason that it shouldn't work.

Hello, I do have an antivirus, but I checked and the google browser does not have any blocking in theory

Disable it temporarily and try again. Only the web app runs in the browser. Leon has its own Node.js process with a few other processes such as the TCP server and the Python bridge to execute skills. It is not only about the browser.


Implement trait

Parses traits, largely reusing the impl implementation. I added code to parse_impl.rs, didn't have a new good name for the file, so I left it for now...
Unfortunately this introduces a breaking change, because existing TyDefinition did not account for : Bounds and optional = initializer. In general, we should probably mark everything #[non_exhaustive] to at least have the option to add fields in non-breaking ways.
But no urgency from my side for any release, just thought I'd implement this while I'm in the flow 😉

My first instinct would be to avoid adding #[non_exhaustive] to structs unless we also give them constructors.

My first instinct would be to avoid adding #[non_exhaustive] to structs unless we also give them constructors.

Good point. I would expect the typical usage is to read those structs (from a parsed result), but there may be use cases where people create them (for testing, or local manipulation).
I removed #[non_exhaustive] from TyDefinition. I guess it's OK to have small breaking API changes every now and then, as we're still in 0.x.


Adding some programs

Summary
< A quick summary of the associated pull request >
Quality Assurance Checklist
< Confirmation of this pull request meeting the following requirements, prior to merge >

Review Items
Y/N

Site has a publicly known bug bounty or vulnerability disclosure program

Disclosure policy is publicly available

Public URL

Submission follows the Diodb schema

Your Twitter handle (Optional):

Thanks @bcdavidchou!

FYI - @bcdavidchou you can add the Hall of Fame value in a separate PR if you like.


move flickr attribution to the footer

The logo is already in the repo. We just need to put it next to the attribute line.

implement as image tag

Attribution is near the picture, closing.


Add ats_unique_buf

Add a mechanism to use std::unique_ptr with ats_malloc.
This is required by QUIC code.

[approve ci autest]

Any reason to not use std::vector<uint8_t>?

@SolidWallOfCode I don't see any reasons to use std::vector<uint8_t>.   Are you suggesting we don't need to use ats_malloc?

Talked on Slack, and my understanding is:
We could/should use std::vector<uint8_t> or std::string instead of ats_malloc in general. Because these two should provide what we need, we might be able to deprecate ats_malloc in the future.
For now, I'd like to stick with the ordinary way (ats_malloc). Replacing internal implementation later shouldn't be difficult.
Merging this for coming 9.0 branching.


[Feature Request]Anyway to get auth working with Organizr SSO

Would be awesome if this could work with Organizr SSO (https://github.com/causefx/Organizr), as from a user standpoint, the user only needs to login once. Organizr already auths with Plex, so passing a success cookie might be an option?

PR https://github.com/samcm/synclounge/pull/169 made to update this on the SyncLounge side