Clarification required django celery,celery and djangoceleryemail compatabilty versions to handle asynchronous tasks - django-celery

I am new to Django.
I am developing one django application which needs following packages to handle asynchronous tasks in the back ground.
1.djangocelery
2.djangocelery email.
App definitions in My settings.py file:
INSTALLED_APPS = [
'django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.messages',
'django.contrib.staticfiles',
'crispy_forms',
'djcelery',
'gspapp',
'djcelery_email',
#'django_celery_results',
]
But when i install these packages in my virtual environment, I encountered with the below errors:
1.I have django-celery - 3.3.1 and celery 4.3.0 initially.
2.when i execute the celery worker command :celery -A gspaat worker --loglevel=info
i got the below error:
ModuleNotFoundError: No module named 'kombu.asynchronous'
As per the message posted in below link,i uninstalled celery version and installed latest celery version 4.3.0 .
Cannot start Celery Worker (Kombu.asynchronous.timer)
But unfortunately i am facing with below error.
ERROR: django-celery 3.3.1 has requirement celery<4.0,>=3.1.15, but you'll have celery 4.3.0 which is incompatible.
Due to above error, i installed celery version :3.1.25 using pip install celery==3.1.25 but i got the below error
ERROR: django-celery-email 2.0.2 has requirement celery>=4.0, but you'll have celery 3.1.25 which is incompatible.
So, please share the compatible version of djcelery , celery and djcelery_email.
Regards,
N.Dilip Kumar.

Related

Beam Dataflow job stuck after upgrading the Apache Beam version from 2.27.0 to 2.32.0

Currently I am in a process of upgrading the Apache Beam version from 2.27.0 to 2.32.0 but when I start my jobs on Dataflow runner the job stucks during the worker-startup and it never finish installing dependencies. The python version is 3.7
This is what I see in the logs
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime
After initial analysis it looks like this is the issue with pip dependencies backtracking and it keeps on downloading and installing dependencies. These are some warnings in the logs
INFO: pip is looking at multiple versions of google-auth to determine which version is compatible with other requirements.
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead:
This is the setup.py for the Beam
import setuptools
REQUIRED_PACKAGES = [
"numpy==1.21.4",
"pandas==0.25.3",
"dateparser==1.1.0",
"python-dateutil==2.8.2",
"pytz==2021.3",
"google-api-core==1.14.0",
"google-cloud-storage==1.36.1",
"fastavro==0.22.10",
]
setuptools.setup(
name="data-workflows",
version="0.1.0",
install_requires=REQUIRED_PACKAGES,
packages=setuptools.find_packages(),
)
The pipelines used to run fine in the Beam version 2.27.0. I am not sure if these warnings are the cause of the issue. Could someone please help me to identify the root cause of this problem?

Compile errors when setting up Plone development environment

I'm trying to follow the walkthrough here to produce a new theme for my Plone 5.1 server:
https://training.plone.org/5/theming/theme-package.html
I'm using MacOS 10.13.6 running clang clang-1000.11.45.5 (the one that comes with XCode) and Python 3.6.4 (installed through Anaconda). I've run into some trouble since the buildout script that is produced by mr.bob doesn't appear to contain all of the dependencies, specifically plone.recipe.zope2instance==4.2.22. When I attempt to install that dependency manually, I get the following compilation error:
src/Persistence/_Persistence.c:178:5: error: non-void function 'init_Persistence' should return a value [-Wreturn-type]
return;
^
17 warnings and 7 errors generated.
error: command 'clang' failed with exit status 1
I tried upgrading to the latest version of mr.bob and the templates, then using the plonecli to create and start the buildout, but I get the same compilation errors.
There are many like it in that module. How do I resolve this so I can finish installing that dependency and finish my buildout?
Try to use Python 2.7, it's better supported by Zope and Plone.
Plone is using Python 2.7.x until Version 5.1.
In Plone 5.2 you will have the option to run Plone under Python 3, but then you have to use the WSGI-Server instead of the ZServer. For now just use Plone 5.1 with Python 2.7 as Plone 5.2 is still not finally released.

Phoenix: Running mix ecto.create Error Compiling Ranch Dependency

I'm trying to go through the Up And Running tutorial on the Phoenix framework site. I have the following setup :
macOS 10.14.5
Phoenix 1.4.6
Elixir 1.8.2
Erlang/OTP 22
I create the project with the mix phx.new command. I get prompted to fetch and install the dependencies. I type Y. The dependencies get fetched and installed successfully.
I go to my project directory and enter the following command :
mix ecto.create
The following error appears :
(Mix) Could not compile dependency :ranch, "/Volumes/Macintosh HD/Users/mark/.mix/rebar3 bare compile --paths "/Code/hello/_build/dev/lib/*/ebin"" command failed.
You can recompile this dependency with "mix deps.compile ranch", update it with "mix deps.update ranch" or clean it with "mix deps.clean ranch"
I get the same error if I run mix phx.server.
If I run mix deps.clean ranch and mix deps.update ranch, it lists the following unchanged dependencies:
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
connection 1.0.4
cowboy 2.6.3
cowlib 2.7.3
db_connection 2.0.6
decimal 1.7.0
ecto 3.1.4
ecto_sql 3.1.3
file_system 0.2.7
gettext 0.16.1
jason 1.1.2
mime 1.3.1
phoenix 1.4.6
phoenix_ecto 4.0.0
phoenix_html 2.13.2
phoenix_live_reload 1.2.0
phoenix_pubsub 1.1.2
plug 1.8.0
plug_cowboy 2.0.2
plug_crypto 1.0.0
postgrex 0.14.3
ranch 1.7.1
telemetry 0.4.0
So ranch has been compiled. But when I run mix ecto.create again, I get the same error about being unable to compile dependency :ranch.
I did an Internet search to see if anyone else had the same issue. Every issue someone had with mix ecto.create involved creating database users. No one else had an issue with ranch.
What do I have to do to get the Up and Running tutorial running properly?
I've run into this problem under Ubuntu, and the issue was that the ~/.configure folder was unreadable by my current user. Changing the owner and group on that folder and it's contents solved the problem for us.
I was able to recreate this problem under MacOS, using Elixir 1.7.4 and Erlang 20.1 by changing the permissions on my ~/.config folder to 600. Setting the permissions back to 755 allowed the compile.

`ReferenceError: Meteor is not defined` in `meteor-client.js` Angular-Meteor Project

After an npm install which triggered meteor-client bundle during postinstall, I am receiving this new error in the browser console:
"ReferenceError: Meteor is not defined
at Object.eval (webpack-internal:///../../../../meteor-client.js:32502:3)
at eval (webpack-internal:///../../../../meteor-client.js:32507:30)
at Object.../../../../meteor-client.js (http://localhost:4200/vendor.bundle.js:1395:1)
at __webpack_require__ (http://localhost:4200/inline.bundle.js:55:30)
at eval (webpack-internal:///../../../../../clients/browser/main.ts:3:72)
at Object.../../../../../clients/browser/main.ts (http://localhost:4200/main.bundle.js:424:1)
at __webpack_require__ (http://localhost:4200/inline.bundle.js:55:30)
at Object.0 (http://localhost:4200/main.bundle.js:439:18)
at __webpack_require__ (http://localhost:4200/inline.bundle.js:55:30)
at webpackJsonpCallback (http://localhost:4200/inline.bundle.js:26:23)"
```
Triggered at:
if (Package.reload) {
Meteor._reload.onMigrate(function () {
return [false];
});
}
This behavior occurs with:
#angular/cli: both 1.6.3 & 1.6.6
meteor-client-bundler: 0.3.0
Meteor: both 1.6.0.1 & 1.6.1
I had the same issue, and downgrade as John mentioned worked for me.
If you are wondering how to downgrade your meteor app follow the instructions bellow that I've taken from how do I install a previous version of meteor JS?
1) Go to your project root folder
2) Run meteor update --release x.y.z
Where x.y.z is the desired version, for example 1.6.0
Might be related to this issue with a normal angular-meteor setup? It seems like the Meteor version 1.6.0.1 is crashing the meteor-angular setup. I was testing both project setups, with and without AngularCLI, and experienced exactly the errors described here and at angular-meteor issues.
However, resetting the project to Meteor 1.6 worked for me in both cases.

Invalid parameter elasticsearch_package_name on Elasticsearch_plugin

OS : 'CentOS 6.5
'
ElasticSearch version : '2.3.0'
Master's puppet version: '3.8.7'
Client's puppet version : '3.7.4'
Base module version before upgrade : '0.10.2'
Base module version after upgrade : '5.1.0'
Error: could not retrieve catalog from remote server: Error 400 on
SERVER: invalid parameter elasticsearch_package_name on
Elasticsearch_plugin[license] at
/etc/puppet/environments/production/modules/elasticsearch/manifests/plugin.pp:169
on node bla-test01.dom'
Hi,
This error started after we upgraded our Elasticsearch's base (Official from puppet forge) module from version '0.10.2' to '5.1.0'. Our puppet module of elasticsearch worked just fine before the upgrade.
Since the upgrade this error occurred whenever puppet ran on our nodes.
After we saw this case we tried to restart our puppetserver service. Since the restart, the error occurs once every 3-4 runs of puppet and we have no idea why.
Looking at the elastic/elasticsearch module which is the one you seem to be using i can see that the elastic_plugin custom type did not have the elasticsearch_package_name parameter in version 0.11.0 however the 5.1.0 version does. This looks to me that you may have updated the module on the system but have not restarted the puppet server so it still has the 0.11.0 custom type/provider ruby files loaded.
Restart the puppet master server and see if that fixes the issue

Resources