Re: [chainsaw] Next steps? Or is it over?
Thank you Scott, It is very encouraging you are joining this effort! Now I feel more confident we can make a new release! I am doing my best to learn more about Chainsaw and contribute further! On Wed, Nov 29, 2023, at 20:13, Scott Deboy wrote: > I'll go through the UI and re-add small features that I think are > critical but were lost in the log4j1-jettison effort. > > I'll follow-up in a new thread. > > Scott > > > On 11/28/23, Scott Deboy wrote: >> I've fixed the logger tree split pane UI (left artifacts when you >> drag), and I've added VFSLogFilePatternReceiver support and it works >> fine. >> >> To test VFSLogFilePatternReceiver: >> * Start Chainsaw >> * View, Show Receivers menu >> * Hit the 'create' icon in the receivers pane >> * Select 'New VFSLogFilePatternReceiver' >> >> In the bottom section of the receivers pane, enter values for the >> following attributes: >> >> fileURL - provide a local text file path (triple-slashes in the URI), like: >> file:///Users/sdeboy/somefile.txt >> >> logFormat - just use a simple format for now: >> MESSAGE >> >> tailing: >> true >> >> * Click OK >> >> A new tab with the receiver name - default is 'Receiver' - will be >> created and entries from the log file will be routed there. >> >> In a text editor, add some lines to the file and you'll see the new >> lines appear in the bottom of the log table. >> >> Scott >> >> >> >> On 11/28/23, Christian Grobmeier wrote: >>> Hi Scott, >>> >>> I believe you; thanks for speaking up and being around. >>> >>> How can I help? >>> >>> I think Chainsaw needs to see a release soon, so what can I do to help >>> you? >>> >>> I am glad to clean up things and whatever is necessary. >>> >>> Kind regards, >>> Christian >>> >>> On Wed, Nov 29, 2023, at 00:15, Scott Deboy wrote: I have dropped the ball here, but will commit to working on this, this year. I want to preserve a bunch of what can be done in the https://github.com/apache/logging-chainsaw/tree/chainsaw-with-log4j1-dep branch, and some of that just isn't possible because equivalent functionality was never added to log4j2. Remote tailing via the VFSLogFilePatternReceiver, with the existing filter and search support, is enough I think. I'll jump in and help. Scott Scott On 11/28/23, Christian Grobmeier wrote: > Hello, > > I have started to clean up a few things that seemed good to me. > The last time I sent a message like this was 1.5 months ago, but there > was > not much progress in maintaining it. > > I am currently in a state where I slowly get what should be happening, > but > unfortunately, it does not. > We are not ready to release a new version, nor do we know what is > necessary > to release one. > > We have lots of dead code in Chainsaw, and it is tough to understand > "what > should it do?" > > I move around many Swing components to understand better, because the > code > is complex. However, I didn't see how Chainsaw would do anything > beneficial. > It's not working at all. > > Yes, I now what a "receiver" is meant to do. But apart from this > description > we have no specific goal nor do we actually receive anything (or I > don't > know how). > > For an ordinary person, it seems impossible to connect to a running > server > to tail a log file (I am not sure if it should do it) or even analyze a > regular log file. > > This is when either old committers step up to tell a new one, like me, > what > is going on or to set a specific goal that we want to reach with a new > version of Chainsaw. > > It was fun to clean up, but we need to talk more about Chainsaw. As for > me, > it is unusable, hard to fix and we need a new set of goals and radical > refactoring to make it work again. If we are not agreeing on what it > should > do, it's time to go dormant. I am sorry to say this, I like Chainsaw. > But > me > alone - I can't fix it. > > Please let me know, > Christian > > >>> >>
Re: [chainsaw] Next steps? Or is it over?
I'll go through the UI and re-add small features that I think are critical but were lost in the log4j1-jettison effort. I'll follow-up in a new thread. Scott On 11/28/23, Scott Deboy wrote: > I've fixed the logger tree split pane UI (left artifacts when you > drag), and I've added VFSLogFilePatternReceiver support and it works > fine. > > To test VFSLogFilePatternReceiver: > * Start Chainsaw > * View, Show Receivers menu > * Hit the 'create' icon in the receivers pane > * Select 'New VFSLogFilePatternReceiver' > > In the bottom section of the receivers pane, enter values for the > following attributes: > > fileURL - provide a local text file path (triple-slashes in the URI), like: > file:///Users/sdeboy/somefile.txt > > logFormat - just use a simple format for now: > MESSAGE > > tailing: > true > > * Click OK > > A new tab with the receiver name - default is 'Receiver' - will be > created and entries from the log file will be routed there. > > In a text editor, add some lines to the file and you'll see the new > lines appear in the bottom of the log table. > > Scott > > > > On 11/28/23, Christian Grobmeier wrote: >> Hi Scott, >> >> I believe you; thanks for speaking up and being around. >> >> How can I help? >> >> I think Chainsaw needs to see a release soon, so what can I do to help >> you? >> >> I am glad to clean up things and whatever is necessary. >> >> Kind regards, >> Christian >> >> On Wed, Nov 29, 2023, at 00:15, Scott Deboy wrote: >>> I have dropped the ball here, but will commit to working on this, this >>> year. >>> >>> I want to preserve a bunch of what can be done in the >>> https://github.com/apache/logging-chainsaw/tree/chainsaw-with-log4j1-dep >>> branch, and some of that just isn't possible because equivalent >>> functionality was never added to log4j2. >>> >>> Remote tailing via the VFSLogFilePatternReceiver, with the existing >>> filter and search support, is enough I think. >>> >>> I'll jump in and help. >>> >>> Scott >>> >>> Scott >>> >>> On 11/28/23, Christian Grobmeier wrote: Hello, I have started to clean up a few things that seemed good to me. The last time I sent a message like this was 1.5 months ago, but there was not much progress in maintaining it. I am currently in a state where I slowly get what should be happening, but unfortunately, it does not. We are not ready to release a new version, nor do we know what is necessary to release one. We have lots of dead code in Chainsaw, and it is tough to understand "what should it do?" I move around many Swing components to understand better, because the code is complex. However, I didn't see how Chainsaw would do anything beneficial. It's not working at all. Yes, I now what a "receiver" is meant to do. But apart from this description we have no specific goal nor do we actually receive anything (or I don't know how). For an ordinary person, it seems impossible to connect to a running server to tail a log file (I am not sure if it should do it) or even analyze a regular log file. This is when either old committers step up to tell a new one, like me, what is going on or to set a specific goal that we want to reach with a new version of Chainsaw. It was fun to clean up, but we need to talk more about Chainsaw. As for me, it is unusable, hard to fix and we need a new set of goals and radical refactoring to make it work again. If we are not agreeing on what it should do, it's time to go dormant. I am sorry to say this, I like Chainsaw. But me alone - I can't fix it. Please let me know, Christian >> >
Re: [chainsaw] Next steps? Or is it over?
I've fixed the logger tree split pane UI (left artifacts when you drag), and I've added VFSLogFilePatternReceiver support and it works fine. To test VFSLogFilePatternReceiver: * Start Chainsaw * View, Show Receivers menu * Hit the 'create' icon in the receivers pane * Select 'New VFSLogFilePatternReceiver' In the bottom section of the receivers pane, enter values for the following attributes: fileURL - provide a local text file path (triple-slashes in the URI), like: file:///Users/sdeboy/somefile.txt logFormat - just use a simple format for now: MESSAGE tailing: true * Click OK A new tab with the receiver name - default is 'Receiver' - will be created and entries from the log file will be routed there. In a text editor, add some lines to the file and you'll see the new lines appear in the bottom of the log table. Scott On 11/28/23, Christian Grobmeier wrote: > Hi Scott, > > I believe you; thanks for speaking up and being around. > > How can I help? > > I think Chainsaw needs to see a release soon, so what can I do to help you? > > I am glad to clean up things and whatever is necessary. > > Kind regards, > Christian > > On Wed, Nov 29, 2023, at 00:15, Scott Deboy wrote: >> I have dropped the ball here, but will commit to working on this, this >> year. >> >> I want to preserve a bunch of what can be done in the >> https://github.com/apache/logging-chainsaw/tree/chainsaw-with-log4j1-dep >> branch, and some of that just isn't possible because equivalent >> functionality was never added to log4j2. >> >> Remote tailing via the VFSLogFilePatternReceiver, with the existing >> filter and search support, is enough I think. >> >> I'll jump in and help. >> >> Scott >> >> Scott >> >> On 11/28/23, Christian Grobmeier wrote: >>> Hello, >>> >>> I have started to clean up a few things that seemed good to me. >>> The last time I sent a message like this was 1.5 months ago, but there >>> was >>> not much progress in maintaining it. >>> >>> I am currently in a state where I slowly get what should be happening, >>> but >>> unfortunately, it does not. >>> We are not ready to release a new version, nor do we know what is >>> necessary >>> to release one. >>> >>> We have lots of dead code in Chainsaw, and it is tough to understand >>> "what >>> should it do?" >>> >>> I move around many Swing components to understand better, because the >>> code >>> is complex. However, I didn't see how Chainsaw would do anything >>> beneficial. >>> It's not working at all. >>> >>> Yes, I now what a "receiver" is meant to do. But apart from this >>> description >>> we have no specific goal nor do we actually receive anything (or I don't >>> know how). >>> >>> For an ordinary person, it seems impossible to connect to a running >>> server >>> to tail a log file (I am not sure if it should do it) or even analyze a >>> regular log file. >>> >>> This is when either old committers step up to tell a new one, like me, >>> what >>> is going on or to set a specific goal that we want to reach with a new >>> version of Chainsaw. >>> >>> It was fun to clean up, but we need to talk more about Chainsaw. As for >>> me, >>> it is unusable, hard to fix and we need a new set of goals and radical >>> refactoring to make it work again. If we are not agreeing on what it >>> should >>> do, it's time to go dormant. I am sorry to say this, I like Chainsaw. But >>> me >>> alone - I can't fix it. >>> >>> Please let me know, >>> Christian >>> >>> >
Re: [chainsaw] Next steps? Or is it over?
Hi Scott, I believe you; thanks for speaking up and being around. How can I help? I think Chainsaw needs to see a release soon, so what can I do to help you? I am glad to clean up things and whatever is necessary. Kind regards, Christian On Wed, Nov 29, 2023, at 00:15, Scott Deboy wrote: > I have dropped the ball here, but will commit to working on this, this year. > > I want to preserve a bunch of what can be done in the > https://github.com/apache/logging-chainsaw/tree/chainsaw-with-log4j1-dep > branch, and some of that just isn't possible because equivalent > functionality was never added to log4j2. > > Remote tailing via the VFSLogFilePatternReceiver, with the existing > filter and search support, is enough I think. > > I'll jump in and help. > > Scott > > Scott > > On 11/28/23, Christian Grobmeier wrote: >> Hello, >> >> I have started to clean up a few things that seemed good to me. >> The last time I sent a message like this was 1.5 months ago, but there was >> not much progress in maintaining it. >> >> I am currently in a state where I slowly get what should be happening, but >> unfortunately, it does not. >> We are not ready to release a new version, nor do we know what is necessary >> to release one. >> >> We have lots of dead code in Chainsaw, and it is tough to understand "what >> should it do?" >> >> I move around many Swing components to understand better, because the code >> is complex. However, I didn't see how Chainsaw would do anything beneficial. >> It's not working at all. >> >> Yes, I now what a "receiver" is meant to do. But apart from this description >> we have no specific goal nor do we actually receive anything (or I don't >> know how). >> >> For an ordinary person, it seems impossible to connect to a running server >> to tail a log file (I am not sure if it should do it) or even analyze a >> regular log file. >> >> This is when either old committers step up to tell a new one, like me, what >> is going on or to set a specific goal that we want to reach with a new >> version of Chainsaw. >> >> It was fun to clean up, but we need to talk more about Chainsaw. As for me, >> it is unusable, hard to fix and we need a new set of goals and radical >> refactoring to make it work again. If we are not agreeing on what it should >> do, it's time to go dormant. I am sorry to say this, I like Chainsaw. But me >> alone - I can't fix it. >> >> Please let me know, >> Christian >> >>
Re: [chainsaw] Next steps? Or is it over?
I have dropped the ball here, but will commit to working on this, this year. I want to preserve a bunch of what can be done in the https://github.com/apache/logging-chainsaw/tree/chainsaw-with-log4j1-dep branch, and some of that just isn't possible because equivalent functionality was never added to log4j2. Remote tailing via the VFSLogFilePatternReceiver, with the existing filter and search support, is enough I think. I'll jump in and help. Scott Scott On 11/28/23, Christian Grobmeier wrote: > Hello, > > I have started to clean up a few things that seemed good to me. > The last time I sent a message like this was 1.5 months ago, but there was > not much progress in maintaining it. > > I am currently in a state where I slowly get what should be happening, but > unfortunately, it does not. > We are not ready to release a new version, nor do we know what is necessary > to release one. > > We have lots of dead code in Chainsaw, and it is tough to understand "what > should it do?" > > I move around many Swing components to understand better, because the code > is complex. However, I didn't see how Chainsaw would do anything beneficial. > It's not working at all. > > Yes, I now what a "receiver" is meant to do. But apart from this description > we have no specific goal nor do we actually receive anything (or I don't > know how). > > For an ordinary person, it seems impossible to connect to a running server > to tail a log file (I am not sure if it should do it) or even analyze a > regular log file. > > This is when either old committers step up to tell a new one, like me, what > is going on or to set a specific goal that we want to reach with a new > version of Chainsaw. > > It was fun to clean up, but we need to talk more about Chainsaw. As for me, > it is unusable, hard to fix and we need a new set of goals and radical > refactoring to make it work again. If we are not agreeing on what it should > do, it's time to go dormant. I am sorry to say this, I like Chainsaw. But me > alone - I can't fix it. > > Please let me know, > Christian > >
[chainsaw] Next steps? Or is it over?
Hello, I have started to clean up a few things that seemed good to me. The last time I sent a message like this was 1.5 months ago, but there was not much progress in maintaining it. I am currently in a state where I slowly get what should be happening, but unfortunately, it does not. We are not ready to release a new version, nor do we know what is necessary to release one. We have lots of dead code in Chainsaw, and it is tough to understand "what should it do?" I move around many Swing components to understand better, because the code is complex. However, I didn't see how Chainsaw would do anything beneficial. It's not working at all. Yes, I now what a "receiver" is meant to do. But apart from this description we have no specific goal nor do we actually receive anything (or I don't know how). For an ordinary person, it seems impossible to connect to a running server to tail a log file (I am not sure if it should do it) or even analyze a regular log file. This is when either old committers step up to tell a new one, like me, what is going on or to set a specific goal that we want to reach with a new version of Chainsaw. It was fun to clean up, but we need to talk more about Chainsaw. As for me, it is unusable, hard to fix and we need a new set of goals and radical refactoring to make it work again. If we are not agreeing on what it should do, it's time to go dormant. I am sorry to say this, I like Chainsaw. But me alone - I can't fix it. Please let me know, Christian
