Vmap_c decompilation errors

Describe the bug
When i try to decompile a vmap_c i got so many errors and the decompilaton failes
Expected behavior
Successfully decompile vmap_c to vmap
Relevant log output or exception with stacktrace
[19:37:34.063] Extracting de_inferno_night.vmap_c to "de_inferno_night.vmap"
[19:37:35.303] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.307] HammerMeshBuilder: Error! Failed to add face '9', face had 0 area
[19:37:35.308] HammerMeshBuilder: extracted '1' of '29' faces
[19:37:35.309] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.311] HammerMeshBuilder: Error! Failed to add face '3', face had 0 area
[19:37:35.313] HammerMeshBuilder: Error! Failed to add face '5', face had 0 area
[19:37:35.314] HammerMeshBuilder: Error! Failed to add face '17', face had 0 area
[19:37:35.316] HammerMeshBuilder: Error! Failed to add face '21', face had 0 area
[19:37:35.317] HammerMeshBuilder: Error! Failed to add face '27', face had 0 area
[19:37:35.319] HammerMeshBuilder: Error! Failed to add face '39', face had 0 area
[19:37:35.321] HammerMeshBuilder: Error! Failed to add face '52', face had 0 area
[19:37:35.323] HammerMeshBuilder: Error! Failed to add face '53', face had 0 area
[19:37:35.325] HammerMeshBuilder: Error! Failed to add face '80', face had 0 area
[19:37:35.327] HammerMeshBuilder: Error! Failed to add face '83', face had 0 area
[19:37:35.329] HammerMeshBuilder: Error! Failed to add face '89', face had 0 area
[19:37:35.333] HammerMeshBuilder: Error! Failed to add face '96', face had 0 area
[19:37:35.336] HammerMeshBuilder: extracted '12' of '122' faces
[19:37:35.339] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.343] HammerMeshBuilder: Error! Failed to add face '35', face had 0 area
[19:37:35.346] HammerMeshBuilder: extracted '1' of '203' faces
[19:37:35.349] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.358] HammerMeshBuilder: Error! Failed to add face '79', face had 0 area
[19:37:35.361] HammerMeshBuilder: extracted '1' of '118' faces
[19:37:35.364] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.367] HammerMeshBuilder: Error! Failed to add face '20', face had 0 area
[19:37:35.370] HammerMeshBuilder: Error! Failed to add face '27', face had 0 area
[19:37:35.373] HammerMeshBuilder: Error! Failed to add face '28', face had 0 area
[19:37:35.376] HammerMeshBuilder: Error! Failed to add face '32', face had 0 area
[19:37:35.380] HammerMeshBuilder: Error! Failed to add face '38', face had 0 area
[19:37:35.383] HammerMeshBuilder: Error! Failed to add face '43', face had 0 area
[19:37:35.386] HammerMeshBuilder: Error! Failed to add face '92', face had 0 area
[19:37:35.389] HammerMeshBuilder: Error! Failed to add face '97', face had 0 area
[19:37:35.392] HammerMeshBuilder: Error! Failed to add face '101', face had 0 area
[19:37:35.395] HammerMeshBuilder: Error! Failed to add face '112', face had 0 area
[19:37:35.398] HammerMeshBuilder: Error! Failed to add face '115', face had 0 area
[19:37:35.401] HammerMeshBuilder: Error! Failed to add face '119', face had 0 area
[19:37:35.404] HammerMeshBuilder: Error! Failed to add face '153', face had 0 area
[19:37:35.407] HammerMeshBuilder: Error! Failed to add face '157', face had 0 area
[19:37:35.410] HammerMeshBuilder: Error! Failed to add face '165', face had 0 area
[19:37:35.413] HammerMeshBuilder: Error! Failed to add face '180', face had 0 area
[19:37:35.416] HammerMeshBuilder: Error! Failed to add face '186', face had 0 area
[19:37:35.419] HammerMeshBuilder: Error! Failed to add face '191', face had 0 area
[19:37:35.422] HammerMeshBuilder: Error! Failed to add face '237', face had 0 area
[19:37:35.425] HammerMeshBuilder: Error! Failed to add face '244', face had 0 area
[19:37:35.428] HammerMeshBuilder: Error! Failed to add face '245', face had 0 area
[19:37:35.431] HammerMeshBuilder: Error! Failed to add face '251', face had 0 area
[19:37:35.434] HammerMeshBuilder: Error! Failed to add face '255', face had 0 area
[19:37:35.437] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.440] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.443] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.446] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.449] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.452] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.455] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.458] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.461] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.464] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.467] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.470] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.473] HammerMeshBuilder: Error! Failed to add face '257', face had 0 area
[19:37:35.476] HammerMeshBuilder: Error! Failed to add face '264', face had 0 area
[19:37:35.479] HammerMeshBuilder: Error! Failed to add face '267', face had 0 area
[19:37:35.483] HammerMeshBuilder: Error! Failed to add face '280', face had 0 area
[19:37:35.485] HammerMeshBuilder: Error! Failed to add face '290', face had 0 area
[19:37:35.489] HammerMeshBuilder: Error! Failed to add face '300', face had 0 area
[19:37:35.492] HammerMeshBuilder: Error! Failed to add face '311', face had 0 area
[19:37:35.495] HammerMeshBuilder: Error! Failed to add face '342', face had 0 area
[19:37:35.498] HammerMeshBuilder: Error! Failed to add face '348', face had 0 area
[19:37:35.501] HammerMeshBuilder: Error! Failed to add face '354', face had 0 area
[19:37:35.504] HammerMeshBuilder: Error! Failed to add face '360', face had 0 area
[19:37:35.507] HammerMeshBuilder: Error! Failed to add face '414', face had 0 area
[19:37:35.510] HammerMeshBuilder: Error! Failed to add face '432', face had 0 area
[19:37:35.513] HammerMeshBuilder: Error! Failed to add face '433', face had 0 area
[19:37:35.516] HammerMeshBuilder: Error! Failed to add face '460', face had 0 area
[19:37:35.519] HammerMeshBuilder: Error! Failed to add face '516', face had 0 area
[19:37:35.522] HammerMeshBuilder: Error! Failed to add face '575', face had 0 area
[19:37:35.525] HammerMeshBuilder: Error! Failed to add face '580', face had 0 area
[19:37:35.528] HammerMeshBuilder: Error! Failed to add face '584', face had 0 area
[19:37:35.531] HammerMeshBuilder: Error! Failed to add face '585', face had 0 area
[19:37:35.534] HammerMeshBuilder: Error! Failed to add face '590', face had 0 area
[19:37:35.537] HammerMeshBuilder: Error! Failed to add face '595', face had 0 area
[19:37:35.540] HammerMeshBuilder: extracted '57' of '605' faces
[19:37:35.543] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.546] HammerMeshBuilder: Error! Failed to add face '30', face had 0 area
[19:37:35.549] HammerMeshBuilder: extracted '1' of '91' faces
[19:37:35.552] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.555] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.558] HammerMeshBuilder: Error! Failed to add face '55', face had 0 area
[19:37:35.561] HammerMeshBuilder: extracted '1' of '65' faces
[19:37:35.564] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.567] HammerMeshBuilder: Error! Failed to add face '62', face had 0 area
[19:37:35.571] HammerMeshBuilder: Error! Failed to add face '182', face had 0 area
[19:37:35.574] HammerMeshBuilder: Error! Failed to add face '184', face had 0 area
[19:37:35.577] HammerMeshBuilder: Error! Failed to add face '194', face had 0 area
[19:37:35.580] HammerMeshBuilder: extracted '4' of '205' faces
[19:37:35.583] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.586] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.589] HammerMeshBuilder: Error! Failed to add face '15', face had 0 area
[19:37:35.592] HammerMeshBuilder: Error! Failed to add face '20', face had 0 area
[19:37:35.595] HammerMeshBuilder: Error! Failed to add face '24', face had 0 area
[19:37:35.599] HammerMeshBuilder: Error! Failed to add face '52', face had 0 area
[19:37:35.603] HammerMeshBuilder: Error! Failed to add face '98', face had 0 area
[19:37:35.606] HammerMeshBuilder: Error! Failed to add face '102', face had 0 area
[19:37:35.609] HammerMeshBuilder: Error! Failed to add face '111', face had 0 area
[19:37:35.612] HammerMeshBuilder: Error! Failed to add face '138', face had 0 area
[19:37:35.640] HammerMeshBuilder: Error! Failed to add face '142', face had 0 area
[19:37:35.643] HammerMeshBuilder: Error! Failed to add face '148', face had 0 area
[19:37:35.646] HammerMeshBuilder: Error! Failed to add face '158', face had 0 area
[19:37:35.649] HammerMeshBuilder: Error! Failed to add face '162', face had 0 area
[19:37:35.652] HammerMeshBuilder: Error! Failed to add face '196', face had 0 area
[19:37:35.655] HammerMeshBuilder: Error! Failed to add face '201', face had 0 area
[19:37:35.658] HammerMeshBuilder: Error! Failed to add face '229', face had 0 area
[19:37:35.661] HammerMeshBuilder: Error! Failed to add face '247', face had 0 area
[19:37:35.664] HammerMeshBuilder: Error! Failed to add face '324', face had 0 area
[19:37:35.667] HammerMeshBuilder: Error! Failed to add face '332', face had 0 area
[19:37:35.670] HammerMeshBuilder: Error! Failed to add face '347', face had 0 area
[19:37:35.673] HammerMeshBuilder: Error! Failed to add face '350', face had 0 area
[19:37:35.676] HammerMeshBuilder: Error! Failed to add face '351', face had 0 area
[19:37:35.679] HammerMeshBuilder: Error! Failed to add face '366', face had 0 area
[19:37:35.683] HammerMeshBuilder: Error! Failed to add face '373', face had 0 area
[19:37:35.686] HammerMeshBuilder: extracted '31' of '389' faces
[19:37:35.689] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.733] HammerMeshBuilder: Error! Failed to add face '10', face had 0 area
[19:37:35.736] HammerMeshBuilder: Error! Failed to add face '23', face had 0 area
[19:37:35.739] HammerMeshBuilder: Error! Failed to add face '33', face had 0 area
[19:37:35.743] HammerMeshBuilder: extracted '3' of '73' faces
[19:37:35.746] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.755] HammerMeshBuilder: Error! Failed to add face '18', face had 0 area
[19:37:35.758] HammerMeshBuilder: Error! Failed to add face '21', face had 0 area
[19:37:35.761] HammerMeshBuilder: Error! Failed to add face '29', face had 0 area
[19:37:35.765] HammerMeshBuilder: Error! Failed to add face '71', face had 0 area
[19:37:35.768] HammerMeshBuilder: extracted '4' of '82' faces
[19:37:35.771] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:35.780] HammerMeshBuilder: Error! Failed to add face '15', face had 0 area
[19:37:35.783] HammerMeshBuilder: Error! Failed to add face '18', face had 0 area
[19:37:35.789] HammerMeshBuilder: Error! Failed to add face '29', face had 0 area
[19:37:35.792] HammerMeshBuilder: Error! Failed to add face '39', face had 0 area
[19:37:35.795] HammerMeshBuilder: Error! Failed to add face '52', face had 0 area
[19:37:35.800] HammerMeshBuilder: Error! Failed to add face '59', face had 0 area
[19:37:35.803] HammerMeshBuilder: Error! Failed to add face '86', face had 0 area
[19:37:35.806] HammerMeshBuilder: Error!  Failed to add face '261', face had 0 area
[19:37:35.936] HammerMeshBuilder: extracted '2' of '400' faces
[19:37:35.939] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.446] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.450] HammerMeshBuilder: Error! Failed to add face '10', face had 0 area
[19:37:36.483] HammerMeshBuilder: extracted '10' of '152' faces
[19:37:36.486] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.489] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.492] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.495] HammerMeshBuilder: extracted '2' of '4' faces
[19:37:36.498] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.546] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:36.549] HammerMeshBuilder: extracted '1' of '17' faces
[19:37:36.552] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.559] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.562] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.565] HammerMeshBuilder: extracted '2' of '6' faces
[19:37:36.569] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.576] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.579] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.582] HammerMeshBuilder: extracted '2' of '7' faces
[19:37:36.585] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.758] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.761] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.764] HammerMeshBuilder: extracted '2' of '0' faces
[19:37:36.767] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.814] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:36.818] HammerMeshBuilder: extracted '1' of '7' faces
[19:37:36.821] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.836] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.840] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.843] HammerMeshBuilder: extracted '2' of '10' faces
[19:37:36.846] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.880] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.883] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:36.885] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.898] HammerMeshBuilder: Error! Failed to add face '266', face had 0 area
[19:37:36.901] HammerMeshBuilder: Error! Failed to add face '266', face had 0 area
[19:37:36.904] HammerMeshBuilder: extracted '2' of '292' faces
[19:37:36.907] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.910] HammerMeshBuilder: Error! Failed to add face '70', face had 0 area
[19:37:36.914] HammerMeshBuilder: extracted '1' of '139' faces
[19:37:36.916] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:36.980] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:36.983] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:36.986] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.134] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:37.137] HammerMeshBuilder: extracted '1' of '3' faces
[19:37:37.140] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.156] HammerMeshBuilder: Error! Failed to add face '20', face had 0 area
[19:37:37.169] HammerMeshBuilder: extracted '4' of '30' faces
[19:37:37.173] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.176] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.179] HammerMeshBuilder: extracted '1' of '215' faces
[19:37:37.182] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.209] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.212] HammerMeshBuilder: extracted '1' of '5' faces
[19:37:37.215] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.218] HammerMeshBuilder: Error! Failed to add face '4', face had 0 area
[19:37:37.221] HammerMeshBuilder: extracted '1' of '4' faces
[19:37:37.224] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.227] HammerMeshBuilder: Error! Failed to add face '3', face had 0 area
[19:37:37.231] HammerMeshBuilder: Error! Failed to add face '3', face had 0 area
[19:37:37.234] HammerMeshBuilder: extracted '2' of '19' faces
[19:37:37.237] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.240] HammerMeshBuilder: Error! Failed to add face '12', face had 0 area
[19:37:37.281] HammerMeshBuilder: extracted '12' of '39' faces
[19:37:37.284] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.287] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.302] HammerMeshBuilder: extracted '5' of '4' faces
[19:37:37.305] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.318] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:37.321] HammerMeshBuilder: extracted '1' of '13' faces
[19:37:37.325] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.328] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.331] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:37.334] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.337] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.340] HammerMeshBuilder: extracted '1' of '4' faces
[19:37:37.344] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.350] HammerMeshBuilder: Error!  Failed to add face '9', face had 0 area
[19:37:37.547] HammerMeshBuilder: extracted '1' of '19' faces
[19:37:37.550] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.559] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:37.562] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:37.565] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:37.863] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:37.867] HammerMeshBuilder: extracted '4' of '8' faces
[19:37:37.870] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.876] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.885] HammerMeshBuilder: extracted '3' of '10' faces
[19:37:37.888] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.892] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.898] HammerMeshBuilder: extracted '2' of '0' faces
[19:37:37.904] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.907] HammerMeshBuilder: Error! Failed to add face '3', face had 0 area
[19:37:37.913] HammerMeshBuilder: extracted '2' of '3' faces
[19:37:37.916] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.919] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.923] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:37.926] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.955] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.983] HammerMeshBuilder: extracted '7' of '9' faces
[19:37:37.986] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:37.990] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:37.995] HammerMeshBuilder: extracted '1' of '1' faces
[19:37:37.998] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.004] HammerMeshBuilder: Error! Failed to add face '6', face had 0 area
[19:37:38.031] HammerMeshBuilder: extracted '8' of '43' faces
[19:37:38.034] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.037] HammerMeshBuilder: Error! Failed to add face '4', face had 0 area
[19:37:38.046] HammerMeshBuilder: extracted '3' of '11' faces
[19:37:38.049] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.069] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:38.074] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:38.077] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:38.080] HammerMeshBuilder: extracted '3' of '1' faces
[19:37:38.083] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.180] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.183] HammerMeshBuilder: extracted '1' of '5' faces
[19:37:38.186] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.244] HammerMeshBuilder: Error! Failed to add face '6', face had 0 area
[19:37:38.289] HammerMeshBuilder: extracted '14' of '26' faces
[19:37:38.292] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.311] HammerMeshBuilder: Error! Failed to add face '8', face had 0 area
[19:37:38.331] HammerMeshBuilder: extracted '6' of '38' faces
[19:37:38.334] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.343] HammerMeshBuilder: Error! Failed to add face '9', face had 0 area
[19:37:38.346] HammerMeshBuilder: Error! Failed to add face '9', face had 0 area
[19:37:38.349] HammerMeshBuilder: extracted '2' of '35' faces
[19:37:38.352] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.359] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.362] HammerMeshBuilder: extracted '1' of '57' faces
[19:37:38.365] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.374] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.377] HammerMeshBuilder: extracted '1' of '23' faces
[19:37:38.380] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.442] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:38.445] HammerMeshBuilder: extracted '1' of '34' faces
[19:37:38.450] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.517] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.520] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.523] HammerMeshBuilder: extracted '2' of '0' faces
[19:37:38.529] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.560] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.565] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.568] HammerMeshBuilder: extracted '2' of '4' faces
[19:37:38.571] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.619] HammerMeshBuilder: Error! Failed to add face '28', face had 0 area
[19:37:38.634] HammerMeshBuilder: extracted '5' of '45' faces
[19:37:38.637] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.704] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.707] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.710] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.713] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.716] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.719] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.722] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.725] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.730] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:38.733] HammerMeshBuilder: extracted '9' of '48' faces
[19:37:38.736] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.777] HammerMeshBuilder: Error! Failed to add face '8', face had 0 area
[19:37:38.780] HammerMeshBuilder: extracted '1' of '18' faces
[19:37:38.783] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.789] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.792] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:38.795] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.876] HammerMeshBuilder: Error! Failed to add face '29', face had 0 area
[19:37:38.880] HammerMeshBuilder: extracted '1' of '69' faces
[19:37:38.883] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.913] HammerMeshBuilder: Error! Failed to add face '9', face had 0 area
[19:37:38.916] HammerMeshBuilder: Error! Failed to add face '9', face had 0 area
[19:37:38.922] HammerMeshBuilder: Error! Failed to add face '9', face had 0 area
[19:37:38.925] HammerMeshBuilder: extracted '3' of '9' faces
[19:37:38.928] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.931] HammerMeshBuilder: Error! Failed to add face '4', face had 0 area
[19:37:38.934] HammerMeshBuilder: Error! Failed to add face '4', face had 0 area
[19:37:38.937] HammerMeshBuilder: extracted '2' of '10' faces
[19:37:38.940] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:38.958] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.961] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.964] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:38.967] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.042] HammerMeshBuilder: extracted '4' of '92' faces
[19:37:39.046] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.058] HammerMeshBuilder: Error! Failed to add face '37', face had 0 area
[19:37:39.062] HammerMeshBuilder: Error! Failed to add face '37', face had 0 area
[19:37:39.065] HammerMeshBuilder: extracted '2' of '87' faces
[19:37:39.069] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.099] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.110] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.115] HammerMeshBuilder: extracted '2' of '6' faces
[19:37:39.118] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.245] HammerMeshBuilder: Error! Failed to add face '311', face had 0 area
[19:37:39.278] HammerMeshBuilder: extracted '8' of '775' faces
[19:37:39.282] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.385] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.388] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.392] HammerMeshBuilder: extracted '2' of '0' faces
[19:37:39.396] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.400] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.403] HammerMeshBuilder: Error! Failed to add face '32', face had 0 area
[19:37:39.409] HammerMeshBuilder: Error! Failed to add face '32', face had 0 area
[19:37:39.412] HammerMeshBuilder: Error! Failed to add face '32', face had 0 area
[19:37:39.415] HammerMeshBuilder: Error! Failed to add face '32', face had 0 area
[19:37:39.419] HammerMeshBuilder: extracted '4' of '34' faces
[19:37:39.422] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.425] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:39.430] HammerMeshBuilder: extracted '1' of '1' faces
[19:37:39.433] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.435] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.439] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:39.443] HammerMeshBuilder: Error! Failed to add face '7', face had 0 area
[19:37:39.446] HammerMeshBuilder: extracted '2' of '7' faces
[19:37:39.449] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.452] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.455] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.459] HammerMeshBuilder: Error! Failed to add face '5', face had 0 area
[19:37:39.462] HammerMeshBuilder: Error! Failed to add face '6', face had 0 area
[19:37:39.465] HammerMeshBuilder: extracted '2' of '7' faces
[19:37:39.469] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.472] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.475] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.480] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.483] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.487] HammerMeshBuilder: extracted '2' of '0' faces
[19:37:39.492] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.496] HammerMeshBuilder: Error! Failed to add face '6', face had 0 area
[19:37:39.500] HammerMeshBuilder: extracted '1' of '6' faces
[19:37:39.503] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.507] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.511] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.515] HammerMeshBuilder: extracted '2' of '5' faces
[19:37:39.518] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.521] HammerMeshBuilder: Error! Failed to add face '5', face had 0 area
[19:37:39.525] HammerMeshBuilder: extracted '1' of '11' faces
[19:37:39.529] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.532] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.535] HammerMeshBuilder: Error! Failed to add face '24', face had 0 area
[19:37:39.538] HammerMeshBuilder: Error! Failed to add face '24', face had 0 area
[19:37:39.541] HammerMeshBuilder: Error! Failed to add face '24', face had 0 area
[19:37:39.548] HammerMeshBuilder: Error! Failed to add face '24', face had 0 area
[19:37:39.551] HammerMeshBuilder: Error! Failed to add face '25', face had 0 area
[19:37:39.554] HammerMeshBuilder: Error! Failed to add face '36', face had 0 area
[19:37:39.558] HammerMeshBuilder: Error! Failed to add face '37', face had 0 area
[19:37:39.563] HammerMeshBuilder: Error! Failed to add face '37', face had 0 area
[19:37:39.566] HammerMeshBuilder: Error! Failed to add face '43', face had 0 area
[19:37:39.570] HammerMeshBuilder: Error! Failed to add face '43', face had 0 area
[19:37:39.574] HammerMeshBuilder: extracted '10' of '48' faces
[19:37:39.577] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.582] HammerMeshBuilder: Error! Failed to add face '19', face had 0 area
[19:37:39.584] HammerMeshBuilder: Error! Failed to add face '21', face had 0 area
[19:37:39.587] HammerMeshBuilder: Error! Failed to add face '22', face had 0 area
[19:37:39.591] HammerMeshBuilder: extracted '3' of '25' faces
[19:37:39.595] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.598] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.601] HammerMeshBuilder: Error! Failed to add face '16', face had 0 area
[19:37:39.604] HammerMeshBuilder: Error! Failed to add face '16', face had 0 area
[19:37:39.607] HammerMeshBuilder: Error! Failed to add face '17', face had 0 area
[19:37:39.611] HammerMeshBuilder: Error! Failed to add face '17', face had 0 area
[19:37:39.614] HammerMeshBuilder: Error! Failed to add face '17', face had 0 area
[19:37:39.617] HammerMeshBuilder: Error! Failed to add face '17', face had 0 area
[19:37:39.620] HammerMeshBuilder: Error! Failed to add face '19', face had 0 area
[19:37:39.623] HammerMeshBuilder: Error! Failed to add face '19', face had 0 area
[19:37:39.627] HammerMeshBuilder: extracted '8' of '19' faces
[19:37:39.631] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.634] HammerMeshBuilder: Error! Failed to add face '8', face had 0 area
[19:37:39.637] HammerMeshBuilder: Error! Failed to add face '10', face had 0 area
[19:37:39.643] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.646] HammerMeshBuilder: extracted '3' of '11' faces
[19:37:39.649] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.674] Failed to extract 'de_inferno_night.vmap_c': Object reference not set to an instance of an object.
[19:37:39.678] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.684] HammerMeshBuilder: Error! Failed to add face '15', face had 0 area
[19:37:39.688] Export completed in 00:00:05.6196279.
[19:37:39.691] HammerMeshBuilder: Error! Failed to add face '15', face had 0 area
[19:37:39.694] HammerMeshBuilder: Error! Failed to add face '17', face had 0 area
[19:37:39.699] HammerMeshBuilder: Error! Failed to add face '17', face had 0 area
[19:37:39.702] HammerMeshBuilder: extracted '4' of '17' faces
[19:37:39.705] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.710] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.713] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.716] HammerMeshBuilder: Error! Failed to add face '38', face had 0 area
[19:37:39.719] HammerMeshBuilder: Error! Failed to add face '38', face had 0 area
[19:37:39.722] HammerMeshBuilder: extracted '2' of '44' faces
[19:37:39.725] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.729] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.732] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.735] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.740] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.743] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.746] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.749] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.752] HammerMeshBuilder: extracted '7' of '32' faces
[19:37:39.755] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.759] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.762] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.764] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.767] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.770] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.773] HammerMeshBuilder: extracted '4' of '6' faces
[19:37:39.777] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.780] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.783] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.789] HammerMeshBuilder: extracted '2' of '12' faces
[19:37:39.791] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.794] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.797] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.800] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.803] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.807] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.810] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.813] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.816] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.819] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.822] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.826] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.828] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.831] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.834] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.837] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.840] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:39.844] HammerMeshBuilder: extracted '15' of '62' faces
[19:37:39.847] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.849] HammerMeshBuilder: Error! Failed to add face '4', face had 0 area
[19:37:39.852] HammerMeshBuilder: extracted '1' of '4' faces
[19:37:39.855] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.873] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:39.876] HammerMeshBuilder: extracted '1' of '1' faces
[19:37:39.880] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.910] HammerMeshBuilder: Error! Failed to add face '8', face had 0 area
[19:37:39.913] HammerMeshBuilder: extracted '1' of '8' faces
[19:37:39.916] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:39.940] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.943] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.946] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.949] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.952] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.955] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.959] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.962] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.965] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.971] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.974] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.976] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.979] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.982] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.985] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.989] HammerMeshBuilder: Error! Failed to add face '11', face had 0 area
[19:37:39.992] HammerMeshBuilder: Error!  Failed to add face '11', face had 0 area
[19:37:39.998] HammerMeshBuilder: extracted '18' of '76' faces
[19:37:40.001] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:40.019] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:40.022] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:40.025] HammerMeshBuilder: extracted '2' of '4' faces
[19:37:40.028] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:40.437] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:40.440] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:40.443] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:40.470] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:40.473] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:40.476] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:40.501] HammerMeshBuilder: Error! Failed to add face '18', face had 0 area
[19:37:40.504] HammerMeshBuilder: Error! Failed to add face '18', face had 0 area
[19:37:40.507] HammerMeshBuilder: extracted '2' of '18' faces
[19:37:40.511] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:40.514] HammerMeshBuilder: Error! Failed to add face '27', face had 0 area
[19:37:40.517] HammerMeshBuilder: extracted '1' of '30' faces
[19:37:40.522] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:40.541] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:40.544] HammerMeshBuilder: extracted '1' of '1' faces
[19:37:40.547] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:40.665] HammerMeshBuilder: Error! Failed to add face '8', face had 0 area
[19:37:40.668] HammerMeshBuilder: extracted '1' of '8' faces
[19:37:40.671] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:41.653] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:41.655] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:41.657] HammerMeshBuilder: extracted '2' of '11' faces
[19:37:41.659] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:42.182] HammerMeshBuilder: Error! Failed to add face '5', face had 0 area
[19:37:42.186] HammerMeshBuilder: extracted '1' of '5' faces
[19:37:42.189] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:42.695] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:42.700] HammerMeshBuilder: extracted '1' of '1' faces
[19:37:42.704] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:42.953] HammerMeshBuilder: Error! Failed to add face '4', face had 0 area
[19:37:42.956] HammerMeshBuilder: extracted '1' of '6' faces
[19:37:42.959] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:42.972] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:42.975] HammerMeshBuilder: extracted '1' of '2' faces
[19:37:42.978] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:43.027] HammerMeshBuilder: Error! Failed to add face '6', face had 0 area
[19:37:43.030] HammerMeshBuilder: Error! Failed to add face '8', face had 0 area
[19:37:43.032] HammerMeshBuilder: extracted '2' of '8' faces
[19:37:43.034] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:43.259] HammerMeshBuilder: Error! Failed to add face '1', face had 0 area
[19:37:43.261] HammerMeshBuilder: extracted '1' of '1' faces
[19:37:43.263] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:43.296] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:43.298] HammerMeshBuilder: extracted '1' of '20' faces
[19:37:43.300] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:43.595] HammerMeshBuilder: Error! Failed to add face '3', face had 0 area
[19:37:43.597] HammerMeshBuilder: extracted '1' of '3' faces
[19:37:43.599] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:43.679] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:43.681] HammerMeshBuilder: extracted '1' of '4' faces
[19:37:43.683] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:43.771] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:43.774] HammerMeshBuilder: extracted '1' of '4' faces
[19:37:43.776] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:44.005] HammerMeshBuilder: Error! Failed to add face '2', face had 0 area
[19:37:44.007] HammerMeshBuilder: extracted '1' of '2' faces
[19:37:44.009] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:44.039] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:44.042] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:44.046] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:44.109] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:44.112] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:44.114] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:44.237] HammerMeshBuilder: Error! Failed to add face '6', face had 0 area
[19:37:44.239] HammerMeshBuilder: extracted '1' of '6' faces
[19:37:44.241] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:44.440] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:44.443] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:44.445] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:44.634] HammerMeshBuilder: Error! Failed to add face '8', face had 0 area
[19:37:44.636] HammerMeshBuilder: extracted '1' of '8' faces
[19:37:44.639] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:44.696] HammerMeshBuilder: Error! Failed to add face '3', face had 0 area
[19:37:44.698] HammerMeshBuilder: extracted '1' of '3' faces
[19:37:44.700] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:45.028] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.030] HammerMeshBuilder: extracted '1' of '2' faces
[19:37:45.034] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:45.085] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.086] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.090] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.093] HammerMeshBuilder: extracted '3' of '128' faces
[19:37:45.095] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:45.116] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.118] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.120] HammerMeshBuilder: extracted '2' of '29' faces
[19:37:45.123] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:45.409] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.411] HammerMeshBuilder: extracted '1' of '16' faces
[19:37:45.414] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:45.643] HammerMeshBuilder: Error! Failed to add face '3', face had 0 area
[19:37:45.646] HammerMeshBuilder: extracted '1' of '7' faces
[19:37:45.648] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:45.689] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.692] HammerMeshBuilder: extracted '1' of '0' faces
[19:37:45.695] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:45.828] HammerMeshBuilder: Error! Failed to add face '0', face had 0 area
[19:37:45.830] HammerMeshBuilder: extracted '1' of '5' faces
[19:37:45.834] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:46.239] HammerMeshBuilder: Error! Failed to add face '17', face had 0 area
[19:37:46.241] HammerMeshBuilder: extracted '1' of '17' faces
[19:37:46.244] PhysicsVertexMatcher: Matched 0.00% (0 vertices) of rendermesh to physics vertices!
[19:37:46.250] HammerMeshBuilder: Error!

What game does this happen in
CS2
Reference file in a Source 2 game
Z:\Program Files (x86)\Steam\steamapps\common\Counter-Strike Global Offensive\content\csgo_addons\inferno_night\maps\de_inferno_night.vpk - de_inferno_night.vmap_c
What version of VRF are you using? Test latest dev build.
Latest, 10.0 version

Error log is shortened, i just removed a bunch of duplicated lines

First of all that is not the entire log, what is the actual issue, second of all I told you before not to decompile inferno night as it's an old decompile itself and it won't work.


phantomjs-node: You don't have 'phantomjs' installed on Windows

Hi,
I am using phantomjs to generate pdf but i m stuck when am using in windows machine it says you dont have phantomjs installed on windows.
But when i type phantomjs it give me the prompt of phantomjs.
var phantom = require('phantom');
phantom.create(function (ph) {
ph.createPage(function (page) {
/* the page actions */
});
}, {
dnodeOpts: {
weak: false
}
});
Please Can anyone help regard this ...

Same here, Windows 8.1

your path from options to phantom.exe, is correct ? like C:\user\phantomjs ?

The error message You don't have 'phantomjs' installed is an internal error from phantomjs-node. I ran into this error myself, and I managed to fix it like this:
var phantom = require('phantom');

var options = {
		path: '/usr/local/bin/'
};

phantom.create(function (ph) {
	ph.createPage(function (page) {
		page.open("http://www.google.com", function (status) {
			console.log("opened google? ", status);
			page.evaluate(function () { return document.title; }, function (result) {
				console.log('Page title is ' + result);
				ph.exit();
			});
		});
	});
}), options);

Notice the options being passed to the phantom.create() method. The path option should be the full path to the directory that contains your phantomjs binary.

@chill117 I copy the exact code and still have an error:
<path>file.js:17
}), options);
           ^
SyntaxError: Unexpected token )
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Function.Module.runMain (module.js:501:10)
    at startup (node.js:129:16)
    at node.js:814:3

@lebedkin There was a syntax error in the code I posted. Sorry about that. I've corrected the error.


fix reactor config test

Signed-off-by: Robert Cerven<EMAIL_ADDRESS>

added more info to the commit message

Not updating release notes draft because this is a change solely to unit tests.


Onboarding Tushar

Covered the following topics yesterday:
Current Tech stack
Data loading
Data harmonization and mapping

moving to the next sprint


List of Critical Projects links

The Google Sheet with the list of Critical Projects has non-canonical links for some projects for which I would request an update.  The Github links for Autotools, Make and GCC are mirrors that are not controlled by the projects (in fact GCC has requested assistance from Github multiple times to move the mirrors to our Github organization)

GCC should be https://gcc.gnu.org/
(Should GCC be listed as GNU Toolchain to encompass the entire toolchain equivalent to the LLVM listing? GCC, GLIBC, Binutils, GDB)

Make should be https://www.gnu.org/software/make/

The link for Autotools also is non-canonical, but there is no official site that encompasses all of the tools. There is no "Autotools" project -- it is term that is used to encompass the GNU Build Tools. Should the projects be listed individually?

Yes, I think the tools should listed individually. The umbrella term "autotools" is widely used, though, so mentioning somewhere that "The term 'autotools' includes the following tools: automake, libtool, autoconf, ..." (I know those are part of the autotools, I don't know if others are also considered to be part).

The Github pseudo-account autotools-mirror includes autoconf, automake, gettext, libtool, and m4.
I don't know if you want to split out the GNU Toolchain projects individually (GCC, GLIBC, GDB, Binutils) but it would be more clear to refer to it as the GNU Toolchain.

A very good point about the importance of considering how granular we want to be. In general, it makes sense to list out the projects.


[APIM 1.10] Issue with the Gateway Caching when Access token is generated with associsted domain/s

Previous to APIM 2.0.0 version we have a feature to have a token that can use for a specific set of domains. Due to this feature, we have to validate token with referer header for blocking API call/s.
Thus when we get Key Validation Info we have a null check for' clientDomain'.
If this 'clientDomain' is not null based on the existing logic gateway token cache is not get populated and therefore to get the key validation information it always calls to the key manager.
In the long run, this becomes a performance hit.

Key validation call to the key manager will be completely removed in the future release.


Rename master view

Just a proposal. Maybe it would be better if master.blade.php was named app.blade.php and avoid renaming?
Also, instead of breaking execution when layouts folder is found, maybe it would be better if user was prompted to overwrite existing layouts/app.blade.php?

  You can call it app, which will result in app.blade.php, but then you may run into problems when running make:auth.   When I get to a refinement phase, I will look at doing your second suggestion about allowing them to overwrite the file because I know we can provide feedback to the user and give them a choice.  That would probably be a better user experience, seems like it would be important, since you are already asking for it.


Socials page

Number of Volunteers: 1
Example from ICLR
ICLR 2020 - Socials.pdf

Reach out the social event chairs to collect the following information

Organizer names
Logo
Event description
Website link
Name of the RocketChat channel, e.g., #queer-in-ai. (the channel name cannot have special characters or space in between)
Live Zoom call schedule

@Robert-Alonso Can you first make a sample webpage with some dummy social events? I'll get back to you with our schedule.
Let me know if you need more instructions about where to start.

@Robert-Alonso I updated the instructions.
Maybe you can make the sample webpage using the ICLR template https://github.com/ICLR/iclr.github.io/blob/master/templates/pages/socials.html
Let me know if you need any more information.
Also, if you feel you need another volunteer to pair with you, please let me know and we will see if we can assign another person on this issue.

Thanks for the extra info and the reference repo @hao-fang, I was just about to ask about some details about the ICLR socials page screenshot which I was replicating in the branch I was working on. I started with a format based on the workshops section with dummy social events, which I'll add to the sitedata repo, I'll be checking out the ICLR template 👍

@Robert-Alonso @dreasysnail -- I think the current version is good for a basic website.
We can do enhancement with follow-up issues. So I'm closing this ticket for now.
But if you are still working on it, feel free to re-open it.


feat: tool calling for Bedrock's Claude and General LLM Agent

A note: let me know what naming is preferred for the agent. I called it LLMAgent but Agent sounds good too I can change it if preferred.
I reshuffled a bunch of things but that was only to make Agent development easier and faster since I'll be adding Gemini tool calling support next.
Technically AnthropicAgent and OpenAIAgent are not explicitly needed but I left them there since someone might be using it and it seems LITS current doesn't have streaming tool support for Calude Models via Anthropic which AnthropicAgent takes into account
  import { LLMAgent } from "llamaindex";

  const agent = new LLMAgent({
    llm, // can be Anthropic, Bedrock, OpenAI or any LITS LLM that has tool calling support added
    tools: [tool]
  });

  const response = await agent.chat({
    stream: false,
    message: "call the tool",
  });

closes #939
@marcusschiesser @himself65

@himself65 as your agent is involved, it's better your reviewing this


Build failures with CMake and Visual Studio

I experienced a few problems when I tried to build the library and the examples via Visual Studio and Intel Fortran oneAPI on Windows. The steps I took are simple enough:

Run CMake with default settings. On my system I get a VS solution for Visual Studio 17 2022.
Build solution: the first round gives a build problem regarding the module file FEQPARSE in the test programs.
Building it again only gives a single error: lib ..\src\libfeqparse-static.a does not exist. This is for "testsuite"
Because the other problems are gone I suspect that the test programs are not properly dependent on the feqparse library. Indeed "testsuite" does not depend on anything but "ZERO_CHECK"(a CMake target).
In tests/CMakeLists.txt I see that a fixed name is used for the libfeqparse-static library. On Windows this would have the extension .lib.

Thanks for reporting. I don't have access to a Windows system with visual studio. If you have modifications for the CMake build system that function for Windows with visual studio and the Intel compilers, feel free to open a pull request.

Hi, well, that should be no particular problem. Will do.
Op za 2 dec 2023 om 15:58 schreef Joe Schoonover @.***>:

Thanks for reporting. I don't have access to a Windows system with visual
studio. If you have modifications for the CMake build system that function
for Windows with visual studio and the Intel compilers, feel free to open a
pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/FluidNumerics/feq-parse/issues/14#issuecomment-1837167329,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN6YR4TEFS77LXLFK7UKN3YHM6XPAVCNFSM6AAAAABAEBGQ42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGE3DOMZSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Well, the linkage problem is gone - that was easy, but the compile problems
are confounding:
There are four source files in the test directory that present problems:
Build Log
Build started: Project: testsuite_fortran, Configuration: Debug|x64
Output
Compiling with Intel® Fortran Compiler Classic 2021.9.0 [Intel(R)
64]...
ifort /nologo /debug:full /Od /fpp /I"D:\fortran\feq-parse\build\include"
/I"D:\fortran\feq-parse\build\include/Debug" /DCMAKE_INTDIR="Debug"
/module:"..\include\Debug" /object:"testsuite_fortran.dir\Debug\"
/Fd"testsuite_fortran.dir\Debug\vc170.pdb" /libs:dll /threads /dbglibs /c
/W1 /Qlocation,link,"C:\Program Files\Microsoft Visual
Studio\2022\Professional\VC\Tools\MSVC\14.36.32532\bin\HostX64\x64" /Qm64
"D:\fortran\feq-parse\test\linear_r1fp32.f90"
D:\fortran\feq-parse\test\linear_r1fp32.f90(3): error #7002: Error in
opening the compiled module file.  Check INCLUDE paths.   [FEQPARSE]
USE FEQParse
------^
D:\fortran\feq-parse\test\linear_r1fp32.f90(7): error #6457: This derived
type name has not been declared.   [EQUATIONPARSER]
TYPE(EquationParser) :: f
-------^
D:\fortran\feq-parse\test\linear_r1fp32.f90(22): error #6404: This name
does not have a type, and must have an explicit type.   [F]
f = EquationParser(eqChar, independentVars)
----^
compilation aborted for D:\fortran\feq-parse\test\linear_r1fp32.f90 (code 1)
The files in question:

linear_r1fp32.f90
asin_r1fp32.f90
atan_sfp64.f90
tan_sfp32.f90

All others are fine. It is not a problem with parallel builds, as the list
is always the same.
I have compared the generated command-lines for one of the above files with
one that does get compiled the first time around and there is no difference
in the options.
I am puzzled :(.
Op zo 3 dec 2023 om 11:09 schreef Arjen Markus @.***>:

Hi, well, that should be no particular problem. Will do.
Op za 2 dec 2023 om 15:58 schreef Joe Schoonover @.***

:

Thanks for reporting. I don't have access to a Windows system with visual
studio. If you have modifications for the CMake build system that function
for Windows with visual studio and the Intel compilers, feel free to open a
pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/FluidNumerics/feq-parse/issues/14#issuecomment-1837167329,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN6YR4TEFS77LXLFK7UKN3YHM6XPAVCNFSM6AAAAABAEBGQ42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGE3DOMZSHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Actually, yes and the other files are compiled without any complaint
whatsoever. I will ask on Discourse whether someone has a solution.
BTW, the fix for the feqparse-static library is:
target_link_libraries (${TARGET} ${TARGET}_fortran feqparse-static)

and remove the line:
target_link_libraries (${TARGET}

${CMAKE_BINARY_DIR}/src/libfeqparse-static.a)
(I Have not figured out how to use the variable holding the name, but this
works)
Op zo 3 dec 2023 om 21:27 schreef Joe Schoonover @.***>:

That is odd. Do either of the include paths
D:\fortran\feq-parse\build\include or
D:\fortran\feq-parse\build\include/Debug contain feqparse.mod ?
—
Reply to this email directly, view it on GitHub
https://github.com/FluidNumerics/feq-parse/issues/14#issuecomment-1837590530,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN6YRYDM6ZRUPIVXSD47ADYHTOB7AVCNFSM6AAAAABAEBGQ42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZXGU4TANJTGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

@arjenmarkus - I added another commit to the bugfix/issue-12 branch that I think will resolve the issue.
What seems to be happening is that the ${TARGET}_fortran target is building before the feqparse-static target is finished building. The test/CMakeLists.txt didn't really have an explicit dependency between compiling the src/ directory and compiling the .f90 files in the test directory (though there is a dependency between compiling the generated main.c and feqparse-static). I've added an add_dependencies statement to force feqparse-static to be built entirely before building any of the test/*.f90 files. I'd be interested to see if this resolves your CMake issue.
I've configured VSCode on Ubuntu 22.04 to use the CMake build system and it seems to build just fine

Right, "add_dependencies" is the statement I was looking for! That did the
trick, it was all built in one go, no issues.
I ran the test program:

The option -A does not seem to work for some reason, at least I see no
output at all.
Several tests, 131 and 132 in particular (I did not manually try all
of them), give a long list of warnings - Attempt to pop from empty token
stack.

Other than that the build process runs smoothly :).
Op ma 4 dec 2023 om 20:17 schreef Joe Schoonover @.***>:

@arjenmarkus https://github.com/arjenmarkus - I added another commit to
the bugfix/issue-12 branch
https://github.com/FluidNumerics/feq-parse/tree/bugfix/issue-12 that I
think will resolve the issue.
What seems to be happening is that the ${TARGET}_fortran target is
building before the feqparse-static target is finished building. The
test/CMakeLists.txt didn't really have an explicit dependency between
compiling the src/ directory and compiling the .f90 files in the test
directory (though there is a dependency between compiling the generated
main.c and feqparse-static). I've added an add_dependencies statement to
force feqparse-static to be built entirely before building any of the
test/*.f90 files. I'd be interested to see if this resolves your CMake
issue.
I've configured VSCode on Ubuntu 22.04 to use the CMake build system and
it seems to build just fine
—
Reply to this email directly, view it on GitHub
https://github.com/FluidNumerics/feq-parse/issues/14#issuecomment-1839307453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN6YRY7HWXH7DX6MJYNESTYHYOWJAVCNFSM6AAAAABAEBGQ42VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZZGMYDONBVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

Excellent, now that we got the CMake and Visual Studio resolved, I'll work on fixing the Intel build. To run the tests, you can move into the test subdirectory underneath CMake's build directory and run ctest


Add Plugin: gatsby-react-next

https://www.gatsbyjs.org/packages/gatsby-plugin-react-next/?=react next

Might not be necessary for SEO due to Netlify's pre-render service. Might be fun to build anyway though.


Same namespace "visualization" in tree and list

When I try to include "algoplus.h" I get the following:
In file included from include/../classes/tree/avl_tree.h:6,
                 from include/algoplus.h:28,
                 from try.cc:2:
include/../classes/tree/../../visualization/tree_visual/tree_visualization.h:20:13: error: redefinition of ‘void visualization::visualize(std::string&, std::string)’
   20 | inline void visualize(std::string &__generate,
      |             ^~~~~~~~~
In file included from include/../classes/list/circular_linked_list.h:6,
                 from include/algoplus.h:22,
                 from try.cc:2:
include/../classes/list/../../visualization/list_visual/linked_list_visualization.h:20:13: note: ‘void visualization::visualize(std::string&, std::string)’ previously defined here
   20 | inline void visualize(std::string &__generate,

Maybe we change the namespace in both of them to be like: "tree_visualization" and everything is ok.

this is closed as of pr #35


There should be a way to set your emacs.d file in a nix expression

As per the title!

Now we don't have ways to create dotfiles. Only vim has such support, but it differs from what we want as a final result.
And there is a https://github.com/NixOS/nixpkgs/pull/9073.

I'm closing this issue because this subject has come up dozens of times before and there's plenty of other tickets here that address all kinds of aspects revolving around the subject of how to manage your home directory ("dot files") with Nix.


Error on Firmata install using the interchange

I can flash the board with Firmata using the Arduino IDE with no problem, but doesn't work using the interchange:
interchange install git+https://github.com/Makeblock-official/mbot_nodebots -a uno --firmata=usb
Retrieving manifest data from GitHub
Downloading hex file
found uno on port /dev/cu.wchusbserial1420
connected
reset complete.
flashing, please wait...
flash complete.
[Error: Sending 55000b20: receiveData timeout after 400ms]

Conversely, the Bluetooth flash using the interchange works great.

Is the Bluetooth module plugged in when you do it?
On Wed, Mar 2, 2016, 05:08 Linda Nichols<EMAIL_ADDRESS>wrote:

I can flash the board with Firmata using the Arduino IDE with no problem,
but doesn't work using the interchange:
interchange install git+
https://github.com/Makeblock-official/mbot_nodebots -a uno --firmata=usb
Retrieving manifest data from GitHub
Downloading hex file
found uno on port /dev/cu.wchusbserial1420
connected
reset complete.
flashing, please wait...
flash complete.
[Error: Sending 55000b20: receiveData timeout after 400ms]
Conversely, the Bluetooth flash using the interchange works great.
—
Reply to this email directly or view it on GitHub
https://github.com/Makeblock-official/mbot_nodebots/issues/12.

Ah, should it be unplugged for both --firmata=usb and --firmata=bluetooth? I am only doing it for the latter.

In theory the bluetooth module shouldn't be plugged in at all when you're
uploading a new firmware so it avoids conflicts...
On Wed, Mar 2, 2016 at 9:20 AM Linda Nichols<EMAIL_ADDRESS>wrote:

Ah, should it be unplugged for both --firmata=usb and --firmata=bluetooth?
I am only doing it for the latter.
—
Reply to this email directly or view it on GitHub
https://github.com/Makeblock-official/mbot_nodebots/issues/12#issuecomment-190933007
.

That did it for me. Thanks!


Add Klu AI

The best open-source LLMs include a comprehensive platform for developing, deploying, and optimizing generative AI applications. It simplifies working with Large Language Models (LLMs) like GPT-4, Claude 2, and Llama 2 by offering a unified API and SDK.

@ashitaprasad Please assign these use to me

@ashitaprasad Can you please review this.


Fancy Zones swapped on multiple monitors after computer sleep

Microsoft PowerToys version
0.68.1
Installation method
GitHub
Running as admin
Yes
Area(s) with issue?
FancyZones
Steps to reproduce
Fancy Zones swapped on multiple monitors after computer sleep
✔ Expected Behavior
Monitors should remember their assigned fancy zone. My left monitor is portrait, my right monitor is landscape.
❌ Actual Behavior
The assigned fancy zones are reversed on sleep / lock.
Other Software
No response

/dup https://github.com/microsoft/PowerToys/issues/24656


Long Messages are shown cut-off

Iphone 5S, iOS10, NEM-Version 3.0Beta3
If you send long messages, the Bubbles will cut off if you reopen the details of an account.
When you see the cut-off messages and you are sending a new one, than they will be stretched right.
[1. Cut-Off Messages]

[2. New Message]

[3. Now it's normal]

[4. reopen, it's cut-off again]

Espo: NDEFC3-H4VAIU-FQ5GFT-IK3IJR-4DGKF7-PEQKRW-LPZ5

This issue is solved.

Bounty Paid Transaction hash: 689bb47af0dd86a9662ecc8ba1999c0feecdbddca38533f2216121a19894ab65


fix(text-field): input not rendered on SSR

The Input component isn't being rendered on the first render (thus, not rendering on SSR) which can cause some issues for SEO and usability, such as the user being unable to type in the form while the JS hasn't run yet.
The markup I'm getting on my SSR with the latest version is

  Username

And with the changes on this PR

  <input type="text" value="" class="mdc-text-field__input" name="username" id=""/>
  Username

And the reason for that is because the TextField component actually controls whether or not the Input will be rendered, which depends on the foundation being initialized.

I'll try to fix the tests tomorrow

hey @moog16, sorry not explaining the bug I've experienced. I've updated the PR description!

I need some help to fix the other tests, I don't know why they are failing

@lucasecdb which tests specifically are you running into issues with? Are they the ones on travis?

@moog16 yeah, those ones.

Codecov Report

Merging #721 into rc0.11.0 will decrease coverage by <.01%.
The diff coverage is 83.33%.

@@             Coverage Diff             @@
##           rc0.11.0    #721      +/-   ##
===========================================
- Coverage      94.6%   94.6%   -0.01%
===========================================
  Files            73      73
  Lines          2928    2927       -1
  Branches        448     447       -1
===========================================
- Hits           2770    2769       -1
  Misses           56      56
  Partials        102     102

Impacted Files
Coverage Δ

packages/text-field/index.tsx
97.54% <ø> (-0.02%)
:arrow_down:

packages/text-field/Input.tsx
96.72% <83.33%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@moog16 I've fixed the tests, but the screenshot isn't passing

@lucasecdb looksl ike screenshots are failing

@moog16 I don't know how the screenshot works, but maybe the component isn't being fully rendered (i.e. the didMount isn't being called)?

@lucasecdb I looked at the 2 different screenshots...this is the golden. The ones that are failing look like the validation styles aren't appearing quick enough.
Locally they are passing, which leads me to think that the ones on travis are too slow.

@moog16 so, I need to increase the screenshot timeout?

@lucasecdb I'm seeing if changing networkidle2 --> networkidle0 will work. Can you try changing that in test/screeshot/screenshot.tsx?

sure!

actually try changing it to load...I think load comes last. https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md
I'm reading this for reference...not sure who is right.

in this screenshot tester they say to wait until the networkidle0, we could wait to see if that passes before trying the load, what do you think?

@lucasecdb looks like all of the options fail locally. I think the foundation check ensured that the input was fully rendered before the networkidlex event occurred. We might need to update the screenshot tests. Are you on Discord? This might be easier to fix there

yes, I am!

Talked offline and will push this off for either a patch / next release. Need to fix how we determine when a page is loaded w/ screenshot tests.

@lucasecdb have you thought about this one at all? I wanna try getting this into 12.0

@moog16 not yet, I'll try to have a look on it later today

can someone help us on this?

You mean do I have other React resources to help fix the tests? I'm actually the only one on the team that works with React, haha. I'll have to revisit once I get select working.

ohh, okayy. it's just that I don't know how to tackle this, tbh, but I didn't wanted to leave this out for 0.12 (which releases next week, right?)

Correct, but I actually wanted to get the updated MDC Web v1 components in 12 as well. So I was thinking I would push it off until we get select and text field into the mdcweb update branch.

@moog16 I just checked this again, and the input on v0.12 is rendering on SSR!! I think we can close this without any problems

That's great! How did it all of a sudden start working? I didn't even realize, but @TroyTae removed the foundation ? ternary. I wonder why we didn't run into the same testing issues.

yeah, that's strange, but I'm glad it's fine :-)


[Bug]: "Could not read username for https://github.com/username/repository.git"

Describe the bug
After installing the plugin and initializing the local repo (.git files/folder), neither pushing nor pulling works and gives this error instead:
Relevant errors (if available)
Could not read username for https://github.com/username/repository.git

Steps to reproduce
Install Obsidian via Flatpak (I'm on Pop!_OS, the "Pop-Shop" seems to just be a flathub skin?)
Install the Plugin
Turn Vault Folder into local Git Repository using GitHub Desktop
Expected Behavior
I did the same stuff on my Windows Desktop and had no problems. It should just work.
Addition context
After two days, many hours of trying different things I found this simple fix:
Operating system
Linux
Plugin version
2.10.2

Uninstall the Flathub Version of Obsidian (applies to Pop!_OS "Pop-Shop" too) and install Obsidian from the AppImage instead (see: https://codeburst.io/how-to-install-and-run-appimage-on-linux-systems-f031ec6a85ce).
As a newbie, I struggled with this for the better part of two days, many hours. I hope this can help someone.


Use the getOwner API to get the owner reference.

I suspect that this PR will resolve this canary failure.

Note: this will make the addon compatible out of the box with only Ember 2.3 and up. It will require installation of ember-getowner-polyfill for older applications.
It is also pretty reasonable to drop support for pre 2.4-lts versions of Ember, making this a non-issue.


Bypassed zone shows as clear

Hi,
Envisalink 3 with a dsc panel.
I bypassed a zone with the integration then armed away.
The zone is showing as clear, not bypassed on the integration while it correctly shows a bypass in the envisalink app.
Is this a known issue?
Even reloading doesn't fix the status.
Thanks

The zone binary_sensors reflect whether a zone is open or closed.  The zone bypass switches reflect whether a zone is bypassed or not.  They are not combined as a single sensor because they are indicating different things.  E.g., a zone can be bypassed and open or bypassed and closed.
Someone here posted an example where they use a mushroom template card to combine zone state and bypass state using different colours which might be something along the lines of what you're looking for.

Hi,
Sorry I didn't explain well my issue.
The zone bypass switch shows the zone as not bypassed, however it isbypassed, and indeed the envisalink app shows is correctly as bypassed.
To bypass it initialky, I used your integration. But once done, the status is not reported correctly afterwards. In practical the integration is showing me all the zones as not bypassed, while one is in reality bypassed.
In the  screenshot here below, this zone is bypassed but it doesn't show it.
I hope it makes more sense.

Ah, okay.  I just tried on my system and it seems to work.  Can you enable debug logging for envisalink_new and post the logs?  If you could turn on the debug logging and then restart HA and once it's come up, try and bypass a zone using the bypass switch a few times.  That should hopefully provide enough info to figure out what's going on.

@doppiaemme I haven't heard anything back from you for several months.  If this is still an issue, feel free to re-open and provide the requested logs.


Incorrect behaviour with component mat-icon which includes a translation for the value of its attribute/property/directive

Bug report
Describe the bug
It looks similar to the issue https://github.com/svoboda-rabstvo/ngx-translate-lint/issues/92
But the current problem has another set.
Linter works incorrectly with <mat-icon>  if it has a translation for its attribute/property/directive value.
<EMAIL_ADDRESS>is used.
<EMAIL_ADDRESS>doesn't have the described problem.
To Reproduce
Steps to reproduce the behavior:

Use <mat-icon [matTooltip]="'general.buttons.back' | translate">keyboard_arrow_left</mat-icon> on the view (or something like this: <mat-icon [attr.aria-label]="'general.buttons.back' | translate">keyboard_arrow_left</mat-icon>).
Run npx ngx-translate-lint -p <view_path> -l <keys_file_path>
See error: Key: 'keyboard_arrow_left' doesn't exist in '<...>.json'

Expected behavior
Ignore a string inside <mat-icon>

:tada: This issue has been resolved in version 1.16.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Skip build-and-test hooks for markdown commits

Changelists that only affect markdown files shouldn't affect the result
of any builds or tests: skip build-and-test actions on commits that only
touch markdown files.
This should vastly reduce the time it takes to merge documentation PRs
into main, and it will also avoid wasting compute running tests on no-op
commits.
This change was inspired by tests running for 30 minutes on the
markdown-only change https://github.com/3rdparty/eventuals/pull/165
which both delayed submission and wasted compute resources.

Looks like you still have a merge commit in here? Are you testing our new
settings? 😜
On Thu Dec 23, 2021, 10:27 PM GMT, Alex McCarthy @.***>
wrote:
@CodingCanuck https://github.com/CodingCanuck requested your review on:
#168 https://github.com/3rdparty/eventuals/pull/168 Skip build-and-test
hooks for markdown commits.
—
Reply to this email directly, view it on GitHub
https://github.com/3rdparty/eventuals/pull/168#event-5811740871, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAGHXYHVDTSMQIN7R6V4J3USOO33ANCNFSM5KVTARWA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because your review was requested.Message ID:
@.***>

Looks like you still have a merge commit in here? Are you testing our new settings? 😜

Evidently :P plz help. (I'm struggling with creating branches, pushing / pulling, and creating PRs, all while minimizing mess: researching + writing this change took me 5 min, and I probably spend 30 minutes trying to figure out how to structure and mail the PR. The next time I encounter anything non-trivial in this process while someone's on Gather I'll definitely reach out for some hand holding!)
I did the following: I think step 6 was likely a mistake (though I don't know of a better alternative), steps 9 + 10 were almost certainly mistakes, and I have no idea if step 13 was a mistake, or GitHub WIP, or GitHub doing the bad thing that we're trying to prevent.

Make a branch ( git checkout -b my-branch ): nice
Update yml files ( git add -p .github ): nice
Make a commit ( git commit ): nice
Pushed the commit ( git push ): nice, though I honestly don't have a great mental model of how this relates to PRs
Started to create a pr ( gh pr create ) but did not finished (opened in browser but abandoned, because I...
Decided to add a sentence to the commit message ( git commit --amend ): uh maybe nice? Seemed to work without errors
Re-push the commit ( git push ): oh jeez

To https://github.com/3rdparty/eventuals.git
 ! [rejected]        alexmc.skip-builds-for-markdown-commits -> alexmc.skip-builds-for-markdown-commits (non-fast-forward)
error: failed to push some refs to 'https://github.com/3rdparty/eventuals.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

oh noes: ok let's git pull: that added a merge commit :/ ok, let's Software Engineering this (i.e. search on stack overflow): https://stackoverflow.com/questions/51447580/git-pull-created-merge-commit-that-is-not-needed
(I ran a bunch of other commands in repeated failed attempts to get this to work, so steps from here on out are untrustworthy) git pull --rebase oh noes, that got me back to 4) where I'm back to the old / wrong commit message
uh https://stackoverflow.com/questions/3968281/git-pushing-amended-commits says git push --force will make the push succeed and what could go wrong with an arg like --force. My thinking: this comment "I'd qualify the "don't use amend" option: don't use it on published work. On unpublished work (local/personal branches) you should absolutely use it. (And if you have more than one personal repo, that does mean you'll use push --force to transfer your work around sometimes. That's fine.)" made me think that this push was ok because while I'd already pushed it, I hadn't (finished) creating a PR yet, and I didn't expect that anyone else should be using the dev branch I created for this change
Create PR: gh pr create: nice
Send pr: click button: nice
GitHub says something like (can't remember exact phrasing): "this change is behind main, click merge (github button) to merge with head": click button: nice
See that clicking said github button added a merge change to the commit chain :/ assume that github buttons are safe and that this will all get auto-squashed on submit? Maybe?

TL;DR the merge commit is gone.
Great news: @FolMing is a hero and he helped me both repair this commit chain as well as understand how I created this mess (it was step 4 + 8-10)!
The sequence I of things did (but should not do) that caused caused this:

Amend a commit (~fine)
Pull, which triggered a merge of my local branch change with the remote branch change

What I should do instead:

Amend a commit
git push --force to allow the remote branch to switch to an ~unrelated history of commits to match my local branch

Looks like you still have a merge commit in here? Are you testing our new settings? 😜

Evidently :P plz help. (I'm struggling with creating branches, pushing / pulling, and creating PRs, all while minimizing mess: researching + writing this change took me 5 min, and I probably spend 30 minutes trying to figure out how to structure and mail the PR. The next time I encounter anything non-trivial in this process while someone's on Gather I'll definitely reach out for some hand holding!)
I did the following: I think step 6 was likely a mistake (though I don't know of a better alternative), steps 9 + 10 were almost certainly mistakes, and I have no idea if step 13 was a mistake, or GitHub WIP, or GitHub doing the bad thing that we're trying to prevent.

Make a branch ( git checkout -b my-branch ): nice
Update yml files ( git add -p .github ): nice
Make a commit ( git commit ): nice
Pushed the commit ( git push ): nice, though I honestly don't have a great mental model of how this relates to PRs
Started to create a pr ( gh pr create ) but did not finished (opened in browser but abandoned, because I...
Decided to add a sentence to the commit message ( git commit --amend ): uh maybe nice? Seemed to work without errors
Re-push the commit ( git push ): oh jeez

To https://github.com/3rdparty/eventuals.git
 ! [rejected]        alexmc.skip-builds-for-markdown-commits -> alexmc.skip-builds-for-markdown-commits (non-fast-forward)
error: failed to push some refs to 'https://github.com/3rdparty/eventuals.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

oh noes: ok let's git pull: that added a merge commit :/ ok, let's Software Engineering this (i.e. search on stack overflow): https://stackoverflow.com/questions/51447580/git-pull-created-merge-commit-that-is-not-needed
(I ran a bunch of other commands in repeated failed attempts to get this to work, so steps from here on out are untrustworthy) git pull --rebase oh noes, that got me back to 4) where I'm back to the old / wrong commit message
uh https://stackoverflow.com/questions/3968281/git-pushing-amended-commits says git push --force will make the push succeed and what could go wrong with an arg like --force. My thinking: this comment "I'd qualify the "don't use amend" option: don't use it on published work. On unpublished work (local/personal branches) you should absolutely use it. (And if you have more than one personal repo, that does mean you'll use push --force to transfer your work around sometimes. That's fine.)" made me think that this push was ok because while I'd already pushed it, I hadn't (finished) creating a PR yet, and I didn't expect that anyone else should be using the dev branch I created for this change
Create PR: gh pr create: nice
Send pr: click button: nice
GitHub says something like (can't remember exact phrasing): "this change is behind main, click merge (github button) to merge with head": click button: nice
See that clicking said github button added a merge change to the commit chain :/ assume that github buttons are safe and that this will all get auto-squashed on submit? Maybe?

BTW, just so we could see it in action: can you make a checkout from this branch and commit a change to .md file? Just want to see if it does actually ignore such commits!

BTW, just so we could see it in action: can you make a checkout from this branch and commit a change to .md file? Just want to see if it does actually ignore such commits!

Done: https://github.com/3rdparty/eventuals/pull/170 and if I'm reading the check log correctly, it does seem like this change is successful in disabling these checks for commits that exclusively contain .md files:
I also made a non-md / code change that's based on this branch, and that one ran the expected build-and-test check:

So it looks like this works as intended, disabling these checks for md-only changes but keeping them for code changes.

Copying my comment in here from #170 so that everything stays in one place:
Can we do the same for our code style check? I don't think we need to run it since we don't change our code, right?

Copying my comment in here from #170 so that everything stays in one place:
Can we do the same for our code style check? I don't think we need to run it since we don't change our code, right?

Good question: does code style only apply to non-markdown files, and do we anticipate it remaining that way going forward? (Do we envision applying style rules or automated formatting to markdown files in the future? A quick googling makes me think that clang-format does not handle markdown https://clang.llvm.org/docs/ClangFormatStyleOptions.html and I don't see an obvious / ubiquitous markdown autoformatter tool)
If we think that we'll never have code style checks for markdown styles then disabling code style checks for them seems like a strict win. If we think we might add them later, disabling them now might cause confusion if/when some future coder tries to add markdown style rules, but I don't know how likely or important that is (probably not very).

Shoot! It auto-merged after my approval, haha! Anyway, I think it's good enough as it currently is and if we want to do the same for code style check we can open up a new PR.


[Feature] Check valid nova-cloud-controller configuration scheduler-default-filters

Based on the charm source code here, the charm uses the scheduler-default-filters configuration value to set the enabled_filters in /etc/nova/nova.conf.
However, some of these filters have been deprecated, as shown here. If any deprecated filters are included in the Nova configuration, the nova-scheduler service will fail to start.
I recommend that the COU (Charmed OpenStack Users) check if the configuration is valid or we should contribute to the charm by implementing validation for this configuration.

Ah I saw this issue a little too late... I opened a duplicate, and will close it. But I'll save what I wrote here for reference:

The filter option AvailabilityZoneFilter was removed at some point, in Bobcat according to charm-nova-cloud-controller.
This means that if we have a scenario where schedule-default-filters has been set on nova-cloud-controller to a value that includes  AvailabilityZoneFilter, and we upgrade from antelope to bobcat, then nova-scheduler will crash with the following message in /var/log/nova/nova-scheduler.log:
2024-10-01 10:42:10.920 724488 CRITICAL nova [None req-4a4d2a3f-bd36-434b-a228-11e3e236d034 - - - - - -] Unhandled error: nova.exception.SchedulerHostFilterNotFound: Scheduler Host Filter AvailabilityZoneFilter could not be found.
2024-10-01 10:42:10.920 724488 ERROR nova Traceback (most recent call last):
2024-10-01 10:42:10.920 724488 ERROR nova   File "/usr/bin/nova-scheduler", line 10, in <module>
2024-10-01 10:42:10.920 724488 ERROR nova     sys.exit(main())
2024-10-01 10:42:10.920 724488 ERROR nova   File "/usr/lib/python3/dist-packages/nova/cmd/scheduler.py", line 47, in main
2024-10-01 10:42:10.920 724488 ERROR nova     server = service.Service.create(
2024-10-01 10:42:10.920 724488 ERROR nova   File "/usr/lib/python3/dist-packages/nova/service.py", line 252, in create
2024-10-01 10:42:10.920 724488 ERROR nova     service_obj = cls(host, binary, topic, manager,
2024-10-01 10:42:10.920 724488 ERROR nova   File "/usr/lib/python3/dist-packages/nova/service.py", line 116, in __init__
2024-10-01 10:42:10.920 724488 ERROR nova     self.manager = manager_class(host=self.host, *args, **kwargs)
2024-10-01 10:42:10.920 724488 ERROR nova   File "/usr/lib/python3/dist-packages/nova/scheduler/manager.py", line 68, in __init__
2024-10-01 10:42:10.920 724488 ERROR nova     self.host_manager = host_manager.HostManager()
2024-10-01 10:42:10.920 724488 ERROR nova   File "/usr/lib/python3/dist-packages/nova/scheduler/host_manager.py", line 356, in __init__
2024-10-01 10:42:10.920 724488 ERROR nova     self.enabled_filters = self._choose_host_filters(self._load_filters())
2024-10-01 10:42:10.920 724488 ERROR nova   File "/usr/lib/python3/dist-packages/nova/scheduler/host_manager.py", line 496, in _choose_host_filters
2024-10-01 10:42:10.920 724488 ERROR nova     raise exception.SchedulerHostFilterNotFound(filter_name=msg)
2024-10-01 10:42:10.920 724488 ERROR nova nova.exception.SchedulerHostFilterNotFound: Scheduler Host Filter AvailabilityZoneFilter could not be found.

This is not an ideal user experience. COU can improve the user experience for this scenario - some ideas:

COU could print an error as part of the verification checks when generating a plan (when run on an antelope cloud, if AvailabilityZoneFilter is included in the list)
COU could automatically adjust the configuration of nova-cloud-controller if it detects this scenario

I will vote for raise an error on verification part and provide step how to change it.


Hardware stack limiter for CM33

@wes @kasjer
I also opt for having it always enabled
and I'm fine with storing stack bottom in os_task, not sure if we need stack top, bottom and size stored at the same time but as far as I see there is code in e.g. mcumgr which unfortunately accesses os_task struct directly (which I don't like, this should be done via API) so perhaps it's better to just add stack bottom as some things may break if we remove stack top. do you have any strong opinion on this?
will also add comment to make sure no one moves these members in future

@andrzej-kaczmarek I would simply add stack bottom if you ask me. I guess I was thinking making this "configurable" because stack bottom would really only be used by the M33 and as you said we store all those things. I cannot imagine folks getting upset about adding 4 bytes though. So my vote would be to always have it, no config, add stack bottom and put that comment about not moving stuff around.

I don't like adding another pointer to stack for the purpose of this feature only. To me this lgtm as is.

@mkiiskila You would rather sacrifice that extra time every context switch for 4 bytes? I definitely would not.

updated as per discussion on dev

build will fail until https://github.com/apache/mynewt-mcumgr/pull/52 is merged