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.

Sign up for GitHub

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

Jump to bottom

TypeError: no implicit conversion of Fixnum into String when using mariadb_replication and master_log_pos #43

Closed
sinfomicien opened this issue Jan 12, 2015 · 2 comments
Closed

TypeError: no implicit conversion of Fixnum into String when using mariadb_replication and master_log_pos #43

sinfomicien opened this issue Jan 12, 2015 · 2 comments
Assignees
@sinfomicien

Comments

@sinfomicien
Copy link
Contributor

master_log_pos is declared as an Interger in the resource... But used as a String in the provider. Just had a to_s will resolve the bug.
@sinfomicien sinfomicien self-assigned this Jan 12, 2015
sinfomicien added a commit that referenced this issue Jan 12, 2015
@sinfomicien
Correct issue #43
19642ad 
- TypeError: no implicit conversion of Fixnum into String
sinfomicien added a commit that referenced this issue Jan 12, 2015
@sinfomicien
Merge pull request #45 from sinfomicien/fix-issue-43
fa0651f 
Correct issue #43
@sinfomicien
Copy link
Contributor Author

It's corrected, merge ok

jfwm2 pushed a commit to jfwm2/mariadb that referenced this issue Apr 4, 2017
@lanyonm
add http_addr and add tests for http_port for sous-chefs#43
f25a0ea
jfwm2 pushed a commit to jfwm2/mariadb that referenced this issue Apr 4, 2017
@lanyonm
more ini templating for sous-chefs#43
1551e6a
jfwm2 pushed a commit to jfwm2/mariadb that referenced this issue Apr 4, 2017
@lanyonm
more configs parameterized for sous-chefs#43
c5a5ce2
jfwm2 pushed a commit to jfwm2/mariadb that referenced this issue Apr 4, 2017
@lanyonm
final updates for new attributes, resolves sous-chefs#43
ff953a0
@lock
Copy link

lock bot commented Jul 24, 2018

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jul 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@sinfomicien sinfomicien

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sinfomicien