Skip to content

feat: add signature verification to node response#105

Open
jorgeantonio21 wants to merge 12 commits intomainfrom
ja-add-signature-verification-to-node-response
Open

feat: add signature verification to node response#105
jorgeantonio21 wants to merge 12 commits intomainfrom
ja-add-signature-verification-to-node-response

Conversation

@jorgeantonio21
Copy link
Contributor

No description provided.

@jorgeantonio21 jorgeantonio21 added the enhancement New feature or request label Jan 1, 2025
@jorgeantonio21 jorgeantonio21 requested a review from Cifko January 1, 2025 12:08
@jorgeantonio21 jorgeantonio21 self-assigned this Jan 1, 2025
@maschad maschad self-assigned this Feb 10, 2025
@maschad maschad marked this pull request as ready for review February 10, 2025 18:35
Copy link
Contributor Author

@jorgeantonio21 jorgeantonio21 left a comment

Choose a reason for hiding this comment

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

LGTM

} else if let Some(usage) = chunk.get(USAGE) {
self.status = StreamStatus::Completed;
let _ = {
let guard = self.sui.blocking_read();
Copy link
Contributor Author

Choose a reason for hiding this comment

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

How safe is it to have a blocking_read in an async stream ?

Another possibility is poll::pending and add logic to the poll next method to handle when a signature is ready, but that's a bit too much of hassle.

Copy link
Member

Choose a reason for hiding this comment

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

That's a good point, we actually try caching the keystore when creating the Streamer to avoid locking during stream processing, wdyt?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think it makes sense, but it is a bit of a pain

Copy link
Member

Choose a reason for hiding this comment

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

You're right, we might introduce unnecessary complexity here, let's revisit this after profiling

- name: cargo format
run: cargo fmt --all -- --check

toml-format:
Copy link
Member

Choose a reason for hiding this comment

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

Added some formatting for our .toml files

Copy link
Member

@maschad maschad left a comment

Choose a reason for hiding this comment

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

Let's hold off on merging this until #219 is merged, we will also want to see the impact of blocking on the stream and the e2e tests are functional

@maschad maschad force-pushed the ja-add-signature-verification-to-node-response branch from ba43916 to b7369fb Compare March 24, 2025 22:46
@maschad maschad self-requested a review March 24, 2025 22:53
@maschad maschad marked this pull request as draft March 24, 2025 22:55
@maschad maschad marked this pull request as ready for review March 25, 2025 00:57
@maschad maschad changed the base branch from main to develop April 23, 2025 16:05
Copy link
Member

@maschad maschad left a comment

Choose a reason for hiding this comment

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

Let's revisit after profiling as mentioned here as mentioned #225

@jorgeantonio21 jorgeantonio21 force-pushed the develop branch 2 times, most recently from 075ca00 to ba3ac8e Compare May 27, 2025 07:49
Base automatically changed from develop to main May 27, 2025 21:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

blocked enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants