Bug #96502 for Artifactory-Client: Bug Report

Tue Jun 17 10:25:31 2014 victor_diec [...] mitel.com - Ticket created

Subject:	Bug Report
Date:	Tue, 17 Jun 2014 10:25:00 -0400
To:	bug-artifactory-client [...] rt.cpan.org
From:	"Diec, Victor" <victor_diec [...] mitel.com>

I would like to report a bug within the Artifactory Client perl module. I am currently using Artifactory-Client 0.5.0 and have noticed that there is a bug that occurs several times within the module. Furthermore, I have also noticed that this bug still exists within the newest release so I would like to report it. In the sub routines: item_properties, set_item_properties, and delete_item_properties, the path provided by the perl module is: << my $url = "$artifactory:$port/api/storage/$repository$path?properties="; Show quoted text

>>. However, with this path either a 403 or a 404 error is returned when

these subroutines are called. I made some adjustments to the original perl module and using this path: << my $url = "$artifactory:$port/*artifactory*/api/storage/$repository$path?properties="; Show quoted text

>>, I can successfully retrieve or manipulate item properties.

-- Victor Diec Email: victor_diec@mitel.com Phone: 613-592-5660 x72875 -- This e-mail (including any attachments) is for the sole use of the intended recipient(s) and may contain information that is confidential and/or protected by legal privilege. Any unauthorized review, use, copy, disclosure or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please notify Mitel immediately and destroy all copies of this e-mail. Mitel does not accept any liability for breach of security, error or virus that may result from the transmission of this message.

Fri Jun 20 00:10:18 2014 SYAGI [...] cpan.org - Correspondence added

Thank you for filing this bug. I'll look at this and update this bug. On Tue Jun 17 10:25:31 2014, victor_diec@mitel.com wrote: Show quoted text

> I would like to report a bug within the Artifactory Client perl > module. I > am currently using Artifactory-Client 0.5.0 and have noticed that > there is > a bug that occurs several times within the module. Furthermore, I have > also > noticed that this bug still exists within the newest release so I > would > like to report it. > > In the sub routines: item_properties, set_item_properties, and > delete_item_properties, the path provided by the perl module is: > << my $url = > "$artifactory:$port/api/storage/$repository$path?properties=";

> >> . However, with this path either a 403 or a 404 error is returned > >> when

> these subroutines are called. > > I made some adjustments to the original perl module and using this > path: > << my $url = > "$artifactory:$port/*artifactory*/api/storage/$repository$path?properties=";

> >> , I can successfully retrieve or manipulate item properties.

Fri Jun 20 00:10:18 2014 The RT System itself - Status changed from 'new' to 'open'

Fri Jun 20 00:20:26 2014 SYAGI [...] cpan.org - Correspondence added

Yes I missed the artifactory pathname as you described. Funny thing is my functional tests are passing, so my artifactory instance isn't complaining about the lack of artifactory keyword. In any event, I need to fix this as your artifactory instance is complaining. On Fri Jun 20 00:10:18 2014, SYAGI wrote: Show quoted text

> Thank you for filing this bug. I'll look at this and update this bug. > > On Tue Jun 17 10:25:31 2014, victor_diec@mitel.com wrote:

> > I would like to report a bug within the Artifactory Client perl > > module. I > > am currently using Artifactory-Client 0.5.0 and have noticed that > > there is > > a bug that occurs several times within the module. Furthermore, I > > have > > also > > noticed that this bug still exists within the newest release so I > > would > > like to report it. > > > > In the sub routines: item_properties, set_item_properties, and > > delete_item_properties, the path provided by the perl module is: > > << my $url = > > "$artifactory:$port/api/storage/$repository$path?properties=";

> > >> . However, with this path either a 403 or a 404 error is > > >> returned > > >> when

> > these subroutines are called. > > > > I made some adjustments to the original perl module and using this > > path: > > << my $url = > > "$artifactory:$port/*artifactory*/api/storage/$repository$path?properties=";

> > >> , I can successfully retrieve or manipulate item properties.

Fri Jun 20 01:38:24 2014 SYAGI [...] cpan.org - Correspondence added

Please give version 0.6.2 a spin and see if the issue persists. On Fri Jun 20 00:20:26 2014, SYAGI wrote: Show quoted text

> Yes I missed the artifactory pathname as you described. Funny thing > is my functional tests are passing, so my artifactory instance isn't > complaining about the lack of artifactory keyword. > > In any event, I need to fix this as your artifactory instance is > complaining. > > On Fri Jun 20 00:10:18 2014, SYAGI wrote:

> > Thank you for filing this bug. I'll look at this and update this > > bug. > > > > On Tue Jun 17 10:25:31 2014, victor_diec@mitel.com wrote:

> > > I would like to report a bug within the Artifactory Client perl > > > module. I > > > am currently using Artifactory-Client 0.5.0 and have noticed that > > > there is > > > a bug that occurs several times within the module. Furthermore, I > > > have > > > also > > > noticed that this bug still exists within the newest release so I > > > would > > > like to report it. > > > > > > In the sub routines: item_properties, set_item_properties, and > > > delete_item_properties, the path provided by the perl module is: > > > << my $url = > > > "$artifactory:$port/api/storage/$repository$path?properties=";

> > > >> . However, with this path either a 403 or a 404 error is > > > >> returned > > > >> when

> > > these subroutines are called. > > > > > > I made some adjustments to the original perl module and using this > > > path: > > > << my $url = > > > "$artifactory:$port/*artifactory*/api/storage/$repository$path?properties=";

> > > >> , I can successfully retrieve or manipulate item properties.

Fri Jun 20 01:38:25 2014 SYAGI [...] cpan.org - Status changed from 'open' to 'resolved'

Fri Jun 20 01:38:26 2014 SYAGI [...] cpan.org - Taken

Fri Jun 20 09:48:28 2014 victor_diec [...] mitel.com - Correspondence added

Subject:	Re: [rt.cpan.org #96502] Resolved: Bug Report
Date:	Fri, 20 Jun 2014 09:48:15 -0400
To:	bug-Artifactory-Client [...] rt.cpan.org
From:	"Diec, Victor" <victor_diec [...] mitel.com>

Thank you for fixing the artifactory pathnames in those subroutines. I have a question/concern regarding deployment of large artifacts or large artifact bundles. I am currently using your perl module to try to upload artifacts that have a size of 350 MB or over. In each attempt to deploy, the command line tells me that I have run "Out of Memory!" After doing some research online, a lot of people are saying that slurp does not upload large files well. Can you make amendments to your perl module to support large uploads or do you have any recommendations as to how to deploy large artifacts or bundles? Once again, I would like to thank you for providing the opportunity to use your perl module! Sincerely, On 20 June 2014 01:38, Satoshi Yagi via RT < bug-Artifactory-Client@rt.cpan.org> wrote: Show quoted text

> <URL: https://rt.cpan.org/Ticket/Display.html?id=96502 > > > According to our records, your request has been resolved. If you have any > further questions or concerns, please respond to this message. >

-- Victor Diec Email: victor_diec@mitel.com Phone: 613-592-5660 x72875 -- This e-mail (including any attachments) is for the sole use of the intended recipient(s) and may contain information that is confidential and/or protected by legal privilege. Any unauthorized review, use, copy, disclosure or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please notify Mitel immediately and destroy all copies of this e-mail. Mitel does not accept any liability for breach of security, error or virus that may result from the transmission of this message.

Fri Jun 20 19:13:07 2014 SYAGI [...] cpan.org - Correspondence added

I'll see what I can do. There is another bug, warning me of the use of File::Slurp module - which seems like the issue here. https://rt.cpan.org/Ticket/Display.html?id=95683 Please refer to the ticket above as I make updates to it. On Fri Jun 20 09:48:28 2014, victor_diec@mitel.com wrote: Show quoted text

> Thank you for fixing the artifactory pathnames in those subroutines. I > have a question/concern regarding deployment of large artifacts or large > artifact bundles. I am currently using your perl module to try to upload > artifacts that have a size of 350 MB or over. In each attempt to deploy, > the command line tells me that I have run "Out of Memory!" > > After doing some research online, a lot of people are saying that slurp > does not upload large files well. Can you make amendments to your perl > module to support large uploads or do you have any recommendations as to > how to deploy large artifacts or bundles? > > Once again, I would like to thank you for providing the opportunity to use > your perl module! > > Sincerely, > > > On 20 June 2014 01:38, Satoshi Yagi via RT < > bug-Artifactory-Client@rt.cpan.org> wrote: >

> > <URL: https://rt.cpan.org/Ticket/Display.html?id=96502 > > > > > According to our records, your request has been resolved. If you have any > > further questions or concerns, please respond to this message. > >

> > >