Error:
The style compilation failed, see the error below. Your recent actions may be the cause, please try reverting the changes you made.
Could not get content for /web_dialog_size/static/src/css/web_dialog_size.css defined in bundle 'web.assets_backend'.
When you get given error then follow the below steps:
Apps -> web_dialog_size -> uninstall module
If you need this module then again install it
Related
I don't understand what is the problem? Webpack does not compile the project and shows the following error:
ERROR in Error: Child compilation failed: Module parse failed: Unexpected character '�' (1:4)
But I can't figure out where the error derives from, in which module or file, where to look for it? This is the error from my IDE.
At the moment, it gives only 1 error when compiling, before that there were 22 errors. Actions that could lead to this - trying to solve the problem through CSS.
After I removed everything in the code (-webkit-min-device-pixel-ratio: 2), the number of errors was reduced to 1, but I don’t understand what to do next.
My webpack 5 config: webpack.config
If someone knows how to solve this problem, or where to look for the root of evil, please help.
Problem solved! It turned out that in my webpack.config in the image processor, I did not add webp support. And when I added it on the fly, the already assembled project did not take this moment into account. As a result, after restarting the build with the npm run dev command, the updated webpack config file started working as it should! Thank you all for your attention to the issue and the desire to help figure it out! enter image description here
So I am just getting started with Codeception (I know, I am late to the game) and Yii2. There is a error I am running into that I don't seem to get fixed.
Problem
When I run 'codecept run', I get the error 'Error with message "Class yii\codeception\TestCase not found". Which is strange to me, because when I look for TestCases, I can find multiple TestCases! F.e. in the folders "backend", "console", ..
Information
Codeception has been installed Globally
The CodeCeption version I am using is the version 4.1.12
When I run any command, the console is giving me the message, "Redirecting to Composer-installed version in vendor/codeception".
What am I doing wrong?
If you guys need any information, hit me up!
Thanks!
Why do you use yii\codeception\TestCase class in your tests?
Have you found it in old tutorial?
yii\codeception\TestCase class was provided by yiisoft/yii2-codeception package which was abandoned back in 2016.
Use Cest format as documented in https://codeception.com/docs/02-GettingStarted#Writing-a-Sample-Test
I just changed two lines of code in the Google cloud functions source code using inline statement, the two lines of code involve parsing date string using datetime library, no updates to anything else. This same deployment has been working for more than a year now.
All of a sudden I get two errors -
Error 1 -
(gcloud.functions.deploy) OperationError: code=3, message=Build
failed: {"error": {"canonicalCode": "INTERNAL", "errorMessage":
"pip_install_from_wheels had stderr
output:\n/opt/python3.7/bin/python3.7: No module named pip\n\nerror:
pip_install_from_wheels returned code: 1", "errorType":
"InternalError", "errorId": "ECB5F712"}}
Resolved that by removing pip from requirements.txt (again not sure why this is a problem now and not for over a year)
If I address 1, I get the following error -
Error 2 -
(gcloud.functions.deploy) OperationError: code=3, message=Build
failed: {"error": {"canonicalCode": "INTERNAL", "errorMessage":
"gzip_tar_runtime_package gzip /tmp/tmpGLHQx9.tar -1\nexited with
error [Errno 12] Cannot allocate memory\ngzip_tar_runtime_package is
likely not on the path", "errorType": "InternalError", "errorId":
"2A1581FF"}}
Memory is already at 2048 and nothing changed other than the two lines of code above.
Let me know if this has been happening and what is the resolution.
It looks like this has to do with packages than anything else. I deployed a dummy function and added each package from requirements.txt until it failed. It turns out the problem packages were
a. gpflow
b. tensorflow
Last deployment with these packages was successful as of Feb 20. Not sure why I can't install them without those errors anymore. regardless, tried using the versions that would have been consistent with Feb 20 timeline with no luck. So refactored my code and removed all the functionality that was using that and deployed successfully.
Request to Google Cloud Folks : Why this behavior ? Also "Invalid ARGUMENT" in logs (Stackdriver or google cloud logging whatever you call it) is misleading.
The first error, as explained in this post, is due to pip being defined in your requirements.txt file. Specifying pip as a dependency for the function causes message to appear. You did the right thing by removing it from the requirements.txt file.
The second error usually appears if the number of files or the size of the content that is being uploaded is too big and the instance used to deploy your code runs out of memory. You perhaps were using too many dependencies or static files, as explained here.
I called today pod update and only FirebaseCore was updated from version 3.4.6 to 3.4.7. After that I am getting following error, no matter how many times I clean all the workspace, checkout again, etc. each time I get this new version I end up with the following errors while compiling:
duplicate symbol _GSDK_NSClassFromString in:
.../Pods/FirebaseCore/Frameworks/FirebaseCore.framework/FirebaseCore(overload_9ea29fd47bf44ee000bc4282b65dac06.o)
...Pods/GoogleSymbolUtilities/Frameworks/frameworks/GoogleSymbolUtilities.framework/GoogleSymbolUtilities(overload.o)
duplicate symbol _GSDK_objc_getClass in:
...Pods/FirebaseCore/Frameworks/FirebaseCore.framework/FirebaseCore(overload_9ea29fd47bf44ee000bc4282b65dac06.o)
...Pods/GoogleSymbolUtilities/Frameworks/frameworks/GoogleSymbolUtilities.framework/GoogleSymbolUtilities(overload.o)
duplicate symbol _GSDK_objc_getProtocol in:
...Pods/FirebaseCore/Frameworks/FirebaseCore.framework/FirebaseCore(overload_9ea29fd47bf44ee000bc4282b65dac06.o)
...Pods/GoogleSymbolUtilities/Frameworks/frameworks/GoogleSymbolUtilities.framework/GoogleSymbolUtilities(overload.o)
duplicate symbol _GSDK_objc_lookUpClass in:
...Pods/FirebaseCore/Frameworks/FirebaseCore.framework/FirebaseCore(overload_9ea29fd47bf44ee000bc4282b65dac06.o)
..Pods/GoogleSymbolUtilities/Frameworks/frameworks/GoogleSymbolUtilities.framework/GoogleSymbolUtilities(overload.o)
ld: 4 duplicate symbols for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Solved removing -all_load from Other Linker Flags under Build Settings
I came to this question trying to integrate AdMob in a Kivy app for iOS. Removing -all_load from Other Linker Flags , as suggested by David, does allow app to compile without errors, but app will subsequently crash when Kivy instantiates your app.
The solution for my case was to use -force_load path_to_archive for each archive library in kivy-ios/dist/lib/
Hopefully this saves someone else a bit of searching!
I'm migrating my WebAPP from Smarty2 to Smarty3. Every step is easy except one. When i display a Smarty Template ( tpl ) an Exception is thrown.
This line
Source: /path_to_file/smarty/libs/sysplugins/smarty_resource.php (773)
(this is the source coude $compiled->timestamp = #filemtime($compiled->filepath); )
raise this Exception when the file doesn't exists
filemtime() [function.filemtime]: stat failed for /path_to_templates/smarty/templates_c/219dfe732aae7bd7c0edab091e3c53f3ce86b058.file.index.tpl.php
Folder permissions:
Smarty template folder Permission : 775
Smarty Cache folder permission: 775
Folder Owners:
both ftp_user:webserver_user
I'm trying to implement different solutions but it seems not possibile to solve this issue whitout changhing Php Error Reporting or disabling my Error Handler .
How can i solve this problem without hacks ?
What you should do is not to downgrade to 3.1.1 but rather try to upgrade to 3.1.19 version. Many bugs are removed all the time so maybe in this version you won't have it.
The other thing is that you can use muteExpectedErrors method to hide file system warnings from Smarty (documentation for this function is not very clear but it affects file system warnings what is explained in error_reporting documentation). You can read at error_reporting documentation page:
Smarty 3.1.2 introduced the muteExpectedErrors() function. Calling
Smarty::muteExpectedErrors(); after setting up custom error handling
will ensure that warnings and notices (deliberately) produced by
Smarty will not be passed to other custom error handlers. If your
error logs are filling up with warnings regarding filemtime() or
unlink() calls, please enable Smarty's error muting.
Check the filesystem permission on /path_to_templates/smarty/templates_c/219dfe732aae7bd7c0edab091e3c53f3ce86b058.file.index.tpl.php
PHP does not seam to have read/write permission on that file.
Also check the permission in the /path_to_templates/smarty/templates_c/ folder. Is the PHP allowed to read list and write in there as well?