-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature/61/subject tester #63
Merged
Merged
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
41babf8
test: Test subject tester(WIP)(#61)
hhkim0729 8668db6
fix: Fix error when POST request is invalid
hhkim0729 0aa5b7e
test: Add test files(#61)
hhkim0729 28ebbd5
feat: Update python-cgi
hhkim0729 ae7cda5
test: Test subject tester(WIP)(#61)
hhkim0729 beb05a3
test: Test subject tester(WIP)(#61)
hhkim0729 c597d1a
test: Test subject tester(#61)
hhkim0729 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
poll()에 설정한 타임아웃 시간동안 아무 이벤트가 발생하지 않으면 0을 반환하는데 이에 대한 처리도 필요해 보입니다~
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
0을 반환한다는 것은 이벤트가 발생한 fd가 없다는 뜻이므로, 아래 masters를 순회하는 반복문 내부의 if 문 조건에 걸리지 않기 때문에 따로 예외처리를 할 필요가 없어 보입니다
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
위에서 잘못 설명한 부분을 정정합니다 poll() 이 하는 역할이 어떤 fd 에 이벤트가 발생할 때까지 block 하는 것이 아니라 fd가 준비될 때까지 block 하는 것인데 이때 타임아웃을 설정한다는 것의 의미는 클라이언트가 무한히 대기하지 않고 일정 시간이 지나면 에러 페이지를 반환 받을 수 있는 데에 의미가 있습니다. 만약에 반환값 0에 대한 처리를 따로 하지 않는다면 기존에 타임아웃이 무한이었던 것과 다른 점이 없지 않나요?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
첫 번째 의견에서 말한게 맞았네요 이벤트가 발생한 것이 없을 때 0을 반환하는게 맞는데, 이때에는 for 문을 돌면서 일일이 모든 마스터에 이벤트가 발생했는지 확인할 필요 없이 바로 continue 를 해주는 것이 효율 상 좋아보입니다.