Jonas Finnemann Jensen

> any other project specific directory symlinks that are not meant to be published This I'm sold we should allow.. I thought we did fix that, or did we never...

@2ZeroSix > disallow directory symlinks and only land a fix for ignored symlinks This seems like a no-brainer. We're just correctly ignoring symlinks. I see how allowing _non-cyclic directory symlinks_...

I enabled coveralls.io for this repository. We can add the following badge to the README too. Though it's not much fun until we've figured out how to get coverage numbers...

Weird, that the tests seem to fail: ``` 🎉 1433 tests passed. Error: Process completed with exit code 1. ``` Do they also fail locally when running with `--coverage`? Like...

> --platform chrome gives me a timeout error everytime. All tests passed in flutter test --coverage : But it works on Github Actions. This might be windows specific, it might...

Yeah, let's close this. I don't think we'll get much improvement by collecting coverage from iphone and android emulators, maybe a little, but I'm guessing not much. We can explore...

I have plans to upgrade boringssl, but haven't had the time. Last I tried it turned out that the python script had changed a lot. So we'll need to change...

> What do you think about using gith hub action workflow for making the rolling process automatic? I don't mind, but let's get the rolling process working first :D

Absolutely, do a PR. I'm hoping you made a script for rolling the source code in. Because it's pretty hard to actually review all the code. So maybe we can...

Let's do this in two PRs. (1) PR that lands a script for rolling a BoringSSL update. (2) PR that actually does the change. In practice, we probably need to...