npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@scramjet/durability-preservation

v0.22.0

Published

Sequence downloads following files every second: ``` [ "http://some.host.com/durability-test/file2.bin", "http://some.host.com/durability-test/file1.bin", "http://some.host.com/durability-test/file3.bin" ] ```

Downloads

9

Readme

Sequence downloads following files every second:

[
    "http://some.host.com/durability-test/file2.bin",
    "http://some.host.com/durability-test/file1.bin",
    "http://some.host.com/durability-test/file3.bin"
]

build everything:

yarn install && yarn build && yarn prepack

Run test

(from bdd dir)

yarn install

Test variations

At least 5 sequences for 15 minutes, check after 6 minutes.

yarn test:bdd --name "PT-003 TC-001"

At least 25 sequences for 2 hours, check after 1 hour

yarn test:bdd --name "PT-003 TC-002"

At least 25 sequences for 25 hours, check after 24 hour

yarn test:bdd --name "PT-003 TC-003"

Run sequence standalone

prepare sequence

✘-INT ~/github/scramjet-csi-dev/packages/reference-apps/durability-preservation
$ yarn build && yarn prepack

start host

✘-INT ~/github/scramjet-csi-dev
$ ts-node packages/host/src/bin/start.ts

send sequence

✘-INT ~/github/scramjet-csi-dev/packages/reference-apps/durability-preservation
$ SEQ_ID=$( \
    curl --location --request POST "http://localhost:8000/api/v1/sequence" \
    --header 'content-type: application/octet-stream' \
    --data-binary '@../durability-preservation.tar.gz' | jq ".id" -r \
)

args meaning:

60 - execution time (SECONDS)
128 - memory allocation size (MB),
[url, url, url] - list of urls of binary files to be downloaded every second

start sequence with args (replace ip with your machine ip)

$ INSTANCE_ID=$(curl --location --request POST "http://localhost:8000/api/v1/sequence/$SEQ_ID/start" \
--header 'content-type: application/json' \
--data-raw '{
    "appConfig": {},
    "args": [60, 128, ["https://assets.scramjet.org/scp-store/durability-test/file1.bin","https://assets.scramjet.org/scp-store/durability-test/file2.bin","https://assets.scramjet.org/scp-store/durability-test/file3.bin"]]
}' | jq ".id" -r)

send event

curl --location --request POST "http://localhost:8000/api/v1/instance/$INSTANCE_ID/_event" \
--header 'Content-Type: application/json' \
--data-raw '[5001,{"eventName":"alive","message":"1234"}]'

get last event

curl --location --request GET "http://localhost:8000/api/v1/instance/$INSTANCE_ID/event" --header 'Transfer-Encoding: chunked' \
--header 'content-type: application/octet-stream'

Response should contains message sent in last event