'Upload OPML'-button grayed out

d3545t3r commented 1 year ago

Describe the bug

Hello,

tried to import my podcasts from my Android app "Podcast Addict".

Podfetch shows

"The following file will be uploaded: PodcastAddict_OPML_export_20230501_055429.opml",

but the "Upload OPML"-button is grayed out, so I can't do it as nothing happens.

Same issue with OPML-files from other sources.

Am I doing Something wrong?

Reproduction

happens with every version of podfetch

System Info

System:
    OS: Linux 5.15 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (4) arm ARMv7 Processor rev 5 (v7l)
    Memory: 394.19 MB / 999.02 MB
    Container: Yes
    Shell: 5.1.4 - /bin/bash

Used Package Manager

n/a

Validations

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

SamTV12345 commented 1 year ago

Thanks for the issue. Glad you solved the issue. May I ask which steps you took to make the opml upload work?

tehniemer commented 1 year ago

@d3545t3r I'm having the same issue, what did you do to solve it?

@SamTV12345 mind reopening this until a solution is found?

tehniemer commented 1 year ago

@SamTV12345 Here's some more info, every time I try to click the button this shows up in the logs.

2023-05-01T12:00:15.160813992Z thread 'tokio-runtime-worker' panicked at 'Error parsing feed: InvalidStartTag', src/controllers/podcast_controller.rs:450:52

SamTV12345 commented 1 year ago

Could you please post your opml file?

d3545t3r commented 1 year ago

Unfortunately, the problem still appears.

I have the following error messages in my logs.

0:   0xeb71cc - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h0d267d3ddd434858
   1:   0xedcf30 - core::fmt::write::h7253a9d64981ec1f
   2:   0xeaf2d8 - std::io::Write::write_fmt::h6d19611cef50d2cb
   3:   0xeb8ca4 - std::panicking::default_hook::{{closure}}::h7a778041ee0c25b0
   4:   0xeb87fc - std::panicking::default_hook::h00d2a169ed3329c4
   5:   0xeb9478 - std::panicking::rust_panic_with_hook::h233948492a2daf92
   6:   0xeb91bc - std::panicking::begin_panic_handler::{{closure}}::h0594b0f8e73c9f79
   7:   0xeb779c - std::sys_common::backtrace::__rust_end_short_backtrace::h86679e0e7e726aea
   8:   0xeb8f70 - rust_begin_unwind
   9:   0x4fc71c - core::panicking::panic_fmt::he71af873a4d08fbd
  10:   0x4fc848 - core::result::unwrap_failed::hf16f916d1dba6e7a
  11:   0x72564c - podfetch::service::file_service::FileService::create_podcast_directory_exists::h4f284fa8d8d8dd92
  12:   0x639f4c - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h8498214aa4335a87
  13:   0x6302b8 - <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h5cae496333ed03c2
  14:   0x55bc38 - <tokio::runtime::blocking::task::BlockingTask<T> as core::future::future::Future>::poll::hd252c75151c2aa9f
  15:   0x7a9a50 - tokio::runtime::task::core::Core<T,S>::poll::h944c6fd32ccb4028
  16:   0x5b1788 - tokio::runtime::task::harness::Harness<T,S>::poll::ha9e0549300636eb6
  17:   0xd44adc - tokio::runtime::blocking::pool::Inner::run::hfface49d139e479e
  18:   0xd3f270 - std::sys_common::backtrace::__rust_begin_short_backtrace::h45cd0b36965f8d2e
  19:   0xd4089c - core::ops::function::FnOnce::call_once{{vtable.shim}}::hed19b19589300585
  20:   0xebd0fc - std::sys::unix::thread::Thread::new::thread_start::hc48028146cb4213a

SamTV12345 commented 1 year ago

Could you please checkout samuel19982/podfetch:develop and pull the image? Does that solve the import of your opml file? Otherwise I need to do some local testing. The feature works but there were some bad file names that were not replaced.

d3545t3r commented 1 year ago

Would like to do it, but pulling

samuel19982/podfetch:develop

only gives me a linux/amd64 image, which I can't test on my arm machine.

Maybe someone else can test it?

SamTV12345 commented 1 year ago

Sorry the dev tag is better suitable in that case. The latest dev image should contain the changes.

d3545t3r commented 1 year ago

the build from

Mon, 01 May 2023 20:53:33 +0000

seems to work (at least for ARM).

Now I have problems with importing some podcasts, but this seems to be a different problem from my point of view and I will open a new ticket for that.

SamTV12345 / PodFetch