change default of rejectRecord operation api to throw
fixes to cloneDeep
change operation rejectRecord api to throw instead of ignore
v0.63.6
Fix _slicer_stats.slicers, which was previously returning a function
Fix updating the executionMetaData function to not set _slicer_stats to null and effectively remove the _slicer_stats when updating the execution.
v0.63.5
This release tries to address #1649 by making sure the execution controller is responding before the worker tries to connect using socket.io.
v0.63.4
Mainly internal fixes, except the docker image now uses 10.19 (without alpine).
Internal Changes
Removed es5 tests from CI
Improvements to Dockerfile and CI builds
Adds .yarn-offline-cache directory that can be committed safely to the repo and used to speed up docker and ci builds. It also allows more reproducible builds.
Fixes missing dependency issues and removes unused/unnecessary dependencies
Removes use of lodash in a couple packages
Removes building / publishing dev docker images
Improve some of the top level scripts, including renaming build:fix to build:doctor. build:fix will now output a deprecation warning.
Moves Queue from @terascope/queue package to @terascope/utils
Removes @terascope/queue and @terascope/error-parser because they aren't needed
v0.63.3
Internal change to use a new method for registering the getMetadata and setMetadata functions on the executionContext api.
v0.63.2
Fixes teraslice to update _updated date on execution and job more often
Fixes teraslice API to return the ex_id when creating a job
Fixes execution pause
Fixes connect timeout issue
Fixes port allocation issues (mainly edge cases like e2e tests)
Kubernetes Note: When upgrading from a release earlier than v0.63.0 to a release newer than v0.63.0, you must first shut down all Teraslice jobs, then upgrade the master, then start the Teraslice jobs back up. Otherwise you will lose the ability to see and manage the jobs running with older labels.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bumps @terascope/scripts from 0.63.0 to 0.64.0.
Release notes
Sourced from
@terascope/scripts
's releases.Commits
1cc8fbe
release: (minor) teraslice@0.64.072069fd
[HOTFIX] fix testsa03e992
Merge pull request #1719 from terascope/fix-clone-deep9e9b982
Simplify cloneDeep to allow the more edge cases for objects5fd280e
Don't export isNullObjectc6437c5
Fix cloneDeep handling of classes with validations61fbbf7
bump: (patch)@terascope/utils
@0
.24.3,@terascope/data-types
@0
.14.3cf575de
Don't use Object.create(null) in some of the utils to avoid weird issuesecf7d2a
Fix cloning objects created by Object.create(null)f70ea3e
add more tests for cloneDeepDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show