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

A bad HTTP request should not trigger an ASync HTTP event #8463

Closed
2 tasks done
peardox opened this issue Nov 20, 2024 · 2 comments
Closed
2 tasks done

A bad HTTP request should not trigger an ASync HTTP event #8463

peardox opened this issue Nov 20, 2024 · 2 comments
Assignees
Labels
gmrt-bug In-game bugs with the "GMRT" runtimes

Comments

@peardox
Copy link

peardox commented Nov 20, 2024

Description

In the attached example change the URL in the url to something non-sensical that can't succeed like http://fakesite.example.com/

This will show a HttpError in the console BUT we'll still get a phantom ASync - HTTP event

No event actually happened though

Expected Change

No response

Steps To Reproduce

  1. Import Project
  2. Run In Debug
  3. See the issue

How reliably can you recreate this issue using your steps above?

Always

Which version of GMRT are you reporting this issue for?

2024.8.1.171

Contact Us Package Attached?

  • I have attached my Contact Us Package

Sample Project Added?

  • I have included a small sample project
@peardox peardox added the gmrt-bug In-game bugs with the "GMRT" runtimes label Nov 20, 2024
@peardox
Copy link
Author

peardox commented Nov 20, 2024

Forgot package
com.peardox.wsock.zip

Also...

Contact Us Package Attached?
This .zip file is essential for all bug reports. Please build your project, so that you have a compiler log inside GameMaker, then open the Help menu inside GameMaker and run the "Create Your Contact Us Package" tool. Attach the .zip file GameMaker makes for you to this report (or upload it somewhere you trust and put the download link into your Description text - make sure the file is shared!).

Help menu has no such option...

@stuckie stuckie moved this from Triage to Backlog in Team Workload Nov 20, 2024
@jackerley
Copy link

The http request creates an async event with a status of -1 which indicates failure. It is necessary so that you can know when your http request fails and allows you to deal with it by retrying or however you wish to deal with it.

@jackerley jackerley closed this as not planned Won't fix, can't repro, duplicate, stale Nov 21, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done in Team Workload Nov 21, 2024
@gurpreetsinghmatharoo gurpreetsinghmatharoo moved this from Done to Not Planned in Team Workload Nov 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gmrt-bug In-game bugs with the "GMRT" runtimes
Projects
Status: Not Planned
Development

No branches or pull requests

2 participants