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

Should exit if --input-file replayed all requests #456

Closed
buger opened this issue May 24, 2017 · 8 comments
Closed

Should exit if --input-file replayed all requests #456

buger opened this issue May 24, 2017 · 8 comments
Labels
enhancement New feature or feature request
Milestone

Comments

@buger
Copy link
Owner

buger commented May 24, 2017

Right now it just hangs and does nothing.

@buger buger added the enhancement New feature or feature request label May 24, 2017
@buger buger added this to the 0.17 milestone May 24, 2017
@klivan
Copy link
Contributor

klivan commented Jun 23, 2017

+1
For now I'm using hack like this (I have only 1 input file) but would love to have this feature in gor:

#!/bin/bash

INPUTFILE="input.gor"
LOGFILE="/tmp/gor.log"
MATCH="FileInput: end of file"

gor --input-file "$filename" --output-http="http://www.test.com" 2>&1 | tee $LOGFILE &
while sleep 5
do
    if fgrep --quiet "$MATCH" "$LOGFILE"
    then
        exit 0
    fi
done

@buger buger modified the milestones: 0.16.1, 0.17 Jun 23, 2017
@buger buger closed this as completed Jun 27, 2017
@klivan
Copy link
Contributor

klivan commented Jun 27, 2017

@buger I see this was closed. So it won't be included in the next release?

@buger
Copy link
Owner Author

buger commented Jun 27, 2017

Sorry for the confusion. It is fixed in upcoming 0.16.1 which will be release today. I will notify you here :)

@klivan
Copy link
Contributor

klivan commented Jun 27, 2017

@buger Thanks you!

@bartbrinkman
Copy link

This issue is not fixed, it'll still hang on --file-input. OS X binary, version 0.16.1.

@buger
Copy link
Owner Author

buger commented Aug 22, 2017

I really look like a lock somewhere in --input-file, can't find it yet 😭

@jordangarrison
Copy link

Hello @buger,

I think this may still be an issue. I'm using a similar workaround to the one shown above.

I'm running version 1.2.0. Love the project!

@urbanishimwe
Copy link
Collaborator

Verified too on my end, this should be tracked on a separate issue.

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

No branches or pull requests

5 participants