#5576 test_dir feature for resolver

**Is your feature request related to a problem? Please describe.**
On the legacy runner was different approach in listing avocado tests. The avocado had a default test directory under `datadir.paths.test_dir` variable and it was possible to run `avocado list` command to list all tests from this default directory. When we moved from the legacy architecture to the resolver architecture, we removed this functionality. Now users have to specify the path to the test directory in the avocado command like this `avocado list examples/tests/`

When you run many different sets of tests in one avocado job, it will save time to specific the path to the test directory where the tests are stored. This feature will bring back the `datadir.paths.test_dir` feature from the legacy architecture.

**Describe the solution you'd like**
```
$ cat /root/.config/avocado/avocado.conf
[datadir.paths]
test_dir = /avocado_dir/examples/tests

$ avocado list
avocado-instrumented examples/tests/abort.py:AbortTest.test
avocado-instrumented examples/tests/assert.py:Assert.test_assert_raises
avocado-instrumented examples/tests/assert.py:Assert.test_fails_to_raise
avocado-instrumented examples/tests/assets.py:Hello.test_gpg_signature
avocado-instrumented examples/tests/assets.py:Hello.test_build_run
avocado-instrumented examples/tests/cabort.py:CAbort.test
avocado-instrumented examples/tests/cancel_on_exception.py:CancelOnException.test
avocado-instrumented examples/tests/cancel_test.py:CancelTest.test_iperf
avocado-instrumented examples/tests/cancel_test.py:CancelTest.test_gcc
avocado-instrumented examples/tests/cancelonsetup.py:CancelOnSetupTest.test_wont_be_executed
avocado-instrumented examples/tests/canceltest.py:CancelTest.test
avocado-instrumented examples/tests/cit_parameters.py:CitParameters.test
exec-test            examples/tests/custom_env_variable.sh
avocado-instrumented examples/tests/datadir.py:DataDirTest.test
avocado-instrumented examples/tests/dependency_ansible.py:FileByAnsible.test
...
```
Job API usage:

```
$ cat job.py
#!/usr/bin/env python3

import sys

from avocado.core.job import Job
from avocado.core.suite import TestSuite

job_config = {
    "datadir.paths.test_dir": "examples/tests",
}

suite_pass_config = {
    "resolver.references": ["/bin/true", "passtest.py"],
}

suite_fail_config = {
    "resolver.references": ["failtest.py"],
}

with Job(
    config=job_config,
    test_suites=[
        TestSuite.from_config(suite_pass_config, name="pass"),
        TestSuite.from_config(suite_fail_config, name="fail"),
    ]
) as j:
    sys.exit(j.run())

$ python job.py
JOB ID     : af6e3bf63665ecf3a9d1e1b3a1111fe66ec7b76e
JOB LOG    : /home/janrichter/avocado/job-results/job-2023-01-12T16.00-af6e3bf/job.log
 (pass-2/2) examples/tests/passtest.py:PassTest.test: STARTED
 (pass-1/2) /bin/true: STARTED
 (pass-1/2) /bin/true: PASS (0.01 s)
 (pass-2/2) examples/tests/passtest.py:PassTest.test: PASS (0.02 s)
 (fail-1/1) examples/tests/failtest.py:FailTest.test: STARTED
 (fail-1/1) examples/tests/failtest.py:FailTest.test: FAIL: This test is supposed to fail (0.04 s)
RESULTS    : PASS 2 | ERROR 0 | FAIL 1 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0
JOB HTML   : /home/janrichter/avocado/job-results/job-2023-01-12T16.00-af6e3bf/results.html
JOB TIME   : 2.56 s
```

**Additional information**
The legacy `datadir.paths.test_dir` variable still has some leftovers in code and documentation. Part of this issue should be removed unnecessary legacy code of test_dir feature.

This issue is based on #5571

Status : open

Created 2023-01-12T15:09:33+00:00, updated 2023-01-12T15:09:33+00:00

Labels: enhancement refactoring

#5285 Limit line-length to 79 characters

In the moment of writing this issue, the master branch has 1044 lines longer than 79 characters.

 This ticket is about removing all these long lines and then enabling the corresponding `pylint` check C0301 and `max-line-length` option in `pylint` as follows:

```diff
--- a/.pylintrc
+++ b/.pylintrc
@@ -81,7 +81,6 @@ disable=W0212,
   C0200,
   C0201,
   C0209,
-  C0301,
   C0302,
   C0321,
   C0325,
@@ -382,7 +381,7 @@ indent-after-paren=4
 indent-string='    '
 
 # Maximum number of characters on a single line.
-max-line-length=100
+max-line-length=79
 
 # Maximum number of lines in a module.
 max-module-lines=1000
```

Status : open

Created 2022-03-15T11:28:07+00:00, updated 2022-03-16T14:25:56+00:00

#5270 fix bandit checks

Bandit is a tool designed to find common security issues in Python code <https://github.com/PyCQA/bandit>.
It can be installed with `pip install bandit` and it can run in avocado with `bandit -r -lll .`

At this moment, the metrics are:

```
...
Run metrics:
        Total issues (by severity):
                Undefined: 0.0
                Low: 85.0
                Medium: 97.0
                High: 4.0
        Total issues (by confidence):
                Undefined: 0.0
                Low: 57.0
                Medium: 16.0
                High: 113.0

```

It would be nice to see if the medium and high issues can be solved. 
Note that there is a PR already in progress with some fixes at https://github.com/avocado-framework/avocado/pull/5256

Status : open

Created 2022-03-03T15:11:21+00:00, updated 2022-03-03T15:11:21+00:00

Labels: enhancement

#5229 Fix junit output file field: file is empty

**Describe the bug**
Some CIs (like Gitlab) is parsing the xml test report for listing the tests in a table. There we have some fields: "name", "file", "classname" and "file". Currently we are not using the "file" field and using the name for that.

**Steps to reproduce**
Visit the following pipeline result, and check that the filename column is empty:

https://gitlab.com/qemu-project/qemu/-/pipelines/449494631/test_report

**Expected behavior**
Here another pipeline with the file properly set:

https://gitlab.com/beraldoleal/foo-bar-test/-/pipelines/450464128/test_report

**Current behavior**

https://gitlab.com/qemu-project/qemu/-/pipelines/449494631/test_report

**System information (please complete the following information):**
 - OS: fedora 34
 - Avocado version: master branch
 - Avocado installation method: pip, rpm, github ? github.
 - 
**Additional information**

Status : open

Created 2022-01-18T14:39:53+00:00, updated 2024-01-08T13:35:38+00:00

Assigned to richtja

#4727 Finish the work on messages in base runners

In #4662 the helper methods for sending messages was introduced. Unfortunately, they couldn't be used inside runners from `avocado/core/nrunner.py` because of the problem with distribution of runners with dependencies #4336. When the #4336 will be solved, we should finish the work on #4662 and use messaging methods in `avocado/core/nrunner.py`

Status : open

Created 2021-06-24T13:37:43+00:00, updated 2021-06-24T13:37:43+00:00

Labels: nrunner

#4300 Improve redability when acquiring parent directory path

Maybe we could improve the readability on occasions where we obtain the parent path using: 

``` python
BASEDIR = os.path.dirname(os.path.abspath(__file__))
BASEDIR = os.path.abspath(os.path.join(BASEDIR, os.path.pardir))
```
Based on the discussion in #4289 and looking on how the `os.path` module is used in the project, one possible alternative could be:

``` python
BASEDIR = os.path.dirname(os.path.dirname(os.path.abspath(__file__)))
```
The above is also used in `selftests/check_tmp_dirs`

Status : open

Created 2020-11-11T15:48:56+00:00, updated 2020-11-12T10:35:22+00:00

Labels: pri:low

#3483 APIs separation: avocado/utils has references to avocado

We recently fixed all imports to remove references to the core and testing APIs from avocado/utils (see https://trello.com/c/QXEu5TXh/387-test-api-one-more-round-of-scope-isolation).

But there's still *knowledge* about avocado in the utils module, something that should not happen. This knowledge shows a dependency, which becomes circular. The issues I've found:

 * `logging.getLogger('avocado....')`: One alternative could be the use of a default logger (`logging.getLogger()`) in the utils modules, leaving the responsibility of setting different defaults to the module which imported it. If multiple loggers are necessary, use a generic name and document it as part of the module (utils) API, so the modules up in the hierarchy have knowledge about the expectation of the included module, not the other way around.

 * Variable names: several variables, prefixes for temporary files and documentation make references to avocado. Results from grep:
```
data_factory.py:Generate data useful for the avocado framework and tests themselves.
data_factory.py:        path = tempfile.mkdtemp(prefix='avocado-make-dir-and-populate',
data_structures.py:avocado core code or plugins.
gdb.py:        prefix = 'avocado_gdbserver_%s_' % self.port
path.py:    :raise: :class:`avocado.utils.path.CmdNotFoundError` in case the
process.py:#: inferior process exit before before avocado resumed the debugger
process.py:                                     'debugger before avocado was resumed. '
process.py:                                     'skipped. Please let avocado finish the '
process.py:    Returns :attr:`avocado.gdb.GDB.DEFAULT_BREAK` as the default breakpoint
script.py:    def __init__(self, name, content, prefix='avocado_script', mode=0775):
script.py:def make_temp_script(name, content, prefix='avocado_script', mode=0775):
script.py:    :param prefix: the directory prefix Default to 'avocado_script'.
software_manager.py:        self.repo_file_path = '/etc/yum.repos.d/avocado-managed.repo'
software_manager.py:        self.repo_file_path = '/etc/apt/sources.list.d/avocado.list'
```
 * At least one import is using `avocado.utils` instead of `.`.

**Original Trello (deprecated) card:** https://trello.com/c/DxqrCvPr/446-apis-separation-avocado-utils-has-references-to-avocado

**Related:**

The `avocado.utils` are supposed to be avocado-independent, but they are using `avocado.test` logger. We should follow the guidelines and use `__file__` instead, which should give us `avocado.utils.$file` logger. That itself should go to `avocado.test` as it's propagated to the root logger, but it'd be probably better to add the `avocado.utils` logger to test too.

**Original Trello (deprecated) card:** https://trello.com/c/4QyUgWsW/720-get-rid-of-avocadotest-loggers-from-avocadoutils

Status : open

Created 2020-01-09T17:50:38+00:00, updated 2020-01-09T17:55:14+00:00

Labels: refactoring

#3479 avocado.utils.partition: should not assume process will be killed

The current implementation of forceful umount, sends a signal to the process and considers that it's enough to have the process killed.  This is not always the case.

Let's fix the code to attempt to behave correctly, and signal the forceful umount failure appropriately.

Status : open

Created 2020-01-08T18:37:16+00:00, updated 2020-01-08T18:37:16+00:00

Labels: optional plugins / utils / contrib

#3474 Evaluate whether selftests should run with C.UTF-8 locale instead

We're setting `en_US.UTF-8` when running the selftests, but maybe the right thing to do is to set `C.UTF-8`.

References:

* https://github.com/avocado-framework/avocado/issues/2978

* https://fedoraproject.org/wiki/Changes/Remove_glibc-langpacks-all_from_buildroot

Status : open

Created 2020-01-08T18:20:19+00:00, updated 2020-01-08T18:20:19+00:00

#3472 Advertise ourselves in: https://wiki.python.org/moin/PythonTestingToolsTaxonomy

Status : open

Created 2020-01-08T18:16:40+00:00, updated 2020-01-08T18:16:40+00:00

Labels: documentation

#3471 Experiment with mypy

From http://mypy-lang.org/:

"Mypy is an optional static type checker for Python that aims to combine the benefits of dynamic (or "duck") typing and static typing. Mypy combines the expressive power and convenience of Python with a powerful type system and compile-time type checking. Mypy type checks standard Python programs; run them using any Python VM with basically no runtime overhead."

Probably the best course of action, before experimenting with it, would be to have an inspektor plugin.

Status : open

Created 2020-01-08T18:15:29+00:00, updated 2020-01-08T18:15:29+00:00

#1448 Get release date with API

If you visit a project on release-monitoring.org, you see the list of all versions. This list contains the date, on which the version was released. But I have not found a way to get this date with the API in the [documentation](https://release-monitoring.org/static/docs/api.html). Could this be added?

Status : open

Created 2022-08-30T10:44:17+00:00, updated 2024-04-04T16:09:40+00:00

Labels: REST API Low Priority

Assigned to ginjardev

#676 Add a page to list all the topics

It would be nice to have a page that would basically be the result of `SELECT DISTINCT topic FROM messages` with a time delta. Having it as an API endpoint would make it even more useful, to know what's available.

Status : open

Created 2024-01-17T16:39:06+00:00, updated 2024-03-18T14:12:12+00:00

Labels: enhancement

Assigned to NoubissiViany

#447 How to get fields from all users in a specific group?

Is it possible to get `username`, `human_name` and `website` fields from all users in a specific group?
This would be used in Fedora Planet to create the planet.ini file. The way it is now, the idea is to query members from the group and then query each user to get its info.

As we have +5k users in fedora-contributor, not all of them have `website` and it's needed to query 2 endpoints:
Would be possible to add an endpoint to get that info easier?
Or does an endpoint with this info already exist?
Or the idea of querying the group members first and then each user is really the one that should be used?

Status : open

Created 2023-02-23T01:28:59+00:00, updated 2024-03-11T07:35:22+00:00

Labels: documentation

Assigned to ginjardev

#212 Improve the usage documentation

The usage documentation is in a pretty sorry state, it should be improved. Don't forget to mention field masks in there too.

Status : open

Created 2021-05-21T07:37:47+00:00, updated 2024-03-08T14:33:25+00:00

Labels: documentation next phase

Assigned to onyiipaula

#37 Add scripts to remove old AMIs we have uploaded

We need a script to run as cron that will remove old AMIs we have uploaded.
- We should keep the last month of AMIs, generally.
- We should keep the GA final release AMIs forever.
- The Alpha, Beta, and TC RC releases might should be kept for a month or two.
- All other AMIs should be deleted after they've been up for a month.

Status : open

Created 2015-10-15T18:53:38+00:00, updated 2018-04-23T04:41:43+00:00

#26 Generate a work report at the end of a job

It would be cool if a human-readable, nicely-formatted job report was written to `/var/tmp/`. It'd be cool for archival purposes, but especially when triggering manual upload jobs. Shouldn't be hard to do at all.

Status : open

Created 2015-04-28T15:46:38+00:00, updated 2024-03-11T07:15:42+00:00

Labels: RFE

#506 gpg crypto backend very likely fails on json serialization

Hello, I think you should 'utf-8' decode the signature here:

https://github.com/fedora-infra/fedmsg/blob/develop/fedmsg/crypto/gpg.py#L177

Status : open

Created 2018-02-26T20:36:00+00:00, updated 2018-02-27T20:31:35+00:00

#339 OS name, release and architecture to meta?

Apparently, for the purposes of FAF, it's useful to further filter notifications by OS name (and while we're at it also release and architecture): https://github.com/abrt/faf/issues/432

Do you think it would make sense elsewhere as well? Would it warrant creating a `os_releases` method in `meta.base.Base` similar to `packages` and `usernames`, and a general filter in FMN? (E.g. filtering out EOL releases, focusing on rawhide, CentOS etc.)

Note that the message might have multiple OS names+releases associated with it.

Status : open

Created 2015-05-11T07:22:40+00:00, updated 2016-11-03T11:05:13+00:00

Labels: enhancement

#414 Support pagure reseting assignee

The same message is sent when an assignee is set or reset but the code assums it's set, we should fix this.

Original ticket at: https://pagure.io/pagure/issue/1896

Status : open

Created 2017-02-13T07:39:21+00:00, updated 2017-02-20T12:14:04+00:00

Labels: bug

#342 Make the icon for pagure messages the pagure logo

We have a logo now.

Status : open

Created 2015-11-16T15:50:51+00:00, updated 2016-01-28T13:12:17+00:00

#337 fedmsg docs for Meetbot Not Updated

fedmsg documentation for meetbot is not up to date. Does not contain newly added topics to meetbot. 
Documentation : https://fedora-fedmsg.readthedocs.org/en/latest/topics.html#meetbot

All available topics for meetbot including those not in documentation : 
https://github.com/fedora-infra/supybot-fedmsg/commit/47339f5741192cb0a2f5b65277cbce0d7c529bed

Documentation gets auto-generated from the test suite of this repo : 
https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure

Adding those topics to the docs would be a matter of adding more test cases to this file:  https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/blob/develop/fedmsg_meta_fedora_infrastructure/tests/zodbot.py

Status : open

Created 2015-10-28T20:23:16+00:00, updated 2016-01-28T13:12:47+00:00

#187 Add messages header that points to the Python package for the schema

Publishers using schema add a header to identify the schema, but from the consumer side it's not obvious where to get the schema.

We can use the entry point of the message being published to inspect that package's metadata and provide things like the URL and so on. Then on the consumer side we can log more helpful messages when users are missing the schema.

Status : open

Created 2019-06-20T15:08:18+00:00, updated 2024-04-17T07:14:12+00:00

Labels: enhancement

#897 It's a bit too easy to miss the final commit step, in creating a rule.

When going through the steps of creating a new rule:

1. Click "Add a new rule"
2. "Choose a Tracking Rule" and set an optional "Rule Title"
3. Click the just-appeared "+Add Destination" button
4. Fill out the destination form and click "Add Destination" (again, but a different one)

...having done that, it's a little bit too easy to miss that you haven't _actually_ created **anything** unless you hit the "Create Rule" button in the upper-right corner, which is what finally does the actual rule-creating.

If the user mistakenly thinks they've already set everything they need for their rule, and instead clicks the "Notifications" logo instead, the interface will (without so much as an "Are you sure?" prompt) happily wander away from the in-progress rule creation, discarding all of the just-configured parameters.

This perhaps somewhat ties in to #877, since having a visible Cancel button would hopefully make it more clear that there's an in-progress activity yet to be completed.

Status : open

Created 2023-04-30T00:09:27+00:00, updated 2024-03-13T10:32:19+00:00

Labels: enhancement frontend

Assigned to Precious000

#891 "Add new rule" v.s. "Create rule"

Both buttons lead to the same place, but having a slightly different text creates unnecessary cognitive overhead.

Status : open

Created 2023-04-27T10:35:06+00:00, updated 2023-12-08T14:45:39+00:00

Labels: frontend

Assigned to abompard

#876 [RFE] Provide "all applications" to rules creation

On creating a new rule (for example for "My Events" or "My artifacts") I would like to select "all applications", so in future when new apps are added I don't have to remember to update my rule.

Status : open

Created 2023-04-24T17:29:33+00:00, updated 2024-03-22T14:19:03+00:00

Labels: frontend

Assigned to RuthM-K

#111 Add contributors file?

Should we include a list of contributors and replace my name in the copyright header with something like ``FreeIPA FAS Contributors``?

The current list of contributors in alphabetical order is:

```
* Aurélien Bompard
* Christian Heimes
* Michael Scherer
* Rick Elrod
* Ryan Lerch
* Stephen Coady
```

Status : open

Created 2020-06-04T07:26:35+00:00, updated 2024-04-05T15:15:33+00:00

Assigned to kaf-lamed-beyt

#4 Deploy a local badgr instance and see if features we want are here

# Summary
Run a local instance of [badgr](https://github.com/concentricsky/badgr-server), and check the [different features](https://github.com/fedora-infra/tahrir/issues?q=is%3Aissue+is%3Aopen+label%3AStory) we were looking to add to see which are already implemented in the new system.

# Background

Badgr is the application we want to use to replace the current system. This is a django application and can be run locally. It do requires a few others component, so a Linux VM would be needed. 

We did write last year a set of features and general improvements we wanted on the bugs tracker of the [current system](https://github.com/fedora-infra/tahrir/issues?q=is%3Aissue+is%3Aopen+label%3AStory).

Some of the issues are related to the deployment, some around the general process, some could be fixed by code, some are not. 

# Details

Complete the following steps
* Get a Linux system (a VM would be perfect for that, ideally Fedora)
* Run a local instance of [badgr](https://github.com/concentricsky/badgr-server) from git, nothing fancy needed since that's just for tests.
* Look the issues from the [bug tracker](https://github.com/fedora-infra/tahrir/issues?q=is%3Aissue+is%3Aopen+label%3AStory)
* Tell which are obsolete once the new system is deployed, by commenting with a screenshot if needed to show that's a feature that already exist. No need to do all of them, a few 2/3 will be enough.

# Outcome
* Working local badgr instance
* Better understanding of what we want with badgr and the architecture

---

_Note_: This issue will remain open until the end of the Outreachy 2020 application phase. This ticket does not require an assignee to work on this task – it can be repeated by anyone.

Status : open

Created 2020-03-09T18:02:16+00:00, updated 2020-04-19T11:57:46+00:00

Labels: research

#3 Deploy a simple django application on Openshift Online

# Summary
Deploy a simple django application on [Openshift Online](https://www.openshift.com/) using the free tier. 

# Background

`Openshift Online` is a container management service, based on `Openshift` and `Kubernetes`. The service offer a free tier for testing purpose, and would be the same environment where we would deploy the badgr system during the internship. 

# Details

Complete the following steps:
* Open a trial account on [the service](https://www.openshift.com/trial/)
* Download the openshift-client binary based on openshift.com instruction
* Deploy a basic django application (just a hello world). 
* Take a screenshoft of the output of `oc get pods` when the application is running and post it on this issue

# Outcome

* Working `hello world` application
* Successful understanding how to do basic tasks on Openshift

---

_Note_: This issue will remain open until the end of the Outreachy 2020 application phase. This ticket does not require an assignee to work on this task – it can be repeated by anyone.

Status : open

Created 2020-03-09T14:52:49+00:00, updated 2020-03-30T04:39:33+00:00

Labels: research

#1 Install fedora-messaging locally and publish a test message

# Summary

[Install `fedora-messaging`](https://fedora-messaging.readthedocs.io/en/stable/tutorial/installation.html) and [publish a test message](https://fedora-messaging.readthedocs.io/en/stable/publishing.html)


# Background

`fedora-messaging` is like a live feed of the Fedora Project. Different kinds of contribution activities are registered in the `fedora-messaging` bus. This allows an application to publish a message that triggers an application somewhere else in Fedora, like awarding a new [Fedora Badge](https://docs.fedoraproject.org/en-US/badges/).

`fedora-badges` receives and publishes messages to the Fedora Infrastructure `fedora-messaging` bus. Understanding how `fedora-messaging` works is useful to understand for future development work.


# Details

Complete the following steps:

* [Install fedora-messaging](https://fedora-messaging.readthedocs.io/en/stable/installation.html) on your device
* [Set up fedora-messaging in new test project](https://fedora-messaging.readthedocs.io/en/stable/tutorial/installation.html)
* Write script to [publish a test message](https://fedora-messaging.readthedocs.io/en/stable/publishing.html)

Use the [fedora-messaging documentation](https://fedora-messaging.readthedocs.io/en/stable/index.html) for guidance. You can post a screenshot of running your test script here in the ticket when you're done! :computer: :camera: 


# Outcome

* Working `fedora-messaging` installation
* Successful understanding how to publish a message to `fedora-messaging` bus

---

_Note_: This issue will remain open until the end of the Outreachy 2020 application phase. This ticket does not require an assignee to work on this task – it can be repeated by anyone.

Status : open

Created 2020-03-02T18:44:58+00:00, updated 2020-04-08T18:29:54+00:00

Labels: research

#16 Schema should handle email2fas somehow

In the fedora-messaging world, message schemas are supposed to do most of the work that in the fedmsg world was done by [fedmsg_meta_fedora_infrastructure](https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure) - producing various bits of meta-information about messages, like a human-readable summary of them, and a set of affected FAS usernames.

Because Bugzilla doesn't use FAS auth, the [Bugzilla fedmsg_meta processor](https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/blob/develop/fedmsg_meta_fedora_infrastructure/bz.py) uses a utility function from [fedmsg_meta_fedora_infrastructure.fasshim](https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/blob/develop/fedmsg_meta_fedora_infrastructure/fasshim.py) called `email2fas`, which takes an email address as input and returns a corresponding FAS username (of a FAS account with that email address attached to it) if it can.

fedora-messaging does not have an equivalent feature, so it is not straightforward to implement this in the fedora-messaging incarnation of bugzilla2fedmsg, and it isn't done yet. There was some discussion about how this can be done in #15 : @jeremycline [suggests](https://github.com/fedora-infra/bugzilla2fedmsg/pull/15#issuecomment-495343647) just depending on fedmsg_meta_fedora_infrastructure and using `email2fas` from it directly, (ab)using the fedora-messaging `consumer_config` to provide the necessary configuration. We decided to handle this separately and not as part of #15 , so I'm filing this issue to ensure it's tracked.

Status : open

Created 2019-06-06T15:55:21+00:00, updated 2024-03-16T16:11:54+00:00

#99 Make the list of banned users configurable

In `fedbadges/rules.py`, there's a list of banned users that should be skipped when awarding badges. This should be in the configuration (and please rename it to `skip_users`, we don't actually "ban" bodhi or pagure).

Status : open

Created 2024-04-24T07:26:45+00:00, updated 2024-04-24T07:26:46+00:00

#97 Use towncrier for the changelog and convert it to markdown

Follow the [cookiecutter template](https://github.com/fedora-infra/cookiecutter-python-app/) with changelog management:
- use towncrier to generate it
- convert it to markdown
- have it be picked up by the Github action on tag/release to generate the Github release notes

Status : open

Created 2024-04-17T06:35:47+00:00, updated 2024-04-17T06:35:48+00:00

#7 Add Packit support

It would be cool if we could auto-generate RPMs of this repo.

Status : open

Created 2023-07-07T09:24:48+00:00, updated 2024-03-13T10:38:44+00:00

Assigned to shubhamkarande13

#687 Multiline info lines are represented as a single line in the minutes.

In [this example](https://meetbot.fedoraproject.org/meeting-3_matrix_fedoraproject-org/2024-01-15/cpe-infra-releng-daily-standup.2024-01-15-08.30.html), the first Info line is represented as one line, but if you look at [the plain text minutes](https://meetbot-raw.fedoraproject.org//meeting-3_matrix_fedoraproject-org/2024-01-15/cpe-infra-releng-daily-standup.2024-01-15-08.30.txt) you can see that it was actually 3 lines.

Status : open

Created 2024-01-16T08:55:03+00:00, updated 2024-04-15T04:37:09+00:00

Assigned to sopyb

#684 Missing navigation between Minutes and Logs

When I display a [minutes summary](https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-01-08/fedora-qa.2024-01-08-16.01.html) of a meeting, there's no option to display the full [meeting logs](https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-01-08/fedora-qa.2024-01-08-16.01.log.html). And vice versa, you can't display the minutes summary when viewing the full logs.

Please hyperlink these two pages, otherwise people have to remember magical keywords to adjust in the URL, or they always need to send/link both URLs, which is not fun. Thank you.

Status : open

Created 2024-01-09T12:44:32+00:00, updated 2024-04-22T05:39:48+00:00

Assigned to Freedisch, raeeceip, Precious000

#214 Make more uses of Jinja templates

We only have 3 html templates for now, but we already have parts of the same code on all of them.

Use the power of templating to refactor those pages and eliminate code duplicates like footer & header.
See https://jinja.palletsprojects.com/en/3.0.x/templates/ 

Status : open

Created 2021-11-03T18:42:10+00:00, updated 2022-09-28T03:06:00+00:00

Labels: T: improvement hacktoberfest fragment frontend

Assigned to subhangi2731

#175 Document API endpoints and returned JSON schema

Document API endpoints and returned JSON schema

Status : open

Created 2021-09-29T02:31:30+00:00, updated 2024-03-12T07:34:47+00:00

Labels: documentation hacktoberfest D: contributor experience fragment

#170 Add relevant links in the footer

Like the one at https://getfedora.org/.

![Screenshot from 2021-08-30 21-04-08](https://user-images.githubusercontent.com/49605954/131365114-84e0de41-e864-4d49-b3ee-9fea259baaf3.png)

Status : open

Created 2021-09-29T02:24:48+00:00, updated 2024-03-13T02:06:45+00:00

Labels: hacktoberfest T: new change fragment frontend

#110 RFE: auto-link all URLs in the summary & logs

To create an href hyperlink in the meeting logs, users have to specifically use the `#link` command.

It would be great to auto-link all URLs in the HTML summary and logs. This would allow readers to easily visit the links as they read the summary and logs.

For example, here is one meeting summary: https://meetbot.fedoraproject.org/tendrl-devel/2017-01-13/check-in_20170113.2017-01-13-09.26.html . Almost all the items in there are URLs, but they are not clickable. I have to copy and paste the URL text into my browser.

Status : open

Created 2017-01-18T16:11:08+00:00, updated 2021-10-12T22:03:19+00:00

Labels: T: bug help wanted dependencies D: research

#117 Timeout parameter has been made configurable. Issue:

The request timeout parameter has been made configurable in order to make it usable on different network conditions. 

Regarding issue: #31 

Status : open

Created 2024-03-09T13:03:07+00:00, updated 2024-03-20T14:09:19+00:00

Labels: enhancement

Assigned to brngylni

#81 Attach the same issue ticket ID in the destination namespace as it was in the source namespace

Attach the same issue ticket ID in the destination namespace as it was in the source namespace

It is possible to do that, you know.

![image](https://github.com/fedora-infra/pagure-exporter/assets/49605954/8170abeb-4e0d-43fd-9856-ec98cf87899f)

More information about the implementation details can be found [here](https://docs.gitlab.com/ee/api/issues.html#new-issue).

Status : open

Created 2023-11-25T05:00:12+00:00, updated 2024-03-19T18:05:09+00:00

Labels: enhancement

Assigned to brngylni

#79 Assert `tkts` option defaults should include everything unless specified otherwise

# Summary

When a user imports tickets from Pagure to GitLab, the tool should default to including everything unless specified otherwise.

# Background

When a user is running the tool, they are likely wanting to make a full copy of what is in Pagure to the extent as much is possible. Different metadata matters to different people. Things like labels and the current status of tickets could be very important data points for a team. Of course, not everyone reads the documentation and they might not realize what all options are available.

I predict it would result in a better user experience if the tool defaults to importing everything, to avoid a user having a negative user experience of realizing that data they thought would come with them did not.

# Details

This is a "good first issue" that a new contributor could help with.

We need to change the default options in `main.py` so that the flags are enabled by default. Perhaps the names and help messages of the flags themselves could be made more clear as well about being omissions instead of additions when invoked.

https://github.com/fedora-infra/pagure-exporter/blob/3d77bfe1a461e7daab6a89b3affa2c2a88a03887/pagure_exporter/main.py#L120-L151

# Outcome

Better user experience when using the tool by porting out all relevant metadata and all issues (`FULL`) by default.

Status : open

Created 2023-11-23T13:05:10+00:00, updated 2024-03-19T04:58:38+00:00

Labels: enhancement

Assigned to brngylni

#69 Fragment the documentation into multiple smaller parts

Fragment the documentation into multiple smaller parts

This is going to help improve the readability of the documentation

Status : open

Created 2023-11-21T14:26:04+00:00, updated 2024-02-27T02:58:50+00:00

Labels: documentation

Assigned to prachi-d-dave

#56 Specify which GitLab access token scopes are required

The current documentation does not specify which GitLab project access token scopes are required. It is up to the user to figure out which scopes are needed or not. More explicit guidance on required and optional scopes would help to encourage responsible API key generation, especially for users with access to many private, sensitive repositories.

Status : open

Created 2023-11-09T16:22:41+00:00, updated 2024-03-12T07:27:44+00:00

Labels: documentation

Assigned to Precious000

#55 Specify which Pagure API ACLs are required

The current documentation does not specify which Pagure API ACLs are required. It is up to the user to figure out what ACLs are needed or not. More explicit guidance on required and optional ACLs would help to encourage responsible API key generation, especially for users with access to many private, sensitive repositories.

Status : open

Created 2023-11-09T16:15:36+00:00, updated 2024-03-23T05:45:34+00:00

Labels: documentation

Assigned to Precious000

#31 Allow configurability of `timeout` variable for the HTTPS requests

This should allow people to use the service even in situations where the network conditions are poor if they tune the `timeout` variable to a comparatively bigger value. 

Status : open

Created 2023-10-12T07:25:30+00:00, updated 2024-03-09T01:22:45+00:00

Labels: enhancement

Assigned to brngylni

#25 The userdata should point to Accounts FPO instead of Pagure userbase

In the event of Pagure being removed, it is in the best interest to point to the accounts of the users that authored issue tickets and comments under them on Fedora Accounts instead of Pagure.

Status : open

Created 2023-10-10T09:26:00+00:00, updated 2024-03-09T01:21:36+00:00

Labels: bug

Assigned to brngylni

#422 Add support of `update_or_create`

Thanks for your project, it's absolutely amazing 

Could you please consider adding a function `update_or_create`?

Thanks

Status : open

Created 2024-03-28T19:46:45+00:00, updated 2024-03-30T18:41:24+00:00

#487 Reports on the explore page should have a dynamic year

On the export page, the reports box suggests reports about year 2013. This is probably less interesting than the current year, so it should do that.

Status : open

Created 2024-04-23T08:08:24+00:00, updated 2024-04-23T08:08:25+00:00

#482 Display user avatars using their actual email adress

In the Badges system, everybody's "email" address is fasusername@fp.o, because users are keyed on email addresses and not nicknames. But FAS has the actual email address that a user may have set their libravatar on.
Tahrir should ask FASJSON what the user's actual email address is to build the libravatar URL. This request should be cached for a reasonable amount of time (or, to be fancier, invalidated by fedbadges when a FAS message comes in about a user changing their email address).

Status : open

Created 2024-04-19T06:34:47+00:00, updated 2024-04-25T08:32:06+00:00

Labels: enhancement

#480 Use Towncrier for the changelog and convert it to Markdown

Follow the [cookiecutter template](https://github.com/fedora-infra/cookiecutter-python-app/) with changelog management:
- use towncrier to generate it
- convert it to markdown
- have it be picked up by the Github action on tag/release to generate the Github release notesFollow the [cookiecutter template](https://github.com/fedora-infra/cookiecutter-python-app/) with changelog management:
- use towncrier to generate it
- convert it to markdown
- have it be picked up by the Github action on tag/release to generate the Github release notes

Status : open

Created 2024-04-17T06:54:14+00:00, updated 2024-04-17T06:54:15+00:00

#382 Sort badge award names alphabetically

Badge pages have a list of users who were awarded the badge. As someone who awards badges, this list is hard to parse for a previous awardee since it's not ordered. Ideally the list should be alphanumerically sorted so I can locate who's already been awarded the badge.

Status : open

Created 2018-03-15T13:51:08+00:00, updated 2024-04-18T01:50:10+00:00

Labels: RFE

#381 Attempting to award a badge again should fail gracefully, not 500

If I attempt to award a badge to a person who already has it, I receive a 500 error. This operation should fail gracefully, either returning to the badge page with a failure notice, or a popup to that effect -- not a server internal error.

Status : open

Created 2018-03-15T13:38:39+00:00, updated 2024-04-18T01:50:10+00:00

Labels: Refactor

#352 404/500 errors

404 and 500 error pages should have actual text, instead of just a centered image. The image is fine for the 404 or 500 badgers, but not for the text itself.

Status : open

Created 2016-11-12T23:09:12+00:00, updated 2024-04-18T01:50:16+00:00

Labels: RFE WebUI

#348 RFE: csv submission of badge awardees

I have a list of ~30 or so Flock speakers I have to award the speaker badge to. It takes about 2-3 minutes per speaker to award (type in speaker name, if the FAS acct is wrong gives me a 404 error and I have to dig around, I have to hit back and fresh reload the page to try again, once it's awarded it brings me to an RSS feed and I have to hit back and reload again)

Life would be a lot easier if I could just upload a csv of fas accounts to award the badge, and it spit out which accounts weren't found.

Status : open

Created 2016-08-16T12:32:13+00:00, updated 2024-04-18T01:50:17+00:00

Labels: RFE

#320 Badges Monthly Leaderboard misses the last day

Badges acquired on last day of the month do not show up on Monthly Leaderboard resulting in wrong ranking.
Eg :
Monthly LeaderBoard Sept 2014 : https://badges.fedoraproject.org/report/2014/9 
It shows @robyduck has earned 16 badges during the period
But if you check out @robyduck 's badges here : https://badges.fedoraproject.org/user/robyduck?history_limit=115
@robyduck has earned 16 badges before 30 Sept + 7 badges on 30 Sept , effectively making @robyduck #3 on Monthly LeaderBoard

Same goes for @bee2502 for Oct 2015 : https://badges.fedoraproject.org/user/bee2502
Badges earned during Oct = 21 = 19 + 2(on 31st)
Monthly Leaderboard still shows 19 badges : https://badges.fedoraproject.org/report/2015/10 

Status : open

Created 2015-11-01T09:19:26+00:00, updated 2024-04-18T01:50:19+00:00

Labels: Bug

#148 reenable gravatar fallback

It used to be that we would first check libravatar for an image, if that failed we'd fallback to gravatar, and if that failed we'd fall back to the fedora logo.

One week before flock, I broke that (commented it out) because I realised that using OpenID as the key for libravatar was _way better_ than using USER@fedoraproject.org as the key.

That gravatar fallback code should probably be re-added.  We'll have to still use http://USERNAME.id.fedoraproject.org for libravatar and USERNAME@fedoraproject.org for gravatar.  Tricky, not impossible.

Status : open

Created 2013-08-10T16:50:14+00:00, updated 2024-04-18T01:50:23+00:00

Labels: Bug blocked

#58 Convert the changelog to Markdown and add towncrier to manage it

Follow the [cookiecutter template](https://github.com/fedora-infra/cookiecutter-python-app/) with changelog management:
- use towncrier to generate it
- convert it to markdown
- have it be picked up by the Github action on tag/release to generate the Github release notes

Status : open

Created 2024-04-17T06:34:57+00:00, updated 2024-04-17T06:35:03+00:00

#54 Migrate to the new SQLAlchemy 2.0 API

There's a new API style in SQLAlchemy 2.0: https://docs.sqlalchemy.org/en/20/changelog/migration_20.html

Status : open

Created 2024-04-11T07:24:12+00:00, updated 2024-04-18T16:28:20+00:00

Labels: enhancement

#8 In previous notifications, the description of the badge was used

In fedmsg_meta_fedora_infrastructure, the body of the email sent by the old FMN when a badge was awarded [was using the description of the badge](https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/blob/c107ffa2b2e4fad86a284453210bad65423a6578/fedmsg_meta_fedora_infrastructure/badges.py#L46). This should be done here as well using  `__str__()`.

Status : open

Created 2024-04-24T07:52:47+00:00, updated 2024-04-24T07:52:47+00:00

#378 Create unit tests for IRC action handler functionality

# Summary

<!-- One sentence summary of how something can be better. -->
IRC messages can also contain actions (/me). We currently do not have unit tests for this functionality.

# Background

**Is your improvement related to a problem? Please describe**:
<!-- A clear and concise description of what the problem is. Ex. I'm frustrated when [...] -->
Not related to a direct problem.


**Describe the solution you'd like**:
<!-- A clear and concise description of what you want to happen. -->
Unit testing needs to cover various ACTION commands to make sure everything works smoothly. 

**Describe alternatives you've considered**:
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
No other alternatives.

# Details

<!-- Details to understand how this task should be completed or carried out. What are the next steps? Add any other context or screenshots about the feature request here. -->
The [girc library](https://github.com/lrstanley/girc/blob/master/event.go#L449) makes use of an `isAction` function to see if a given message contains an action (i.e. /me). We need to figure out the best way to mock an action and test for it.



# Outcome

<!-- One sentence to describe what the end result will be once this ticket is complete. -->
IRC actions are fully tested.

Status : open

Created 2021-08-18T19:08:07+00:00, updated 2021-10-20T20:17:17+00:00

Labels: help wanted quality assurance IRC

#56 Large Telegram messages should go on pastebin

IRC users get annoyed when one Telegram user posts a codeblock or just a multiline message.
It should be configurable that `preformatted multilined text` and any other text with >_n_ carriage returns/newlines automatically are turned into a pastebin to be linked to in the IRC.

see also: https://github.com/FruitieX/teleirc/issues/249

Status : open

Created 2018-06-06T11:52:25+00:00, updated 2023-01-25T04:14:19+00:00

Labels: improvement help wanted

#131 Update TigerOS Website

* [ ] On mirror, create /TigerOS/latest symlink for current release number
* [x] Have both download links on tigeros.ritlug.com point to /TigerOS/latest/release
* [x] Make the link buttons at the bottom of tigeros.ritlug.com visually similar in the text
* [ ] How to download and install TigerOS (not building)
* [ ] Make wiki not have dev instructions on home page; put in content pointing to sidebar?

Status : open

Created 2018-04-25T19:43:00+00:00, updated 2021-03-31T21:57:57+00:00

Labels: enhancement priority:high website good first issue

#152 Client side reminders for a complete calendar

At the moment, when downloading a single meeting to your calendar, you can add client-side reminder (ie: have your phone, own calendar remind you about the meeting).

This is nice and people like it, but we should add this feature as an option when adding a complete calendar.

This would then add a client-side reminder to all the event present in the calendar.
This would likely be an argument to specify to the download URL.

Status : Open

Created 2015-07-07T10:04:11+00:00, updated 2017-02-08T16:07:43+00:00

#6 Add *-v, --version* option

I think you missed to --version option, it's useful for testing

Status : Open

Created 2020-04-30T18:56:18+00:00, updated 2024-04-17T07:42:57+00:00

#207 New doc page: Fedora Community vocabulary

# Summary

Create a new Fedora Docs page under CommOps docs called "Fedora Community vocabulary" that defines Fedora jargon and context-specific vocabulary

# Background

There are a lot of things we write in Fedora for shorthand to save time. Things we do to signal quick agreement like `+1`, or an old-school emoticon that might just look weird to someone else (`\o/`). So, to help newcomers to the Fedora Community, we can create a community-maintained page that tries to start defining what we mean by certain things in Fedora.

I think this would be a great resource during the peak times where we see new contributors, like for Mentored Project / Summer Coding rounds. It saves on-boarding time and also gives permission to ask for clarification on what we mean if we say some word or phrase.

# Details

This could be a new docs page in the Fedora Docs site: https://docs.fedoraproject.org/en-US/commops/

It can be a new page at the top-level of the sidebar. The page can include some examples to start (like `+1/+0/-1` meanings). The page should have some instructions on how to submit contributions to the vocabulary page. When it is published, we could follow up with a Call for Contributions on the Fedora Community Blog to raise awareness for it as a resource. Or ask @bcotton nicely for a shout-out in his reports too.

# Outcome

Fedora gets better at documenting what we mean when we say specific things, to help newcomers learn the "Fedora jargon"

--

P.S. - Shout-out to a conversation I had with @nasirhm for giving me this idea :smile: 

Status : Open

Created 2020-04-29T00:16:04+00:00, updated 2021-06-26T13:52:33+00:00

Labels: help wanted team - g11n team - mindshare type - docs type - inclusion

#732 [Recognition] Heroes of Fedora 40 Beta

Beta is out now and we would want to publish the Heroes of Fedora. @coremodule previously you handled this. Do you intend to do it this time as well?
HoF is sadly the *only* way, we present/recognize the community members with a token of gratitude for the time, effort and commitment towards QA activities amongst other things in Fedora.
It's crucial that we keep true!

Status : Open

Created 2023-03-15T05:14:50+00:00, updated 2024-02-21T23:00:53+00:00

Labels: task

#1068 PPC64LE Workstation CHECKSUM file link is missing from https://alt.fedoraproject.org/en/verify.html

See issue title. There's no link to the CHECKSUM file. I had to ask on #fedora-devel and someone was kind enough to point me to https://getfedora.org/static/checksums/Fedora-Workstation-33-1.2-ppc64le-CHECKSUM. 

Status : Open

Created 2021-03-31T19:33:56+00:00, updated 2022-09-10T22:20:53+00:00

Labels: alt.fp.o

#9450 Find and replace del os.environ['foo'] with os.environ.pop('foo', None)

### Issue
A new change included code that called "del os.environ['KRB5CCNAME']" where there was no such value in the environment. This caused an unnecessary installation failure.

commit https://pagure.io/freeipa/c/f248b22ef4d98293224b49576f5e6a1b8d672d76 addressed this issue by using pop instead.

There are other occurrences of this code style spread around various utilities. While it may be fair to assume that a given environment variable will always be present, using pop should be a safer route.

We should find and replace them. From a quick search there are only a few.

```
$ git grep "del os.environ"
install/certmonger/dogtag-ipa-ca-renew-agent-submit.in:            
del os.environ['CERTMONGER_CA_PROFILE']
ipaclient/install/ipa_certupdate.py:                del os.env
iron['KRB5CCNAME']
ipaserver/install/server/upgrade.py:            del os.environ
['KRB5CCNAME']
ipatests/test_ipaserver/test_ipap11helper.py:            del o
s.environ['SOFTHSM2_CONF']
```

Status : Open

Created 2023-09-14T12:30:10+00:00, updated 2023-09-14T12:30:10+00:00

#8546 RFC: Extend max-line-length from 80 to 88+ (100?)

Proposal: change tox.ini's 80c character limit to 88 or more.
- 88 is the limit for a font size of 14 on a FHD (1920x1200) screen with two editors side-by-side.
- Some team members would prefer more.
- A too-high number can become an issue for potential contributors with eyesight problems. So we want to avoid that.
- Please add comments to the (upcoming, linked) PR.

Deadline is end of October 2020.

Status : Open

Created 2020-10-15T13:53:07+00:00, updated 2020-10-15T14:11:23+00:00

Assigned to fcami

#8061 Add __all__ to modules used by ansible-freeipa

FreeIPA should use ``__all__`` to mark objects that are considered exported and used by ansible-freeipa. This will make it more obvious which functions and attributes are used by ansible-freeipa and reduce the likelihood of breaking ansible-freeipa.

Background: Commit 2da90887632c764a73866c9ad3824ebb53c0aa73 moved ``configure_nsswitch_database`` to another module. This caused ansible-freeipa to break very late in the current release cycle.

The module global variable ``__all__`` is used for ``*`` imports and as a marker for attributes that can be considered as exported. ``__all__`` makes it more obvious which module members are used outside of FreeIPA and by ansible-freeipa. The variable a tuple of attribute names, e.g. ``__all__ = ('api', )``. If an attribute is not define pylint will complain with an error like ``ipalib/__init__.py:885: [E0603(undefined-all-variable), ] Undefined variable name 'foo' in __all__)``.

A quick search over ansible-freeipa code base revealed imports of these modules:

```
ipaclient.install.client
ipaclient.install.ipachangeconf
ipalib
ipalib.config
ipalib.constants
ipalib.install.kinit
ipalib.krb_utils
ipalib.rpc
ipalib.util
ipaplatform.debian.paths
ipaplatform.debian.tasks
ipaplatform.fedora.paths
ipaplatform.fedora.tasks
ipaplatform.rhel.paths
ipaplatform.rhel.tasks
ipapython.admintool
ipapython.certdb
ipapython.dn
ipapython.dnsutil
ipapython.ipa_log_manager
ipapython.ipautil
ipapython.version
ipaserver.install.dogtaginstance
ipaserver.install.installutils
ipaserver.install.replication
ipaserver.install.server.install
ipaserver.install.server.replicainstall
ipaserver.install.service
ipaserver.masters
```

The task is to identify all used members and to add them to ``__all__`` of these modules.

Status : Open

Created 2019-09-05T14:22:15+00:00, updated 2019-09-06T01:15:58+00:00

#7113 Add Certificate Mapping Data: confusing selection of options

Ticket was cloned from Red Hat Bugzilla (product _Red Hat Enterprise Linux 7_): [Bug 1480272](https://bugzilla.redhat.com/show_bug.cgi?id=1480272)


```text
Created attachment 1311794
Add Certificate Mapping Data

Description of problem:

The form for adding cert mapping data in the web UI (see the attached
screenshot) makes it look like the users have two options -- two radio buttons:
cert mapping data, or issuer and subject.

However, there are actually three options: provide certificate mapping data,
the certificate, or the issuer and subject.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Open the web UI.
2. Click Identity > Users > a user > Certificate Mapping Data - Add.

Actual results:

Two radio buttons, which suggests only two equivalent options for providing the
data. Users might think that both Cert mapping data and Certificate are
required, for example.


Expected results:

Change the form for adding the data. For example, three radio buttons, each for
one of the available options, would make the expected input much clearer.


Additional info:
```

Status : Open

Created 2017-08-18T16:29:42+00:00, updated 2020-06-02T07:01:33+00:00

Labels: webui

Assigned to pvomacka

#6910 Need to remove certain files in /var/run/ipa directory after uninstalling ipa-server

Ticket was cloned from Red Hat Bugzilla (product _Red Hat Enterprise Linux 7_): [Bug 1441050](https://bugzilla.redhat.com/show_bug.cgi?id=1441050)


```text
Description of problem: Need to remove certain files in /var/run/ipa directory
after uninstalling ipa-server


Version-Release number of selected component (if applicable):
ipa-server-4.5.0-5.el7.x86_64

How reproducible: Always

Steps to Reproduce:
1. Install IPA server, establish trust with win2k16 AD
2. Ensure trust is established and now delete the trust
3. Now Uninstall IPA server .

#ipa-server-install --uninstall -U

Actual results:
ipa-server is uninstalled successfully without any issues, but there are
certain files which are left over in /var/run/ipa directory

[root@master ipa]# pwd
/var/run/ipa

-rw-------. 1 root   root   2924 Apr 10 06:17 krb5cc_oddjob_trusts
-rw-------. 1 root   root   2819 Apr 10 06:17 krb5cc_oddjob_trusts_fetch

/var/run/ipa/ccaches
[root@master ccaches]# ls -l
total 20
-rw-------. 1 ipaapi ipaapi 6364 Apr 11 01:13
admin@TESTRELM.TEST
-rw-------. 1 ipaapi ipaapi 2262 Apr 11 01:13
host~client.testrelm.test@TESTRELM.TEST
-rw-------. 1 ipaapi ipaapi 4198 Apr 10 04:08
host~master.testrelm.test@TESTRELM.TEST

Expected results: Unless and until these files are important for the system,
they should be removed after ipa-server uninstall.

Additional info: Logging this as a bug to have a clean uninstall
```

Status : Open

Created 2017-04-28T12:29:28+00:00, updated 2018-07-19T17:23:08+00:00

#6699 Deprecate return value 3 in ipa-replica-install

The return value 3 of ipa-replica-install is documented as

    3 if the host exists in the IPA server or a replication agreement to the
    remote master already exists

While this explanation is not good (should say "if the host with this hostname" and "the remote server has a replication agreement to this server"), it's also not entirely true.
If you look for "rval=3" in ipa-replica-install, you will find that there are many additional scenarios where ipa-replica-install fails with return value 3. This means that it's been broken for some time.
I propose deprecating return value 3. `ipa-replica-install` is a complex installer, if it fails, one usually has to look in the log to see what the actual problem was. Therefore we can do with just two return values, one for success, one for failure.

Status : Open

Created 2017-02-23T12:19:13+00:00, updated 2019-02-14T20:02:57+00:00

Assigned to someone

#361 400 Error Description should be improved

Hey there,

I raised this on our Noggin tracker: https://github.com/fedora-infra/noggin/issues/752

The wording is confusing when an auth request failed, in my example I entered the wrong password and got a 'User not authenticated at continue' error. I get what this is trying to achieve as I'm a native English speaker but it's still confusing and took me a few goes to figure it out. This could be a quick fix and might help the end user understand what went wrong

Status : Open

Created 2021-09-29T13:19:44+00:00, updated 2021-09-29T14:15:11+00:00

#190 Logging instrumentation info for backend auth

It would be very useful to log information like response time and response code for backend authentication providers.
That will make debugging for example slow links to backend providers a lot easier.

Status : Open

Created 2015-10-09T16:06:26+00:00, updated 2017-02-13T18:49:29+00:00

Assigned to puiterwijk

#95 Add tool-tips and descriptions on admin pages

Some feedback I've heard from new Ipsilon admin users is that they are not sure what each plug-in page is meant to do.  Some helpful basic description paragraphs could help here.  For example, something similar to:

"Login plugins are responsible for authenticating users to Ipsilon.  You can enable different login plugins to allow users to authenticate using different authentication methods."

In addition, some tool-tips that pop up when you hover over UI elements might be helpful to explain what text-fields or buttons do.

Status : Open

Created 2015-03-23T14:45:25+00:00, updated 2017-02-13T18:50:29+00:00

Assigned to nkinder

#19 Add option to provide certificates to installers

Some peoplem prefer to use certificates signed by trusted CAs for their IDPs and SPs. Even though certificates are cross-trusted by the metadata exchange process.

Add a way to pass in pem/p12 files to installers so that externally provided certificates can be used instead of self-signed ones

Status : Open

Created 2014-11-18T15:46:10+00:00, updated 2017-02-13T18:51:10+00:00

#5453 pagure does not support git's "advertised references"

Pagure does not seem to support git's "advertised references" feature causing
"git clone https://github.com/systemd/systemd.git --no-tags --depth 1
--recurse-submodules --shallow-submodules" to fail with the following
error when the submodule does not track the latest commit on the
systemd master branch on code.opensuse.org (which is backed by pagure):

"""
error: Server does not allow request for unadvertised object
37aca188c2ef606319217b30ff8b0c66df6c60f1
fatal: Fetched in submodule path 'pkg/opensuse', but it did not
contain 37aca188c2ef606319217b30ff8b0c66df6c60f1. Direct fetching of
that commit failed.
"""

Other git forges do support this feature. It would be great if pagure could support the "advertised references" or if it is already supported, include the last X commits (50 or 100 or so I would guess) commits as advertised references so that a git checkout with --shallow-submodules and --depth=1 still works if the submodule does not track the latest commit on its configured branch.

Status : Open

Created 2024-03-25T13:44:36+00:00, updated 2024-03-31T02:57:43+00:00

#5423 Logout redirects to plain text HTTP

Using the "Log Out" function on our Pagure instance (code.opensuse.org) in Firefox shows 

```
Secure Site Not Available
You’ve enabled HTTPS-Only Mode for enhanced security, and a HTTPS version of code.opensuse.org is not available.
```

while trying to redirect to dashboard/projects. Confirming the security warning then follows with another redirect to the OpenID provider (correctly using HTTPS).

Downstream issue https://progress.opensuse.org/issues/152709.

Status : Open

Created 2023-12-16T21:02:45+00:00, updated 2024-04-19T09:52:14+00:00

Labels: UI bug

Assigned to sawe-dee

#5306 Obsolete installation instructions for pygit2

The "manual" paragraph of the installation section in the README mentions the installation libgit2-devel from the OS package manager, and then to install pygit2==<version of libgit2 found>.* from pip.
This was giving me errors though. I found [this comment](https://github.com/libgit2/pygit2/issues/999#issuecomment-614670140) that mention how libgit2 is included on pygit2 for newer versions.
I think the README should be updated by removing this step. Pygit2 and libgit2 should be installed with just the "pip install -r requirements.txt" step

Status : Open

Created 2022-06-15T07:14:42+00:00, updated 2024-01-25T13:03:34+00:00

Labels: bug

#5260 [RFE] history on folders

as we already have on files  https://pagure.io/releng/history/scripts/find_unblocked_orphans.py?identifier=main have the some feature on folders would be nice 

Status : Open

Created 2021-12-11T19:16:14+00:00, updated 2021-12-13T10:37:12+00:00

Labels: RFE UI

#5251 merge button green but just shows (empty, lighter-green) blank bar when I click it

PR is here: https://pagure.io/fedora-docs/release-docs-home/pull-request/12

screenshot of what I'm seeing:

Status : Open

Created 2021-11-27T22:17:48+00:00, updated 2023-12-22T14:52:38+00:00

Labels: UI bug

#5158 Using Twemoji for Pagure

The basic idea is using more D&I respectful emoji kit and details in the ticket.  

Related ticket : https://pagure.io/fedora-diversity/issue/196

Twemoji link : https://twemoji.twitter.com/
Github link : https://github.com/twitter/twemoji

Thank you.

Status : Open

Created 2021-04-29T14:39:11+00:00, updated 2021-04-29T15:00:36+00:00

Labels: RFE UI

#5067 use 7 char shorts git hashes if you don't render 6 char hashes

Suggestion: either allow rendering 6 char short git hashes in comments
or display commit hashes with 7 chars (not 6) by default in Pagure :)

Status : Open

Created 2020-12-12T15:07:38+00:00, updated 2021-08-03T09:31:02+00:00

Labels: RFE

#4988 Default theme glitch?

CSS tags are shown in the screen.

Please see https://lutim.net/cYPLH11q.png

Status : Open

Created 2020-09-10T18:19:02+00:00, updated 2023-01-12T20:29:26+00:00

Labels: UI bug

#4965 Different formating on tooltips

We have some tooltips with `<span data-toggle="tooltip" title="Tooltip">` and some others without the `data-toggle` attribute.

This ends on different padding/font size tooltips here and there.

Status : Open

Created 2020-08-17T15:37:59+00:00, updated 2024-04-20T18:23:06+00:00

Labels: UI

Assigned to wombelix

#4736 No handlers could be found for logger "pagure.lib.notify"

On `fedpkg push`, I get:

```
Enumerando objetos: 7, listo.
Contando objetos: 100% (7/7), listo.
Compresión delta usando hasta 4 hilos
Comprimiendo objetos: 100% (5/5), listo.
Escribiendo objetos: 100% (5/5), 3.24 KiB | 3.24 MiB/s, listo.
Total 5 (delta 2), reusado 0 (delta 0)
remote: Emitting a message to the fedmsg bus.
remote: * Publishing information for 1 commits
remote: No handlers could be found for logger "pagure.lib.notify"
remote: Sending to redis to log activity and send commit notification emails
remote: * Publishing information for 1 commits
remote:   - to fedmsg
To ssh://pkgs.fedoraproject.org/rpms/krb5
   8fb4697..edfb00e  master -> master
```

The message that "No handlers could be found for logger "pagure.lib.notify"" looks like an error, but it's from the remote, so I'm not sure what to do about it.

Status : Open

Created 2020-02-06T15:32:56+00:00, updated 2021-03-14T01:24:35+00:00

#4734 Text entry is too small when editing comments

When editing a comment in Pagure 5.8.1 using WebKitGTK 2.27.4, the text box is only large enough to display two lines of text. It should expand to fill the available vertical space.

I've repeatedly attempted to attach screenshots to this comment, but nothing happens after I select the screenshot in the file chooser. Guess I should report a second bug for that....

Status : Open

Created 2020-02-05T19:53:06+00:00, updated 2020-02-05T20:42:14+00:00

Labels: UI bug

#4660 emoji point to a parked domain

In the list of emoji icons that appears when writing ":", there is a BROWSE ALL link that points to http://www.emoji.codes/

The web page states that "This domain is parked free of charge with NameSilo.com. NameSilo offers the cheapest domains on the Internet as well as"

Status : Open

Created 2019-11-18T10:28:21+00:00, updated 2022-08-24T16:15:42+00:00

Labels: UI bug

#4546 [RFE] expose relationships between Issue and PR in the API

The data model contains links between issues and PRs.  It would be helpful to expose this through the API

Status : Open

Created 2019-07-18T15:28:39+00:00, updated 2020-05-25T16:10:21+00:00

Labels: RFE

#4544 better tarball release management system

E.g. in copr/copr.git, there's Releases section which provides tarball download links for each tag we do -- but that links are bad,  because
- we have tags for separate packages (sub-directories)
- the links generate a tarball containing all the project sources, not only to the corresponding package.

It would be nice to have at least a knob to disable this "automatic release tarball" feature -- that is - keep only the manually "uploaded" tarballs.  Maybe also provide a way to bound released tarball with the corresponding tag.

Status : Open

Created 2019-07-17T09:51:29+00:00, updated 2023-02-21T05:23:21+00:00

Labels: RFE

#4513 Jenkins integration should add comment or otherwise trigger notification

Right now, when using Jenkins integration for performing CI checks on a pull request, there is no feedback to the submitter of the PR unless they think to go check for it some time later.

Problems:

1. There's no indication that CI runs have been started. You only see the results once they end (which may be minutes or hours later).
2. There's no notification emitted on the completion of the CI run, so a new contributor will have no reason at all to think that they might need to go and manually check the results.

For example: https://pagure.io/releng/fedora-module-defaults/pull-request/123

I have CI that verifies that the YAML documents being modified meet Fedora policies. As the reviewer, *I* know that I need to check the CI results, but this leads to a much longer round-trip time since I have to add a comment informing the contributor that their submission didn't pass the tests.

Status : Open

Created 2019-06-26T15:59:27+00:00, updated 2023-01-21T12:42:13+00:00

Labels: doc

Assigned to wombelix

#4201 Celery nodes naming missing(?)

When setting multiple celery workers,

- main worker
- gitolite
- ci

I'm looking at,

```
Jan 14 08:55:32 qemu celery[26037]: 2019-01-14 08:55:32,083 [WARNING] celery.redirected: /opt/pag_01/pag_01-server/venv/lib/python3.5/site-packages/celery/app/control.py:52: DuplicateNodenameWarning: Received multiple replies from node name: celery@qemu.
Jan 14 08:55:32 qemu celery[26037]: Please make sure you give each node a unique nodename using
Jan 14 08:55:32 qemu celery[26037]: the celery worker `-n` option.
Jan 14 08:55:32 qemu celery[26037]:   pluralize(len(dupes), 'name'), ', '.join(sorted(dupes)),
Jan 14 08:55:32 qemu celery[26037]: 2019-01-14 08:55:32,086 [INFO] celery.worker.consumer.mingle: mingle: all alone
Jan 14 08:55:32 qemu celery[26037]: 2019-01-14 08:55:32,132 [INFO] celery.apps.worker: celery@qemu ready.
```

Maybe using a <code>-n pagure_$name</code>
e.g. <code>-n pagure_ci</code> or <code>-n pagure_gitoline</code>

For the systemd files would be a solution to it.

Status : Open

Created 2019-01-14T16:14:05+00:00, updated 2023-01-21T10:27:13+00:00

Labels: RFE

Assigned to wombelix

#3931 How can I start

Hello,
I was trying to get started with pagure, but I am not able to figure out the files. I believe there must be a doc file which can guide the newbies where to start from. I am not able to understand which is the very first file from where i should start understanding the code and also not able to find some specific code files. Can someone guide me regarding files? Is there any specific pattern? I am looking for the code for "Settings Option".

Status : Open

Created 2018-10-18T19:17:43+00:00, updated 2023-01-21T12:45:11+00:00

Labels: RFE doc

Assigned to wombelix

#3714 [UI/UX - 5.0+] Better explanation of regenerating repos in Settings menu

# Problem

Regenerating repos sounds dangerous and scary but there isn't anything clear in the UI or an explanation to tell me otherwise :sweat_smile: 

# Analysis

I noticed this setting in 5.0+ when going through the _Settings_ menu. I was hoping for an explanation or link to docs to learn what this does or an explanation of when I would need to do this.

# Implementation

* Short paragraph or hover-over hint to explain usage?
* Link to existing documentation?
* If dangerous, more clear hinting with red buttons and maybe something clever like a hazard symbol for colorblind users

Status : Open

Created 2018-09-26T04:42:09+00:00, updated 2023-01-21T12:44:03+00:00

Labels: doc

Assigned to wombelix

#2445 Pagure hook does not work for non-master branches

I manually merged a Koji PR that targeted the legacy-py24 branch

https://pagure.io/koji/pull-request/520

The commit message contained the line `Merges #520`, yet when I pushed the changes, the Pagure hook did not close the pr as it normally does.

Granted, perhaps this is intentional. I expect there are folks using non-master public branches for development (e.g. a devel or testing branch), and it might be confusing to close a pr or issue when it has only been pushed to devel or testing. OTOH, if the PR in question is *targeting* that branch, then perhaps it would make sense regardless.

I'm not sure what the best answer is here, but I think at least the behavior for non-master branches should be clarified in the docs.

Status : Open

Created 2017-07-25T13:21:33+00:00, updated 2023-01-25T23:11:52+00:00

Labels: bug doc

Assigned to pingou

#14 A push to a fork is considered as affecting the main package

When pushing to a fork, the main GitMessage schema will use `_name_if_namespace` to populate the `packages` property, and this will return the name of the packaged the repo was forked from. As a result the maintainers of the main package will get notified of what happens in the fork.

The method should check whether the commit has been made to a fork.

Example: https://apps.fedoraproject.org/datagrepper/v2/id?id=a716a8cd-2a5f-4cad-96ad-a40eafda036a&is_raw=true&size=extra-large caused a notification to be sent to Vit, as reported in https://pagure.io/fedora-infrastructure/issue/11687#comment-889972

Status : Open

Created 2024-01-11T11:01:54+00:00, updated 2024-03-16T16:44:06+00:00

#11 No Git diff for "[Pagure] <fas> pushed 2 commits on rpms/<pkg> (branch: <branch>)"

Reported at: https://github.com/fedora-infra/fmn/issues/949

The old FMN send **two** e-mails for this case, each with a Git diff. The new one sends one e-mail, with no Git diff at all, just with a link. Any chance to improve this behaviour? I like to archive such Git diffs, thus a link has less value for me compared to the actual diff.

```
Date: Wed, 12 Jul 2023 18:11:50 +0000 (UTC)
From: Fedora Notifications <notifications@fedoraproject.org>
To: <me>
Subject: [Pagure] <fas> pushed 2 commits on rpms/<pkg> (branch: <branch>)

John Doe (<fas>) pushed 2 commits on rpms/<pkg>.
Branch: <branch>

https://src.fedoraproject.org/rpms/openbgpd/c/8ccf7c1d460a354e2fccbc4ac433e406d453b756..2435104bec4a340f0bcda4186365d509e8d5abe0
```

Status : Open

Created 2023-08-23T09:41:29+00:00, updated 2023-12-15T14:37:21+00:00

Assigned to abompard

#219 Lots of dead links reported at build time

Since Antora 3.0, the build script now report any internal dead links. And we have a lot of them.

https://darknao.fedorapeople.org/build.log

Guide on how to fix it:
~~~
[19:47:33.715] ERROR (asciidoctor): target of xref not found: After_Installation.adoc#sect-gnome-initial-setup
    file: modules/install-guide/pages/install/After_Installation.adoc
    source: https://pagure.io/fedora-docs/install-guide.git (refname: master)
~~~

- Go to the specified repository: https://pagure.io/fedora-docs/install-guide.git
- Find the specified file in the `master` branch (refname) : https://pagure.io/fedora-docs/install-guide/blob/master/f/modules/install-guide/pages/install/After_Installation.adoc
- Find the line where the xref is defined. Sometime, the page includes other pages using the keyword `include`: 
~~~
include::{partialsdir}/install/InitialSetupHub.adoc[]
~~~
  In this example, the bad link can be found in this file: https://pagure.io/fedora-docs/install-guide/blob/master/f/modules/install-guide/pages/_partials/install/InitialSetupHub.adoc#_11

- Fix the link. Refer to [Antora documentation about xref](https://docs.antora.org/antora/latest/page/xref/)
  In this case, the correct link syntax is:
~~~
xref:install/After_Installation.adoc#sect-gnome-initial-setup[GNOME Initial Setup]
~~~
- Use the local preview to check your fix.
- Create a PR with your changes.

Status : Open

Created 2022-04-20T17:11:27+00:00, updated 2022-04-21T05:26:34+00:00

Labels: content

#26 Doc to write: Getting help, common bugs, etc.

I don't think we should have a top-level link to the Common Bugs wiki page, because it isn't like the other docs ... it's a wiki page, and is going to remain that way for a while. Instead, let's write a short document that addresses what to do if you encounter a problem in a Fedora  release in general — how to see if others have the same issue, where to get help, how to report a bug effectively, what to expect when you report a bug, and so on. This would include links to Common Bugs, to Ask, to Bugzilla, and some level-setting on what kind of support one can expect to receive.

Status : Open

Created 2017-10-20T14:39:17+00:00, updated 2022-04-27T21:02:12+00:00

Labels: content

#9 In general, removing an HTML page and going to the directory level should not give a 403

Going from e.g. https://docs.fedoraproject.org/f26/release-notes/sysadmin/Kernel.html to
https://docs.fedoraproject.org/f26/release-notes/sysadmin/ gives a 403 error. This looks sloppy. Doing this should take you up one step in the navigation, just like clicking one step back in the cookie-crumbs navigation. 

As I understand the structure, though, the above should take you to https://docs.fedoraproject.org/f26/release-notes/sysadmin/Modularity.html, which is a little odd. Apparently each level of the tree does not have its own node?

I think probably we want to do this with redirects, so that there is a canonical name for each document — that is,  https://docs.fedoraproject.org/f26/release-notes/sysadmin/ should redirect to https://docs.fedoraproject.org/f26/release-notes/sysadmin/overview.html or whatever.

Status : Open

Created 2017-08-27T14:07:20+00:00, updated 2022-03-09T19:40:06+00:00

Labels: tooling

#533 Review of older documents: How to enable nested virtualization in KVM

We decided to start a Review of older Quick Docs articles:

Content: Is it technically up to date?
Quality: determine the type (how-to, tutorial, guide,...)
Usability: Add author (optional), related Fedora release, date of last substantial review/update

Subject here: [How to enable nested virtualization in KVM](https://docs.fedoraproject.org/en-US/quick-docs/using-nested-virtualization-in-kvm/)

Status : Open

Created 2022-12-27T12:24:20+00:00, updated 2023-05-05T06:35:58+00:00

Labels: needs info

Assigned to pboy

#529 Link to (old) Wiki page "Reset Bootloader Password"

By chance I found, that the QD article "How to Reset the root Password" (#524) links to a (old) WIKI page [Reset Bootloader Password](https://fedoraproject.org/wiki/Reset_Bootloader_Password). 

* Is that Wiki page still current? 
* Should we transfer the Wiki page or remove the link to it?

Status : Open

Created 2022-12-19T19:34:01+00:00, updated 2023-05-05T06:36:31+00:00

#524 Review of older documents: How to Reset the root Password

We decided to start a Review of older Quick Docs articles:

* Content: Is it technically up to date?
* Quality: determine the type (how-to, tutorial, guide,...)
* Usability: Add author (optional), related Fedora release, date of last substantial review/update

URL: https://docs.fedoraproject.org/en-US/quick-docs/reset-root-password/ 

Status : Open

Created 2022-12-09T07:36:02+00:00, updated 2023-05-05T06:38:15+00:00

Assigned to computersavvy

#183 "Running Windows applications with Wine" needs review

https://docs.fedoraproject.org/en-US/quick-docs/wine/ was autoconverted and needs review

Status : Open

Created 2020-03-02T19:39:58+00:00, updated 2020-03-02T19:39:58+00:00

Labels: help wanted improvement

#76 [f35] Doc issue in file modules/system-administrators-guide/pages/kernel-module-driver-configuration/Working_with_the_GRUB_2_Boot_Loader.adoc

The https://fedoraproject.org/wiki/GRUB_2 says "Refrain from using grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg going forward. This is a valid location on Fedora 33 and earlier. However on Fedora 34 and later, it is a small stub file that merely forwards to /boot/grub2/grub.cfg. See the Reinstalling GRUB section if you have accidentally overwritten this file."

But the system administrator's guide says otherwise, this can confuse people, it'd be nice if it can be fixed.

Status : Open

Created 2022-04-09T17:11:12+00:00, updated 2022-04-09T17:11:12+00:00

#30 Contrary to docs it's not totally impossible to switch an install between BIOS and UEFI

In section Preparing to boot we say that it's impossible to migrate between BIOS and UEFI once the system is installed. Apparently that's not completely true: https://oded.blog/2017/11/13/fedora-bios-to-uefi/

We should amend that to say it's possible and link the post while stressing that this is dangerous and might ruin your install.

Status : Open

Created 2019-05-23T12:47:41+00:00, updated 2019-05-23T12:47:41+00:00

#270 Adjust status icons in buglist

Some of the buglist view are confusing. The light bulb and green circle icon are not immediately clear what they mean. It also seems that it's overkill to highlight any activity in any bug - usually the light bulb is displayed for half of the bugs.

Let's get rid of those two status icons and instead let's add a short clear label for new bugs proposed in the last 2 days, I'd say.

I think we could possibly even reuse the current data we have for the green circle icon ("blocker/fe status changed recently"), and just use it to display the new label. But this needs to be verified. It might turn out that it's not exactly that, and that it's not that easy to figure out when was the bug proposed.

Status : Open

Created 2023-03-16T13:27:55+00:00, updated 2023-03-16T13:28:52+00:00

Labels: enhancement

#269 Copy justification to the voting tickets

imho, it'd be good idea if we copied proposal justification to the voting ticket, if the proposal was done via the blockerbugs application.

Status : Open

Created 2023-03-15T16:57:13+00:00, updated 2023-03-16T12:57:51+00:00

Labels: enhancement

#253 Make it clear when an old inactive milestone is accessed

When the user sees data for an old invalid milestone, it is not immediately obvious. For example, look at data for F35 Final:
https://qa.fedoraproject.org/blockerbugs/milestone/35/final/buglist

It is not clear that it's F35. It is not clear that it's no longer updated.

Proposed solution:
If the displayed milestone is not active, show the milestone identification ("Fedora 35 Final") and some visible warning dialog that this milestone is no longer active and the displayed data are outdated. Make sure to display it in all related views (Info, Bug List, Updates).

Status : Open

Created 2022-06-23T10:16:10+00:00, updated 2023-04-19T17:52:41+00:00

Labels: enhancement next

Assigned to harvey010

#249 Mention ON_QA/VERIFIED bugs without an update in Requests

Bodhi updates are often not linked to accepted bugs. In that case, it's easy to miss that a blocker/FE fix is ready to be included/pushed. We can't do much about it, but can at least notify readers when the state is suspicious. If bugs are in ON_QA or VERIFIED state, but they don't have any linked update, that's suspicious. Let's add another alert section into `/requests` (we already have one for bug dependencies) which will list such bugs and ask the person to inspect them manually.

@adamwill 

Status : Open

Created 2022-05-02T20:27:50+00:00, updated 2022-05-02T20:28:53+00:00

Labels: enhancement next

#245 shorten long update titles

If there's a Bodhi update with a very long title (e.g. with 50 builds included), it can occupy a lot of space and make the UI elements harder to read and navigate. It's probably a good idea to shorten it, either by cropping after X characters, or by using the update id instead of update title in these cases (not always). This affects the bug list view, the updates view, and the requests view.

Status : Open

Created 2022-03-11T11:10:16+00:00, updated 2024-03-08T20:22:20+00:00

Labels: enhancement next

#221 "Voted" label shows even if I didn't vote for that particular tracker

If a bug is proposed as a blocker and a freeze exception, voting just for one of the trackers makes the label "Voted" appear in buglist under both sections (proposed blockers and proposed FEs). Ideally "Voted" should appear only under that section which I actually voted for, and there should be standard "Vote" in the other one.

Status : Open

Created 2021-10-20T07:37:09+00:00, updated 2021-10-20T07:39:48+00:00

Labels: bug next

#220 buglist votes don't consider 0Day and PreviousRelease

When voting for a proposed blocker, it is also possible to vote as `0Day +1` or `PreviousRelease +1`. However, the buglist view only considers `Beta/FinalBlocker +1` votes, when showing the counts, and that's wrong. For example, in https://pagure.io/fedora-qa/blocker-review/issue/521 there was:

> Current vote summary
>    0Day (+7, 0, -0)
>        +1 by catanzaro, mohanboddu, bcotton, kevin, lruzicka, geraldosimiao, ngompa

but https://qa.fedoraproject.org/blockerbugs/milestone/35/final/buglist showed `+0, 0, -0` in the **Review** column.

Status : Open

Created 2021-10-11T11:50:17+00:00, updated 2021-10-11T14:40:22+00:00

Labels: bug next

#219 Highlight certain bug states

If bug states (NEW, MODIFIED, etc) were differentiated slightly, it could draw eyes to those which are currently in a test-able state. So MODIFIED and ON_QA labels could be colored, or perhaps in bold. And VERIFIED on the other hand could be gray, or similar, to indicate that your eyes can skip that entry. Just an idea to try out.

Status : Open

Created 2021-10-07T10:24:45+00:00, updated 2021-10-07T10:26:42+00:00

Labels: enhancement next

#561 Package dabest: Data Analysis and Visualization using Bootstrap-Coupled Estimation

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: dabest

Short description: Data Analysis and Visualization using Bootstrap-Coupled Estimation

Upstream URL: https://acclab.github.io/DABEST-python-docs/ + https://github.com/ACCLAB/DABEST-python

License: ASL-2.0

Domain: Data analysis/Utilities


##### Additional information

Status : Open

Created 2023-10-18T10:28:49+00:00, updated 2023-10-18T10:29:31+00:00

Labels: D: Normal F: Data Analysis S: Needs packaging T: Software

Assigned to ankursinha

#560 Package vispy: high-performance interactive 2D/3D data visualization library

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: vispy

Short description: VisPy is a high-performance interactive 2D/3D data visualization library leveraging the computational power of modern Graphics Processing Units (GPUs) through the OpenGL library to display very large datasets.

Upstream URL: https://vispy.org/ + https://github.com/vispy/vispy

License: BSD

Domain: (Computational modelling/Neuroimaging/Data analysis/Utilities)


##### Additional information

Status : Open

Created 2023-09-17T16:48:48+00:00, updated 2023-09-17T16:48:48+00:00

Labels: D: Normal F: Data Analysis F: Utilities S: Needs packaging T: Software

#559 Package pydapsys: an open-source library for accessing electrophysiology data recorded with DAPSYS

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: pydapsys
Short description:  an open-source library for accessing electrophysiology data recorded with DAPSYS

Upstream URL:  https://pypi.org/project/pydapsys/ + https://github.com/Digital-C-Fiber/PyDapsys

License: BSD-3-Clause

Domain: (Computational modelling/Neuroimaging/Data analysis/Utilities)


##### Additional information
https://www.frontiersin.org/articles/10.3389/fninf.2023.1250260/full

Status : Open

Created 2023-09-14T10:35:44+00:00, updated 2023-09-14T10:35:44+00:00

Labels: D: Easy F: Data Analysis F: Utilities S: Needs packaging T: Software

#557 Package SWC_BATCH_CHECK: Provides methods for batch validating data in SWC neuron morphology files

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: SWC_BATCH_CHECK

Short description: Provides methods for batch validating data in SWC neuron morphology files

Upstream URL: https://github.com/dohalloran/SWC_BATCH_CHECK

License: GPL-2.0

Domain: Data analysis/Utilities


##### Additional information

Written in Perl, so should be easy to package.

Peer-reviewed publication: https://journals.plos.org/plosone/article?id=10.1371%2Fjournal.pone.0228091

Status : Open

Created 2023-09-11T15:52:29+00:00, updated 2023-09-11T15:52:29+00:00

Labels: D: Easy F: Data Analysis F: Utilities S: Needs packaging T: Software

#556 Package sciris: Fast, flexible tools to simplify scientific Python

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: sciris

Short description: Fast, flexible tools to simplify scientific Python

Upstream URL: https://github.com/sciris/sciris

License: MIT

Domain: Utilities


##### Additional information

Status : Open

Created 2023-08-24T12:06:33+00:00, updated 2023-12-15T16:26:52+00:00

Labels: D: Easy F: Utilities S: In review T: Software

Assigned to nerdsville

#553 Package Grape: GRAPE is a Rust/Python Graph Representation Learning library for Predictions and Evaluation

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: grape

Short description: GRAPE is a Rust/Python Graph Representation Learning library for Predictions and Evaluation

Upstream URL: https://github.com/AnacletoLAB/grape

License: MIT

Domain: Computational modelling/Data analysis/Utilities


##### Additional information

https://www.nature.com/articles/s43588-023-00466-7

Says it'll probably be faster than networkx, but I didn't see a mention of graphtool.

Python, but also rust from the looks of it.

Status : Open

Created 2023-06-29T09:45:42+00:00, updated 2023-06-30T20:34:30+00:00

Labels: D: Normal F: Computational neuroscience F: Data Analysis F: Utilities S: Needs packaging T: Software

#550 Package PHATE: Visualizing Transitions and Structure for Biological Data Exploration

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: phate
Short description: Visualizing Transitions and Structure for Biological Data Exploration

Upstream URL: https://github.com/KrishnaswamyLab/PHATE

License: GPL-2.0

Domain: Data analysis


##### Additional information

Associated paper (a good read): https://www.nature.com/articles/s41587-019-0336-3

Status : Open

Created 2023-06-08T13:06:41+00:00, updated 2023-06-08T13:09:13+00:00

Labels: D: Easy F: Data Analysis S: Needs packaging T: Software

#547 Package MouseLand/rastermap: A multi-dimensional embedding algorithm

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: MouseLand/rastermap

Short description: A multi-dimensional embedding algorithm

Upstream URL: https://github.com/MouseLand/rastermap

License: GPLv3

Domain: Data analysis/Utilities


##### Additional information

Python based, also has a PyQT based GUI

Status : Open

Created 2023-05-25T10:46:39+00:00, updated 2023-05-25T10:46:39+00:00

Labels: D: Normal F: Data Analysis F: Utilities S: Needs packaging T: Software

#546 Package sanpy: software for whole-cell current clamp analysis

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: sanpy

Short description: software for whole-cell current clamp analysis.

Upstream URL: https://github.com/cudmore/SanPy

License: GPL-3

Domain: Data analysis


##### Additional information

Status : Open

Created 2023-05-18T13:05:03+00:00, updated 2023-05-18T13:05:03+00:00

Labels: D: Normal F: Data Analysis F: Neuroimaging S: Needs packaging T: Software

#545 Package pynapple: PYthon Neural Analysis Package

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: pynapple

Short description: a light-weight python library for neurophysiological data analysis

Upstream URL: https://github.com/pynapple-org/pynapple

License: GPLv3

Domain: Data analysis/Utilities


##### Additional information

Status : Open

Created 2023-05-18T12:48:30+00:00, updated 2023-05-18T12:53:26+00:00

Labels: D: Easy F: Data Analysis S: Needs packaging T: Software

#541 Package python-meshparty: A package to work with meshes, designed around use cases for analyzing neuronal morphology.

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: python-meshparty

Short description: A package to work with meshes, designed around use cases for analyzing neuronal morphology.



Upstream URL: https://github.com/sdorkenw/MeshParty

License: ASL 2.0

Domain: Data analysis/Utilities


##### Additional information

Status : Open

Created 2023-02-28T13:40:24+00:00, updated 2023-05-21T14:02:31+00:00

Labels: D: Easy F: Data Analysis F: Utilities S: Needs packaging T: Software

#531 Package ontquery: a framework querying ontology terms

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: ontquery

Short description: a framework querying ontology terms

Upstream URL: https://pypi.org/project/ontquery/  and  https://github.com/tgbugs/ontquery

License: MIT

Domain: Utilities


##### Additional information

Status : Open

Created 2022-09-29T13:24:52+00:00, updated 2022-09-29T13:24:52+00:00

Labels: D: Easy F: Utilities S: Needs packaging T: Software

#529 Package Neurokit: Python Toolbox for Neurophysiological Signal Processing

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: NeuroKit

Short description: Python Toolbox for Neurophysiological Signal Processing

Upstream URL: https://github.com/neuropsychology/NeuroKit

License: MIT

Domain: Data analysis


##### Additional information

The major deps seem to be all in Fedora, so should be OK to package:

https://github.com/neuropsychology/NeuroKit/blob/master/setup.py#L29

Status : Open

Created 2022-09-05T15:18:40+00:00, updated 2022-09-05T15:18:40+00:00

Labels: D: Normal F: Data Analysis S: Needs packaging T: Software

#524 Package blenderNEURON: Exports 3D structure and activity from NEURON simulator to Blender

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: blenderNEURON

Short description: Exports 3D structure and activity from NEURON simulator to Blender

Upstream URL: https://github.com/JustasB/BlenderNEURON and https://blenderneuron.org/

License: MIT

Domain: Computational modelling/Utilities


##### Additional information

Looks like a straightforwared python project.

Status : Open

Created 2022-07-27T16:28:57+00:00, updated 2022-07-27T16:28:57+00:00

Labels: D: Easy F: Computational neuroscience F: Utilities S: Needs packaging

#523 Package genepy3D: a python library for quantitative geometry,

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: genepy3d

Short description: GeNePy3D is a python library for quantitative geometry, in particular in the context of quantitative microscopy. It aims at providing an easy interface to perform complex data science workflow on geometric data, manipulating point cloud, surfaces, curves and trees, converting between them, and performing analysis tasks to extract information and knowledge out of raw geometrical data.

Upstream URL: https://genepy3d.gitlab.io/

License: https://genepy3d.gitlab.io/#licences : BSD/GPL (for CGAL)

Domain:Data analysis


##### Additional information
Should be relatively straightforward

Status : Open

Created 2022-07-07T11:06:21+00:00, updated 2022-07-07T11:06:44+00:00

Labels: D: Normal F: Data Analysis F: Utilities S: Needs packaging T: Software

#522 Package ipympl: matplotlib extension for jupyter

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: ipympl

Short description: matplotlib extension for jupyter

Upstream URL: https://pypi.org/project/ipympl/

License: BSD

Domain: Utilities


##### Additional information
Should be a straightforward package.

Status : Open

Created 2022-07-05T12:02:54+00:00, updated 2022-08-22T18:00:53+00:00

Labels: D: Easy F: Utilities S: Needs packaging T: Software

#521 Package python-grip: Render local readme files before sending off to GitHub.

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: python-grip

Short description: Render local readme files before sending off to GitHub.

Upstream URL: https://pypi.org/project/grip/

License: MIT

Domain: Utilities


##### Additional information
A simple utility, should be simple enough to package.

Status : Open

Created 2022-07-01T10:31:38+00:00, updated 2022-08-30T10:48:29+00:00

Labels: D: Easy F: Utilities S: Needs packaging

Assigned to vanessakris

#519 Package ngltr/sinaps: a Python package providing a fast, flexible and expressive tool to model signal propagation and ionic electrodiffusion in neurons

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: Sinaps

Short description: a Python package providing a fast, flexible and expressive tool to model signal propagation and ionic electrodiffusion in neurons

Upstream URL: https://sinaps.readthedocs.io/en/stable/ and https://github.com/ngltr/sinaps

License: GPLv3
 
Domain: Computational modelling


##### Additional information

Status : Open

Created 2022-05-17T09:56:24+00:00, updated 2022-08-23T15:03:08+00:00

Labels: D: Easy F: Computational neuroscience S: Needs packaging

Assigned to vanessakris

#517 Package PeyracheLab/pynapple: PYthon Neural Analysis Package

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: pynapple

Short description: PeyracheLab/pynapple: PYthon Neural Analysis Package

Upstream URL: https://github.com/PeyracheLab/pynapple

License: GPLv3

Domain: Data analysis/Utilities


##### Additional information

Status : Open

Created 2022-04-13T10:33:58+00:00, updated 2022-04-13T10:33:58+00:00

Labels: D: Easy F: Data Analysis S: Needs packaging T: Software

#516 Package biokit/biokit: Bioinformatics in Python

Please use this ticket to add new software to the NeuroFedora packaging queue.

#### New software: biokit

Short description: biokit/biokit: Bioinformatics in Python

Upstream URL: https://github.com/biokit/biokit

License: BSD

Domain: Data analysis/Utilities


##### Additional information

Status : Open

Created 2022-04-07T14:41:11+00:00, updated 2022-04-07T14:41:11+00:00

Labels: D: Easy F: Data Analysis S: Needs packaging T: Software

#392 Replace hawkey usage with libdnf

Apparently, [hawkey](https://github.com/rpm-software-management/hawkey) has been replaced by [libdnf](https://github.com/rpm-software-management/libdnf) with warnings that hawkey has been depricated and will get farther development. libdnf/libhif warns that it's not stable right now, so I'm not entirely sure what we're supposed to be using.

Replace hawkey references (ext/fedora/rpm_utils.py) with code that utilizes libdnf. If hawkey is stable for now and libdnf is not, it might be worth waiting a bit until that stabilizes.

Status : Open

Created 2017-08-23T19:33:53+00:00, updated 2018-11-22T09:33:06+00:00

#379 allow to specify config file from cmdline

This is inconvenient:

> Taskotron’s configuration file needs adjustments to communicate with the staging environment. Unfortunately, the runtask command does not currently have an option to specify an alternate configuration file. Thus, you have to modify /etc/taskotron/taskotron.yaml each time you want to switch between production and staging.

https://osmerlin.wordpress.com/2017/04/18/how-to-configure-your-fedora-development-system-to-access-the-fedora-staging-infrastructure/

Let's add a cmdline option to specify the config file.

Status : Open

Created 2017-04-19T08:39:04+00:00, updated 2018-07-10T09:05:40+00:00

#354 create_report_directive: improve rendering when there's no artifact, cover with unit tests

In [D945](https://fedorapeople.org/groups/qa/phabarchive/differentials/phab.qa.fedoraproject.org/D945.html) we quickly fixed a crash that occurred when ResultsYAML items had no `artifact` defined. It fixed the crash, but it did not fix the template rendering (the artifact currently shows as hyperlinked "None" and it leads to a `/path/None` file) and it did not cover the bug with a unit test.

Please improve the rendering (for example, if there's no artifact, show `---` similarly to a missing Note and don't hyperlink it) and also add unit tests to cover this change.

Thanks.

Status : Open

Created 2016-07-21T14:08:02+00:00, updated 2018-07-12T21:58:42+00:00

#312 download progressbars are printed out into stdio logs

There are now download progressbars printed out into logs when files are being downloaded:
```
[libtaskotron:file_utils.py:120] 2016-01-08 09:14:47 DEBUG   Downloading: http://kojipkgs.fedoraproject.org/packages/python-matplotlib/1.4.3/9.fc22/i686/python2-matplotlib-1.4.3-9.fc22.i686.rpm
  0%|                                                |ETA:  --:--:--  0.00  B/s
  2%|#                                                |ETA:  0:00:00 64.36 MB/s
  5%|##                                               |ETA:  0:00:00 73.43 MB/s
  8%|####                                             |ETA:  0:00:00 75.56 MB/s
 11%|#####                                            |ETA:  0:00:00 77.82 MB/s
 14%|######                                           |ETA:  0:00:00 79.33 MB/s
 16%|########                                         |ETA:  0:00:00 79.75 MB/s
 19%|#########                                        |ETA:  0:00:00 80.25 MB/s
 22%|###########                                      |ETA:  0:00:00 80.92 MB/s
 25%|############                                     |ETA:  0:00:00 81.48 MB/s
 28%|#############                                    |ETA:  0:00:00 76.86 MB/s
 31%|###############                                  |ETA:  0:00:00 67.87 MB/s
 33%|################                                 |ETA:  0:00:00 71.42 MB/s
 36%|##################                               |ETA:  0:00:00 71.37 MB/s
 39%|###################                              |ETA:  0:00:00 70.64 MB/s
 42%|####################                             |ETA:  0:00:00 69.26 MB/s
 45%|######################                           |ETA:  0:00:00 66.91 MB/s
 48%|#######################                          |ETA:  0:00:00 65.87 MB/s
 50%|########################                         |ETA:  0:00:00 64.96 MB/s
 53%|##########################                       |ETA:  0:00:00 63.72 MB/s
 56%|###########################                      |ETA:  0:00:00 62.41 MB/s
 59%|#############################                    |ETA:  0:00:00 60.41 MB/s
 62%|##############################                   |ETA:  0:00:00 58.65 MB/s
 65%|###############################                  |ETA:  0:00:00 56.84 MB/s
 67%|#################################                |ETA:  0:00:00 55.39 MB/s
 70%|##################################               |ETA:  0:00:00 51.85 MB/s
 73%|####################################             |ETA:  0:00:00 51.34 MB/s
 76%|#####################################            |ETA:  0:00:00 50.95 MB/s
 79%|######################################           |ETA:  0:00:00 50.40 MB/s
 81%|########################################         |ETA:  0:00:00 49.06 MB/s
 84%|#########################################        |ETA:  0:00:00 48.57 MB/s
 87%|##########################################       |ETA:  0:00:00 48.05 MB/s
 90%|############################################     |ETA:  0:00:00 47.54 MB/s
 93%|#############################################    |ETA:  0:00:00 47.14 MB/s
 96%|###############################################  |ETA:  0:00:00 46.71 MB/s
 98%|################################################ |ETA:  0:00:00 46.23 MB/s
100%|#################################################|ETA:  0:00:00 46.16 MB/s
100%|#################################################|Time: 0:00:00 46.14 MB/s
```
This does seem to affect only 'stdio' logs, not standard taskotron debug logs.

I think this is caused by a combination of two factors:
a) we enabled DEBUG level printing into standard output
b) we run in a remote minion mode and capture stdout over ssh and save it into a log file

So I guess `python-progressbar` thinks it's printing to a terminal, so it's printing progress bars, but in fact it's stdio over ssh captured to a file. I don't know if we can do something about this, but I file this ticket so that we at least have a look. With the current approach the logs are not really nice and they occupy more disk space.

As a tip, it would be interesting to compare what `urlgrabber` used to do, and if it behaved differently in this case, find out how it detected terminal/non-terminal output and put the same patch into `python-progressbar`.

Status : Open

Created 2016-01-13T13:54:50+00:00, updated 2017-08-04T17:06:54+00:00

#20 Report rpmlint version used for checks

Looking at taskotron results \[[1]\], there are reported some issues (specifically the "specfile-error error") I cannot see in rpmlint output I tried locally. I suspect that this is due to different version of rpmlint, but it is hard to tell. It would be nice if rpmlint version was recorded alongside the results, so I knew how to reproduce locally.

[1]: https://taskotron.fedoraproject.org/artifacts/all/df5bd6ec-bbf6-11e8-8509-525400fc9f92/tests.yml/vagrant-2.1.2-2.fc29.log

Status : Open

Created 2018-10-05T09:11:00+00:00, updated 2018-10-05T14:09:37+00:00