This library has been running in a production codebase for a while and
can be considered stable.
There is a minor breaking change between this version and the previous
0.1.0 in that the `ValidationError` enum has gained additional variants.
After upgrading the base64 library, tests were failing because the new
default of the library is to disallow trailing bits in JWTs.
Some JWT provider implementations do however use this "forgiving"
version of base64-encoding, hence it is required for token validation.
This adds a base64::Config with the appropriate settings and also
chains base64-errors separately from other token errors.
For some reason that I can not be bothered to debug this mode will
only work correctly if initialised from inside this hook function (or
manually, after startup).
Adds a workaround for commercialhaskell/intero#569 by adding a
function that disables the offending GHCi flag in the Intero REPL, and
advising the `intero-repl` and `intero-repl-load` commands to always
execute it.
I did not manage to locate a common entrypoint to the REPL, but it's
probably not worth spending more time on as this will be fixed
properly in a future GHC release.
This is the first in a series of commits for refactoring my
configuration to make use of jwiegley's use-package.
In the previous layout of the configuration there were some questions
around what settings go into which file, but in the end it is all just
related to which packages are being configured (besides settings
related to global Emacs behaviour).
This commit introduces use-package forms for all currently used
packages (which are still installed via Nix, not via package.el) but
does not yet clean up the rest of the configuration in a suitable way.
Note that this version introduces a bug in which the configuration of
telephone line is not correctly initialised after package setup.
This adds support for a special log stream name called "global", which
instead of setting that as a log stream changes the resource
descriptor to be of the `global` monitored resource descriptor.
According to the information we have in #4 logs submitted to that
resource descriptor should be compatible with Stackdriver Error
Reporting. This is relevant when running journaldriver outside of GCP
as there is no way to utilise Error Reporting with the log stream
resource.
This relates to #4. I'm unsure about saying whether or not it "fixes"
it.
Adds a home-manager configuration that can be used in a Crostini
container running Nix. There isn't any truly ChromeOS-specific stuff
in this yet, as I've set up the interoperability with garcon etc.
manually for now.
