Add ruby-actionview52 version 5.2.2 package.
Action View provides simple, battle-tested conventions and helpers for
building web pages.
This is for Ruby on Rails 5.2.
Add ruby-activejob52 version 5.2.2 package.
Active Job is a framework for declaring jobs and making them run on a
variety of queueing backends. These jobs can be everything from
regularly scheduled clean-ups, to billing charges, to
mailings. Anything that can be chopped up into small units of work and
run in parallel, really.
It also serves as the backend for Action Mailer's #deliver_later
functionality that makes it easy to turn any mailing into a job for
running later. That's one of the most common jobs in a modern web
application: Sending emails outside of the request-response cycle, so
the user doesn't have to wait on it.
The main point is to ensure that all Rails apps will have a job
infrastructure in place, even if it's in the form of an "immediate
runner". We can then have framework features and other gems build on
top of that, without having to worry about API differences between
Delayed Job and Resque. Picking your queuing backend becomes more of
an operational concern, then. And you'll be able to switch between
them without having to rewrite your jobs.
This is for Ruby on Rails 5.2.
Add ruby-activemodel52 version 5.2.2 package.
Active Model provides a known set of interfaces for usage in model classes.
They allow for Action Pack helpers to interact with non-ActiveRecord models,
for example. Active Model also helps building custom ORMs for use outside of
the Rails framework.
This is for Ruby on Rails 5.2.
Add ruby-activesupport52 version 5.2.2 package.
A toolkit of support libraries and Ruby core extensions extracted from
the Rails framework. Rich support for multibyte strings,
internationalization, time zones, and testing.
This is for Ruby on Rails 5.2.
1.16.0:
Added support for Ed448 host/client keys and certificates and rewrote Ed25519 support to use the PyCA implementation, reducing the dependency on libnacl and libsodium to only be needed to support the chacha20-poly1305 cipher.
Added support for PKCS-8 format Ed25519 and Ed448 private and public keys (in addition to the OpenSSH format previously supported).
Added support for multiple delimiters in SSHReader’s readuntil() function, causing it to return data as soon as any of the specified delimiters are matched.
Added the ability to register custom key handlers in the line editor which can modify the input line, extending the built-in editing functionality.
Added SSHSubprocessProtocol and SSHSubprocessTransport classes to provide compatibility with asyncio.SubprocessProtocol and asyncio.SubprocessTransport. Code which is designed to call BaseEventLoop.subprocess_shell() or BaseEventLoop.subprocess_exec() can be easily adapted to work against a remote process by calling SSHClientConnection.create_subprocess().
Added support for sending keepalive messages when the SSH connection is idle, with an option to automatically disconnect the connection if the remote system doesn’t respond to these keepalives.
Changed AsyncSSH to ignore errors when loading unsupported key types from the default file locations.
Changed the reuse_port option to only be available on Python releases which support it (3.4.4 and later).
Fixed an issue where MSG_IGNORE packets could sometimes be sent between MSG_NEWKEYS and MSG_EXT_INFO, which caused some SSH implementations to fail to properly parse the MSG_EXT_INFO.
Fixed a couple of errors in the handling of disconnects occurring prior to authentication completing.
Renamed “session_encoding” and “session_errors” arguments in asyncssh.create_server() to “encoding” and “errors”, to match the names used for these arguments in other AsyncSSH APIs. The old names are still supported for now, but they are marked as deprecated and will be removed in a future release.
19.1.0:
Backward-incompatible Changes
- Fixed a bug where deserialized objects with cache_hash=True could have incorrect hash code values.
This change breaks classes with cache_hash=True when a custom __setstate__ is present.
An exception will be thrown when applying the attrs annotation to such a class.
Changes
- Add is_callable, deep_iterable, and deep_mapping validators.
* is_callable: validates that a value is callable
* deep_iterable: Allows recursion down into an iterable,
applying another validator to every member in the iterable
as well as applying an optional validator to the iterable itself.
* deep_mapping: Allows recursion down into the items in a mapping object,
applying a key validator and a value validator to the key and value in every item.
Also applies an optional validator to the mapping object itself.
You can find them in the attr.validators package.
- Fixed stub files to prevent errors raised by mypy's disallow_any_generics = True option.
- Attributes with init=False now can follow after kw_only=True attributes.
- attrs now has first class support for defining exception classes.
If you define a class using @attr.s(auto_exc=True) and subclass an exception, the class will behave like a well-behaved exception class including an appropriate __str__ method, and all attributes additionally available in an args attribute.
- Clarified documentation for hashing to warn that hashable objects should be deeply immutable (in their usage, even if this is not enforced).
4.3.10:
- Fixed Windows incompatibilities
- Fixed relative import sorting bug
- Fixed "no_lines_before" to also be respected from previous empty sections.
- Fixed slow-down introduced by finders mechanism by adding a LRU cache
- Fixed issue 842 default encoding not-set in Python2
- Restored Windows automated testing
- Added Mac automated testing
ReText is a text editor for various markup languages (such as Markdown
and reStructuredText). It gives you the power to control all output
formatting. The files it works with are plain text files, however it
can export to PDF, HTML and other formats, and can display content in
WYSIWYG form.
Changes between version 4.2.1 and 4.2.2:
Improvements:
Quicker connection handshake for clients which use CAP and/or SASL.
With "TOPIC #chan" and "MODE #chan +b" (and +e/+I) you can see who set the topic and bans/exempts/invex. The default is to only show the nick of the person who set the item. This can be changed (not the default) by setting:
set { topic-setter nick-user-host; };
set { ban-setter nick-user-host; };
The 'set by' and 'set at' information for +beI lists are now synchronized when servers link. You still see the MODE originating from the server, however when the banlist is queried you will now be able to see the original nick and time of the bansetter rather than serv.er.name. If you want the OLD behavior you can use: set { ban-setter-sync no; };
The default maximum topic length has been increased from 307 to 360.
You can now set more custom limits. The default settings are shown below:
set {
topic-length 360; /* maximum: 360 */
away-length 307; /* maximum: 360 */
quit-length 307; /* maximum: 395 */
kick-length 307; /* maximum: 360 */
};
The message sent to users upon *LINE can now be adjusted completely via set::reject-message::kline and set::reject-message::gline.
New set::anti-flood::max-concurrent-conversations which configures the maximum number of conversations a user can have with other users at the same time.
Until now this was hardcoded at limiting /MSG and /INVITE to 20 different users in a 15 second period. The new default is 10 users, which serves as a protection measure against spambots.
New set::max-targets-per-command which configures the maximum number of targets accepted for a command, such as 4 to allow e.g. /MSG nick1,nick2,nick3,nick4 hi.
Also changed the following defaults (previously hardcoded):
PRIVMSG from 20 to 4 targets, to counter /amsg spam
NOTICE from 20 to 1 target, to counter /anotice spam
KICK from 1 to 4 targets, to make it easier for channel operators to quickly kick a large amount of spambots
Added INVITE and KNOCK flood protection (command rate limiting):
set::anti-flood::invite-flood now defaults to 4 per 60 seconds (previously the effective limit was 1 invite per 6 seconds).
set::anti-flood::knock-flood now defaults to 4 per 120 seconds.
New set::outdated-tls-policy which describes what to do with clients that use outdated SSL/TLS protocols (eg: TLSv1.0) and ciphers.
The default settings are to warn in all cases: users connecting, opers /OPER'ing up and servers linking in. The user will see a message telling them to upgrade their IRC client.
This should help with migrating such users, since in the future, say one or two years from now, we would want to change the default to only allow TSLv1.2+ with ciphers that provide Forward Secrecy. Instead of rejecting clients without any error message, this provides a way to warn them and give them some time to upgrade their outdated IRC client.
Major issues fixed:
Crash issue in the 'websocket' module.
Minor issues fixed:
The advertised "link-security" was incorrectly downgraded from level 2 to 1 if spkifp was used as an authentication method.
In case of a crash, the ./unrealircd backtrace script was not working correctly in non-English environments, leading to less accurate bug reports.
Various crashes if a server receives incorrect commands from a trusted linked server.
A number of memory leaks on REHASH (about 1K).
SASL was not working post-registration, eg: when services link back in. This is now fixed in UnrealIRCd, but may require a services update as well.
Changed:
The noctcp user mode (+T) will now only block CTCP's and not CTCP REPLIES. Also, IRCOps can bypass user mode +T restrictions.
The server will warn if your ulines { } are matching UnrealIRCd servers.
The m_whox module now contains various features that m_who already had.
Also, m_whox will try to convert classic UnrealIRCd WHO requests such as "WHO +i 127.0.0.1" to whox style "WHO 127.0.0.1 i".
Unfortunately auto-converting WHO requests is not always possible. When in doubt the WHOX syntax is assumed. Users are thus (still) encouraged to use the whox style when m_whox is loaded.
For module coders:
New hook HOOKTYPE_WELCOME (aClient *acptr, int after_numeric): allows you to send a message at very specific places during the initial welcome.
New Isupport functions: IsupportSet, IsupportSetFmt and IsupportDelByName.
The M_ANNOUNCE flag in the command add functions should no longer be used as CMDS= is removed. Please update your module.
New "SJSBY" in PROTOCTL, which is used in SJOIN to sync extra data. See the last part of the SJOIN documentation.
For a command with 2 arguments, eg "PRIVMSG #a :txt", parv[1] is "#a", parv[2] is "txt" and parv[3] is NULL. Any arguments beyond that, such as parv[4] should not be accessed. To help module coders with detecting such bugs we now poison unused parv[] elements that should never be accessed. Note that without this poison your code will also crash, now it just crashes more consistently.
IRC protocol:
This section is intended for client coders and people interested in IRC protocol technicalities
Many changes in the tokens used in numeric 005 (RPL_ISUPPORT):
Removed CMDS= because this was an unnecessary abstraction and it was not picked up by any other IRCd.
The tokens KNOCK MAP USERIP have been added (moved from CMDS=..)
STARTTLS is no longer advertised in 005 since doing so would be too late. Also, STARTTLS is not the preferred method of using SSL/TLS.
Added TARGMAX= to communicate set::max-targets-per-command limits.
Removed the MAXTARGETS= token because TARGMAX= replaces it.
Added DEAF=d to signal what user mode is used for "deaf"
Added QUITLEN to communicate the set::quit-length setting (after all, why communicate length for KICK but not for QUIT?)
The 005 tokens are now sorted alphabetically
When hitting the TARGMAX limit (set::max-targets-per-command), for example with "/MSG k001,k002,k003,k004,k005 hi", you will see:
:server 407 me k005 :Too many targets. The maximum is 4 for PRIVMSG.
When hitting the set::anti-flood::max-concurrent-conversations limit (so not per command, but per time frame), you will see:
:server 439 me k011 :Message target change too fast. Please wait 7 seconds
When hitting the set::anti-flood::invite-flood limit you will get:
:server 263 me INVITE :Flooding detected. Please wait a while and try again.
When hitting the set::anti-flood::knock-flood limit you will get:
:server 480 me :Cannot knock on #channel (You are KNOCK flooding)
Not a protocol change. But when a server returns from a netsplit and syncs modes such as: :server MODE #chan +b this!is@an.old.ban
Then later on you can query the banlist (MODE #chan b) and you may see the actual original setter and timestamp of the ban. So if a user wishes to see the banlist then IRC clients are encouraged to actively query the banlist before displaying it. Fortunately most clients do this.
If the set::topic-setter or set::ban-setter are set to nick-user-host then the "added by" field in numerics that show these entries will contain nick!user@host instead of nick, eg:
:server 367 me #channel this!is@some.banbansetter!user@some.host 1549461765
7.6.10:
* Eliminate 'my_chunk_ptr-AO_initial_heap out of bounds' cppcheck warning
* Fix 'AO_*_TS_T is not defined' compiler warnings (GCC-8)
* Fix 'duplicate symbol' error for test_malloc/stack with static libs (OS X)
* Workaround 'argument to function assert is always 1' cppcheck warnings
v1.9.0:
Description
Fixed Tab indenting - when tabs indenting enabled, they are used universally. Also, tab size customizable: 8-space tabs would mean each tab is treated as 8 spaces.
Accurate line wrapping - Layout always wraps when line length exceed specified column, unless wrapping would not reduce line length.
Improved Template handling in HTML - Go, Django, Handlebars, ERB/EJS/ASP, PHP (still only handlebars indenting)
Improved Template handling in Javascript - ERB/EJS/ASP, PHP (no indenting, no Django or Handlebars due to potential syntax conflicts for curly braces)
Fixed indenting of mustache inverted conditionals
Fixed indenting for HTML tags with option end tags
https://github.com/beautify-web/js-beautify/compare/v1.8.9...v1.9.0
Closed Issues
Incorrect indentation of ^ inverted section tags in Handlebars/Mustache code
PHP In HTML Attributes
DeanEdward python unpacker offset problem
CLI on Windows doesn't accept -f - for stdin?
HTML type attribute breaks JavaScript beautification?
Use of global MODE before declaration caused uglify problem
When building html tags using Mustache variables, extra whitespace is added after opening arrow
<script type="text/html">isnot abled to be beautified
_get_full_indent undefined
Website "autodetect" setting doesn't distinguish css vs javascript
Add setting to keep HTML tag text content unformatted or ignore custom delimiters
HTML auto formatting using spaces instead of tabs
Unclosed single quote in php tag causes formatting changes which break php code
Using tabs when wrapping attributes and wrapping if needed
HTML --wrap-attributes doesn't respect --wrap-line-length
Bad indent level(HTML)
js-beautify produces invalid code for variables with Unicode escape sequences
support vuejs
Go templates in HTML
Better behavior for javascript --wrap-line-length
Upstream changes:
Changes for version 1.55 - 2019-02-25
Improve AppVeyor tests for older Perls (Thanks Roy Ivy)
Check for Test::More 0.94 and skip tests if not installed where done_testing() is used (Thanks Roy Ivy).
Improve workaround for broken Win32 File::Temp taint failure (Thanks Roy Ivy).
Skip/todo tests which fail under Devel::Cover (Thanks Roy Ivy)
Add checks and skip_all checks for non-core test modules (Thanks Roy Ivy)
v3.0.0
* Support for Draft 6 and Draft 7
* Draft 7 is now the default
* New TypeChecker object for more complex type definitions (and overrides)
* Falling back to isodate for the date-time format checker is no longer
attempted, in accordance with the specification
Pyrsistent is a number of persistent collections (by some referred to as
functional data structures). Persistent in the sense that they are immutable.
All methods on a data structure that would normally mutate it instead return a
new copy of the structure containing the requested updates. The original
structure is left untouched.
This will simplify the reasoning about what a program does since no hidden side
effects ever can take place to these data structures. You can rest assured that
the object you hold a reference to will remain the same throughout its lifetime
and need not worry that somewhere five stack levels below you in the darkest
corner of your application someone has decided to remove that element that you
expected to be there.
Pyrsistent is influenced by persistent data structures such as those found in
the standard library of Clojure. The data structures are designed to share
common elements through path copying. It aims at taking these concepts and make
them as pythonic as possible so that they can be easily integrated into any
python program without hassle.
