Scrapy version. If used with -v it also prints Python, Twisted and Platform info, which is useful for bug reports. ## bench New in version 0.17. • Syntax: scrapy bench • Requires project: no Run a quick relevant). scrapy shell index.html will not work as one might expect (and this is by design, not a bug). Because shell favors HTTP URLs over File URIs, and index.html being syntactically similar to example leading or trailing whitespace in the option values will not work due to a bug in lxml [https://bugs.launchpad.net/lxml/+bug/1665241], which should be fixed in lxml 3.8 and above. ## Parameters: • response

versions, such as: • A build with other dependencies, such as Python 3.4 instead of Python 2.7. • A bug fix in the build process. • Some different optional dependencies, such as MKL versus ATLAS linkage names and versions to determine the latest one. This is important because new builds that contain bug fixes for the way a package is built may be added to a repository.| |depends|list of strings|A list patch. Patches typically contain bug fixes, so if you want to keep version 2.3 in your environment without updating to 2.4 or 3.0, but want to take advantage of any bug fixes, using 2.3.* in your environment

certificate is known to not work (websockets will fail). ## User interface components When opening bug reports or sending emails to the Jupyter mailing list, it is useful to know the names of different relevant. Unfortunately it’s not always easy to figure out what packages are relevant, but if there was a bug that’s already been fixed, it’s easy to upgrade and get on with what you wanted to do. ## Jupyter [https://github.com/jupyter/notebook/compare/v6.4.4...ccd9665571107e02a325a738b8baebd6532b2d3d] ## Bug fixes • Recover from failure to render mimetype #6181 [https://github.com/jupyter/notebook/pull/6181]

33/p2_1.jpg) On an unsuspecting Monday last July, the team I was working at the time received a bug report. The report claimed that our delete button wasn’t working in certain scenarios. In our case meant that our containers were failing to be destroyed. Three months and a tough journey later, this bug report had grown into a contribution to the go language. This talk is about how that happened, and 2af33/p9_1.jpg) Remove = Go's os.RemoveAll() Lets dive into the problem that came from the bug report. The problem was that long enough file paths could not be removed. What do I mean by long

details 38 2.2.2 Compatibility changes 47 2.2.3 Deprecated features 76 2.2.4 Improvements 76 2.2.5 Bug fixes 79 2.2.6 Contributors 85 2.3 TiDB Features 85 2.3.1 Data types, functions, and operators 86 TiDB Lightning reports an error when the space of TiFlash is insufficient #50324 @okJiang ## 2.2.5 Bug fixes ## TiDB - Fix the issue that auto analyze is triggered multiple times when there is no data developers contribute to new feature development, performance improvement, stability guarantee, and bug fixes. The following is the list of contributors in TiDB related repos: - pingcap/tidb - tikv/tikv

recipes, packages or command line flows • If something is breaking, it will be considered a bug and reverted • Bug fixes will not be considered breaking, recipes and packages relying on the incorrect behavior the path. • In Windows, Python 3 installation can fail installing the wrapt dependency because of a bug in pip. Information about this issue and workarounds is available here: https://github.com/GrahamD declaring self.cpp_info.libdirs as lib, the consumption of the package was broken. This was considered a bug in the build helper, as it should be as much deterministic as possible when building the same package

fixed while allowing the patch to be any number allows you to use your environment file to get any bug fixes while still maintaining consistency in your environment. For more information on package installation versions, such as: • A build with other dependencies, such as Python 3.4 instead of Python 2.7. • A bug fix in the build process. • Some different optional dependencies, such as MKL versus ATLAS linkage names and versions to determine the latest one. This is important because new builds that contain bug fixes for the way a package is built may be added to a repository.| |depends|list of strings|A list

versions, such as: • A build with other dependencies, such as Python 3.4 instead of Python 2.7. • A bug fix in the build process. • Some different optional dependencies, such as MKL versus ATLAS linkage names and versions to determine the latest one. This is important because new builds that contain bug fixes for the way a package is built may be added to a repository.| |depends|list of strings|A list patch. Patches typically contain bug fixes, so if you want to keep version 2.3 in your environment without updating to 2.4 or 3.0, but want to take advantage of any bug fixes, using 2.3.* in your environment

certificate is known to not work (websockets will fail). ## USER INTERFACE COMPONENTS When opening bug reports or sending emails to the Jupyter mailing list, it is useful to know the names of different relevant. Unfortunately it’s not always easy to figure out what packages are relevant, but if there was a bug that’s already been fixed, it’s easy to upgrade and get on with what you wanted to do. ### 4.1 Jupyter @maliubiao | @nsait-linaro | @takluyver | @Zsailer ##### 5.12 6.4.5 (Full Changelog) #### 5.12.1 Bug fixes • Recover from failure to render mimetype #6181 (@martinRenou) #### 5.12.2 Maintenance and

HTTP POST when resolving multipart request controller method arguments * fixed request mapping bug involving direct vs pattern path matches with HTTP methods * updated @RequestMapping and reference