Single character prepended to a math expression ($...$) make LTeX failing to check a document #442
Assignees
Labels
1-bug 🐛
Issue type: Bug report (something isn't working as expected)
2-confirmed
Issue status: Confirmed, reproducible bug in LTeX
3-fixed
Issue resolution: Issue has been fixed on the develop branch
Milestone
Comments
laclouis5
added
1-bug 🐛
|
valentjn
added
the
2-needs-info
|
I'm using LATEX. Note that I'm using the French language (FR). Here is a document that reproduces the error. Removing one item (either the equation, a sentence, the references, etc.) makes the bug to disappear. I manually added grammar errors that should be caught by LTEX. Sample document \subsubsection{Fonction de coût}
\begin{equation}
L = \frac{\lambda_y}{N_y} \left\|Y - \mathrm{sig}(\hat{Y}) \right\|^2 + \frac{\lambda_o}{N_p} \sum_{\tilde{p}}{\left| O_{\tilde{p}} - \hat{O}_{\tilde{p}} \right|} + \frac{\lambda_e}{N_e} \sum_{\tilde{e}}{\left| E_{\tilde{e}} - \hat{E}_{\tilde{e}} \right|}
\end{equation}
\subsubsection{Un titres}
\label{sec:une-section}
Le post-traitement des données (parfois appelé décodage) désigne l'algorithme qui étant donné des tenseurs de sortie du réseau $\hat{Y}$, $\hat{O}$ et $\hat{E}$ produit un ensemble $\mathcal{S}$ de graphes étoilés représentant la structure des objets présents dans l'image d'entrée. Ce post-traitement est réalisé en deux étapes : (i) les ancres $\mathcal{A}$ et parties d'objet $\mathcal{P}$ sont prédites et (ii) les ancres et les parties sont associées pour former les structures d'objets.
Dans un premier temps la carte de chaleur $\mathrm{sig}(\hat{Y})$ est filtrée afin d'extraire la position et le type des ancre et parties d'objets. Cette carte de chaleure a une valleur proche de 1 aux localisations où le réseau prédit une forte probabilité de présence de point d'intérêt et une valeur de 0 aux endroits où la probabilitée est faible. Une représentation de la carte de chaleur pour les ancres est donnée en figures \ref{fig:sdnet-decoder}b et en \ref{fig:sdnet-decoder}c pour les parties d'objets. Ce filtrage consist en l'application d'une opérassion de max-pooling de taille de fenêtre 5$\times$5 permettant de supprimer les maximums local éventuels de la carte de chaleur (NMS) afin d'extraire uniquement les pics principaux.LTeX configuration "LTeX Language Server" log file "LTeX Language Client" log file Version information
|
valentjn
added
2-confirmed
|
Minimum example: \begin{equation}
X
\end{equation}
$a$ $b$ $c$ $d$ $e$ $f$ $g$ \ref{foo} \ref{bar} 5$\times$5 |
|
Should be fixed now. Edit: Fix released in 13.0.0. |
valentjn
added
the
3-fixed
|
it's not. got the same w latest versions. |
|
@rschinkoeth Please open a new full bug report. I always test via unit tests and manual E2E tests that all reported issues are indeed solved, so your issue is probably unrelated to this one. |
me-johnomar
added a commit
to me-johnomar/ltex-ls
that referenced
this issue
Jan 31, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A single character prefixing a math expression (
$...$) makes LTeX to crash under certain circonstances. I narrowed the bug down to an expression such as:some sentence 5$\times$5In those cases LTeX stops working. The bug is not present if there is no command used inside the math expression (I did not tested all combinations):
some sentence 5$a$5Also, the bug is not present if the prepended item has length > 1:
some sentence 55$\times$5It works with numbers and also characters. A simple workaround is to put a space after:
some sentence 5 $\times$5Expected behavior
No LTeX crash.
LTeX configuration
Please paste all configuration settings starting with
ltex.from yoursettings.json. You can help us by temporarily removing some irrelevant settings from yoursettings.jsonand see if the bug still occurs."LTeX Language Server" log file
First, reproduce the bug. Then, go to
View→Outputand selectLTeX Language Serverin the drop-down list. Paste this log here:"LTeX Language Client" log file
First, set the
ltex.trace.serversetting in yoursettings.jsonto"verbose". Then, reload the VS Code window and reproduce the bug. Go toView→Outputand selectLTeX Language Clientin the drop-down list. Paste this log here (note: it will contain your checked document):Version information
List here the version information of the relevant software.
Additional context/information
You can add any other context or information about the problem here.
The text was updated successfully, but these errors were encountered: