After anaconda upgrade --all anaconda-navigator does not launch - qt

After upgrade --all launching anaconda-navigator raise an error:
Exception: setResizeMode is only available in Qt4. Use setSectionResizeMode instead.
I am using version 1.6.0 on MacBook OSX (Sierra). Can anyone help. It seems that there is a conflict with spyder.

There is some change with going from qtpy version 4 to version 5. I thought I had version 4 installed, but based on this exception, something isn't quite right. I was able to get anaconda-navigator to launch after editing this file on line 155:
anaconda/lib/python3.5/site-packages/anaconda_navigator/widgets/manager/table.py
155c155
< self._hheader.setResizeMode(self._hheader.Fixed)
---
> self._hheader.setSectionResizeMode(self._hheader.Fixed)
Edit: it appears a fix is coming in the next release for spyder. anaconda-navigator will probably need a similar patch.
https://github.com/spyder-ide/spyder/issues/3943

Related

Microsoft Visual C++ Runtime error - Assertion Failed

Using: VS Code
Working on: Running automation test scripts for WebdriverIO.
Error facing:
because of this error, my test specs are not executing. Is there any way to get rid of this??
Please follow the below steps to resolve this issue
Uninstall the current version of node.js.
Go to https://nodejs.org/en/blog/release/
Install the previous version of node.js (I installed from here 4.
https://nodejs.org/dist/v14.17.3/node-v14.17.3-x64.msi)
Restart your system
Try building the project using npm install
I hope this will solve your problem
The error here is coming from the Fibers npm package. Fibers only supports node versions before version 16. I had the same error message and switched the node version to 14.20.0 ,which is the newest LTS before version before 16 at the moment, and that solved the problem for me.

Next-auth Package subpath '.providers/...' is not defined by "exports" in

Just got this error while working with Next-auth
Server Error
Error: Package subpath './providers/google' is not defined by "exports" in C:\Users...\node_modules\next-auth\package.json
Any help?
I think this comes from your next-auth version.
Make sure you're not working with mixed versions' features.
We now have two main versions: Version 3 and Version 4 (beta version).
By Reading the Docs, You can figure it out.
Check this Thread and use the Link to know more about this version issue
You can solve the problem by upgrading the Version 👉 Upgrade your Next-auth for some compatibilities issues
yes, I have the same issue as this, don't panic.
I solved just trying to install and reinstall node_module.
case 1 remove node_module and install again use npm (install success install not information error)
case 2 remove node_module again and install node_module use yarn ( I getting some information error for requiring version nodejs version), so in this case you need to upgrade or downgrade nodejs to another version.
okay that it, I hope this help you.
I had the same error, and in my particular case are be because i been running a old version of node.
first check your version of node
node -v
after upgrate with your package manager of your preference (brew, apt-get, etc)
brew upgrade node
and finally switch your version with a version manager tool of node
npm i -g n
n latest
for me updating the node version fixed the above issue
Try this:
import GoogleProvider from "next-auth/providers/google";

Install Flex SDK on ubuntu

i've been following this article to install apache flex on ubuntu 12.04, but unfortunately the last step doesnt work for me.
after successfully installing adobe air, if i run dpkg -l adobeair i get the expected:
ii adobeair 1:2.6.0.19170 Adobe AIR 2
also just to be sure, running dpkg -l|grep adobeair yells the same as the previous command.
just like mentioned in the link, trying to execute the flex deb package displays an error saying that the adobe air dependency cannot be satisfied.
trying to execute the solution that they propose: sudo dpkg -i --force-depends apache-flex-sdk-installer-2.7.0-bin.deb returns the following:
Selecting previously unselected package org.apache.flex.installapacheflex:i386.
dpkg: regarding apache-flex-sdk-installer-2.7.0-bin.deb containing org.apache.flex.installapacheflex:i386, pre-dependency problem:
org.apache.flex.installapacheflex:i386 pre-depends on adobeair (>= 1:2.6.0.0)
dpkg: warning: ignoring pre-dependency problem!
(Reading database ... 187989 files and directories currently installed.)
Unpacking org.apache.flex.installapacheflex:i386 (from apache-flex-sdk-installer-2.7.0-bin.deb) ...
dpkg: org.apache.flex.installapacheflex:i386: dependency problems, but configuring anyway as you requested:
org.apache.flex.installapacheflex:i386 depends on adobeair (>= 1:2.6.0.0).
Setting up org.apache.flex.installapacheflex:i386 (2.7.0) ...
Processing triggers for software-center ...
Updating software catalog...this may take a moment.
INFO:softwarecenter.db.pkginfo_impl.aptcache:aptcache.open()
Software catalog update was successful.
and nothing else happens, the installation wizard doesnt start up. After that,double clicking on the flex package opens up the software center that displays an error saying "Items cannot be installed or removed until the package catalog is repaired" with the option to repair or cancel. no matter what option i choose, the flex package is still not allowed to install...
I've been struggling with this for several hours now, its driving me insane, any input would be greatly appreciated! :)
So I've finally figured out after poking around, once all the steps described in the question are done, you will find the installer located at /opt/Apache Flex/Apache Flex SDK Installer/bin so basically then you just need to execute the installer with root permissions and everything will be hunky dory:
cd /opt/Apache\ Flex/Apache\ Flex\ SDK\ Installer/bin/
sudo ./Apache\ Flex\ SDK\ Installer
Follow the wizard and when it is completed you can make sure by doing mxmlc -help
Apache Flex Compiler (mxmlc)
Version 4.12.0 build 20140303
Copyright 2013 The Apache Software Foundation.
Maybe this will help somebody in the future :)

unable to find mpd.conf file

I have installed MPICH2 1.4 version on RHEL.
Whenever I'm trying to run a program then it is throwing following error
unable to find mpd.conf file
How to resolve this problem.?
This error comes from running an old version of MPICH that requires some setup. You might try upgrading to a much newer version (the latest is 3.0.4) available at http://www.mpich.org and you don't have to worry about setting up MPD because it will use the newer process manager (Hydra) by default.

How long does it take to build MacVim from source?

I am trying to install MacVim in my Macbook Pro from Homebrew. However it "got stuck" at
xcodebuild -project MacVim/Macvim.xcodeproj ARCHS="x86_64" ONLY_ACTIVE_ARCHS="NO"
for nearly 6 hours. Last time I remember building from source that took me so long was the Open Office.
By the way. I am running Lion. I know there is no stable version of MacVim for Lion yet but I guess this shouldn't be a problem building it. I have Xcode 4 installed with Command Line Tools.
Am I missing something?
Thanks in Advance.
Problem solved. What happened is that I installed the command line tools for xcode but its path was not properly configured. For example, to compile MacVim it required xcodebuild to run. The only reference for xcodebuild I found in my system was in /usr/bin so I set the path to that location. Even though xcodebuild was being found by make, it would get stuck forever and not returning any erros (weird). I tried to build other application purely based on gcc and it got stuck with no errors too. Finaly I found the correct path for command-line tools for Xcode 4.3. The code to set it up is:
sudo xcode-select -switch /Applications/Xcode.app/Contents/Developer
source: http://jeffreyearly.com/2012/02/28/broken-command-line-tools-clt-in-xcode-4-3/

Resources