Bug jail / bug hunt weeks?


These were not any special “initiatives”, that’s common sense. We need to make a public release, we make a deeper dive into our app, we fix bugs. :man_shrugging: If a bug is in an external library, we try to fix it upstream because we don’t want to support/update a separate fork of a library.

Sure, I see you have your pet peeves in the app, but try installing a version from the beginning of 2018 and compare it to what we have now :sunny:

So, my logic behind all this is that if the app is getting better, it means that what we do works, somehow. Sure it is a very subjective feeling, but the last thing I want is to make everyone to try to optimize some metric as a KPI. In general, treating code quality by then number of open bugs is hardly better then measuring programmer’s productivity by lines of code written.

A huge amount of issues in the repo is also explained by the fact that we used to use them for project management and coordination and now we mostly not. So it is good that the bot is closing them.

On the other hand, you are doing a nice job of keeping some of the bugs alive, thanks!


I hope you don’t take this personally, I’m just a concerned citizen. I’m commenting on what I see, and what I see right now is that both implementations I’m using - Windows and Android 9+ - are currently broken or semi-functional for me and there’s been surprisingly little feedback on it. I find it hard to believe there’s so few people with Android 9+ phones that can just say “can’t reproduce” or “here too”. So I’m just trying to find out why I’m getting this impression, if it’s my fault, and how I can help and/or learn more.

IMO this is not a good argument. Sacrifices have been made to get to this state (centralized elements were introduced), so I wouldn’t call it an all out win, but I would agree that, in broad strokes, we have a better app now than we used to, of course. My peeves are not pet, though - they’re blockers and why I don’t use Status nearly as much as I’d want to.

100% agree - not something I was recommending. The kudos would have as much significance to one’s job as the Slack kudos did, it’s just flair for the gamification lovers out there.

Yes but none of those are tagged as bugs I think?

Anyway, what I’m saying is I’m seeing the Chrome effect forming. The Google Chrome repo has open issues from 2009, but those were all neglected because they had to add bells and whistles to compete with Firefox’s bells and whistles.

I think discussions like these contribute to transparency and clear things up, far from murkying up. We have extremely silly blockers in Nimbus too but we’re aware of them and have plans for dedicated “tech debt removal” periods. That’s all I’m trying to bring up here to see if there’s any interest in crowdsourcing or Statussourcing it.


Again, you make it sound (to me) like everyone with Android 9 has this issue, but that is just not true. Some phones with Android 9 have it, some don’t. It’s not reproducible with Android 9 on my Pixel 2, so it is not even everyone with it.

As for centralized elements (as of mailservers and Infura): they were introduced before beginning of 2018, so they aren’t the reason the app has become better last year. And we also expanded from 2 to 5 platforms that are used by the core contributors.

I have nothing against the initiatives to focus on bugfixing. If anything, I did them as a standard practice at Opera.
I read into your initial post the attitude I really disliked and it really hurt my feelings. I really felt that the team wasn’t judged appropriately. I hope I’m the most sensitive one there :slight_smile:


Is this an appropriate moment to ask why the desktop version doesn’t work when subscribed to a single public channel?


Maybe, if you describe what “doesn’t work” means, which version is that and how to reproduce it :slight_smile: But submitting a GH issue is a better idea, of course.


V 0.9.0 (2777809) on Linux

After it wiped out my local configuration, I subscribed to #status and it did not sync. I waited a few hours, then subscribed to 3-4 more channels - that’s when it started syncing.

More than the bug itself, this is about user experience - the only feelings that matter :wink:


I’m very sorry about that, not my intention at all. I’ll try and be much more tactful in the future.


yeah, that sucks
can you open a github issue in https://github.com/status-im/status-react/ ?

I’m not sure how prioritized the desktop is right now though, but it sounds like a fairly simple issue…


No problem.

Okay, just to put numbers in perspective.

(1) Priorities. We have 6 developers on Core Improvements that actually fixes issues and improves different aspects of the app vs 2 developers on the Sticker Market.

(2) High-severity issues. Sure, we have 16 open as of now, and the oldest one is very old, but to put it in perspective:
- 2 were fixed since this post was opened;
- 11 were fixes since December 1st
- 129 were closed since July when we actually introduced the severity field.


Okay, thanks for the insight!


In theory, yes, but in practice this is what happened the last time I did: https://github.com/status-im/status-react/issues/7122

Maybe the number of reported bugs is actually low because of this.


I don’t know… We have a QA team that tests (mobile) nightlies, and we have automation so it looks unlikely to me.

On the other hand, I agree that that bug reporting experience was very bad. Obviously, the issue was fixed somewhere, but no one actually answered.
Probably, right now to get your issue properly noticed, you also want to ping people in #status-desktop channel. And that should be improved, yes.


The good news is that this particular bug has been already reported and is being handled: https://github.com/status-im/status-react/issues/7282

The bad news is that it’s cross-platform.


Not sure if that is bad or good. But anyway, feel free to ping me or Anna on Status (or #status-core) or via email if you bump into something.

So, maybe we can just make a poll for people to specify top 3 blockers for them and a version that they use? Maybe after the next release (beginning of February)? What do you think?


A poll would be great to get a partial snapshot of user experience - even if it’s just us chickens participating.


sure, I will schedule an internal poll in the first half of February, I want the next public release to happen before that :slight_smile:


How about this.

We have Bamboo with a list of devices per person. If we pull that and merge with a manually populated list of devices from people (I have Android 9, iphone SE, iphone 6s+) we have a master list of devices. Make groups / teams in GH and ping them when an issue needs to be reproed, especially if simple like mine with the crash post sleep. I’m 100% sure you’ll get at least 30% of the pinged people to try it out which would help the issue immensely.

I know we have QA but that’s hardly enough at this scale and we all use Status so why not use everyone. We’re in the rare position of having contact information of a core and engaged userbase, let’s use it.


It’s a good idea for the issues that aren’t easily reproducible for devs/QA.

especially if simple like mine with the crash post sleep

about that, I actually asked for your help to verify this issue is fixed here: https://github.com/status-im/status-react/pull/7334#issuecomment-457239672 :wink:

I think we used to have this master list somewhere in a Google Sheet, @anna should know about that. I wasn’t probably update to the all core contributors devices.


I usually keep track of all issues, I’m not sure how I missed this. I think it’s because the bot’s updates are also sent out as issue updates, and since my email inbox uses nested emails, it only showed me the latest email (bot update) and not my mention :grimacing: I’ll make a new filter for mentions in particular. Giving you feedback asap.

Chaos Unicorn Day, April 1 2019 (aka kill our cluster)

If there is a second list of devices, feel free to send it my way and I can add them into BambooHR so we have a single source of truth. Cheers!