Hello Om,
I raised a JIRA issue (https://issues.apache.org/jira/browse/FLEX-33539) on the
installer about a month ago. It could be unrelated but maybe not. If you push
through any fixes on this please let me know and I can test against this
problem anyway.
All the best,
Mick
On Jun 11, 2013, at 1:10 PM, OmPrakash Muppirala <bigosma...@gmail.com> wrote:
> This is the relevant function (I dint write it) We essentially keep
> calling update() and in the end call complete() I have never seen this
> fail before.
>
> =================================================================================
> private function fileStreamOpenHandler(event:Event):void
> {
> var data:ByteArray = new ByteArray();
> _fileStream.readBytes(data, 0, _fileStream.bytesAvailable);
> if (event is ProgressEvent)
> {
> _md5Stream.update(data);
> dispatchEvent(event.clone());
> }
> else
> {
> if (event.type == Event.COMPLETE)
> {
> _fileIsVerified = (_md5Stream.complete(data) == _remoteMD5Value);
> _callback();
> }
> }
> }
> =================================================================================
>
> Thanks,
> Om
>
> On Tue, Jun 11, 2013 at 11:57 AM, Alex Harui <aha...@adobe.com> wrote:
>
>> Did you verify the number of bytes you are sending in to MD5Stream and
>> that you've reset ByteArray.position before doing so?
>>
>> -Alex
>>
>> On 6/11/13 11:22 AM, "OmPrakash Muppirala" <bigosma...@gmail.com> wrote:
>>
>>> I have been working on getting the nightly builds working with the
>>> Installer. If I invoke the Installer from the command line like this:
>>>
>>> C:\Program Files (x86)\Apache Flex\Apache Flex SDK Installer>"Apache Flex
>>> SDK Installer.exe" -config="
>>>
>> http://people.apache.org/~bigosmallm/sdk-nightly/nightly-sdk-installer-con
>>> fig.xml
>>> "
>>>
>>> The installer loads the config from
>>>
>> http://people.apache.org/~bigosmallm/sdk-nightly/nightly-sdk-installer-con
>>> fig.xmland
>>> loads the sdk binary artifact from
>>>
>> https://builds.apache.org/job/flex-sdk_release/lastSuccessfulBuild/artifac
>>> t/out/
>>>
>>> So far so good. The problem comes up with the MD5 check occurs. I have
>>> manually verified that that the MD5 checksum of the downloaded file
>>> matches
>>> exactly that of the generated file. But, for some reason, the MD5Stream
>>> class generates a different MD5 checksum. As a result, the installation
>>> is
>>> aborted.
>>>
>>> Can someone test this independently and see if you are having similar
>>> problems as well?
>>>
>>> Any ideas why this could be happening?
>>>
>>> Thanks,
>>> Om
>>
>>
