libgit2sharp : Clone does not work with Latest Nuget version - version

I am trying to clone a repository which is available in BitBucket. Providing correct proxy settings in my git.config file, Clone works only with a specific version of LibGit2Sharp(0.22.0).
With all other latest versions it fails with exception => "failed to send request: The server name or address could not be resolved"
We want to use the latest available version of LibGit2Sharp always. Currently stuck with only version 0.22.0.
Does latest version of LibGit2Sharp does not support Proxy authentication? How latest version of LibGit2Sharp could be used ?

Related

Strapi Rest API - Nextjs - Server error: Fetch Failed

I use Strapi and Nextjs. When trying to fetch Data threw the Rest api i´m getting the Error (see Screenshot)The Rest API is working and the URL for the fetch is correct as well...
Operating System: Mac OS
Strapi: 4.5.3
Node: 18.12.1
Next: 13.0.6
I had the same issue yesterday and it drove me crazy. I finally fixed it by reverting to older versions of Strapi and Node. Try this:
Install a version manager tool like asdf or nvm
In your project directory, set Node version to v16.19.0
Re-install Strapi using npx create-strapi-app#4.3.8 my-project --quickstart in the terminal (Strapi version 4.3.8)
This solved my issue. Hopefully it works for you too. This Strapi page has some version info that also might be helpful. I used it to determine what versions to revert to:
https://docs.strapi.io/developer-docs/latest/getting-started/quick-start.html#_1-install-strapi-and-create-a-new-project

Chocolatey - Install major version of package and update to latest minor version

For my project, I need .NET Core 2.2. The Chocolatey package repository states that .NET Core 2.2.8 is the most recent version of .NET Core 2.2 available. I can install this package with choco install dotnetcore --version 2.2.8 -m. But when 2.2.9 will be released, I will still be on 2.2.8, because I specified that specific version. What command do I need to have .NET Core 2.2 updated to a new minor version when I issue choco upgrade all?
EDIT: I do not want to upgrade to .NET Core 3.x when I issue choco upgrade all, because I have some projects that depend on it. Instead, I explicitly want Chocolatey to upgrade to .NET Core 2.2.9 if it will be released
While I think this belongs better on Super User, based on what is implied by using side by side installations of a package, if you want a new version of that package, use choco install -m to install the newer version of that package. Based on your experience of choco upgrade all upgrading one of your side by side packages however, you may want to inquire on the Chocolatey issue tracker as to what the recommended method of upgrading your other packages would be here.

Microsoft WebDriver installation issue

I am getting an error while installing the MicrosoftWebDriver as mentioned below:
"The version of web browser is not supported for MicrosoftWebDriver"
I downloaded the MicrosoftWebDriver from Release 10586 and checked the Version of my browser and its 13.10586 but still not able to install.

PyCharm unable to load NoseGAE

I've created a nose test config in PyCharm. I have NoseGAE installed in the virtualenv where I'm working. Running tests from the terminal with ./env/bin/nosetests --with-gae src/tests works great. The PyCharm test config, however, yields
/Users/bistenes/Code/myproject/env/bin/python /Applications/PyCharm.app/Contents/helpers/pycharm/noserunner.py src/tests/
Testing started at 6:31 PM ...
/Users/bistenes/Code/myproject/env/lib/python2.7/site-packages/nose/plugins/manager.py:395: RuntimeWarning: Unable to load plugin nosegae = nosegae:NoseGAE: nose>=0.10.1
RuntimeWarning)
Config is set to Nosetests, "All in folder" src/tests. The error happens whether or not --with-gae is passed as a param.
The ensuing failures are indicative of NoseGAE not being loaded:
AssertionError: No api proxy found for service "datastore_v3"
Make sure you have the latest pkg_resources by running pip install --upgrade setuptools. Then add the version of pkg_resources you want to be using to the front of your path. In PyCharm you can do this by adding an environment variable to the test configuration: PYTHONPATH=/path/to/site-packages:$PYTHONPATH.
This is happening because PyCharm, when support for Google App Engine is enabled (under "Languages & Frameworks"), inserts a bunch of GAE SDK directories to the front of the PYTHONPATH. The Python GAE SDK ships with setuptools-0.6c11, a version of setuptools from 2009. This has a very old version of pkg_resources bundled with it, which doesn't work with newer nose plugins.

Failed to initialize App Engine SDK 1.8.9

I am using Indigo on a Mac Pro (10.9.1). I updated to Java1.7 in order to run some updated Google Play Service samples. Under Installed JREs, JAVA7 is shown as the only and default choice, which points to the new Java path. But when I start Eclipse, it started complaining that "JRE version is 1.6.0; version 1.7.0 or later is needed to run Google plugin for Eclipse".
I tried to add the vm option in eclipse.ini, i.e. I added
-vm
/Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/home/bin/java
above "-vmargs" as described here: http://wiki.eclipse.org/Eclipse.ini.
It doesn't make any difference though. Since then, I have uninstalled GPE from Eclipse and installed them again via "install new software" from https://dl.google.com/eclipse/plugin/3.7. Still the same problem. Under Google->App Engine, there is an error message "Failed to initialize App Engine SDK (path)". This points to appengine-java-sdk-1.8.9.
I have checked my Java version using all means I am aware of, i.e. from run Java -version, using Java's control panel, output from code... They all show I am using Java 1.7.0.51.
Any help is appreciated!
Edit: Google has provided a solution that works great. Add this argument in eclipse.ini
-vm
/Library/Java/JavaVirtualMachines/jdk1.7.0_WHATEVERTHESUFFIXIS/Contents/Home/jre/lib/server/libjvm.dylib
Make sure that eclipse Is compiling your project to 1.7 specifications. Even though you have 1.7 selected as your virtual machine, it might be compiling to 1.6. It's in the eclipse project settings

Resources