globus_xio...ver_errors(3)

✨ NAME ✨

globus_xio_udp_driver_errors — Error Types 💖

ok so basically: Error Types. that's the whole vibe bestie, this page is a lil glossary of the errors the UDP driver can throw at u 🫶

---

🌸 SYNOPSIS 🌸

Enumerations

enum globus_xio_udp_error_type_t {
    GLOBUS_XIO_UDP_ERROR_NO_ADDRS,
    GLOBUS_XIO_UDP_ERROR_SHORT_WRITE
};

---

🦋 Detailed Description 🦋

Error Types. ✨

ngl the UDP driver is like so close to the system code, they're basically holding hands 💅 so most of the errors it reports to u are just straight-up converted from the system errno. no cap.

but the exceptions — the lil glow-ups that are not just errno in a trench coat — are:

• GLOBUS_XIO_ERROR_COMMAND
• GLOBUS_XIO_ERROR_CONTACT_STRING
• GLOBUS_XIO_ERROR_CANCELED
• GLOBUS_XIO_UDP_ERROR_NO_ADDRS
• GLOBUS_XIO_UDP_ERROR_SHORT_WRITE

See also 👀

• globus_xio_driver_error_match()
• globus_error_errno_match()

---

🎀 Enumeration Type Documentation 🎀

enum globus_xio_udp_error_type_t

UDP driver specific error types 🌈 — the ones that are uniquely, iconically this driver's own.

Enumerator

• GLOBUS_XIO_UDP_ERROR_NO_ADDRS — it's giving "couldn't find anything" 😭 this one means that no IPv4/6 compatible sockets could be resolved for the specified hostname. literally nothing to connect to, bestie.
• GLOBUS_XIO_UDP_ERROR_SHORT_WRITE — this one means that a write of the full buffer failed 💀 and the vibe check here is: u possibly need to increase the send buffer size. yeah. the buffer wasn't buffering. 🔥

---

👑 Author 👑

Generated automatically by Doxygen for globus_xio from the source code. so like, not a human wrote this, it's a robot's lil autograph 🤖💖

---

and that's the whole page bestie!! 🌟 this came from the globus_xio library, Version 6.6, and the man page itself goes by globus_xio...ver_errors(3). slay, go forth and debug 💅✨🫶