We used ag-grid version 20 in our application and I followed the instructions on how to import the theme and override the scss variables in our React application. Everything went great and worked as expected. We just updated to version 21.0 so we can use the dndSource feature, but our code won't compile anymore. The error we get is
"Module build failed: Error: resolve-url-loader: CSS error
source-map information is not available at url() declaration"
I looked around and this is what libsass library listed:
Windows line breaks
Normal windows linebreaks are CRLF. But sometimes libsass will output single CR characters.
This problem is specific to multiline declarations. Refer to the libsass bug #2693.
If you have any such multiline declarations preceding url() statements it will fail your build.
Libsass doesn't consider these orphan CR to be newlines but postcss engine does. The result being an offset in source-map line-numbers which crashes resolve-url-loader.
Module build failed: Error: resolve-url-loader: CSS error
source-map information is not available at url() declaration
Some users find the node-sass linefeed option solves the problem.
Solutions
Try the node-sass linefeed option by way of sass-loader.
Not sure how to get around this? We use create-react-app and I dont think the team likes the idea of ejecting and then taking over the webpack config.
Short answer - configure your editor to save files with Linux line endings. Stop putting Windows line endings in your source files, and you won't have that problem.
Related
I'm trying to learn how to use DOTS, and I can't seem to get it to compile in a blank project.
I installed the following packages into a new unity project using editor version 2021.3.6f1:
com.unity.entities 0.51.1-preview.21
com.unity.rendering.hybrid 0.51.1-preview.21
com.unity.dots.editor 0.12.0-preview.6
Most of the (999+) compilation errors are file conflicts between the dots editor and the entities package, on top of some accessibility errors and some general other compilation errors.
One example of a conflict is:
GUID [0f14985c7cd188246a215cae5e2919a6] for asset 'Packages/com.unity.dots.editor/Runtime/Unity.InternalAPIEngineBridge.002/Unity.InternalAPIEngineBridge.002.asmdef' conflicts with: 'Packages/com.unity.entities/Unity.Entities.Editor/Unity.InternalAPIEngineBridge.002/Unity.InternalAPIEngineBridge.002.asmdef' (current owner) We can't assign a new GUID because the asset is in an immutable folder. The asset will be ignored.
And an example of an accessibility error is:
Library\PackageCache\com.unity.dots.editor#0.12.0-preview.6\Editor\SystemSchedule\Details\SystemDetailsVisualElement.cs(36,16): error CS0122: 'SystemTreeViewItem' is inaccessible due to its protection level
Any ideas on how to resolve this? I assume it's a package versioning issue, but I don't know what versions might be compatible
Definitely remove com.unity.dots.editor package from this list. This early dots editor tooling package became replaced by newer & built-in dots tools.
It is no longer needed since 2021.3 (I believe) and is likely to throw all kinds of errors in the newer editor versions.
I am having trouble compiling a book of editing using LaTex via VS Code and the following is the error message I get:
Latexmk: Summary of warnings from last run of (pdf)latex:
Latex failed to resolve 15 reference(s)
Latex failed to resolve 4 citation(s)
Collected error summary (may duplicate other messages):
bibtex waysofmentalprayer: Could not open bibtex log file for 'waysofmentalprayer'
Latexmk: Errors, so I did not complete making targets
It seems that the problem is bibtex. I was playing around and decided to rename the file extension from .bib to .tex and it worked. However, when I use Rstudio, it compiles perfectly with the file extension .bib. Why is this happening?
Update: The document compiles on Rstudio but the citation doesn't work. All that appears is ? instead of the citation.
Update 2: It seems that on my local machine, it is not recognizing bibtex. I downloaded TeXworks but the bibtex option was in gray i.e. I couldn't use it. Does this mean I can't use bibtex?? How do I install it?
I have found a solution. I have answered it here. Basically, I used biblatex instead of natbib.
I am using php-cs-fixer for code formatting in Netbeans 8.2. When I try to format one file, it shows the error
Files that were not fixed due to errors reported during linting after fixing:
I searched for the fix in many websites, but couldn't get this fixed. Is there any way to fix this? I tried with both php-cs-fixer 1 and php-cs-fixer 2.
The error message means that PHP CS Fixer loaded some files from drive, apply changes on them, and then realised that files are not valid anymore (invalid PHP syntax) after those changes, thus it decided to not save it. That's one of the safety mechanism of PHP CS Fixer to not break your project.
This means that you have found an issue in PHP CS Fixer itself.
Please, verify you are using newest release, maybe the bug was already fixed!
If not, please consider to expose your configuration file (if any) and content of files you got listed at https://github.com/FriendsOfPHP/PHP-CS-Fixer/issues/new !
There is also an option to see what happen in progress.
$ ./vendor/bin/php-cs-fixer fix src/ErrorFile.php -vvv
The --verbose option will show the applied rules. When using the txt format it will also display progress notifications.
NOTE: if there is an error like "errors reported during linting after fixing", you can use this to be even more verbose for debugging purpose
-v: verbose
-vv: very verbose
-vvv: debug
So, I've been using Sublime for a while as a simple text editor, but I'm venturing into the land of plugins for work and I've run into an issue getting pylint to work. Specifically I have it installed and have the Sublime package manager working, but I'm not sure how to include paths in my sublime settings.
I haven't found very useful documentation on this point, but if you are willing to point me towards it that would be a perfectly acceptable answer. My basic issue is that currently every time I save a file, the following error message shows up:
"Please define the full path to 'lint.py' in the settings"
I understand this error message which is great, I just have no idea where the sublime settings are or what the standard format for defining a path is. Any help would be appreciated.
There are quite complete directions at the SublimeLinter GitHub page that should describe how to set everything up. Briefly, go to Preferences->Package Settings->SublimeLinter->Settings - Default to see where the different settings are defined. Then, open Preferences->Package Settings->SublimeLinter->Settings - User to change anything, as the main settings will be overwritten when the package is updated. Remember that settings files are in JSON format, so you'll need opening and closing curly brackets to enclose settings, and a comma between them:
{
"sublimelinter_delay": 30,
"sublimelinter_mark_style": "none"
}
I haven't gotten the error you have, are you sure you're using the regular SublimeLinter and not the new beta version? I just installed it fresh on my work machine (I've been using it for a while at home) and after restarting ST2 it's working like a charm with Python.
I had the same problem. I found it to be coming from the package "Pylinter". I removed Pylinter and added SublimeLinter, it covers more than python and is well used. I'm enjoying it quite a bit.
From your command line just run:
sudo easy_install pylint
sudo easy_install pep8
After that restart your sublime.
I encounter the same situation today. In my case, that is because I have not installed the 'pylint' in my system yet. It works fine after I installed the 'pylint' through pip.
Just for other people reference.
I've been trying to build some huge projects in BCB5 for some time now. I want to use the command line tools because it would cut build time by more than 50% (it already takes 4 hours in the IDE). Often, projects will build just fine in the IDE but fail miserably in the command line. I did some digging and discovered this nice little comment in a header file:
__published: // IDE-managed Components
Is this saying that the components that follow can only be built with the IDE open? Please tell me there is a way around this. BCB5 is starting to make me depressed.
Extra info:
Make.exe gives a pile of errors claiming ambiguity between the header file and an imported file. I''m pretty sure the header file is supposed to be referencing the imported file though, rather than comparing with it.
In the header file:
#include <ComCtrls.hpp>
ComCtrls.hpp has the variable TTreeNode.
Error from make:
[exec] Error E2015 .\TMain.h 876: Ambiguity between 'TTreeNode' and 'Comctrls::TTreeNode'
__published: // IDE-managed Components Is this saying that the
components that follow can only be
built with the IDE open? Please tell
me there is a way around this. BCB5 is
starting to make me depressed.
No, this does not mean that you can only build the source in the IDE. It just means that this section is automatically populated by the IDE (the form designer)
While there are good third party solutions (as mentioned by the others) C++Builder 2007 and above made huge improvements in the build system. IDE build times are very similar to command line builds and the MSBuild integration now makes it possible to be sure that the same parameters are passed to the command line tools as are used by the IDE.
Have you tried installing the C++ Compiler Enhancements plugin, by Andreas Hausladen, which improves the compilation speed. I would also recommend installing the DelphiSpeedUp plugin.
I think you need to export the project as makefile, to compile from the command line, because C++Builder 5 project files are XML. Have a look at this article, from the C++Builder Developer's Journal.
If none of the above fails try the official C++Builder Forum.
I've more or less given up on the BCB5 command line tools. It appears that they are fundamentally broken.
I did, however, manage to find a nice open source tool, ProjectMaker, that uses the command line tools effectively. You can find it here: http://projectmaker.jomitech.com.
ProjectMaker fixes up a few of the problems with BPR2MAK, but it's not perfect. Most project build perfectly with ProjectMaker, some still require the IDE. It's not a perfect solution, but it does alright.