Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
"unidentified alias" not expected
See original GitHub issueDescribe the bug
When using an anchor like this:
foo:
- &name bar
*name:
- baz
Expected Behavior
Syntax is valid, so I expect no error
Ouput via yamllint
---
bar:
- baz
foo:
- bar
Current Behavior
Environment
- Windows
- Mac
- Linux
- other (please specify)
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Help! Provider aliases no longer working since .14 - Terraform
I used to be able to do this: ### Provider provider "aws" { alias = "foo" ... Blocks of type "required_providers" are not...
Read more >Unknown alias when loading any yaml file - Stack Overflow
I'm updating a Rails app from 4.1 to 4.2.8 using Ruby 2.2.3. The yaml file is this one: default: &default no_yearly_plans: - TH ......
Read more >Gitlab CI "include" doesn't support hidden jobs with aliases
Has this: This GitLab CI configuration is invalid: Unknown alias: my_job instead of working as expected and documented.
Read more >Please help with first steps using anchors - Configuration
realize anchors: is not a component, so took that out, made no ... Error loading /config/configuration.yaml: found undefined alias ...
Read more >Top 10 Most Common Errors In GitLab CI Pipelines - Medium
Because the script is not properly indented, it has been defined as a variable. (<unknown>): did not find expected key while parsing a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Just noticed that I was looking at a build from HEAD which lists 2 problems as expected. When I revert to 1.6.0 it shows only a single item.
@eemeli can you check the “Problems” view, if there are more reported?