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.

Sign up for GitHub

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

Jump to bottom

can't import or sync on openwrt #938

Open
5 tasks done
jenningsloy318 opened this issue Sep 15, 2024 · 8 comments
Open
5 tasks done

can't import or sync on openwrt #938

jenningsloy318 opened this issue Sep 15, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@jenningsloy318
Copy link

Describe the bug

I compile this application on openwrt, it can start up successfully, but when I tried to import opml seeds, the error occured
I compiled it with rust 1.81.0 with node 18.20.4

there is no reactor running, must be called from the context of a Tokio 1.x runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime

Makefile

include $(TOPDIR)/rules.mk
PKG_NAME:=podfetch
PKG_VERSION:=4.7.1
PKG_RELEASE:=1

PKG_BUILD_DEPENDS:=rust node postgresql sqlite3
PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-$(PKG_VERSION)
PKG_INSTALL_DIR=$(PKG_BUILD_DIR)/target
PKG_SOURCE:=v$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=https://github.com/SamTV12345/PodFetch/archive/refs/tags/
PKG_HASH:=9cc859c3c90707d234af4ffc64fbba619a5485fd9002c1619f15aa7ff27cf5ea

PKG_LICENSE:=Apache License 2.0
PKG_LICENSE_FILES:=LICENSE
PKG_MAINTAINER:=Jennings Liu <[email protected]>

PKG_INSTALL:=1
PKG_BUILD_FLAGS:=no-mips16

include $(INCLUDE_DIR)/package.mk
include ../../feeds/packages/lang/rust/rust-package.mk

define Package/podfetch
	SECTION:=utils
	CATEGORY:=Utilities
	TITLE:=PodFetch - A podcast caching application
	DEPENDS:=+libstdcpp +libpq +libsqlite3 +node-npm
endef

define Package/podfetch/description
	A sleek and efficient podcast downloader.
endef


define Build/Prepare
	$(call Build/Prepare/Default)
endef


define Build/Compile
	cd $(PKG_BUILD_DIR)/ui && npm install && npm run build-github
	$(call Build/Compile/Cargo)
endef

define Package/podfetch/install
	$(INSTALL_DIR) $(1)/$(CONFIGURE_PREFIX)/bin/
	$(INSTALL_BIN) $(PKG_INSTALL_DIR)/bin/podfetch $(1)/$(CONFIGURE_PREFIX)/bin/podfetch
	$(INSTALL_DIR) $(1)/etc/podfetch/static
	$(CP) $(PKG_BUILD_DIR)/static/* $(1)/etc/podfetch/static
endef

$(eval $(call BuildPackage,podfetch))

Reproduction

  1. set up the openwrt environment 2. use the makefile to build, currently it will build, but package is not successful, I just copy the binary to execute it

System Info

System:
    OS: Linux 5.15 ImmortalWrt 23.05.2
    CPU: (4) arm64 Cortex-A53
    Memory: 329.83 MB / 983.02 MB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 18.20.4 - /usr/bin/node
    npm: 10.7.0 - /usr/bin/npm

Used Package Manager

npm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.
@SamTV12345
Copy link
Owner

Describe the bug

I compile this application on openwrt, it can start up successfully, but when I tried to import opml seeds, the error occured I compiled it with rust 1.81.0 with node 18.20.4

there is no reactor running, must be called from the context of a Tokio 1.x runtime
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime
thread '<unnamed>' panicked at /home/jenningsl/development/openwrt/openwrt-sdk-23.05.2-mediatek-filogic_gcc-12.3.0_musl.Linux-x86_64/dl/cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/hyper-util-0.1.8/src/client/legacy/connect/dns.rs:122:24:
there is no reactor running, must be called from the context of a Tokio 1.x runtime

Makefile

include $(TOPDIR)/rules.mk
PKG_NAME:=podfetch
PKG_VERSION:=4.7.1
PKG_RELEASE:=1

PKG_BUILD_DEPENDS:=rust node postgresql sqlite3
PKG_BUILD_DIR:=$(BUILD_DIR)/$(PKG_NAME)-$(PKG_VERSION)
PKG_INSTALL_DIR=$(PKG_BUILD_DIR)/target
PKG_SOURCE:=v$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=https://github.com/SamTV12345/PodFetch/archive/refs/tags/
PKG_HASH:=9cc859c3c90707d234af4ffc64fbba619a5485fd9002c1619f15aa7ff27cf5ea

PKG_LICENSE:=Apache License 2.0
PKG_LICENSE_FILES:=LICENSE
PKG_MAINTAINER:=Jennings Liu <[email protected]>

PKG_INSTALL:=1
PKG_BUILD_FLAGS:=no-mips16

include $(INCLUDE_DIR)/package.mk
include ../../feeds/packages/lang/rust/rust-package.mk

define Package/podfetch
	SECTION:=utils
	CATEGORY:=Utilities
	TITLE:=PodFetch - A podcast caching application
	DEPENDS:=+libstdcpp +libpq +libsqlite3 +node-npm
endef

define Package/podfetch/description
	A sleek and efficient podcast downloader.
endef


define Build/Prepare
	$(call Build/Prepare/Default)
endef


define Build/Compile
	cd $(PKG_BUILD_DIR)/ui && npm install && npm run build-github
	$(call Build/Compile/Cargo)
endef

define Package/podfetch/install
	$(INSTALL_DIR) $(1)/$(CONFIGURE_PREFIX)/bin/
	$(INSTALL_BIN) $(PKG_INSTALL_DIR)/bin/podfetch $(1)/$(CONFIGURE_PREFIX)/bin/podfetch
	$(INSTALL_DIR) $(1)/etc/podfetch/static
	$(CP) $(PKG_BUILD_DIR)/static/* $(1)/etc/podfetch/static
endef

$(eval $(call BuildPackage,podfetch))

Reproduction

  1. set up the openwrt environment 2. use the makefile to build, currently it will build, but package is not successful, I just copy the binary to execute it

System Info

System:
    OS: Linux 5.15 ImmortalWrt 23.05.2
    CPU: (4) arm64 Cortex-A53
    Memory: 329.83 MB / 983.02 MB
    Container: Yes
    Shell: 5.2.15 - /bin/bash
  Binaries:
    Node: 18.20.4 - /usr/bin/node
    npm: 10.7.0 - /usr/bin/npm

Used Package Manager

npm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.

I'll debug this tomorrow. I guess this is a PodFetch problem as Rust should compile on OpenWRT.

@SamTV12345 SamTV12345 added the bug Something isn't working label Sep 15, 2024
@jenningsloy318
Copy link
Author

Yes, I compile rust 1.81.0 on openwrt as defult rust in openwrt is 1.73.0, it is really outdated

@SamTV12345
Copy link
Owner

Yes, I compile rust 1.81.0 on openwrt as defult rust in openwrt is 1.73.0, it is really outdated

Has the recent version fixed your errors?

@jenningsloy318
Copy link
Author

no，the app occured this error message is compiled with the latest rust, previous rust can't build

@SamTV12345
Copy link
Owner

Do you have an update? Is it working now on openwrt?

@jenningsloy318
Copy link
Author

no tests recently, i will try this tonight

@SamTV12345
Copy link
Owner

Is there something like a guide on setting up OpenWRT? Would be interesting to test that out.

@jenningsloy318
Copy link
Author

jenningsloy318 commented Jan 22, 2025 •
edited
Loading

@SamTV12345
i simply follow the openwrt official guide. for instance

i also made the config here, you can reference https://github.com/jenningsloy318/cool-packages/blob/main/podfetch/Makefile

today I retried again, found that now previous issue is disappeared, but due to the incomplete build of postgresql on openwrt, it is impossible to link again libpq.a, so I tried to build with following parameter

cargo build  --release  --package podfetch --bin podfetch --features "sqlite"

but it still tried to link against libpq, is it possible only link to sqlite if we choose --features "sqlite"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jenningsloy318 @SamTV12345