mirror of
https://github.com/R0m1k3/Loki.git
synced 2026-10-12 01:37:06 +02:00
MichaelandClaude Opus 5
b405adea6c
Trois défauts sans rapport entre eux, tous visibles à l'écran. Jauge de contexte bloquée à « 0 / N (0 %) » : le comptage exact vient de usage.prompt_tokens (include_usage), qu'un llama-server récent a cessé de renvoyer. On note désormais si l'usage est arrivé ; sinon la fin de tour publie l'estimation qui pilote déjà la compaction — approximative, mais jamais absente. Et la souscription envoie la valeur courante juste après le rattrapage : une page rechargée affichait zéro sur une discussion pourtant pleine, faute d'événement ctx_used dans la fenêtre rejouée. Espace disque : « il ne reste que 11,9 Go » sur un partage Unraid qui en a des centaines. /mnt/user est servi par shfs, un FUSE qui agrège plusieurs disques — statfs y renvoie l'espace d'un seul, et ce chiffre REFUSAIT l'installation du modèle. Les systèmes de fichiers qui approximent (FUSE, overlay, NFS, CIFS, Ceph, Gluster) sont reconnus par leur magie : leur chiffre reste affiché, précédé d'un « ~ », mais ne bloque plus rien. Panneau Fichiers : le panneau entier défilait, emportant vers le haut l'en-tête, le fil d'Ariane et le pied (occupation disque, bouton .zip) dès qu'il y avait quelques fichiers. Seule la liste défile maintenant ; le pied reste en bas et l'état vide se centre. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
83 lines
2.6 KiB
Markdown
83 lines
2.6 KiB
Markdown
# postcss-selector-parser [](https://github.com/postcss/postcss-selector-parser/actions/workflows/test.yml)
|
|
|
|
> Selector parser with built in methods for working with selector strings.
|
|
|
|
## Install
|
|
|
|
With [npm](https://npmjs.com/package/postcss-selector-parser) do:
|
|
|
|
```
|
|
npm install postcss-selector-parser
|
|
```
|
|
|
|
## Quick Start
|
|
|
|
```js
|
|
const parser = require('postcss-selector-parser');
|
|
const transform = selectors => {
|
|
selectors.walk(selector => {
|
|
// do something with the selector
|
|
console.log(String(selector))
|
|
});
|
|
};
|
|
|
|
const transformed = parser(transform).processSync('h1, h2, h3');
|
|
```
|
|
|
|
To normalize selector whitespace:
|
|
|
|
```js
|
|
const parser = require('postcss-selector-parser');
|
|
const normalized = parser().processSync('h1, h2, h3', {lossless: false});
|
|
// -> h1,h2,h3
|
|
```
|
|
|
|
Async support is provided through `parser.process` and will resolve a Promise
|
|
with the resulting selector string.
|
|
|
|
## API
|
|
|
|
Please see [API.md](API.md).
|
|
|
|
## Security
|
|
|
|
### Selector nesting depth (CVE-2026-9358)
|
|
|
|
The parser walks the selector AST recursively, both when parsing and when
|
|
serializing it back to a string (`.toString()`). In versions up to and
|
|
including `7.1.1`, a selector with extreme nesting — for example thousands of
|
|
nested `:not(...)` — could recurse deeply enough to overflow the call stack and
|
|
throw `RangeError: Maximum call stack size exceeded`, a potential
|
|
denial-of-service when processing untrusted CSS.
|
|
|
|
This is now bounded by a maximum nesting depth (default: `256`). Beyond that
|
|
depth, parsing and serialization throw a regular, catchable `Error` at a
|
|
predictable point instead of relying on the runtime hitting its stack limit.
|
|
The default is far above any realistic selector, so it does not affect normal
|
|
use.
|
|
|
|
**Practical impact is low.** The only attacker-controlled input is the selector
|
|
string itself, which is now capped by the default limit. The limit is
|
|
adjustable through the `maxNestingDepth` option, but that option is trusted
|
|
configuration provided by the integrating code — it is never derived from the
|
|
parsed CSS, so a malicious selector cannot change it:
|
|
|
|
```js
|
|
// Tighten the limit when parsing untrusted input:
|
|
parser().processSync(untrustedSelector, {maxNestingDepth: 128});
|
|
```
|
|
|
|
Raising `maxNestingDepth` to a very large value is an explicit, informed choice
|
|
and can reintroduce the stack-overflow risk in environments with a small call
|
|
stack (e.g. browser workers). The default is recommended unless you have a
|
|
specific need.
|
|
|
|
## Credits
|
|
|
|
* Huge thanks to Andrey Sitnik (@ai) for work on PostCSS which helped
|
|
accelerate this module's development.
|
|
|
|
## License
|
|
|
|
MIT
|