I am looking into it.
Could you provide the shape of NDArrayIter and minimal reproducible code?
Thank you so much!
Alfredo Luque 於 2018年9月11日 週二 下午6:05寫道：
> Looks like https://github.com/apache/incubator-mxnet/pull/12285 broke a
> ton
> of our test cases iterating over 3D NDArray instances
do you log on finalize() if the object wasn’t properly freed (ie
NDArray.finalize())? is that available in Scala?
On Tue, Sep 11, 2018 at 6:12 PM Qing Lan wrote:
> Nice document! Way better than current .dispose() in Scala!
>
> Thanks,
> Qing
>
> On 9/11/18, 6:04 PM, "Chris Olivier" wrote:
>
Nice document! Way better than current .dispose() in Scala!
Thanks,
Qing
On 9/11/18, 6:04 PM, "Chris Olivier" wrote:
wow, incredible document!
On Tue, Sep 11, 2018 at 2:37 PM Naveen Swamy wrote:
> Hi All,
>
> I am working on managing Off-Heap Memory Management
wow, incredible document!
On Tue, Sep 11, 2018 at 2:37 PM Naveen Swamy wrote:
> Hi All,
>
> I am working on managing Off-Heap Memory Management and have written a
> proposal here based on my prototype and research I did.
>
> Please review the doc and provide your feedback ?
>
>
Looks like https://github.com/apache/incubator-mxnet/pull/12285 broke a ton
of our test cases iterating over 3D NDArray instances (eg; MNIST) by
creating an index out of range.
Stacktrace:
.com/airbnb/bighead/python/bighead/ml_frameworks/mxnet/gluon.py", line
434, in transform
for batch in
Qing helped test by excluding the bundle/source. It still creates 2 repos
in Staging. I am not sure if Maven Version or some other maven-plugin
difference is causing this issue, there was no issue publishing to
Linux-CPU and Linux-GPU from the same code.
For now, I have manually uploaded the
Hi All,
I am working on managing Off-Heap Memory Management and have written a
proposal here based on my prototype and research I did.
Please review the doc and provide your feedback ?
https://cwiki.apache.org/confluence/display/MXNET/JVM+Memory+Management
I had offline discussion with a few
that seems reasonable. I also asked this question on d...@maven.apache.org
to see if there is anything obvious that we missed.
https://lists.apache.org/thread.html/def6e5c6c47ab2f39592a1fe060b6cfd0008d303a2b5c814545d231b@%3Cdev.maven.apache.org%3E
On Tue, Sep 11, 2018 at 11:25 AM, Carin Meier
I would suggest trying
* Remove bundle/source jar from 1.3.0 and attempt publishing OSX package.
and seeing if that solves the problem and allows publishing to staging.
If it does work then it helps to identity the cause.
If the effort does not take to long. I would recommend timeboxing the
hey all,
I am working on publishing the 1.3.0 Scala package to Maven and
encountering a error when I am about to Close the Repo on Nexus. When I
publish the OSX package to Staging, the artifacts gets split into 2
repositories and when I close[1] the repo(to make it available for use) it
fails
Done, here is the ticket:
https://issues.apache.org/jira/browse/INFRA-17004
On 10.09.2018 14:49, Marco de Abreu wrote:
Hello Sebastian,
could you please file a ticket with Apache Infra to enable Travis CI for
our main repository? The discussion thread is available at
FYI GitHub is having issues today. It's severe enough that it's blocking my
ability to validate PRs. I'm sure it will be resolved soon, but it might
be a good day to read a few papers ;-).
https://status.github.com/messages
-Kellen
12 matches
Mail list logo
