Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call to a member function status() on bool in EnsureRequestsDontExceedMaxExecutionTime #588

Closed
ibrunotome opened this issue Sep 28, 2022 · 5 comments · Fixed by #590
Closed
Assignees
Labels

Comments

@ibrunotome
Copy link

ibrunotome commented Sep 28, 2022

  • Octane Version: v1.3.1
  • Laravel Version: v9.32.0
  • PHP Version: 8.1.1
  • Server & Version: OpenSwoole 4.11.1
  • Database Driver & Version: postgres 14

Description:

Screen Shot 2022-09-28 at 18 33 00

this line https://github.com/laravel/octane/blob/1.x/src/Swoole/Actions/EnsureRequestsDontExceedMaxExecutionTime.php#L33

is returning a bool instead of a http response

Steps To Reproduce:

Make a request longer than config max_execution_time

@driesvints
Copy link
Member

Can you send in a PR?

@ibrunotome
Copy link
Author

Can you send in a PR?

Sure, What behavior do you want that I implement when $response = Response::create($this->server, $row['fd']); returns a bool?

@driesvints
Copy link
Member

@nunomaduro do you know?

@driesvints driesvints changed the title bug: Call to a member function status() on bool in EnsureRequestsDontExceedMaxExecutionTime Call to a member function status() on bool in EnsureRequestsDontExceedMaxExecutionTime Sep 30, 2022
@ibrunotome
Copy link
Author

This is the exact same issue #545 opened 3 months ago and closed because "it is a support request" 🤔

But I'm happy that it's fixed now.

@driesvints
Copy link
Member

It was not clear to me that this was a bug at that time. Your report here was more insightful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants