-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to pause data updates #1123
Conversation
@@ -177,11 +177,16 @@ export class WorkspaceExperiments extends BaseWorkspaceWebviews< | |||
} | |||
} | |||
|
|||
public createRepository(dvcRoot: string, resourceLocator: ResourceLocator) { | |||
public createRepository( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Function createRepository
has 26 lines of code (exceeds 25 allowed). Consider refactoring.
485dad4
to
c4ef586
Compare
@@ -1,3 +1,4 @@ | |||
import { EventEmitter } from 'vscode' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[F] These are the functional changes and the corresponding test is here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The rest is just EventEmitter
drilling and signature changes.
dc90c83
to
a7969dd
Compare
c4ef586
to
058d5f2
Compare
a7969dd
to
55ee93f
Compare
058d5f2
to
211138d
Compare
Code Climate has analyzed commit 211138d and detected 1 issue on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 100.0% (85% is the threshold). This pull request will bring the total coverage in the repository to 96.7% (0.1% change). View more on Code Climate. |
4/5
master
<- #1120 <- #1122 <- #1124 <- this <- #1125Follow up from https://github.com/iterative/vscode-dvc/pull/1120/files#r762631396 i.e the "temporary fix" (
waitForLock
) which was implemented so that we could queue experiments without error because they were running into the locks created bystatus
,diff
,exp show
, etc.This will mitigate the issue of updates running whenever we perform an action running within the extension but there is nothing that comes to mind for something that we can do about updates running when a user uses the CLI directly.
Also relates to #948 (comment).