3 ms·
I am very excited to see if this helps. I use GitHub Actions constantly for very large builds with very large logs and I find their log browser infuriatingly us
by saurik 6y ago
I am very excited to see if this helps. I use GitHub Actions constantly for very large builds with very large logs and I find their log browser infuriatingly useless... like: actively harmful :(. It punished me so much and so often and so consistently for having the gall to think that logs would be useful that I finally became demoralized and gave up trying to use their interface: I just wait until the builds complete (as they sadly refuse to do this during a build) and ask for the "raw log" so I can get the experience they seem to believe I couldn't possibly want: a ridiculously long text file downloaded into my browser, which allows me to use built-in browser features to scroll through and search it :(. I will, I guess, cautiously try to venture into using the logs again to see if they managed to fix things.
- napsterbr 6y agoI'm with you. The usability behind Actions is terrible, in every possible way. At least when compared to what I used before (Jenkins).
- IshKebab 6y agoWow you must be the only person in the world that things Jenkins is more usable than Github Actions!
- ec109685 6y agoWhat is strange about this is VSCode which Microsoft owns has no problem with 50kb files. Surprised they just don’t go with its text editor. Even more sad, vim 20 years ago could handle these files with ease, and here we are where 20kb causes the browser to choke.
- Varriount 6y agoNot too long ago had to search through a truly gigantic file (I believe it contained JSON logs?). Sublime Text slowed to a crawl and froze when attempting to open it, and I didn't even bother with VS Code. On a hunch, I tried opening it in Notepad - and it loaded quite quickly!
- Spqa 6y agoSublime and VS code might try to parse it for syntax highlighting, notepad simply read the text.
- IshKebab 6y agoVSCode disables syntax highlighting on very large files.
- scaladev 6y agovim does this too. If it hangs on you when opening a very large file, don't hesitate to press Ctrl+C. It does not terminate the whole process, but aborts the syntax highlighting, and the editor becomes very snappy.
- suprfsat 6y agoTo proactively turn off syntax highlighting, bracket matching, and so forth, I use alias vi='vim -u NONE' which makes it skip vimrc.
- deleted 6y ago[deleted]