Cashew is a simple, fast, and elegant app to manage your Github issues.Features GitHub.com and GitHub Enterprise support Ability to view issue details, assign to users, add labels, attach milestone, comment on issues and much more Ability to save common search queries for quick access. Cashew 1.3 – Desktop client for Github issues. Contribute to codecombat/cashew development by creating an account on GitHub.
- Cashew 1 1 – Desktop Client For Github Issues Working
- Cashew 1 1 – Desktop Client For Github Issues Windows 10
- Cashew 1 1 – Desktop Client For Github Issues Free
I recently installed GitHub for Windows for the first time so I could compile an open source project. While trying to clone the repository, I got this error:
failed to clone the repository ‘whatever’
Please check your internet connection.
Please check your internet connection.
I knew my internet connection was working. A web search revealed answers that didn’t apply or didn’t work for me (an issue that was resolved in an earlier version, and an issue that was fixed by re-installing).
Other descriptions of the problem seemed to happen right at the beginning of the clone operation, or somewhere in the middle. For me it happened at the very end, every time.
Also, if I tried to clone the repo again after the failed attempt, it would take a long time comparing all the files, and then tell me there were thousands of uncommitted files.
So I told GutHub for Windows to stop tracking the repo, and then manually deleted the folder before my many re-attempts.
Using Git Shell
GitHub for Windows configures a Git Shell for you, which seems to be a pre-configured version of an existing shell. For me, it defaulted to PowerShell (other options were Cmd, Git Bash, and Custom). The following steps should work with any shell.
I figured I’d try to clone the repo using the command line. To do this, find Git Shell on the start menu and open it. It should start in your default storage directory (more on this later).
First, get the clone URL. This will be on the right side of the GitHub repo’s web page, like so:
The command to clone a repo from GitHub is:
Note: do this in the directory that will be the parent of your project. Git will create the project directory for you.
In the following screen shot, you’ll see my failed attempt. My default storage directory is
C:UsersBriantistDocumentsGitHub
(the default that GitHub for Windows chose).I got errors that it was unable to create a few files:
error: unable to create file very/long/path/name (no such file or directory)
Bill 2 8 2 sezon. As well as:
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed
warning: Clone succeeded, but checkout failed
Default Storage Directory and Path Name Length
You might be seeing the problem already. That very long path name is not too big by itself, but when added to the default data directory it seems to be exceeding what Windows can handle.
I simply changed the default storage directory in GitHub for Windows to
C:GitHub
to keep it nice and short. This is in under tools
> Options
. After that I had no issues.I suspect that this problem will affect .NET projects more than most because of the long names used in some of the files.
It was just my luck that the first repo I tried to clone contained such long file names. I hope this post helps someone else save the hour+ it took me to figure it out.
Cashew
Cashew is a .NET library for caching responses easily with an HttpClient through an API that is simple and elegant yet powerful.There's support out of the box for the awesome CacheManager via the
Cashew.Adapters.CacheManager
package. Its aim is to focus on the HTTP part of caching and not worrying about how stuff is stored, meaning no half-arsed cache implementations!Cashew targets .NET 4.5 and .NET Standard 1.1 (.NET Core, Mono, Xamarin.iOS, Xamarin.Android, UWP and more) meaning it can be used on all sorts of devices.
Installation
The latest versions of the packages are available on NuGet. To install, run the following command if you want to roll your own cache:
or the command below if you want to utilise the power of CacheManager
Features
General features
- Extremely easy to use, all it takes is one line to configure the whole thing!
- Simple but powerful API that allows customisation
Cache stores
Type | Out of the box? |
---|---|
Dictionary | Yes* |
System.Runtime.Caching.MemoryCache | Yes* |
Microsoft.Extensions.Caching.Memory | Yes* |
Redis | Yes* |
Memcached | Yes* |
Couchbase | Yes* |
Custom | No, but it's super easy to implement your own. |
*Provided that you use
Cashew.Adapters.CacheManager
HTTP Cache-Control Headers
Header | Aka |
---|---|
max-age | 'I don't want cached responses older than this' |
s-maxage | 'I don't want cached responses older than this' |
max-stale | 'Stale responses are OK for this long' |
min-fresh | 'The response has to still be fresh for at least this long' |
no-cache | 'You must validate the cached response with the server |
no-store | 'DO NOT CACHE THIS OR I WILL MAKE YOUR LIFE MISERABLE!' |
only-if-cached | 'I only want a response if it's cached' |
must-revalidate | 'You MUST revalidate stale responses' |
proxy-revalidate | 'You MUST revalidate stale responses' |
Customisation
Cashew provides a lot of customisation opportunities for its users. The most important ones are listed below:
Feature | Quickstart | In-depth |
---|---|---|
Use any cache store | Link | Wiki |
Decide how cache keys are created | Link | Wiki |
Decide which status codes are cacheable | Link | Wiki |
Cashew 1 1 – Desktop Client For Github Issues Working
Usage
For more in-depth information on how to use Cashew, please refer to our wiki.
Configuring HttpClient
Use any cache store
Decide how cache keys are created
Cashew 1 1 – Desktop Client For Github Issues Windows 10
Decide how query strings are handled
Cacheable status codes
Contributing
Cashew 1 1 – Desktop Client For Github Issues Free
Please refer to our guidelines on contributing.