forked from svenvc/zinc
-
Notifications
You must be signed in to change notification settings - Fork 10
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
release v2.4.3.1 #66
Merged
Merged
release v2.4.3.1 #66
+3,404
−823
Conversation
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
…roject and add backin into CI group, since the project should now load without errors
…or all required projects for zinc ... may need to pull in tests vi CI group
….. will be available soonish on the glass master branch
…on Travis, but not locally...
…implemented methods
…erver-Tools, a new package which holds ZnServerStarter class needed by web socket tests ...
- always snap off continuation when an error event occurs - add some error handling a bit higher up the zn stack ... to catch application errors as well ... might be able to continue processing without passing error ... still passing at the moment... - ZnTranscriptLogger for all ZnGemServer guys ... might want to make this easier to customize
…default errors are logged to transcript and continuation commmited to object log....
…use ZnObjectLogLogger ... practical to debug ZnGemServer using object log logging and continuations
…secure sockets (Zodiac) ... not supported in GemStone at the moment
… on debugMode: for all of the tests useing GemServer ... if there is a problem with the test passing we are going to want to look at the object log ...
… the exception ... debugMode doesn't quite appy to GemStone ... need different granularity I think ... GsPharo 0.9.2 needs to be used
…o understand the odd 30 second delay for the chat delegate
…cket instances cannot be persisted
… log an error: and handleError: for GemStone so we make sure that all errors make it to the log (object log and continuation) AND the gem file .... add gobs of log helper methods to ZnGemServer ... control logging method and filter and whether or not continuations are created for errors from ZnGemServer
…rveConnectionOn: and ZnMultiThreadedServer>>executeRequestResponseLoopOn:
…the object log...refactor REST tests to allow for testing using remote ZnGemServer and add persistence to ZnExampleStorageRestServerDelegate ... a bit of house cleaning in ZnGemServer
…etStreamSocket would lead to an infinite loop creating processes and then running out of memory ... Fix Rest test error ... only pass exceptions in debugMode for ZnServer
…erver, but it is natural for ZnGemServer to refer to ports ... a bow to compat
…licationTools:v.1.?
…ing ZnNewGemServer that is married with ZnGemServerManagingMultiThreadedServer which is a refactored ZnTransactionSafeManagingMultiThreadedServer/ZnManagingMultiThreadedServer that replaces all of the error handling with gemServer:* calls ... create interfact to delegates so that ZnGemServerManagingMultiThreadedServer can be used with any existing delegates, although by default there are no transactions being performed, but the handleRequest:gemServer: method can changed to add transactions ... no tests for the new boys ... yet
…e tests can be run against an interactive gem server running in second tODE environmnent ... 19 run, 9 passes, 0 expected defects, 10 failures, 0 errors, 0 unexpected passes .... so blatant server-side errors have been cleaned up
…ly failure for 2.4.x versions
…nal logging for testError mystery
…erTests>>testError logging
… handling to the handler up the stack ... logging and proper error response handling is already defined ...revise comments in delegate handleRequest:gemServer: methods
…ort for Rest transactional example
…ver and the "proper" persistence model
…m failures .... all tests run clean in my 3.2.2 dev image
…out object log logging ... CHECKPOINT
… passing tests ...
merge Issue 69 into Issue 58
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
accept
callFrom PR #70: