Configure automated testing #3
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We should run automated tests when a PR is opened.
Might be because I don't have write permissions, but put me in for this one
Gladly - thanks!
i had pinged @vulfox on matrix; i may also take a stab at this thursday night
We should probably also incorporate #6 as well. This way even if someone doesn't use a formatter in one of our soon to be recommended ways, the code all still ends up with the same style.
if a maintainer provides me with a runner token, i can register a gitea actions runner for this
may first need to enable actions at the instance or organization level (or in the instance configfile).
@sundog could you increase the maximum upload size in nginx? when i push docker images, the largest layer fails and i'm getting:
error parsing HTTP 413 response body: invalid character '<' looking for beginning of value: "<html>\r\n<head><title>413 Request Entity Too Large</title><script type=\"text/javascript\" src=\"/ynh_portal.js\"></script><link type=\"text/css\" rel=\"stylesheet\" href=\"/ynh_overlay.css\"><script type=\"text/javascript\" src=\"/ynhtheme/custom_portal.js\"></script><link type=\"text/css\" rel=\"stylesheet\" href=\"/ynhtheme/custom_overlay.css\"></head>\r\n<body>\r\n<center><h1>413 Request Entity Too Large</h1></center>\r\n<hr><center>nginx</center>\r\n</body>\r\n</html>\r\n"
it looks like all the official rust docker images include a layer that's around 700MB or larger, so would be great if you could bump the nginx upload limit to 800MB or a gig or something
@ajr @sundog bump re: previous note about nginx upload limit
I added
client_max_body_size 1024M;
to the base http block in/etc/nginx/nginx.conf
and reloaded nginx - let me know if that didn't resolve the issue.huh, oddly that did not resolve it
still seeing the same nginx 413