Bug 131339 - calc: #REF! error condition not evaluated for dependent cells, needs recalc, autocalculate failure
Summary: calc: #REF! error condition not evaluated for dependent cells, needs recalc, ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.4.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, regression
Depends on:
Blocks: Calculate
  Show dependency treegraph
 
Reported: 2020-03-14 17:23 UTC by b.
Modified: 2024-06-10 03:13 UTC (History)
3 users (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 b. 2020-03-14 17:23:52 UTC
Description:
an error condition injected in the head of a dependecy chain is (sometimes in distinct situations) not evaluated for dependent cells, it needs any recalc to apply to the dependent cells, autocalculate doesn't handle. bug maybe older, i observed it in 7.0.0.0.a0+ and tested 6.2.8.2 to be buggy too. 
on a quick check: it looks as if only errors injected above the dependent cells are critical, similar constructions at the left, right or bottom border worked ok. 

Steps to Reproduce:
minimum reproducer: 
0. fresh sheet, 
1. put '=B1' into B2, 
2. observe B2 showing '0' - correct, 
3. copy B2 - ctrl-c, 
4. paste into B1 - ctrl-v, 
5. observe B1 showing #REF! or err:522 - correct, 
6. observe B2 still showing '0' - incorrect, 
7. whenever a cell gets an error condition making it 'uncalculateable' all dependency chains should inherit that and switch to err too, that insn't respected for B2 in this case, 
7a. it is! respected for - at least some - other error conditions, e.g. changing B1 to '=0/0' or deleting row 1 instead of implementing error formulae, 


Actual Results:
dependent cells (B2 in this case) don't inherit #REF! or err:522 error conditions from upstream cells, 

Expected Results:
error condition handed over to dependent cells, 


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: 9ed75e2c65544b4f71c73e1c51a68d74e31d544b
CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win; 
Locale: de-DE (de_DE); UI-Language: en-US
Calc:
Comment 1 Telesto 2020-04-26 21:02:05 UTC
Repro with
Versie: 6.4.3.2 (x64)
Build ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8
CPU-threads: 4; Besturingssysteem: Windows 6.3 Build 9600; UI-render: GL; VCL: win; 
Locale: nl-NL (nl_NL); UI-taal: nl-NL
Calc: CL

Also in
Versie: 4.4.7.2 
Build ID: f3153a8b245191196a4b6b9abd1d0da16eead600
Locale: nl_NL

but not in
Version: 4.3.7.2
Build ID: 8a35821d8636a03b8bf4e15b48f59794652c68ba

Another observation
1. Type =B1 into B2
2. Enable track changes
3. Copy B2
4. Paste in B1
5. CTRL+SHIFT+F9 
6. Edit -> Track Changes -> Manage
7. Discard the change (paste)
8. #REF! still around -> Also not in 4.3.7.2
Comment 2 Buovjaga 2020-06-09 19:40:29 UTC
Bibisected with Linux 44max to https://git.libreoffice.org/core/+/6b4e767cf90e4f384a6b3dd43aa51c09b500b97b%5E!/
Use group-area listeners during copy & paste if we can.

Same blame as bug 128975
Comment 3 QA Administrators 2022-06-10 03:33:49 UTC Comment hidden (obsolete)
Comment 4 QA Administrators 2024-06-10 03:13:32 UTC
Dear b.,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug