Skip to content

[Bug][Config-UI] React error #31 when creating a new connection #8969

Closed as not planned

Description

@pegedece

Search before asking

  • I had searched in the issues and found no similar issues.

What happened

When attempting to create a new connection from the Config UI in Apache DevLake v1.0.3-beta13, the UI immediately throws a React error before the connection form can be used normally.

The error is not specific to Bitbucket. The same behavior is observed when creating different connection types.

The browser console shows:

Image

Minified React error #31

with additional details indicating that React is attempting to render an object containing properties such as:

{
_reactName,
_targetInst,
type,
nativeEvent,
target,
currentTarget,
...
}

This prevents connection creation from the web interface.

The issue was observed both in an upgraded installation and in a completely fresh installation.

What do you expect to happen

Clicking "Create New" should open the connection creation workflow and allow users to configure and save the connection.

How to reproduce

  1. Deploy Apache DevLake v1.0.3-beta13.
  2. Open the Config UI.
  3. Navigate to Connections.
  4. Select any connection type.
  5. Click "Create New".
  6. Observe that the UI immediately throws a React error.

Browser console shows:

Minified React error #31

The issue is reproducible without creating a connection and without interacting with the target service.

Anything else

  1. Upgraded installation

    • Apache DevLake v1.0.3-beta13
    • Upgraded from v1.0.3-beta12
    • Podman on RHEL 9
  2. Fresh installation

    • Apache DevLake v1.0.3-beta13
    • Podman on RHEL 9
    • New database

The issue is reproducible in both environments.

Firefox 152.0.3

Version

v1.0.3-beta13

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. klesh commented on Jul 2, 2026

    @klesh
    Contributor

    fixed in #8952

  2. github-actions commented on Sep 1, 2026

    @github-actions
    Contributor

    This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

  3. github-actions commented on Sep 9, 2026

    @github-actions
    Contributor

    This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions