Configure automated testing #3

Open
opened 2023-10-17 18:32:40 -04:00 by sundog · 11 comments
Owner

We should run automated tests when a PR is opened.

We should run automated tests when a PR is opened.
sundog added the
help wanted
label 2023-10-17 18:32:40 -04:00
Collaborator

Might be because I don't have write permissions, but put me in for this one

Might be because I don't have write permissions, but put me in for this one
vulfox was assigned by sundog 2023-10-18 15:08:14 -04:00
Author
Owner

Gladly - thanks!

Gladly - thanks!
Collaborator

i had pinged @vulfox on matrix; i may also take a stab at this thursday night

i had pinged @vulfox on matrix; i may also take a stab at this thursday night
Collaborator

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.

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.
Collaborator

if a maintainer provides me with a runner token, i can register a gitea actions runner for this

if a maintainer provides me with a runner token, i can register a gitea actions runner for this
Collaborator

may first need to enable actions at the instance or organization level (or in the instance configfile).

may first need to enable actions at the instance or organization level (or in the instance configfile).
cascode self-assigned this 2023-10-21 15:28:24 -04:00
Collaborator

@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

@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
cascode added reference automated-testing 2023-10-21 16:26:35 -04:00
Collaborator

@ajr @sundog bump re: previous note about nginx upload limit

@ajr @sundog bump re: previous note about nginx upload limit
Author
Owner

@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.

> @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.
Collaborator

huh, oddly that did not resolve it

huh, oddly that did not resolve it
Collaborator

still seeing the same nginx 413

still seeing the same nginx 413
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: MountainTownTechnology/aural_isle#3
No description provided.