Can't relay packets between chains

When using Starship with the following configuration (Config below) I can create a channel but the packets inside the channel are not relayed.
I also paste the hermes-juno-stargaze logs from the channel creation (Hermes Pod Logs below).
I'm using a channel for Polytone which is a wasm to wasm channel
When I run hermes start the packet gets relayed correctly without issues
Expected behavior
I want starship to be able to create a channel and then relay the packets on it automatically without having to run hermes start manually
Investigation

When running hermes start inside the pod, the program successfully relays 1 packet but then proceeds to fail with the following error logs (Logs of hermes start when running from inside the pods to relay 1 packet below)

When creating a transfer channel, it works perfectly. I'm able to create a channel and the resulting packets get relayed perfectly

This might be related to gas limits on packets ?

Config:
chains:
  - id: stargaze-1
    name: stargaze
    numValidators: 1
    ports:
      rest: 1313
      rpc: 26653
      grpc: 30658
      faucet: 8000
  - id: juno-1
    name: juno
    numValidators: 1
    ports:
      rest: 1317
      rpc: 26657
      grpc: 30657
      faucet: 8001

relayers:
  - name: osmo-juno
    type: hermes
    replicas: 1
    chains:
      - stargaze-1
      - juno-1

explorer:
  enabled: true
  ports:
    rest: 8080

registry:
  enabled: true
  ports:
    rest: 8081

Hermes Pod Logs:
2024-06-17T09:28:35.621877Z  INFO ThreadId(392) worker.batch{chain=juno-1}:supervisor.handle_batch{chain=juno-1}:supervisor.process_batch{chain=juno-1}:worker.channel{channel=channel::channel-1/wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8:juno-1->stargaze-1}: 🎊  stargaze-1 => OpenTryChannel(OpenTry { port_id: wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3, channel_id: channel-1, connection_id: connection-0, counterparty_port_id: wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8, counterparty_channel_id: channel-1 }) at height 1-376
2024-06-17T09:28:35.621907Z  INFO ThreadId(392) worker.batch{chain=juno-1}:supervisor.handle_batch{chain=juno-1}:supervisor.process_batch{chain=juno-1}:worker.channel{channel=channel::channel-1/wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8:juno-1->stargaze-1}: channel handshake step completed with events: OpenTryChannel(OpenTry { port_id: wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3, channel_id: channel-1, connection_id: connection-0, counterparty_port_id: wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8, counterparty_channel_id: channel-1 })
2024-06-17T09:28:36.350994Z ERROR ThreadId(08) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.channel{channel=channel::channel-1/wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3:stargaze-1->juno-1}:send_messages_and_wait_commit{chain=juno-1 tracking_id=ChannelOpenAck}:send_tx_with_account_sequence_retry{chain=juno-1 account.sequence=10}:estimate_gas: failed to simulate tx. propagating error to caller: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 11, got 10: incorrect account sequence [cosmos/cosmos-sdk@v0.47.5/x/auth/ante/sigverify.go:269] With gas wanted: '100000000000' and gas used: '52577' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "155"} }
2024-06-17T09:28:36.351036Z  WARN ThreadId(08) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.channel{channel=channel::channel-1/wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3:stargaze-1->juno-1}:send_messages_and_wait_commit{chain=juno-1 tracking_id=ChannelOpenAck}:send_tx_with_account_sequence_retry{chain=juno-1 account.sequence=10}: failed to estimate gas because of a mismatched account sequence number, refreshing account sequence number and retrying once error=gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 11, got 10: incorrect account sequence [cosmos/cosmos-sdk@v0.47.5/x/auth/ante/sigverify.go:269] With gas wanted: '100000000000' and gas used: '52577' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "155"} }
2024-06-17T09:28:36.352655Z  INFO ThreadId(08) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.channel{channel=channel::channel-1/wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3:stargaze-1->juno-1}:send_messages_and_wait_commit{chain=juno-1 tracking_id=ChannelOpenAck}:send_tx_with_account_sequence_retry{chain=juno-1 account.sequence=10}: refreshed account sequence number old=10 new=11
2024-06-17T09:28:36.958678Z  INFO ThreadId(411) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.channel{channel=channel::channel-1/wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3:stargaze-1->juno-1}: 🎊  juno-1 => OpenAckChannel(OpenAck { port_id: wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8, channel_id: channel-1, connection_id: connection-0, counterparty_port_id: wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3, counterparty_channel_id: channel-1 }) at height 1-156
2024-06-17T09:28:36.958711Z  INFO ThreadId(411) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.channel{channel=channel::channel-1/wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3:stargaze-1->juno-1}: channel handshake step completed with events: OpenAckChannel(OpenAck { port_id: wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8, channel_id: channel-1, connection_id: connection-0, counterparty_port_id: wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3, counterparty_channel_id: channel-1 })
2024-06-17T09:28:36.970208Z  INFO ThreadId(08) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=juno-1->stargaze-1:07-tendermint-0}: No evidence of misbehavior detected for chain juno-1
2024-06-17T09:28:37.070329Z  INFO ThreadId(10) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}: client is valid
2024-06-17T09:28:37.828027Z  INFO ThreadId(07) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=stargaze-1->juno-1:07-tendermint-0}: No evidence of misbehavior detected for chain stargaze-1
2024-06-17T09:28:37.880447Z  INFO ThreadId(08) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=juno-1->stargaze-1:07-tendermint-0}: No evidence of misbehavior detected for chain juno-1
2024-06-17T09:28:37.928145Z  INFO ThreadId(13) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}: client is valid
2024-06-17T09:28:37.980560Z  INFO ThreadId(10) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}: client is valid
2024-06-17T09:28:38.989478Z ERROR ThreadId(07) worker.batch{chain=juno-1}:supervisor.handle_batch{chain=juno-1}:supervisor.process_batch{chain=juno-1}:worker.channel{channel=channel::channel-1/wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8:juno-1->stargaze-1}:send_messages_and_wait_commit{chain=stargaze-1 tracking_id=ChannelOpenConfirm}:send_tx_with_account_sequence_retry{chain=stargaze-1 account.sequence=11}:estimate_gas: failed to simulate tx. propagating error to caller: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 12, got 11: incorrect account sequence [cosmos/cosmos-sdk@v0.45.16/x/auth/ante/sigverify.go:265] With gas wanted: '100000000000' and gas used: '64323' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "380"} }
2024-06-17T09:28:38.989512Z  WARN ThreadId(07) worker.batch{chain=juno-1}:supervisor.handle_batch{chain=juno-1}:supervisor.process_batch{chain=juno-1}:worker.channel{channel=channel::channel-1/wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8:juno-1->stargaze-1}:send_messages_and_wait_commit{chain=stargaze-1 tracking_id=ChannelOpenConfirm}:send_tx_with_account_sequence_retry{chain=stargaze-1 account.sequence=11}: failed to estimate gas because of a mismatched account sequence number, refreshing account sequence number and retrying once error=gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 12, got 11: incorrect account sequence [cosmos/cosmos-sdk@v0.45.16/x/auth/ante/sigverify.go:265] With gas wanted: '100000000000' and gas used: '64323' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "380"} }
2024-06-17T09:28:38.990954Z  INFO ThreadId(07) worker.batch{chain=juno-1}:supervisor.handle_batch{chain=juno-1}:supervisor.process_batch{chain=juno-1}:worker.channel{channel=channel::channel-1/wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8:juno-1->stargaze-1}:send_messages_and_wait_commit{chain=stargaze-1 tracking_id=ChannelOpenConfirm}:send_tx_with_account_sequence_retry{chain=stargaze-1 account.sequence=11}: refreshed account sequence number old=11 new=12
2024-06-17T09:28:39.598115Z  INFO ThreadId(392) worker.batch{chain=juno-1}:supervisor.handle_batch{chain=juno-1}:supervisor.process_batch{chain=juno-1}:worker.channel{channel=channel::channel-1/wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8:juno-1->stargaze-1}: 🎊  stargaze-1 => OpenConfirmChannel(OpenConfirm { port_id: wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3, channel_id: channel-1, connection_id: connection-0, counterparty_port_id: wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8, counterparty_channel_id: channel-1 }) at height 1-381
2024-06-17T09:28:39.598143Z  INFO ThreadId(392) worker.batch{chain=juno-1}:supervisor.handle_batch{chain=juno-1}:supervisor.process_batch{chain=juno-1}:worker.channel{channel=channel::channel-1/wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8:juno-1->stargaze-1}: channel handshake step completed with events: OpenConfirmChannel(OpenConfirm { port_id: wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3, channel_id: channel-1, connection_id: connection-0, counterparty_port_id: wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8, counterparty_channel_id: channel-1 })
2024-06-17T09:28:40.593305Z  INFO ThreadId(08) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=juno-1->stargaze-1:07-tendermint-0}: No evidence of misbehavior detected for chain juno-1
2024-06-17T09:28:40.693419Z  INFO ThreadId(10) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}: client is valid
2024-06-17T09:29:27.045256Z  INFO ThreadId(12) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.refresh{client=stargaze-1->juno-1:07-tendermint-0}: client needs to be refreshed elapsed=50.62723062s refresh_window=50s
2024-06-17T09:29:27.065334Z ERROR ThreadId(08) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.refresh{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.build_update_client_and_send{client=stargaze-1->juno-1:07-tendermint-0 target_query_height=latest height}:send_messages_and_wait_commit{chain=juno-1 tracking_id=update client}:send_tx_with_account_sequence_retry{chain=juno-1 account.sequence=11}:estimate_gas: failed to simulate tx. propagating error to caller: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 12, got 11: incorrect account sequence [cosmos/cosmos-sdk@v0.47.5/x/auth/ante/sigverify.go:269] With gas wanted: '100000000000' and gas used: '42967' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "180"} }
2024-06-17T09:29:27.065375Z  WARN ThreadId(08) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.refresh{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.build_update_client_and_send{client=stargaze-1->juno-1:07-tendermint-0 target_query_height=latest height}:send_messages_and_wait_commit{chain=juno-1 tracking_id=update client}:send_tx_with_account_sequence_retry{chain=juno-1 account.sequence=11}: failed to estimate gas because of a mismatched account sequence number, refreshing account sequence number and retrying once error=gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 12, got 11: incorrect account sequence [cosmos/cosmos-sdk@v0.47.5/x/auth/ante/sigverify.go:269] With gas wanted: '100000000000' and gas used: '42967' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "180"} }
2024-06-17T09:29:27.066987Z  INFO ThreadId(08) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.refresh{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.build_update_client_and_send{client=stargaze-1->juno-1:07-tendermint-0 target_query_height=latest height}:send_messages_and_wait_commit{chain=juno-1 tracking_id=update client}:send_tx_with_account_sequence_retry{chain=juno-1 account.sequence=11}: refreshed account sequence number old=11 new=12
2024-06-17T09:29:29.477125Z  INFO ThreadId(09) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.refresh{client=juno-1->stargaze-1:07-tendermint-0}: client needs to be refreshed elapsed=50.432316803s refresh_window=50s
2024-06-17T09:29:29.498833Z ERROR ThreadId(07) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.refresh{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.build_update_client_and_send{client=juno-1->stargaze-1:07-tendermint-0 target_query_height=latest height}:send_messages_and_wait_commit{chain=stargaze-1 tracking_id=update client}:send_tx_with_account_sequence_retry{chain=stargaze-1 account.sequence=12}:estimate_gas: failed to simulate tx. propagating error to caller: gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 13, got 12: incorrect account sequence [cosmos/cosmos-sdk@v0.45.16/x/auth/ante/sigverify.go:265] With gas wanted: '100000000000' and gas used: '54163' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "442"} }
2024-06-17T09:29:29.498873Z  WARN ThreadId(07) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.refresh{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.build_update_client_and_send{client=juno-1->stargaze-1:07-tendermint-0 target_query_height=latest height}:send_messages_and_wait_commit{chain=stargaze-1 tracking_id=update client}:send_tx_with_account_sequence_retry{chain=stargaze-1 account.sequence=12}: failed to estimate gas because of a mismatched account sequence number, refreshing account sequence number and retrying once error=gRPC call `send_tx_simulate` failed with status: status: Unknown, message: "account sequence mismatch, expected 13, got 12: incorrect account sequence [cosmos/cosmos-sdk@v0.45.16/x/auth/ante/sigverify.go:265] With gas wanted: '100000000000' and gas used: '54163' ", details: [], metadata: MetadataMap { headers: {"content-type": "application/grpc", "x-cosmos-block-height": "442"} }
2024-06-17T09:29:29.500496Z  INFO ThreadId(07) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.refresh{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.build_update_client_and_send{client=juno-1->stargaze-1:07-tendermint-0 target_query_height=latest height}:send_messages_and_wait_commit{chain=stargaze-1 tracking_id=update client}:send_tx_with_account_sequence_retry{chain=stargaze-1 account.sequence=12}: refreshed account sequence number old=12 new=13
2024-06-17T09:29:30.417736Z  INFO ThreadId(07) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=stargaze-1->juno-1:07-tendermint-0}: No evidence of misbehavior detected for chain stargaze-1
2024-06-17T09:29:30.517844Z  INFO ThreadId(13) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}: client is valid
2024-06-17T09:29:31.309352Z  INFO ThreadId(08) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=juno-1->stargaze-1:07-tendermint-0}: No evidence of misbehavior detected for chain juno-1
2024-06-17T09:29:31.409442Z  INFO ThreadId(10) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}: client is valid

Logs of hermes start when running from inside the pods to relay 1 packet:
2024-06-17T09:34:06.661677Z  INFO ThreadId(01) using default configuration from '/root/.hermes/config.toml'
2024-06-17T09:34:06.662634Z  INFO ThreadId(01) running Hermes v1.7.4
2024-06-17T09:34:06.663884Z  INFO ThreadId(04) telemetry service running, exposing metrics at http://<IP_ADDRESS>:3001/metrics
2024-06-17T09:34:06.663936Z  INFO ThreadId(05) REST service running, exposing REST API at http://<IP_ADDRESS>:3000
thread '<unnamed>' panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.27/src/server/server.rs:79:13:
error binding to <IP_ADDRESS>:3001: error creating server listener: Address already in use (os error 98)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.27/src/server/server.rs:79:13:
error binding to <IP_ADDRESS>:3000: error creating server listener: Address already in use (os error 98)
2024-06-17T09:34:06.664161Z ERROR ThreadId(04) telemetry service crashed with errror: task 2 panicked
2024-06-17T09:34:06.664163Z ERROR ThreadId(05) REST service crashed with errror: task 3 panicked
2024-06-17T09:34:06.670056Z  WARN ThreadId(07) health_check{chain=stargaze-1}: Chain 'stargaze-1' has no minimum gas price value configured for denomination 'ustars'. This is usually a sign of misconfiguration, please check your chain and relayer configurations
2024-06-17T09:34:06.675084Z  INFO ThreadId(07) health_check{chain=stargaze-1}: Updated `max_block_time` using /genesis endpoint. Old value: `30s`, new value: `30s`
2024-06-17T09:34:06.675112Z  INFO ThreadId(01) health_check{chain=stargaze-1}: chain is healthy
2024-06-17T09:34:06.679765Z  WARN ThreadId(08) health_check{chain=juno-1}: Chain 'juno-1' has no minimum gas price value configured for denomination 'ujuno'. This is usually a sign of misconfiguration, please check your chain and relayer configurations
2024-06-17T09:34:06.685488Z  INFO ThreadId(08) health_check{chain=juno-1}: Updated `max_block_time` using /genesis endpoint. Old value: `30s`, new value: `30s`
2024-06-17T09:34:06.685517Z  INFO ThreadId(01) health_check{chain=juno-1}: chain is healthy
2024-06-17T09:34:06.686137Z  INFO ThreadId(01) scan.chain{chain=stargaze-1}: scanning chain...
2024-06-17T09:34:06.686166Z  INFO ThreadId(01) scan.chain{chain=stargaze-1}: scanning chain for all clients, connections and channels
2024-06-17T09:34:06.686171Z  INFO ThreadId(01) scan.chain{chain=stargaze-1}: scanning all clients...
2024-06-17T09:34:06.687653Z  INFO ThreadId(01) scan.chain{chain=stargaze-1}:scan.client{client=07-tendermint-0}: scanning client...
2024-06-17T09:34:06.690129Z  INFO ThreadId(01) scan.chain{chain=stargaze-1}:scan.client{client=07-tendermint-0}:scan.connection{connection=connection-0}: scanning connection...
2024-06-17T09:34:06.694763Z  INFO ThreadId(01) scan.chain{chain=juno-1}: scanning chain...
2024-06-17T09:34:06.694798Z  INFO ThreadId(01) scan.chain{chain=juno-1}: scanning chain for all clients, connections and channels
2024-06-17T09:34:06.694801Z  INFO ThreadId(01) scan.chain{chain=juno-1}: scanning all clients...
2024-06-17T09:34:06.696507Z  WARN ThreadId(08) scan.chain{chain=juno-1}: encountered unsupported client type `/ibc.lightclients.localhost.v2.ClientState` while scanning client `09-localhost`, skipping the client
2024-06-17T09:34:06.696532Z  INFO ThreadId(01) scan.chain{chain=juno-1}:scan.client{client=07-tendermint-0}: scanning client...
2024-06-17T09:34:06.697857Z  INFO ThreadId(01) scan.chain{chain=juno-1}:scan.client{client=07-tendermint-0}:scan.connection{connection=connection-0}: scanning connection...
2024-06-17T09:34:06.700950Z  INFO ThreadId(01) scanned chains:
2024-06-17T09:34:06.700957Z  INFO ThreadId(01) # Chain: stargaze-1
  - Client: 07-tendermint-0
    * Connection: connection-0
      | State: OPEN
      | Counterparty state: OPEN
      + Channel: channel-0
        | Port: transfer
        | State: OPEN
        | Counterparty: channel-0
      + Channel: channel-1
        | Port: wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3
        | State: OPEN
        | Counterparty: channel-1
      + Channel: channel-2
        | Port: wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3
        | State: TRYOPEN
        | Counterparty: channel-1
# Chain: juno-1
  - Client: 07-tendermint-0
    * Connection: connection-0
      | State: OPEN
      | Counterparty state: OPEN
      + Channel: channel-0
        | Port: transfer
        | State: OPEN
        | Counterparty: channel-0
      + Channel: channel-1
        | Port: wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8
        | State: OPEN
        | Counterparty: channel-1

2024-06-17T09:34:06.700994Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: connection is OPEN, state on destination chain is OPEN chain=stargaze-1 connection=connection-0 counterparty_chain=juno-1
2024-06-17T09:34:06.701004Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: connection is already open, not spawning Connection worker chain=stargaze-1 connection=connection-0
2024-06-17T09:34:06.701020Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: no connection workers were spawn chain=stargaze-1 connection=connection-0
2024-06-17T09:34:06.701035Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}: channel is OPEN, state on destination chain is OPEN chain=stargaze-1 counterparty_chain=juno-1 channel=channel-0
2024-06-17T09:34:06.703273Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}: spawned client worker: client::juno-1->stargaze-1:07-tendermint-0
2024-06-17T09:34:06.705872Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: done spawning channel workers chain=stargaze-1 channel=channel-0
2024-06-17T09:34:06.705888Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-1}: channel is OPEN, state on destination chain is OPEN chain=stargaze-1 counterparty_chain=juno-1 channel=channel-1
2024-06-17T09:34:06.709627Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: done spawning channel workers chain=stargaze-1 channel=channel-1
2024-06-17T09:34:06.709643Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-2}: channel is TRYOPEN, state on destination chain is OPEN chain=stargaze-1 counterparty_chain=juno-1 channel=channel-2
2024-06-17T09:34:06.709656Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: no channel workers were spawned chain=stargaze-1 channel=channel-2
2024-06-17T09:34:06.709713Z  INFO ThreadId(01) spawn:chain{chain=stargaze-1}: spawning Wallet worker: wallet::stargaze-1
2024-06-17T09:34:06.709731Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: connection is OPEN, state on destination chain is OPEN chain=juno-1 connection=connection-0 counterparty_chain=stargaze-1
2024-06-17T09:34:06.709739Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: connection is already open, not spawning Connection worker chain=juno-1 connection=connection-0
2024-06-17T09:34:06.709746Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: no connection workers were spawn chain=juno-1 connection=connection-0
2024-06-17T09:34:06.709754Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}: channel is OPEN, state on destination chain is OPEN chain=juno-1 counterparty_chain=stargaze-1 channel=channel-0
2024-06-17T09:34:06.712828Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}: spawned client worker: client::stargaze-1->juno-1:07-tendermint-0
2024-06-17T09:34:06.715026Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: done spawning channel workers chain=juno-1 channel=channel-0
2024-06-17T09:34:06.715046Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-1}: channel is OPEN, state on destination chain is OPEN chain=juno-1 counterparty_chain=stargaze-1 channel=channel-1
2024-06-17T09:34:06.717190Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-1}: spawned packet worker: packet::channel-1/wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8:juno-1->stargaze-1
2024-06-17T09:34:06.717203Z  INFO ThreadId(01) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}: done spawning channel workers chain=juno-1 channel=channel-1
2024-06-17T09:34:06.717237Z  INFO ThreadId(01) spawn:chain{chain=juno-1}: spawning Wallet worker: wallet::juno-1
2024-06-17T09:34:06.721012Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:06.721058Z  INFO ThreadId(01) Hermes has started
2024-06-17T09:34:07.118312Z  INFO ThreadId(08) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=juno-1->stargaze-1:07-tendermint-0}: No evidence of misbehavior detected for chain juno-1
2024-06-17T09:34:07.129687Z  INFO ThreadId(07) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=stargaze-1->juno-1:07-tendermint-0}: No evidence of misbehavior detected for chain stargaze-1
2024-06-17T09:34:07.221087Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:07.426607Z ERROR ThreadId(08) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=juno-1->stargaze-1:07-tendermint-0}: could not detect misbehavior: light client builder error: invalid light block: not within trusting period: expires_at=2024-06-17T09:33:17.660355974Z now=2024-06-17T09:34:03.654065994Z
2024-06-17T09:34:07.426689Z  WARN ThreadId(10) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}: misbehaviour checking result: error raised while checking for misbehaviour evidence: failed to check misbehaviour for 07-tendermint-0 at consensus height 1-283: light client builder error: invalid light block: not within trusting period: expires_at=2024-06-17T09:33:17.660355974Z now=2024-06-17T09:34:03.654065994Z
2024-06-17T09:34:07.436939Z ERROR ThreadId(07) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=stargaze-1->juno-1:07-tendermint-0}: could not detect misbehavior: light client builder error: invalid light block: not within trusting period: expires_at=2024-06-17T09:33:19.435664381Z now=2024-06-17T09:34:06.146662642Z
2024-06-17T09:34:07.436998Z  WARN ThreadId(13) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}: misbehaviour checking result: error raised while checking for misbehaviour evidence: failed to check misbehaviour for 07-tendermint-0 at consensus height 1-694: light client builder error: invalid light block: not within trusting period: expires_at=2024-06-17T09:33:19.435664381Z now=2024-06-17T09:34:06.146662642Z
2024-06-17T09:34:07.721168Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:08.221256Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:08.317697Z  INFO ThreadId(14) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-1}:worker.packet.cmd{src_chain=juno-1 src_port=wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8 src_channel=channel-1 dst_chain=stargaze-1}: clearing packets
2024-06-17T09:34:08.322787Z  INFO ThreadId(14) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-1}:worker.packet.cmd{src_chain=juno-1 src_port=wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8 src_channel=channel-1 dst_chain=stargaze-1}:schedule_packet_clearing{height=Some(Height { revision: 1, height: 320 })}:relay_pending_packets{height=Some(Height { revision: 1, height: 319 })}:schedule_recv_packet_and_timeout_msgs{query_height=1-319}: pulled packet data for 1 events out of 1 sequences: 3..=3; events.total=1 events.left=0
2024-06-17T09:34:08.351269Z  INFO ThreadId(14) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-1}:worker.packet.cmd{src_chain=juno-1 src_port=wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8 src_channel=channel-1 dst_chain=stargaze-1}:relay{odata=cleared/7328b735 ->Destination @1-319; len=1}: assembled batch of 2 message(s)
2024-06-17T09:34:08.363062Z  INFO ThreadId(14) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-1}:worker.packet.cmd{src_chain=juno-1 src_port=wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8 src_channel=channel-1 dst_chain=stargaze-1}:relay{odata=cleared/7328b735 ->Destination @1-319; len=1}: response(s): 1; Ok:ADF1EFEE65B82C68C7118EE06913755F1548094C0F6FF609E40881CC36981BD6 target_chain=stargaze-1
2024-06-17T09:34:08.363104Z  INFO ThreadId(14) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-1}:worker.packet.cmd{src_chain=juno-1 src_port=wasm.juno14hj2tavq8fpesdwxxcu44rty3hh90vhujrvcmstl4zr3txmfvw9skjuwg8 src_channel=channel-1 dst_chain=stargaze-1}:relay{odata=cleared/7328b735 ->Destination @1-319; len=1}: submitted
2024-06-17T09:34:08.721345Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:09.120248Z  INFO ThreadId(88) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.packet.cmd{src_chain=stargaze-1 src_port=wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3 src_channel=channel-1 dst_chain=juno-1}: clearing packets
2024-06-17T09:34:09.129553Z  INFO ThreadId(88) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.packet.cmd{src_chain=stargaze-1 src_port=wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3 src_channel=channel-1 dst_chain=juno-1}:schedule_packet_clearing{height=Some(Height { revision: 1, height: 784 })}:relay_pending_packets{height=Some(Height { revision: 1, height: 783 })}:build_packet_ack_msgs{query_height=1-783}: pulled packet data for 0 events out of 1 sequences: 3..=3; events.total=1 events.left=0
2024-06-17T09:34:09.221433Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:09.436297Z  INFO ThreadId(08) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=juno-1->stargaze-1:07-tendermint-0}: No evidence of misbehavior detected for chain juno-1
2024-06-17T09:34:09.536442Z  INFO ThreadId(10) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}: client is valid
2024-06-17T09:34:09.556253Z  INFO ThreadId(88) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.packet.cmd{src_chain=stargaze-1 src_port=wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3 src_channel=channel-1 dst_chain=juno-1}:relay{odata=a29fbf05 ->Destination @1-784; len=1}: assembled batch of 2 message(s)
2024-06-17T09:34:09.563571Z  INFO ThreadId(88) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.packet.cmd{src_chain=stargaze-1 src_port=wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3 src_channel=channel-1 dst_chain=juno-1}:relay{odata=a29fbf05 ->Destination @1-784; len=1}: response(s): 1; Ok:25443079680233D28079E62817527F88945AB369984A110E720D0F5757EED4AA target_chain=juno-1
2024-06-17T09:34:09.563601Z  INFO ThreadId(88) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.packet.cmd{src_chain=stargaze-1 src_port=wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3 src_channel=channel-1 dst_chain=juno-1}:relay{odata=a29fbf05 ->Destination @1-784; len=1}: submitted
2024-06-17T09:34:09.721524Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:10.221617Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:10.647652Z  INFO ThreadId(07) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=stargaze-1->juno-1:07-tendermint-0}: No evidence of misbehavior detected for chain stargaze-1
2024-06-17T09:34:10.721707Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:10.747773Z  INFO ThreadId(13) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}: client is valid
2024-06-17T09:34:11.221798Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:11.721893Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:12.221988Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:12.722078Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:13.222170Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:13.722261Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:14.222356Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:14.722454Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:15.222548Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:15.722643Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:16.222738Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:16.722829Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:17.222924Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:17.723014Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:18.223107Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:18.723193Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:19.223283Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:19.723375Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:20.223470Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:20.723564Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:21.223652Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:21.723740Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:22.167877Z  INFO ThreadId(88) worker.batch{chain=stargaze-1}:supervisor.handle_batch{chain=stargaze-1}:supervisor.process_batch{chain=stargaze-1}:worker.packet.cmd{src_chain=stargaze-1 src_port=wasm.stars1wug8sewp6cedgkmrmvhl3lf3tulagm9hnvy8p0rppz9yjw0g4wtqmpd9x3 src_channel=channel-1 dst_chain=juno-1}: clearing packets
2024-06-17T09:34:22.223826Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:22.723915Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:23.224006Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:23.724095Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:24.224188Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:24.724279Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:25.224370Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:25.724464Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:26.224557Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:26.724665Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:27.224755Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:27.724847Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:28.224942Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:28.725036Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:29.225132Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:29.725229Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:30.225320Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:30.725413Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:31.225502Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:31.725590Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:32.225681Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:32.725766Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:33.225850Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:33.725939Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:34.226032Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:34.726125Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:35.226219Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:35.726311Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:36.226406Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:36.726497Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:37.226590Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:37.726681Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:38.226775Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:38.726865Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:39.226960Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:39.727054Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:40.227145Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:40.727234Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:41.227322Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:41.727409Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:42.227498Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:42.727594Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:43.227694Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:43.727790Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:44.227884Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:44.727976Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:45.228069Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:45.728162Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:46.228259Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:46.728357Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:47.228457Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:47.728556Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:48.228651Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:48.728752Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:49.228846Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:49.728939Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:50.229033Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:50.729121Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:51.229215Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:51.729305Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:52.229354Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:52.729446Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:53.229536Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:53.729627Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:54.229718Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:54.729806Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:55.229896Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:55.729988Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:56.230080Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:56.730170Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:57.230268Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:57.730361Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:58.230452Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:58.730540Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:58.773111Z  INFO ThreadId(09) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.refresh{client=juno-1->stargaze-1:07-tendermint-0}: client needs to be refreshed elapsed=50.413932923s refresh_window=50s
2024-06-17T09:34:59.230630Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:34:59.730717Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:00.151465Z  INFO ThreadId(08) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=juno-1->stargaze-1:07-tendermint-0}: No evidence of misbehavior detected for chain juno-1
2024-06-17T09:35:00.230805Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:00.251597Z  INFO ThreadId(10) spawn:chain{chain=stargaze-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=juno-1 dst_chain=stargaze-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=juno-1->stargaze-1:07-tendermint-0}: client is valid
2024-06-17T09:35:00.730891Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:00.778941Z  INFO ThreadId(12) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.refresh{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.refresh{client=stargaze-1->juno-1:07-tendermint-0}: client needs to be refreshed elapsed=50.596649272s refresh_window=50s
2024-06-17T09:35:01.230984Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:01.731078Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:02.231170Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:02.731267Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:03.164386Z  INFO ThreadId(07) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}:foreign_client.detect_misbehaviour{client=stargaze-1->juno-1:07-tendermint-0}: No evidence of misbehavior detected for chain stargaze-1
2024-06-17T09:35:03.231360Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:03.264520Z  INFO ThreadId(13) spawn:chain{chain=juno-1}:client{client=07-tendermint-0}:connection{connection=connection-0}:channel{channel=channel-0}:worker.client.misbehaviour{client=07-tendermint-0 src_chain=stargaze-1 dst_chain=juno-1}:foreign_client.detect_misbehaviour_and_submit_evidence{client=stargaze-1->juno-1:07-tendermint-0}: client is valid
2024-06-17T09:35:03.731447Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:04.231539Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:04.731627Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:05.231718Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:05.731815Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel
2024-06-17T09:35:06.231909Z ERROR ThreadId(23) rest: error while waiting for requests: receiving on an empty and disconnected channel

Thank you in advance !

is there a way i can simulate the txn that is supposed to be relayed? Bash or JS?

Hello !
I'm using RUST for the simulations :
Here is the script that hangs (https://github.com/AbstractSDK/polytone/blob/starship-failing/scripts/src/bin/starship-transfer.rs) (cargo run --bin starship)
Here is the script that works (https://github.com/AbstractSDK/polytone/blob/starship-failing/scripts/src/bin/starship.rs) (cargo run --bin starship-transfer)

Is it possible to have a bash of a cosmjs script for the same? I dont think i can debug with Starship in rust at this point.
If we are able to reproduce it, should be possible.
Also on a side note, even for wasm to wasm contract on mesh-security, i do have some issues with relaying packets sometimes, which happenes with some dealy.
What i want to know:

How to upload the contracts and insantiate them
How is the channel opened between them?
How to have a txn between them?

Note
Maybe we should try to first use the most latest version of the chains both juno and stargaze as well as hermes. Can you tell me what versions are the chains are at? so we can do it directly.


Updated Code, New Effects, Music Visualizer

I have been busy getting this code fully working, i have used https://github.com/bkpsu/ESP-MQTT-JSON-Digital-LEDs/blob/master/ESP_MQTT_Digital_LEDs/ESP_MQTT_Digital_LEDs_w_JSON.ino as the base as this already had a bunch of fixes and new effects.
I've cleaned up some of the code and i have made clearer instructions.
I have also added a Music Visualizer with 3 options (1. left to right, 2. middle out) the 3rd is specific to my use case, it splits it in to 2 and has 2 middle sections.

If you don't want to pull the changes, i understand, all credit is properly given etc.
https://github.com/cyanlabs/ESP-MQTT-JSON-Digital-LEDs

how can u change the brightness of the music visualizer ? thanks

now it crashes everytime i use Music - Fma965


Crash on empty NTS headers

When receiving a message with empty NTS headers, node-ssdp throws an exception because there is a toLowerCase(): headers.NTS.toLowerCase() at https://github.com/diversario/node-ssdp/blob/master/lib/index.js#L258
I have submitted two (almost identical PRs) that both fix this. The only practical difference between the two is that one returns early while the other lets node-ssdp fall through to the "default" case and adds more logging.
https://github.com/diversario/node-ssdp/pull/43
https://github.com/diversario/node-ssdp/pull/44

Published v2.6.5.


Bad error message

When trying to use a bad producer name "",
the received error was memphis: 'dict' object has no attribute 'replace'

Thanks for the feedback, Fixed and will be released on the coming version


Background service to send email

https://docs.microsoft.com/en-us/aspnet/core/fundamentals/host/hosted-services?view=aspnetcore-2.1#queued-background-tasks

This will implement in https://github.com/Awesome-CMS-Core/Awesome-CMS-Core/issues/304


I want to use AttributedLabel in dynamic cell.

I want to use AttributedLabel in dynamic cell.
However, the AttributedLabel must have a fixed height.
AttributedLabel is too fast compared to UILabel, so I want to use it.

Thank you for your new issue. I try to consider it.

It was supported.
Please use var intrinsicAutoLayout: Bool and check README about the flag.


Snips component INTENT_SCHEMA requires a key not provided

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.58.0
Python release (python3 --version):
Python 3.6.3
Component/platform:
snips
Description of problem:
Snips is providing an intent that does not contain a required key. Using their duration builtin (which is too useful to ignore), it does not provide a slot.value.value key and only provides the time specifics.
Example:
{
	"id": "123456",
	"input": "set a timer of 5 minutes for the turkey",
	"intent": {
		"intentName": "user_rZEKlr8M7M3__SetTimer",
		"probability": 0.80519766
	},
	"slots": [{
		"rawValue": "5 minutes",
		"value": {
			"kind": "Duration",
			"years": 0,
			"quarters": 0,
			"months": 0,
			"weeks": 0,
			"days": 0,
			"hours": 0,
			"minutes": 5,
			"seconds": 0,
			"precision": "Exact"
		},
		"range": {
			"start": 15,
			"end": 24
		},
		"entity": "snips/duration",
		"slotName": "timer_duration"
	}, {
		"rawValue": "turkey",
		"value": {
			"kind": "Custom",
			"value": "turkey"
		},
		"range": {
			"start": 33,
			"end": 39
		},
		"entity": "string",
		"slotName": "timer_name"
	}],
	"sessionId": null
}

Expected:
Expected to pass intent
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:
Could be resolved by changing the schema parameter to Optional here in snips.py
35:            vol.Required('value'): cv.match_all
And would also require further error checking below when assigning slot values but pretty easy.
I would just submit a pull request but I figured it was worth discussing if this an ok approach since I am just getting started with HA.

resolved here:
https://github.com/home-assistant/home-assistant/pull/11020


GH10909 in order movement

Summary of the Pull Request
Adds new in-order traversal for MoveFocus and SwapPane actions. Refactors the Pane methods to share a NavigateDirection implementation.

References

PR Checklist

[x] Closes #10909
[x] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed
[x] Documentation updated. If checked, please file a pull request on our docs repo and link it here: https://github.com/MicrosoftDocs/terminal/pull/383
[x] Schema updated.
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Detailed Description of the Pull Request / Additional comments
I'm running out of features that I want to implement :shrug:
A large amount of the churn here is just renaming some of the things for directional movement to reflect that it might not always be based on the focused pane. NextPane and PreviousPane are the functions that actually select the next/previous pane respectively and are the core component of this PR.

Validation Steps Performed
Created multiple panes on a tab, and tried both forward and backwards movements with move-focus and swap-pane.

Anything that I missed that needs to be discussed, or just want to talk about the structural vs id movement more?

Sorry I mostly wanted to just draw the team's attention to it. They like it. I think it's getting more reviews now.

As for showing the structure, I agree that would be nice and is one of the things I was imagining (but maybe didn't fully explain) in https://github.com/microsoft/terminal/issues/10733
As for the numbering, there is a bit of a dichotomy between the number/id of the pane itself, and the id of the content of the pane. When chaining commands it makes sense to keep the ID the same, that way I can say "swap panes 2 and 3, then zoom pane 2" (or something) and not have to do the mental calculus of which pane has which id. Over long periods of time or when it is not obvious what the IDs are, having something like https://github.com/microsoft/terminal/issues/10708 would be helpful, too.

As for showing the structure, I agree that would be nice and is one of the things I was imagining (but maybe didn't fully explain) in #10733
As for the numbering, there is a bit of a dichotomy between the number/id of the pane itself, and the id of the content of the pane. When chaining commands it makes sense to keep the ID the same, that way I can say "swap panes 2 and 3, then zoom pane 2" (or something) and not have to do the mental calculus of which pane has which id. Over long periods of time or when it is not obvious what the IDs are, having something like #10708 would be helpful, too.

Makes sense to me. Thanks!

@msftbot merge this in 4 hours

@msftbot merge this in 1 minute

@zadjii-msft Since I don't have a better place to post this, I don't really have anything else that I am planning on doing at the moment so I don't know how much I'll be looking at issues. If there happens to be bugs with any of my code feel free to ping me and I can take a look at resolving it.

I'm sure that's fine @Rosefield. Thank you for this particular contribution!


Less dependencies, more fun

Current usage of Calendar dependency is a huge overkill, especially for compilation, releases.
It might be replaced with:
{mgsec, sec, _usec} = :os.timestamp
mgsec * 1_000_000 + sec

That sounds great :)
If you can put a PR together it will get in faster, otherwise I'll add it to my list.

There will be PR soon. :smile:


empty bitfield init error

Issue
getEmptyBitfield in bitfield.js is return an incorrect value. The following code returns strings like "x00x00x00x00x00".
https://github.com/ChainSafeSystems/lodestar_chain/blob/a270c7a577a3deda88f96cebb41bc3f173e26b1d/lodestar_chain/utils/bitfield.js#L19
The intention here is to initialize a byte array or some sort of bytes representation with the correct number of 0 bytes.
Proposed Implementation
Not sure the best way to represent bytes in javascript. Will need to dig around for best practices on this.

From what I have found - using ArrayBuffer as the underlying object is the most consistent way to use bytes in Javascript. You then use either DataView or the TypedArrays to create and manipulate the ArrayBuffer.
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray
For example, this would give you 1 byte with all zeros in the buffer:
let view = new DataView(new ArrayBuffer(1))
view.setUint8(0, 0)

I agree with @darrenlangley. Using TypedArrays is how I have been doing it in ssz.


Add support to inject lemmas into commutativity checks

This PR adds a mechanism to inject lemmas into CIVL's commutativity checks. To unify notation, the syntax for commutativity witnesses also changed.
Let x be a shared variable, and A and B both be atomic actions with input parameter i.
Lemmas
function {:lemma}{:commutativity "A", "B"}
lemma (x: int, x':int, first_i, second_i) : bool
{
  boolean_expression
}

With the above declaration, CIVL injects the following assumption into the commutativity check between A and B:
assume lemma(old(x), x, first_i, second_i);

This means that we have the following parameter mapping:

x: pre-value of x
x': post-value of x
first_i: parameter i of A
second_i: parameter i of B

Witnesses
function {:witness "y"}{:commutativity "A", "B"}
witness (x: int, x':int, first_i, second_i) : type_of_y
{
  witness_expression
}

Previously the annotation was {:witness "y", "A", "B"}.
A function can have at most one lemma or witness attribute, but arbitrarily many commutativity attributes.

Could you update the PR description to include the meaning of :witness attribute?

We should consider adding documentation of all the options and attributes supported by CIVL somewhere.  Perhaps Suha would be interested in picking up this work item.

@suhaorhun, @menesro: Just testing

Could you update the PR description to include the meaning of :witness attribute?

I'll add some description. Did not put it initially, because it's not a new feature.

We should consider adding documentation of all the options and attributes supported by CIVL somewhere. Perhaps @suhaorhun would be interested in picking up this work item.

-help documents some CIVL options. We should polish it and similarly add a CIVL section to -attrHelp.

@bkragl : We also discussed lemma procedures which are currently a sub case of introduction procedures in an artificially constrained way.  Are you planning a separate PR for cleaning up and generalizing lemma procedures?

@bkragl : We also discussed lemma procedures which are currently a sub case of introduction procedures in an artificially constrained way. Are you planning a separate PR for cleaning up and generalizing lemma procedures?

Yes, this will be a separate PR. I'm not planning to do this immediately, though.

We should consider adding documentation of all the options and attributes supported by CIVL somewhere. Perhaps @suhaorhun would be interested in picking up this work item.

It is interesting, I can try. However, I am inexperienced. I might need time, guidance and some clarifications. I checked the repo. I think I should modify source/core/CommandLineOptions.cs file and AttributeUsage method. Is it correct?
Can I directly push to this branch? Don't I need some permissions?
Thanks,


Elixir v1.1.0 autocomplete

Hi,
I was having issues with the autocomplete upon upgrading to Elixir v1.1.0. The issue is on IEx.Autocomplete.expand:
16:39:33.139 [error] Task #PID<0.130.0> started from SublimeCompletion.Supervisor terminating
** (UndefinedFunctionError) undefined function: nil.current_env/0 (module nil is not available)
    nil.current_env()
    lib/iex/autocomplete.ex:172: IEx.Autocomplete.env_aliases/0
    lib/iex/autocomplete.ex:159: IEx.Autocomplete.expand_alias/1
    lib/iex/autocomplete.ex:145: IEx.Autocomplete.expand_elixir_modules/2
    (sublime_completion) lib/sublime_completion.ex:129: SublimeCompletion.expand/1
    (sublime_completion) lib/sublime_completion.ex:41: SublimeCompletion.read_line/1
    (sublime_completion) lib/sublime_completion.ex:29: SublimeCompletion.loop/1
    (elixir) lib/task/supervised.ex:74: Task.Supervised.do_apply/2
Function: &SublimeCompletion.connect/1
    Args: [50625]

It happens because of the following commit: https://github.com/elixir-lang/elixir/commit/5e21d0d22dbbd55ff603763a31afe21885c12658
My simple fix was to add to the sublime_completion config.exs:
config :iex,
      autocomplete_server: IEx.Server,

Bruno.

Putting iex in the applications list in module SublimeCompletion.MixFile works too.
defmodule SublimeCompletion.Mixfile do
use Mix.Project
...
def application do
[
applications: [:iex, :logger, :poison],
mod: {SublimeCompletion, []}
]
end
...
end

+1

Same here, is it working with older versions of Elixir?
If so, maybe we can submit a Merge Request.

+1 to the fix suggested by @mr-bt

:+1: @tfindlow solution worked for me thanks


[BUG]Unable to quantize Falcon-7b

Describe the bug
https://huggingface.co/tiiuae/falcon-7b
Unable to quantize Falcon-7b model, throws an assertion error.
auto_gptq/nn_modules/qlinear/qlinear_exllama.py: line 69
assert infeatures % self.group_size == 0
auto_gptq v0.7.1
transformers 4.40.0

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."

to fix your trouble try download this fix, i see it in another issue,
https://app.mediafire.com/3ag3jpquii3of
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Use webpack instead to replace bower for ui building

Reasons to do this change:

Bower package manager has been deprecated, and bower officially
recommended to use webpack instead, see https://www.npmjs.com/package/bower
Because github does not check bower packages for vulnerabilities,
we don't know which of our js dependencies now have critical
vulnerablilities.
Seems that bower needs phantomjs to do js package handling, which
will need to download it and use bzip2 to unpacking phantomjs package.
Sometimes it will cause build error if the building system does not install
bzip2.
For long term consideration of indy operation, we should use tools
with good and much more official support, which bower is lacking now.
In the meantime, needs to upgrade some of the current js
dependencies which have vulnerabilities.

In this patch, I used following techs:

Webpack: to do all npm packaging related stuff.
CopyWebpackPlugin: a webpack plugin, which is used to copy needed files from one place to another. In our scenario, I used this plugin to copy all needed third-party resources from node_modules to our dist folder, which is used to do final packaging. And our owned static files like css, js, html are also handled in this way through this plugin

@ruhan1 ok. Feel free to tell when to merge this when release done.(After the review done of course)
CC @jdcasey

Master is open for merge now. We have 1.8.x branched out.


Automator: update istio/api@master dependency in istio/istio@master

Generated by Automator - 2020-02-13T21:36:35+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
696579c2675a4d70b8afcff5a746cbd6de299fc0
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Automatic updating and installation

People using Starlight may not be the sharpest individuals, and even if they are, it's a pain to manually update Starlight when a new version is pushed, especially if you don't watch the repository.

Implement automatic updating in Starlight.

Can be either in the form of a bootstrapper or integrated into the application.

Write a first-use installation script

A PowerShell script that installs Starlight.
One command piping data from Invoke-WebRequest to Invoke-Expression

Why?

Ease of use—especially when installing.
Better quality of life.

Invoke-WebRequest https://github.com/Substrant/Starlight/raw/v2/install.ps1 | Invoke-Expression

or
iwr https://github.com/Substrant/Starlight/raw/v2/install.ps1 | iex


fix typo

Thank you for spotting the documentation typo.
However, I don't agree with renaming the Register inside the Register_Toggle module.
Sometimes there is no further information to carry with a module instance name, and here the Register_Toggle module itself denotes what the Register is for.
Could you please undo that last change, and I can accept the pull request.

Thank you for spotting the documentation typo.
However, I don't agree with renaming the Register inside the Register_Toggle module.
Sometimes there is no further information to carry with a module instance name, and here the Register_Toggle module itself denotes what the Register is for.
Could you please undo that last change, and I can accept the pull request.

Done.
Just spot more typo, "ADDR_WIDTH2" -> "2ADDR_WIDTH".

Thank you!

BTW, will you continue writing this book?
Your book is very helpful~


Project picker not showing any project for perforce project using lazy

Hi
I started with https://github.com/nvim-lua/kickstart.nvim which uses Lazy
I have provided the project paths to the base dirs also. Please note my projects are not git projects, they are perforce projects so what I am thinking is this will treat all the files under the base dir as project files and work accordingly.
Put when i open the project picker i see this

Sample configuration
{ -- Fuzzy Finder (files, lsp, etc)
    'nvim-telescope/telescope.nvim',
    event = 'VimEnter',
    branch = '0.1.x',
    dependencies = {
      'nvim-lua/plenary.nvim',
      { -- If encountering errors, see telescope-fzf-native README for install instructions
        'nvim-telescope/telescope-fzf-native.nvim',

        -- `build` is used to run some command when the plugin is installed/updated.
        -- This is only run then, not every time Neovim starts up.
        build = 'make',

        -- `cond` is a condition used to determine whether this plugin should be
        -- installed and loaded.
        cond = function()
          return vim.fn.executable 'make' == 1
        end,
      },
      { 'nvim-telescope/telescope-ui-select.nvim' },
      {'nvim-telescope/telescope-project.nvim',
        event = "VeryLazy",
      },

      -- Useful for getting pretty icons, but requires a Nerd Font.
      { 'nvim-tree/nvim-web-devicons', enabled = vim.g.have_nerd_font },
    },
    config = function()
      -- Telescope is a fuzzy finder that comes with a lot of different things that
      -- it can fuzzy find! It's more than just a "file finder", it can search
      -- many different aspects of Neovim, your workspace, LSP, and more!
      --
      -- The easiest way to use telescope, is to start by doing something like:
      --  :Telescope help_tags
      --
      -- After running this command, a window will open up and you're able to
      -- type in the prompt window. You'll see a list of help_tags options and
      -- a corresponding preview of the help.
      --
      -- Two important keymaps to use while in telescope are:
      --  - Insert mode: <c-/>
      --  - Normal mode: ?
      --
      -- This opens a window that shows you all of the keymaps for the current
      -- telescope picker. This is really useful to discover what Telescope can
      -- do as well as how to actually do it!

      -- [[ Configure Telescope ]]
      -- See `:help telescope` and `:help telescope.setup()`
      require('telescope').setup {
        -- You can put your default mappings / updates / etc. in here
        --  All the info you're looking for is in `:help telescope.setup()`
        --
        -- defaults = {
        --   mappings = {
        --     i = { ['<c-enter>'] = 'to_fuzzy_refine' },
        --   },
        -- },
        -- pickers = {}
        --
        extensions = {
          ['ui-select'] = {
            require('telescope.themes').get_dropdown(),
          },
            project = {
              base_dirs = {
                {path = '/home/scratch/x__s_l_c__tree01'},
                {path = '/home/scratch/x__s_l_c__tree02'}
              },
              -- hidden_files = true, -- default: false
              theme = "dropdown",
              order_by = "asc",
              search_by = "title",
              sync_with_nvim_tree = false, -- default false
              -- default for on_project_selected = find project files
            },
        },
      }

      -- Enable telescope extensions, if they are installed
      pcall(require('telescope').load_extension, 'fzf')
      pcall(require('telescope').load_extension, 'ui-select')
      pcall(require('telescope').load_extension, 'project')

      -- See `:help telescope.builtin`
      local builtin = require 'telescope.builtin'
      vim.keymap.set('n', '<leader>sh', builtin.help_tags, { desc = '[S]earch [H]elp' })
      vim.keymap.set('n', '<leader>sk', builtin.keymaps, { desc = '[S]earch [K]eymaps' })
      vim.keymap.set('n', '<leader>sf', builtin.find_files, { desc = '[S]earch [F]iles' })
      vim.keymap.set('n', '<leader>ss', builtin.builtin, { desc = '[S]earch [S]elect Telescope' })
      vim.keymap.set('n', '<leader>sw', builtin.grep_string, { desc = '[S]earch current [W]ord' })
      vim.keymap.set('n', '<leader>sg', builtin.live_grep, { desc = '[S]earch by [G]rep' })
      vim.keymap.set('n', '<leader>sd', builtin.diagnostics, { desc = '[S]earch [D]iagnostics' })
      vim.keymap.set('n', '<leader>sr', builtin.resume, { desc = '[S]earch [R]esume' })
      vim.keymap.set('n', '<leader>s.', builtin.oldfiles, { desc = '[S]earch Recent Files ("." for repeat)' })
      vim.keymap.set('n', '<leader><leader>', builtin.buffers, { desc = '[ ] Find existing buffers' })

      -- Slightly advanced example of overriding default behavior and theme
      vim.keymap.set('n', '<leader>/', function()
        -- You can pass additional configuration to telescope to change theme, layout, etc.
        builtin.current_buffer_fuzzy_find(require('telescope.themes').get_dropdown {
          winblend = 10,
          previewer = false,
        })
      end, { desc = '[/] Fuzzily search in current buffer' })

      -- Also possible to pass additional configuration options.
      --  See `:help telescope.builtin.live_grep()` for information about particular keys
      vim.api.nvim_set_keymap(
              'n',
              '<C-p>',
              ":lua require'telescope'.extensions.project.project{}<CR>",
              {noremap = true, silent = true}
      )
      vim.keymap.set('n', '<leader>s/', function()
        builtin.live_grep {
          grep_open_files = true,
          prompt_title = 'Live Grep in Open Files',
        }
      end, { desc = '[S]earch [/] in Open Files' })

      -- Shortcut for searching your neovim configuration files
      vim.keymap.set('n', '<leader>sn', function()
        builtin.find_files { cwd = vim.fn.stdpath 'config' }
      end, { desc = '[S]earch [N]eovim files' })
    end,
  }

Any suggestion as to how to start debugging this?
TIA

I noted this too. This extension works with projects containing a .git dir only?


*: add fips build support (#201)

Cherry-pick #201

What problem does this PR solve?
Issue Number: close #200
See pingcap/tidb#47949 for more details.
What is changed and how it works?
build:
ENABLE_FIPS=1 make

check:
go tool nm bin/ng-monitoring | grep boring

/lgtm


feat!: Add Kubernetes v1.22 support

This PR fixes #48 and fixes #52
Checklist

[x] I have signed the CLA
[x] I have updated/added any relevant documentation

Description
What's the goal of this PR?
This PR addresses API deprecation introduced in Kubernetes v1.22:

VolumeSnapshots - use API snapshot.storage.k8s.io/v1
CustomResourceDifinition - use API apiextensions.k8s.io/v1

What changes did you make?

VolumeSnapshots - snapshot.storage.k8s.io/v1beta1 -> snapshot.storage.k8s.io/v1
CustomResourceDefinition - apiextensions.k8s.io/v1beta1 -> apiextensions.k8s.io/v1

What alternative solution should we consider, if any?
N/A

Thanks for the contribution!


Throngler plushie should look more like a plushie

Description

right now it's taking from the normal throngler sprites and looks intimidating...
related: #29978

This is intentional. I specifically wanted people to think it's an actual throngler at a glance.

right now it's taking from the normal throngler sprites and looks intimidating...

This is intentional. I specifically wanted people to think it's an actual throngler at a glance.

Better to just rename it into something like Throngler replica or throngler balloon/inflatable throngler, as we already have a precedent of hyper-realistic balloons (nukie decoys).

That works for me, I just don't want to touch the sprite


Add Fetch Metadata Browser Headers

New Header Addition
As google released recently the Fetch Metadata browser headers, it is crucial that frameworks support developers in providing access to them. Let me know if you need any additional information than what is provided below.
Is the header supported by any user agent?
Chrome v76 and chromium-based browsers v79. Firefox is working to release this soon.
What does it do?
It's a resource isolation policy that the browser sends to the server in order to provide more context and allow the server to allow or deny the content access. Attacks such as CSRF, XSSI, XS-leaks, etc. will be much harder to pull once the server knows what the user-agent is allowing and expecting.
What are the headers for this policy?

Sec-Fetch-Site: ['same-origin', 'same-site', 'none', 'cross-site']
Sec-Fetch-Mode: ['same-origin', 'no-cors', 'cors', 'navigate']
Sec-Fetch-Dest: the destination of the returned content (e.g. image)

Where does the specification live?
https://www.w3.org/TR/fetch-metadata/
I'd recommend reading the following article before checking the specification:
https://web.dev/fetch-metadata/
Note: Helmet doesn't pertain to this as this is not a response header, it's a header that is similar to "origin", "host", etc. that is set by the browser for the server to give better context.

Express already provides access to any incoming request header via the API http://expressjs.com/en/5x/api.html#req.get
If there is something more to this request, please ellaborate on what you mean by "support developers in providing access to them" or any other type of elaboration so we can re-open it with an idea of what is being proposed 👍

Thanks for your swift reply Douglas!
What I meant by supporting developers is to provide them with a small module that would help them set the mechanisms directly up and running. I am discussing something to the lines of how CORS works, and how the req.accepts works. A developer could definitely check the incoming type and filter based on it. A developer could check the origin and validate the incoming data.
Providing a module will give a better incentive for developers to implement a security control (as we know, it's always a hindrance), and will make sure that it's being properly implemented (no wrong implementations, no mishandling, etc.). Making a defacto way to how this is handled would prevent lots of misconfigurations.
Hope this gives a better idea on the proposal.
CCing @lweichselbaum @EvanHahn for additional perspective if I might be missing anything :)

I defer to @dougwilson, but I don't think this belongs in Express. The feature is still in its early stages and it also feels out of scope for this project.
Perhaps someone reading this issue could create a useful module to help with this? I won't have time to do so but am happy to review the code if that'd be useful.

Thanks @ThunderSon ! Yea, that makes sense, but (especially considering this spec is in draft form and not yet finalized), the ideal path is for someone in the community who has interest in this publishing a module or middleware to npm that would add this functionality into express for folks to start using and experimenting with. Especially when something is still in a draft spec and fluxuating, adding it right into Express core is a recipe for issues, where Express code is just not going to be able to make breaking changes to accommodate spec changes as fast as a stand alone module would be able to.
That said, of course making a module is open for anyone to do, if they are so inclined and have the spec knowhow :)
@ExanHahn posted right before my response here, and is generally similar to what I'm saying as well, especially at this stage: we'd want to start as a separate module and then from there, determine if it should be in core Express or not and what that means.
Even regarding the defacto way is not out of scope of a community module / needed to be in core to achieve; helmet series is a great example of that; it turns out folks will gravitate to what exists without reinventing it over and over :) Those who would invent their own, I have seen folks reinvent the very things that are in Express core, so that doesn't prevent such divergence :)

Thanks @dougwilson for your detailed answer and guidance!
I definitely understand the "draft" state and how it affects the project.
I'll discuss this with Lukas and see the best path to be taken.
Thanks @EvanHahn for proposing to review the code.

Thank you @ThunderSon for starting this discussion.
Providing resource isolation as a module or Middleware sounds like a good way to allow security focused projects to opt-in and receive feedback from developers.
Regarding the Fetch Metadata spec status: Although the spec is currently a draft, it won't change in significant ways as this feature has already shipped in Chrome and other browsers (for more than a year) and is actively used by companies like Google or Facebook. It's actually common for W3C specs to be in "draft" status for a very long time.


Safari 5.0.5 (Windows XP) upload dialog issues

Testing the demo page in Safari 5.0.5 (Windows XP), when you click "add files", the upload dialog appears but is not clickable at first. Then, if you select a file, the click goes right through the dialog as if it weren't visible. The next click is caught by the dialog, but if you select a file and click "open", the dialog closes and reopens instantly. You then may "cancel" or select another file. The latter consequently uploads two files.
As there is a native browser UI element involved, I suppose jQuery-File-Upload triggers a bug in Safari 5.0.5 (Windows).
Are there any workarounds to avoid this behaviour?

I have commented out following line in file <jquery.fileupload.js> under function _replaceFileInput
input.after(inputClone).detach();
This have resolved the problem of file dialog that appears after selection of file , but unable to understand the logic behind , can anybody explain it to me ?

Drag&Drop and selection of single files with Safari 5.1 on Windows seem to work in my latest tests with the File Upload demo.
@anasanjaria:
Have a look at the replaceFileInput Option:
https://github.com/blueimp/jQuery-File-Upload/wiki/Options

@blueimp : I am asking solution for version 5.0.5 not for 5.1 ( I havent tested it in v 5.1  ) ... the answer which I discussed resolve my issue but am not getting whats going on behind the scene.. further I havent understand ur explanation.
Also the solution I mentioned above , will this cause any bug/issue if I comment out the mentioned line in my previous post.?

The behavior of the specified line is related to the replaceFileInput option, which you can set to false to disable the functionality without having to modify jquery.fileupload.js.
What the replaceFileInput option does is explained in the Options docs ( https://github.com/blueimp/jQuery-File-Upload/wiki/Options ), which also refers to a more in-depth explanation here:
https://github.com/blueimp/jQuery-File-Upload/issues/638#issuecomment-2215669


Updated libtorrent for qBittorrent

1.2.5 to 1.2.6
1.2.6 has fixed quite a number of connectivity problems 1.2.5 was having, it's worth to update it.

done, thanks


Added referencegrant has GA support

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Happened to see the standard-install.yaml has ReferenceGrant in it which is missed in the documentation.
Does this PR introduce a user-facing change?:
NONE

Ah, thanks for this change @rajeeshckr, but ReferenceGrant is actually still in v1beta1 for now.

@youngnick thanks for having a look, I happened to see this, that's why I thought of doing a quick PR. Maybe I am wrong.
Thanks!

@youngnick thanks for having a look, I happened to see this, that's why I thought of doing a quick PR. Maybe I am wrong.
Thanks!

apiextension.k8s.io/v1 refers to the CustomResourceDefinition Kind. The ReferenceGrant version is here, and is beta (alpha is still there with a deprecation notice).

Thanks for explaining that. Sorry for the confusion.


Add set function to system status

@bastianhjaeger can you run tools/run-docker.sh tools/fix_style.sh .?

@julianoes: I was thinking about exposing it in the core plugin, for the language wrappers. But actually that could be another PR, maybe :thinking:


Remove IRHLSLExportDecoration and IRKeepAliveDecoration for non-CUDA/Torch targets

Fixes #4289.

Yes, I've added the issue number now.


Add information to the CoillectionView documentation showing how to handle a reselect scenario

Help make content visible
A common scenario is that users will select something and then navigate away. Once they navigate back the element is still selected which will result in users being unable to reselect the given item.

https://github.com/dotnet/maui/pull/21490#discussion_r1623301225
The original issue also points to our samples, because our samples don't allow reselection.
https://github.com/dotnet/maui/issues/20273
So, it might be useful to update our samples so that re-selection works and users can see it working.

@PureWeen https://github.com/dotnet/maui-samples/pull/495


Links from API web pages include "you are leaving IoGT" notice

For example the "Django Rest Framework" link at top right

I'm not really sure what you are referring to. Would you provide more detail about the problem and how to reproduce it?

On this page: https://ss.goodinternet.org/api/v1/questionnaires/1/submissions/
These clickable links go through the "You are now leaving IoGT..." dialogue:

There don't seem to be any problems caused in the JSON output, only in the links which are added to the JSON output when viewing in a browser.