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

added an error handler for zipkin-web #233

Merged
merged 2 commits into from
Mar 12, 2013
Merged

added an error handler for zipkin-web #233

merged 2 commits into from
Mar 12, 2013

Conversation

bmdhacks
Copy link
Contributor

@bmdhacks bmdhacks commented Mar 8, 2013

This doesn't fully work until we integrate with my patch to finatra, but I'm submitting this now because it's done. Once finatra releases the new version we'll change the build and it will all be happy.

@johanoskarsson
Copy link
Contributor

+1 from me, but Franklin is probably a better reviewer for this one

… exist in Finatra.

I submitted a patch to finatra, and it was accepted, and julio rolled a release, but it depends on finagle 6
which breaks our dependency tree.  Sooo I'm forced to put this code in here with a FIXME because I want
the feature.
@franklinhu
Copy link
Contributor

+1

bmdhacks pushed a commit that referenced this pull request Mar 12, 2013
Error handling for zipkin-web.  Before we were returning an empty document if a downstream exception happened, now we print the stacktrace to the screen.  There is some hackish code in here that is needed until we upgrade to Finatra 1.3.0 + Finagle 6 + Cassie 0.?? (cassie not released yet)
@bmdhacks bmdhacks merged commit 2340e1b into master Mar 12, 2013
@bmdhacks bmdhacks deleted the web-error-status branch March 12, 2013 21:30
codefromthecrypt pushed a commit that referenced this pull request Jun 3, 2016
…tions

Per #233, we need to be very explicit about mysql not being the choice for big data
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.

3 participants