as a beginner i'm trying to follow up with a tutorial that uses sanity for backend , the problem is that when it come to the step to start sanity , so many errors are showing up here is the first one that i think is the major one that blocks the compilation
Error in ./schemas/schema.js (part:#sanity/base/schema)
Module build failed: Error: [BABEL]: Cannot find module 'C:\Users\ghars\tiktik-a
pp\sanity-backend\node_modules\#babel\helper-plugin-utils\lib\index.js'. Please
verify that the package.json has a valid "main" entry (While processing: C:\User
s\ghars\tiktik-app\sanity-backend\node_modules\#babel\plugin-proposal-class-prop
erties\lib\index.js)
i've searched about this and i think that sanity have a problem when it comes to node version 17 that i'm using , is there any solution without passing back to node 16 ?
Related
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
/data/local/tmp/VtsHalBiometricsFaceV1_0TargetTest/VtsHalBiometricsFaceV1_0TargetTest.config[1]: syntax error: unexpected 'newline'
Total Tests : 1
PASSED : 1
FAILED : 0
IMPORTANT: Some modules failed to run to completion, tests counts may be inaccurate.
============== End of Results ==============
Issue : Test case is passing but module is not getting reported as completed.
Issue seen with only Android 11 based VTS suites and works well with older android flavor VTS suites.
Environment of 18.04.2 LTS ubuntu and few modules inspite of passing the test cases it does not report a module pass (only for few modules) and shows it as Done=false in results report.
Logs indicate this kind of errors pointing to various .config files.
Any idea / suggestion what could be issue ?
This was asked again in syntax error: unexpected 'newline' in .config file in android vts and that got an answer that if you've modified the vts-tradefed file, then this error appears.
Additionally I noticed that even chmod changes can cause this problem to appear.
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 doing the Pintos project on the side to learn more about operating systems. I had tons of devops trouble at first with it not running well on an 18.04 Ubuntu droplet. I am now running it on the VirtualBox image that UCCS tells students to download for pintos.
I finished project 1 and started to map out my solution to project 2. Following the instructions to create a file I ran
pintos-mkdisk filesys.dsk --filesys-size=2
pintos -- -f -q
but am getting error
Kernel PANIC at ../../threads/vaddr.h:87 in vtop(): assertion
`is_kernel_vaddr (vaddr)' failed.
I then tried running make check (all the tests). They are all failing for the same reason.
Am I missing something? Is there something I need to implement to fix this? I reread the instructions and didnt see anything?
Would appreciate help!
Thanks
I had a similar problem. My code for Project 1 ran fine, but I could not format the filesystem for Project 2.
The failure for me came from the following call chain:
thread_init() -> ... -> thread_schedule_tail() -> process_activate() -> pagedir_activate() -> vtop()
The problem is that init_page_dir is still NULL when pagedir_activate() is called. init_page_dir should have been initialized in paging_init() but this is called after thread_init().
The root cause was that my scheduler was being called too early, i.e. before the call to thread_start(). The reason for my problem was that I had built in a call to thread_yield() upon completion of every call to lock_release() which makes sense from a priority donation standpoint. Unfortunately, locks are used prior to the scheduler being ready! To fix this, I installed a flag called threading_started that bails in the first line of my thread_block() and thread_yield() functions if thread_start() has not yet been called.
Good luck!
Our automated build process incorporates a grunt task that periodically (more times than I'd like) generates a 6 return code.
According to the grunt web page 6 is a "Warning". Well okay, a warning for what? It's breaking our build since we would only pass on a 0 exit case. I'm looking at wrapping this in a script so I can catch this warning condition and generate a success exit code, though without any idea what the Warning might be I'm hesitant. It appears to work when I get this exit condition but would like a better understanding on what it may be.
Any ideas?
So this turned out to be an issue with grunt-contrib-less. I didn't recognize the associated less compiler error in our build log:
[39mnon_object_property_loadError: Cannot read property 'rules' of undefined in ../../XXXX/styles/modules/SomeLessFile.less on line null, column 0: [31m
Once I found this line a google search quickly found this in GitHub:
And have updated the grunt-contrib-less package. So far so good.
check http://gruntjs.com/api/grunt.fail:
If --stack is specified on the command-line and an error object was
specified, a stack trace will be logged.
Or try to run "grunt --verbose --force"