napi-rs / napi-rs/node-rs

jieba: Failed to get cpu info on deno in glibc runner in termux in android

Open
#1,009 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
1.5k
Forks
52
Avg merge
13h 37m
Merged PRs (30d)
19

Description

env: deno in glibc runner in termux in android

角色选择

选择一个角色——然后开启聊天!
GentianAphrodite

error loading part
undefined

详细信息
error loading part

Failed to get cpu info
TypeError: Failed to get cpu info
    at cpus (node:os:66:10)
    at Object.getReport (ext:deno_node/internal/process/report.ts:42:13)
    at isMuslFromReport (file:///data/data/com.termux/files/home/.local/share/fount/node_modules/.deno/@node-rs+jieba@2.0.1/node_modules/@node-rs/jieba/index.js:38:82)
    at isMusl (file:///data/data/com.termux/files/home/.local/share/fount/node_modules/.deno/@node-rs+jieba@2.0.1/node_modules/@node-rs/jieba/index.js:18:14)
    at requireNative (file:///data/data/com.termux/files/home/.local/share/fount/node_modules/.deno/@node-rs+jieba@2.0.1/node_modules/@node-rs/jieba/index.js:226:11)
    at Object.<anonymous> (file:///data/data/com.termux/files/home/.local/share/fount/node_modules/.deno/@node-rs+jieba@2.0.1/node_modules/@node-rs/jieba/index.js:335:17)
    at Object.<anonymous> (file:///data/data/com.termux/files/home/.local/share/fount/node_modules/.deno/@node-rs+jieba@2.0.1/node_modules/@node-rs/jieba/index.js:370:4)
    at Module._compile (node:module:745:34)
    at loadMaybeCjs (node:module:770:10)
    at Object.Module._extensions..js (node:module:755:12)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure in Deno on a glibc Termux Android runner, then inspect @node-rs/jieba/index.js around isMuslFromReport and requireNative, using the reported stack trace as the entry point. Done means the CPU-info error no longer prevents the jieba native binding from loading in that environment.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, deno, node.js, rust
Domain
mobile-dev, operating-systems, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.