Glauber Costa

@espindola any comments on the backtrace format and / or how hard it would be to show more of the user code instead of deno internals ?

Thinking more about this, for node-mode imports (which is what we expect our users to use), that go through esbuild, won't we lose all this information ?

Reference, if useful https://esbuild.github.io/api/#sourcemap

the reason we parse strings is that we want combinations of columns, and not columns, to be unique. Field names have to be unique within a model, but not globally...

That depends on the failure. If it is a network failure we should keep the last version (impossible with files, essentially). If the payload is bad, then it should vanish...

you mean chiseld not even starting? I can't see why. we should just not have a secret at that point.

chisel_secret_key_location is only read once, and it is fair to assume we'll need to restart the process if the key location fails. So it is fine to fail at that...

`build` should arguably fail if required fields are not present (it doesn't, right now). I would like us to fix this, because it is part of "making this typescript". However,...

Not sure this is a bug, @honzasp . As far as I understand, node wouldn't be able to import those modules with that syntax, so we shouldn't expect to be...

This was the bug: https://github.com/docker/for-linux/issues/1374 Someone with a Linux box should be able to easily reproduce this by removing the ::1 entry. I am wondering if we can't default to...