Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Filespray::DropZoneFiles no longer reporting errors

Description

Earlier in the 7.12.x series, an invalid NetAddress value resulted in a soapfault with a message claiming the NetAddress seemed invalid (very reasonable).

In the latest 7.12.x branch, the same scenario no longer results in a soapfault, but somehow results in a valid response with seemingly valid Dropzone values filled in (perhaps a default DZ?).

 

FYI

Conclusion

None

Activity

Show:

Gavin Halliday February 11, 2021 at 11:12 AM

 I think it makes sense to reinstate that check - since we have used an alternative work around to produce support blob drop zones.

Separately shouldn't the netAddress and directory be used to filter the list of drop zones that are returned?  This shouldn't be changed for 7.12.x, but would it make sense for 8.0?

 

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Compatibility

Point

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/14568
https://github.com/hpcc-systems/HPCC-Platform/pull/14568

Affects versions

Created February 10, 2021 at 3:53 PM
Updated February 15, 2021 at 1:24 PM
Resolved February 15, 2021 at 1:24 PM

Flag notifications