Reports

Check out a userscript which highlights deleted posts. GitHub

79620096

Date: 2025-05-13 16:52:27

Score: 0.5

Natty:

Well, it's a true Heisenbug: the bug disappeared when I added logging to the relevant functions! Through a painful ablation process, I determined that the 'fixing' log was:

if let role = appElement.role() { print("Role: \(role)")}

While it's impossible to know what's going on under the hood in Accessibility APIs, this strongly implies that it's a matter of lazy initialization. Adding an observer or reading child elements does not trigger the initialization, but somehow reading the kAXRoleAttribute does. Strangely, reading the kAXTitleAttribute didn't work: there's something special about role. Opening the Accessibility Inspector must also have the same effect.

After reading and printing the role, the kAXSelectedTextChangedNotifications start coming through correctly. Moreover, reading the kAXSelectedTextAttribute on the Application's AXUIElement returns the proper value (instead of nil, before). A whole host of other Accessibility-related logic that was previously broken also started working.

So the fix is simple: just read out the Role attribute. You can store the role as an unused variable if you don't want the print statement. The interpreter won't like it, but hey, you can please some of the people, some of the time.

let role = appElement.role()

For completeness, the 'role()' function in my sample code is a helper function that reads the kAXRoleAttribute, per the popular AXUIElement+Accessors extension pattern:

    func role() -> String? {
        return self.attribute(forAttribute: kAXRoleAttribute as CFString) as? String
    }
    
    func attribute(forAttribute attribute: CFString) -> Any? {
        var value: CFTypeRef?
        let result = AXUIElementCopyAttributeValue(self, attribute, &value)
        if result == .success {
            return value
        } else {
            return nil
        }
    }

Reasons:

Contains signature (1):
Long answer (-1):
Has code block (-0.5):
Self-answer (0.5):
Low reputation (0.5):

Posted by: Tim

79620084

Date: 2025-05-13 16:42:24

Score: 2.5

Natty:

	Azure SQL	Azure Cosmos
Data Model	Relational tables, T-SQL, strong schema, ACID transactions.	Schemaless JSON documents (or MongoDB/Cassandra/Gremlin/Table models); multi-model, vector support.
Scale	“Scale up” (vCores/DTUs) with optional read-scale-out or geo-replicas.	“Scale out” automatically via physical partitions; virtually unlimited throughput & storage.
Consistency	Strict (snapshot, serializable, etc.).	Five tunable levels (Strong → Eventual).
Pricing unit	vCore / DTU / serverless per-second; long-running transactions encouraged.	Request Units (RU/s) for reads, writes & queries; optimize for small atomic operations.
When to pick	OLTP/OLAP apps that need joins, stored procs, mature relational tooling.	Globally distributed, high-throughput, low-latency micro-services, IoT, gaming, personalisation, etc.
Latency & SLA	Single-region HA SLA 99.99 %; write latency measured in ms – tens ms.	Multi-region (reads & writes) SLA 99.999 %; P99 <10 ms reads/writes in region.

1) Build & push to a private ACR

A. Use ACR Tasks (server-side build)

B. Or run docker build & docker push on a self-hosted agent in your VNET

2) Let your Container App actually pull that image

A. Feed it credentials

B. Use a Managed Identity (recommended)

3) DNS & network checklist

TLDR (Summary):

Using match() Function

B. Or run `docker build` & `docker push` on a self-hosted agent in your VNET