Drop/resolve TODO's #847
No reviewers
TrueCloudLab/storage-core-committers
TrueCloudLab/storage-core-developers
Labels
No labels
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#847
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:fix/todo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The most of TODOs are more than one year old, so looks like they will be never resolved.
Some "young" TODOs are still present.
48efdb391a
to940554edce
940554edce
to63a87eb3c5
63a87eb3c5
tod4be3ea940
@ -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.
#848
What is the problem with still having it in code?
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.
Ok, reverted comment.
It is different now and misses the link to the task.
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).
Source code is not the best place for discussions:)
Then we need to add links to all tasks from gitea to the source code.
Exactly, and link links to a proper place for discussion.
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 removedone
d4be3ea940
to41e22f69e7
@ -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
Could you please replace it on #849?
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.
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
Could you please replace it on #849?
41e22f69e7
tocb6d097e0a
My position on TODO has not found support.
Pull request closed