Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[Bug] test_send_email test fails with 404 when testing email from UI works

Chiusa
  • Qualcosa non va?
#751 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@ian-flores ci sta già lavorando.

Dal 2/10/2026.

  • #760 di @ian-flores — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
70/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
api, testing

Direzione di ricerca

Start with vip/clients/connect.py at send_test_email and the failing test in vip_tests/connect/test_email.py. Compare the client request with the Connect admin UI request described in the issue, then run vip verify with the test_send_email filter against Connect 2026.09.0. Done means the test sends email successfully without a 404.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug
VIP version

2026.9.3

Affected area

Connect tests

What happened?

test_send_email fails with a 404 - seemingly because ConnectClient.send_test_email uses
__api__/v1/tasks/send-test-email, which I've been unable to find in Connect 2026.09.0.

Email delivery works: the Connect admin UI's "Send Test Email" button succeeds
on the same server, and the email arrives. The UI test button seems to use GET __api__/server_settings/mail/test

What did you expect to happen?

Email to be sent

Steps to reproduce
> vip verify --config vip.toml --interactive-auth --filter "test_send_email"
>>> Reusing cached auth session from <home>\.vip-auth-cache.json
======================== test session starts ========================
2 workers [1 item]     skipped
scheduling tests via LoadGroupScheduling

vip_tests/connect/test_email.py::test_send_email FAILED        [100%]

============================= FAILURES ==============================
__________________________ test_send_email __________________________
test_send_email: an unexpected error occurred: httpx.HTTPStatusError: Client error '404 Not Found' for url 'https://connect.example.com/__api__/v1/tasks/send-test-email' For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/404
----------------------- Captured log teardown -----------------------
WARNING  vip_tests.conftest:conftest.py:110 end-of-run Connect content sweep could not reach the tag API
Traceback (most recent call last):
  File "<site-packages>\vip\clients\connect.py", line 281, in list_vip_content
    return resp.json().get("results", [])
           ^^^^^^^^^^^^^^^
AttributeError: 'list' object has no attribute 'get'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "<site-packages>\vip_tests\conftest.py", line 108, in _connect_end_of_run_sweep
    connect_client.cleanup_vip_content()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "<site-packages>\vip\clients\connect.py", line 292, in cleanup_vip_content
    guids = [item.get("guid") for item in self.list_vip_content()]
                                          ~~~~~~~~~~~~~~~~~~~~~^^
  File "<site-packages>\vip\clients\connect.py", line 283, in list_vip_content
    raise ProductUnreachableError(f"could not list VIP-tagged content: {exc}") from exc
vip.errors.ProductUnreachableError: could not list VIP-tagged content: 'list' object has no attribute 'get'
=================== 1 failed, 1 skipped in 6.06s ====================
Relevant logs or output
vip_tests/connect/test_email.py::test_send_email FAILED

test_send_email: an unexpected error occurred: httpx.HTTPStatusError: Client error
'404 Not Found' for url 'https://connect.example.com/__api__/v1/tasks/send-test-email'

vip/clients/connect.py:513: in send_test_email
    resp.raise_for_status()
E   httpx.HTTPStatusError: Client error '404 Not Found' for url
    'https://connect.example.com/__api__/v1/tasks/send-test-email'
Environment
  • VIP 2026.9.3
  • Python 3.14.3
  • Windows 11 (10.0.26200)
  • Connect 2026.09.0
Lingua principale
Python
Stelle
8
Fork
1
Merge medio
1g 8h
PR unite (30g)
51

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di posit-dev/vip

Tutte le issue di posit-dev/vip

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.