Qt bug report closed incorrectly... I believe
-
What can I do if a Qt bug report I have made has been (I believe) erroneously closed by the individual it is assigned to.
I have submitted many bug reports over the years and I'm glad to say that a significant number of them have been addressed and resolved, typically P1-P3.
I have also had instructive conversations with certain people (and even been thanked for my contributions).
While most of the Qt team is responsive and polite, there have been a couple of individuals who appear to try and find the quickest way to mark an issue as 'out of scope' or 'incomplete' or 'needs more info' and show poor regard for the person submitting the issue, with no apparent interest in engaging in a discussion with a view to really understanding whether there is something worth addressing in the code.
If an issue is assigned to such an individual and gets closed down without the opportunity to respond, what can I do? How can I get the issue reviewed by another member of staff so that the bug can actually get dealt with and not sidelined.
It's not good for product quality, let alone community morale, when this happens.
-
What can I do if a Qt bug report I have made has been (I believe) erroneously closed by the individual it is assigned to.
I have submitted many bug reports over the years and I'm glad to say that a significant number of them have been addressed and resolved, typically P1-P3.
I have also had instructive conversations with certain people (and even been thanked for my contributions).
While most of the Qt team is responsive and polite, there have been a couple of individuals who appear to try and find the quickest way to mark an issue as 'out of scope' or 'incomplete' or 'needs more info' and show poor regard for the person submitting the issue, with no apparent interest in engaging in a discussion with a view to really understanding whether there is something worth addressing in the code.
If an issue is assigned to such an individual and gets closed down without the opportunity to respond, what can I do? How can I get the issue reviewed by another member of staff so that the bug can actually get dealt with and not sidelined.
It's not good for product quality, let alone community morale, when this happens.
@paulmasri said in Qt bug report closed incorrectly... I believe:
mark an issue as 'out of scope' or 'incomplete' or 'needs more info'
Did you address this? Can you post the link to this ticket?
-
@paulmasri said in Qt bug report closed incorrectly... I believe:
If an issue is assigned to such an individual and gets closed down without the opportunity to respond, what can I do? How can I get the issue reviewed by another member of staff so that the bug can actually get dealt with and not sidelined.
You should always have the possibility to comment, so please politely explain in a comment why you think the task was closed incorrectly. If you have a commercial license, you can also involve Qt support (a good idea anyhow).
-
@paulmasri said in Qt bug report closed incorrectly... I believe:
If an issue is assigned to such an individual and gets closed down without the opportunity to respond, what can I do? How can I get the issue reviewed by another member of staff so that the bug can actually get dealt with and not sidelined.
You should always have the possibility to comment, so please politely explain in a comment why you think the task was closed incorrectly. If you have a commercial license, you can also involve Qt support (a good idea anyhow).
Obviously there's a particular bug that I'm referring to at the moment. I have indeed posted a comment laying out why I think the issue remains valid and in scope and I've addressed the specific comments of the assigned person.
I'll give it a few days for them to respond before I post a link here. Hopefully it will be picked up again.
I'm sole developer for an organisation with a startup licence not a full commercial licence, so I can't go via the Qt support route.
But taking my question in the more general case, what avenues are open to us if we believe we're stuck in this situation and it's not being addressed?
-
Obviously there's a particular bug that I'm referring to at the moment. I have indeed posted a comment laying out why I think the issue remains valid and in scope and I've addressed the specific comments of the assigned person.
I'll give it a few days for them to respond before I post a link here. Hopefully it will be picked up again.
I'm sole developer for an organisation with a startup licence not a full commercial licence, so I can't go via the Qt support route.
But taking my question in the more general case, what avenues are open to us if we believe we're stuck in this situation and it's not being addressed?
I really wonder why such a topic is brought up here - if you think that it was wrongly closed then re-open it and hope it gets fixed. I also closed bugs when I think it's not a Qt issue - if the reporter prooves me wrong it's ok.
Afaics you already did some debugging so since you've the code and it's only specific to a recent os version maybe try to add some debug stuff to see what's happening and compare it with the older os version.
-
I really wonder why such a topic is brought up here - if you think that it was wrongly closed then re-open it and hope it gets fixed. I also closed bugs when I think it's not a Qt issue - if the reporter prooves me wrong it's ok.
Afaics you already did some debugging so since you've the code and it's only specific to a recent os version maybe try to add some debug stuff to see what's happening and compare it with the older os version.
I have not had a response to the bug report I'm referring to at the moment, which is https://bugreports.qt.io/browse/QTBUG-114674
@Christian-Ehrlicher said in Qt bug report closed incorrectly... I believe:
I really wonder why such a topic is brought up here - if you think that it was wrongly closed then re-open it and hope it gets fixed. I also closed bugs when I think it's not a Qt issue - if the reporter prooves me wrong it's ok.
As a member of the community I don't have the ability to re-open it. I have done all I can by responding.
Afaics you already did some debugging so since you've the code and it's only specific to a recent os version maybe try to add some debug stuff to see what's happening and compare it with the older os version.
It looks like you've found the specific bug report in this case. I have compared behaviours between versions of iOS and determined that the audio stream fails (incorrectly I believe) on iOS 16. I have also determined that Qt Multimedia does not show the state as having changed from QAudio::ActiveState or error state as having changed from QAudio::NoError.
If there is more that I can do please do suggest. I think I've identified where the problem lies, which is within QAudioSink.
-
I have not had a response to the bug report I'm referring to at the moment, which is https://bugreports.qt.io/browse/QTBUG-114674
@Christian-Ehrlicher said in Qt bug report closed incorrectly... I believe:
I really wonder why such a topic is brought up here - if you think that it was wrongly closed then re-open it and hope it gets fixed. I also closed bugs when I think it's not a Qt issue - if the reporter prooves me wrong it's ok.
As a member of the community I don't have the ability to re-open it. I have done all I can by responding.
Afaics you already did some debugging so since you've the code and it's only specific to a recent os version maybe try to add some debug stuff to see what's happening and compare it with the older os version.
It looks like you've found the specific bug report in this case. I have compared behaviours between versions of iOS and determined that the audio stream fails (incorrectly I believe) on iOS 16. I have also determined that Qt Multimedia does not show the state as having changed from QAudio::ActiveState or error state as having changed from QAudio::NoError.
If there is more that I can do please do suggest. I think I've identified where the problem lies, which is within QAudioSink.
@paulmasri said in Qt bug report closed incorrectly... I believe:
As a member of the community I don't have the ability to re-open it. I have done all I can by responding.
When you created the bug report then you can also re-open it.
-
@paulmasri said in Qt bug report closed incorrectly... I believe:
As a member of the community I don't have the ability to re-open it. I have done all I can by responding.
When you created the bug report then you can also re-open it.
@Christian-Ehrlicher said in Qt bug report closed incorrectly... I believe:
@paulmasri said in Qt bug report closed incorrectly... I believe:
As a member of the community I don't have the ability to re-open it. I have done all I can by responding.
When you created the bug report then you can also re-open it.
Thanks! I did not know that. I have reopened it, along with a comment to justify why.
