Hyperframe

------------------

**Bugfixes**

- Fixed AltSvc stream association, which was incorrectly set to ``'both'``:
should have been ``'either'``.
- Fixed a bug where stream IDs on received frames were allowed to be 32-bit,
instead of 31-bit.
- Fixed a bug with frames that had the ``PADDING`` flag set but zero-length
padding, whose flow-controlled length was calculated wrongly.
- Miscellaneous performance improvements to serialization and parsing logic.

------------------

**Bugfixes**

- Fixed bug with the repr of ``AltSvcFrame``, where building it could throw
exceptions if the frame had been received from the network.

------------------

**Backwards Incompatible API Changes**

- Updated old ALTSVC frame definition to match the newly specified RFC 7838.
- Remove BLOCKED frame, which was never actually specified.
- Removed previously deprecated ``SettingsFrame.SETTINGS_MAX_FRAME_SIZE`` and
``SettingsFrame.SETTINGS_MAX_HEADER_LIST_SIZE``.

------------------

**API Changes (Backward Compatible)**

- Invalid PING frame bodies now raise ``InvalidFrameError``, not
``ValueError``. Note that ``InvalidFrameError`` is a ``ValueError`` subclass.
- Invalid RST_STREAM frame bodies now raise ``InvalidFramError``, not
``ValueError``. Note that ``InvalidFrameError`` is a ``ValueError`` subclass.
- Canonicalized the names of ``SettingsFrame.SETTINGS_MAX_FRAME_SIZE`` and
``SettingsFrame.SETTINGS_MAX_HEADER_LIST_SIZE`` to match their peers, by
adding new properties ``SettingsFrame.MAX_FRAME_SIZE`` and
``SettingsFrame.SETTINGS_MAX_HEADER_LIST_SIZE``. The old names are still
present, but will be deprecated in 4.0.0.

**Bugfixes**

- The change in ``3.1.0`` that ensured that ``InvalidFrameError`` would be
thrown did not affect certain invalid values in ALT_SVC frames. This has been
fixed: ``ValueError`` will no longer be thrown from invalid ALT_SVC bodies.

------------------

**Bugfixes**

- Correctly error when receiving Ping frames that have insufficient data.

------------------

**API Changes**

- Added new ``InvalidFrameError`` that is thrown instead of ``struct.error``
when parsing a frame.

**Bugfixes**

- Fixed error when trying to serialize frames that use Priority information
with the defaults for that information.
- Fixed errors when displaying the repr of frames with non-printable bodies.