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

TOML warnings from Netlify build #49875

Closed
sftim opened this issue Feb 24, 2025 · 4 comments
Closed

TOML warnings from Netlify build #49875

sftim opened this issue Feb 24, 2025 · 4 comments
Labels
area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sftim
Copy link
Contributor

sftim commented Feb 24, 2025

This is a Bug Report

Incorrect TOML configuration format: Key production is already used as table key
Post processing - header rules
Incorrect TOML configuration format: Key production is already used as table key
Incorrect TOML configuration format: Key production is already used as table key
Post processing done
Section completed: postprocessing
Starting post processing
Incorrect TOML configuration format: Key production is already used as table key
Post processing - redirect rules
Incorrect TOML configuration format: Key production is already used as table key
Incorrect TOML configuration format: Key production is already used as table key
Skipping form detection
Incorrect TOML configuration format: Key production is already used as table key

/kind bug
/priority important-longterm

This is because netlify.toml is invalid TOML. See how context.production.environment appears before context.production.
@sftim sftim added the kind/bug Categorizes issue or PR as related to a bug. label Feb 24, 2025
@k8s-ci-robot k8s-ci-robot added the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Feb 24, 2025
@sftim
Copy link
Contributor Author

sftim commented Feb 24, 2025

/triage accepted

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 24, 2025
@dipesh-rawat
Copy link
Member

/area web-development

@k8s-ci-robot k8s-ci-robot added the area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes label Feb 24, 2025
@sftim
Copy link
Contributor Author

sftim commented Feb 24, 2025

Fixed in #49873
/close

@k8s-ci-robot
Copy link
Contributor

@sftim: Closing this issue.

In response to this:

Fixed in #49873
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/web-development Issues or PRs related to the kubernetes.io's infrastructure, design, or build processes kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dipesh-rawat @k8s-ci-robot @sftim