A secret that will never be readable stops calling itself a race (hq issue 225)
The harness says 'secret not readable yet' when it cannot open a consumer's sealed credential, which is true and ordinary on the first pass. It said it 4330 times in three hours on the control machine while two consumers were never provisioned, because a permission the host will never grant reads exactly like a file that has not arrived. After about a minute it says so plainly instead, once and then rarely, and names what to look at: who owns the file and who this process runs as. The ownership itself is the controller's to fix. 0.1.9.
This commit is contained in:
Generated
+2
-2
@@ -1,12 +1,12 @@
|
||||
{
|
||||
"name": "@novox/mesh-sdk",
|
||||
"version": "0.1.8",
|
||||
"version": "0.1.9",
|
||||
"lockfileVersion": 3,
|
||||
"requires": true,
|
||||
"packages": {
|
||||
"": {
|
||||
"name": "@novox/mesh-sdk",
|
||||
"version": "0.1.8",
|
||||
"version": "0.1.9",
|
||||
"devDependencies": {
|
||||
"@types/node": "^22.0.0",
|
||||
"typescript": "^5.6.0"
|
||||
|
||||
Reference in New Issue
Block a user