I got an error from the site:
Unfortunately, something broke on our side. We've been notified automatically.
Can someone help with this?
cc @ngompa - who sent the packet.
thanks @dustymabe - we will work on it.
Anyone that wants to fix this issue?
Hi @jonatoni! I know this issue isn't labeled as new comer but since all the new comers issues were assigned can I give this a go? Thanks!
@shraddhaag sure :)
Metadata Update from @jonatoni: - Issue assigned to shraddhaag
@jonatoni Update: The issue is resolved apart from the usage of fedmsg. It needs to be updated to use fedora-messaging now as fedmsg is deprecated in favour of fedora-messaging. It's out of scope for this issue and thus I'm opening issue #96 for the same. I'll follow up this one, once that is resolved.
Metadata Update from @jflory7: - Assignee reset - Issue marked as depending on: #96 - Issue priority set to: waiting on external (was: awaiting triage) - Issue tagged with: blocked, bug, type - backend, type - fedora-messaging
@shraddhaag Thanks for digging into this. :smile: I marked this ticket as blocked by #96 for now.
Metadata Update from @jflory7: - Issue unmarked as depending on: #96 - Issue untagged with: blocked - Issue assigned to shraddhaag - Issue marked as blocking: #96 - Issue priority set to: waiting on assignee (was: waiting on external) - Issue set to the milestone: Summer Coding 2019: community bonding
I confirmed @dustymabe's original bug in my local environment and validated @shraddhaag's fix in #129. I believe this is fixed. I am closing as complete. :clapper:
This is fixed in master, but it might be a while before this fix makes it to the production site. #111 needs to be solved to improve on deployment strategy, hopefully with Fedora Infra OpenShift later down the line.
master
@shraddhaag Thanks for figuring this out and fixing it! :100: :100:
Metadata Update from @jflory7: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.