I am using an older version of pyOptSparse (tied to a license) which worked fine in the past with older versions of OpenMDAO (1.x) and WISDEM, but with my current OpenMDAO 3.1.0, with Anaconda/Windows,
when I issue prob.driver =om.pyOptSparseDriver()
I get this error:
AttributeError: module 'signal' has no attribute 'SIGUSR1'
Is there a work around for this?
This is definitely a bug. We have now fixed it as of OpenMDAO 3.3.1.
A workaround would require you to edit the pyoptsparse.py file and replace the default option signal.SIGUSR1 with None in the "user_terminate_signal" definition.
Related
I have an issue and it wont let me create a component because of mismatch versions, I tried deleting vue-loader, vue-template-compiler node modules. Deleting #vue/compiler-sf an reinstalling etc and i always get the same message.
new components
(use "bit tag --all [version]" to lock a version with all your changes)
> test-test ... issues found
error found while parsing the file (edit the file and fix the parsing error):
src/components/testTest.vue ->
Vue packages version mismatch:
vue#3.2.31 (C:\Users\Alex 2019\AppData\Roaming\npm\node_modules\vue\index.js)
vue-template-compiler#2.7.13 (C:\Users\Alex 2019\AppData\Roaming\npm\node_modules\bit-bin\node_modules\vue-template-compiler\package.json)
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using vue-loader#>=10.0, simply update vue-template-compiler.
If you are using vue-loader#<10.0 or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.
2022-03-08 11:21:22 WARN Selenium [DEPRECATION] [:driver_path] Selenium::WebDriver::Chrome#driver_path= is deprecated. Use Selenium::WebDriver::Chrome::Service#driver_path= instead.
An error occurred while loading spec_helper.
Failure/Error: browser = Capybara.current_session.driver.browser
Selenium::WebDriver::Error::SessionNotCreatedError:
session not created: This version of ChromeDriver only supports Chrome version 99
Current browser version is 98.0.4758.102 with binary path /usr/bin/google-chrome
The error message explains exactly what your issue is - You're using chromedriver v99.x with Chrome v98.x -- that won't work. Rather than trying to manually manage the version of chromedriver being used, just use the webdrivers gem to automatically manage it for you.
Having an issue running airflow on my M1 Mac. Keeps erroring out with error in Flask-OpenID setup command: use_2to3 is invalid. I have setuptools < 58 and still having issues.
ERROR: Could not find a version that satisfies the requirement flask-openid==1.2.5 (from versions: 0.9, 0.9.1, 1.0, 1.0.1, 1.1, 1.1.1, 1.2, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.3.0)
ERROR: No matching distribution found for flask-openid==1.2.5
Yes. It's been fixed in flask_openid 1.2.6 (It's not a problem with Airflow but with FlaskOpenID).
Looks like for some reason your setuptools is not what you think it is. See:
https://github.com/pallets-eco/flask-openid/issues/59
You have not explained a crucial things - how you are installing airflow, neither which version of Airflow you try to install - which does not help in trying to help you unfortunately, so I have to make some guesses. Here is what you can do if you cannot - for any reason - downgrade to setuptools < 0.58.
If you are using Airlfow 2 and using constraints (as you should - this is the only supported way https://airflow.apache.org/docs/apache-airflow/stable/installation/installing-from-pypi.html) for some older version of Airflow, then possibly flask-openid is 1.2.5 in those old constraint versions. Please check it and if you REALLY want to stay with an older version, then you can download the constraint file locally, modify flask-openid version to 1.2.6 and point to the file instead of the github URL as you should do normally (If you don't use constraints - start using them immediately).
However, better option than installing an old version of Airflow, will be to update to the latest version of Airflow (currently 2.2.2 but we are about to start voting on 2.2.3), where this problem is for sure fixed (also in few other versions). Airflow folows SemVer so you should be generally safe to migrate to 2.2.2 if you've used an earlier version of Airflow 2.
If you are trying to install Airflow 1.10.* - then don't do it. Move Airflow 2 immediately. Airflow 1.10 has reached end of life in June 2021 and it's almost half a year as it did not receive any fixes - it won't receive any fixes for the Flask OpenID problem, so you are pretty much on your own here.
Also you make yourself vulnerable to unpatched security issues (Airlfow 1.10 stopped receiving also critical security fixes as of June 2021).
I've downloaded a working UWP solution targeting 16299 which I changed to target 14393 (Anniversary) so it would work on all Windows 10 Phones as well. Apart from the obvious errors where the solution uses newer W10 version methods and namespaces, I also get:
Error NU1202 Package Microsoft.Data.Sqlite.Core 2.0.0 is not compatible with uap10.0.14393 (UAP,Version=v10.0.14393) / win10-x64. (multiple times)
But according to https://blogs.windows.com/buildingapps/2017/02/06/using-sqlite-databases-uwp-apps/ Microsoft SQLite should work from 14393.
I've tried installing the oldest version number available (2.0.0 instaed of 2.1.0 now included) but that doesn't change the error.
How can I solve this problem?
Dick
sqlite.core is the core version and will work only from fall creators update and above. if you want to use sqlite on older versions then you can see details here : https://learn.microsoft.com/en-us/windows/uwp/data-access/sqlite-databases
I'm trying to install Products.ATSuccessStory in a fresh Plone 4.1.3 instance on OS X Lion using Python 2.6.7. Buildout runs fine but when I try to get my instance started I get the following error:
zope.configuration.config.ConfigurationExecutionError: : (, u'cmf.ManagePortal')
in:
File "/Users/keith/Documents/plone-sites/caches/4.1.3/Products.ATSuccessStory-4.0.0-py2.6.egg/Products/ATSuccessStory/browser/configure.zcml", line 8.5-17.11
<plone:portlet
name="atss.rotating.portlet"
interface=".portlets.successstory.ISuccessStoryPortlet"
assignment=".portlets.successstory.Assignment"
view_permission="zope2.View"
edit_permission="cmf.ManagePortal"
renderer=".portlets.successstory.Renderer"
addview=".portlets.successstory.AddForm"
editview=".portlets.successstory.EditForm"
/>
I'm not as in tune with zope's inner working, but as far as I know there is absolutely nothing wrong with this portlet block in the configuration. Any guidance on how I should fix this would be greatly appreciated.
Thanks
Judging from the date of its last release, the product has likely not been updated for Plone 4.1, which requires a few very minor tweaks. These are documented at https://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-4.0-to-4.1/updating-add-on-products-for-plone-4.1/changing-dependencies-from-plone-to-products.cmfplone
ATSuccessStory 4.1.1 has just been released that includes the fix to this issue.
The source egg for this version is available on pypi but not yet (eventually will be) on plone.org