2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6
-
Currently - as of typing this - the "Download"-buttons on https://triplea-game.org/download/
point to 2.5.22294 again - obviously silently, without any further info or note to the users.Is the roll-back to the previous ('stable') release intended?
Shall we encourage players who updated to the recently offered '2.6.stable' encourage to revert back?
-
@panther The serious problem is only for bot-users right? Anyone who does not use bots has no reasons not to get 2.6 correct?
-
@cernel
I have no idea, that is why I asked. But if that's the case, I know what to do (or not to do). Thank you. -
Thanks to everyone for their hard work on 2.6, love some of the new features:
- Potential scramble warning
- Showing units in a territory in the status bar
- No retreat symbol when picking casualties
-
@flyingbadger
Thanks for engaging and your 1st post! -
I still get websocket errors sometimes on joining, I just had a string of like 6 of them. When I get one I can't chat at all, and I have to re-log in until it works. It happens maybe 20-30% of all logins, and I've never had a run fo the problem this long before.
on 2.6.14748
-
@zlefin said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
I still get websocket errors sometimes on joining, I just had a string of like 6 of them. When I get one I can't chat at all, and I have to re-log in until it works. It happens maybe 20-30% of all logins, and I've never had a run fo the problem this long before.
on 2.6.14748
Can you post a screenshot of the specific error you're seeing?
-
I may be able to assist in playtesting if it's needed
-
@lafayette said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
@thedog & @Cernel , appreciate the recommendations. There were some updates to unit 'cycling', I think it was something like the 'sleep' was removed or something that. ...
why would you remove the 'sleep' option‽
-
So the error I get is
"Web Socket error ConcurrentModificationException"
Error Communicating with Lobby
I just updated to 2.6.14759 and am still getting the issue sometimes on login.
I'm not able to access or see the console window that I've sometimes seen in the past with error messages, maybe cuz I'm not in a game when this happens, I dunno, or maybe due to my installation on this computer being setup different.
The error I'm getting may be the same one logged by the builderbot here, hard to say.
https://github.com/triplea-game/triplea/issues/12613If I try sending a message when I get the websocket error on login, I cannot and it says
"Failed to send text IOException: Output closed"
which matches what's in that listed issue.I don't have any of the special testing settings enabled (eg the websocket beta one under settings - testing).
If other people aren't getting it, then it just won't be that important and we'll figure out why my system is having it, still not sure who else is using 2.6.x stuff and if anyone is gettin this issue, losing track of the prior discussion.
-
@zlefin said in 2.6 Release Getting Close - Need Volunteers to Help Beta Test 2.6:
ConcurrentModificationException
Do you mind posting a screenshot next time it happens?
I'm not aware of a Web Socket error that's related to a ConcurrentModificationException. I see this error report about the latter, but it doesn't mention web socket. This would help us understand if it's the same thing or not. -
@myrd Sorry, meant to link to https://github.com/triplea-game/triplea/issues/12623
-
I can try posting a screenshot, but it's not going to add any information, I already copied everything that was useable, and like I already said, it doesn't give the full console dump.
-
@zlefin Check for a file called 'triplea.log', it would be in the 'triplea' folder. That file likely has the full stack trace in it.
-
@cameron wrote:
why would you remove the 'sleep' option‽
https://forums.triplea-game.org/topic/2458/unit-scroller-issues-rfc-on-changes
In short:
- multiplayer games don't go for that many rounds, sleep not persisted in save games, relatively frequent loading of saves make sleep not useful. Sleep is most useful for large maps ,large maps are likely to be played for fewer rounds (where it would be most useful, except for those games don't go that many rounds between save/reload)
- the number of units that are put to sleep is overall low, the effort to skip them again is somewhat low
- issues with keybindings, particularly an issue in multiplayer where it's easier to not have keyboard focus on the map.
3 years later, I think we need usage statistics more than ever to help us. That is a bit of an aside.. Before bringing back sleep, we would want to redesign the hot keys a bit at least. I feel like 'a,s,d,f' should also be used for map navigation. Though, working through the various design issues and everything working well in multiplayer is possibly a hot mess. Getting 2.6 actually launched at all is the goal at the moment. Following that the release model is different.
-
@panther The serious problem is only for bot-users right? Anyone who does not use bots has no reasons not to get 2.6 correct?
I think @TheDog narrowed it down pretty precisely somewhere... My recollection, 2.5 host with 2.6 client is bad, mixing versions is bad. The problem is observed after trying to move a unit as a client, game crashes. (Bots are running 2.5, they count as the host)
Another issue, 2.6 can read save games from 2.5, but not the other way round. Having players downgrade pro-actively is not cost free (breaks all of their saves). Meanwhile those that joined lobby with 2.6 & played on bots quickly ran into issues already. This makes me think the focus needs to be on getting the 2.6 lobby & bots up & then vetted properly before we take next steps.
-
-
surely large maps mean more turns not less... certainly do in my games.
it seems what you're saying is that it's not useful in multiplayer games so you're taking away the option from solo players just because we don't matter? i really don't understand why you'd remove the option. people don't have to use it if they don't want to. seems like you're punishing people for not playing the way you do.
i didn't really get your bit about the keyboard shortcuts but if that's the problem just remove the keyboard shortcut - surely we don't have to have a keyboard shortcut for everything.ugh. skipping dozens of aaguns every round is such a pain in the arse.
-
ok, found that log file. here's the data it has from around the most recent instance
313 08:16:49.940 [main] INFO o.t.game.client.HeadedGameRunner - Launching game, version: 2.6.14759
406 08:16:50.033 [Thread-4] DEBUG g.s.e.data.gameparser.GameParser - Parsing game XML: C:\Users\Tom\triplea\downloadedMaps\battle_for_arda\map\games\Battle_For_Arda.xml
10049 08:16:59.676 [HttpClient-1-Worker-0] ERROR o.t.h.c.w.s.GenericWebSocketClient - Web Socket error
java.util.ConcurrentModificationException: null
at java.base/java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1626)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:497)
at org.triplea.http.client.web.socket.GenericWebSocketClient.messageReceived(GenericWebSocketClient.java:133)
at org.triplea.http.client.web.socket.WebSocketConnection$InternalWebSocketListener.onText(WebSocketConnection.java:248)
at java.net.http/jdk.internal.net.http.websocket.WebSocketImpl$ReceiveTask.processText(WebSocketImpl.java:627)
at java.net.http/jdk.internal.net.http.websocket.WebSocketImpl$ReceiveTask.run(WebSocketImpl.java:435)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:147)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:198)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:271)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:224)
at java.net.http/jdk.internal.net.http.websocket.WebSocketImpl.tryChangeState(WebSocketImpl.java:853)
at java.net.http/jdk.internal.net.http.websocket.WebSocketImpl$SignallingMessageConsumer.onText(WebSocketImpl.java:786)
at java.net.http/jdk.internal.net.http.websocket.MessageDecoder.payloadData(MessageDecoder.java:222)
at java.net.http/jdk.internal.net.http.websocket.Frame$Reader.readFrame(Frame.java:465)
at java.net.http/jdk.internal.net.http.websocket.TransportImpl$ReceiveTask.run(TransportImpl.java:665)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:147)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:198)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:271)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:224)
at java.net.http/jdk.internal.net.http.websocket.TransportImpl$ReadEvent.handle(TransportImpl.java:762)
at java.net.http/jdk.internal.net.http.RawChannelTube$ReadSubscriber.checkEvents(RawChannelTube.java:174)
at java.net.http/jdk.internal.net.http.RawChannelTube$ReadSubscriber.onNext(RawChannelTube.java:204)
at java.net.http/jdk.internal.net.http.RawChannelTube$ReadSubscriber.onNext(RawChannelTube.java:157)
at java.net.http/jdk.internal.net.http.common.SSLTube$DelegateWrapper.onNext(SSLTube.java:202)
at java.net.http/jdk.internal.net.http.common.SSLTube$SSLSubscriberWrapper.onNext(SSLTube.java:484)
at java.net.http/jdk.internal.net.http.common.SSLTube$SSLSubscriberWrapper.onNext(SSLTube.java:287)
at java.net.http/jdk.internal.net.http.common.SubscriberWrapper$DownstreamPusher.run1(SubscriberWrapper.java:318)
at java.net.http/jdk.internal.net.http.common.SubscriberWrapper$DownstreamPusher.run(SubscriberWrapper.java:261)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SynchronizedRestartableTask.run(SequentialScheduler.java:175)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:147)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:198)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:271)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:224)
at java.net.http/jdk.internal.net.http.common.SubscriberWrapper.outgoing(SubscriberWrapper.java:234)
at java.net.http/jdk.internal.net.http.common.SubscriberWrapper.outgoing(SubscriberWrapper.java:200)
at java.net.http/jdk.internal.net.http.common.SSLFlowDelegate$Reader.processData(SSLFlowDelegate.java:403)
at java.net.http/jdk.internal.net.http.common.SSLFlowDelegate$Reader$ReaderDownstreamPusher.run(SSLFlowDelegate.java:264)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SynchronizedRestartableTask.run(SequentialScheduler.java:175)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:147)
at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:198)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829) -
@zlefin Thanks for reporting!
I believe it should be fixed now with 2.6.14762.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login