Is there any problem with fiware repositories? - fiware

Good morning!
I have tried to install cygnus on fiware lab instances and Amazon EC2 instances but I get an error that the repositories dosen´t exist.
I atached image with the problem, what´s happening?
Thank you for your response!
EDIT ANSWER
I have tried edit the file fiware.repo with the following content https://nexus.lab.fiware.org/repository/raw/public/repositories/el/7/x86_64/fiware-release.repo , but when I tried to install I get an error again.
Whtat's happening?

Yes, it was a problem with the public repository. Please, try again.

Related

Does the new update of mosaic (1.8.3) not work on mac?

I notice that the mosaic package was updated a few days ago (1.8.3). Since then, I keep getting an error message that mosaic can't load.
> library(mosaic)
Error: package or namespace load failed for ‘mosaic’:
object ‘compare’ is not exported by 'namespace:mosaicCore'
The package installed, and it works on a PC. I've tried reinstalling R and R studio to be sure but I keep getting the same error. Anyone who has had the same problem or figured out how to fix it?
It works fine on a Mac (it was developed on a Mac).
I'm not sure how you did your installation, but you also need to have an updated version of mosaicCore. Looks like that didn't happen for some reason.
I'd suggest updating mosaicData and ggformula as well, if your update method didn't trigger those already. All four packages went to CRAN last week. If it has been awhile, you might do update.packages().
My daughter met the same problem today.
As per the suggestion here, we install the newest mosaicData, and the problem remains.
Then quit Rstudio, restart Rstudio, after running library(mosaic) again, it mentions that several packages are missing,
After installing the missing packages, everything is ok.
I had other people in my class that had the same issue. Similar to the above answer, i had to:
Uninstall/delete the package ggformula
Update the package mosaicCore
Reinstall ggformula
Reinstall mosaic
That is how i was able to resolve the issue.

Firebase Functions for Firestore Failing due to NanoMatch Issue

I am new to cloud functions and was testing this sample code https://github.com/firebase/functions-samples/tree/master/quickstarts/uppercase-firestore
This fails to execute due to an error from nanomatch. Looking at nanomatch repository on GitHub This is a listed issue and reverting back to 1.2.9 takes care of this error.
I am trying to fix this on my end - but how do I do this? Can somebody guide me on this. Thank you for the help.
TypeError: Cannot read property 'addQmark' of undefined
at Object.<anonymous> (/user_code/node_modules/firebase-admin/node_modules/nanomatch/lib/compilers.js:92:15)
at Object.visit (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:129:15)
at Object.mapVisit (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:143:12)
at Object.compile (/user_code/node_modules/firebase-admin/node_modules/snapdragon/lib/compiler.js:168:10)
at Snapdragon.compile (/user_code/node_modules/firebase-admin/node_modules/snapdragon/index.js:156:32)
at /user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:786:23
at memoize (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:859:13)
at Function.micromatch.compile (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:783:10)
at create (/user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:686:25)
at /user_code/node_modules/firebase-admin/node_modules/micromatch/index.js:695:16
THIS BUG WAS FIXED
The version that caused the bug was reverted right when this issue was reported on GitHub, which was within minutes of it being released. To get the fix, just reinstall. You might need to delete node_modules and/or lockfiles first, to ensure cached versions aren't used by NPM. This conversation belongs on GitHub, so that we can respond to user feedback. I found this by chance. StackOverflow is not for support).
Edit 2: it appears that firebase-admin itself needs to re-install dependencies as well. I'm looking into how to make that happen.
Please report and check issues on GitHub, where the codebase is and where this discussion belongs.
Visit https://github.com/micromatch/nanomatch/issues/15 for more info.
Faced the same problem "Thumbnail URL not saved to firestore. Cannot read property 'addQmark' of undefined"
Started today morning when I upgraded to the latest firebase-tools#3.19.1
At first thought was issue with my code, but after rollbacking my code the situation persisted.
Rolled back to firebase-tools#3.19.0 and the situation got fixed.
There is a bug in the latest firebase-tools
Use this:
npm install nanomatch#1.2.9 -S
just rollback to older version
npm install -g firebase-tools#3.19.0
Firebase team is probably/hopefully redeploying all functions without the broken nanomatch package, but for me following the advice from #abhi and redeploying immediately solved the issue!
npm install nanomatch#1.2.9 -S
firebase deploy --only functions
(npm install in the functions folder!)

Magento 1 to Magento 2 Migration Tool Issue with No Commands Defined In "Migrate" Namespace

When using the Magento Migration Tool, If I run:
php -f bin/magento migrate:data [-r] /vendor/magento/data-migration-tool/etc/ce-to-ce/1.9.2.1/config.xml
I get the following Response...
[InvalidArgumentException]
There are no commands defined in the "migrate" namespace.
I have googled and just found many closed issues and unable to find a solution. Has anyone found a work around for this?
Thanks In advance.
hope this may help.
Please clear cache
OR
delete cache and generation folder in var directory
Probably the tool was installed incorrectly in magento 2 code base
Link To Install Migration Tool

Aptana won't load due to CRC error

I am trying to download a simple HTML editor, Aptana,and I keep getting the following error, "Failed to aquire installer_nodejs_windows.msi file:CSC error." Has anyone encountered this before? If so, what's the workaround? Thanks in advance.
Go to https://nodejs.org/en/ and download and install node.js. Try your installation again. There are other users who have had slightly different problem than yours and here's how they solved it.

Glassfish Deploy CommandException Error

I want to deploy my application to glassvish v3 with asadmin deploy command however I get an error:
com.sun.enterprise.admin.cli.CommandException: remote failure: There is no installed container capable of handling this application com.sun.enterprise.deploy.shared.FileArchive#1c2a1c7
What can be the problem?
To me, the problem was coming from the fact that in /domains/domain/applications there was still the application I was trying to deploy again.
Another file access possibility I just ran into:
Service was started as root and the app undeployed/deployed. Then, as the correct limited rights user, undeploy/deploy. On deploy you'll receive this error, as the application files will still exist in he 'domains/yourdomain/applications' directory, and will be owned by root.
+1 to Keeg's comment on the awesome error messages we've all come to expect from Glassfish.
Hey I got the same error.In my case,I'd made a directory named "Web-INF",apparently the name of the folder has to be (mandatory) in upper-case i.e. "WEB-INF".
In short,check for spelling errors.
It solved my issue.So just wanted to share.I'm new to glassfish, so can't really tell you the exact solution.But what worked for me could be a solution for you as well.
Just in case someone else finds this question and the above answer doesn't match your case... Our problem was that the temporary area on the Glassfish server was full. Clearing some space let me redeploy the same application. Thank goodness for excellent error messages.
I had an ear project, where the ear package had different version number configured to maven pom.xml than the rest of the projects it contained. It searched sub-modules from version 1.x and the rest of the project was at 1.y version. I updated every pom to same version and that made the trick.