David Edler

Results 42 comments of David Edler

This should be solved in discourse parser, not in this project. There is an open issue over there, see https://github.com/canonical/canonicalwebteam.discourse/issues/105

Thanks for the review @ru-fu ! Changed the line below header to span full width and signed the commit. The Doc version part should adjust as soon as there is...

![step0](https://user-images.githubusercontent.com/1155472/196676567-6aae5479-8765-422d-89bf-b7b625bc0c7d.png) ![step1](https://user-images.githubusercontent.com/1155472/196676560-a44e0357-5a3e-4255-99e2-56f346efe434.png) ![step2](https://user-images.githubusercontent.com/1155472/196676556-f7fc5c14-814d-4143-a0e2-16f048904caa.png) ![step3](https://user-images.githubusercontent.com/1155472/196676553-ac68ecfb-69c7-40ed-99f1-11014760844d.png) ![step4](https://user-images.githubusercontent.com/1155472/196676542-d5ac33f3-46d3-44b0-8c27-1f7e2f99145d.png) Some screenshots of the prototype above. Currently, just a gray box filled with a green bar. A state variable with the current percentage (number from...

Display size (with attachments) per mail and sort mails by size would be super useful!

> Does the workaround with `rollup/wasm-node` work? We need it in combination with vite 5.0 -- which uses rollup 4. It seems to work with `rollup/wasm-node` on s390x at first,...

> Please have a look at CI, unfortunately it does not work yet. Fixed the lint error, though no clue yet how to fix the [build error](https://github.com/rollup/rollup/actions/runs/7568759831/job/20663909080?pr=5346).

> Normally, cargo should be able to use the proper cross-linker. You need to set the environment variable > > ``` > CARGO_TARGET_S390X_UNKNOWN_LINUX_GNU_LINKER=s390x-linux-gnu-gcc > ``` Thanks for the suggestion, I...

> > This CI run actually looked quite good! Now the only missing thing is `s390x-unknown-linux-gnu-strip: command not found`. Of course we can live without stripping debug symbols for the...

I can't reproduce the situation with an orphaned image volume any more. Unfortunately, I removed the storage pool from the issue description, so failing to reproduce the situation right now....