Resolved Issues#

Table 76 Release Summary#

Release Date

Description

2025-02-13

Nonlinear Solver: Some Problems Delayed

2024-12-11

Some Customers Could Not Log In to the Leap Service

2024-12-05

Leap Admin: Organization Admin Role Temporarily Unavailable

2024-11-28

Advantage_system4.1: Temporarily Degraded Solution Quality

2024-11-27

Advantage_system4.1: Temporarily Degraded Solution Quality

2024-10-28

QPU Solvers: Solution Quality for Fast Anneal Degraded

2024-10-21

Certain Problems Submitted to QPU Solvers Failed with HTTP 403

2024-10-02

Nonlinear-Program Solver Did Not Reject Invalid Models

Advantage_system4.1: Temporarily Degraded Solution Quality

Solver Parameters and Properties Were Not Displayed for Some Users on the Dashboard

2024-08-07

Error Received When Failing to Join Project

2024-07-26

Advantage_system5.4: Degraded Solution Quality

2024-07-16

Retrieving SAPI Tokens via the Leap Service’s API Failed

2024-07-10

Leap Admin: Global Search on Members Could Have Failed

Leap Admin’s “Export to JSON” Did Not Download Sample Sets

2024-06-12

Advantage2_prototype2.3: Performance Temporarily Degraded

2024-05-15

Some Administrators Could Not Access Leap Admin

2024-05-08

Advantage2_prototype2.3 Solver: Some Submissions May Have Had Degraded Solution Quality

2024-05-01

Older Codespaces May Have Required Rebuild

Advantage2_prototype2.3 Solver: Unstable Behavior at Short Fast-Anneal Times

2024-04-18

Could Not Retrieve a SAPI Token via the Leap Service’s API

2024-04-17

Sometimes Access Renewal Dates Were Outdated

2025-02-13 Release#

Nonlinear Solver: Some Problems Delayed#

On 2025-02-10, some problems submitted to the Nonlinear solver were stuck in pending from approximately 04:03 AM to 09:51 AM Pacific time, at which time they were processed.

2024-12-11 Release#

Some Customers Could Not Log In to the Leap Service#

From 2024-12-03 at 1:00 PM Pacific time to 2024-12-05 at 5:52 PM, some customers could not log in to the Leap service; API access was unaffected.

2024-12-05 Release#

Leap Admin: Organization Admin Role Temporarily Unavailable#

The Organization Admin role in Leap Admin was temporarily unavailable from 2024-12-03 at 1:10 PM Pacific time to 4:30 PM the next day.

2024-11-28 Release#

Advantage_system4.1: Temporarily Degraded Solution Quality#

The Leap service’s Advantage_system4.1 QPU solver’s performance was degraded on 2024-11-27 from 2:54 PM to 3:14 PM Pacific time. Affected users have been contacted by D‑Wave.

2024-11-27 Release#

Advantage_system4.1: Temporarily Degraded Solution Quality#

The Leap service’s Advantage_system4.1 QPU solver’s performance was degraded on 2024-11-23 from 5:50 PM to 6:26 PM Pacific time. Affected users have been contacted by D‑Wave.

2024-10-28 Release#

QPU Solvers: Solution Quality for Fast Anneal Degraded#

Due to a software issue, performance of the fast-anneal feature on QPU solvers in the Leap service was degraded from 2024-10-02 to 2024-10-28. Affected users have been contacted by D‑Wave.

2024-10-21 Release#

Certain Problems Submitted to QPU Solvers Failed with HTTP 403#

Certain problems submitted to QPU solvers failed with the 403 Forbidden HTTP status code. This issue was due to overzealous firewall rules in the Leap service.

Compression on problem upload for QPU solvers, which is only available for Ocean SDK version 8 or greater and is enabled by default, made this issue more likely to occur.

2024-10-02 Release#

Nonlinear-Program Solver Did Not Reject Invalid Models#

The dwave-optimization package version 0.3.0 or earlier allowed models that attempted to access an array outside the array’s index range. From 2024-09-18 to 2024-10-02, the nonlinear-program solver, hybrid_nonlinear_program_version1, did not properly reject problems with such models. Affected users have been contacted by D‑Wave.

Advantage_system4.1: Temporarily Degraded Solution Quality#

The Leap service’s Advantage_system4.1 QPU solver’s performance was degraded from 2024-09-24 at 11:41 PM Pacific time to 12:12 AM the next morning. Affected users have been contacted by D‑Wave.

Solver Parameters and Properties Were Not Displayed for Some Users on the Dashboard#

For some users, clicking a solver in the Solvers section on the dashboard did not display the solver’s properties and parameters; instead, some text that included N/A was displayed.

2024-08-07 Release#

Error Received When Failing to Join Project#

When invited to join a project, a very small number of existing Leap service users received an error when clicking the email’s project acceptance link. Affected users have been contacted by D‑Wave.

2024-07-26 Release#

Advantage_system5.4: Degraded Solution Quality#

A small number of problems submitted to the Advantage_system5.4 solver from 2024-07-10 to 2024-07-24 may have experienced degraded solution quality. Affected users have been contacted by D‑Wave.

2024-07-16 Release#

Retrieving SAPI Tokens via the Leap Service’s API Failed#

From 2024-07-10 to 2024-07-16, attempting to retrieve a SAPI token via the Leap service’s API (for example, while configuring access to solvers in the Leap service from a Codespace) failed with an HTTP 404 error.

2024-07-10 Release#

Leap Admin: Global Search on Members Could Have Failed#

When an organization administrator typed a user’s name in the global-search bar and then clicked on a result, an HTTP 404 error was displayed instead of the user profile.

Leap Admin’s “Export to JSON” Did Not Download Sample Sets#

Some Leap service administrators may have received an error when attempting to export a solver’s returned sample set to JSON format.

2024-06-12 Release#

Advantage2_prototype2.3: Performance Temporarily Degraded#

The Advantage2_prototype2.3 solver’s performance was degraded from 2024-06-03 at 2:45 PM Pacific time to 8:05 AM the next morning. Problems submitted using the fast-anneal protocol with anneals faster than 300 ns were affected.

2024-05-15 Release#

Some Administrators Could Not Access Leap Admin#

From 2024-05-01 to 2024-05-02, some administrators were automatically logged out of their Leap service accounts when attempting to access Leap Admin.

2024-05-08 Release#

Advantage2_prototype2.3 Solver: Some Submissions May Have Had Degraded Solution Quality#

From 2024-05-01 to 2024-05-08, some problems submitted to the Advantage2_prototype2.3 solver might have experienced a small degradation in solution quality resulting from a now-corrected, minor shift in the inductance of about 7% of the processor’s qubits.

For more information, contact D‑Wave Customer Support.

2024-05-01 Release#

Older Codespaces May Have Required Rebuild#

Due to a backwards-incompatible upgrade to the Solver API introduced on March 20, 2024, upgrading the Ocean SDK to version 6.9.0 or later was recommended if planning to use the dwave auth login CLI command.

Codespaces created from a D‑Wave GitHub repository before February 26, 2024, requiring reauthorization in the Leap service may have encountered an issue when attempting to log back into an existing Codespace after logging out. This issue could be resolved by launching the Codespace and running the following command in the VS Code command palette to rebuild the workspace with the latest Ocean SDK:

Codespaces: Full Rebuild Container

Advantage2_prototype2.3 Solver: Unstable Behavior at Short Fast-Anneal Times#

For the Advantage2_prototype2.3 solver, unstable behavior occurs when fast-anneal times are below about 5 ns; however, this unstable behavior has no effect on problem submissions because the lower limit for anneal time, as returned by the fast_anneal_time_range solver property, is now 5 ns.

2024-04-18 Release#

Could Not Retrieve a SAPI Token via the Leap Service’s API#

Due to an issue affecting OAuth 2.0 access to some of the Leap service’s API endpoints, OAuth clients were unable to fetch SAPI tokens or the list of projects from the Leap service.

The issue manifested in the Ocean CLI when configuring access to solvers in the Leap service, for example when running dwave config create --auto-token or dwave leap project token.

You may have encountered this issue in your GitHub Codespace with the Ocean SDK installed. For example, when running dwave auth login --oob && dwave config create --auto-token, the Ocean software’s CLI authorization command suggested for D-Wave examples opened in your GitHub Codespace, failed with error message Failed to fetch SAPI token from Leap API.

2024-04-17 Release#

Sometimes Access Renewal Dates Were Outdated#

If a project’s Anniversary Date changed, sometimes the Access Renewal date as shown on the dashboard was not updated to the project’s new Anniversary Date.