Drop/resolve TODO's #847

Closed
dstepanov-yadro wants to merge 1 commits from dstepanov-yadro/frostfs-node:fix/todo into master

The most of TODOs are more than one year old, so looks like they will be never resolved.

Some "young" TODOs are still present.

The most of TODOs are more than one year old, so looks like they will be never resolved. Some "young" TODOs are still present.
dstepanov-yadro force-pushed fix/todo from 48efdb391a to 940554edce 2023-12-06 13:30:44 +00:00 Compare
dstepanov-yadro requested review from storage-core-committers 2023-12-06 13:31:04 +00:00
dstepanov-yadro requested review from storage-core-developers 2023-12-06 13:31:09 +00:00
dstepanov-yadro force-pushed fix/todo from 940554edce to 63a87eb3c5 2023-12-06 13:32:10 +00:00 Compare
dstepanov-yadro force-pushed fix/todo from 63a87eb3c5 to d4be3ea940 2023-12-06 13:32:55 +00:00 Compare
fyrchik reviewed 2023-12-06 13:35:42 +00:00
@ -276,4 +276,2 @@
for {
listPrm.WithCursor(c)
// TODO (@fyrchik): #1731 this approach doesn't work in degraded modes

Please, let's leave this TODO as it is, it is sth we would like to support.

Please, let's leave this TODO as it is, it is sth we would like to support.
Poster
Collaborator
https://git.frostfs.info/TrueCloudLab/frostfs-node/issues/848

What is the problem with still having it in code?

What is the problem with still having it in code?
Poster
Collaborator

The task can be scheduled and completed. The comment in the code will be lost.

The task can be scheduled and completed. The comment in the code will be lost.

The comment reminds you that the task exists in the first place, so everyone who touches the code sees possible implications.

The comment reminds you that the task exists in the first place, so everyone who touches the code sees possible implications.
Poster
Collaborator

Ok, reverted comment.

Ok, reverted comment.

It is different now and misses the link to the task.

It is different now and misses the link to the task.
Poster
Collaborator

The meaning of the comment is the same. Why store references to tasks in the code?

The meaning of the comment is the same. Why store references to tasks in the code?

To link to the task and discussion (and not to create it again).

To link to the task and discussion (and not to create it again).
Poster
Collaborator

Source code is not the best place for discussions:)

Then we need to add links to all tasks from gitea to the source code.

Source code is not the best place for discussions:) Then we need to add links to all tasks from gitea to the source code.

Source code is not the best place for discussions:)

Exactly, and link links to a proper place for discussion.

Then we need to add links to all tasks from gitea to the source code.

No, we don't. In some cases we feel the need to leave a comment, nothing wrong with it.

>Source code is not the best place for discussions:) Exactly, and link links to a proper place for discussion. >Then we need to add links to all tasks from gitea to the source code. No, we don't. In _some_ cases we feel the need to leave a comment, nothing wrong with it.
@ -79,4 +79,2 @@
// TODO: #1142 consider parallel execution
// TODO: #1142 consider optimization: if status == SPLIT we can continue until
// we reach the best result - split info with linking object ID.

This is a continuation of TODO comment, could remove

This is a continuation of `TODO` comment, could remove
Poster
Collaborator

done

done
dstepanov-yadro force-pushed fix/todo from d4be3ea940 to 41e22f69e7 2023-12-06 13:47:54 +00:00 Compare
acid-ant reviewed 2023-12-07 06:50:02 +00:00
@ -108,7 +108,6 @@ func getObject(cmd *cobra.Command, _ []string) {
func processResult(cmd *cobra.Command, res *internalclient.GetObjectRes, binary bool, payloadBuffer *bytes.Buffer, out io.Writer, filename string) {
if binary {
objToStore := res.Header()
// TODO(@acid-ant): #1932 Use streams to marshal/unmarshal payload
Collaborator

Could you please replace it on #849?

Could you please replace it on #849?
Poster
Collaborator

Why do I need a link to the task in the code? I think it is possible to delete this TODO, especially if there is a task.

Why do I need a link to the task in the code? I think it is possible to delete this TODO, especially if there is a task.
Collaborator

Yeah, agree.

Yeah, agree.
@ -156,7 +156,6 @@ func readFilePayload(filename string, cmd *cobra.Command) (io.Reader, cid.ID, us
buf, err := os.ReadFile(filename)
commonCmd.ExitOnErr(cmd, "unable to read given file: %w", err)
objTemp := objectSDK.New()
// TODO(@acid-ant): #1932 Use streams to marshal/unmarshal payload
Collaborator

Could you please replace it on #849?

Could you please replace it on #849?
dstepanov-yadro force-pushed fix/todo from 41e22f69e7 to cb6d097e0a 2023-12-07 08:42:59 +00:00 Compare
Poster
Collaborator

My position on TODO has not found support.

My position on TODO has not found support.
dstepanov-yadro closed this pull request 2023-12-08 11:13:20 +00:00
All checks were successful
DCO action / DCO (pull_request) Successful in 2m7s
Vulncheck / Vulncheck (pull_request) Successful in 2m21s
Build / Build Components (1.20) (pull_request) Successful in 3m43s
Build / Build Components (1.21) (pull_request) Successful in 3m38s
Tests and linters / Staticcheck (pull_request) Successful in 5m59s
Tests and linters / Tests (1.20) (pull_request) Successful in 6m26s
Tests and linters / Tests with -race (pull_request) Successful in 6m38s
Tests and linters / Lint (pull_request) Successful in 6m58s
Tests and linters / Tests (1.21) (pull_request) Successful in 3m8s

Pull request closed

Sign in to join this conversation.
No reviewers
TrueCloudLab/storage-core-committers
TrueCloudLab/storage-core-developers
No Milestone
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#847
There is no content yet.