Skip to content

can only throw objects #109

Closed
Closed

Description

@dbu
Q A
Bug? yes
New Feature? no
Version 1.8.0

Actual Behavior

Error: Can only throw objects
/home/travis/build/php-http/HttplugBundle/vendor/php-http/client-common/src/Deferred.php:129
/home/travis/build/php-http/HttplugBundle/vendor/php-http/client-common/src/PluginClient.php:87
/home/travis/build/php-http/HttplugBundle/Tests/Functional/ProfilingTest.php:96

Activity

  1. Nyholm commented on Sep 23, 2018

    @Nyholm
    Member
  2. Nyholm commented on Sep 23, 2018

    @Nyholm
    Member

    I think, the issue is that $this->state is not updated after we execute the callback.
    https://github.com/php-http/client-common/blob/1.8.0/src/Deferred.php#L118

  3. joelwurtz commented on Sep 23, 2018

    @joelwurtz
    Member

    I think it comes from the underlying promise that do not call onResolve / onFullfill callback no ?

  4. mxr576 commented on Sep 25, 2018

    @mxr576
    Contributor

    @joelwurtz @Nyholm any ETA for a fix for this? If someone installs our module with the latest version of the php-http/client-common lots of things gets broken and I do not want to create a new release just to blacklist php-http/client-common:>=1.8.0. Couldn't you rollback the related changes in a new 1.8.1 release until you can figure out how to address this problem properly?

    Btw wasn't this change a BC breaking change so it should have been introduced in 2.x.y?

  5. joelwurtz commented on Sep 25, 2018

    @joelwurtz
    Member

    There is a fix in #110 if you have time to test it would be nice (but it fixes this bug on my end)

  6. mxr576 commented on Sep 25, 2018

    @mxr576
    Contributor

    @joelwurtz Please see my comment in #110.

  7. Jean85 commented on Sep 26, 2018

    @Jean85
    Contributor

    This is currently breaking the build in the incoming 2.0 release of the Sentry client: https://travis-ci.org/getsentry/sentry-php/jobs/433720358

    #110 does not currently fix the issue. I'll have to add a conflict to ^1.8.0 until this is fixed.

  8. pascal-hofmann commented on Oct 2, 2018

    @pascal-hofmann

    I ran into this issue too. Is there a reason for not pulling back the 1.8 release? I guess this will cause harm for more people…

  9. mxr576 commented on Oct 8, 2018

    @mxr576
    Contributor

    Seriously guys, just rollback these changes... since two weeks all depending libs/projects are that uses the retry plugin with a synchronous client are broken. If you do not have time to find the proper fix for this is fine, this is open source, rolling back the problematic changes since 1.7.0 should not be that complicated/time consuming.

  10. Jean85 commented on Oct 8, 2018

    @Jean85
    Contributor

    #111 reverts everything but it's still pending...

  11. dbu commented on Oct 9, 2018

    @dbu
    ContributorAuthor

    i released 1.8.1 with the revert now.

  12. dbu commented on Oct 9, 2018

    @dbu
    ContributorAuthor

    created #112 to document the problem but i don't plan to work on this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions