Known issues

This topic describes the known issues and limitations when working with PulseUno.

Installation and upgrade

Uninstalling or upgrading 20.1 on Windows: Depending on your system's virtual memory, when you attempt to uninstall or upgrade PulseUno 20.1, the following errors may occur:

Unable to load and to prepare the installer in GUI mode.

or

CopyAndModFiles Git data-dir processing error: file does not exist C:\PulseUno\git-server\logback-dimensions-remote-helper.xml

Solution:

  1. Edit the Change PulseUno Installation.lax file in the PulseUno installation directory.

    Default path: C:\Program Files\Micro Focus\PulseUno\Change PulseUno Installation.lax

    Copy code
    lax.nl.java.option.java.heap.size.initial=536870912
    lax.nl.java.option.java.heap.size.max=1073741824
  2. Try uninstalling or upgrading PulseUno again.

Back to top

PulseUno vaults

  • Deploying Maven artifacts: When deploying a Maven artifact with an incorrect password, you may get the "Connection reset by peer" error instead of the "Failed to log in with user name <username>" error.

    When you deploy a Maven artifact with an -X switch, a detailed error message is displayed:

    [DEBUG] Failed to dispatch transfer event 'PUT PROGRESSED <URL> <> <local-path> to org.apache.maven.cli.transfer.ConsoleMavenTransferListener
    java.lang.IllegalArgumentException: progressed file size cannot be greater than size: 696320 > 568158

    This is an issue with Maven, and it may be fixed in a future Maven release.

  • Serena SSO: The PulseUno Vault server is not supported when using Serena SSO.

Back to top

Git functionality

  • Serena SSO/CAC: The PulseUno Git server is not supported when using Serena SSO/CAC. To work with the Git server, choose an authentication scheme other than Serena SSO.

  • Signed commits and server-side merge: Defining a branch policy that enforces signed commits in a particular branch may prevent server-side merges of pull requests to that branch. This behavior is expected, as the server-side merge doesn't have access to your private GPG key to sign commits on your behalf.

    Workaround: Merge locally with a signature and push.

  • Enabling automatic pull request creation after the upgrade: If you had automatic pull request creation enabled for a repository, and you upgraded from PulseUno 20.1, you may need to reset the branch name patterns for pull request creation before making other changes to the repository settings.

    For details, see Configure how pull requests are created.

Back to top