ShoreLine Reporter - A tool to collect stack traces
Locked
ShoreLine Reporter - A tool to collect stack traces
 
|
Hello everybody,
for those of you who were not at ESUG, I present ShoreLine Reporter. ShoreLine Reporter is a Pharo plugin to collect stack traces from exceptions and send them to a central repository. You can give feedback to the community by breaking things: how cool is that? * Why? We are collecting stack traces for research purposes and to identify the Pharo components that can be improved or optimized. We are also working on a web platform where users can access the submitted data and use them during the debugging process. More on that soon! * How? You can install ShoreLine Reporter by visiting the project page on SmalltalkHub: http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ Installing ShoreLine Reporter requires only a couple of seconds, and you can configure it with the level of feedback that you prefer. On the SmalltalkHub page you can find a script to automatically install ShoreLine Reporter with every new Pharo image. Just drop it in your Pharo preferences directory and forget about it. Once ShoreLine Report is installed, you can decide to configure if you want to be prompted to submit a stack trace, or to automatically submit each exception without any bother. * What? We try to collect as few data as possible: the execution stacktrace, the name of the author and the Pharo build. We do *not* any collect personal data, such as passwords or repositories. The data is currently stored on our server, at the University of Lugano. * Compatibility ShoreLine Reporter is developed for the Pharo debugger. We are improving ShoreLine Reporter to work with GTInspector, we will push an update in the following days. For any problem, contact me! Thanks, hope to see a lot of your exceptions ;-) Tommaso Dal Sasso @ REVEAL |
|
|
Shouldn’t the install script be:
=-=-=-==-=-=-==-=-=-==-=-=-= StartupLoader default executeAtomicItems: { StartupAction name: 'ShoreLine-Reporter Installer' code: [ [ Gofer it smalltalkhubUser: 'dalsat' project: 'ShoreLine-Reporter'; configuration; load. (Smalltalk at: #ConfigurationOfShoreLineReporter) load. "Setting Reporter configuration" (Smalltalk at: #SlReporter) enabled: true. (Smalltalk at: #SlReporter) perform: #autoSubmit: with: true. (Smalltalk at: #SlReporter) perform: #showSummary: with: false. (Smalltalk at: #SlReporter) perform: #showNotification: with: true. ] asJob run ] runOnce: true. }. =-=-=-==-=-=-==-=-=-==-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Oct 7, 2014, at 1:23 PM, Tommaso Dal Sasso <[hidden email]> wrote: > Hello everybody, > > for those of you who were not at ESUG, I present ShoreLine Reporter. > > ShoreLine Reporter is a Pharo plugin to collect stack traces from exceptions and send them to a central repository. > You can give feedback to the community by breaking things: how cool is that? > > > * Why? > > We are collecting stack traces for research purposes and to identify the Pharo components that can be improved or optimized. > We are also working on a web platform where users can access the submitted data and use them during the debugging process. More on that soon! > > > * How? > > You can install ShoreLine Reporter by visiting the project page on SmalltalkHub: > http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ > > Installing ShoreLine Reporter requires only a couple of seconds, and you can configure it with the level of feedback that you prefer. On the SmalltalkHub page you can find a script to automatically install ShoreLine Reporter with every new Pharo image. Just drop it in your Pharo preferences directory and forget about it. > > Once ShoreLine Report is installed, you can decide to configure if you want to be prompted to submit a stack trace, or to automatically submit each exception without any bother. > > > * What? > > We try to collect as few data as possible: the execution stacktrace, the name of the author and the Pharo build. We do *not* any collect personal data, such as passwords or repositories. The data is currently stored on our server, at the University of Lugano. > > > * Compatibility > > ShoreLine Reporter is developed for the Pharo debugger. We are improving ShoreLine Reporter to work with GTInspector, we will push an update in the following days. > > > For any problem, contact me! > > Thanks, hope to see a lot of your exceptions ;-) > Tommaso Dal Sasso @ REVEAL > |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
Yes, makes sense when installing it from the workspace.
I corrected it, thanks a lot! Tommaso On 07/10/14 23:20, Alexandre Bergel wrote: > Shouldn’t the install script be: > =-=-=-==-=-=-==-=-=-==-=-=-= > StartupLoader default executeAtomicItems: { > StartupAction > name: 'ShoreLine-Reporter Installer' > code: [ [ > Gofer it > smalltalkhubUser: 'dalsat' project: 'ShoreLine-Reporter'; > configuration; > load. > (Smalltalk at: #ConfigurationOfShoreLineReporter) load. > > "Setting Reporter configuration" > (Smalltalk at: #SlReporter) enabled: true. > (Smalltalk at: #SlReporter) perform: #autoSubmit: with: true. > (Smalltalk at: #SlReporter) perform: #showSummary: with: false. > (Smalltalk at: #SlReporter) perform: #showNotification: with: true. > > ] asJob run ] > runOnce: true. > }. > =-=-=-==-=-=-==-=-=-==-=-=-= > > Cheers, > Alexandre |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
In reply to this post by Tommaso DS
This is nice!
We should think about including this by default. It will be interesting to see what can be deduced from the data! Marcus > On 07 Oct 2014, at 18:23, Tommaso Dal Sasso <[hidden email]> wrote: > > Hello everybody, > > for those of you who were not at ESUG, I present ShoreLine Reporter. > > ShoreLine Reporter is a Pharo plugin to collect stack traces from exceptions and send them to a central repository. > You can give feedback to the community by breaking things: how cool is that? > > > * Why? > > We are collecting stack traces for research purposes and to identify the Pharo components that can be improved or optimized. > We are also working on a web platform where users can access the submitted data and use them during the debugging process. More on that soon! > > > * How? > > You can install ShoreLine Reporter by visiting the project page on SmalltalkHub: > http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ > > Installing ShoreLine Reporter requires only a couple of seconds, and you can configure it with the level of feedback that you prefer. On the SmalltalkHub page you can find a script to automatically install ShoreLine Reporter with every new Pharo image. Just drop it in your Pharo preferences directory and forget about it. > > Once ShoreLine Report is installed, you can decide to configure if you want to be prompted to submit a stack trace, or to automatically submit each exception without any bother. > > > * What? > > We try to collect as few data as possible: the execution stacktrace, the name of the author and the Pharo build. We do *not* any collect personal data, such as passwords or repositories. The data is currently stored on our server, at the University of Lugano. > > > * Compatibility > > ShoreLine Reporter is developed for the Pharo debugger. We are improving ShoreLine Reporter to work with GTInspector, we will push an update in the following days. > > > For any problem, contact me! > > Thanks, hope to see a lot of your exceptions ;-) > Tommaso Dal Sasso @ REVEAL > |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
In reply to this post by Tommaso DS
Do you have a link to ESUG's slides/presentation?
Regards! Esteban A. Maringolo 2014-10-07 13:23 GMT-03:00 Tommaso Dal Sasso <[hidden email]>: > Hello everybody, > > for those of you who were not at ESUG, I present ShoreLine Reporter. > > ShoreLine Reporter is a Pharo plugin to collect stack traces from exceptions > and send them to a central repository. > You can give feedback to the community by breaking things: how cool is that? > > > * Why? > > We are collecting stack traces for research purposes and to identify the > Pharo components that can be improved or optimized. > We are also working on a web platform where users can access the submitted > data and use them during the debugging process. More on that soon! > > > * How? > > You can install ShoreLine Reporter by visiting the project page on > SmalltalkHub: > http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ > > Installing ShoreLine Reporter requires only a couple of seconds, and you can > configure it with the level of feedback that you prefer. On the SmalltalkHub > page you can find a script to automatically install ShoreLine Reporter with > every new Pharo image. Just drop it in your Pharo preferences directory and > forget about it. > > Once ShoreLine Report is installed, you can decide to configure if you want > to be prompted to submit a stack trace, or to automatically submit each > exception without any bother. > > > * What? > > We try to collect as few data as possible: the execution stacktrace, the > name of the author and the Pharo build. We do *not* any collect personal > data, such as passwords or repositories. The data is currently stored on our > server, at the University of Lugano. > > > * Compatibility > > ShoreLine Reporter is developed for the Pharo debugger. We are improving > ShoreLine Reporter to work with GTInspector, we will push an update in the > following days. > > > For any problem, contact me! > > Thanks, hope to see a lot of your exceptions ;-) > Tommaso Dal Sasso @ REVEAL > |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
Tommaso: I also started to load it On Wed, Oct 8, 2014 at 6:09 PM, Esteban A. Maringolo <[hidden email]> wrote: Do you have a link to ESUG's slides/presentation? |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
Hello,
thanks for the feedback! I uploaded the slides here: http://shoreline.inf.usi.ch/files/ESUG2014.pdf (I tried slideshare, but it didm't work...). The video of the presentation is among the ESUG2014 videos, this are the direct links: https://www.youtube.com/watch?v=_PDQGlq4yxw&index=61&list=PLJ5nSnWzQXi_6yyRLsMMBqG8YlwfhvB0X https://www.youtube.com/watch?v=GgXdA-bcmyA&index=60&list=PLJ5nSnWzQXi_6yyRLsMMBqG8YlwfhvB0X Tommaso On 08/10/14 18:36, Martin Dias wrote: > Tommaso: I also started to load it > > On Wed, Oct 8, 2014 at 6:09 PM, Esteban A. Maringolo > <[hidden email] <mailto:[hidden email]>> wrote: > > Do you have a link to ESUG's slides/presentation? > > Regards! > Esteban A. Maringolo > > > 2014-10-07 13:23 GMT-03:00 Tommaso Dal Sasso > <[hidden email] <mailto:[hidden email]>>: > > Hello everybody, > > > > for those of you who were not at ESUG, I present ShoreLine Reporter. > > > > ShoreLine Reporter is a Pharo plugin to collect stack traces > from exceptions > > and send them to a central repository. > > You can give feedback to the community by breaking things: how > cool is that? > > > > > > * Why? > > > > We are collecting stack traces for research purposes and to > identify the > > Pharo components that can be improved or optimized. > > We are also working on a web platform where users can access the > submitted > > data and use them during the debugging process. More on that soon! > > > > > > * How? > > > > You can install ShoreLine Reporter by visiting the project page on > > SmalltalkHub: > > http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ > <http://www.smalltalkhub.com/#%21/%7Edalsat/ShoreLine-Reporter/> > > > > Installing ShoreLine Reporter requires only a couple of seconds, > and you can > > configure it with the level of feedback that you prefer. On the > SmalltalkHub > > page you can find a script to automatically install ShoreLine > Reporter with > > every new Pharo image. Just drop it in your Pharo preferences > directory and > > forget about it. > > > > Once ShoreLine Report is installed, you can decide to configure > if you want > > to be prompted to submit a stack trace, or to automatically > submit each > > exception without any bother. > > > > > > * What? > > > > We try to collect as few data as possible: the execution > stacktrace, the > > name of the author and the Pharo build. We do *not* any collect > personal > > data, such as passwords or repositories. The data is currently > stored on our > > server, at the University of Lugano. > > > > > > * Compatibility > > > > ShoreLine Reporter is developed for the Pharo debugger. We are > improving > > ShoreLine Reporter to work with GTInspector, we will push an > update in the > > following days. > > > > > > For any problem, contact me! > > > > Thanks, hope to see a lot of your exceptions ;-) > > Tommaso Dal Sasso @ REVEAL > > > > |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
> On 09 Oct 2014, at 11:25, Tommaso Dal Sasso <[hidden email]> wrote: > > Hello, > > thanks for the feedback! > > I uploaded the slides here: http://shoreline.inf.usi.ch/files/ESUG2014.pdf (I tried slideshare, but it didm't work…) They are on the ESUG account: http://www.slideshare.net/esug/shoreline-bugs-the-smalltalk-way Marcus |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
In reply to this post by Tommaso DS
I was thinking... would it make sense to have this in the image by default? On Tue, Oct 7, 2014 at 6:23 PM, Tommaso Dal Sasso <[hidden email]> wrote: Hello everybody, -- Marcus Denker -- [hidden email] http://www.marcusdenker.de |
|
|
In reply to this post by Tommaso DS
tommaso
send us a working script not something that we should browse and understand. Stef On 7/10/14 11:23, Tommaso Dal Sasso wrote: > Hello everybody, > > for those of you who were not at ESUG, I present ShoreLine Reporter. > > ShoreLine Reporter is a Pharo plugin to collect stack traces from > exceptions and send them to a central repository. > You can give feedback to the community by breaking things: how cool is > that? > > > * Why? > > We are collecting stack traces for research purposes and to identify > the Pharo components that can be improved or optimized. > We are also working on a web platform where users can access the > submitted data and use them during the debugging process. More on that > soon! > > > * How? > > You can install ShoreLine Reporter by visiting the project page on > SmalltalkHub: > http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ > > Installing ShoreLine Reporter requires only a couple of seconds, and > you can configure it with the level of feedback that you prefer. On > the SmalltalkHub page you can find a script to automatically install > ShoreLine Reporter with every new Pharo image. Just drop it in your > Pharo preferences directory and forget about it. > > Once ShoreLine Report is installed, you can decide to configure if you > want to be prompted to submit a stack trace, or to automatically > submit each exception without any bother. > > > * What? > > We try to collect as few data as possible: the execution stacktrace, > the name of the author and the Pharo build. We do *not* any collect > personal data, such as passwords or repositories. The data is > currently stored on our server, at the University of Lugano. > > > * Compatibility > > ShoreLine Reporter is developed for the Pharo debugger. We are > improving ShoreLine Reporter to work with GTInspector, we will push an > update in the following days. > > > For any problem, contact me! > > Thanks, hope to see a lot of your exceptions ;-) > Tommaso Dal Sasso @ REVEAL > > |
|
|
In reply to this post by Marcus Denker-4
It depends:
- is it overriding? - is it well packaged? - is it cross cutting a lot? Stef On 27/10/14 07:01, Marcus Denker wrote:
|
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
In reply to this post by Tommaso DS
Marcus wrote
> I was thinking... would it make sense to have this in the image by default? Not all my work is open source. How do I make sure I don't inadvertently leak information? Stephan |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
It would need to filter and only send those traces that are part of the image.
In a later step, it would be interesting to give people the same infrastructure for their
own code, private to them.
(like those error stack trace collecting tools that are used for mobile apps) On Mon, Oct 27, 2014 at 1:18 PM, Stephan Eggermont <[hidden email]> wrote:
|
Re: ShoreLine Reporter - A tool to collect stack traces
|
In reply to this post by Marcus Denker-4
pretty every one does this nowdays since most people are too busy or dont care about bug reports it would make sense for a dialog to pop up the first time to ask the user if he allows the tool to collect information and then store that to the image so it can collect the info so it wont have to bother the user again. Standard practice. On Mon, Oct 27, 2014 at 2:01 PM, Marcus Denker <[hidden email]> wrote:
|
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
In reply to this post by stepharo
Hello everybody,
thanks for your feedback. > On 27/10/14 07:01, Marcus Denker wrote: >> I was thinking... would it make sense to have this in the image by >> default? On 27/10/14 13:07, stepharo wrote: > It depends: > - is it overriding? > - is it well packaged? > - is it cross cutting a lot? > I have been extremely careful to be as clean as possible. The stack trace catching is implemented with a PreDebuggingAction without overriding any of the existing code. It was one of my first design goals, especially because the purpose of the tool is to be completely pluggable and unpluggable without influencing the system. Also, we tested it for three months in daily development activities, so it is reasonably stable. We are analyzing the stack traces we collected so far to see if what useful information a developer can obtain from that. I would love to see ShoreLine Reporter used to help the development of the Pharo ecosystem and I would be glad to help if you think that such a tool could be useful if integrated into Pharo. Tommaso >> >> >> On Tue, Oct 7, 2014 at 6:23 PM, Tommaso Dal Sasso >> <[hidden email] <mailto:[hidden email]>> wrote: >> >> Hello everybody, >> >> for those of you who were not at ESUG, I present ShoreLine Reporter. >> >> ShoreLine Reporter is a Pharo plugin to collect stack traces from >> exceptions and send them to a central repository. >> You can give feedback to the community by breaking things: how >> cool is that? >> >> >> * Why? >> >> We are collecting stack traces for research purposes and to >> identify the Pharo components that can be improved or optimized. >> We are also working on a web platform where users can access the >> submitted data and use them during the debugging process. More on >> that soon! >> >> >> * How? >> >> You can install ShoreLine Reporter by visiting the project page >> on SmalltalkHub: >> http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ >> <http://www.smalltalkhub.com/#%21/%7Edalsat/ShoreLine-Reporter/> >> >> Installing ShoreLine Reporter requires only a couple of seconds, >> and you can configure it with the level of feedback that you >> prefer. On the SmalltalkHub page you can find a script to >> automatically install ShoreLine Reporter with every new Pharo >> image. Just drop it in your Pharo preferences directory and >> forget about it. >> >> Once ShoreLine Report is installed, you can decide to configure >> if you want to be prompted to submit a stack trace, or to >> automatically submit each exception without any bother. >> >> >> * What? >> >> We try to collect as few data as possible: the execution >> stacktrace, the name of the author and the Pharo build. We do >> *not* any collect personal data, such as passwords or >> repositories. The data is currently stored on our server, at the >> University of Lugano. >> >> >> * Compatibility >> >> ShoreLine Reporter is developed for the Pharo debugger. We are >> improving ShoreLine Reporter to work with GTInspector, we will >> push an update in the following days. >> >> >> For any problem, contact me! >> >> Thanks, hope to see a lot of your exceptions ;-) >> Tommaso Dal Sasso @ REVEAL >> >> >> >> >> -- >> -- >> Marcus Denker -- [hidden email] <mailto:[hidden email]> >> http://www.marcusdenker.de > |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
In reply to this post by stepharo
On 27/10/14 13:05, stepharo wrote: > tommaso > send us a working script > not something that we should browse and understand. > > Stef You are right, the loading script is in the project page, but it is indeed another step of unneeded indirection. Thanks, Tommaso P.s.: for the sake of completeness, this is the script to load ShoreLine Reporter and configure it to automatically submit the stack traces without bothering the user ;-) StartupLoader default executeAtomicItems: { StartupAction name: 'ShoreLine-Reporter Installer' code: [ [ Gofer it smalltalkhubUser: 'dalsat' project: 'ShoreLine-Reporter'; configuration; load. #ConfigurationOfShoreLineReporter asClass load. "Setting Reporter configuration" #SlReporter asClass enabled: true. #SlReporter asClass autoSubmit: true. #SlReporter asClass showSummary: false. #SlReporter asClass showNotification: true. ] asJob run ] runOnce: true. }. > > On 7/10/14 11:23, Tommaso Dal Sasso wrote: >> Hello everybody, >> >> for those of you who were not at ESUG, I present ShoreLine Reporter. >> >> ShoreLine Reporter is a Pharo plugin to collect stack traces from >> exceptions and send them to a central repository. >> You can give feedback to the community by breaking things: how cool >> is that? >> >> >> * Why? >> >> We are collecting stack traces for research purposes and to identify >> the Pharo components that can be improved or optimized. >> We are also working on a web platform where users can access the >> submitted data and use them during the debugging process. More on >> that soon! >> >> >> * How? >> >> You can install ShoreLine Reporter by visiting the project page on >> SmalltalkHub: >> http://www.smalltalkhub.com/#!/~dalsat/ShoreLine-Reporter/ >> >> Installing ShoreLine Reporter requires only a couple of seconds, and >> you can configure it with the level of feedback that you prefer. On >> the SmalltalkHub page you can find a script to automatically install >> ShoreLine Reporter with every new Pharo image. Just drop it in your >> Pharo preferences directory and forget about it. >> >> Once ShoreLine Report is installed, you can decide to configure if >> you want to be prompted to submit a stack trace, or to automatically >> submit each exception without any bother. >> >> >> * What? >> >> We try to collect as few data as possible: the execution stacktrace, >> the name of the author and the Pharo build. We do *not* any collect >> personal data, such as passwords or repositories. The data is >> currently stored on our server, at the University of Lugano. >> >> >> * Compatibility >> >> ShoreLine Reporter is developed for the Pharo debugger. We are >> improving ShoreLine Reporter to work with GTInspector, we will push >> an update in the following days. >> >> >> For any problem, contact me! >> >> Thanks, hope to see a lot of your exceptions ;-) >> Tommaso Dal Sasso @ REVEAL >> >> > > |
Re: ShoreLine Reporter - A tool to collect stack traces
|
|
In reply to this post by Marcus Denker-5
On Mon, Oct 27, 2014 at 1:18 PM, Stephan Eggermont <[hidden email]
<mailto:[hidden email]>> wrote: > > Marcus wrote > > I was thinking... would it make sense to have this in the image > by default? > > Not all my work is open source. How do I make sure I don't > inadvertently > leak information? > > Stephan > > given your experience. The status of ShoreLine Reporter is that it stores the name of the class and the name of the method, no parameter is involved. I indeed understand that the name of the method and the trace of calls may reveal information that a user may want to keep private. As Markus said, we could filter the classes included in the stock Pharo image, but this would discard classes of projects like Voyage or Seaside. Another option could be to provide the user with a way to filter some classes, for example by matching the class name prefix. I am the first one to dislike "Big Brother" systems, so I am particularly sensible on the matter. What do you think? Thanks, Tommaso On 27/10/14 13:22, Marcus Denker wrote: > It would need to filter and only send those traces that are part of > the image. > > In a later step, it would be interesting to give people the same > infrastructure for their > own code, private to them. > > (like those error stack trace collecting tools that are used for > mobile apps) > > > > |
|
|
In reply to this post by Tommaso DS
> I have been extremely careful to be as clean as possible. The stack
Sounds promising :)
> trace catching is implemented with a PreDebuggingAction without > overriding any of the existing code. It was one of my first design > goals, especially because the purpose of the tool is to be completely > pluggable and unpluggable without influencing the system. > Also, we tested it for three months in daily development activities, > so it is reasonably stable. > > We are analyzing the stack traces we collected so far to see if what > useful information a developer can obtain from that. I would love to > see ShoreLine Reporter used to help the development of the Pharo > ecosystem and I would be glad to help if you think that such a tool > could be useful if integrated into Pharo. |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |