Unsubscribe assistance

Hi Jeromey Please follow the instructions to self-service unsubscribe. https://logging.apache.org/mailing-lists.html Best Dominik On Fri, 22 Nov 2024, 19:51 Jeromey Lange, wrote: > Unsubscribe me please > > > > Best regards, > > > > Jeromey Lange > Security Manager: GRC > > [image: Logo Descr

Re: Successor to mailing lists

tried to explain in detail in my > > first email. There are "workarounds" (see Mailman DMARC mitigations link > I > > shared), but no one-size-fits-all solution. See the INFRA tickets I > shared > > for such rejected messages. > > > > On Tue, Oct 15,

Re: Successor to mailing lists

60 filters set up to route my mail into > them. But even that isn’t perfect. GitHub generates so much noise that it > is impossible to keep up with all the notifications it sends me. That is > one of the major reasons I am not in love with the idea of using > discussions. >

Re: Successor to mailing lists

What concerns me is that email appears to be unreliable where it shouldn't. Either it works always or it doesn't at all. I experience it to be 100% reliable. Short downtimes are OK and to be expected while systems are patched. But then email are delivered later. The technology is much like a postm

Re: Feature proposal for a new Filter result: Throw

If the scope is limited to unit tests, the log message could also be intercepted in the test and interpreted as a failure (or success) without throwing any exceptions. As a consumer, I would be surprised and interpret it as a bug if a filter was to throw exceptions. From the separation of concern p

Re: [VOTE] Move Flume to dormant

+1, i see no harm in a dormant state and only benefits from signalling this to the outside world On Thu, 3 Oct 2024, 20:28 Jan Friedrich, wrote: > +1 > > On 2 October 2024 21:29:44 CEST, Christian Grobmeier > wrote: > >Hello everyone, > > > >We have discussed this in the past. I hope we can pic

Re: [log4net] INFRA-managed NuGet account

I accepted with my microsoft account tied to dpsen...@gmail.com and am now a collaborator (pending for approval) in the organization asf. On Mon, 2 Sept 2024, 11:51 Davyd McColl, wrote: > I've accepted; delete the other org at your convenience. > > > -d > On 2024-09-02 11:39, Volkan Yazıcı wrote

Re: Updating the Logging Services Logo

The blog post mentions the 7 oct 2024 as the deadline to be compliant. This coincides with the day when the new marketing guidelines are unveiled. It is probably impossible to implement this within hours. Therefore I propose to ask Marketing for assistance/guiding/new marketing material right now i

Re: Archive `logging-pipelines`

Hi Volkan. Log4net used to use jenkins pipelines. But I can't recall any reference to that repository. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Fri, Sep 15, 2023, 09:04 Volkan Yazıcı wrote: > AFAIC, no Logging Services projects use Jenkins pipelines an

Re: I have a question regarding LOG4NET-27 and LOG4NET-367.

67 > would call it at the right time from the appropriate method in > RollingFileAppender. > > However, since Log4Net became dormant on 2020/04/05 and was revived on > 2020/04/06, we are not sure who is now in charge and leading LOG4NET-367. > Is Dominik Psenner still

Re: [ANNOUNCE] Changes to Jira Account Creation (issues.a.o/jira)

GitHub issues could be a good replacement for jira IMO. Mailing lists do not have an issue with spam because there are human moderators doing most of the filtering. ;-) There are several moderation messages every day, some of them even directly land in my spam folder and I won't bother finding

Re: log issue

Hi, As far as I know log4rc is not a library part of Apache Logging Services TLP. Would it be possible that you have sent this to the wrong recipient? Dominik -- Sent from my phone. On Wed, Oct 12, 2022, 07:35 Krotha, Suharika wrote: > Hii, > Logs are not appearing on using log4rc > >

Re: ci-builds all 3.6TB disk is full!

> > 7.6GMyFaces > > > 7.6GDirectory > > > 6.4GOpenJPA > > > 6.0GManifoldCF > > > 5.9GActiveMQ > > > 5.7GLogging > > > 5.6GArchiva > > > 5.5GUIMA > > > 5.3Gctakes > > > 4.7GHeron > > > 4.6GJena > > > 4.0GOpenOffice > > > 3.8GCloudstack > > > 3.4GShiro > > > 2.5GQpid > > > 2.1GJSPWiki > > > 2.1GJMeter > > > 2.0GJClouds > > > 1.8GSantuario > > > 1.8GOpenMeetings > > > 1.8GCamel > > > 1.7GKaraf > > > 1.7GHttpComponents > > > 1.7GAnt > > > 1.5GTapestry > > > 1.5GCommons > > > 1.3GDeltaSpike > > > 1.2GRya > > > 1.2GAries > > > 1.2GAccumulo > > > 1.1GPDFBox > > > > > > -- > > > > > > *Gavin McDonald* > > > Systems Administrator > > > ASF Infrastructure Team > > > > > > -- Dominik Psenner

Re: Dynamically updating filters across many instances

Ralph, I do not believe that there exists a "one size fits it all" solution. Yes, running in debug log has drawbacks and should not be necessary. And yet I learned that only debug logs may provide enough insights. The cause for this is simple: developers test code at "debug" level and when time is

Re: Dynamically updating filters across many instances

each must be specified in its own key. That would mean > the > >> filter would have to be preconfigured with the maximum number of > accounts > >> it can look for. It would also mean the syntax for specifying the > account > >> numbers could get messy. However, it could register a Watcher for the > >> external file and force a reconfiguration when it does. > >> > >> An alternative to reconfiguring could be to specify the variable as > >> $${src:accountNumber) and resolve the lookup for every log event. > >> Presumably it would use a cached value and cause the value to change > when > >> the file is changed. > >> > >> These are just the first few things I thought of to do this. Does anyone > >> else have any ideas? > >> > >> Ralph > > -- Dominik Psenner

Re: [Newsletter] Re: log4net - performance hit because UserName is fetched always

; > > > > Geschäftsführung / Executive Board: Christian Leicher (Vorsitzender / > Chairman), Peter Riedel, Sitz der Gesellschaft / Company's Place of > Business: München, Registereintrag / Commercial Register No.: HRA 16 270, > Persönlich haftender Gesellschafter / Personally Liable Partner: RUSEG > Verwaltungs-GmbH, Sitz der Gesellschaft / Company's Place of Business: > München, Registereintrag / Commercial Register No.: HRB 7 534, > Umsatzsteuer-Identifikationsnummer (USt-IdNr.) / VAT Identification No.: DE > 130 256 683, Elektro-Altgeräte Register (EAR) / WEEE Register No.: DE 240 > 437 86 > > > > > -- Dominik Psenner

Re: [logging-log4j1] branch v1.2.8 created (now 0cde9dd)

End-Of-Life means End-Of-Life and that is the end of the story. If someone keeps patching an End-Of-Life component, how should downstream understand when they should update their product? The answer to this question is the technical definition of End-Of-Life. Upgrade, migrate, rewrite, throw awa

Re: [VOTE] Future of Log4j 1.x

+1, option 1 -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Tue, Jan 4, 2022, 22:19 Remko Popma wrote: > +1 for Option 1 > > On Wed, Jan 5, 2022 at 4:51 AM Volkan Yazıcı wrote: > > > +1, Option 1 > > > > On Wed, 29 Dec 2021, 20:33 Christian Grobmeier > > w

Re: [VOTE] CVE creation process

+-0 I have no strong opinion. I do believe that an informal consensus about our best practice should be all we need. It should suffice when two pmc members acknowledge both fix and official communication. My perception is that we already do our best. Beyond that, it will always be a walk on the ed

Re: [DISCUSS][VOTE] Future of Log4j 1.x

you will send patches" too intimate. > >> > >> 2) I have already filed a patch for buildscripts. Whould you review it > and > >> merge? > >> > >> 3) Suppose I find a team (e.g 4-5 ASF fellows) who are willing to > support > >> 1.2. What do you do then? Would you add all of them to the logging pmc? > >> I don't really see the point why do you ask, and at the same time I > can't > >> guarantee the people I gather will be alive tomorrow. I can't guarantee > >> they will always have interest in 1.2 > >> > >> Vladimir > -- Dominik Psenner

Re: [log4cxx] CI Benchmarking

Hi Stephen, The trouble with benchmarks in CI is that the numbers may be largely unreliable, depending mostly on the hardware where it runs and in general the surrounding environment. Chances are high that the benchmarks will not produce comparable results. It would however be good to provide som

Re: [DISCUSS] The future of Log4j 1.x

I am in favor of option 1, basically this: * Add an EOL marker, big and bold * Allow the repository to be cloned * Allow the repository to be forked * Disable the creation of new pull requests (on github) * Disable creation of issues (on github; this is the default; I want to stress this by mentio

Re: [VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

As PMC member I voted to make the source code available in a git repository. The git repository and the mailing list are all the tools needed to prepare contributions and fixes. It allows for easy forking and contributions to prosper. I would love to see this cause the community to grow. It would b

Re: [VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

My reasoning behind my +1 vote is that it is good to have the log4j1 repository on git, aligned with other repositories and easily available to the public. As a starter, the repository should clearly mention its EOL and NOT provide any interactivity through issues and pull requests. -- Sent from

Re: [VOTE] Move apache/log4j1 Git repo to apache/logging-log4j1 Git repo

+1 -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Thu, Dec 23, 2021, 22:38 Ralph Goers wrote: > +1 > > Ralph > > > On Dec 23, 2021, at 2:35 PM, Ralph Goers > wrote: > > > > In https://issues.apache.org/jira/browse/INFRA-22654 Chris Lambertus > has recommend

Re: Resurrecting log4j 1.x

So far it has been discussed to patch 1.2.17. I propose to fork logging-log4j1 [1] and base improvements on tag v1_2_17, de9f0ea. As far as I can tell, no additional work is required from Infra or Logging Services. [1] https://github.com/apache/logging-log4j1 -- Sent from my phone. Typos are a ki

Re: Resurrecting log4j 1.x

There are fixes for the flaws of log4j1 available: migrate to log4j2. Is there a concrete need for log4j1 to be patched and that need cannot be satisfied by migrating to log4j2? -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Thu, Dec 23, 2021, 16:39 Vladimir

Re: [VOTE] Release log4net 2.0.14

>> davyd.mcc...@codeo.co.za) which I believe has been lost somewhere > along the > >> way. Please ignore the other if it pops up. > >> > >> > >> -- > >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > >> If you say that getting the money is the most important thing > >> You will spend your life completely wasting your time > >> You will be doing things you don't like doing > >> In order to go on living > >> That is, to go on doing things you don't like doing > >> > >> Which is stupid. > >> > >> - Alan Watts > >> https://www.youtube.com/watch?v=-gXTZM_uPMY > >> > >> *Quidquid latine dictum sit, altum sonatur. * > > > -- Dominik Psenner

Re: [Lo4Net] Cyber Vulnerability Vendor Impact Assessment for Lo4Net

-cm.com> > > This message, including any attachments, may contain information that is > privileged, confidential and/or protected by copyright, and is subject to > the terms available at > https://www.smbcgroup.com/americas/disclaimers/emaildisclaimer.html/ > If you are not the intended recipient, or have received this message in > error, please notify the sender immediately and delete this message. > -- Dominik Psenner

Re: [VOTE] Release log4net 2.0.14

. > > Thanks Ralph for assisting me in being able to uplodate artifacts myself. > Much appreciated. > > -d -- Dominik Psenner

Re: Answering FAQ regarding recent CVEs, was: log4net

ceeded ? > > -Mayank > > On Tue, Dec 14, 2021 at 12:16 PM Dominik Psenner > wrote: > > > This question has been asked several times now. I'm proposing to update > the > > website so that it is more obvious that log4net and log4xx are not > > affected. > &

Answering FAQ regarding recent CVEs, was: log4net

t from disclosure. If the reader of > >> this e-mail is not the intended recipient or the employee or agent > >> responsible for delivering the message to the intended recipient, you > >> are hereby notified that any dissemination, distribution, or copying > >> of this communication is strictly prohibited. If you have received > >> this communication in error, please immediately notify us by replying > >> to the original message at the listed email address. > >> > >> Happy to Help > >> Oklahoma's Credit Union > >> https://urldefense.com/v3/__http://www.okcu.org__;!!FbZ0ZwI3Qg!6hdye55 > <https://urldefense.com/v3/__http://www.okcu.org__;!!FbZ0ZwI3Qg!6hdye55> > >> e93GuHBF0X4qMKophICSr0Nb5ggI6RBgb2lJoysQv8jdWynWoouaTpixMWg$ > > > > INTERNAL - NI CONFIDENTIAL > > -- Dominik Psenner

Re: Cek's new log4j vs logback benchmark

May a ringbuffer cache be a viable solution? Knowing the resolution (ticks, microseconds, milliseconds, seconds,..), a key could be generated to lookup and return a previously created formatted string from a ringbuffer or create it on the fly and store it for later. During bursts of log events, th

Re: [general] Recommended event log storage?

Hi I like Json as the transport format over mqtt. A few hundred lines of code persist events to a postgresql database by calling a stored procedure that handles the json directly. The stored procedure allows for plugging in some fancy aggregation logic or distribution across tables or even retenti

Re: Any plans to release log4j TCP server?

Hi, I would rather advise to not reinvent the wheel of tcp communication but implement some simplistic mqtt appender that transports log events as json serialized messages. In combination with a broker like mosquitto it provides secure communication, temporary peristent storage and many more adva

Re: Revamping website design and logo

Hi, in the past some effort has been made to make all log4xxx project websites look alike. If the site design should be changed, I propose to expand the discussion to the other projects. Greets, Dominik -- Sent from my phone. On Wed, Mar 10, 2021, 18:33 Ralph Goers wrote: > > > > On Mar 10, 20

Re: [VOTE] Move Log4PHP to dormant status

+1 -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Fri, Dec 11, 2020, 19:59 Christian Grobmeier wrote: > Very sad, but +1. > > Code base became very old and there is lots to do. > > -- > The Apache Software Foundation > V.P., Data Privacy > > On Wed, Dec 9, 2

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

, Dominik On Fri, 23 Oct 2020 at 20:52, Davyd McColl wrote: > Hi Dominik > > iirc, this was fixed in 2.0.11. 2.0.12, with another fix for current user > name on !win32, is waiting on one more +1 vote for release. > > -d > > On October 23, 2020 18:05:18 Dominik Psenner wro

Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

See the message below. -- Sent from my phone. -- Forwarded message - From: NuGet Gallery Date: Fri, Oct 23, 2020, 07:51 Subject: [NuGet Gallery] Message for owners of the package 'log4net' To: *User santoshkallatti > sends the following message to the owners of Package 'log4net

Re: [VOTE] [log4net] Release 2.0.11

+1 -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Tue, Sep 22, 2020, 08:37 Davyd McColl wrote: > Hi all > > I'd appreciate any more +1's (thanks, Remko!). I'd like to get this out > the door because it fixes confusing versioning on the released binaries (in

Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

See the message below. Apparently something went wrong during the last release. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. -- Forwarded message - From: NuGet Gallery Date: Fri, Sep 18, 2020, 12:10 Subject: [NuGet Gallery] Message for owners of

Re: [VOTE] [log4net] Release 2.0.10

at mostly I just want to deprecate > client profiles to enable easier cross-platform dev (those are the only > targets I haven't had joy supporting on Linux so far) > > -d > > > > On September 7, 2020 19:55:51 Dominik Psenner > wrote: > > Hi > > Does

Re: [VOTE] [log4net] Release log4net 2.0.10

functional: > - install node if you don't have it yet (I suggest via nvm) > - `npm ci` > - `npm test` > > (assuming that you have all the required build targets -- there are helper > .ps1 scripts to get the older targets -- netcore 1.1 and netfx35) > > -d > > >

Re: [VOTE] [log4net] Release log4net 2.0.10

Hi Sorry to not have responded earlier. Time is short and the days are busy. I looked at the diff and found several suspicious changes. Several hundred ifdefs have been removed/replaced along with tests. Therefore I have a bad feeling about those changes without further careful checking. I propose

Re: [NuGet Gallery] Message for owners of the package 'log4net'

ce the > user to follow the link to the web site. > > Ralph > > > On Sep 8, 2020, at 11:17 AM, Dominik Psenner wrote: > > > > This reflects my impression that the volume of individuals that do not > know > > the mechanics of the mailing lists has increased. I

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

ucky ones if it will help (: > >> > >> -d > >> > >> > >> On September 8, 2020 17:47:57 Matt Sicker wrote: > >> > >> > The main problem with sending nuget info to the PMC is that nobody in > >> > the PMC are working on

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

In the past security vulnerabilities were reported via nuget and it is not a good idea to publish those in an automated way. I suggest to update the nuget project documentation and prominently point to our mailing lists and discourage the communication via nuget. Users may continue sending message

Re: [VOTE] [log4net] Release 2.0.10

Hi Does this break support for netstandard1.3 and enforces users to update all their dependants? Best regards -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Sun, Sep 6, 2020, 21:04 Davyd McColl wrote: > Hi all > > > I'd like to propose a vote to release 2.0

Log4net: 2.0.9 release notes missing

Hi People noticed that the release notes of 2.0.9 are missing while they should be documented here: http://logging.apache.org/log4net/release/release-notes.html Best regards -- Sent from my phone. Typos are a kind gift to anyone who happens to find them.

Log4net: Insecure site url on nuget

Hi, I noticed that the site url of the log4net nuget package is http instead of https (http://logging.apache.org/log4net/) and propose to update it. See: https://www.nuget.org/packages/log4net/ Best regards -- Sent from my phone. Typos are a kind gift to anyone who happens to find them.

Re: [VOTE] Release Log4Net 2.0.9

McColl wrote: > Oh ok, well, mine is davydm (: > > -d > > > On August 22, 2020 20:49:59 Dominik Psenner wrote: > > > Apparently it cant be the email but must be the nuget accounts username, > > apologies. > > > > -- > > Sent from my phone.

Re: [VOTE] Release Log4Net 2.0.9

y > Microsoft > account for nuget is this email address (dav...@gmail.com) > > -d > > > On August 22, 2020 19:46:45 Dominik Psenner wrote: > > > Hi > > > > I recall that we were forced to transform the nuget account > Apache.Logging ( > > https:

Re: [VOTE] Release Log4Net 2.0.9

sn’t used to sign the document. > >>> > >>> Ralph > >>> > >>>> On Aug 21, 2020, at 3:53 PM, Ralph Goers > wrote: > >>>> > >>>> Dominik, > >>>> > >>>> The README file says that the keys

Re: [VOTE] Release Log4Net 2.0.9

gt; If it's of interest to anyone, my profile is at > https://www.nuget.org/profiles/davydm > > -d > > > On August 17, 2020 18:46:50 Dominik Psenner wrote: > > > I guess that would be a nuget publish. > > > > https://docs.microsoft.com/en-us/nuget/nuget-or

Re: [VOTE] Release Log4Net 2.0.9

I guess that would be a nuget publish. https://docs.microsoft.com/en-us/nuget/nuget-org/publish-a-package The credentials to that account are stored in the private repos of logging pmc. Most members of the pmc should be in the set of recipients with their gpg key. -- Sent from my phone. Typos are

Re: [VOTE] Log4Net dormant release

wrote: > Unfortunately, I had to moderate the message you just responded to so I am > not sure if they will see the response. That said, I don’t think we should > be cc’ing posters. They should subscribe. > > Ralph > > > On Jul 30, 2020, at 9:14 AM, Dominik Psenner wrote

Re: [VOTE] Log4Net dormant release

Hi Shushi Kant, There is no maintainer to release binaries for You. A source only release was made some time ago, also to signal the dormant state of the project. This was aimed to be a signal to interesting parties to get involved in the project. I see at least these options: Option 1 is to get

Re: [CVE-2018-1285] XXE vulnerability in Apache log4net

Good Day!> > > > > > > Is there any mitigation or vulnerability fix available for .NET Core> > > > frameworks?> > > > > > > Please let me know.> > > > > > > Regards> > > > Suthish> > > > > > > > -- > Matt Sicker > -- Dominik Psenner

Re: [CVE-2018-1285] XXE vulnerability in Apache log4net

The fix has been committed for some time now and is available with all branches that I know. You are affected by this CVE if your application consumes configuration files from untrusted sources, especially in dtd statements. 1. You should assert that your deployment does not rely on dtd processing

Re: [log4net] CI server question

a good build environment, which I'm probably going to > try > to replicate in docker, though that would still require a windows host. > > -d > > > On April 27, 2020 21:07:50 Dominik Psenner wrote: > > > As apache folks, we have the benefit of sponsored msdn subsc

Re: [log4net] CI server question

As apache folks, we have the benefit of sponsored msdn subscriptions and thus some sponsored computing time in azure. May that be an option? I dont know about the tasks involved. I can also think of cross compiling on ubuntu inside docker by leveraging dotnet-sdk and linking against the reference

Re: [Log4Net]: resurrection

greatly integrate with msbuild inline tasks which could be used to build site and other non-code assemblies: https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuild-inline-tasks?view=vs-2019 Cheers, Dominik On Sun, 19 Apr 2020 at 10:41, Dominik Psenner wrote: > You may find the develop

Re: [Log4Net]: resurrection

You may find the develop and other branches useful: https://github.com/apache/logging-log4net/tree/develop/buildtools/docker There are dockerfiles along with shell scripts that used to work for building sev

Re: log4net: resurrection

; (I've had > >>>>>>>>>>> reasonable experience, but not with pipelines)). I'm not even > sure what > >>>>>>>>>> the > >>>>>>>>>>> state of play is for that infra. I'm sure there are good > reasons for > >>>>>>>>>> making > >>>>>>>>>>> the project dormant -- some of those may include the desire to > free up > >>>>>>>>>>> infra which could be used elsewhere (or just not paid for). > >>>>>>>>>>> As I say, I'd like to keep log4net alive. I see a few options > here: > >>>>>>>>>>> 1. I learn your infra and your processes. I integrate and try > to keep > >>>>>>>>>>> things pretty-much as they were (though I'm sure some things > would have > >>>>>>>>>> to > >>>>>>>>>>> change -- all things do). I don't mind spending the time > learning the > >>>>>>>>>>> domain, if that's agreeable to everyone and the project > retains it's > >>>>>>>>>>> original branding and status. One thing I'm concerned about > here is the > >>>>>>>>>>> dormant backlog > >>>>>>>>>>> 2. As above, with a bit of a clean-slate philosophy: I'd like > to remove > >>>>>>>>>> all > >>>>>>>>>>> backlog items that aren't critical and start with the least > outstanding > >>>>>>>>>>> stuff possible. If a report is important, it will be reported > again. > >>>>>>>>>> Trying > >>>>>>>>>>> to trace down the authors and origins of 2+year-old reports is > going to > >>>>>>>>>> be > >>>>>>>>>>> frustrating. Issues which aren't attended to just become noise > in the > >>>>>>>>>>> backlog, imo. > >>>>>>>>>>> 3. I fork and perform the "clean slate" approach of above, > inviting > >>>>>>>>>> others > >>>>>>>>>>> to use my variant and log issues there. Uptake will naturally > be slow (if > >>>>>>>>>>> even noticeable), which will give me time to deal with > incoming issues. > >>>>>>>>>> On > >>>>>>>>>>> the other hand, I'd have full control and no need to bother > anyone else. > >>>>>>>>>> I > >>>>>>>>>>> would have to come up with a new name and make it clear that > it's a fork, > >>>>>>>>>>> though also make it clear I'd be standing on the shoulders of > giants. > >>>>>>>>>>> Personally, I'd like (1) because it keeps the project that > people rely on > >>>>>>>>>>> alive. Since I'm new to the mailing list, I can't discern yet > the > >>>>>>>>>> sentiment > >>>>>>>>>>> towards the project, except that everyone was quite happy to > have it made > >>>>>>>>>>> dormant, so it feels like there's not a lot of desire to keep > it going -- > >>>>>>>>>>> which is ok: everything comes to an end at some point, and, as > stated > >>>>>>>>>>> earlier, I'm sure there are good reasons for making log4net > dormant. As a > >>>>>>>>>>> consumer of log4net, I'd much rather not have to switch over > to another > >>>>>>>>>>> framework once there's an issue which affects me more than my > logged one > >>>>>>>>>>> (inability to flush logs -- it was on a proof-of-concept > project, so it > >>>>>>>>>>> isn't _that_ important to have the functionality right now). > >>>>>>>>>>> Apologies for the rambling message. I was prompted to reach > out by Ralph > >>>>>>>>>>> Goers in the discussion for LOG4NET-606, so I hope I haven't > been a > >>>>>>>>>> bother. > >>>>>>>>>>> -d > >>>>>>>>>>> -- > >>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > >>>>>>>>>>> If you say that getting the money is the most important thing > >>>>>>>>>>> You will spend your life completely wasting your time > >>>>>>>>>>> You will be doing things you don't like doing > >>>>>>>>>>> In order to go on living > >>>>>>>>>>> That is, to go on doing things you don't like doing > >>>>>>>>>>> Which is stupid. > >>>>>>>>>>> - Alan Watts > >>>>>>>>>>> https://www.youtube.com/watch?v=-gXTZM_uPMY > >>>>>>>>>>> *Quidquid latine dictum sit, altum sonatur. * > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >>> -- > >>> Matt Sicker > >> > >> > > > > > > -- > > Matt Sicker > > > -- Dominik Psenner

Re: Log4Net

Thanks Ralph for taking care of this. -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Sun, Apr 5, 2020, 02:28 Ralph Goers wrote: > The steps to mark Log4jNet as inactive were: > > 1. Create a tag of the source. > 2. Create an archive of the source to be place

Re: [VOTE] Log4Net dormant release

+1 -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Sun, Apr 5, 2020, 09:21 Volkan Yazıcı wrote: > +1 > > On Sun, 5 Apr 2020, 00:25 Ralph Goers wrote: > > > I have modified the STATUS.txt and README.txt for Log4Net, tagged the > > source, zipped it and then p

Re: [VOTE] Move Log4net to dormant state

+1 -- Sent from my phone. Typos are a kind gift to anyone who happens to find them. On Mon, Mar 30, 2020, 16:44 Volkan Yazıcı wrote: > +1 > > On Mon, Mar 30, 2020 at 12:23 AM Ralph Goers > wrote: > > > Seeing as there have been no volunteers after my last message regarding > > Log4Net, I propo

Re: [Discuss] Retire Log4net to the attic.

logger?view=dotnet-plat-ext-3.1 [2] https://docs.microsoft.com/en-us/dotnet/api/microsoft.extensions.dependencyinjection?view=dotnet-plat-ext-3.1 -- Dominik Psenner

Re: Problem in RollingFileAppender and ConsoleAppender .net core log4net

Hi Shubham Jain, welcome to this mailing list. Plese consider subscribing to avoid future manual interventions by a human moderator. The application works with consoleappender enabled when run from console. This indicates to me that the issue is related to the environment in headless mode. The sy

Re: Log4Net Extensions for ASPNet Core

ave written a small project that hooks log4net into asp net core > architecture and am looking to publish the package to nuget under the > apache foundation. > > > > Brian > > > > > > Sent from Outlook<http://aka.ms/weboutlook> > > > > -- > Matt Sicker > -- Dominik Psenner

Re: Is Log4Net project abandoned?

me of what I read indicates some developers moving in that direction. > > > > Any comments? > > > > Mike > > > > Get Outlook for iOS<https://aka.ms/o0ukef> > > > > From: Dominik Psenner > > Sent: Monday, Sept

Re: Is Log4Net project abandoned?

means that the decision is obviously community driven. So long people step up and get involved the project is healthy. Me being the only one to do releases, review and apply PR, etc does not scale. Any contribution is welcome! Best regards -- Dominik Psenner On Sat, Jun 29, 2019, 20:00 Kabilan VK

Re: Is Log4Net project abandoned?

n the foreseeable future. To repopulate the set of developers we could lower the bar for adding new committers. We could also push log4net back to incubation. What do you think? -- Dominik Psenner On Fri, Jun 28, 2019, 17:22 Matt Sicker wrote: > It is not abandoned; it is in need of more developers

Re: Do I need to clear programmatic loggers/appenders

://blogs.technet.microsoft.com/markrussinovich/2009/09/29/pushing-the-limits-of-windows-handles/ -- Dominik Psenner On Sat, Jun 29, 2019, 12:00 Jochen Wiedmann wrote: > You are creating millions of loggers? Meaning either of > > - I have a million different logger Id's, and create a logg

Re: Filename too long

Thanks Thorsten! I was not aware of these changes. Finally a step into the right direction. I wonder when the (not so) "special" characters ":?" will become acceptable in file and directory names.. -- Dominik Psenner On Thu, Feb 21, 2019, 11:22 Thorsten Schöning Guten Tag D

Re: [log4net] RollingFileAppender extension that backs up only a last specified period (days, hours, etc.)

On 2018-12-19 20:55, Farhan Nasim wrote: 1. Thanks for informing about the 'next generation' RollingFileAppender. I have been going through your feature branch and it seems to be the right futuristic path. I'd like to contribute to it. Awesome! Let me know if I can help you in any way. 2. How

Re: [log4net] RollingFileAppender extension that backs up only a last specified period (days, hours, etc.)

Hi Farhan, it's great to see your interest in the logging framework log4net. I'm commenting inline below .. On 2018-12-13 23:31, Farhan Nasim wrote: Have encountered a scenario in many projects where log files covering only a last user specified period is needed (e.g. last 5 days, last 3 hour

Re: Filename too long

. -- Dominik Psenner On Sun, Dec 2, 2018, 07:22 Ralph Goers Never mind. Figured out the solution. > > Ralph > > > On Dec 1, 2018, at 11:06 PM, Ralph Goers > wrote: > > > > Gary, when I clone the git repo to my Windows VM I am getting the error > message > > >

Fwd: log4net / .ner core 2.1 / SmtpAppender

Apparently I forgot to add dev at logging dot apache dot org to the recipients. Here comes the last message as a forward. -- Forwarded message - From: Dominik Psenner Date: Mon, 22 Oct 2018 at 13:57 Subject: Re: log4net / .ner core 2.1 / SmtpAppender To: Michael Karmazin (public

Re: log4net / .ner core 2.1 / SmtpAppender

Hi Michael, it's great to see your interest in log4net. I'm responding inline .. On 2018-10-22 04:14, Michael Karmazin (public) wrote: Hi Dominik, I've got your email from the log4net repo on GitHub - sorry if it's a wrong way to contact the log4net team, but I did not find any other. There

LOG4NET: LOG4NET-611

diff: https://github.com/apache/logging-log4net/commit/e769e01b85db9a8afe22ff8fdd6cc4d8f0c8ee34 I am inclined to drop support for partially trusted environments also for the other targets. If that's not a path that you can walk, then we should talk. Cheers -- Dominik Psenner

Re: Vacation

Please install a radio jammer and enjoy the time! :-) On 2018-09-17 02:57, Gary Gregory wrote: I've been told all beach umbrellas form a mesh network. No escape. Gary On Sun, Sep 16, 2018 at 6:38 PM Remko Popma wrote: Don’t the beaches have Wi-Fi? Just kidding. :-) Enjoy! On Sep 17, 2

Re: Build failed in Jenkins: logging-log4net » PR-24 #1

codebase. It resembles much on what was already done with modularizing log4j into api, core etc. On 2018-07-31 15:09, Matt Sicker wrote: Is it possible to run nant in a Docker container? I’m not too familiar with Windows containers. On Tue, Jul 31, 2018 at 06:55, Dominik Psenner wrote: I

Re: Build failed in Jenkins: logging-log4net » PR-24 #1

I assume that nant was purged from this node with the last infrastructure update. I can well understand this decision because nant is an abandoned tool that is heavily outdated. We should have moved away from it already. Unfortunately this means rewriting all the build scripts that automate bui

Re: Build failed in Jenkins: Log4j 2 3.x #148

Jenkins slaves currently have very low disk space. This may be a out of disk space in disguise. On Sat, 21 Jul 2018, 14:12 Rob Tompkins, wrote: > Looks like Jenkins timed out on checkout or something. > > > On Jul 20, 2018, at 1:08 PM, Ralph Goers > wrote: > > > > No idea. > > > > Ralph > > > >

Re: Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

On 2018-07-19 22:17, sean.co...@gmail.com wrote: Dominik, There are a number of issues in your tracker that are directly related to sticking with NetStandard 1.3. That was an early release and must have been painful to try to do a full implementation of Log4Net. 2 issues dear to me are Va

Re: AdoNetAppenderIssue Multithreaded Application Freeze

ads just never finish there > Do() Method > > > > So if I skip the part where I Recreate the database (with DROP und CREATE > Database), then it works. > > Also if put a log statement after the recreation of the database but > BEFORE the multithreaded part starts, it also works. > > > > Please advise what to do, is this the right place to address such an issue > or should it be posted as an issue on jira? > > > > Greets > > Sebastian Morgenbesser > > > > > -- Dominik Psenner

Fwd: [NuGet Gallery] Message for owners of the package 'log4net'

Hi Bart, thanks for your interest in log4net. There's an issue for this and we have an open pull request that adds this target. We have however no plan yet of when this should happen. By targeting log4net against netstandard-1.3 it can be referenced from that netstandard and any netstandard f

Re: [VOTE] Migrate git repositories to gitbox

something worth to be shared with everyone. On 18 June 2018 at 13:22, Dominik Psenner wrote: Moving to gitbox would give github users ci outputs and thus provide automated feedbacks from ci when pull requests are built. https://issues.apache.org/jira/plugins/servlet/mobile# issue/INFRA-144

Re: [log4net] crafting the next release

On Mon, 18 Jun 2018, 09:12 Stefan Bodewig, wrote: > On 2018-06-17, Dominik Psenner wrote: > > > Am Fr., 15. Juni 2018 um 10:53 Uhr schrieb Stefan Bodewig < > > bode...@apache.org>: > > >> On 2018-06-13, Dominik Psenner wrote: > > >>> That is p

Re: [VOTE] Migrate git repositories to gitbox

ood point on the clarification. I said all git repos, and that > > actually > > >>>> entails: > > >>>> > > >>>> * chainsaw > > >>>> * log4cxx > > >>>> * log4j2 and all its repos > > >>>> * log4net

Re: [log4net] crafting the next release

Am Fr., 15. Juni 2018 um 10:53 Uhr schrieb Stefan Bodewig < bode...@apache.org>: > On 2018-06-13, Dominik Psenner wrote: > > > That is possible. I restricted access to the github token to the log4net > > build job only. Stefan, would you like to try whether you can gain

Re: [log4net] crafting the next release

of storing credentials. However, I don’t know if > there is a way to limit which jobs can use the credentials. > > Ralph > > > On Jun 13, 2018, at 6:48 AM, Stefan Bodewig wrote: > > > > On 2018-06-13, Dominik Psenner wrote: > > > >> As far as I

Re: [log4net] crafting the next release

ly and build the releases locally. Matt, I think, has been talking about the PGP signature on the resulting ZIPs. At least I wouldn't trust any key that can be used by Jenkins :-) Stefan On 2018-06-12, Dominik Psenner wrote: That's an interesting question to ask. As I see it, ci should

Re: [log4net] crafting the next release

n Tue, 12 Jun 2018, 18:54 Matt Sicker, wrote: > Will you be signing and uploading them locally or via Jenkins? > > On Tue, Jun 12, 2018 at 10:05, Dominik Psenner > wrote: > > > Hi, > > > > our CI is ready to supply us with binaries along with the log4net > &g

[log4net] crafting the next release

Hi, our CI is ready to supply us with binaries along with the log4net website. This will be the first time that binaries from the CI are shipped as a release. Therefore we seek out for volunteers who evaluate the CI binaries [1]. Doing so is a great help and allows us to take the next steps o

[log4net] ci pipeline

ither. Cheers -- Dominik Psenner

Re: [log4net] dotnet test host process crashes or hangs when run by jenkins docker container

T+01:00 Dominik Psenner : > *bump* > > Has anyone out there an idea how we could troubleshoot the issue or any > ideas what else we could do? > > > > On 2018-02-03 11:51, Dominik Psenner wrote: > >> The first message was rejected by the mailing list, pl

Re: Async Appenders

ots of logs :) I'll reach out to Nick at SE and see if > he can expound upon his previous message. > > On Thu, May 10, 2018 at 5:55 PM, Dominik Psenner > wrote: > > > Interesting discussion in that pull request, yet it's missing links to > hard > > facts what th

Re: Async Appenders

licit support for it. (with > out any additional effort) > > On Thu, May 10, 2018 at 2:42 PM, Dominik Psenner > wrote: > > > Sure. This will however block by itself and take care of preserving > > compatibility with the ancient frameworks. With this mentioned, today

  1   2   3   4   >