-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
"qgis:checkvalidity" procesing algorithm not found #352
Comments
Hi, It's working again now. In trying to figure out the algorithm Id, I run the Check Validity, not sure if that had anything to do😅 Thank you for your help. Fingers crossed it's back to normal. |
I will still make a test for that. You are not the first one. |
If you need any more information from my side, just let me know. |
Message on #364
|
Hi, I'm having the same issue.. Once checking validity, what I have to do to fix it ? Thanks |
I mean do you have the algorithm ? |
I have been trying to run a query that I have previously had no problem running at all and have run into this error every time. QGIS version | 3.22.4-Białowieża QGIS code revision 3f4577ce6e Active Python plugins And this is the dialogue from the QuickOSM Panel
Finally: Error: Algorithm qgis:checkvalidity not found I do not know how to access the processing toolbox in this recent version so any help would be appreciated |
According to feedbacks on this ticket, I still don't know why the Processing algorithm was not found among some users. In the meantime, QuickOSM will just check if the algorithm exists in Processing before launching it. |
The quickosm plugin give this error if the "processing" plugin is not activate (selected) in the plugins list |
Ah yes ... thanks for the feedback. Processing is required now to run QuickOSM. It will call some QGIS native algorithms, such as Explode HStore, Refactor fields, Check validity ... So QuickOSM must check that Processing is enabled. |
Even disabling the Processing plugin, restarting QGIS, checking that Processing is well disabled, I can still call Processing algorithm : QgsApplication.processingRegistry().algorithmById("native:buffer") in the Python console, it works well. I still couldn't replicate the issue. |
I'm having the same problem now that I upgraded.
I looked for the 'processing' plugin, it was disabled. I enabled it but got this message in Plugins log and it was automatically disabled again:
|
Okay, I found the solution here: When upgrading, before installing the new version, you must delete your default profile folder, otherwise this will not be updated in the install. This folder includes such things as the core "processing" plugin, and it won't be updated if the folder already exists (somebody should probably do something about that for when we want to upgrade). If you don't want to lose your presets, etc., rename the folder to something such as "default (old)" rather than deleting it, and you can copy over your Query presets, Query history, fonts, themes, palettes, etc. in mac os the folder is here: in windows it is here: in linux it is here: info source: https://plugins.qgis.org/planet/tag/qgis3/ |
Darn, everything has been working fine after I did the above; delete default profile folder and reinstall. I have done hours of queries and edits etc.
I checked the 'processing' plugin, and now I get the same error yet again:
It says the 'processing' plugin is version 2.12.99 |
I tried creating a new user profile by selecting 'choose profile on startup' in the Profiles are of QGIS preferences/settings and restarting the app and choosing +new profile, made a new profile, installed the QuickOSM and QuickMapServices. Tried doing a basic Query (highway - unclassified, there's only one on my map) through QuickOSM and got an error. GENERAL TAB
MESSAGES TAB
QUICK OSM TAB
PROCESSING TAB
Again, if I disable then reenable the Processing plugin, I get this error:
Very odd, as it came bundled with the app as a core plugin. "version=2.12.99" I am running 3.34.3-Prizren. So??? What the heck? |
I would say, this is now "normal", because Processing is now a core plugin since QGIS 3.0 and its version is not changed. Plugin is updated with QGIS source code. See the version hardcoded in QGIS https://github.com/qgis/QGIS/blob/master/python/plugins/processing/metadata.txt#L6 Starting a new QGIS profile, as soon as you are using some plugins, Processing get disabled ? Can you identify when/why Processing get disabled ? |
What is normal? The Error says that the Processing Plugin is not compatible with this version of QGIS, but it should be, it meets the minimum requirement.
It happens with the default QGIS profile. I tried making new profiles to see if that would solve the problem. It did nothing. I tried deleting the profile folder and reinstalling QGIS and that seemed to fix the problem, but eventually the error happened again. I always use QGIS with QuickOSM and QuickMapServices. I haven't tried using QGIS without the plugins. I'd have to learn to import and query data without them to see if the QuickOSM or QuickMapServices plugin is the problem/trigger
I can try deleting everything and reinstalling QGIS, if everything works fine again, I can try to see if there is some kind of 'trigger'. Instead of deleting the profile folder, I can try deleting everything related to QGIS before the reinstall. That's all I can think of trying at the moment. |
Look at my quote ;-) I was just quoting "'processing' plugin is version 2.12.99". That's the only thing normal. Then indeed for now, I'm also clueless for now what is happening... |
I looked at your quote. It's confusing English, but thanks for explaining.
Last time I did this, it seemed to fix the problem. I don't know... maybe there are some hidden files somewhere that are the cause of the problem, or... it's a problem with this version. Super annoying. |
I just tried downloading QGIS 3.28 LTR and seeing if using this version would 'fix' the problem. No, same error:
Maybe I'll try an older version. Oh, crap, I forgot to delete the profile folder before installing. Damn, I might have screwed up my 'test'. #$%^! |
I went back to a prior version from 2023-08-20, closer to the last update of the Processing Plugin, and it works fine! So, definitely something is fucked up with the newer versions and compatibility with Processing/QuickOSM/QGIS. At least for the mac version. I didn't have any problems until I updated to the newest version. QGIS_ltr_final-3_28_10_20230819_180849 https://download.qgis.org/downloads/macos/ltr/ If I use this version, everything works as it should. |
What is the bug?
2021-09-28T12:52:43 INFO Query: highway
2021-09-28T12:52:43 INFO Encoded URL: https://lz4.overpass-api.de/api/interpreter?data=[out:xml] [timeout:25];%0A(%0A node%22highway%22;%0A way%22highway%22;%0A relation%22highway%22;%0A);%0A(._;%3E;);%0Aout body;&info=QgisQuickOSMPlugin
2021-09-28T12:52:52 INFO Request completed
2021-09-28T12:52:52 INFO Checking OSM file content C:/Users/HP/AppData/Local/Temp/request-fAUDEI.osm
2021-09-28T12:52:52 INFO The OSM file is: C:/Users/HP/AppData/Local/Temp/request-fAUDEI.osm
2021-09-28T12:52:53 CRITICAL A critical error occurred, this is the traceback:
2021-09-28T12:52:53 CRITICAL
2021-09-28T12:52:53 CRITICAL base_processing_panel.py
2021-09-28T12:52:53 CRITICAL Error: Algorithm qgis:checkvalidity not found
2021-09-28T12:52:53 CRITICAL File "C:\Users/HP/AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\QuickOSM\ui\base_processing_panel.py", line 47, in run
self._run()
Environment
The text was updated successfully, but these errors were encountered: