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

Execute rule operation, when given non-existing function for 'rule-text' parameter, is causing invalid free to occur when http api is shut down #313

Open
farbs03 opened this issue Jul 25, 2024 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@farbs03
Copy link

farbs03 commented Jul 25, 2024

Bug Report

iRODS Version, OS and Version

Tip of main

What did you try to do?

Execute a rule operation with a non-existing function, "writeline" (which was a typo, supposed to be "writeLine") then stop the http api container directly after.

Expected behavior

op_execute: RcComm::rError info = [status=[-1220000], message=[DEBUG:]] gets logged by the http api, and no message indicating an invalid free is occuring gets logged when shutting down the container.

Observed behavior (including steps to reproduce, if applicable)

The same message above gets logged, except free(): invalid pointer gets logged when shutting down the container.

Steps to reproduce:

  1. Send execute rule request to the http api with a non-existing function passed to the 'rule-text' parameter
  2. Shut down the container running the http api
@korydraughn korydraughn added the bug Something isn't working label Jul 25, 2024
@korydraughn korydraughn added this to the 0.4.0 milestone Jul 25, 2024
@korydraughn korydraughn self-assigned this Aug 3, 2024
@korydraughn
Copy link
Contributor

I've tried to reproduce this against the following (all linux-based solutions):

  • 0.3.0 release published on Docker hub
  • A build later than tip-of-main (7b5ed8a)
  • A Docker container running a build later than tip-of-main (7b5ed8a)

No attempt produced the results reported.

Given that this issue was reported from use of the Docker for Windows, it's possible the behavior stems from Docker running in a Windows environment.

I'll double check the implementation and see if anything stands out. Aside from that, I don't think there's anything actionable here without being able to reproduce it locally.

@korydraughn korydraughn modified the milestones: 0.4.0, 0.6.0 Aug 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants