fix(hamqth): the whole-log upload reports itself
It ran into a panel nobody was showing: the button never set showLog, so the tab sat on 'Pick a service' while a 25000-QSO upload came and went. Now it opens the console like every other action here, and the console has something to say: the callsign it is scoped to and how many of the logbook's QSOs that leaves (a two-callsign database sends one of them, which is the whole explanation for a count that looks short), the exported record count and file size, and HamQTH's own reply. Plus the two facts that make the site's own number readable: HamQTH accepts the file and imports it in the BACKGROUND, and it reports what it made of each record by e-mail — never in the reply we get. An operator comparing counts a minute later is not looking at a failure.
This commit is contained in:
@@ -732,8 +732,10 @@ export function QSLManagerPanel({ onEditQSO, actions, paperRequest }: {
|
||||
title={t('qslm.hqFullTitle')}
|
||||
onClick={async () => {
|
||||
if (!window.confirm(t('qslm.hqFullConfirm'))) return;
|
||||
setBusy(true);
|
||||
setLogLines([]);
|
||||
// Same three lines every other action here runs: without
|
||||
// setShowLog the whole upload reported itself into a panel
|
||||
// nobody was showing, and the tab sat on "Pick a service".
|
||||
setLogLines([]); setBusy(true); setLogAction('upload'); setShowLog(true);
|
||||
try { await UploadFullLogHamQTH(); }
|
||||
catch (e: any) { setBusy(false); setLogLines((l) => [...l, String(e?.message ?? e)]); }
|
||||
}}>
|
||||
|
||||
Reference in New Issue
Block a user