ClrDateContainer receive in docker undefined commonStrings - vmware-clarity

We use submodules. From one times we started received error
TypeError: Cannot read property '__source' of undefined
After debug code I founded that problem is commonString in ClrDateContainer component in undefinded
link for screenshots (I can't publish)
https://ibb.co/SyRRCHZ
https://ibb.co/gwQWW5R
With local build ok. It happens looks like only in docker.

Related

Error with context.scriptLoader in next js 10

I'm getting this error when running my NextJS app
TypeError: Cannot read property 'eager' of undefined
at Head.getPreloadMainLinks (/Users/someuser/dev/temp/next-js-10-1-error/mobile/.next/server/pages/_document.js:4936:30)
at Head.render (/Users/someuser/dev/temp/next-js-10-1-error/mobile/.next/server/pages/_document.js:5160:130)
My app was working fine in next js 10.0.1 but does not work on 10.1.3
I created an MVE here: https://github.com/jeznag/next-js-10-1-error
I'm not sure it is a bug in next as even if I revert to 10.0.1 in the MVE, I still get the error. (But in my real app on 10.0.1 I don't get an error)

How to fix "vagrant up" errors when trying to set up Trellis?

I've been trying to set up a Trellis local WordPress dev environment from the Roots stack. I did all the steps from the docs, have the recommended folder structure, downloaded all the dependencies, but I still get a few errors.
First I get some errors and warnings when I use "yarn" in my theme folder, as suggested here. They say to use the CLI from my host instead of Vagrant box, that's just the MacBook's terminal right? Or do I need a CLI from VirtualBox?
The second error happens when trying to call "vagrant up", and this is one that I can paste here as it's a bit more concise.
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["hostonlyif", "create"]
Stderr: 0%...
Progress state: NS_ERROR_FAILURE
VBoxManage: error: Failed to create the host-only adapter
VBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: failed to open /dev/vboxnetctl: No such file or directory
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage: error: Context: "RTEXITCODE handleCreate(HandlerArg *)" at line 95 of file VBoxManageHostonly.cpp
After Googling this I got a lot of outdated suggestions to check my PATH and restart the VirtualBox, but these I tried and didn't help. I hope someone can help me set this up, thanks. :)

Error on meteor project setup

I setup meteor environment
meteor create todoapp
cd todoapp
Then write meteor and press enter after then I run on localhost:3000 then I receive following error on terminal
Exception from sub meteor_autoupdate_clientVersions id fRm2pMK35Ji2uPut5
TypeError: Cannot read property 'OneOf' of undefined
I don't know what the actual reason of this issue any way I found a solution I uninstalled Meteor the reinstalled it after this the issue has been resolved.

using node-inspector with meteor on windows

I am trying to use node-inspector to help debug my meteor app on windows. As indicated here: https://docs.meteor.com/commandline.html#meteordebug
running meteor debug should start the node-inspector portal at http://localhost:8080/debug?port=5858 by default.
I can navigate to the url, but do not see any files under "Sources" (or anywhere for that matter)
I've tried setting the port manually, and tried installing node-inspector via npm as well in case it was needed, and tried running "meteor NODE_OPTIONS='--debug' ...but those don't seem to help (and the NODE_OPTIONS parameter doesn't even work...)
what am I missing/why don't the files show up? how can I debug this debuggng issue...?
PS - i do see Notifications permission has been blocked as the user has dismissed the permission prompt several times. See https://www.chromestatus.com/features/6443143280984064 for more information.
in the dev console on the debugger tab. Could this cause any issues? Not really sure what notification permissions I supposedly blocked.
UPDATE:
Also getting these 3 errors popping up in the console:
Runtime.js:358 Assertion failed: Unknown experiment canvasInspection
Runtime._assert # Runtime.js:358
21:53:06.599 Runtime.js:367 TypeError: Cannot read property 'createSetting' of undefined
at WebInspector.FilterBar.setName (:8080/ui/FilterBar.js:62)
at WebInspector.NetworkPanel (:8080/network/NetworkPanel.js:47)
at Function.WebInspector.NetworkPanel._instance (:8080/network/NetworkPanel.js:408)
at eval (:8080/node/network/NetworkPanel.js:13)
at eval (<anonymous>)
at evaluateScript (Runtime.js:153)
at scriptSourceLoaded (Runtime.js:136)
at <anonymous>
Runtime._reportError # Runtime.js:367
21:53:06.772 Runtime.js:367 TypeError: Cannot read property 'sources' of undefined
at WebInspector.SourcesOverrides._hideChromeSpecifics (:8080/node/sources/SourcesOverrides.js:12)
at WebInspector.SourcesOverrides (:8080/node/sources/SourcesOverrides.js:5)
at eval (:8080/node/sources/SourcesOverrides.js:63)
at eval (<anonymous>)
at evaluateScript (Runtime.js:153)
at scriptSourceLoaded (Runtime.js:136)
at <anonymous>
many thanks for any help.

New Static Library has build error "libtool exited with code 1"

I created a new static library in my iOS project and now I'm getting the build error
Command /Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin/libtool failed with exit code 1
How do I go about debugging this?
To see the actual output and not just the error message, try building your target or scheme with xcodebuild from command line.
I had a problem with the same error message. In my case, I couldn't build for the simulator, but it worked find when building for the device. The output from xcodebuild confirmed that Xcode could not set the proper architecture to build for the simulator.
Long story short, it turned out that one build setting was corrupted. The Mach-O Type setting in the Linking category was set to Relocatable Object File for some reason. I switched it back to Static Library and the error disappeared.

Resources