Restricted nodes may provide enough security for some use cases, but in my
opinion they don't provide enough for artifact publishing. An example would
be if there were a exploit available that worked against a Jenkins master.
In this case I think an attacker code still pivot to a secure node
Welcome Da, great to have you on board!
Am Di., 18. Dez. 2018, 02:35 hat Lv, Tao A geschrieben:
> Congrats Da! Thank you for the effort on bringing MKL-DNN to MXNet. It's
> really the footstone for the latter work and improvements.
>
> -Original Message-
> From: Tianqi Chen
Hi Kellen,
Firstly the restricted node is completely isolated to the PR-checking CI system
(physically) which is explained in here:
https://cwiki.apache.org/confluence/display/MXNET/Restricted+jobs+and+nodes.
What you are mentioning: the Public CIs are all having troubles if they are
public
Kellen, please see conversation [1] on previously published proposal re: maven
publishing pipeline. I think your concerns are valid and we should look into
security aspect of running our CI on a broader scope, not bound to just
artifact publishing.
I believe right now Qing's question is
Hi,
sorry for derailing the discussion another time (I'm slow to respond,
sorry) but I just wanted to give a little statement about the security
aspect of Jenkins.
Kellen is right that Jenkins is by its nature quite insecure due to the
high frequency of discovered security vulnerabilities. These
Congrats Da! Thank you for the effort on bringing MKL-DNN to MXNet. It's really
the footstone for the latter work and improvements.
-Original Message-
From: Tianqi Chen [mailto:tqc...@apache.org]
Sent: Tuesday, December 18, 2018 1:02 AM
To: dev@mxnet.incubator.apache.org
Subject:
Attempting to answer Qing's question
--
If you can digest the legal terms:
https://docs.nvidia.com/cuda/eula/index.html#distribution-requirements.
It sounds its OK("
1. Your application must have material additional functionality, beyond
the included portions of the SDK.")
but I not don't
Congratulation, Da!
Really thanks for your great supports and looking forward the more cooperation
together :)
> -Original Message-
> From: Tianqi Chen [mailto:tqc...@apache.org]
> Sent: Tuesday, December 18, 2018 1:02 AM
> To: dev@mxnet.incubator.apache.org
> Subject: [Annoucement]
Congrats Da!
On Mon, Dec 17, 2018 at 5:44 PM Marco de Abreu
wrote:
> Welcome Da, great to have you on board!
>
> Am Di., 18. Dez. 2018, 02:35 hat Lv, Tao A
> geschrieben:
>
> > Congrats Da! Thank you for the effort on bringing MKL-DNN to MXNet. It's
> > really the footstone for the latter work
I think it would be a good idea to do this in all the language bindings so that
error messages can be appropriate and familiar in the user’s language rather
than confusing exceptions coming from the c++ backend. Heres an issue I filed
for tracking:
Congrats!
On Mon, Dec 17, 2018 at 9:19 AM Steffen Rochel
wrote:
> Congratulation Da!
>
> On Mon, Dec 17, 2018 at 9:02 AM Tianqi Chen wrote:
>
> > Dear Community:
> >
> > Please join me to welcome Da Zheng as a new committer of the MXNet.
> >
> > Da is the main author of MKL-DNN integration and
Congrats Da.
On Mon, Dec 17, 2018, 7:20 PM Emani, Ashok Congratulations Da, well deserved!
>
> On 12/17/18, 9:02 AM, "Tianqi Chen" wrote:
>
> Dear Community:
>
> Please join me to welcome Da Zheng as a new committer of the MXNet.
>
> Da is the main author of MKL-DNN integration and
Congratulations Da, well deserved!
On 12/17/18, 9:02 AM, "Tianqi Chen" wrote:
Dear Community:
Please join me to welcome Da Zheng as a new committer of the MXNet.
Da is the main author of MKL-DNN integration and recently he champions the
control flow support. He is one
Dear community,
Currently me and Zach are working on the Automated-publish pipeline on Jenkins
which is a pipeline used to publish Maven packages and pip packages nightly
build. We are trying to use NVIDIA deb which could help us to build different
CUDA/CUDNN versions in the publish system.
I'm not in favour of publishing artifacts from any Jenkins based systems.
There are many ways to bundle artifacts and publish them from an automated
system. Why we would use a CI system like Jenkins for this task? Jenkins
frequently has security vulnerabilities and is designed to run arbitrary
Dear Community:
Please join me to welcome Da Zheng as a new committer of the MXNet.
Da is the main author of MKL-DNN integration and recently he champions the
control flow support. He is one of the few "explorer style" contributors of
the community, who we desperately need in this fast change
Congratulation Da!
On Mon, Dec 17, 2018 at 9:02 AM Tianqi Chen wrote:
> Dear Community:
>
> Please join me to welcome Da Zheng as a new committer of the MXNet.
>
> Da is the main author of MKL-DNN integration and recently he champions the
> control flow support. He is one of the few "explorer
Hello everyone,
As a contributor to Apache MXNet project, I wanted to ask the developer
community a few questions pertaining to Gluon Model Zoo API.
1. With regards to APIs for networks like - mobile nets, densenets,
resnets, squeezenets (note the case sensitivity of these APIs), they are
"mshadow is being deprecated."
Surprised to know that. Was it discussed before? Do we have any document to
tell contributors and developers about that?
-tao
-Original Message-
From: Chris Olivier [mailto:cjolivie...@gmail.com]
Sent: Monday, December 17, 2018 3:10 PM
To:
Hi Haochong
Welcome to MXNet, It's exciting to have additional hardware platforms
added and supported in the project.
The CI system for MXNet is donated by AWS to the project. We have a
small hardware lab with embedded physical hardware like ARM boards
including NVidia Jetson which we are
Hi Steffen
Added some notes in your PR for the release notes.
In particular, I'm a bit concerned about the status of topology aware
communication, since it has open issues and is not being tested in CI.
(The tests also fail). I think we should anounce it when it's working
properly and it's well
21 matches
Mail list logo
