Mark Change Detection app as unstable?
-
That sounds unfortunate. The app being marked as stable on our side mostly refers to the package itself. For example if data is correctly migrated and if it starts up fine as well as basic functionality is working.
For app internal bugs it would be helpful to create upstream issues at https://github.com/dgtlmoon/changedetection.io/issues
Of course if it turns out the app is overall entering some instable state as to not be useful anymore for longer, then I guess instead we should maybe remove the package itself.
-
That sounds unfortunate. The app being marked as stable on our side mostly refers to the package itself. For example if data is correctly migrated and if it starts up fine as well as basic functionality is working.
For app internal bugs it would be helpful to create upstream issues at https://github.com/dgtlmoon/changedetection.io/issues
Of course if it turns out the app is overall entering some instable state as to not be useful anymore for longer, then I guess instead we should maybe remove the package itself.
-
@nebulon “Unstable” can actually have many meanings, eg. from a purely technical or operational (user side) standpoint.
In my opinion, app instability should also be considered when the use of the app itself or specific functions may be subject to distruptions related to the development process.
However, I understand that, from a purely technical standpoint, the definition of instability is a bit more restrictive.
About next steps, I'll wait for the app to work properly again and disable automatic updates.
I'll then update only after reviewing the changelog and possibly testing that everything is working properly.
This way, I can revert immediately, not days later @robi
Thanks all for your comments and suggestions.
-
That sounds unfortunate. The app being marked as stable on our side mostly refers to the package itself. For example if data is correctly migrated and if it starts up fine as well as basic functionality is working.
For app internal bugs it would be helpful to create upstream issues at https://github.com/dgtlmoon/changedetection.io/issues
Of course if it turns out the app is overall entering some instable state as to not be useful anymore for longer, then I guess instead we should maybe remove the package itself.
You have my vote.
@nebulon said in Mark Change Detection app as unstable?:
Of course if it turns out the app is overall entering some instable state as to not be useful anymore for longer, then I guess instead we should maybe remove the package itself.
-
You have my vote.
@nebulon said in Mark Change Detection app as unstable?:
Of course if it turns out the app is overall entering some instable state as to not be useful anymore for longer, then I guess instead we should maybe remove the package itself.
@svtx said in Mark Change Detection app as unstable?:
POS app
However, it does work when it's set up. At least for me.
cost me too much time of my life
Well, yeah.
Maybe it's time to fork it and make it usable lol
-
Hi all! dgtlmoon from changedetection.io / https://github.com/dgtlmoon/changedetection.io here
I can say that we've added about 1200 lines of automated tests and fixed a whole bunch of bugs, the most recent release is even more solid than previous releases
@svtx if you can not use such strong language I would probably appreciate it
Of course if it turns out the app is overall entering some instable state as to not be useful anymore for longer, then I guess instead we should maybe remove the package itself.
This is completely untrue, I can prove this by the fact that theres 28,300+ stars on github and only a bug reported about once a week, there is a LOT of users, plus all of our paid accounts, it is now very stable
I would like to remind people that it's better to be productive when complaining than just complaining - it's nice if people can write exactly what is the wrong and what their settings were instead of just saying "its a piece of SH...T", this is not mature opensource community behaviour in that respect
however, please be calm, and remember that it is free opensource software and sometimes mistakes happen, its only a couple of guys writing the software for you to enjoy for free
there is nothing unstable about it, and I can assure you that for every bug that is reported there is several automated tests added so that it doesnt ever happen again
If there are any issues, PLEASE report them on https://github.com/dgtlmoon/changedetection.io instead of just saying saying "it's a POS" I would really appreciate it.
Thank you - and please be sure that you're on the latest version 0.50.38
-
@james @svtx @p44 Hello from changedetection - please - if you can be productive rather than just complaining, please let me know what those bugs were? we had a lot of refactors and fixes in the last week but everything should be fixed, we added 1200+ lines of automated tests, and our github issue queue is VERY quiet
"unstable state" i dont think so, we just had to drop a few updates around the notifications, but again, NO ONE here has bothered to explain exactly what's their issue - all should be fixed now
-
Hello @dgtlmoon
I am sorry that your experience started so negatively.
This is normally not the standard in our forum and I believe we can turn this into a productive topic as it should be.
@dgtlmoon said in Mark Change Detection app as unstable?:
please let me know what those bugs were?
That is what I asked of the users.
@dgtlmoon said in Mark Change Detection app as unstable?:
if you can not use such strong language I would probably appreciate it
Only because of you I now know what the
POSeven means. I was unaware that it was"its a piece of SH...T". Thank you for that.
This is indeed no productive way and does not improve anything.
@svtx I have reviewed your previous topic on @change-detection, and it seems your overall negative view on this software stems from not getting it to work in the proper way.
But nowhere did you explain your issues. Otherwise, we (the Cloudron Forum) would have been able to assist in a meaningful way.
Could you please describe your issues so that we can work on that?
Regarding the:
@dgtlmoon said in Mark Change Detection app as unstable?:"unstable state"
For clarification, if we Cloudron mark an app as unstable, it does not mean the software itself is unstable.
Since we have to package the app to work within the Cloudron ecosystem the issue can be with us packaging the app.
To improve future topics for @change-detection @dgtlmoon I took the liberty and took the official bug issue template from your GitHub and changed it a little to fit the Cloudron scope.
If people create topic for @change-detection they can use the template.
Once again @dgtlmoon I must apologize about this negative experience.
Let's make it a productive one! -
Hi all! dgtlmoon from changedetection.io / https://github.com/dgtlmoon/changedetection.io here
I can say that we've added about 1200 lines of automated tests and fixed a whole bunch of bugs, the most recent release is even more solid than previous releases
@svtx if you can not use such strong language I would probably appreciate it
Of course if it turns out the app is overall entering some instable state as to not be useful anymore for longer, then I guess instead we should maybe remove the package itself.
This is completely untrue, I can prove this by the fact that theres 28,300+ stars on github and only a bug reported about once a week, there is a LOT of users, plus all of our paid accounts, it is now very stable
I would like to remind people that it's better to be productive when complaining than just complaining - it's nice if people can write exactly what is the wrong and what their settings were instead of just saying "its a piece of SH...T", this is not mature opensource community behaviour in that respect
however, please be calm, and remember that it is free opensource software and sometimes mistakes happen, its only a couple of guys writing the software for you to enjoy for free
there is nothing unstable about it, and I can assure you that for every bug that is reported there is several automated tests added so that it doesnt ever happen again
If there are any issues, PLEASE report them on https://github.com/dgtlmoon/changedetection.io instead of just saying saying "it's a POS" I would really appreciate it.
Thank you - and please be sure that you're on the latest version 0.50.38
@dgtlmoon said in Mark Change Detection app as unstable?:
If there are any issues, PLEASE report them
Hi there! I don't think your app is bad, on the contrary I've been using it successfully for a while now and it's working pretty stable. My main issues with the app are mostly on the UI/UX side. But since I don't have to teach non-technical people how to use it and I mostly got the hang of it by now, it's not really an issue anymore for me.
-
@andreasdueren Thanks for the feedback, but again, I have to repeat to you - yet again - rather than just complaining about that something doesnt work (including UX UI) - please try to be productive and give more information about what is confusing for the users or is hard to manage in the UI/UX so it can be improved on
-
@svtx said in Mark Change Detection app as unstable?:
POS app
However, it does work when it's set up. At least for me.
cost me too much time of my life
Well, yeah.
Maybe it's time to fork it and make it usable lol
@andreasdueren said in Mark Change Detection app as unstable?:
Well, yeah.
Maybe it's time to fork it and make it usable lol
This is what you said, now please own it, since you seem to already have formed an idea of what can be improved, why don't you share it? Or now that you've pulled up by the admin suddenly everyone is like "oh yeah its ok i was just referring to this thing i cant explain" when you even basically agreed with someone else calling the software a "POS"
cost me too much time of my life
Well, yeah.
Maybe it's time to fork it and make it usable lol@james @nebulon can we delete this whole forum thread? it's looked incredibly bad, disrespectful and unprofessional for all involved
@james secondly, this kind of negative absolutely unprofessional and negative experience in this forum thread is exactly the reason why a lot of people dont go near opensource, it is exactly these kinds of attitudes that are still following forum threads for decades now and should be absolutely NOT tollerated
thank you
-
@james thanks for your answer.
Updates in versions 0.50.28–0.50.38 introduced several notification-related issues:
https://changedetection.io/CHANGELOG.txt
Two problems were particularly impactful from my side: migration of text/markdown notification types failed, causing some notifications to be missed.
Also, selecting the notification format from the menu sometimes resulted in the wrong type being sent, such as receiving an HTML-formatted notification instead of plain text.
That issues affected existing features, not new ones.
As you can see, there is a lot of active development.
Is very positive side, of course, as it means app is being actively maintained, but such frequent changes ca affect stability and break existing functionality.
Here updates activity:
https://git.cloudron.io/packages/changedetection-app/activity
In my opinion, level and frequency of updates makes app a bit unstable at the moment.
@dgtlmoon I wrote here about:
said in Mark Change Detection app as unstable?:
Updates in versions 0.50.28–0.50.38 introduced several notification-related issues:
https://changedetection.io/CHANGELOG.txt
Two problems were particularly impactful from my side: migration of text/markdown notification types failed, causing some notifications to be missed.
Also, selecting the notification format from the menu sometimes resulted in the wrong type being sent, such as receiving an HTML-formatted notification instead of plain text.
These problems affected instance from updates 0.50.28–0.50.38.
In the past, I've had similar issues with RSS generation, which is equally crucial for notifications.
Obviously, I don't want to dwell on the specific technical issues in this discussion, which are recommended - which, as noted, should be reported on your GitHub - but I did suggest marking the application as "unstable" due to these uncertainties in the releases which could disrupt the application's proper and normal functioning.
Everyone on this forum supports open source software and, eventually, recognizes its value by paying for licenses if with value. However, this doesn't mean we should necessarily settle.
I've been using Cloudron on various instances for over 5 years, with various paid licenses, and I've never never never had one problems with the stability of Cloudron or other apps. Also, amazing support, amazing forum, and a place where we try to help each other.
Therefore, I believe it's right to post observations when something isn't giving some troubles, always with the goal of improving and addressing each issue.
The request to delete the post also seems inappropriate: it's a form of censorship. On the contrary, it's important to explore these issues s community can make a more informed decision about whether and which solutions to use.
Obviously I disagree with the other forms of offense towards ChangeDetection.io and I thank you for the development work you are doing, as I immediately recognized in my first response post (where I wrote: As you can see, there is a lot of active development. Is very positive side, of course)
Thanks again for your efforts.
-
@dgtlmoon I wrote here about:
said in Mark Change Detection app as unstable?:
Updates in versions 0.50.28–0.50.38 introduced several notification-related issues:
https://changedetection.io/CHANGELOG.txt
Two problems were particularly impactful from my side: migration of text/markdown notification types failed, causing some notifications to be missed.
Also, selecting the notification format from the menu sometimes resulted in the wrong type being sent, such as receiving an HTML-formatted notification instead of plain text.
These problems affected instance from updates 0.50.28–0.50.38.
In the past, I've had similar issues with RSS generation, which is equally crucial for notifications.
Obviously, I don't want to dwell on the specific technical issues in this discussion, which are recommended - which, as noted, should be reported on your GitHub - but I did suggest marking the application as "unstable" due to these uncertainties in the releases which could disrupt the application's proper and normal functioning.
Everyone on this forum supports open source software and, eventually, recognizes its value by paying for licenses if with value. However, this doesn't mean we should necessarily settle.
I've been using Cloudron on various instances for over 5 years, with various paid licenses, and I've never never never had one problems with the stability of Cloudron or other apps. Also, amazing support, amazing forum, and a place where we try to help each other.
Therefore, I believe it's right to post observations when something isn't giving some troubles, always with the goal of improving and addressing each issue.
The request to delete the post also seems inappropriate: it's a form of censorship. On the contrary, it's important to explore these issues s community can make a more informed decision about whether and which solutions to use.
Obviously I disagree with the other forms of offense towards ChangeDetection.io and I thank you for the development work you are doing, as I immediately recognized in my first response post (where I wrote: As you can see, there is a lot of active development. Is very positive side, of course)
Thanks again for your efforts.
@p44 On the topic of issues in changedetection.io, I want to illustrate to you how insanely difficult it is to even get accurate issue/bug reporting from the general public, something that should take an hour to fix often takes over a week because people
- Dont follow the issue template
- Give misleading, wrong, often completely made up information
- Say they followed the instructions when they didnt
- Miss out critical things from the issue report - like the exact (except for password/host etc) info from the notification URLs
And then I come here and people calling it "A piece of shit", and yet, people cant even fill in a issue report with complete information
infuriating
-
@dgtlmoon yes, I can understand how frustrating is.
Inaccurate reporting is a big waste of time, specially from developers side, and specially when those rules are written and are ignored by most...
Thanks for sharing your concerns, also will help this forum to have better reports and to be better place.
About negative feedback on this thread, please don’t care, I’m sorry if you got a different image about this place.
-
@p44 I'm trying to track down this issue https://github.com/dgtlmoon/changedetection.io/issues/3591 is it possible that cloudron has deployed old code or incomplete code? I wonder if theres a way for publishers (me) to know if the code you're running on Cloudron is accurate to my release and not making the publisher look bad?
-
Late to this thread.
@svtx please don't use such wording. as you can tell, it's offensive and not constructive. technical discussions simply get derailed like this thread. you have used such language in other threads in the past too which I have ignored (like SUX and calling cloudron backups defunct).
@dgtlmoon I have removed the offensive wording . If the user continues, we will react accordingly.
FWIW, we use changedetection to track changes on the minecraft pages. It works quite reliably for us. Thanks for your great work!
