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

policy_yaml incorrectly renders value.connect_timeout #1617

Open
slonka opened this issue Jan 29, 2024 · 3 comments
Open

policy_yaml incorrectly renders value.connect_timeout #1617

slonka opened this issue Jan 29, 2024 · 3 comments
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it

Comments

@slonka
Copy link
Contributor

slonka commented Jan 29, 2024

What happened?

follow up from #1615 (comment)

policy_yaml seems to incorrectly render this part:

image

vs

image

😢

to reproduce checkout 88a5e35
@slonka slonka added triage/pending This issue will be looked at on the next triage meeting kind/bug A bug labels Jan 29, 2024
@jakubdyszkiewicz jakubdyszkiewicz added triage/accepted The issue was reviewed and is complete enough to start working on it and removed triage/pending This issue will be looked at on the next triage meeting labels Jan 29, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Apr 29, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@jakubdyszkiewicz jakubdyszkiewicz removed the triage/stale Inactive for some time. It will be triaged again label Apr 29, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Jul 29, 2024
@github-actions GitHub Actions
Copy link
Contributor

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lobkovilya lobkovilya removed the triage/stale Inactive for some time. It will be triaged again label Aug 5, 2024
@github-actions github-actions bot added the triage/stale Inactive for some time. It will be triaged again label Nov 4, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 4, 2024

This issue was inactive for 90 days. It will be reviewed in the next triage meeting and might be closed.
If you think this issue is still relevant, please comment on it or attend the next triage meeting.

@lukidzi lukidzi removed the triage/stale Inactive for some time. It will be triaged again label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug triage/accepted The issue was reviewed and is complete enough to start working on it
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@slonka @jakubdyszkiewicz @lobkovilya @lukidzi