Permalink
Switch branches/tags
request_handler_with_pipes release-5.1.8 release-5.1.7 release-5.1.6 release-5.1.5 release-5.1.4 release-5.1.3 release-5.1.2 release-5.1.1 release-5.1.0 release-5.0.30 release-5.0.29 release-5.0.28 release-5.0.27 release-5.0.26 release-5.0.25 release-5.0.24 release-5.0.23 release-5.0.22 release-5.0.21 release-5.0.20 release-5.0.19 release-5.0.18 release-5.0.17 release-5.0.16 release-5.0.15 release-5.0.14 release-5.0.13 release-5.0.11 release-5.0.10 release-5.0.9 release-5.0.8 release-5.0.7 release-5.0.6 release-5.0.5 release-5.0.4 release-5.0.3 release-5.0.2 release-5.0.1 release-5.0.0.rc2 release-5.0.0.rc1 release-5.0.0.beta3 release-5.0.0.beta2 release-5.0.0.beta1 release-4.0.60 release-4.0.59 release-4.0.58 release-4.0.57 release-4.0.56 release-4.0.55 release-4.0.53 release-4.0.52 release-4.0.51 release-4.0.50 release-4.0.49 release-4.0.48 release-4.0.46 release-4.0.45 release-4.0.44 release-4.0.43 release-4.0.42 release-4.0.41 release-4.0.40 release-4.0.39 release-4.0.38 release-4.0.37 release-4.0.36 release-4.0.35 release-4.0.34 release-4.0.33 release-4.0.32 release-4.0.31 release-4.0.30 release-4.0.29 release-4.0.28 release-4.0.27 release-4.0.26 release-4.0.25 release-4.0.24 release-4.0.23 release-4.0.21 release-4.0.20 release-4.0.19 release-4.0.18 release-4.0.17 release-4.0.16 release-4.0.14 release-4.0.13 release-4.0.10 release-4.0.8 release-4.0.7 release-4.0.6 release-4.0.5 release-4.0.4 release-4.0.3 release-4.0.2 release-4.0.1 release-4.0.0.rc6 release-4.0.0.rc4 release-3.9.5.rc3
Nothing to show
Commits on Aug 18, 2017
  1. Revert "Build system: CxxCodeTemplateRenderer: only update destinatio…

    FooBarWidget committed Aug 18, 2017
    …n file when changed"
    
    This reverts commit 2392936.
    
    Turns out writing the file is necessary. It updates the file's timestamp so that
    the build system won't try to rebuild it next time.
Commits on Aug 17, 2017
  1. Document the --max-requests fix in the CHANGELOG

    FooBarWidget committed Aug 17, 2017
    [ci:skip]
Commits on Aug 16, 2017
  1. Document the new logging format

    FooBarWidget committed Aug 16, 2017
    [ci:skip]
  2. CHANGELOG: fix typo

    FooBarWidget committed Aug 16, 2017
    [ci:skip]
Commits on Aug 15, 2017
  1. ConfigKit: update comments

    FooBarWidget committed Aug 15, 2017
  2. StringKeyTable: have insert() return the affected Cell

    FooBarWidget committed Aug 15, 2017
    That way callers that want to operate on the inserted copy of the value
    don't have to perform another lookup.
  3. ConfigKit::Store::previewUpdate(): insert schema entry inspection res…

    FooBarWidget committed Aug 15, 2017
    …ult before store inspection result
    
    This makes the behavior consistent with inspect().
  4. ConfigKit: update recommended component composition pattern to allow …

    FooBarWidget committed Aug 15, 2017
    …default values from the parent to be correctly passed to subcomponents
    
    Parent components may define different default values for the equivalent keys in subcomponents.
    
    [ci:skip]
Commits on Aug 11, 2017
Commits on Aug 9, 2017
  1. Standalone: automatically uses Nginx to serves static asset URLs that…

    CamJN committed with FooBarWidget Aug 2, 2017
    … conform to the webpacker gem's format
    
    
    Closes GH-1966.
  2. Refactor logging system and integrate it with ConfigKit

    FooBarWidget committed Mar 10, 2017
    The new logging system is called LoggingKit. It has cleaner code
    and allows more complex configuration while being fully thread-safe.
    
    It also slightly changes the log output format: it includes the log
    message's log level.
  3. ConfigKit: improve recommended component patterns

    FooBarWidget committed Aug 8, 2017
    The previous pattern recommendation did not correctly handle errors
    when composing multiple subcomponents. If one subcomponent fails
    to apply a configuration, then the other subcomponents -- as well
    as the parent component -- can end up in an inconsistent state.
    We solve this problem by splitting configure() into two separate
    methods: prepareConfigChange() and commitConfigChange().
    
    The new pattern also provides an official answer on how to deal
    with configuration activation work, such as opening new log files
    after a configuration change. Previously we only had an official
    answer on how to cache config options. The new pattern unifies
    config caching and arbitrary activation work.
    
    We also officially document how to subclass a component.