Node mongodb native driver version 3.7 provides a domainsEnabled connection option (as described in 3.7 documentation)
Enable the wrapping of the callback in the current domain, disabled by default to avoid perf hit
However, I don't find a similar option in 4.0 release
Why has it been removed? Is there any workaround to have the same functionality with 4.0?
Thanks!
Related
My mirth is running on an AWS EC2 instance. I want to upgrade the version of Mirth Connect running there. I am currently using 3.8.0, which I want to upgrade to version 3.11. However, I haven't found any good instructions or scripts for performing the upgrade that does not involve GUI tools. Does anyone know where I can find such a script or instructions?
In place upgrades are not safe, given enhancements within Mirth Connect itself and JRE. Many changes might have happened across versions 3.9 and 3.10. I suggest getting the appropriate tar.gz file version from the NextGen website then installing version 3.11.0 as a second instance while assigning different HTTP and HTTPS ports. You can then export channels in version 3.8 and do incremental imports to version 3.11.0 while you monitor closely. The command line interface documentation here offers an easier way to handle channel exports and imports.
We upgraded our Oracle DB and oracle client from 12.1 to 19.10.
Our application server have below setup
OS is Linux
Python version is 2.7.5 and there is no plan to upgrade the python version yet
cx_Oracle library version is 5.3
A quick test shows the application works fine but I am wondering if I need to upgrade the cx_Oracle library? Does it have a support expiry date? I tried to google it, read the information on its Github page but can't find any statement that answers my question.
This combination hasn't been tested. But since the Oracle Client libraries keep compatibility it is likely to work, subject to whatever underlaying enforced changes have been made to the Oracle libraries, perhaps to drop unsupported TLS versions or whatever has occurred in the 8 years since 12.1 was released that I don't know about. You application testing should be the final confirmation.
You should definitely set a goal to update to Python 3 so you can get the latest cx_Oracle version.
Even in an extremely simple setting, I'm unable to get any breakpoints in my code to hit. See the attached screenshot. After hitting 'Debug "main.js"', the execution is never interrupted.
Since you are using Node v7.x ... the solution for now is:
either downgrade Node to v6.x
or WebStorm to older version.
From this official comment:
Are you using Node 7.x? It's a known issue unfortunately, see https://youtrack.jetbrains.com/issue/WEB-24629. Hidden option for turning dev tools protocol support off (js.debugger.node.use.inspect=false) will be included in next 2016.3 update - see https://youtrack.jetbrains.com/issue/WEB-24629#comment=27-1809582.
For now the only workaround is downgrading Node.js to 6.x :( Full Node 7 support (using v8 inspector) will be available in 2017.1
You may also try latest EAP build of 2017.1 -- https://confluence.jetbrains.com/display/WI/WebStorm+EAP -- it may have that fix already available (sorry, not using NodeJS myself so cannot confirm it).
I am using the Java driver 4.0.0 and DB version 3.1. When I try to query, using FILTER, the ArangoCursor returns with a null element. Tried using Vpack and POJO. Neither of them work.
This is a bug in the DB in version 3.1.RC2. It is fixed in final version 3.1, which we release at the moment. It should be available in the next 1-2 days. With that version you need the driver in version 4.1.0, because we changed the velocystream protocol in the DB version 3.1, to remove the need of an extra velocystream endpoint. Driver version 4.1.0 only works with the final release and not with the RCs.
I am a beginner in Azure and have come across a task to change the storage version.I basically found that the versions are obsolete and need to upgrade them as per http://blogs.msdn.com/b/windowsazurestorage/archive/2014/08/05/microsoft-azure-storage-service-version-removal.aspx
So, in one of the paragraphs its mentioned
"What to change
If you find any log entries which show that version to be removed is being used, you will need to find that component and either validate that it will continue to work (unversioned requests may continue to work as their implicit version will simply increase – see above), or take appropriate steps to change the version being used. Most commonly, one of the following two steps will be used:
1) Change the version specified in the request, typically by migrating to a later version of the libraries/tools. When possible, migrate to the latest version to get the most improvements and fixes.
2) Set the default service version to one of the supported versions now so that the behavior can be verified prior to removal. This only applies to anonymous requests with no explicit version. "
Question is, how to go about implementing point 1 and 2 ?
Thanks
Since your code is written in C# and uses Azure SDK your best bet is to upgrade it to a "new enough" SDK. It's unclear whether version 2.0 or 2.1 is the lowest required. So your route is the following:
First, check if you really have to do anything.
You check which Azure SDK your service uses. If it's 2.1 or higher you don't need to worry yet. If your're unsure - use Fiddler to validate the version headers as explained in the linked to post.
If you use Azure SDK 2.0 you'd better check the version headers as explained in the linked to post.
If you use Azure SDK prior to 2.0 you are surely affected and have to upgrade.
So if you found you do need to upgrade you'll have to download and install the newer SDK and then remove references to old SDK assemblies from your projects and add references to new SDK assemblies. Then you try to build your code and maybe fix a lot of calls because SDK interfaces have changed (that's what I see migrating from 1.8 to 2.4). Once it builds you test it works fine and then you remove the old SDK version to ensure the code builds without it present.
There was a breaking change between 2.1 and 2.2 - the latter only support Visual Studio 2012 and higher. There was another set of changes in Azure Diagnostics functioning between 2.4 and 2.5 which are so long to read that I chose to migrate to 2.4 instead of 2.5.