Commits on Jan 9, 2017
  1. Pinning Jinja to <2.9 for now

    Variables defined in an outer scope can no longer be set from an inner scope (see
    pallets/jinja#641). Regardless of whether that is right or wrong, we can't control if
    people are using such constructs in their plugins, which versions of Jinja >= 2.9 would
    now break out of the blue, regardless of OctoPrint version. That is unacceptable sadly
    and requires pinning for now, until plugin authors have had a chance to adapt
    Also see #1697.
    committed Jan 9, 2017
Commits on Dec 8, 2016
  1. Preparing release of 1.3.0

    committed Dec 8, 2016
Commits on Dec 7, 2016
  1. Fix docs for OctoPrint.upload method

    committed Dec 7, 2016
  2. Make OctoPrint.upload's url behave like others

    So far only was interpreted relatively to the defined base url.
    We want this to behave like other requests from the client lib
    though, so now it does.
    committed Dec 7, 2016
  3. Fix filesize not being defined

    committed Dec 7, 2016
Commits on Dec 2, 2016
  1. Preparing release of 1.3.0rc3

    committed Dec 2, 2016
  2. Fix temperature history on server reconnect

    Two problems solved:
      * Make sure to only process temperature data once we
        have printer profile information on hand to evaluate
        the heater data. If we don't have that yet, create a client
        side backlog and process that once we have the necessary
        data on hand.
      * Do not use uninitialized history cutoff values - if our cutoff
        value hasn't yet synced (no settings response arrived yet),
        just don't perform the cutoff.
    committed Dec 2, 2016
Commits on Dec 1, 2016
  1. Fix yet another settings caching issue

    That api endpoint really is a tough nut. ETag calculation now also
    takes full settings dump from settings plugins into account, because
    those might be providing custom keys through custom on_settings_load
    implementations, for which we will not notice any changes if we are
    only looking at the effective config.
    Of course, the more we put into that ETag calculation, the slower it will
    be and the less sense it will make. Somewhat annoying :/
    committed Dec 1, 2016
  2. Fix handling of new structures in getOnlyChangedData

    Not testing if oldRoot was actually set and contained the
    key in question could cause issues if a completely new data
    structure was sent to the backend that was not mirrored by
    the default settings. Things like e.g. complex configuration
    items in a by default empty object.
    committed Dec 1, 2016
Commits on Nov 30, 2016
  1. Merge branch 'maintenance' into devel

    # Conflicts:
    committed Nov 30, 2016
  2. Improved (manually to run) doc test for latest release selector

    committed Nov 30, 2016
  3. Preparing release of 1.2.18

    committed Nov 30, 2016
Commits on Nov 28, 2016
  1. Added note that jquery and lodash are dependencies of the js client lib

    committed Nov 28, 2016
Commits on Nov 25, 2016
  1. Make sure our command line calls always exit

    sarge's "wait_events" is unreliable. If an asynchronous
    job is started but stops immediately and raises a sarge
    Exception (inside the async thread), the associated
    command's event will never be set event though the
    process finished. So we'd wait indefinitely here.
    We circumvent this by first waiting until the commands
    are parsed and processed (p.commands contains
    elements), then until said commands are started and then
    making sure the command's process is actually set. Only
    then do we actually have a background process running
    that we'll be able to monitor further down, otherwise
    the command immediately failed.
    committed Nov 25, 2016
  2. Better error and subprocess handling

    Removed a potential deadlock, added logging for all
    raised exceptions, made _to_error more solid and
    removed another potential encoding issue when
    creating diffs
    committed Nov 25, 2016
Commits on Nov 24, 2016
  1. Slight rewording in Cura wizard

    committed Nov 24, 2016
  2. Pin tornado dependency to 4.0.2 for now

    ">=4.0.2,<4.1" will pull in 4.1b and we don't want that due to issue with
    that and websocket communication due to permessage-deflate.
    While we desperately need to migrate to a newer tornado, due to some
    voodoo needed to get large streamed uploads and downloads to work
    that is probably not completely straightforward and therefore
    something for post-1.3.0-stable release.
    committed Nov 24, 2016
  3. Prepare release of 1.3.0rc2

    committed Nov 24, 2016
  4. Actually add config subcommand to CLI

    committed Nov 24, 2016
Commits on Nov 23, 2016
  1. SWU: "busy" spinner while checking for updates

    committed Nov 23, 2016
  2. Documentation for last_position, pause_position, cancel_position

    committed Nov 23, 2016
  3. Add M600 (filament change) to long running commands

    committed Nov 23, 2016
  4. Fix working dialog of pgmr and swu being closeable while active

     Only the close button should work now
    committed Nov 23, 2016
  5. Demote pip upgrade message from stderr to stdout in client output

    Having that output stay on stderr and hence in shiny red looks way
    too alarming considering that it's only a pip update that is not THAT
    critical usually (and we don't want to do it automatically anyhow
    considering how often that appears to break stuff).
    committed Nov 23, 2016
  6. Fixed a rare race condition causing a "settings changed" popup in cas…

    …e of local changes
    If the SettingsUpdated event for whatever reason got slightly delayed and arrived AFTER
    the save request was already processed, in rare situations it could happen that the
    "Settings Changed" popup was triggered even though the settings had already been
    successfully saved.
    Modified such that we now keep track of if we already saw the SettingsUpdated event
    associated with our save request and if not we ignore the next one.
    To ensure that we don't get out of sync due to that when a settings update request is
    sent, but no settings are actually change, we also now always trigger the SettingsUpdated
    event, even in such cases. Clients can use the hashs in the payload to test if something
     actually changed - if necessary.
    committed Nov 23, 2016
Commits on Nov 22, 2016
  1. Fix update of webcam streamURL not being recognized

    We used to track our webcam stream URL by the global variable
    CONFIG_WEBCAMURL. That's still a left over from the architecture
    about four years ago and completely obsolete these days.
    Additionally it causes issues now that anything rendered into
    the page (as this variable value is through initscript.jinja2)
    will not be changed unless the page cache is refreshed.
    Taking the stream URL from the settings view model instead
    solves that problem and is way cleaner anyhow.
    committed Nov 22, 2016
  2. Inapplicable pip arguments can be blacklisted when installing or unin…

    …stalling a package
    donovan6000 committed with Nov 7, 2016
  3. Changed help text slightly

    committed Nov 22, 2016
  4. Merge branch 'feature/timelapse_repeat_frames' of…

    …dattas/OctoPrint into pr/dattas/feature/timelapse_repeat_frames
    committed Nov 22, 2016
  5. Merge branch 'maintenance' into devel

    # Conflicts:
    #	src/octoprint/translations/de/LC_MESSAGES/
    #	src/octoprint/translations/de/LC_MESSAGES/messages.po
    #	translations/de/LC_MESSAGES/
    #	translations/de/LC_MESSAGES/messages.po
    #	translations/messages.pot
    committed Nov 22, 2016