[jira] [Updated] (COMPRESS-619) Large SevenZFile fails When Next Header Size is Greater than Max Int
[
https://issues.apache.org/jira/browse/COMPRESS-619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary D. Gregory updated COMPRESS-619:
-
Assignee: Gary D. Gregory
> Large SevenZFile fails When Next Header Size is Greater than Max Int
>
>
> Key: COMPRESS-619
> URL: https://issues.apache.org/jira/browse/COMPRESS-619
> Project: Commons Compress
> Issue Type: Bug
> Components: Archivers
>Affects Versions: 1.21
>Reporter: Brian Miller
>Assignee: Gary D. Gregory
>Priority: Minor
>
> When reading a large file (42GB) the following stack trace is produced:
>
> {code:java}
> java.io.IOException: Cannot handle nextHeaderSize 4102590414
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.assertFitsIntoNonNegativeInt(SevenZFile.java:2076)
> ~[classes/:?]
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.initializeArchive(SevenZFile.java:528)
> ~[classes/:?]
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.readHeaders(SevenZFile.java:474)
> ~[classes/:?]
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.(SevenZFile.java:343)
> ~[classes/:?]
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.(SevenZFile.java:136)
> ~[classes/:?]
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.(SevenZFile.java:376)
> ~[classes/:?]
> at
> org.apache.commons.compress.archivers.sevenz.SevenZFile.(SevenZFile.java:364)
> ~[classes/:?] {code}
>
> The file was produced using the SevenZOutputFile class and contains a large
> number of very small files all inserted using copy compression. It passes the
> 7z tests and has the following statistics:
>
> {code:java}
> Files: 40872560
> Size: 43708874326
> Compressed: 47811464772
> {code}
> It is failing because a ByteBuffer can't be created that is large enough with
> something over max integer in size to do the CRC check.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
[jira] [Created] (MATH-1645) EigenDecomposition returns eigenvalues/vectors IN ORDER?
Richard K Belew created MATH-1645: - Summary: EigenDecomposition returns eigenvalues/vectors IN ORDER? Key: MATH-1645 URL: https://issues.apache.org/jira/browse/MATH-1645 Project: Commons Math Issue Type: Improvement Affects Versions: 3.6.1 Reporter: Richard K Belew It appears that getRealEigenvalues() and getEigenvector() return values in decreasing order of eigenvalues (largest first)? This would be a good feature to reveal in the `org.apache.commons.math4.linear.EigenDecomposition.java` documentation. I propose adding this simple sentence: > The columns of V represent the eigenvectors in the sense that A*V = V*D, i.e. > A.multiply(V) equals V.multiply(D). The matrix V may be badly conditioned, or > even singular, so the validity of the equation A = V*D*inverse(V) depends > upon the condition of V. The eigenvalues returned by getRealEigenvalues() and eigenvectors returned by getEigenvector() are in decreasing order of eigenvalues (largest first). > This implementation is based on the paper by A. Drubrulle, R.S. Martin and > J.H. Wilkinson "The Implicit QL Algorithm" in Wilksinson and Reinsch (1971) > Handbook for automatic computation, vol. 2, Linear algebra, Springer-Verlag, > New-York. (I've not tried to patch within the Commons framework, or I'd produce a pull request.) -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (JEXL-369) Add 'let' and 'const' variable declarations
[ https://issues.apache.org/jira/browse/JEXL-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17533205#comment-17533205 ] Dmitri Blinov edited comment on JEXL-369 at 5/7/22 7:29 AM: You are right about case 4. It differs from the case 2 in a sense that the inner scoped var is declared first, and the outer scoped var is declared afterwards. But it should be disallowed also. Added case 0 as compatibility check was (Author: dmitri_blinov): You are right about case 4. It differs from the case 2 in a sense that the inner scoped var is declared first, and the outer scoped var is declared afterwards. But it should be disallowed also > Add 'let' and 'const' variable declarations > --- > > Key: JEXL-369 > URL: https://issues.apache.org/jira/browse/JEXL-369 > Project: Commons JEXL > Issue Type: Improvement >Affects Versions: 3.2.1 >Reporter: Henri Biestro >Assignee: Henri Biestro >Priority: Major > Fix For: 3.3 > > > WHAT: > Add creation of lexical scope variables, modifiable with 'let', > non-modifiable through 'const'. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Comment Edited] (JEXL-369) Add 'let' and 'const' variable declarations
[
https://issues.apache.org/jira/browse/JEXL-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17532992#comment-17532992
]
Dmitri Blinov edited comment on JEXL-369 at 5/7/22 7:28 AM:
So, to sum up, what should we expect (in non-lexical mode)?
Case 0
{code:java}
var x = 1; // allowed
var x = 2; // allowed {code}
Case 1
{code:java}
var x = 1; // allowed
let x = 2; // disallowed {code}
Case 2
{code:java}
let x = 1; // allowed
var x = 2; // disallowed {code}
Case 3
{code:java}
let x = 1; // allowed
{
let x = 2; // disallowed
} {code}
Case 4
{code:java}
{
let x = 1; // allowed
var x = 2; // disallowed
} {code}
Case 5
{code:java}
{
let x = 1; // allowed
}
var x = 2; // allowed
{code}
Right? In lexical mode there should be no difference between var and let, I
guess.
was (Author: dmitri_blinov):
So, to sum up, what should we expect (in non-lexical mode)?
Case 1
{code:java}
var x = 1; // allowed
let x = 2; // disallowed {code}
Case 2
{code:java}
let x = 1; // allowed
var x = 2; // disallowed {code}
Case 3
{code:java}
let x = 1; // allowed
{
let x = 2; // disallowed
} {code}
Case 4
{code:java}
{
let x = 1; // allowed
var x = 2; // disallowed
} {code}
Case 5
{code:java}
{
let x = 1; // allowed
}
var x = 2; // allowed
{code}
Right? In lexical mode there should be no difference between var and let, I
guess.
> Add 'let' and 'const' variable declarations
> ---
>
> Key: JEXL-369
> URL: https://issues.apache.org/jira/browse/JEXL-369
> Project: Commons JEXL
> Issue Type: Improvement
>Affects Versions: 3.2.1
>Reporter: Henri Biestro
>Assignee: Henri Biestro
>Priority: Major
> Fix For: 3.3
>
>
> WHAT:
> Add creation of lexical scope variables, modifiable with 'let',
> non-modifiable through 'const'.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
