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.

Sign up for GitHub

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

Jump to bottom

Collecting crash reports (optional) to central service using bugzilla #471

Closed
JohnMcLear opened this issue Feb 20, 2012 · 6 comments
Closed

Collecting crash reports (optional) to central service using bugzilla #471

JohnMcLear opened this issue Feb 20, 2012 · 6 comments
Labels
Feature Request Plugin Request

Comments

@JohnMcLear
Copy link
Member

First of all, every server should collect its own errors and show them on a admin page. Once this works well we can think about a opt in of sending bug reports to our server
@JohnMcLear
Copy link
Member Author

Bugzilla XML-RPC and JSON-RPC APIs:
http://www.bugzilla.org/docs/tip/en/html/api/Bugzilla/WebService.html
(and linked pages)

REST API, a separate proxy server, of which there is an instance pointed at bugzilla.mozilla.org and of which you could set up your own instance as well:
https://wiki.mozilla.org/Bugzilla:REST_API
(and linked pages)

From Gerv at Mozilla. We can prolly get some support from Mo to help deploy this.

@JohnMcLear
Copy link
Member Author

Also look at JIRA

@redhog
Copy link

redhog commented Mar 14, 2012

JIRA is a monstrosity... At least that's my experience...

@marcelklehr
Copy link
Contributor

Let's make a plugin out of this!

@JohnMcLear
Copy link
Member Author

Please create a vote for this plugin / feature on http://etherpad.idea.informer.com/

@JohnMcLear
Copy link
Member Author

Plugins exist for catching stats etc. and you can use a service to monitor log files. This issue is no longer relevant.

muxator added a commit that referenced this issue Nov 25, 2019
@muxator
dependencies: upgrade npm 6.12.1 -> 6.13.1
ba38ed3 
This upgrade solves the high-severity vulnerabilities regarding
https-proxy-agent that were still present in 8e6bca4.

The output of `npm audit` goes from this:
  found 29 vulnerabilities (3 low, 26 high) in 13338 scanned packages
    run `npm audit fix` to fix 4 of them.
    1 vulnerability requires semver-major dependency updates.
    24 vulnerabilities require manual review. See the full report for details.

To this:
found 5 vulnerabilities (3 low, 2 high) in 13338 scanned packages
  1 vulnerability requires semver-major dependency updates.
  4 vulnerabilities require manual review. See the full report for details.


Changelog:
- https://github.com/npm/cli/releases

6.13.1 (2019-11-18)
    BUG FIXES
    938d6124d #472 fix(fund): support funding string shorthand (@ruyadorno)
    b49c5535b #471 should not publish tap-snapshot folder (@ruyadorno)
    3471d5200 #253 Add preliminary WSL support for npm and npx (@infinnie)
    3ef295f23 #486 print quick audit report for human output (@isaacs)

    TESTING
    dbbf977ac #278 added workflow to trigger and run benchmarks (@mikemimik)
    b4f5e3825 #457 feat(docs): adding tests and updating docs to reflect changes in registry teams API. (@nomadtechie)
    454c7dd60 #456 fix git configs for git 2.23 and above (@isaacs)

    DEPENDENCIES
    661d86cd2 [email protected] (@claudiahdz)

6.13.0 (2019-11-05)
    NEW FEATURES
    4414b06d9 #273 add fund command (@ruyadorno)

    BUG FIXES
    e4455409f #281 delete ps1 files on package removal (@NoDocCat)
    cd14d4701 #279 update supported node list to remove v6.0, v6.1, v9.0 - v9.2 (@ljharb)

    DEPENDENCIES
    a37296b20 [email protected]
    d3cb3abe8 [email protected]

    TESTING
    688cd97be #272 use github actions for CI (@JasonEtco)
    9a2d8af84 #240 Clean up some flakiness and inconsistency (@isaacs)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature Request Plugin Request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@redhog @JohnMcLear @marcelklehr