Error after updating to 1.0.0-alpha3

[Uwe Jäger]

Hi,

I just updated to alpha3 (actually composer did while update symfony-cmf/block-bundle) and face an error that wasn't there before (not finding a node that should be there actually). Do I have to update any other packages (phpcr, odm etc.) to have everything working again? In the current setup doctrine:phpcr:dump doesn't work anymore, too.

Any help appreciated ...

Cheers

Uwe

[Uwe Jäger]

Hi David,

looks like the change in Session::getNodeByIdentifier (https://github.com/jackalope/jackalope/commit/b332120db672f58d3046cd4241d361ad8bc50603) is responsible for the change. Now it really expects an UUID, before you could also pass in a path and it worked. The DumpCommand actually relies on that behaviour. Will do a PR for phpcr-utils next. My guess is that the other issue in the odm is also related to that, but I haven't checked yet ...

Cheers

Uwe

---------- Forwarded message ----------
From: David Buchmann <da...@liip.ch>
Date: 2013/3/26
Subject: Re: [Jackalope] Error after updating to 1.0.0-alpha3
To: Uwe Jäger <uwe...@gmail.com>


hi uwe,

hm, bad. travis and i agree that all tests still succeed. so it would
mean there is something not covered by tests. i have to leave now, but
can try to update the sandbox tomorrow.
if i understand correctly, you don't get exceptions but simple no
content. how does dump not work? exceptions or just empty result?

if you have any exception trace that would of course be helpful ;-)

we don't use any of the new things in the cmf yet, so you can also fix
to < 1.0.0-alpha3 for now to get an update that hopefully works (unless
it was not this change that broke things)

cheers,david

> --
> You received this message because you are subscribed to the Google
> Groups "Jackalope" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jackalope-de...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
Liip AG // Agile Web Development // T +41 26 422 25 11
CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch

[Uwe Jäger]

Hi,

so the other error was my own mistake probably just showing now after the update. I found another wrong usage of Session::getNodeByIdenifier in the DoctrinePHPCRBundle: https://github.com/doctrine/DoctrinePHPCRBundle/issues/47

Cheers

Uwe

2013/3/26 Uwe Jäger <uwe...@gmail.com>

[David Buchmann]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

thanks a lot uwe for finding and fixing the issue.


indeed, the PHPCR api specified that these are different things, but
we had some weird things in jackalope mixing the two up and then
needing to use UUIDHelper::isUUID to sort it out again. but that was
an implemenation specific pecularity, i would expect that it does not
work with midgard2 phpcr for example.

cheers,david

Am 26.03.2013 22:13, schrieb Uwe J�ger:
> Hi,
>
> so the other error was my own mistake probably just showing now
> after the update. I found another wrong usage of
> Session::getNodeByIdenifier in the DoctrinePHPCRBundle:
> https://github.com/doctrine/DoctrinePHPCRBundle/issues/47
>
> Cheers Uwe
>
>

> 2013/3/26 Uwe J�ger <uwe...@gmail.com <mailto:uwe...@gmail.com>>

>
> Hi David,
>
> looks like the change in Session::getNodeByIdentifier
> (https://github.com/jackalope/jackalope/commit/b332120db672f58d3046cd4241d361ad8bc50603)
>
>
is responsible for the change. Now it really expects an UUID, before
> you could also pass in a path and it worked. The DumpCommand
> actually relies on that behaviour. Will do a PR for phpcr-utils
> next. My guess is that the other issue in the odm is also related
> to that, but I haven't checked yet ...
>
> Cheers Uwe
>
>

> ---------- Forwarded message ---------- From: *David Buchmann*
> <da...@liip.ch <mailto:da...@liip.ch>> Date: 2013/3/26 Subject: Re:
> [Jackalope] Error after updating to 1.0.0-alpha3 To: Uwe J�ger
> <uwe...@gmail.com <mailto:uwe...@gmail.com>>

>
>
> hi uwe,
>
> hm, bad. travis and i agree that all tests still succeed. so it
> would mean there is something not covered by tests. i have to leave
> now, but can try to update the sandbox tomorrow. if i understand
> correctly, you don't get exceptions but simple no content. how does
> dump not work? exceptions or just empty result?
>
> if you have any exception trace that would of course be helpful
> ;-)
>
> we don't use any of the new things in the cmf yet, so you can also
> fix to < 1.0.0-alpha3 for now to get an update that hopefully works
> (unless it was not this change that broke things)
>
> cheers,david
>

> Am 26.03.2013 17 <tel:26.03.2013%2017>:29, schrieb Uwe J�ger:
>> Hi,
>>
>> I just updated to alpha3 (actually composer did while update
>> symfony-cmf/block-bundle) and face an error that wasn't there
>> before (not finding a node that should be there actually). Do I
>> have to
> update
>> any other packages (phpcr, odm etc.) to have everything working
>> again? In the current setup doctrine:phpcr:dump doesn't work
>> anymore, too.
>>
>> Any help appreciated ...
>>
>> Cheers Uwe
>>
>> -- You received this message because you are subscribed to the
>> Google Groups "Jackalope" group. To unsubscribe from this group
>> and stop receiving emails from it, send an email to
>> jackalope-de...@googlegroups.com

> <mailto:jackalope-dev%2Bunsu...@googlegroups.com>.

>> For more options, visit
>> https://groups.google.com/groups/opt_out.
>>
>>
>
> -- Liip AG // Agile Web Development // T +41 26 422 25 11

> <tel:%2B41%2026%20422%2025%2011> CH-1700 Fribourg // PGP 0xA581808B
> // www.liip.ch <http://www.liip.ch>
>
>

- --

Liip AG // Agile Web Development // T +41 26 422 25 11
CH-1700 Fribourg // PGP 0xA581808B // www.liip.ch

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJRUhHpAAoJED/JtliXIA4s1EMIAJItUNH+8XreucsZ3UT5mVdx
5wbf+/1hga+hIwL+qSNZUcnQIMt2Yy3PJZbfXDvNc99WZ1yZcHJeLNf+NI4KBoNO
gqw+LoqHr3omRiq6iTmcin2W2QvHEnqxxuE1d3BHQXRKXy6pjMt/XWih3vuEyTE+
KuqGzAFG0Co4AVrYkJQ425Kk6Th8USwnKGU+lBpBJfZ4KLrgkLLo7HInBAD2egVR
x28fPYarim/DBT/NndVuf1PINPHmSfUbATHCXQ9hsBnE1QdcNPcASiQ/WpVf5Y5J
RwxKNmXM+t55QXVjbZ/FMFxgvQFwE33EUP6N+mZuc9CAPP6moCXYqRGLuegxOSY=
=syeS
-----END PGP SIGNATURE-----