Ticket #175 (closed defect: fixed)

Opened 17 months ago

Last modified 17 months ago

Host existence verification fails under certain circumstances

Reported by: tsnorri Owned by: tsnorri
Priority: critical Milestone:
Component: BaseTenAppKit Keywords:
Cc:

Description

Steps to reproduce:

  1. Connect to a database with a partial URI that contains the host name using -connect: and without having the modalWindow outlet's value set.
  2. Observe how the application waits for host verification indefinitely.

When modalWindow isn't set, the host verification callback is set to happen in NSModalPanelRunLoopMode. The run loop doesn't run in this mode, though, because the connection panel hasn't been shown.

Change History

Changed 17 months ago by tsnorri

  • component changed from BaseTen to BaseTen Assistant

Changed 17 months ago by tsnorri

  • component changed from BaseTen Assistant to BaseTenAppKit

Changed 17 months ago by tsnorri

  • status changed from new to closed
  • resolution set to fixed

(In [1057]) Bug fixes - Fixed a bug in BXNetServiceConnector which caused the CFHost's run loop callback to be left pending even after the listener had been deallocated. - Fixed a bug in BXSynchronizedArrayController which caused garbage to be left in an ivar. - BXNetServiceConnector now handles the situation in which an application modal panel is being used and the host is specified in the initial database URI. (Fixes #175.)

Note: See TracTickets for help on using tickets.