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.
Related
I was migrating to sveltekit 1.7.2 from 1.5.3, as there was a security vulnerability. NPM did not tell me that 1.7.2 was a breaking change, so I installed the new version. I found that the latest compatible version was 1.5.6, anything higher resulted in the same error. I don't know why this is an issue, I guess it wouldn't be if you were making a new project, but as I am not doing that, can anyone tell me how to fix this?
Entire error:
Error: Cannot find module '__sveltekit/paths' imported from [path to project]/node_modules/#sveltejs/kit/src/runtime/server/respond.js'
at nodeImport (file:///[path to project]/vite/dist/node/chunks/dep-3007b26d.js:52431:25)
at ssrImport (file:///[path to project]/node_modules/vite/dist/node/chunks/dep-3007b26d.js:52354:20)
at eval (/node_modules/#sveltejs/kit/src/runtime/server/respond.js:5:37)
at async instantiateModule (file://path to project]/node_modules/vite/dist/node/chunks/dep-3007b26d.js:52400:9)
This error tells me that the file "__sveltekit/paths" has either moved, been replaced, or deleted entirely. Does anyone know where the file is now/if it even still exists?
Please note, that I see this error in the browser and in the node console. No other content is rendered at all.
I've been trying to setup firebase in my app for a while now with no luck.
Immediately I install the lastest version of com.google.firebase:firebase-auth -> 21.0.6 which is required for setting up firebase, I get the above error which doesn't seem to go away no matter what unless I remove the package.
I looked around everywhere to see if it's defined somewhere in the package to change it but it's no where to be found.
Finally tracked it down in the dependencies tree, it only appears once and it seems to be resolving to 9.8.0 in the following line
com.google.android.gms:play-services-auth-api-phone:17.4.0 -> 9.8.0 FAILED
Things i've tried (Basically anything I could find on it or anything similar on the internet)
Installed different version of the firebase dependencies auth & app (even to versions where play-services-auth-api-phone had not been introduced as a dependency and it still does not work.
Moved around a couple things in my /build.gradle, jcenter, google(), etc to no luck
Played around with different versions of play-services and gradle.
Any help will be much appreciated.
Also this is the error that gets thrown when running the project:
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
Could not find com.google.android.gms:play-services-auth-api-phone:9.8.0.
Searched in the following locations:
- file:/C:/Users/username/.m2/repository/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- file:/D:/Github/app_name/node_modules/react-native/android/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- file:/D:/Github/app_name/node_modules/jsc-android/dist/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- https://maven.google.com/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- https://dl.google.com/dl/android/maven2/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- https://www.jitpack.io/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
- https://jcenter.bintray.com/com/google/android/gms/play-services-auth-api-phone/9.8.0/play-services-auth-api-phone-9.8.0.pom
Required by:
project :app > project :react-native-firebase_auth > com.google.firebase:firebase-auth:21.0.6
For setting up AWS MWAA with snowflake, as per the AWS documentation here, I created a requirements.txt file with following content:
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.2.2/constraints-3.7.txt"
apache-airflow[snowflake]
This worked successfully. Next I wanted to add dbt to my eco-system and updated my constraint file to:
--constraint "https://raw.githubusercontent.com/apache/airflow/constraints-2.2.2/constraints-3.7.txt"
apache-airflow[snowflake]
dbt-core==1.1.1
dbt-snowflake==1.1.0
Now this is where things start breaking. I get the following error when I build this-
ERROR: Cannot install snowflake-connector-python[secure-local-storage]==2.7.0 because these package versions have conflicting dependencies.
The conflict is caused by:
snowflake-connector-python[secure-local-storage] 2.7.0 depends on keyring!=16.1.0 and <22.0.0; extra == "secure-local-storage"
The user requested (constraint) keyring==23.2.1
This seems really weird since both versions: snowflake-connector-python 2.7.0 and keyring==23.2.1 are enforced in the airflow constraint file itself: https://raw.githubusercontent.com/apache/airflow/constraints-2.2.2/constraints-3.7.txt
It is highly unlikely that airflow constraint file is incorrect. Am I missing something here?
Yes, I guess there are some inconsistencies and version conflicts. What I ended up doing is copying all libraries from constraints.txt to requirements.txt, removing unused libraries and run ./mwaa-local-env test-requirements to check for inconsistencies.
Then I manually changed versions of all version conflicts.
Details
I am getting a build failure of my read-the-docs that I don't understand. The assertion of "verbatim" in line 2151 of nbsphinx.py is causing the build failure. So the build fails when I try to include the Jupyter Notebook tutorials I created. I compared current versions of the tutorials to previous versions which had not caused the build to fail, and I can't find a difference that could account for the current failure.
Read the Docs project URL: lofti_gaia
Build URL: https://github.com/logan-pearce/lofti_gaia
Read the Docs username: logan-pearce
Expected Result
A passing build including *.ipynb files
Actual Result
Build failed at line 2151 of nbsphinx.py due to assertion of 'Verbatim' failing.
Terminal output:
Running Sphinx v4.1.2
loading translations [en]... done
making output directory... done
WARNING: html_static_path entry '_static' does not exist
loading pickled environment... done
building [mo]: targets for 0 po files that are out of date
building [latex]: all documents
updating environment: 0 added, 0 changed, 0 removed
looking for now-outdated files... none found
processing lofti_gaia.tex... index installation tutorials/QuickStart tutorials/Tutorial api lofti loftitools
resolving references...
done
writing... failed
Exception occurred:
File "/home/docs/checkouts/readthedocs.org/user_builds/lofti-gaia/conda/latest/lib/python3.7/site-packages/nbsphinx.py", line 2151, in depart_codearea_latex
assert 'Verbatim' in lines[0]
AssertionError
The full traceback has been saved in /tmp/sphinx-err-x1h83s3m.log, if you want to report the issue to the developers.
Please also report this if it was a user error, so that a better error message can be provided next time.
A bug report can be filed in the tracker at <https://github.com/sphinx-doc/sphinx/issues>. Thanks!
According to the github issue 584 for nbsphinx (https://github.com/spatialaudio/nbsphinx/issues/584), this is due to a compatibility issue with sphinx 4.1.0. It can be gotten around by requiring sphinx version 4.0.2.
So in my requirements.txt file, I included sphinx==4.0.2, after which the build passes. So now my requirements.txt file looks like:
numpy
matplotlib
astropy>=4.0.1.post1
astroquery>=0.4
sphinx==4.0.2
ipython==7.19.0
nbsphinx>=0.8.6
and the build passes.
I have encountered the same issue. I did not solve it with .ipynb format, but converting the jupyter notebook to .rst format works.
May it helps
I am new to Julia's package manager, and I am having trouble installing GLPK and LinProgGLPK.
I have already run Pkg.Init() and have successfully installed Curl using Pkg.add("Curl"). However, when I try to install GLPK or LinProgGLPK (using Pkg.add("GLPK") and Pkg.add("LinProgGLPK")), I get the following message:
MESSAGE: Installing BinDeps v0.0.0
ERROR: Path BinDeps already exists! Please remove to allow installation.
in _resolve at pkg.jl:345
in anonymous at no file:163
in cd at file.jl:26
in cd_pkgdir at pkg.jl:42
in add at pkg.jl:143
in add at pkg.jl:175
I seem to get the same message for other packages that are dependent on BinDeps (including Winston).
I have tried calling Pkg.rm("BinDeps"), Pkg.add("BinDeps"), Pkg.update(), and Pkg.resolve(), and then returned to trying to add GLPK, but the same message persists. I have also entered ~/.julia to remove the BinDeps folder, but that did not work either. What am I missing?
P.S. I am running julia in Linux Ubuntu.
Honestly, when something gets screwed up, it's best just to wipe ~/.julia and re-add the packages.
Just make sure you back up your local changes!