Re: Request for Edit Permissions on Confluence

Granted. Thanks for contributing! -sz On 4/2/20, 11:18 AM, "Goggins, Connor" wrote: Hello, I would like to be given edit permissions on the Apache MXNet Confluence wiki so that I can add important documentation

Re: MXNet CD pipelines cost savings

+dev@ -sz On Feb 10, 2020, at 1:35 PM, Zha, Sheng wrote:  As already stated in the public threads, I’ve vetoed the CodeBuild solution from becoming the long term solution as it’s not publicly manageable. As communicated before, the team should have put efforts in maintaining and fixing

Acknowledgement for 1.3.0 release (was: Re: [RESULT][VOTE] Release MXNet version 1.3.0)

Kolychev, Sergey Sokolov, Sheng Zha, Sheng-Ying, Simon, Sina Afrooze, solin319, Soonhwan-Kwon, Steffen Rochel, Taliesin Beynon, Tao Lv, Thom Lane, ThomasDelteil, Tianqi Chen, Tong He, Wei Wu, Wen-Yang Chu, Xingjian Shi, Xinyu Chen, yifeim, Yizhi Liu, Yu-Xiang Wang, Yuan Tang, Yuntao Chen, Zhi

Re: [DISCUSS] Subscribe dev@ to Github Activities?

My intention is really just to bridge the gap between so much happening on github v.s. "whatever didn't happen on dev list didn't happen". Also, since dev@ is intended to be an asynchronous way for community to follow technical conversations, there wasn't really a requirement for anyone to read

Re: move entirely to CMakefiles for building MXNet, drop Makefiles

You can set rpath to $${ORIGIN} to make the path where the libmxnet.so resides a path to look up. -sz - Sent by my thumb > On Mar 7, 2018, at 7:45 AM, Pedro Larroy wrote: > > About libomp.so > > This is giving me some problems when creating a pip package for

Re: dmlc packages into 3rdpary

Some existing release pipelines may rely on the folder structure for caching, so this needs to be coordinated. Best regards, -sz On 1/19/18, 11:51 AM, "Tianqi Chen" wrote: I think it is fine either way as it won’t affect the build status of the projects.

Re: Protected master needs to be turned off

ot; <cjolivie...@gmail.com>: > Revised: > > > +1 at least until new CI is implemented. Then reevaluate. > > On Sun, Nov 19, 2017 at 1:07 PM Chris Olivier <cjolivie...@gmail.com> > wrote: > > > +1 > > > >

Re: AWS contributing ONNX-MXNet

Hi Hagay, > But why assume this was done on intention? Given that you mentioned that you talked to Mu on this, would it be right to assume that you have paid sufficient attention and have been extra careful on acknowledgements already? > import_onnx.py [1] is the only one that seem to have

Re: [RESULT][VOTE] Release Apache MXNet (incubating) Version 0.12.0.rc0

Who’s executing? Best regards, -sz On 10/24/17, 4:50 PM, "Meghna Baijal" wrote: Hi All, The vote for releasing Apache MXNet (incubating) 0.12.0 RC0 passed with the following result - +1 binding - Chris Olivier - Suneel Marthi - Indhu

Re: Improving and rationalizing unit tests

Here’s a package that may help us on flaky tests: https://pypi.python.org/pypi/flaky. It can retry tests that are marked flaky and can pass or fail based on specified threshold. In the short term we can use this to pass tests that are not 100% reliable. Best regards, -sz On 10/16/17, 10:32

Re: MXNet Slack channel

Invited. Best regards, -sz On 9/28/17, 12:31 PM, "Jin Sun" wrote: Please give me an invite as well. Thanks, Jin 2017-09-28 12:14 GMT-07:00 Jean K : > Hi, > I would like to join the MXNet Slack Channel. >

Re: Apache MXNet build failures are mostly valid - verify before merge

t; > > > > > we > > > > > > > > have > > > > > > > > > > not > > > > > > > > > > > seen any case where instance died due to high memory > > usage > > > or > &g

Re: Apache MXNet build failures are mostly valid - verify before merge

Just one thing: please don’t disable more tests or just raise the tolerance thresholds. Best regards, -sz On 8/31/17, 10:45 AM, "Madan Jampani" wrote: +1 Before we can turn protected mode I feel we should first get to a stable CI pipeline. Sandeep is