Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@cumulus/errors

Package Overview
Dependencies
Maintainers
4
Versions
128
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@cumulus/errors - npm Package Versions

1
13

13.3.3-alpha.0

Diff

lfrederick
published 13.4.0 •

Changelog

Source

[v13.4.0] 2022-10-31

Notable changes

Added

  • CUMULUS-2998
    • Added Memory Size and Timeout terraform variable configuration for the following Cumulus tasks:
      • fake_processing_task_timeout and fake_processing_task_memory_size
      • files_to_granules_task_timeout and files_to_granule_task_memory_size
      • hello_world_task_timeout and hello_world_task_memory_size
      • sf_sqs_report_task_timeout and sf_sqs_report_task_memory_size
  • CUMULUS-2986
    • Adds Terraform memory_size configurations to lambda functions with customizable timeouts enabled (the minimum default size has also been raised from 256 MB to 512 MB) allowed properties include:
      • add_missing_file_checksums_task_memory_size
      • discover_granules_task_memory_size
      • discover_pdrs_task_memory_size
      • hyrax_metadata_updates_task_memory_size
      • lzards_backup_task_memory_size
      • move_granules_task_memory_size
      • parse_pdr_task_memory_size
      • pdr_status_check_task_memory_size
      • post_to_cmr_task_memory_size
      • queue_granules_task_memory_size
      • queue_pdrs_task_memory_size
      • queue_workflow_task_memory_size
      • sync_granule_task_memory_size
      • update_cmr_access_constraints_task_memory_size
      • update_granules_cmr_task_memory_size
    • Initializes the lambda_memory_size(s) variable in the Terraform variable list
    • Adds Terraform timeout variable for add_missing_file_checksums_task
  • CUMULUS-2631
    • Added 'Bearer token' support to s3credentials endpoint
  • CUMULUS-2787
    • Added lzards-api-client package to Cumulus with submitQueryToLzards method
  • CUMULUS-2944
    • Added configuration to increase the limit for body-parser's JSON and URL encoded parsers to allow for larger input payloads

Changed

  • Updated example/cumulus-tf/variables.tf to have cmr_oauth_provider default to launchpad
  • CUMULUS-3024
    • Update PUT /granules endpoint to operate consistently across datastores (PostgreSQL, ElasticSearch, DynamoDB). Previously it was possible, given a partial Granule payload to have different data in Dynamo/ElasticSearch and PostgreSQL
    • Given a partial Granule object, the /granules update endpoint now operates with behavior more consistent with a PATCH operation where fields not provided in the payload will not be updated in the datastores.
    • Granule translation (db/src/granules.ts) now supports removing null/undefined fields when converting from API to Postgres granule formats.
    • Update granule write logic: if a null files key is provided in an update payload (e.g. files: null), an error will be thrown. null files were not previously supported and would throw potentially unclear errors. This makes the error clearer and more explicit.
    • Update granule write logic: If an empty array is provided for the files key, all files will be removed in all datastores
  • CUMULUS-2787
    • Updated lzards-backup-task to send Cumulus provider and granule createdAt values as metadata in LZARDS backup request to support querying LZARDS for reconciliation reports
  • CUMULUS-2913
    • Changed process-dead-letter-archive lambda to put messages from S3 dead letter archive that fail to process to new S3 location.
  • CUMULUS-2974
    • The DELETE /granules/<granuleId> endpoint now includes additional details about granule deletion, including collection, deleted granule ID, deleted files, and deletion time.
  • CUMULUS-3027
    • Pinned typescript to ~4.7.x to address typing incompatibility issues discussed in https://github.com/knex/knex/pull/5279
    • Update generate-ts-build-cache script to always install root project dependencies
  • CUMULUS-3104
    • Updated Dockerfile of async operation docker image to build from node:14.19.3-buster
    • Sets default async_operation_image version to 43.
    • Upgraded saml2-js 4.0.0, rewire to 6.0.0 to address security vulnerabilities
    • Fixed TS compilation error caused by @aws-sdk/client-s3 3.190->3.193 upgrade
lfrederick
published 13.3.2 •

Changelog

Source

[v13.3.2] 2022-10-10 [BACKPORT]

Please note changes in 13.3.2 may not yet be released in future versions, as this is a backport and patch release on the 13.3.x series of releases. Updates that are included in the future will have a corresponding CHANGELOG entry in future releases.

Fixed

  • CUMULUS-2557
    • Updated @cumulus/aws-client/S3/moveObject to handle zero byte files (0 byte files).
  • CUMULUS-2971
    • Updated @cumulus/aws-client/S3ObjectStore class to take string query parameters and its methods signGetObject and signHeadObject to take parameter presignOptions
  • CUMULUS-3021
    • Updated @cumulus/api-client/collections and @cumulus/integration-tests/api to encode collection version in the URI path
  • CUMULUS-3024
    • Update PUT /granules endpoint to operate consistently across datastores (PostgreSQL, ElasticSearch, DynamoDB). Previously it was possible, given a partial Granule payload to have different data in Dynamo/ElasticSearch and PostgreSQL
    • Given a partial Granule object, the /granules update endpoint now operates with behavior more consistent with a PATCH operation where fields not provided in the payload will not be updated in the datastores.
    • Granule translation (db/src/granules.ts) now supports removing null/undefined fields when converting from API to Postgres granule formats.
    • Update granule write logic: if a null files key is provided in an update payload (e.g. files: null), an error will be thrown. null files were not previously supported and would throw potentially unclear errors. This makes the error clearer and more explicit.
    • Update granule write logic: If an empty array is provided for the files key, all files will be removed in all datastores
lfrederick
published 12.0.3 •

Changelog

Source

[v12.0.3] 2022-10-03 [BACKPORT]

Please note changes in 12.0.3 may not yet be released in future versions, as this is a backport and patch release on the 12.0.x series of releases. Updates that are included in the future will have a corresponding CHANGELOG entry in future releases.

Fixed

  • CUMULUS-3024
    • Update PUT /granules endpoint to operate consistently across datastores (PostgreSQL, ElasticSearch, DynamoDB). Previously it was possible, given a partial Granule payload to have different data in Dynamo/ElasticSearch and PostgreSQL
    • Given a partial Granule object, the /granules update endpoint now operates with behavior more consistent with a PATCH operation where fields not provided in the payload will not be updated in the datastores.
    • Granule translation (db/src/granules.ts) now supports removing null/undefined fields when converting from API to Postgres granule formats.
    • Update granule write logic: if a null files key is provided in an update payload (e.g. files: null), an error will be thrown. null files were not previously supported and would throw potentially unclear errors. This makes the error clearer and more explicit.
    • Update granule write logic: If an empty array is provided for the files key, all files will be removed in all datastores
  • CUMULUS-2971
    • Updated @cumulus/aws-client/S3ObjectStore class to take string query parameters and its methods signGetObject and signHeadObject to take parameter presignOptions
  • CUMULUS-2557
    • Updated @cumulus/aws-client/S3/moveObject to handle zero byte files (0 byte files).
  • CUMULUS-3021
    • Updated @cumulus/api-client/collections and @cumulus/integration-tests/api to encode collection version in the URI path
lfrederick
published 11.1.7 •

Changelog

Source

[v11.1.7] 2022-10-05 [BACKPORT]

Please note changes in 11.1.7 may not yet be released in future versions, as this is a backport and patch release on the 11.1.x series of releases. Updates that are included in the future will have a corresponding CHANGELOG entry in future releases.

Fixed

  • CUMULUS-3024
    • Update PUT /granules endpoint to operate consistently across datastores (PostgreSQL, ElasticSearch, DynamoDB). Previously it was possible, given a partial Granule payload to have different data in Dynamo/ElasticSearch and PostgreSQL
    • Given a partial Granule object, the /granules update endpoint now operates with behavior more consistent with a PATCH operation where fields not provided in the payload will not be updated in the datastores.
    • Granule translation (db/src/granules.ts) now supports removing null/undefined fields when converting from API to Postgres granule formats.
    • Update granule write logic: if a null files key is provided in an update payload (e.g. files: null), an error will be thrown. null files were not previously supported and would throw potentially unclear errors. This makes the error clearer and more explicit.
    • Update granule write logic: If an empty array is provided for the files key, all files will be removed in all datastores
  • CUMULUS-2971
    • Updated @cumulus/aws-client/S3ObjectStore class to take string query parameters and its methods signGetObject and signHeadObject to take parameter presignOptions
  • CUMULUS-2557
    • Updated @cumulus/aws-client/S3/moveObject to handle zero byte files (0 byte files).
  • CUMULUS-3021
    • Updated @cumulus/api-client/collections and @cumulus/integration-tests/api to encode collection version in the URI path
  • CUMULUS-3027
    • Pinned typescript to ~4.7.x to address typing incompatibility issues discussed in https://github.com/knex/knex/pull/5279
    • Update generate-ts-build-cache script to always install root project dependencies
lfrederick
published 13.3.1 •

lfrederick
published 11.1.6 •

lfrederick
published 13.3.0 •

Changelog

Source

[v13.3.0] 2022-8-19

Notable Changes

  • CUMULUS-2930
    • The GET /granules endpoint has a new optional query parameter: searchContext, which is used to resume listing within the same search context. It is provided in every response from the endpoint as meta.searchContext. The searchContext value must be submitted with every consequent API call, and must be fetched from each new response to maintain the context.
    • Use of the searchContext query string parameter allows listing past 10,000 results.
    • Note that using the from query param in a request will cause the searchContext to be ignored and also make the query subject to the 10,000 results cap again.
    • Updated GET /granules endpoint to leverage ElasticSearch search-after API. The endpoint will only use search-after when the searchContext parameter is provided in a request.
lfrederick
published 12.0.2 •

Changelog

Source

[v12.0.2] 2022-08-10 [BACKPORT]

Please note changes in 12.0.2 may not yet be released in future versions, as this is a backport and patch release on the 12.0.x series of releases. Updates that are included in the future will have a corresponding CHANGELOG entry in future releases.

Notable Changes

  • CUMULUS-3019
    • Fix file write logic to delete files by granule_cumulus_id instead of cumulus_id. Previous logic removed files by matching file.cumulus_id to granule.cumulus_id.
lfrederick
published 13.2.1 •

Changelog

Source

[v13.2.1] 2022-8-10 [BACKPORT]

Notable changes

  • CUMULUS-3019
    • Fix file write logic to delete files by granule_cumulus_id instead of cumulus_id. Previous logic removed files by matching file.cumulus_id to granule.cumulus_id.
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc