Effect unit tests tests are failing

$ NODE_ENV=prod npm run test                                                                                12:04:43 PM

> test
> vitest --run

 RUN  v0.32.4 /Users/br/code/5esheets/dnd5esheets/front

 ✓ src/effects/parser/index.test.ts (10)
 ❯ src/effects/index.test.ts (18)
   ❯ apply effect (18)
     ✓ applies a static effect
     ✓ applies a derived effect
     × applies a derived effect which updates from its dependency
     ✓ applies a nested derived effect
     × applies a nested derived effect which updates from its dependency
     ✓ applies a deeply nested derived effect
     × applies a nested derived effect which updates from its dependency
     ✓ applies a non-computed nested derived effect
     × applies a non-computed nested derived effect which updates from its dependency
     ✓ applies a non-computed deeply nested derived effect
     × applies a non-computed deeply nested derived effect which updates from its dependency
     ✓ applies an effect containing a function
     ✓ applies a derived effect containing a function
     × applies a derived effect containing a function which updates from its dependency
     × applies a somewhat complex effect which updates from its dependency
     × applies a somewhat complex effect on a nested target which updates from its dependency
     × applies a nested derived effect on a sibling target which updates from its dependency
     ↓ applies a derived effect containing a function which updates from its dependency [skipped]

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 9 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a derived effect which updates from its dependency
AssertionError: expected 1 to be 2 // Object.is equality

- Expected
+ Received

- 2
+ 1

 ❯ src/effects/index.test.ts:40:25
     38|       setContext("a", 2);
     39|       expect(context.a).toBe(2);
     40|       expect(context.b).toBe(context.a);
       |                         ^
     41|     }));
     42|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:35:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/9]⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a nested derived effect which updates from its dependency
AssertionError: expected 1 to be 2 // Object.is equality

- Expected
+ Received

- 2
+ 1

 ❯ src/effects/index.test.ts:55:25
     53|       applyEffect("b := nested.a", context, setContext);
     54|       setContext("nested", "a", 2);
     55|       expect(context.b).toBe(context.nested.a);
       |                         ^
     56|     }));
     57|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:51:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[2/9]⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a nested derived effect which updates from its dependency
AssertionError: expected 1 to be 2 // Object.is equality

- Expected
+ Received

- 2
+ 1

 ❯ src/effects/index.test.ts:74:25
     72|       applyEffect("b := deeply.nested.a", context, setContext);
     73|       setContext("deeply", "nested", "a", 2);
     74|       expect(context.b).toBe(context.deeply.nested.a);
       |                         ^
     75|     }));
     76|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:68:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[3/9]⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a non-computed nested derived effect which updates from its dependency
AssertionError: expected 1 to be 2 // Object.is equality

- Expected
+ Received

- 2
+ 1

 ❯ src/effects/index.test.ts:89:25
     87|       applyEffect("b := nested[key]", context, setContext);
     88|       setContext("nested", "a", 2);
     89|       expect(context.b).toBe(context.nested.a);
       |                         ^
     90|     }));
     91|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:85:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/9]⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a non-computed deeply nested derived effect which updates from its dependency
AssertionError: expected 1 to be 2 // Object.is equality

- Expected
+ Received

- 2
+ 1

 ❯ src/effects/index.test.ts:112:25
    110|       applyEffect("b := nested[key_][key__]", context, setContext);
    111|       setContext("nested", "a_", "a__", 2);
    112|       expect(context.b).toBe(context.nested.a_.a__);
       |                         ^
    113|     }));
    114|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:104:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[5/9]⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a derived effect containing a function which updates from its dependency
AssertionError: expected 1 to be 2 // Object.is equality

- Expected
+ Received

- 2
+ 1

 ❯ src/effects/index.test.ts:134:25
    132|       applyEffect("b := id(a)", context, setContext);
    133|       setContext("a", 2);
    134|       expect(context.b).toBe(context.a);
       |                         ^
    135|     }));
    136|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:130:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[6/9]⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a somewhat complex effect which updates from its dependency
AssertionError: expected 3 to be 4 // Object.is equality

- Expected
+ Received

- 4
+ 3

 ❯ src/effects/index.test.ts:150:25
    148|       );
    149|       setContext("nested", "a", 2);
    150|       expect(context.d).toBe(4);
       |                         ^
    151|     }));
    152|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:138:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[7/9]⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a somewhat complex effect on a nested target which updates from its dependency
AssertionError: expected 3 to be 4 // Object.is equality

- Expected
+ Received

- 4
+ 3

 ❯ src/effects/index.test.ts:167:32
    165|       );
    166|       setContext("nested", "a", 2);
    167|       expect(context.effect.d).toBe(4);
       |                                ^
    168|     }));
    169|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:154:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[8/9]⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a nested derived effect on a sibling target which updates from its dependency
AssertionError: expected 1 to be 2 // Object.is equality

- Expected
+ Received

- 2
+ 1

 ❯ src/effects/index.test.ts:179:32
    177|       applyEffect("nested.d := nested.a", context, setContext);
    178|       setContext("nested", "a", 2);
    179|       expect(context.nested.d).toBe(context.nested.a);
       |                                ^
    180|     }));
    181|
 ❯ src/effects/index.test.ts:11:7
 ❯ Module.createRoot node_modules/solid-js/dist/server.js:53:14
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:171:5

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[9/9]⎯

 Test Files  1 failed | 1 passed (2)
      Tests  9 failed | 18 passed | 1 skipped (28)
   Start at  12:06:33
   Duration  506ms (transform 91ms, setup 0ms, collect 193ms, tests 20ms, environment 414ms, prepare 111ms)

Every single failing test has from its dependency in the test description. I'm thinking there's something wrong when it comes to propagating dependent changes.

Tests are ... passing with node 18.16.0 and failing with node 20.3.1.

I've defined a Dockerfile for the frontend, as such
FROM node:18.16.1
WORKDIR /usr/src/app
COPY package-lock.json .
COPY package.json .
RUN npm install

and built it with cd dnd5esheets/front && docker build -t 5esheets-front .. In then renamed my local node_modules to node_modules-old to avoid shadowing the node_modules in the container, and ran cd dnd5esheets/front && docker run -it -v "$(pwd)/:/usr/src/app/"  5sheets-front bash
root@3195b611cbe7:/usr/src/app# npm exec vitest --config vitest.config.js  src/effects/index.test.ts  src/effects/parser/index.test.ts

 DEV  v0.32.2 /usr/src/app

 ✓ src/effects/parser/index.test.ts (10)
 ✓ src/effects/index.test.ts (18)

 Test Files  2 passed (2)
      Tests  27 passed | 1 skipped (28)
   Start at  12:27:26
   Duration  4.35s (transform 164ms, setup 1.28s, collect 368ms, tests 17ms, environment 2.50s, prepare 415ms)

That works

I then built another docker image defined as
FROM node:20.2.0-bullseye-slim
WORKDIR /usr/src/app
COPY package-lock.json .
COPY package.json .
RUN npm install

and ran the same steps. This time, the tests failed:
root@92519af685a1:/usr/src/app# npm exec vitest --config vitest.config.js  src/effects/index.test.ts  src/effects/parser/index.test.ts

 DEV  v0.32.2 /usr/src/app

 ✓ src/effects/parser/index.test.ts (10)
 ❯ src/effects/index.test.ts (18)
   ❯ apply effect (18)
     × applies a static effect
     × applies a derived effect
     × applies a derived effect which updates from its dependency
     × applies a nested derived effect
     × applies a nested derived effect which updates from its dependency
     × applies a deeply nested derived effect
     × applies a nested derived effect which updates from its dependency
     × applies a non-computed nested derived effect
     × applies a non-computed nested derived effect which updates from its dependency
     × applies a non-computed deeply nested derived effect
     × applies a non-computed deeply nested derived effect which updates from its dependency
     × applies an effect containing a function
     × applies a derived effect containing a function
     × applies a derived effect containing a function which updates from its dependency
     × applies a somewhat complex effect which updates from its dependency
     × applies a somewhat complex effect on a nested target which updates from its dependency
     × applies a nested derived effect on a sibling target which updates from its dependency
     ↓ applies a derived effect containing a function which updates from its dependency [skipped]

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 17 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  src/effects/index.test.ts > apply effect > applies a static effect
TypeError: Cannot read properties of undefined (reading 'registerGraph')
 ❯ Module.createStore node_modules/solid-js/store/dist/dev.js:213:9

 ❯ src/effects/index.test.ts:21:37
 ❯ src/effects/index.test.ts:11:7
 ❯ updateFn node_modules/solid-js/dist/dev.js:180:17
 ❯ runUpdates node_modules/solid-js/dist/dev.js:800:17
 ❯ Module.createRoot node_modules/solid-js/dist/dev.js:185:12
 ❯ src/effects/index.test.ts:10:5
 ❯ inRoot src/effects/index.test.ts:9:9
 ❯ src/effects/index.test.ts:20:5
 ...

@etnbrd do you want to try to debug this, or should we pin node to 18.16.1 and call it a day?

Frontend tests are succeeding when using node 18.16.1 in CI: https://github.com/brouberol/5esheets/actions/runs/5464409518/jobs/9946400764?pr=97

Cool. I've added an .nvmrc file containing the node version we pinned the project to, installable via nvm.
~/code/5esheets main *2 ❯ node --version
v18.16.1
~/code/5esheets main *2 ?3 ❯ make front-test

 [+] Running the frontend tests

> test
> vitest

 DEV  v0.32.2 /Users/br/code/5esheets/dnd5esheets/front

 ✓ src/effects/parser/index.test.ts (10)
 ✓ src/effects/index.test.ts (18)

 Test Files  2 passed (2)
      Tests  27 passed | 1 skipped (28)

We're all good!


If we have enough data, what will the model achieve for hard SQL?

We are afraid that the hard SQL like TABLE JOIN is the limit for industrial application.
Thank you very much.

it is very hard to say. Even the way of how questions are asked could change the results a lot.


[@azure/arm-marketplaceordering] does not work

@azure/arm-marketplaceordering
1.3.1
Windows/Linux
[x] nodejs

14.7.0

Describe the bug
Got the following error while trying to invoke get operation:
Cookie not in this host's domain. Cookie:storeapi.azure.com Request:management.azure.com
To Reproduce
Execute the following code:
const { TokenCredentials } = require('@azure/ms-rest-js');
const { MarketplaceAgreements, MarketplaceOrderingAgreements } = require('@azure/arm-marketplaceordering');

const token = '<USER TOKEN>';
const subscription = '<SUBSCRIPTION>';
const agreements = new MarketplaceAgreements(new MarketplaceOrderingAgreements(new TokenCredentials(token), subscription));
const response = await agreements.get('publisherId','offerId', 'planId');

Expected behavior
Marketplace agreement information expected
Additional context
The reason for this issue is that @azure/arm-marketplaceordering depends on "@azure/ms-rest-js": "^1.6.0"
Invalid cookie domain issue was fixed in @azure/ms-rest-js 2.0.2
https://github.com/Azure/ms-rest-js/blob/master/Changelog.md#202---2019-07-08

Thanks for reporting and getting to the root cause @sashakorman!
@qiaozha Can we have the package re-generated using the latest v4 of the code generator so that the fix to @azure/ms-rest-js is absorbed?

@ramya-rao-a  Can you help review this PR #10428 Thanks

@sashakorman<EMAIL_ADDRESS>Can you please try 2.0.0 version of this package to see if it works ? Thanks

@qiaozha thank you for the quick fix. Everything works as expected now.


Add Tap-zendesk_sell

Migrated from GitLab: https://gitlab.com/meltano/hub/-/issues/185
Originally created by @tayloramurphy on 2022-01-18 14:18:43

Community created tap with the SDK https://github.com/leag/tap-zendesk_sell

View 4 previous comments from the original issue on GitLab


CREATE/DROP plan node cleanup and executors

It's not gonna pass CI yet, but looking for feedback on the overview of changes:

There's a static util class in execution/sql that can take in CREATE or DROP plan nodes along with an ExecutionContext and perform the operation. Is this the API we want? Names are undecided and easy to change. I'm not happy with them right now.
I gutted any fields that weren't required to execute these plan nodes. Note: I did not remove fields that we would eventually want to support (i.e. constraints for CREATE TABLE).  I only removed fields that legitimately seemed redundant.
Removed SetFromCreateStatement and SetFromDropStatement methods on plan node Builders. These were used for a few contrived tests, but represent a special case code path that will not be used in the real system. All plan nodes will be generated by going through the parser, binder, and optimizer.
Removed references to skiplist and ART indexes from PostgresParser. I'm not a fan of dead code coming over from Peloton.
Unclear how to write meaningful tests that aren't just coverage fluff at the moment. Will revisit tomorrow.
Typing up #635 pretty much convinced me that IF EXISTS should not be in physical plan nodes so I removed that field, but that issue exists to discuss it.

While working on this, I realized that the only drop operation that currently cascades in the Catalog is drop database. In an effort to limit the scope of this PR, I'm pushing cascading to the next PR since we'll still need that behavior, particularly for drop namespace for #632.

Want to also document that this PR strengthens the asserts in the Catalog and removes some TODOs related to IF EXISTS and future expected behavior from the binder. I will open a new issue for that.


DNS Bruteforce Injection Point Definition

Adding Injection Point indicator in DNS Bruteforce Process in order to expand the subdomain enumeration capabilities.
The modified code can be triaged using the following execution line:
go run main.go dns -t 50 -d *-app.abumedia.yql.yahoo.com -w wordlist.txt
Result:
===============================================================
Gobuster v3.0.1
by OJ Reeves (@TheColonial) & Christian Mehlmauer (@_FireFart_)
===============================================================
[+] Domain:     *-app.abumedia.yql.yahoo.com
[+] Threads:    50
[+] Timeout:    1s
[+] Wordlist:   /Users/hdbreaker/Desktop/Scripts/DirBuster/directory-list-lowercase-2.3-medium.txt
===============================================================
2019/07/27 15:19:58 Starting gobuster
===============================================================
2019/07/27 15:19:58 [-] Warning: Injection char (*) was provided, no base domain validation will be performed!
Found: news-app.abumedia.yql.yahoo.com
Found: tv-app.abumedia.yql.yahoo.com
===============================================================
2019/07/27 15:20:06 Finished
===============================================================

If the * character is not provided Gobuster will work as before.

this is possible in v3.1-working with the patterns option. Thanks for the PR and sorry for the long waittime!


refactor: hook new uniq() command using new format

Fixes the new uniq() command to use the new format. This also adds a test to make sure it permits globbing (this was broken after merging #452 because of a recent refactor).

I'm going to go ahead and merge this, since it just updates to the new refactor.
LGTM


XML::Reader#expand changes

Makes XML::Reader#expand raise a XML::Error if the node could not be expanded.
Adds a new method XML::Reader#expand? that retains the previous behavior of returning nil on error.

Anything left to do here?

Thank you


Mysql

Hi!
I have been successful cross compiling outstation-demo using openGDB for armbian(orangePI r1). I have a problem which I do not know how to handle it. How can I add mysql to this project? If I should change the makefile, how?
Thanks!

Install opendnp3 as a library:

sudo make install

The default location will be /usr/local/lib and /usr/local/include
You can then use opendnp3 like any other library in your project that integrates it w/ mysql.


Adds CoreOS Support

Adds initial support for running Kubernetes on CoreOS. This commit
adds :

Tasks and files to install pypy to CoreOS.
ansible_python_interpreter was added to group_vars/all.yml to
reference the Python installation path.

Roles were updated to reference systemd unit files or dropins
that are specific to CoreOS.

Conditional logic added throughout based on the
ansible_lsb.id == "CoreOS" system fact.

Closes Issue: https://github.com/kubernetes/contrib/issues/406

Some nits: and I dislike the double flannel and double etcd installs....   What can we do to reduce that duplication?

@eparis thanks for the review. I responded to your line notes and will update my PR accordingly.
Regarding the double flannel/etcd installs, the PR does not install etcd, it only manages the existing etcd service that comes with CoreOS. CoreOS advises not changing the etcd version of a particular release. I am however using etcd2 instead of etcd. I can go back and test etcd instead of etcd2, but CoreOS recommends the use of etcd2 over etcd. I think etcd2 support should be added throughout the roles as a separate PR. Please let me know if you require that I change from etcd2 > etcd to merge the PR.
The PR uses GH bins to install Flannel. I saw support for pkg installs [1]. CoreOS does not have a pkg manager, so pulling GH bins is required. Therefore, I added include: github-release.yml when flannel_source_type == "github-release".
[1] https://github.com/kubernetes/contrib/blob/master/ansible/roles/flannel/tasks/client.yml#L2-L7

This PR breaks playbook on RHEL
05:37:33 TASK: [common | Set the bin directory path for CoreOS] ************************
05:37:33 fatal: [<IP_ADDRESS>] => error while evaluating conditional: ansible_lsb.id == "CoreOS"


'postcss-cssnext' has been deprecated in favor of 'postcss-preset-env'

Is postcss-cssnext even used here? Can't find it in the webpack conf

Hello,
Currently, postcss-cssnext is only included as devDependency ready for configuration.
I've started rewriting webpack.config.js - main reason: extract-text-webpack-plugin  (https://github.com/webpack-contrib/extract-text-webpack-plugin) has been DEPRECATED in favor of mini-css-extract-plugin (https://github.com/webpack-contrib/mini-css-extract-plugin).
Migration is almost completed and will be pushed - stay tuned


feat: Add nightly integration "canary" build

Issue #
#1014
Description of changes
Adds a build, scheduled once a day overnight, that:

Pulls latest C2J changes in from the models repository
Code generates them
Builds and tests them

The objective is to detect breaking model changes early in the development cycle.  Right now, this type of breakage is only detected on a release.
A couple steps in this process are extracted into reusable scripts, for use in future CI workflows.  I may extract more of this workflow to scripts in the future.
Also: deletes the unused & obsolete generate-docs.yml workflow.
New/existing dependencies impact assessment, if applicable
No new dependencies were added to this change.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/test

Here's a workflow run where this new workflow succeeded:
https://github.com/awslabs/aws-sdk-swift/actions/runs/5094199823/jobs/9157717132
Once this is ready to merge, I will remove the pull_request trigger from this workflow, that was only put in to facilitate running the workflow during development.

/test


New Project: Cannot Install Packages

When I create a new application, as per the directions listed on your Getting Started

You probably need to add in Visual Studio new NuGet Package Source:
Go to Options, search for NuGet and in Package Source click + button and input:
Name:  api.nuget.org
Source: https://api.nuget.org/v3/index.json

Just checked, and I already have that:

@srsgores could you check which version of the "NuGet Package Manager for Visual Studio 2015" you have installed? It should be version 3.5.

I just checked, and I have 3.4.4:

I don't see version 3.5.  Where can I find and install it?

Installing Update 3 for Visual Studio 2015 solved the problem for me.

Just installed update.  All is working well.


Could not authenticate you

hi,
i want to post a tweet but i got the error :
{"errors":[{"code":32,"message":"Could not authenticate you."}]}
this is my code
$settings = array(
'oauth_access_token' => $oauth_token,
'oauth_access_token_secret' =>$this->oauth_token_secret ,
'consumer_key' =>  $this->consumerPublic[$this->settings->network],
'consumer_secret' =>  $this->consumerSecret[$this->settings->network]
);
$postfields = array();
foreach($urlParams as $key=>$value) {
if ( strpos($key, "?") === 0 ) {
$key =substr($key,1);
}
$postfields[$key] = $value;
}
error_log("SocialJson : "  .  print_r($postfields,true) . "\n", 3, "/var/www/html/vooffdesa/logs/vooff-info.log");
error_log("SocialJson : "  .  print_r($settings,true) . "\n", 3, "/var/www/html/vooffdesa/logs/vooff-info.log");
$twitter = new TwitterAPIExchange($settings);
$socialJson = $twitter->buildOauth($this->path, $_GET['method'])->setPostfields($postfields)->performRequest(true, array (CURLOPT_SSL_VERIFYPEER => false));
where:
$options :
Array
(
[10023] => Array
(
[0] => Authorization: OAuth XXXXXXXXXXXXXXXX
[1] => Expect:
[2] => Content-Length: 0
[3] => Content-Type:application/x-www-form-urlencoded
)
[42] =>
[10002] => https://api.twitter.com/1.1/statuses/update.json
[19913] => 1
[13] => 10
[64] =>
[10015] => include_entities=1&status=hola+hola

)
Hope you can help me.
thanks
Willy

Hi, you don't say what's in the $urlParams array. To debug this, I'll need a very simple example of what the parameters you're passing in to the object, and the lines of code you're doing to make the request.

hi J7mbo,
thanks for the response, here the code
$settings = array(
'oauth_access_token' => $oauth_token,
'oauth_access_token_secret' =>$this->oauth_token_secret ,
'consumer_key' => $this->consumerPublic[$this->settings->network],
'consumer_secret' => $this->consumerSecret[$this->settings->network]
);
$postfields = array();
foreach($urlParams as $key=>$value) {
if ( strpos($key, "?") === 0 ) {
$key =substr($key,1);
}
$postfields[$key] = $value;
}
$twitter = new TwitterAPIExchange($settings);
$socialJson = $twitter->buildOauth($this->path, $_GET['method'])->setPostfields($postfields)->performRequest(true, array (CURLOPT_SSL_VERIFYPEER => false));
variables value:
urlParams : Array
(
[?include_entities] => 1
[status] => #Violencia mucha violenciaaaa, help......
[callback] =>
)
$this->path,
https://api.twitter.com/1.1/statuses/update.json
$_GET['method']
post
$options, this variable exist inside performRequest, I add it Content-Length and Content-Type:application/x-www-form-urlencoded but the same error occurred
Array
(
[10023] => Array
(
[0] => Authorization: OAuth XXXXXXXXXXXXXXXX
[1] => Expect:
[2] => Content-Length: 0
[3] => Content-Type:application/x-www-form-urlencoded
)
[42] =>
[10002] => https://api.twitter.com/1.1/statuses/update.json
[19913] => 1
[13] => 10
[64] =>
[10015] => include_entities=1&status=hola+hola
)
thanks
willy

Can you give me your code, without any extras?
It should be about 5 lines to show what isn't working. I need to see: your post fields, your request using the object methods, and that's it. Anything else won't help.
This means no $_GET (how am I supposed to know what you're passing in!?) and no $_POST.
As of right now, I can't copy and paste your code and have it immediately running on my machine.
Again, this urlParams variable - that isn't part of the API call - replace all of the non-api stuff with a simple, reproducible example and I may be able to help you :-)

Closing as no update here.


String literal that fits keyof X cannot be used as key of X in some cases

TypeScript Version:  3.5.3

Search Terms:

keyof
string literal
extends

Code
type Config = { method: "POST" | "GET" };

<X extends Config>() => {
    type Mapper = { [ item in X["method"] ] : number };

    let mapper : Mapper;

    let a = { POST:1, GET:2 }; // `a` has type `{ POST: number, GET: number }`
    mapper = a; // `a` is a legit value for `Mapper` ✔
    mapper = { POST:1, GET:2 };  // tsc complains about the assignment ❌

    let key : keyof Mapper = "POST"; // "POST" is a legit `keyof Mapper` ✔
    mapper[key] = 0; // `key` is a legit key of `Mapper`  ✔
    mapper["POST"] = 0; // tsc complains about the assignment ❌
};

Expected behavior:
tsc reports no syntax error on the above code snippet.
Actual behavior:
tsc complains on the two marked above with Object literal may only specify known properties, and 'POST' does not exist in type 'Mapper'.
Playground Link:
https://www.typescriptlang.org/play/?target=1#code/C4TwDgpgBAwg9gOwGYEsDmUC8UDeUC2EwAFnACYBcUARAAoDyAygCrVQA+NA4gKKtQBfANwAoEQB4AGlAgAPYBARkAzrESo0APgAUASiybcIqCaihIUALIBDMJABOWXFADaUFAvzuEUSS+qEJOTUALpQYVQIAK74AEYQjsJiplAANkQEtg5QVDZ2CaLGpunAUNY5zgwskTHx9gA0ULzMNXEJgk54VS0AjI3NFABMgqIp+Fnt2NZCUAD0s2XuquXpaB5QAG7WqVHQSHCOedmAKORFJuP5jthdTL39fEMjJvNmygDGUG9w+GCp1igIZaxOBRUokaDWZTKdAIQgIUqAGXJksUMgBrCAgCrokBwJBWCZXGjdagzF50W5sFDLNIQNalbFQXH4y5QU5jAkubFhbAABlJCwABtiBUtFqt1gymUd2qyzplLv5idyoHy5gtgO9Pt9fv9AWVgaCzMQIVCYXDESJhEA
Related Issues:

const f = <X extends Config>() => {
  /* snip */
};
/**
 * Of course you **MUST NOT** set `mapper["POST"]`!
 * Because "POST" is not assignable to `X["method"]`
 */
f<{ method : "GET" }>();

@AnyhowStep This is a simplified example, just to illustrate the issue. The actual code that leads me to this is using the type parameter in the parameter list.
My point it that:
    let a = { POST:1, GET:2 }; // `a` has type `{ POST: number, GET: number }`
    mapper = a;

and
    mapper = { POST:1, GET:2 };

The two pieces of code shall both fail or pass the syntax check. It's weird that one passes the check while the other failed the check.
Same thing to:
    let key : keyof Mapper = "POST";
    mapper[key] = 0;

v.s.
    mapper["POST"] = 0;

let a = { POST:1, GET:2 }; // `a` has type `{ POST: number, GET: number }`
mapper = a; //  ✔, tsc think this is OK
mapper = { POST:1, GET:2 };  //  ❌, but this is not

This is because of excess property checking, which only applies to "fresh" object literals.  Types are not closed, otherwise you wouldn't be able to have subtypes under structural typing.
I still believe the error message for this needs reworded because it seems to be very misleading to people as it is right now.  See discussion here: https://github.com/microsoft/TypeScript/issues/32158#issuecomment-507089327

You can rewrite this as
type Config = {method:"POST"|"GET"};
type Mapper = {[item in Config["method"]]:number};

function fn<X extends Config>() {
    let mapper:Mapper;

    let a = {POST: 1, GET: 2}; // `a` has type `{ POST: number, GET: number }`

    mapper = a; //  ✔, tsc think this is OK

    mapper = {POST: 1, GET: 2}; // ✔

    let key: keyof Mapper;
    key = "FETCH"; // ❌, tsc think "FETCH" is not a valid key
    key = "POST"; //  ✔
    mapper[key] = 0; //  ✔, tsc think mapper[key] is OK
    mapper["POST"] = 0; // ✔
}

to overcome some of these issues.
Putting the type declaration inside the function to reference the generic may be problematic here.
TS Playground


SNMP extension - Sequence

Hello Arun,
Did you encounter any issues like this in troubleshooting ? As error after excueting the signed package ?
Error as below -
WARN
Failed to assign monitoring configuration to Active Gate. Reason: Cannot extract extension from C:\WINDOWS\SERVIC1\LOCALS1\AppData\Local\Temp

Hello, Yeah, I  have seen this with certificate related errors. Can you confirm if ca.pem file has been copied to ActiveGate server?. Also, are you using dt-cli utility to generate certs and sign extension?

Hello Arun
Yes  I used the dt-cli and created both the certificates.
As per the procedure I also uploaded in the Active gate
@.***
While the ca.pem file was loaded to the  tenancy I saw this error below -did you see this in your case ?
PEM client certificate format requires Active Gates version 195 or higher
I didn't get any other exceptions anywhere.
Also I am using the snmp simulator and hence the local machine is given as the IP for adding the monitoring.
But in yours I see the IP <IP_ADDRESS> is it the IP of your device or the simulator reference you have ?
Cheers,
PraseethaMS
From: arunkrishnan-dt @.>
Sent: Monday, December 6, 2021 8:46 PM
To: arunkrishnan-dt/dynatrace_snmp_2.0 @.>
Cc: Praseetha Mohandas Sylaja @.>; Author @.>
Subject: Re: [arunkrishnan-dt/dynatrace_snmp_2.0] SNMP extension - Sequence (Issue #1)
Hello, Yeah, I have seen this with certificate related errors. Can you confirm if ca.pem file has been copied to ActiveGate serverhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farunkrishnan-dt%2Fdynatrace_snmp_2.0%2Fblob%2Fmain%2F3_Sign_extension.md%23upload-capem-to-activegates&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|fc1a052ae3c249aa310308d9b8f10012|1685007349774869916308e8d38eac81|1|0|637744167495850030|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=qZiUnpwKbcZ0tWpRgeX1eWLhN0VpRiSoIkHmZeVkla4%3D&reserved=0?. Also, are you using dt-cli utility to generate certs and sign extension?

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farunkrishnan-dt%2Fdynatrace_snmp_2.0%2Fissues%2F1%23issuecomment-987124254&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|fc1a052ae3c249aa310308d9b8f10012|1685007349774869916308e8d38eac81|1|0|637744167495860021|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=rf%2BYOAioIVSZMWQrV8jrbqkuCtBfr%2BLaHu66EcYxZs0%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV6WIB3T6V6E64SVZ2ZZ3JLUPUHGVANCNFSM5JO3JVBA&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|fc1a052ae3c249aa310308d9b8f10012|1685007349774869916308e8d38eac81|1|0|637744167495860021|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=al0HPITsTruF9YCYP%2B3rdyf%2Fug3W3VB2Zm0dXqiXIdg%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|fc1a052ae3c249aa310308d9b8f10012|1685007349774869916308e8d38eac81|1|0|637744167495870020|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=XowIXbHY5iIvbYa6ly3KOKe%2FgDxCQLM0EsCFGOJglL8%3D&reserved=0 or Androidhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|fc1a052ae3c249aa310308d9b8f10012|1685007349774869916308e8d38eac81|1|0|637744167495870020|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=PDki7mc7ayC5yZHE2dmAriLqNRw0tHeu00oN3HH1Hck%3D&reserved=0.

Hey Praseetha, Apologies for the delay. Hope you were able to get this resolved! If it's still an issue, I would recommend contacting Official Dynatrace Support (if not done already). They should be able to look at your specific issue and help.
Thank you, Arun

Hello Arun
I have a question. I saw you gave the IP address of a machine.
@.***
Say if we have more than 10 network devices we will have to repeat giving these IP address of those machines which we intend to monitor I suppose and keep adding the monitoring.
Is it a must that we need to have some criteria's on those end network machines - apart from the fact that it needs to be connected with Active gate ?
In my testing case I was using my local host as the simulator and the active gate together; so I didn't have chance to test with real machines >1 devices.
Cheers,
PraseethaMS
From: arunkrishnan-dt @.>
Sent: Monday, December 20, 2021 11:34 PM
To: arunkrishnan-dt/dynatrace_snmp_2.0 @.>
Cc: Praseetha Mohandas Sylaja @.>; Author @.>
Subject: Re: [arunkrishnan-dt/dynatrace_snmp_2.0] SNMP extension - Sequence (Issue #1)
Hey Praseetha, Apologies for the delay. Hope you were able to get this resolved! If it's still an issue, I would recommend contacting Official Dynatrace Supporthttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.dynatrace.com%2F&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|b2aca8e781ca47eaefc408d9c408c0ed|1685007349774869916308e8d38eac81|1|0|637756364145930115|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=t9DYZxz3OY6l0anRtTuW%2BpfW8XilRY%2F5HdKc0haD8UI%3D&reserved=0 (if not done already). They should be able to look at your specific issue and help.
Thank you, Arun

Reply to this email directly, view it on GitHubhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Farunkrishnan-dt%2Fdynatrace_snmp_2.0%2Fissues%2F1%23issuecomment-998320474&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|b2aca8e781ca47eaefc408d9c408c0ed|1685007349774869916308e8d38eac81|1|0|637756364145930115|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=z%2FOxuprPtUoajsko4hi2PuwY8SWV04D89oqWUSfnLOU%3D&reserved=0, or unsubscribehttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAV6WIB7LOTN3AUMPPKGHZ33UR6VLXANCNFSM5JO3JVBA&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|b2aca8e781ca47eaefc408d9c408c0ed|1685007349774869916308e8d38eac81|1|0|637756364145930115|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=%2FuyL8kjVrZ2BRzSO67C7NwsmhnwGb1BWrIrq5Uptsvc%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|b2aca8e781ca47eaefc408d9c408c0ed|1685007349774869916308e8d38eac81|1|0|637756364145930115|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=PbzShufRGJ%2B0OUa8%2BOhiqDc4dZoS2J5qIXkTTAnlCHg%3D&reserved=0 or Androidhttps://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|Praseetha.MohandasSylaja%40inetum-realdolmen.world|b2aca8e781ca47eaefc408d9c408c0ed|1685007349774869916308e8d38eac81|1|0|637756364145930115|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=QsmbPAATO00f9sMDsby9fcSfUFPmPGQMM8265ToBjKQ%3D&reserved=0.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>

Hey, There are  few things you will need to do on network device, depending on setup. A network admin should be able to help with it. Some items I can this of are:

SNMP must be enabled on network device
Create a SNMP Community string on network device
Whitelist IP addresses that can make SNMP requests to network devices (in some cases)

Thank you,
Arun


Not working with ng-if

When I use select input with ng-if attribute it won't show any options
<select ng-if="condition" selector multi="true" model="model" options="options" label-attr="label" value-attr="id"></select>

Hi @RushabhJoshi, you can't use ng-if directive with other directives that use a private scope.
You need to wrap your select inside another block like this:
<div ng-if="condition">
    <select selector ...></select>
</div>

Still no luck, Also tried in span tag

Check out this plunker: http://plnkr.co/edit/BppzOSMEU8edgaasr3Pt?p=preview

I appreciate
and this is strange atleast your example shows options (I will see whats missing in my code), but in your example change does not reflect on browser model.
anyways solved a problem with ng-show
problem with prefill data in input,
Thanks


Change console.log in gluesql.js -> console.debug

close #1124
Changes:
move "[GlueSQL] hello :)" to debug.
Is any others log calls needing to change debug

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
21 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 98.649%

Files with Coverage Reduction
New Missed Lines
%

core/src/executor/execute.rs
21
91.86%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
45058

Relevant Lines:
45675

💛  - Coveralls

Thanks, I will commit lately.


sample_batch args in test_top_k in gflownet.py

I just cloned a fresh copy of the repo in WSL and tried a run with all default configs, and it looks like the sample_batch on line 906 in gflownet.py is getting the wrong arguments (at least, it crashes every time). Looks like the parent function test_top_k was added August 1.
call:
for b in batch_with_rest(0, self.logger.test.n_top_k, self.batch_size.forward):
    gfn_states += self.sample_batch(
        self.env, len(b), train=False, progress=progress
    )[0]

function definition:
def sample_batch(
    self,
    n_forward: int = 0,
    n_train: int = 0,
    n_replay: int = 0,
    train=True,
    progress=False,
):

You were right. This crash was due to a large domino-multi-way merge of branches into main. This PR fixes this issue.


qbittorrent-nox: missing meta.mainProgram

No bug so skipping the steps-to-reproduce stuff and all that. It works as it is, but throws a warning.
Needed for things like lib.getExe, which is a common pattern in systemd services - something very reasonable to assume people would want for a package like this.
https://github.com/NixOS/nixpkgs/blob/e4509b3a560c87a8d4cb6f9992b8915abf9e36d8/pkgs/applications/networking/p2p/qbittorrent/default.nix#L92-L99
Suggested fix:
mainProgram = "qbittorrent-nox";
@Anton-Latukha  @kashw2

feel free to send a PR yourself :) it's not restricted to maintainers

As qbittorrent has three varients in nixpkgs (qbittorrent-nox, qbittorrent-qt and qbittorrent). I'm not sure what one we want to specify as the actual main program. We could use the same logic we use to separate the pnames.

As qbittorrent has three varients in nixpkgs (qbittorrent-nox, qbittorrent-qt and qbittorrent). I'm not sure what one we want to specify as the actual main program. We could use the same logic we use to separate the pnames.

Oh, wow, I didn't even notice they were the same package. I mean, we should be able to figure it out using something like qbittorrent${lib.optionalString (!guiSupport) "-nox"}, right? Maybe something extra for -qt as well?


Hi,
Same problem here.
Freshly updated to V2J31S7 and I have the same error.


fix(clerk-js): Introduce ability to read multiple errors

Type of change

[ ] 🐛 Bug fix
[x] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[x] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

Currently, client-side password validation constructs dynamically all error messages based on the password complexity settings. In this PR we want to support reading multiple errors in order to construct a password error with information
that comes from FAPI. This way we can achieve parity between password client-side validations and errors
returned from FAPI, resulting in the same exact message.
Currently, we support handling only one error object that comes from FAPI so if we have many errors regarding passwords(e.g. too short password, uppercase required, lowercase required) it will only show the first. We want the error handler to read all incoming errors(only password relating errors will be multiple) so a more concise password can be shown.
Before
https://github.com/clerkinc/javascript/assets/23478420/338cbe9e-ff5f-4149-9a5d-b7bc1494368d
After
https://github.com/clerkinc/javascript/assets/23478420/12b8b50c-68cc-4878-8541-4e50dab80a00

!snapshot

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


[BUG] Chip-cert-bins docker script failing on TOT

Reproduction steps
Trying to build the cert-bins docker image and its failing :
Steps used :
docker buildx build --build-arg COMMITHASH=bbb8e935b250e5dc291021cb220b192a50cc98cf --platform linux/arm64 --tag connectedhomeip/chip-cert-bins:bbb8e935b250e5dc291021cb220b192a50cc98cf --push .
Probably a zap issue ?
Error Snippet is here :
#0 0.820 🚀 Executing: git log -1 --format={"hash": "%H","timestamp": %ct}
#0 0.825 🔍 Git commit: ac6dd831c2634315b5c847e37cc9b44bb7c22e5e from Mon Mar 06 2023 20:44:30 GMT+0000 (Coordinated Universal Time)
#0 0.848 🔍 Current src hash: tt1kGIKwkwmZc8maXjP1W3u9tu4=
#0 0.850 🔍 Current src-shared hash: g/WbG5bVfcehj7QTAknSkxvoR5c=
#0 0.851 🔍 Previous src hash: tt1kGIKwkwmZc8maXjP1W3u9tu4=
#0 0.851 🔍 Previous src-shared hash: g/WbG5bVfcehj7QTAknSkxvoR5c=
#0 0.851 👍 There were no changes to front-end code, so we don't have to rebuild the SPA.
#0 0.851 🚀 Executing: npx tsc --build ./tsconfig.json
#0 2.786 🚀 Executing: npx copyfiles ./src-electron/**/*.sql ./src-electron/icons/* ./dist/
#0 2.877 🚀 Executing: npx node --unhandled-rejections=strict /opt/zap-v2023.03.06-nightly/dist/src-electron/main-process/main.js generate -z /root/connectedhomeip/src/app/zap-templates/zcl/zcl.json -g /root/connectedhomeip/src/app/zap-templates/matter-idl.json -i /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap -o /root/connectedhomeip/scripts/examples/../../zzz_generated/placeholder/app1/zap-generated --tempState
#0 3.135 Expected node versions: v14.x.x,v16.x.x
#0 3.136 Provided node version: v12.22.12
#0 3.136 WARNING: you are using different node version than recommended.
#0 3.141 🔧 Using temporary state directory: /tmp/zapvn0hytrg/zap.o4VDoC
#0 3.141 🤖 ZAP generation started:
#0 3.141     🔍 input files: /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap
#0 3.141     🔍 output pattern: /root/connectedhomeip/scripts/examples/../../zzz_generated/placeholder/app1/zap-generated
#0 3.141     🔍 using templates: /root/connectedhomeip/src/app/zap-templates/matter-idl.json
#0 3.141     🔍 using zcl data: /root/connectedhomeip/src/app/zap-templates/zcl/zcl.json
#0 3.141     🔍 zap version: ver. undefined, featureLevel 94, commit: ac6dd831c2634315b5c847e37cc9b44bb7c22e5e from 2023-03-06T20:44:30.000Z, mode: source, exe: node
#0 3.763 🕐 Setup time: 622ms
#0 3.763 👉 using input file: /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap
#0 3.855 👉 using output destination: /root/connectedhomeip/scripts/examples/../../zzz_generated/placeholder/app1/zap-generated
#0 3.857 🕐 File loading time: 94ms
#0 4.140 🤖 Generating files:
#0 4.140     ✍  /root/connectedhomeip/zzz_generated/placeholder/app1/zap-generated/Clusters.matter
#0 4.140 🕐 Generation time: 283ms
#0 4.170 😎 All done: 3s 350ms.
#0 4.175 Searching for zcl file from /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap
#0 4.175 Unable to check version using %r. Assuming version is ok. ['node', 'src-script/zap-start.js']
#0 4.175 Files generated in: /root/connectedhomeip/scripts/examples/../../zzz_generated/placeholder/app1/zap-generated
#0 4.231 Searching for zcl file from /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap
#0 4.231 Error: /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/../templates/templates.json does not exists or is not a file.
------
Dockerfile:275
--------------------
 273 |         esac
 274 |
 275 | >>> RUN scripts/examples/gn_build_test_example.sh app1
 276 |
 277 |     RUN source scripts/activate.sh && scripts/build_python.sh -m platform -d true -i no
--------------------
ERROR: failed to solve: process "/bin/bash -c scripts/examples/gn_build_test_example.sh app1" did not complete successfully: exit code: 1
raju@Rajus-MacBook-Pro chip-cert-bins %

Docker_chip_cert_bins_error.rtf.zip
Bug prevalence
Every time
GitHub hash of the SDK that was being used
bbb8e935b250e5dc291021cb220b192a50cc98cf
Platform
raspi
Platform Version(s)
Linux/arm64
Anything else?
Trying to build the cert-bins docker image and its failing :
Steps used :
docker buildx build --build-arg COMMITHASH=bbb8e935b250e5dc291021cb220b192a50cc98cf --platform linux/arm64 --tag connectedhomeip/chip-cert-bins:bbb8e935b250e5dc291021cb220b192a50cc98cf --push .
Error Snippet :
#0 0.820 🚀 Executing: git log -1 --format={"hash": "%H","timestamp": %ct}
#0 0.825 🔍 Git commit: ac6dd831c2634315b5c847e37cc9b44bb7c22e5e from Mon Mar 06 2023 20:44:30 GMT+0000 (Coordinated Universal Time)
#0 0.848 🔍 Current src hash: tt1kGIKwkwmZc8maXjP1W3u9tu4=
#0 0.850 🔍 Current src-shared hash: g/WbG5bVfcehj7QTAknSkxvoR5c=
#0 0.851 🔍 Previous src hash: tt1kGIKwkwmZc8maXjP1W3u9tu4=
#0 0.851 🔍 Previous src-shared hash: g/WbG5bVfcehj7QTAknSkxvoR5c=
#0 0.851 👍 There were no changes to front-end code, so we don't have to rebuild the SPA.
#0 0.851 🚀 Executing: npx tsc --build ./tsconfig.json
#0 2.786 🚀 Executing: npx copyfiles ./src-electron/**/*.sql ./src-electron/icons/* ./dist/
#0 2.877 🚀 Executing: npx node --unhandled-rejections=strict /opt/zap-v2023.03.06-nightly/dist/src-electron/main-process/main.js generate -z /root/connectedhomeip/src/app/zap-templates/zcl/zcl.json -g /root/connectedhomeip/src/app/zap-templates/matter-idl.json -i /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap -o /root/connectedhomeip/scripts/examples/../../zzz_generated/placeholder/app1/zap-generated --tempState
#0 3.135 Expected node versions: v14.x.x,v16.x.x
#0 3.136 Provided node version: v12.22.12
#0 3.136 WARNING: you are using different node version than recommended.
#0 3.141 🔧 Using temporary state directory: /tmp/zapvn0hytrg/zap.o4VDoC
#0 3.141 🤖 ZAP generation started:
#0 3.141     🔍 input files: /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap
#0 3.141     🔍 output pattern: /root/connectedhomeip/scripts/examples/../../zzz_generated/placeholder/app1/zap-generated
#0 3.141     🔍 using templates: /root/connectedhomeip/src/app/zap-templates/matter-idl.json
#0 3.141     🔍 using zcl data: /root/connectedhomeip/src/app/zap-templates/zcl/zcl.json
#0 3.141     🔍 zap version: ver. undefined, featureLevel 94, commit: ac6dd831c2634315b5c847e37cc9b44bb7c22e5e from 2023-03-06T20:44:30.000Z, mode: source, exe: node
#0 3.763 🕐 Setup time: 622ms
#0 3.763 👉 using input file: /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap
#0 3.855 👉 using output destination: /root/connectedhomeip/scripts/examples/../../zzz_generated/placeholder/app1/zap-generated
#0 3.857 🕐 File loading time: 94ms
#0 4.140 🤖 Generating files:
#0 4.140     ✍  /root/connectedhomeip/zzz_generated/placeholder/app1/zap-generated/Clusters.matter
#0 4.140 🕐 Generation time: 283ms
#0 4.170 😎 All done: 3s 350ms.
#0 4.175 Searching for zcl file from /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap
#0 4.175 Unable to check version using %r. Assuming version is ok. ['node', 'src-script/zap-start.js']
#0 4.175 Files generated in: /root/connectedhomeip/scripts/examples/../../zzz_generated/placeholder/app1/zap-generated
#0 4.231 Searching for zcl file from /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/apps/app1/config.zap
#0 4.231 Error: /root/connectedhomeip/scripts/examples/../../examples/placeholder/linux/../templates/templates.json does not exists or is not a file.
------
Dockerfile:275
--------------------
 273 |         esac
 274 |
 275 | >>> RUN scripts/examples/gn_build_test_example.sh app1
 276 |
 277 |     RUN source scripts/activate.sh && scripts/build_python.sh -m platform -d true -i no
--------------------
ERROR: failed to solve: process "/bin/bash -c scripts/examples/gn_build_test_example.sh app1" did not complete successfully: exit code: 1
raju@Rajus-MacBook-Pro chip-cert-bins %

@andreilitvin can you take a look please ? does the ZAP need to be updated?

Presumably something about #25378 and the changes it made?  @krypton36

Does applying:
diff --git a/scripts/examples/gn_build_test_example.sh b/scripts/examples/gn_build_test_example.sh
index 52b56c2428..66ed9c3dd6 100755
--- a/scripts/examples/gn_build_test_example.sh
+++ b/scripts/examples/gn_build_test_example.sh
@@ -40,7 +40,7 @@ function runZAP() {
     "$CHIP_ROOT"/scripts/tools/zap/generate.py "$ZAP_INPUT_FILE" -o "$ZAP_OUTPUT_DIR"

     # Generates the specific files for the given zap configuration
-    TARGET_APP=$APP_DIR "$CHIP_ROOT"/scripts/tools/zap/generate.py "$ZAP_INPUT_FILE" -t "$INPUT_DIR"/../templates/templates.json -o "$ZAP_OUTPUT_DIR"
+    TARGET_APP=$APP_DIR "$CHIP_ROOT"/scripts/tools/zap/generate.py "$ZAP_INPUT_FILE" -t "$INPUT_DIR"/apps/$APP_DIR/templates/templates.json -o "$ZAP_OUTPUT_DIR"
 }

 function runGN() {

help?

Thanks @krypton36 , will wait for your PR to land and then try to re-build on TOT


Step-wise processing, better support for IterableDataset, and others

I have been using PTL for a month. It is nice and saves a lot of time, and I intend to use it in future projects. That said, I have a list of feature requests and improvements that would be very helpful to have to support a wider set of use cases. I am not sure what the best format for this list, so I will just write them here.

Better support for IterableDataset

In addition to val_check_interval, we also need num_val_steps and num_train_steps. num_val_steps is needed because the validation set is also using an IterableDataset. num_train_steps is needed because you usually need to carefully pick number of gradient updates which has some interaction with the learning rate scheduler (num_train_steps=inf is not sufficient)
For validation, keep the same DataLoader object instead of instantiating a new one on each validation cycle, because it is costly to construct new workers each time.
Some of the debugging features that run on a small percentage of the training/validation don't work because they are assuming a Dataset not IterableDataset

Step-wise processing
Thinking of the "gradient update" as the unit of training instead of (or in addition to) an epoch. A typical use case is pretraining a language model, where you want to control for number of gradient updates, not epochs (e.g. check the RoBERTa/BERT papers).

Add an option to do scheduler.step() after every gradient update
Have self.trainer.num_train_steps be available for the LR scheduler. The scheduler is usually a function of number of steps
Checkpointing the current step, and resume from that step. Again, this is important to get the right scheduler, and also important for the tensorboard logging. It will be nice to resume from the same training example, but this is less important.

Misc. These are smaller points, but nice to have.

Having the default tensorboard logging include LR, time per steps, allgradnorm (check fairseq)
Trainer(gpus=2) ignores CUDA_VISIBLE_DEVICES and always picks the first two gpus.
with ddp, sync validation stats across processes. This is a common mistake, and it will be nice to guard users against it. It is something like having the following line at the end of validation_end:

val_loss = torch.distributed.all_reduce(val_loss, op=torch.distributed.ReduceOp.SUM)/self.trainer.world_size

various logs refer to "batches", and it is not clear if it a "batch" or a "step". They are usually the same except with gradient accumulation. Personally, I prefer the word step because it eliminates that confusion.

Thanks for the helpful library and sorry for the long list.

Trainer(gpus=2) ignores CUDA_VISIBLE_DEVICES and always picks the first two gpus.

Trainer cannot ignore CUDA_VISIBLE_DEVICES, as it is handled by the underlaying libraries.
The device ids in pytorch/tensorflow applications are not consistent with the ids showed in nvidia-smi .  E.g, the gpu:0 in pytorch may be the gpu:2 in nvidia-smi. I guess that's why you failed to set the device id to use card you want.
You may set this env variable export CUDA_DEVICE_ORDER=PCI_BUS_ID, then the order of device ids will be consistent.

Is num_val_steps added, or some alias?

As far as I can tell, no. My workaround is to add
    def __len__(self):
        return 1000000  # a large positive constant

in the IterableDataset, then use val_percent_check to run for a smaller number of steps.


IndexError: index 1719 is out of bounds for axis 0 with size 1710

Hello sir,when i use a mat file with network 21592159 and group 2159573,it tells me
Finish building Skip-gram model on the coarsened graphs.
Traceback (most recent call last):
File "src/harp.py", line 77, in
sys.exit(main())
File "src/harp.py", line 62, in main
lr_scheme='default',alpha=0.025,min_alpha=0.001,sg=1,hs=1,coarsening_scheme=2, sample=0.5)
File "/home/rainsong/Desktop/2/HARP-master/src/graph_coarsening.py", line 333, in skipgram_coarsening_disconnected
embeddings[real_ind] = vec
IndexError: index 1719 is out of bounds for axis 0 with size 1710
I set the parameters by default.
Can you help me?thank you very mush.

My guess is that you have some nodes without any edge in your input network -- not 100% sure

Yes,you are right,there are some nodes without any edge.
The dataset I used is about diseases and drugs,and the network is a very sparse matrix.
If I want to use your algorithm on my dataset,how can i do.
Thank you very much.

One solution is to construct another graph by removing nodes without any edge, and run HARP on the new graph. You also need to preserve the mapping between node indices in the original graph versus in the new graph (note that node indices should always start from 0 and be continuous).
I can also fix this on my side, but I probably will not have time to work on this until late August. Sorry about that!

Thank  you for your help.I have solved the problem.
😀


Integrate Occuspace UI

Build out UI from issue #465

A working prototype is on the feature/occuspace branch
commit hash: 198cdfa451649cb7d83a6b6b47e68294788ad610

Updates:

fixed scrolling issue on android
updated height on progress bar
automatically store users added locations to DB (if signed in)
updated error reporting for more information on Bugsnag

branch: feature/occuspace
commit: 248cae0d01608a12001faab79bb510dc01c3f845


Add documentation for Kinesis source in Data prepper

Description
This PR adds documentation for a new kinesis source in Data Prepper. It includes the following:

Example configuration
Required configuration attributes along with their description
Required permissions to run kinesis source

Issues Resolved
N/A
Checklist

[X] By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and subject to the Developers Certificate of Origin.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@dlvenable This PR is tagged as a first-time contributor. Will you or your team provide a technical review? Once that review is done, I'll do a doc review. Thank you.

@sb2k16 Is this PR ready for a doc review? I can give it a first review and then give it a final review before the Data Prepper 2.10.

@sb2k16 , @vagimeli , This is a new feature for Data Prepper 2.10, which has not yet been released. We should target this to a new branch. I just created one named data-prepper-2.10.
@sb2k16 , Can you edit your PR to target the data-prepper-2.10 branch?

I have edited the PR to target data-prepper-2.10 branch.

@sb2k16 , @vagimeli , This is a new feature for Data Prepper 2.10, which has not yet been released. We should target this to a new branch. I just created one named data-prepper-2.10.
@sb2k16 , Can you edit your PR to target the data-prepper-2.10 branch?

I have edited the PR to target data-prepper-2.10 branch.

@dlvenable Once you approve, I'll move this PR forward for publishing.


"Register" a territory

Register means a new entry for a preacher, but without changing the "older than 4 or 8" months pool info. The oldest date remains the same.

Implemented


Removing Romana

Romana is defunct and has been removed from main networking docs already.

Hi @caseydavenport.  Can you please serve as the technical reviewer for this. Simply add a /lgtm if you feel it is technically correct and I'll take care of the rest.
/assign @caseydavenport

/assign

/lgtm


No way to set timeout for any request

Some proxies are very slow. A request can take up to 2 minutes and then fail due to timeout.

Individual trackers do have the ability to pass options directly to HTTParty [1]. So, if HTTParty has an option for it, you can do it that way. You're correct that there is no way to do it with the group methods (ranks, etc) though. I'd happily accept a pull request for passing the options through and any extra gymnastics HTTParty needs to set timeouts.

I'll do it when I have some free time.
BTW How about switching to restclient?

When I switched from Typhoeus, I evaluated a couple libraries. I believe the issue with restclient is that it doesn't allow per connection proxies. You could only do it at the global level. That behavior wouldn't work well with multiple threads and the proxy services.
I personally prefer Faraday these days, because of the ability to inject middleware to customize requests and responses.
I wouldn't be opposed to a switch, as long as it maintains feature parity with what's currently used and provides some notable benefit. If it's just switching for switching's sake, then I wouldn't accept it.


[Bug]: Memory consumption

Component
Heimdall CLI
Version
Heimdall Version: 0.3.0
System Configuration:
CPU: AMD Ryzen 7 5800X 8-Core Processor 3.80 GHz
RAM: 32.0 GB
System type: 64-bit
Rust Version: 1.66.1
Please check the following

[X] This is not a duplicate issue
[X] I have checked the wiki and tried troubleshooting the issue

Operating System
Windows
Describe the issue you are facing

Input used: heimdall decompile 0x100f0013372bf98f72fcb946883016958e59d1b0 --rpc-url https://polygon-rpc.com -vvv -d --include-sol --skip-resolving
After run for 40 minutes the program paused in this screen:

I have been tried the same input on a linux machine but resulted in out of memory in 3 seconds.
This contract already been verified on polygonscan: https://polygonscan.com/address/0x100f0013372bf98f72fcb946883016958e59d1b0#code

Thanks for raising this. I'll take a look and build a patch this weekend :)
Note: Decompilation / CFG should never take over a minute. At that point just stop the program and make a bug report.

Thx for the quick response 😁
this project is help-me a lot.

Happy to hear <3

Btw, what program did you use to make the screenshots?

Sharex: https://getsharex.com/
Github: https://github.com/ShareX/ShareX
Site with temes: https://getsharex.com/image-effects

Resolved, will be fixed when I publish 0.3.1 today.

Pushing release to tomorrow


Introduce KeyNormalizer decorator

See https://github.com/yiisoft/cache/pull/54

Maybe a function that returns the normalized key as a string is enough?


Update scala 3 version

Pull Request Checklist

[x] I agree to licence my contributions under the MIT licence
[x] I have added copyright headers to new files -- No new files
[ ] I have added tests for any changed functionality -- Not done, see comment under 'Purpose' section

Welp, embarrassingly, fixes nothing directly. It turns out that the scala bump was... not why this started working locally in downstream. Once I figured out why my local scala 3.3.0 version was acting janky, it turns out that actually my reproduction started working because the fix had been merged to scalamock since the 6.0.0 version was released 🤦.
I'm gonna leave this open for now in case there's any interest in bumping the scala version, but I would understand if this were closed as a wontfix 😅 . Original comment below:
Fixes
Usage in downstream projects on scala >= 3.3.1 fails to mock classes with parameterised constructor args. Minimal reproduction:
build.sbt:
scalaVersion := "3.3.3"
libraryDependencies ++= Seq(
  "org.scalamock" %% "scalamock" % "6.0.0" % Test,
  "org.specs2" %% "specs2-core" % "4.20.8" % Test
)

src/test/scala/reproduce_bug/MockabilityTest.scala:
package reproduce_bug

import org.scalamock.specs2.IsolatedMockFactory
import org.specs2.mutable.Specification

class MockabilityTest extends Specification with IsolatedMockFactory {

  "MockableSubclass utils" >> {
    val ok: Unmockable = mock[Unmockable]
    classOf[Unmockable].isAssignableFrom(ok.getClass) must beTrue
  }
}

case class HasParam[T](t: T)

case class Unmockable(a: String, b: Int, c: HasParam[Double]) {
  def foo: String = "foo"
}

Produces error
[error] -- [E007] Type Mismatch Error: /Users/hughsimpson/Sandbox/Play/reproduce_bug/src/test/scala/reproduce_bug/MockabilityTest.scala:10:25
[error] 10 |    val ok: Unmockable = mock[Unmockable]
[error]    |                         ^^^^^^^^^^^^^^^^
[error]    |                         Found:    reproduce_bug.HasParam
[error]    |                         Required: reproduce_bug.HasParam[Double]
[error]    |
[error]    | longer explanation available when compiling with `-explain`
[error] one error found

Purpose
Upgrading the scala version with which the library is built fixes this bug downstream in the above minimal reproduction. Writing the code as a test within the project does not prompt the bug so I have not attempted to add it here.
The reproduction test passes with the following updated build.sbt (where 6.0.1-LOCAL is a locally published version of this branch):
scalaVersion := "3.4.0"
libraryDependencies ++= Seq(
  "org.scalamock" %% "scalamock" % "6.0.1-LOCAL" % Test,
  "org.specs2" %% "specs2-core" % "4.20.8" % Test
)
Test / scalacOptions += "-experimental"

No changes were required for the test file.
Background Context
The above failure appears to be a bug with scala 3.3.0 (possibly with TASTy? I don't know anything about the scalac internals). The earliest minor scala version that supports the -experimental scalacOption is 3.4.0; to avoid having to annotate everything with @experimental I've gone for bumping the scalaVersion to beyond the LTS release.
I don't know whether this bug would be present in a project that stuck to scala 3.3.0 specifically, since when attempting to use that specific version I get:
[error] error while loading ElementType,
[error] class file /modules/java.base/java/lang/annotation/ElementType.class is broken, reading aborted with class java.lang.RuntimeException
[error] bad constant pool index: 0 at pos: 1220

on the bug reproduction

I don't see the experimental flag on the roadmap for scala 3.3.4, and we're already on 3.3.4-RC1 so... Think the window for that is gone...

Hadn't updated the scala 3 version in the GitHub workflow so that test failed. Pushed an update there

So anyway this whole pr was way off base and I do apologise for that. I guess I figured it might still be worth leaving open on the off-chance, and because it had already been tagged (presumably because of my initial false claim about the downstream impact 😬). I was tempted to close it or mark as draft but... idk. Potentially scala 3.4 warrants discussing even though I originally introduced the idea for bad reasons

As a library, I'd suggest staying on LTS versions, as not to force downstreams to update

The compatibility guarantees for scala 3 make me question whether that's a useful goal... If you're in the business of upgrading your libraries at all, is there actually a valid reason to not bump scala versions as a downstream application?

I think there is no problem of bumping version up to latest 3.4 or even 3.5.0 if we can get rid of annotating everything as @experimental, this is crucial, essentially for library users.
Anyway we are exploiting a bug in the compiler to make it work.
If we decide to go experimental way, I would also consider using TupledFunction to make scalamock simpler

I think there is no problem of bumping version up to latest 3.4 or even 3.5.0 if we can get rid of annotating everything as @experimental, this is crucial, essentially for library users.
Anyway we are exploiting a bug in the compiler to make it work.
If we decide to go experimental way, I would also consider using TupledFunction to make scalamock simpler

Also, in my opinion, we should drop support for Scala 2.12 and Scala 2.13, since library is stable enough and nobody anyway would fix anything for scala 2. This would make library development with scala 3 much simpler.

@goshacodes I love that energy. Happy to drop scala 2 support in this pr. Will look into your suggestions on this after I've addressed the ones on the other two.

Let's proceed then. @hughsimpson please drop scala 2 in this PR

@goshacodes  Dropped scala 2, haven't looked into TupledFunction yet - probably won't have the bandwidth for a few days now - but that can probably come later anyway?

@goshacodes Dropped scala 2, haven't looked into TupledFunction yet - probably won't have the bandwidth for a few days now - but that can probably come later anyway?

At first lets rewrite everything to scala 3 with scalafix (or similar utility, not sure which one does it)
With tupled functions research is needed anyway, If you want to take it, it will be great

@barkhorn Could you please close all scala-2 related issues with wont-fix to cleanup everything, after this MR is merged
Also this is not related, but If you know, could you please tell us, what does proxy package meant for?
Not found anything related in the docs or in issues

@hughsimpson opened an issue about TupledFunction https://github.com/paulbutcher/ScalaMock/issues/533

Not sure if I'll get to it or not... Once the next release is cut with the bugfix prs I'll probably be snowed under trying to finalise some chunky migrations, so will probably vanish off the reservation for a while tbqh. But if it's still waiting for me when that work is done I'll be diving straight in

I don't mind ripping out a bit more whilst I'm in here. @barkhorn @goshacodes you think this pr should go further? Or merge as it stands and perform the rest of the actions in follow-up?

I think we should merge as it is now and handle it later. Just asked)

I've recently found one issue, which IMO should be fixed before we merge this.
Current scalamock internal implementation is not thread safe and may cause throw of ConcurrentModificationException.
This can and should be fixed for scala 2 also

I'll rebase this tomorrow. No worries

I've had a crack at that bug here. Pushed the test before the fix so you can see that it at least failed in scala 2.13 and 3 with the expected error. Probably the best I can do, took way too long to write a test that failed consistently without the fix.

This should go as 7.0 series


map.getSize() returns incorrect value

I am migrating openlayers from 4.6.5 to 6.14.1. I am facing an issue with screen extent and map size
map.getSize() is returning [1184,0] earlier it used to return [1184,592]

[629, 0]


Tests not working after Shadow DOM v1 Slots Implementation

Tests make use of _ContentSelector which was removed by #357.
https://github.com/aurelia/templating/blob/9c602dd477c10ce671d593be2f21e2cfefbe72d8/test/view-slot.spec.js#L8

Any update on this?

It will get fixed this week.
On Jun 12, 2016 7:14 PM, "Bruce Denham"<EMAIL_ADDRESS>wrote:

Any update on this?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aurelia/templating/issues/375#issuecomment-225466278,
or mute the thread
https://github.com/notifications/unsubscribe/AAIBnS1RztzSAN20Cd7S5nbP6MetMQzkks5qLJLQgaJpZM4IwYuW
.

Fixed by 10ccb740597fee8a42a40c70201c0cacab2fb47f I guess.


Add python3 support

What does this PR do?
Add support for Python3 for apache integration
Motivation
More python3 support
Review checklist

[ ] PR has a meaningful title or PR has the no-changelog label attached
[ ] Feature or bugfix has tests
[ ] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo

Additional Notes
Anything else we should know when reviewing?

Codecov Report

Merging #2497 into master will increase coverage by 8.12%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master    #2497      +/-   ##
==========================================
+ Coverage   84.59%   92.71%   +8.12%
==========================================
  Files         622        4     -618
  Lines       34675      151   -34524
  Branches     4205       17    -4188
==========================================
- Hits        29332      140   -29192
+ Misses       4084        7    -4077
+ Partials     1259        4    -1255


Support grid layout and tab navigation in GridList

Related to https://github.com/adobe/react-spectrum/discussions/4742
This adds a layout prop to the RAC GridList component, which can be set to "stack" (default) or "grid". When set to "grid", arrow key navigation is used to move left and right between columns. To access focusable elements inside the items, tab can be used instead. The tab sequence goes through elements within the focused item before going out of the collection.
This can also be enabled even for stack layouts via the navigationBehavior="tab" prop. For example, if you have a list where interactive elements within items aren't arranged horizontally, tab might make more sense.

This is useful. Can you add a Storybook control for this so that it's easier to demo the behavior with stack layout?

@jaknas I don't think so. This line enables grid layout support, which is already available in ListBox: https://github.com/adobe/react-spectrum/pull/6486/files#diff-87753d6f055505c1f4a4cb6698abe34276d6aa0c17bee1f8b9ec509c4e22944aR169


FCMA permutation feature selection Acc above chance

Hello,
I'm using FCMA with Brianiak for my analysis - first thank you for developing this awesome toolbox!
Everything makes sense to me until I started to do the permutation task as mentioned in Wang et al., 2015 for information mapping. Based on my understanding, after I randomized the data, the classification acc (per voxel) I obtain during the feature selection step should be around chance level -- just as a sanity check. However, the top voxel's acc I got for each permutation is around 60%, which is way above chance, and does not make sense to me, suggesting that even if I throw random time series into the clf, the performance is still above chance. In order to make sure that this is replicable, I run FCMA permutation test with the face-scene dataset from the BRAINIAK dataset and got similar result -- with the original data, the top voxel acc is around 80%, and for the permutation test, after randomization, the top voxel acc is around 70% (still above chance).
The only change I made to the script is by adding the RandomType argument as following.  Note that the top_3000 voxel's locations I got during permutation test are indeed different from those I got from the original data -- they are random, unclustered. The only thing that bothers me is their above chance acc.
raw_data, _, labels = prepare_fcma_data(images, epoch_list, mask, random=RandomType.REPRODUCIBLE)
I'm not sure which step i did wrong that ended up causing this problem, or if I misunderstood the concept and that this above chance performance was expected for permutation test. I'm grateful for any sorts of help, and thank you all in advance!
Thank you very much,
Peeta

@yidawang, could you please chime in?

I don't recall the exact precision numbers I got before after permutation. Perhaps you can analyze it from the statistical perspective to see for totally random data, would the top voxels get above chance values. I guess that you may get a normal distribution in terms of precision numbers among all voxels, with mean value around 0.5. I am not sure about the variance though. In any case, if you see the random top voxels are scattered in the brain, but not clustered, it appears right to me.

@yidawang Thank you very much for the reply! I get what you suggested and I'll go ahead and check the distribution of voxel-wise classification accuracy.
One thing that still bothers me is that, for a given run of the permutation test, if I made a mask of the top 3000 voxels from feature selection, and then test on the classification accuracy using this mask (i.e., step 3) the ACC I got is above chance (here RandomType = REPRODUCIBLE, so the data should be randomized the same way as it was for feature selection). This is a problem to me because I'm doing FCMA on background connectivity. A above chance classification accuracy would indicate that the intrinsic functional connectivity pattern of the brain (i.e., after removing task-evoked response) still conveys information about the task. However, if a randomized 4D data can get above chance performance, it would be very hard for me to make conclusion for the result I have.

You probably can try one mask of top 3000, and the other mask for the whole brain. Limiting in top 3000 voxels may consistently give you above chance results as they are all informative in some way. DISCLAIMER: I may not remember every detail of FCMA implementation.

Ok that make sense! Thank you @yidawang and @mihaic for the reply!
I'll look into the distribution of voxel-wise acc and also check the clf acc with the full mask. I'll also try the permutation test with randomized label instead of the 4D data. It will take a while for the permutation to run but I'll come back here with what I end up having.

Hi, @peetal. Please remember to update or close this issue when you get results.

Sry for the late update, I think i figured out now. The code for shuffling the 2d data per subject [nVoxels, nTRs] uses np.random.shuffle(data), which by default shuffle the 2d array along the first axis. Thus the spatially relevance was randomized, but the timeseries structures was remained. Thus  the result of the permutation test should still have above chance accuracy, but the top k voxel mask should be completely randomized. And as Yida suggested, the voxel-wise acc for each voxel should be normally distributed. The randomization code could be modified in a sense that both two dimensions are shuffled, in that case the voxelwise acc should be around chance level. Another option is to shuffle the label instead of shuffling the data, which i have tried and works pretty well.

@peetal thanks for working on this and finding a workaround. It would be great if you could paste sample code of your workaround here. Thanks.


how could I use http2 protocol in vue

What problem does this feature solve?
As I know, I could use http2 protocol in node. how could u use it in vue?
What does the proposed API look like?
like axios module

Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the forum, the Discord server or StackOverflow.
This question is also unrelated to Vue as the http protocol happens on the server


Validation - late submit (@Mahmoudelsayed2)

Hello, here are web app logs from one user who had late submit. He said he submited with lot of time left 50sec-1min. He did validation using PC. Was connected to idena.to shared node. I will try to get logs from it.
https://scan.idena.io/identity/0xC680Ed4e4450D55A46D288056f76275B94E23D4e/epoch/72/validation
logs_validation_71_0xc680ed4e4450d55a46d288056f76275b94e23d4e.txt

Logs from idena.to shared node, thanks to idenato
https://idena.to/validation72-KSD83FA93DSF92D.zip
node operator comment
"looks like i forgot to update a script in charge of restarting the node in case it gets killed. Every minute it checked if 0.26.5 is active and since it wasn't (because 0.26.6 was running), it tried to start it. Doesn't seem to have any effect on the active instance though.."


Context persistency between sessions + fix multimonitor

Added a button to change monitors because dragging the window between screens causes an autoresizing problem.
Added support for other resolutions (e.g. 21:9).
Added writing to JSON for Context persistence between sessions

Hello @Creiv I've merged some of your changes into the 0.95b, let me know if I did break something on your code (hope not), not sure if I did this in the best way, I'm still learning about github and how to properly maintain the code, feel free to open further requests and Thanks again for contributing.


Deploy webhook, peerpod and peerpodconfig controllers via make target

When deploying CAA in a cluster via make deploy provide a way to deploy the webhook, peerpod and peerpodconfig controllers so that we have a fully working setup using extended resources for resource accouting, handling of dangling resources etc.

@jtumber-ibm @huoqifeng do you folks currently deploy all the components in your environment for testing ?

@jtumber-ibm @huoqifeng do you folks currently deploy all the components in your environment for testing ?

@bpradipt our testing pipeline did not cover cases regard webhook, peerpod and peerpodconfig yet but we have plan to add them.

This is partially done. However let's handle remaining work as part of https://github.com/confidential-containers/cloud-api-adaptor/issues/1976


GC Spikes with Hand Tracking

Describe the bug
Unity debugging is showing very large GC spikes which are impacting performance. Spikes appear to be related to hand tracking.

Turning on Incremental GC apparently didn’t help much. It did spread out the GC.Allocs, but didn’t reduce the overall GC pressure.

Your setup (please complete the following information)

Unity Version: 2019.4.12
MRTK Version: MRTK 2.4.0

Target platform (please complete the following information)

HoloLens 2

This is under active investigation. Looking into using faster unity APIs and caching some data where appropriate.
Hope to have more to share soon!

We believe this is fixed (in the upcoming 2.7.0 release) by #9490

Or at least improved. I'm still investigating additional paths for improvement.

@jbienzms have you been able to confirm whether the fix was good?

Some additional research uncovered some per frame allocs that have been mitigated. We also have identified some instances where the neutral pose version is changing over time. This is causing allocs at points throughout the runtime of the application.
There are some fixes incoming for 2.7.0.
At the same time, investigations will continue and incremental fixes (as identified) will be added in "dot dot" (ex: 2.7.1) releases.

#9746 adds some perf improvements.


Injecting a detected barcode frame inside a provided imageview

Provide a builder method that allows users to pass an imageview that will be injected with a detected barcode frame.

Hey Edward. Any progress on this feature. Would be very appreciated :)


FAQ item, retrieving substrates for all kinases or phosphatases

add FAQ  to retrieve
all substrates for a kinase phosphatase etc
https://helpdesk.ebi.ac.uk/Ticket/Display.html?id=163765
I wanted to add instructions using AmiGO too, as I thought this would provide an option without any need for  parsing.
However, probably best to include when we know which download option gives human readable extensions
https://github.com/geneontology/amigo/issues/413
===
AmiGO instructions
Locate the  GO term for your modification of interest
For example, GO:0004672 protein kinase activity for ALL protein kinases
If you are not familiar with the ontology you can use QuickGO browser ancestor view
http://www.ebi.ac.uk/QuickGO/GTerm?id=GO:0004672#term=ancchart to locate the most general applicable term.
Search for your term in Amigo using the term name or ID
http://amigo.geneontology.org/amigo
Use the “organism” filter (left panel) to select pombe
to filter on “fungi” and then “pombe”
The default  download file includes annotation extensions providing the target information in the form:
has_direct_input(PomBase:SPACXXXX)
(ideally we would be able to filter on relationship type too, not possible right now)

Well we will probably be able to do this in pombase before we can do it using AmiGO...

Closing,  we will make this a  custom download option, and I think it is already    included in the list?

is not easy with AmiGO
and should be able to do soonish
https://github.com/pombase/website/issues/576


Command to repeat the last action on a new target

When the user applies the same action multiple times to different targets subsequently, instead of repeating the action again, a one-word command to refer to the last action would save time and syllable.
Example:
“format camel at air”,
then “also bat”, “also cap and drum”, etc

Obviously not ideal but a workaround in the meantime
https://github.com/saidelike/saidelike_talon/blob/49bcb6cbae24ef5105fd96d12c55cbcfdf210857/cursorless.talon


Options for font source imports

What is the best way to include fonts from a CDN, like Google? Or Typekit?
Currently, I think this is set up to expect font files within the project on the same server. Would be nice to clearly document other ways to import/include font files, if possible.
If it doesn't work well with these other options, can we create this feature?  If not, can we state this within the readme and/or in the file in which we import the source?

@stacyk working on a solution for this, to set up fonts on OddSite. How does this syntax look? or do you have another idea?
// set variant path to 'false' to stop import.
$font: (
  'my-font': {
    'normal': 'my/local/font-path', // will be imported
    'italic': false, // will not be imported
  }
);

The goal is that we still list the available variants (italic, bold, etc) for Herman, but the system doesn't try to import those variants.

Would it make any sense to handle an absolute URI here? Or do these services vary too much in how they handle importing fonts?

We should handle absolute URI's for anyone serving their own fonts that way, but that's not how the big CDN services work. They all use JS to inject the font directly in the html — so we don't want the CSS to do anything in those cases.

Google puts all of them in one string instead of separate paths for different fonts/weights.
@import url('https://fonts.googleapis.com/css?family=Cabin+Condensed:700|Merriweather|Open+Sans+Condensed:400,700|Roboto+Condensed:400,700');


Add app-global GcmRegistrationManager to register for push services

Registration must be done both with the GCM server and with the matrix
home server, supplying a token acquired from the GCM server.
Registration is done in an AsyncTask, therefore the Matrix pushers API
can be called in a synchronous fashion without impacting responsiveness.
Registration of the pusher with the Matrix server is currently done on
every startup by SplashActivity but should eventually become a one-time
background task that is not tied to a specific activity.

LGTM other than comments (which I seem to have done on a commit rather than the full diff, sorry!)

Thank you for the review! I've rebased this onto develop, squashed the fixup commits and pushed the result to https://github.com/leonhandreke/matrix-android-sdk/tree/gcm-registration-develop. It's probably easiest if you pull from there.

That's awesome, thanks. Could you please open a PR for gcm-registration-develop, just so we can be consistent with how PRs are being created/processed/accepted, then I'll merge it in.


Need Help Installing ("Configure Krita")

I have a Mac and this is version 5.2.3 of Krita.
I made it to step 7 in the installation process and where I have to go from (Settings -> Configure Krita -> Python Plugin Manager). The only problem is that (for me at least) I can not find (Configure Krita) anywhere. The screenshot attached is what happens when I press settings while Krita is open:

Please help me with this, I really want to replace Adobe and this could really help me out.

It seems like the "Configure Krita" option is in a different place on Mac. When you press the "Krita" button in the top left corner (next to the Apple icon) you should be able to find the "Configure Krita" option in the menu that opens. Apparently it may also be nested in a "Preferences" menu but I'm not completely sure.
Once you find it, if you could let me know exactly where it's at that would be super helpful so I could update the instructions.

Thanks for the help, I found it exactly where you said it would be: On the Krita button -> Preferences -> Configure Krita.

I test it out with a mini animation, kind of disappointed in the fact it doesn't export an XML file like Adobe, but still does as advertised. But that's besides the point, I found out that when I exported the spritesheet, it also included the onion layered frames. This is done by using the sprite sheet generator while Onion frames are on or off. Here's the comparison:

Again, thanks for your help and making this awesome tool.

Thanks for the help, I found it exactly where you said it would be: On the Krita button -> Preferences -> Configure Krita.

Perfect, glad you were able to find it there!

I tested it out with a mini animation, kind of disappointed in the fact it doesn't export an XML file like Adobe, but it still does as advertised.

Ah yeah I didn't realize XML (and JSON) were formats that were being used for spritesheets/texture atlases so I didn't really consider them while making this tool. For the time being I'll probably keep it limited to PNGs (and maybe other basic image types), but if I find that XML/JSON is more commonly used than I thought then I'll reconsider.

But that's besides the point, I found out that when I exported the spritesheet, it also included the onion layered frames.

I noticed this as well, but unfortunately Krita doesn't seem to have an simple way to detect and disable onion skins through scripting as far as I know. I'll keep looking into it since it's something that's a bit annoying for my workflow as well though.


USD -> SDF: polygon triangulation

🎉 New feature
Summary
This implements the PolygonToTriangles function using the fan-triangulation algorithm. Initially tried to implement delaunay triangulation based on ignition::common's implementation, but the implementation is a wrapper around gts's implementation, which does not support 3D.
While researching a custom implementation, found out that there is a much simpler way using the fan-triangulation, it is not as robust as delaunay but it looks like a better fit for the use case of triangulating convex polygons. It seems like tools like blender also uses a form of fan-triangulation of these use cases and delaunay is more commonly used for more complex scenarios like generating terrains/heightmaps etc.
Test it
Currently tested with GearJoint.usd in isaac sim's examples (should be able to find it with a file system search). It seems to work somewhat, but I'm not sure if the current output is due to bad triangulation or other bugs.
usd:

sdf:

Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

It appears that gts already supports triangulating meshes, gts_surface_strip should do the trick. I will start that functionality to ignition common, after which, this PR will need the new version.

Opening the dae in blender at least looks like a cylinder

Will try to find out more about what is going on, maybe the way ign performs smoothing causes the distortion.


i3: 4.18.2 -> 4.18.3

Motivation for this change
Fixes #99197
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 102615 run on x86_64-darwin 1

2 packages marked as broken and skipped:

python37Packages.py3status
python38Packages.py3status

5 packages failed to build:

i3
powerline (python38Packages.powerline)
python37Packages.i3ipc
python37Packages.powerline
python38Packages.i3ipc

That's weird. The only functional change between i3-4.18.2 and i3-4.18.3 is this single commit, which not related to cairo. i3 depends on pango and pango has cairo in its propagatedBuildInputs.
If I run echo $NIX_CFLAGS_COMPILE|tr ' ' '\n'|grep cairo in my nixpkgs-review/pr-102615 shell, I get:
/nix/store/fn6sjqf47cgalkxgp7dmqi5grp9ifqdm-cairo-1.16.0-dev/include
/nix/store/2i8qx6qrl96yq5k5yfb5w24nz7c7f5mf-python3.8-pycairo-1.18.2/include
/nix/store/ij5rnq40r5b7x0f2b8mahg0rrqlx09ir-python3.7-pycairo-1.18.2/include
/nix/store/fn6sjqf47cgalkxgp7dmqi5grp9ifqdm-cairo-1.16.0-dev/include
/nix/store/2i8qx6qrl96yq5k5yfb5w24nz7c7f5mf-python3.8-pycairo-1.18.2/include

I guess that on Darwin, the cairo lines would be missing. Is it the case?

I guess that on Darwin, the cairo lines would be missing. Is it the case?

echo $NIX_CFLAGS_COMPILE|tr ' ' '\n'
-isystem
/nix/store/acbsjshd9mpq3hn9i1mj1l03jmc41828-libc++-7.1.0/include
-isystem
/nix/store/84507pkw9i7j3hc2dnc6nrzf10szmbzr-libc++abi-7.1.0/include
-isystem
/nix/store/r4np6gv2xaxr09l0mlviwq2sk1jadl8r-compiler-rt-7.1.0-dev/include
-iframework
/nix/store/4yfhzgb68xj7157b9qxxl8gr3v5q5nax-swift-corefoundation/Library/Frameworks
-isystem
/nix/store/acbsjshd9mpq3hn9i1mj1l03jmc41828-libc++-7.1.0/include
-isystem
/nix/store/84507pkw9i7j3hc2dnc6nrzf10szmbzr-libc++abi-7.1.0/include
-isystem
/nix/store/r4np6gv2xaxr09l0mlviwq2sk1jadl8r-compiler-rt-7.1.0-dev/include
-iframework
/nix/store/4yfhzgb68xj7157b9qxxl8gr3v5q5nax-swift-corefoundation/Library/Frameworks

Yes. If I add the grep back I get no output.

I'm affraid, I cannot help here. I'm not familiar with how nix works on Darwin and I doubt that the problem is caused by this PR. I believe, the same must happen even with i3 4.18.2. You can verify it by reverting the commit:

git revert e90cfc722dceae9ac947e51fe33f66e972beb0ea
nix-review rev HEAD

Can we just mark i3 broken on darwin to reduce random build failures in future PRs?

Feel free to send a PR or file an issue. I'm quite new to Nix ecosystem and don't feel qualified for doing it myself. But as I mentioned above, I don't think that it's i3, what's broken.


UploadFile API Extra unnecessary characters

extra '}' character in the file name;

@wsy19961129 This is very opened. Can you provide more context ? Are those two different issues ?

@wsy19961129 This is very opened. Can you provide more context ? Are those two different issues ?

Sure,

When the backend generate the file name from the file description, there is an extra '}' at the end;

The logs now could not show the correct information, the reason might be the using of the uploadFile API.

Indeed they are two issues, will open another issue.

When the backend generate the file name from the file description, there is an extra '}' at the end

Do we have to plan some work to correct this at the DB level ?

When the backend generate the file name from the file description, there is an extra '}' at the end

Do we have to plan some work to correct this at the DB level ?

No, this error appears only in the training dataset; and it only affects the name of the file extension.


username update issue

I recently updated my GIthub username but it was not updated by the ghuser server please check and fix this issue. @styfle @trel @jamesgeorge007 .

Hi @Ishaan28malik, your username is Ishaan28malik and https://ghuser.io/Ishaan28malik looks good. Am I missing something?

@AurelienLourot It got update and sorry I was refering to my display name and I just observed that it just took a day to get updated .


docs(orderBy): clarify behavior of default comparator

Doc update to clarify behavior of the default comparator starting in v1.3.7. See https://github.com/angular/angular.js/issues/15293

I signed it!

You can update the commit message by cloning your fork of this repo, amending the commit, and then force pushing it back.

This PR is for the 1.3.x branch. This is not maintained any more and even if we merged it, it wouldn't show up in the docs until there is a new release (and there will be no new release on the 1.3.x series :smiley:).

No problem - makes sense!


fix(parser): fix go test error on parser (#70)

golang/go#32479 removed the explicit type conversion string(i) where i has an integer type other than rune in go 1.15.
That is a backward incompatible change.
Fix #70.

 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.

 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.