-QA Testing-
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 1 2017
-QA Testing-
Oh,
did not consider the fact it only happens on replacing CW to CCW and CCW to CW rotators.
CW to CW and CCW to CCW seem to be fine.
Oct 8 2017
its on my Ubuntu install. German localization.
and the server.cfg looks like this too.
Oct 2 2017
Aug 14 2017
there is any update on this bug ?
Jul 20 2017
Jul 17 2017
-QA Testing-
Jul 13 2017
-QA Testing-
-QA Testing-
Yeah, this is the result of cleaning stuff up a bit more. Other stuff has to be adapted for it
-QA Testing-
this will be fixed in the next update ?
Jul 12 2017
Definitely needs a fallback or an easy way to toggle it.
Jul 11 2017
-QA Testing-
Jul 7 2017
Jul 6 2017
-QA Testing-
-QA Testing-
might be a language thing
Jul 5 2017
-QA Testing-
Jun 30 2017
-QA Testing-
-QA Testing-
Jun 29 2017
-QA Testing-
-QA Testing-
Jun 27 2017
[SERVER] ListenerId[0] connection registered (TRunning: 0/2/0) 22 [SERVER][PROCESSOR] client setup completed for PID: 22. listening for input [CLIENT] Admin parameter 0: SELECT COUNT(ID) FROM ENTITIES WHERE UPPER(name) LIKE UPPER('%MINING%') ; [ADMIN COMMAND] SQL_QUERY from org.schema.schine.network.server.AdminRemoteClient@60070e6c params: [SELECT COUNT(ID) FROM ENTITIES WHERE UPPER(name) LIKE UPPER('%MINING%') ;] [SERVER] client has not send any login information: 2000 / 10000 ms; ProcessorID: 22 [SERVER] client has not send any login information: 3000 / 10000 ms; ProcessorID: 22 [SERVER] client has not send any login information: 4000 / 10000 ms; ProcessorID: 22 [SERVER] client has not send any login information: 5001 / 10000 ms; ProcessorID: 22 [SERVER] client has not send any login information: 6001 / 10000 ms; ProcessorID: 22 [SERVER] client has not send any login information: 7001 / 10000 ms; ProcessorID: 22 [SERVER] client has not send any login information: 8001 / 10000 ms; ProcessorID: 22 [SERVER] client has not send any login information: 9001 / 10000 ms; ProcessorID: 22 [SERVER] client has not send any login information: 10002 / 10000 ms; ProcessorID: 22 [SERVER] NULL CLIENT TIMED OUT: DISCONENCTING; ProcessorID: 22 [SERVER] NTException on: null; ProcessorID: 22 [SERVER] last received size: 116 [SERVER] last received check: 42 [SERVER] last received header: 111: Param [SERVER] last received command: ExecuteAdminCommand[return] java.net.SocketException: Socket closed at java.net.SocketInputStream.read(SocketInputStream.java:204) at java.net.SocketInputStream.read(SocketInputStream.java:141) at java.net.SocketInputStream.read(SocketInputStream.java:224) at java.io.DataInputStream.readInt(DataInputStream.java:387) at org.schema.schine.network.server.ServerProcessor.run(SourceFile:522) at java.lang.Thread.run(Thread.java:745) [SERVER][DISCONNECT] Client 'null' HAS BEEN DISCONNECTED . PROBE: false; ProcessorID: 22 [SERVER] COULD NOT UNREGISTER CLIENT null [SERVER] COULD NOT UNREGISTER CLIENT null [SERVER] SERVER PROCESSOR STOPPED FOR null; PID 22
-QA Testing-
Jun 26 2017
-QA Testing-
Jun 22 2017
-QA Testing-
-QA Testing-
-QA Testing-
-QA Testing-
Jun 21 2017
-QA Testing-
-QA Testing-
Jun 16 2017
-QA Testing-
Jun 15 2017
-QA Testing-
Jun 6 2017
-QA Testing-
Apr 23 2017
I can't reliably reproduce it anymore, only got it once now and the exact same steps don't trigger the issue again.
Should be fixed in 0.199.534
Apr 20 2017
In T2118#98526, @33Cav wrote:2 could be a result of the core counting as 2m cube. In your example did you add 19 or 20 blocks to reach dimension of 21?
2 could be a result of the core counting as 2m cube. In your example did you add 19 or 20 blocks to reach dimension of 21?
Apr 19 2017
-QA Testing-
Apr 14 2017
-QA Testing-
-QA Testing-
Apr 11 2017
got my hands on a mac and am close to fixing this
Apr 10 2017
FYI the issue I raised is a duplicate of this one and can be merged/closed:
https://phab.starma.de/T2299
I'm sorry, I'm trying to get a mac here to fix the issue.
Apr 7 2017
the dialog title "SELL" and "BUY" are incorrect still, see 2nd image in description.
Apr 3 2017
Unfortunately MacOS did not provide backwards compatibility from core 3.2. That means that it's impossible to request a context without forward compatibility, which removes fixed function pipeline. This is used by the current text rendering library, and in a few other places, since I always went with backwards compatibility over using the latest openGL without a fallback.