Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Wrong package detected as source of exception #66

Open
izuzak opened this issue May 24, 2015 · 3 comments
Open

Wrong package detected as source of exception #66

izuzak opened this issue May 24, 2015 · 3 comments

Comments

@izuzak
Copy link
Contributor

izuzak commented May 24, 2015

Example 1: atom/command-palette#43
Example 2: atom/atom#7120
Example 3: atom/atom#7163
Example 4: atom/atom#6534
Example 5: atom/atom-dark-syntax#12
Example 6: atom/atom-dark-syntax#8
Example 7: atom/atom#7313
Example 8: atom/atom#7571
Example 9: atom/atom#7721
Example 10: atom/atom#8065
Example 11: atom/atom-dark-syntax#17
Example 12: atom/atom#8333
Example 13: atom/atom#8545
Example 14: atom/atom#8552
Example 15: atom/atom#8825
Example 16: atom/atom#8970
Example 17: atom/atom#9033
Example 18: atom/atom#9036
Example 19: atom/atom#9110

@izuzak
Copy link
Contributor Author

izuzak commented Nov 2, 2015

More problems reported here: #98

@dirk-thomas
Copy link
Contributor

It looks like I ran into this with atom-community/sync-settings#291

The stacktrace doesn't mention sync-settings anywhere but gist-it so the ticket should have been created against that repo instead.

@Arcanemagus
Copy link

@dirk-thomas Actually sync-settings is the very first package mentioned in the stack trace 😛.

It looks like part of gist-it is using the agent-base NPM package, which the github4 dependency of sync-settings includes. Atom is loading it from your package, but using it in gist-it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants