Guillaume Giudicelli
Guillaume Giudicelli
since we are only doing a (=0) + b for insertion then (a+b) - b for retrieval I think we are guaranteed that at exactly 0 we will never have...
but we can just error then. And then whoever wants that will have to offset their mesh by (1, 1, 1) to make it work.
I think I have a lead on setting a dimension on the map. I think it s possible now, thanks to the struct around the map
@roystgnr I worked around the issue. See the commit message for the explanation on the design
wouhou! Thanks for the careful reviews @roystgnr and thanks for the excellent work @fdkong !! It was a pleasure building on it
Another similar issue is that MooseDocs introduces a space on both sides of numbers so instead of WCNSFV2Pblabla we have WCNSFV 2 Pblabla
the fix would likely be in moosedocs/extensions/content.py lemme see if I can find it while compiling griffin with a jamf-handicapped machine
ok for my issue (numbers) I have a fix for special characters, I think we need to create a new token, just like "Word" and "Number". Maybe it should be...
Fixed the numbers issues in #27453
Probably just a network error causing the test harness to crash after. It seems invalidating it fixed it