Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
156,535 | 5,970,954,034 | IssuesEvent | 2017-05-31 00:29:47 | mozafari/verdict | https://api.github.com/repos/mozafari/verdict | closed | Sometimes we can make the confidence interval for `count` smaller than what we get from bootstrap | enhancement low priority | example:
when result of `count` on the sample is `a` and the confidence interval is `[s,t]` where `s < a`, more accurate answer c.i. is `[a,t]`. Because the true answer cannot be smaller than the result on the sample.
| 1.0 | Sometimes we can make the confidence interval for `count` smaller than what we get from bootstrap - example:
when result of `count` on the sample is `a` and the confidence interval is `[s,t]` where `s < a`, more accurate answer c.i. is `[a,t]`. Because the true answer cannot be smaller than the result on the sample.
| priority | sometimes we can make the confidence interval for count smaller than what we get from bootstrap example when result of count on the sample is a and the confidence interval is where s a more accurate answer c i is because the true answer cannot be smaller than the result on the sample | 1 |
603,111 | 18,527,418,735 | IssuesEvent | 2021-10-20 22:39:02 | NOAA-GSL/VxIngest | https://api.github.com/repos/NOAA-GSL/VxIngest | opened | Specify isobaric levels for each model | enhancement Priority: Low | In the legacy ingest, upper air isobaric verification was done using assumptions in the code as to what levels existed inside the model grib2 output. Ensure that this does not happen when designing the new UA ingest and work to find another solution, whether it be in model configuration or in pygrib file quering. | 1.0 | Specify isobaric levels for each model - In the legacy ingest, upper air isobaric verification was done using assumptions in the code as to what levels existed inside the model grib2 output. Ensure that this does not happen when designing the new UA ingest and work to find another solution, whether it be in model configuration or in pygrib file quering. | priority | specify isobaric levels for each model in the legacy ingest upper air isobaric verification was done using assumptions in the code as to what levels existed inside the model output ensure that this does not happen when designing the new ua ingest and work to find another solution whether it be in model configuration or in pygrib file quering | 1 |
485,613 | 13,996,075,441 | IssuesEvent | 2020-10-28 04:57:32 | gradebook/server | https://api.github.com/repos/gradebook/server | closed | Allow grade names to be up to 55 characters in length | Effort: Low Priority: Medium question | Currently, we allow grades to have a maximum of 50 character names. This is normally fine, but now that we've made changes to the create category UI, we're running into validation errors with really long category names.
Why? Because category names and grade names have the same maximum length (50ch), but grade names have more context than category names (adding the grade "id")
As an example, if you have a category called `This will be a very long category name for a demos`, the grades will be `This will be a very long category name for a demo 35` which is 52 characters and fails validation
Proposal:
Update grade max length to be 55ch to account for increased context
@joshcosta what do you think, do you see any issues with this? | 1.0 | Allow grade names to be up to 55 characters in length - Currently, we allow grades to have a maximum of 50 character names. This is normally fine, but now that we've made changes to the create category UI, we're running into validation errors with really long category names.
Why? Because category names and grade names have the same maximum length (50ch), but grade names have more context than category names (adding the grade "id")
As an example, if you have a category called `This will be a very long category name for a demos`, the grades will be `This will be a very long category name for a demo 35` which is 52 characters and fails validation
Proposal:
Update grade max length to be 55ch to account for increased context
@joshcosta what do you think, do you see any issues with this? | priority | allow grade names to be up to characters in length currently we allow grades to have a maximum of character names this is normally fine but now that we ve made changes to the create category ui we re running into validation errors with really long category names why because category names and grade names have the same maximum length but grade names have more context than category names adding the grade id as an example if you have a category called this will be a very long category name for a demos the grades will be this will be a very long category name for a demo which is characters and fails validation proposal update grade max length to be to account for increased context joshcosta what do you think do you see any issues with this | 1 |
286,144 | 8,784,240,477 | IssuesEvent | 2018-12-20 09:16:25 | cortex-lab/alyx | https://api.github.com/repos/cortex-lab/alyx | closed | Read from LAMIS, especially cages | feature priority: low | Since BSU already keeps track of cages/cage movements, it would be ideal to take advantage of this automatically. | 1.0 | Read from LAMIS, especially cages - Since BSU already keeps track of cages/cage movements, it would be ideal to take advantage of this automatically. | priority | read from lamis especially cages since bsu already keeps track of cages cage movements it would be ideal to take advantage of this automatically | 1 |
299,335 | 9,205,369,905 | IssuesEvent | 2019-03-08 10:22:59 | qissue-bot/QGIS | https://api.github.com/repos/qissue-bot/QGIS | closed | Layer Properties/Legendtype/Individual Symbol | Category: Symbology Component: Affected QGIS version Component: Crashes QGIS or corrupts data Component: Easy fix? Component: Operating System Component: Pull Request or Patch supplied Component: Regression? Component: Resolution Priority: Low Project: QGIS Application Status: Closed Tracker: Bug report | ---
Author Name: **horst-duester -** (horst-duester -)
Original Redmine Issue: 732, https://issues.qgis.org/issues/732
Original Assignee: nobody -
---
When I select a classification field N the field N-1 is classified.
| 1.0 | Layer Properties/Legendtype/Individual Symbol - ---
Author Name: **horst-duester -** (horst-duester -)
Original Redmine Issue: 732, https://issues.qgis.org/issues/732
Original Assignee: nobody -
---
When I select a classification field N the field N-1 is classified.
| priority | layer properties legendtype individual symbol author name horst duester horst duester original redmine issue original assignee nobody when i select a classification field n the field n is classified | 1 |
354,590 | 10,569,840,364 | IssuesEvent | 2019-10-06 22:21:03 | MisaelUrq/Blueberry-Issues | https://api.github.com/repos/MisaelUrq/Blueberry-Issues | closed | Modificar información de la empresa. | empresas enhancement priority-low | No nos permite modificar información de la empresa una vez guardada, como lo es RFC y Domicilio | 1.0 | Modificar información de la empresa. - No nos permite modificar información de la empresa una vez guardada, como lo es RFC y Domicilio | priority | modificar información de la empresa no nos permite modificar información de la empresa una vez guardada como lo es rfc y domicilio | 1 |
234,054 | 7,715,708,048 | IssuesEvent | 2018-05-23 08:31:05 | telerik/kendo-ui-core | https://api.github.com/repos/telerik/kendo-ui-core | closed | Chart MVC wrapper is missing Line configuration for Waterfall series | Bug C: Chart Kendo1 Priority 1 S: Wrappers (ASP.NET MVC) SEV: Low | ### Bug report
The Chart MVC wrapper is missing the Line setting for Waterfall series, described in the jQuery docs here:
[series.line](https://docs.telerik.com/kendo-ui/api/javascript/dataviz/ui/chart/configuration/series.line#series.line)
The Line configuration can re-use the [ChartLine type](https://github.com/telerik/kendo/blob/master/wrappers/mvc/src/Kendo.Mvc/UI/Chart/ChartLine.cs), as all four properties (color, dashType, width, visible) get correctly applied when testing in a jQuery Waterfall Chart.
### Environment
* **Kendo UI version:** 2018.1.221
| 1.0 | Chart MVC wrapper is missing Line configuration for Waterfall series - ### Bug report
The Chart MVC wrapper is missing the Line setting for Waterfall series, described in the jQuery docs here:
[series.line](https://docs.telerik.com/kendo-ui/api/javascript/dataviz/ui/chart/configuration/series.line#series.line)
The Line configuration can re-use the [ChartLine type](https://github.com/telerik/kendo/blob/master/wrappers/mvc/src/Kendo.Mvc/UI/Chart/ChartLine.cs), as all four properties (color, dashType, width, visible) get correctly applied when testing in a jQuery Waterfall Chart.
### Environment
* **Kendo UI version:** 2018.1.221
| priority | chart mvc wrapper is missing line configuration for waterfall series bug report the chart mvc wrapper is missing the line setting for waterfall series described in the jquery docs here the line configuration can re use the as all four properties color dashtype width visible get correctly applied when testing in a jquery waterfall chart environment kendo ui version | 1 |
64,015 | 3,203,661,911 | IssuesEvent | 2015-10-02 20:13:17 | coreyjackwilson/Locl | https://api.github.com/repos/coreyjackwilson/Locl | closed | Database Management/Admin System | Backend Database Low Priority | - [ ] There is a portal that the Admin can login to to see the database visually and issue commands
- [ ] Admin can query stores, users, sales, items, preferences
- [ ] Admin can edit/update/insert stores, users, items, preferences, UUID lists
- [ ] Admin can attach/detach Facebook
POSSIBLE
- [ ] Admin can send notifications to device
- [ ] Admin can request current information from device
- [ ] Admin can see a map of store locations, with visual representations for when store is open, selling, closed, etc | 1.0 | Database Management/Admin System - - [ ] There is a portal that the Admin can login to to see the database visually and issue commands
- [ ] Admin can query stores, users, sales, items, preferences
- [ ] Admin can edit/update/insert stores, users, items, preferences, UUID lists
- [ ] Admin can attach/detach Facebook
POSSIBLE
- [ ] Admin can send notifications to device
- [ ] Admin can request current information from device
- [ ] Admin can see a map of store locations, with visual representations for when store is open, selling, closed, etc | priority | database management admin system there is a portal that the admin can login to to see the database visually and issue commands admin can query stores users sales items preferences admin can edit update insert stores users items preferences uuid lists admin can attach detach facebook possible admin can send notifications to device admin can request current information from device admin can see a map of store locations with visual representations for when store is open selling closed etc | 1 |
617,135 | 19,343,853,585 | IssuesEvent | 2021-12-15 08:46:14 | Code-Poets/sheetstorm | https://api.github.com/repos/Code-Poets/sheetstorm | closed | Inconsistent layout in projects list | bug priority low UX | I think Sheet Storm and Others field should have same size.
| 1.0 | Inconsistent layout in projects list - I think Sheet Storm and Others field should have same size.
| priority | inconsistent layout in projects list i think sheet storm and others field should have same size | 1 |
659,976 | 21,946,555,918 | IssuesEvent | 2022-05-24 01:41:17 | 3jins/blog-renewal | https://api.github.com/repos/3jins/blog-renewal | opened | [IMPROVE] Edit all tests with D-C-T BDD pattern | type: improvement field: backend priority: low | - Refer this: https://johngrib.github.io/wiki/junit5-nested
- Most of nested `describe`s would be replaced with `context`. | 1.0 | [IMPROVE] Edit all tests with D-C-T BDD pattern - - Refer this: https://johngrib.github.io/wiki/junit5-nested
- Most of nested `describe`s would be replaced with `context`. | priority | edit all tests with d c t bdd pattern refer this most of nested describe s would be replaced with context | 1 |
732,583 | 25,266,381,670 | IssuesEvent | 2022-11-16 05:10:33 | climbjios-sg/climbjios-app | https://api.github.com/repos/climbjios-sg/climbjios-app | closed | Refactor: Change relative imports to absolute imports | priority.Low difficulty.M | **Describe the solution you'd like**
Change relative to absolute imports for cleaner imports
**Additional context**
Add any other context or screenshots about the feature request here.
See discussion in PR here
https://github.com/climbjios-sg/climbjios-app/pull/49#discussion_r993628315
| 1.0 | Refactor: Change relative imports to absolute imports - **Describe the solution you'd like**
Change relative to absolute imports for cleaner imports
**Additional context**
Add any other context or screenshots about the feature request here.
See discussion in PR here
https://github.com/climbjios-sg/climbjios-app/pull/49#discussion_r993628315
| priority | refactor change relative imports to absolute imports describe the solution you d like change relative to absolute imports for cleaner imports additional context add any other context or screenshots about the feature request here see discussion in pr here | 1 |
388,933 | 11,495,240,690 | IssuesEvent | 2020-02-12 04:07:28 | wso2/product-is | https://api.github.com/repos/wso2/product-is | opened | Handling Last login time as identity claim | Affected/5.10.0-beta Complexity/Low Component/Identity Mgt Component/Migration Priority/High Type/Docs | With the fix \[1] we are handling the Last login time(which claim is used in account suspension) as identity claim in identity server. Before the fix we have handled the last login claim as default claim. Since this is a behavioural change we have introduced a new property to disable this behaviour.
If you want to get the previous behaviour please add the following property in deployment.toml file
```
[account.suspension]
lastlogin_as_default_claim=true
```
\[1] https://github.com/wso2-extensions/identity-governance/pull/358 | 1.0 | Handling Last login time as identity claim - With the fix \[1] we are handling the Last login time(which claim is used in account suspension) as identity claim in identity server. Before the fix we have handled the last login claim as default claim. Since this is a behavioural change we have introduced a new property to disable this behaviour.
If you want to get the previous behaviour please add the following property in deployment.toml file
```
[account.suspension]
lastlogin_as_default_claim=true
```
\[1] https://github.com/wso2-extensions/identity-governance/pull/358 | priority | handling last login time as identity claim with the fix we are handling the last login time which claim is used in account suspension as identity claim in identity server before the fix we have handled the last login claim as default claim since this is a behavioural change we have introduced a new property to disable this behaviour if you want to get the previous behaviour please add the following property in deployment toml file lastlogin as default claim true | 1 |
103,490 | 4,174,066,985 | IssuesEvent | 2016-06-21 12:57:32 | eXistSolutions/hsg-shell | https://api.github.com/repos/eXistSolutions/hsg-shell | closed | Improve search summary for zero results | bug low priority xquery | As seen on pages with 0 search results, such as https://history.state.gov/search?q=%22America+of+States+United%22:
> Displaying 1–0 of 0 results.
A better message would be: No results were found. Or 0 results found. | 1.0 | Improve search summary for zero results - As seen on pages with 0 search results, such as https://history.state.gov/search?q=%22America+of+States+United%22:
> Displaying 1–0 of 0 results.
A better message would be: No results were found. Or 0 results found. | priority | improve search summary for zero results as seen on pages with search results such as displaying – of results a better message would be no results were found or results found | 1 |
100,600 | 4,099,181,219 | IssuesEvent | 2016-06-03 11:32:40 | foundersandcoders/How-Am-I-Doing | https://api.github.com/repos/foundersandcoders/How-Am-I-Doing | opened | Buttons on dashboard could be smaller on android phone | enhancement frontend low-priority | Part of the problem of treading the line between the large iphone 6 and the smaller samsung screens | 1.0 | Buttons on dashboard could be smaller on android phone - Part of the problem of treading the line between the large iphone 6 and the smaller samsung screens | priority | buttons on dashboard could be smaller on android phone part of the problem of treading the line between the large iphone and the smaller samsung screens | 1 |
822,117 | 30,853,868,155 | IssuesEvent | 2023-08-02 18:54:35 | PrefectHQ/prefect | https://api.github.com/repos/PrefectHQ/prefect | closed | `run_shell_script` does not expand environment variables to values set in step parameter `env:` | bug status:accepted priority:low | ### First check
- [X] I added a descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the Prefect documentation for this issue.
- [X] I checked that this issue is related to Prefect and not one of its dependencies.
### Bug summary
In order for environment variables to be expanded in a subprocess, `shell` should be `True`, but at least trying this on MacOS, it seems not to be.
I think this is associated with the behavior across `prefect.utilities.processutils.open_process` and `anyio.open_process`.
From [prefect 2.10.13](https://github.com/PrefectHQ/prefect/blob/2.10.13/src/prefect/utilities/processutils.py#L189):
```
# Passing a string to open_process is equivalent to shell=True which is
# generally necessary for Unix-like commands on Windows but otherwise should
# be avoided
if not isinstance(command, list):
raise TypeError(
"The command passed to open process must be a list. You passed the command"
f"'{command}', which is type '{type(command)}'."
)
if sys.platform == "win32":
command = " ".join(command)
process = await _open_anyio_process(command, **kwargs)
else:
process = await anyio.open_process(command, **kwargs)
```
Since `prefect.utilities.processutils.open_process` requires the command to be a `list`, and that list is not rejoined into a single `str` before being passed to `anyio.open_process`, `shell` is `False`.
From [anyio 3.7.0](https://github.com/agronholm/anyio/blob/3.7.0/src/anyio/_core/_subprocesses.py#LL125C1-L135C6):
```
shell = isinstance(command, str)
return await get_asynclib().open_process(
command,
shell=shell,
stdin=stdin,
stdout=stdout,
stderr=stderr,
cwd=cwd,
env=env,
start_new_session=start_new_session,
)
```
I fixed this locally by invoking `open_process` from within `prefect.projects.steps.utility.run_shell_script` like so:
```
async with open_process(
split_command,
stdout=subprocess.PIPE,
stderr=subprocess.PIPE,
cwd=directory,
env=current_env,
shell=True,
) as process:
```
Then, in `prefect.utilities.processutils.open_process` I handled the `shell` kwarg as follows, joining the command into a single string:
```
if sys.platform == "win32":
command = " ".join(command)
process = await _open_anyio_process(command, **kwargs)
elif kwargs.pop("shell"):
command = " ".join(command)
process = await anyio.open_process(command, **kwargs)
else:
process = await anyio.open_process(command, **kwargs)
```
I'd be happy to open a PR with these changes, but I'm not sure if there'd be any side effects.
### Reproduction
```python3
build:
- prefect.projects.steps.run_shell_script:
script: echo "Hello $NAME"
env:
NAME: World
```
```
>>> prefect deploy --all
Hello $NAME
```
```
### Error
_No response_
### Versions
```Text
2.10.13
```
### Additional context
_No response_ | 1.0 | `run_shell_script` does not expand environment variables to values set in step parameter `env:` - ### First check
- [X] I added a descriptive title to this issue.
- [X] I used the GitHub search to find a similar issue and didn't find it.
- [X] I searched the Prefect documentation for this issue.
- [X] I checked that this issue is related to Prefect and not one of its dependencies.
### Bug summary
In order for environment variables to be expanded in a subprocess, `shell` should be `True`, but at least trying this on MacOS, it seems not to be.
I think this is associated with the behavior across `prefect.utilities.processutils.open_process` and `anyio.open_process`.
From [prefect 2.10.13](https://github.com/PrefectHQ/prefect/blob/2.10.13/src/prefect/utilities/processutils.py#L189):
```
# Passing a string to open_process is equivalent to shell=True which is
# generally necessary for Unix-like commands on Windows but otherwise should
# be avoided
if not isinstance(command, list):
raise TypeError(
"The command passed to open process must be a list. You passed the command"
f"'{command}', which is type '{type(command)}'."
)
if sys.platform == "win32":
command = " ".join(command)
process = await _open_anyio_process(command, **kwargs)
else:
process = await anyio.open_process(command, **kwargs)
```
Since `prefect.utilities.processutils.open_process` requires the command to be a `list`, and that list is not rejoined into a single `str` before being passed to `anyio.open_process`, `shell` is `False`.
From [anyio 3.7.0](https://github.com/agronholm/anyio/blob/3.7.0/src/anyio/_core/_subprocesses.py#LL125C1-L135C6):
```
shell = isinstance(command, str)
return await get_asynclib().open_process(
command,
shell=shell,
stdin=stdin,
stdout=stdout,
stderr=stderr,
cwd=cwd,
env=env,
start_new_session=start_new_session,
)
```
I fixed this locally by invoking `open_process` from within `prefect.projects.steps.utility.run_shell_script` like so:
```
async with open_process(
split_command,
stdout=subprocess.PIPE,
stderr=subprocess.PIPE,
cwd=directory,
env=current_env,
shell=True,
) as process:
```
Then, in `prefect.utilities.processutils.open_process` I handled the `shell` kwarg as follows, joining the command into a single string:
```
if sys.platform == "win32":
command = " ".join(command)
process = await _open_anyio_process(command, **kwargs)
elif kwargs.pop("shell"):
command = " ".join(command)
process = await anyio.open_process(command, **kwargs)
else:
process = await anyio.open_process(command, **kwargs)
```
I'd be happy to open a PR with these changes, but I'm not sure if there'd be any side effects.
### Reproduction
```python3
build:
- prefect.projects.steps.run_shell_script:
script: echo "Hello $NAME"
env:
NAME: World
```
```
>>> prefect deploy --all
Hello $NAME
```
```
### Error
_No response_
### Versions
```Text
2.10.13
```
### Additional context
_No response_ | priority | run shell script does not expand environment variables to values set in step parameter env first check i added a descriptive title to this issue i used the github search to find a similar issue and didn t find it i searched the prefect documentation for this issue i checked that this issue is related to prefect and not one of its dependencies bug summary in order for environment variables to be expanded in a subprocess shell should be true but at least trying this on macos it seems not to be i think this is associated with the behavior across prefect utilities processutils open process and anyio open process from passing a string to open process is equivalent to shell true which is generally necessary for unix like commands on windows but otherwise should be avoided if not isinstance command list raise typeerror the command passed to open process must be a list you passed the command f command which is type type command if sys platform command join command process await open anyio process command kwargs else process await anyio open process command kwargs since prefect utilities processutils open process requires the command to be a list and that list is not rejoined into a single str before being passed to anyio open process shell is false from shell isinstance command str return await get asynclib open process command shell shell stdin stdin stdout stdout stderr stderr cwd cwd env env start new session start new session i fixed this locally by invoking open process from within prefect projects steps utility run shell script like so async with open process split command stdout subprocess pipe stderr subprocess pipe cwd directory env current env shell true as process then in prefect utilities processutils open process i handled the shell kwarg as follows joining the command into a single string if sys platform command join command process await open anyio process command kwargs elif kwargs pop shell command join command process await anyio open process command kwargs else process await anyio open process command kwargs i d be happy to open a pr with these changes but i m not sure if there d be any side effects reproduction build prefect projects steps run shell script script echo hello name env name world prefect deploy all hello name error no response versions text additional context no response | 1 |
724,101 | 24,917,293,073 | IssuesEvent | 2022-10-30 14:57:35 | tachiyomiorg/tachiyomi | https://api.github.com/repos/tachiyomiorg/tachiyomi | closed | Open random manga from library | Feature request priority: very low | In #964, there was a mention of a random manga from each catalogue. I'm not requesting that, but rather one that will open a random manga that I've already added to my library.
Essentially, there will be a "Random" button at the top of the my library page that'll open a chapter from one of the manga that we have in the library. In the best case scenario, the random button would also have a set of options to choose from like:
- Selecting from downloaded
- Selecting from unread
- Selecting the first unread chapter instead of the latest | 1.0 | Open random manga from library - In #964, there was a mention of a random manga from each catalogue. I'm not requesting that, but rather one that will open a random manga that I've already added to my library.
Essentially, there will be a "Random" button at the top of the my library page that'll open a chapter from one of the manga that we have in the library. In the best case scenario, the random button would also have a set of options to choose from like:
- Selecting from downloaded
- Selecting from unread
- Selecting the first unread chapter instead of the latest | priority | open random manga from library in there was a mention of a random manga from each catalogue i m not requesting that but rather one that will open a random manga that i ve already added to my library essentially there will be a random button at the top of the my library page that ll open a chapter from one of the manga that we have in the library in the best case scenario the random button would also have a set of options to choose from like selecting from downloaded selecting from unread selecting the first unread chapter instead of the latest | 1 |
411,194 | 12,015,533,009 | IssuesEvent | 2020-04-10 14:12:00 | deora-earth/tealgarden | https://api.github.com/repos/deora-earth/tealgarden | closed | buy the domain teal.garden | 01 Low Priority 200 Deora RepPoints | <!--
# Simple Summary
This policy allows to write out rewards to complete required tasks. Completed tasks are payed by the deora council to the claiming member.
# How to create a new bounty?
1. To start you'll have to fill out the bounty form below.
- If the bounty spans across multiple repositories, consider splitting it in a smaller per-repo bounties if possible.
- If the bounty is larger than M, then the best known expert in the bounty matter should be consulted and included in an
"Expert" field in the bounty description.
2. Communicate the bounty to the organisation by submitting the following form:
https://forms.gle/STSNjTBGygNtTUwLA
- The bounty will get published on the deora communication channel.
# Bounty sizes
XS / 50 to 200 / DAI
S / 200 to 350 / DAI
M / 350 to 550 / DAI
L / 550 to 900 / DAI
XL / 900 to 1400 / DAI
You can specify the range individually under #Roles
# Pair programming
If 2 people claim the bounty together, the payout increases by 1.5x.
# Bounty Challenge
Once a bounty is assigned, the worker is asked to start working immediately on the issue.
If the worker feels blocked in execution, he/she has to communicate the tensions to the gardener.
Only if tensions are not reported and the bounty get's no further attention, anyone can challenge the bounty or takeover.
Bounties should be delivered within time, even if work is left to be performed. Leftover work can be tackled by submitting a new bounty with support by the organisation.
Bounty forking: complexity of bounties that has been undersized can be forked out by a new bounty submission.
**START DESCRIBING YOUR BOUNTY HERE:**
-->
# Bounty
We discussed in the daily standup and in the deora tactical to focus on the main branding deora and communicate everything as deora. The Main page should be hosted on teal.deora.earth but it would be grate to also have the site teal.garden with a redirect. Therfore someone has to buy the domain and request a reimbursement by the deora multisig
## Scope
- buy the domain
## Deliverables
- the domain teal.garden
## Gain for the project
nice user experiance and good for SEO
## Roles
bounty gardener: @cyan-one / 10%
bounty worker: name / share
bounty reviewer: name / share
| 1.0 | buy the domain teal.garden - <!--
# Simple Summary
This policy allows to write out rewards to complete required tasks. Completed tasks are payed by the deora council to the claiming member.
# How to create a new bounty?
1. To start you'll have to fill out the bounty form below.
- If the bounty spans across multiple repositories, consider splitting it in a smaller per-repo bounties if possible.
- If the bounty is larger than M, then the best known expert in the bounty matter should be consulted and included in an
"Expert" field in the bounty description.
2. Communicate the bounty to the organisation by submitting the following form:
https://forms.gle/STSNjTBGygNtTUwLA
- The bounty will get published on the deora communication channel.
# Bounty sizes
XS / 50 to 200 / DAI
S / 200 to 350 / DAI
M / 350 to 550 / DAI
L / 550 to 900 / DAI
XL / 900 to 1400 / DAI
You can specify the range individually under #Roles
# Pair programming
If 2 people claim the bounty together, the payout increases by 1.5x.
# Bounty Challenge
Once a bounty is assigned, the worker is asked to start working immediately on the issue.
If the worker feels blocked in execution, he/she has to communicate the tensions to the gardener.
Only if tensions are not reported and the bounty get's no further attention, anyone can challenge the bounty or takeover.
Bounties should be delivered within time, even if work is left to be performed. Leftover work can be tackled by submitting a new bounty with support by the organisation.
Bounty forking: complexity of bounties that has been undersized can be forked out by a new bounty submission.
**START DESCRIBING YOUR BOUNTY HERE:**
-->
# Bounty
We discussed in the daily standup and in the deora tactical to focus on the main branding deora and communicate everything as deora. The Main page should be hosted on teal.deora.earth but it would be grate to also have the site teal.garden with a redirect. Therfore someone has to buy the domain and request a reimbursement by the deora multisig
## Scope
- buy the domain
## Deliverables
- the domain teal.garden
## Gain for the project
nice user experiance and good for SEO
## Roles
bounty gardener: @cyan-one / 10%
bounty worker: name / share
bounty reviewer: name / share
| priority | buy the domain teal garden simple summary this policy allows to write out rewards to complete required tasks completed tasks are payed by the deora council to the claiming member how to create a new bounty to start you ll have to fill out the bounty form below if the bounty spans across multiple repositories consider splitting it in a smaller per repo bounties if possible if the bounty is larger than m then the best known expert in the bounty matter should be consulted and included in an expert field in the bounty description communicate the bounty to the organisation by submitting the following form the bounty will get published on the deora communication channel bounty sizes xs to dai s to dai m to dai l to dai xl to dai you can specify the range individually under roles pair programming if people claim the bounty together the payout increases by bounty challenge once a bounty is assigned the worker is asked to start working immediately on the issue if the worker feels blocked in execution he she has to communicate the tensions to the gardener only if tensions are not reported and the bounty get s no further attention anyone can challenge the bounty or takeover bounties should be delivered within time even if work is left to be performed leftover work can be tackled by submitting a new bounty with support by the organisation bounty forking complexity of bounties that has been undersized can be forked out by a new bounty submission start describing your bounty here bounty we discussed in the daily standup and in the deora tactical to focus on the main branding deora and communicate everything as deora the main page should be hosted on teal deora earth but it would be grate to also have the site teal garden with a redirect therfore someone has to buy the domain and request a reimbursement by the deora multisig scope buy the domain deliverables the domain teal garden gain for the project nice user experiance and good for seo roles bounty gardener cyan one bounty worker name share bounty reviewer name share | 1 |
785,717 | 27,623,556,431 | IssuesEvent | 2023-03-10 03:36:56 | darwinia-network/apps | https://api.github.com/repos/darwinia-network/apps | closed | Show balance details on account section | low-priority | - Total
- Transferrable
Show corresponding entry when value is not 0
- Locked
- Bonded
- Unbonding
- Democracy
- Election
- Vesting | 1.0 | Show balance details on account section - - Total
- Transferrable
Show corresponding entry when value is not 0
- Locked
- Bonded
- Unbonding
- Democracy
- Election
- Vesting | priority | show balance details on account section total transferrable show corresponding entry when value is not locked bonded unbonding democracy election vesting | 1 |
452,450 | 13,050,699,263 | IssuesEvent | 2020-07-29 15:53:20 | StatCan/daaas | https://api.github.com/repos/StatCan/daaas | closed | Enable Kubeflow artifacts/data lineage | component/kubeflow current-sprint kind/experiment priority/important-soon size/L | Kubeflow portal has support to view persisted artifacts, data lineage, etc., but it is not connected. This could be used to browse products of pipelines without having to open minio.
Appears to work (shown in IBM presentations and others) but not yet set up on our side. | 1.0 | Enable Kubeflow artifacts/data lineage - Kubeflow portal has support to view persisted artifacts, data lineage, etc., but it is not connected. This could be used to browse products of pipelines without having to open minio.
Appears to work (shown in IBM presentations and others) but not yet set up on our side. | priority | enable kubeflow artifacts data lineage kubeflow portal has support to view persisted artifacts data lineage etc but it is not connected this could be used to browse products of pipelines without having to open minio appears to work shown in ibm presentations and others but not yet set up on our side | 1 |
452,879 | 13,060,639,464 | IssuesEvent | 2020-07-30 12:45:39 | geosolutions-it/MapStore2 | https://api.github.com/repos/geosolutions-it/MapStore2 | closed | Collapsed icons of widgets change order in Widgets Bar | Priority: Low bug | ### Description
depends on geosolutions-it/MapStore2#3531
### In case of Bug (otherwise remove this paragraph)
*Browser Affected*
(use this site: https://www.whatsmybrowser.org/ for non expert users)
- [ ] Internet Explorer
- [ ] Chrome
- [ ] Firefox
- [ ] Safari
*Browser Version Affected*
- all
*Steps to reproduce*
- use following [map configuration](https://github.com/geosolutions-it/MapStore2/files/2880065/collapsed_widgets.txt) as new.json
- open the map #/viewer/openlayers/new
- save the map to geostore and refresh the page
- click on expand all widgets button (see GIF in the description)
- select the first icon on the right (sheet icon)
*Expected Result*
- sheet icon is still in its position
*Current Result*
- sheet icon shifts on the right
### Other useful information (optional):
| 1.0 | Collapsed icons of widgets change order in Widgets Bar - ### Description
depends on geosolutions-it/MapStore2#3531
### In case of Bug (otherwise remove this paragraph)
*Browser Affected*
(use this site: https://www.whatsmybrowser.org/ for non expert users)
- [ ] Internet Explorer
- [ ] Chrome
- [ ] Firefox
- [ ] Safari
*Browser Version Affected*
- all
*Steps to reproduce*
- use following [map configuration](https://github.com/geosolutions-it/MapStore2/files/2880065/collapsed_widgets.txt) as new.json
- open the map #/viewer/openlayers/new
- save the map to geostore and refresh the page
- click on expand all widgets button (see GIF in the description)
- select the first icon on the right (sheet icon)
*Expected Result*
- sheet icon is still in its position
*Current Result*
- sheet icon shifts on the right
### Other useful information (optional):
| priority | collapsed icons of widgets change order in widgets bar description depends on geosolutions it in case of bug otherwise remove this paragraph browser affected use this site for non expert users internet explorer chrome firefox safari browser version affected all steps to reproduce use following as new json open the map viewer openlayers new save the map to geostore and refresh the page click on expand all widgets button see gif in the description select the first icon on the right sheet icon expected result sheet icon is still in its position current result sheet icon shifts on the right other useful information optional | 1 |
308,072 | 9,429,836,074 | IssuesEvent | 2019-04-12 07:26:04 | CS2103-AY1819S2-W15-2/main | https://api.github.com/repos/CS2103-AY1819S2-W15-2/main | closed | As a user I want to be able to track my investments | priority.Low type.Story | so that I can see how much money I have in assets and also to possibly see my positive cashflow from these investments | 1.0 | As a user I want to be able to track my investments - so that I can see how much money I have in assets and also to possibly see my positive cashflow from these investments | priority | as a user i want to be able to track my investments so that i can see how much money i have in assets and also to possibly see my positive cashflow from these investments | 1 |
242,039 | 7,836,929,057 | IssuesEvent | 2018-06-18 01:48:19 | tlienart/JuDoc.jl | https://api.github.com/repos/tlienart/JuDoc.jl | opened | Minify output | engine low-priority | Can use something like a [generic minifyer](https://github.com/juancarlospaco/css-html-js-minify) to do the trick *at the end*.
Potential problem: the files should be replaced so that in the `git-push` to (for example) git pages, it's the minified version that is served.
Could also maybe directly apply it on every file that is compiled but that would make things slower. Could also minify stuff yourself removing whitespaces or whatever. | 1.0 | Minify output - Can use something like a [generic minifyer](https://github.com/juancarlospaco/css-html-js-minify) to do the trick *at the end*.
Potential problem: the files should be replaced so that in the `git-push` to (for example) git pages, it's the minified version that is served.
Could also maybe directly apply it on every file that is compiled but that would make things slower. Could also minify stuff yourself removing whitespaces or whatever. | priority | minify output can use something like a to do the trick at the end potential problem the files should be replaced so that in the git push to for example git pages it s the minified version that is served could also maybe directly apply it on every file that is compiled but that would make things slower could also minify stuff yourself removing whitespaces or whatever | 1 |
61,541 | 3,146,981,852 | IssuesEvent | 2015-09-15 04:02:37 | wwivbbs/wwiv | https://api.github.com/repos/wwivbbs/wwiv | closed | Telnet server position | 5.0 auto-migrated low priority sourceforge | A option into the telnet server that you can set the screen position for showing on your windows desktop.
So the place where it will set the telnet screen.
Original comment by: xray1870 | 1.0 | Telnet server position - A option into the telnet server that you can set the screen position for showing on your windows desktop.
So the place where it will set the telnet screen.
Original comment by: xray1870 | priority | telnet server position a option into the telnet server that you can set the screen position for showing on your windows desktop so the place where it will set the telnet screen original comment by | 1 |
357,698 | 10,616,948,544 | IssuesEvent | 2019-10-12 15:33:08 | bounswe/bounswe2019group8 | https://api.github.com/repos/bounswe/bounswe2019group8 | opened | Auto-deploy backend app using Jenkins in a Docker container | Backend Effort: High Priority: Low Type: Enhancement | **Actions:**
1. When a push is made to a specific branch, GitHub webhook will trigger the Jenkins pipeline.
1. Jenkins will clone the repo, build image from Dockerfile, push the image to the Docker Hub and run the the app in a container from the pushed image.
**Deadline:** 19.10.2019 - 23.59
| 1.0 | Auto-deploy backend app using Jenkins in a Docker container - **Actions:**
1. When a push is made to a specific branch, GitHub webhook will trigger the Jenkins pipeline.
1. Jenkins will clone the repo, build image from Dockerfile, push the image to the Docker Hub and run the the app in a container from the pushed image.
**Deadline:** 19.10.2019 - 23.59
| priority | auto deploy backend app using jenkins in a docker container actions when a push is made to a specific branch github webhook will trigger the jenkins pipeline jenkins will clone the repo build image from dockerfile push the image to the docker hub and run the the app in a container from the pushed image deadline | 1 |
756,049 | 26,454,199,750 | IssuesEvent | 2023-01-16 13:24:22 | ncssar/radiolog | https://api.github.com/repos/ncssar/radiolog | opened | undecodable fleetsync data | enhancement Priority:Low | Noticed by @RadiosPRN:
------------------
Every once in a while when I start RadioLog fleetsync will not work. Keying up a radio does nothing as far as firing a NED. The only thing in the log is this entry after the first key up:
```
144529: DATA IS WAITING!!!
Uncaught exception
Traceback (most recent call last):
File "radiolog.py", line 1732, in fsCheck
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe1 in position 6: invalid continuation byte
```
After this entry there will be no further entries of fleetsync data and it acts like the data is not making it to RadioLog. Restarting it will again log this entry after the first key up and then nothing after that. RadioLog can be used as normal with no fleetsync. The pattern I have noticed is that this always seems to happen when there are software updates and the computer needs to be restarted. After updating and restarting everything works great.
----------------------
Guessing this is an OS-related thing, internal to the COM port guts. But, if it's possible to handle this exception, in order to allow any future valid FS data to be handled correctly, that would win. Also, if it's possible to show the FS data before the exception happens, that would also win, though if it can't be decoded and the actual data is not known, then this might not be feasible. Step 1: Try to reproduce the exception by sending some garbled goop from a terminal emulator.
Labeling this a s low priority enhancement until the testing can be done | 1.0 | undecodable fleetsync data - Noticed by @RadiosPRN:
------------------
Every once in a while when I start RadioLog fleetsync will not work. Keying up a radio does nothing as far as firing a NED. The only thing in the log is this entry after the first key up:
```
144529: DATA IS WAITING!!!
Uncaught exception
Traceback (most recent call last):
File "radiolog.py", line 1732, in fsCheck
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe1 in position 6: invalid continuation byte
```
After this entry there will be no further entries of fleetsync data and it acts like the data is not making it to RadioLog. Restarting it will again log this entry after the first key up and then nothing after that. RadioLog can be used as normal with no fleetsync. The pattern I have noticed is that this always seems to happen when there are software updates and the computer needs to be restarted. After updating and restarting everything works great.
----------------------
Guessing this is an OS-related thing, internal to the COM port guts. But, if it's possible to handle this exception, in order to allow any future valid FS data to be handled correctly, that would win. Also, if it's possible to show the FS data before the exception happens, that would also win, though if it can't be decoded and the actual data is not known, then this might not be feasible. Step 1: Try to reproduce the exception by sending some garbled goop from a terminal emulator.
Labeling this a s low priority enhancement until the testing can be done | priority | undecodable fleetsync data noticed by radiosprn every once in a while when i start radiolog fleetsync will not work keying up a radio does nothing as far as firing a ned the only thing in the log is this entry after the first key up data is waiting uncaught exception traceback most recent call last file radiolog py line in fscheck unicodedecodeerror utf codec can t decode byte in position invalid continuation byte after this entry there will be no further entries of fleetsync data and it acts like the data is not making it to radiolog restarting it will again log this entry after the first key up and then nothing after that radiolog can be used as normal with no fleetsync the pattern i have noticed is that this always seems to happen when there are software updates and the computer needs to be restarted after updating and restarting everything works great guessing this is an os related thing internal to the com port guts but if it s possible to handle this exception in order to allow any future valid fs data to be handled correctly that would win also if it s possible to show the fs data before the exception happens that would also win though if it can t be decoded and the actual data is not known then this might not be feasible step try to reproduce the exception by sending some garbled goop from a terminal emulator labeling this a s low priority enhancement until the testing can be done | 1 |
504,896 | 14,623,295,364 | IssuesEvent | 2020-12-23 02:56:00 | EUCweb/BIS-F | https://api.github.com/repos/EUCweb/BIS-F | reopened | EventLog is moved, but Path is never changed | Priority: Low Status: Completed Type: Bug | issues with Event log redirections on some Projects, i beleive the commonality is IF BIS-F is run to move the event logs to say "D: but then that needs to be changed to "E" - I am not sure why, but it only changes some event logs and leaves the rest broken
Fix it with the following script
https://gallery.technet.microsoft.com/scriptcenter/Change-the-path-of-the-f86d2427 | 1.0 | EventLog is moved, but Path is never changed - issues with Event log redirections on some Projects, i beleive the commonality is IF BIS-F is run to move the event logs to say "D: but then that needs to be changed to "E" - I am not sure why, but it only changes some event logs and leaves the rest broken
Fix it with the following script
https://gallery.technet.microsoft.com/scriptcenter/Change-the-path-of-the-f86d2427 | priority | eventlog is moved but path is never changed issues with event log redirections on some projects i beleive the commonality is if bis f is run to move the event logs to say d but then that needs to be changed to e i am not sure why but it only changes some event logs and leaves the rest broken fix it with the following script | 1 |
96,925 | 3,975,522,735 | IssuesEvent | 2016-05-05 06:03:28 | dhowe/RiTa | https://api.github.com/repos/dhowe/RiTa | closed | Convert gallery examples to p5js | enhancement ongoing PRIORITY: Low | (any that are still using processing.js)
also check that the link on the HTML page goes to p5js and not processing.js
only work on this when other tasks are finished or on-hold... | 1.0 | Convert gallery examples to p5js - (any that are still using processing.js)
also check that the link on the HTML page goes to p5js and not processing.js
only work on this when other tasks are finished or on-hold... | priority | convert gallery examples to any that are still using processing js also check that the link on the html page goes to and not processing js only work on this when other tasks are finished or on hold | 1 |
320,037 | 9,763,956,167 | IssuesEvent | 2019-06-05 14:49:57 | wherebyus/general-tasks | https://api.github.com/repos/wherebyus/general-tasks | closed | My Account: "Subscriptions" should be called "My Membership" | Feasibility: High Priority: Low Product: Membership Product: Site checked | 
## DOD
- [x] "Subscriptions" in the My Account left navigation is now called "My Membership"
- [ ] The URL endpoint is now called `my-membership` (Note this may be dependent on #486)
- [ ] The "Subscription" table column header is now called "ID"
- [ ] Any "Subscription" references in the order receipts are references to Memberships instead | 1.0 | My Account: "Subscriptions" should be called "My Membership" - 
## DOD
- [x] "Subscriptions" in the My Account left navigation is now called "My Membership"
- [ ] The URL endpoint is now called `my-membership` (Note this may be dependent on #486)
- [ ] The "Subscription" table column header is now called "ID"
- [ ] Any "Subscription" references in the order receipts are references to Memberships instead | priority | my account subscriptions should be called my membership dod subscriptions in the my account left navigation is now called my membership the url endpoint is now called my membership note this may be dependent on the subscription table column header is now called id any subscription references in the order receipts are references to memberships instead | 1 |
180,783 | 6,653,484,533 | IssuesEvent | 2017-09-29 08:36:19 | telerik/kendo-ui-core | https://api.github.com/repos/telerik/kendo-ui-core | closed | When selecting some of the bottom items in a scrollable ListBox the focus is automatically push to the top(Only in Internet Explorer and Edge) | Bug C: ListBox Kendo1 Priority 2 SEV: Low | ### Bug report
When selecting some of the bottom items in a scrollable ListBoxt the focus is automatically pushed to the top(Only in Internet Explorer and Edge).
### Reproduction of the problem
The issue can be observed in our demo: http://demos.telerik.com/kendo-ui/listbox/events
### Environment
* **Kendo UI version:** 201x.r.ddd
* **jQuery version:** x.y
* **Browser:** [ IE 11, Edge |]
| 1.0 | When selecting some of the bottom items in a scrollable ListBox the focus is automatically push to the top(Only in Internet Explorer and Edge) - ### Bug report
When selecting some of the bottom items in a scrollable ListBoxt the focus is automatically pushed to the top(Only in Internet Explorer and Edge).
### Reproduction of the problem
The issue can be observed in our demo: http://demos.telerik.com/kendo-ui/listbox/events
### Environment
* **Kendo UI version:** 201x.r.ddd
* **jQuery version:** x.y
* **Browser:** [ IE 11, Edge |]
| priority | when selecting some of the bottom items in a scrollable listbox the focus is automatically push to the top only in internet explorer and edge bug report when selecting some of the bottom items in a scrollable listboxt the focus is automatically pushed to the top only in internet explorer and edge reproduction of the problem the issue can be observed in our demo environment kendo ui version r ddd jquery version x y browser | 1 |
627,841 | 19,915,407,808 | IssuesEvent | 2022-01-25 21:58:14 | medic-code/IOL-Assist | https://api.github.com/repos/medic-code/IOL-Assist | closed | Description of use case for IOL Assist | Clinical Low priority | In order to have the IOL Assist on the App store we will need to outline a use case description for the users, to entice and to inform them about the product. Would also be useful for the Github Repo! | 1.0 | Description of use case for IOL Assist - In order to have the IOL Assist on the App store we will need to outline a use case description for the users, to entice and to inform them about the product. Would also be useful for the Github Repo! | priority | description of use case for iol assist in order to have the iol assist on the app store we will need to outline a use case description for the users to entice and to inform them about the product would also be useful for the github repo | 1 |
46,210 | 2,948,387,948 | IssuesEvent | 2015-07-06 02:32:31 | CrimsonGlory/posaderos | https://api.github.com/repos/CrimsonGlory/posaderos | opened | nombre al bajar un archivo. | enhancement low-priority | SI subo algo.zip, a la hora de bajarlo el nombre que me da para elegir es el id del fileentry. sin extensión ni nada.
Cuando debería ser algo.zip
Hay dos formas de solucionar esto. una es con el content-disposition
y otra haciendo un redirect justo antes de bajarlo.
https://stackoverflow.com/questions/1741353/how-to-set-response-filename-without-forcing-saveas-dialog | 1.0 | nombre al bajar un archivo. - SI subo algo.zip, a la hora de bajarlo el nombre que me da para elegir es el id del fileentry. sin extensión ni nada.
Cuando debería ser algo.zip
Hay dos formas de solucionar esto. una es con el content-disposition
y otra haciendo un redirect justo antes de bajarlo.
https://stackoverflow.com/questions/1741353/how-to-set-response-filename-without-forcing-saveas-dialog | priority | nombre al bajar un archivo si subo algo zip a la hora de bajarlo el nombre que me da para elegir es el id del fileentry sin extensión ni nada cuando debería ser algo zip hay dos formas de solucionar esto una es con el content disposition y otra haciendo un redirect justo antes de bajarlo | 1 |
260,373 | 8,209,412,504 | IssuesEvent | 2018-09-04 07:30:11 | easybuilders/easybuild-framework | https://api.github.com/repos/easybuilders/easybuild-framework | closed | make EasyBuild check easyconfig repository | enhancement priority:low | EasyBuild should check the easyconfig repository it dumps easyconfig file to after building, when resolving dependencies for a build or when being run without a supplied easyconfig file.
| 1.0 | make EasyBuild check easyconfig repository - EasyBuild should check the easyconfig repository it dumps easyconfig file to after building, when resolving dependencies for a build or when being run without a supplied easyconfig file.
| priority | make easybuild check easyconfig repository easybuild should check the easyconfig repository it dumps easyconfig file to after building when resolving dependencies for a build or when being run without a supplied easyconfig file | 1 |
354,962 | 10,575,088,125 | IssuesEvent | 2019-10-07 15:07:24 | Kurt-Hetrick/CIDR_WES | https://api.github.com/repos/Kurt-Hetrick/CIDR_WES | closed | per chromosome verifybamid in one job instead of 1 job per chromosome | low priority | this is fast anyways and there is no good reason why it couldn't be in one job | 1.0 | per chromosome verifybamid in one job instead of 1 job per chromosome - this is fast anyways and there is no good reason why it couldn't be in one job | priority | per chromosome verifybamid in one job instead of job per chromosome this is fast anyways and there is no good reason why it couldn t be in one job | 1 |
811,459 | 30,288,696,226 | IssuesEvent | 2023-07-09 02:02:36 | UBC-DSCI/introduction-to-datascience | https://api.github.com/repos/UBC-DSCI/introduction-to-datascience | closed | Clean up datasets and images | enhancement low priority | Worth going through and removing old / unused images and datasets. I'll likely do this as part of the summer 2023 update | 1.0 | Clean up datasets and images - Worth going through and removing old / unused images and datasets. I'll likely do this as part of the summer 2023 update | priority | clean up datasets and images worth going through and removing old unused images and datasets i ll likely do this as part of the summer update | 1 |
817,481 | 30,641,448,004 | IssuesEvent | 2023-07-24 22:27:53 | TownyAdvanced/Towny | https://api.github.com/repos/TownyAdvanced/Towny | closed | Suggestion: force integer monetary values | enhancement Priority-Low Label-Money | **Please explain your feature request to the best of your abilities:**
Add the option to force monetary costs to be integer numbers.
Exemple: if the mayor tries to set any taxes 3.1 he'll get an error. If he tries to set to 3 or 3.0 it'll work fine.
Why? I am using Gringotts, an item based economy plugin, so there is no decimal values. Setting a non-integer value in an integer only economy can lead to problems. I tried to break Towny setting decimal tax values, but it seems Towny just ignores then? Anyway, that simple option would be great to avoid any problems. | 1.0 | Suggestion: force integer monetary values - **Please explain your feature request to the best of your abilities:**
Add the option to force monetary costs to be integer numbers.
Exemple: if the mayor tries to set any taxes 3.1 he'll get an error. If he tries to set to 3 or 3.0 it'll work fine.
Why? I am using Gringotts, an item based economy plugin, so there is no decimal values. Setting a non-integer value in an integer only economy can lead to problems. I tried to break Towny setting decimal tax values, but it seems Towny just ignores then? Anyway, that simple option would be great to avoid any problems. | priority | suggestion force integer monetary values please explain your feature request to the best of your abilities add the option to force monetary costs to be integer numbers exemple if the mayor tries to set any taxes he ll get an error if he tries to set to or it ll work fine why i am using gringotts an item based economy plugin so there is no decimal values setting a non integer value in an integer only economy can lead to problems i tried to break towny setting decimal tax values but it seems towny just ignores then anyway that simple option would be great to avoid any problems | 1 |
399,553 | 11,756,881,847 | IssuesEvent | 2020-03-13 12:34:33 | Broken-Gem-Studio/Broken-Engine | https://api.github.com/repos/Broken-Gem-Studio/Broken-Engine | opened | Cannot see framerate/ms in PanelSettings/Application (Editor) | Bug Low Priority | ## Bug Description
Should be able to see the historiograms there, they are blank now
## Type of Bug
Select the type of bug with and "x" ([x])
* [ ] Visual
* [ ] Physics
* [ ] Audio
* [ ] Particles
* [ ] Resource Management & Save/Load
* [ ] Materials
* [ ] Components
* [ ] Game Objects
* [ ] UI/UX
* [X] Other
## Severity
Select the severity of bug affection and mark with "x" ([x])
- [ ] Crash
- [ ] Game stopper/slower
- [X] Cosmetic
## Reproduction
Steps to reproduce the behavior:
1. Just open panelSettings, Application tab
2.
3.
4.
## Frequency
Select the frequency with which the bug appears and mark it "x" ([x])
* [X] Always
* [ ] Very Often
* [ ] Usually
* [ ] Few Times
* [ ] Few Times under specific conditions
## Conduct
### Expected result:
We can see the logs there
### Actual result:
Historiogram is blank
## Screenshots and Illustrations:
## Build
- **Please specify the build:** ``Insert the build here``
Development branch commit 1067
## Observations and Additional Information
Might have to do with the dll, exe communication, thus I assign sergi to the issue | 1.0 | Cannot see framerate/ms in PanelSettings/Application (Editor) - ## Bug Description
Should be able to see the historiograms there, they are blank now
## Type of Bug
Select the type of bug with and "x" ([x])
* [ ] Visual
* [ ] Physics
* [ ] Audio
* [ ] Particles
* [ ] Resource Management & Save/Load
* [ ] Materials
* [ ] Components
* [ ] Game Objects
* [ ] UI/UX
* [X] Other
## Severity
Select the severity of bug affection and mark with "x" ([x])
- [ ] Crash
- [ ] Game stopper/slower
- [X] Cosmetic
## Reproduction
Steps to reproduce the behavior:
1. Just open panelSettings, Application tab
2.
3.
4.
## Frequency
Select the frequency with which the bug appears and mark it "x" ([x])
* [X] Always
* [ ] Very Often
* [ ] Usually
* [ ] Few Times
* [ ] Few Times under specific conditions
## Conduct
### Expected result:
We can see the logs there
### Actual result:
Historiogram is blank
## Screenshots and Illustrations:
## Build
- **Please specify the build:** ``Insert the build here``
Development branch commit 1067
## Observations and Additional Information
Might have to do with the dll, exe communication, thus I assign sergi to the issue | priority | cannot see framerate ms in panelsettings application editor bug description should be able to see the historiograms there they are blank now type of bug select the type of bug with and x visual physics audio particles resource management save load materials components game objects ui ux other severity select the severity of bug affection and mark with x crash game stopper slower cosmetic reproduction steps to reproduce the behavior just open panelsettings application tab frequency select the frequency with which the bug appears and mark it x always very often usually few times few times under specific conditions conduct expected result we can see the logs there actual result historiogram is blank screenshots and illustrations build please specify the build insert the build here development branch commit observations and additional information might have to do with the dll exe communication thus i assign sergi to the issue | 1 |
515,398 | 14,961,911,368 | IssuesEvent | 2021-01-27 08:31:22 | projectdiscovery/nuclei | https://api.github.com/repos/projectdiscovery/nuclei | closed | [feature] Default Parameters / Headers | Priority: Low Status: Completed Status: In Progress Type: Enhancement | **Is your feature request related to a problem? Please describe.**
It's not really a problem it's just related to stream-lining my work
**Describe the solution you'd like**
I sometimes find myself repeating headers (such as User-Agent) using -H over and over again. It would be great if I would save them once in a default config file and they would be used without me having to repeat it | 1.0 | [feature] Default Parameters / Headers - **Is your feature request related to a problem? Please describe.**
It's not really a problem it's just related to stream-lining my work
**Describe the solution you'd like**
I sometimes find myself repeating headers (such as User-Agent) using -H over and over again. It would be great if I would save them once in a default config file and they would be used without me having to repeat it | priority | default parameters headers is your feature request related to a problem please describe it s not really a problem it s just related to stream lining my work describe the solution you d like i sometimes find myself repeating headers such as user agent using h over and over again it would be great if i would save them once in a default config file and they would be used without me having to repeat it | 1 |
312,194 | 9,544,640,918 | IssuesEvent | 2019-05-01 14:48:06 | typicalbot/typicalbot | https://api.github.com/repos/typicalbot/typicalbot | closed | Command similarity | level: experienced priority: low status: completed type: enhancement type: feature | ## Issue
- [X] I have checked for related issues.
- [ ] I have updated to the latest [TypicalBot version](https://github.com/typicalbot/typicalbot).
- [ ] I am using an official bot operated by TypicalBot.
### Issue Type
- [ ] Bug Report
- [X] Feature Request
### Description
When making a mistake in command, check for similarity and prompt the user if they meant X instead Y. Maybe make it so it'll auto run the correct command? | 1.0 | Command similarity - ## Issue
- [X] I have checked for related issues.
- [ ] I have updated to the latest [TypicalBot version](https://github.com/typicalbot/typicalbot).
- [ ] I am using an official bot operated by TypicalBot.
### Issue Type
- [ ] Bug Report
- [X] Feature Request
### Description
When making a mistake in command, check for similarity and prompt the user if they meant X instead Y. Maybe make it so it'll auto run the correct command? | priority | command similarity issue i have checked for related issues i have updated to the latest i am using an official bot operated by typicalbot issue type bug report feature request description when making a mistake in command check for similarity and prompt the user if they meant x instead y maybe make it so it ll auto run the correct command | 1 |
520,347 | 15,084,857,085 | IssuesEvent | 2021-02-05 17:46:28 | zeebe-io/zeebe | https://api.github.com/repos/zeebe-io/zeebe | closed | Document Grafana dashboard panels | Priority: Low Status: Backlog Type: Docs good first issue | **Description**
The current Grafana dashboard works well, but it is not obvious how to interpret each panel. While it's meant to serve a springboard for users to build their own dashboards, it's also used internally by the Zeebe team, and having non-documented panels leads to:
1. Steeper learning curve to onboard new developers
1. Older members have to still edit the panel to figure out what is the data if they were not involved in the addition of the panel/metric
It's possible in Grafana to add help information to the dashboards, so the first step should be to do this for all panels. If we need more complete documentation, the next step would be to add it as part of the monitor `README.md` file.
| 1.0 | Document Grafana dashboard panels - **Description**
The current Grafana dashboard works well, but it is not obvious how to interpret each panel. While it's meant to serve a springboard for users to build their own dashboards, it's also used internally by the Zeebe team, and having non-documented panels leads to:
1. Steeper learning curve to onboard new developers
1. Older members have to still edit the panel to figure out what is the data if they were not involved in the addition of the panel/metric
It's possible in Grafana to add help information to the dashboards, so the first step should be to do this for all panels. If we need more complete documentation, the next step would be to add it as part of the monitor `README.md` file.
| priority | document grafana dashboard panels description the current grafana dashboard works well but it is not obvious how to interpret each panel while it s meant to serve a springboard for users to build their own dashboards it s also used internally by the zeebe team and having non documented panels leads to steeper learning curve to onboard new developers older members have to still edit the panel to figure out what is the data if they were not involved in the addition of the panel metric it s possible in grafana to add help information to the dashboards so the first step should be to do this for all panels if we need more complete documentation the next step would be to add it as part of the monitor readme md file | 1 |
371,821 | 10,981,712,939 | IssuesEvent | 2019-12-01 00:21:37 | vizstack/vizstack | https://api.github.com/repos/vizstack/vizstack | closed | Only fetch symbols if needed | priority: low type: improvement | Currently, whenever a new viewer is open, we fetch the symbol information, even if it has already been fetched. This can be expensive for tensors or other data-heavy symbols; we should only fetch a symbol if it's not already in the symbol table. | 1.0 | Only fetch symbols if needed - Currently, whenever a new viewer is open, we fetch the symbol information, even if it has already been fetched. This can be expensive for tensors or other data-heavy symbols; we should only fetch a symbol if it's not already in the symbol table. | priority | only fetch symbols if needed currently whenever a new viewer is open we fetch the symbol information even if it has already been fetched this can be expensive for tensors or other data heavy symbols we should only fetch a symbol if it s not already in the symbol table | 1 |
539,045 | 15,782,621,245 | IssuesEvent | 2021-04-01 13:01:43 | practice-enterprise/canvas-discord-bot | https://api.github.com/repos/practice-enterprise/canvas-discord-bot | opened | [Teachers request] Post changes in announcements as well | Priority: Low Type: School | This could be done by keeping a hash of an announcement and checking for changes. | 1.0 | [Teachers request] Post changes in announcements as well - This could be done by keeping a hash of an announcement and checking for changes. | priority | post changes in announcements as well this could be done by keeping a hash of an announcement and checking for changes | 1 |
376,014 | 11,137,113,988 | IssuesEvent | 2019-12-20 18:25:12 | open-learning-exchange/myplanet | https://api.github.com/repos/open-learning-exchange/myplanet | closed | clean detail if no record | low priority newbie friendly | If there are no records for any specific details of resources or courses. We should not show those tables. | 1.0 | clean detail if no record - If there are no records for any specific details of resources or courses. We should not show those tables. | priority | clean detail if no record if there are no records for any specific details of resources or courses we should not show those tables | 1 |
553,859 | 16,384,024,872 | IssuesEvent | 2021-05-17 08:09:32 | kf5i/k3ai-core | https://api.github.com/repos/kf5i/k3ai-core | closed | Delete name space when delete a plugin | area/core ena low priority work-in-progress/do-not-merge | When we delete a plugin, we don't remove the namespace.
We could check if there are resources under the namespace and decide to remove it.
See https://github.com/kf5i/k3ai-core/pull/37/files#r512158973
| 1.0 | Delete name space when delete a plugin - When we delete a plugin, we don't remove the namespace.
We could check if there are resources under the namespace and decide to remove it.
See https://github.com/kf5i/k3ai-core/pull/37/files#r512158973
| priority | delete name space when delete a plugin when we delete a plugin we don t remove the namespace we could check if there are resources under the namespace and decide to remove it see | 1 |
492,467 | 14,213,786,794 | IssuesEvent | 2020-11-17 03:26:19 | amnh/PCG | https://api.github.com/repos/amnh/PCG | closed | Find space leaks in code | low priority performance/optimization | We should use the method described [here](https://github.com/ndmitchell/spaceleak) to try to find any space leaks in our code.
| 1.0 | Find space leaks in code - We should use the method described [here](https://github.com/ndmitchell/spaceleak) to try to find any space leaks in our code.
| priority | find space leaks in code we should use the method described to try to find any space leaks in our code | 1 |
685,611 | 23,462,733,323 | IssuesEvent | 2022-08-16 14:19:57 | DSD-DBS/capella-collab-manager | https://api.github.com/repos/DSD-DBS/capella-collab-manager | closed | Readonly containers: Allow selection of branches and tags | enhancement priority:low effort:medium | Allow the selection of branches and tags of the linked Git repository. | 1.0 | Readonly containers: Allow selection of branches and tags - Allow the selection of branches and tags of the linked Git repository. | priority | readonly containers allow selection of branches and tags allow the selection of branches and tags of the linked git repository | 1 |
600,482 | 18,297,555,427 | IssuesEvent | 2021-10-05 22:05:52 | azerothcore/azerothcore-wotlk | https://api.github.com/repos/azerothcore/azerothcore-wotlk | reopened | Plans: Lionheart Helm, Drop Chance and droppable mobs appear incorrect on Azeroth Core | 50-59 Priority-Low | ### What client do you play on?
enUS
### Faction
- [ ] Alliance
- [X] Horde
### Content Phase:
- [ ] Generic
- [ ] 1-19
- [ ] 20-29
- [ ] 30-39
- [ ] 40-49
- [X] 50-59
### Current Behaviour
Original report: https://github.com/chromiecraft/chromiecraft/issues/1715 & https://github.com/chromiecraft/chromiecraft/issues/1716
Currently, 16 mobs can drop 'Plans: Lionheart Helm (ID 12717)'.
### Expected Blizzlike Behaviour
Comparing [Wowhead](https://tbc.wowhead.com/item=12717/plans-lionheart-helm#dropped-by) and the [DB](https://wowgaming.altervista.org/aowow/?item=12717) for the item, shows that multiple mobs are missing the chance of dropping the item. Although, Wowhead shows 39 mobs, there are most likely even more mobs, as some of them has only dropped it once.
Tho, as the drop chance seems really low for the missing mobs, this is really a small problem. And on that note, the drop chance might be a bit off, although with these numbers, Wowhead isn't rally the most viable source.
### Source
Wowpedia indicates it can also be dropped by elites 61+
https://wowpedia.fandom.com/wiki/Plans:_Lionheart_Helm
### Steps to reproduce the problem
1. ``SELECT * FROM `creature_loot_template` WHERE `item` = 12717 OR `Reference` = 34002;``
SQL explanation: 12717 is the ID of the item and the reference loot table 34002 contains the item, therefore any row which matches either, can drop the item.
### Extra Notes
This seems to stem from a general issue of the elite drop table.
### AC rev. hash/commit
https://github.com/chromiecraft/azerothcore-wotlk/commit/595bb6adccbabc714469f3935541978283b8bdfb
### Operating system
Ubuntu 20.04
### Modules
- [mod-ah-bot](https://github.com/azerothcore/mod-ah-bot)
- [mod-cfbg](https://github.com/azerothcore/mod-cfbg)
- [mod-chromie-xp](https://github.com/azerothcore/mod-chromie-xp)
- [mod-desertion-warnings](https://github.com/azerothcore/mod-desertion-warnings)
- [mod-duel-reset](https://github.com/azerothcore/mod-duel-reset)
- [mod-eluna-lua-engine](https://github.com/azerothcore/mod-eluna-lua-engine)
- [mod-ip-tracker](https://github.com/azerothcore/mod-ip-tracker)
- [mod-low-level-arena](https://github.com/azerothcore/mod-low-level-arena)
- [mod-multi-client-check](https://github.com/azerothcore/mod-multi-client-check)
- [mod-pvp-titles](https://github.com/azerothcore/mod-pvp-titles)
- [mod-pvpstats-announcer](https://github.com/azerothcore/mod-pvpstats-announcer)
- [mod-queue-list-cache](https://github.com/azerothcore/mod-queue-list-cache)
- [mod-server-auto-shutdown](https://github.com/azerothcore/mod-server-auto-shutdown)
- [lua-carbon-copy](https://github.com/55Honey/Acore_CarbonCopy)
- [lua-custom-worldboss](https://github.com/55Honey/Acore_CustomWorldboss)
- [lua-level-up-reward](https://github.com/55Honey/Acore_LevelUpReward)
- [lua-recruit-a-friend](https://github.com/55Honey/Acore_RecruitAFriend)
- [lua-send-and-bind](https://github.com/55Honey/Acore_SendAndBind)
- [lua-temp-announcements](https://github.com/55Honey/Acore_TempAnnouncements)
- [lua-zonecheck](https://github.com/55Honey/acore_Zonecheck)
### Customizations
None
### Server
ChromieCraft
| 1.0 | Plans: Lionheart Helm, Drop Chance and droppable mobs appear incorrect on Azeroth Core - ### What client do you play on?
enUS
### Faction
- [ ] Alliance
- [X] Horde
### Content Phase:
- [ ] Generic
- [ ] 1-19
- [ ] 20-29
- [ ] 30-39
- [ ] 40-49
- [X] 50-59
### Current Behaviour
Original report: https://github.com/chromiecraft/chromiecraft/issues/1715 & https://github.com/chromiecraft/chromiecraft/issues/1716
Currently, 16 mobs can drop 'Plans: Lionheart Helm (ID 12717)'.
### Expected Blizzlike Behaviour
Comparing [Wowhead](https://tbc.wowhead.com/item=12717/plans-lionheart-helm#dropped-by) and the [DB](https://wowgaming.altervista.org/aowow/?item=12717) for the item, shows that multiple mobs are missing the chance of dropping the item. Although, Wowhead shows 39 mobs, there are most likely even more mobs, as some of them has only dropped it once.
Tho, as the drop chance seems really low for the missing mobs, this is really a small problem. And on that note, the drop chance might be a bit off, although with these numbers, Wowhead isn't rally the most viable source.
### Source
Wowpedia indicates it can also be dropped by elites 61+
https://wowpedia.fandom.com/wiki/Plans:_Lionheart_Helm
### Steps to reproduce the problem
1. ``SELECT * FROM `creature_loot_template` WHERE `item` = 12717 OR `Reference` = 34002;``
SQL explanation: 12717 is the ID of the item and the reference loot table 34002 contains the item, therefore any row which matches either, can drop the item.
### Extra Notes
This seems to stem from a general issue of the elite drop table.
### AC rev. hash/commit
https://github.com/chromiecraft/azerothcore-wotlk/commit/595bb6adccbabc714469f3935541978283b8bdfb
### Operating system
Ubuntu 20.04
### Modules
- [mod-ah-bot](https://github.com/azerothcore/mod-ah-bot)
- [mod-cfbg](https://github.com/azerothcore/mod-cfbg)
- [mod-chromie-xp](https://github.com/azerothcore/mod-chromie-xp)
- [mod-desertion-warnings](https://github.com/azerothcore/mod-desertion-warnings)
- [mod-duel-reset](https://github.com/azerothcore/mod-duel-reset)
- [mod-eluna-lua-engine](https://github.com/azerothcore/mod-eluna-lua-engine)
- [mod-ip-tracker](https://github.com/azerothcore/mod-ip-tracker)
- [mod-low-level-arena](https://github.com/azerothcore/mod-low-level-arena)
- [mod-multi-client-check](https://github.com/azerothcore/mod-multi-client-check)
- [mod-pvp-titles](https://github.com/azerothcore/mod-pvp-titles)
- [mod-pvpstats-announcer](https://github.com/azerothcore/mod-pvpstats-announcer)
- [mod-queue-list-cache](https://github.com/azerothcore/mod-queue-list-cache)
- [mod-server-auto-shutdown](https://github.com/azerothcore/mod-server-auto-shutdown)
- [lua-carbon-copy](https://github.com/55Honey/Acore_CarbonCopy)
- [lua-custom-worldboss](https://github.com/55Honey/Acore_CustomWorldboss)
- [lua-level-up-reward](https://github.com/55Honey/Acore_LevelUpReward)
- [lua-recruit-a-friend](https://github.com/55Honey/Acore_RecruitAFriend)
- [lua-send-and-bind](https://github.com/55Honey/Acore_SendAndBind)
- [lua-temp-announcements](https://github.com/55Honey/Acore_TempAnnouncements)
- [lua-zonecheck](https://github.com/55Honey/acore_Zonecheck)
### Customizations
None
### Server
ChromieCraft
| priority | plans lionheart helm drop chance and droppable mobs appear incorrect on azeroth core what client do you play on enus faction alliance horde content phase generic current behaviour original report currently mobs can drop plans lionheart helm id expected blizzlike behaviour comparing and the for the item shows that multiple mobs are missing the chance of dropping the item although wowhead shows mobs there are most likely even more mobs as some of them has only dropped it once tho as the drop chance seems really low for the missing mobs this is really a small problem and on that note the drop chance might be a bit off although with these numbers wowhead isn t rally the most viable source source wowpedia indicates it can also be dropped by elites steps to reproduce the problem select from creature loot template where item or reference sql explanation is the id of the item and the reference loot table contains the item therefore any row which matches either can drop the item extra notes this seems to stem from a general issue of the elite drop table ac rev hash commit operating system ubuntu modules customizations none server chromiecraft | 1 |
770,092 | 27,028,625,846 | IssuesEvent | 2023-02-11 23:04:26 | SirEndii/AdvancedPeripherals | https://api.github.com/repos/SirEndii/AdvancedPeripherals | closed | Player Detector Pocket Computer throws Java Exception when moved in player Inventory | bug Priority-Low Fixed/Added in dev 1.18x 1.19x | ### Describe
PlayerDetector code crashes because of a exception in Java Code when the pocket computer thats running the code is moved in the player inventory.
### Steps to reproduce
1. Get an Advanced Player Detector Pocket Computer
2. Write a programm that uses the function PlayerDetector.getPlayerPos()
(For testing purpose i would recommend a while true loop)
3. Start the programm
4. In the moment the getPlayerPos gets called move the pocket computer in the inventory from one slot to another
(See attached video)
My Lua Stacktrace:
and my "errorRecreation.lua":
```
local playerDetector = peripheral.wrap("back");
while true
do
os.queueEvent("anticrash");
os.pullEvent("anticrash");
player = playerDetector.getPlayerPos("radston12") -- get player position data of radston12
print(player["x"] .. " " .. player["y"] .. " " .. player["z"])
end
```
### Multiplayer?
No
### Version
1.19.2-0.7.19a (Latest 1.19)
### Minecraft, Forge and maybe other related mods versions
Minecraft 1.19.2, Forge 43.1.47, Advanced Peripherials 0.7.21b, CC: Tweaked 1.101.0, (all from the CurseForge launcher)
### Screenshots or Videos
https://youtu.be/tfiqrOPeWo0
### Crashlog/log
_No response_ | 1.0 | Player Detector Pocket Computer throws Java Exception when moved in player Inventory - ### Describe
PlayerDetector code crashes because of a exception in Java Code when the pocket computer thats running the code is moved in the player inventory.
### Steps to reproduce
1. Get an Advanced Player Detector Pocket Computer
2. Write a programm that uses the function PlayerDetector.getPlayerPos()
(For testing purpose i would recommend a while true loop)
3. Start the programm
4. In the moment the getPlayerPos gets called move the pocket computer in the inventory from one slot to another
(See attached video)
My Lua Stacktrace:
and my "errorRecreation.lua":
```
local playerDetector = peripheral.wrap("back");
while true
do
os.queueEvent("anticrash");
os.pullEvent("anticrash");
player = playerDetector.getPlayerPos("radston12") -- get player position data of radston12
print(player["x"] .. " " .. player["y"] .. " " .. player["z"])
end
```
### Multiplayer?
No
### Version
1.19.2-0.7.19a (Latest 1.19)
### Minecraft, Forge and maybe other related mods versions
Minecraft 1.19.2, Forge 43.1.47, Advanced Peripherials 0.7.21b, CC: Tweaked 1.101.0, (all from the CurseForge launcher)
### Screenshots or Videos
https://youtu.be/tfiqrOPeWo0
### Crashlog/log
_No response_ | priority | player detector pocket computer throws java exception when moved in player inventory describe playerdetector code crashes because of a exception in java code when the pocket computer thats running the code is moved in the player inventory steps to reproduce get an advanced player detector pocket computer write a programm that uses the function playerdetector getplayerpos for testing purpose i would recommend a while true loop start the programm in the moment the getplayerpos gets called move the pocket computer in the inventory from one slot to another see attached video my lua stacktrace and my errorrecreation lua local playerdetector peripheral wrap back while true do os queueevent anticrash os pullevent anticrash player playerdetector getplayerpos get player position data of print player player player end multiplayer no version latest minecraft forge and maybe other related mods versions minecraft forge advanced peripherials cc tweaked all from the curseforge launcher screenshots or videos crashlog log no response | 1 |
113,339 | 4,546,902,310 | IssuesEvent | 2016-09-12 01:27:19 | loomio/loomio | https://api.github.com/repos/loomio/loomio | closed | As a member of no groups, when I visit /dashboard I'm not redirected to /explore | Priority: Low | 
repro steps: start a new group with a new account, deactivate the group, browse to /dashboard | 1.0 | As a member of no groups, when I visit /dashboard I'm not redirected to /explore - 
repro steps: start a new group with a new account, deactivate the group, browse to /dashboard | priority | as a member of no groups when i visit dashboard i m not redirected to explore repro steps start a new group with a new account deactivate the group browse to dashboard | 1 |
676,883 | 23,141,176,199 | IssuesEvent | 2022-07-28 18:38:41 | nextstrain/augur | https://api.github.com/repos/nextstrain/augur | closed | ENH: Add flag that ignores version mismatch checks in `export` | enhancement low priority good first issue | My augur workflow contains runs a custom version of refine based on Augur 14.0.0 with FFT treetime PR patches on top.
However, the rest uses Augur 15.0.0. Now `export` complains that `branch lenghts` was produced by version 14 and says the versions are incompatible. That's actually not true, export would still work, `augur` is just being overly careful.
We introduced an option to skip output json validation in v14, I think it could be useful for situations like mine to have a flag `--ignore-version-mismatch` in `export`.
It's good to have that warning on by default but it'd be nice to be able to override.
| 1.0 | ENH: Add flag that ignores version mismatch checks in `export` - My augur workflow contains runs a custom version of refine based on Augur 14.0.0 with FFT treetime PR patches on top.
However, the rest uses Augur 15.0.0. Now `export` complains that `branch lenghts` was produced by version 14 and says the versions are incompatible. That's actually not true, export would still work, `augur` is just being overly careful.
We introduced an option to skip output json validation in v14, I think it could be useful for situations like mine to have a flag `--ignore-version-mismatch` in `export`.
It's good to have that warning on by default but it'd be nice to be able to override.
| priority | enh add flag that ignores version mismatch checks in export my augur workflow contains runs a custom version of refine based on augur with fft treetime pr patches on top however the rest uses augur now export complains that branch lenghts was produced by version and says the versions are incompatible that s actually not true export would still work augur is just being overly careful we introduced an option to skip output json validation in i think it could be useful for situations like mine to have a flag ignore version mismatch in export it s good to have that warning on by default but it d be nice to be able to override | 1 |
604,085 | 18,676,360,592 | IssuesEvent | 2021-10-31 16:23:47 | TuSimple/naive-ui | https://api.github.com/repos/TuSimple/naive-ui | closed | NImage better to have a close button | feature request priority: low | <!-- generated by issue-helper DO NOT REMOVE __FEATURE_REQUEST__ -->
### This function solves the problem (这个功能解决的问题)
Sometimes image is big and cover the whole screen. User have to zoom out before click the mask to close the preview dialog. Maybe we can put a close button on toolbar.
### Expected API (期望的 API)
no new api needed.
<!-- generated by issue-helper DO NOT REMOVE __FEATURE_REQUEST__ --> | 1.0 | NImage better to have a close button - <!-- generated by issue-helper DO NOT REMOVE __FEATURE_REQUEST__ -->
### This function solves the problem (这个功能解决的问题)
Sometimes image is big and cover the whole screen. User have to zoom out before click the mask to close the preview dialog. Maybe we can put a close button on toolbar.
### Expected API (期望的 API)
no new api needed.
<!-- generated by issue-helper DO NOT REMOVE __FEATURE_REQUEST__ --> | priority | nimage better to have a close button this function solves the problem 这个功能解决的问题 sometimes image is big and cover the whole screen user have to zoom out before click the mask to close the preview dialog maybe we can put a close button on toolbar expected api 期望的 api no new api needed | 1 |
67,958 | 3,283,328,773 | IssuesEvent | 2015-10-28 12:05:18 | leeensminger/OED_Wetlands | https://api.github.com/repos/leeensminger/OED_Wetlands | closed | Results - Delineations or Mitigation Assets - Rename the field "# Selections" | bug - low priority | Within the Results tab for Delineations or Mitigation Assets, within the Study Areas data grid (OR Mitigation Sites data grid, if in Mitigation workflow), please update the last field within the grid ("# Selections") to read "# Systems". | 1.0 | Results - Delineations or Mitigation Assets - Rename the field "# Selections" - Within the Results tab for Delineations or Mitigation Assets, within the Study Areas data grid (OR Mitigation Sites data grid, if in Mitigation workflow), please update the last field within the grid ("# Selections") to read "# Systems". | priority | results delineations or mitigation assets rename the field selections within the results tab for delineations or mitigation assets within the study areas data grid or mitigation sites data grid if in mitigation workflow please update the last field within the grid selections to read systems | 1 |
194,393 | 6,894,449,254 | IssuesEvent | 2017-11-23 10:02:33 | pmem/issues | https://api.github.com/repos/pmem/issues | closed | test: obj_lane/TEST0 fails with drd | Exposure: Low OS: Linux Priority: 4 low State: To be verified Type: Bug | Found on 7f6dcc563f09d1aeae49dabc33ebdbcc1bb2f961
> obj_lane/TEST0: SETUP (all/pmem/debug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11213== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11213== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11213== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11213== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11213== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11213== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11213== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11213== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11213== at 0x4061DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11213== by 0x40408E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11213== by 0x404799: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> pmem0.log below.
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:265 out_init] pid 11213: program: /home/jenkins/workspace/nvml_tests_drd/src/test/obj_lane/obj_lane
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:267 out_init] libpmem version 1.0
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [mmap.c:91 util_mmap_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [libpmem.c:56 libpmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1255 pmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1217 pmem_get_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1221 pmem_get_cpuinfo] clflush supported
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1190 pmem_log_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1197 pmem_log_cpuinfo] using clflush
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1204 pmem_log_cpuinfo] using movnt
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=pmem BUILD=debug
> obj_lane/TEST0: SETUP (all/pmem/nondebug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11264== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11264== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11264== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11264== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11264== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11264== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11264== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11264== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11264== at 0x4061DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11264== by 0x40408E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11264== by 0x404799: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=pmem BUILD=nondebug
> obj_lane/TEST0: SETUP (all/pmem/static-debug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11306== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11306== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11306== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11306== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11306== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11306== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11306== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11306== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11306== at 0x40618A: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11306== by 0x40403E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11306== by 0x404749: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> pmem0.log below.
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:265 out_init] pid 11306: program: /home/jenkins/workspace/nvml_tests_drd/src/test/obj_lane/obj_lane.static-debug
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:267 out_init] libpmem version 1.0
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [mmap.c:91 util_mmap_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [libpmem.c:56 libpmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1255 pmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1217 pmem_get_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1221 pmem_get_cpuinfo] clflush supported
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1190 pmem_log_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1197 pmem_log_cpuinfo] using clflush
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1204 pmem_log_cpuinfo] using movnt
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=pmem BUILD=static-debug
> obj_lane/TEST0: SETUP (all/pmem/static-nondebug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11357== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11357== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11357== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11357== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11357== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11357== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11357== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11357== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11357== at 0x4062DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11357== by 0x40418E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11357== by 0x404899: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=pmem BUILD=static-nondebug
> obj_lane/TEST0: SETUP (all/non-pmem/debug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11398== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11398== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11398== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11398== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11398== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11398== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11398== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11398== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11398== at 0x4061DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11398== by 0x40408E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11398== by 0x404799: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> pmem0.log below.
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:265 out_init] pid 11398: program: /home/jenkins/workspace/nvml_tests_drd/src/test/obj_lane/obj_lane
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:267 out_init] libpmem version 1.0
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [mmap.c:91 util_mmap_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [libpmem.c:56 libpmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1255 pmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1217 pmem_get_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1221 pmem_get_cpuinfo] clflush supported
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1190 pmem_log_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1197 pmem_log_cpuinfo] using clflush
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1204 pmem_log_cpuinfo] using movnt
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=non-pmem BUILD=debug
> obj_lane/TEST0: SETUP (all/non-pmem/nondebug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11449== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11449== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11449== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11449== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11449== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11449== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11449== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11449== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11449== at 0x4061DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11449== by 0x40408E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11449== by 0x404799: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=non-pmem BUILD=nondebug
> obj_lane/TEST0: SETUP (all/non-pmem/static-debug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11491== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11491== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11491== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11491== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11491== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11491== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11491== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11491== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11491== at 0x40618A: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11491== by 0x40403E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11491== by 0x404749: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> pmem0.log below.
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:265 out_init] pid 11491: program: /home/jenkins/workspace/nvml_tests_drd/src/test/obj_lane/obj_lane.static-debug
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:267 out_init] libpmem version 1.0
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [mmap.c:91 util_mmap_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [libpmem.c:56 libpmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1255 pmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1217 pmem_get_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1221 pmem_get_cpuinfo] clflush supported
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1190 pmem_log_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1197 pmem_log_cpuinfo] using clflush
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1204 pmem_log_cpuinfo] using movnt
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=non-pmem BUILD=static-debug
> obj_lane/TEST0: SETUP (all/non-pmem/static-nondebug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11542== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11542== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11542== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11542== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11542== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11542== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11542== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11542== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11542== at 0x4062DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11542== by 0x40418E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11542== by 0x404899: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=non-pmem BUILD=static-nondebug
> ../Makefile.inc:350: recipe for target 'TEST0' failed
> make[3]: *** [TEST0] Error 1 | 1.0 | test: obj_lane/TEST0 fails with drd - Found on 7f6dcc563f09d1aeae49dabc33ebdbcc1bb2f961
> obj_lane/TEST0: SETUP (all/pmem/debug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11213== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11213== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11213== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11213== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11213== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11213== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11213== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11213== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11213== at 0x4061DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11213== by 0x40408E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11213== by 0x404799: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> pmem0.log below.
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:265 out_init] pid 11213: program: /home/jenkins/workspace/nvml_tests_drd/src/test/obj_lane/obj_lane
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:267 out_init] libpmem version 1.0
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [mmap.c:91 util_mmap_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [libpmem.c:56 libpmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1255 pmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1217 pmem_get_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1221 pmem_get_cpuinfo] clflush supported
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1190 pmem_log_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1197 pmem_log_cpuinfo] using clflush
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1204 pmem_log_cpuinfo] using movnt
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=pmem BUILD=debug
> obj_lane/TEST0: SETUP (all/pmem/nondebug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11264== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11264== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11264== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11264== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11264== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11264== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11264== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11264== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11264== at 0x4061DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11264== by 0x40408E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11264== by 0x404799: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=pmem BUILD=nondebug
> obj_lane/TEST0: SETUP (all/pmem/static-debug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11306== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11306== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11306== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11306== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11306== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11306== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11306== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11306== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11306== at 0x40618A: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11306== by 0x40403E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11306== by 0x404749: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> pmem0.log below.
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:265 out_init] pid 11306: program: /home/jenkins/workspace/nvml_tests_drd/src/test/obj_lane/obj_lane.static-debug
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:267 out_init] libpmem version 1.0
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [mmap.c:91 util_mmap_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [libpmem.c:56 libpmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1255 pmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1217 pmem_get_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1221 pmem_get_cpuinfo] clflush supported
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1190 pmem_log_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1197 pmem_log_cpuinfo] using clflush
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1204 pmem_log_cpuinfo] using movnt
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=pmem BUILD=static-debug
> obj_lane/TEST0: SETUP (all/pmem/static-nondebug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11357== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11357== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11357== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11357== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11357== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11357== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11357== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11357== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11357== at 0x4062DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11357== by 0x40418E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11357== by 0x404899: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=pmem BUILD=static-nondebug
> obj_lane/TEST0: SETUP (all/non-pmem/debug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11398== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11398== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11398== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11398== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11398== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11398== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11398== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11398== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11398== at 0x4061DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11398== by 0x40408E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11398== by 0x404799: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> pmem0.log below.
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:265 out_init] pid 11398: program: /home/jenkins/workspace/nvml_tests_drd/src/test/obj_lane/obj_lane
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:267 out_init] libpmem version 1.0
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [mmap.c:91 util_mmap_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [libpmem.c:56 libpmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1255 pmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1217 pmem_get_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1221 pmem_get_cpuinfo] clflush supported
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1190 pmem_log_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1197 pmem_log_cpuinfo] using clflush
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1204 pmem_log_cpuinfo] using movnt
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=non-pmem BUILD=debug
> obj_lane/TEST0: SETUP (all/non-pmem/nondebug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11449== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11449== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11449== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11449== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11449== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11449== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11449== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11449== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11449== at 0x4061DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11449== by 0x40408E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11449== by 0x404799: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=non-pmem BUILD=nondebug
> obj_lane/TEST0: SETUP (all/non-pmem/static-debug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11491== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11491== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11491== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11491== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11491== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11491== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11491== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11491== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11491== at 0x40618A: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11491== by 0x40403E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11491== by 0x404749: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> pmem0.log below.
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:265 out_init] pid 11491: program: /home/jenkins/workspace/nvml_tests_drd/src/test/obj_lane/obj_lane.static-debug
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:267 out_init] libpmem version 1.0
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:268 out_init] src version SRCVERSION:1.3-88-g7f6dcc5
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:276 out_init] compiled with support for Valgrind pmemcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:281 out_init] compiled with support for Valgrind helgrind
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:286 out_init] compiled with support for Valgrind memcheck
> obj_lane/TEST0 pmem0.log <libpmem>: <1> [out.c:291 out_init] compiled with support for Valgrind drd
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [mmap.c:91 util_mmap_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [libpmem.c:56 libpmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1255 pmem_init]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1217 pmem_get_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1221 pmem_get_cpuinfo] clflush supported
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1190 pmem_log_cpuinfo]
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1197 pmem_log_cpuinfo] using clflush
> obj_lane/TEST0 pmem0.log <libpmem>: <3> [pmem.c:1204 pmem_log_cpuinfo] using movnt
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=non-pmem BUILD=static-debug
> obj_lane/TEST0: SETUP (all/non-pmem/static-nondebug/drd)
> obj_lane/TEST0: START: obj_lane
> obj_lane/TEST0 failed with exit code 1. err0.log below.
> Last 30 lines of drd0.log below (whole file has 44 lines).
> obj_lane/TEST0 drd0.log ==11542== by 0x38080441: vgDrd_thread_stop_using_mem (drd_thread.c:1201)
> obj_lane/TEST0 drd0.log ==11542== by 0x3808761A: drd_stop_using_mem (drd_main.c:388)
> obj_lane/TEST0 drd0.log ==11542== by 0x3808761A: vgDrd_clean_memory (drd_main.c:409)
> obj_lane/TEST0 drd0.log ==11542== by 0x38074A0A: handle_client_request (drd_clientreq.c:585)
> obj_lane/TEST0 drd0.log ==11542== by 0x380E2A00: do_client_request (scheduler.c:2076)
> obj_lane/TEST0 drd0.log ==11542== by 0x380E2A00: vgPlain_scheduler (scheduler.c:1409)
> obj_lane/TEST0 drd0.log ==11542== by 0x380F15D9: thread_wrapper (syswrap-linux.c:103)
> obj_lane/TEST0 drd0.log ==11542== by 0x380F15D9: run_a_thread_NORETURN (syswrap-linux.c:156)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log sched status:
> obj_lane/TEST0 drd0.log running_tid=1
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Thread 1: status = VgTs_Runnable
> obj_lane/TEST0 drd0.log ==11542== at 0x4062DA: lane_hold (lane.c:462)
> obj_lane/TEST0 drd0.log ==11542== by 0x40418E: test_lane_hold_release (obj_lane.c:246)
> obj_lane/TEST0 drd0.log ==11542== by 0x404899: main (obj_lane.c:398)
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log Note: see also the FAQ in the source distribution.
> obj_lane/TEST0 drd0.log It contains workarounds to several common problems.
> obj_lane/TEST0 drd0.log In particular, if Valgrind aborted or crashed after
> obj_lane/TEST0 drd0.log identifying problems in your program, there's a good chance
> obj_lane/TEST0 drd0.log that fixing those problems will prevent Valgrind aborting or
> obj_lane/TEST0 drd0.log crashing, especially if it happened in m_mallocfree.c.
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log If that doesn't help, please report this bug to: www.valgrind.org
> obj_lane/TEST0 drd0.log
> obj_lane/TEST0 drd0.log In the bug report, send all the above text, the valgrind
> obj_lane/TEST0 drd0.log version, and what OS and version you are using. Thanks.
> obj_lane/TEST0 drd0.log
>
> Last 30 lines of trace0.log below (whole file has 68 lines).
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:112 lane_noop_boot} lane_noop_init
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2800
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x3400
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x4c00
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x5800
> obj_lane/TEST0 trace0.log {obj_lane.c:92 lane_noop_recovery} lane_noop_recovery 0x2000
> obj_lane/TEST0 trace0.log {obj_lane.c:102 lane_noop_check} lane_noop_check 0x2000
>
> RUNTESTS: stopping: obj_lane/TEST0 failed, TEST=all FS=non-pmem BUILD=static-nondebug
> ../Makefile.inc:350: recipe for target 'TEST0' failed
> make[3]: *** [TEST0] Error 1 | priority | test obj lane fails with drd found on obj lane setup all pmem debug drd obj lane start obj lane obj lane failed with exit code log below last lines of log below whole file has lines obj lane log by vgdrd thread stop using mem drd thread c obj lane log by drd stop using mem drd main c obj lane log by vgdrd clean memory drd main c obj lane log by handle client request drd clientreq c obj lane log by do client request scheduler c obj lane log by vgplain scheduler scheduler c obj lane log by thread wrapper syswrap linux c obj lane log by run a thread noreturn syswrap linux c obj lane log obj lane log sched status obj lane log running tid obj lane log obj lane log thread status vgts runnable obj lane log at lane hold lane c obj lane log by test lane hold release obj lane c obj lane log by main obj lane c obj lane log obj lane log obj lane log note see also the faq in the source distribution obj lane log it contains workarounds to several common problems obj lane log in particular if valgrind aborted or crashed after obj lane log identifying problems in your program there s a good chance obj lane log that fixing those problems will prevent valgrind aborting or obj lane log crashing especially if it happened in m mallocfree c obj lane log obj lane log if that doesn t help please report this bug to obj lane log obj lane log in the bug report send all the above text the valgrind obj lane log version and what os and version you are using thanks obj lane log last lines of log below whole file has lines obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop check lane noop check log below obj lane log pid program home jenkins workspace nvml tests drd src test obj lane obj lane obj lane log libpmem version obj lane log src version srcversion obj lane log compiled with support for valgrind pmemcheck obj lane log compiled with support for valgrind helgrind obj lane log compiled with support for valgrind memcheck obj lane log compiled with support for valgrind drd obj lane log obj lane log obj lane log obj lane log obj lane log clflush supported obj lane log obj lane log using clflush obj lane log using movnt runtests stopping obj lane failed test all fs pmem build debug obj lane setup all pmem nondebug drd obj lane start obj lane obj lane failed with exit code log below last lines of log below whole file has lines obj lane log by vgdrd thread stop using mem drd thread c obj lane log by drd stop using mem drd main c obj lane log by vgdrd clean memory drd main c obj lane log by handle client request drd clientreq c obj lane log by do client request scheduler c obj lane log by vgplain scheduler scheduler c obj lane log by thread wrapper syswrap linux c obj lane log by run a thread noreturn syswrap linux c obj lane log obj lane log sched status obj lane log running tid obj lane log obj lane log thread status vgts runnable obj lane log at lane hold lane c obj lane log by test lane hold release obj lane c obj lane log by main obj lane c obj lane log obj lane log obj lane log note see also the faq in the source distribution obj lane log it contains workarounds to several common problems obj lane log in particular if valgrind aborted or crashed after obj lane log identifying problems in your program there s a good chance obj lane log that fixing those problems will prevent valgrind aborting or obj lane log crashing especially if it happened in m mallocfree c obj lane log obj lane log if that doesn t help please report this bug to obj lane log obj lane log in the bug report send all the above text the valgrind obj lane log version and what os and version you are using thanks obj lane log last lines of log below whole file has lines obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop check lane noop check runtests stopping obj lane failed test all fs pmem build nondebug obj lane setup all pmem static debug drd obj lane start obj lane obj lane failed with exit code log below last lines of log below whole file has lines obj lane log by vgdrd thread stop using mem drd thread c obj lane log by drd stop using mem drd main c obj lane log by vgdrd clean memory drd main c obj lane log by handle client request drd clientreq c obj lane log by do client request scheduler c obj lane log by vgplain scheduler scheduler c obj lane log by thread wrapper syswrap linux c obj lane log by run a thread noreturn syswrap linux c obj lane log obj lane log sched status obj lane log running tid obj lane log obj lane log thread status vgts runnable obj lane log at lane hold lane c obj lane log by test lane hold release obj lane c obj lane log by main obj lane c obj lane log obj lane log obj lane log note see also the faq in the source distribution obj lane log it contains workarounds to several common problems obj lane log in particular if valgrind aborted or crashed after obj lane log identifying problems in your program there s a good chance obj lane log that fixing those problems will prevent valgrind aborting or obj lane log crashing especially if it happened in m mallocfree c obj lane log obj lane log if that doesn t help please report this bug to obj lane log obj lane log in the bug report send all the above text the valgrind obj lane log version and what os and version you are using thanks obj lane log last lines of log below whole file has lines obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop check lane noop check log below obj lane log pid program home jenkins workspace nvml tests drd src test obj lane obj lane static debug obj lane log libpmem version obj lane log src version srcversion obj lane log compiled with support for valgrind pmemcheck obj lane log compiled with support for valgrind helgrind obj lane log compiled with support for valgrind memcheck obj lane log compiled with support for valgrind drd obj lane log obj lane log obj lane log obj lane log obj lane log clflush supported obj lane log obj lane log using clflush obj lane log using movnt runtests stopping obj lane failed test all fs pmem build static debug obj lane setup all pmem static nondebug drd obj lane start obj lane obj lane failed with exit code log below last lines of log below whole file has lines obj lane log by vgdrd thread stop using mem drd thread c obj lane log by drd stop using mem drd main c obj lane log by vgdrd clean memory drd main c obj lane log by handle client request drd clientreq c obj lane log by do client request scheduler c obj lane log by vgplain scheduler scheduler c obj lane log by thread wrapper syswrap linux c obj lane log by run a thread noreturn syswrap linux c obj lane log obj lane log sched status obj lane log running tid obj lane log obj lane log thread status vgts runnable obj lane log at lane hold lane c obj lane log by test lane hold release obj lane c obj lane log by main obj lane c obj lane log obj lane log obj lane log note see also the faq in the source distribution obj lane log it contains workarounds to several common problems obj lane log in particular if valgrind aborted or crashed after obj lane log identifying problems in your program there s a good chance obj lane log that fixing those problems will prevent valgrind aborting or obj lane log crashing especially if it happened in m mallocfree c obj lane log obj lane log if that doesn t help please report this bug to obj lane log obj lane log in the bug report send all the above text the valgrind obj lane log version and what os and version you are using thanks obj lane log last lines of log below whole file has lines obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop check lane noop check runtests stopping obj lane failed test all fs pmem build static nondebug obj lane setup all non pmem debug drd obj lane start obj lane obj lane failed with exit code log below last lines of log below whole file has lines obj lane log by vgdrd thread stop using mem drd thread c obj lane log by drd stop using mem drd main c obj lane log by vgdrd clean memory drd main c obj lane log by handle client request drd clientreq c obj lane log by do client request scheduler c obj lane log by vgplain scheduler scheduler c obj lane log by thread wrapper syswrap linux c obj lane log by run a thread noreturn syswrap linux c obj lane log obj lane log sched status obj lane log running tid obj lane log obj lane log thread status vgts runnable obj lane log at lane hold lane c obj lane log by test lane hold release obj lane c obj lane log by main obj lane c obj lane log obj lane log obj lane log note see also the faq in the source distribution obj lane log it contains workarounds to several common problems obj lane log in particular if valgrind aborted or crashed after obj lane log identifying problems in your program there s a good chance obj lane log that fixing those problems will prevent valgrind aborting or obj lane log crashing especially if it happened in m mallocfree c obj lane log obj lane log if that doesn t help please report this bug to obj lane log obj lane log in the bug report send all the above text the valgrind obj lane log version and what os and version you are using thanks obj lane log last lines of log below whole file has lines obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop check lane noop check log below obj lane log pid program home jenkins workspace nvml tests drd src test obj lane obj lane obj lane log libpmem version obj lane log src version srcversion obj lane log compiled with support for valgrind pmemcheck obj lane log compiled with support for valgrind helgrind obj lane log compiled with support for valgrind memcheck obj lane log compiled with support for valgrind drd obj lane log obj lane log obj lane log obj lane log obj lane log clflush supported obj lane log obj lane log using clflush obj lane log using movnt runtests stopping obj lane failed test all fs non pmem build debug obj lane setup all non pmem nondebug drd obj lane start obj lane obj lane failed with exit code log below last lines of log below whole file has lines obj lane log by vgdrd thread stop using mem drd thread c obj lane log by drd stop using mem drd main c obj lane log by vgdrd clean memory drd main c obj lane log by handle client request drd clientreq c obj lane log by do client request scheduler c obj lane log by vgplain scheduler scheduler c obj lane log by thread wrapper syswrap linux c obj lane log by run a thread noreturn syswrap linux c obj lane log obj lane log sched status obj lane log running tid obj lane log obj lane log thread status vgts runnable obj lane log at lane hold lane c obj lane log by test lane hold release obj lane c obj lane log by main obj lane c obj lane log obj lane log obj lane log note see also the faq in the source distribution obj lane log it contains workarounds to several common problems obj lane log in particular if valgrind aborted or crashed after obj lane log identifying problems in your program there s a good chance obj lane log that fixing those problems will prevent valgrind aborting or obj lane log crashing especially if it happened in m mallocfree c obj lane log obj lane log if that doesn t help please report this bug to obj lane log obj lane log in the bug report send all the above text the valgrind obj lane log version and what os and version you are using thanks obj lane log last lines of log below whole file has lines obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop check lane noop check runtests stopping obj lane failed test all fs non pmem build nondebug obj lane setup all non pmem static debug drd obj lane start obj lane obj lane failed with exit code log below last lines of log below whole file has lines obj lane log by vgdrd thread stop using mem drd thread c obj lane log by drd stop using mem drd main c obj lane log by vgdrd clean memory drd main c obj lane log by handle client request drd clientreq c obj lane log by do client request scheduler c obj lane log by vgplain scheduler scheduler c obj lane log by thread wrapper syswrap linux c obj lane log by run a thread noreturn syswrap linux c obj lane log obj lane log sched status obj lane log running tid obj lane log obj lane log thread status vgts runnable obj lane log at lane hold lane c obj lane log by test lane hold release obj lane c obj lane log by main obj lane c obj lane log obj lane log obj lane log note see also the faq in the source distribution obj lane log it contains workarounds to several common problems obj lane log in particular if valgrind aborted or crashed after obj lane log identifying problems in your program there s a good chance obj lane log that fixing those problems will prevent valgrind aborting or obj lane log crashing especially if it happened in m mallocfree c obj lane log obj lane log if that doesn t help please report this bug to obj lane log obj lane log in the bug report send all the above text the valgrind obj lane log version and what os and version you are using thanks obj lane log last lines of log below whole file has lines obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop check lane noop check log below obj lane log pid program home jenkins workspace nvml tests drd src test obj lane obj lane static debug obj lane log libpmem version obj lane log src version srcversion obj lane log compiled with support for valgrind pmemcheck obj lane log compiled with support for valgrind helgrind obj lane log compiled with support for valgrind memcheck obj lane log compiled with support for valgrind drd obj lane log obj lane log obj lane log obj lane log obj lane log clflush supported obj lane log obj lane log using clflush obj lane log using movnt runtests stopping obj lane failed test all fs non pmem build static debug obj lane setup all non pmem static nondebug drd obj lane start obj lane obj lane failed with exit code log below last lines of log below whole file has lines obj lane log by vgdrd thread stop using mem drd thread c obj lane log by drd stop using mem drd main c obj lane log by vgdrd clean memory drd main c obj lane log by handle client request drd clientreq c obj lane log by do client request scheduler c obj lane log by vgplain scheduler scheduler c obj lane log by thread wrapper syswrap linux c obj lane log by run a thread noreturn syswrap linux c obj lane log obj lane log sched status obj lane log running tid obj lane log obj lane log thread status vgts runnable obj lane log at lane hold lane c obj lane log by test lane hold release obj lane c obj lane log by main obj lane c obj lane log obj lane log obj lane log note see also the faq in the source distribution obj lane log it contains workarounds to several common problems obj lane log in particular if valgrind aborted or crashed after obj lane log identifying problems in your program there s a good chance obj lane log that fixing those problems will prevent valgrind aborting or obj lane log crashing especially if it happened in m mallocfree c obj lane log obj lane log if that doesn t help please report this bug to obj lane log obj lane log in the bug report send all the above text the valgrind obj lane log version and what os and version you are using thanks obj lane log last lines of log below whole file has lines obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop boot lane noop init obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop check lane noop check obj lane log obj lane c lane noop recovery lane noop recovery obj lane log obj lane c lane noop check lane noop check runtests stopping obj lane failed test all fs non pmem build static nondebug makefile inc recipe for target failed make error | 1 |
73,390 | 3,411,506,950 | IssuesEvent | 2015-12-05 04:26:05 | PolarisSS13/Polaris | https://api.github.com/repos/PolarisSS13/Polaris | closed | Escape shuttle leaves sand floor. | Priority: Low Unwanted Feature Removal | Once the escape shuttle/transfer shuttle has left it leaves an asteroid sand floor where it was. | 1.0 | Escape shuttle leaves sand floor. - Once the escape shuttle/transfer shuttle has left it leaves an asteroid sand floor where it was. | priority | escape shuttle leaves sand floor once the escape shuttle transfer shuttle has left it leaves an asteroid sand floor where it was | 1 |
708,775 | 24,354,272,901 | IssuesEvent | 2022-10-03 05:26:57 | erlang/otp | https://api.github.com/repos/erlang/otp | closed | ERL-691: time_SUITE:univ_to_local depends on local TZ | team:VM help wanted bug priority:low |
Original reporter: `dotsimon.`
Affected version: `OTP-21.0`
Component: `erts`
Migrated from: https://bugs.erlang.org/browse/ERL-691
---
```
time_SUITE:univ_to_local & time_SUITE:local_to_univ both fail if the local TZ is not CET or SAST
A possible solution that tests both of those timezones independent of the local TZ:
https://github.com/dotsimon/otp/tree/time_SUITE_location
*How to reproduce*
TZ=PDT erl
ts:run(emulator, time_SUITE, univ_to_local, [batch]).
```
| 1.0 | ERL-691: time_SUITE:univ_to_local depends on local TZ -
Original reporter: `dotsimon.`
Affected version: `OTP-21.0`
Component: `erts`
Migrated from: https://bugs.erlang.org/browse/ERL-691
---
```
time_SUITE:univ_to_local & time_SUITE:local_to_univ both fail if the local TZ is not CET or SAST
A possible solution that tests both of those timezones independent of the local TZ:
https://github.com/dotsimon/otp/tree/time_SUITE_location
*How to reproduce*
TZ=PDT erl
ts:run(emulator, time_SUITE, univ_to_local, [batch]).
```
| priority | erl time suite univ to local depends on local tz original reporter dotsimon affected version otp component erts migrated from time suite univ to local time suite local to univ both fail if the local tz is not cet or sast a possible solution that tests both of those timezones independent of the local tz how to reproduce tz pdt erl ts run emulator time suite univ to local | 1 |
510,360 | 14,789,157,145 | IssuesEvent | 2021-01-12 10:11:30 | ZeusWPI/hydra | https://api.github.com/repos/ZeusWPI/hydra | closed | Clean-up | low priority | - The logo's have been transferred to the DSA API for a while, and both apps have used the new API for a while. We can remove the logo's and related code from this repo.
- Remove references to Google Assistent integration, e.g. on website and in readme, as it is now defunkt. | 1.0 | Clean-up - - The logo's have been transferred to the DSA API for a while, and both apps have used the new API for a while. We can remove the logo's and related code from this repo.
- Remove references to Google Assistent integration, e.g. on website and in readme, as it is now defunkt. | priority | clean up the logo s have been transferred to the dsa api for a while and both apps have used the new api for a while we can remove the logo s and related code from this repo remove references to google assistent integration e g on website and in readme as it is now defunkt | 1 |
226,330 | 7,517,921,800 | IssuesEvent | 2018-04-12 06:28:44 | cms-gem-daq-project/gem-plotting-tools | https://api.github.com/repos/cms-gem-daq-project/gem-plotting-tools | closed | Feature Request: anaUltraScurve.py uses TGraphAsymmErrors::BayesDivide() | Priority: Low Type: Enhancement Type: Maintenance | <!--- Provide a general summary of the issue in the Title above -->
## Brief summary of issue
<!--- Provide a description of the issue, including any other issues or pull requests it references -->
Based on the suggestion of @cbravo135 in https://github.com/cms-gem-daq-project/gem-plotting-tools/issues/37:
> We should change the scurve object to be a TGraphAsymmErrors made by dividing 2 histograms so C-P confidence intervals are used. Then all fits will be done with an efficiency of 0 to 1 and have the proper error bars. This would also mean several scurves could be statistically summed together and the analysis would be robust. It would also allow the number of pulses per Vcal bin to be unequal and the fit could still work.
I think the best way to implement this would be to change `anaUltraScurve.py` to fit a distribution that is made with the `TGraphAsymmErrors::Divide()` method following the `BayesDivide()` approach described [here](https://root.cern.ch/doc/master/classTGraphAsymmErrors.html#a78cd209f4da9a169848ab23f539e1c94), or more aptly as the documentation suggests e.g.:
```
TGraphAsymmErrors::Divide(pass,total,"cl=0.683 b(1,1) mode")
```
### Types of issue
<!--- Propsed labels (see CONTRIBUTING.md) to help maintainers label your issue: -->
- [ ] Bug report (report an issue with the code)
- [X] Feature request (request for change which adds functionality)
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
scurve distributions made and fit by `anaUltraScurve.py` should go from 0 to 1 instead of 0 to `options.Nev` and then their error bars should reflect appropriate confidence intervals.
## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
scurve distributions made and fit by `anaUltraScurve.py` should go from 0 to `options.Nev` which require knowledge of the number of triggers per `VCAL` value that were used during the scan. Error bars at each point are simply `sqrt(N)` where `N` is the value of the function at a given `VCAL` value.
<!--- Template thanks to https://www.talater.com/open-source-templates/#/page/98 -->
| 1.0 | Feature Request: anaUltraScurve.py uses TGraphAsymmErrors::BayesDivide() - <!--- Provide a general summary of the issue in the Title above -->
## Brief summary of issue
<!--- Provide a description of the issue, including any other issues or pull requests it references -->
Based on the suggestion of @cbravo135 in https://github.com/cms-gem-daq-project/gem-plotting-tools/issues/37:
> We should change the scurve object to be a TGraphAsymmErrors made by dividing 2 histograms so C-P confidence intervals are used. Then all fits will be done with an efficiency of 0 to 1 and have the proper error bars. This would also mean several scurves could be statistically summed together and the analysis would be robust. It would also allow the number of pulses per Vcal bin to be unequal and the fit could still work.
I think the best way to implement this would be to change `anaUltraScurve.py` to fit a distribution that is made with the `TGraphAsymmErrors::Divide()` method following the `BayesDivide()` approach described [here](https://root.cern.ch/doc/master/classTGraphAsymmErrors.html#a78cd209f4da9a169848ab23f539e1c94), or more aptly as the documentation suggests e.g.:
```
TGraphAsymmErrors::Divide(pass,total,"cl=0.683 b(1,1) mode")
```
### Types of issue
<!--- Propsed labels (see CONTRIBUTING.md) to help maintainers label your issue: -->
- [ ] Bug report (report an issue with the code)
- [X] Feature request (request for change which adds functionality)
## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->
scurve distributions made and fit by `anaUltraScurve.py` should go from 0 to 1 instead of 0 to `options.Nev` and then their error bars should reflect appropriate confidence intervals.
## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->
scurve distributions made and fit by `anaUltraScurve.py` should go from 0 to `options.Nev` which require knowledge of the number of triggers per `VCAL` value that were used during the scan. Error bars at each point are simply `sqrt(N)` where `N` is the value of the function at a given `VCAL` value.
<!--- Template thanks to https://www.talater.com/open-source-templates/#/page/98 -->
| priority | feature request anaultrascurve py uses tgraphasymmerrors bayesdivide brief summary of issue based on the suggestion of in we should change the scurve object to be a tgraphasymmerrors made by dividing histograms so c p confidence intervals are used then all fits will be done with an efficiency of to and have the proper error bars this would also mean several scurves could be statistically summed together and the analysis would be robust it would also allow the number of pulses per vcal bin to be unequal and the fit could still work i think the best way to implement this would be to change anaultrascurve py to fit a distribution that is made with the tgraphasymmerrors divide method following the bayesdivide approach described or more aptly as the documentation suggests e g tgraphasymmerrors divide pass total cl b mode types of issue bug report report an issue with the code feature request request for change which adds functionality expected behavior scurve distributions made and fit by anaultrascurve py should go from to instead of to options nev and then their error bars should reflect appropriate confidence intervals current behavior scurve distributions made and fit by anaultrascurve py should go from to options nev which require knowledge of the number of triggers per vcal value that were used during the scan error bars at each point are simply sqrt n where n is the value of the function at a given vcal value | 1 |
251,431 | 8,015,344,467 | IssuesEvent | 2018-07-25 09:42:04 | wso2/devstudio-tooling-ei | https://api.github.com/repos/wso2/devstudio-tooling-ei | closed | API handlers cannot be added via design view | Priority/Low enhancement | **Description:**
In Dev Studio tool, there's no any UI available to add handlers to a particular API. However, developers still can add handlers via source view.
**Affected Product Version:**
EI 6.2.0
**Related Issues:**
https://wso2.org/jira/browse/ESBJAVA-3395 | 1.0 | API handlers cannot be added via design view - **Description:**
In Dev Studio tool, there's no any UI available to add handlers to a particular API. However, developers still can add handlers via source view.
**Affected Product Version:**
EI 6.2.0
**Related Issues:**
https://wso2.org/jira/browse/ESBJAVA-3395 | priority | api handlers cannot be added via design view description in dev studio tool there s no any ui available to add handlers to a particular api however developers still can add handlers via source view affected product version ei related issues | 1 |
384,796 | 11,403,666,152 | IssuesEvent | 2020-01-31 07:52:43 | lorenzwalthert/precommit | https://api.github.com/repos/lorenzwalthert/precommit | closed | Cannot exclude .RProfile from R pre-commit hooks | Complexity: Medium Priority: Low Status: Unassigned Type: User question | I'm having the problem of running these precommit hooks because we have a `.RProfile` file in the root folder of our project that contains:
```
setwd("/aktionstool")
```
When I run the precommit hooks (e.g. `style-files`) I get the following error:
```
Error in setwd("/aktionstool") : cannot change working directory
Execution halted
```
I have tried altering the `.pre-commit-config.yaml` file to exclude the `.Rprofile` file with
```
- id: style-files # Autoformat code syntax
args: [--style_pkg=styler, --style_fun=tidyverse_style]
exclude: .Rprofile
```
and variants of this using regex (e.g. `*.Rprofile`, `$Rprofile`, etc.) or but I unfortunately cannot get this file to be ignored. I'm not sure if this is a misunderstanding on my part with how the pre-commit library works or if it is specific to these hooks?
| 1.0 | Cannot exclude .RProfile from R pre-commit hooks - I'm having the problem of running these precommit hooks because we have a `.RProfile` file in the root folder of our project that contains:
```
setwd("/aktionstool")
```
When I run the precommit hooks (e.g. `style-files`) I get the following error:
```
Error in setwd("/aktionstool") : cannot change working directory
Execution halted
```
I have tried altering the `.pre-commit-config.yaml` file to exclude the `.Rprofile` file with
```
- id: style-files # Autoformat code syntax
args: [--style_pkg=styler, --style_fun=tidyverse_style]
exclude: .Rprofile
```
and variants of this using regex (e.g. `*.Rprofile`, `$Rprofile`, etc.) or but I unfortunately cannot get this file to be ignored. I'm not sure if this is a misunderstanding on my part with how the pre-commit library works or if it is specific to these hooks?
| priority | cannot exclude rprofile from r pre commit hooks i m having the problem of running these precommit hooks because we have a rprofile file in the root folder of our project that contains setwd aktionstool when i run the precommit hooks e g style files i get the following error error in setwd aktionstool cannot change working directory execution halted i have tried altering the pre commit config yaml file to exclude the rprofile file with id style files autoformat code syntax args exclude rprofile and variants of this using regex e g rprofile rprofile etc or but i unfortunately cannot get this file to be ignored i m not sure if this is a misunderstanding on my part with how the pre commit library works or if it is specific to these hooks | 1 |
731,310 | 25,209,524,460 | IssuesEvent | 2022-11-14 01:35:39 | crushten/go_endpoint_cloud | https://api.github.com/repos/crushten/go_endpoint_cloud | closed | Clean up/format application code | type: operations and maintenance priority: low application | There are some general best practices/formatting recommened. Shoud probably check that and change the code accordingly.
See:
* https://go.dev/doc/effective_go
* https://github.com/golang/go/wiki/CodeReviewComments
* https://github.com/smallnest/go-best-practices
* https://github.com/golang-standards/project-layout
* http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in-go-golang/
Note some of these have overlap. | 1.0 | Clean up/format application code - There are some general best practices/formatting recommened. Shoud probably check that and change the code accordingly.
See:
* https://go.dev/doc/effective_go
* https://github.com/golang/go/wiki/CodeReviewComments
* https://github.com/smallnest/go-best-practices
* https://github.com/golang-standards/project-layout
* http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in-go-golang/
Note some of these have overlap. | priority | clean up format application code there are some general best practices formatting recommened shoud probably check that and change the code accordingly see note some of these have overlap | 1 |
729,888 | 25,148,937,299 | IssuesEvent | 2022-11-10 08:29:10 | Automattic/newspack-popups | https://api.github.com/repos/Automattic/newspack-popups | closed | Campaigns + no AMP cause Web Stories block not to work | bug released released on @alpha [Priority] Low | When Google's [Web Stories](https://wordpress.org/plugins/web-stories/) block is embedded on a site with AMP disabled and Campaigns running, clicking on the different stories loads a black screen, but not the story itself.
If you either enable AMP on the page the block is embedded in, or turn off campaigns on that specific page, the stories will load as expected.
When they're not working, you get this error in the Console:
`Uncaught Error: Render timeout waiting for service amp-story-render to be ready.`
Originally reported by a publisher, but I was able to recreate on a pretty vanilla Newspack site (just running the theme, Web Stories and Campaigns plugins).
## Steps to reproduce
1. Install the [Web Stories](https://wordpress.org/plugins/web-stories/) plugin and create one story
2. Enable the Campaigns plugin and disable AMP
3. Add the Web stories block to a page
4. Click on one of the stories
5. Get just a black screen
If you disable Campaigns on that page, or enable AMP, when you click on a story, it will open in a full-screen popup.
I'm guessing this has something to do with the partial-AMP state that Campaigns + no AMP creates on a site; I'm not sure if this is the correct place to file this, so please let me know if it should be moved! | 1.0 | Campaigns + no AMP cause Web Stories block not to work - When Google's [Web Stories](https://wordpress.org/plugins/web-stories/) block is embedded on a site with AMP disabled and Campaigns running, clicking on the different stories loads a black screen, but not the story itself.
If you either enable AMP on the page the block is embedded in, or turn off campaigns on that specific page, the stories will load as expected.
When they're not working, you get this error in the Console:
`Uncaught Error: Render timeout waiting for service amp-story-render to be ready.`
Originally reported by a publisher, but I was able to recreate on a pretty vanilla Newspack site (just running the theme, Web Stories and Campaigns plugins).
## Steps to reproduce
1. Install the [Web Stories](https://wordpress.org/plugins/web-stories/) plugin and create one story
2. Enable the Campaigns plugin and disable AMP
3. Add the Web stories block to a page
4. Click on one of the stories
5. Get just a black screen
If you disable Campaigns on that page, or enable AMP, when you click on a story, it will open in a full-screen popup.
I'm guessing this has something to do with the partial-AMP state that Campaigns + no AMP creates on a site; I'm not sure if this is the correct place to file this, so please let me know if it should be moved! | priority | campaigns no amp cause web stories block not to work when google s block is embedded on a site with amp disabled and campaigns running clicking on the different stories loads a black screen but not the story itself if you either enable amp on the page the block is embedded in or turn off campaigns on that specific page the stories will load as expected when they re not working you get this error in the console uncaught error render timeout waiting for service amp story render to be ready originally reported by a publisher but i was able to recreate on a pretty vanilla newspack site just running the theme web stories and campaigns plugins steps to reproduce install the plugin and create one story enable the campaigns plugin and disable amp add the web stories block to a page click on one of the stories get just a black screen if you disable campaigns on that page or enable amp when you click on a story it will open in a full screen popup i m guessing this has something to do with the partial amp state that campaigns no amp creates on a site i m not sure if this is the correct place to file this so please let me know if it should be moved | 1 |
796,062 | 28,098,194,486 | IssuesEvent | 2023-03-30 17:19:45 | Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | https://api.github.com/repos/Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | opened | Playable unlanded characters | suggestion :question: priority low :grey_exclamation: | <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Describe your suggestion in full detail below:**
Would be fun to play unlanded characters that have importance to the story. Like playing Jaina before the start date where she is already in theramore. Would even be cool to add in more of a class system that gives bonuses(kinda like the hunter trait, rename blade master to warrior etc). Make the unlanded characters work like how rags to riches worked for ck2
| 1.0 | Playable unlanded characters - <!--
**DO NOT REMOVE PRE-EXISTING LINES**
------------------------------------------------------------------------------------------------------------
-->
**Describe your suggestion in full detail below:**
Would be fun to play unlanded characters that have importance to the story. Like playing Jaina before the start date where she is already in theramore. Would even be cool to add in more of a class system that gives bonuses(kinda like the hunter trait, rename blade master to warrior etc). Make the unlanded characters work like how rags to riches worked for ck2
| priority | playable unlanded characters do not remove pre existing lines describe your suggestion in full detail below would be fun to play unlanded characters that have importance to the story like playing jaina before the start date where she is already in theramore would even be cool to add in more of a class system that gives bonuses kinda like the hunter trait rename blade master to warrior etc make the unlanded characters work like how rags to riches worked for | 1 |
117,840 | 4,728,388,733 | IssuesEvent | 2016-10-18 15:49:53 | CS2103AUG2016-W13-C3/main | https://api.github.com/repos/CS2103AUG2016-W13-C3/main | closed | As a user with many events, I have multiple time slots for events | priority.low type.story | So that I can input for events which span multiple days | 1.0 | As a user with many events, I have multiple time slots for events - So that I can input for events which span multiple days | priority | as a user with many events i have multiple time slots for events so that i can input for events which span multiple days | 1 |
442,541 | 12,747,057,291 | IssuesEvent | 2020-06-26 17:08:08 | RespiraWorks/VentilatorSoftware | https://api.github.com/repos/RespiraWorks/VentilatorSoftware | closed | Less noisy/repetitive way of specifying integration tests in build system | Bug Low Priority Needs help | The current way we're specifying integration tests in the build system is leading to noise and repetition.
I should say upfront, the way we're doing it seems to me very natural in PlatformIO, and I'm not sure how else we *should* do it. So this isn't criticism of the authors of the code; it's a problem with PlatformIO. But having said that, I still think we need to figure out something to do about it.
- It's leading to noise because when you run `pio test -e native`, it prints every environment that it skipped:
```
$ pio test -e native
checksum stm32 IGNORED
checksum stm32-test IGNORED
checksum stm32-dma-test IGNORED
checksum int-test-blower IGNORED
checksum int-test-solenoid IGNORED
checksum int-test-stepper IGNORED
checksum int-test-pinch-valve IGNORED
checksum native PASSED 00:00:02.539
circ_buff stm32 IGNORED
circ_buff stm32-test IGNORED
circ_buff stm32-dma-test IGNORED
circ_buff int-test-blower IGNORED
circ_buff int-test-solenoid IGNORED
circ_buff int-test-stepper IGNORED
circ_buff int-test-pinch-valve IGNORED
circ_buff native IGNORED
[many lines snipped]
```
As you can see above, we have an n^2 problem of num_integration_tests * num_unit_tests, that's going to become bad very quickly.
- It's leading to repetition in the `platformio.ini` file. If and when we want to change flags in a way that affects integration tests, there is a high likelihood we're not going to do so in a consistent way, and ultimately that will lead to sadness.
cc @martukas | 1.0 | Less noisy/repetitive way of specifying integration tests in build system - The current way we're specifying integration tests in the build system is leading to noise and repetition.
I should say upfront, the way we're doing it seems to me very natural in PlatformIO, and I'm not sure how else we *should* do it. So this isn't criticism of the authors of the code; it's a problem with PlatformIO. But having said that, I still think we need to figure out something to do about it.
- It's leading to noise because when you run `pio test -e native`, it prints every environment that it skipped:
```
$ pio test -e native
checksum stm32 IGNORED
checksum stm32-test IGNORED
checksum stm32-dma-test IGNORED
checksum int-test-blower IGNORED
checksum int-test-solenoid IGNORED
checksum int-test-stepper IGNORED
checksum int-test-pinch-valve IGNORED
checksum native PASSED 00:00:02.539
circ_buff stm32 IGNORED
circ_buff stm32-test IGNORED
circ_buff stm32-dma-test IGNORED
circ_buff int-test-blower IGNORED
circ_buff int-test-solenoid IGNORED
circ_buff int-test-stepper IGNORED
circ_buff int-test-pinch-valve IGNORED
circ_buff native IGNORED
[many lines snipped]
```
As you can see above, we have an n^2 problem of num_integration_tests * num_unit_tests, that's going to become bad very quickly.
- It's leading to repetition in the `platformio.ini` file. If and when we want to change flags in a way that affects integration tests, there is a high likelihood we're not going to do so in a consistent way, and ultimately that will lead to sadness.
cc @martukas | priority | less noisy repetitive way of specifying integration tests in build system the current way we re specifying integration tests in the build system is leading to noise and repetition i should say upfront the way we re doing it seems to me very natural in platformio and i m not sure how else we should do it so this isn t criticism of the authors of the code it s a problem with platformio but having said that i still think we need to figure out something to do about it it s leading to noise because when you run pio test e native it prints every environment that it skipped pio test e native checksum ignored checksum test ignored checksum dma test ignored checksum int test blower ignored checksum int test solenoid ignored checksum int test stepper ignored checksum int test pinch valve ignored checksum native passed circ buff ignored circ buff test ignored circ buff dma test ignored circ buff int test blower ignored circ buff int test solenoid ignored circ buff int test stepper ignored circ buff int test pinch valve ignored circ buff native ignored as you can see above we have an n problem of num integration tests num unit tests that s going to become bad very quickly it s leading to repetition in the platformio ini file if and when we want to change flags in a way that affects integration tests there is a high likelihood we re not going to do so in a consistent way and ultimately that will lead to sadness cc martukas | 1 |
500,903 | 14,516,955,770 | IssuesEvent | 2020-12-13 17:47:10 | DelgadoTrueba/registro-horario-sc | https://api.github.com/repos/DelgadoTrueba/registro-horario-sc | closed | Configurar Guía de estilos Solidity y Análisis Estático | points: 1 priority: low type: ci | # prettier-plugin-solidity
__INSTALACIÓN__
* npm install --save-dev prettier prettier-plugin-solidity
* crear fichero
```json
{
"overrides": [
{
"files": "*.sol",
"options": {
"printWidth": 80,
"tabWidth": 4,
"useTabs": false,
"singleQuote": false,
"bracketSpacing": false,
"explicitTypes": "always"
}
}
]
}
```
* package.json
```
"style-check": "prettier --check ./contracts/**/*.sol",
"style-fix": "prettier --write ./contracts/**/*.sol"
```
# solhint
https://github.com/protofire/solhint
https://marketplace.visualstudio.com/items?itemName=JuanBlanco.solidity
__INSTALACIÓN__
* npm install --save-dev solhint
* npx solhint --init
```
{
"extends": "solhint:recommended",
"plugins": [],
"rules": {
"avoid-suicide": "error",
"avoid-sha3": "warn",
"compiler-version": "off"
}
}
```
* package.json
```
"linter": "npx solhint ./contracts/**/*.sol"
``` | 1.0 | Configurar Guía de estilos Solidity y Análisis Estático - # prettier-plugin-solidity
__INSTALACIÓN__
* npm install --save-dev prettier prettier-plugin-solidity
* crear fichero
```json
{
"overrides": [
{
"files": "*.sol",
"options": {
"printWidth": 80,
"tabWidth": 4,
"useTabs": false,
"singleQuote": false,
"bracketSpacing": false,
"explicitTypes": "always"
}
}
]
}
```
* package.json
```
"style-check": "prettier --check ./contracts/**/*.sol",
"style-fix": "prettier --write ./contracts/**/*.sol"
```
# solhint
https://github.com/protofire/solhint
https://marketplace.visualstudio.com/items?itemName=JuanBlanco.solidity
__INSTALACIÓN__
* npm install --save-dev solhint
* npx solhint --init
```
{
"extends": "solhint:recommended",
"plugins": [],
"rules": {
"avoid-suicide": "error",
"avoid-sha3": "warn",
"compiler-version": "off"
}
}
```
* package.json
```
"linter": "npx solhint ./contracts/**/*.sol"
``` | priority | configurar guía de estilos solidity y análisis estático prettier plugin solidity instalación npm install save dev prettier prettier plugin solidity crear fichero json overrides files sol options printwidth tabwidth usetabs false singlequote false bracketspacing false explicittypes always package json style check prettier check contracts sol style fix prettier write contracts sol solhint instalación npm install save dev solhint npx solhint init extends solhint recommended plugins rules avoid suicide error avoid warn compiler version off package json linter npx solhint contracts sol | 1 |
769,521 | 27,010,160,071 | IssuesEvent | 2023-02-10 14:49:33 | adrian-jonsson-sjoedin/IV1201-Project | https://api.github.com/repos/adrian-jonsson-sjoedin/IV1201-Project | opened | Account page | low priority | Account page with settings, ability to change password, add additional information or delete account. | 1.0 | Account page - Account page with settings, ability to change password, add additional information or delete account. | priority | account page account page with settings ability to change password add additional information or delete account | 1 |
662,354 | 22,113,826,456 | IssuesEvent | 2022-06-02 00:29:16 | az-digital/az_quickstart | https://api.github.com/repos/az-digital/az_quickstart | opened | Change email addresses in demo content from @email.arizona.edu to @arizona.edu | bug low priority | ## Problem/Motivation
Now that [@arizona.edu is the primary domain name for email addresses at the university](https://it.arizona.edu/email-projects-2020-faqs), email addresses in the Quickstart Demo Content module that end in @email.arizona.edu should be updated accordingly. Making the email addresses shorter in this way will also benefit the card display of AZ Person nodes, reducing the likelihood that an email address will be truncated with ellipses (or overflow to the next line).
This issue is a follow-up from #1328.
### Describe the bug
AZ Person nodes in the demo content use emails that end in @email.arizona.edu.
### To Reproduce
Steps to reproduce the behavior:
Go to either directory page from the demo content and observe that all the email addresses end with @email.arizona.edu.
## Proposed resolution
Change the email addresses in the Quickstart Demo Content module to end with @arizona.edu instead of @email.arizona.edu.
### Expected behavior
Email addresses in the demo content will now end with @arizona.edu.
| 1.0 | Change email addresses in demo content from @email.arizona.edu to @arizona.edu - ## Problem/Motivation
Now that [@arizona.edu is the primary domain name for email addresses at the university](https://it.arizona.edu/email-projects-2020-faqs), email addresses in the Quickstart Demo Content module that end in @email.arizona.edu should be updated accordingly. Making the email addresses shorter in this way will also benefit the card display of AZ Person nodes, reducing the likelihood that an email address will be truncated with ellipses (or overflow to the next line).
This issue is a follow-up from #1328.
### Describe the bug
AZ Person nodes in the demo content use emails that end in @email.arizona.edu.
### To Reproduce
Steps to reproduce the behavior:
Go to either directory page from the demo content and observe that all the email addresses end with @email.arizona.edu.
## Proposed resolution
Change the email addresses in the Quickstart Demo Content module to end with @arizona.edu instead of @email.arizona.edu.
### Expected behavior
Email addresses in the demo content will now end with @arizona.edu.
| priority | change email addresses in demo content from email arizona edu to arizona edu problem motivation now that email addresses in the quickstart demo content module that end in email arizona edu should be updated accordingly making the email addresses shorter in this way will also benefit the card display of az person nodes reducing the likelihood that an email address will be truncated with ellipses or overflow to the next line this issue is a follow up from describe the bug az person nodes in the demo content use emails that end in email arizona edu to reproduce steps to reproduce the behavior go to either directory page from the demo content and observe that all the email addresses end with email arizona edu proposed resolution change the email addresses in the quickstart demo content module to end with arizona edu instead of email arizona edu expected behavior email addresses in the demo content will now end with arizona edu | 1 |
81,472 | 3,591,371,425 | IssuesEvent | 2016-02-01 11:25:19 | Project-M-CC/Project-M-CC | https://api.github.com/repos/Project-M-CC/Project-M-CC | reopened | Sonic Heroes Metal | Costumes Knuckles Low Priority Model/Animation | So PM added Peach's offical metal form. I want to gauge how much we would be in approval of these official metal forms, as I can implement them.
So basically, metal box turns Sonic and Knuckles into this, from Sonic Heroes. | 1.0 | Sonic Heroes Metal - So PM added Peach's offical metal form. I want to gauge how much we would be in approval of these official metal forms, as I can implement them.
So basically, metal box turns Sonic and Knuckles into this, from Sonic Heroes. | priority | sonic heroes metal so pm added peach s offical metal form i want to gauge how much we would be in approval of these official metal forms as i can implement them so basically metal box turns sonic and knuckles into this from sonic heroes | 1 |
176,274 | 6,557,983,842 | IssuesEvent | 2017-09-06 19:32:48 | ponylang/ponyc | https://api.github.com/repos/ponylang/ponyc | closed | Character literal quirks | bug: 3 - ready for work priority: 1 - low | Character literals should only support one character in them except for escape sequences:
```pony
//allowed
let escaped = '\xFF'
// forbidden
let multiple_chars = 'FF'
```
The current logic for creating an Int from multiple characters is to concatenate the least significant Bytes into the target type Integer/Float.
Unicode characters Always seem to return 0.
The empty character literal ``''`` also results in 0 although an empty character literal doesnt make sense and should be considered invalid syntax (imo).
See: https://playground.ponylang.org/?gist=3aedc58eadfca46c5c0133fa2af4a703
```pony
actor Main
new create(env : Env) =>
let wat_chars: Array[U64] = [as U64:
'' // 0
'AAA' // 0b010000010100000101000001
'\n\0\0' // 10 * (2^16)
'🎠' // 0
]
for wat_char in wat_chars.values() do
env.out.print(wat_char.string())
end
```
Does anybody have a valid use case for multi-character character literals? | 1.0 | Character literal quirks - Character literals should only support one character in them except for escape sequences:
```pony
//allowed
let escaped = '\xFF'
// forbidden
let multiple_chars = 'FF'
```
The current logic for creating an Int from multiple characters is to concatenate the least significant Bytes into the target type Integer/Float.
Unicode characters Always seem to return 0.
The empty character literal ``''`` also results in 0 although an empty character literal doesnt make sense and should be considered invalid syntax (imo).
See: https://playground.ponylang.org/?gist=3aedc58eadfca46c5c0133fa2af4a703
```pony
actor Main
new create(env : Env) =>
let wat_chars: Array[U64] = [as U64:
'' // 0
'AAA' // 0b010000010100000101000001
'\n\0\0' // 10 * (2^16)
'🎠' // 0
]
for wat_char in wat_chars.values() do
env.out.print(wat_char.string())
end
```
Does anybody have a valid use case for multi-character character literals? | priority | character literal quirks character literals should only support one character in them except for escape sequences pony allowed let escaped xff forbidden let multiple chars ff the current logic for creating an int from multiple characters is to concatenate the least significant bytes into the target type integer float unicode characters always seem to return the empty character literal also results in although an empty character literal doesnt make sense and should be considered invalid syntax imo see pony actor main new create env env let wat chars array as aaa n 🎠 for wat char in wat chars values do env out print wat char string end does anybody have a valid use case for multi character character literals | 1 |
378,427 | 11,202,138,148 | IssuesEvent | 2020-01-04 09:58:20 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | Site incompatibility with Shields on: https://www.shortoftheweek.com/ | feature/shields/webcompat feature/video priority/P3 workaround/allow-all-cookies | <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
Site incompatibility with Shields on: https://www.shortoftheweek.com/
Movies on https://www.shortoftheweek.com/ do not show. They do play, but are only visible when double clicking on the area where the movie ought to be so it becomes full screen.
## Steps to Reproduce
1. Go to https://www.shortoftheweek.com/2019/05/10/the-unconditional/
2. There is a 'rotating square' where the play button should be.
3. Double click to enter full screen.
## Actual result:
Brave window:
Double clicking shows movie in full screen.
## Expected result:
Chrome window:
Pressing the play button starts the movie.
## Reproduces how often:
always
## Brave version (brave://version info)
Brave | 0.65.88 Chromium: 74.0.3729.131 (Official Build) beta(64-bit)
Revision | 518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954}
OS | Linux
## Version/Channel Information:
- Can you reproduce this issue with the current release? Don't know
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Don't know
- Can you reproduce this issue with the nightly channel? Don't know
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? Yes, thanks!
- Does the issue resolve itself when disabling Brave Rewards? No
- Is the issue reproducible on the latest version of Chrome? No (74.0.3729.131)
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
| 1.0 | Site incompatibility with Shields on: https://www.shortoftheweek.com/ - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
Site incompatibility with Shields on: https://www.shortoftheweek.com/
Movies on https://www.shortoftheweek.com/ do not show. They do play, but are only visible when double clicking on the area where the movie ought to be so it becomes full screen.
## Steps to Reproduce
1. Go to https://www.shortoftheweek.com/2019/05/10/the-unconditional/
2. There is a 'rotating square' where the play button should be.
3. Double click to enter full screen.
## Actual result:
Brave window:
Double clicking shows movie in full screen.
## Expected result:
Chrome window:
Pressing the play button starts the movie.
## Reproduces how often:
always
## Brave version (brave://version info)
Brave | 0.65.88 Chromium: 74.0.3729.131 (Official Build) beta(64-bit)
Revision | 518a41c1fa7ce1c8bb5e22346e82e42b4d76a96f-refs/branch-heads/3729@{#954}
OS | Linux
## Version/Channel Information:
- Can you reproduce this issue with the current release? Don't know
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Don't know
- Can you reproduce this issue with the nightly channel? Don't know
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? Yes, thanks!
- Does the issue resolve itself when disabling Brave Rewards? No
- Is the issue reproducible on the latest version of Chrome? No (74.0.3729.131)
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
| priority | site incompatibility with shields on have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description site incompatibility with shields on movies on do not show they do play but are only visible when double clicking on the area where the movie ought to be so it becomes full screen steps to reproduce go to there is a rotating square where the play button should be double click to enter full screen actual result brave window double clicking shows movie in full screen expected result chrome window pressing the play button starts the movie reproduces how often always brave version brave version info brave chromium official build beta bit revision refs branch heads os linux version channel information can you reproduce this issue with the current release don t know can you reproduce this issue with the beta channel yes can you reproduce this issue with the dev channel don t know can you reproduce this issue with the nightly channel don t know other additional information does the issue resolve itself when disabling brave shields yes thanks does the issue resolve itself when disabling brave rewards no is the issue reproducible on the latest version of chrome no miscellaneous information | 1 |
607,576 | 18,786,208,165 | IssuesEvent | 2021-11-08 12:25:12 | jiy00nn/deu_car | https://api.github.com/repos/jiy00nn/deu_car | closed | SFR#201 맵 경로 탐색 | enhancement Priority: Low | ## SFR-200 지도 작성 기능 ##
- 요구사항 ID : SFR-201
- 제목 : 제공된 맵의 경로를 탐색할 수 있다.
- 설명 : 주행 로봇으로서 경로 탐색 기능이 필요하다. 왜냐하면 경로를 알아야 주행이 가능하기 때문이다.
- 추정치 (예상 소요 기간) : 3일 | 1.0 | SFR#201 맵 경로 탐색 - ## SFR-200 지도 작성 기능 ##
- 요구사항 ID : SFR-201
- 제목 : 제공된 맵의 경로를 탐색할 수 있다.
- 설명 : 주행 로봇으로서 경로 탐색 기능이 필요하다. 왜냐하면 경로를 알아야 주행이 가능하기 때문이다.
- 추정치 (예상 소요 기간) : 3일 | priority | sfr 맵 경로 탐색 sfr 지도 작성 기능 요구사항 id sfr 제목 제공된 맵의 경로를 탐색할 수 있다 설명 주행 로봇으로서 경로 탐색 기능이 필요하다 왜냐하면 경로를 알아야 주행이 가능하기 때문이다 추정치 예상 소요 기간 | 1 |
800,794 | 28,432,333,705 | IssuesEvent | 2023-04-15 00:07:19 | sct/overseerr | https://api.github.com/repos/sct/overseerr | reopened | Ability to configure an outbound web proxy server | topic:backend type:enhancement priority:low stale | #### Description
Ability to configure an outbound web proxy server
#### Desired Behavior
Be able to use the outbound proxy server to request image or metadata
#### Additional Context
| 1.0 | Ability to configure an outbound web proxy server - #### Description
Ability to configure an outbound web proxy server
#### Desired Behavior
Be able to use the outbound proxy server to request image or metadata
#### Additional Context
| priority | ability to configure an outbound web proxy server description ability to configure an outbound web proxy server desired behavior be able to use the outbound proxy server to request image or metadata additional context | 1 |
228,425 | 7,550,765,402 | IssuesEvent | 2018-04-18 17:56:46 | JacksonCollege/jc-theme-2015 | https://api.github.com/repos/JacksonCollege/jc-theme-2015 | closed | Additional Fields for staff directory | enhancement lower priority | Could you add a few more optional fields for the staff directory? If you could add Office Location and Office Hours that would be great! For the office location, I would like to not have the words "Office Location" show up, just the field contents like the others. But for Office Hours if we could have a drop down like the "more info" that is currently there that would be great!. and if there could be sub fields for the semester and days of the week? (Monday: Tuesday: Wednesday: ) I think that look cleaner and be easier to input.
And if both of these fields could be optional that would be great too. I'm adding the office hours just for faculty so it will just apply to them (right now we are linking to pdf's of their office hours and they look awful!)
Also, is there a way to add an additional optional misc field? There are a few of our faculty that want to display the link to their Youtube channels and right now I have them tacked on to their phone field and it looks bad.
This isn't a big rush, I would like to get the accessibility errors taken care of first if we could - just thought I would track this while I was thinking about it.
Thanks! | 1.0 | Additional Fields for staff directory - Could you add a few more optional fields for the staff directory? If you could add Office Location and Office Hours that would be great! For the office location, I would like to not have the words "Office Location" show up, just the field contents like the others. But for Office Hours if we could have a drop down like the "more info" that is currently there that would be great!. and if there could be sub fields for the semester and days of the week? (Monday: Tuesday: Wednesday: ) I think that look cleaner and be easier to input.
And if both of these fields could be optional that would be great too. I'm adding the office hours just for faculty so it will just apply to them (right now we are linking to pdf's of their office hours and they look awful!)
Also, is there a way to add an additional optional misc field? There are a few of our faculty that want to display the link to their Youtube channels and right now I have them tacked on to their phone field and it looks bad.
This isn't a big rush, I would like to get the accessibility errors taken care of first if we could - just thought I would track this while I was thinking about it.
Thanks! | priority | additional fields for staff directory could you add a few more optional fields for the staff directory if you could add office location and office hours that would be great for the office location i would like to not have the words office location show up just the field contents like the others but for office hours if we could have a drop down like the more info that is currently there that would be great and if there could be sub fields for the semester and days of the week monday tuesday wednesday i think that look cleaner and be easier to input and if both of these fields could be optional that would be great too i m adding the office hours just for faculty so it will just apply to them right now we are linking to pdf s of their office hours and they look awful also is there a way to add an additional optional misc field there are a few of our faculty that want to display the link to their youtube channels and right now i have them tacked on to their phone field and it looks bad this isn t a big rush i would like to get the accessibility errors taken care of first if we could just thought i would track this while i was thinking about it thanks | 1 |
715,720 | 24,607,624,393 | IssuesEvent | 2022-10-14 17:49:37 | MAKENTNU/web | https://api.github.com/repos/MAKENTNU/web | opened | Forms with rich text fields are unmarked as dirty when clicking another field | bug priority: 5 - low | ### Steps to reproduce
1. Visit a page with both a rich text field and a field of another type; https://makentnu.dev/en/contentbox/7/edit/ for this example
2. Add a character anywhere inside the "Content" field
3. Click the label of the "Title" field (i.e. click on the text that says "Title"), so that the "Title" text input is focused
4. Reload the page
### Expected results
The page should not reload, but instead display a browser-native prompt, asking if the user actually wants to reload/leave the page.
---
This issue seems to be most likely caused by a bug in [the `jquery.dirty` library](https://github.com/simon-reynolds/jquery.dirty). | 1.0 | Forms with rich text fields are unmarked as dirty when clicking another field - ### Steps to reproduce
1. Visit a page with both a rich text field and a field of another type; https://makentnu.dev/en/contentbox/7/edit/ for this example
2. Add a character anywhere inside the "Content" field
3. Click the label of the "Title" field (i.e. click on the text that says "Title"), so that the "Title" text input is focused
4. Reload the page
### Expected results
The page should not reload, but instead display a browser-native prompt, asking if the user actually wants to reload/leave the page.
---
This issue seems to be most likely caused by a bug in [the `jquery.dirty` library](https://github.com/simon-reynolds/jquery.dirty). | priority | forms with rich text fields are unmarked as dirty when clicking another field steps to reproduce visit a page with both a rich text field and a field of another type for this example add a character anywhere inside the content field click the label of the title field i e click on the text that says title so that the title text input is focused reload the page expected results the page should not reload but instead display a browser native prompt asking if the user actually wants to reload leave the page this issue seems to be most likely caused by a bug in | 1 |
542,104 | 15,838,888,286 | IssuesEvent | 2021-04-06 23:29:35 | returntocorp/semgrep | https://api.github.com/repos/returntocorp/semgrep | closed | typescript parsing bug: 'public abstract async methodName()' | bug external-user lang:typescript priority:low | https://semgrep.dev/s/Bkl2
Verified to compile correctly in TS4.0, although editors complain about this. | 1.0 | typescript parsing bug: 'public abstract async methodName()' - https://semgrep.dev/s/Bkl2
Verified to compile correctly in TS4.0, although editors complain about this. | priority | typescript parsing bug public abstract async methodname verified to compile correctly in although editors complain about this | 1 |
309,268 | 9,466,087,214 | IssuesEvent | 2019-04-18 02:45:06 | LambdaInnovation/AcademyCraft | https://api.github.com/repos/LambdaInnovation/AcademyCraft | closed | [Bug] 单人游戏基础能力学习机第一次获得能力后游戏崩溃 | bug priority: low | **Describe the bug**
使用能源桥链接IC线缆并用改良能量节点链接，在使用基础能力学习机输入learn，待进度条走完后游戏崩溃
**Desktop (please complete the following information):**
- 系统：Win10
- MC：Minecraft 1.7.10 Forge 1.7.10-Forge10.13.4.1614-1.7.10
- Version AcademyCraft-1.0.7 with LambdaLib-1.2.3
部分崩溃日志
-- Head --
Stacktrace:
at java.util.HashMap$HashIterator.nextNode(Unknown Source)
at java.util.HashMap$ValueIterator.next(Unknown Source)
at cn.lambdalib.util.datapart.EntityData.tick(EntityData.java:209)
at cn.lambdalib.util.datapart.EntityData.access$000(EntityData.java:34)
at cn.lambdalib.util.datapart.EntityData$EventListener.onLivingUpdate(EntityData.java:223)
at cpw.mods.fml.common.eventhandler.ASMEventHandler_316_EventListener_onLivingUpdate_LivingUpdateEvent.invoke(.dynamic)
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:54)
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:140)
at net.minecraftforge.common.ForgeHooks.onLivingUpdate(ForgeHooks.java:287)
at net.minecraft.entity.EntityLivingBase.func_70071_h_(EntityLivingBase.java:1560)
at net.minecraft.entity.player.EntityPlayer.func_70071_h_(EntityPlayer.java:288)
at net.minecraft.entity.player.EntityPlayerMP.func_71127_g(EntityPlayerMP.java:295)
-- Player being ticked --
Details:
Entity Type: null (net.minecraft.entity.player.EntityPlayerMP)
Entity ID: 2707
Entity Name: _Shigure
Entity's Exact location: -331.24, 69.00, 200.96
Entity's Block location: World: (-332,69,200), Chunk: (at 4,4,8 in -21,12; contains blocks -336,0,192 to -321,255,207), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Entity's Momentum: 0.00, -0.08, 0.00
Stacktrace:
at net.minecraft.network.NetHandlerPlayServer.func_147347_a(NetHandlerPlayServer.java:303)
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(SourceFile:137)
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(SourceFile:8)
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:212)
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:165)
-- Ticking connection --
Details:
Connection: net.minecraft.network.NetworkManager@549abb13
Stacktrace:
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:659)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:547)
at net.minecraft.server.integrated.IntegratedServer.func_71217_p(IntegratedServer.java:186)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:396)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)
| 1.0 | [Bug] 单人游戏基础能力学习机第一次获得能力后游戏崩溃 - **Describe the bug**
使用能源桥链接IC线缆并用改良能量节点链接，在使用基础能力学习机输入learn，待进度条走完后游戏崩溃
**Desktop (please complete the following information):**
- 系统：Win10
- MC：Minecraft 1.7.10 Forge 1.7.10-Forge10.13.4.1614-1.7.10
- Version AcademyCraft-1.0.7 with LambdaLib-1.2.3
部分崩溃日志
-- Head --
Stacktrace:
at java.util.HashMap$HashIterator.nextNode(Unknown Source)
at java.util.HashMap$ValueIterator.next(Unknown Source)
at cn.lambdalib.util.datapart.EntityData.tick(EntityData.java:209)
at cn.lambdalib.util.datapart.EntityData.access$000(EntityData.java:34)
at cn.lambdalib.util.datapart.EntityData$EventListener.onLivingUpdate(EntityData.java:223)
at cpw.mods.fml.common.eventhandler.ASMEventHandler_316_EventListener_onLivingUpdate_LivingUpdateEvent.invoke(.dynamic)
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:54)
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:140)
at net.minecraftforge.common.ForgeHooks.onLivingUpdate(ForgeHooks.java:287)
at net.minecraft.entity.EntityLivingBase.func_70071_h_(EntityLivingBase.java:1560)
at net.minecraft.entity.player.EntityPlayer.func_70071_h_(EntityPlayer.java:288)
at net.minecraft.entity.player.EntityPlayerMP.func_71127_g(EntityPlayerMP.java:295)
-- Player being ticked --
Details:
Entity Type: null (net.minecraft.entity.player.EntityPlayerMP)
Entity ID: 2707
Entity Name: _Shigure
Entity's Exact location: -331.24, 69.00, 200.96
Entity's Block location: World: (-332,69,200), Chunk: (at 4,4,8 in -21,12; contains blocks -336,0,192 to -321,255,207), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Entity's Momentum: 0.00, -0.08, 0.00
Stacktrace:
at net.minecraft.network.NetHandlerPlayServer.func_147347_a(NetHandlerPlayServer.java:303)
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(SourceFile:137)
at net.minecraft.network.play.client.C03PacketPlayer.func_148833_a(SourceFile:8)
at net.minecraft.network.NetworkManager.func_74428_b(NetworkManager.java:212)
at net.minecraft.network.NetworkSystem.func_151269_c(NetworkSystem.java:165)
-- Ticking connection --
Details:
Connection: net.minecraft.network.NetworkManager@549abb13
Stacktrace:
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:659)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:547)
at net.minecraft.server.integrated.IntegratedServer.func_71217_p(IntegratedServer.java:186)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:396)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)
| priority | 单人游戏基础能力学习机第一次获得能力后游戏崩溃 describe the bug 使用能源桥链接ic线缆并用改良能量节点链接，在使用基础能力学习机输入learn，待进度条走完后游戏崩溃 desktop please complete the following information 系统： mc：minecraft forge version academycraft with lambdalib 部分崩溃日志 head stacktrace at java util hashmap hashiterator nextnode unknown source at java util hashmap valueiterator next unknown source at cn lambdalib util datapart entitydata tick entitydata java at cn lambdalib util datapart entitydata access entitydata java at cn lambdalib util datapart entitydata eventlistener onlivingupdate entitydata java at cpw mods fml common eventhandler asmeventhandler eventlistener onlivingupdate livingupdateevent invoke dynamic at cpw mods fml common eventhandler asmeventhandler invoke asmeventhandler java at cpw mods fml common eventhandler eventbus post eventbus java at net minecraftforge common forgehooks onlivingupdate forgehooks java at net minecraft entity entitylivingbase func h entitylivingbase java at net minecraft entity player entityplayer func h entityplayer java at net minecraft entity player entityplayermp func g entityplayermp java player being ticked details entity type null net minecraft entity player entityplayermp entity id entity name shigure entity s exact location entity s block location world chunk at in contains blocks to region contains chunks to blocks to entity s momentum stacktrace at net minecraft network nethandlerplayserver func a nethandlerplayserver java at net minecraft network play client func a sourcefile at net minecraft network play client func a sourcefile at net minecraft network networkmanager func b networkmanager java at net minecraft network networksystem func c networksystem java ticking connection details connection net minecraft network networkmanager stacktrace at net minecraft server minecraftserver func q minecraftserver java at net minecraft server minecraftserver func p minecraftserver java at net minecraft server integrated integratedserver func p integratedserver java at net minecraft server minecraftserver run minecraftserver java at net minecraft server minecraftserver run minecraftserver java | 1 |
113,506 | 4,560,832,832 | IssuesEvent | 2016-09-14 09:27:56 | Starbugstone/ADListing | https://api.github.com/repos/Starbugstone/ADListing | closed | check on IE for accent errors between JS and PHP | bug Priority:Low Priority:Medium | The check for Group and user returs an error with accents.
Check that out and also test for other errors wth ajax calls.
Probably be wize while debugging to check other main navigators and prehaps some less well known just in case.
Remember this is a lesser case so no major redo's | 2.0 | check on IE for accent errors between JS and PHP - The check for Group and user returs an error with accents.
Check that out and also test for other errors wth ajax calls.
Probably be wize while debugging to check other main navigators and prehaps some less well known just in case.
Remember this is a lesser case so no major redo's | priority | check on ie for accent errors between js and php the check for group and user returs an error with accents check that out and also test for other errors wth ajax calls probably be wize while debugging to check other main navigators and prehaps some less well known just in case remember this is a lesser case so no major redo s | 1 |
175,253 | 6,548,531,201 | IssuesEvent | 2017-09-04 23:00:06 | enforcer574/smashclub | https://api.github.com/repos/enforcer574/smashclub | opened | Contact info field on guest RSVP form overflows the form box | Bug Priority: P4 - Low | On mobile, the guest RSVP form for events shows the Contact Info field being larger than the enclosing form box. | 1.0 | Contact info field on guest RSVP form overflows the form box - On mobile, the guest RSVP form for events shows the Contact Info field being larger than the enclosing form box. | priority | contact info field on guest rsvp form overflows the form box on mobile the guest rsvp form for events shows the contact info field being larger than the enclosing form box | 1 |
613,859 | 19,100,392,912 | IssuesEvent | 2021-11-29 21:44:12 | Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | https://api.github.com/repos/Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth-2 | opened | Limit mercenaries for cultures with certain religions | suggestion :question: priority low :grey_exclamation: | - Using religious doctrines we should limit mercenary companies for the cultures that have certain religions | 1.0 | Limit mercenaries for cultures with certain religions - - Using religious doctrines we should limit mercenary companies for the cultures that have certain religions | priority | limit mercenaries for cultures with certain religions using religious doctrines we should limit mercenary companies for the cultures that have certain religions | 1 |
369,925 | 10,920,030,801 | IssuesEvent | 2019-11-21 20:19:58 | KrzysztofSzewczyk/asmbf | https://api.github.com/repos/KrzysztofSzewczyk/asmbf | closed | On-memory operations | complexity: medium enhancement priority: low |
```
rcl r1, r2
inc r1
sto r2, r1
```
=>
```
ime r2
```
etc...
| 1.0 | On-memory operations -
```
rcl r1, r2
inc r1
sto r2, r1
```
=>
```
ime r2
```
etc...
| priority | on memory operations rcl inc sto ime etc | 1 |
820,056 | 30,758,871,121 | IssuesEvent | 2023-07-29 12:32:26 | chaotic-aur/packages | https://api.github.com/repos/chaotic-aur/packages | closed | [Request] protonmail-bridge-nogui | request:new-pkg priority:low | ### Package:
[protonmail-bridge-nogui](https://aur.archlinux.org/packages/protonmail-bridge-nogui)
### Purpose:
A bridge that allows using paid proton mail account with mail clients like thunderbird and outlook, built with 'nogui' option. Daemon included.
### Benefits:
It's built without gui, therefore display server isn't needed. Account and mail configuration setup is done in an interactive command-line interface, then bridge.service can be enabled and started.
### Building:
makepkg, yay.
### Copyright:
GPL3
### Expected Interest:
Some
### Already available?
No
### Unique request?
Yes
### Banned package?
No
### More information:
No remote tool is present, therefore bridge.service needs to be stopped in order to open interactive cli. then started again after. | 1.0 | [Request] protonmail-bridge-nogui - ### Package:
[protonmail-bridge-nogui](https://aur.archlinux.org/packages/protonmail-bridge-nogui)
### Purpose:
A bridge that allows using paid proton mail account with mail clients like thunderbird and outlook, built with 'nogui' option. Daemon included.
### Benefits:
It's built without gui, therefore display server isn't needed. Account and mail configuration setup is done in an interactive command-line interface, then bridge.service can be enabled and started.
### Building:
makepkg, yay.
### Copyright:
GPL3
### Expected Interest:
Some
### Already available?
No
### Unique request?
Yes
### Banned package?
No
### More information:
No remote tool is present, therefore bridge.service needs to be stopped in order to open interactive cli. then started again after. | priority | protonmail bridge nogui package purpose a bridge that allows using paid proton mail account with mail clients like thunderbird and outlook built with nogui option daemon included benefits it s built without gui therefore display server isn t needed account and mail configuration setup is done in an interactive command line interface then bridge service can be enabled and started building makepkg yay copyright expected interest some already available no unique request yes banned package no more information no remote tool is present therefore bridge service needs to be stopped in order to open interactive cli then started again after | 1 |
241,858 | 7,834,992,348 | IssuesEvent | 2018-06-16 21:20:31 | bigbluebutton/bigbluebutton | https://api.github.com/repos/bigbluebutton/bigbluebutton | closed | In client ChatModule add a property to config.xml to disable chat input | Chat Enhancement Low Priority | Originally reported on Google Code with ID 1508
```
Add property to ChatModule
<module name="ChatModule" ...
enableInput ="false"
/>
that disables the chat input field for user. The could be used with the dynamic config.xml
to restrict features to a view only mode.
```
Reported by `ffdixon` on 2013-05-17 12:23:34
| 1.0 | In client ChatModule add a property to config.xml to disable chat input - Originally reported on Google Code with ID 1508
```
Add property to ChatModule
<module name="ChatModule" ...
enableInput ="false"
/>
that disables the chat input field for user. The could be used with the dynamic config.xml
to restrict features to a view only mode.
```
Reported by `ffdixon` on 2013-05-17 12:23:34
| priority | in client chatmodule add a property to config xml to disable chat input originally reported on google code with id add property to chatmodule module name chatmodule enableinput false that disables the chat input field for user the could be used with the dynamic config xml to restrict features to a view only mode reported by ffdixon on | 1 |
380,666 | 11,269,480,272 | IssuesEvent | 2020-01-14 09:00:37 | daostack/client | https://api.github.com/repos/daostack/client | closed | way to sort suggestions | Low Priority | Need `ICompetitionSuggestionQueryOptions` to provide a way to sort the suggestions. Need Elon to tell us how. Or maybe they should be returned in a 'random' order, to be fair. | 1.0 | way to sort suggestions - Need `ICompetitionSuggestionQueryOptions` to provide a way to sort the suggestions. Need Elon to tell us how. Or maybe they should be returned in a 'random' order, to be fair. | priority | way to sort suggestions need icompetitionsuggestionqueryoptions to provide a way to sort the suggestions need elon to tell us how or maybe they should be returned in a random order to be fair | 1 |
85,648 | 3,697,220,217 | IssuesEvent | 2016-02-27 14:36:02 | DirtDiglett/Pressure2 | https://api.github.com/repos/DirtDiglett/Pressure2 | closed | Friends list difficult to read as "offline" | bug low priority bug | As on tin. Screenshot for you:
Steam beta. Just go offline to repro, no need to start steam in offline mode. Though, that probably should be checked too. | 1.0 | Friends list difficult to read as "offline" - As on tin. Screenshot for you:
Steam beta. Just go offline to repro, no need to start steam in offline mode. Though, that probably should be checked too. | priority | friends list difficult to read as offline as on tin screenshot for you steam beta just go offline to repro no need to start steam in offline mode though that probably should be checked too | 1 |
191,747 | 6,841,359,656 | IssuesEvent | 2017-11-11 12:36:24 | SvenEV/WinSwag | https://api.github.com/repos/SvenEV/WinSwag | opened | YAML Support | Priority: Low Status: Pending Type: Enhancement | OpenAPI specifications can be in JSON or YAML, but WinSwag only supports JSON at the moment. | 1.0 | YAML Support - OpenAPI specifications can be in JSON or YAML, but WinSwag only supports JSON at the moment. | priority | yaml support openapi specifications can be in json or yaml but winswag only supports json at the moment | 1 |
322,236 | 9,815,117,277 | IssuesEvent | 2019-06-13 11:53:34 | mini2Dx/mini2Dx | https://api.github.com/repos/mini2Dx/mini2Dx | closed | MonoGameGraphics clears the screen when preRender is called | 2.0.x low priority | Everything drawn to the screen using MonoGame APIs before calling MonoGameGraphics.preRender is ignored.
The issue is that if you call MonoGame Texture2D.SetData using an array of transparent pixels as the argument the resulting texture will be black. | 1.0 | MonoGameGraphics clears the screen when preRender is called - Everything drawn to the screen using MonoGame APIs before calling MonoGameGraphics.preRender is ignored.
The issue is that if you call MonoGame Texture2D.SetData using an array of transparent pixels as the argument the resulting texture will be black. | priority | monogamegraphics clears the screen when prerender is called everything drawn to the screen using monogame apis before calling monogamegraphics prerender is ignored the issue is that if you call monogame setdata using an array of transparent pixels as the argument the resulting texture will be black | 1 |
214,029 | 7,262,731,160 | IssuesEvent | 2018-02-19 07:56:48 | pmem/issues | https://api.github.com/repos/pmem/issues | closed | test: obj_ravl/TEST0: SETUP (all/none/debug/memcheck) | Exposure: Low OS: Linux Priority: 4 low State: To be verified Type: Bug | Found on dd622819dd4ee97d3920f913c70be371b5ee215f
```
==3182== Memcheck, a memory error detector
==3182== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3182== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==3182== Command: ./obj_ravl.static-nondebug
==3182== Parent PID: 3162
==3182==
==3182==
==3182== HEAP SUMMARY:
==3182== in use at exit: 9,920 bytes in 248 blocks
==3182== total heap usage: 1,000,052 allocs, 999,804 frees, 40,069,017 bytes allocated
==3182==
==3182== 9,920 bytes in 248 blocks are definitely lost in loss record 1 of 1
==3182== at 0x4C2DBB6: malloc (vg_replace_malloc.c:299)
==3182== by 0x405221: ravl_new_node (ravl.c:176)
==3182== by 0x40575F: ravl_emplace (ravl.c:408)
==3182== by 0x405707: ravl_insert (ravl.c:388)
==3182== by 0x404C36: test_stress (obj_ravl.c:182)
==3182== by 0x404FD6: main (obj_ravl.c:239)
==3182==
==3182== LEAK SUMMARY:
==3182== definitely lost: 9,920 bytes in 248 blocks
==3182== indirectly lost: 0 bytes in 0 blocks
==3182== possibly lost: 0 bytes in 0 blocks
==3182== still reachable: 0 bytes in 0 blocks
==3182== suppressed: 0 bytes in 0 blocks
==3182==
==3182== For counts of detected and suppressed errors, rerun with: -v
==3182== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
``` | 1.0 | test: obj_ravl/TEST0: SETUP (all/none/debug/memcheck) - Found on dd622819dd4ee97d3920f913c70be371b5ee215f
```
==3182== Memcheck, a memory error detector
==3182== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3182== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info
==3182== Command: ./obj_ravl.static-nondebug
==3182== Parent PID: 3162
==3182==
==3182==
==3182== HEAP SUMMARY:
==3182== in use at exit: 9,920 bytes in 248 blocks
==3182== total heap usage: 1,000,052 allocs, 999,804 frees, 40,069,017 bytes allocated
==3182==
==3182== 9,920 bytes in 248 blocks are definitely lost in loss record 1 of 1
==3182== at 0x4C2DBB6: malloc (vg_replace_malloc.c:299)
==3182== by 0x405221: ravl_new_node (ravl.c:176)
==3182== by 0x40575F: ravl_emplace (ravl.c:408)
==3182== by 0x405707: ravl_insert (ravl.c:388)
==3182== by 0x404C36: test_stress (obj_ravl.c:182)
==3182== by 0x404FD6: main (obj_ravl.c:239)
==3182==
==3182== LEAK SUMMARY:
==3182== definitely lost: 9,920 bytes in 248 blocks
==3182== indirectly lost: 0 bytes in 0 blocks
==3182== possibly lost: 0 bytes in 0 blocks
==3182== still reachable: 0 bytes in 0 blocks
==3182== suppressed: 0 bytes in 0 blocks
==3182==
==3182== For counts of detected and suppressed errors, rerun with: -v
==3182== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
``` | priority | test obj ravl setup all none debug memcheck found on memcheck a memory error detector copyright c and gnu gpl d by julian seward et al using valgrind and libvex rerun with h for copyright info command obj ravl static nondebug parent pid heap summary in use at exit bytes in blocks total heap usage allocs frees bytes allocated bytes in blocks are definitely lost in loss record of at malloc vg replace malloc c by ravl new node ravl c by ravl emplace ravl c by ravl insert ravl c by test stress obj ravl c by main obj ravl c leak summary definitely lost bytes in blocks indirectly lost bytes in blocks possibly lost bytes in blocks still reachable bytes in blocks suppressed bytes in blocks for counts of detected and suppressed errors rerun with v error summary errors from contexts suppressed from | 1 |
306,775 | 9,403,864,786 | IssuesEvent | 2019-04-09 03:21:17 | ClangBuiltLinux/linux | https://api.github.com/repos/ClangBuiltLinux/linux | closed | -Wparentheses-equality in kernel/bpf/syscall.c | -Wparentheses-equality [ARCH] arm32 [BUG] linux good first issue low priority | from linaro tcwg ci:
```
00:00:34 kernel/bpf/syscall.c:767:30: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]
00:00:34 } else if (((map)->map_type == BPF_MAP_TYPE_HASH_OF_MAPS)) {
00:00:34 ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~
00:00:34 kernel/bpf/syscall.c:767:30: note: remove extraneous parentheses around the comparison to silence this warning
00:00:34 } else if (((map)->map_type == BPF_MAP_TYPE_HASH_OF_MAPS)) {
00:00:34 ~ ^ ~
00:00:34 kernel/bpf/syscall.c:767:30: note: use '=' to turn this equality comparison into an assignment
00:00:34 } else if (((map)->map_type == BPF_MAP_TYPE_HASH_OF_MAPS)) {
00:00:34 ^~
00:00:34 =
00:00:34 1 warning generated.
``` | 1.0 | -Wparentheses-equality in kernel/bpf/syscall.c - from linaro tcwg ci:
```
00:00:34 kernel/bpf/syscall.c:767:30: warning: equality comparison with extraneous parentheses [-Wparentheses-equality]
00:00:34 } else if (((map)->map_type == BPF_MAP_TYPE_HASH_OF_MAPS)) {
00:00:34 ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~
00:00:34 kernel/bpf/syscall.c:767:30: note: remove extraneous parentheses around the comparison to silence this warning
00:00:34 } else if (((map)->map_type == BPF_MAP_TYPE_HASH_OF_MAPS)) {
00:00:34 ~ ^ ~
00:00:34 kernel/bpf/syscall.c:767:30: note: use '=' to turn this equality comparison into an assignment
00:00:34 } else if (((map)->map_type == BPF_MAP_TYPE_HASH_OF_MAPS)) {
00:00:34 ^~
00:00:34 =
00:00:34 1 warning generated.
``` | priority | wparentheses equality in kernel bpf syscall c from linaro tcwg ci kernel bpf syscall c warning equality comparison with extraneous parentheses else if map map type bpf map type hash of maps kernel bpf syscall c note remove extraneous parentheses around the comparison to silence this warning else if map map type bpf map type hash of maps kernel bpf syscall c note use to turn this equality comparison into an assignment else if map map type bpf map type hash of maps warning generated | 1 |
654,777 | 21,662,371,241 | IssuesEvent | 2022-05-06 20:54:32 | curiouslearning/FeedTheMonsterH5P | https://api.github.com/repos/curiouslearning/FeedTheMonsterH5P | opened | Question # UI has 4 places instead of 5 | Low Priority | There is probably another UI asset we haven't found.
H5P version:
Unity version:
| 1.0 | Question # UI has 4 places instead of 5 - There is probably another UI asset we haven't found.
H5P version:
Unity version:
| priority | question ui has places instead of there is probably another ui asset we haven t found version unity version | 1 |
700,215 | 24,051,632,203 | IssuesEvent | 2022-09-16 13:19:10 | unfoldingWord/translationCore | https://api.github.com/repos/unfoldingWord/translationCore | closed | Need to show org for Bible in scripture pane | QA/Pass Priority/Low Regression 3.3.0 | ## Story Explanation
### User Story
Russ requested to show org for Bible in scripture pane.
Add org to tool tip for scripture in scripture pane.
As a [type of user], I want [some goal] so that [some reason].
### Features / Specifications
<!-- What are the high level features that need to be completed? -->
- [ ]
- [ ]
- [ ]
### Definition of Done
<!-- This is all the conditions, or acceptance criteria, that a
software product must satisfy are met and ready to be
accepted by a user, customer, team, or consuming system. -->
- [ ]
- [ ]
- [ ]
<!--
## QA
### Fails
- [ ]
- [ ]
-->
## Additional Context
### Mockups
| 1.0 | Need to show org for Bible in scripture pane - ## Story Explanation
### User Story
Russ requested to show org for Bible in scripture pane.
Add org to tool tip for scripture in scripture pane.
As a [type of user], I want [some goal] so that [some reason].
### Features / Specifications
<!-- What are the high level features that need to be completed? -->
- [ ]
- [ ]
- [ ]
### Definition of Done
<!-- This is all the conditions, or acceptance criteria, that a
software product must satisfy are met and ready to be
accepted by a user, customer, team, or consuming system. -->
- [ ]
- [ ]
- [ ]
<!--
## QA
### Fails
- [ ]
- [ ]
-->
## Additional Context
### Mockups
| priority | need to show org for bible in scripture pane story explanation user story russ requested to show org for bible in scripture pane add org to tool tip for scripture in scripture pane as a i want so that features specifications definition of done this is all the conditions or acceptance criteria that a software product must satisfy are met and ready to be accepted by a user customer team or consuming system qa fails additional context mockups | 1 |
272,753 | 8,517,239,235 | IssuesEvent | 2018-11-01 07:06:39 | Automattic/simplenote-electron | https://api.github.com/repos/Automattic/simplenote-electron | opened | Remotes changes do not recalculate display height in Note List | bug priority-low | #### Steps to reproduce
1. Log in to two different clients with the same account.
1. Set Note Display to either Comfy or Expanded.
1. Create a note in one client, and write two lines.
#### What I expected
The first line (title) and second line (excerpt) is correctly updated in the Note List of the other client.
#### What happened instead
The second line is cut off in the other client:
<img width="314" alt="screen shot 2018-11-01 at 15 52 54" src="https://user-images.githubusercontent.com/555336/47837364-1d1a8680-ddef-11e8-889c-300e3027b485.png">
A subsequent change to the second line will correctly recalculate the height.
#### Simplenote version
1.2.1 (after #977) | 1.0 | Remotes changes do not recalculate display height in Note List - #### Steps to reproduce
1. Log in to two different clients with the same account.
1. Set Note Display to either Comfy or Expanded.
1. Create a note in one client, and write two lines.
#### What I expected
The first line (title) and second line (excerpt) is correctly updated in the Note List of the other client.
#### What happened instead
The second line is cut off in the other client:
<img width="314" alt="screen shot 2018-11-01 at 15 52 54" src="https://user-images.githubusercontent.com/555336/47837364-1d1a8680-ddef-11e8-889c-300e3027b485.png">
A subsequent change to the second line will correctly recalculate the height.
#### Simplenote version
1.2.1 (after #977) | priority | remotes changes do not recalculate display height in note list steps to reproduce log in to two different clients with the same account set note display to either comfy or expanded create a note in one client and write two lines what i expected the first line title and second line excerpt is correctly updated in the note list of the other client what happened instead the second line is cut off in the other client img width alt screen shot at src a subsequent change to the second line will correctly recalculate the height simplenote version after | 1 |
809,116 | 30,174,850,980 | IssuesEvent | 2023-07-04 02:56:34 | CAMaji/oxygen-cs-grp2-eq10 | https://api.github.com/repos/CAMaji/oxygen-cs-grp2-eq10 | closed | [FEATURE] - Ajouter une table Project à la base de données (LABO 1) | feature wont fix low priority | ## Description de la fonctionnalité
Ajouter une table Project à la base de données. La table possèderait des champs (project id, repo owner, repo name, repo project number) qui permettrait de savoir d'où vient les métriques.
## Niveau de priorité (critique, important, ou utile)
Niveau critique
## Exigences et contraintes (optionnel)
## Détails techniques (optionnel)
| 1.0 | [FEATURE] - Ajouter une table Project à la base de données (LABO 1) - ## Description de la fonctionnalité
Ajouter une table Project à la base de données. La table possèderait des champs (project id, repo owner, repo name, repo project number) qui permettrait de savoir d'où vient les métriques.
## Niveau de priorité (critique, important, ou utile)
Niveau critique
## Exigences et contraintes (optionnel)
## Détails techniques (optionnel)
| priority | ajouter une table project à la base de données labo description de la fonctionnalité ajouter une table project à la base de données la table possèderait des champs project id repo owner repo name repo project number qui permettrait de savoir d où vient les métriques niveau de priorité critique important ou utile niveau critique exigences et contraintes optionnel détails techniques optionnel | 1 |
35,210 | 2,789,837,725 | IssuesEvent | 2015-05-08 21:49:14 | google/google-visualization-api-issues | https://api.github.com/repos/google/google-visualization-api-issues | opened | Ability to invert Timeline chart | Priority-Low Type-Enhancement | Original [issue 257](https://code.google.com/p/google-visualization-api-issues/issues/detail?id=257) created by orwant on 2010-04-14T13:52:35.000Z:
Please add something like
chart.draw(data, {'invert': y});
The chart will invert the y axis. This means that charts from the type
"lower = better" will be converted into the type "higher is better".
| 1.0 | Ability to invert Timeline chart - Original [issue 257](https://code.google.com/p/google-visualization-api-issues/issues/detail?id=257) created by orwant on 2010-04-14T13:52:35.000Z:
Please add something like
chart.draw(data, {'invert': y});
The chart will invert the y axis. This means that charts from the type
"lower = better" will be converted into the type "higher is better".
| priority | ability to invert timeline chart original created by orwant on please add something like chart draw data invert y the chart will invert the y axis this means that charts from the type quot lower better quot will be converted into the type quot higher is better quot | 1 |
81,079 | 3,587,270,383 | IssuesEvent | 2016-01-30 06:11:50 | hydrabolt/discord.js | https://api.github.com/repos/hydrabolt/discord.js | closed | Mentions should be ordered in the same order as written in the Message | enhancement low priority | This can be problematic. One has to avoid using commands with multiple mentions as arguments, otherwise they have to compare the clean text of the message versus the mentions and reorder them. This should most definitely be handled by the library. | 1.0 | Mentions should be ordered in the same order as written in the Message - This can be problematic. One has to avoid using commands with multiple mentions as arguments, otherwise they have to compare the clean text of the message versus the mentions and reorder them. This should most definitely be handled by the library. | priority | mentions should be ordered in the same order as written in the message this can be problematic one has to avoid using commands with multiple mentions as arguments otherwise they have to compare the clean text of the message versus the mentions and reorder them this should most definitely be handled by the library | 1 |
244,617 | 7,877,482,689 | IssuesEvent | 2018-06-26 07:13:08 | bleehu/Compound_X | https://api.github.com/repos/bleehu/Compound_X | closed | Attribute-based "spell" efficacy | Priority - Low Yellowlit - Awaiting Approval | We can differentiate between different skill levels of users of the same high-tech abilities by integrating attribute modifiers into the numbers of those abilities. I.e. "heals one wound up to X + Y*ability_mod" or "sucks out a 50% + ability_mod ~~of target's soul~~ complete copy of target's personality gestalt"
The ability modifier used is ideally the most relevant gauge of the quality of the relevant procedure, which is not necessarily the same as the most relevant gauge of the *quantity of* such procedures that particular user can perform.
From a design standpoint, I would like to see the quantity gauge (which directly determines the size of the resource pool) be the class' primary attribute and the quality gauge (which would be used as described above in spell descriptions) specifically not be the primary attribute, wherever plausible.
Such treatment for most relevant classes must await the aesthetic purge of actual magic, but specifically in the case of Medics, many Medic procedures could benefit from the integration of the user's Dex modifier. | 1.0 | Attribute-based "spell" efficacy - We can differentiate between different skill levels of users of the same high-tech abilities by integrating attribute modifiers into the numbers of those abilities. I.e. "heals one wound up to X + Y*ability_mod" or "sucks out a 50% + ability_mod ~~of target's soul~~ complete copy of target's personality gestalt"
The ability modifier used is ideally the most relevant gauge of the quality of the relevant procedure, which is not necessarily the same as the most relevant gauge of the *quantity of* such procedures that particular user can perform.
From a design standpoint, I would like to see the quantity gauge (which directly determines the size of the resource pool) be the class' primary attribute and the quality gauge (which would be used as described above in spell descriptions) specifically not be the primary attribute, wherever plausible.
Such treatment for most relevant classes must await the aesthetic purge of actual magic, but specifically in the case of Medics, many Medic procedures could benefit from the integration of the user's Dex modifier. | priority | attribute based spell efficacy we can differentiate between different skill levels of users of the same high tech abilities by integrating attribute modifiers into the numbers of those abilities i e heals one wound up to x y ability mod or sucks out a ability mod of target s soul complete copy of target s personality gestalt the ability modifier used is ideally the most relevant gauge of the quality of the relevant procedure which is not necessarily the same as the most relevant gauge of the quantity of such procedures that particular user can perform from a design standpoint i would like to see the quantity gauge which directly determines the size of the resource pool be the class primary attribute and the quality gauge which would be used as described above in spell descriptions specifically not be the primary attribute wherever plausible such treatment for most relevant classes must await the aesthetic purge of actual magic but specifically in the case of medics many medic procedures could benefit from the integration of the user s dex modifier | 1 |
690,003 | 23,642,595,231 | IssuesEvent | 2022-08-25 18:34:18 | easystats/easystats | https://api.github.com/repos/easystats/easystats | closed | Update to `v2` of GHA | Core Packages :package: low priority :sleeping: | A lot of minor and major improvements from `v1`. Just copy files from here:
https://github.com/r-lib/actions/tree/v2-branch/examples
Progress tracker:
- [x] insight
- [x] modelbased
- [x] bayestestR
- [x] effectsize
- [x] parameters
- [x] performance
- [x] correlation
- [x] report
- [x] see
- [x] datawizard
- [x] easystats | 1.0 | Update to `v2` of GHA - A lot of minor and major improvements from `v1`. Just copy files from here:
https://github.com/r-lib/actions/tree/v2-branch/examples
Progress tracker:
- [x] insight
- [x] modelbased
- [x] bayestestR
- [x] effectsize
- [x] parameters
- [x] performance
- [x] correlation
- [x] report
- [x] see
- [x] datawizard
- [x] easystats | priority | update to of gha a lot of minor and major improvements from just copy files from here progress tracker insight modelbased bayestestr effectsize parameters performance correlation report see datawizard easystats | 1 |
241,368 | 7,811,714,415 | IssuesEvent | 2018-06-12 11:03:22 | FubarDevelopment/QuickGraph | https://api.github.com/repos/FubarDevelopment/QuickGraph | closed | CP-13035: Unnecessary temp variables in UndirectedGraph.ContainsEdgeBetweenVertices | priority:Low | *From unknown CodePlex user on Friday, 17 April 2009 05:00:28*
Why are 2 vars being created/assigned here, when Edge PROPERTIES (to comply with whatever..) could just be passed directly?
private bool ContainsEdgeBetweenVertices(IEnumerable<TEdge> edges, TEdge edge)
{
Contract.Requires(edges != null);
Contract.Requires(edge != null);
var source = edge.Source;
var target= edge.Target;
foreach (var e in edges)
if (this.EdgeEqualityComparer(e,source, target))
return true;
return false;
}
COULD BE RESTATED AS:
private bool ContainsEdgeBetweenVertices(IEnumerable<TEdge> edges, TEdge edge)
{
Contract.Requires(edges != null);
Contract.Requires(edge != null);
foreach (var e in edges)
if (this.EdgeEqualityComparer(e,edge.Source edge.Target))
return true;
return false;
}
just pass the PROPERTIES directly, without hitting the stack for 2 variable declarations.
there is NO NEED for two temp vars in this routine.. | 1.0 | CP-13035: Unnecessary temp variables in UndirectedGraph.ContainsEdgeBetweenVertices - *From unknown CodePlex user on Friday, 17 April 2009 05:00:28*
Why are 2 vars being created/assigned here, when Edge PROPERTIES (to comply with whatever..) could just be passed directly?
private bool ContainsEdgeBetweenVertices(IEnumerable<TEdge> edges, TEdge edge)
{
Contract.Requires(edges != null);
Contract.Requires(edge != null);
var source = edge.Source;
var target= edge.Target;
foreach (var e in edges)
if (this.EdgeEqualityComparer(e,source, target))
return true;
return false;
}
COULD BE RESTATED AS:
private bool ContainsEdgeBetweenVertices(IEnumerable<TEdge> edges, TEdge edge)
{
Contract.Requires(edges != null);
Contract.Requires(edge != null);
foreach (var e in edges)
if (this.EdgeEqualityComparer(e,edge.Source edge.Target))
return true;
return false;
}
just pass the PROPERTIES directly, without hitting the stack for 2 variable declarations.
there is NO NEED for two temp vars in this routine.. | priority | cp unnecessary temp variables in undirectedgraph containsedgebetweenvertices from unknown codeplex user on friday april why are vars being created assigned here when edge properties to comply with whatever could just be passed directly private bool containsedgebetweenvertices ienumerable edges tedge edge contract requires edges null contract requires edge null var source edge source var target edge target foreach var e in edges if this edgeequalitycomparer e source target return true return false could be restated as private bool containsedgebetweenvertices ienumerable edges tedge edge contract requires edges null contract requires edge null foreach var e in edges if this edgeequalitycomparer e edge source edge target return true return false just pass the properties directly without hitting the stack for variable declarations there is no need for two temp vars in this routine | 1 |
452,150 | 13,046,745,401 | IssuesEvent | 2020-07-29 09:30:25 | mantidproject/mantid | https://api.github.com/repos/mantidproject/mantid | closed | Ensure that Unit Test for Parameter Correction File works when append is false | Framework Low Priority Stale | In my work on issue #12255 , I have not yet been able to get a unit test to work, for an append flag set to false. I have disabled this unit test to enable an early release of that issue for scientists to evaluate.
This unit test is `test_parameter_correction_file_replace`.
This issue is to ensure that the unit test is both appropriate and works.
| 1.0 | Ensure that Unit Test for Parameter Correction File works when append is false - In my work on issue #12255 , I have not yet been able to get a unit test to work, for an append flag set to false. I have disabled this unit test to enable an early release of that issue for scientists to evaluate.
This unit test is `test_parameter_correction_file_replace`.
This issue is to ensure that the unit test is both appropriate and works.
| priority | ensure that unit test for parameter correction file works when append is false in my work on issue i have not yet been able to get a unit test to work for an append flag set to false i have disabled this unit test to enable an early release of that issue for scientists to evaluate this unit test is test parameter correction file replace this issue is to ensure that the unit test is both appropriate and works | 1 |
194,581 | 6,896,456,066 | IssuesEvent | 2017-11-23 17:56:30 | feup-infolab/dendro | https://api.github.com/repos/feup-infolab/dendro | closed | [IMPROVEMENT] Searching for descriptors should take into account the label of the descriptor as well as its description | enhancement Low Priority | ### Dendro Version if known (or site URL)
Tested in the branch [machine-plus-human-identifiers](https://github.com/feup-infolab/dendro/tree/machine-plus-human-identifiers)
In the [commit](https://github.com/feup-infolab/dendro/commit/938e26a4d09ee8f2298bcad83fc79eb1477dcb1d)
### Please describe the expected behaviour
Seaching for the descriptor "title" and having previously selected the dcterms ontology, should return the dcterms:title descriptor.
### Please describe the actual behaviour
For the above result to be obtained it is necessary to search for "a name given to the resource", meaning that it is necessary for the search to include the label and the description.
### What steps can be taken to reproduce the issue?
Search for "title" in the dcterms ontology
### Possible ways to fix the problem (programmers)
Searching for descriptors should take into account the label and the description fields. | 1.0 | [IMPROVEMENT] Searching for descriptors should take into account the label of the descriptor as well as its description - ### Dendro Version if known (or site URL)
Tested in the branch [machine-plus-human-identifiers](https://github.com/feup-infolab/dendro/tree/machine-plus-human-identifiers)
In the [commit](https://github.com/feup-infolab/dendro/commit/938e26a4d09ee8f2298bcad83fc79eb1477dcb1d)
### Please describe the expected behaviour
Seaching for the descriptor "title" and having previously selected the dcterms ontology, should return the dcterms:title descriptor.
### Please describe the actual behaviour
For the above result to be obtained it is necessary to search for "a name given to the resource", meaning that it is necessary for the search to include the label and the description.
### What steps can be taken to reproduce the issue?
Search for "title" in the dcterms ontology
### Possible ways to fix the problem (programmers)
Searching for descriptors should take into account the label and the description fields. | priority | searching for descriptors should take into account the label of the descriptor as well as its description dendro version if known or site url tested in the branch in the please describe the expected behaviour seaching for the descriptor title and having previously selected the dcterms ontology should return the dcterms title descriptor please describe the actual behaviour for the above result to be obtained it is necessary to search for a name given to the resource meaning that it is necessary for the search to include the label and the description what steps can be taken to reproduce the issue search for title in the dcterms ontology possible ways to fix the problem programmers searching for descriptors should take into account the label and the description fields | 1 |
783,646 | 27,539,801,097 | IssuesEvent | 2023-03-07 07:40:45 | translate-tools/linguist | https://api.github.com/repos/translate-tools/linguist | opened | Support legacy configs - add config version while export | enhancement low priority | Now legacy config cannot be imported successfully, because structural changes
To fix it, we may add config version to a export file and migrate config while importing.
I suggest to add linter rule for GH actions, to check if config structure changed, version property must be increased | 1.0 | Support legacy configs - add config version while export - Now legacy config cannot be imported successfully, because structural changes
To fix it, we may add config version to a export file and migrate config while importing.
I suggest to add linter rule for GH actions, to check if config structure changed, version property must be increased | priority | support legacy configs add config version while export now legacy config cannot be imported successfully because structural changes to fix it we may add config version to a export file and migrate config while importing i suggest to add linter rule for gh actions to check if config structure changed version property must be increased | 1 |
203,343 | 7,059,999,057 | IssuesEvent | 2018-01-05 06:01:38 | Navarra/game | https://api.github.com/repos/Navarra/game | opened | Mouse allows to walk on blocked tiles after path lands mouse on a blocked tile | bug canvas easy good first issue low priority | <!-- Please don't delete this template or we'll close your issue -->
<!-- Before creating an issue please make sure you are using the latest version of Navarra. -->
**Do you want to request a *feature* or report a *bug*?**
bug
**What is the current behavior?**
When you right-click to walk somewhere, your mouse will still show "yellow" when the path finishes and your mouse is hovering on a blocked tile.
**If the current behavior is a bug, please provide the exact steps to reproduce.**
Make sure that your mouse will land on a blocked tile when player is finished walking.
1. Right-click on a walkable tile
2. Click on 'Walk here'
**What is the expected behavior?**
For the mouse selection to turn red and thus not click be attempt to walk there. | 1.0 | Mouse allows to walk on blocked tiles after path lands mouse on a blocked tile - <!-- Please don't delete this template or we'll close your issue -->
<!-- Before creating an issue please make sure you are using the latest version of Navarra. -->
**Do you want to request a *feature* or report a *bug*?**
bug
**What is the current behavior?**
When you right-click to walk somewhere, your mouse will still show "yellow" when the path finishes and your mouse is hovering on a blocked tile.
**If the current behavior is a bug, please provide the exact steps to reproduce.**
Make sure that your mouse will land on a blocked tile when player is finished walking.
1. Right-click on a walkable tile
2. Click on 'Walk here'
**What is the expected behavior?**
For the mouse selection to turn red and thus not click be attempt to walk there. | priority | mouse allows to walk on blocked tiles after path lands mouse on a blocked tile do you want to request a feature or report a bug bug what is the current behavior when you right click to walk somewhere your mouse will still show yellow when the path finishes and your mouse is hovering on a blocked tile if the current behavior is a bug please provide the exact steps to reproduce make sure that your mouse will land on a blocked tile when player is finished walking right click on a walkable tile click on walk here what is the expected behavior for the mouse selection to turn red and thus not click be attempt to walk there | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.