Prüft behauptete einmalige mq_notify-Benachrichtigungsanforderungen und deren Re...

{ "body": { "artifact": { "claimed_notifications": [ { "process": 1, "step": 1 } ], "claimed_outcomes": [ "registered", "queued", "queued", "consumed", "consumed", "queued" ], "claimed_queue_sizes": [ 0, 1, 2, 1, 0, 1 ], "claims": { "blocked_receiver": false, "busy_registrations": 0, "notification_requests": 1, "operations": 6, "receiver_handoffs": 0, "registration_active": false, "remaining_messages": 1 }, "initial_messages": 0, "operations": [ { "kind": "register", "process": 1 }, { "kind": "arrive" }, { "kind": "arrive" }, { "kind": "consume" }, { "kind": "consume" }, { "kind": "arrive" } ] } }, "bodyType": "json", "method": "POST", "type": "http" }

{ "example": { "billable": true, "findings": [ { "confidence": 100, "evidence": [], "limits": [ "POSIX.1-2024Issue8 mq_notify DESCRIPTION/ERRORS: one process registration; any repeat registration even bysameprocess EBUSY; notify only empty→nonempty arrival, then remove registration; a blocked receiver consumes arriving message as if queue stayedempty, withoutnotification and registration remains. Own coupled queue/registration/blocked-receiver projection, no OS/IPC/notification SDK calls.", "Closed one synthetic queue and at mostONEblocked receiver. register/deregister model mq_notify; arrive/consume are GIVEN successful queue/message events, block is a GIVEN newly blocked receive fact requiring emptyqueue. Not raw mq_send/receive syscall simulation, capacity/error policy, thread scheduling, actual signal delivery, credentials, queue creation or OSobservations. Initial0..128messages, at most128events.", "Deregister supported only for currently registeredowner; NULL deregistration byother/unregisteredprocess has optional POSIXEINVAL behavior and is outside this fixed profile=>wholeunknown. Morethanoneblocked receiver, blocked fact onnonemptyqueue, empty successfulconsumption, close/fork/exit/sigevmechanisms outside profile=>unknown, no invented behavior.", "Registration onalready nonemptyqueue doesNOTnotify immediately. Arrival satisfying a blockedreceiver preserves armedregistration. After one request registration isfree for rearming, and nonemptyarrivals cannot retrigger. Abstract processIDs positiveuint32, identities only, no realPIDexistence asserted. Notification facts mean normative request/trigger, not observed signal receipt.", "Only bounded counts/booleans output. No process/notificationowner IDs, steps, outcome strings, callerqueue-size arrays, claims or exceptiontext echoed; legal phone-shaped opaque process IDs and falsecontact-valuedoutcomeclaims neverreturned. Exact discrete claim comparisons, no epsilon or rawobject-order dependence." ], "module": "posix-mq-notify-oneshot-arrival-receiver-precedence", "state": "not_observed", "value": { "blocked_receiver": false, "busy_registrations": 0, "claim_mismatches": 0, "claims_match": true, "notification_claim_matches": true, "notification_requests": 1, "operations": 6, "outcome_claim_matches": true, "queue_claim_matches": true, "receiver_handoffs": 0, "registration_active": false, "remaining_messages": 1 }, "warnings": [] } ], "known_count": 1, "scope": { "contact_values_returned": false, "network": false, "supplied_artifact_only": true }, "warnings": [] }, "type": "json" }