Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove superfluous trailing arguments from parseFloat-calls (PR 14978 follow-up) #15027

Merged
merged 1 commit into from
Jun 11, 2022

Conversation

Snuffleupagus
Copy link
Collaborator

Fixes two recent "Code scanning alerts" on GitHub, which likely happened because these calls originally used parseInt instead (during initial development).

@Snuffleupagus Snuffleupagus changed the title Remove superfluous trailing arguments from parseFloat-calls (14978 follow-up) Remove superfluous trailing arguments from parseFloat-calls (PR 14978 follow-up) Jun 11, 2022
…78 follow-up)

Fixes two recent "Code scanning alerts" on GitHub, which likely happened because these calls originally used `parseInt` instead (during initial development).
@Snuffleupagus
Copy link
Collaborator Author

/botio unittest

@pdfjsbot
Copy link

From: Bot.io (Windows)


Received

Command cmd_unittest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.193.163.58:8877/0b43ecb16011886/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_unittest from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.241.84.105:8877/f0021903c6b5702/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Failed

Full output at http://54.241.84.105:8877/f0021903c6b5702/output.txt

Total script time: 3.20 mins

  • Unit Tests: FAILED

@pdfjsbot
Copy link

From: Bot.io (Windows)


Success

Full output at http://54.193.163.58:8877/0b43ecb16011886/output.txt

Total script time: 7.03 mins

  • Unit Tests: Passed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants