is there a way to remove all the circular dependencies warnings (from typeorm) in the console? everything is working fine but i have like 50+ pages of warning in the console log before the start up NestJs logs
Related
I'm trying to deploy my own .bna file to a business network using
this tutorial.
The only difference is that I am doing this with three organizations.
Everything works fine until I run the step eight because when I run this command:
composer network ping -c alice#trade-network
I got this error:
Error trying to ping. Unexpected end of JSON input.
Does anybody know how can I solve this?
Thank you
I had the same issue, and I knew it was a matter of local configuration since it stopped working suddenly after throwing several commands. So, I fixed it by stopping fabric and tearing it down.
Then, started fabric, created my peer credential and deployed everything again.
Review the commands in here (section: Controlling your dev environment):
https://hyperledger.github.io/composer/v0.19/installing/development-tools.html
Hi guys im having an issue with my intellij react project, ive already connected to the MySQL DB from intelliJ..
After running springboot:run, it installs all dependencies for the app after all is done i get a target folder thats red and a package-lock.json thats also red what does this mean?
Im new to react so im trying to run this app locally but when i run the project i get this error:
"Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled.
2018-06-22 13:23:20.295 ERROR 6796 --- [ restartedMain] o.s.boot.SpringApplication : Application startup failed"
Project has already been built by previous Dev im just trying to get it ti run locally now.
what could i be doing wrong?
Spring-boot is one of the wonderful thing to get started to fast, it
does many things automatically. At the same time, missing
configuration will lead to this kind of errors.
Please double check application.yaml/.properties and pom.xml for more details.
This error is thrown when dependencies are not resolved correctly and mis-configuration of dependencies.
If it is a Maven project, right click on project folder and do 'Maven -> Re-Import'. It will fetch the missing maven dependencies.
Also, whatever is mentioned as part of the dependencies should have proper configurations. Let's say for example, you're mentioning mysql as dependency and doesn't provide connection/username/password details then this error occurs.
Please provide more details/error-trace log to provide more accurate answer.
Hope it helps!!
We recently upgraded an old rails app from rails 3 to 4.2, along with many other gem updates. Now I can't get my rails app to load any pages. We were on JRuby 9.1.0.0 but upgraded to 9.1.8.0. However, I'm hitting the same problem on both versions.
Once we start tomcat with our latest .war, it runs all the way until I see the INFO: Server startup in 1234ms message. I've added some debug statements in my rails environment / initializers files to follow it through and it is hitting each of them. So once I see the startup message from tomcat, I figured it would be okay. However, it immediately spits out the following message quite a few times:
DEBUG: resetting rack response due exception
Every time I load a URL, it also shows that message in my logs.
I see that it's from this jruby-rack class but I have no idea how to debug or troubleshoot this further.
I assume that something in my configuration is causing a problem or that a class/module is somehow short-circuiting it but I'm not sure how to identify which one it is or isolate the issue.
Does anybody know of a way to get some more verbose logs or ways to figure out where the problem is happening?
Happy to post any config/gemfiles etc if it will help.
After receiving some great help from the #jruby IRC channel, they mentioned the error message was missing the specific exception message. I was using the latest version, v1.1.21 so I just made a hack-build that added some logging to identify my problem further. Turns out it was a runtime error because of some missing config.
I made an issue with jruby-rack and a PR which will hopefully make its way into the next release!
I get a dyld fatal error as xcode attempts to initiate the UI test suite.
dyld: Library not loaded: #rpath/XCTest.framework/XCTest
Referenced from: /var/mobile/Containers/Bundle/Application/9A03F81B-1A93-4F0E-88B0-56C0748D1D43/ExampleUITests-Runner.app/XCTRunner
Reason: no suitable image found. Did find:
/private/var/mobile/Containers/Bundle/Application/9A03F81B-1A93-4F0E-88B0-56D0748D1D43/ExampleUITests-Runner.app/Frameworks/XCTest.framework/XCTest: mmap() errno=1 validating first page of '/private/var/mobile/Containers/Bundle/Application/9A03F81B-1A93-4F0E-88B0-56D0748D1D43/ExampleUITests-Runner.app/Frameworks/XCTest.framework/XCTest'
So I'm running this on a Mac Mini which is a designated testing workstation. I have the same identical project on my macbook and it runs fine. I tried deleting my project and re-cloning it and it still goes through the same issue.
Any ideas on what the issue may be?
On a side note, I had this issue before. My solution was doing a re-format since re-installing Xcode and recloning my project from github did not fix the issue.
Error seems to suggest that Xcode is not able to locate XCTest.framework on your mac mini.Did you try adding $(PLATFORM_DIR)/Developer/Library/Frameworks to Framework Search Path of your UI Test Target.
You can also test adding XCTest.framework as a Build Phases Dependency.
It turned out it was an error regarding my certificates and this issue was resolved by revoking my certificates and resetting all of them.
Then I had to remove the problem apps from my device from Window > Devices and that allowed me to run my tests.
I'm having the following problem with Hudson after upgrading to 2.1.0:
After successfully creating the doxygen output, the following exception occurs:
Publishing Doxygen HTML results.
The determined Doxygen directory is 'C:/doxy/myDir'.
FATAL: error
hudson.util.IOException2: java.io.IOException: Unconnected pipe
The error did not occur with 2.0.1, unfortunately, downgrading does not work - Hudson tells me, that it can't read the job files anymore.
Does anyone know the best way to deal with this? Is there a simple solution to either make the doxygen plugin work in 2.1.0 or to successfully downgrade to 2.0.1?
Not sure what exactly the problem was, but migrating to the newest Jenkins release and using the HTML report publisher plugin instead of the Doxygen plugin is at least a work