Closed marun closed 1 week ago
This was intentional to notify all old plugin users. It is just too aggressive and super ugly in CI (because we don't set proper version info).
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten
A virtual workspace e2e test failure revealed a considerable amount of log spew due to an apparent version mismatch between the server and plugin. In the event of version skew, maybe log output could be reduced?
Also, given that this was a ci job with fresh builds, shouldn't the plugin and server be using matching versions?
cc: @sttts @davidfestal