Lightrun
question-mark
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.

strict validate_chord_label in 0.4 release

See original GitHub issue

Although issue #217 was solved by bmcfee in #242 , it is still present in the current 0.4 release, which results in undesired behavior. For example mir_eval.chord.validate_chord_label('C:maj') and mir_eval.chord.validate_chord_label('iwufhiweuhf') both pass without an exception.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
craffelcommented, Oct 24, 2018

Ok, 0.5 release created and on PyPI, and docs are updated! Closing this issue.

1reaction
craffelcommented, Sep 26, 2018

Cool, I can make one in the not-too-distant-future.

Read more comments on GitHub >

github_iconTop Results From Across the Web

No results found

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found
Previous page

bss_eval_sources gets slower with more CPUs

Next page

Extended chords not mapped correctly?