Code Monkey home page Code Monkey logo

datadog-tracer-js's People

Contributors

greenkeeper[bot] avatar rochdev avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

datadog-tracer-js's Issues

An in-range update of gulp-sourcemaps is breaking the build 🚨

Version 2.6.3 of gulp-sourcemaps was just published.

Branch Build failing 🚨
Dependency gulp-sourcemaps
Current Version 2.6.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

gulp-sourcemaps is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 9 commits.

  • b97fe77 bump 2.6.3
  • e75e0c2 readme typos
  • 8774287 Merge pull request #338 from ogvolkov/master
  • 5d60422 fix coverage by extracting exception to string
  • f82acba simplify exception output
  • c73db90 Test for missing source map handling
  • 114c336 fix jshint
  • d62f16d Include exception message in logs if available
  • 134a47c Log if external source map is not found with loadMaps: true

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of sinon is breaking the build 🚨

Version 4.1.6 of sinon was just published.

Branch Build failing 🚨
Dependency sinon
Current Version 4.1.5
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 10 commits.

  • 68c37ed Update docs/changelog.md and set new release id in docs/_config.yml
  • cd8ae51 Add release documentation for v4.1.6
  • 29e80be 4.1.6
  • a5c59a5 Update History.md and AUTHORS for new release
  • 0ae60b6 Merge pull request #1653 from mroderick/upgrade-dependencies
  • dcd4191 Upgrade browserify to latest
  • a316f02 Upgrade markdownlint-cli to latest
  • 78ebdb3 Upgrade lint-staged to latest
  • fcf967b Upgrade dependency supports-color
  • 7c3cb4f Enable StaleBot with default configuration (#1649)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

Version 4.15.0 of eslint was just published.

Branch Build failing 🚨
Dependency eslint
Current Version 4.14.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

eslint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v4.15.0
  • 6ab04b5 New: Add context.report({ messageId }) (fixes #6740) (#9165) (Jed Fox)
  • fc7f404 Docs: add url to each of the rules (refs #6582) (#9788) (Patrick McElhaney)
  • fc44da9 Docs: fix sort-imports rule block language (#9805) (ferhat elmas)
  • 65f0176 New: CLIEngine#getRules() (refs #6582) (#9782) (Patrick McElhaney)
  • c64195f Update: More detailed assert message for rule-tester (#9769) (Weijia Wang)
  • 9fcfabf Fix: no-extra-parens false positive (fixes: #9755) (#9795) (Erin)
  • 61e5fa0 Docs: Add table of contents to Node.js API docs (#9785) (Patrick McElhaney)
  • 4c87f42 Fix: incorrect error messages of no-unused-vars (fixes #9774) (#9791) (akouryy)
  • bbabf34 Update: add ignoreComments option to indent rule (fixes #9018) (#9752) (Kevin Partington)
  • db431cb Docs: HTTP -> HTTPS (fixes #9768) (#9768) (Ronald Eddy Jr)
  • cbf0fb9 Docs: describe how to feature-detect scopeManager/visitorKeys support (#9764) (Teddy Katz)
  • f7dcb70 Docs: Add note about "patch release pending" label to maintainer guide (#9763) (Teddy Katz)
Commits

The new version differs by 14 commits.

  • e14ceb0 4.15.0
  • 2dfc3bd Build: changelog update for 4.15.0
  • 6ab04b5 New: Add context.report({ messageId }) (fixes #6740) (#9165)
  • fc7f404 Docs: add url to each of the rules (refs #6582) (#9788)
  • fc44da9 Docs: fix sort-imports rule block language (#9805)
  • 65f0176 New: CLIEngine#getRules() (refs #6582) (#9782)
  • c64195f Update: More detailed assert message for rule-tester (#9769)
  • 9fcfabf Fix: no-extra-parens false positive (fixes: #9755) (#9795)
  • 61e5fa0 Docs: Add table of contents to Node.js API docs (#9785)
  • 4c87f42 Fix: incorrect error messages of no-unused-vars (fixes #9774) (#9791)
  • bbabf34 Update: add ignoreComments option to indent rule (fixes #9018) (#9752)
  • db431cb Docs: HTTP -> HTTPS (fixes #9768) (#9768)
  • cbf0fb9 Docs: describe how to feature-detect scopeManager/visitorKeys support (#9764)
  • f7dcb70 Docs: Add note about "patch release pending" label to maintainer guide (#9763)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of safe-buffer is breaking the build 🚨

Version 5.1.0 of safe-buffer just got published.

Branch Build failing 🚨
Dependency safe-buffer
Current Version 5.0.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As safe-buffer is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • bitHound - Code No failing files. Details
  • bitHound - Dependencies 1 failing dependency. Details

Commits

The new version differs by 10 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of sinon is breaking the build 🚨

Version 3.3.0 of sinon just got published.

Branch Build failing 🚨
Dependency sinon
Current Version 3.2.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • bitHound - Dependencies Error analyzing branch. Details
  • bitHound - Code Error analyzing branch. Details

Commits

The new version differs by 24 commits.

  • e9f40a2 Rename Changelog.txt to History.md
  • 40edb3e Update docs/changelog.md and set new release id in docs/_config.yml
  • 27986c8 Add release documentation for v3.3.0
  • 85f30b5 3.3.0
  • 7d45683 Update Changelog.txt and AUTHORS for new release
  • 10906a7 Merge pull request #1560 from servel333/nested_property_matcher
  • a54b38c Fixes docs for error.
  • 04ba963 Adds sinon.match.hasNested
  • 5fbd9ee Merge pull request #1549 from killmenot/fix-1442
  • 0a34cf5 Merge pull request #1550 from kuba-orlik/patch-1
  • a90f3ce Merge pull request #1558 from fatso83/fix-eslint-error
  • 32e4516 Update code to stricter linting
  • 212e91d Fix eslint peerDependencies error
  • 5606815 Fix double backticks in inline code examples
  • af30213 fix #1442

There are 24 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of protobufjs is breaking the build 🚨

Version 6.8.2 of protobufjs was just published.

Branch Build failing 🚨
Dependency protobufjs
Current Version 6.8.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

protobufjs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 2 commits.

  • d130b52 Other: Update CHANGELOG
  • 6fc6481 Other: Include dist files in npm package, see #955

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Examples of linking spans together

I'm trying to wrap my head around creating relationships to spans. This mentions passing the context https://github.com/opentracing/specification/blob/master/specification.md. do you have any recommendations here? Do you just create a span and then pass the instance to the respective modules you want to relate to that span? I see this https://github.com/opentracing/opentracing-javascript/blob/master/src/examples/demo/demo.ts but it's too trivial and not reflective of an actual use case of tracing the db calls down the stack

An in-range update of opentracing is breaking the build 🚨

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.14.2 of opentracing was just published.

Branch Build failing 🚨
Dependency opentracing
Current Version 0.14.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

opentracing is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 13 commits.

  • 3abef18 0.14.2
  • d18156f Downgrade typescript version to avoid bug (#103)
  • aa9a455 Fix small typo in README markdown
  • eb7a9cc Fix license key typo in package.json (#101)
  • 948cd08 Fix grammatical errors and add Licence information (#100)
  • caffd2d Export SpanOptions (#94)
  • 1b32dfd Export mock tracer via standard package; add options to API test harness (#98)
  • 1f32ae4 Fix linter errors (#88)
  • ff284ca Fix Broken URL (#86)
  • 8f0798b Fix typo in README.md (#87)
  • de1dc3d Fix how requiring apiCompatibilityChecks (#85)
  • 95d73dd Fix code snippet in README.md (#84)
  • 9cce537 Update the CHANGELOG

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of sinon is breaking the build 🚨

Version 2.3.3 of sinon just got published.

Branch Build failing 🚨
Dependency sinon
Current Version 2.3.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • bitHound - Code No failing files. Details
  • bitHound - Dependencies 1 failing dependency. Details

Release Notes Make stubbing of static function properties possible
  • Fix #1450, make stubbing of static function properties possible
Commits

The new version differs by 24 commits.

  • bade318 Update docs/changelog.md and set new release id in docs/_config.yml
  • 65d4e88 Add release documentation for v2.3.3
  • 2204e72 2.3.3
  • 64034ee Update Changelog.txt and AUTHORS for new release
  • 1ece07c Merge pull request #1450 from raulmatei/fix-1445-sandbox-stubbing-static-function-property-throws-error
  • 452981c Fix 1445: make stubbing of static function properties possible
  • 25f3eeb Update sandbox configuration docs. (#1443)
  • c76fa2e Merge pull request #1444 from piperchester/patch-1
  • 6539d94 Update README.md
  • c6d01d8 Add missing function name (#1440)
  • 5f989a8 Remove confusing .withArgs from spy documentation (#1438)
  • 9ca272e Remove superfluous calls in example (#1437)
  • 9e3eac3 Merge pull request #1436 from sinonjs/feature-detect-name-property
  • 65d3d7b Feature detect function name property in issue 950
  • e0c75bd Add test for #950, show that it has been fixed (#1435)

There are 24 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Browser updates?

Hello. I am curious if there are any updates on the browser side of this, or a sample of how this works?

Thanks!

An in-range update of sinon is breaking the build 🚨

Version 2.3.2 of sinon just got published.

Branch Build failing 🚨
Dependency sinon
Current Version 2.3.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build passed Details
  • bitHound - Dependencies 1 failing dependency. Details
  • bitHound - Code No failing files. Details
  • codecov/patch Coverage not affected when comparing 331ef15...9cdff54 Details
  • codecov/project 100% remains the same compared to 331ef15 Details

Release Notes Minor fixes
  • Fix failing sandbox.resetBehavior() (#1428)
  • Fix restoring getters/setters/values for previously unexisting props (#1419)
  • Called in order takes callCount into account. Closes #1398.
Commits

The new version differs by 17 commits.

  • 2463d10 Update docs/changelog.md and set new release id in docs/_config.yml
  • 2e6bb45 Add release documentation for v2.3.2
  • 87abc01 2.3.2
  • 96e8abe Update Changelog.txt and AUTHORS for new release
  • 2f941e2 Merge pull request #1406 from lucasfcosta/called-in-order-considers-callcount
  • 3af985a Merge pull request #1427 from fearphage/remove-try-from-tests
  • c81d76b Merge pull request #1428 from fatso83/failing-sandbox-reset
  • 0bf0a79 Fix failing sandbox.resetBehavior()
  • be4e53b Add failing tests for sandbox.reset()
  • fe049aa Add code snippet for createStubInstance (#1423)
  • 9e23c4a added rule to prevent try-catch usage in tests
  • 528a7dc switched from try-catch to assert.exception()
  • d8dac84 Add downloads per month banner to README.md
  • e933add Add site/_docs/ to .eslintignore
  • ebe37da Add documentation for "has" matcher on embedded objects (#1422)

There are 17 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Usage question

Hi, I'm trying to use this module but I only get cannot PUT /v0.3/traces (400) errors.
Is there a particular agent version or configured required? (besides enabling the apm module)
Thanks

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch Build failing 🚨
Dependency mocha
Current Version 3.3.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • bitHound - Code No failing files. Details,- ✅ bitHound - Dependencies No failing dependencies. Details,- ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

  • allowUncaught added to commandline as --allow-uncaught (and bugfixed)
  • warning-related Node flags

🎉 Enhancements

🐛 Fixes

🔩 Other

Commits

The new version differs by 9 commits0.

  • 7554b31 Add Changelog for v3.4.0
  • 9f7f7ed Add --trace-warnings flag
  • 92561c8 Add --no-warnings flag
  • ceee976 lint test/integration/fixtures/simple-reporter.js
  • dcfc094 Revert "use semistandard directly"
  • 93392dd no special case for macOS running Karma locally
  • 4d1d91d --allow-uncaught cli option
  • fb1e083 fix allowUncaught in browser
  • 4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of sinon is breaking the build 🚨

Version 2.3.4 of sinon just got published.

Branch Build failing 🚨
Dependency sinon
Current Version 2.3.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • bitHound - Code No failing files. Details
  • bitHound - Dependencies 1 failing dependency. Details

Release Notes Make sandbox.resetHistory also reset spies
  • Fix #1372: make sandbox.resetHistory also reset spies (#1424)
Commits

The new version differs by 5 commits.

  • 72ae300 Update docs/changelog.md and set new release id in docs/_config.yml
  • 769d770 Add release documentation for v2.3.4
  • c8d2ec0 2.3.4
  • d27976a Update Changelog.txt and AUTHORS for new release
  • 330101a Fix #1372: make sandbox.resetHistory also reset spies (#1424)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of sinon-chai is breaking the build 🚨

Version 2.11.0 of sinon-chai just got published.

Branch Build failing 🚨
Dependency sinon-chai
Current Version 2.10.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As sinon-chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build is in progress Details
  • bitHound - Code No failing files. Details
  • bitHound - Dependencies 1 failing dependency. Details

Release Notes 2.11.0

Added support for Chai 4.x (@charlierudolph, #101).

Commits

The new version differs by 5 commits.

  • 1513007 Version 2.11.0
  • 63ac40f Convert the tests away from CoffeeScript
  • 40b35f3 Add support for, and test against, Chai v4
  • 5ff1468 Various cleanups and updates
  • 10dd944 Only test "immediately" call order variants when they exist

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of eslint is breaking the build 🚨

Version 4.7.0 of eslint just got published.

Branch Build failing 🚨
Dependency eslint
Current Version 4.6.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • bitHound - Code null Details
  • bitHound - Dependencies Error analyzing branch. Details
  • continuous-integration/travis-ci/push The Travis CI build passed Details

Release Notes v4.7.0
  • 787b78b Upgrade: Espree v3.5.1 (fixes #9153) (#9314) (Brandon Mills)
  • 1488b51 Update: run rules after node.parent is already set (fixes #9122) (#9283) (Teddy Katz)
  • 4431d68 Docs: fix wrong config in max-len example. (#9309) (薛定谔的猫)
  • 7d24dde Docs: Fix code snippet to refer to the correct option (#9313) (Ruben Tytgat)
  • 12388d4 �Chore: rewrite parseListConfig for a small perf gain. (#9300) (薛定谔的猫)
  • ce1f084 Update: fix MemberExpression handling in no-extra-parens (fixes #9156) (jackyho112)
  • 0c720a3 Update: allow autofixing when using processors (fixes #7510) (#9090) (Teddy Katz)
  • 838df76 Chore: upgrade deps. (#9289) (薛定谔的猫)
  • f12def6 Update: indent flatTernary option to handle return (fixes #9285) (#9296) (Teddy Katz)
  • e220687 Fix: remove autofix for var undef inits (fixes #9231) (#9288) (Victor Hom)
  • 002e199 Docs: fix no-restricted-globals wrong config. (#9305) (薛定谔的猫)
  • fcfe91a Docs: fix wrong config in id-length example. (#9303) (薛定谔的猫)
  • 2731f94 Update: make newline-per-chained-call fixable (#9149) (João Granado)
  • 61f1093 Chore: avoid monkeypatching Linter instances in RuleTester (#9276) (Teddy Katz)
  • 28929cb Chore: remove Linter#reset (refs #9161) (#9268) (Teddy Katz)
  • abc8634 Build: re-run browserify when generating site (#9275) (Teddy Katz)
  • 7685fed Fix: IIFE and arrow functions in no-invalid-this (fixes #9126) (#9258) (Toru Nagashima)
  • 2b1eba2 Chore: enable eslint-plugin/no-deprecated-context-methods (#9279) (Teddy Katz)
  • 981f933 Fix: reuse the AST of source code object in verify (#9256) (Toru Nagashima)
  • cd698ba Docs: move RuleTester documentation to Node.js API page (#9273) (Teddy Katz)
  • 4ae7ad3 Docs: fix inaccuracy in npm run perf description (#9274) (Teddy Katz)
  • cad45bd Docs: improve documentation for rule contexts (#9272) (Teddy Katz)
  • 3b0c6fd Chore: remove extraneous linter properties (refs #9161) (#9267) (Teddy Katz)
  • c3231b3 Docs: Fix typo in array-bracket-newline.md (#9269) (宋文强)
  • 51132d6 Fix: Formatters keep trailing '.' if preceded by a space (fixes #9154) (#9247) (i-ron-y)
  • 88d5d4d Chore: remove undocumented Linter#markVariableAsUsed method (refs #9161) (#9266) (Teddy Katz)
  • 09414cf Chore: remove internal Linter#getDeclaredVariables method (refs #9161) (#9264) (Teddy Katz)
  • f31f59d Chore: prefer smaller scope for variables in codebase (#9265) (Teddy Katz)
  • 3693e4e Chore: remove undocumented Linter#getScope method (#9253) (Teddy Katz)
  • 5d7eb81 Chore: refactor config hash caching in CLIEngine (#9260) (Teddy Katz)
  • 1a76c4d Chore: remove SourceCode passthroughs from Linter.prototype (refs #9161) (#9263) (Teddy Katz)
  • 40ae27b Chore: avoid relying on Linter#getScope/markVariableAsUsed in tests (#9252) (Teddy Katz)
  • b383d81 Chore: make executeOnFile a pure function in CLIEngine (#9262) (Teddy Katz)
  • 5e0e579 Chore: avoid internal SourceCode methods in Linter tests (refs #9161) (#9223) (Teddy Katz)
  • adab827 Chore: remove unused eslint-disable comment (#9251) (Teddy Katz)
  • 31e4ec8 Chore: use consistent names for apply-disable-directives in tests (#9246) (Teddy Katz)
  • 7ba46e6 Fix: shebang error in eslint-disable-new-line; add tests (fixes #9238) (#9240) (i-ron-y)
  • 8f6546c Chore: remove undocumented defaults() method (refs #9161) (#9237) (Teddy Katz)
  • 82d8b73 Docs: Fix error in example code for sort-imports (fixes #8734) (#9245) (i-ron-y)
  • a32ec36 Update: refactor eslint-disable comment processing (#9216) (Teddy Katz)
  • 583f0b8 Chore: avoid using globals in CLIEngine tests (#9242) (Teddy Katz)
  • c8bf687 Chore: upgrade [email protected] (#9234) (薛定谔的猫)
  • 3c41a05 Chore: always normalize rules to new API in rules.js (#9236) (Teddy Katz)
  • c5f4227 Chore: move logic for handling missing rules to rules.js (#9235) (Teddy Katz)
  • bf1e344 Chore: create report translators lazily (#9221) (Teddy Katz)
  • 2eedc1f Chore: remove currentFilename prop from Linter instances (refs #9161) (#9219) (Teddy Katz)
  • 5566e94 Docs: Replace misleading CLA links (#9133) (#9232) (i-ron-y)
  • c991630 Chore: remove ConfigOps.normalize in favor of ConfigOps.getRuleSeverity (#9224) (Teddy Katz)
  • 171962a Chore: remove internal Linter#getAncestors helper (refs #9161) (#9222) (Teddy Katz)
  • a567499 Chore: avoid storing list of problems on Linter instance (refs #9161) (#9214) (Teddy Katz)
  • ed6d088 Chore: avoid relying on undocumented Linter#getFilename API in tests (#9218) (Teddy Katz)
Commits

The new version differs by 55 commits.

  • 439e8e6 4.7.0
  • 2ec62f9 Build: changelog update for 4.7.0
  • 787b78b Upgrade: Espree v3.5.1 (fixes #9153) (#9314)
  • 1488b51 Update: run rules after node.parent is already set (fixes #9122) (#9283)
  • 4431d68 Docs: fix wrong config in max-len example. (#9309)
  • 9d1df92 Chore: Revert "avoid handling Rules instances in config-validator" (#9295)
  • 7d24dde Docs: Fix code snippet to refer to the correct option (#9313)
  • 12388d4 �Chore: rewrite parseListConfig for a small perf gain. (#9300)
  • ce1f084 Update: fix MemberExpression handling in no-extra-parens (fixes #9156)
  • 0c720a3 Update: allow autofixing when using processors (fixes #7510) (#9090)
  • 838df76 Chore: upgrade deps. (#9289)
  • f12def6 Update: indent flatTernary option to handle return (fixes #9285) (#9296)
  • e220687 Fix: remove autofix for var undef inits (fixes #9231) (#9288)
  • 002e199 Docs: fix no-restricted-globals wrong config. (#9305)
  • fcfe91a Docs: fix wrong config in id-length example. (#9303)

There are 55 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

How should span references work?

Hello, I am propagating the spans and when I call startSpan passing the property childOf I have no problem. But when I pass references, it creates another row in the datadog APM dashboard and I don't know how to trace it. I thought this should be in the same trace, isn't it?

I start an span, send a message to a queue (should I finish this span after sending the message?), consume the message and start a new span referencing the one I opened before.

Thanks

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .travis.yml
  • Replaced the old Node.js version in your .nvmrc with the new one

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

  • engines was only updated if it defined a single version, not a range.
  • .nvmrc was updated to Node.js 10
  • .travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

trace requests

If receive one request and want to send another request using axios and keep the trace of the this span, how can i do it?

An in-range update of eslint-plugin-import is breaking the build 🚨

Version 2.4.0 of eslint-plugin-import just got published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.3.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As eslint-plugin-import is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • continuous-integration/travis-ci/push The Travis CI build passed Details
  • codecov/project 100% remains the same compared to 331ef15 Details
  • codecov/patch Coverage not affected when comparing 331ef15...7e9760b Details
  • bitHound - Dependencies Error analyzing branch. Details
  • bitHound - Code Error analyzing branch. Details

Commits

The new version differs by 10 commits.

  • 44ca158 update utils changelog
  • a3728d7 bump eslint-module-utils to v2.1.0
  • 3e29169 bump v2.4.0
  • ea9c92c Merge pull request #737 from kevin940726/master
  • 8f9b403 fix typos, enforce type of array of strings in allow option
  • 95315e0 update CHANGELOG.md
  • 28e1623 eslint-module-utils: filePath in parserOptions (#840)
  • 2f690b4 update CI to build on Node 6+7 (#846)
  • 7d41745 write doc, add two more tests
  • dedfb11 add allow glob for rule no-unassigned-import, fix #671

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.