Getting strange ClassNotFound org.apache.ignite.internal.processors.query.GridQueryRowDescriptor trying to run Ignite examples - ignite

I've been playing around with the Apache Ignite examples trying to learn my way around. I have everything loaded in Eclipse and everything is compiling correctly. At one point, I was able to successfully run the ExampleNodeStartup class, but after stopping the process, I'm no longer able to launch it. I keep getting:
java.lang.ClassNotFoundException: org.apache.ignite.internal.processors.query.GridQueryRowDescriptor
I didn't change anything in the class or the config file, so I'm at a loss as to why it no longer works. I'm using Ignite 2.13.0.

Related

HTTP requests stuck in Pending state when using Vite

I have a rather large Vue 3 application (~550 components). It takes two minutes just to run vue-cli-service serve and around 20 seconds to re-build it after each change. Hot reload stopped working a long time ago so it always needs to be refreshed in the browser even after a small style change. Moreover, the app is still not finished and it will probably get 2-3 times this big in the next year so it will probably be even worse.
Because of these problems, I've decided to migrate it from Vue CLI to Vite. I have already resolved a lot of problems and the app seems to work with Vite now with so much better loading times.
However, it sometimes gets stuck when I start a dev server (vite command) and open it in a browser. The page keeps loading and I can see a lot of pending requests in the Network tab of Chrome DevTools. There's nothing special in the output of vite --debug and running vite --force doesn't help either.
When this problem occurs, the browser always loads a lot of modules (~900) and then it gets stuck on 10-20 modules. The status of all these HTTP requests is simply Pending and they never finish. There are no errors in the browser or on the command line.
I don't think any particular file causes this. Maybe the problem is in my deeply nested folder structure with a lot of re-exports using index.ts file on each level. It mostly gets stuck on my own modules but I've also seen cases when it was waiting for a module of some external library.
Has anybody experienced a similar problem? How did you solve it?
EDIT: I have discovered that this issue only occurs in Chromium-based browsers (Google Chrome, Brave, etc.) on Linux. It works without any problems in Chrome on MacOS and Windows as well as in other browsers (Firefox, GNOME Web, etc.) on Linux.
Thanks to this comment, I realized this was a problem with the file descriptors limit.
On Manjaro Linux (Arch-based), I was able to solve it by adding the following line to both /etc/systemd/system.conf and /etc/systemd/user.conf file:
DefaultLimitNOFILE=65536
After this change, Vite works without any problems in all browsers.

IntelliJ Remote Debug does not work at times

I am using IntelliJ for development and remote debugging of my OSGI code. Most of the time it works. However, at times I am facing the below issue.
IntelliJ connects and the code stops when running; however, I do not see any values at my breakpoint.
Once I could resolve this problem by removing a swap file. Another possibility is a slow resync between my memory and file values.
I restarted my OSGI service and it seems to have resolved the issue. Any details on the internals will be useful.

<BEA-160228> AppMerge failed to merge your application

Got this dreaded <BEA-160228> & ToolFailureException when deploying spring-boot 2.x app on weblogic 12.1.x multiple times. Solved one with some package guesswork in <wls:prefer-application-packages>, but got another again each time we add new dependencies.
I know there's some thread asking this already, but it's usually very specific to each dependencies, i need different perspective on this.
Is there a way to debug/analyze what happened inside weblogic AppMerge process?
So we could exactly pinpoint what library caused this.
I've tried enabling debug deployment options, but didn't see any clue on the logs

AppDomain unloaded issue with service bus version 2.6.5

We have multiple projects that are making use of the service bus library. We are currently using v2.6.5 at the moment and we've been getting several warnings for unit tests that calls to the code in the library. This is the warning message:
System.AppDomainUnloadedException: Attempted to access an unloaded AppDomain. This can happen if the test(s) started a thread but did not stop it. Make sure that all the threads started by the test(s) are stopped before completion.
And we would get it everytime we invoke this method: TopicClient.CreateFromConnectionString(connectionString, topicName)
This warning will not appear if we use the built-in Visual Studio test runner (2012/2015) and it would appear if we opt to use the MSTest runner via the .runsettings file.
It will also not appear if I update my service bus to version 3.0.0 and above but that is not possible because we were having a separate issues with them so the only option now is the stick to version 2.6.5 and try to fix those warnings.
Any idea what could be wrong? If you guys need additional information I'm happy to come up with a simple project that is able to reproduce the warning.

django-jenkins ERROR: runTest (django_jenkins.tasks.lettuce_tests.LettuceTestCase)

I've been working with lettuce for interface testing for the last year and lately I've been trying to use it with django-jenkins for continuous integration.
However, I am having problems on executing only the lettuce tests cases I have into the app directory of my Django project.
When I run python manage.py jenkins I get the lettuce tests executed and the lettuce.xml file with the execution details created into the reports folder. Although I am getting two errors I don't know why (see the errors at the end of my post).
I've been trying to google it to see if someone else is having the same problem but I couldn't find anything. If anyone has any idea I will appreciate.
I've been following this tutorial.
You can check the error here
Here you can access my code on github.