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

Logs output for running Starlark isn't in a codeblock/monospaced #1386

Closed
mieubrisse opened this issue Sep 26, 2023 · 2 comments · Fixed by #1454 or #1453
Closed

Logs output for running Starlark isn't in a codeblock/monospaced #1386

mieubrisse opened this issue Sep 26, 2023 · 2 comments · Fixed by #1454 or #1453
Labels
bug Something isn't working bugbash frontend Label for issues (bugs, FRs, etc) that pertain to the Kurtosis frontend papercut

Comments

@mieubrisse
Copy link
Member

What's your CLI version?

0.83.7

Description & steps to reproduce

This suggests to me that we're not using the same component as the service logs:

Screen Shot 2023-09-26 at 13 17 02

Desired behavior

The Starlark logs output looks just like the service logs

What is the severity of this bug?

Papercut; this bug is frustrating, but I have a workaround.

@mieubrisse mieubrisse added bug Something isn't working bugbash labels Sep 26, 2023
@mieubrisse
Copy link
Member Author

Confirmed that the logs output of the service actually also isn't a codeblock (I thought it was)

@mieubrisse mieubrisse changed the title Logs output for running Starlark isn't in a codeblock/monospaced (while service logs is) Logs output for running Starlark isn't in a codeblock/monospaced Sep 26, 2023
@mieubrisse
Copy link
Member Author

Hit this again - it makes consuming the logs hard to read

@mieubrisse mieubrisse added the frontend Label for issues (bugs, FRs, etc) that pertain to the Kurtosis frontend label Sep 29, 2023
adschwartz added a commit that referenced this issue Oct 2, 2023
## Description:
The current font isn't recognized (on mac os at least), adding multiple
that should mean at least one is supported by your OS/browser.

## Is this change user facing?
YES

## References (if applicable):
Closes #1386
adschwartz added a commit that referenced this issue Oct 2, 2023
🤖 I have created a release *beep* *boop*
---


##
[0.83.16](0.83.15...0.83.16)
(2023-10-02)


### Features

* add font
([#1454](#1454))
([75ce332](75ce332)),
closes [#1386](#1386)
* added --args-file to Kurtosis run
([#1451](#1451))
([fdc6220](fdc6220)),
closes [#1112](#1112)


### Bug Fixes

* Remove mouse wheel capture
([#1452](#1452))
([2d35d77](2d35d77)),
closes [#1438](#1438)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: Anders Schwartz <adschwartz@users.noreply.github.com>
leoporoli pushed a commit that referenced this issue Oct 3, 2023
## Description:
The current font isn't recognized (on mac os at least), adding multiple
that should mean at least one is supported by your OS/browser.

## Is this change user facing?
YES

## References (if applicable):
Closes #1386
leoporoli pushed a commit that referenced this issue Oct 3, 2023
🤖 I have created a release *beep* *boop*
---


##
[0.83.16](0.83.15...0.83.16)
(2023-10-02)


### Features

* add font
([#1454](#1454))
([75ce332](75ce332)),
closes [#1386](#1386)
* added --args-file to Kurtosis run
([#1451](#1451))
([fdc6220](fdc6220)),
closes [#1112](#1112)


### Bug Fixes

* Remove mouse wheel capture
([#1452](#1452))
([2d35d77](2d35d77)),
closes [#1438](#1438)

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: Anders Schwartz <adschwartz@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working bugbash frontend Label for issues (bugs, FRs, etc) that pertain to the Kurtosis frontend papercut
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant