Skip to content
This repository has been archived by the owner on Jun 16, 2021. It is now read-only.

Updating a dataport clobbers retention settings. #5

Open
tadpol opened this issue Apr 21, 2015 · 2 comments
Open

Updating a dataport clobbers retention settings. #5

tadpol opened this issue Apr 21, 2015 · 2 comments
Assignees
@tadpol
Labels
bug

Comments

@tadpol
Copy link
Contributor

tadpol commented Apr 21, 2015

Updating a data port clobbers the retention.

when creating a new EXORpcDataportResource if you pass in nil for the retention, it fills it with a default retention (∞,∞). Which means when you then call EXORpcUpdateRequest it clobbers any prior setting with the new one.

What you intended was to leave the prior setting there.
@tadpol tadpol added the bug label Apr 21, 2015
@tadpol tadpol self-assigned this Apr 21, 2015
@tadpol tadpol closed this as completed in fcbd3a0 Apr 21, 2015
@tadpol
Copy link
Contributor Author

tadpol commented Aug 4, 2015

sigh This fix makes creating dataports fail.

@tadpol tadpol reopened this Aug 4, 2015
@tadpol
Copy link
Contributor Author

tadpol commented Aug 4, 2015

This might be a documentation bug.

Or a bug in the expectation of + (EXORpcDataportResource*)dataportWithName:(NSString *)name format:(EXORpcDataportFormat_t)format; in how it sets the retention. Should it set it to nil? or to (∞,∞)?

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

@tadpol tadpol

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tadpol