Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency updates, required for ARM #11

Closed
wants to merge 9 commits into from
Closed

Dependency updates, required for ARM #11

wants to merge 9 commits into from

Conversation

rajkowski
Copy link
Contributor

Please review these updates, they were required to build for Mac M1 and run in Docker. There are other issues with libxml but hopefully those can be resolved.

@@ -61,7 +61,7 @@ services:
- API_KEY=${PLAYER_KEY}
- API_SECRET=${PLAYER_SECRET}
rdbms:
image: mysql:8.0.17
image: mysql/mysql-server:8.0.26
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We specifically avoided the most up to date version of mySQL because of an issue we saw with the server falling over. I'll see if I can dig up more information on that, but I'd hold off on merging this until that is determined to have been fixed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the bug https://bugs.mysql.com/bug.php?id=103225 that we ran into. Unfortunately they have it marked as Won't Fix but there seem to be a number of people still running into it. It seems like they plan to fix it, but just not where it will be reported outside of the manual.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, good to know. I see that at https://bugs.mysql.com/bug.php?id=103465 too. There is a note to either increase or decrease sort_buffer_size and innodb_sort_buffer_size however that's not great either.

@@ -24,7 +24,7 @@
"@hapi/jwt": "^2.0.1",
"@hapi/vision": "^6.1.0",
"@hapi/wreck": "^17.1.0",
"bcrypt": "^5.0.1",
"bcrypt": "5.0.0",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This effectively locks the version for all users to satisfy one set of users and could lead to security issues in the future. I don't know that there is a better way to handle this, but locking an older version for that reason doesn't seem desirable, in theory it should be fixed up stream. Has there been an issue opened there?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Brian, thanks or reviewing these changes. It's possible that the other M1 pull request fixes this by building from source on the fly.... there are details in kelektiv/node.bcrypt.js#868 which suggest that, but also looking at bcryptjs. I'm going to give the other M1 pull request some review and hopefully the x86 platform suggestion can be avoided.

@rajkowski
Copy link
Contributor Author

Dependencies have been updated to match improvements for ARM

@rajkowski rajkowski changed the title Some updates for Mac M1 Dependency updates, required for ARM Nov 15, 2022
@rajkowski rajkowski marked this pull request as ready for review November 15, 2022 19:21
@rajkowski rajkowski closed this by deleting the head repository Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants