Patch File.pdf
- 1. Can we use first and third party cookies and web beacons to understand our audience, and to tailor promotions you see? Yes, please No, do not track me Documentation Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center. Learn more Advertising sustains the DA. Ads are hidden for members. Join today Get 10 free Adobe Stock photos. Start downloading amazing royalty-free stock photos today. ADS VIA CARBON Using GitLab to Contribute to Drupal Introduction Creating issue forks Creating merge requests Rebase a merge request Reviewing merge requests GitLab CI Editing a merge request Policy for use of Personal Access Tokens (PATs) and other automation Use issue forks to make core version compatibility fixes GitLab Frequently Asked Questions Downloading a patch file
- 2. Downloading a patch file Last updated on 9 November 2023 This documentation needs work. See "Help improve this page" in the sidebar. Downloading a patch file from a merge request You can download a patch file directly from an issue by clicking the plain diff link at the top of an issue Or, while on the MR page from the Plain diff button in the download menu of an MR (See screenshot). You can also get a patch file for any merge request by appending .patch to the end of the url. For example, if this is your merge request: https://git.drupalcode.org/project/drupalorg/-/merge_requests/17 add '.patch' https://git.drupalcode.org/project/drupalorg/-/merge_requests/17.patch to get a patch url.
- 3. The patch resulting from adding .patch has separate changes for each commit. When the MR is long and has several changes to the same files, including file renames, the resulting patch file may not be useable. In this situation, you can replace .patch with .diff to get a simpler patch file with each file only appearing once but containing consolidated changes for the whole merge request. Also note that if more commits are added to the merge request, the patch that you can download from that URL will change. So if you want to preserve a patch at a certain point, download the patch file and save it locally. Patch files for use with Composer While project maintainers may not require patches and can handle merging and testing themselves with Git remotes, non-maintainers trying to test an issue will be greatly helped by a patch file. Patch files also allow for faster delivery of changes across multiple test environments. Composer can only get patch files applied to the code and can't deal with commits from forks without extra burden. Luckily Gitlab provides patches both for single commits and for Merge Requests. Patch files can be obtained for both single commits and Merge Requests. There are two methods for getting the patch file: 1. By appending .patch at the end of the url displayed in gitlab when viewing a commit or a Merge Request. 2. By using the Email Patches option in the Gitlab UI. An example using method 1: If you're looking at a merge request, for example https://git.drupalcode.org/project/drupal/-/merge_requests/20 you can append .patch to the url to obtain a patch file like so: https://git.drupalcode.org/project/drupal/-/merge_requests/20.patch More details on method 2 through the Gitlab UI: To get a patch file for a single commit navigate to the commit page, click on Options and select Email Patches: Patch files are also useful if you use bash patch -p1 < file or git apply patch
- 4. To get the patch for a Merge Request that consists of several commits navigate to the overview of the MR, click on the "arrow down" icon and then click Email Patches:
- 5. In both cases, download the patch file to your site’s codebase and add the path to the patch file to your composer.json file. See Composer-Patches: The Dependency You Never Knew You Needed for a tutorial on how to add a patch to your composer.json file The contents of merge request patch file will change as commits are pushed! This means that you will get the latest version of the code from an issue. So, it brings a security risk because any new commit to the issue’s branch will be automatically deployed to your site when composer runs. It's strongly recommended to lock the patch file versions on production sites. To do so you must download the patch file and use it in composer from a local directory. If you use the URL to the Gitlab MR directly, your codebase will change without warning, as people work on the merge request.
- 6. Drupal’s online documentation is © 2000-2024 by the individual contributors and can be used in accordance with the Creative Commons License, Attribution-ShareAlike 2.0. PHP code is distributed under the GNU General Public License. Drupal is a registered trademark of Dries Buytaert. You can still use git diff to generate patches, and attach with an issue comment in the usual way. Rather than generating an interdiff.txt file, you can link to GitLab’s Merge Request (MR) or Commit page to get the diff between two stages/commits. Help improve this page Page status: Needs work You can: Log in, click Edit, and edit this page Log in, click Discuss, update the Page status value, and suggest an improvement Log in and create a Documentation issue with your suggestion
- 7. Task 1: Interface with a stock price data feed
- 8. First Step Now that you have your local development environment set up, it’s time to actually run the program. Run server3.py and client3.py (in that order) and take a look at the output. You should notice two things: (1) The Ratio in the client output is always 1 (2) The price of each stock is always the same as its bid These are obviously wrong so your job is to fix them… Making changes in `client3.py` All the changes you have make to get the right output will be in the client3.py file inside the repository The changes you need to make will be in the following methods of the file • getDataPoint • getRatio • Main The changes for each method will be dissected on the next slide.
- 9. Making changes in `client3.py` - getDataPoint Method In this method, you'll have to make modifications to compute the right stock price. This means you have to change how `price` is computed by using the formula: (bid_price+ask_price) / 2. YOU DO NOT NEED TO CHANGE the return value as that is representational of the entire data point. You should end up with something like:
- 10. Making changes in client3.py – getRatio method Right now, this method just returns 1 all the time. To correct this, you must change the return value to the ratio of stock price_a to stock price_b note: that we’ve also added the condition of the case where in price_b could be zero, i.e. division by zero, in the rare chance that it might happen...
- 11. Making changes in client3.py - Main method Now that you've fixed the two other methods, it's just a matter of printing the correct values. For every iteration in the main method, you need to store the datapoints you get from the getDataPoint method so that you can properly call getRatio and print the right ratio. To review, we created a prices dictionary to store the stock prices. Think of a dictionary as a key-value store wherein you can specify a key and be able to retrieve a value. In our case, the key was the stock name and the value was the price. We then used this prices dictionary at the end to pass in the right values in the getRatio function.