Plans for additionnal storage backend

Hi there, first thanks for open-sourcing a new UI for traces!
I'm working on Quickwit OSS engine and we are actively plugin it into different UI. We did it for Jaeger and I'm working currently on a Grafana plugin.
I'm wondering if you are considering supporting other storage backends and if yes, where I can find the API Quickwit would need to support (note that we are adding Elastic DSL support in the next release so this might help).
Thanks!

Hi @fmassot, thanks for taking an interest in the project.
Teletrace architecture doesn't assume specific database usage and supports writing custom plugins for solutions like Quickwit.
Teletrace has two main contact points with the plugin system: ingestion and querying. You would need to implement both for your solution to fully work with Teletrace.

Ingestion - The ingestion part of Teletrace is implemented using an OTel collector distribution. Traces that reach Teletrace via OTLP/gRPC (:4317) or OTLP/HTTP (:4318) are processed by one of the supported exporters (we currently support Elasticsearch, OpenSearch, and SQLite). You would have to write your own exporter and then add it to the components list so users would be able to use it in their Teletrace distribution config (example).
Querying - Now that the traces are stored somewhere, we need to retrieve them via the API. The Teletrace API is a simple web server that runs alongside the Teletrace collector distribution on a different goroutine. Since each database has its own format for storing traces, each database must also have its own SpanReader interface implemented to allow us to get the traces formatted according to our internal models (here and here). So as a first step, you would have to implement the SpanReader interface and put it alongside the other supported databases, then you can connect it to the rest of the system in the span reader initialization stage. You can take notes from the ES span reader on how to add and read options from the Teletrace global config.

Feel free to ask any questions you might have during the integration process.

Thanks @ophiryael for your detailed response.
Adding a new exporter + span reader will require some work so I need to look at the code and estimate that.
One shortcut could be using the OpenSearch exporter as this should work out of the box. For the ES span reader, I saw that you were using the elastic client which expects a header x-elastic-product and there are some subtitles in the query building (like the necessity to add .keyword to a text field on which to need to do aggregations).
Do you plan to have an OpenSearch span reader too?
I will let you know if/when we start working on this.

Hey, @fmassot we are currently working on adding full support for OpenSearch and I assume it will be available within the next few weeks or so, regardless, taking a look at Openwit I think it would be better to add official support for it instead of "riding" on the OpenSearch support.
I will gladly work on it along side you if you are willing, feel free to reach me over Slack.


Release v2

Please cut a new release so that fixes such as https://github.com/codespell-project/actions-codespell/pull/60 become available in a released form. Otherwise we are doomed to use @master version.

https://github.com/codespell-project/actions-codespell/releases/tag/v2.0
hopefully it worked :)

@larsoner please also create a v2 tag so that we can update to a version that only pins the major version rather than having to pin all the way to v2.0. The action's users will start getting Dependabot PRs for the bump to the new action version in our workflows so it would be nice if those were for a v1 -> v2 bump instead of a v1 -> v2.0 bump.
More information on the reason and use of the major version ref here: https://github.com/codespell-project/actions-codespell/issues/47

well, if so, may be it should have been a v1.1 release (my bad to suggest jumping right to v2) and then v1 tag was updated?  Then may be v1 could be a branch (inherently mutable) to follow tags within v1.x series -- I wonder how other actions organize that flow.

Pushed a v2 that's the same as v2.0


coalesce CIDRs across rules for l3 maps

Add functionality in pkg/ip for combining sets of CIDRs into the smallest possible equivalent set of CIDR. Utilize this functionality for ingress / egress CIDR rules in Cilium.
Signed-off by: Ian Vernon<EMAIL_ADDRESS>

I keep hitting errors unrelated to my changes; the code is ready for review.

Closed in favor of #3619 , which only contains the pkg/ip changes and no pkg/policy changes for now.


cloudflare tunnel status goes up and down

The problem
in the last few days my cloudflare tunnel goes up and down causing loss of remote access.  I deleted the cloudflared addon, reinstalled, and this time configured it as a remote managed tunnel.  started working, then same result, tunnel goes up and down.
What version of Cloudflared has the issue?
4.1.7
What was the last working version of Cloudflared?
4.1.6
What type of installation are you running?
Home Assistant Supervised
Add-on YAML Configuration
#cloudflared trust docker network
http:
  use_x_forwarded_for: true
  trusted_proxies:
    - <IP_ADDRESS>/24

Anything in the logs that might be useful for us?
2023-06-14T02:12:05Z INF Unregistered tunnel connection connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:05Z ERR  error="timeout: no recent network activity" cfRay=7d6f0b5c394b1020-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:12:05Z ERR Request failed error="timeout: no recent network activity" connIndex=3 dest=https://xx.xxx.xxx/api/hassio/addons/e33666f6_rtsp_simple_server/icon event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:12:05Z INF Unregistered tunnel connection connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:05Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:05Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:05Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:05Z ERR  error="timeout: no recent network activity" cfRay=7d6f0b5dcac41020-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:12:05Z ERR Request failed error="timeout: no recent network activity" connIndex=3 dest=https://xx.xxx.xxx/api/hassio/app/frontend_latest/7021-KX4kgoN8iAQ.js event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:12:05Z WRN Failed to serve quic connection error="timeout: no recent network activity" connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:05Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:05Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:05Z WRN Connection terminated error="timeout: no recent network activity" connIndex=3
2023-06-14T02:12:05Z WRN Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1
2023-06-14T02:12:11Z INF Unregistered tunnel connection connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:11Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:11Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:11Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:11Z INF Unregistered tunnel connection connIndex=2 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:11Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:11Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:11Z INF Retrying connection in up to 1s connIndex=2 event=0 ip=<IP_ADDRESS>
2023-06-14T02:12:11Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2
2023-06-14T02:12:12Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0
2023-06-14T02:12:21Z INF Registered tunnel connection connIndex=1 connection=bd19ca9b-985b-494b-825d-3c8a8299395f event=0 ip=<IP_ADDRESS> location=SLC protocol=quic
2023-06-14T02:12:21Z INF Registered tunnel connection connIndex=2 connection=3b4cb42e-0729-4ae2-9a5a-2acd22d69f14 event=0 ip=<IP_ADDRESS> location=DEN protocol=quic
2023-06-14T02:12:21Z INF Registered tunnel connection connIndex=3 connection=5b5bd2be-1081-4518-a761-1430ab6c720e event=0 ip=<IP_ADDRESS> location=SLC protocol=quic
2023-06-14T02:12:21Z INF Registered tunnel connection connIndex=0 connection=7ed9dbbc-7401-4ef1-9217-130f0299e65b event=0 ip=<IP_ADDRESS> location=DEN protocol=quic
2023-06-14T02:13:05Z ERR  error="stream 193 canceled by remote with error code 0" cfRay=7d6f0d556fb30906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:05Z ERR Request failed error="stream 193 canceled by remote with error code 0" connIndex=3 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/0.5.m4s event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad40906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=1 dest=https://xx.xxx.xxx/api/hls/a7e71c685c040d2b1f756d301395528b75f6ed0be8b000d6ec82d3ea43fb3cef/playlist.m3u8 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad60906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=1 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/playlist.m3u8 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z INF Unregistered tunnel connection connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR  error="context canceled" cfRay=7d6f0d0cb9c50906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.front_door?token=cd38fbad7015999791d38d8204477f483b802910b14df732974b7a9a0bb1418c event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad40906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/hls/a7e71c685c040d2b1f756d301395528b75f6ed0be8b000d6ec82d3ea43fb3cef/playlist.m3u8 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad60906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/playlist.m3u8 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR  error="context canceled" cfRay=7d6f0d0cb9b00906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.back_door?token=c5bd757962e822e6e98ddbdef541695ad2e6ef8cef638817a6577150c7c3af32 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z INF Unregistered tunnel connection connIndex=2 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d970b2a0906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/1.2.m4s event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z INF Retrying connection in up to 1s connIndex=2 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad60906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d970b2a0906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/playlist.m3u8 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/1.2.m4s event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad40906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d96d9f652c5-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://xx.xxx.xxx/api/hls/a7e71c685c040d2b1f756d301395528b75f6ed0be8b000d6ec82d3ea43fb3cef/playlist.m3u8 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=0 dest=https://xx.xxx.xxx/api/websocket event=0 ip=<IP_ADDRESS> type=ws
2023-06-14T02:13:51Z INF Unregistered tunnel connection connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z INF Unregistered tunnel connection connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-14T02:13:51Z ERR  error="context canceled" cfRay=7d6f0d0cb9ab0906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR  error="Incoming request ended abruptly: context canceled" cfRay=7d6f0d831ad60906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.mud_door?token=e346a04e764a4558150af76b686e671ecc4dc0983e661327877233854e39083e event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR Request failed error="Incoming request ended abruptly: context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/playlist.m3u8 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR  error="context canceled" cfRay=7d6f0d0cb9c80906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR  error="timeout: no recent network activity" cfRay=7d6f0d717cef0906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:13:51Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.mud_entry?token=e06ea4fd2e4de1733f53a815ef188e28242316ddac66d148d9b29f2a5b4062e4 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:51Z ERR Request failed error="timeout: no recent network activity" connIndex=3 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/1.2.m4s event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:13:52Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=2
2023-06-14T02:13:52Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=1
2023-06-14T02:13:52Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=3
2023-06-14T02:14:12Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0
2023-06-14T02:14:12Z INF Registered tunnel connection connIndex=1 connection=ecaab329-8a41-4844-8a4b-ba4eb5e820fc event=0 ip=<IP_ADDRESS> location=SLC protocol=quic
2023-06-14T02:14:12Z INF Registered tunnel connection connIndex=3 connection=1cc7e0c4-ea59-459c-99ea-810799f67cb8 event=0 ip=<IP_ADDRESS> location=SLC protocol=quic
2023-06-14T02:14:12Z INF Registered tunnel connection connIndex=2 connection=f72f7c92-bfea-47f6-8a96-7e492b34c5e7 event=0 ip=<IP_ADDRESS> location=DEN protocol=quic
2023-06-14T02:14:16Z ERR  error="stream 21 canceled by remote with error code 0" cfRay=7d6f0f0b7c590906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:14:16Z ERR Request failed error="stream 21 canceled by remote with error code 0" connIndex=2 dest=https://xx.xxx.xxx/api/hls/97383cb6c7a94eb6be0015ea0205f9dfa67e6129d1153f3fa333c7778fe11f96/segment/1.3.m4s event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:14:19Z INF Unregistered tunnel connection connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:14:19Z WRN Failed to serve quic connection error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:14:19Z WRN Serve tunnel error error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:14:19Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-14T02:14:21Z WRN Connection terminated error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1
2023-06-14T02:14:34Z INF Registered tunnel connection connIndex=1 connection=0613b45b-af2f-4aca-b8f9-d99b7e7e9ceb event=0 ip=<IP_ADDRESS> location=SLC protocol=quic
2023-06-14T02:14:34Z INF Registered tunnel connection connIndex=0 connection=8883d3ae-0491-4df1-ba17-842eeb7f0fc2 event=0 ip=<IP_ADDRESS> location=DEN protocol=quic
2023-06-14T02:15:58Z ERR  error="context canceled" cfRay=7d6f0f1dad350906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:15:58Z ERR Request failed error="context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.back_door?token=5fd8964971f31a55cf5d3ae04861b5fb724ba304df14741eabf9cccb49af4204 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:15:58Z ERR  error="context canceled" cfRay=7d6f0f1dad340906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:15:58Z ERR Request failed error="context canceled" connIndex=3 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.mud_door?token=cf8ff776599111ba7c4c31458916f0fb5072f4e7766207dfe58965439d7bdecc event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:15:59Z ERR  error="context canceled" cfRay=7d6f0f1dad370906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:15:59Z ERR Request failed error="context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.front_door?token=741c5cae21a2c0afbc503531fef48274fa3208613e9ce4c71831e945f1926db5 event=0 ip=<IP_ADDRESS> type=http
2023-06-14T02:15:59Z ERR  error="context canceled" cfRay=7d6f0f1dbd390906-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-14T02:15:59Z ERR Request failed error="context canceled" connIndex=2 dest=https://xx.xxx.xxx/api/camera_proxy_stream/camera.mud_entry?token=ecbdf59a68f38258260bdc648f5bc1e0fab17f67d9f006fb01f78e89444f47db event=0 ip=<IP_ADDRESS> type=http

Steps to reproduce the issue
fresh install works, then tunnel starts to go up and down as I access HA via the tunnel.
Additional information
No response

Thanks for raising. Since nothing tunnel / Cloudflared related changed with 4.1.7 (only documentation), this cannot be caused by the update.
It fells like a temporary problem with Cloudfalred, so it would be great if you could check for some days, how this evolves (also if you are able to connect or not, not just the logs). I also do have some connection drops from time to time, so if you can connect it's ok.

I can connect, but it was dropping so often it was not very functional.  i rolled back to 2023.5.4 (still running 4.1.7 of cloudflared) and it is much better (fewer disconnects). from reading other posts https://github.com/cloudflare/cloudflared/issues sounds like others are having the same problem.  hopefully the just released  2023.6.2 addresses the issue.
2023-06-15T19:51:10Z INF Unregistered tunnel connection connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-15T19:51:10Z WRN Failed to serve quic connection error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-15T19:51:10Z WRN Serve tunnel error error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-15T19:51:10Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-15T19:51:12Z WRN Connection terminated error="failed to accept QUIC stream: Application error 0x0 (remote)" connIndex=1
2023-06-15T19:51:33Z INF Registered tunnel connection connIndex=1 connection=9b50c91e-5ac3-43e8-bdd7-9fecfa2d3b3b event=0 ip=<IP_ADDRESS> location=SLC protocol=quic

@tivo65 Please check with the newest version released yesterday and let us know

I have the same issue, just installed latest version and deleted tunnel. Uninstalled addon an reinstall, created tunnel and after a few minutes the tunnel shows down again.

Unfortunately, I cannot reproduce this. Can you share your addon logs and any special network config or setup that you might have?

Sure https://pastebin.com/M0Q33Vtw

Fresh install full log
https://pastebin.com/tPmEjhsW

Changed domain and same problem.

Which Top Level Domain and registrar are you using?

One I have from cloudflare, thought I'd get everything at the same place.
tielen.cc

i have updated home assistant to the latest patches including cloudflared.  i am running on a cloudflare tunnel I created on the cloudflare site.  my domain is with omnis.  my HA is running on debian in a vm guest on macos host.  since the update it is running better, but I still get an occasional reconnecting message.  Interesting, it generally happens when I am loading node-red.  when I do get the reconnecting message it will load after about 30-60 seconds.  here are the logs when that happens.  the error always references "failed to accept QUIC stream"
2023-06-25T21:44:26Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:26Z INF Retrying connection in up to 1s connIndex=3 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:27Z ERR  error="timeout: no recent network activity" cfRay=7dd0641acbf4533d-LAX event=1 ingressRule=0 originService=http://homeassistant:8123
2023-06-25T21:44:27Z ERR Request failed error="timeout: no recent network activity" connIndex=0 dest=https://xxxx/api/hassio_ingress/iwUCOPVYCQeCL8JdifRj3nei0F8pobiDV3cM86moXtM/vendor/monaco/dist/editor.js event=0 ip=<IP_ADDRESS> type=http
2023-06-25T21:44:27Z INF Unregistered tunnel connection connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:27Z WRN Failed to serve quic connection error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:27Z WRN Serve tunnel error error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:27Z INF Retrying connection in up to 1s connIndex=0 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:27Z INF Unregistered tunnel connection connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:27Z WRN Failed to serve quic connection error="timeout: no recent network activity" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:27Z WRN Serve tunnel error error="timeout: no recent network activity" connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:27Z INF Retrying connection in up to 1s connIndex=1 event=0 ip=<IP_ADDRESS>
2023-06-25T21:44:28Z ERR Connection terminated error="timeout: no recent network activity" connIndex=3
2023-06-25T21:44:28Z ERR Connection terminated error="timeout: no recent network activity" connIndex=1
2023-06-25T21:44:28Z ERR Connection terminated error="failed to accept QUIC stream: timeout: no recent network activity" connIndex=0
2023-06-25T21:44:28Z INF Registered tunnel connection connIndex=2 connection=63731ffb-8a93-423b-a425-b6ba24f8e193 event=0 ip=<IP_ADDRESS> location=DEN protocol=quic
2023-06-25T21:44:28Z INF Registered tunnel connection connIndex=0 connection=5f620907-6abb-4a31-bc5a-f068ad885b17 event=0 ip=<IP_ADDRESS> location=DEN protocol=quic
2023-06-25T21:44:28Z INF Registered tunnel connection connIndex=3 connection=e1a712e9-9995-43da-9fe1-3d3928ff7450 event=0 ip=<IP_ADDRESS> location=SLC protocol=quic
2023-06-25T21:44:29Z INF Registered tunnel connection connIndex=1 connection=577bf9b1-8008-4ebe-bb12-1a4054e06a3c event=0 ip=<IP_ADDRESS> location=SLC protocol=quic

How are you running HA in Debian?
Since with running it in a VM you are introducing many potential problems, I suggest to not use this add-on but use Docker within Debian, run the official Cloudflared Container  and follow the instructions to create a tunnel in the Cloudflare Zero Trust Dashboard.

It's running on a nuc in a proxmox VM, it's been running fine with cloudflare for a while. Trouble started few days ago.

I am running a VM using virtualbox with the supplied VDI file. at HAOS ver 10.3 - https://www.home-assistant.io/installation/alternative -  I am somewhat new to HA, been running it for a few months now.  please elaborate why running home assistant in a VM is problematic.  I thought it was a fully supported installation.  Runs totally file other than this cloudflare issue.  I believe if I were to run cloudflared outside HA it would require me to spin up another linux VM as HAOS takes over my entire homeassitant VM.

i moved cloudflared to docker running on a separate host and so far no problems.  you do have to update the trusted_proxies: setting in HA to the subnet where docker is running.

i moved cloudflared to docker running on a separate host and so far no problems. you do have to update the trusted_proxies: setting in HA to the subnet where docker is running.

HI, I don't understand about trusted proxies setting, can you share your configuration ?

from my configuration.yaml on HA.  my cloudflared is running on a host in docker that is, for example, <IP_ADDRESS>
#cloudflared
#trusted proxies is subnet where tunnel running on synology
http:
use_x_forwarded_for: true
trusted_proxies:
- <IP_ADDRESS>/24


Is there a way for setting network proxy of Client in java library?

TDLib supports MTProto, Socks5 and HTTP proxies. All of them can be added using the method addProxy.

TDLib supports MTProto, Socks5 and HTTP proxies. All of them can be added using the method TdApi.AddProxy.

thanks for reply~


Fixes #1041 and #1038 on linux variants

Compilation fails due to tighter type restrictions on newer swift builds. Casting works and produces no errors. See #1041 and #1038 for complaints on this issue.

[ ] Does this have tests?
Unnecessary, existing tests cover this case (it is purely a type definition in two places)
[ ] Does this have documentation?
Not needed
[ ] Does this break the public API (Requires major version bump)?
No
[ ] Is this a new feature (Requires minor version bump)?
No

Any movement here? I'm developing a cross-platform library that depends on SwiftyJSON and having this fixed would be a huge benefit!

@monomadic This isn't compiling (at least on a mac).
I think the Swift compiler thinks < is part of a Generic statement and is erroring with
❌  /Users/travis/build/SwiftyJSON/SwiftyJSON/Source/SwiftyJSON/SwiftyJSON.swift:1215:79: expected '>' to complete generic argument list

    case (.number, .number): return lhs.rawNumber as NSNumber < rhs.rawNumber as NSNumber
                                                              ^

on Travis CI.
You need to put brackets around the left side of <.
    case (.number, .number): return (lhs.rawNumber as NSNumber) < rhs.rawNumber as NSNumber
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^ Need brackets

After applying that fix on a local checkout of this branch under Ubuntu 18.04 in WSL 2, it still doesn't work. I've changed the line to:
    case (.number, .number): return (lhs.rawNumber as NSNumber) < (rhs.rawNumber as NSNumber)

When adding the local copy as a dependency of another project and running swift test on that project, I get the following error:
% swift test
/home/george/Code/monomadic/SwiftyJSON/Source/SwiftyJSON/SwiftyJSON.swift:1215:65: error: ambiguous use of operator '<'
    case (.number, .number): return (lhs.rawNumber as NSNumber) < (rhs.rawNumber as NSNumber)
                                                                ^
/home/george/Code/monomadic/SwiftyJSON/Source/SwiftyJSON/SwiftyJSON.swift:1251:6: note: found this candidate
func < (lhs: NSNumber, rhs: NSNumber) -> Bool {
     ^
Foundation.NSNumber:2:24: note: found this candidate
    public static func < (lhs: NSNumber, rhs: NSNumber) -> Bool

It seems there's a deeper issue that this PR doesn't address at all.

@Geo1088 Yeah, you're right.
The quick fix might be to rename the operators like this.
The build passes on macOS and Linux but the tests still gives errors around INT64_MAX and autoreleasepool on Linux (tested on a Docker instance based on Ubuntu 18)  and obviously may not be the right way to fix it.

Consider #1083  instead.


Sorting milestones list

I'm trying to list issues per milestone, I've had progress with
https://github.com/cli/cli/discussions/6178
gh-milestone extension isn't used there, but it could as well have been used to get the list of milestone names that is done in the first step of the iterative solution
I have the issue that the milestones are returned in an order for which I can't specify sorting. In specific I'd like to do semantic version SORTING that the bash "sort -V" command can do but on DOS batch that I use there is no ready-made alternative for doing semantic sorting
Seems GitHub CLI supports sorting for other lists, can follow this path of discussions/docs on search's sort:
https://github.com/cli/cli/releases/tag/v1.8.0
https://cli.github.com/manual/gh_search_issues
https://docs.github.com/en/search-github/searching-on-github/searching-issues-and-pull-requests
https://docs.github.com/en/search-github/getting-started-with-searching-on-github/sorting-search-results
eg they have syntax:
`gh issue list -l "bug" --search "sort:interactions-desc"
they don't have a separate sort flag but do it via the search one
So similarly it would be nice to have something like
gh milestone list --search "sort:Version(title)"
or
gh milestone list --search "sort:title:version"
to treat the milestone title as a version string
(code would have to use some semantic version sorting routine though, since GitHub API doesn't seem to have sorting by a "semantic" string)

doing
gh milestone list -?
noticed there's a sorting option
gh milestone list --state all --orderBy.direction desc
the implied --orderBy.field number there does the job in my case since the temporal order of creation of my milestones is the same as their semantic ordering (based on their title that uses a semantic version string)
However, I need to output only a list of milestone titles. There's a --jq option there and experimented a bit with that with no success. Now I'm getting
``
Showing 48 milestones
#48                    0.8.0   https://github.com/Zoomicon/READCOM_App/milestone/48
#47                    0.7.2   https://github.com/Zoomicon/READCOM_App/milestone/47
#46                    0.7.1   https://github.com/Zoomicon/READCOM_App/milestone/46
#45                    0.5.13  https://github.com/Zoomicon/READCOM_App/milestone/45
#44                    0.5.12  https://github.com/Zoomicon/READCOM_App/milestone/44
#43                    0.5.11  https://github.com/Zoomicon/READCOM_App/milestone/43
#42                    0.5.10  https://github.com/Zoomicon/READCOM_App/milestone/42
#41                    0.5.9   https://github.com/Zoomicon/READCOM_App/milestone/41
#40                    0.5.8   https://github.com/Zoomicon/READCOM_App/milestone/40
#39                    0.5.7   https://github.com/Zoomicon/READCOM_App/milestone/39
#38                    0.5.6   https://github.com/Zoomicon/READCOM_App/milestone/38
#37                    0.5.5   https://github.com/Zoomicon/READCOM_App/milestone/37
#36                    0.5.4   https://github.com/Zoomicon/READCOM_App/milestone/36
#35                    0.5.3   https://github.com/Zoomicon/READCOM_App/milestone/35
#34                    0.5.2   https://github.com/Zoomicon/READCOM_App/milestone/34
#33                    0.5.1   https://github.com/Zoomicon/READCOM_App/milestone/33
#32                    0.5.0   https://github.com/Zoomicon/READCOM_App/milestone/32
#31                    0.4.4   https://github.com/Zoomicon/READCOM_App/milestone/31
#30                    0.4.3   https://github.com/Zoomicon/READCOM_App/milestone/30
#29                    0.4.2   https://github.com/Zoomicon/READCOM_App/milestone/29
#28                    0.4.1   https://github.com/Zoomicon/READCOM_App/milestone/28
#27                    0.4.0   https://github.com/Zoomicon/READCOM_App/milestone/27
#26                    0.3.6   https://github.com/Zoomicon/READCOM_App/milestone/26
#25                    0.3.5   https://github.com/Zoomicon/READCOM_App/milestone/25
#24                    0.3.4   https://github.com/Zoomicon/READCOM_App/milestone/24
#23                    0.3.3   https://github.com/Zoomicon/READCOM_App/milestone/23
#22                    0.3.2   https://github.com/Zoomicon/READCOM_App/milestone/22
#21                    0.3.1   https://github.com/Zoomicon/READCOM_App/milestone/21
#20                    0.6.0   https://github.com/Zoomicon/READCOM_App/milestone/20
#19                    0.3.0   https://github.com/Zoomicon/READCOM_App/milestone/19
#18                    0.2.0   https://github.com/Zoomicon/READCOM_App/milestone/18
#17                    0.1.0   https://github.com/Zoomicon/READCOM_App/milestone/17
#16                    0.0.19  https://github.com/Zoomicon/READCOM_App/milestone/16
#15                    0.0.18  https://github.com/Zoomicon/READCOM_App/milestone/15
#14                    0.0.17  https://github.com/Zoomicon/READCOM_App/milestone/14
#13                    0.0.16  https://github.com/Zoomicon/READCOM_App/milestone/13
#12                    0.0.15  https://github.com/Zoomicon/READCOM_App/milestone/12
#11                    0.0.14  https://github.com/Zoomicon/READCOM_App/milestone/11
#10                    0.0.13  https://github.com/Zoomicon/READCOM_App/milestone/10
#9                     0.0.12  https://github.com/Zoomicon/READCOM_App/milestone/9
#8                     0.0.11  https://github.com/Zoomicon/READCOM_App/milestone/8
#7                     0.0.10  https://github.com/Zoomicon/READCOM_App/milestone/7
#6                     0.0.9   https://github.com/Zoomicon/READCOM_App/milestone/6
#5                     0.0.8   https://github.com/Zoomicon/READCOM_App/milestone/5
#4                     0.0.7   https://github.com/Zoomicon/READCOM_App/milestone/4
#3                     0.0.6   https://github.com/Zoomicon/READCOM_App/milestone/3
#2                     0.0.4   https://github.com/Zoomicon/READCOM_App/milestone/2
#1                     0.0.3   https://github.com/Zoomicon/READCOM_App/milestone/1
``
and I need to get back instead:
0.8.0
0.7.2
0.7.1
...

to get just the 2nd column of the output (the title) and to skip the first three lines - the " Showing 48 milestones" is preceeded and followed by an empty line) I used in DOS batch file a FOR command with /F "skip=3 tokens=2" like below:
for /F "skip=3 tokens=2" %%i in (listMilestones.txt) do (
  echo Milestone %%i
  gh issue list --milestone "%%i"  --search "sort:updated-desc" --state "all" --repo "%1/%2"
  ::APPEND THIS TO SHOW JUST ISSUE NUMBER AND TITLE:  --jq ".[] | (.number|tostring)+\" \"+.title" --json number,title
  echo.
)

However, GitHub seems to have reused probably a deleted index number from a milestone that had been removed (though I don't remember removing one) for my 0.6.0 milestone, ending up in it using #20 and its previous and next ones using numbers 45 an 46 instead. Nevertheless they happen to sort fine in https://github.com/Zoomicon/READCOM_App/milestones?state=closed using the "Recently updated" Sort order (the default). Obviously if I edit an older one it will damage the sorting in that page. I don't see any way to sort semantically in that page either (nor to sort by creation date or index number of milestone), and that doesn't even have a way to show both open and closed ones (tried puttin ?state=all at the url with no success)
So semantic sorting is still useful to have, can't trust the number of the milestone as it seems that GitHub doesn't leave gap numbers if you delete a milestone (next one will use the gap number instead of the highest number + 1)

However, GitHub seems to have reused probably a deleted index number from a milestone that had been removed (though I don't remember removing one) for my 0.6.0 milestone, ending up in it using #20 and its previous and next ones using numbers 45 an 46 instead. Nevertheless they happen to sort fine in https://github.com/Zoomicon/READCOM_App/milestones?state=closed using the "Recently updated" Sort order (the default). Obviously if I edit an older one it will damage the sorting in that page. I don't see any way to sort semantically in that page either (nor to sort by creation date or index number of milestone), and that doesn't even have a way to show both open and closed ones (tried puttin ?state=all at the url with no success)
So semantic sorting is still useful to have, can't trust the number of the milestone as it seems that GitHub doesn't leave gap numbers if you delete a milestone (next one will use the gap number instead of the highest number + 1)


Some bug for fake stattrak.

1.Does not download automatically [https://prnt.sc/rhaitv] if you manually set it works.

I did not actually test the protobuf downloader. I have fixed the issue (eecb3219778bbefaa21a533df8af7e1b28379909), It should work now.

Since there are no further reports of this happening I am going to assume this has been successfully fixed.


Resolved thumbnail image rotation issue

Fixes #74

Thanks @khyativyasargus Have you tested it with the sensory app ? I think you need to also remove the screenOrientation from AndroidManifest!

Yes @MJ1998 , Yes I tested in sensory app and it works without removing screenOrientation!

Hey @khyativyasargus. I looked into Glide. Seems it automatically handles the exif rotation things.
Do you know why without providing the transform to glide it does not work ?


How to stop Hack from creating Events

Hi All,
Apologies if this has been asked before but is there any way to stop this hack from creating events i.e. mp4 files.
It's just that my SD card seems to fill up extremely quickly 16 GB.
If there isn't a way of stopping these events from occurring.  What's the easiest way to delete them (don't really want to go through the web-interface as it take ages to delete)
Thank you.

The hack is not responsible for this behavior. It's the main configuration made with the app.
But you could:

Disable che switch "Recording without Cloud".
Set a percentage in the "SD free space (%)" box.
Create a script and schedule with cron where you delete the files.

The hack is not responsible for this behavior. It's the main configuration made with the app.
But you could:

Disable che switch "Recording without Cloud".
Set a percentage in the "SD free space (%)" box.
Create a script and schedule with cron where you delete the files.

Thank you for the info.

Thank you for the info.


Dependency was not found after installed.

` ERROR  Failed to compile with 1 errors                                              friendly-errors 22:57:24
This dependency was not found:                                                       friendly-errors 22:57:24
friendly-errors 22:57:24

lazysizes in ./.nuxt/lazySizes.js`

buildModules
buildModules: [     '@nuxtjs/eslint-module',     '@nuxtjs/tailwindcss',     'nuxt-lazysizes',   ],

Hi, I just tested nuxt-lazysizes (v1.1.2) with the latest Nuxt (v2.14.12) and it works fine.
Can you provide a link to the repo or codesandbox?

I'm sorry for the misunderstanding. This problem solved after I reinstall the package and Its work fine.
+<EMAIL_ADDRESS>updated 1 package and moved 1 package in 7.016s
But I don't know why when adding lazyload class. It's showing a broken image icon and text 'Background' when I hover on it. (The images work on the second hover but sometimes it's not working for the first time.)
https://user-images.githubusercontent.com/20911264/102835157-896dff00-4428-11eb-97df-e6ca1e98ee09.mp4

But I don't know why when adding lazyload class. It's showing a broken image icon and text 'Background' when I hover on it. (The images work on the second hover but sometimes it's not working for the first time.)

Not sure, but I don’t think it’s directly related to the package.

Edit1: I share the repo through your email.

Please create a reproduction (link to the code) that shows the issue.

I'll close the issue due to inactivity. Feel free to reopen it with an attached link to a minimal reproduction that shows the issue.


CSUB-699: Remove switch_to_pos() extrinsic b/c mainnet has now been migrated to PoS

keep storage item b/c it is important
remove related tests and test jobs

Description of proposed changes

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #1289 (3eb112a) into dev (bae0fca) will decrease coverage by 61.94%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev   #1289       +/-   ##
==========================================
- Coverage   70.25%   8.32%   -61.94%
==========================================
  Files         103      28       -75
  Lines       12157     889    -11268
  Branches      114     114
==========================================
- Hits         8541      74     -8467
+ Misses       3607     815     -2792
+ Partials        9       0        -9

see 83 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Split the click groups and commands into separate modules

TO DO
To simplify maintenance and future changes, it's need to implement more complex code structure.
As help references:

https://click.palletsprojects.com/en/latest/quickstart/#nesting-commands
https://stackoverflow.com/questions/34643620/how-can-i-split-my-click-commands-each-with-a-set-of-sub-commands-into-multipl

Now package structure is
playlist_along
│   cli.py
│   playlist.py
│   py.typed
│   _utils.py
│   __init__.py
│   __main__.py
│
├───commands
│   │   convert.py
│   │   display.py
│   │   __init__.py


Add default middleware to patch location of tenantId for MS Teams

Fixes #884
Description
This change handles the in-transition locaiton of the tenant ID field for MS Teams.
Specific Changes
Load a middleware in the constructor for BotFrameworkAdapter that will look for channelData.tenant.id and copy the value to conversation.tenantId for use in createConversation.
Testing

Unit tests have been updated
Connect a bot to MS Teams, then use adapter.createConversation to create a DM with a user.

NOTE: I fixed this with a middleware because it seemed like this was the LEAST disruptive place to put code that will only be needed until the protocol change happens.
The other possible place to do this would be inside processActivity, which seemed less good.

Pull Request Test Coverage Report for Build #2208

3 of 5 (60.0%)  changed or added relevant lines in 1 file are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.005%) to 88.292%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

libraries/botbuilder/src/botFrameworkAdapter.ts
3
5
60.0%

Files with Coverage Reduction
New Missed Lines
%

libraries/botframework-config/src/botConfigurationBase.ts
2
85.59%

Totals

Change from base Build #2206:
0.005%

Covered Lines:
3241

Relevant Lines:
3528

💛  - Coveralls


Fixes #6

Thanks!

I won't be at my computer with this code for awhile but I'll push a new version to npm later today.

No worries ;) Thanks a lot!

1.0.3 is now on npm


Can't specify embedding model via API?

I've setup a txtai with the following configuration.
# config.yml
writable: true

embeddings:
  content: true
  defaults: false

  indexes:
    minilm:
      path: "sentence-transformers/all-MiniLM-L6-v2"

    nli:
      path: "sentence-transformers/nli-mpnet-base-v2"

I'm trying to get the vec embeddings of a given document using the API but cannot figure out how to specify the desired model, e.g.
curl -X GET "http://localhost:8000/transform?text=hello&index=nli"

Thank you for the write up on this.
Currently, the Embeddings instance doesn't have support for specifying the target index to use for the transform function. This would be a straightforward change and we can leave this issue open to add it in.


cargo-deny: 0.13.5 -> 0.13.7

Diff: https://github.com/EmbarkStudios/cargo-deny/compare/0.13.5...0.13.7
Changelog: https://github.com/EmbarkStudios/cargo-deny/blob/0.13.7/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Can we have a backport release-21.11 label on this one?

NVM, I opened a backport PR.

Argh... sorry. I will close mine!


Grammar in the README.md file

Greetings!
In the README.md file on line 8, the sentence, "Issues with the cascade can be the bane of their existence for many when it comes to CSS" should be changed to "Issues with the cascade can be the bane of the existence for many when it comes to CSS"

This applies to 'the many' and thus doesn't sound wrong to me. Just like mosquitos can be "the bane of my existence".
I will close this, but feel free to open a PR if you feel strongly about this or think I'm incorrect, since English is not my first language.


[full-ci] Minor changes to README to trigger CI

I want to see which CI pipelines are failing on current master.

One of the drone acceptance test pipelines failed: https://drone.owncloud.com/cs3org/reva/2578/8/4
pkg/storage/fs/s3/s3.go:31:2<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>403 Forbidden
pkg/storage/fs/s3/s3.go:32:2<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>403 Forbidden
pkg/storage/fs/s3/s3.go:33:2<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>403 Forbidden
pkg/storage/fs/s3/s3.go:34:2<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>403 Forbidden
pkg/storage/fs/s3/s3.go:35:2<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>403 Forbidden
pkg/storage/fs/s3/s3.go:36:2<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>403 Forbidden
/go/pkg/mod/github.com/nats-io/nats-server/v2@v2.9.16/server/events.go:32:2<EMAIL_ADDRESS>reading<EMAIL_ADDRESS>403 Forbidden

"something happened" with fetching from GitHub. This looks to be an intermittent problem.

One of the GitHub workflows failed in the Clean step: https://github.com/cs3org/reva/actions/runs/5817147292/job/15771424809?pr=4108
failed to remove network docker_default: Error response from daemon: error while removing network: network docker_default id be14571debb3e2ca56fd3db9340c66c74339ddd40f190f313ee90fc807b55b73 has active endpoints

But the actual tests passed.

This was just for a test of CI in the master branch - closing.


Saving a notebook doesn't work on VS Code Insiders

Version: 1.47.0-insider
Commit: d5e9aa0227e057a60c82568bf31c04730dc15dcd
OS: macOS Catalina (10.15.5)
Extension version: 2020.7.93499-rc
Steps to reproduce

Command palette > Python: Create New Blank Jupyter Notebook
Add content to the notebook
Save the notebook somewhere

Expected behaviour
The notebook's content gets saved
Actual behaviour
The saved notebook reopens but is empty, content is lost.

Closing as this was not reproducible.
Possibly an issue related to VSC Insiders or the like.


Expanding with editGPT

The add in is working great and has increased my productivity already. However - with the polish feature, it is not always easy to track the changes made. Here, the editGPT add in has an extremely smooth solution, to a large extent mirroring the track changes feature in word. Would it be possible to implement this as an overlay for the polish feature in ChatGPTBox?

It may require a lot of code refactoring, and even with a planned addition of this feature, it won't be quick.


Better error message/logging for Subscriptions with missing URLs

if a Subscription specifies a channel of rest-hook, but no URL, it will silently be ignored, and nothing is logged. This makes it hard to debug when a subscription is not firing

This is fixed by #2437 for now


Does nothing on vite 3.0.3

I'm using latest version: 0.2.5. With Vite 2.9 it works seamlessly
import react from '@vitejs/plugin-react'
import { fileURLToPath, URL } from 'url'
import { defineConfig } from 'vite'
import { chunkSplitPlugin } from 'vite-plugin-chunk-split'
import tsconfigPaths from 'vite-tsconfig-paths'

const splitConfig: any = {
  strategy: 'single-vendor',
  customSplitting: {
    'react-vendor': ['react', 'react-dom', 'react-router-dom'],
    'ionic-react-vendor': ['@ionic/react'],
    'ionic-react-router-vendor': ['@ionic/react-router'],
    'side-effects-vendor': [/src\/state/]
  }
}

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react(), tsconfigPaths(), chunkSplitPlugin(splitConfig)],
  resolve: {
    alias: {
      '@': fileURLToPath(new URL('./src', import.meta.url))
    }
  }
})

Can you provide a example project to preproduce the problem? I found it works in the project initialized by vite-cli.

Sorry, not at the time, but it is reproducible when you use @ionic/react package

Finding similar, React 18, Ionic, Vite 3.0.8. Tried just the example with the react-vendor.
Before:
➜  rm -rf build && yarn build
yarn run v1.22.18
$ tsc --noEmit && vite build
vite v3.0.8 building for production...
✓ 590 modules transformed.
build/index.html                          1.05 KiB
build/assets/swipe-back.b38f4a88.js       0.65 KiB / gzip: 0.45 KiB
build/assets/status-tap.696bf4f4.js       0.47 KiB / gzip: 0.33 KiB
build/assets/index10.86b21fec.js          1.79 KiB / gzip: 0.88 KiB
build/assets/input-shims.9072cc79.js      4.44 KiB / gzip: 1.93 KiB
build/assets/md.transition.e8122942.js    0.92 KiB / gzip: 0.50 KiB
build/assets/web.b7cabcff.js              0.35 KiB / gzip: 0.24 KiB
build/assets/ios.transition.4ba8ffef.js   9.19 KiB / gzip: 2.60 KiB
build/assets/index.d015e152.css           31.42 KiB / gzip: 6.06 KiB
build/assets/swiper.bundle.a76d5250.js    93.45 KiB / gzip: 25.24 KiB
build/assets/index.6edf5f23.js            1972.70 KiB / gzip: 519.72 KiB

(!) Some chunks are larger than 600 KiB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/guide/en/#outputmanualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✨  Done in 16.65s.

After:
➜  rm -rf build && yarn build
yarn run v1.22.18
$ tsc --noEmit && vite build
vite v3.0.8 building for production...
✓ 590 modules transformed.
build/index.html                         1.13 KiB
build/assets/swipe-back.0ca92795.js      0.65 KiB / gzip: 0.46 KiB
build/assets/index10.8e1fac96.js         1.79 KiB / gzip: 0.88 KiB
build/assets/status-tap.0fb7f632.js      0.47 KiB / gzip: 0.34 KiB
build/assets/web.6f60cc13.js             0.35 KiB / gzip: 0.24 KiB
build/assets/input-shims.9ecdd870.js     4.45 KiB / gzip: 1.94 KiB
build/assets/index.d015e152.css          31.42 KiB / gzip: 6.06 KiB
build/assets/index.f703b555.js           67.40 KiB / gzip: 18.66 KiB
build/assets/swiper.bundle.a76d5250.js   93.45 KiB / gzip: 25.24 KiB
build/assets/vendor.c6e65f37.js          1916.38 KiB / gzip: 503.39 KiB

(!) Some chunks are larger than 600 KiB after minification. Consider:
- Using dynamic import() to code-split the application
- Use build.rollupOptions.output.manualChunks to improve chunking: https://rollupjs.org/guide/en/#outputmanualchunks
- Adjust chunk size limit for this warning via build.chunkSizeWarningLimit.
✨  Done in 16.26s.

same. It does not work on vite 3.
Are you going to fix it @sanyuan0704  ?

I need to find the reproduction way.

I need to find the reproduction way.

OK，i have resolved the problem now.The reason is that vite 3.0 exposes pure esm format only.I have adopt it in latest plugin version.


Quality control

Hello, awesome work on automatic data generation! I believe the high quality of generated data, as mentioned in your paper (91% reasonable for instruction and 85% accurate for response). Despite the high quality, have you tried any further methods to filter the generated data? In particular, when running large-scale data generation, manual checking is infeasible and how to control the quality of the final dataset becomes a noticeable issue.

Thanks for your comments. We manually check the training set again and update the training set.


Update tapir-enumeratum, tapir-json-circe, ... to 1.9.10

About this PR
📦 Updates

com.softwaremill.sttp.tapir:tapir-enumeratum
com.softwaremill.sttp.tapir:tapir-json-circe
com.softwaremill.sttp.tapir:tapir-pekko-http-server
com.softwaremill.sttp.tapir:tapir-swagger-ui-bundle

from 1.9.4 to 1.9.10
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.tapir" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.softwaremill.sttp.tapir" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #553.


len() builtin function

Need the len() builtin function for getting the length of arrays.

Closing because #578


Update model.js

Modern Sequelize doesn't have findById anymore, so, we need to change this to add support to findByPk function.

I agree that we need to support findByPk and it should replace it. but this is another functionality.
primary key is not always id. Pk column can be called in many names (id, UUID, ID).
also we need to refactor the tests if we are changing the function name.


Refactor Survival Extrapolation

Goal is to calculate the revision risk at each cycle in the model. Data originally come from a weibull distribution. Dealing with this type of survival data will be a common problem in economic evaluations. When extrapolating a parametric survival function over the time horizon there are three steps: i) defining the parameters for the underlying distribution, ii) estimating the CDF, and iii) calculating the survival function (probabilities) from the CDF.
Goal is to refactor code to make the steps involved in extrapolating survival clearer!
https://github.com/dan-wagner/DMHEE_THR/blob/9d9a7a70c9627ca6a8e37106c5a2c3d46fbb8f0b/src/FUNS/Model-Parameters_Time-Dependencies.R#L24-L79

Key to solving this issue is making sure the correct implementation of the above-mentioned sequence:

Obtain the parameters for the distribution of interest. In this case, data were fitted to a parametric survival model with a Weibull distribution with proportional hazards assumption.
Build the model's cumulative distribution function. This is the step where the data are extrapolated over the model's time horizon. Can be achieved by supplying the parameters to the relevant distribution function with the p prefix. Given future requirements, need to generate the CDF at the beginning and end of each cycle.
The survival function, S(t), is the complement of the CDF.
Calculate the ratio of S(t) at the beginning and end of each cycle.


DotenvBootloader::loadEnvVariables is not called anymore after Update 2.9 -> 3.1

Description
After upgrading to spiral/framework 3.1, the DotenvBootloader::loadEnvVariable is not called anymore.
The bootloader is registered, DotenvBootloader::init() is called. It seems that $runningCallbacks is missing the closure when $this->fireCallbacks is called.
How To Reproduce
class App extends Kernel
{
    protected const LOAD = [
...
        DotEnv\DotenvBootloader::class,
...
]
}

Additional Info
Changing DotenvBootloader::init to
    public function init(
        AbstractKernel $kernel,
        DirectoriesInterface $dirs
    ): void {
        $kernel->booting(fn (EnvironmentInterface $env) => $this->loadEnvVariables($dirs, $env));
    }

everything works as expected again.

Q
A

Framework Version
3.1.0

PHP version
8.1.2

Operating system
Linux

Is the problem solved?

Hey @butschster,
thanks for your reply!
I am still investigating right now. Oddly enough it seems to work during the CI pipeline but not local.
A dump $callbacks in AbstractKernel::fireCallbacks() list all closures but not the dotenv clousure.

Move the bootloader like in the last version of spiral/app https://github.com/spiral/app/blob/master/app/src/App.php#L29

That apparently fixes the issue! I changed the documentation accordingly in https://github.com/spiral/docs/pull/355


Add Archana's patch on libcontainers-common back.

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[ ] The toolchain has been rebuilt successfully (or no changes were made to it)
[ ] The toolchain/worker package manifests are up-to-date
[ ] Any updated packages successfully build (or no packages were changed)
[ ] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[ ] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[ ] All package sources are available
[ ] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[ ] LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
[ ] All source files have up-to-date hashes in the *.signatures.json files
[ ] sudo make go-tidy-all and sudo make go-test-coverage pass
[ ] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Recent merge from 2.0, removed this patch and failing fasttrack/2.0 build.
Change Log

Change
Change
Change

Does this affect the toolchain?

YES/NO
NO
Links to CVEs

https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

Pipeline build id: xxxx

Please clean-up the summary and reference the original PR (#9888) we're restoring here.

Auto cherry-pick results:

main :white_check_mark: -> Skipped

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=619257&view=results


Feature: Anonymous voting

I noticed in the code there are some references to user but in UI I could not see anything related to users who voted for each category.
Does this plugin support (or plan to support) both anonymous and not anonymous kinds of polls?
By not anonymous I mean for example showing the list of users who voted for each option next to it in the results view.

I would really like to have this possibility to vote anonymously  too. :+1:

+1 for this feature

+1 for me as well

+1 for this feature


Serde OffsetDateTime as Unix timestamp

I need to de/serialize OffsetDateTime from/to Unix timestamps.
For that purpose I wrote a module for use in combination with serde's with-annotation.
Would such a module be in scope for this project? If yes, I would happily create a PR.

As I'm sure you can imagine, different people have different needs for serialization. With time v0.2, a round-trip ser/de actually loses information, as the UtcOffset isn't encoded. This would also be the case with using Unix timestamps. The v0.3 branch has changed ser/de to use the defaults, essentially, which doesn't lose any information.
My recommendation would be to have a wrapper struct, which would allow you to implement Serialize and Deserialize as you need. Assuming you implement Deref, it would also be mostly transparent. You'd also only need to use this when necessary, and could fall back to an OffsetDateTime for nearly all purposes.

Thanks for the fast response!
I just wanted to know if this clearly alternative approach to de/serialization would be useful for addition to this project. I did not intend to replace the default. Modules fulfilling the requirements of serde's with-annotation actually allow overriding the Serialize and Deserialize implementations per field without having to resort to a wrapper struct.
I am completely fine with this being out of scope of this project though.

I wasn't aware serde allowed for end-users to "override" the default, so to speak.
I'd be open to a pull request for the Unix timestamp on OffsetDatetime specifically, given it's probably one of the more common use cases. This can be based on master and not v0.3, as it would be safe to add as non-default.


BREAKING CHANGE: remove eye.pl APIs

This is a PR that removes the eye.pl APIs. Leaving this as draft until we are confident there are no usages for those APIs; we may also wish to bundle in another couple of breaking changes at the same time. These further breaking changes include:

Getting a stricter typing applied to SWIPL which should happen once https://github.com/rla/npm-swipl-wasm/pull/8 is resolved
Targeting es2020 rather than es6 in the tsconfig

As it turns out, our use of .pvm lets us also make the files that users need about 3x smaller as we no longer need to include the .data file from npm-swipl-wasm (as per https://github.com/SWI-Prolog/swipl-devel/pull/1088#issuecomment-1375059941). This is a bit more reasonable for browsers to load now
Here
452K Jan  9 14:58 eye.js
2712K Jan  9 14:58 swipl-bundled.temp.js

On Main
452K Jan  9 14:58 eye.js
10429K Jan  9 14:58 swipl-bundled.temp.js

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature Preview Component

Per: https://github.com/skeletonlabs/skeleton/issues/783
Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
This will be a new component that allows us to quickly show an interactive example a feature (ex: accordion), while also being able to quickly toggle and reveal the code powering the snippet.
Notable features include:

[x] Preview an interactive example of a component or feature
[x] Ability to toggle to view the code required for that specific demo
[x] Background color selection, to preview in different themes and environments
[x] Responsive breakpoint settings for mobile/table/full

What type of pull request would this be?
New Feature
Any links to similar examples or other references we should review?
This is a common feature on most UI library sites. A few examples are provided below:
Radix

Flowbite

DaisyUI

Tailwind UI

Good progress made on this today. This can be previewed here:
Some early work in progress screenshots:

I've adjusted the design a bit. This should now be ready to test and merge asap.
https://user-images.githubusercontent.com/1509726/221278006-520713a3-e80c-4b04-920d-bcfb7e2fad06.mp4

FYI I've updated the Svelte > Components from Accordion to Avatars to use the new preview component. This includes a few tweaks and adjustments to the styling and features. I'll aim to return to this on Sunday and update the rest of the pages to use the new component. Once that's done I'll merge and the doc content audit process can begin with our volunteers!
In the meantime, please feel free to submit feedback for this new component. The sooner the better!

Preview components now support a means to use dynamic variants:
https://user-images.githubusercontent.com/1509726/221692341-b7daa811-00ef-4b66-ad37-b28c859ee6cb.mp4
Additionally I've updated the navigation under the Docs section a bit, move tokens over, and added a new top-level Variants documentation section.

With this I'm going to consider this done and merge into dev branch. We welcome additional test for these changes leading up to release though. Thanks!


Add version to code

Love the driver, thanks.  I was updating it but I realized I can't really tell afterwards if i did or not since you don't have a version history in the source.  Please add it.  While you're at it, update the copyright to say 2019-2020.  That's what I was looking for in absence of a version changelist.

Latest versions now have version number.  Best way to get code is now through Hubitat Package Manager.


fix to catch last entites

Small change to catch entities that go up until last character when there is no tag (i.e. it is an '' (empty string) which will evaluate to False)

@ivyleavedtoadflax

Thanks for this @pimmeerdink, I will look into this.

Hmm i'm not sure why the CI has failed to run on this after all this time. Will try to kick start it now.

I just want to write a test for this, then i will merge - thanks again @pimmeerdink


feat(Scaling): add an example to show uniform object scaling - issue #31

Add an example to demonstrate uniform object scaling with two controllers.

Thanks for this PR, it's something that I am going to look at making part of the toolkit.
so at the moment there is an Is Swappable flag on the Interactable Object which basically means if you grab the object with the second controller then the grab swaps to the second controller (and the first controller is no longer grabbing).
my plan is to remove the Is Swappable flag and replace it with a Other Controller Grab Action (working title :p)
And the options can be:

Do Nothing = You cannot do anything with the other controller on grab (same as not swappable)
Swap Grab = You swap the grab action to the new controller (same as is swappable)
Scale Object = You scale the object based on the distance between the new controller (what you've done)
Control Direction = The object will follow the direction of the second controller (like a basic two hand grab of like a cue or a gun)

This will mean that the scale solution won't need to be implemented in a custom script and will be done out of the box :)

Sounds very reasonable.
I think this type of functionality should be part of the toolkit versus an example as implemented in this PL. I did a pass as an example as a quick way of showing a simple / quick implementation that minimized deeper changes to the toolkit and as a way to kick off discussion on how to better integrate a final version --  I think the solution you propose sounds good and seems to include two handed rotation when using "Control Direction".
In the short term this could still be a useful example to include and just remove once Other Controller Grab Action gets implemented (especially if it's not high priority).

I'm definitely using the code in this pr :) as both reference and to copy and paste! :)

Excellent!

Superseded by https://github.com/thestonefox/VRTK/pull/711
If you can take a look at the above PR and see if you can iron out any of the glitches then that would be great!

Hello,
Sorry about the delay (finishing up some other work). I see you closed the
issue. Anything else need for this?
On Wed, Nov 2, 2016 at 2:49 AM, StoneFox<EMAIL_ADDRESS>wrote:

Superseded by #711 https://github.com/thestonefox/VRTK/pull/711
If you can take a look at the above PR and see if you can iron out any of
the glitches then that would be great!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/thestonefox/VRTK/pull/682#issuecomment-257818260, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AABQXB61ZLnp6EhWplt9yxRXirnZqiLLks5q6FyigaJpZM4Kdt6l
.

--
Serban Porumbescu
http://hiddenelephant.com
http://twitter.com/serban

The new "secondary grab actions" has now been merged into master, one of the secondary grab actions is a scale.
If you want to take a look at it, perhaps look for ways to improve it too?


New Ascend readme

added graph mode and w4a16.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit tests to ensure the correctness.
If the modification has a dependency on downstream projects of a newer version, this PR should be tested with all supported versions of downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

linting faied. Please run the following commands to resolve it.
pip install pre-commit
cd lmdeploy # the root path of lmdeploy repo
pre-commit install
pre-commit run --all-files


Converting binary segmentations to point sets

Hi,
I am trying to use ICP for registration. I have binary segmentations as NIfTI images in the fixed and moving space. Is there a best practice for converting these to point sets? Ultimately I want to do something like
-m CC[ fixedT1.nii.gz, movingT1.nii.gz, 0.5, $radius ] -m ICP [fixedPoints.EXT, movingPoints.nii.EXT, 0.5, 1]
Thanks

Hi phil
Unfortunately I think this isn't properly implemented yet.
A meansquares metric will have to suffice.
On May 4, 2015 3:35 PM, "Philip Cook"<EMAIL_ADDRESS>wrote:

Hi,
I am trying to use ICP for registration. I have binary segmentations as
NIfTI images in the fixed and moving space. Is there a best practice for
converting these to point sets? Ultimately I want to do something like
-m CC[ fixedT1.nii.gz, movingT1.nii.gz, 0.5, $radius ] -m ICP
[fixedPoints.EXT, movingPoints.nii.EXT, 0.5, 1]
Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/183.

I've used marching cubes from tvtk and it has worked well.  You can also
decimate and smooth point sets.
2015-05-04 18:39 GMT-04:00 stnava<EMAIL_ADDRESS>
Hi phil
Unfortunately I think this isn't properly implemented yet.
A meansquares metric will have to suffice.
On May 4, 2015 3:35 PM, "Philip Cook"<EMAIL_ADDRESS>wrote:

Hi,
I am trying to use ICP for registration. I have binary segmentations as
NIfTI images in the fixed and moving space. Is there a best practice for
converting these to point sets? Ultimately I want to do something like
-m CC[ fixedT1.nii.gz, movingT1.nii.gz, 0.5, $radius ] -m ICP
[fixedPoints.EXT, movingPoints.nii.EXT, 0.5, 1]
Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/183.

—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/183#issuecomment-98874828.

You can use itk::BinaryMask3DMeshSource :
// The label you want to get the points for
LabelImageType::PixelType labelValue;
typedef itk::Mesh MeshType;
typedef itk::BinaryMask3DMeshSource< LabelImageType, MeshType >
MeshSourceType;
MeshSourceType::Pointer meshSource = MeshSourceType::New();
const LabelImageType::PixelType objectValue =
static_castLabelImageType::PixelType (label);
meshSource->SetObjectValue(objectValue);
// labelImage is your binary segmentation
meshSource->SetInput(labelImage);
// You can speed up by first finding a tight bounding box of your label
and setting that
// instead of Largest Possible region
meshSource->SetRegionOfInterest(labelImage->GetLargestPossibleRegion());
// Get the mesh
try
{
meshSource->Update();
}  catch (itk::ExceptionObject & exp)
{
std::cerr << "Exception thrown during Update() " << std::endl;
std::cerr << exp << std::endl;
return;
}
std::cout << "Label = " << objectValue << std::endl;
std::cout << "Nodes = " << meshSource->GetNumberOfNodes() << std::endl;
std::cout << "Cells = " << meshSource->GetNumberOfCells() << std::endl;
// Convert to vtkPolyData for Visualization
if(meshSource->GetNumberOfNodes() > 0)
{
typedef itk::MeshToVTKPolyData MeshToVTKFilterType;
MeshToVTKFilterType::Pointer mestTovtkFilter = MeshToVTKFilterType::New();
mestTovtkFilter->SetInput(meshSource->GetOutput());
mestTovtkFilter->Update();
vtkPolyData* pd = mestTovtkFilter->GetOutput();
}
Thanks,
Somesh
On Tue, May 5, 2015 at 10:06 AM, bkandel<EMAIL_ADDRESS>wrote:

I've used marching cubes from tvtk and it has worked well. You can also
decimate and smooth point sets.
2015-05-04 18:39 GMT-04:00 stnava<EMAIL_ADDRESS>
Hi phil
Unfortunately I think this isn't properly implemented yet.
A meansquares metric will have to suffice.
On May 4, 2015 3:35 PM, "Philip Cook"<EMAIL_ADDRESS>wrote:

Hi,
I am trying to use ICP for registration. I have binary segmentations as
NIfTI images in the fixed and moving space. Is there a best practice
for
converting these to point sets? Ultimately I want to do something like
-m CC[ fixedT1.nii.gz, movingT1.nii.gz, 0.5, $radius ] -m ICP
[fixedPoints.EXT, movingPoints.nii.EXT, 0.5, 1]
Thanks
—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/183.

—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/183#issuecomment-98874828.

—
Reply to this email directly or view it on GitHub
https://github.com/stnava/ANTs/issues/183#issuecomment-99087709.

@someshSandbox - does this produce a mesh that is in the correct physical space?
@cookpa - the issue is currently that the I/O and registration capabilities in antsRegistration lag what's available in old ANTS e.g.
guided registration
this has not been used (by us) for some time but is likely to still work.

and i do think that
antsRegistration ...   -m cc[ f, m ]   -m meansquares[ f_seg, m_seg ] ...

would suffice

@stnava As far as I know ,  itk::BinaryMask3DMeshSource generates Mesh is the same physical space ( I have used ITK 4.3 and 4.5 and seems to work ok). I have even voxelized the mesh and overlaid over the original Image to check and found not issues. The following example displays both the mesh and the image slice http://itk.org/ITKExamples/src/Core/Mesh/ExtractIsoSurface/Documentation.html .

Thanks for all the suggestions, everyone. I'll revisit this when ICP is working, for now I will go with the label images using a mean squares metric.
On May 5, 2015, at 11:11 AM, Somesh Kashyap<EMAIL_ADDRESS>wrote:

@stnava As far as I know , itk::BinaryMask3DMeshSource generates Mesh is the same physical space ( I have used ITK 4.3 and 4.5 and seems to work ok). I have even voxelized the mesh and overlaid over the original Image to check and found not issues. The following example displays both the mesh and the image slice http://itk.org/ITKExamples/src/Core/Mesh/ExtractIsoSurface/Documentation.html .
—
Reply to this email directly or view it on GitHub.


Fix typo in experiments created with 'magpie new'

Currently, it says:
<!-- While developing your experiment, using the DebugResults screen is fine,
  once you're going live, you can use the <SubmitResults> screen to automatically send your experimental data to the server. -->

It should be:
...  ...

Ah, that one slipped through. Fixed. Will be released together with the next fix.


adding flake8

added flake8 yml and workflows directory
#5

Amended

@RonTuretzky please add the pipfiles otherwise we don't have flake8 to work with it


Greater Orb of Regret issue is back

Hey, it's Sideralis, remember the issue with the Greater Orb of Regret when this mod first came out? It's back now but only with the Healing stat specifically. The issue is that if you have any points in Healing, you have to refund those first or you won't be able to refund any other points back after using a Greater Orb of Regret and if you only have points in Healing, then you can't refund those at all until you put points into the PlayerEx tab.

Uhhh okay I'll get it fixed in the next two days. I'm sorry I've hardly been on my computer since the new job. I remember the author of origins fixed the issue last time, I'll check back on his commit and see what he did / check our messages on Curseforge and figure it out.


update jQuery webpack integration to select which parts we want

We can do this in v3 without hacks but for now:
resolve: {
    alias: {
      jquery: "jquery/src/jquery"
    }
  },

and http://alexomara.com/blog/webpack-and-jquery-include-only-the-parts-you-need/

Blocked until v3 launches

This now needs looking into as V3 has launched.

Is this needed? if Jquery is required in a project, I'd probably want the whole thing included anyway.

Wontfix. jQuery usage is being phased out as per comment above.


Can no longer start/continue a run when AdvancedCompany is present

Describe the bug
As of more recently, I've been unable to start/continue a run at all after hitting "Continue".  My console seems to hang with a specific error (see screenshot below) and never proceeds to starting a run. I am able to quit out of the preset menu, but that does not fix the issue of the continue button not proceeding to a run. I believe something for AC got corrupted when my PC was forcefully shut off due to my power going out.
To Reproduce
Steps to reproduce the behavior:

Go to the preset menu and try to edit some values.
Have the PC forcefully shut off in some way.
Boot up the game again like normal.
Attempt to start/continue a run.
Check console and see if the game hangs due to a specific error.

Expected behavior
Should be able to start/continue a run like normal after I hit "Continue" on the preset screen.
Screenshots
My console seems to hang at this error shown below:

Additional context
I thought at first this issue was occurring due to a mod incompatibility with my usual group pack
Code: 018d7b20-82c9-7665-9c33-59e70928e8ef
At the time this bug occurred, I was editing the spawn weights of the "Immortal Snail" enemy on all maps.
During this time I had a nasty thunderstorm occurring and it knocked out my power for several hours.
After enough testing via disabling mods, I finally ruled out that AC seems to be the one causing the issue to hang when trying to start runs, as the profile linked below (that does NOT use AC) can start/continue a run just fine.
Code: 018d7b25-d244-721d-8a9f-70b957a41840
Logfiles
Player.log
Add a list of all of your mods
BepInEx-BepInExPack-5.4.2100
Rune580-LethalCompany_InputUtils-0.6.3
PotatoePet-AdvancedCompany-1.0.148

Apologies for the immediate update but I managed the fix the issue, here's what I did to fix it:
I went to where the game's log files are stored as I noticed there's files tied to advancedcompany stored here as well, I deleted these and rebooted the game to regenerate them, and that's seem to fix the issue.
Directory for the game log files being this one: %AppData%..\LocalLow\ZeekerssRBLX\Lethal Company


[WIP] Check slot bounds. Fixes #409

Although I failed to reproduce the error as the mod in the issue doesn't seem to activate on a server without the serverside component. I do however believe this safety check will solve the issue of invalid clicked slots being sent to the server. The player will be kicked as @Mumfrey indicated this is to be treated as an exploit.

This needs a clean way to reverse the click event so the items don't end up dropped on the ground.

This is un-needed as it was simply the wrong container being checked.


text.replace() isn't a function

Idk why this text.replace() error is comming for code blocks from md to html?

Can you give more detail? It's difficult to figure out what you're talking about from:

Idk why this text.replace() error is comming for code blocks from md to html?

Are you talking about extensions? A random showdown error?
A complete code example demonstrating the issue would be ideal.

I think what happened was that he provided the argument incorrectly
like if you put in undefined, obviously the output would be an error.

No i didnt eneterd undefined or others i just did
const showdown = require('showdown')
const converter = new showdown.converter()

console.log(converter,makeHtml('```js\nconst test = 'test'\n```'))

I eneterd this sample code

@Scientific-Guy  '```js\nconst test = 'test'\n```' is not a valid string. Also, test is undefined.

Thats just a string not a code so it wont matter its defined or undefined. And it is supposed to make a html

I'm trying to say that the code you posted is invalid. It produces a syntax error.

Uhmmm np i figured some other way


Update Composer dependencies (2022-10-18-00-06)

Visual regression test passed!
View the visual regression test report


Refactor dataloading

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos, doc improvements)
[ ] Did you read the contributor guideline?
[ ] Did you make sure to update the docs?
[x] Did you write any new necessary tests?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

What does this PR do?
Fixes #953 Fixes #840 Fixes #698

Refactored calls to reset_train_dataloader and reset_val_dataloader to only happen when needed
Slightly changes the logic for disable validation to ignore the validation_dataloader length
Removed default unpacking of dataloader and adding of RandomSampler - see comment in #953
Changed Exception order so that MisconfigurationException will be called and given when using IterableDataset
Removed dependency on Dataloader.dataset following #840
num_training_batches =float('inf') is now the default when train dataloader doesn't have __len__ (in addition to when using an IterableDataset)
Added test for training using an iterable

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

@ethanwharris nice job.
I'll merge this, then fix the TPU stuff then you can add what @Darktex suggested!
Running GPU tests now


species_id

Thanks for publishing this, it is too bad it is not available via the Data Catalogue. Going forward, I'll grab WHSE_FISH.SPECIES_CD from this csv.
To make things a bit easier when querying by species in postgres, it would be nice to have a species_id column. I see there is already an integer column in https://github.com/poissonconsulting/fishbc/blob/master/data-raw/whse_fish_species_cd/whse_fish_species_cd.csv, it just lacks a name in the header.  Would it be reasonable to label this column as species_id and use it as the primary key?

closed by pull request #2


chore(documentdb): Change checks IDs to match with metadata

Context
Current DocumenDB checks do not match name of the class and metadata name.
Description
Changed name to match in checks:

documentdb_cluster_backup_enabled
documentdb_cluster_deletion_protection_enabled

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Close this PR in favor of #4522


Pretrained models and train dataset of 3DMatch

I am interested in your excellent work, and I want to know 1) what are the differences between your processed training dataset of 3DMatch and the training dataset provided by PREDATOR; 2) could you please provide the pre-trained models on 3DMatch to reproduce the results?

Hi, @Pterosaur-Yao , thanks for your interest in our work!

The 3DMatch training set we processed is almost the same as the PREDATOR, the only difference should be the subsampling. To enhance computational efficiency, we subsampled the raw fragments with voxel size of 1.5cm instead of directly using the raw dense fragments.

Sorry for the inconvenience, I missed this file in the previous upload. Now I have updated the project.

Best,
Sheng

Thank you, Sheng. I'm interested in how the method performs on the rotated 3DMatch dataset,  could you please provide a test script or tell me how to modify the test file?

To evaluate the rotated 3DMatch dataset, maybe you can add an arbitrary rotation for each pair of fragments in https://github.com/aosheng1996/BUFFER/blob/8c5d6c7772e5b8c5ae70e8c568ce1545c7d976d5/ThreeDMatch/dataset.py#L121C15-L121C15 and update the 'relt_pose'.


[MS Teams] Sideloaded bot not discoverable for 1:1 chat

Bot Info

Bot handle: kirkaldy_KlvHehCPM5Z
App ID: 67a4826b-3d7e-44f4-8cfe-432868eff1e7
SDK Platform: Node.js
SDK Version: 3.9.1
Active Channels: MS Teams
Deployment Environment: Elastic Beanstalk

Issue Description
Sideloaded bot can be mentioned in team channel yet can't be invited to 1:1 chat by other members of the team, despite manifest.json including "personal" scope.
When opening a new chat, the bot is not available to be invited by anyone except the bot's admin.
What would I need to do to ensure 1:1 chat can be initiated by anyone in the team the bot is sideloaded to?

@wilcovanesch Did you follow all the steps to enable your bot on Teams channel?
How to load your bot into MS Teams
Quick MS Teams bot deployment checklist:

Did your O365 tenant administrator enable sideloading of apps for your organization?
Did you create an app package
Did you sideload your bot app into the relevant team?

Recommended reading:

Getting Started with Bots for Microsoft Teams
Create the package for your Microsoft Teams app - aka manifest.json file
Sideloading your app in a team
Testing your Bot

@wilcovanesch see also: https://msdn.microsoft.com/en-us/microsoft-teams/bots1on1

Yes, the app is side-loaded into the relevant team using an app package I validated against the manifest schema.
Each of those articles I've encountered in my journey, but so far haven't found anything in them to give me ideas on why the bot works in a Team context yet not in a 1:1 context with a member of the Team.

@wilcovanesch - how are other users trying to start a conversation with your bot?

They hit the New Chat icon and start typing the name of the bot. I've looked over their shoulders and it just doesn't come up with the bot name (despite them being members of the same Team the bot is side-loaded to).

@wilcovanesch - were you able to resolve this issue?

@Wajeed-msft - Unfortunately I haven't been able to resolve it.
I'd still be grateful for anyone's help on this.

@wilcovanesch - We side loaded your bot by creating a new manifest file. We are able to search the bot by name i.e. David Kirkaldy. This worked fine in Teams channel conversation as well as 1:1 conversation.
Could you please share your manifest.json so that we could have a look?

@Wajeed-msft - Many thanks. Hopefully you can find an issue with my manifest. Attached is the app package, containing the manifest.json and icons.
sideload.zip

@wilcovanesch - we were able to sideload your manifest and bot was discoverable by admin as well as members in both 1:1 and channel conversation.
I have attached manifest with a test bot ( name: MicrosoftTeamsFAQ). Could you please try to sideload this in your team and check if this is comming up when you search by name (MicrosoftTeamsFAQ)?
Also try a scenario where member (not owner) sideloads this app and check if it's discoverable in personal chat.
package.zip

Miraculously the bot is discoverable in 1:1 chats now, without having made any change to code or configuration. What I've found after giving more people access is that initially each individual is unable to find the bot, but it shows up after - for example - navigating to Teams and back to Chat. However, it does not show up if the user merely keeps trying the user search or lets it sit for any amount of time.
I'm closing this issue. Thanks for assisting me with it.


attributes rendering?

Hello,
does the attributes rendering are plan to be implemented?
thanks
cf https://github.com/hendrikmaus/reynaldo/issues/6

In Blueprint Doc's output, when you click on a request, you can see the defined body attributes. Where else and how would you like the attributes to be shown? Please attach a simple blueprint file for your use case.

Sorry, didn't see you PR. Thank you! Could you still attach a simple blueprint file for your use case and I'll check it out asap.

An example :
FORMAT: 1A
HOST: https://api.example.tld

# Foo

## Bar [POST /{language}/bar/]
+ Parameters
    + language: en (string) - the language of the user
+ Attributes
    + foo: 1 (number) - Your foo
    + bar: 7894 (string) - Your bar
+ Request (application/x-www-form-urlencoded)
    foo=1&bar=7894
+ Response 200

Hey @Grummfy,
I had a good look at attributes today and I think your blueprint is incorrect. Attributes are specific to requests or responses and should therefore be added inside respective sections. This is an example taken from the API Blueprint Advanced Tutorial:
### Create a New Question [POST]
You may create your own question using this action. It takes a JSON object
containing a question and a collection of answers in the form of choices.

+ Request (application/json)

    + Attributes

        + question: Favourite Language? (required)
        + choices: Swift, `Objective-C` (array, required)

They can be added higher up inside the action if referenced later inside a request or response section. This is API Blueprint's example 09. Advanced Attributes:
### Create a Coupon [POST]
Creates a new Coupon.

+ Attributes (object)
    + percent_off: 25 (number)
    + redeem_by (number)

+ Request (application/json)

+ Response 200 (application/json)
    + Attributes (Coupon)

When used with application/json the API Blueprint parser provides a JSON body and JSON Schema to render. As one of the API Blueprint authors Zdenek Nemec comments on a Stack Overflow question regarding support for application/x-www-form-urlencoded, MSON does not have url encoded support for rendering the MSON attributes, "you will still need to provide [the] body manually".
Rendering the upper level attributes (the data structure that the parser holds for referencing the attributes in later sections), as you do in your PR, is a workaround and breaks with API Blueprint's Attributes examples 09. Advanced Attributes.


Explicit Blob Storage URLs to bypass Proxy Intercept

Hi there,
We need to be explicit about which blob storage URLs can bypass TLS interception on our proxy. Is it possible to provide explicit blob storage hostnames for Azure Migrate? Excluding *.blob.core.windows.net is not secure.
Likewise, for dynamic firewall rules an explicit hostname is required
https://docs.microsoft.com/en-us/azure/migrate/migrate-appliance#public-cloud-urls
Thanks! Phil

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

ID: 7a4a21a9-fcda-355f-6668-21cd3adf25af
Version Independent ID: 659ad43a-882f-1510-36df-dd1d994b6a09
Content: Azure Migrate appliance - Azure Migrate
Content Source: articles/migrate/migrate-appliance.md
Service: azure-migrate
GitHub Login: @rayne-wiselman
Microsoft Alias: raynew

Thanks for the feedback @phillym! We are currently investigating and will update you shortly.

hello @phillym , from my internal research, there's currently no supported way to isolate & provide explicit blob storage hostnames for Azure Migrate. Also note that this approach may cause unexpected disruption as these hosts can be swapped for internal maintenance and/or service healing requirements at any time.
If this is a requirement you would like to see supported, kindky re-post your suggestion on the feedback portal. This allows the feature owners and the general user community to up-vote and comment on this suggestoin. This helps with prioritization against the existing feature backlog.
Cheers,
femsulu

We will now close this issue. If there are further questions regarding this matter, please reply and we will gladly continue the discussion.
#please-close


Implement NSArray.indexOfObject(inSortedRange:options:usingComparator)

Implement NSArray.indexOfObject(inSortedRange:options:usingComparator) and add test cases for it.

looks pretty reasonable to me passes on mac and linux


Restore jobs are not idempotent

@eliobischof is it still open and which milestone should it be assigned?

@eliobischof Is this issue still relevant? Or can we close this?

I'll reopen it if it becomes relevant again.


Abstracting classes simulation

we have a class for generating json and simulating a process so that we can have main cleared for testing and that we can keep this streamlined approach cleared in a specific abstracted class

small bug that needs to be fixed, will be added in next PR


Test multiple Ruby versions on CI

It would make sense to test multiple ruby versions in CI, starting with 2.0 up to current versions people might use.
Research:

AppVeyor/Windows: https://mattbrictson.com/how-to-test-ruby-windows
Circle CI: https://jtway.co/run-tests-against-multiple-ruby-versions-on-circleci-60e1e523e245

I think adding to the current circle CI configuration to test on multiple Ruby versions is a nice idea. Sometimes we receive PRs that add new functionality and is hard to know which operator or function was added in which Ruby version so I'm totally agreeing on this 😁


How does from_json work?

Sorry, I don't know if the question is right here, but I really needs help.
I need to convert json str to QString, and I defines the from_json function,
void from_json(const json& j, QString& str)
{
    str = QString::fromStdString(j.get<std::string>());
}

json object = {{"string","string"}};
then I code this ,
QString str = object["string"];
it works no problem.but when I code this,
QString str;
str = object["string"];

then the compiler do not know how to compile，error with
Error: C2593: "operator =" is not clear
Do non-built-in variables can not be pre-defined? (I tried int and double type，it can work，)

I think @theodelrieu could help here.

now I use
QString str;
str = object["string"].get<QString>();

to explicit type conversion, it can work. maybe
QString str = object["string"];
can do some implicit type conversion during compilation ? while I don‘’t understand why
QString str;
str = object["string"];

can't do that.
Thanks, I think this issue can be closed.

object["string"] returns a basic_json object which can implicitly convert to std::string. object["string"].get<QString>() explicitly converts to QString. I'm not sure whether QString implicitly converts from std::string though...
Happy to hear that your issue is solved. :-)