tkopecek@redhat.com
- Login: tkopecek@redhat.com
- Email: tkopecek@redhat.com
- Registered on: 02/19/2015
- Last connection: 06/02/2016
Issues
| open | closed | Total | |
|---|---|---|---|
| Assigned issues | 0 | 0 | 0 |
| Reported issues | 0 | 3 | 3 |
Projects
| Project | Roles | Registered on |
|---|---|---|
| Container Support | Private Access | 12/06/2019 |
| Crane | Private Access | 02/19/2015 |
| Debian Support | Private Access | 02/19/2015 |
| Docker Support | Private Access | 02/19/2015 |
| File Support | Private Access | 07/17/2017 |
| Migration Plugin | Private Access | 01/14/2020 |
| Nectar | Private Access | 02/19/2015 |
| OSTree Support | Private Access | 02/19/2015 |
| Packaging | Private Access | 02/19/2015 |
| Pulp | Private Access | 02/19/2015 |
| Puppet Support | Private Access | 02/19/2015 |
| Python Support | Private Access | 02/19/2015 |
| RPM Support | Private Access | 02/19/2015 |
Activity
10/19/2018
10/16/2018
06/02/2016
02/28/2015
-
Doesn't it just ignore non-existent fields? If it is the base of the problem, let's close it as NOTABUG. I'm already using per unit type approach, but was thinking that we can get to lower number of queries with this.
\+ This comment wa... Issue #596: Multiple unit_types in association call causes to fetch everything from source repoWhen I run two almost same copy calls it has very different impact on performance. First (a) is creating correct query on all-content repo. It means it contains filters. If I call second one (b), pulp somehow leave out filters and querie... -
Differrence is not the result - this is really correct - but performance. Running associate per unit_type works appropriately. Running your json with will drastically influence performance. My worst case is importing few new units to rep...· Commented on issue
-
When I run two almost same copy calls it has very different impact on performance. First (a) is creating correct query on all-content repo. It means it contains filters. If I call second one (b), pulp somehow leave out filters and querie...· Closed issue
-
Issue #395 (CLOSED - CURRENTRELEASE): Corrupted data in api call import_upload for rpm causes server-side error with no explanationWhen I try upload to upload correct rpm metadata with corrupted import, I've got only HTTP 500 with no correct error response. Not sure what happened on server and if there is everything reverted correctly. It can happen even in normal p...
Also available in: Atom
.