Skip to content
Tests

Handling the conflict case where email has been already taken in AWS #10722

Sign in to view logs

Handling the conflict case where email has been already taken in AWS

Handling the conflict case where email has been already taken in AWS #10722

Triggered via pull request November 27, 2024 18:08
@vikhyat187vikhyat187
synchronize #2271
remove-log-aws-command
Status Success
Total duration 3m 11s
Artifacts –

test.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
build (20.11.x): config/default.js#L76
Unsafe Regular Expression
build (20.11.x): controllers/discordactions.js#L344
Variable Assigned to Object Injection Sink
build (20.11.x): controllers/discordactions.js#L360
Generic Object Injection Sink
build (20.11.x): controllers/issues.js#L17
Found non-literal argument to RegExp Constructor
build (20.11.x): middlewares/validators/monitor.js#L73
Generic Object Injection Sink
build (20.11.x): middlewares/validators/task-requests.js#L6
Found non-literal argument to RegExp Constructor
build (20.11.x): middlewares/validators/task-requests.js#L7
Found non-literal argument to RegExp Constructor
build (20.11.x): models/discordactions.js#L526
Variable Assigned to Object Injection Sink
build (20.11.x): models/progresses.js#L82
Generic Object Injection Sink
build (20.11.x): models/progresses.js#L83
Generic Object Injection Sink