-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Incompatibility with Reach Entity Attributes #13
Comments
Seems to be an incompatibilty with reach-entity-attributes. Did it work without crashing since your last crash report once? I haven't touched |
Also have you already tried updating reach-entity-attributes? I saw you use v1.0.2 but at least v2.0.0 is out already |
Can you try if this works? |
no, last report immediately followed by this |
Have you tried that? I can't really test it myself atm |
crash-2021-03-12_15.00.45-server.txt |
Next try: This should in theory work, at least it did in my tests with reach-entity-attributes v1.0.1, I would just like a confirmation before I close the issue. |
confirmed working(at least the client booted up). One thing notable is that REA 2.0 is only available for 1.17. thnakx a lot |
Still an issue in 1.19 |
Happy to grab a log if need be, you can reproduce it by installing origins which uses REA causing a conflict with RUG |
I think, I already know the cause, but since I am on vacation now I will have to find a better wifi connection somewhere before I can work on it |
@Mattabase can you please try this pre-release? When it works I can make it stable |
Quick test and looks to have stopped the crash but the reach rule in Rug seems to not be applying Doing more testing with a smaller instance, this was being done in my large test instance. |
Cool thanks for the crash fix |
three individual crash reports all in one go:
crash-2021-03-11_03.00.19-server.txt
crash-2021-03-11_03.00.23-server.txt
crash-2021-03-11_03.00.24-client.txt
The text was updated successfully, but these errors were encountered: