-
Notifications
You must be signed in to change notification settings - Fork 327
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
site: Ensure that preview-site can watch for changes #9
Labels
Comments
After the upgrade to sbt 0.13 we have a serveSite task that fires |
ivantopo
pushed a commit
that referenced
this issue
Mar 7, 2020
* Context Propagation Throught Kanela instrumentation for ExecutorService(submit|execute|invokeAll|invokeAny)` * JMH Instrumentation Benchmark module * remove akka.dispatch package from instrumentation * * Introduce Runnable|Callable module * * Disable All Intrumentations by default * Kanela instrumentation + update to kamon 1.2.0-M1 (#9) * update to kamon-core 1.2.0-M1, latest kamon-sbt-umbrella and sbt 1.2.6
ivantopo
pushed a commit
that referenced
this issue
Mar 9, 2020
* Add instrumentation for cats effect * Fix targetType for IOShift.Tick
ivantopo
pushed a commit
that referenced
this issue
Mar 9, 2020
Closes #9 [On Gitter](https://gitter.im/kamon-io/Kamon?at=5ad7947327c509a77426fa50), @ivantopo mentioned that another feature was copying context keys into MDC. I don't know exactly how to document this, so I left it out.
ivantopo
pushed a commit
that referenced
this issue
Mar 29, 2020
* Fix reverse parameters to recordResponse
ivantopo
pushed a commit
that referenced
this issue
Mar 29, 2020
log connection error as warning if retries > 0
ivantopo
added a commit
that referenced
this issue
Mar 29, 2020
Update Jaeger and add enviroment tag propagation
ivantopo
added a commit
that referenced
this issue
Mar 31, 2020
directly calc the average as sum/count
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently we either start/stop the
preview-site
task to see the changes or we runjekyll serve --watch
directly in the jekyll folder.. ideally, sbt should take care of watching the changes and building again.The text was updated successfully, but these errors were encountered: