-
-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error with Tasks in Titled Callouts – Obsidian v1.6.0 to v1.6.4 [fixed by making v1.6.5 recreate its cache] #2890
Comments
Created after Q&A: |
I have reported my findings to the Obsidian devs informally in this and the next few Discord posts. Basically, Obsidian is reporting that the 4 tasks in the file are on different lines to what they actually are, and Tasks uses that info from Obsidian to find the task lines. I will add the |
There are multiple reports of issues with tasks in callout in Obsidian 1.6.3 already in the Forum: https://forum.obsidian.md/t/last-checkbox-in-a-callout-cant-be-clicked/82742/3 The above says it will be fixed in 1.7 - no ETA. |
@georgziganek, thanks for the info. If you want someone to try reproducing it, please post text for people to copy and paste. Thank you. |
@claremacrae Sure, no problem! Here's the text block:
and here is the query. You'll have to update the folder path accordingly.
|
By removing all my custom callout labels, I can verify that the Task query worked as it should and returned all tasks. |
Awesome - thank you both very much indeed! |
I'm also experiencing this issue with: Any task created inside any callout box will not be Listed in a Tasks query, but if I move the task outside the Callout, it shows up. |
Yes, I have confirmed this. It is specifically the labels on callouts that cause a task to be not found. For each labelled callout, Obsidian adds 1 to the line numbers it reports for the locations of the task lines and tags inside the callout. There are 3 callouts with labels here, meaning that only the 4th (and any later) to be read by Tasks:
There are 0 callout labels here, so all 4 tasks are found:
It does not matter whether they are custom callouts, or nested - or whether they are collapsible: the issue is the labels on the callout lines. |
I have renamed the issue to clarify that the problem is labelled callouts, not nested ones. |
And again, the issue is Obsidian giving incorrect line numbers in this situation. |
I have written up all my research on this here: Also, I note that the Obsidian team is now saying this will be fixed in 1.6.4 instead of 1.7 - still no ETA, of course. |
Magnificent, thanks for escalating this in the Obsidian Forums! |
Obsidian 1.6.4 has been released to Insiders. It says it has fixed the problems with callouts.
Unfortunately, I am not seeing any improvements to the behaviour described in this issue. |
I can also confirm that this update had no impact on the issue. Still missing tasks in query if custom labels used in callouts. |
Ah - it turns out that the fix requires knowing that an edit needs to be made anywhere in the markdown file containing the labelled callout, in order to force Obsidian to re-parse the file and generate correct line numbers. After a couple of seconds of inactivity, the cached data will be updated. Don't Undo the edit, as apparently the cached data would then be reverted. You will need to do this in all your files that contain labelled callouts. |
Can confirm! Adding an edit immediately brought back the proper tasks query results. |
My comments have been separated out to a new report, so the research is now detailed at: |
…outs This required forcing Obsidian to regenerate its cache for the following files, by editing them, so its fix for its cause of #2890: - callout_labelled.md - callouts_nested_issue_2890_labelled.md
test: Add tests of Obsidian cache with labelled callouts - see #2890
I didn't intend #2905 to auto-close this issue. |
Hi, I've written documentation for the Tasks plugin about the underlying Obsidian issue: Missing tasks in callouts with some Obsidian 1.6.x versions I will update the page as the Obsidian behaviour improves. |
Now that I have written Tasks docs about this, I've labelled this issue as 'no action needed', as it really is an Obsidian issue and needs to be fully fixed in Obsidian. |
But I'll leave this open, and pinned, until there is a fixed public Obsidian release. |
The Tasks docs write-up is well done and should help guide other users with similar callout issues. Thank you for all the efforts here! |
Thank you @damclarkd - it did take a ridiculously long time to try and shrink down all the information into a useful structure, so I appreciate your kind comment greatly. |
From the Obsidian team:
You will need to do this on all vaults, on all devices... I've updated the Tasks notes on this issue. |
I'm closing this now, as no further action is needed in Tasks... This issue is pinned, so it will still be visible to any users that come to the Tasks repo to report the problem... |
Please check that this issue hasn't been reported before.
Expected Behavior
Running Tasks Query on the current file.path should find all Tasks in Callouts.
Current behaviour
Starting in Obsidian V1.6.3, What I have been able to reproduce is when I have nested callouts, the number of tasks in the query is incorrect based on the number of callout levels.
i.e.
I have: Header Callout(Month), then Group Callout, then Task Callout. In the Task Callout I have four Tasks. In the Query it will ignore the first three tasks. If I remove the Header Callout and have only two levels of nested Callouts, it will ignore only the first two Tasks.
Basically -- The number of nested callouts = number of ignored Tasks. If 3 callouts nested, only Task4 is found.
The Query is simply:
And the test md is:
Steps to reproduce
Which Operating Systems are you using?
Obsidian Version
1.6.3
Tasks Plugin Version
7.4.0
Checks
Possible solution
This appears to be an Obsidian problem not a Tasks issue.
The text was updated successfully, but these errors were encountered: