guacamole-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Jumper (JIRA)" <>
Subject [jira] [Commented] (GUACAMOLE-320) Text attributes may erroneously be set as blank
Date Mon, 03 Jul 2017 17:27:00 GMT


Michael Jumper commented on GUACAMOLE-320:

thanks mike, you are the best.


When the 9.13 gets released i test your change.

If you can test _before_ 0.9.13 gets released, that would be ideal.

I've tested this on my side, of course, so I believe this bug has been addressed, but after
the release is a bad time to find out that a known regression in the release was not fixed
after all. It would mean that the release has to remain buggy, and users would need to wait
for the following release for that bug to be properly fixed.

> Text attributes may erroneously be set as blank
> -----------------------------------------------
>                 Key: GUACAMOLE-320
>                 URL:
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole, guacamole-ext
>    Affects Versions: 0.9.13-incubating
>            Reporter: Karl Fiabeschi
>            Assignee: Michael Jumper
>            Priority: Blocker
>             Fix For: 0.9.13-incubating
> The recently-added text attributes for connections and users can be accidentally set
to a blank value (rather than null) if the value is edited and then deleted. This is particularly
problematic for the new guacd hostname attribute for connections, which causes connections
to fail if set to a blank value:
> {code:none}
> [http-bio-8080-exec-9] DEBUG - Connecting to guacd at :4822.
> {code}
> For fields which internally use {{null}} to represent a blank value, blank values provided
by the interface should be properly translated back to {{null}}, including {{""}}.

This message was sent by Atlassian JIRA

View raw message