Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

please tell me where is the “error: 'dict' object has no …” #37795

Merged
merged 2 commits into from
Nov 21, 2016

Conversation

jettero
Copy link
Contributor

@jettero jettero commented Nov 20, 2016

What does this PR do?

Tell me where the "error: 'dict' object has no attribute 'seek'" is so I can go fix it. It makes no attempt to resolve the error, just gives me a hint about what broke.

What issues does this PR fix or reference?

#29028 and possibly others.

Previous Behavior

complain uselessly to the minion log

New Behavior

complain usefully to the minion log

Tests written?

no

Paul Miller and others added 2 commits November 20, 2016 11:07
Also switched the arg order in the format call to make it easier to determine which option is referenced where.
@rallytime rallytime merged commit 3184b65 into saltstack:develop Nov 21, 2016
@jettero jettero deleted the grr-object-has-no-seek branch February 20, 2017 23:09
@defanator
Copy link
Contributor

Is that fix presents in 2016.11.3?

@jettero
Copy link
Contributor Author

jettero commented Mar 29, 2017

@defanator I don't think so. I thought I did my PR against 2016.11, but it looks like the merge went into develop. I think merges in 2016.11 auto merge into dev, but not the other way around.

Yeah, I updated a checkout of 2016.11 and it's not in there. 2016.11.3 is just the tag v2016.11.3; I don't think they're likely to update the tag. If it appeared anywhere, it'd be in 2016.11.4 or greater.

@rallytime
Copy link
Contributor

If this needs to be in the 2016.11.4 release, then the fix needs to be submitted against the 2016.11 branch. I can back-port it right now, but just for future reference. :) Dot releases are on the branch, develop is for the next major feature release.

@rallytime rallytime added the ZZZ[Done]-back-ported-bf RETIRED The pull request has been back-ported to an older branch. label Mar 29, 2017
@jettero
Copy link
Contributor Author

jettero commented Mar 29, 2017

Thanks for the backport @rallytime. I think I must have just submitted the PR against the wrong branch.

@rallytime
Copy link
Contributor

@jettero For sure! No problem at all. I just wanted to make sure we were all on the same page. Thanks again for the fix and discussion.

rallytime pushed a commit that referenced this pull request Mar 29, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ZZZ[Done]-back-ported-bf RETIRED The pull request has been back-ported to an older branch.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants