Bug 123404 - Removing xtext annotations doesn't throw an exception - it silently fails
Summary: Removing xtext annotations doesn't throw an exception - it silently fails
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-02-12 11:59 UTC by Hamish McIntyre-Bhatty
Modified: 2019-09-30 11:27 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Hamish McIntyre-Bhatty 2019-02-12 11:59:47 UTC
Description:
When creating and removing annotations as shown in /sw/qa/python/xtext.py, annotations can be removed twice without causing exceptions or any kind of warning. This seems to be a silent failure, but I don't know if there are any side effects of doing this.

Steps to Reproduce:
1. Run the xtext unit test:
2. cd sw
3. make PythonTest_sw_python PYTHON_TEST_NAME="xtext"
4. The test completes successfully, even though it removes annotations twice.

Actual Results:
The test completes - unexpected success.

Expected Results:
The test as it is at the moment should fail in some way - throw an exception. I expected it to segfault, but it doesn't.


Reproducible: Always


User Profile Reset: No



Additional Info:
Throw an exception or issue some other kind of warning or error when an annotation that doesn't exist is removed.
Comment 1 Xisco Faulí 2019-03-21 14:37:28 UTC
Hello Hamish McIntyre-Bhatty,
Thanks for reporting this issue.
Would you mind sending an email to the mailing list for discussing this issue ? -> https://wiki.documentfoundation.org/Development/Mailing_List
Comment 2 Hamish McIntyre-Bhatty 2019-03-23 11:07:58 UTC
I have sent an email.
Comment 3 Miklos Vajna 2019-03-29 16:41:15 UTC
Do you have a suggestion how to do this in a backwards-compatible way? Otherwise the change is probably not worth it.
Comment 4 Hamish McIntyre-Bhatty 2019-04-02 16:17:51 UTC
No, I don't really have enough knowledge of the Libreoffice codebase to really have any idea what this might affect, or in what way :/. Is there any kind of unified set of documents I can read to better understand how everything gels together?

Perhaps a warning could be logged - like a deprecation warning or similar, so we can figure out what this affects?

If not fixed, maybe this should be documented somewhere though, because whoever wrote the unit test seemed surprised to discover that this happened?

Hamish
Comment 5 Xisco Faulí 2019-09-30 11:27:33 UTC
(In reply to Miklos Vajna from comment #3)
> Do you have a suggestion how to do this in a backwards-compatible way?
> Otherwise the change is probably not worth it.

Closing as RESOLVED WONTFIX