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

No longer use deprecated version of v8::Object::SetAccessor #43

Merged
merged 1 commit into from
Jan 4, 2018

Conversation

hashseed
Copy link
Member

@hashseed hashseed commented Jan 4, 2018

No description provided.

@hashseed hashseed requested a review from fhinkel January 4, 2018 08:23
@hashseed hashseed merged this pull request into v8:vee-eight-lkgr Jan 4, 2018
@hashseed hashseed deleted the setaccessor branch January 4, 2018 08:24
@addaleax
Copy link

addaleax commented Jan 4, 2018

@hashseed These kinds of things can always be PR’ed against the main repo as well, if you want :)

@hashseed
Copy link
Member Author

hashseed commented Jan 4, 2018

@addaleax I know. I'm just trying to optimize for turn-around time for my V8 CL :)

I'll submit a PR to upstream soon.

@fhinkel
Copy link

fhinkel commented Jan 4, 2018

Late LGTM :) Pinging @targos who's usually doing the V8 updates: How much extra work do commit like this cause? Is it OK to have them or should we PR's them against the main repo and wait longer until we can land something in V8?

@hashseed
Copy link
Member Author

hashseed commented Jan 4, 2018

Turns out it's already been fixed upstream. And @addaleax actually reviewed it 😜

@targos
Copy link

targos commented Jan 4, 2018

@fhinkel you mean commits like in this PR or https://chromium-review.googlesource.com/c/v8/v8/+/848782 ?

@fhinkel
Copy link

fhinkel commented Jan 4, 2018

I mean a PR like this to v8/node instead of to node/node. I thought when you update V8 in Node master, you cherry-pick from v8/node.

@fhinkel
Copy link

fhinkel commented Jan 4, 2018

Turns out it's already been fixed upstream. And @addaleax actually reviewed it 😜

And I landed it. I thought it looked familiar 😊

@targos
Copy link

targos commented Jan 4, 2018

v8/node is not part of my usual workflow. I sometimes look at it if canary has failures to see if it's fixed here.

@fhinkel
Copy link

fhinkel commented Jan 4, 2018

Thanks for clarifying, makes sense.

hashseed pushed a commit that referenced this pull request Aug 26, 2019
BUGFIXES

* [`27cccfbda`](npm/cli@27cccfb)
  [nodejs#223](npm/cli#223) vulns → vulnerabilities in
  npm audit output ([@sapegin](https://github.com/sapegin))
* [`d5e865eb7`](npm/cli@d5e865e)
  [nodejs#222](npm/cli#222)
  [nodejs#226](npm/cli#226) install, doctor: don't crash
  if registry unset ([@dmitrydvorkin](https://github.com/dmitrydvorkin),
  [@isaacs](https://github.com/isaacs))
* [`5b3890226`](npm/cli@5b38902)
  [nodejs#227](npm/cli#227)
  [npm.community#9167](https://npm.community/t/npm-err-cb-never-called-permission-denied/9167/5)
  Handle unhandledRejections, tell user what to do when encountering an
  `EACCES` error in the cache.  ([@isaacs](https://github.com/isaacs))

DEPENDENCIES

* [`77516df6e`](npm/cli@77516df)
  `licensee@7.0.3` ([@isaacs](https://github.com/isaacs))
* [`ceb993590`](npm/cli@ceb9935)
  `query-string@6.8.2` ([@isaacs](https://github.com/isaacs))
* [`4050b9189`](npm/cli@4050b91)
  `hosted-git-info@2.8.2`
    * [#46](npm/hosted-git-info#46)
      [#43](npm/hosted-git-info#43)
      [#47](npm/hosted-git-info#47)
      [#44](npm/hosted-git-info#44) Add support for
      GitLab subgroups ([@mterrel](https://github.com/mterrel),
      [@isaacs](https://github.com/isaacs),
      [@ybiquitous](https://github.com/ybiquitous))
    * [`3b1d629`](npm/hosted-git-info@3b1d629)
      [#48](npm/hosted-git-info#48) fix http
      protocol using sshurl by default
      ([@fengmk2](https://github.com/fengmk2))
    * [`5d4a8d7`](npm/hosted-git-info@5d4a8d7)
      ignore noCommittish on tarball url generation
      ([@isaacs](https://github.com/isaacs))
    * [`1692435`](npm/hosted-git-info@1692435)
      use gist tarball url that works for anonymous gists
      ([@isaacs](https://github.com/isaacs))
    * [`d5cf830`](npm/hosted-git-info@d5cf830)
      Do not allow invalid gist urls ([@isaacs](https://github.com/isaacs))
    * [`e518222`](npm/hosted-git-info@e518222)
      Use LRU cache to prevent unbounded memory consumption
      ([@iarna](https://github.com/iarna))

PR-URL: nodejs#29023
Reviewed-By: Jiawen Geng <technicalcute@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
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.

4 participants