shimmering-obsidian: [Bug]: cannot search (o ... search)
Bug Description
cannot search using o ...
Relevant Screenshot

To Reproduce
No response
Debugging Log
[09:30:39.782] Logging Started...
[09:30:42.331] Shimmering Obsidian[Script Filter] Queuing argument '(null)'
[09:30:42.616] Shimmering Obsidian[Script Filter] Script with argv '(null)' finished
[09:30:42.621] ERROR: Shimmering Obsidian[Script Filter] Code 1: /Users/boxcounter/Alfred.alfredpreferences/workflows/user.workflow.B844E779-37E6-4BDB-8178-E9B075D501F3/scripts/o_search.js: execution error: Error: SyntaxError: JSON Parse error: Unexpected EOF (-2700)
[09:37:27.490] Shimmering Obsidian[Script Filter] Queuing argument '(null)'
[09:39:39.871] Shimmering Obsidian[Script Filter] Queuing argument '(null)'
Workflow Configuration 1
Workflow Configuration 2
Version & System Information
- macOS: 13.1 (22C65)
- Obsidian: 1.1.9
- Alfred: v5.0.6 [2110]
- Shimmering-obsidian: v.3.3.0
- Advanced URI: v1.31.2
- Metadata Extractor: v1.1.0
Make sure you have done the following
- I have updated to the latest version of this workflow.
- I have read the Troubleshooting Documentation.
- If the
o…main search does not work, I have tried rerunningosetupand it still does not work. - If I updated to version 3+ for the first time, I have disabled migrating workflow cutomizations. (If you haven’t, you can simply re-download and install the latest release from GitHub and uncheck
Migrate my workflow customizations.)
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 19 (10 by maintainers)
Commits related to this issue
- fix: more validation for o-search & oinfo (#108) — committed to chrisgrieser/shimmering-obsidian by chrisgrieser a year ago
- fix: write canvas.json metad. on osetup (fix #108) — committed to chrisgrieser/shimmering-obsidian by chrisgrieser a year ago
- refactor/fix:write vaultpath tofile (#108,#101) — committed to chrisgrieser/shimmering-obsidian by chrisgrieser a year ago
thanks for the thorough retracing! I have added some extra safety-nets to handle this stuff, so the issue should not occur anymore.