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

Disconnect when clicking "craft" on item in terminal. #1222

Closed
halvors opened this issue Apr 6, 2015 · 7 comments
Closed

Disconnect when clicking "craft" on item in terminal. #1222

halvors opened this issue Apr 6, 2015 · 7 comments
Labels
bug Self explanatory?

Comments

@halvors
Copy link

halvors commented Apr 6, 2015

This happends when i click the "craft" on an item in the terminal. Seems to be a NPE in AE2 netty channel.

Here is the log: http://pastebin.com/JVxvwThK

@zeryl
Copy link

zeryl commented Apr 6, 2015

I am experiencing the same. Using DW20 1.2.1, updated AE2 to beta 26, any crafting recipe is an instant disconnect for the client.

@yueh
Copy link
Member

yueh commented Apr 6, 2015

It would be helpful, if people would describe how it happens and not let us guess for hours about an edge case.

@yueh yueh added the bug Self explanatory? label Apr 6, 2015
@halvors
Copy link
Author

halvors commented Apr 6, 2015

@yueh Well. Thought i already did that. When i click on a "craft" item (Also try to start a new crafting job) the server disconnects you and i see a stacktrace in the server console as attached to ths issue.

@yueh
Copy link
Member

yueh commented Apr 7, 2015

Sadly it is a mostly generic stacktrace and not containing any hint about how it was called. Basically anything opening a GUI would produce the same one.

It is similar to say "one of the 123 buttons does not work, go find it by yourself". Not even thinking that other mods are also using our internal code and could potentially cause it.

@yueh yueh closed this as completed in #1228 Apr 7, 2015
@halvors
Copy link
Author

halvors commented Apr 7, 2015

@yueh Is this fixed or just closed? It is kinda hard for me to provide information that are now shown. That is the only stacktrace that i was getting. I'm sorry about that.

@yueh
Copy link
Member

yueh commented Apr 7, 2015

The more precise your are with your description, the faster we can solve it.

For example include in which GUI it happened. A crafting terminal? Wireless access terminal etc?
Basically any piece of information you can provide to reproduce it. A crashlog just shows what went wrong, but normally does not include how you can reproduce it.

Fixed for the next build, it was automatically closed through the PR.

@halvors
Copy link
Author

halvors commented Apr 7, 2015

Ok thanks :-) But I did actually say that it happed in an ME Terminal. :-)

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Self explanatory?
Projects
None yet
Development

No branches or pull requests

3 participants