Closed martinig94 closed 3 weeks ago
Looks great to me! Will leave to @zackarno to approve!
looks like a nice addition! i get a little blocked trying to figure out how to interactively step through
triage_signals()
for testing. Could one of you could explain how to do that step by step here -- it would be useful for this review and myself/others in the future
Seth gave me some specific steps to follow to allow debugging. Have written them down in internal doc, but perhaps Giulia and I can develop something more formal later. Nonetheless will summarise here so we it's at least somewhere we can reference for now (feel free to fill in gaps):
output/indicator_id/test/
(path made by cs$signals_path
). Therefore you need to create this test file by running a manual GHA workflow (i.e wfp_market_monitor
) with the following parameters set (leave all the rest on default)
a. HS_LOCAL = FALSE
b. HS_DRY_RUN=TRUE
HS_ADMIN_NAME
- this should just be your nameHS_LOCAL=FALSE
manually in you Rsession and test
param in triage_signals() is TRUE. So code could look like:debugonce(triage_signals$triage_signals)
Sys.setenv("HS_LOCAL" = FALSE) # if u dont do this, email wont send
triage_signals$triage_signals(indicator_id,n_campaigns = 1, test=TRUE) # if test = TRUE email will send
If you were to accidentally put test= FALSE you could potentially send signal externally, but it's very unlikely as the process will most likely be aborted when the non-test parquet file is not found in the scanned directory
Deals with with issue 243
Due to a branch renaming some previous comments are in a closed PR. All the comments have been addressed and an additional change has been added: