[Bug] Assertion about dynamic data sources failed

Bug report
A subgraph deployed into my graph node is failing with
thread 'QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC[2737]' panicked at 'assertion failed: self.hosts.last().and_then(|h| h.creation_block_number()) <=
    data_source.creation_block()', /graph-node/core/src/subgraph/context/instance.rs:136:9

I'm also seeing issues with the creation of runtime hosts.
Relevant log output
Nov 16 09:27:23.651 WARN no runtime host created, there is already a runtime host instantiated for this data source, address: 6261666b726569676875626d677572717070336b6d6f666c637663356635766c366661376b736f34657077737a366235366e73706d377669346c75, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
Nov 16 09:27:23.810 WARN no runtime host created, there is already a runtime host instantiated for this data source, address: 6261666b726569633671767073636c6d6f6570787473726e786d6f7a70326f3566777579756c6164753733773762677461366b35796c766c6c7779, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
Nov 16 09:27:31.856 WARN no runtime host created, there is already a runtime host instantiated for this data source, address: 6261666b726569676d32717264357366656c756a35367135783274673369706674676e6b7a6b37697a6b7a6e7868346a676f697965776d32697234, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
Nov 16 09:27:32.002 WARN no runtime host created, there is already a runtime host instantiated for this data source, address: 6261666b72656964643765377669706b36787978657078646a3468616268357a6e75717173326b65696e796b733433376f35326f69376536746561, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
thread 'QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC[2737]' panicked at 'assertion failed: self.hosts.last().and_then(|h| h.creation_block_number()) <=
    data_source.creation_block()', /graph-node/core/src/subgraph/context/instance.rs:136:9

IPFS hash
QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC
Subgraph name or link to explorer
No response
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
Linux

Some more logs. Here's what I see during indexer startup
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:47.911 DEBG Subgraph started, start_ms: 14, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphRegistrar
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:47.920 INFO Resolve subgraph files using IPFS, n_templates: 9, n_data_sources: 7, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:47.922 INFO Resolve offchain mapping, link: /ipfs/QmdtYrMLRLGywMcJQZeSAyMjJ3ZfCVRaHj3v2AwFPtFuux, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:48.156 INFO Successfully resolved subgraph files using IPFS, features: nonFatalErrors, grafting, n_templates: 9, n_data_sources: 7, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:48.195 INFO Starting subgraph writer, queue_size: 5, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:49.101 INFO Data source count at start: 16951, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:49.138 INFO forcing subgraph to use static filters., sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:55.577 DEBG Requesting 0 block(s), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:55.581 DEBG Starting or restarting subgraph, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:55.582 DEBG subscribing to chain head updates, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:55.617 DEBG Starting block stream, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager

Here are 3 different instances of the panic happening
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.721 DEBG Requesting logs for blocks [111450, 111949], contract 0x7777777f279eba3d3ad8f4e708545291a6fdba8b, 3 events, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.721 DEBG Requesting logs for blocks [111450, 111949], contract 0x7777777a456ff23d9b6851184472c08fbda73e32, 3 events, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.721 DEBG Requesting logs for blocks [111450, 111949], event 0xad59ebba8bfb06ba01a615a611467ca3bef86a275bd5e9704d3b295112550ba5, 2 contracts, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.722 DEBG Requesting logs for blocks [111450, 111949], event 0xa45800684f65ae010ceb4385eceaed88dec7f6a6bcbe11f7ffd8bd24dd2653f4, 2 contracts, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.722 DEBG Requesting logs for blocks [111450, 111949], contract 0x7777773606e7e46c8ba8b98c08f5cd218e31d340, 1 events, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.727 INFO Create data source, params: bafkreigu544g6wjvqcysurpzy5pcskbt45a5f33m6wgythpgb3rfqi3lzi, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.727 INFO Done processing trigger, gas_used:<PHONE_NUMBER>, data_source: ZoraCreator1155Impl, thread 'QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC[2737]' panicked at 'assertion failed: self.hosts.last().and_then(|h| h.creation_block_number()) <=\n    data_source.creation_block()', /graph-node/core/src/subgraph/context/instance.rs:136:9
zora-indexer-2-graph-node-67889449d8-94mlc graph-node handler: handleSetupNewToken, total_ms: 10, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: SetupNewToken(indexed uint256,indexed address,string,uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.730 INFO Done processing trigger, gas_used: 270057097, data_source: ZoraCreator1155Impl, handler: handleUpdatedPermissions, total_ms: 1, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedPermissions(indexed uint256,indexed address,indexed uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.777 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.777 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.778 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.779 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.781 DEBG Found 0 relevant block(s), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-2-graph-node-67889449d8-94mlc graph-node Nov 16 18:38:00.785 DEBG Requesting 0 block(s), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream

and another
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.408 DEBG Requesting logs for blocks [111450, 111949], event 0xa45800684f65ae010ceb4385eceaed88dec7f6a6bcbe11f7ffd8bd24dd2653f4, 2 contracts, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.408 DEBG Requesting logs for blocks [111450, 111949], contract 0x7777773606e7e46c8ba8b98c08f5cd218e31d340, 1 events, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: BlockStream
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.409 INFO Create data source, params: bafkreigu544g6wjvqcysurpzy5pcskbt45a5f33m6wgythpgb3rfqi3lzi, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.410 INFO Done processing trigger, gas_used:<PHONE_NUMBER>, data_source: ZoraCreator1155Impl, handler: handleURI, total_ms: 6, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: URI(string,indexed uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.411 DEBG eth_call, block_number: 110450, block_hash: 63a1d30b01071f9abdf9d93ca6c41c667204480a237eb80e4f3535863cbcdb23, data: 0e89341c0000000000000000000000000000000000000000000000000000000000000001, address: 027232b4613e7e243e2ea57c37094226b9671f50, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.415 INFO Create data source, params: bafkreigu544g6wjvqcysurpzy5pcskbt45a5f33m6wgythpgb3rfqi3lzi, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.416 INFO Done processing trigger, gas_used:<PHONE_NUMBER>, data_source: ZoraCreator1155Impl, handler: handleSetupNewToken, total_ms: 5, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: SetupNewToken(indexed uint256,indexed address,string,uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.417 INFO Done processing trigger, gas_used: 270057097, thread 'data_sourceQmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC[2737]: ' panicked at 'ZoraCreator1155Implassertion failed: self.hosts.last().and_then(|h| h.creation_block_number()) <=\n    data_source.creation_block(), ', handler/graph-node/core/src/subgraph/context/instance.rs: :handleUpdatedPermissions136:, 9total_ms
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node 1, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedPermissions(indexed uint256,indexed address,indexed uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.491 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.492 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.492 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.492 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-0-graph-node-78d7b9c565-tmrxg graph-node Nov 16 18:27:52.492 DEBG Subgraph stopped, WASM runtime thread terminated, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager

and another
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.630 INFO Create data source, params: bafybeicgolwqpozsc7iwgytavete56a2nnytzix2nb2rxefdvbtwwtnnoe/metadata, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.630 DEBG eth_call, block_number: 110450, block_hash: 63a1d30b01071f9abdf9d93ca6c41c667204480a237eb80e4f3535863cbcdb23, data: 13966db5, address: 027232b4613e7e243e2ea57c37094226b9671f50, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.634 DEBG eth_call, block_number: 110450, block_hash: 63a1d30b01071f9abdf9d93ca6c41c667204480a237eb80e4f3535863cbcdb23, data: a0a8e460, address: 027232b4613e7e243e2ea57c37094226b9671f50, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.639 DEBG eth_call, block_number: 110450, block_hash: 63a1d30b01071f9abdf9d93ca6c41c667204480a237eb80e4f3535863cbcdb23, data: e8a3d485, address: 027232b4613e7e243e2ea57c37094226b9671f50, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.648 INFO Create data source, params: bafybeicgolwqpozsc7iwgytavete56a2nnytzix2nb2rxefdvbtwwtnnoe/metadata, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.648 INFO Create data source, params: 0x027232b4613e7e243e2ea57c37094226b9671f50, name: ZoraCreator1155Impl, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.648 INFO Done processing trigger, gas_used:<PHONE_NUMBER>8, data_source: ZoraNFTCreatorFactory1155V1, handler: handleNewContractCreated, total_ms: 19, transaction: 0x2fb6…63ab, address: 0x6a35…6703, signature: SetupNewContract(indexed address,indexed address,indexed address,string,string,(uint32,uint32,address)), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.655 INFO Done processing trigger, gas_used: 251142831, data_source: ZoraCreator1155Impl, handler: handleUpdatedPermissions, total_ms: 6, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedPermissions(indexed uint256,indexed address,indexed uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.661 INFO Done processing trigger, gas_used: 489099942, data_source: ZoraCreator1155Impl, handler: handleUpdatedToken, total_ms: 6, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedToken(indexed address,indexed uint256,(string,uint256,uint256)), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.662 INFO Done processing trigger, gas_used: 176871672, data_source: ZoraCreator1155Impl, handler: handleUpdatedRoyalties, total_ms: 1, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedRoyalties(indexed uint256,indexed address,(uint32,uint32,address)), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.664 INFO Done processing trigger, gas_used: 259832522, data_source: ZoraCreator1155Impl, handler: handleOwnershipTransferred, total_ms: 1, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: OwnershipTransferred(address,address), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.668 INFO Done processing trigger, gas_used: 251142831, data_source: ZoraCreator1155Impl, handler: handleUpdatedPermissions, total_ms: 4, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedPermissions(indexed uint256,indexed address,indexed uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.672 INFO Done processing trigger, gas_used: 488981628, data_source: ZoraCreator1155Impl, handler: handleUpdatedToken, total_ms: 4, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedToken(indexed address,indexed uint256,(string,uint256,uint256)), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.676 INFO Done processing trigger, gas_used: 252614536, data_source: ZoraCreator1155Impl, handler: handleUpdatedPermissions, total_ms: 3, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedPermissions(indexed uint256,indexed address,indexed uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.678 DEBG eth_call, block_number: 110450, block_hash: 63a1d30b01071f9abdf9d93ca6c41c667204480a237eb80e4f3535863cbcdb23, data: 0e89341c0000000000000000000000000000000000000000000000000000000000000001, address: 027232b4613e7e243e2ea57c37094226b9671f50, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.682 INFO Create data source, params: bafkreigu544g6wjvqcysurpzy5pcskbt45a5f33m6wgythpgb3rfqi3lzi, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.683 INFO Done processing trigger, gas_used:<PHONE_NUMBER>, data_source: ZoraCreator1155Impl, handler: handleURI, total_ms: 6, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: URI(string,indexed uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.684 DEBG eth_call, block_number: 110450, block_hash: 63a1d30b01071f9abdf9d93ca6c41c667204480a237eb80e4f3535863cbcdb23, data: 0e89341c0000000000000000000000000000000000000000000000000000000000000001, address: 027232b4613e7e243e2ea57c37094226b9671f50, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.688 INFO Create data source, params: bafkreigu544g6wjvqcysurpzy5pcskbt45a5f33m6wgythpgb3rfqi3lzi, name: MetadataInfo, sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.689 INFO Done processing trigger, gas_used:<PHONE_NUMBER>, data_source: ZoraCreator1155Impl, handler: handleSetupNewToken, total_ms: 5, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: SetupNewToken(indexed uint256,indexed address,string,uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node Nov 16 18:39:59.690 INFO Done processing trigger, gas_used: 270057097, data_source: ZoraCreator1155Impl, handler: handleUpdatedPermissions, total_ms: 1, transaction: 0x2fb6…63ab, address: 0x0272…1f50, signature: UpdatedPermissions(indexed uint256,indexed address,indexed uint256), sgd: 2737, subgraph_id: QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC, component: SubgraphInstanceManager
zora-indexer-2-graph-node-5478c6c5c5-fwd9x graph-node thread 'QmbrEG3Ph195yb341q1utKWu1WiupaeSeYRGRTdZaDASqC[2737]' panicked at 'assertion failed: self.hosts.last().and_then(|h| h.creation_block_number()) <=\n    data_source.creation_block()', /graph-node/core/src/subgraph/context/instance.rs:136:9

Actually it's happened to 4 subgraphs

Actually this is happening for ~4 different subgraphs in our infra

Thanks @paymog

For the one above, we dropped it entirely (and removed all underlying data) then redeployed and everything worked perfectly.

You are saying that this happens intermittently?
Is there any pattern to the subgraphs, i.e. is it affecting File Data Sources, or any dynamic data source?

yup, seems to happen intermittently and only on some subgraphs.
I went through the drop and redeploy flow mentioned above for another subgraph today and was surprised to be confronted with this error log after the redeployment
Failed to start subgraph, code: SubgraphStartFailure, error: internal constraint violated: deployment sgd31426 must have been created before calling initialize_block_ptr but we got NotFound, sgd: 32135, subgraph_id: QmXbNGPEF78kmKZWkrPDvVctiVQGshcLQCoXe2wk5B5sTa, component: SubgraphInstanceManager

Restarting the indexer fixed the issue. I've never seen this error log before though.
It seems to be happening with dynamic data sources and the assertion mentioned seems to be part of the dynamic data sources code path.

I know of two situations that can trigger this assert:

Two Graph Nodes attempting to index the same deployment, in the same DB shard. This will cause race conditions and can manifest with that error.
This bug we fixed a while ago https://github.com/graphprotocol/graph-node/pull/4810, the fix is included in the latest release so you shouldn't see this issue with subgraphs you deployed on the latest release.

I know of two situations that can trigger this assert:

Two Graph Nodes attempting to index the same deployment, in the same DB shard. This will cause race conditions and can manifest with that error.
This bug we fixed a while ago fix(store): Fix rewinding of dynamic data sources #4810, the fix is included in the latest release so you shouldn't see this issue with subgraphs you deployed on the latest release.

We're running v0.33.0 so I guess the PR should in our build.
How would it be that 2 graph nodes attempt to index the same deployment? In the original case and the one I just mentioned, there definitely are multiple nodes running in the cluster. I wonder if this might be related to #5011 and #5014 which are showing issues with assigning subgraphs to specific indexers.

Sometimes graphman commands are not very obvious, which graphman commands do you typically run to manage assignments, and what documentation do you read for them (so we can make it better)?

Sometimes graphman commands are not very obvious, which graphman commands do you typically run to manage assignments, and what documentation do you read for them (so we can make it better)?

We use the JSON API to remove and change assignments, specifically the subgraph_reassign and subgraph_remove APIs. I also use graphman reassign when trying to do manual pausing/reassigning (eg when debugging the issue in #5011). I know it would be better to use graphman pause but that doesn't seem to have an API we can build automation around.
That being said, we should probably move this specific thread to one of the other issues and keep this issue focused on the assertion failure.

subgraph_remove and subgraph_reassign should stop the subgraph without requiring a restart of the index node, but it's not immediate, it can take a few seconds. Restarting the node does guarantee that it will stop. There is one situation I'm not sure of though:
On subgraph_reassign, from index node A to node B, then A will be notified to stop the subgraph and B will be notified to start the subgraph. My question is, does B make sure A has stopped before starting? @lutter, do you know? If B doesn't wait, then a race condition could happen where both are indexing the deployment. Though I'd think the error would clear with a restart of both nodes.

subgraph_remove and subgraph_reassign should stop the subgraph without requiring a restart of the index node, but it's not immediate, it can take a few seconds. Restarting the node does guarantee that it will stop. There is one situation I'm not sure of though:

Yup, that was our experience as well on prior versions of graph node. We never encountered issues like this on v0.33.0. However, for some reason we don't always see that behavior now.

@leoyvens is it safe to downgrade from 0.33.0 to 0.32.0?

@leoyvens will a new patch version with this fix be released anytime soon?


extra space in orderby crashes the query

I'm not sure if this is a bug or just my sloppy code but the following query works with Microsoft's OData implementation but crashes when I switch over to LinqToQuerystring
/api/purchases?$orderby=PurchasedOn+desc,+Id+desc

The issue is due to the extra + in the orderby right after the comma. If I remove it the query runs successfully.

+1
This is easy to handle if you're creating the url's yourself, however I'm using the OQuery library to generate the url's and it inserts spaces in the query which causes exceptions.
In my case it generates:
$filter=(%20substringof(%27thename%27,ParentFolderName)
which fails.
This succeeds:
$filter=(substringof(%27thename%27,ParentFolderName)


fixed issue 1

fixes #1

was having issues getting the environment setup.. added this but still didnt not fix.. forgot to remove..

LGTM!  Thanks!
(ideally you ought to not alter the Gemfile...but close enough :-p)


Bump the version of the stackdriver logging agent to 1.9

@pjh I haven't tested this manually. Can we merge this and see if anything fails?

:+1:

I just reverted this change (https://github.com/pjh/kubernetes/commit/dd563cb9b1d573c8af460785d700eeb83a35cdf0) because it may be causing our test nodes to fail and reboot. We'll see if the rebooting stops after reverting.
Current test run is 1330, so 1331 should be the first run that reverts back to Stackdriver 1.8. https://testgrid.k8s.io/google-windows#windows-prototype&width=20


[ui] No scope option disappears from drop down when adding API key

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Log in to Rancher.
Go to API & Keys.
Click Add Key button in top right.
In the Scope dropdown, note No Scope is selected. Select another scope. Now try to select "No Scope", but it's no longer there. It's gone, vanished, disappeared, forever lost! Well, not forever, you can cancel and add key again to work around this issue.

Result:

Other details that may be helpful:
Firefox 68.0.2 on MacOSX 10.14.6
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
v2.2.8, UI v2.2.94
Installation option (single install/HA):
HA

I have reproduced this, exactly as the issue describes in v2.3 (master-head (9/6/19)
I have also reproduced in v2.2.8
There are no browser dev console errors. I was unable to determine the cause.

Version: master-head (v2.3) (9/9/19)
The issue no longer occurrs. You can pick "No scope" after picking something else from the drop down. The API key is created without any issues. HTTP/API look good.


PyFerret SHADE box outlines overlap and obscure each other

Reported by andrew wittenberg on 10 Apr 2015 16:30 UTC
Plot the following:
 	NOAA/PMEL TMAP
 	FERRET v6.941 (PyFerret 1.2)
 	Linux 2.6.32-504.8.1.el6.x86_64 - 04/07/15
 	10-Apr-15 11:53

yes? set win/asp=.7 1; use coads_climatology; shade/l=1 sst

Then in the plot window "Image" pull-down menu, set "scale" to 10.  Note how the grid cells overlap, when they should abut.  Also, the corners of the cells are beveled instead of right angles.  I'll attach a section of the above plot as 2deg.png.
This causes much bigger problems for high-res grids, where the outline can actually be much wider than the grid cell itself.  See e.g. 0p1deg.png, which is a zoom into one of our 1/10 degree ocean models.  In this case the grid cells, which should be tiny squares that abut each other, instead appear as big octagons that are almost entirely overlapping.  This overlap leads to jagged artifacts, e.g. off the coast of the southeast U.S. in 0p1deg.png.
Is a thin outline drawn around each box?  (Was that to eliminate antialiasing artifacts?)  It'd be good if possible to set that line thickness to 0 (or as close as possible to 0) and also enable sharp 90deg corners.  And enable the user to turn the outline on or off somehow.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/2268

Comment by ansley.b.manke on 20 May 2015 00:10 UTC
Test: take out the drawing of lines around the rectangles in a SHADE plot or shapes in the FILL plots, and look in the PPLUS code to see if we can see what issues might be causing this. Maybe precision?

Comment by karl.smith on 19 Jun 2015 22:33 UTC
Removed drawing the outline around polygons, including rectangles.  This removed the overlap issue and the beveled edges issue.  So the zoomed-in displayed plot looks much better now.
This was to help with the "white lines" issues in some plots - PS and PDFs in particular if I remember correctly.  Need to see where the issue arises and look for a better fix.

Comment by karl.smith on 19 Jun 2015 22:56 UTC
So bnplot.pdf and closed_lev.pdf from the RUN_TESTS.sh benchmarks (found in bench/test_results/) do show the white lines when displayed with evince or acroread on my monitor.

Comment by ansley.b.manke on 19 Jun 2015 23:07 UTC
I'll be looking into the drawing code in PPLUS to see if there are places where precision might be increased to match the polygons and eliminate the white lines at their source.

Comment by andrew.wittenberg on 19 Jun 2015 23:44 UTC
It'll be wonderful if improved PPLUS precision could remove the non-abutting polygons issue at its source.  This has has caused the longstanding problems with white lines (due to mixing in the background color when antialiasing).  When Karl fixed that by adding outlines around each polygon, it led to the above issue, as well as an overlap that leads to darkened outlines when we use transparency in PyFerret.
If the PPLUS road doesn't work out, then one workaround might be to enable the user to set the outline width, with something like
SET MODE OUTLINE:width

where "width" is in micrometers or whatever; default would be 0.

Comment by karl.smith on 27 Aug 2015 21:51 UTC
This has also become an issue when using PyFerret within LAS.  The PNG plots displayed by LAS sometimes show the white lines.  The PDFs, when displayed by 'evince' (default PDF viewer in RHEL) also show the white lines, but when displayed by acroread (Acrobat reader - the official PDF viewer) they do not show up.
Ansley was seeing that adjacent polygons were drawn with edges at the exact same floating-point values.  When drawing rectangles and polygons, anti-aliasing is turned off regardless of user settings.  (User setting for anti-aliasing is used for lines and points; although it is also set for text, I think non-Hershey-font text will ignore it and always use anti-aliasing.)
The difference in appearance based on PDF viewers makes me think the problem is actually with the software used to display a high-resolution image on a monitor that cannot display that high of a resolution image.  This seems to argue in favour of some user control for adding the outlines, and their width, when drawing polygons.  I am thinking a SET WINDOW /OUTLINE= may be most consistent with what has already been done.

Comment by karl.smith on 30 Sep 2015 22:48 UTC
SET WINDOW /OUTLINE=... option added to PyFerret.  Default value is zero, which means no outline is drawn for polygons including rectangles.  When a positive (floating point) value is given, that is the line thickness of the outline for the polygons.  This line thickness is the same as the thickness for other lines drawn by PyFerret, including being scaled by the window line thickness scaling factor (SET WINDOW /THICK=....)  This outline is drawn with a miter join (instead of a bevel normally used by line drawings) so square corners have square outlines.
While not the ideal solution, this does allow the user to (artificially) fix the white lines problem that seems to keep showing up.  Where the white lines do not appear (or are not a problem), the default does not draw these outlines that is the source of the problem reported in this ticket.
Note that the scale bar is drawn with polygons, so the default shade or fill will outline these as well.  If the outline is thin (the normal use-case), this outline should not be noticeable as the boxes are outlined in black.

Comment by andrew.wittenberg on 1 Oct 2015 18:59 UTC
I'm looking forward to trying this out!
I'd suggest making SET WINDOW/OUTLINE have a default of whatever Ferret uses at the moment, rather than zero.  Mainly because it's counter-intuitive to say /OUTLINE and get no outline.  Whereas SET WINDOW/OUTLINE=0 is explicit and does what it says.  And that also saves the user from having to look up whatever the Ferret default is, if they ever want to restore it after a change.

Comment by karl.smith on 2 Oct 2015 00:00 UTC
Sorry, I was not clear what I meant by default.  If the user has never specified /OUTLINE=..., then there will not be any outlines drawn.  If the user specifies "SET WINDOW /OUTLINE", an error is generated saying "value out of legal range: Invalid outline width specification; a non-negative number must be given".  So usage will always be /OUTLINE= where float is non-negative.  I think it would be rather difficult to come up with a decent default non-zero outline width to use with "SET WINDOW /OUTLINE", so I opted to not even try.

Comment by andrew.wittenberg on 8 Oct 2015 01:56 UTC
Thanks very much!
One more question: has the drawing of the Hershey fonts been affected at all by the switch to a miter (rather than bevel) join for the SHADE outlines?  I'm noticing little corner artifacts at the acute angles of A's and M's, which I don't recall seeing before.
I may well be wrong -- actually it does look like the font "joins", like at the base of the number "2", are indeed beveled.  So perhaps the M's and A's are just drawn with multiple separate strokes, and so what I'm see are line "ends" rather than "joins".
Out of curiosity, are there any other options for ends and joins, like "rounded"?  I guess that could be expensive, if all the points of every curve had to be computed stored in the output file.  Unless there were some standard Cairo/Qt/PDF/PS primitives that were used for those curves.

Comment by andrew.wittenberg on 8 Oct 2015 02:12 UTC
After some experimentation, it seems like /OUTLINE=0.01 is a good compromise that cuts way down on the white lines in PostScript, while inducing very little overlap for a grid like that of coads_climatology.
It's great to have this user-settable though.  I'll turn up the outline for PostScript with coarse grids where the overlap is less visible, reduce the outline for fine grids, and just set it to zero for PDF.

Attachment from andrew.wittenberg on 10 Apr 2015 16:31 UTC
zoom into a 2-degree grid
REPLACE THIS TEXT WITH UPLOADED FILE ./attachments/TRAC_2268_GIT_1540/2deg.png

Attachment from andrew.wittenberg on 10 Apr 2015 16:31 UTC
zoom into a 1/10 degree grid
REPLACE THIS TEXT WITH UPLOADED FILE ./attachments/TRAC_2268_GIT_1540/0p1deg.png


Exception in thread "main" java.nio.file.NoSuchFileException: target/test-classes

Hi, all!
I tried to deal with this Gradle plugin and realized that it has not been updated for a long time (the latest commit was on Feb 16, 2015)
It is necessary to make at least two changes in this plugin:
Number 1.
final String GATLING_VERSION = '2.1.3' should be replaced by final String GATLING_VERSION = '2.2.0-SNAPSHOT'
Number 2.
OK, the above change will allow us to download gatling-charts-highcharts.
But what about the rest of dependencies?
For example, I observed the following errors:
Could not resolve all dependencies for configuration ':testCompile'.

Could not find com.nimbusds:nimbus-jose-jwt:2.22.1.
Could not find org.scala-lang:scala-library:2.11.6
........ and so on and so forth

Solution:
Need to add the line “mavenCentral()” to the list of repositories here:
project.repositories {
mavenCentral()
maven {
url 'http://repository.excilys.com/content/groups/public'
url 'https://oss.sonatype.org/content/repositories/snapshots'
}
}
After that I run ./gradlew from gradle-gatling-plugin directory once again (this by default places an artifact in mavenLocal)
Using the command “gradle gatlingTest” I finally managed to build .JAR file
But too early to celebrate, because gatling scenarios execution failed:
[ant:scalac] Element '/home/user/TEMP/scala/build/classes/main' does not exist.
[ant:scalac] Element '/home/user/TEMP/scala/build/resources/main' does not exist.
Executing gatling scenarios: [UserPermissionScenario]
Exception in thread "main" java.nio.file.NoSuchFileException: target/test-classes
Could you help solve this issue?

I got this issue too.
I had to create dir target/test-classes and copy the compiled class file from build/classes here.
I am using the latest version 1.2-SNAPSHOT.
Will this be fixed?
Should it not be looking in build/classes instead?

Hi Alexey, I'm not the maintainer but I doubt there would be an official release which had SNAPSHOT dependencies.  Perhaps a way to manually override the gatling version in your project's gradle file could be provided.

@shavo007 please submit a pull request if you have a working patch

Hi @alxndrsn ,
I didn't make a code change. It was a hack locally to get it to work!
It seems to me that even tho this is a gradle plugin and it should be looking inside build/classes, its expecting the maven folder structure of target/test-classes?

I'm seeing the same problem.  It is looking for target/test-classes instead of build/test-classes

You need to explicitly set the binaries folder either in gatling.conf or via command line (-bf or -sbf depending on the version you are using) to sourceSets.test.output.classesDir if you are using gradle.

This should be fixed on the master branch


specifying rustc version requirement in pcli installation docs

Just went through the process of installing pcli and got the following error:

failed to select a version for ibc-proto which could resolve this conflict

Fixed it by updating the rustc version to 1.7.3. Perhaps specifying it in the docs will save others some time.

Thanks!!


Return arbitrary fields

Currently return.all() returns all fields. It would be useful to introduce a method to specify an arbitrary list of fields to be returned.

I'm pretty sure this is an issue for https://github.com/redis/redis-om-node


Parse let expressions

parse an Identifier (i.e. variable) as an Expression
Identifier should own the str/String it holds. Now it does. Otherwise, do we really want our AST tied to the lifetime of the parsed source file?
renamed some things because they're more general now
make RawIdentifier hold a nameless field instead of naming the field name, because this was ridiculous: bindings.first().thing.variable_declaration.thing.name.thing.name

Identifier should own the str/String it holds. Now it does. Otherwise, do we really want our AST tied to the lifetime of the parsed source file?

I struggled with this, and I'm still not 100% certain of where I stand. Ultimately, I guess it boils down to: I expect that the entire AST will be held in some top-level structure that will, indeed, own the input string, so then why not make Identifiers hold references?

make RawIdentifier hold a nameless field instead of naming the field name, because this was ridiculous: bindings.first().thing.variable_declaration.thing.name.thing.name

lol
ok reviewing now

I struggled with this, and I'm still not 100% certain of where I stand. Ultimately, I guess it boils down to: I expect that the entire AST will be held in some top-level structure that will, indeed, own the input string, so then why not make Identifiers hold references?

That's a very reasonable position to take. I made this change on Feb 8. I can't recall now what motivated me to do this. I think that something I was trying to do was made harder by the reference lifetime.

...
I can see what happens when I revert this specific change... if you want me to?

No, don't bother reverting it. It is a bit early to be "optimizing" stuff, esp. something that's not a super-clear 100% definite win. Tell you what - add a comment that "hey, this is something that might make sense in the future" and I'll be satisfied.


Generate a new dataset?

Is there in the repository any code that given a set of tweets produces a suitable dataset?
I mean a dataset in the format  [{ id, text, count }].
I could do it manually but how should I compute count for each tweet? Is it the number of retweets? What is it exactly?

The preprocessing is not in the scope of this library. It was designed to support any text and not limited to Tweets. We believe the users of this library should be able to convert from their own data source into this simple format by themselves.
The count can be retweets, likes, or any number you want it to be. This is used to determine how important that Tweet is, and affect the word size.


Assigns Rules first and DeviceTypes next as serial calls

From @ganeshx on January 18, 2018 14:13
null
Copied from original issue: hashmapinc/Timeseries#135

From @jetinder20 on January 30, 2018 6:42
This is not needed as now the device types are assigned at backend. So just assigning rules is required


Remove instance labels for metrics with instance=-1

We're assuming that instances with a -1 value cannot possibly have multiple instances. If that's the case, then the label is unnecessary, so you should avoid creating it in the first place.

Addressed by PR #10


Use javascript to get tag_name for ElementCollection elements

This replaces #802, updated due to rebase conflicts

When the selector does not contain :tag_name, we are currently querying the tag_name from the element. This causes N wire calls which, depending on how many elements there are, can take a while when testing remotely.
The idea is to us the javascript executor to retrieve all the tags once. In doing so, we do miss out on the added benefit of element_call which #tag_name uses, but that shouldn't be an issue as we have already located the elements.
The only concern I could think of was with elements going stale between retrieving them and then performing javascript on them, but this should be a rare scenario. This is mitigated by the rescue and retry. Theoretically there is a chance for an infinite loop on the retry, but the likelihood of that is near impossible in normal conditions.

Pull Request Test Coverage Report for Build 1927

15 of 15 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 97.554%

Totals

Change from base Build 1920:
0.01%

Covered Lines:
2313

Relevant Lines:
2371

💛  - Coveralls

Pull Request Test Coverage Report for Build 1927

15 of 15 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 97.554%

Totals

Change from base Build 1920:
0.01%

Covered Lines:
2313

Relevant Lines:
2371

💛  - Coveralls

Pull Request Test Coverage Report for Build 1927

15 of 15 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 97.554%

Totals

Change from base Build 1920:
0.01%

Covered Lines:
2313

Relevant Lines:
2371

💛  - Coveralls

Pull Request Test Coverage Report for Build 1927

15 of 15 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 97.554%

Totals

Change from base Build 1920:
0.01%

Covered Lines:
2313

Relevant Lines:
2371

💛  - Coveralls

Updated and moved the js to a snippet. Also added a new spec to ensure we're getting the right container back without specifying tag_name


Breaking bloblang regression in 3.43.0 with path references

Create this config.yaml and run with

echo '{"Metadata":{"job-id":"abc"}}' | benthos -c config.yaml

input:
  stdin:
    codec: lines

pipeline:
  processors:
    - bloblang: |
        root = this
        meta "a" = this.Metadata."job-id"
    - bloblang: |
        root = this
        meta "b" = json("Metadata.job-id")
    - bloblang: |
        root = this
        meta "c" = this.Metadata.job-id

logger:
  format: classic

On Benthos 3.42.1 this will succeed but on 3.43.0 it will fail.
If you delete the last bloblang processor c from the config then it will work on both versions.

It looks like the parser is not reading - as subtraction operator

Ok, I guess the previous behaviour was technically a bug?

Bloblang compressed arithmetic expressions with field names (foo+bar) now correctly parse.

Hey @razor-x, yeah this is an unfortunate consequence of the previous parser being too relaxed around allowed path characters. The correct way to do this would be to quote the path segment containing symbols, so in your case it would be this.Metadata."job-id".
The runtime error is also trash, which really doesn't help. I've recently improved them in:  https://github.com/Jeffail/benthos/commit/9427cc3367f268d3dc5a35d764d314b69e68ddd0, and running that gives you failed assignment (line 2): cannot subtract types null (from field this.Metadata.job) and null (from field this.id).
I think given the possibility of others hitting this same issue with kebab-case fields I might publish the improved error messages ASAP as a patch release, and I'll leave this issue open so that others than find it easier if they have similar problems.


Niloofar/ Added tests for MobileMenu component

This PR includes:

MobileMenu component tests

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 75.81%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
4686

Relevant Lines:
5593

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 75.81%

Totals

Change from base Build<PHONE_NUMBER>:
0.07%

Covered Lines:
4686

Relevant Lines:
5593

💛  - Coveralls


skopeo: build manpage

Success on x86_64-linux (full log)
Attempted: skopeo
Partial log (click to expand)
/nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29/share/go/src/github.com/projectatomic/skopeo/hack/make/validate-lint: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29/share/go/src/github.com/projectatomic/skopeo/hack/make/validate-git-marks: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29/share/go/src/github.com/projectatomic/skopeo/hack/make/test-integration: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29/share/go/src/github.com/projectatomic/skopeo/hack/make/validate-vet: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29/share/go/src/github.com/projectatomic/skopeo/hack/make/validate-gofmt: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29/share/go/src/github.com/projectatomic/skopeo/hack/make.sh: interpreter directive changed from "/usr/bin/env bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29/share/go/src/github.com/projectatomic/skopeo/hack/libdm_tag.sh: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
/nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29/share/go/src/github.com/projectatomic/skopeo/hack/btrfs_tag.sh: interpreter directive changed from "/bin/bash" to "/nix/store/q1g0rl8zfmz7r371fp5p42p4acmv297d-bash-4.4-p19/bin/bash"
checking for references to /build in /nix/store/25xkxc74smgnlwpaxsvi78d5bpafnhkv-skopeo-0.1.29...
/nix/store/zpivmk1faj0ra2cf0jsc9cjiix27ys7r-skopeo-0.1.29-bin


Manganis: Preserve Folder Files By Default

Adds a optimize_files option for FolderAsset e.g.
const FOLDER_OPTIONS: FolderAssetOptions = FolderAssetOptions::new().with_optimize_files(true);

If the flag is set, the file will go under minor processing. The flag defaults to false.

I think we originally wanted Folders to retain their asset names internally but have a different name externally - did that change? I'm ambivalent to either so @ealmloff can make the final call

Why should we have a different default for optimizations for folders vs files? I would expect these two to point to the same asset:
const FOLDER: ASSET = asset!("/myfolder");
const ASSET: ASSET = asset!("/myfolder/asset.js");

rsx! {
   script { src: "{FOLDER}/asset.js" }
   script { src: ASSET }
}

I'm mixed between both approaches, but I think it should be opt-in for consistency.

IMO asset-optimization ought to be opt-in in general. People wanted asset optimization will likely go looking for a setting and find it easily enough. People not wanting optimization are more likely to be surprised by it happening.


OpenSSL EDIPartyName denial of service

OpenSSL EDIPartyName denial of service
cveid: 2020-1971

I'm not sure what you're trying to tell us. That bug / CVE has
been fixed in the latest releases.


Publish binaries to Releases

It would be useful to publish binaries (HtmlGenerator.exe etc) to https://github.com/KirillOsenkov/SourceBrowser/releases so users can download and run the app without having to build it theirself

Workaround: download NuGet package https://www.nuget.org/packages/Microsoft.SourceBrowser , extract Tools folder from .nupkg


Live preview for pages other than the index page

Hi there,
Thanks for the Amazing Package. Just wondering how can we use the live preview per a post. I have it working for the index page but can get the preview working for when I just want to preview a single post.
I keep getting the following error:
TypeError: useReducer only works in Client Components. Add the "use client" directive at the top of the file to use it.

Hi, give this a look: https://github.com/sanity-io/sanity-template-nextjs-appdir-personal-website/blob/main/app/(personal)/projects/[slug]/page.tsx
Other than that, based on the error message it sounds like you need to add use client at the top of the file that exports a React component that calls the usePreview hook :relaxed:

Thanks for sharing the repo. I'll have a look. I have added use client to everywhere I have used usePreview but still no luck :(

By the way although this has given me a headache Sanity is so Amazing!

Ah it was because I was using the wrong PreviewSuspence component. Thanks for pointing me in the right direction 👍

Happy to hear you figured it out @nizam0786! 🎉


[ENG-1354, 1415] Fixes bottom sidesheet and ReactFlow alignment issues

Describe your changes and why you are making these changes
This PR fixes two bugs around the layout of the ReactFlow canvas and the bottom sidesheet:

The fix for ENG-1354 is around calling fitView at the right time. Because we were previously calling fitView on componentDidMount, it didn't actually work on the first load because the nodes and edges were loaded in after the component was mounted. This PR changes the fitView effect so that it also is called when the node/edge positions are changed, which causes the view to be fit correctly (after a small lag) on first load.
This PR also fixes ENG-1415 simplifies absolute positioning of the bottom side sheet so that it properly aligns with the ReactFlow viewport (see screenshot below):

(Ignore the miscolored artifacts; that's because my local backend isn't updated.)

Related issue number (if any)
Checklist before requesting a review

[x] I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
[x] I have performed a self-review of my code.
[x] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
[N/A] If this is a new feature, I have added unit tests and integration tests.
[N/A] I have run the integration tests locally and they are passing.
[x] I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
[x] All features on the UI continue to work correctly.
[x] Added one of the following CI labels:

run_integration_test: Runs integration tests
skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

Looks good, remember to also update the version number of @aqueducthq/common here as well.
We can say something like v0.0.11-rc.0 so as not to have too many version numbers.
Here's how the folks at emotion do it:


Fix repetitive formatting with VisualStudioRazorParser

Formatting a document => Undoing => Formatting does not work.

Turns out this issue lies in the fact that the new VisualStudioRazorParser does not have a concept of TreeStructureChanged in its DocumentStructureChangedEventArgs.
The editor was utilizing TreeStructureChanged to determine if its formatters needed to regenerate their formattable artifacts for the current document. In reality the editor should be utilizing its C# projections as a source of truth when determining if artifacts should be regenerated; to work around this I made the editor track the current and previous parse and compare the SourceLineMappings of both to determine if formatter artifacts needed to be regenerated.


models: Add plan_type to Realm.

@hackerkid fyi, separating out this commit from the rest.
Tim: one thing I wanted to check was the migration default. Should that function be copied into the migration file as well?

Updated to remove the funny migration stuff, so this should be more straightforward now.

Merged, after extending a comment in models.py as to what this is for.  We'll want to add more comments there around how these values are different as they start to impact the API.  Thanks @rishig!


Takes a long time to load on gallery

I was try your sample app with my Lenovo and cannot take the picture, when get inside the gallery just loading but no image to show. How i supposed to do

Should be fixed in https://github.com/esafirm/android-image-picker/releases/tag/1.13.1


Quickstart Documentation

Add documentation on how to run the application including short description about submodules.

@Ghesselink who's reviewing it?

Done
rebase and update readme
Merge branch 'development-0.6' into quickstart_documentation
I'd also be nice to add a link to each individual task (to be able to run them separately). At the risk of asking an obvious question; am I correct to say that BSDD has not been added yet?


{Compute} BREAKING CHANGE: Support Trusted Launch as default deployment option

Related command

az vm/vmss create
Description

Merge changes from:
#27636
#27722
#27635
Close: #23450
Close: #23476
Close: #23440
Testing Guide

History Notes

[Compute] BREAKING CHANGE: az vm/vmss create: Support Trusted Launch as default deployment option when creating vm/vmss with marketplace image
[Compute] BREAKING CHANGE: az vm/vmss create: Support Trusted Launch as default deployment option when creating vm/vmss from existing disk or image
[Compute] BREAKING CHANGE: az vm/vmss create: Support Trusted Launch as default deployment option when creating vm/vmss with minimal inputs

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Compute

/azp run


Add base Node 12.14.0

This PR adds a base image with Node 12.14.0.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Size of iOS versions very large - is this normal for RN apps ?

Hi! Thanks for trying out NativeBase!
Due to the overwhelming requests and issues/questions we ask you to add the following details with your issue.
Please check the existing open/closed issues for a possible duplicate before creating a new issue :)
Also DO fill out the below form to give us a better idea about your environment and help us debug it quicker. Issues without the required details will mostly be unattended to.
react-native, react and native-base version
Expected behaviour
Actual behaviour
Steps to reproduce (code snippet or screenshot)
Screenshot of emulator/device
Is the bug present in both ios and android or in any one of them?
Any other additional info which would help us debug the issue quicker.

Nevermind, the actual size that gets in the store with app thinning and all is much smaller.


Compile assets instructions unclear

The docs say to compile assets instructions with
go-bindata -pkg bindata -o bindata/bindata.go config/providers/... ui/assets/... ui/views/...
but does not say what the ellipses are supposed to represent. Am I supposed to type something where the ellipses are? I would like to go on record suggesting the ban of the usage of ellipses in urls, as the user does not know what they are supposed to represent, only the person who wrote them.

In general, it looks like the README needs to be redone I could not contribute if I wanted to, because the instructions are so outdated.

@zwhitchcox If you're familiar with Golang, you'll understand that the ellipses represent all child packages in the directory. 🙂 Go-bindata follows this convention. Some browsing through the go-bindata docs and FAQ may clear up some confusion as well. 🙂

Ah, ok, my mistake, I'm fairly new to go, so I did not know that, but good info!


[PE-D][Tester B] Adding names and addresses over a certain length are truncated and the user has no way to extract that information

Steps to reproduce:

Add a name or address that is longer than a certain length in the software. for e.g add n/sdlbsdjlfbdfljfhaldfadljbvladb a/dvkdbjvadjlvbladvdbvljdabvl
Attempt to extract the full name or address by opening the closer view using view
Observe that the name or address has been replaced by ... in the software, making it impossible to extract the full information.

Expected:
The software should allow for the input and extraction of names and addresses of any length, without truncating the information, at the very least for addresses as those can be pretty long.
Actual:
Names and addresses over a certain length get replaced by "..." in the software, making it impossible to extract the full information.
Issue:
When names and addresses are truncated by the software, it can make it impossible to accurately manage and extract information related to individuals. This can lead to confusion and errors when managing data and can negatively impact the user experience. For example, if the delivery person have no way to view the address, they may not be able to deliver the parcel to the correct location. To improve the software, it is recommended that the software be updated to allow for the input and extraction of names and addresses of any length, without truncating the information. This will enable users to more effectively manage and access information, improving the overall user experience.
Screenshot:

Labels: severity.High type.FunctionalityBug
original: Tohtoroo/ped#5

Duplicated bug (refer to issue #132)


New Organization Day 0: walkthrough/automation example

20230714: to review

https://github.com/ssc-spc-ccoe-cei/gcp-documentation/blob/main/Architecture/Repository Structure.md#hydration-process
Short Sequence
get a new org (kcc-kls) (cloudlift reserved for interconnect use case)
start at https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md
above points to https://github.com/ssc-spc-ccoe-cei/gcp-documentation
issue to make it clearer where to start in gcp-documentation https://github.com/ssc-spc-ccoe-cei/gcp-documentation/issues/25
if we start at the following for an unmanaged install - it also back references 2nd above https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md#organization for interleaved content
https://github.com/ssc-spc-ccoe-cei/gcp-documentation/blob/main/Landing Zone Operations/Building.md
run https://github.com/ssc-spc-ccoe-cei/gcp-tools/blob/main/scripts/bootstrap/setup-kcc.sh
above deprecates https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/advanced-install.md
review https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/onboarding-admin.md
continue review of setup-kcc.sh https://github.com/ssc-spc-ccoe-cei/gcp-tools/issues/32

20230523: udpate

kcc cluster up via https://github.com/ssc-spc-ccoe-cei/gcp-tools/issues/32 with secure boot disable and wait state on project creation

Issues pending

DI1: add sleep(30) on project creation to avoid failure on VPC creation - see PR https://github.com/ssc-spc-ccoe-cei/gcp-tools/pull/38
DI2: add options for org and billing id generation from current project
DI3: add check on constraints/compute.requireShieldedVm - make sure it is off to avoid GKE creation failure (it is set by previous runs of the LZ) - see https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/issues/132

moving back to main readme

20230503: update
Adjust in place the following script in the gcp-tools repo
https://github.com/ssc-spc-ccoe-cei/gcp-tools/blob/main/scripts/bootstrap/setup-kcc.sh
https://github.com/ssc-spc-ccoe-cei/gcp-tools/issues/32

see https://github.com/ssc-spc-ccoe-cei/gcp-documentation/issues/12
see https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/issues/344
Older walk through
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/issues/33
Work Items:

migrate/retrofit script to landing-zone-v2 from https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/dev/solutions/landing-zone/deployment.sh
complete https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/solutions/landing-zone-v2/README.md#gke-autopilot---fully-managed-cluster use https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/dev/docs/advanced-install.md#gke-autopilot---recommended

General Docs

https://kustomize.io/

Onboarding:

follow the 10 step Google Cloud Setup Checklist https://cloud.google.com/docs/enterprise/setup-checklist

Start with a clean organization - in this case Cloud Identity based

remove the "Project Creator" and "Billing Account Creator" IAM roles and move them to the super admin identity account
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/issues/290

2nd environment: kcc.landing.systems

 gcloud config set project kcc-kls
 mkdir kcc-kls
 cd kcc-kls/

move deployment.sh from #192 and retrofit for v2
mkdir CloudLandingSystems
git clone https://github.com/CloudLandingZone/pubsec-declarative-toolkit.git
cd pubsec-declarative-toolkit/
cd solutions/
cd landing-zone-v2/
git checkout canary
cp ../landing-zone/deployment.sh .
cp ../landing-zone/vars.sh .
rm -rf ../landing-zone/deployment.sh
rm -rf ../landing-zone/vars.sh
git add deployment.sh
git add vars.sh
git add ../landing-zone/
git commit -m "#192 - move deployment sh to v2"
git push origin canary

LZ V2 install - follow

https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit
need link from above to
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/tree/main/solutions/landing-zone-v2
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md
follow documentation link
https://github.com/ssc-spc-ccoe-cei/gcp-documentation
determine which procedure to use to bootstrap a default landing zone
the LZ operations link looks relevant
https://github.com/ssc-spc-ccoe-cei/gcp-documentation/blob/main/Landing Zone Operations/Building.md#landing-zone-building
place a PDT link to https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md below
https://github.com/ssc-spc-ccoe-cei/gcp-documentation/blob/main/Landing Zone Operations/Building.md#3-deploy-the-infrastructure-using-either-kpt-or-gitops-git-or-gitops-oci

modifying
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/blob/main/docs/landing-zone-v2/README.md#initial-organization-configuration
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ export REGION=northamerica-northeast1
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ export PROJECT_ID=kcc-kls
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ export NETWORK=vpc-pdt
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ export SUBNET=vpc-pdt-sn
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ export ORG_ID=$(gcloud projects get-ancestors $PROJECT_ID --format='get(id)' | tail -1)
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ echo $ORG_ID
156483884993
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ export PROJECT_ID=$(gcloud config list --format 'value(core.project)')
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ echo $PROJECT_ID
kcc-kls
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ gcloud alpha logging settings update --organization=$ORG_ID --storage-location=$REGION
name: organizations/156483884993/settings
storageLocation: northamerica-northeast1
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ export BILLING_ID=$(gcloud alpha billing projects describe $PROJECT_ID '--format=value(billingAccountName)' | sed 's/.*\///')
root_@cloudshell:~/kcc-kls/CloudLandingSystems/pubsec-declarative-toolkit (kcc-kls)$ echo $BILLING_ID
015254-F59978-C1E833

Align with ACM alignment across docs in https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/issues/349

returning from https://github.com/ssc-spc-ccoe-cei/gcp-tools/issues/32
CC cluster up - installing minimum LZ V2

Move to kcc.landing.systems
follow
https://cloud.google.com/anthos-config-management/docs/concepts/config-controller-overview
from
export CLUSTER=kcc-kls
export REGION=northamerica-northeast1
export PROJECT_ID=kcc-kls-cluster
export LZ_FOLDER_NAME=kcc-lz-20230802
export NETWORK=kcc-kls-vpc1
export SUBNET=kcc-kls-sn1
export ORG_ID=1564838...
export ROOT_FOLDER_ID=444332200332
export BILLING_ID=01A4...
#export GIT_USERNAME=<Git-Username> # For Azure Devops, this is the name of the Organization
#export CONFIG_SYNC_REPO=<Repo for Config Sync> # tierX repo URL
#export CONFIG_SYNC_VERSION='HEAD'
#export CONFIG_SYNC_DIR=<Directory for config sync repo which syncs> # Should default to csync/deploy/<env>

root_@cloudshell:~/kcc-kls/20230719/gcp-tools/scripts/bootstrap (kcc-kls)$ ./setup-kcc.sh -f pdt-kls.env

##INFO - Update the logging for region

kmsServiceAccountId<EMAIL_ADDRESS>loggingServiceAccountId<EMAIL_ADDRESS>name: organizations/156483884993/settings
storageLocation: northamerica-northeast1

##INFO - create folder and project

Create in progress for [https://cloudresourcemanager.googleapis.com/v1/projects/kcc-kls-cluster].
Waiting for [operations/cp.7418676574276417307] to finish...done.
Enabling service [cloudapis.googleapis.com] on project [kcc-kls-cluster]...
Operation "operations/acat.p2-630577449085-fcb8f6cb-0970-4a84-872c-dde3178ce3e5" finished successfully.
Updated property [core/project] to [kcc-kls-cluster].

##INFO - Link billing account

installing lz

ongoing #296 day0 instructions
#296 -  day0 install readme must include 2 core-landing-zone pkg instructions link
make the instructions clearer on the 2 step quickstart - to avoid client confusion

install the kcc cluster
install a default landing-zone-v2 - composed of the dual pkg - core-landing-zone and experimentation/core-landing-zone

verified all link changes
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/pull/443

the following
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/pull/441
was affected by
https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/pull/447
TODO: check all incoming links into files moved into the legacy folder for redirection
see one change in https://github.com/GoogleCloudPlatform/pubsec-declarative-toolkit/issues/475


Split tests into separate files & other cleanup

+1

Other than comments on a couple of verbose statements, +1

!squash


Investigate Gesture Sensor

The SPIKE Prime Hub can recognize taps on the device. Maybe also the TechnicMediumHub since it exposes the internal device.

Port Mode Info
  Port: 100
    IOTypeId: TechnicMediumHubGestSensor
    HardwareRevision: <IP_ADDRESS>
    SoftwareRevision: <IP_ADDRESS>
    OutputCapability: False
    InputCapability: True
    LogicalCombinableCapability: False
    LogicalSynchronizableCapability: False
    ModeCombinations: []
    UsedCombinationIndex: 0
    MultiUpdateEnabled: False
    ConfiguredModeDataSetIndex: []
    Mode: 0
      Name: GEST
      IsInput: True
      IsOutput: False
      RawMin: 0
      RawMax: 4
      PctMin: 0
      PctMax: 100
      SIMin: 0
      SIMax: 4
      Symbol:
      InputSupportsNull: False
      InputSupportFunctionalMapping20: True
      InputAbsolute: False
      InputRelative: False
      InputDiscrete: True
      OutputSupportsNull: False
      OutputSupportFunctionalMapping20: False
      OutputAbsolute: False
      OutputRelative: False
      OutputDiscrete: False
      NumberOfDatasets: 1
      DatasetType: SByte
      TotalFigures: 1
      Decimals: 0
      DeltaInterval: 0
      NotificationEnabled: False

Value is discrete and can be between 0 and 4. Which would conclude to 4-5 gestures. SPIKE Prime specification list 3 gestures: free fall, tap, shake. I rudimentary mapped them the following ... however .. the sensor emits many of them for the free fall and tapping is a pretty rough gesture. So that could be also crash or something.
    public enum Gesture : int
    {
        None = 0, // UNSPECED
        Tap = 1, // UNSPECED
        Gesture_2 = 2,
        Shake = 3, // UNSPECED
        FreeFall = 4, // UNSPECED
    }

Asked Bricks Community


Rewrite HX-Trigger support in HtmxResponse

@wimdeblauwe I have updated the PR so that the API no longer breaks. Would you mind taking a second look?


Arena allocator refactor

This refactors the implementation to use an arena allocator.
The StringDTypeObject struct gains two new fields: int array_owned and npy_string_allocator *allocator. The array_owned flag is used to indicate if an array owns the descriptor or not and the allocator is used to mediate heap memory access and allocation.
The main new feature here is that newly created arrays store data in a contiguous buffer that lives inside an npy_string_arena struct (that itself is an attribute of the allocator struct). There's only one arena per dtype instance - as declared with the NPY_DT_UNIQUE_ARRAY_DESCRIPTOR flag on the DType with bookeeping managed via the array_owned flag.
The allocator and arena structs look like this:

typedef struct npy_string_arena {
    size_t cursor;
    size_t size;
    char *buffer;
} npy_string_arena;

typedef void *(*npy_string_malloc_func)(size_t size);
typedef void (*npy_string_free_func)(void *ptr);
typedef void *(*npy_string_realloc_func)(void *ptr, size_t size);

struct npy_string_allocator {
    npy_string_malloc_func malloc;
    npy_string_free_func free;
    npy_string_realloc_func realloc;
    npy_string_arena arena;
};

Heap-allocated string data lives in allocator->arena->buffer. Internally the buffer works by prepending each string allocation with a field indicating the size of the string. Right now it's always a size_t, but that adds a lot of overhead for small strings (alignment makes it worse) so I'd like to add a mode where small heap strings have lengths stored in a char or unsigned char.
Another nice aspect of this is now packed heap strings that are in the arena don't store a memory address directly, instead they now store an offset into the arena.
I still have it set up so that if you modify an existing string and the modification would exceed the available space to store that string, the modified string is allocated on the heap using malloc/free directly.
The bookeeping for this is mediated via the new NPY_STRING_ARENA_FREED and NPY_STRING_ON_HEAP flags. The former indicates a packed string that is freed but not yet overwritten. The latter indicates a packed string that corresponds to a string allocated directly on the heap, outside the arena buffer. Unfortunately this uses up the two unused flag bits we had available, although we still have four flags available for non-short strings.

Tests are passing again.
I'm very aware this is an unreviewably large PR. @seberg do you have any desire to look over these changes at a high level?
I realized that I do actually need to store the allocation size, so I need to come back to the over-allocation issues related to that. I'd also like to figure out if it's possible to do a final realloc after the array buffer is fully initialized to resize the sidecar buffer to only what's needed. I'd like to do that in a followup, though.
For now I've xfailed the test that's failing due to a ufunc error because upstream changes in numpy to handle python integers in ufuncs. I'll also come back to this later or fix it upstream in numpy.

Happy if you just merge.  I can try to have a look over soonish, but overall, it's probably just as well to continue.  Do you have anything specific you would like me to look at closer?

OK, let's pull this in then. I think we've hashed out the bits I wanted you to look carefully at already and I think the high-level design is fine and more or less matches what's in the NEP already.

About a potential array-is-filled hook.  I don't mind the idea in general, since it could be useful.  But do wonder if we need it here.  Because we may mutate the array anyway or use it for buffers.  OTOH, making an immutable string array seems like it could be worthwhile and that may just be the right approach.
I also slightly wonder if traversal during the GC might actually be better point where to do memory management book-keeping (if necessary).

We should have a traversal function for GC traversal.  However, I will note that NumPy simply doesn't do GC traversal currently.  (which I hate, but no review meant fixing it never went anywhere, although now with the new traversals adding it might also be a bit saner.)

I guess you're referring to https://github.com/numpy/numpy/pull/15065? Reviving that might be more than I can take on right now but let's chat a bit about this at today's triage meeting if you're going to be there. Something like this is needed if we want to move to heap types, I think.

It's actually not hard to do now, TBH.  So we either one or both of:

Jus talways set the flag and don't try to be smart
Ignore any reference cycles that may occur due to the dtype itself.

That PR wasn't even particlarly tricky, just ugly and with that subtlety above that I don't have a clear answer to.  Plus a large chunk of "is it slow?", which I honestly don't want to even start answering, because it also is a clear bug.


Fixes wsgi.py app_path to avoid deleting all /config occurrences.

Fixes #1466 using parent directory instead of replacing /config in app_path.

it not solve problem at heroku.

@joseGabriel06 please explain in detail what's wrong.


⚠ BeyondHD has degraded performance

In 31e85cf, BeyondHD ($BHD) experienced degraded performance:

HTTP code: 200
Response time: 2143 ms

Resolved: BeyondHD performance has improved in a5ca65a after 9 minutes.


Use Promise.all in NativeStakingMapper

Changes

Optimizes NativeStakingMapper by using Promise.all to parallelize API calls.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 46.335%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/transactions/mappers/common/native-staking.mapper.ts
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>2:
0.008%

Covered Lines:
4811

Relevant Lines:
8361

💛  - Coveralls


formatting data for arcgis

This notebook includes reference codes for the final process of data pipeline: formatting the data for arcgis.

Thanks! I also link to this notebook in issue #110, where I list all the code that will be useful to write the data pipeline notebook.


Enable-AzureADDirectoryRole is implemented by New-MgDirectoryRole, not New-MgDirectoryRoleTemplate

The equivalent Graph endpoint of Enable-AzureADDirectoryRole is indeed POST /directoryRoles as confirmed in the Graph API doc: https://learn.microsoft.com/en-us/graph/api/directoryrole-post-directoryroles?view=graph-rest-1.0&tabs=http
And this endpoint, is accessible via the New-MgBetaDirectoryRole Graph PowerShell cmdlet as confirmed by:
PS> Find-MgGraphCommand -Uri '/directoryRoles'

   APIVersion: v1.0

Command             Module                       Method URI             OutputType                   Permissions                                                                                Variants
-------             ------                       ------ ---             ----------                   -----------                                                                                --------
Get-MgDirectoryRole Identity.DirectoryManagement GET    /directoryRoles IMicrosoftGraphDirectoryRole {Directory.Read.All, Directory.ReadWrite.All, RoleManagement.Read.Directory, RoleManagement.ReadWrite.Directory} {List}
New-MgDirectoryRole Identity.DirectoryManagement POST   /directoryRoles IMicrosoftGraphDirectoryRole {RoleManagement.ReadWrite.Directory}                                                                             {Create, CreateExpanded}

So, the replacement for Enable-AzureADDirectoryRole is New-MgDirectoryRole, and not New-MgDirectoryRoleTemplate as currently documented

@CelesteDG - ok to merge.


feat: revamp two split body

What

Adds two split view

How
To use the component you will add a <TwoSplitPane></TwoSplitPane> which can hold two BodyCard components as children. If you add more then two children the component will throw an error.
Responsiveness
I've added some very rudimental responsiveness to the component, but I definitely think we should revisit this once Ludvig has taken a look at how this component should look on different screen sizes.
Note
PR feat/revamp-buttons and fix/icon-type should be merged beforehand

Should the BodyCard be able to be used without putting it in a TwoSplitPane?
If you try that now it's still half split, I would suggest we make it full width and have the TwoSplitPane adjust the width of the BodyCard. Then in sub menus with only one side we would still use the TwoSplitPane and have the same halving effect, but we can use the BodyCard for full width components.
I.e remove medium:w-1/2 from the outer div of BodyCard and adjust the TwoSplitPane to map children like so:
{Children.map(children, (child, i) => {
  return (

      {child}

  )
})}

Should the BodyCard be able to be used without putting it in a TwoSplitPane?
If you try that now it's still half split, I would suggest we make it full width and have the TwoSplitPane adjust the width of the BodyCard. Then in sub menus with only one side we would still use the TwoSplitPane and have the same halving effect, but we can use the BodyCard for full width components.
I.e remove medium:w-1/2 from the outer div of BodyCard and adjust the TwoSplitPane to map children like so:
{Children.map(children, (child, i) => {
  return (

      {child}

  )
})}

Totally agree! I've added it to the update 👍


Use mplhep for plotting

https://mplhep.readthedocs.io/en/latest/index.html

Done as of eb30e987e1969e2ee656db72df92993b4142cb5c


fix: add ability to use custom flatlist implementation

Add ability to use custom Flatlist as component with example
Before: Flatlist does not scroll when used inside bottomsheet
https://github.com/user-attachments/assets/780cc5b0-069a-4dfd-9a86-92ac0c654774
After: Using BottomSheetFlatlist which scrolls when used inside @gorhom/bottom-sheet
https://github.com/user-attachments/assets/3e0af8e9-fd53-4db1-8628-d424288f9b1b

updated patch version based on suggestion: https://github.com/10play/10tap-editor/pull/170#issuecomment-2254365308
Please let me know if it is to be reverted
If this patch version update is to be kept, this PR is to be merged after #172

@17Amir17 I've updated this branch too.
Previous branch to refer comments: #170


Add GitHub Action support for PHP Grpc

#76 has added the PHP related scripts for generating the GRPC stubs in PHP, so all the PHP related code will be fully automated after we create its GitHub Action.
It will great if @zhangchunsheng  can create another PR to implement it.

I will add Github Action when I have time.

Awesome! Looking forward to adding the GitHub Action for PHP to our GRPC service!

I have added php action.

Fantastic! Thank you very much for improving our DevOps pipeline for PHP Wechaty!


gtk application bugs

Unsure if this has to do with sway but
on gtk applications, I can only right click once, then the functionality of right clicking will be disabled until I restart the program. Also drop down menus hardly display correctly.

Dupe https://github.com/SirCmpwn/sway/issues/571

@Cloudef: pretty please fix this


Maprefs

Finally figured out how to upload Bowtie1 .ebwt index files!!!!
Using Git LFS (supports larger files)
Hope this won't make downloads more difficult

I think all reference files are now uploaded


Fixed 8 dictionaries with dic and aff mixed up

Regenerated the following that had the dic and aff files mixed up to fix #2

bulgarian
czech
galician
greek
russian
turkish
ukrainian
vietnamese

Thanks @Thomas101! I opted to use patch versions instead, as these are definitely bug fixes.
I’ll release in a sec!

Published, thanks again, and do let me know if you find something else wrong with this project. Great to see it being used :)

Awesome! Thank you and thanks for your work on this. It's super useful :-)


QA: Delete an account

Delete a Hedera account using AccountDeleteTransaction.

###Code Example
https://github.com/hashgraph/hedera-sdk-cpp/blob/main/sdk/examples/DeleteAccountExample.cc
#include "AccountCreateTransaction.h"
#include "AccountDeleteTransaction.h"
#include "Client.h"
#include "ED25519PrivateKey.h"
#include "PublicKey.h"
#include "Status.h"
#include "TransactionReceipt.h"
#include "TransactionResponse.h"

#include <iostream>

using namespace Hedera;

int main(int argc, char** argv)
{
  if (argc < 3)
  {
    std::cout << "Please input account ID and private key" << std::endl;
    return 1;
  }

  // Get a client for the Hedera testnet, and set the operator account ID and key such that all generated transactions
  // will be paid for by this account and be signed by this key.
  Client client = Client::forTestnet();
  const AccountId operatorAccountId = AccountId::fromString(argv[1]);
  client.setOperator(operatorAccountId, ED25519PrivateKey::fromString(argv[2]));

  // Generate a ED25519 private, public key pair
  const std::shared_ptr<PrivateKey> privateKey = ED25519PrivateKey::generatePrivateKey();
  const std::shared_ptr<PublicKey> publicKey = privateKey->getPublicKey();

  std::cout << "Generated private key: " << privateKey->toStringRaw() << std::endl;
  std::cout << "Generated public key: " << publicKey->toStringRaw() << std::endl;

  // Create a new account with an initial balance of 2 Hbars. The only required field here is the key.
  TransactionResponse txResp =
    AccountCreateTransaction().setKey(publicKey).setInitialBalance(Hbar(2LL)).execute(client);

  // Get the receipt when it becomes available
  TransactionReceipt txReceipt = txResp.getReceipt(client);

  const AccountId newAccountId = txReceipt.mAccountId.value();
  std::cout << "Created new account with ID " << newAccountId.toString() << std::endl;

  // Delete the newly-created account
  txReceipt = AccountDeleteTransaction()
                .setDeleteAccountId(newAccountId)
                .setTransferAccountId(operatorAccountId)
                .freezeWith(&client)
                .sign(privateKey)
                .execute(client)
                .getReceipt(client);

  std::cout << "Deleted account with response code: " << gStatusToString.at(txReceipt.mStatus) << std::endl;

    return 0;
}

Output
Generated private key: 46F281EA435373D82DC4F136E61884199BCABD55A89A0F4EBE4CC456BFB1929F
Generated public key: 351AD91E190E7574A051B20555D1213F3150146D7BA0B83F1B12460A68071B48
Created new account with ID 0.0.5868767
Deleted account with response code: SUCCESS


Support extension wallets by serving a website on localhost

Added a way to connect extension wallets: using a localhost web server to forward signature requests to the browser.

Hi @artistic709 ,
Could you elaborate a bit on the use case you have in mind please?
There is a plan to run anvil on localhost to be able to fork etc, which would make it possible to connect eclair and the browser wallet to the same development node. Is it what you have in mind?

Hi @danhper , this is the scenario I'm considering:
I want to send transactions in production environment via command line. Rather than using a hardware wallet or importing a private key, I would prefer to use, say, a MetaMask account to sign transactions.

Ahhh, I see, that makes sense! In theory this is definitely doable but it might be a bit of work, especially given that alloy does not seem to support anything like this out of the box.
I think that the flow could look like:

Spin up an http server to serve a very simple webpage (the page doesn't really need to do anything)
Spin up a websocket server to communicate between eclair and the webpage
Connect from the webpage to eclair's websocket server
When eclair needs to sign something, send a request to the webpage via ws
Request the signature from metamask and sent it back to eclair via ws
Send the signed tx in eclair

This does look like a fun little project but there are a few things I'll be prioritising before it, so I can't really give a timeline for when I think it might be ready.
If you'd like to give it a shot, I'm of course more than open to contributions!
Thanks again for the idea!

Yeah I think that will be really helpful for advanced users.
Unfortunately I don't write Rust, but I can make a proof of concept in Python + vanilla JS.
BTW the 5th and 6th steps might not work
because it's very difficult (if not impossible) to ask MetaMask to sign a raw transaction.
Instead, we'll just let MetaMask broadcast the tx and wait for the txid to come back.

I see, thanks for the explanation! Yeah, then the transaction would be sent by metamask and the txid would be sent back to eclair via websocket.
A proof-of-concept would be super helpful and the JS part could be used directly, so that would definitely be very welcome, thanks!


Create CODE_OF_CONDUCT.md

Codecov Report

Merging #1 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #1   +/-   ##
=======================================
  Coverage   97.45%   97.45%
=======================================
  Files          22       22
  Lines        1337     1337
=======================================
  Hits         1303     1303
  Misses         17       17
  Partials       17       17

Continue to review full report at Codecov.

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


TensorBoard support?

As it's based on pix2pix (which had a good tensorflow implementation with tensorboard support) does DualGAN support tensorboard? What is the logdir?

Thanks for your feedback. I will add some logs when I get some time.
On 27 August 2017 at 10:37, Buleandra Cristian<EMAIL_ADDRESS>wrote:

As it's based on pix2pix (which had a good tensorflow implementation with
tensorboard support) does DualGAN support tensorboard? What is the logdir?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/duxingren14/DualGAN/issues/5, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACc6ew-Sq-ZUcaBMY-Ay7z99wVuoNuYZks5scallgaJpZM4PD3YU
.


Adds auto batch tracer support for JS

CC @nfcampos @hinthornw
Unit tests TODO but seems like it works via integration test.
Supersedes #383

@hinthornw @nfcampos have added unit tests 👍