Re: S3 Writes using SIG4 Authentication

I was looking at SIG4's documentation for S3 here earlier. The section on Chunked Upload confused me because it said I need to pass Content-Length header in the request. I now realize that I was using the terms `chunked

Re: Assign JIRA issue

yeah I fixed that On Wed, Mar 7, 2018 at 11:09 AM, Marco de Abreu < marco.g.ab...@googlemail.com> wrote: > Would it be possible to make tickets assigned to Nobody by default? > > On Wed, Mar 7, 2018 at 6:15 PM, Chris Olivier > wrote: > > > Please assign JIRA issue to

Re: Assign JIRA issue

Would it be possible to make tickets assigned to Nobody by default? On Wed, Mar 7, 2018 at 6:15 PM, Chris Olivier wrote: > Please assign JIRA issue to yourself after creating. I think it was > assigning to me for some reason. Just click "assign to me" link. > > If you

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

I also see this as a big advantage in terms of transparency. I personally will try to move away from any company internal issue trackers (except for confidential cases) and instead work on Jira that is being managed by the community. This allows everybody to see what is being worked on and gives

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

I am +1 for using JIRA. Managing bigger projects within MXNet on JIRA brings openness to the project. MXNet Users and the contributors also get a sense of where the project is heading. Bigger Tasks can be divided into sub-tasks which contributors can pick up small tasks based on their expertise on

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

The vote was discussed on private@ before the vote on dev@, and the vote went on for a very long time. There was ZERO resistance. No one "snuck" it in or "slipped it by". This, hopefully, phases out both SIM and tt, which are both are being used in ways that aren't what they're even designed

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

I'm not quite sure if I have enough background on reasons for or against this to vote in the next round, but my two cents: I didn't see much debate on why we need yet another tool for issues that we have to manually maintain...the vote kind of slid in there without many stakeholders realizing what

Re: S3 Writes using SIG4 Authentication

Multi-part upload with finalization seems like a good approach for this problem. Bhavin Thaker. On Wed, Mar 7, 2018 at 7:45 AM Naveen Swamy wrote: > Rahul, > IMO It is not Ok to write to a local file before streaming, you have to > consider security implications such as: >

Assign JIRA issue

Please assign JIRA issue to yourself after creating. I think it was assigning to me for some reason. Just click "assign to me" link. If you don't have permissions, please email me directly (or even better, ping on slack) and I will add you to a permission group (let me know if you're a

Re: S3 Writes using SIG4 Authentication

Rahul, IMO It is not Ok to write to a local file before streaming, you have to consider security implications such as: 1) will your local file be encrypted(encryption at rest) 2) what happens if the process crashes, you will have to make sure the local file is deleted in failure and process exit

Re: S3 Writes using SIG4 Authentication

Hi Rahul, Rahul> Is it okay to buffer it to a local file, and then upload this file to S3 at the end? Short answer: Yes. S3 is object storage. See: https://en.m.wikipedia.org/wiki/Object_storage The granularity of access for object storage is an object. This is different from a filesystem or

Re: [RESULT][VOTE] tracking code changes with JIRA by associating pull requests

Would it be possible to add the instruction to the PR template (along with a link to Jira) in order to provide users with an easy way to create an issue if required. -Marco On Wed, Mar 7, 2018 at 6:34 AM, Chris Olivier wrote: > Eric, > > while you may not be, most people

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: move entirely to CMakefiles for building MXNet, drop Makefiles

About libomp.so This is giving me some problems when creating a pip package for installing on Jetson. I'm thinking that in this case would be better to compile with -fopenmp. I tried adding libomp.so to the pip package next to libmxnet.so and still I couldn't load the library... Any ideas?