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

return an error code when the parsed CSS stdin is invalid #342

Conversation

lade-odoo
Copy link
Contributor

No description provided.

lade-odoo added a commit to odoo-dev/odoo that referenced this pull request Aug 27, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342
@MohammadYounes
Copy link
Owner

@lade-odoo Kindly fix the lint errors to be able to merge this.

@lade-odoo lade-odoo force-pushed the master-return_error_code_invalid-lade branch from a7cc308 to 8df4fbc Compare August 27, 2024 14:32
@MohammadYounes MohammadYounes merged commit e1e5ef7 into MohammadYounes:master Aug 27, 2024
11 checks passed
robodoo pushed a commit to odoo/odoo that referenced this pull request Sep 10, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

closes #178021

Signed-off-by: Aaron Bohy (aab) <[email protected]>
lade-odoo added a commit to odoo-dev/odoo that referenced this pull request Sep 10, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

X-original-commit: 0c9dbd4
robodoo pushed a commit to odoo/odoo that referenced this pull request Sep 11, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

closes #179784

X-original-commit: 0c9dbd4
Signed-off-by: Aaron Bohy (aab) <[email protected]>
Signed-off-by: Laurent Desausoi (lade) <[email protected]>
lade-odoo added a commit to odoo-dev/odoo that referenced this pull request Sep 12, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

X-original-commit: a50f197
robodoo pushed a commit to odoo/odoo that referenced this pull request Sep 12, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

closes #179852

X-original-commit: a50f197
Signed-off-by: Aaron Bohy (aab) <[email protected]>
Signed-off-by: Laurent Desausoi (lade) <[email protected]>
fw-bot pushed a commit to odoo-dev/odoo that referenced this pull request Sep 12, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

X-original-commit: 52ebdb5
fw-bot pushed a commit to odoo-dev/odoo that referenced this pull request Sep 12, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

X-original-commit: 52ebdb5
robodoo pushed a commit to odoo/odoo that referenced this pull request Sep 13, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

closes #180093

X-original-commit: 52ebdb5
Signed-off-by: Aaron Bohy (aab) <[email protected]>
Signed-off-by: Laurent Desausoi (lade) <[email protected]>
robodoo pushed a commit to odoo/odoo that referenced this pull request Sep 13, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

closes #180110

X-original-commit: 52ebdb5
Signed-off-by: Aaron Bohy (aab) <[email protected]>
Signed-off-by: Laurent Desausoi (lade) <[email protected]>
lade-odoo added a commit to odoo-dev/odoo that referenced this pull request Sep 13, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

X-original-commit: 52ebdb5
robodoo pushed a commit to odoo/odoo that referenced this pull request Sep 14, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

closes #180120

X-original-commit: 52ebdb5
Signed-off-by: Aaron Bohy (aab) <[email protected]>
Signed-off-by: Laurent Desausoi (lade) <[email protected]>
riccardo-metrum pushed a commit to resultrum/odoo that referenced this pull request Sep 30, 2024
Steps to reproduce:

- Include in your assets a CSS file with invalid formatting.
- Translate your website in RTL language.
> The website will never load and you will be left with a blank page.

Cause of the issue:
`rtlcss` never exit with a returncode, consequently our error management
there is useless. As from `rtlcss` 4.1.0 [1], an error code is returned but
only when using a CSS file. In our case, Odoo pass the CSS payload via
the `stdin`. A PR [2] has been opened on `rtlcss` to also exit with a return
code in this scenario (and log details to `stderr`).
In the meantime and also for earlier versions, the error management had
to be slightly adjusted. As we cannot deduce any informations from the
return code (and the `stderr` is completely empty), we can exploit the
fact that, in case of errors, `rtlcss` doesn't output anything to `stdout`.

[1]: MohammadYounes/rtlcss@4e62545
[2]: MohammadYounes/rtlcss#342

closes odoo#179852

X-original-commit: a50f197
Signed-off-by: Aaron Bohy (aab) <[email protected]>
Signed-off-by: Laurent Desausoi (lade) <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants