Added the feature to Remove annotation objects in a specified range of frames #3617

gudipudiramanakumar · 2021-08-28T18:04:21Z

Issue: #33

The problem mentioned was to be able to remove all annotation objects in a given range of frames i.e. remove annotations on video from frame N till frame N+K.

Solution

Added a redirect to the Remove Annotations Modal to ask if the user wants to remove all the annotations or select the range of annotations to be removed in AnnotationMenuComponent
Added a new Modal RemoveRangeConfirmComponent that appears on clicking select range which allows the user to select the start frame and end frame of the range.
On selecting the range and confirming the container RemoveAnnotationsRangeContainer calls the action removeAnnotationsinRangeAsync
The removeAnnotationsinRangeAsync action removes the frames using the removeObjectAsync action which handles throwing errors

Note: The locked objects will not be removed

Motivation and context

This fixes Issue: #33 and the workflow for removing annotations in bulk can be improved

How has this been tested?

Tested locally by running the CVAT Application and the requested feature is working. All the Annotation Objects are being removed in the specified range of frames.

Checklist

I submit my changes into the develop branch
I have added description of my changes into CHANGELOG file
I have updated the documentation accordingly
I have added tests to cover my changes
I have linked related issues (read github docs)
I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
I have updated the license header for each file (see an example below)

# Copyright (C) 2021 Intel Corporation
#
# SPDX-License-Identifier: MIT

Test Commit for Remove Range

Remove annotations in range merged with remove annotations button merged

…inrange

bsekachev · 2021-09-23T07:59:21Z

cvat-ui/src/components/annotation-page/top-bar/remove-range-confirm.tsx

@@ -0,0 +1,83 @@
+// Copyright (C) 2020-2021 Intel Corporation


Suggested change

// Copyright (C) 2020-2021 Intel Corporation

// Copyright (C) 2021 Intel Corporation

bsekachev · 2021-09-23T07:59:32Z

cvat-ui/src/containers/annotation-page/top-bar/remove-range-confirm.tsx

@@ -0,0 +1,118 @@
+// Copyright (C) 2020-2021 Intel Corporation


Suggested change

// Copyright (C) 2020-2021 Intel Corporation

// Copyright (C) 2021 Intel Corporation

bsekachev · 2021-09-23T08:02:46Z

cvat-ui/src/actions/annotation-actions.ts

+                    startFrame,
+                    endFrame,


Do you really need this payload? It was not changed in the function, so, I believe we do not need to pass it to reducers

bsekachev · 2021-09-23T08:04:07Z

cvat-ui/src/reducers/interfaces.ts

+    removeinrange: {
+        sessionInstance: any | null;
+        startFrame: number;
+        endFrame: number;
+    };


I do not think that the state should be global. It is only used in one Modal window.

bsekachev · 2021-09-23T08:06:02Z

cvat-ui/src/reducers/annotation-reducer.ts

+                ...state,
+                removeinrange: {
+                    ...state.removeinrange,
+                    sessionInstance,


Why do we need this field in redux storage? It is already there. But in your case it is not necessary even to pass to removeAnnotationsinRangeAsync. Just look how fetchAnnotationsAsync is implemented.

bsekachev · 2021-09-23T08:07:25Z

cvat-ui/src/actions/annotation-actions.ts

+        try {
+
+            for(let frame = startFrame; frame<=endFrame; frame++){
+                await dispatch(changeFrameAsync(frame));


Do we really need to navigate each frame here? In this case annotation removing can fetch huge amount of time (getting frames from the server, decoding them, etc).

bsekachev · 2021-09-23T08:08:38Z

cvat-ui/src/actions/annotation-actions.ts

+            for(let frame = startFrame; frame<=endFrame; frame++){
+                await dispatch(changeFrameAsync(frame));
+
+                const states = await sessionInstance.annotations.get(frame, showAllInterpolationTracks, filters );


If showAllInterpolationTracks is true, it will remove all the tracks in the job, even if they are not presented in range.
If filters is not empty, it will not remove some objects which are not filtered according to filters.

bsekachev · 2021-09-23T08:10:26Z

cvat-ui/src/actions/annotation-actions.ts

+                const states = await sessionInstance.annotations.get(frame, showAllInterpolationTracks, filters );
+
+                states.forEach(async (state: any) => {
+                    await   dispatch(removeObjectAsync(sessionInstance,state,force));


Have you tested it with undo/redo? The objects probably can be restored with undo in this case, at the same time when remove all annotations, they can't be restored.

bsekachev · 2021-09-23T08:14:02Z

Hi, @gudipudiramanakumar

Sorry for the long response. Generally I like this patch, but I believe, it would be better to implement removing logic on cvat-core level, instead of removing all the objects via removeObjectAsync() (I has shown in comments above why it could be bad practice, what is more it has pure performance).

For example adding addition arguments to:
await sessionInstance.annotations.clear(from, to);

And one more question is to how to deal with tracks. Shall we remove full track if it's part is in removing range? Or shall we just clear track's keyframes in this range? Maybe support both ways by additional arguments in clear() method?

bsekachev · 2021-09-23T08:15:55Z

cvat-ui/src/containers/annotation-page/top-bar/remove-range-confirm.tsx

+}
+
+type Props = StateToProps & DispatchToProps;
+class RemoveAnnotationsRangeContainer extends React.PureComponent<Props> {


Definition of containers for components is outdated practice. Probably you can combine all the code in component file using useSelector(), useState(), and useDispatch() hooks

bsekachev · 2021-09-30T05:35:49Z

I will close the pull request, because there is not any reply. Do not hesitate to reopen it if you plan to continue working

gudipudiramanakumar · 2021-09-30T07:01:38Z

Hi, @bsekachev I am willing to continue my work on this issue, could you please reopen this pull request.

bsekachev · 2021-09-30T07:02:09Z

Sure

nmanovic · 2021-10-07T07:01:25Z

@gudipudiramanakumar , no need to keep the PR open. Just send us an updated PR as you are ready. No rush here.

Removed all the global states previously used and converted all the parameters to local state in annotation menu and remove range component.

gudipudiramanakumar · 2021-10-13T01:01:13Z

Hey @bsekachev and @nmanovic , sorry for the delay. I started working on the issue again and completed converting the RemoveRangeConfirmComponent to hook based approach and removed all the global states related to it.

But I want to understand how the cvat-core is setup and how to add a function on the backend.

bsekachev · 2021-10-14T10:44:06Z

@gudipudiramanakumar

how to add a function on the backend

I believe, you don't need to change backend in this feature

how the cvat-core is setup

What are your specific questions about cvat-core?

gudipudiramanakumar · 2021-10-14T11:52:57Z

Hi @bsekachev,
I understood how to work with cvat-core and I got the clear method working but I observe that there are two types of removal happening in the cvat,

Removing the objects, shapes, tags and tracks from the lists like in "Remove Annotations" in clear method (or)
Only toggling the removed key to false like in "RemoveObject".

Which one should be implemented here?

bsekachev · 2021-10-18T07:07:41Z

@gudipudiramanakumar

From my opinion - the first.
Feature removing annotations on frames range should be similar to remove all annotations, IMHO. Just only on specific frames.
The main question is what to do with tracks, where some keyframes are inside the range, some outside.

gudipudiramanakumar · 2021-10-18T13:39:23Z

@bsekachev

Ok, sure currently I got that working. But for tracks I am currently deleting the track object if the start frame is in the range, do you suggest deleting only the keyframes.

And I see that you previously suggested adding additional arguments to allow both ways would be ideal, but should this also reflect on the modal as an option for users or just an additional option on the funtion.

Added arguments of startframe and endframe to clear method in annotation-collection, and also added the updating of the states with payload on removeannotationsinrangeasync action in the reducer.

Merge all the commits during the development of the feature-removeannotationsinrange

…inrange

bsekachev · 2021-10-20T09:48:37Z

I fixed all ESLint errors but one

That is probably a new rule from airbnb style preset we use.
Could you please rewrite onClickMenuWrapper as () => onClickMenuWrapper()?

bsekachev · 2021-10-20T10:36:47Z

cvat-ui/src/components/annotation-page/top-bar/dist/remove-range-confirm.js

@@ -0,0 +1,46 @@
+"use strict";


Are you sure you want to commit this file?

No this happened by accident, how can I revert this?

Just remove it from your files and commit

bsekachev · 2021-10-20T10:45:41Z

cvat-core/src/annotations.js

+            if (startframe !== undefined && endframe !== undefined) {
+                cache.get(session).collection.clear(startframe, endframe, delTrackKeyframesOnly);
+            } else {
+                cache.get(session).collection.clear();
+            }


I think this check is extra. You call the same method and do the same check inside

bsekachev · 2021-10-20T10:58:58Z

cvat-core/src/annotations-collection.js

+                    delete this.objects[object.clientID];
+                });
+
+                this.count -= objectsRemovable.length;


this.count is used to generate clientIDs.
Do not need to decrease it if do not remove all objects, otherwise you might get several objects with the same clientID.

We are removing all the given objects in range, it is also only counting if objects are being removed. Even in tracks, they are pushed in objectsRemovable only if they are being removed and not when removing keyframes.

Or are you suggesting to completely avoid this line as the garbage collector is removing the objects as you mentioned below

should I completely avoid this line as the garbage collector is removing the objects

Yes. If you look at previous clear() implementation, it just clears all the arrays and objects. We do not remove each object separately there

bsekachev · 2021-10-20T10:59:54Z

cvat-core/src/annotations-collection.js

+                objectsRemovable.forEach((object) => {
+                    delete this.objects[object.clientID];
+                });


Probably we do not need to remove them explicitly. Garbage collector does it itself when there are no links to these objects anymore.

bsekachev · 2021-10-20T11:05:20Z

cvat-core/src/annotations-collection.js

+
+                this.count -= objectsRemovable.length;
+
+                this.flush = true;


I believe if remove from range, this flag should not be set to true.
If this flag is true, client sends put annotation request and all annotations are removed from the database.
If this flag is false, client sends only changes.

bsekachev · 2021-10-20T11:06:52Z

cvat-core/src/session.js

@@ -37,8 +37,8 @@
                        return result;
                    },

-                    async clear(reload = false) {
-                        const result = await PluginRegistry.apiWrapper.call(this, prototype.annotations.clear, reload);
+                    async clear(reload = false, startframe, endframe, delTrackKeyframesOnly = true) {


Arguments with default parameters should be placed at the end.
Maybe just set startframe and endframe to null as default?

bsekachev · 2021-10-20T11:08:16Z

cvat-ui/src/actions/annotation-actions.ts

+// eslint-disable-next-line max-len
+export function removeAnnotationsinRangeAsync(sessionInstance: any, startFrame: number, endFrame: number, delTrackKeyframesOnly: boolean): ThunkAction {


Do not need to add // eslint-disable-next-line max-len
Just format lines. For example this way:

export function removeAnnotationsinRangeAsync( sessionInstance: any, startFrame: number, endFrame: number, delTrackKeyframesOnly: boolean ): ThunkAction {

Also instead of passing sessionInstance here, just do:

const { jobInstance } = receiveAnnotationsParameters();

in the function body.

bsekachev · 2021-10-20T11:11:56Z

cvat-ui/src/containers/annotation-page/top-bar/annotation-menu.tsx

 } from 'actions/annotation-actions';
 import { exportActions } from 'actions/export-actions';

 interface StateToProps {
    annotationFormats: any;
    jobInstance: any;
+    stopFrame: any;


Why any? It is a number

bsekachev · 2021-10-20T11:12:24Z

cvat-ui/src/containers/annotation-page/top-bar/annotation-menu.tsx

@@ -32,6 +34,8 @@ interface DispatchToProps {
    loadAnnotations(job: any, loader: any, file: File): void;
    showExportModal(task: any): void;
    removeAnnotations(sessionInstance: any): void;
+    // eslint-disable-next-line max-len


Please, avoid adding these directives. Just format the line

bsekachev · 2021-10-20T11:16:22Z

cvat-ui/src/containers/annotation-page/top-bar/annotation-menu.tsx

+    const removeRange = (startFrame: number, endFrame: number, delTrackKeyframesOnly:boolean) : void => {
+        removeAnnotationinRangeAsync(jobInstance, startFrame, endFrame, delTrackKeyframesOnly);
+    };


Do not need to create one more wrapper to pass jobInstance. jobInstance can be fetched in ThunkAction body. Please, refer my comment above.

bsekachev · 2021-10-20T11:20:02Z

cvat-ui/src/containers/annotation-page/top-bar/annotation-menu.tsx

@@ -74,6 +82,11 @@ function mapDispatchToProps(dispatch: any): DispatchToProps {
        removeAnnotations(sessionInstance: any): void {
            dispatch(removeAnnotationsAsync(sessionInstance));
        },
+        // eslint-disable-next-line max-len
+        removeAnnotationinRangeAsync(sessionInstance:any, startnumber: number, endnumber: number, delTrackKeyframesOnly:boolean) {


Name it just:

removeAnnotationinRange

gudipudiramanakumar · 2021-10-20T14:54:59Z

I fixed all ESLint errors but one

That is probably a new rule from airbnb style preset we use. Could you please rewrite onClickMenuWrapper as () => onClickMenuWrapper()?

Hi @bsekachev
Added the onClickMenuWrapper in onClick according to the new rule with passing the parameters like (params: MenuInfo) => onClickMenuWrapper(params). Could you review all the changes?

Changed all the suggested changes and also removed unnecessary files in dist. Removed unnecessary explicit removals in objects and additional wrappers.

…/gudipudiramanakumar/cvat into feature-removeannotationsinrange

Fixed the mistake of wrong variable name.

Additional ESLint Issue fixed

bsekachev · 2021-10-21T10:45:29Z

cvat-core/src/annotations-collection.js

@@ -553,7 +553,35 @@
            return groupIdx;
        }

-        clear() {
+        clear(startframe, endframe, delTrackKeyframesOnly) {
+            let objectsRemovable = [];


Now it is unused variable

bsekachev · 2021-10-21T10:50:11Z

cvat-ui/src/components/annotation-page/top-bar/annotation-menu.tsx

+                onCancel: () => {
+                    toggleOpenRemoveRangeComponent(!openRemoveRangeComponent);
+                },


I do not think it is the best solution. Cancel button is not obvious to do action you programmed.

bsekachev · 2021-10-21T10:57:53Z

cvat-ui/src/components/annotation-page/top-bar/annotation-menu.tsx

                    'It will stay on the server till you save the job. Continue?',
                className: 'cvat-modal-confirm-remove-annotation',
                onOk: () => {
-                    onClickMenu(params);
+                    Modal.confirm({


I would suggest following:

pseudocode

let removeFrom; let removeUpTo; let removeOnlyKeyframes = false; Modal.confirm({ content: ( <div> // of course, need to format content properly <Text>message</Text> // of course, need to format content properly <Text>Leave the inputs below empty to remove all the annotations from this job</Text> <Text>From:</Text><InputNumber onChange={(value) => removeFrom = value} /> <Text>To:</Text><InputNumbe onChange={(value) => removeUpTo= value} /> <Tooltip title='Applicable if remove annotations in range'> <Checkbox onClick={(checked) => removeOnlyKeyframes = checked}>Delete only keyframes for tracks</Checkbox> </Tooltip> </div> ) onOk: () => removeAnnotations(removeFrom, removeUpTo, ) })

Here you do not need remove-range-confirm.tsx Component.

Ok, I'll try this approach.

Do you also suggest clubbing the removeAnnotationsAsync and removeAnnotationsinRangeAsync actions as one action

So, I think yes. They are very similar each other.

Changed the approach of removeAnnotations modal so that it could match the implementation of all the other components

gudipudiramanakumar · 2021-10-23T10:37:14Z

Hi @bsekachev
I worked on the suggested changes, I added a Collapse from Ant Design on top of the suggested approach for hiding the inputs when not needed. Please do check the commit and do suggest if anything else needs to be updated.

…inrange

gudipudiramanakumar · 2021-10-25T11:47:06Z

Hi @bsekachev
I did not understand what has failed in the workflow run, can you suggest what to be done.

bsekachev · 2021-10-26T10:36:45Z

Hi @gudipudiramanakumar

Don't worry about CI now. Looks like the same test failed in several PRs.

bsekachev · 2021-10-26T10:38:07Z

cvat-ui/src/components/annotation-page/top-bar/annotation-menu.tsx

@@ -80,14 +89,52 @@ export default function AnnotationMenuComponent(props: Props): JSX.Element {
        }

        if (params.key === Actions.REMOVE_ANNO) {
+            let removeFrom: any;
+            let removeUpTo: any;
+            let removeOnlyKeyframes: any = false;


Please, use: boolean instead of any

I did change the numbers but ESLint is throwing this error for boolean, it is suggesting to keep

let removeOnlyKeyframes = false;

Type boolean trivially inferred from a boolean literal, remove type annotation. eslint@typescript-eslint/no-inferrable-types

Okay, than just: let removeOnlyKeyframes = false;

bsekachev · 2021-10-26T10:38:25Z

cvat-ui/src/components/annotation-page/top-bar/annotation-menu.tsx

+            let removeFrom: any;
+            let removeUpTo: any;


Please, use number instead of any.

bsekachev · 2021-10-26T10:44:12Z

Thank you for this great job!
Just a couple of comments and please, update versions for cvat-core and cvat-ui:

cd cvat-core && npm version minor
cd ../cvat-ui && npm version minor

And add a line to CHANGELOG.md file (added section):

The feature to remove annotations in a specified range of frames (<https://github.com/openvinotoolkit/cvat/pull/3617>)

Fixed type annotations in the annotation-menu component for remove annotations, and updated cvat-ui and cvat-core npm versions.

…/gudipudiramanakumar/cvat into feature-removeannotationsinrange

…inrange

gudipudiramanakumar · 2021-10-26T11:23:03Z

Hi @bsekachev ,
I updated the mentioned changes and added the commits. Please have a look.

bsekachev · 2021-10-26T13:07:02Z

Great, thank you again!

gudipudiramanakumar · 2021-10-26T13:07:09Z

Thanks a lot for guiding me all the way, this was my first contribution and I am very happy to have a chance to work on this project and the issue. Thank you very much.

bsekachev · 2021-10-27T17:51:13Z

@aschernov @TOsmanov

Hi guys, could you please update documentation after this patch will be available?
I suppose need just to update the screenshot and add one sentence.

TOsmanov · 2021-10-28T05:23:35Z

@aschernov @TOsmanov

Hi guys, could you please update documentation after this patch will be available? I suppose need just to update the screenshot and add one sentence.

@bsekachev Hi, yes

gudipudiramanakumar added 5 commits August 27, 2021 15:51

Test Commit for Remove Range

25527db

Test Commit for Remove Range

Remove annotations in range merged with remove annotations button merged

aab67f4

Remove annotations in range merged with remove annotations button merged

Update annotation-reducer.ts

a085554

Update annotation-actions.ts

7839fe8

Update annotation-reducer.ts

c092a56

gudipudiramanakumar requested a review from bsekachev as a code owner August 28, 2021 18:04

gudipudiramanakumar mentioned this pull request Aug 28, 2021

Remove all annotations inside a range of frames #33

Closed

Merge branch 'openvinotoolkit:develop' into feature-removeannotations…

4d39b94

…inrange

bsekachev self-assigned this Sep 23, 2021

bsekachev reviewed Sep 23, 2021

View reviewed changes

gudipudiramanakumar closed this Sep 23, 2021

gudipudiramanakumar reopened this Sep 23, 2021

bsekachev closed this Sep 30, 2021

bsekachev reopened this Sep 30, 2021

nmanovic closed this Oct 7, 2021

Converting remove range component to hook based component

cde900f

Removed all the global states previously used and converted all the parameters to local state in annotation menu and remove range component.

gudipudiramanakumar added 3 commits October 19, 2021 01:19

Improved clear in cvat core and implemented remove range

5ed81c3

Added arguments of startframe and endframe to clear method in annotation-collection, and also added the updating of the states with payload on removeannotationsinrangeasync action in the reducer.

Merge branch 'feature-removeannotationsinrange' into develop

6f5b922

Merge pull request #1 from gudipudiramanakumar/develop

d47db3c

Merge all the commits during the development of the feature-removeannotationsinrange

Merge branch 'openvinotoolkit:develop' into feature-removeannotations…

88d1ec1

…inrange

bsekachev reviewed Oct 20, 2021

View reviewed changes

gudipudiramanakumar added 4 commits October 20, 2021 20:44

More ESLint and other updates

6cc2403

Changed all the suggested changes and also removed unnecessary files in dist. Removed unnecessary explicit removals in objects and additional wrappers.

Merge branch 'feature-removeannotationsinrange' of https://github.com…

5317c04

…/gudipudiramanakumar/cvat into feature-removeannotationsinrange

Update annotation-menu.tsx

c7a4a03

Fixed the mistake of wrong variable name.

Update remove-range-confirm.tsx

e5c23b0

Additional ESLint Issue fixed

bsekachev reviewed Oct 21, 2021

View reviewed changes

Changed the approach of removeAnnotations modal

455466f

Changed the approach of removeAnnotations modal so that it could match the implementation of all the other components

Merge branch 'openvinotoolkit:develop' into feature-removeannotations…

a313f46

…inrange

bsekachev reviewed Oct 26, 2021

View reviewed changes

gudipudiramanakumar added 2 commits October 26, 2021 16:38

Added to changelog

8b0dc67

Fixed type annotations in the annotation-menu component for remove annotations, and updated cvat-ui and cvat-core npm versions.

Merge branch 'feature-removeannotationsinrange' of https://github.com…

96e73a7

…/gudipudiramanakumar/cvat into feature-removeannotationsinrange

gudipudiramanakumar requested a review from nmanovic as a code owner October 26, 2021 11:09

Merge branch 'openvinotoolkit:develop' into feature-removeannotations…

b92b93c

…inrange

bsekachev approved these changes Oct 26, 2021

View reviewed changes

bsekachev merged commit 78158cb into cvat-ai:develop Oct 26, 2021

TOsmanov mentioned this pull request Nov 2, 2021

Add documentation about remove annotation in a frame range #3854

Merged

8 tasks

		@@ -0,0 +1,83 @@
		// Copyright (C) 2020-2021 Intel Corporation

	// Copyright (C) 2020-2021 Intel Corporation
	// Copyright (C) 2021 Intel Corporation

		@@ -0,0 +1,118 @@
		// Copyright (C) 2020-2021 Intel Corporation

		// eslint-disable-next-line max-len
		export function removeAnnotationsinRangeAsync(sessionInstance: any, startFrame: number, endFrame: number, delTrackKeyframesOnly: boolean): ThunkAction {

Added the feature to Remove annotation objects in a specified range of frames #3617

Added the feature to Remove annotation objects in a specified range of frames #3617

Conversation

gudipudiramanakumar commented Aug 28, 2021 • edited Loading

Issue: #33

Solution

Motivation and context

How has this been tested?

Checklist

License

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bsekachev commented Sep 23, 2021 • edited Loading

Choose a reason for hiding this comment

bsekachev commented Sep 30, 2021

gudipudiramanakumar commented Sep 30, 2021

bsekachev commented Sep 30, 2021

nmanovic commented Oct 7, 2021

gudipudiramanakumar commented Oct 13, 2021

bsekachev commented Oct 14, 2021

gudipudiramanakumar commented Oct 14, 2021 • edited Loading

bsekachev commented Oct 18, 2021

gudipudiramanakumar commented Oct 18, 2021 • edited Loading

bsekachev commented Oct 20, 2021

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gudipudiramanakumar Oct 20, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gudipudiramanakumar commented Oct 20, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bsekachev Oct 21, 2021 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

gudipudiramanakumar commented Oct 23, 2021

gudipudiramanakumar commented Oct 25, 2021

bsekachev commented Oct 26, 2021

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

bsekachev commented Oct 26, 2021

gudipudiramanakumar commented Oct 26, 2021

bsekachev commented Oct 26, 2021

gudipudiramanakumar commented Oct 26, 2021

bsekachev commented Oct 27, 2021

TOsmanov commented Oct 28, 2021

gudipudiramanakumar commented Aug 28, 2021 •

edited

Loading

bsekachev commented Sep 23, 2021 •

edited

Loading

gudipudiramanakumar commented Oct 14, 2021 •

edited

Loading

gudipudiramanakumar commented Oct 18, 2021 •

edited

Loading

gudipudiramanakumar Oct 20, 2021 •

edited

Loading

gudipudiramanakumar commented Oct 20, 2021 •

edited

Loading

bsekachev Oct 21, 2021 •

edited

Loading