![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
@shelf/jest-elasticsearch
Advanced tools
Readme
Jest preset for running tests with local ElasticSearch
$ yarn add @shelf/jest-elasticsearch --dev
jest.config.js
module.exports = {
preset: '@shelf/jest-elasticsearch'
};
If you have a custom jest.config.js
make sure you remove testEnvironment
property, otherwise it will conflict with the preset.
jest-es-config.js
module.exports = () => {
return {
esVersion: '8.4.0', // ! must be exact version. Ref: https://github.com/elastic/elasticsearch-js .
// don't be shy to fork our code and update deps to correct.
clusterName: 'your-cluster-name',
nodeName: 'your-node-name',
port: 9200,
indexes: [
{
name: 'your-index-name',
body: {
settings: {
number_of_shards: '1',
number_of_replicas: '1'
},
aliases: {
'your-alias': {}
},
mappings: {
dynamic: false,
properties: {
//here you should paste your mapping
//Example:
id: {
type: 'keyword'
}
}
}
}
}
]
};
};
it();
By default the jest-es-config.js
is read from cwd
directory, but this might not be suitable for
monorepos with nested jest projects
with nested jest.config.*
files nested in subdirectories.
If your jest-es-config.js
file is not located at {cwd}/jest-es-config.js
or you are using
nested jest projects
, you can define the environment variable JEST_ELASTICSEARCH_CONFIG
with
the absolute path of the respective jest-es-config.js
file.
JEST_ELASTICSEARCH_CONFIG
in nested project// src/nested/project/jest.config.js
const path = require('path');
// Define path of project level config - extension not required as file will be imported
// via `require(process.env.JEST_ELASTICSEARCH_CONFIG)`
process.env.JEST_ELASTICSEARCH_CONFIG = path.resolve(__dirname, './jest-es-config');
module.exports = {
preset: '@shelf/jest-elasticsearch'
displayName: 'nested-project',
};
Exception in thread "main'
java.lang.UnsupportedOperationException The Security Manager is deprecated and will be removed in a future release
at java.base/java.lang.System.setSecurityManager(System. java: 416)
at ora.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.iava:71
The main reason why this issue appears is that you have an incompatible java version installed to run elastic locally.
$ /usr/libexec/java_home -V
$ /usr/libexec/java_home -v 18
If you see no versions or do not have a compatible version installed - Install version 18 https://www.oracle.com/java/technologies/downloads/#java18
Reload the console and check the java version with
$ java -version
Output for proper work
$ java -version
java version "18.0.2.1"
Java(TM) SE Runtime Environment (build 18.0.2.1+1-1)
Java HotSpot(TM) 64-Bit Server VM (build 18.0.2.1+1-1, mixed mode, sharing)
Note: If you need to run elastic <=
v7.17.x
locally, then perform the steps above but for the java version 1.8.xxx
$ git checkout master
$ yarn version
$ yarn publish
$ git push origin master --tags
Releases
Draft a new release
Publish release
MIT © Shelf
FAQs
Run your tests using jest & elasticsearch-local
We found that @shelf/jest-elasticsearch demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 61 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.