thomas.weltenbauer. Posted September 6, 2022 Report Share Posted September 6, 2022 Hello! I'm not sure if this is the right place to post this. Also a search gave me no result about this error, so I'm not sure if it is known already. With the current PlasticX Version (11.0.16.7359) I get this dialog e.G. when merging from one branch into another: "The method GetChangesetsInfoByNumber is not supported." The legacy client is working without problems. Also everything is working with older verison of PlasticX. There are no log entries at the given time (relevant and debug). 1 Link to comment Share on other sites More sharing options...
thomas.weltenbauer. Posted September 7, 2022 Author Report Share Posted September 7, 2022 This also happens when we view incomming changes / newer changesets. Link to comment Share on other sites More sharing options...
thomas.weltenbauer. Posted September 8, 2022 Author Report Share Posted September 8, 2022 The new version (11.0.16.7388) has the same error. 1 Link to comment Share on other sites More sharing options...
Anders Vagner Rostgaard Posted September 8, 2022 Report Share Posted September 8, 2022 Just adding my voice to the chorus here. This happens when: Trying to do any merge Trying to do any diff Trying to view history of a file It also stalls the client and gives no results, meaning I can't do any of these operations in PlasticX currently - I have to switch the legacy to do each of these things. 1 1 Link to comment Share on other sites More sharing options...
mnow Posted September 9, 2022 Report Share Posted September 9, 2022 (edited) I'm facing the same error whenever I try a merge. Unlike the OP and the other posts, I get the same error on the Legacy GUI as well. I'm on PlasticSCM 11.0.16.7388 on Ubuntu 18.04. Edited September 9, 2022 by mnow typos Link to comment Share on other sites More sharing options...
blue Posted September 9, 2022 Report Share Posted September 9, 2022 Hi @thomas.weltenbauer., The issue seems related with compatibilities between client and server. Are you currently using older version of the server? Link to comment Share on other sites More sharing options...
thomas.weltenbauer. Posted September 13, 2022 Author Report Share Posted September 13, 2022 What would be an older version? I think we are using the 10.0.16.5622 .net core version. Yes, it is a little older but we had no time to switch to the .net core version with installer yet. Server incompatibility would be a pretty bad thing. This would break the "as long as the third number (16) stays the same it is compatible to the server" rule. As I said: The legacy client is working for me (looks like others have different experiences). So at least the logic there is kind of compatible. Link to comment Share on other sites More sharing options...
Todd A Posted September 13, 2022 Report Share Posted September 13, 2022 Just to add to others, We also have multiple people that have reported this problem. Always it is when using the new GUI. Only solution is to have them switch to legacy gui and then they no longer see the problem. Link to comment Share on other sites More sharing options...
blue Posted September 14, 2022 Report Share Posted September 14, 2022 Hi, @thomas.weltenbauer., The team is investigating further of the issue. I would like to amend my previous comment. The issue should not be related with compatibility. As a workaround, please try to use legacy GUI or older version of PlasticX. Thanks for understanding. Link to comment Share on other sites More sharing options...
argb32 Posted September 21, 2022 Report Share Posted September 21, 2022 Is this fixed in latest? Is there a way to track issues like this? Link to comment Share on other sites More sharing options...
thomas.weltenbauer. Posted September 22, 2022 Author Report Share Posted September 22, 2022 In version 11.0.16.7411 (Released: 19-Sep-2022) this issue is still present. Link to comment Share on other sites More sharing options...
JackAlta Posted September 22, 2022 Report Share Posted September 22, 2022 I also get this error Link to comment Share on other sites More sharing options...
Patrice Beauvais Posted September 28, 2022 Report Share Posted September 28, 2022 Any update on this bug? It's a real blocking one, you cannot merge a branch or check history of files. I told everyone to go back to Old Plastic client for now. Link to comment Share on other sites More sharing options...
blue Posted October 11, 2022 Report Share Posted October 11, 2022 Thanks for your patience. The next release will include the fix. Please let us know if you have any questions. Link to comment Share on other sites More sharing options...
argb32 Posted October 12, 2022 Report Share Posted October 12, 2022 Still not fixed.. Link to comment Share on other sites More sharing options...
thomas.weltenbauer. Posted October 13, 2022 Author Report Share Posted October 13, 2022 19 hours ago, argb32 said: Still not fixed.. As blue said, it will be fixed in the next upcomming release, so it is not fixed in the current version, right. Based on the last releases I would guess the next version is released this week. So.. fingers crossed Link to comment Share on other sites More sharing options...
thomas.weltenbauer. Posted October 14, 2022 Author Report Share Posted October 14, 2022 The bug is indeed fixed for us in version 11.0.16.7504 which was released yesterday. Thanks! 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now