Sqlite Creates lot of dll files on tomcat temp folder - sqlite

i'm using Java 8, gradle, tomcat8 and Sqlite 3.8.11.2.
I installed sqlite on my project obviously using gradle.
All works fine, i dont have any problems but i have lots of dll files on my tomcat/temp folder
You can check on the next link an image that shows it:
http://prntscr.com/bvbgxm
Does anybody know how to avoid it?
Did a miss some configurations?
Thanks!

I was reading in some forum and discovered that Its a reported bug.
https://github.com/xerial/sqlite-jdbc/issues/80

Related

Firebase SDK creating ambiguities with Unity's System.threading.Tasks

I've recently upgraded my Unity project to 2021.2.3f1 on the new M1 16inch macbooks. Upon importing Firebase's SDK, I get the following error on async Tasks types:
It seems there's an ambiguity happening since it works fine without the SDK. Someone in the Firebase discord suggested that:
it's most likely related to the plugins folder dll files,
there should be a some dlls and a folder called net4xx,
if you remove (zip so you can restore it) the rogue dll files, it may fix it..
so only the net4x folder remains
Unfortunately the only net-something folder i've got in my project is in Assets>Parse>Plugins> and is called dotNet45, but it's the only one and there isn't any other net4-something folder anywhere in the project. Removing that dotNet45 folder creates lots of errors.
Someone knows what are the steps to fix this pls?
Thanks !
Actually I was almost there. They're not folders, its these two files that should be deleted:
Then it should be fixed !

Issue with open and running already existing Magnolia-CMS project

I started looking at the Magnolia CMS system and found a project on the web and I can't open it and run it.
This are the files:
author.tar
magnolia.tar.xz
public.tar.xz
magnolia.tar
I tried to add the files into apache folder and run it, I tried with Magnolia CLI to run it, but with no success.
I miss something, but I'm completely new to Magnolia, so I have no idea.
Thanks in advance.
These pages should be sufficient to get started.
https://documentation.magnolia-cms.com/display/DOCS56/Getting+started+with+Magnolia
If you fancy CLI, then
https://documentation.magnolia-cms.com/display/DOCS56/Magnolia+CLI
Hope that helps,
Cheers,

App doesn't load an SQLite database on other machines

I have an app that uses an SQLite database. I'm trying to get a demo version to work, so I can show it to the person I am making it for, it runs, but it refuses to do any sort of SQL. Importing a database, reading it, or creating a new one - nothing happens. Usually such things happen because one or another library is missing - but I doubt that's the case. qsqlite.dll is safe and sound in the sqldrivers folder in the root directory, and Qt5Sql.dll is in the root directory as well. According to Dependancy Walker I'm not missing any libraries. (also resizing images on resizeEvent() doesn't work... huh?!"
What could be the reason here?
/imageformats/qjpegd.dll
/platforms/qwindowsd.dll
/sqldrivers/qsqlited.dll
app.exe
icudt54.dll
icuin54.dll
icuuc54.dll
libgcc_s_dw2-1.dll
libstdc++-6.dll
libwinpthread-1.dll
Qt5Cored.dll
Qt5Guid.dll
Qt5Sqld.dll
Qt5Widgetsd.dll
I found the problem after dropping the issue... this time the answer isn't the usual "wrong library". No. Wrong compilation.
I compiled with MinGW, while after compiling with regular Qt Desktop 5.5 it worked.

BuildTasks.Csc task could not be loaded from the assembly?

I feel guilty asking a question like this around here, but I'm at a loss and would appreciate some help.
A proof-of-concept like web application was built on one PC and put up on a repo to download on another PC at a different location. There was originally an auto-build feature set up where Azure would build and publish automatically on check-in, but that was removed. Things were working on both ends until one side included a bulk of excluded changes. Now I'm seeing the following error:
The "Microsoft.CodeAnalysis.BuildTasks.Csc" task could not be
loaded from the assembly
...\packages\Microsoft.Net.Compilers.1.0.0\build..\tools\Microsoft.Build.Tasks.CodeAnalysis.dll.
Could not load file or assembly
'file:///...\packages\Microsoft.Net.Compilers.1.0.0\tools\Microsoft.Build.Tasks.CodeAnalysis.dll'
or one of its dependencies. The system cannot find the file specified.
Confirm that the declaration is correct, that the assembly
and all its dependencies are available, and that the task contains a
public class that implements Microsoft.Build.Framework.ITask.
Does anyone have any suggestions on where to begin looking for the issue?
It turns out that NuGet packages were committed to the repository and breaking everything. Deleting the project\project\packages directory from the repo solved all build problems since NuGet fetches the packages automatically on build.
I got this error when I created a new branch for my project.
It drove me crazy for an hour. I tried most of the suggestions over the internet including the accepted answer to this question.
I then closed the project, opened it again, cleaned it and the error is gone. So this means this could be cache issue.
Anyways, just wanted to share.
I too tried the top answer with no luck so deleted the contents of my bin and packages dir, closed and re-opened VS and everything fine now.
I have tried all solutions described before, but none worked.
What solved it for me, was to update the Microsoft.Net.Compilers from the NuGet Package Manager
Right-click on your solution.
Go to Manage Nuget Packages.
Search for Microsoft.Net.Compilers.
Install or update on dependent projects as necessary.
Re-build, clean solution and restart Visual Studio worked for me.
Deleting the package and cleaning the solution solved it for me.
Deleting these three directories solves the problem.
/packages
/bin
/obj
NOTE: delete both /bin and /obj from all projects included in the solution (including Test projects).
Problem hides on TFS, you need to remove folder TestProject...\packages from TFS, check in, delete it from your local dir and build again. Worked!
Use the below step:
1) Delete the package folder.
2) close the visual studio.
3) open the project and rebuild the project.
I delete all from packages folder and rebuild solution. It's worked for me.
In my case: this works for me.
It turns out my teammate had already started looking into Windows 10 development and had Microsoft Build Tools 2015 installed on his machine.
I installed the software from https://www.microsoft.com/en-us/download/details.aspx?id=48159 and the problem was solved.
In my case, the solution was:
Use Windows Explorer and navigate to the offending path:
C:\MyApplication\Code\Main\ABCProject\ABCProject.UI\Bin
Right click on bin folder > select properties > Uncheck ReadOnly.
In my case, the solution was:
Right Click on Solution.
Go to Manage Nuget Packages for this Solution.
Search for Microsoft.CodeDom.Providers.DotNetCompilerPlatform.
Uninstall the searched Package.
Restart the Visual Studio.
I just tried this on a clean install of a Windows 10 machine and the issue for me ended up being that I didn't have the .NET 3.5 framework installed. This stackoverflow question helps explain why.
Cannot build WIX project on windows 10
Right Click on Solution.
Go to Manage Nuget Packages for this Solution.
Search forMicrosoft.Net.Compilers on Browse Section.
Deleting the bin folder worked for me
In vs2017 community there appeared a new item in the "build" menu. It disappeared after I used it and was called something like "Optimise project build packages". I clicked it and it fixed everything, just restart etc. I did it on two machines.
What it did was removed Microsoft.net.compilers 2.10.0 and replaced with Microsoft.CodeDom.Providers.DotNetCompilerPlatform 2.0.1
So there you go - more automagic...
My project was built with .Net Core 2.2 but I had .Net core 3.0 preview installed. I uninstalled .Net Core 3.0 from my system and went through all my class libraries, removing Microsoft.Net.Compilers 3.0, then rebuilt and it worked.
I moved my solution from one drive to another, and one of the files could not be copied because "in used", for which I click ignored, producing the error described in this post. Copying the missing file manually fixed it.
file: Microsoft.Build.Tasks.CodeAnalysis.dll
Destination directory: packages\Microsoft.Net.Compilers.2.1.0\tools
For me I was trying to open a MVC5 project in VS 2013 and I was getting this error, Opened it in VS 2017 and up it worked just fine.

When using py2exe, PyQt application cannot load SQlite database

My PyQt application works fine when running on Linux, when in my Windows build environment, or frozen on the machine where it was build with py2exe. But after moving the frozen executable and its supporting files to another machine it can't load the database driver.
It worked fine when I had Python2.5 and an earlier version of PyQt and py2exe. But after upgrading my toolchain I get these errors:
dbname.open returns false
lastError(dbname) is "Driver not loaded"
I have an sqldrivers folder where I put qsqlite4.dll. This was necessary with the previous build environment, but moving or renaming that DLL doesn't change any behavior. I think that's the DLL that Qt can't find, but I haven't been able to tell Qt where to look.
I am currently running these versions:
python-2.6.3
PyQt-Py2.6-gpl-4.6-1
py2exe-0.6.9.win32-py2.6
Profiling in Dependency Walker gives me this error:
LoadLibraryW("\application\sqldrivers\qsqlite4.dll") returned NULL. Error: This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem (14001).
When I ask Dependency Walker for details about Qsqlite4.dll it says:
Error: The Side-by-Side configuration information for "\application\sqldrivers\QSQLITE4.DLL" contains errors.
That would explain why the DLL won't load, but I'm still unclear how to fix it. Closer inspection shows that error for most of the DLLs I call. Do I need to include a manifest for each Qt DLL I load?
Thanks in advance.
DEAR PEOPLE FROM THE FUTURE: Here's what we've figured out so far ...
The accepted answer doesn't really say what dlls they copied and in what places. I managed to fix it by copying the driver inside the sqldrivers directory relative to where the exe and qt dlls are (I'm using PySide but should work with PyQt4 as well). In setup.py:
setup(
...,
data_files = [('sqldrivers', ('C:\Python27\Lib\site-packages\PySide\plugins\sqldrivers\qsqlite4.dll',))],
...,
)
I solved it!
I had a really clever way to avoid making my users install vcredist--I copied the manifest and the DLLs into two places and all the errors about the MS DLLs went away. That's when I started trying to figure out this SQLite driver error.
I wasn't as smart as I thought. If I install vcredist all the "Driver Not Loaded" and "No SQL drivers found" errors go away. Arg.
Try to re-install SOLite, or verify if you have putted the DLL in the correct place, because i remember that the MySQL DLL have to be in System32 directory to develop something that uses it.
Regards.

Resources