Project: vue3+vite+ts, created by npm init vue#latest
Software: phpstorm
Problems and errors:
The style has taken effect, but the ide does not have any intellisense and reports an error
Error notification:Tailwind CSS: Cannot read properties of undefined (reading 'modifier')
I'm using phpstorm, it has nothing to do with vscode.
But the problem is found, the tailwindcss plugin built in phpstorm has not been updated, it is currently incompatible with taiwindcss 3.2
Same issue here
Just update your extension to >=0.9.0
And you may need to update your vscode too, because higher version of the extension won't work with old versions of vscode
Related
I have a problem with installing and using qt via conan.
The actual error looks like below:
WARN: glib/2.58.3#bincrafters/stable: requirement zlib/1.2.11 overridden by qt/5.13.0#bincrafters/stable to zlib/1.2.11#conan/stable
WARN: pcre/8.41: requirement zlib/1.2.11 overridden by glib/2.58.3#bincrafters/stable to zlib/1.2.11#conan/stable
ERROR: Conflict in pcre/8.41
Requirement bzip2/1.0.8 conflicts with already defined bzip2/1.0.8#conan/stable
To change it, override it in your base requirements
My conanfile.txt:
[requires]
gtest/1.8.1#bincrafters/stable
boost/1.70.0#conan/stable
jsonformoderncpp/3.7.0#vthiery/stable
qt/5.13.0#bincrafters/stable
[generators]
cmake
[options]
qt:with_mysql=False
I managed to resolve this dependency by adding bzip2/1.0.8#conan/stable to [requires] section, but than my application is missing fonts, that are mandatory:
QFontDatabase: Cannot find font directory /home/<user>/.conan/data/qt/5.13.0/bincrafters/stable/package/82f32da7b204a38af07f00f05f94ebbfd7454b77/lib/fonts.
Note that Qt no longer ships fonts. Deploy some (from https://dejavu-fonts.github.io/ for example) or switch to fontconfig.
This fonts directory is actually missing. Please note, that this project builds and run without such problems on other coworkers, same machines.
The question is - what causes those problems and how to resolve them?
The dependencies conflict should be solved by switching to qt/5.13.1#bincrafters/stable, because a lot of dependencies have migrated to conan center.
Regarding the fonts issue, I'm in the process of adding an optional dependancy on fontconfig/2.13.1#conan/stable in the qt recipe. In the meantime, you could try to install system version of fontconfig, rebuild the qt recipe, and check the output to see if has "Fontconfig ............................. yes"
When trying to get started with Cloudify, importing the "Cloudify Hello World Example", I get an error:
TypeError: Object.getOwnPropertyNames called on non-object
I get the same error for any blueprint I try to import. I've searched, but found no help on this error.
The example is being imported from a local clone of cloudify-hello-world-example.git on GitHub. I'm using the Composer UI "Blueprint Settings" tool "Import" option, and selecting the local file "blueprint.yaml" from the cloned repo.
I'm running this on CentOS 7, and installed the Composer as described at thank_you_composer.htm on getcloudify.org. Logging into the Composer at localhost port 3000, using Chrome or Firefox, same result.
What is the reason for this TypeError when importing Cloudify blueprints, and how do I correct/avoid it?
The composer philosophy is to model and design applications.
You can use it to create new blueprints and add new stencils.
For the moment (version 3.3.1) there is a problem importing blueprints that are using external imports (https://cloudifysource.atlassian.net/browse/CFY-4325), you can bypass it by importing the blueprint without those plugins and then add lifecycle operations that will add the functions of those plugins.
I'm developing a couple of packages for plone 4.2. For some reason, when I install mypackage.blah through mypackage.policy, it loses access to its resourceDirectories, and its CSS and javascript are unavailable.
If I install mypackage.blah alone, it works fine. But I'm trying to install it using mypackage.policy, so I declared mypackage.blah as a dependency in setup.py and metadata.xml. When I install mypackage.policy, it install mypackage.blah, and its JS and CSS resources are registered, but portal_javascript they marked the files as "resource not found or innaccesible". It's as if it ignored the resourceDirectory directives.
What could be happening for resourceDirectory to be ignored?
Originally mypackage.policy used z3c.autoinclude, but I tried including mypackage.blah configuration directly in mypakcage.policy and even in buildout.cfg, and the problem persisted. There are no error traces in the log or console.
Any idea on how can I solve this problem?
Thanks in advance.
Did you upgrade collective.js.jqueryui? I did that and it REMOVED all other javascript!
I went into the ZMI->portal_CSS-> bundles (tab) and changed from 'jQueryUI' to 'default' in the 3 boxes. if it already is default, go to ZMI->portal_javacripts-> bundles (tab) and change 'jQueryUI' to 'default' in the 3 boxes.
When I recompile my (previously working) Flex code using the updated Apache Flex 4.10 I get scads of "An internal build error has occurred" messages.
I have tried:
doing a 'clean' and build
checking various installed java versions
building a new project with the existing code
None of these work.
How do I fix this?
Reinstall the Apache Flex 4.10 compiler but make sure to check the box marked "Remoting Support(optional)".
Yes - it says optional but if you use any remoting in your code (AMFPHP anyone?) you will need this. After reinstalling, do a clean and build.
I have followed the instructions on http://doc.qt.nokia.com/stable/sql-driver.html#qibase for compiling Interbase support into Qt, and made sure all of my libraries are in the right place. qmake runs successfully, but when I run nmake, I get a series of undefined reference errors in qsql_ibase.cpp. If I open up the .pro in Qt Creator and hover over one of the functions that is throwing the undefined reference errors and follow the symbol (F2), it takes me to the ibase.h file where it is declared. Is it throwing the undefined reference errors because there is no function definition? If that is the case, why isn't it giving me any errors about a missing library?
Output example:
Creating library file: debug\libqsqlibased4.a
debug/qsql_ibase.o: In function getIBaseError':
C:\QtSDK\QtSources\4.7.4\src\plugins\sqldrivers\ibase/../../../sql/drivers/ibase
/qsql_ibase.cpp:80: undefined reference toisc_sqlcode'
C:\QtSDK\QtSources\4.7.4\src\plugins\sqldrivers\ibase/../../../sql/drivers/ibase
/qsql_ibase.cpp:85: undefined reference to isc_interprete'
debug/qsql_ibase.o:C:\QtSDK\QtSources\4.7.4\src\plugins\sqldrivers\ibase/../../.
./sql/drivers/ibase/qsql_ibase.cpp:406: undefined reference toisc_dsql_free_st
atement'
debug/qsql_ibase.o:C:\QtSDK\QtSources\4.7.4\src\plugins\sqldrivers\ibase/../../.
./sql/drivers/ibase/qsql_ibase.cpp:421: undefined reference to isc_create_blob2
'
debug/qsql_ibase.o:C:\QtSDK\QtSources\4.7.4\src\plugins\sqldrivers\ibase/../../.
./sql/drivers/ibase/qsql_ibase.cpp:427: undefined reference toisc_put_segment'
This continues for many more errors, all undefined references.
That really sounds like the first issue mentioned under the "Troubleshooting" section of the page to which you link above:
You should always use client libraries that have been compiled with
the same compiler as you are using for your project. If you cannot get
a source distibution to compile the client libraries yourself, you
must make sure that the pre-compiled library is compatible with your
compiler, otherwise you will get a lot of "undefined symbols" errors.
Some compilers have tools to convert libraries, e.g. Borland ships the
tool COFF2OMF.EXE to convert libraries that have been generated with
Microsoft Visual C++.
Which compiler are you using to compile Qt, and where did you get the Interbase libraries? You also need to make sure those libraries can be found at link time. If you look at the output of your compiler, it should show you all the link directories in which it is searching (in addition to any globally defined, like PATH in Windows.) If the folder with your Interbase library is listed, it is probably that the compiler versions aren't matching.
Sorry for raising so old theme, but I found a solution and want to share with it. The problem is that macro ISC_EXPORT was not defined in Interbase's SDK due to conditional compilation defines. See details here - Howto build Interbase plugin for Qt by MinGW