-
Notifications
You must be signed in to change notification settings - Fork 33
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
fix!: configuration improvements #58
fix!: configuration improvements #58
Conversation
Breaking changesThe configuration has been changed to facilitate user's understanding of the values. The new possible values for the reward multipliers are as follow:
QA run with the new configurationMeniole#6 (comment) (comments are not evaluated because I burst through the API limits of ChatGpt) |
@gentlementlegen Could you provide a full bot's config? Can't make it run with this one (some config validation errors). |
@rndquu I think the main issue is that the yaml is invalid, it seems the items under |
@gentlementlegen Check this config and this CI run which outputs these errors:
The config is from the readme file. Are those errors expected? |
@rndquu No these errors are not expected. I provided a fix, that hopefully works because my GitHub Actions have been stuck for the past hour, so I cannot test in a real-world use case. |
The
Is it expected for this config? |
@rndquu Yes it is expected because these modules seem to be missing from the configuration, so they are disabled, which is in check with this comment. Maybe the message is misleading. Edit: they seem to be present in the configuration so it is not expected. I think because they are empty they get de-serialized as |
I'm concerned about the above errors because they are caused by the default config provided in the readme file. It is somewhat expected that if you copy a config from the readme file then the plugin should run without any errors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works fine
The errors mentioned here are actually present in the development
branch so they are not caused by this PR. @gentlementlegen perhaps it makes sense to fix those errors in a separate PR.
…ents # Conflicts: # src/issue-activity.ts
d862d53
into
ubiquity-os-marketplace:development
Resolves #46