[jira] [Commented] (COMPRESS-453) Facing block overrun error while building TensorFlow
[
https://issues.apache.org/jira/browse/COMPRESS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476890#comment-16476890
]
Stefan Bodewig commented on COMPRESS-453:
-
Works just fine for me
{code}
$ cat Test.java
import org.apache.commons.compress.compressors.bzip2.BZip2CompressorInputStream;
import org.apache.commons.compress.utils.IOUtils;
import java.io.*;
public class Test {
public static void main(String[] args) throws Exception {
try (InputStream f = new FileInputStream("nasm-2.12.02.tar.bz2");
InputStream b = new BufferedInputStream(f);
InputStream c = new BZip2CompressorInputStream(b);
OutputStream o = new FileOutputStream("nasm-2.12.02.tar")) {
IOUtils.copy(c, o);
}
}
}
$ javac -cp
~/.m2/repository/org/apache/commons/commons-compress/1.16.1/commons-compress-1.16.1.jar
Test.java
$ java -cp
~/.m2/repository/org/apache/commons/commons-compress/1.16.1/commons-compress-1.16.1.jar:.
Test
$ java -fullversion
java full version "1.8.0_171-b11"
{code}
Can you please run the same test and paste the stack trace you see? Inside of
the github issue I see many people who don't have any problem with the file, so
maybe it is your JVM or another local issue.
For reference I used the second link to obtain nasm-2.12.02.tar.bz2 and I get
{code}
$ sha1sum nasm-2.12.02.tar.bz2
a166e8d0fa567855053ebb8d0ed3ee22f1deb30f nasm-2.12.02.tar.bz2
{code}
> Facing block overrun error while building TensorFlow
>
>
> Key: COMPRESS-453
> URL: https://issues.apache.org/jira/browse/COMPRESS-453
> Project: Commons Compress
> Issue Type: Bug
> Components: Compressors
>Affects Versions: 1.9, 1.16.1
> Environment: Linux Ubuntu 16.04 s390x
>Reporter: Namrata Bhave
>Priority: Major
>
> Building TensorFlow master using Bazel v0.12.0.
> Facing build issue immediately with error:
> {{ERROR: /home/jenkins/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
> no such package '@nasm//': java.io.IOException: block overrun and referenced
> by '//tensorflow/tools/pip_package:licenses'}}
> {{ ERROR: Analysis of target
> '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no
> such package '@nasm//': java.io.IOException: block overrun}}
> This is intermittent. Sometimes the build goes ahead. Also observed this
> error once:
> {{ERROR: /home/test/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
> such package '@nasm//': java.io.IOException: Error detected parsing the
> header and referenced by '//tensorflow/tools/pip_package:licenses'ERROR:
> Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed;
> build aborted: no such package '@nasm//': java.io.IOException: Error detected
> parsing the header}}
> Can someone please help in resolving this?
> Getting this error with AdoptJDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (COMPRESS-453) Facing block overrun error while building TensorFlow
[
https://issues.apache.org/jira/browse/COMPRESS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476827#comment-16476827
]
Namrata Bhave commented on COMPRESS-453:
Sorry about missing these details Stefan.
The bzip2 files are being downloaded from:
[https://mirror.bazel.build/www.nasm.us/pub/nasm/releasebuilds/2.12.02/nasm-2.12.02.tar.bz2]
[http://www.nasm.us/pub/nasm/releasebuilds/2.12.02/nasm-2.12.02.tar.bz2]
[http://pkgs.fedoraproject.org/repo/pkgs/nasm/nasm-2.12.02.tar.bz2/d15843c3fb7db39af80571ee27ec6fad/nasm-2.12.02.tar.bz2]
I tried using all 3, but get same error for them.
> Facing block overrun error while building TensorFlow
>
>
> Key: COMPRESS-453
> URL: https://issues.apache.org/jira/browse/COMPRESS-453
> Project: Commons Compress
> Issue Type: Bug
> Components: Compressors
>Affects Versions: 1.9, 1.16.1
> Environment: Linux Ubuntu 16.04 s390x
>Reporter: Namrata Bhave
>Priority: Major
>
> Building TensorFlow master using Bazel v0.12.0.
> Facing build issue immediately with error:
> {{ERROR: /home/jenkins/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
> no such package '@nasm//': java.io.IOException: block overrun and referenced
> by '//tensorflow/tools/pip_package:licenses'}}
> {{ ERROR: Analysis of target
> '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no
> such package '@nasm//': java.io.IOException: block overrun}}
> This is intermittent. Sometimes the build goes ahead. Also observed this
> error once:
> {{ERROR: /home/test/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
> such package '@nasm//': java.io.IOException: Error detected parsing the
> header and referenced by '//tensorflow/tools/pip_package:licenses'ERROR:
> Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed;
> build aborted: no such package '@nasm//': java.io.IOException: Error detected
> parsing the header}}
> Can someone please help in resolving this?
> Getting this error with AdoptJDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (DBCP-484) Connection leak during XATransaction in high load
[
https://issues.apache.org/jira/browse/DBCP-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476664#comment-16476664
]
Zheng Feng commented on DBCP-484:
-
There could be an issue with the Narayana related to the afterCompletion and I
think we have fixed in [JBTM-3021|https://issues.jboss.org/browse/JBTM-3021]
which should be include in the Narayan 5.8.2.Final
> Connection leak during XATransaction in high load
> -
>
> Key: DBCP-484
> URL: https://issues.apache.org/jira/browse/DBCP-484
> Project: Commons DBCP
> Issue Type: Bug
>Affects Versions: 2.2.0
>Reporter: Emanuel Freitas
>Priority: Major
> Attachments: dbcp-test.zip
>
>
> We're experiencing a connection leak in a distributed transaction when the
> system is under heavy load. We're using commons-dbcp (latest version) +
> eclipselink and narayana to perform transaction coordination.
> From time to time we can see a stacktrace reporting an abandoned connection.
> We are trying to figure out what's the root cause and we think that might be
> some issue in the commons dbcp (not sure) . More specifically, this parte of
> the code:
> ManagedConnection#updateTransactionStatus
> {code:java}
> if (transactionContext != null) {
> if (transactionContext.isActive()) {
> if (transactionContext !=
> transactionRegistry.getActiveTransactionContext()) {
> throw new SQLException("Connection can not be used while enlisted
> in another transaction");
> }
> return;
> }
> // transaction should have been cleared up by TransactionContextListener,
> but in
> // rare cases another lister could have registered which uses the
> connection before
> // our listener is called. In that rare case, trigger the transaction
> complete call now
> transactionComplete();
> }{code}
>
> If the transactionContext is different than null but the state is not
> "active" (ex: STATUS_ROLLEDBACK, STATUS_ROLLING_BACK, etc) it executes the
> transactionComplete mothod that clears the reference to a shared connection
> and after that the connection is never closed (returned to the pool).
>
> If we move the transactionComplete(); to an else,(see below), the connection
> leak does not happen.
> {code:java}
> if (transactionContext != null) {
> if (transactionContext.isActive()) {
> if (transactionContext !=
> transactionRegistry.getActiveTransactionContext()) {
> throw new SQLException("Connection can not be used while enlisted
> in another transaction");
> }
> return;
> }
> } else {
> transactionComplete();
> }{code}
>
> After this the dbcp unit tests still pass but I'm not sure about this
> changes. Can you please check?
> Thanks
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MATH-1459) Create a way to calculate the Jacobian Matrix using a Differentiator
[ https://issues.apache.org/jira/browse/MATH-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16476437#comment-16476437 ] adrian commented on MATH-1459: -- [~erans] I made the change you suggested regarding the unit test. Let me know if this is closer to what you suggested last week. I assume I should also remove the java 8 lambda in favor of the anonymous class. Is that correct? > Create a way to calculate the Jacobian Matrix using a Differentiator > > > Key: MATH-1459 > URL: https://issues.apache.org/jira/browse/MATH-1459 > Project: Commons Math > Issue Type: Improvement >Affects Versions: 4.X >Reporter: adrian >Priority: Minor > Fix For: 4.X > > > Create a way to automatically calculate a Jacobian Matrix using a > Differentiator. > I have done this with a pull request, but would like feedback. > edit: https://github.com/apache/commons-math/pull/84 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] commons-lang pull request #329: Travis: Add Java 10 "Oracle JDK", Java 10 "O...
Github user asfgit closed the pull request at: https://github.com/apache/commons-lang/pull/329 ---
[jira] [Updated] (MATH-1461) Real DFT
[ https://issues.apache.org/jira/browse/MATH-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide updated MATH-1461: - Summary: Real DFT (was: Rea DFT) > Real DFT > > > Key: MATH-1461 > URL: https://issues.apache.org/jira/browse/MATH-1461 > Project: Commons Math > Issue Type: Improvement >Affects Versions: 3.6.1 > Environment: Used on: > * Debian 9 > * x86 AMD64 > * ItelliJ Idea >Reporter: Davide >Priority: Major > > I've noticed that since the DFT on real inputs produces half the size of the > inputs (since they are real), then, maybe, the > FastFourierTransformation.transform(double[], TransformType) should return an > half sized Complex array, but it still return a Complex array of the same > size of the input double array. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MATH-1461) Rea DFT
Davide created MATH-1461: Summary: Rea DFT Key: MATH-1461 URL: https://issues.apache.org/jira/browse/MATH-1461 Project: Commons Math Issue Type: Improvement Affects Versions: 3.6.1 Environment: Used on: * Debian 9 * x86 AMD64 * ItelliJ Idea Reporter: Davide I've noticed that since the DFT on real inputs produces half the size of the inputs (since they are real), then, maybe, the FastFourierTransformation.transform(double[], TransformType) should return an half sized Complex array, but it still return a Complex array of the same size of the input double array. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FILEUPLOAD-119) The encryption & decryption of uploaded file
[ https://issues.apache.org/jira/browse/FILEUPLOAD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475943#comment-16475943 ] David Carboni commented on FILEUPLOAD-119: -- Thanks for the reply Jochen, I respect your view on what should be in or out of the library. I've occasionally had to make calls on what should be in or out of libraries I've built, even when I've had willing contribution offers, (in my case from colleagues I could talk things through with). I believe a clear understanding of intent and scope is key to the integrity of a library and support that. Thanks for the offer to support the ability for an encrypted implementation to work with FileUpload. Having built a range of options (specifically implementing FileItem) the current implementation of FileUpload enables this to be done without breaking the interface. I'll update the release of my original companion library above. Is there a way to offer this as an option for people who do want the additional capability? Thanks David > The encryption & decryption of uploaded file > > > Key: FILEUPLOAD-119 > URL: https://issues.apache.org/jira/browse/FILEUPLOAD-119 > Project: Commons FileUpload > Issue Type: New Feature > Environment: Windows/Linux >Reporter: inderjeet >Priority: Critical > > Hi, > Can we upload the file in the encypted format and later decrypt it to show > the file so that noone can directly open the file from the disk space (hard > disk) where i have uploaded the file usinf fileUpload functionality. This is > the major concern for our project ? > Is there any external library which can do this for us even just after we > upload the file through this API ? > Thanks & Regards > Inderjeet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (COMPRESS-453) Facing block overrun error while building TensorFlow
[
https://issues.apache.org/jira/browse/COMPRESS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated COMPRESS-453:
--
External issue URL: https://github.com/tensorflow/tensorflow/issues/16862
External issue ID: 16862
> Facing block overrun error while building TensorFlow
>
>
> Key: COMPRESS-453
> URL: https://issues.apache.org/jira/browse/COMPRESS-453
> Project: Commons Compress
> Issue Type: Bug
> Components: Compressors
>Affects Versions: 1.9, 1.16.1
> Environment: Linux Ubuntu 16.04 s390x
>Reporter: Namrata Bhave
>Priority: Major
>
> Building TensorFlow master using Bazel v0.12.0.
> Facing build issue immediately with error:
> {{ERROR: /home/jenkins/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
> no such package '@nasm//': java.io.IOException: block overrun and referenced
> by '//tensorflow/tools/pip_package:licenses'}}
> {{ ERROR: Analysis of target
> '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no
> such package '@nasm//': java.io.IOException: block overrun}}
> This is intermittent. Sometimes the build goes ahead. Also observed this
> error once:
> {{ERROR: /home/test/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
> such package '@nasm//': java.io.IOException: Error detected parsing the
> header and referenced by '//tensorflow/tools/pip_package:licenses'ERROR:
> Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed;
> build aborted: no such package '@nasm//': java.io.IOException: Error detected
> parsing the header}}
> Can someone please help in resolving this?
> Getting this error with AdoptJDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (COMPRESS-453) Facing block overrun error while building TensorFlow
[
https://issues.apache.org/jira/browse/COMPRESS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475892#comment-16475892
]
Stefan Bodewig edited comment on COMPRESS-453 at 5/15/18 2:22 PM:
--
Actually it is Compress, please see
https://github.com/tensorflow/tensorflow/issues/16862 for reference.
The build process uses Compress to deal with a tar.gz downloaded by the process
- and the exception is raised by BZipCompressorInputStream
[~bhavenamrata] we need the bzip2 file that is causing the exception. Without
that we won't be able to help.
was (Author: bodewig):
Actually it is Compress, please see
https://github.com/tensorflow/tensorflow/issues/16862 for reference.
The build process uses Compress to deal with a tar.gz downloaded by the process
- and the exception is raised by BZipCompressorInputStream
[~bhavenamrata] we need the bzip2 that is causing the exception. Without that
we won't be able to help.
> Facing block overrun error while building TensorFlow
>
>
> Key: COMPRESS-453
> URL: https://issues.apache.org/jira/browse/COMPRESS-453
> Project: Commons Compress
> Issue Type: Bug
> Components: Compressors
>Affects Versions: 1.9, 1.16.1
> Environment: Linux Ubuntu 16.04 s390x
>Reporter: Namrata Bhave
>Priority: Major
>
> Building TensorFlow master using Bazel v0.12.0.
> Facing build issue immediately with error:
> {{ERROR: /home/jenkins/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
> no such package '@nasm//': java.io.IOException: block overrun and referenced
> by '//tensorflow/tools/pip_package:licenses'}}
> {{ ERROR: Analysis of target
> '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no
> such package '@nasm//': java.io.IOException: block overrun}}
> This is intermittent. Sometimes the build goes ahead. Also observed this
> error once:
> {{ERROR: /home/test/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
> such package '@nasm//': java.io.IOException: Error detected parsing the
> header and referenced by '//tensorflow/tools/pip_package:licenses'ERROR:
> Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed;
> build aborted: no such package '@nasm//': java.io.IOException: Error detected
> parsing the header}}
> Can someone please help in resolving this?
> Getting this error with AdoptJDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (COMPRESS-453) Facing block overrun error while building TensorFlow
[
https://issues.apache.org/jira/browse/COMPRESS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Bodewig reopened COMPRESS-453:
-
Actually it is Compress, please see
https://github.com/tensorflow/tensorflow/issues/16862 for reference.
The build process uses Compress to deal with a tar.gz downloaded by the process
- and the exception is raised by BZipCompressorInputStream
[~bhavenamrata] we need the bzip2 that is causing the exception. Without that
we won't be able to help.
> Facing block overrun error while building TensorFlow
>
>
> Key: COMPRESS-453
> URL: https://issues.apache.org/jira/browse/COMPRESS-453
> Project: Commons Compress
> Issue Type: Bug
> Components: Compressors
>Affects Versions: 1.9, 1.16.1
> Environment: Linux Ubuntu 16.04 s390x
>Reporter: Namrata Bhave
>Priority: Major
>
> Building TensorFlow master using Bazel v0.12.0.
> Facing build issue immediately with error:
> {{ERROR: /home/jenkins/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
> no such package '@nasm//': java.io.IOException: block overrun and referenced
> by '//tensorflow/tools/pip_package:licenses'}}
> {{ ERROR: Analysis of target
> '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no
> such package '@nasm//': java.io.IOException: block overrun}}
> This is intermittent. Sometimes the build goes ahead. Also observed this
> error once:
> {{ERROR: /home/test/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
> such package '@nasm//': java.io.IOException: Error detected parsing the
> header and referenced by '//tensorflow/tools/pip_package:licenses'ERROR:
> Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed;
> build aborted: no such package '@nasm//': java.io.IOException: Error detected
> parsing the header}}
> Can someone please help in resolving this?
> Getting this error with AdoptJDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (COMPRESS-453) Facing block overrun error while building TensorFlow
[
https://issues.apache.org/jira/browse/COMPRESS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMPRESS-453.
---
Resolution: Invalid
Does not appear to be anything to do with Apache Commons Compress.
Nor even Apache.
> Facing block overrun error while building TensorFlow
>
>
> Key: COMPRESS-453
> URL: https://issues.apache.org/jira/browse/COMPRESS-453
> Project: Commons Compress
> Issue Type: Bug
> Components: Compressors
>Affects Versions: 1.9, 1.16.1
> Environment: Linux Ubuntu 16.04 s390x
>Reporter: Namrata Bhave
>Priority: Major
>
> Building TensorFlow master using Bazel v0.12.0.
> Facing build issue immediately with error:
> {{ERROR: /home/jenkins/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
> no such package '@nasm//': java.io.IOException: block overrun and referenced
> by '//tensorflow/tools/pip_package:licenses'}}
> {{ ERROR: Analysis of target
> '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no
> such package '@nasm//': java.io.IOException: block overrun}}
> This is intermittent. Sometimes the build goes ahead. Also observed this
> error once:
> {{ERROR: /home/test/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
> such package '@nasm//': java.io.IOException: Error detected parsing the
> header and referenced by '//tensorflow/tools/pip_package:licenses'ERROR:
> Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed;
> build aborted: no such package '@nasm//': java.io.IOException: Error detected
> parsing the header}}
> Can someone please help in resolving this?
> Getting this error with AdoptJDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (COMPRESS-453) Facing block overrun error while building TensorFlow
[
https://issues.apache.org/jira/browse/COMPRESS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Namrata Bhave updated COMPRESS-453:
---
Description:
Building TensorFlow master using Bazel v0.12.0.
Facing build issue immediately with error:
{{ERROR: /home/jenkins/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
such package '@nasm//': java.io.IOException: block overrun and referenced by
'//tensorflow/tools/pip_package:licenses'}}
{{ ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package'
failed; build aborted: no such package '@nasm//': java.io.IOException: block
overrun}}
This is intermittent. Sometimes the build goes ahead. Also observed this error
once:
{{ERROR: /home/test/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
such package '@nasm//': java.io.IOException: Error detected parsing the header
and referenced by '//tensorflow/tools/pip_package:licenses'ERROR: Analysis of
target '//tensorflow/tools/pip_package:build_pip_package' failed; build
aborted: no such package '@nasm//': java.io.IOException: Error detected parsing
the header}}
Can someone please help in resolving this?
Getting this error with AdoptJDK 8.
was:
Building TensorFlow master using Bazel v0.12.0.
Facing build issue immediately with error:
ERROR:
/home/jenkins/workspace/TensorFlow_IBMZ_CI/TensorFlow_SC/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
no such package '@nasm//': java.io.IOException: block overrun and referenced
by '//tensorflow/tools/pip_package:licenses'
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package'
failed; build aborted: no such package '@nasm//': java.io.IOException: block
overrun
This is intermittent. Sometimes the build goes ahead. Also observed this error
once:
{quote}ERROR:
/home/test/TF_another/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
such package '@nasm//': java.io.IOException: Error detected parsing the header
and referenced by '//tensorflow/tools/pip_package:licenses'ERROR: Analysis of
target '//tensorflow/tools/pip_package:build_pip_package' failed; build
aborted: no such package '@nasm//': java.io.IOException: Error detected parsing
the header
{quote}
Can someone please help in resolving this?
Getting this error with AdoptJDK 8.
> Facing block overrun error while building TensorFlow
>
>
> Key: COMPRESS-453
> URL: https://issues.apache.org/jira/browse/COMPRESS-453
> Project: Commons Compress
> Issue Type: Bug
> Components: Compressors
>Affects Versions: 1.9, 1.16.1
> Environment: Linux Ubuntu 16.04 s390x
>Reporter: Namrata Bhave
>Priority: Major
>
> Building TensorFlow master using Bazel v0.12.0.
> Facing build issue immediately with error:
> {{ERROR: /home/jenkins/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
> no such package '@nasm//': java.io.IOException: block overrun and referenced
> by '//tensorflow/tools/pip_package:licenses'}}
> {{ ERROR: Analysis of target
> '//tensorflow/tools/pip_package:build_pip_package' failed; build aborted: no
> such package '@nasm//': java.io.IOException: block overrun}}
> This is intermittent. Sometimes the build goes ahead. Also observed this
> error once:
> {{ERROR: /home/test/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
> such package '@nasm//': java.io.IOException: Error detected parsing the
> header and referenced by '//tensorflow/tools/pip_package:licenses'ERROR:
> Analysis of target '//tensorflow/tools/pip_package:build_pip_package' failed;
> build aborted: no such package '@nasm//': java.io.IOException: Error detected
> parsing the header}}
> Can someone please help in resolving this?
> Getting this error with AdoptJDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (COMPRESS-453) Facing block overrun error while building TensorFlow
Namrata Bhave created COMPRESS-453:
--
Summary: Facing block overrun error while building TensorFlow
Key: COMPRESS-453
URL: https://issues.apache.org/jira/browse/COMPRESS-453
Project: Commons Compress
Issue Type: Bug
Components: Compressors
Affects Versions: 1.16.1, 1.9
Environment: Linux Ubuntu 16.04 s390x
Reporter: Namrata Bhave
Building TensorFlow master using Bazel v0.12.0.
Facing build issue immediately with error:
ERROR:
/home/jenkins/workspace/TensorFlow_IBMZ_CI/TensorFlow_SC/tensorflow/tensorflow/tools/pip_package/BUILD:117:1:
no such package '@nasm//': java.io.IOException: block overrun and referenced
by '//tensorflow/tools/pip_package:licenses'
ERROR: Analysis of target '//tensorflow/tools/pip_package:build_pip_package'
failed; build aborted: no such package '@nasm//': java.io.IOException: block
overrun
This is intermittent. Sometimes the build goes ahead. Also observed this error
once:
{quote}ERROR:
/home/test/TF_another/tensorflow/tensorflow/tools/pip_package/BUILD:117:1: no
such package '@nasm//': java.io.IOException: Error detected parsing the header
and referenced by '//tensorflow/tools/pip_package:licenses'ERROR: Analysis of
target '//tensorflow/tools/pip_package:build_pip_package' failed; build
aborted: no such package '@nasm//': java.io.IOException: Error detected parsing
the header
{quote}
Can someone please help in resolving this?
Getting this error with AdoptJDK 8.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FILEUPLOAD-119) The encryption & decryption of uploaded file
[ https://issues.apache.org/jira/browse/FILEUPLOAD-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475682#comment-16475682 ] Jochen Wiedmann commented on FILEUPLOAD-119: Hi, David, while I agree with you wholeheartedly on the importance of encryption, I still fail to bring it into the picture for FileUpload as a library. You are welcome to provide another library, sitting on top of FileUpload, which does offer all that you feel important. In fact, it the current implementation of FileUpload prevents you from doing so (say, due to missing features), then I'd take it upon me to provide the necessary extensions. However, that's as far as I will offer. Sorry, Jochen > The encryption & decryption of uploaded file > > > Key: FILEUPLOAD-119 > URL: https://issues.apache.org/jira/browse/FILEUPLOAD-119 > Project: Commons FileUpload > Issue Type: New Feature > Environment: Windows/Linux >Reporter: inderjeet >Priority: Critical > > Hi, > Can we upload the file in the encypted format and later decrypt it to show > the file so that noone can directly open the file from the disk space (hard > disk) where i have uploaded the file usinf fileUpload functionality. This is > the major concern for our project ? > Is there any external library which can do this for us even just after we > upload the file through this API ? > Thanks & Regards > Inderjeet -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DAEMON-243) Support for Failure Recovery
[ https://issues.apache.org/jira/browse/DAEMON-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Abrarov updated DAEMON-243: - Attachment: (was: fail_without_stopped_status.diff) > Support for Failure Recovery > > > Key: DAEMON-243 > URL: https://issues.apache.org/jira/browse/DAEMON-243 > Project: Commons Daemon > Issue Type: New Feature > Components: Procrun >Affects Versions: 1.0.10 > Environment: MS Windows >Reporter: Peter Ehrbar >Priority: Minor > Attachments: fail_without_stopped_status.diff > > > The MS Windows Service Controller provides functionality to perform some > basic failure recovery actions: Restart service or execute any command or > restart the machine. This can be configured using the Service Controller GUI > or in a shell with SC.EXE (commands FAILURE and FAILUREFLAG). > It would be convenient if this could be configured also using procrun. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (DAEMON-243) Support for Failure Recovery
[ https://issues.apache.org/jira/browse/DAEMON-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marat Abrarov updated DAEMON-243: - Attachment: fail_without_stopped_status.diff > Support for Failure Recovery > > > Key: DAEMON-243 > URL: https://issues.apache.org/jira/browse/DAEMON-243 > Project: Commons Daemon > Issue Type: New Feature > Components: Procrun >Affects Versions: 1.0.10 > Environment: MS Windows >Reporter: Peter Ehrbar >Priority: Minor > Attachments: fail_without_stopped_status.diff > > > The MS Windows Service Controller provides functionality to perform some > basic failure recovery actions: Restart service or execute any command or > restart the machine. This can be configured using the Service Controller GUI > or in a shell with SC.EXE (commands FAILURE and FAILUREFLAG). > It would be convenient if this could be configured also using procrun. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
