uim: PLIST fix #153
Open
uim: PLIST fix #153
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changes not found.
2.3.0 (2024-12-22) ================== Features -------- - Added ``HTTPResponse.shutdown()`` to stop any ongoing or future reads for a specific response. It calls ``shutdown(SHUT_RD)`` on the underlying socket. This feature was `sponsored by LaunchDarkly <https://opencollective.com/urllib3/contributions/815307>`__. - Added support for JavaScript Promise Integration on Emscripten. This enables more efficient WebAssembly requests and streaming, and makes it possible to use in Node.js if you launch it as ``node --experimental-wasm-stack-switching``. - Added the ``proxy_is_tunneling`` property to ``HTTPConnection`` and ``HTTPSConnection``. - Added pickling support to ``NewConnectionError`` and ``NameResolutionError``. Bugfixes -------- - Fixed an issue in debug logs where the HTTP version was rendering as "HTTP/11" instead of "HTTP/1.1". Deprecations and Removals ------------------------- - Removed support for Python 3.8.
=============== Version 4.3.0.4 =============== Bug corrected: * WebUI errors in 4.3.0.4 on iPad Air (and Browser with low resolution) #3057 =============== Version 4.3.0.4 =============== Continuous integration and documentation: * Pin Python version in Ubuntu image to 3.12 =============== Version 4.3.0.3 =============== Continuous integration and documentation: * Pin Alpine image to 3.20 (3.21 is not compliant with Netifaces) Related to #3053 =============== Version 4.3.0.2 =============== Enhancements: * Revert "Replace netifaces by netifaces-plus" #3053 because it break build on Alpine Image =============== Version 4.3.0.1 =============== Enhancements: * Replace netifaces by netifaces-plus #3053 Bug corrected: * CONTAINERS section missing in 4.3.0 WebUI #3052
Fix two seg faults Reported by: portscout
v25.6.0 ======= Features -------- - Avoid logging a warning when config does not specify a backend. (#682)
Add missing version in pyproject.toml. Seems required with newer maturin. Bump PKGREVISION.
Patch from upstream git repository.
v0.8.3 - fix: variant `XXH3_128bits_withSecretandSeed()` could produce an invalid result in some specific set of conditions - cli: vector extension detected at runtime on x86/x64, enabled by default - cli: new commands `--filelist` and `--files-from` - cli: XXH3 64-bits GNU format can now be generated and checked (command `-H3`) - portability: LoongArch SX SIMD extension - portability: can build on AIX, suggeste
3.10.13 - Fix compatibility with maturin introducing a breaking change in 1.8.0 and specify a fixed version of maturin. Projects relying on any previous version being buildable from source by end users (via PEP 517) must upgrade to at least this version.
Version 5.7.3 Fixes a regression in version 5.7.3. Fixes * fixed a regression in version 5.7.2 that `tempfile` was not patched after pause/resume (POSIX only, see [#1098](../../issues/1098)) * added workaround for a recursion occurring if using pytest under Windows and Python >= 3.12 (see [#1096](../../issues/1096)) Infrastructure * run pytest-specific tests for all supported Python versions * pytest is only supported for versions >= 6.2.5, earlier version do not work in Python >= 3.10 due to a pytest issue - adapted tests and documentation
2.7.1 Bug Fixes Wait for the IOLoop to be stopped before attempting to close it.
0.303 doesn't install any files.
# downlit 0.4.4 * Use simpler parsing algorithm for R 4.0, which avoids crash with certain UTF-8 characters (#189). # downlit 0.4.3 * Fix for upcoming R-devel (NetBSD#169). # downlit 0.4.2 * `highlight()` no longer errors if a package imputed to have been attached isn't installed. * Correctly link `requireNamespace(MASS)` (NetBSD#151). # downlit 0.4.1 ## Syntax highlighting * Supports new base pipe `|>` syntax (NetBSD#126). * Every line get its own `<span>` to match pandoc (NetBSD#122). * Multi-line tokens (e.g. strings) now get a `<span>` per line (NetBSD#139). * Very long strings or other tokens are no longer truncated (@dmurdoch, NetBSD#128). ## Auto-linkg * Function calls (in inline and code blocks) will no longer to non-function topics (NetBSD#135). * Re-exports detection no longer relies on name of `.Rd` file (NetBSD#134). * Link to correct topic with `::()` and `utils::help()` (@IndrajeetPatil, NetBSD#131). * Generate correct link for Bioconductor vignettes (@zeehio, NetBSD#145)
Upstream changes: https://github.com/sparklemotion/nokogiri/releases/tag/v1.18.1 https://github.com/sparklemotion/nokogiri/releases/tag/v1.18.0 https://github.com/sparklemotion/nokogiri/releases/tag/v1.17.2 https://github.com/sparklemotion/nokogiri/releases/tag/v1.17.1 https://github.com/sparklemotion/nokogiri/releases/tag/v1.17.0 v1.18.1 / 2024-12-29 Fixed * [CRuby] XML::SAX::ParserContext keeps a reference to the input to avoid a potential use-after-free issue that's existed since v1.4.0 (2009). (#3395) @flavorjones v1.18.0 / 2024-12-25 Notable Changes Ruby This release introduces native gem support for Ruby 3.4. This release ends support for Ruby 3.0, for which upstream support ended 2024-04-23. This release ships separate precompiled GNU and Musl gems for all linux platforms. Previously both GNU and Musl target systems could use and install the same gem, e.g., the platform gem for x86_64-linux. Now, however, the precompiled gem platforms would be x86_64-linux-gnu and x86_64-linux-musl. So long as you're on bundler >= 2.5.6 this should be seamless other than perhaps needing to update the platforms in your "Gemfile.lock". This release drops precompiled native platform gems for x86-linux and x86-mingw32. These platforms are still supported. Users on these platforms must install the "ruby platform" gem which requires a compiler toolchain. See Installing the ruby platform gem in the installation docs. (#3369, #3081) Improved * [CRuby] CSS and XPath queries are faster now that Node#xpath, Node#css, and related functions are using a faster XPathContext initialization process. We benchmarked a 1.9x improvement for a 6kb file. Big thanks to @nwellnhof for helping with this one. (#3378, superseded by #3389) @flavorjones v1.17.2 / 2024-12-12 Fixed * [JRuby] Fixed an issue where Node#dup when called with the new_parent_doc parameter was not decorating the node with the document's Node decorators. [#3372] @flavorjones v1.17.1 / 2024-12-10 Fixed * Fixed a potential segfault when using Node#dup and DocumentFragment#dup. [# 3359] @byroot @flavorjones * Node#dup and Node#clone now correctly decorate the new node with the document's Node decorators. [#3363] @flavorjones v1.17.0 / 2024-12-08 Dependencies * [CRuby] Vendored libxml2 is updated to v2.13.5. @flavorjones * [CRuby] Vendored libxslt is updated to v1.1.42. @flavorjones * [CRuby] Minimum supported version of libxml2 raised to v2.9.2 (released 2014-10-16) from v2.6.21. [#3232, #3287] @flavorjones * [JRuby] Minimum supported version of Java raised to 8 (released 2014-03-18) from 7. [#3134] @flavorjones * [CRuby] Update to rake-compiler-dock v1.5.1 for building precompiled native gems. [#3216] @flavorjones Notable changes SAX Parsers The XML and HTML4 SAX parsers have received a lot of attention in this release, and we've fixed multiple long-standing bugs with encoding and entity handling. In addition, libxml2 v2.13 has also made some underlying fixes and improvements to encoding and entity handling. We're shipping these fixes in a minor release because we firmly believe the resulting behavior is correct and standards-compliant, however applications that have been depending on the buggy behavior may be impacted. If your application relies on the SAX parsers, and in particular if you're SAX-parsing documents with parsed entities or incorrect encoding declarations, please read the changelog below carefully. Fragment parsing Document fragment parsing has been improved, particularly with respect to handling malformed fragments or fragments with implicit namespace prefixes. Namespace reconciliation still isn't where we want it to be, but it's an improvement. HTML5 fragment parsing now allows the context node to be specified as a context: keyword argument to the HTML5::DocumentFragment.parse and .new methods, which should allow for more flexible sanitization and future support for the draft HTML Sanitizer API in downstream libraries. Error handling In scenarios where multiple errors could be reported by the underlying parser, the errors will be aggregated into a single Nokogiri::XML::SyntaxError that is raised. Previously only the final error reported by libxml2 was raised (which was often misleading if it was only a warning and not the fatal error). Schema validation We've resolved many long-standing bugs in the various schema classes, validation methods, and their error reporting. Behavior is now consistent across schema types and input types, as well as parser backends (Xerces and libxml2). Keyword arguments The following methods now accept keyword arguments in addition to positional arguments, and use ... parameter forwarding when possible: HTML4(), HTML4.fragment, HTML4.parse, HTML4::Document.parse, HTML4::DocumentFragment#initialize, HTML4::DocumentFragment.parse, HTML5(), HTML5.fragment, HTML5.parse, HTML5::Document.parse, HTML5::Document.read_io, HTML5::Document.read_memory, HTML5::DocumentFragment#initialize, HTML5::DocumentFragment.parse, XML(), XML.fragment, XML.parse, XML::Document.parse, XML::DocumentFragment#initialize, XML::DocumentFragment.parse, XML::Node#canonicalize, XML::Node.parse, XML::Reader(), XML::RelaxNG(), XML::RelaxNG.new, XML::RelaxNG.read_memory, XML::SAX::PushParser#initialize, XML::Schema(), XML::Schema.new, XML::Schema.read_memory, and XSLT(). Special thanks to those contributors who participated in the RubyConf 2024 Hack Day to work on #3323 to help modernize Nokogiri by adding keyword arguments and using parameter forwarding in many methods, and expanding some of the documentation! We intend to continue adding keyword argument support to more methods. #3323 #3324 #3326 #3327 #3329 #3330 #3332 #3333 #3334 #3335 #3336 # 3342 #3355 #3356 @infews @matiasow @MattJones @mononoken @openbl @flavorjones Added * Introduce support for a new SAX callback XML::SAX::Document#reference, which is called to report some parsed XML entities when XML::SAX::ParserContext#replace_entities is set to the default value false. This is necessary functionality for some applications that were previously relying on incorrect entity error reporting which has been fixed (see below). For more information, read the docs for Nokogiri::XML::SAX::Document. [#1926] @flavorjones * XML::SAX::Parser#parse_memory and #parse_file now accept an optional encoding argument. When not provided, the parser will fall back to the encoding passed to the initializer, and then fall back to autodetection. [# 3288] @flavorjones * XML::SAX::ParserContext.memory now accepts an optional encoding argument. When not provided, the encoding will be autodetected. [#3288] @flavorjones * New readonly attributes XML::DocumentFragment#parse_options and HTML4::DocumentFragment#parse_options return the options used to parse the document fragment. @flavorjones * New method XML::Reader.new is the primary constructor to which XML::Reader () forwards. Both methods now take url:, encoding:, and options: kwargs in addition to the previous calling convention of passing positional parameters. #3326 @infews @flavorjones * [CRuby] The HTML5 parse methods accept a :parse_noscript_content_as_text keyword argument which will emulate the parsing behavior of a browser which has scripting enabled. [#3178, #3231] @stevecheckoway * [CRuby] HTML5::DocumentFragment.parse and .new accept a :context keyword argument that is the parse context node or element name. Previously this could only be passed in as a positional argument to .new and not at all to .parse. @flavorjones * [CRuby] Nokogiri::HTML5::Builder is similar to HTML4::Builder but returns an HTML5::Document. [#3119] @flavorjones * [CRuby] Attributes in an HTML5 document can be serialized individually, something that has always been supported by the HTML4 serializer. [#3125, # 3127] @flavorjones * [CRuby] Introduce a compile-time option, --disable-xml2-legacy, to remove from libxml2 its dependencies on zlib and liblzma and disable implicit HTTP network requests. These all remain enabled by default, and are present in the precompiled native gems. This option is a precursor for removing these libraries in a future major release, but may be interesting for the security-minded who do not need features like automatic decompression and would like to remove these dependencies. You can read more and give feedback on these plans in #3168. [#3247] @flavorjones * [CRuby] If errors are returned from schema validation, a new attribute SyntaxError#path will contain the XPath path of the node that caused the validation failure. [#3316] @ryanong Improved * Documentation has been improved for XML::RelaxNG, XML::Schema, XML::Reader, HTML5, HTML5::Document, HTML5::DocumentFragment, HTML4::Document, HTML4::DocumentFragment, XML, XML::Document, XML::DocumentFragment. #3355 @flavorjones * Documentation has been improved for CSS.xpath_for. [#3224] @flavorjones * Documentation for the SAX parsing classes has been greatly improved, including encoding overrides and the complex entity-handling behavior. [# 3265] @flavorjones * XML::Schema#read_memory and XML::RelaxNG#read_memory are now Ruby methods that call #from_document. Previously these were native functions, but they were buggy on both CRuby and JRuby (but worse on JRuby) and so this is now useful, comparable in performance, and simpler code that is easier to maintain. [#2113, #2115] @flavorjones * XML::SAX::ParserContext.io's encoding argument is now optional, and can now be an Encoding or an encoding name. When not provided will default to autodetecting the encoding. [#3288] @flavorjones * [CRuby] The update to libxml v2.13 improves "in context" fragment parsing recovery. We removed our hacky workaround for recovery that led to silently-degraded functionality when parsing fragments with parse errors. Specifically, malformed XML fragments that used implicit namespace prefixes will now "link up" to the namespaces in the parent document or node, where previously they did not. [#2092] @flavorjones * [CRuby] When multiple errors could be detected by the parser and there's no obvious document to save them in (for example, when parsing a document with the recovery parse option turned off), the libxml2 errors are aggregated into a single Nokogiri::XML::SyntaxError. Previously, only the last error recorded by libxml2 was raised, which might be misleading if it's merely a warning and not the fatal error preventing the operation. [#2562] @flavorjones * [CRuby] The SAX parser context and handler implementation has been simplified and now takes advantage of some of libxml2's default SAX handlers for entities and DTD management. [#3265] @flavorjones * [CRuby] When compiling packaged libraries from source, allow users' AR and LD environment variables to set the archiver and linker commands, respectively. This augments the existing CC environment variable to set the compiler command. [#3165] @ziggythehamster * [CRuby] When building from source on MacOS, environment variables AR and RANLIB are now respected when set instead of being overridden to /usr/bin/ {ar,ranlib} (which is still the default). [#3338] @joshheinrichs-shopify Fixed * Node#clone, NodeSet#clone, and *::Document#clone all properly copy the metaclass of the original as expected. Previously, #clone had been aliased to #dup for these classes (since v1.3.0 in 2009). [#316, #3117] @flavorjones * CSS queries for pseudo-selectors that cannot be translated into XPath expressions now raise a more descriptive Nokogiri::CSS::SyntaxError when they are parsed. Previously, an invalid XPath expression was evaluated and a hard-to-understand XPath error was raised by the query engine. [#3193] @flavorjones * Schema#validate returns errors on empty and malformed files. Previously, it would return errors on empty/malformed Documents, but not when reading from files. [#642] @flavorjones * XML::Builder is now consistent with how it sets block scope. Previously, missing methods with blocks on dynamically-created nodes were always handled by invoking instance_eval(&block) on the Builder, even when the Builder was yielding self for all other missing methods with blocks. [#1041 ] @flavorjones * HTML4::DocumentFragment.parse accepts IO input. Previously, it required a string and would raise a TypeError when passed an IO. [#2069] @sharvy * [CRuby] libgumbo (the HTML5 parser) treats reaching max-depth as EOF. This addresses a class of issues when the parser is interrupted in this way. [# 3121] @stevecheckoway * [CRuby] Update node GC lifecycle to avoid a potential memory leak with fragments in libxml 2.13.0 caused by changes in xmlAddChild. [#3156] @flavorjones * [CRuby] libgumbo correctly prints nonstandard element names in error messages. [#3219] @stevecheckoway * [CRuby] External entity references no long cause the SAX parser to register errors. [#1926] @flavorjones * [JRuby] Fixed entity reference serialization, which rendered both the reference and the replacement text. Incredibly nobody noticed this bug for over a decade. [#3272] @flavorjones * [JRuby] Fixed some bugs in how Node#attributes handles attributes with namespaces. [#2677, #2679] @flavorjones * [JRuby] Fix Schema#validate to only return the most recent Document's errors. Previously, if multiple documents were validated, this method returned the accumulated errors of all previous documents. [#1282] @flavorjones * [JRuby] Fix Schema#validate to not clobber the @errors instance variable. [ #1282] @flavorjones * [JRuby] Empty documents fail schema validation as they should. [#783] @flavorjones * [JRuby] SAX parsing now respects the #replace_entities attribute, which defaults to false. Previously this flag defaulted to true and was completely ignored. [#614] @flavorjones * [JRuby] The SAX callback Document#start_element_namespace received a blank string for the URI when a namespace was not present. It now receives nil (as does the CRuby impl). [#3265] @flavorjones * [JRuby] Reader#outer_xml and #inner_xml encode entities properly. [#1523] @flavorjones Changed * [CRuby] Nokogiri::XML::CData.new no longer accepts nil as the content argument, making CData behave like other character data classes (like Comment and Text). This change was necessitated by behavioral changes in libxml2 v2.13.0. If you wish to create an empty CDATA node, pass an empty string. [#3156] @flavorjones * Internals: + The internal CSS::XPathVisitor class now accepts the xpath prefix and the context namespaces as constructor arguments. The prefix: and ns: keyword arguments to CSS.xpath_for cannot be specified if the visitor: keyword argument is also used. CSS::XPathVisitor now exposes #builtins, #doctype, #prefix, and #namespaces attributes. [#3225] @flavorjones + The internal CSS selector cache has been extracted into a distinct class, CSS::SelectorCache. Previously it was part of the CSS::Parser class. [#3226] @flavorjones + The internal Gumbo.parse and Gumbo.fragment methods now take keyword arguments instead of positional arguments. [#3199] @flavorjones Deprecated * The undocumented and unused method Nokogiri::CSS.parse is now deprecated and will generate a warning. The AST returned by this method is private and subject to change and removal in future versions of Nokogiri. This method will be removed in a future version of Nokogiri. * Passing an options hash to CSS.xpath_for is now deprecated and will generate a warning. Use keyword arguments instead. This will become an error in a future version of Nokogiri. * Passing libxml2 encoding IDs to SAX::ParserContext methods is now deprecated and will generate a warning. The use of SAX::Parser::ENCODINGS is also deprecated. Use Encoding objects or encoding names instead.
# gargle 1.5.2 * Fixed a bug in an internal helper that validates input specifying a service account. The helper targets a common mistake where the JSON for an OAuth client is provided to an argument that is meant for a service account (#270). # gargle 1.5.1 * Completed some overlooked, unfinished work around the OAuth "app" to "client" transition that affected out-of-bound auth (#263, #264). * The `secret_*()` functions are more discoverable via documentation.
(missed yesterday)
feat: print fixed rules count #1708
fix: move unused suppressions to config crate #1624
fix: allow malformed pattern to be dumped as tree #804
fix: fix files not recognize in lsp #1691
fix: fix crash when internal node has no child #1688
feat: use mutable self in Printer trait 5e3835a
feat: reduce binary size by remove Printer polymorphism 8b735cf
feat: resolve rule id for ScanResult 9a7f3cc
Railties -- Gluing the Engine to the Rails Railties is responsible for gluing all frameworks together. Overall, it: * handles the bootstrapping process for a Rails application; * manages the +rails+ command line interface; * and provides the Rails generators core. This is for Ruby on Rails 8.0.
Active Storage Active Storage makes it simple to upload and reference files in cloud services like [Amazon S3](https://aws.amazon.com/s3/), [Google Cloud Storage](https://cloud.google.com/storage/docs/), or [Microsoft Azure Storage](https://azure.microsoft.com/en-us/services/storage/), and attach those files to Active Records. Supports having one main service and mirrors in other services for redundancy. It also provides a disk service for testing or local deployments, but the focus is on cloud storage. Files can be uploaded from the server to the cloud or directly from the client to the cloud. Image files can furthermore be transformed using on-demand variants for quality, aspect ratio, size, or any other [MiniMagick](https://github.com/minimagick/minimagick) or [Vips](https://www.rubydoc.info/gems/ruby-vips/Vips/Image) supported transformation. This is for Ruby on Rails 8.0.
Action Mailer -- Easy email delivery and testing Action Mailer is a framework for designing email service layers. These layers are used to consolidate code for sending out forgotten passwords, welcome wishes on signup, invoices for billing, and any other use case that requires a written notification to either a person or another system. Action Mailer is in essence a wrapper around Action Controller and the Mail gem. It provides a way to make emails using templates in the same way that Action Controller renders views using templates. Additionally, an Action Mailer class can be used to process incoming email, such as allowing a blog to accept new posts from an email (which could even have been sent from a phone). This is for Ruby on Rails 8.0.
Action Mailbox Action Mailbox routes incoming emails to controller-like mailboxes for processing in Rails. It ships with ingresses for Mailgun, Mandrill, Postmark, and SendGrid. You can also handle inbound mails directly via the built-in Exim, Postfix, and Qmail ingresses. The inbound emails are turned into `InboundEmail` records using Active Record and feature lifecycle tracking, storage of the original email on cloud storage via Active Storage, and responsible data handling with on-by-default incineration. These inbound emails are routed asynchronously using Active Job to one or several dedicated mailboxes, which are capable of interacting directly with the rest of your domain model. This is for Ruby on Rails 8.0.
Action Text Action Text brings rich text content and editing to Rails. It includes the [Trix editor](https://trix-editor.org) that handles everything from formatting to links to quotes to lists to embedded images and galleries. The rich text content generated by the Trix editor is saved in its own RichText model that's associated with any existing Active Record model in the application. Any embedded images (or other attachments) are automatically stored using Active Storage and associated with the included RichText model. This is for Ruby on Rails 8.0.
Ruby on Rails Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern. This is meta gem package for Ruby on Rails 8.0.
netbsd-srcmastr
force-pushed
the
trunk
branch
from
d20f2e4 to
c5df823
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
inputmethod/uim: fix for make package failure if gtk2 is disabled.