JavaFx installaion returns Cannot perform operation. Computing alternate solutions, may take a while: 15/15 - javafx

I am using
Windows 7 Ultimate edition
Java 10.0.2
Eclipse OXYGEN.3A (April 2018) Version: Oxygen.3a Release (4.7.3a)
When I try to install the JavaFx from the location http://download.eclipse.org/efxclipse/updates-released/1.2.0/site/
then I got the following
Cannot perform operation. Computing alternate solutions, may take a while: 15/15
Cannot complete the install because one or more required items could not be found.
Software being installed: e(fx)clipse - IDE - PDE 1.2.0.201501301049 (org.eclipse.fx.ide.pde.feature.feature.group 1.2.0.201501301049)
Missing requirement: JDT UI Tooling for JavaFX 1.2.0.201501301049 (org.eclipse.fx.ide.jdt.ui 1.2.0.201501301049) requires 'bundle org.eclipse.xtext.xbase.lib 2.7.1' but it could not be found
Cannot satisfy dependency:
From: e(fx)clipse - IDE - Basic 1.2.0.201501301049 (org.eclipse.fx.ide.basic.feature.feature.group 1.2.0.201501301049)
To: org.eclipse.fx.ide.jdt.ui [1.2.0.201501301049]
Cannot satisfy dependency:
From: e(fx)clipse - IDE - PDE 1.2.0.201501301049 (org.eclipse.fx.ide.pde.feature.feature.group 1.2.0.201501301049)
To: org.eclipse.fx.ide.basic.feature.feature.group 0.0.0
What requirement am I missing.

You do unterstand, that the version of e(fx)clipse you're attempting to install is basically years old!
For example check here - the updates-released section shows versions up to 3.3.0 with a fairly recent date feature_3.3.0.201805280700.
So either use this or use the marketplace entry (which seem to point to version 3.0.0) - drag and drop the install button into your running Eclipse instance or use the marketplace from within Eclipse itself (Help menu, as far as I recall or installable) and search for efxclipse.

Related

Issue running airflow on Mac M1: error in Flask-OpenID setup command: use_2to3 is invalid

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).

Azure Machine Learning integration of R: Should the 'azureml' module have an attribute 'core'?

I'm having issues with Azure Machine Learning SDK for R: "module 'azureml' has no attribute 'core'"...
For reasons that aren't my own, I have to use azureml to apply machine learning (my own stuff, written in R) to data from our data warehouse that is put in the blob storage. The modelled output should be put back into the blob storage so it can be accessed from the data warehouse.
I've written the code in R on my local machine (stored in a git repo). Preferably, I'd find some method to pull my code from git into a pipeline in the azureml environment so that it can be directly run whenever new data is available in the blob storage.
I've embarked on a tutorial-spree and found this seemingly relevant walkthrough: Train and deploy your first model with Azure ML (and this one).
But... after trying all I could think of, I'm stuck on the first steps. After installing all (or at least.. that's what I think) packages, modules, apps etc, and running the following code in RStudio:
library(azuremlsdk)
existing_ws <- get_workspace(name = name,
subscription_id = subscription_id,
resource_group)
I run into an error that I haven't been able to fix:
AttributeError: module 'azureml' has no attribute 'core'
It seems that the azuerml is supposed to have an attribute "core", but when looking at it more closely, there is indeed no such attribute.
The function "get_workspace()" is trying to access: "azureml$core$Workspace$get".
I found that "azuerML$Workspace" does exist, but then I can't figure out how to make that work.
Can anyone explain to me why I'm encountering this error?
Does anyone know of a better tutorial on how to connect my R code the azureml's cloud service?
Any pointers in the right direction are much appreciated!
EDITS - still not solved:
After advice from others, I double, triple and quadruple checked the installation.
I updated R and I'm now running:
R.version
platform x86_64-w64-mingw32
arch x86_64
os mingw32
system x86_64, mingw32
status
major 3
minor 6.2
year 2019
month 12
day 12
svn rev 77560
language R
version.string R version 3.6.2 (2019-12-12)
nickname Dark and Stormy Night
I installed Conda with Python 3.6.10.
I installed the azuremlsdk R package (I tried both provided options).
I then realized that there are some inconsistencies with the versions of the azure-modules, so I also tried installing it with the keyword 'multi-arch':
remotes::install_cran('azuremlsdk', repos = 'http://cran.us.r-project.org', INSTALL_opts=c("--no-multiarch"))
Then, I installed the azureml python sdk.
I had a look at all the versions again (using python -m pip freeze):
azure-common==1.1.24
azure-graphrbac==0.61.1
azure-mgmt-authorization==0.60.0
azure-mgmt-containerregistry==2.8.0
azure-mgmt-keyvault==2.0.0
azure-mgmt-resource==7.0.0
azure-mgmt-storage==7.1.0
azureml==0.2.7
azureml-automl-core==1.0.83.1
azureml-core==1.0.69
azureml-dataprep==1.1.36
azureml-dataprep-native==13.2.0
azureml-pipeline==1.0.69
azureml-pipeline-core==1.0.69
azureml-pipeline-steps==1.0.69
azureml-sdk==1.0.69
azureml-telemetry==1.0.69
azureml-train==1.0.69
azureml-train-automl-client==1.0.83
azureml-train-core==1.0.69
azureml-train-restclients-hyperdrive==1.0.69
As I was surprised to see all the 1.0.69 versions, instead of the 1.0.83 versions, I re-installed the azureml python sdk using:
azuremlsdk::install_azureml(version = "1.0.83")
This worked, in the sense that indeed all versions are now 1.0.83:
azure-common==1.1.24
azure-graphrbac==0.61.1
azure-mgmt-authorization==0.60.0
azure-mgmt-containerregistry==2.8.0
azure-mgmt-keyvault==2.0.0
azure-mgmt-resource==7.0.0
azure-mgmt-storage==7.1.0
azureml==0.2.7
azureml-automl-core==1.0.83.1
azureml-core==1.0.83
azureml-dataprep==1.1.36
azureml-dataprep-native==13.2.0
azureml-pipeline==1.0.83
azureml-pipeline-core==1.0.83
azureml-pipeline-steps==1.0.83
azureml-sdk==1.0.83
azureml-telemetry==1.0.83
azureml-train==1.0.83
azureml-train-automl-client==1.0.83
azureml-train-core==1.0.83
azureml-train-restclients-hyperdrive==1.0.83
But still... I get the error with the missing core. I get it both when running:
library(azuremlsdk)
get_current_run()
and also when running:
library(azuremlsdk)
existing_ws <- get_workspace(name = name,
subscription_id = subscription_id,
resource_group)
Note that the first time running this code after starting up RStudio, I get the error:
Error in py_get_attr_impl(x, name, silent) :
AttributeError: module 'azureml' has no attribute '_base_sdk_common'
And every time after that I get this error:
Error in py_get_attr_impl(x, name, silent) :
AttributeError: module 'azureml' has no attribute 'core'
Any help would be much appreciated!
This issue was introduced by the latest reticulate 1.14 release, in which reticulate would create a default r-reticulate conda environment. Since Azure ML was installing the python SDK in an environment named r-azureml, the r-reticulate environment used by reticulate was missing the python SDK. A fix for this issue was addressed in a PR and has been merged into master. Please install from GitHub for now if you have reticulate version 1.14 and are running into this issue. We will be releasing an update to CRAN shortly.
I seemed to have fixed the issue by specifically installing the python package azureml AND azureml.core:
python -m pip install azureml
and then...
python -m pip install azureml.core
I did this for the Conda version that was called by R (r-reticulate). It's a bit odd to not be able to use the Conda environment 'r-azureml' without R switching back to 'r-reticulate', but ah well... at least I don't get my 'azureml' has no attribute 'core' anymore.

Error NU1202 Package Microsoft.Data.Sqlite.Core 2.0.0 is not compatible with uap10.0.14393 (UAP,Version=v10.0.14393) / win10-x64.

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

Error when trying to add meteor-jade

I'm surprised that I can not find anything regarding the error I am seeing... basically, when I do mrt add jade (https://github.com/mquandalle/meteor-jade/), I get the following:
=> Errors while scanning packages:
While building package `jade`:
packages/compileJade/plugin/compiler.js:126: HTML is not defined (compiling tests/tests.jade)
at _.extend.visitTag (packages/compileJade/plugin/compiler.js:126)
at _.extend.visitNode (packages/compileJade/plugin/compiler.js:90)
at _.extend.visitBlock (packages/compileJade/plugin/compiler.js:74)
at _.extend.visitNode (packages/compileJade/plugin/compiler.js:84)
at _.extend.visitBlock (packages/compileJade/plugin/compiler.js:74)
at _.extend.compile (packages/compileJade/plugin/compiler.js:21)
at sourceHandler (packages/compileJade/plugin/handler.js:11)
While building plugin `compileJade` in package `jade`:
error: no such package: 'html-tools'
error: no such package: 'spacebars-compiler'
I did mrt update but still the same thing, any clue what is going on?
Try doing:
meteor update --release blaze-rc0
As explained on the meteor-jade github page:
Warning: This package is made for the new Meteor UI system, which is not released as a stable version yet. You'll need to run the blaze-rc0 release.
I believe the next major release of Meteor (0.8 or 1.0) is supposed to include the stable release of Blaze UI. At that point, you should be able to just do:
meteor update

Products.ATSuccessStory in Plone 4.1.3, Zope ConfigurationExecutionError

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

Resources