[
https://issues.apache.org/jira/browse/COMPRESS-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16053266#comment-16053266
]
Simon Spero commented on COMPRESS-411:
--------------------------------------
Everything I've opened so far has been something I'm working on, or will be
shortly :-)
Annoyingly, JIRA doesn't support workflow triggers from github integration
until a Pull-Request is created (which the examples discuss as being suitable
for moving into an "In Review" state (merging a PR is the closeout state).
I'm not sure if that works if the merge is done wrt the asf git (I've always
just assumed the github repository is a one-way mirror).
What I really want is some way to only not receive a billion different
notifications for every commit or comment - I really wish I hadn't found the
rat issue that was breaking coveralls :-)
[https://confluence.atlassian.com/adminjiraserver071/configuring-workflow-triggers-802592811.html]
> TarUtils.formatLongOctalOrBinaryBytes never uses result of formatLongBinary
> ---------------------------------------------------------------------------
>
> Key: COMPRESS-411
> URL: https://issues.apache.org/jira/browse/COMPRESS-411
> Project: Commons Compress
> Issue Type: Bug
> Components: Archivers
> Affects Versions: 1.14
> Reporter: Simon Spero
> Priority: Minor
> Fix For: 1.15
>
>
> if the length < 9, formatLongBinary is executed, then overwritten by the
> results of formatBigIntegerBinary.
> If the results are not ignored, a unit test would fail.
> Also, do the binary hacks need to support negative numbers?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
