Skip to content

test(506): regarded as a successful closure when session not found#609

Merged
merlimat merged 1 commit intooxia-db:mainfrom
lsytj0413:fix-506
Feb 21, 2025
Merged

test(506): regarded as a successful closure when session not found#609
merlimat merged 1 commit intooxia-db:mainfrom
lsytj0413:fix-506

Conversation

@lsytj0413
Copy link
Copy Markdown
Contributor

@lsytj0413 lsytj0413 commented Feb 19, 2025

Fix: #506

// Size: Length of the payload data
// Payload: Byte stream as long as specified by the payload size.

// Idx File:
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is removing a valid comment explaining the header format

"sync"
"time"

"google.golang.org/grpc/keepalive"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should move this refactoring (and all the similar) into a separate PR

opts.secondaryIndexName = &u.indexName
}

// UseIndex let the users specify a different index to follow for the
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why removing this part of the comment?

// +--------------+-----------+-----------+-----+
// | CRC(4Bytes) | Index(4B) | Index(4B) | ... |
// +--------------+-----------+-----------+-----+
// CRC: 32bit hash computed over the payload using CRC.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same, we shouldn't be removing this comment

@lsytj0413
Copy link
Copy Markdown
Contributor Author

@merlimat all other changes have been removed(it was auto changed by lint).

@merlimat merlimat merged commit 899b456 into oxia-db:main Feb 21, 2025
5 checks passed
@lsytj0413 lsytj0413 deleted the fix-506 branch February 22, 2025 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

server: too many warn logs when shard move to other node

2 participants