Recached

MITLibraries / timdex-pipeline-lambdas
96%

DEFAULT BRANCH: main
Repo Added
Token 4RoYGm1RZncTw4D1pthGX04d7T6Jd4PKO regen
Build 413 Last
Files 6
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

LAST BUILD ON BRANCH main
branch: SELECT
CHANGE BRANCH
x
Sync Branches

coverage: 96.164% (-0.05%) from 96.216%
21413873513

push

github

web-flow 
Merge pull request #333 from MITLibraries/timx-590-early-exits

TIMX-590 early exits

0 of 1 new or added line in 1 file covered. (0.0%)

1 existing line in 1 file now uncovered.

351 of 365 relevant lines covered (96.16%)

0.96 hits per line

Relevant lines Covered
365 RELEVANT LINES 351 COVERED LINES
0.96 HITS PER LINE
Source Files on main

Recent builds

Builds Branch Commit Type Ran Committer Via Coverage
21413873513 main Merge pull request #333 from MITLibraries/timx-590-early-exits TIMX-590 early exits push web-flow github
96.16
21410465738 timx-590-early-exits TIMX-590 early exits Why these changes are being introduced: * Remove deprecated success and failure attributes that are no longer used by the TIMDEX step function How this addresses that need: * Remove success and failure attributes from format... push ehanson8 github
96.16
20342813103 v2.8 Merge pull request #332 from MITLibraries/USE-279-raise-errors-versus-failure-result USE 279 - utilize and control next-step values push web-flow github
96.22
20342765058 main Merge pull request #332 from MITLibraries/USE-279-raise-errors-versus-failure-result USE 279 - utilize and control next-step values push web-flow github
96.22
20315941574 USE-279-raise-errors-versus-failure-result Temporarily restore success and failure response properties Why these changes are being introduced: Until changes can be made to the StepFunction that would lean into a controlled use of `next-step`, we need to keep `success` and `failure` as pr... Pull #332 ghukill github
96.22
20312802350 USE-279-raise-errors-versus-failure-result Further utilize and control next-step values Why these changes are being introduced: This lambda project has a tightly coupled relationship with the TIMDEX ETL StepFunction. Currently, at three points in the StepFunction this lambda is invovked ... push ghukill github
96.16
20279470882 main Merge pull request #331 from MITLibraries/USE-279-refactor-input-output-handling USE 279 - Refactor handling of input payload and output response push web-flow github
96.05
20248401219 USE-279-refactor-input-output-handling Refactor handling of input payload and output response Why these changes are being introduced: Each time a change is required in this lambda, one can feel some of brittleness that has collected around input handling, argument passing, and logic ... Pull #331 ghukill github
96.05
20143806851 v2.7 Merge pull request #330 from MITLibraries/USE-270-update-browsetrix-command-generation USE 270 - update browsetrix command generation push web-flow github
95.3
20140365958 main Merge pull request #330 from MITLibraries/USE-270-update-browsetrix-command-generation USE 270 - update browsetrix command generation push web-flow github
95.3
See All Builds (268)

Badge your Repo: timdex-pipeline-lambdas

We detected this repo isn’t badged! Grab the embed code to the right, add it to your repo to show off your code coverage, and when the badge is live hit the refresh button to remove this message.
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

Refresh