Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified	Actions
📁 ..	-	2025-06-25 08:26
📄 CODE_OF_CONDUCT.md # Treat each other well Everyone participating in the _requests_ project, and in particular in the issue tracker, pull requests, and social media activity, is expected to treat other people with respect and more generally to follow the guidelines articulated in the [Python Community Code of Conduct](https://www.python.org/psf/codeofconduct/).	346 B	2024-05-29 15:36
📄 CONTRIBUTING.md # Contribution Guidelines Before opening any issues or proposing any pull requests, please read our [Contributor's Guide](https://requests.readthedocs.io/en/latest/dev/contributing/). To get the greatest chance of helpful responses, please also observe the following additional notes. ## Questions The GitHub issue tracker is for bug reports and feature requests. Please do not use it to ask questions about how to use Requests. These questions should instead be directed to [Stack Overflow](https://stackoverflow.com/). Make sure that your question is tagged with the `python-requests` tag when asking it on Stack Overflow, to ensure that it is answered promptly and accurately. ## Good Bug Reports Please be aware of the following things when filing bug reports: 1. Avoid raising duplicate issues. Please use the GitHub issue search feature to check whether your bug report or feature request has been mentioned in the past. Duplicate bug reports and feature requests are a huge maintenance burden on the limited resources of the project. If it is clear from your report that you would have struggled to find the original, that's ok, but if searching for a selection of words in your issue title would have found the duplicate then the issue will likely be closed extremely abruptly. 2. When filing bug reports about exceptions or tracebacks, please include the complete traceback. Partial tracebacks, or just the exception text, are not helpful. Issues that do not contain complete tracebacks may be closed without warning. 3. Make sure you provide a suitable amount of information to work with. This means you should provide: - Guidance on how to reproduce the issue. Ideally, this should be a small code sample that can be run immediately by the maintainers. Failing that, let us know what you're doing, how often it happens, what environment you're using, etc. Be thorough: it prevents us needing to ask further questions. - Tell us what you expected to happen. When we run your example code, what are we expecting to happen? What does "success" look like for your code? - Tell us what actually happens. It's not helpful for you to say "it doesn't work" or "it fails". Tell us how it fails: do you get an exception? A hang? A non-200 status code? How was the actual result different from your expected result? - Tell us what version of Requests you're using, and how you installed it. Different versions of Requests behave differently and have different bugs, and some distributors of Requests ship patches on top of the code we supply. If you do not provide all of these things, it will take us much longer to fix your problem. If we ask you to clarify these and you never respond, we will close your issue without fixing it.	2.82 KB	2024-05-29 15:36
📄 FUNDING.yml custom: ['https://www.python.org/psf/sponsorship/']	52 B	2024-05-29 15:36
📁 ISSUE_TEMPLATE	-	2024-05-29 15:36
📄 ISSUE_TEMPLATE.md Summary. ## Expected Result What you expected. ## Actual Result What happened instead. ## Reproduction Steps ```python import requests ``` ## System Information $ python -m requests.help ``` <paste here> ``` This command is only available on Requests v2.16.4 and greater. Otherwise, please provide some basic information about your system (Python version, operating system, &c).	394 B	2024-05-29 15:36
📄 SECURITY.md # Vulnerability Disclosure If you think you have found a potential security vulnerability in requests, please email [Nate](mailto:nate.prewitt@gmail.com) and [Seth](mailto:sethmichaellarson@gmail.com) directly. Do not file a public issue. Our PGP Key fingerprints are: - 8722 7E29 AD9C FF5C FAC3 EA6A 44D3 FF97 B80D C864 ([@nateprewitt](https://keybase.io/nateprewitt)) - EDD5 6765 A9D8 4653 CBC8 A134 51B0 6736 1740 F5FC ([@sethmlarson](https://keybase.io/sethmlarson)) You can also contact us on [Keybase](https://keybase.io) with the profiles above if desired. If English is not your first language, please try to describe the problem and its impact to the best of your ability. For greater detail, please use your native language and we will try our best to translate it using online services. Please also include the code you used to find the problem and the shortest amount of code necessary to reproduce it. Please do not disclose this to anyone else. We will retrieve a CVE identifier if necessary and give you full credit under whatever name or alias you provide. We will only request an identifier when we have a fix and can publish it in a release. We will respect your privacy and will only publicize your involvement if you grant us permission. ## Process This following information discusses the process the requests project follows in response to vulnerability disclosures. If you are disclosing a vulnerability, this section of the documentation lets you know how we will respond to your disclosure. ### Timeline When you report an issue, one of the project members will respond to you within two days at the outside. In most cases responses will be faster, usually within 12 hours. This initial response will at the very least confirm receipt of the report. If we were able to rapidly reproduce the issue, the initial response will also contain confirmation of the issue. If we are not, we will often ask for more information about the reproduction scenario. Our goal is to have a fix for any vulnerability released within two weeks of the initial disclosure. This may potentially involve shipping an interim release that simply disables function while a more mature fix can be prepared, but will in the vast majority of cases mean shipping a complete release as soon as possible. Throughout the fix process we will keep you up to speed with how the fix is progressing. Once the fix is prepared, we will notify you that we believe we have a fix. Often we will ask you to confirm the fix resolves the problem in your environment, especially if we are not confident of our reproduction scenario. At this point, we will prepare for the release. We will obtain a CVE number if one is required, providing you with full credit for the discovery. We will also decide on a planned release date, and let you know when it is. This release date will always be on a weekday. At this point we will reach out to our major downstream packagers to notify them of an impending security-related patch so they can make arrangements. In addition, these packagers will be provided with the intended patch ahead of time, to ensure that they are able to promptly release their downstream packages. Currently the list of people we actively contact ahead of a public release is: - Jeremy Cline, Red Hat (@jeremycline) - Daniele Tricoli, Debian (@eriol) We will notify these individuals at least a week ahead of our planned release date to ensure that they have sufficient time to prepare. If you believe you should be on this list, please let one of the maintainers know at one of the email addresses at the top of this article. On release day, we will push the patch to our public repository, along with an updated changelog that describes the issue and credits you. We will then issue a PyPI release containing the patch. At this point, we will publicise the release. This will involve mails to mailing lists, Tweets, and all other communication mechanisms available to the core team. We will also explicitly mention which commits contain the fix to make it easier for other distributors and users to easily patch their own versions of requests if upgrading is not an option.	4.11 KB	2024-05-29 15:36
📄 dependabot.yml version: 2 updates: - package-ecosystem: github-actions directory: / schedule: interval: weekly ignore: # Ignore all patch releases as we can manually # upgrade if we run into a bug and need a fix. - dependency-name: "*" update-types: ["version-update:semver-patch"]	313 B	2024-05-29 15:36
📁 workflows	-	2024-05-29 15:36

Terminal