Tina Müller (tinita)

Results 411 comments of Tina Müller (tinita)

btw, for python tests it unfortunately looks like this: ``` PYTHON: callstack: - [Inline::Python, 3, testapi::set_var] - [Inline::Python, 3, (eval)] - [basetest, 352, search::run] value: hello ```

> There is [a clear restriction in the anchor names](https://github.com/yaml/libyaml/issues/205#issuecomment-694826652) What do you mean by that? The 1.2 spec allows colons in anchor names: https://yaml.org/spec/1.2.2/#rule-ns-anchor-char > But the tests (Y2GN,...

I only saw the linked issue now: https://github.com/jruby/jruby/issues/8352 I answered there. The important point there is: an emitter must add a space after an alias, if it is used as...

Hi, I've just enabled private vulnerability reporting for this repo: https://github.com/yaml/pyyaml/security Please report anything security related there, thanks. I think I am on the recipients list for the security policy...

Feedback from @nitzmahone and @ingydotnet : This will break stuff relying on that output, so it can't be the default. It should wait until we have the new API with...

With this PR I'm getting: ``` % make test TESTS=t/api/10-jobgroups.t KEEP_DB=1 ./t/test_postgresql /dev/shm/tpg Re-using existing database in /dev/shm/tpg because KEEP_DB is set to 1. make test-unit-and-integration TEST_PG="DBI:Pg:dbname=openqa_test;host=/dev/shm/tpg" make[1]: Entering directory...

The proper fix is to add a space after the alias: ``` *1 : true ``` It's valid to have a colon in anchor names (and yes, I agree that...

I did a PR for this last year: #159

> [...] that `ruamel.yaml` fails in exactly the same way. really? It works for me here with ruamel. The only thing ruamel does not support is nested lists. edit: here...

It would be cool if someone could have a look at my PR (#159). It still might need some work (what if we have circular aliases?), but if there's something...