Bazel rules for the `tsc` compiler from http://typescriptlang.org
issue commentmicrosoft/TypeScript
Compiled code contain jsx code.
Once merged, can the fix be cherry picked into a 5.1.x release? This seems like a regression currently in 5.1.2-rc.
comment created time in 6 days
pull request commentaspect-build/rules_ts
chore: Update tool versions to include TS 5.0.2 and 5.0.3
tests will most likely fail due to recent changes to the typescript packaging.
Thanks for pointing this out! I'm about to head on holiday so will close out this PR for now since more substantial changes will be required :)
comment created time in 2 months
push eventericrafalovsky/rules_ts
commit sha ef7e5e7448caf3ebca6db9d76f8bbbb882192882
chore: Update tool versions to include TS 5.0.2 and 5.0.3
push time in 2 months
create barnchericrafalovsky/rules_ts
branch : update-tool-versions-5x
created branch time in 2 months
Bazel rules for the `tsc` compiler from http://typescriptlang.org
https://docs.aspect.build/rules/aspect_rules_ts
fork in 2 months
startedaspect-build/rules_ts
started time in 2 months
issue commentamir20/dozzle
[Feature Request] Display container health status
Tried it out and it works great!! 💯
comment created time in 2 months
startedamir20/dozzle
started time in 2 months
issue commentamir20/dozzle
[Feature Request] Display container health status
Hmm that's an interesting finding! I'm unfamiliar with how docker ps
works under the hood but perhaps utilizing the filter functionality of docker ps
(ie docker ps --filter health=unhealthy
) is a way to grab the relevant minimal information quickly
comment created time in 2 months
issue openedamir20/dozzle
[Feature Request] Display container health status
Description
One of our uses cases for dozzle
is to look at logs to understand why a container may be unhealthy. Docker has a healthcheck feature that is exposed in docker ps
that can point developers to what continer's logs may be interesting to investigate, but this requires using both the docker CLI and dozzle. It would be great if dozzle
was able to surface this information to avoid needing to use the docker CLI.
Potential solutions
- Display a red icon in the left sidebar if a container is not healthy (per docker)
- Display some green/red indicator at the top of the UI to indicate if all containers are healthy / unhealthy
Thanks for all your work on this awesome project ❤️ !
created time in 2 months
issue openedbuchgr/bazel-remote
Latest bazel-remote (2.4.1) fails to run on Ubuntu 18 due to GLIBC error
Summary
Running bazel-remote
version 2.4.1 on Ubuntu 18 fails with the following error message:
/lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.34 not found
Notably, bazel-remote version 2.4.0 works fine, so reporting this issue as perhaps there were some inadvertent changes in how this point release was packaged.
Details
bazel-remote version: 2.4.1 Ubuntu version: 18.04.5
created time in 3 months