CodeTogether 2022.1 is Live!
In case you missed it, we released 2022.1 yesterday and it's a gargantuan release with:
- Blazing fast content assist for guests
- New strong-style pairing and presentation modes
- Synchronized scrolling, smarter driver management, and clearer collaboration controls
- CodeTogether Pro for Longer Sessions with More Guests
- On-premises updates like multi-server deployment and an enhanced dashbaord. No more Log4J libs in our images
- VS Code compatibility fixes (with version 1.63+ and Windows 11)
Please read our release blog for details and let us know if you have any questions: https://www.codetogether.com/blog/codetogether-2022-1-blazing-fast-content-assist-extensive-scalability/
invalid_scope error saying that some required scopes aren't whitelisted. I think it is the offline_access scope because as per some OneLogin docs that scope if used with the Authorisation Code flow will result in an error. This is the exact error I see in the browser: OPError: invalid_scope (some of requested scopes are not whitelisted) and from the logs in the CodeTogether pod it is the same, just with a stack trace
204 replies
1 reply
Hi Everyone! I started using CodeTogether (on VS Code) for my class yesterday (it's a 4th year complex network analysis, we use R and Julia mostly). I had a flurry of glitches and errors popping up. Is there a good way of reporting and getting some assistance?
Briefly:
- connection was jumpy (a lot of hanging connection, "session is no more available"...), especially if the session was started from a student
- The students working from mac os x laptop had issues executing the code remotely (i.e., instead of being executed in the host instance, VS Code spawned a local repl and used that to run the code). They could copy and paste the code by hand in the Terminal and run it on the host, but not ctrl+enter it from the editor.
- when trying to host the session from a Remote SSH instance rather then local, the codetogether clients were not able to see the files in the remote server (but would see the terminal). This is the most annoying, as it bars us to use the computational resources we have in that server.
9 replies
83 replies
Hey - in our PoC some of our engineers came across an issue with running tests in IntelliJ - the issue from our engineer
"I was the host and when running the tests, colleague couldn’t see the Test results within IntelliJ. When he runs the test they do get executed in my IDE (the host) and I can see the results but he still cannot see them. We were looking the docs and supposedly we can set up a Run configuration using a “Remote Test (CodeTogether)” that could work. But when we tried setting it up to add our test the Select button would not work. Also, setting this up for every test seems a bit painful as it doesn’t show up as a default run configuration in the Test file."
A workaround for this is to just use the terminal window in IntelliJ and use gradle to run our tests but is there a way to fix the above?
50 replies
24 replies
1 reply
3 replies
Hello @brianvfernandes after we finished the company wide test phase we gathered some feedback:
I would create github issues from those remarks, however I wanted to confirm with you beforehand, which one are actionable on your side.
Best regards, Tony
Testing (Intellij, Kotlin):
tests cannot be executed on method level
test results are sometimes not visible
upvoted this Genuitec/CodeTogether#239
Session is project scoped:
- Feature/Session is only scoped to project, people often have multiple projects open
Not all panels are visible:
- (i.e terminal / run / debug panels)
Dependencies (Intellij, Kotlin):
Navigation through files and dependencies that are not part of the project
Especially third-party libraries often cannot be navigated into, has to be done manually by the host
Autocompletion and highlighting:
- Does not consistently work for every project, especially in big projects with spring boot
Shortcuts:
- Shortcuts dont work reliably (i.e. run debug, detect duplicate lines...)
31 replies
1 reply
2 replies
1 reply