Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to a new V8 interceptors Api #180

Merged

Conversation

isheludko
Copy link

@isheludko isheludko commented Apr 22, 2024

The new callback should return v8::Intercepted::kYes/kNo to indicate whether the operation was intercepted. This replaces the old approach where the callback had to leave the return value unset or set it to an empty handle to indicate that the the request wasn't intercepted.

See https://crrev.com/c/5465509 and https://crrev.com/c/5465513.

The new callback should return v8::Intercepted::kYes/kNo to indicate
whether the operation was intercepted. This replaces the old approach
where the callback had to leave the return value unset or set it to
an empty handle to indicate that the the request wasn't intercepted.

See https://crrev.com/c/5465509 and https://crrev.com/c/5465513.
@victorgomes victorgomes merged commit 4aa6997 into v8:node-ci-2024-03-21 Apr 22, 2024
8 of 14 checks passed
victorgomes added a commit that referenced this pull request Apr 23, 2024
The new callback should return v8::Intercepted::kYes/kNo to indicate
whether the operation was intercepted. This replaces the old approach
where the callback had to leave the return value unset or set it to
an empty handle to indicate that the the request wasn't intercepted.

See https://crrev.com/c/5465509 and https://crrev.com/c/5465513.
# Conflicts:
#	src/node_contextify.cc
targos pushed a commit to targos/node that referenced this pull request Apr 29, 2024
nodejs-github-bot pushed a commit to nodejs/node that referenced this pull request May 1, 2024
Refs: v8#180
PR-URL: #52745
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
Ch3nYuY pushed a commit to Ch3nYuY/node that referenced this pull request May 8, 2024
Refs: v8#180
PR-URL: nodejs#52745
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
targos added a commit to nodejs/node that referenced this pull request May 8, 2024
Refs: v8#180
PR-URL: #52745
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
victorgomes added a commit that referenced this pull request Jun 3, 2024
The new callback should return v8::Intercepted::kYes/kNo to indicate
whether the operation was intercepted. This replaces the old approach
where the callback had to leave the return value unset or set it to
an empty handle to indicate that the the request wasn't intercepted.

See https://crrev.com/c/5465509 and https://crrev.com/c/5465513.
# Conflicts:
#	src/node_contextify.cc

# Conflicts:
#	src/node_contextify.cc
#	src/node_env_var.cc
EliphazBouye pushed a commit to EliphazBouye/node that referenced this pull request Jun 20, 2024
Refs: v8#180
PR-URL: nodejs#52745
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
bmeck pushed a commit to bmeck/node that referenced this pull request Jun 22, 2024
Refs: v8#180
PR-URL: nodejs#52745
Reviewed-By: Yagiz Nizipli <[email protected]>
Reviewed-By: Stephen Belanger <[email protected]>
pthier pushed a commit that referenced this pull request Jul 15, 2024
The new callback should return v8::Intercepted::kYes/kNo to indicate
whether the operation was intercepted. This replaces the old approach
where the callback had to leave the return value unset or set it to
an empty handle to indicate that the the request wasn't intercepted.

See https://crrev.com/c/5465509 and https://crrev.com/c/5465513.
# Conflicts:
#	src/node_contextify.cc

# Conflicts:
#	src/node_contextify.cc
#	src/node_env_var.cc
victorgomes added a commit that referenced this pull request Aug 22, 2024
The new callback should return v8::Intercepted::kYes/kNo to indicate
whether the operation was intercepted. This replaces the old approach
where the callback had to leave the return value unset or set it to
an empty handle to indicate that the the request wasn't intercepted.

See https://crrev.com/c/5465509 and https://crrev.com/c/5465513.
# Conflicts:
#	src/node_contextify.cc

# Conflicts:
#	src/node_contextify.cc
#	src/node_env_var.cc
pthier pushed a commit that referenced this pull request Oct 2, 2024
The new callback should return v8::Intercepted::kYes/kNo to indicate
whether the operation was intercepted. This replaces the old approach
where the callback had to leave the return value unset or set it to
an empty handle to indicate that the the request wasn't intercepted.

See https://crrev.com/c/5465509 and https://crrev.com/c/5465513.
# Conflicts:
#	src/node_contextify.cc

# Conflicts:
#	src/node_contextify.cc
#	src/node_env_var.cc
victorgomes added a commit that referenced this pull request Nov 18, 2024
The new callback should return v8::Intercepted::kYes/kNo to indicate
whether the operation was intercepted. This replaces the old approach
where the callback had to leave the return value unset or set it to
an empty handle to indicate that the the request wasn't intercepted.

See https://crrev.com/c/5465509 and https://crrev.com/c/5465513.
# Conflicts:
#	src/node_contextify.cc

# Conflicts:
#	src/node_contextify.cc
#	src/node_env_var.cc
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.

2 participants