Basically, if the deployer is setup correctly, but the laconic.yml is misconfigured (and so doesn't publish records) we end up in a situation where an app has actually deployed, but isn't registered onchain.
This is expected deployer behaviour (AFIACT) but could confuse users
Basically, if the deployer is setup correctly, but the `laconic.yml` is misconfigured (and so doesn't publish records) we end up in a situation where an app has actually deployed, but isn't registered onchain.
example: https://pwa-test-13-b311b1142a.pwa.kenz.world
this app has no DnsRecord or ApplicationDeploymentRecord, but the deployer deployed it.
This is expected deployer behaviour (AFIACT) but could confuse users
Tight consistency isn't possible here, but the deployer could do some sort of pre-flight check that its config is correct, I think -- try to publish a test record, something like that.
Tight consistency isn't possible here, but the deployer could do some sort of pre-flight check that its config is correct, I think -- try to publish a test record, something like that.
i think all that's needed here is for the deployer logs to surface laconic failures, or even just the logs normally viewed at the UI --> green deployed button --> black screen with logs, to be included in the deployer logs
i think all that's needed here is for the deployer logs to surface `laconic` failures, or even just the logs normally viewed at the UI --> green deployed button --> black screen with logs, to be included in the deployer logs
2024-08-18 14:07:53.652126 - bafyreif4kgenticfrbyf4zmbaup2xqavvoaigns4xmllsdzghugsiyvxfa-1723990011-34db9321 - 0:00:00.001761 (step): Publishing DnsRecord.
record:
meta:
so: 5f79f7368e2841718c83d7d369101be3
name: pwa-test-613-03bea2fad1.pwa.realitynetwork.store
request: bafyreif4kgenticfrbyf4zmbaup2xqavvoaigns4xmllsdzghugsiyvxfa
resource_type: A
type: DnsRecord
version: 0.0.1
laconic -c /etc/config/laconic.yml registry record publish --filename /tmp/tmp1npf8erv/record.yml
laconic -c /etc/config/laconic.yml registry name set lrn://lcn-example/dns/pwa-test-613-03bea2fad1.pwa.realitynetwork.store bafyreics5ayn7jyuhdp5ovkhymtkc7tix2orvhfkmnkm5b5mg7rf43ilaq
laconic registry name set [name] [id]
Set name (create name to record ID mapping).
Options:
--version Show version number [boolean]
-v, --verbose Verbose output [boolean] [default: false]
-c, --config Config file path. [string] [default: "config.yml"]
-o, --output Gives output in json format when specified. [string]
--user-key [string]
--tx-key [string]
--bond-id [string]
--chain-id [string]
-f, --filename
--id [string]
--address [string]
--gas [string]
--fees [string]
--help Show help [boolean]
TimeoutError: Transaction with ID 49BEA6FE54B16B7914BFDD28EDE632BE859AB0212CEC1985F744C7160E76CAAF was submitted but was not yet found on the chain. You might want to check later. There was a wait of 60 seconds.
at pollForTx (/usr/lib/node_modules/@cerc-io/laconic-registry-cli/node_modules/@cosmjs/stargate/build/stargateclient.js:249:23)
at pollForTx (/usr/lib/node_modules/@cerc-io/laconic-registry-cli/node_modules/@cosmjs/stargate/build/stargateclient.js:265:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
txId: '49BEA6FE54B16B7914BFDD28EDE632BE859AB0212CEC1985F744C7160E76CAAF'
}
rm -rf /tmp/tmp1npf8erv
2024-08-18 14:09:19.980237 - bafyreif4kgenticfrbyf4zmbaup2xqavvoaigns4xmllsdzghugsiyvxfa-1723990011-34db9321 - 0:01:26.328098 (step): ERROR: Command '('laconic', '-c', '/etc/config/laconic.yml', 'registry', 'name', 'set', 'lrn://lcn-example/dns/pwa-test-613-03bea2fad1.pwa.realitynetwork.store', 'bafyreics5ayn7jyuhdp5ovkhymtkc7tix2orvhfkmnkm5b5mg7rf43ilaq')' returned non-zero exit status 1.
2024-08-18 14:09:19.980317 - bafyreif4kgenticfrbyf4zmbaup2xqavvoaigns4xmllsdzghugsiyvxfa-1723990011-34db9321 - 0:02:27.981609 (total): DONE with status ERROR
see https://git.vdb.to/cerc-io/laconicd/issues/55 for a commonly encountered error:
```
2024-08-18 14:07:53.652126 - bafyreif4kgenticfrbyf4zmbaup2xqavvoaigns4xmllsdzghugsiyvxfa-1723990011-34db9321 - 0:00:00.001761 (step): Publishing DnsRecord.
record:
meta:
so: 5f79f7368e2841718c83d7d369101be3
name: pwa-test-613-03bea2fad1.pwa.realitynetwork.store
request: bafyreif4kgenticfrbyf4zmbaup2xqavvoaigns4xmllsdzghugsiyvxfa
resource_type: A
type: DnsRecord
version: 0.0.1
laconic -c /etc/config/laconic.yml registry record publish --filename /tmp/tmp1npf8erv/record.yml
laconic -c /etc/config/laconic.yml registry name set lrn://lcn-example/dns/pwa-test-613-03bea2fad1.pwa.realitynetwork.store bafyreics5ayn7jyuhdp5ovkhymtkc7tix2orvhfkmnkm5b5mg7rf43ilaq
laconic registry name set [name] [id]
Set name (create name to record ID mapping).
Options:
--version Show version number [boolean]
-v, --verbose Verbose output [boolean] [default: false]
-c, --config Config file path. [string] [default: "config.yml"]
-o, --output Gives output in json format when specified. [string]
--user-key [string]
--tx-key [string]
--bond-id [string]
--chain-id [string]
-f, --filename
--id [string]
--address [string]
--gas [string]
--fees [string]
--help Show help [boolean]
TimeoutError: Transaction with ID 49BEA6FE54B16B7914BFDD28EDE632BE859AB0212CEC1985F744C7160E76CAAF was submitted but was not yet found on the chain. You might want to check later. There was a wait of 60 seconds.
at pollForTx (/usr/lib/node_modules/@cerc-io/laconic-registry-cli/node_modules/@cosmjs/stargate/build/stargateclient.js:249:23)
at pollForTx (/usr/lib/node_modules/@cerc-io/laconic-registry-cli/node_modules/@cosmjs/stargate/build/stargateclient.js:265:19)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
txId: '49BEA6FE54B16B7914BFDD28EDE632BE859AB0212CEC1985F744C7160E76CAAF'
}
rm -rf /tmp/tmp1npf8erv
2024-08-18 14:09:19.980237 - bafyreif4kgenticfrbyf4zmbaup2xqavvoaigns4xmllsdzghugsiyvxfa-1723990011-34db9321 - 0:01:26.328098 (step): ERROR: Command '('laconic', '-c', '/etc/config/laconic.yml', 'registry', 'name', 'set', 'lrn://lcn-example/dns/pwa-test-613-03bea2fad1.pwa.realitynetwork.store', 'bafyreics5ayn7jyuhdp5ovkhymtkc7tix2orvhfkmnkm5b5mg7rf43ilaq')' returned non-zero exit status 1.
2024-08-18 14:09:19.980317 - bafyreif4kgenticfrbyf4zmbaup2xqavvoaigns4xmllsdzghugsiyvxfa-1723990011-34db9321 - 0:02:27.981609 (total): DONE with status ERROR
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Basically, if the deployer is setup correctly, but the
laconic.ymlis misconfigured (and so doesn't publish records) we end up in a situation where an app has actually deployed, but isn't registered onchain.example: https://pwa-test-13-b311b1142a.pwa.kenz.world
this app has no DnsRecord or ApplicationDeploymentRecord, but the deployer deployed it.
This is expected deployer behaviour (AFIACT) but could confuse users
Tight consistency isn't possible here, but the deployer could do some sort of pre-flight check that its config is correct, I think -- try to publish a test record, something like that.
i think all that's needed here is for the deployer logs to surface
laconicfailures, or even just the logs normally viewed at the UI --> green deployed button --> black screen with logs, to be included in the deployer logssee cerc-io/laconicd#55 for a commonly encountered error: