Whenever the allocated shared (slave) instance is destroyed or stopped, isn't included on the getComputerInformation, so the timestamp can eventually go back in time (so partition skips process).

  This ensures that the partition information gets a newer timestamp (larger them the previous one).

   All timestamps parameters should be int, and be consistent accross
   the parameters.

   The client compare previous/fetched as float, so use string can break
   later on if we introduce a non-numeric value on returned dict.

    Check if bang_timestamp is consistent and updated
    accordingly by the normal usage.

    Whenever an instance is allocated the partition must
    update its bang_timestamp.

    Ensure the implementation is consistent with the precision (1e6) otherwise partition modification date will never
    ever be larger, when compared.

  This ensure that timestamp is updated, and enforces that cache is updated

Instances were not allocated on this project in reality.

It is otherwise difficult for a Project Manager to access it on the panel

Only payable deliveries will generate invoices.

It is needed for libslap.getInformation method compatibility.
It was dropped by nexedi/slapos.core@784e255f

  Conflict resolution in git added a new line while editing the file

   Use recently added API to speed up the rendering.

  After the 25 of the month, the simulation generate extra SPL for discounts,
  pin DateTime to have stable assertions regardless the date the test runs.

   The object will be reindexed regardless with the recent upgrades (due various factors), so this is end up as a duplicated check.

  Only edit if the document isMemberOf

  Include exceptional value (cabo verde) since the title is different
  between the removed object and the ones that was kept.

  Remove all duplication and normalize id/path to prevent further problems.
  Set int_index to 1 on all region categories to facilitate the migration script, to know
      which ones are the "latest". This flagging allow us search for a proper category
  when cleaning up.

  *portal_categories/region/* was added to keep path to prevent categories be removed
  during the upgrade. This should be done (or not) by a migration script later on, since
  it is required to update the related objects.
  We kept a large list, because we want the int_index:1 be set on upgrade,
  so the change only keeps the removed objects, but edit everything else
  remaining.

   Those are external tests that depends on gitlab, so they are marked as expected failures until the expected
   changes be released as tags.

    Those tests aims to check if the missuse of allOf was properly handled w/o compromise the rendering of the UI or its usage.

   Prefer use payment page related to the instance tree rather them the generic one, so it reduces confusion.

   Introduce a listbox rather them a page template or HTML for a more
   future-proof approach.

   Some logic could be generalized for shorten the test/get scripts,
   but for now it is better keep them as is.

  The alarm should update the state of Subscription Request whenever Compute Node and Project are invalidated, to proper cancel it as soon as possible.

   The cancellation and validation occur on the same group of objects, so to save code and processing merge both.

   "Cancel" takes precedence over "validate", if the user destroys his instance "too fast" we should not drop his subscription request as soon as possible.

  This helps to preserve backward compatibility with existing sites, that would have broken documents by the absence of the portal types.

  This was causing bt5 to generate delta while export.