All Projects

Events are handled in different groups, it makes sense to handle them in as few listeners as possible (where they can be logically grouped)

No need for description

Original report by ya at:

Video Contact Sheet *NIX v1.12, (c) 2007-2010 Toni Corvera
Processing <FILE>...
awk: BEGIN { if (4993,00000000000000000000 == 0) exit 0 ; else exit 1 }
awk:                 ^ syntax error
awk: BEGIN { if (4993,00000000000000000000 == 0) exit 0 ; else exit 1 }
awk:                                           ^ syntax error
awk: BEGIN { if (4993,00000000000000000000 == 0) exit 0 ; else exit 1 }
awk:                                                      ^ syntax error
awk: BEGIN { printf "%.20f", ((4993,00000000000000000000 - 4993.92))+0 }
awk:                                                               ^ syntax error
awk: BEGIN { printf "%.20f", ((4993,00000000000000000000 - 4993.92))+0 }
awk:                                                                ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:              ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                       ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                                 ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                                       ^ syntax error
awk: BEGIN { if (() < (0)) print (() * -1) ; else print () }
awk:                                                       ^ syntax error
...

Originally reported by Markus and Wade

The codec information box gets cropped with current versions of ImageMagick.

The updated version to return to the Play Store isn’t adapted to the new notification system

First reported on BSD and Debian 10 (reproducible), apparently tied to some updated tool

Only basename should be printed instead.

“Failed to capture frame (at second xxx.yyy)”

Known bug, reported by various users.

E.g. on FreeBSD

pyth_th() uses **, accepted by gawk but not mawk

Also Ubuntu uses mawk by default.

Version 1.12.3 breaks on FreeBSD due to the usage of GNU-specific extensions of expr, sed and an incompatible Bash RE.

As reported by Dirk Reiners (paraphrased)

When steps get too small they might round to 0 ⇒ infinite loop in compute_timecodes.

There’s a new, more secure, file format

References:
https://bitbucket.org/jakobwesthoff/revelation
http://oss.codepoet.no/revelation/wiki/FileFormatSpec
http://knoxin.blogspot.com.es/2012/06/revelation-password-manager-considered.html
http://www.westhoffswelt.de/blog/2010/4/19/from-revelation-security-to-android-password-managers

main(sys.argv[1:])
  File "./relevation.py", line 628, in main
    numhits = dump_all_entries(xmldata)
  File "./relevation.py", line 213, in dump_all_entries
    return dump_result(res, 'all')
  File "./relevation.py", line 290, in dump_result
    dumpfn(typeName, name, descr, notes, fields)
  File "./relevation.py", line 253, in dump_single_result
    print s
UnicodeEncodeError: 'ascii' codec can't encode character u'\xf3' in position 19: ordinal not in range(128)

Traceback (most recent call last):
  File "./relevation.py", line 658, in <module>
    main(sys.argv[1:])
  File "./relevation.py", line 638, in main
    numhits += dump_entries(xmldata, needles, 'folder', caseInsensitive, True)
  File "./relevation.py", line 224, in dump_entries
    res = tree.xpath(xpath)
  File "lxml.etree.pyx", line 1509, in lxml.etree._Element.xpath (src/lxml/lxml.etree.c:50702)
  File "xpath.pxi", line 306, in lxml.etree.XPathElementEvaluator.__call__ (src/lxml/lxml.etree.c:145829)
  File "apihelpers.pxi", line 1395, in lxml.etree._utf8 (src/lxml/lxml.etree.c:26485)
ValueError: All strings must be XML compatible: Unicode or ASCII, no NULL bytes or control characters

Seen in HEVC contained in MPEG-TS

This is a meta-item depending on bugs/features required to complete before releasing nettype 1.5.1.

1.5.1 is a hotfix release for issues found during the staged release of 1.5.

Previous:  FS#215  (1.5),  FS#252  (1.4),  FS#203  (1.3)
Next: FS#329 (1.6)

Reported by Sarah Thomasson 15/08/2017 on Google Play:

“The new ‘4’ is missing the triangle in the body of the glyph 4 -.-”