AR.js ES6 (#ar-js-org/ar.js) npm gives "Assertion failed: console.assert" error in console - aframe

I am looking for some guidance. I have implemented AR.js via npm (ES6 - #ar-js-org/ar.js) import to build my app via webpack 5, everything seems to be imported ok; however, when running test i am getting an "Assertion failed: console.assert" error in console.
My console initialization tracing looks like this:
*"A-Frame Version: 1.3.0 (Date 2022-02-04, Commit #cc3516ce)
aframe-master.js:71837 THREE Version (https://github.com/supermedium/three.js): ^0.137.0
aframe-master.js:71839 WebVR Polyfill Version: ^0.10.12
aframe-ar.js:1 Assertion failed: console.assert
aframe-ar.js:1 Assertion failed: console.assert
aframe-ar.js:1 Assertion failed: console.assert
aframe-ar.js:1 AR.js 3.4.1 - trackingBackend: artoolkit
aframe-ar.js:1 ARToolkit 0.2.0
aframe-ar.js:1 [ARController] ARToolkit initialized
aframe-ar.js:1 [ARController] Camera params loaded with ID 0
aframe-ar.js:1 [ARController] Got ID from setup 0
aframe-ar.js:1 actual source dimensions 1023 767
aframe-ar.js:1 source orientation landscape
aframe-ar.js:1 actual source dimensions 1023 767
aframe-ar.js:1 source orientation landscape"*
Did anybody came accross this issue? is there a standard approach to fix the "Assertion failed: console.assert" ? I notice as well that a live example is experiencing the same issue (https://thauska.github.io/peticov-ar/#/ar) It is dated from Oct 31, 2021 so it is a bit old but exactly the same issue in the console.
If any one would have an idea on where to start to troubleshoot, maybe tweaks in webpack output(?) , I am a scratching my head on this one! :) Any little bit of info will help. In advance thank you very much!
I am not very familiar with the inner workings of the #ar-js-org/ar.js, so I am not sure where to start in the troubleshooting. Issues occur like models are off set of the marker but register x,y,z = 0. I imported the basic example from the doc. barebone i think the "Assertion failed: console.assert" result in different issues.

Related

why sanity start failed to compile in my nextjs app?

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 ?

VTS few test cases give syntax error unexpected 'newline' and module gets reported as incomplete (inspite of test cases pass)

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

Julia - how to update WinRPM in julia version 0.6.4

I'm new to Julia and I want to use COBRA Package.
For adding COBRA I use command :
Pkg.add("COBRA")
But when running, I get these errors:
INFO: Building WinRPM
WARNING: skipping repodata/repomd.xml, not in cache -- call WinRPM.update() to download
WARNING: skipping repodata/repomd.xml, not in cache -- call WinRPM.update() to download
INFO: Downloading https://cache.julialang.org/http://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_Leap_42.2/repodata/repomd.xml
WARNING: Unknown download failure, error code: 2148270086
WARNING: Retry 1/5 downloading: https://cache.julialang.org/http://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_Leap_42.2/repodata/repomd.xml
until:
WARNING: Unknown download failure, error code: 2148270086
WARNING: Retry 5/5 downloading: https://cache.julialang.org/http://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_Leap_42.2/repodata/repomd.xml
WARNING: received error 0 while downloading
https://cache.julialang.org/http://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_Leap_42.2/repodata/repomd.xml
After these errors, I have checked the link and I've found out the source is not there, anymore.
So then I ran this command as said above:
WinRPM.update()
But it has thrown this error:
ERROR: UndefVarError: WinRPM not defined
Please Help me to add COBRA to Julia. I'm using version 0.6.4 because Cobra does not work on the next versions.(Windows 10)
Any help would be appreciated.
The problem, as you've mentioned, is that the original sources used by the package aren't valid URLs anymore. The proper way to solve this is to open a pull request with the package to change the URLs (which I've now done here ). As a stopgap measure, here's a hacky way to work around this issue for now:
Do a Pkg.add("WinRPM"). This might trigger the same warnings as above, ignore these.
Next, using WinRPM to load the package we added
Now, the source URLs are read from the sources.list file (linked above) into a global WinRPM.sources variable. We're going to edit this variable's contents to point to new working URLs. (This is generally a terrible idea, to directly poke into the internals of a module and change things.)
julia> WinRPM.sources[:] = replace.(WinRPM.sources, "Leap_42.3" => "Leap_15.3")
2-element Vector{String}:
"https://cache.julialang.org/http://download.opensuse.org/repositories/windows:/mingw:/win32/openSUSE_Leap_15.3"
"https://cache.julialang.org/http://download.opensuse.org/repositories/windows:/mingw:/win64/openSUSE_Leap_15.3"
A WinRPM.update() should now work, and download things into a local cache.
I'm using version 0.6.4 because Cobra does not work on the next versions.
I hope you mean Julia 1.6.4 here, or version 0.6.4 of something else in the stack. If you mean Julia version 0.6.4, you might face further problems down the road and find it hard to get support for such an old version.

nbsphinx causes build to fail when building Jupyter Notebooks

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

trigger.io - Can't create ipa-file anymore

I usually use trigger.io to generate my ipa-Files for iOS. Now when I want to generate the file, I get the following error message:
Failed when running /usr/bin/codesign: codesign_allocate: object: /Users/mherceg/Desktop/ag-app/development/ios/device-ios.app/Forge malformed object (unknown load command 39)
/Users/mherceg/Desktop/ag-app/development/ios/device-ios.app: object file format unrecognized, invalid, or unsuitable
It worked yesterday, but now it doesn't. Any help is very welcome.
Thanks,
enne
This is probably to do with v1.4.16 of our platform, where we switched over to building on Xcode 4.5: I'd recommend upgrading Xcode and make sure the Command-line Tools (Preferences ↦ Downloads) are installed.

Resources