Hugo

Corrección: ese ejemplo saltearía comprobantes con alguna validación fallida.

Capaz así? ```py for receipt in Receipt.objects.filter( receipt_number__isnull=False, ).exclude( validation__result=ReceiptValidation.RESULT_APPROVED, ): receipt.revalidate() ```

Puede que valga la pena eliminar `ReceiptValidation.RESULT_REJECTED` completamente. Por ahora dejo un issue como recordatorio: https://github.com/WhyNotHugo/django-afip/issues/214 > que opinás de que el revalidate setee receipt_number=None en caso de que no...

Me parece que la opción 1 va bien :+1:

> I edited .local/share/containers/storage/networks/podman.json to include "ipv6_enabled": true, before starting the container to enable IPv6. Connections are now received by podman, but immediately dropped, and never reach the container. Note...

@sbrivio-rh Nope: ```con > podman run --rm -it --publish 8001:8001 fedora python3 -m http.server -b ::1 8001 Serving HTTP on ::1 port 8001 (http://[::1]:8001/) ... ``` ```con > curl 'http://[::1]:8001/'...

> Pasta only uses ipv6 when the host has "public" ipv6 routes, you can easily test what pasta by running it interactively: I don't really understand how public ips addresses...

Apparently my router was in some bogus state and had no public IPv6. I restarted it and now I have a public IPv6. The requirements is still a problem: sometimes...

The address on the host can change during the lifetime of the container. If you want to avoid NAT and inherit the same IP on the container, then you're going...

@Luap99 Yes, this is still an issue. To summarise, if the host doesn't have a publicly routable IPv6 address when a container is started, the container cannot be reached from...