Github command delete file and download again

MWB 3. Hi everyone, spent a couple of hours before turning off MalwareBytes Ransomware Protection, and finally got things to work. I have just encountered this very issue. I have no node processes active and I dont even have vscode installed. Removing the package-lock. The downside of this, is that I don't know if "npm install" removes the extra modules that are not required by the new project, therefore having extra module folders that are not being used.

I got no VSCODE, no Malware, no Defender, not sure node-gyp would cause any sharing issue, if I run npm install individually for that package, it works, it is my workaround anyways but I dont like workarounds.

For me the problem was solved apparently with npm uninstall I was installing using bash in powershell. I tried switching to normal cmd and it works. Just experienced this on MacOS Just experienced this issue with npm 6. I had to delete package-lock. Same problem here. Removing package-lock. However, this is by no means a solution nor a workaround. Hello everyone, for this problem just run npm update after that you can install module as usual. I'm going to both close and lock this, since it's resolved.

If you're still experiencing this and you have a reliable repro, and none of the above steps fixed it for you please file a new issue in the npm. Skip to content.

This repository has been archived by the owner. It is now read-only. Star Labels npm5 support. Copy link. I'm opening this issue because: npm is failing for some reason I don't understand What's going wrong? This is happening to me more often than not.

Example: npm ERR! DELETE' It is a different file every time, sometimes doesn't happen at all, but when it does, always with [something]. Turning off virus protection doesn't help. Running npm cache clean -f , as administrator doesn't help The problem has been getting steadily worse since a week or so ago, but seems somewhat random as to which file it will fail upon.

How can the CLI team reproduce the problem? I use a proxy to connect to the web. I use a proxy when downloading Git repos. If for some reason e. This downloads the zipped repo for a given branch. Note that you can also replace the branch by a commit hash.

Will also expand and delete the archive. I believe GitHub server will accept wget request and treat it as same as request with browser.

Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. How to download a GitHub repo as. Asked 4 years, 4 months ago. Active 4 months ago.

Viewed 70k times. Improve this question. Melebius UbuntuCoder UbuntuCoder 1 1 gold badge 1 1 silver badge 6 6 bronze badges. Does your URL really ends with. I am trying to download a project from github and it has a download button giving zip and other options. So, I'm trying from there. Also known as: Help, my important issue not being solved! The youtube-dl core developer team is quite small. While we do our best to solve as many issues as possible, sometimes that can take quite a while.

To speed up your issue, here's what you can do:. First of all, please do report the issue at our issue tracker. That allows us to coordinate all efforts by users and developers, and serves as a unified point. Unfortunately, the youtube-dl project has grown too large to use personal email as an effective communication channel. Please read the bug reporting instructions below.

A lot of bugs lack all the necessary information. If you can, offer proxy, VPN, or shell access to the youtube-dl developers. If you are able to, test the issue from multiple computers in multiple countries to exclude local censorship or misconfiguration issues. Feel free to bump the issue from time to time by writing a small comment "Issue is still present in youtube-dl version Please do not declare your issue as important or urgent.

For one, have a look at the list of supported sites. In that case, simply report a bug. It is not possible to detect whether a URL is supported or not. That's because youtube-dl contains a generic extractor which matches all URLs. You may be tempted to disable, exclude, or remove the generic extractor, but the generic extractor not only allows users to extract videos from lots of websites that embed a video from another service, but may also be used to extract video from a service that it's hosting itself.

Therefore, we neither recommend nor support disabling, excluding, or removing the generic extractor. If you want to find out whether a given URL is supported, simply call youtube-dl with it.

If you get no videos back, chances are the URL is either not referring to a video or unsupported. You can find out which by examining the output if you run youtube-dl on the console or catching an UnsupportedError exception if you run it from a Python program.

The issue template also guides you through some basic steps you can do, such as checking that your version of youtube-dl is current. Most users do not need to build youtube-dl and can download the builds or get them from their distribution. To run youtube-dl as a developer, you don't need to build anything either. Simply execute.

To run the test, simply invoke your favorite test runner, or execute a test file directly; any of the following work:. See item 6 of new extractor tutorial for how to run extractor specific test cases. If you want to add support for a new site, first of all make sure this site is not dedicated to copyright infringement. After you have ensured this site is distributing its content legally, you can follow this quick list assuming your service is called yourextractor :.

This should fail at first, but you can continually re-run it until you're done. The tests will then be named TestDownload. Add tests and code for as many as you want. Make sure your code follows youtube-dl coding conventions and check the code with flake8 :.

Make sure your code works under all Python versions claimed supported by youtube-dl, namely 2. When the tests pass, add the new files and commit them and push the result, like this:.

Finally, create a pull request. We'll then review and merge it. This section introduces a guide lines for writing idiomatic, robust and future-proof extractor code.

Extractors are very fragile by nature since they depend on the layout of the source data provided by 3rd party media hosters out of your control and this layout tends to change. As an extractor implementer your task is not only to write code that will extract media links and metadata correctly but also to minimize dependency on the source's layout and even to make the code foresee potential future changes and be ready for that.

This is important because it will allow the extractor not to break on minor layout changes thus keeping old youtube-dl versions working. Even though this breakage issue is easily fixed by emitting a new version of youtube-dl with a fix incorporated, all the previous versions become broken in all repositories and distros' packages that may not be so prompt in fetching the update from us.

Needless to say, some non rolling release distros may never receive an update at all. For extraction to work youtube-dl relies on metadata your extractor extracts and provides to youtube-dl expressed by an information dictionary or simply info dict. Only the following meta fields in the info dict are considered mandatory for a successful extraction process by youtube-dl:. In fact only the last option is technically mandatory i.

But by convention youtube-dl also treats id and title as mandatory. Thus the aforementioned metafields are the critical data that the extraction does not make any sense without and if any of them fail to be extracted then the extractor is considered completely broken. Any field apart from the aforementioned ones are considered optional.

That means that extraction should be tolerant to situations when sources for these fields can potentially be unavailable even if they are always available at the moment and future-proof in order not to break the extraction of general purpose mandatory fields. Assume you want to extract summary and put it into the resulting info dict as description.

Since description is an optional meta field you should be ready that this key may be missing from the meta dict, so that you should extract it like:. The latter will break extraction process with KeyError if summary disappears from meta at some later time but with the former approach extraction will just go ahead with description set to None which is perfectly fine remember None is equivalent to the absence of data.

On failure this code will silently continue the extraction with description set to None. That is useful for metafields that may or may not be present.

When extracting metadata try to do so from multiple sources. For example if title is present in several places, try extracting from at least some of them. This makes it more future-proof in case some of the sources become unavailable. Say meta from the previous example has a title and you are about to extract it.

Since title is a mandatory meta field you should end up with something like:. If title disappears from meta in future due to some changes on the hoster's side the extraction would fail since title is mandatory. That's expected.

Assume that you have some another source you can extract title from, for example og:title HTML meta of a webpage. In this case you can provide a fallback scenario:. This code will try to extract from meta first and if it fails it will try extracting og:title from a webpage. Capturing group must be an indication that it's used somewhere in the code. Any group that is not used must be non capturing. When using regular expressions try to write them fuzzy, relaxed and flexible, skipping insignificant parts that are more likely to change, allowing both single and double quotes for quoted values and so on.

Note how you tolerate potential changes in the style attribute's value or switch from using double quotes to single for class attribute:. There is a soft limit to keep lines of code under 80 characters long.

This means it should be respected if possible and if it does not make readability and code maintenance worse. For example, you should never split long string literals like URLs or some other often copied entities over multiple lines to fit this limit:.

Extracting variables is acceptable for reducing code duplication and improving readability of complex expressions. However, you should avoid extracting variables used only once and moving them to opposite parts of the extractor file, which makes reading the linear flow difficult. Multiple fallback values can quickly become unwieldy. Collapse multiple fallback values into a single expression via a list of patterns. Use them for string to number conversions as well.

If you encounter any problems parsing its output, feel free to create a report. From a Python program, you can embed youtube-dl in a more powerful fashion, like this:. Most likely, you'll want to use various options. For a start, if you want to intercept youtube-dl's output, set a logger object.

Unless you were prompted to or there is another pertinent reason e. GitHub fails to accept the bug report , please do not send bug reports via personal email. For discussions, join us in the IRC channel youtube-dl on freenode webchat. Please include the full output of youtube-dl when run with -v , i.

It should look similar to this:. Do not post screenshots of verbose logs; only plain text is acceptable. The output including the first lines contains important debugging information. Issues without the full output are often not reproducible and therefore do not get solved in short order, if ever.

Please re-read your issue once again to avoid a couple of common mistakes you can and should use this as a checklist :. We often get issue reports that we cannot really decipher. While in most cases we eventually get the required information after asking back multiple times, this poses an unnecessary drain on our resources.

Many contributors, including myself, are also not native speakers, so we may misread some parts. So please elaborate on what feature you are requesting, or what bug you want to be fixed.

Make sure that it's obvious. If your report is shorter than two lines, it is almost certainly missing some of these, which makes it hard for us to respond to it. We're often too polite to close the issue outright, but the missing info makes misinterpretation likely. As a committer myself, I often get frustrated by these issues, since the only possible way for me to move forward on them is to ask for clarification over and over.

For bug reports, this means that your report should contain the complete output of youtube-dl when called with the -v flag. The error message you get for most bugs even says so, but you would not believe how many of our bug reports do not contain this information. If your server has multiple IPs or you suspect censorship, adding --call-home may be a good idea to get more diagnostics.

Site support requests must contain an example URL. There should be an obvious video present. Except under very special circumstances, the main page of a video service e.

Before reporting any issue, type youtube-dl -U. This should report that you're up-to-date. This goes for feature requests as well. Make sure that someone has not already opened the issue you're trying to open.

Search at the top of the window or browse the GitHub Issues of this repository. If there is an issue, feel free to write something along the lines of "This affects me as well, with version Here is some more information on the issue While some issues may be old, a new post into them often spurs rapid activity. Before requesting a new feature, please have a quick peek at the list of supported options. Many feature requests are for features that actually exist already!