[GitHub] log4net pull request: Fixes for the LogicalThreadContext

Github user bodewig commented on the pull request: https://github.com/apache/log4net/pull/12#issuecomment-87385635 I had to tweak things a little to make it build on Mono and it looks as if I had to do a little bit more for .NET 2.0, these will be follow up commits. --- If

[GitHub] log4net pull request: Fixed stackoverflow when logging internal

Github user asfgit closed the pull request at: https://github.com/apache/log4net/pull/14 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

Build failed in Jenkins: log4net-trunk-tests #39

See https://builds.apache.org/job/log4net-trunk-tests/39/changes Changes: [bodewig] When internal logging is on, manually shutdown and stderr/stdout redirection is performed in log4net we get infinite loop. This fixes the stack overflow but doe snot fix the fact that logging is done after the

[GitHub] log4net pull request: Mono improvements

Github user bodewig commented on the pull request: https://github.com/apache/log4net/pull/11#issuecomment-87388090 part of your patch has been done by a commit earlier today, but I overlooked a few other places that you fixed, thanks! Also added Mono 3.5. --- If your

[GitHub] log4net pull request: Mono improvements

Github user asfgit closed the pull request at: https://github.com/apache/log4net/pull/11 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Comment Edited] (LOG4NET-453) log4net.Appender.ColoredConsoleAppender Fail Under Mono

[ https://issues.apache.org/jira/browse/LOG4NET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385815#comment-14385815 ] Stefan Bodewig edited comment on LOG4NET-453 at 3/29/15 3:24 PM:

[jira] [Updated] (LOG4NET-458) LocalSyslogAppender does not support multiple identities

[ https://issues.apache.org/jira/browse/LOG4NET-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig updated LOG4NET-458: --- Attachment: localsyslog.patch The attached patch tries to cover things up in a threadsafe

Build failed in Jenkins: log4net-trunk-tests #41

See https://builds.apache.org/job/log4net-trunk-tests/41/changes Changes: [bodewig] old key is no longer needed [bodewig] log4net.dll = log4net-1.3.dll [bodewig] remove 'oldkey' stuff -- [...truncated 730 lines...] [csc]

[jira] [Commented] (LOG4NET-453) log4net.Appender.ColoredConsoleAppender Fail Under Mono

[ https://issues.apache.org/jira/browse/LOG4NET-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14385815#comment-14385815 ] Stefan Bodewig commented on LOG4NET-453: doesn't ManagedColoredConsoleAppender

Build failed in Jenkins: log4net-trunk-tests #42

See https://builds.apache.org/job/log4net-trunk-tests/42/changes Changes: [bodewig] .NET 2.0 compatibility [bodewig] LOG4NET-447 provide a PopAllEvents method for thread-safe access to MemoryAppender Patch by Gregory Babski [bodewig] allow compilation on .NET 2.0

Build failed in Jenkins: log4net-trunk-tests #43

See https://builds.apache.org/job/log4net-trunk-tests/43/changes Changes: [bodewig] adapt test to renamed assembly -- [...truncated 716 lines...] [csc]

[jira] [Resolved] (LOG4NET-447) MemoryAppender class is not thread safe

[ https://issues.apache.org/jira/browse/LOG4NET-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved LOG4NET-447. Resolution: Fixed Fix Version/s: 1.3.0 added PopAllEvents with svn revision

Build failed in Jenkins: log4net-trunk-tests #38

See https://builds.apache.org/job/log4net-trunk-tests/38/changes Changes: [bodewig] copy paste error [bodewig] add support for Mono 3.5 and 4.0 and tentative support for .NET 4.5 -- [...truncated 714 lines...] [csc]

[GitHub] log4net pull request: Fixes for the LogicalThreadContext

Github user asfgit closed the pull request at: https://github.com/apache/log4net/pull/12 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Resolved] (LOG4NET-456) Include debug symbol files in release packages

[ https://issues.apache.org/jira/browse/LOG4NET-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved LOG4NET-456. Resolution: Fixed Fix Version/s: 1.3.0 Thanks, patch applied with svn revision

[jira] [Resolved] (LOG4NET-455) LogicalThreadContext does not flow correctly through async/await

[ https://issues.apache.org/jira/browse/LOG4NET-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Bodewig resolved LOG4NET-455. Resolution: Fixed Fix Version/s: 1.3.0 applied modified version of PR with svn

Build failed in Jenkins: log4net-trunk-tests #40

See https://builds.apache.org/job/log4net-trunk-tests/40/changes Changes: [bodewig] fix year [bodewig] checking for the wrong symbol [bodewig] some fixes for Mono based on Patch by Antonius Riha closes #11 by @antoniusriha -- [...truncated 723

Build failed in Jenkins: log4net-trunk-tests #44

See https://builds.apache.org/job/log4net-trunk-tests/44/changes Changes: [bodewig] fix some tests for systems with log4net residing in the GAC [bodewig] use a fresh repository for tests [bodewig] another assembly reference to fix -- [...truncated 769