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

Parse Error: Invalid character in chunk size #4434

Open
stoffel7 opened this issue Jul 2, 2024 · 1 comment
Open

Parse Error: Invalid character in chunk size #4434

stoffel7 opened this issue Jul 2, 2024 · 1 comment
Labels
needs more info issues that need more info from the author

Comments

@stoffel7
Copy link

stoffel7 commented Jul 2, 2024

Version

V20.15.0

Platform

Linux raspberrypi 6.1.21-v7+ nodejs/node#1642 SMP Mon Apr  3 17:20:52 BST 2023 armv7l GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

see following code
`
async function Counter() {

httpGet('http://10.10.13.14/counter?PW=&', {
    timeout: 2000
},
(error, response) => {
    if (!error) {
            if (error) {
                log('Fehler  ' + error, 'warn');
            } else {
                log( response.data); 
            }
    } else {
        console.error(error);
    }
});

}
Counter();
`

How often does it reproduce? Is there a required condition?

every time with Nodejs V20.15
is does not happen in V18.17

What is the expected behavior? Why is that the expected behavior?

this is the expected output:
counter;0;0;0;95998;0;0;0;0;0;713496;0;0

What do you see instead?

script.js.Skript_9: Parse Error: Invalid character in chunk size

Additional information

what is wrong here…
with NodeJS V18.17.1 is doesn‘t happen

@RedYetiDev
Copy link
Member

RedYetiDev commented Jul 2, 2024

Hi! Thanks for the report, can you provide a minimal reproducible example? One that utilizes only Node.js features?

@marco-ippolito marco-ippolito transferred this issue from nodejs/node Jul 2, 2024
@RedYetiDev RedYetiDev added needs more info issues that need more info from the author and removed wrong repo labels Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info issues that need more info from the author
Projects
None yet
Development

No branches or pull requests

2 participants