cargs | lightweight cross-platform getopt alternative | Parser library

I successfully fixed it!

The mistake was that, I just mentioned the password in the posgres_deployment.yaml file, but I should also mention the database name and the username, using which the web_deployment.yaml is trying to access this db service.

Now the new postgres_deployment.yaml file, after the correction, looks like this:

The application that I was trying to integrate was using libssl 1.0.2 which doesn't support TLS1.3 but grpc 1.35 by default uses TLS1.3 and openssl 1.1.1. So built gRPC with gRPC_SSL_PROVIDER=package and it picked up libssl 1.0.2 and that fixed the issue. Hope this helps anyone.

I think problem is in ApScheduler.

What is happening is that scheduler.start() will attempt to create the job table in your database. But since your database url is specified as +asyncpg and there is no async coroutine running (ie: async def) when ApScheduler tries to create the table. Hence the "coroutine 'connect' was never awaited" error.

After reading the ApScheduler code, I think "integrates with asyncio" is a little misleading - specifically the scheduler can run asyncio, but the JobStore itself has no provision for an asyncio database connection.

You can get it working by removing +asyncpg in the connection url used with ApScheduler.

Note it would still be possible to use async db calls within job functions with a separate asyncpg connection.

The IDispatch::Invoke() method must be called with parameters in reverse order, as stated in the official documentation:

Implementing IDispatch / Passing Parameters:

The arguments are passed in the array rgvarg[ ], with the number of arguments passed in cArgs. The arguments in the array should be placed from last to first, so rgvarg[0] has the last argument and rgvarg[cArgs -1] has the first argument.

Also, in your case, you don't need "named arguments", only "positional arguments". If cNamedArgs is 0, all of the elements of rgvarg[ ] represent positional arguments.

After further investigation I found that it has to do with namespace resolution. The following expression:

There is a problem with your postgres configuration in app.py.

You're not trying to connect to your postgres container, rather your Flask container's localhost. You'll need to specify the address of the postgres container instead. Then it will work perfectly.

You can read more about how network communication in Docker works here.

On the face of it, what you want to do is perfectly possible.

However, you need to be careful about the nature of modules and object references.

For example, say we have your module file:

module.js

All the packages like npm or pip fetches the driver from https://public.dhe.ibm.com/ibmdl/export/pub/software/data/db2/drivers/odbc_cli/ . And they randomly update the file without maintaining the versions. All the versions are maintained in https://www.ibm.com/support/pages/node/323035 Their is some issue with latest version of clidriver(11.5) which is mapped to the link https://public.dhe.ibm.com/ibmdl/export/pub/software/data/db2/drivers/odbc_cli/

Instead, I am able to resolve it by downloading 11.1 version from https://www.ibm.com/support/docview.wss?uid=ibm11116777

For linux downloaded as there are no 64bit driver for odbc-cli so downloaded IBM Data Server Runtime Client Linux x86 and extracted the v11.1.4fp5_linuxx64_dsdriver.tar.gz and replaced node_modules/ibm_db/installer/ and /usr/local/lib/python3.7/site-packages/ with v11.1.4fp5_linuxx64_dsdriver.tar.gz\v11.1.4fp5_linuxx64_dsdriver.tar\dsdriver\odbc_cli_driver\linuxamd64\

For windows : IBM Data Server Driver for ODBC and CLI (64-bit) and replaced node_modules/ibm_db/installer/ and /usr/local/lib/python3.7/site-packages/ with Windows 64bit