I'm using Django, Celery, and Rabbit MQ on my project and developing everything under Windows 10 before until everything is not working with different error messages that i tried to fix with no luck. And found out that I'm not able to upgrade my Celery from 3.x to 4.x because
Celery 4.x stops support for Windows.
http://docs.celeryproject.org/en/latest/faq.html#does-celery-support-windows
All my development has been in Windows and cannot afford to use other platform or machine for now.
I'm not asking on how to fix the project but on how to face this issue without letting go of Celery and still running it on Windows platform. Any suggestion would be appreciated.
You can run celery under windows just fine. Just make sure to set the FORKED_BY_MULTIPROCESSING environment variable to 1
Related
The question says it all.
Running Windows 10 (home) and googling for the past two hours on running SonarQube in windows10. Everything I came cross talks about running SonarQube in docker.
Anyone out here know if it's even possible to run SonarQube in windows without a container. If it is, how do I do it?
Looks like I can run the server with a Java 11 install.
Once I did that the docs led the way.
I have an Electron app in the Mac AppStore that is essentially just a wrapper around a hosted web app. A few months ago one specific thing has stopped working in this app. I'm using redux-offline to sync changes to the server and this is just not happening any more.
It's working when running it outside of Electron - in any modern browser.
All other requests are working fine.
It's working when debugging it locally.
It's working when running the built version locally.
BUT it fails in the published Mac App Store version. I'm not catching any errors in my logs (server-side or client-side). I just upgraded to the latest Electron (electron#4.1.4, electron-packager#13.1.1) hoping it would solve it - to no avail. I don't even know how to properly debug it since it's only failing in the published version.
Any ideas? On causes, solutions or ways to debug it?
Seems like your application closes by itself. Check all of app.quit executions. For me issue was that app.requestSingleInstanceLock() returns the wrong value for Mac Store build. Please check this issue, if the problem is related to app.requestSingleInstanceLock().
My next work project is going to be using the Meteor framework. Our team recently got licensed to use WebStorm IDE, which has been our favorite up until this point. so we were planning on continuing the project with it.
That is, until it was time to install it. Then we found out that the Windows version of Meteor is only partially finished, and all of our development PC's are windows based.
So we were considering as a work-around for this, we may use Cloud9 as our development IDE, as it supports Meteor. The sharing functions may help our team productivity a bit as well.
But this has some problems...
First, we just invested in WebStorm, so we would ideally like to use it as our primary IDE. But I do not know how we would be able to work with WebStorm if we can not run an up to date version of Meteor on our windows systems?
Second, I'm not sure if it's even possible to use Cloud9 as the development IDE, but then move the C9 project over to our Ubuntu server for hosting when it is time to go live?
Third, even if we could deploy to our Ubuntu server after C9, we plan on many updates to our live application after deployment. I'm not sure if there would be issues with this if our development is on C9 and deployment on a completely different server.
So I'm wondering if anyone has a potential solution for these issues? Is there any way for us to work with Meteor on our live Ubuntu server, or Cloud9, from WebStorm on our Windows systems? Or any way we could integrate Cloud9 and WebStorm together for the best of both worlds? Or any way we could use a Linux emulator or something to allow us to use Meteor on our local windows system, without making it difficult for multiple developers to work on the project at the same time?
Thanks in advance!
The Windows port of Meteor actually is working quite well; the only major issue is that mobile development doesn't work. That is going to be fixed in Meteor 1.1 anyway, whose primary goal is to get Windows support up to that of Linux and Mac OS X.
As the user who initially pushed for Webstorm to add Meteor support back in October 2012, I'd recommend starting with Webstorm and Meteor on Windows right away, unless you need mobile development. In that case, you need native *nix machine (an Ubuntu VM on Windows won't be able to run the Android emulator, for example).
WebStorm also supports server-side Meteor debugging, and they're pretty responsive when it comes to fixing bugs you report on YouTrack. See for example https://youtrack.jetbrains.com/issue/WEB-13490
With Cloud9, you cannot currently SSH into a workspace you have, so a hybrid Webstorm/Cloud9 situation might not be doable at this point.
As for deploying your stuff from Cloud9, that is very doable. There's some documentation here about that: https://docs.c9.io/v1.0/docs/deploying-via-the-command-line
Can the code developed and running in Websphere application server v5.1 run in Websphere application server v6.0/6.1/7.0 without any problems?
My scenario:
Originally, the application developed using Java 1.4 and WAS v5.1. As part of change request, we are going to do some changes in that application.
Currently, in my development environment i have RSA(Rational Software Architect) 7.5. It complaint with only WAS v6.0/6.1/7.0. So i can work with one of these WAS version.
Which version i can choose to work for development WAS v6.0/6.1/7.0?
But finally the developed/changed code in WAS6.0/6.1/7.5 will be deployed in WAS v5.1(PRODUCTION) only. I am worried about whether code will run properly or not.
Will i get any complaint problem in this scenario?
Thanks in advance.
The most important is not to change your compiler settings from 1.4 to the RSA 7.5 default which I believe is 1.5.
In case you compile your source code with higher version of Java and deploy it in a Container which runs on a lower version you are going to have trouble.
Generally it is safe to run and test your legacy app on a higher WAS version but keep your eyes on the compiler settings as I mentioned.
I have had basic tests for meteor on a Windows7 PC.
But there the application crashed too often.
Before this, I tested meteor on PC running Windows8. There, crashes happened much less often and generally they were recovered when I shutdown and rebooted the meteor.
Is Meteor unstable on windows7?
Or is there any way to avoid this?
The version packaged to the MSI installer that can be found on win.meteor.com is not official. If you want a more stable, try the virtualized option I've described on the site. I've been using that for a month without issues.
Please could you be specific about what problems you are seeing, for example, what do you mean by 'crash'.
You can certainly raise issues on SO, but if they appear to be specific to the windows port, please raise a ticket at: https://github.com/sdarnell/meteor
The only difference between Win7 and Win8 meteor, is that the installer sets the Win7 compatibility mode for the node.exe executable on Windows 8.
There are also relatively few differences between the windows port of meteor and the official linux/mac release. So there is a possibility that the issue is either environmental (e.g. you have different things installed on the two machines), or it may even be a core issue that just happens to appear more often Win7 due to timing issues (there was a case of this in 0.6.3).