- Apr 09, 2020
-
-
Henne Vogelsang authored
Display a message based on the context when there are no notifications
-
Victor Pereira authored
Notifications routes
-
Dany Marcoux authored
Closes #9314
-
Victor Pereira authored
Because now the route is under /my/notifications and it's bound to User.session, the test wasn't relevant anymore.
-
Henne Vogelsang authored
Add descendent order in notification
-
Victor Pereira authored
-
Victor Pereira authored
-
Victor Pereira authored
-
Henne Vogelsang authored
Notifications data migration
-
depfu[bot] authored
-
depfu[bot] authored
-
depfu[bot] authored
-
Adrian Schröter authored
[backend] fix dying workers in cleanup_chroot mode
-
depfu[bot] authored
-
Henne Vogelsang authored
[dist] move memcached restart to postun of obs-api package
-
Dany Marcoux authored
Link to Tasks in the Places menu
-
- Apr 08, 2020
-
-
David Kang authored
We always want to see the most recent notifications.
-
Dany Marcoux authored
This implies removing the `All Requests` workaround we had in the `Notifications` page. The link to the `Notifications` page in the top-level navigation is now correctly named.
-
Saray Cabrera Padrón authored
Recent refactoring on notification creation code and database structure left some inconsistent data in the database. To solve the problem, we are going to remove the affected notifications (in the previous data migration) and then we are going to re-generate the notifications (with the current data migration). In this case, we are taking objects existing in the database with certain states and conditions (requests, reviews and comments) and we are creating a notification for each of them. The notifications affected are those related to the events 'ReviewWanted', 'RequestCreate', 'RequestStatechange' and 'CommentForRequest'. This data migration makes use of the recently created NotificationCreator and refactored code. Data migration's tests included. Co-authored-by: David Kang <dkang@suse.com> Co-authored-by: Eduardo Navarro <enavarro@suse.com>
-
Saray Cabrera Padrón authored
Recent refactoring on notification creation code and database structure left some inconsistent data in the database. To solve the problem, with the current data migration we are going to remove the affected notifications as first step. Then, they will be re-generated in the following data migration. Data migration's tests included. Co-authored-by: David Kang <dkang@suse.com> Co-authored-by: Eduardo Navarro <enavarro@suse.com>
-
Rüdiger Oertel authored
where it belongs according to package conventions
-
Sumit Jamgade authored
[backend]pass --ccache param if usecache:packid is present as buildflag
-
Henne Vogelsang authored
Refactor notification's creation code
-
Henne Vogelsang authored
Upgrade OBS to Rails 6.0
-
Saray Cabrera Padrón authored
A few event types used to track, in its payload, the date and time when the event was triggered. The 'when' key was used for this. From now on, all the notifiable event types track this value. Now, when a notification is created, its timestaps fields (create_at and updated_at) are set to the 'when' value. This way, we ensure they have realistic date and time according to the moment when the event happened and not when the notification was created (what usually happens some time later).
-
Adrian Schröter authored
it is racy by design, since a job can get aborted at any time in parallel.
-
Eduardo J authored
[src/api] Update autoprefixer-rails: 9.7.5 → 9.7.6 (patch)
-
depfu[bot] authored
-
- Apr 07, 2020
-
-
Sumit Jamgade authored
this buildflag is to be manually added in project config as BuildFlags: useccache:package-name along with this ccache has be included as BuildRequires in the spec file for ccache to be installable. If buildflag is added but ccache is not present it will result in error
-
Frank Schreiner authored
[dist] fix db:setup in setup-appliance.sh
-
Frank Schreiner authored
fixes problem with rake command db:setup: ``` ** Invoke environment ** Execute strong_migrations:safety_assured rails aborted! Set SAFETY_ASSURED=1 to run this task in production ```
-
Eduardo J authored
[src/api] Update loofah: 2.4.0 → 2.5.0 (minor)
-
Eduardo J authored
[src/api] Update capybara: 3.32.0 → 3.32.1 (patch)
-
depfu[bot] authored
-
depfu[bot] authored
-
- Apr 06, 2020
-
-
Eduardo J authored
[src/api] Update public_suffix: 4.0.3 → 4.0.4 (patch)
-
depfu[bot] authored
-
David Kang authored
Fix import_database script
-
David Kang authored
We need to specify the environment to take the data from options.yml file. Co-authored-by: Saray Cabrera Padrón <scabrerapadron@suse.de>
-
Saray Cabrera Padrón authored
The notification creation code used to be inside the SendEventEmailsJob. The parameters needed to create the notifications were also calculated there (according to the type of event). Now, the creation is isolated in the NotificationCreator service, which keeps the code tidy and makes it accesible from other parts of the code. The calculation of the parameters has been distributed to the corresponding models. They all have now a method called 'parameters_for_notification' to do so. Co-authored-by: David Kang <dkang@suse.com> Co-authored-by: Eduardo Navarro <enavarro@suse.com>
-