primordic/IssueDupesLite huggingface dataset:
Repository: localsend/localsend

Issue #101: Provide a Linux on ARM64 build
Created: 2023-02-01T13:17:38Z
Linux on ARM64 is growing in popularity. It would be nice to have a Linux on ARM64 build.
I can include it in flathub/flathub#3869.

Duplicate issue #183: linux arm64 support
Created: 2023-02-19T12:51:58Z
linux arm64 support

Closing comment (2023-02-19T13:13:18Z): Please checkout existing issues first before creating a new one.
Duplicate of #101
Repository: log2timeline/plaso

Issue #1636: Question:  List of all data fields
Created: 2018-01-05T22:39:49Z
Plaso 20171231
I there a list of all the fields that can be extracted via psort.py?   I have pulled apart the sqlite output from log2timeline.py  and extracted the zlib data from the blob column.  I unzip the data and I can make out some of the fields from there.
Second,  it appears the -o l2tcsv format does not support the --additional_fields option. Is that correct?   It would be nice to have the datetime in ISO 8601 formant in the l2tcsv format.  Also, it seems that some of the l2tcsv format fields are empty when adding them to the dynamic output option.  Like MACB.
-Mark

Duplicate issue #1595: Question - What are the possible "additional fields"
Created: 2017-12-28T23:12:57Z
The following is found in the psort.py usage.  What are the possible additional fields?  I have searched the docs and even tried to review code to find this answer.  I have not had any luck so I am raising the question here.
A related question - Is there documentation of the database structure for the storage file?
Thanks for your help with this question(s).
-Mark
--additional_fields ADDITIONAL_FIELDS
Defines extra fields to be included in the output, in
addition to the default fields, which are datetime,
timestamp_desc, source, source_long, message, parser,
display_name, tag.

Closing comment (2018-01-06T17:48:16Z): Duplicate of #1636
Repository: log2timeline/plaso

Issue #1047: Performance: export after nsrlsvr analysis very slow
Created: 2016-10-16T11:16:50Z
While running:
psort.py --analysis nsrlsvr --nsrlsvr-hash md5 --nsrlsvr-host 127.0.0.1 --nsrlsvr-port 9120 -w output.log --disable-zeromq test.plaso 

The export after the analysis is very slow, a couple of events per update cycle.
To do:

 set up end-to-end test - #1904
 find and fix issue

Duplicate issue #1099: analysis tagging plugin very slow 
Created: 2016-12-05T10:05:09Z
Plaso version:
plaso - psort version 1.5.1_20161022
Operating system Plaso is running on:
Ubuntu 16.04.1
Installation method:
[GiFT][https://launchpad.net/~gift]
Description of problem:
Running psort.py with --analysis tagging (--tagging-file tag_windows.txt) is very slow.
Only a few events per second...
I noted that if I run psort.py with nsrlsvr + tagging analysis, it's fast (hundreds of events per second)
but if I (re)run psort.py with just the tagging analysis, it's slow...
Debug output/tracebacks:
plaso - psort version 1.5.1_20161022
Storage file	: ./IE9-Win7.plaso
Identifier		PID	Status		Events		Tags		Reports
Main			29485	running		2109 (6)	0 (0)		0 (0)
tagging			29493	analyzing	2109 (6)	0 (0)		0 (0)
Source data:

Closing comment (2016-12-07T00:17:17Z): Closing as this is sort of a duplicate of #1047
Repository: log2timeline/plaso

Issue #2170: ERROR: Unable to read artifact definitions from: \artifacts with error: At start Artifact definition: HadoopAppRoot found undefined labels: Hadoop.
Created: 2018-10-05T08:39:32Z
Hi,
The Windows version of log2timeline.exe fails with the error "ERROR: Unable to read artifact definitions from: \artifacts with error: At start Artifact definition: HadoopAppRoot found undefined labels: Hadoop."
Version used: plaso-20180930.zip
Tested on Windows 10

Duplicate issue #2186: Error: Unable to read artifact definitions
Created: 2018-10-23T18:48:36Z
Description of problem:
Trying to run log2timeline.exe (Windows 10) over E01 image.
ERROR: Unable to read artifact definitions from C:\Tools\Plaso\artifacts with error: At start Artifact definition: HapoopAppRoot found undefined label: Hadoop.
Command line and arguments:
log2timeline.exe G:\body.l2t D:\image.e01
Source data:
Image of Windows 10 based system
Plaso version:
20180930
Operating system Plaso is running on:
Windows 10 Pro
Installation method:
Downloaded latest package release from site. Python 2.7 and 3.6, and Visual C++ packages already installed.
Debug output/tracebacks:

Closing comment (2018-11-06T05:33:06Z): Duplicate of #2170
Repository: log2timeline/plaso

Issue #100: Expand Chrome Preferences parser
Created: 2015-01-29T22:26:38Z
add extension.autoupdate.next_check timestamp support
 add extension.install_signature.timestamp timestamp support
 add extension.settings.[ID].lastpingday timestamp support
 Additional ideas from http://www.obsidianforensics.com/blog/the-chrome-history-was-cleared-now-what/

Source file for some comments on their purpose:
https://chromium.googlesource.com/chromium/chromium/+/trunk/extensions/browser/extension_prefs.cc

Duplicate issue #970: Improvements to the chrome preferences parser
Created: 2016-08-29T19:59:06Z
A FR to add more details into the Chrome preferences parser, specifically to parse the:

last_clear_browsing_data_time (WebKit timestamp) indicating the last time the browser history was cleared
There are multiple other timestamps that are found within the Preferences file (that are webkit timestamped), such as,lastpingday, last_check, next_check, etc. that need to be investigated whether or not it makes sense to add them (ATM the only timestamp that is pulled in is the install_time for each extension)

Closing comment (2016-08-29T20:08:34Z): This looks like a duplicate of: #100
Repository: log2timeline/plaso

Issue #1406: Release preparations for Docker/Dockerhub
Created: 2017-09-18T10:51:17Z
Make sure we didn't break the docker container
 Ensure dockerhub will result in containers that will include the new release

Duplicate issue #1424: Update dockerhub for heimdall
Created: 2017-09-27T14:25:38Z

Closing comment (2017-10-02T13:12:05Z): Dupe of #1406
Repository: log2timeline/plaso

Issue #163: Windows Event Log message strings support enhancements
Created: 2015-04-14T05:16:53Z
Enhance Windows Event Log message strings support with:

 have psort re-use preferred language - now needs to be set manually
 Add support for more than 1 Event Log provider log source - #4159
 Ensure log source names are handled case insensitive - #4162
 Support multi stage message string look up by name, provider identifier and log source - #4160
 Add support for WEVT_TEMPLATE PE/COFF resource message identifier mappings

Add support to extract event definitions #4165
Map event identifiers to message identifiers using event definitions - #4166


 Look into event definition mapped to 0xffffffff (see #163 (comment))

Does not appear to be a valid message identifier

Duplicate issue #99: add Windows Event Log message strings support
Created: 2015-01-29T20:25:10Z
use winevt-rc.db to read and format Windows Event Log message strings at the formatting phase

Closing comment (2015-02-02T09:15:13Z): Preparations:

Step 1: https://codereview.appspot.com/193700043/
Step 2: https://codereview.appspot.com/204950043/

Add formatter mediator:

Step 3: https://codereview.appspot.com/203920043/

Add initial winevt-rc support:

Step 4: https://codereview.appspot.com/200460043/

After care:

set data location to a sane default
add support to pre format message string in PEP 3101 format
add documentation on how to build and use winevt_rc.db (pending review and release)
Add means to set the preferred LCID

https://codereview.appspot.com/215550043/


Add more formatter tests

https://codereview.appspot.com/204410043/
https://codereview.appspot.com/213650043/
https://codereview.appspot.com/213680043
https://codereview.appspot.com/221880043/
https://codereview.appspot.com/228160043/



Future enhancements are now tracked in: #163
Repository: louislam/uptime-kuma

Issue #1936: Status Page: Sort offline monitors at the top of the status page in 'offline' group
Created: 2022-07-24T18:11:18Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
UI Feature
🔖 Feature description
Currently, the status page isn't glanceable for offline monitors. I have a lot of monitors and it requires me to scroll through the list to see which monitors are offline.
✔️ Solution
I would find it useful if offline monitors could be shown at the top of the status page in an 'Offline' group.
This also allows displaying the status page on a TV for keeping track of offline monitors.
Optionally, make this behaviour configurable.
❓ Alternatives
No response
📝 Additional Context
Slightly similar as #1165, #1921 and #1585
Context
For additional context. This issue is specifically asking for sorting on the status page, not the dashboard.

Duplicate issue #4543: Dynamic warning first
Created: 2024-02-29T08:58:01Z
📑 I have found these related issues/pull requests
no issue
🏷️ Feature Request Type
Status-page
🔖 Feature description
good morning,
We currently use uptime kuma to monitor certain elements of our network. We have a screen dedicated to displaying the status page (http://kuma:3001/status/page).
The problem is that we have a large number of checks on this status page and it is impossible for us to see them at first glance.
Would it be possible to move the warning elements to the top of the page?

✔️ Solution
add an automatic sorting function to add warnings to the top of the page
❓ Alternatives
No response
📝 Additional Context
No response

Closing comment (2024-02-29T11:00:41Z): Duplicate of #1936
TLDR: currently only such a PR has been opened for the dashboard
Repository: louislam/uptime-kuma

Issue #1585: Ability to sort list or filter list by Status
Created: 2022-04-28T21:48:17Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
UI Feature
🔖 Feature description
I have more than two thousand websites I monitor using this easy-to-use awesome tool. When I do see a few sites down, it's difficult to find the sites being impacted as there seems to be no way to filter the list by up, down or paused status. It would nice that under Quick Stats, each stat number is a hyperlink to a filtered list showing all sites that have a matching status. Please see image: https://i.imgur.com/uP9VJgH.png
✔️ Solution
Add sort of list or filter by status
❓ Alternatives
No response
📝 Additional Context
No response

Duplicate issue #3162: Auto order Left Panel 
Created: 2023-05-15T10:39:30Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
UI Feature
🔖 Feature description
On the main home page where the quick stats part is, the left hand colum which shows all the servers should be able to re order its self and if a server is down show the server at the top of that list, as a  quick way to see what is down  in a simple format
✔️ Solution
Make it so the left column on the home page puts down Devices to the top.
❓ Alternatives
a drop down to select the feature to be enabled or disabled.
📝 Additional Context
No response

Closing comment (2023-05-19T10:29:35Z): This is a duplicate of #1585
Repository: louislam/uptime-kuma

Issue #2477: Request for monthly and yearly response time graph
Created: 2022-12-27T02:26:13Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
Other
🔖 Feature description
I would like to request to enable monthly and yearly response time graph option.  Currently only 3h,6h,24h and 1 week response time graph enabled.

✔️ Solution
Please add 1 month, 1 year and custom date to view response time graph would be great!
❓ Alternatives
No response
📝 Additional Context
No response

Duplicate issue #3843: chart with total uptime per day/week/month
Created: 2023-10-04T18:45:01Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
UI Feature
🔖 Feature description
I use uptime-kuma to track uptime of my laptop and set-top-box.
It would be nice to have an overview with the total uptime (hours and minutes) per day, week and month.
So I would have an overview how long I'm working and how long I watch TV. 😄
Not sure if this would be a usecase for uptime-kuma. :think
✔️ Solution
graph with total uptime per day, week and month
❓ Alternatives
No response
📝 Additional Context
No response

Closing comment (2023-10-04T20:46:37Z): I think this is a duplicate of #2477 (and other issues related to further configuring the response-timeframe graphs)
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^
Side-Note: please provide a meaningfull title
Repository: louislam/uptime-kuma

Issue #3743: Sort the status pages' monitors by `name`, `tags` or `uptime`
Created: 2023-09-15T03:18:44Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
UI Feature
🔖 Feature description
I have a few suggestions. As a system administrator, I find it the issue below is the most needed. The status page URL has been given to the operator who works 24H to monitor closely the URL status. When 1 page has 400+ URLs, it is harder for them to find which is down. they need to scroll until they find the down URL. Also, the operator did not have access to the dashboard.
✔️ Solution
Suggestion 1: When the URL is down, bring the URL to the top of the page instead of just saying Partially Degraded Service.
Suggestion 2: Put a drop-down menu on all URLs to show what is the latest error. 1 or 2 error is okay I guess.
❓ Alternatives
No response
📝 Additional Context
No response

Duplicate issue #4257: Status sorting on the status screen
Created: 2023-12-19T18:21:45Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
UI Feature
🔖 Feature description
On the status page, I would like the broken service to be at the top of the page and not at the bottom of the list. I would like to use the status page on surveillance monitors, so the header text could also be smaller to fit more information on the screen. I would also like the name of the outage service at the top of the screen and not the whole group.
✔️ Solution
see feature description
❓ Alternatives
No response
📝 Additional Context
No response

Closing comment (2023-12-20T16:20:16Z): Duplicate of #3743
Repository: louislam/uptime-kuma

Issue #2196: Select language for each status page
Created: 2022-10-07T17:18:19Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
UI Feature
🔖 Feature description
The Status Pages are the first face of uptime kuma and you can have many status pages as you want, however the language of the status pages are consistent with the selected language on the dashboard, it would be very useful to specify the language of each status page so you can serve status pages in different languages than the one selected in the dashboard
✔️ Solution
On the status page creation/edition add a button like the "show powered by" button but that says... "Main Language" On/Off; when "on", the language will be the same of the selected in dashboard (so if you change the language on the dashboard it change on the status page as well); when "off", a user can select the language for that specific status page
❓ Alternatives
No response
📝 Additional Context
No response

Duplicate issue #2784: Localize content (description, footer, etc.) on status pages
Created: 2023-02-15T16:04:13Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
UI Feature
🔖 Feature description
There should be a possibility in the UI to localize description, footer, title, etc.
This would easily implement as a additional feature (completely optional), because the status page itself is already localized. It would just add the possibility to display different content specific to the language that has been „guessed" by uptime-kuma.
If this feature is somewhat relevant and usefull, I could give implementing it as a feature a try 🤝
Just wanted to make sure to not waste my time on an unwanted implementation
✔️ Solution
There should be some kind of language-explorer in the status page settings where so called „language-keys“ should be defineable, that will be parsed to the guessed language as soon as the page loads.
As I have not looked into an simple implementation for it, it could not say what new ui elements would be needed (maybe some kind of context-menu).
❓ Alternatives
No response
📝 Additional Context
Uptime-Kuma is really great and super well implemented as well as maintained. Having user-defined content localized would elevate the functionality even further.

Closing comment (2023-07-27T16:38:46Z): @F0rce
I cannot reproduce this issue


The language of the status page matches the one defined in the settings
I don't know what this issue is referring to too be honest when you are talking about localising content.
I think what you want could be a duplicate of #2196
Repository: louislam/uptime-kuma

Issue #2991: Ability to monitor individual SSL sites on single server via SNI
Created: 2023-03-28T18:28:05Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
New Monitor
🔖 Feature description
Multiple sites being served securely from a single server behind a load balancer using SNI cannot be individual monitored using the host headers in HTTPS. This type of monitoring requires SNI, specifically the host name to be passed as part of the TLS negotiation.
✔️ Solution
The existing URL field of the HTTPS monitor would specify an IP address of the shared server, and a separate host name field would be required to specify the site to check. The contents of the host name field would be passed to the server as part of the TLS negotiation, allowing the server to properly route the request to the correct site.
A potential solution to this would be to not perform a DNS lookup for the host name on the HTTPS monitor and use the IP address specified in the monitor in conjunction with the user specified hostname.
❓ Alternatives
I'm aware of no alternatives, but I'm very open to suggestions.
📝 Additional Context
No response

Duplicate issue #3979: Feature: Let HTTP monitoring type use custom IP
Created: 2023-11-05T07:20:55Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
New Monitor, Other
🔖 Feature description
Uptime Kuma's HTTP monitoring type currently only supports inputting URLs for monitoring. However, some websites will configure multiple IPs for a single domain name. If you want to monitor only one of them, Uptime Kuma currently cannot achieve this.
For example: a.example.com points to 1.1.1.1 and 2.2.2.2
If I want to check whether https://a.example.com/blabla runs well on 1.1.1.1, Uptime Kuma currently cannot achieve this.
✔️ Solution
Add an option to specify an IP for the HTTP monitoring type.
❓ Alternatives
No response
📝 Additional Context
No response

Closing comment (2023-11-05T22:00:18Z): You can do that with the tools currently at your disposal:

you enter the ip into the url field
you enter the Host header as described in #2991

I think this is a duplicate of #2991
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^
Note that our contribution guide can be found here and that we are open to contributions if you adhere to this
Repository: louislam/uptime-kuma

Issue #4233: Automatically add `docker compose`/ `docker swarm` stacks as groups to be tracked
Created: 2023-12-13T12:20:21Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
New Monitor
🔖 Feature description
I am happily using Dockge and Uptime Kuma but I frequently forget to create new monitors in uptime-kuma whenever I create a new container/ docker compose file in dockge.
Could it be possible to have an integration between the two systems, so that any new container managed in dockge automatically gets a monitor created within Uptime Kuma?
✔️ Solution
Could it be possible to have an integration between the two systems, so that any new docker compose stacks managed in dockge automatically gets a monitor-group created within Uptime Kuma?
❓ Alternatives
No response
📝 Additional Context
No response

Duplicate issue #957: Automatically add `docker` containers to be tracked
Created: 2021-11-24T13:24:45Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
Other
🔖 Feature description
You should add a possibility for Kuma to check what docker containers are running, and start tracking them .
This way it would not be needed to manually add them.
✔️ Solution
In my use case, I would want to see appear my running docker containers in the kuma webUI.
❓ Alternatives
I have considered having to add a special label to each container to be tracked (in the docker-compose file)
📝 Additional Context
Netdata has a similar feature : (source)

Netdata auto-detects running containers and auto-populates the right-hand menu with their IDs or container names, based on the configuration of your system.

Flame also has a similar functionnality using labels : (source)

In order to use the Docker integration, each container must have the following labels

Closing comment (2023-12-13T13:22:35Z): docker-compose based group creation will continue to be tracked in #4233 to make this more focused and hopefully more implementable
Repository: louislam/uptime-kuma

Issue #3323: CA check reports  -635 days
Created: 2023-06-27T17:07:00Z
⚠️ Please verify that this bug has NOT been raised before.

 I checked and didn't find similar issue

🛡️ Security Policy

 I agree to have read this project Security Policy

Description
After I updated to 1.22.0 I got a lot of notifications about "expired" CA certificates. My certs are coming from Let's encrypt and they are Not After: Mon, 04 Jun 2035 11:04:38 GMT.

(matrix alert)
I have a few platforms to alert and I got spammed on all channels.
👟 Reproduction steps
I just update, nothing special.
👀 Expected behavior
I don't get notified about expired CA certificate if it's not expired.
😓 Actual Behavior
I got expired CA notification for every single https monitors.
🐻 Uptime-Kuma Version
1.22.0
💻 Operating System and Arch
Ubuntu 20.04
🌐 Browser
N/A
🐋 Docker Version
Docker 20.10.14 + Swarm
🟩 NodeJS Version
I'm using the official docker image
📝 Relevant log output
nothing

Duplicate issue #3424: Negative day for certificates reported in Slack notification
Created: 2023-07-14T16:31:58Z
⚠️ Please verify that this bug has NOT been raised before.

 I checked and didn't find similar issue

🛡️ Security Policy

 I agree to have read this project Security Policy

Description
Using Notification of certificates (generated by letencrypt's)  expiration into a slack channel return negative day.
In Kuma: expiration in 71 Days, notified in the slack channel: root CA certificate DST Root CA X3 will be expired in -652 days
👟 Reproduction steps
Monitor an https website with a certificates generated by letencrypt's with domain challenge.
Send a notification via webhooks into a slack channel, return negative expiration day.
👀 Expected behavior
Similar day remaining than Kuma (with have a correct number of remaining day)
😓 Actual Behavior
In Kuma: expiration in 71 Days, notified in the slack channel: root CA certificate DST Root CA X3 will be expired in -652 days


🐻 Uptime-Kuma Version
docker->louislam/uptime-kuma:1.22.1-alpine
💻 Operating System and Arch
docker->louislam/uptime-kuma:1.22.1-alpine
🌐 Browser
any
🐋 Docker Version
Docker version 24.0.2, build cb74dfc
🟩 NodeJS Version
No response
📝 Relevant log output
No response

Closing comment (2023-07-14T16:38:57Z): closed as duplicate of
#3323
Repository: louislam/uptime-kuma

Issue #84: Remote Executors
Created: 2021-07-19T05:51:56Z
OK, so this is quite possibly taking the project way past what it was ever intended to be, but stay with me on this one...
It would be amazing if I could launch "remote executors" and install them on various devices/virtual instances but have them report back to a central Uptime-Kuma instance.
This is a feature that some of the more advanced site-monitoring tools have, and would allow me to spin up instances across the globe to see what the response time was from each region etc.
As a rough outline, I'd probably be looking for the agents to either post their results back to the "primary" setup via HTTPS, or just load the results onto an MQTT Queue and have the "primary" read those results and log them.
Having it as a lightweight app would also mean that I could deploy onto a Raspberry Pi or similar if I didn't want to use virtual machines in a cloud-provider.

Duplicate issue #2955: Monitoring Agent for multi location status
Created: 2023-03-21T14:48:07Z
⚠️ Please verify that this feature request has NOT been suggested before.

 I checked and didn't find similar feature request

🏷️ Feature Request Type
Other
🔖 Feature description
Sometimes outages are only partial across the internet, to notice that it is useful to set up multiple agents at different locations, each independently executing the same monitoring actions.
✔️ Solution
An agent that executes only actual actions and communicates them back to the master.
❓ Alternatives
No response
📝 Additional Context
No response

Closing comment (2023-12-06T21:41:41Z): Duplicate of #84
Repository: lowRISC/ibex

Issue #741: [doc] Document basic commands for running/checking Ibex
Created: 2020-03-27T13:46:07Z
We should add some documentation around how to run lint, run RISC-V verification etc. The current top-level Makefile does help here but it'd be useful for this information to be included in the main Ibex documentation set as part of the getting started information.

Duplicate issue #1170: [docs] We don't have an easily discoverable page for "how do I run some Ibex tests?"
Created: 2020-11-02T10:43:11Z
See #1169 for a perfectly reasonable "Huh?! How do I do this thing?". At the very least, we need a link to the detailed verification docs in the user guide section. Ideally, we should probably add some links in the top-level README.md too.

Closing comment (2021-01-27T15:00:03Z): This is a duplicate of #741.
Repository: lowRISC/ibex

Issue #428: RISC-V compliance mtvec alignment
Created: 2019-10-25T14:13:22Z
Follow-up for PR #427 and in connection to #100
The current RISC-V compliance test places a trap handler at non 256-byte aligned position and uses this as a target for mtvec.
Ibex requires that the mtvec value is 256-byte aligned.
RISC-V Privileged Spec:

If mtvec is writable, the set of values the register may hold can vary by implementation. The value in the BASE field must always be aligned on a 4-byte boundary, and the MODE setting may impose additional alignment constraints on the value in the BASE field.


An implementation may have different alignment constraints for different modes. In particular,
MODE=Vectored may have stricter alignment constraints than MODE=Direct.


Allowing coarser alignments in Vectored mode enables vectoring to be implemented without a
hardware adder circuit.

@vogelpi mentioned in #427 that this should be fixed upstream.
The purpose of this issue is make the problem visible and to discuss the correct solution.

Duplicate issue #100: [tracking] Pass RISC-V compliance test suite
Created: 2019-06-26T13:56:49Z
We want to execute and pass the RISC-V compliance tests on Ibex.
Setup tasks

Create target to run the compliance tests in Verilator: #99

Known issues:

 Standards-compliant trap/interrupts: #70
 Implement the MSCRATCH CSR: #97

Closing comment (2021-01-27T17:02:06Z): Related to #428 and some recent changes that were done upstream to address the mtvec issues, I wanted to quickly check the riscv-compliance suite. Using v.2.1 from upstream (Dec 2020), I see many failures.
In CI, we are running an older version 844c666 (Feb 2020). Are there any plans to update the version?
Repository: lowRISC/ibex

Issue #845: Unique case isn't unique in ibex_alu.sv
Created: 2020-05-06T13:33:11Z
On the head of master (7dafdf64), run the following command:
cd dv/uvm/core_ibex
make WAVES=1 VERBOSE=1 ISS=spike COV=1 SEED=26187 TEST=riscv_arithmetic_basic_test
Once this has finished, have a look at one of the simulation logs. For example, out/seed-26187/rtl_sim/riscv_arithmetic_basic_test.0/sim.log (attached). You'll see VCS warning about incorrect unique case:
Warning-[RT-MTOCMUCS] More than one condition match in statement
/src/lr/ibex/rtl/ibex_alu.sv, 78
  More than one condition matches are found in 'unique case' statement inside 
  core_ibex_tb_top.dut.u_ibex_core.ex_block_i.alu_i, at time 32370000ps.
  
  Line number 79 and 80 are overlapping.

Rather upsettingly, this doesn't actually cause the test to fail. But it does suggest a problem with the RTL.

Duplicate issue #879: [RTL] Overlapping case statements in ibex_alu.sv
Created: 2020-05-18T18:10:28Z
Ran into this warning in OpenTitan chip level sim:
Warning-[RT-MTOCMUCS] More than one condition match in statement
../src/lowrisc_ibex_ibex_core_0.1/rtl/ibex_alu.sv, 78
  More than one condition matches are found in 'unique case' statement inside 
  tb.dut.top_earlgrey.u_rv_core_ibex.u_core.ex_block_i.alu_i, at time 
  234570001 psps.
  
  Line number 79 and 80 are overlapping

Steps to reproduce:

Clone OpenTitan repo, cd to repo top
Checkout PR 2052 if it is not already merged
Run chip DV sim:

$ util/dvsim/dvsim.py -i hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_uart_tx_rx [--waves] [--build-modes en_ibex_tracer]

PTAL, thanks!

Closing comment (2020-05-19T19:21:53Z): Duplicate of #845, closing.
Repository: lowRISC/ibex

Issue #25: Remove reg-reg loads
Created: 2019-05-06T14:07:10Z
reg-reg load (i.e., offset taken from a register and not from an immediate) should not be part of the Ibex ISA.
The code at line 261 here:
https://github.com/lowRISC/ibex/blob/master/rtl/ibex_decoder.sv
is a piece of code coming from RISCY and it should be removed.

Duplicate issue #175: Illegal load instruction causes data written to GPR
Created: 2019-07-18T20:23:44Z
ibex log
           551503000          275653 8000f926 0020ff83 INVALID                              x31=0x0000002d PA:0x0001b8ee  load:0x0000002d
           551505000          275654 8000f92a 0c8cb4ab INVALID                             
           551513000          275658 80000000 0001d06f jal              x0, 118784         

0020ff83 is an illegal load instruction (bit[14:12] = 3'b111), ibex detects it correctly. However, the read data is still written to the register.

Closing comment (2019-07-19T08:15:06Z): Duplicate of #25.
Repository: lowRISC/ibex

Issue #1656: riscv_mem_error_test failing under IBEX_CONFIG={small,experimental-branch-predictor}
Created: 2022-05-12T14:11:24Z
Observed Behavior
riscv_mem_error_test fails for IBEX_CONFIG={small,experimental-branch-predictor} when using the cosim flow
This failure is highlighted because riscv_mem_error_test was part of the smoketest ci run against all pull requests, and has been swapped out for the riscv_arithmetic_basic_test in the meantime.


Steps to reproduce the issue
cd dv/uvm/core_ibex
make -k SIMULATOR=xlm ITERATIONS=1 SEED=1 TEST=riscv_mem_error_test IBEX_CONFIG=small


Increasing estimate as further work was required
old estimate: 4

estimate 6
remaining 2022-08-11 3
remaining 2022-08-31 1

Duplicate issue #1711: [cosim,dv] riscv_mem_error_test failing under IBEX_CONFIG={small,experimental-branch-predictor} (ePMP / Cosim)
Created: 2022-07-19T08:52:35Z
riscv_mem_error_test failing under IBEX_CONFIG={small,experimental-branch-predictor}
see issue - #1656
From Rupert's last point on that issue:

For the small configuration, at least, the problem seems to be that we're running with no PMP. But the Spike configuration assumes otherwise!
The way to get this to work would be to call processor->set_pmp_num() and processor->set_pmp_granularity() in the  SpikeCosim constructor. Unfortunately, I'm not sure that it's going to be particularly easy to get at the right configuration variables from there: some plumbing required, I suspect.

Unsure if we are still observing the error. If we are not and happy that the related issue is resolved please comment on #1656 that it has been resolved or will not be triggered any more and then close the issue.

Closing comment (2022-08-10T19:49:19Z): Closing as tracked in #1656
Repository: lowRISC/ibex

Issue #25: Remove reg-reg loads
Created: 2019-05-06T14:07:10Z
reg-reg load (i.e., offset taken from a register and not from an immediate) should not be part of the Ibex ISA.
The code at line 261 here:
https://github.com/lowRISC/ibex/blob/master/rtl/ibex_decoder.sv
is a piece of code coming from RISCY and it should be removed.

Duplicate issue #4:  If instr[14:12]=3’b111”, rd=M[rs1+rs2]. This instruction code is not defined in the RISC-V spec.
Created: 2018-04-13T15:29:36Z
Please refer the line 289-307 in the RTL file “zeroriscy_decoder.sv”. If instr[14:12]=3’b111”, rd=M[rs1+rs2]. This instruction code is not defined in the RISC-V spec.

Closing comment (2019-05-16T16:37:00Z): This is referring to reg-reg loads as shown in this older snippet of the file:

  
    
      ibex/zeroriscy_decoder.sv
    
    
        Lines 289 to 307
      in
      f7c2b64
    
  
  
    

        
          
            
        

        
          
           // reg-reg load (different encoding) 
        

        
          
           if (instr_rdata_i[14:12] == 3'b111) begin 
        

        
          
             // offset from RS2 
        

        
          
             alu_op_b_mux_sel_o = OP_B_REGB_OR_FWD; 
        

        
          
            
        

        
          
             // sign/zero extension 
        

        
          
             data_sign_extension_o = ~instr_rdata_i[30]; 
        

        
          
            
        

        
          
             // load size 
        

        
          
             unique case (instr_rdata_i[31:25]) 
        

        
          
               7'b0000_000, 
        

        
          
               7'b0100_000: data_type_o = 2'b10; // LB, LBU 
        

        
          
               7'b0001_000, 
        

        
          
               7'b0101_000: data_type_o = 2'b01; // LH, LHU 
        

        
          
               7'b0010_000: data_type_o = 2'b00; // LW 
        

        
          
               default: begin 
        

        
          
                 illegal_insn_o = 1'b1; 
        

        
          
               end 
        
    
  


Duplicate of #25
Repository: lowRISC/ibex

Issue #1569: Add support for passing fixed binaries to our uvm/core_ibex regression flow
Created: 2022-03-16T22:35:23Z
estimate 4

Duplicate issue #1622: No Sequencer for Request Agent in the Memory Interface Agents directory.
Created: 2022-04-20T06:46:52Z
My Environment
I am trying to run tests on Ibex core from the binary generated from RISCV-DV verification environment. I've generated the tests separately from RV-DV and got the binaries which needs to be loaded into memory. I'm looking in to the files for Memory Interface Agent. For the request agent, no file for sequencer is provided. Do we need to create it separately? Or is it provided somewhere else?
EDA tool and version:
Synopsys VCS 2016
Operating system:
Ubuntu Linux
Version of the Ibex source code:
0a9f5ed

Closing comment (2022-07-20T12:16:37Z): Going to tag this as a PendingClose Issue and then close it off as the associated work is tracked in #1569. As a note to the original poster, these efforts have moved from the near-term tracking items to mid to long term.
Repository: lowRISC/ibex

Issue #2053: [dv, fcov] Look at use of U mode in riscv_mem_intg_error_test
Created: 2023-06-22T13:26:43Z
We're rarely hitting some bins of priv_mode_irq_cross, though associated with internal NMIs seen in U mode (which occur on ECC errors), increasing test iterations does help but doesn't reliably hit them every regression (#2051)
Investigate why and rework the test to more reliably cover everything without excessive iterations.

Duplicate issue #1825: [dv] Implement testing and coverage for various mstatus states
Created: 2022-09-30T17:12:49Z
I recently discovered Ibex enabled/disabled interrupts in U mode based on the mstatus.mie bit which is a violation of the spec (mie applies only to M-mode in U mode it is ignored, only the per interrupt MIE CSR bits should be considered. This is fixed in #1824
I found this when adding interrupts to the debug single step test, which does execute code in U mode with mstatus.mie set to 0, but clearly other testing (in particular the interrupt tests) don't do this otherwise we would have found this bug earlier.
This indicates a gap in our testing. We should add some coverage over different mstatus states that checks we see various states across U-mode/M-mode and with interrupts/debugs/exceptions occurring.
Coverpoints:

  cross - priv_modes, interrupts, mstatus.MIE (excluding mstatus.MIE == 1 && priv_mode == MACHINE as interrupt will not be taken in that case)
  cross - priv_modes, exceptions

Existing tests will require expanding to meet the new coverage

estimate 4

Closing comment (2023-06-22T13:27:02Z): Ran a local regression which has demonstrated the coverage holes are getting hit but even with the iteration increase it's not super reliable. Can consider this complete for V2.5 can revisit for V3 which is tracked in #2053
Repository: lowRISC/ibex

Issue #1598: [dv, fcov] Outstanding fcov implementation tracking
Created: 2022-04-01T13:39:59Z
Required coverage points are listed in the Ibex Coverage Plan.
Where coverage is implemented a coverpoint or cross name is listed in the documentation.
The following coverage still needs to be implemented. The descriptions are copied from the coverage plan. It is broken down by coverage plan section. See the coverage plan for further details
Hazards

 #1601

State Specific Behaviour

 Loads/stores with mstatus.mprv set and unset.

PMP

 PMP region access pass/fail with all combinations of unaligned access split across a boundary, both halves pass, neither pass, just the first passes, just the second passes.
 Compressed instruction access (16-bit) passes PMP but 32-bit access at same address crosses PMP region boundary.
 Each field of mssecfg enabled/disabled with relevant functionality tested.
 Access close to PMP region modification that allows/disallows that access

CSRs

 Write illegal/unsupported value to WARL field.
 Read and write from/to an unimplemented CSR

Exceptions/Interrupts/Debug

 #1664

Miscellaneous

 Double fault
 Awake from sleep due to interrupt or debug
 Interrupt/Debug whilst entering sleep.
 Enabling/Disabling ICache

Cross Coverage

 Instruction Categories x Controller state transitions of interest

Duplicate issue #1564: Implement all functional coverage points
Created: 2022-03-16T22:24:25Z

Closing comment (2022-07-20T12:25:29Z): @ctopal - given that the issues are tracked in #1598 and at least in that issue it looks like all the issues are marked as done, could you just have a quick check to see if that issue can be closed? Status on this issue is set to done but current is_open is still true. So if you are happy that everything here is closed please also click the close with comment. Thanks!
Repository: lowRISC/ibex

Issue #108: Interrupt context saving not working
Created: 2019-07-01T09:38:29Z
The problem is not systematic.
The problem is detected by comparing the files generated by the tracer.sv module, for the zero_riscy and the Ibex.
A small modification (around the is_decoding_o signal)of ibex_controller.sv module permits to avoid the problem (but this modification is not safe to 100 %;   The problem must be present in Debug mode : not tested).
list of file:
zero_riscy_VS_ibex_problem.log    : comparaison, line by line of trace_core.log (generated by trace.sv)
modifications_ibex_controller.log     :  modification that improves the behavior of Ibex during an interruption
ibex_writing_during_an_interruption.png  : waveforms to show the problem
zero_riscy_writing_during_an_interruption.pgn   : waveforms of zero_riscy (no problem)
zero_riscy_VS_ibex_problem.log
modifications_ibex_controller.log




modifications_ibex_controller.log
zero_riscy_VS_ibex_problem.log

Duplicate issue #136: Illegal JALR instruction is executed unexpectedly
Created: 2019-07-11T06:49:24Z
Here's the related instruction trace.
97598000           48700 8000f7e0 34391c67 INVALID
97638000           48720 00002dac f2051ae3 bne              x10, x0, -204       x10:00001900
0x34391c67 is decoded as illegal instruction correctly, as it's a JALR instruction with bit[14:12] != 0. However, looks like ibex doesn't jump to the boot address correctly to do the trap handling. Instead, the JALR instruction is executed and an instruction from 0x2adc is fetched unexpectedly.
Waveform snapshot:

please let me know if more information is needed to debug this issue

Closing comment (2019-07-11T08:48:17Z): Hi @taoliug ,
thanks for reporting this bug. There are currently problems with multicycle instructions (jumps, branches, mult/div, loads/stores) in combination with exceptions and interrupt requests as reported in #108  and #121 . The source of the problem is the main controller FSM inside ibex_controller.sv. I have been working on this and created a PR #132 to solve these issues. While this PR seems to fix the previous issues, it must first be reviewed before we can merge it into master. This hould happen soon.
In the meantime, if you want you can try out the fixes in PR #132 to see if it also solves your problem. I would be happy for feedback.
Best regards,
Pirmin
Repository: luakit/luakit

Issue #271: http://doc.luakit.org/ is not available
Created: 2015-02-18T20:57:02Z
Hello !
I am having fun configuring my Awesome WindowManager (in Lua), and I just discovered luakit... Wooaaa cool !! Another big thing to configure !! :)
on http://www.linuxjournal.com/content/luakit-extensible-micro-browser I've seen a picture of a luakit documentation, data structure, etc...
but the website seems to be out of service...
where can we get the documentation (other than searching in the source code), or when does the doc.luakit.org website will be up ?
Thank's !
bew78

Duplicate issue #276: doc.luakit.org/html/ is gone
Created: 2015-03-26T15:43:09Z
doc.luakit.org/html/ is gone, and the README doesn't link a full API reference. This should be considered a basic requirement for anything with a non-trivial api like luakit. It would be pretty good if you could fix that again.

Closing comment (2015-03-26T19:58:16Z): Isn't that a duplicate of #271?
Repository: luakit/luakit

Issue #509: Open new tabs instead of new windows
Created: 2017-09-09T12:42:18Z
Hey
luakit provides tabs but I prefer to use an other windows manager.  Then I press "w" instead of "t" to open in a new windows.
Unfortunately, bookmarks does not provide a shortkey to be opened in a new window. Maybe there is many other features that do not provide those mecanisms too.
For now, I use "w" luakit://bookmarks to open it in a new window.
Does this new feature make sense ?
Thanks

Duplicate issue #513: Tabs as windows feature
Created: 2017-09-13T15:51:41Z
Hi there. It would be really cool if there would be feature to open one window per one tab. There are lots of usecases for it(mostly switching tabs as regular windows with your wm and also for emacs users using Emacs WM they can treat their tabs in browser as regular Emacs buffers)

Closing comment (2017-09-14T04:34:01Z): Yep, I think this is a dup of #509
Repository: luakit/luakit

Issue #708: Follow hinting doesn't work on miniflux
Created: 2018-05-30T08:21:20Z
Hi there!
I've set up my own miniflux instance and have found out that luakit is not able to hint URLs on a page that miniflux provides. Here is the link to my miniflux Login: luakit, Password: luakit. Feel free to use it for testing.

Duplicate issue #760: Broken styles of hints on hepp.gmxhome.de
Created: 2019-03-03T01:17:07Z
I'm submitting a…
Bug Report
Current Behavior
Hints become unstyled and appear in a single row:
Without hints:

With hints:

Expected Behavior
The styling of hints should not be broken by certain sites.
Reproduction Instructions
http://hepp.gmxhome.de/
Environment

Linux Distribution & Version: Debian 10
Output of luakit --version: luakit 2.0.0
built with webkit 2.22.5 (installed version: 2.22.5)

Closing comment (2019-03-05T13:17:34Z): Also happens on https://lemondrops.xyz/
Probably the duplicate of #708 ?
Repository: luakit/luakit

Issue #804: Broken UI under webkit2gtk 2.26
Created: 2019-09-10T17:51:16Z
I'm submitting a…
Bug Report
Current Behavior
Broken UI under webkit2gtk 2.26: frozen webpages, favicons not showing
Environment
Linux Distribution & Version: Arch

Duplicate issue #807: `o` and `t` commands don't load pages
Created: 2019-09-26T17:04:44Z
I'm submitting a…
Bug Report
Current Behavior
I just upgraded to
luakit 2.1-12-g65f3f8d2
  built with webkit 2.24.0 (installed version: 2.26.1)

and now my o and t keys don't load the page. They'll navigate away from the current page, or open a new tab, but not load. Pressing r will then cause the page to load. They will also load if I close the current tab and press u to bring it back. Middle clicking links to open new tabs doesn't work either.
This issue doesn't occur when clicking on links (that is to say, the mouse works correctly).
Expected Behavior
o and t should immediately load pages.
Reproduction Instructions
Try thello<CR>. It will open a new empty tab. Press r to load it.
Environment
Arch linux, pacman -Syu last performed on 2019-09-26 at 12:00 UTC.
luakit 2.1-12-g65f3f8d2
  built with webkit 2.24.0 (installed version: 2.26.1)

Closing comment (2019-09-26T17:46:40Z): Ah, I didn't see 804. Yeah, this looks like a duplicate.
…
On Thu, Sep 26, 2019 at 7:41 PM Aidan Holm ***@***.***> wrote:
 This looks to me like a duplicate of #804
 <#804>. Or is there buggy behavior
 here that differs?

 —
 You are receiving this because you authored the thread.
 Reply to this email directly, view it on GitHub
 <#807?email_source=notifications&email_token=AACLAF3747OH3TX4F7JTLNLQLTX6LA5CNFSM4I24VPBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7WMVBY#issuecomment-535612039>,
 or mute the thread
 <https://github.com/notifications/unsubscribe-auth/AACLAF4XXQC6QD3W5AAULWDQLTX6LANCNFSM4I24VPBA>
 .


-- 
I'm currently travelling the world, sleeping on people's couches and doing
full-time collaboration on Haskell projects. If this seems interesting to
you, please consider signing up as a host!
https://isovector.github.io/erdos/