primordic/IssueDupesLite huggingface dataset:
Repository: cucumber/common

Issue #2168: Slack inviter is broken
Created: 2024-03-29T13:28:39Z
👓 What did you see?
From @sebrose I received this via LinkedIn: “I tried to join the community slack but it states TOKEN REVOKED”
The person was using the process documented in https://cucumber.io/docs/community/get-in-touch/#slack

Duplicate issue #2169: Can't register for slack for cuke
Created: 2024-04-29T18:41:01Z
🤔 What's the problem you've observed?
When I type in my email on your registration page I get.   An error like..
API token expired
Is that app broken?
Thanks John
✨ Do you have a proposal for making it better?
No response
📚 Any additional context?
No response

Closing comment (2024-04-29T21:39:53Z): Duplicate of #2168. As a work around you can use https://join.slack.com/t/cucumberbdd/shared_invite/zt-2i0fvyv35-PgrGAwIx3L~lFngzWkb86Q for now.
Repository: cucumber/common

Issue #59: Gherkin Lint - New project?
Created: 2016-08-08T04:43:21Z
A recent discussion in the cucumber/gherkin gitter room revealed that there are (at least) 3 Cucumber linters out there:

cuke_sniffer - Ruby
gherkin-lint - JavaScript
gherkin-lint - Ruby

The projects are similar, and I think there are some great unique things in each one of them.
What do you think about joining forces to create a single one to rule them all? Ideally in JavaScript since it's easier to use on the web, and also relatively easy to embed into other libraries as well as editors and IDEs.
If you're interested, just reply here and fill out this doodle for a google hangout kickoff meeting.
/cc @enkessler @allustin @vsiakka @r-cochran

Duplicate issue #320: gherkin-lint: consider adopting an already functional tool
Created: 2017-12-28T21:48:03Z
Summary
There is a tool called gherkin-lint written by vsiakka.
It has about 6k downloads this month and is license compatible.
I'm curious if there's any interest in picking it up?

Closing comment (2017-12-30T00:22:06Z): Related to #59
Repository: cucumber/common

Issue #148: Mark Gherkin gem as executable CLI
Created: 2017-03-16T16:36:31Z
Summary
It's got a CLI, but rubygems doesn't know it
Expected Behavior
gem install gherkin
gherkin some/feature/file.feature
# lots of events printed

Current Behavior
-bash: gherkin: command not found

Possible Solution
Tweak the gemspec

Duplicate issue #149: Mark Gherkin npm package as executable CLI
Created: 2017-03-16T16:37:24Z
Summary
It's got a CLI, but rubygems doesn't know it
Expected Behavior
npm install -g gherkin
gherkin some/feature/file.feature
# lots of events printed

Current Behavior
-bash: gherkin: command not found

Possible Solution
Tweak package.json

Closing comment (2017-03-16T16:38:12Z): Related to #148. Maybe we should name the CLIs gherkin-ruby and gherkin-javascript to avoid collision?
Repository: cucumber/common

Issue #107: Cucumber Expressions and special characters
Created: 2017-01-30T14:01:57Z
Cucumber Expressions currently use some special characters:

{ and } for parameters. (The optional : inside also has special meaning)
( and ) for optional text
/ (not yet used, but planned for alternation, e.g. likes/loves becomes (?:likes|loves)

So the question is - should we allow escaping of these characters so they are not interpreted? How likely is it that someone will want to escape them?
Thoughts?

Duplicate issue #333: cucumber-expressions: Matching a literal open-parenthesis
Created: 2018-02-09T15:11:58Z
Summary
I'm using cucumber as a platform-agnostic way to describe an API in a book I'm writing, which is perhaps a bit out-of-the-ordinary for cucumber, but so far has worked great. Upgrading to 3.x has proven awkward, though, as many of my steps involve describing function calls, with parameters lists enclosed in parentheses, like so:
Scenario: Subtracting two vectors
  Given v1 := vector(3, 2, 1)
    And v2 := vector(5, 6, 7)
  Then v1 - v2 = vector(-2, -4, -6)
While I can represent this with a raw regex, the cucumber expressions are beautifully convenient. Sadly, given a step definition like this:
Given("{word} := vector({float}, {float}, {float})") do |var, x, y, z|
  # ...
end
The parentheses are being interpreted as optional groups. Is there already a way to escape those, so they can be interpreted literally?
Expected Behavior
I would expect there to be a way to escape parentheses in cucumber expressions, so that they can be interpreted literally.
Current Behavior
There does not currently appear to be a way to escape parentheses in cucumber expressions.
Possible Solution
Consider OPTIONAL_REGEXP, here:
https://github.com/cucumber/cucumber/blob/fc5308ff70378277cfbe6a56d102c5a8c42be69f/cucumber-expressions/ruby/lib/cucumber/cucumber_expressions/cucumber_expression.rb#L11
If this were made a bit more sophisticated, it could be made to ignore parentheses that are prefixed by an escape character (a backslash comes to mind, but maybe there's something else that is more idiomatic to Cucumber?)
Your Environment

Version used: 5.0.13 (Ruby)
Operating System and version: macOS 10.13.3

Closing comment (2018-02-09T15:31:46Z): Hi @jamis!
This sounds like a dupe of #107, which we decided not to prioritise. Now, if you submit a PR that's a different story - I'd be happy to add it if you did! Using \ for escaping would be fine.
Repository: cucumber/common

Issue #190: cucumber-expression: Define default parameter type for quoted strings
Created: 2017-04-27T09:01:35Z
Summary
Cucumber should recognise double-quoted strings out of the box, in a consistent way across implementations.
Expected Behavior
Consider the undefined step:
Given my "blue" coat is zipped
Cucumber should recognise "blue" as a match of a string parameter type and suggest a snippet with the following Cucumber Expression:
my {string} coat is zipped

When the step defintion is implemented, Cucumber should pass the part between the double quotes to the step definition.
Current Behavior
Cucumber.js already registers a default stringInDoubleQuotes parameter type which does all of this.
Possible Solution
Define and register this default parameter type in cucumber-expressions so Cucumber implementations don't have to do it.
Context & Motivation
The parameter type name stringInDoubleQuotes is a bit long, and won't read well in step definitions. Using string instead would make it more readable/intuitive and it would standardise the behaviour in the cucumber-expression library, avoiding inconsistent behaviour on different cucumber implementations.

Duplicate issue #218: Add qstring parameter type for 'single quoted' and "double quoted" arguments
Created: 2017-06-06T18:57:08Z
Add built-in parameter types for matching 'single quoted' and "double quoted" arguments. Let's call it qstring (quoted string)

Closing comment (2017-06-08T08:32:44Z): Dupe of #190
Repository: cucumber/common

Issue #1681: Json-formatter detected as trojan horse
Created: 2021-08-04T10:01:03Z
Describe the bug
The executable cucumber-json-formatter-windows-amd64 v7.01 is being detected as Trojan named Artemis!2DD068390E80 by McAfee Antivirus software.
To Reproduce
Steps to reproduce the behavior:

On Windows system with McAfee antivirus attempt to download latest version of cucumber-json-formatter
Attempt to use/rename exe
McAfee on-access scan detects trojan (and deletes exe)

Expected behavior
No detection.
Context & Motivation
We are using cucumber-json-formatter in our AzureDevops release pipeline to generate a HTML report. We are using it to  convert ndjson results from cucumber to JSON to be consumed by this extension which in turn uses this node package.
We are using a previous version of cucumber-json-formatter (unsure what version as I can't see any version info on the exe) and this is not detected by McAfee but wanted to try the latest version I was trying to get screenshots to show on failed steps (not even sure this new version will help with that problem yet)
Screenshots

Your Environment

cucumber-json-formatter-windows-amd64 v7.01
McAfee Agent - v5.7.3.245
Windows 10 x64 - v1909

I will start looking at alternative for generating the HTML report but thought this was worth mentioning.

Duplicate issue #1974: Cucumber-json-formatter-windows is recognized as a malicious file
Created: 2022-05-09T10:45:27Z
👓 What did you see?
Cucumber-json-formatter-windows is recognized as a malicious file. By the browser as well as by the antivirus.


✅ What did you expect to see?
I would want the file to not be considered a threat.
📦 Which tool/library version are you using?
N/A I'm using it for cucumber/cypress reporting.
📚 Any additional context?
I have full confidence in the plugin, but security procedures at individual sites can cause misunderstandings - I would love to be able to use this great tool freely. I've seen old tickets about security problems (interpreting this file as a Virus) and that they were closed, but isn't there any way to correct this?

Closing comment (2022-05-09T10:51:09Z): Duplicate of #1681, #1556. TL;DR: It's a go executable. See https://go.dev/doc/faq#virus
Repository: cucumber/common

Issue #208: gherkin-ruby: The `rule_type` parameter in `AstBuilder#end_rule` is not used?
Created: 2017-05-12T00:51:06Z
Summary
While working on porting gherkin-ruby to crystal as gherkin-cr, I noticed that the AstBuilder#end_rule method in lib/gherkin/ast_builder.rb looks odd:
    def end_rule(rule_type)
      node = @stack.pop
      current_node.add(node.rule_type, transform_node(node))
    end
Current Behavior
The rule_type parameter passed into end_rule is not used. (The rule_type in node.rule_type is that node's attribute, not the end_rule method's parameter.)
Expected Behavior
I'm not sure which is expected.
Possible Solution
Should def end_rule(rule_type) be just def end_rule, or should rule_type somehow be used to filter the @stack items?

Duplicate issue #207: The `rule_type` parameter in 
Created: 2017-05-12T00:40:37Z
lib/gherkin/ast_builder.rb
    def end_rule(rule_type)
      node = @stack.pop
      current_node.add(node.rule_type, transform_node(node))
    end




Summary

Expected Behavior



Current Behavior




Possible Solution


Steps to Reproduce (for bugs)








Context & Motivation


Your Environment


Version used:
Operating System and version:
Link to your project:

Closing comment (2017-07-20T13:55:55Z): Dupe of #208
Repository: cucumber/cucumber-jvm

Issue #258: CucumberException when running Cucumber with Jacoco code coverage
Created: 2012-03-14T12:26:32Z
Hi,
running cucumber tests with Jacoco code coverage enabled causes a cucumber exception.
Cause of this exception:
The Jacoco code coverage introduces new methods in the class using byte code manipulation. This then causes the following assertion to throw a cucumber exception:
private void assertNoDeclaredMethods(Class clazz) {
    if (clazz.getDeclaredMethods().length != 0) {
        throw new CucumberException(
                "\n\n" +
                        "Classes annotated with @RunWith(Cucumber.class) must not define any methods.\n" +
                        "Their sole purpose is to serve as an entry point for JUnit.\n" +
                        "Step Definitions should be defined in their own classes.\n" +
                        "This allows them to be reused across features.\n" +
                        "Offending class: " + clazz + "\n"
        );
    }
}

I suggest to change this code so that a warning is logged instead of throwing an exception. After all even if methods are declared in that class it does not do much harm.

Duplicate issue #275: Preventing JUnits from having methods interferes with emma
Created: 2012-03-26T20:54:36Z
Curious to see the code that is executed (covered) by my Cucumber tests I attempted to run a code coverage analysis with Emma (eclemma to be more specific - i.e. the eclipse plugin).   It seems that it must be doing some augmentation of the test classes and introducing its own methods, because when I attempted to run this against my Cucumber JUnits it failed with the error message:   Classes annotated with @RunWith(Cucumber.class) must not define any methods.
Yea its sort of an edge case.  I'm not even sure that code coverage via Cucumber is a metric that is meaningful.  However, I'm also not sure if the Cucumber runner needs to be so strict about preventing methods on the JUnit runner.   Perhaps it should just prevent JUnit annotated methods from being on the JUnit class.

Closing comment (2012-03-26T20:59:21Z): Dupe of #258, which was fixed in 1.0.0.RC23.
See https://github.com/cucumber/cucumber-jvm/blob/master/History.md
Please always report what version you are using - now I just have to guess that you're using something < 1.0.0.RC23.
Repository: cucumber/cucumber-jvm

Issue #966: Test output logs incorrect when running Cucumber feature files in parallel
Created: 2016-02-28T16:51:19Z
When the following surefire plugin config is used
<threadCount>2</threadCount>
<parallel>classes</parallel>
<redirectTestOutputToFile>true</redirectTestOutputToFile>

then the output from the tests is partially directed to the 'xxxtest-output.txt file and partially to stdout.  At first I thought this was a surefire plugin bug and filed this ticket (https://issues.apache.org/jira/browse/SUREFIRE-1230). The ticket has steps to reproduce the issue.
However, I debugged the issue a bit and found that when I run cukes, the JUnit4RunListener.testStarted method in Surefire is called after each step definition (i.e test) is executed.  When I run plain junit based unittests, that method is called before test is executed. This is the correct behaviour, i.e the 'testStarted' method should be called prior to the test.
Surefire sets the logger inside the 'testStarted' method. Since Cucumber calls this after running the tests, the logs are redirected partially to stdout and partially to the file.

Duplicate issue #951: Cucumber reports - Multi Features
Created: 2016-01-19T12:34:50Z
Hi,
I have an internally mounted test environment without using a CI tool like Jenkins and travis where I schedule my tests.
i use: selenium-grid + maven + cucumber-jvm + junit + cucumber reports plugin
my problem is when I send run a multiple tests (parallel) the cucumber reports plugin only show me the report of the last test .
I need that cucumber reports plugin return me a report with the results of all the tests that were run .
i run my test by command line with maven like this:
mvn clean install -Dtest="teste1, teste2, teste3" -Dcucumber.options="--tags $tags --plugin html:/reports/report --plugin json:/reports/report/output.json" -Dbase.url="$baseurl" -Dnode.url="$nodeurl"
NOTE: if i run only one test, runs fine and the report is perfect.
it is possible?  any suggestions to overcome my problem?

Closing comment (2016-08-30T21:44:28Z): Sounds like a dupe of #966
Repository: cucumber/cucumber-jvm

Issue #912: cucumber-java8 fails on OpenJDK 1.8.0
Created: 2015-09-23T11:10:24Z
Cucumber-Java8 depends on internals of the implementation of Oracle's JDK8. When I started experimenting with it I just always got the following exception:
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.056 sec <<< FAILURE! - in soy.wimmer.CucumberIT
Feature: Cucumber with Java8  Time elapsed: 0.047 sec  <<< ERROR!            
cucumber.runtime.CucumberException: Failed to instantiate class soy.wimmer.CucumberStepdefs
[…]                                                                          
Caused by: java.lang.reflect.InvocationTargetException: null                 
[…]                                                                          
Caused by: cucumber.runtime.CucumberException: java.lang.IllegalArgumentException: Wrong type at constant pool index
[…]                                                                          
Caused by: java.lang.IllegalArgumentException: Wrong type at constant pool index
    at sun.reflect.ConstantPool.getMemberRefInfoAt0(Native Method)           
    at sun.reflect.ConstantPool.getMemberRefInfoAt(ConstantPool.java:47)     
    at cucumber.runtime.java8.ConstantPoolTypeIntrospector.getTypeString(ConstantPoolTypeIntrospector.java:37)
    at cucumber.runtime.java8.ConstantPoolTypeIntrospector.getGenericTypes(ConstantPoolTypeIntrospector.java:27)
    at cucumber.runtime.java.Java8StepDefinition.<init>(Java8StepDefinition.java:45)
    at cucumber.runtime.java.JavaBackend.addStepDefinition(JavaBackend.java:162)
    at cucumber.api.java8.En.Given(En.java:190)                              
    at soy.wimmer.CucumberStepdefs.<init>(CucumberStepdefs.java:8)           
[…]

The test project causing this output is available at https://github.com/mawis/cucumber-java8-test
While it fails on OpenJDK8 it works without problems on Oracle JDK8. I consider this to be a bug, as I don't think that cucumber should depend on a specific implementation of the compiler.

Duplicate issue #949: ConstantPoolTypeIntrospector.java:37 problem with Oracle JDK 8u60+ 
Created: 2016-01-18T08:55:21Z
I'm using Cucumber 1.2.4 with the Java 8 extension. Everything worked fine with Oracle's JDK 8u45. After upgrading to JDK 8u60, Cucumber is throwing an exception:
java.lang.IllegalArgumentException: Wrong type at constant pool index
        at sun.reflect.ConstantPool.getMemberRefInfoAt0(Native Method)
        at sun.reflect.ConstantPool.getMemberRefInfoAt(ConstantPool.java:47)
        at cucumber.runtime.java8.ConstantPoolTypeIntrospector.getTypeString(ConstantPoolTypeIntrospector.java:37)
        at cucumber.runtime.java8.ConstantPoolTypeIntrospector.getGenericTypes(ConstantPoolTypeIntrospector.java:27)
        at cucumber.runtime.java.Java8StepDefinition.&lt;init&gt;(Java8StepDefinition.java:45)
        at cucumber.runtime.java.JavaBackend.addStepDefinition(JavaBackend.java:162)
        ... 74 more
The newest JDK version (8u66) unfortunately also has this issue.

Closing comment (2016-01-18T08:57:54Z): Dupe of #912
Repository: cucumber/cucumber-jvm

Issue #2723: how to add a time stamp to file name of the plugin file ?
Created: 2023-04-05T17:15:22Z
Hi ,
I have custom plugin for running cucumber tests. The log file name is static.
I wanted to change the file name embedded with timestamp. How can i achieve this ? Please share your thoughts.

Duplicate issue #2733: how to add a time stamp to file name of the plugin file ?
Created: 2023-04-13T02:59:50Z
Hi ,
I have custom plugin for running cucumber tests. The log file name is static.
I wanted to change the file name embedded with timestamp. How can i achieve this ? Please share your thoughts.
I have posted this on community also.. I don't see the community is active. I wanted to hear from core developers thoughts.

Closing comment (2023-04-13T10:22:02Z): Hi! This is the issue tracker of an open source project. We use this for bugs and feature requests. The project is mostly developed by volunteers in their spare time. It is not the right place to ask for help.
Additionally when asking for help from complete strangers you should at least make it easy for them to answer your question. You may want to read this and the linked pages for a better understanding.
Duplicate of #2723,  #2722.
Repository: custom-components/ble_monitor

Issue #372: BLE sensor updates
Created: 2021-05-29T05:28:26Z
After the last update LYWSDCGQ sensors send data only with the 'Discovery' option enabled. The 'Active Scan' useless too.

Duplicate issue #375: LYWSDCGQ no data since update
Created: 2021-05-29T09:27:04Z
Hello,
There was several updates in the past few days, and now I notice that I don't have anymore data coming from my temp sensors.
There are no errors in the logs, but i noticed that the log saying which is the bt interface used (at startup) is not showing up anymore
Tried rebooting, restarting, reloading .... nothing works

Closing comment (2021-05-29T09:44:31Z): Probably a duplicate of #372, are you using discovery: False?
The message of the bt interface has been moved to info level in the log, so it won't be displayed anymore. We changed that to prevent spamming the log. So, that is "by design".
Repository: custom-components/ble_monitor

Issue #793: [Bug]: Discovered sensors do not restore state after a restart
Created: 2022-03-23T09:31:48Z
What happened?
When sensors are discovered, they do not restore their state after a restart of HA, even if this is the default BLE monitor setting. This is caused by the fact that the HA config entity is not aware of the newly added sensors yet.
Opening the BLE monitor settings and clicking submit will add the MAC's to the config option devices and will immediately restore the state, after which it does work. However, this requires that if an sensor is added, you will have to open the BLE monitor options to make the restore state function to work.
Sensor type
All
Relevant log output
No response

Duplicate issue #998: [Bug]:  restore_state at device level it is not working
Created: 2022-08-26T15:39:32Z
What happened?
  ble_monitor:
    bt_auto_restart: true
    discovery: false
    decimals: 2
    devices:
      - name: 'Xiaomi - Window Sensor - Test'            
        mac: 'MAC'
        encryption_key: 'KEY'
        restore_state: true

the state is not preserved after restart and it remain on unavailable until an event occour...
ble_monitor: 9.1.1
thanks
Sensor type
Xiaomi Window Sensor 2
Relevant log output
No response

Closing comment (2022-09-04T19:54:01Z): Duplicate of #793, please check the last post there and provide some info such that I can narrow the issue down. I'm closing this issue, to keep things together in one issue.
Repository: custom-components/ble_monitor

Issue #215: Add Windows support
Created: 2020-12-24T00:46:12Z
Which version/build of "Python" works correctly with this component under Windows 10 ?
Hi all,
I'm still trying to run this component (ble_monitor https://github.com/custom-components/ble_monitor) under Home Assistant for Windows Protable https://github.com/AlexxIT/HassWP (v0.116.4 - 2020-10-22, Python v3.8.5 32bit)
I just want to see if I can make my Xiaomi "Temperature and Humidity Monitor 2" LYWSD03MMC sensors working on a fresh installation of Home Assistant with Bluetooh Low Energy (BLE) component under Windows 10.
I have already tried 7 times (install and re-install, numerous tries...).
If it's definetly not possible with Home Assistant under Windows 10 like https://github.com/AlexxIT/HassWP, just let me... (I will stop tries).
Like everybody, I get stuck with the famous error :
"\Home Assistant\config\custom_components\ble_monitor\aioblescan_ext.py", line 1383, in create_bt_socket
sock = socket.socket(family=socket.AF_BLUETOOTH,
AttributeError: module 'socket' has no attribute 'AF_BLUETOOTH'
See
That's almost crazy : everybody says "rebuild your Python 3.x.x, make sure you have included "Bluetooh.h", try reinstall BlueZ... But nothing works (on Windows) !
I know I have to rebuild a totally new Python v3.8.x or v3.9.x (I will see) on my Windows system, but I didn't know I had to do this before using this very 'formidable' app Home Assistant on a my system (just Windows 10, the most used OS in the world !)...
Numerous Issues and messages have been posted on the subject, but still no clear solution for (very lonely) Windows users...
Should I have to investigate a rebuild/compilation of Python under my Windows 10 system, just to see my simple temperature sensor work ?
Really ?
I'm open to all working solutions, now... (includind dev if really necessary !)
Please, help !
Domi
PS: If I can get this Xiaomi sensor working LYWSD03MMC under Home Assistant for Windows, I promise you to publish a very nice tutorial !

Duplicate issue #171: module 'socket' has no attribute 'AF_BLUETOOTH'
Created: 2020-11-25T22:27:31Z
Hello. Im trying to run this on Windows and getting an error module 'socket' has no attribute 'AF_BLUETOOTH' 
What can i do? Could you maybe change to pybluez?

Closing comment (2021-01-17T17:27:40Z): Closing this issue, as a duplicate of #215. Please continue this conversation there.
Repository: custom-components/ble_monitor

Issue #854: [Enhancement] Support multiple measurements of the same type in BTHome DIY format
Created: 2022-05-02T20:15:30Z
Hi Ernst,
Good work on adding the HA BLE DIY format!  It's been a while since I last updated my Home Assistant as it was working fine for me, so I'd been using my own DIY format, but have now moved over to the official format.
A feature I was using that you don't currently have is support for more than one reading of the same type, e.g. my device is an ESP32 advertising 3x 32-bit 'count' values for my gas and electricity meters (but not my water meter as it doesn't have an LED/magnet :-( ).
I have had a go at adding this feature in my branch of the ble_monitor repository here:
https://github.com/scrambledleek/ha_hacs_ble_monitor
The homebrew-devel branch is my latest, and I have branches for various ble_monitor versions.
I just append '_' to the HA BLE result data (except for the 'packet' type).  Then there are some changes in sensor.py to recognise sensor data measurements with an appended index (using a regular expression) and adjust the key/name/unique_id of the description so that a separate Home Assistant entity is created.
I've only tested it for my case, so there may be some issues, but feel free to incorporate it if it seems good to you.
Thanks for all your efforts!

Duplicate issue #987: [Bug]: HA BLE DIY format - not work two counters
Created: 2022-08-09T16:56:23Z
What happened?
Hello.
My advertsing payload
0x02010615161C180200010201640509BE0000000509C8000100
0x020106 - LE only
0x15 - size
0x16 - 16-bit UUID
0x1C18 - GAT service User Data
0x020001 - incrementable Packet ID
0x020164 - battery level
0x0509BE000000 - first 32-bit counter
0x0509C8000100 - second 32-bit counter
BLE Monitor finds 1 device and 3 entities.
1 entity - battery level
2 entity - last counter
3 entity - RSSI
How can I get two counters?
Thanks.
Sensor type
HA BLE DIY format
Relevant log output
No response

Closing comment (2022-08-10T19:58:45Z): For now, Im closing this issue, as it is a duplicate of #854
Repository: custom-components/ble_monitor

Issue #295: Event loop stopped before Future completed
Created: 2021-02-26T17:19:20Z
Hello,
I think this is linked to #167, but since I upgraded to Home Assistant OS 5.12 yesterday, I have trouble with my bluetooth temperature sensors.
I don't see any other event that could have cause an issue, before that it was working perfectly well for months.
Now I can see this error multiple times in the logs:
**ERROR (Thread-3) [custom_components.ble_monitor] HCIdump thread: Runtime error while stop scan request on hci0: Event loop stopped before Future completed.**
By reading the previous issue, I didn't really get what was the solution.
Additional info: I am running "pure" HassOS on RPI 4B, so I don't have access to root or to the linux behind or to commands like hcitool, the only command that seems to work is bluetoothctl, with which I already tried to re-enable everything and repair all devices without success.
Another info, I use an external dongle (I identified its mac address by plugging it/unplugging it and by seing the output of bluetoothctl list command, and I set the external one as default controller with bluetoothctl)
Config:
ble_monitor:
  decimals: 1
  period: 60
  log_spikes: False
  use_median: False
  active_scan: False
  hci_interface:
    - 1
    - 0
  batt_entities: True
  discovery: False
  restore_state: False 
  report_unknown: False
  devices:
    - mac: 'xxx'
      name: 'xxx'
      temperature_unit: C

Thanks for the help !

Duplicate issue #519: HCIdump thread: Runtime error while stop scan request on hci0: Event loop stopped before Future completed.
Created: 2021-09-26T10:12:48Z
Logger: custom_components.ble_monitor
Source: custom_components/ble_monitor/init.py:634
Integration: Passive BLE monitor (documentation, issues)
First occurred: 08.48.39 (14 occurrences)
Last logged: 12.04.02
From host log
[245936.042183] Bluetooth: hci0: command 0x1002 tx timeout
[246838.039306] Bluetooth: hci0: command 0x1002 tx timeout
[247739.784431] Bluetooth: hci0: command 0x1002 tx timeout
[248641.648943] Bluetooth: hci0: command 0x1002 tx timeout
[249543.585830] Bluetooth: hci0: command 0x1002 tx timeout
[250445.579825] Bluetooth: hci0: command 0x1002 tx timeout
[251347.545491] Bluetooth: hci0: command 0x1002 tx timeout
[252249.446223] Bluetooth: hci0: command 0x1002 tx timeout
Setup:
RPI4 8GB
supervisor-2021.09.0
core-2021.9.7
Python 3.9.7
It have been working fine on my RPI3 but after i migrated i'am not able to use the Bluetooth.
I did a fresh install on my RPI4 and the restorted the snapshot.
Have uninstalled the BLE_monitor under intergration and also under HACS but same issue after fresh install.

Closing comment (2021-10-22T06:33:03Z): I'm closing this issue as a duplicate of #295, please continue discussing your issue in #295 and try with 5.6.0-beta.
Repository: custom-components/ble_monitor

Issue #1451: [Bug]: HA 2025.4.0 Setup failed for custom integration 'ble_monitor'
Created: 2025-04-03T20:46:38Z
What happened?
After updating Home Assistant to 2025.4 ble_monitor stopped working


Sensor type
No response
Relevant log output
Setup failed for custom integration 'ble_monitor': Requirements for ble_monitor not found: ['aioblescan>=0.2.14', 'janus>=2.0.0'].

Duplicate issue #1452: [Bug]: HA OS 15.1
Created: 2025-04-04T09:27:47Z
What happened?
Hello, I have a problem after upgrading to HAOS 15.1 the ble_monitor integration broke. The errors that pop up in my logs are the ones in the image. Please help with fixing this.

Sensor type
No response
Relevant log output
Unable to install package janus>=2.0.0: error: Failed to fetch: `https://files.pythonhosted.org/packages/68/34/65604740edcb20e1bda6a890348ed7d282e7dd23aa00401cbe36fd0edbd9/janus-2.0.0-py3-none-any.whl.metadata` Caused by: Could not connect, are you offline? Caused by: Request failed after 3 retries Caused by: error sending request for url (https://files.pythonhosted.org/packages/68/34/65604740edcb20e1bda6a890348ed7d282e7dd23aa00401cbe36fd0edbd9/janus-2.0.0-py3-none-any.whl.metadata) Caused by: client error (Connect) Caused by: dns error: failed to lookup address information: Name does not resolve Caused by: failed to lookup address information: Name does not resolve
Unable to install package aioblescan>=0.2.14: error: Failed to fetch: `https://files.pythonhosted.org/packages/2a/4c/b8e1a16c5baf299b540dd4a21c1b804651d9d7a1b2f459557d94f16c2baa/aioblescan-0.2.14-py3-none-any.whl.metadata` Caused by: Could not connect, are you offline? Caused by: Request failed after 3 retries Caused by: error sending request for url (https://files.pythonhosted.org/packages/2a/4c/b8e1a16c5baf299b540dd4a21c1b804651d9d7a1b2f459557d94f16c2baa/aioblescan-0.2.14-py3-none-any.whl.metadata) Caused by: client error (Connect) Caused by: dns error: failed to lookup address information: Name does not resolve Caused by: failed to lookup address information: Name does not resolve

Closing comment (2025-04-04T09:29:12Z): Duplicate of #1451
Repository: custom-components/ble_monitor

Issue #295: Event loop stopped before Future completed
Created: 2021-02-26T17:19:20Z
Hello,
I think this is linked to #167, but since I upgraded to Home Assistant OS 5.12 yesterday, I have trouble with my bluetooth temperature sensors.
I don't see any other event that could have cause an issue, before that it was working perfectly well for months.
Now I can see this error multiple times in the logs:
**ERROR (Thread-3) [custom_components.ble_monitor] HCIdump thread: Runtime error while stop scan request on hci0: Event loop stopped before Future completed.**
By reading the previous issue, I didn't really get what was the solution.
Additional info: I am running "pure" HassOS on RPI 4B, so I don't have access to root or to the linux behind or to commands like hcitool, the only command that seems to work is bluetoothctl, with which I already tried to re-enable everything and repair all devices without success.
Another info, I use an external dongle (I identified its mac address by plugging it/unplugging it and by seing the output of bluetoothctl list command, and I set the external one as default controller with bluetoothctl)
Config:
ble_monitor:
  decimals: 1
  period: 60
  log_spikes: False
  use_median: False
  active_scan: False
  hci_interface:
    - 1
    - 0
  batt_entities: True
  discovery: False
  restore_state: False 
  report_unknown: False
  devices:
    - mac: 'xxx'
      name: 'xxx'
      temperature_unit: C

Thanks for the help !

Duplicate issue #584: Runtime error while sending scan request
Created: 2021-12-14T22:24:43Z
Hi, I've been having this problem for a while when I try to connect the xiaomi thermometer with the bluetooth. The error happens with Home assistent and I don't know why, could someone give me a clue as to what it could be?
Cheers

``

31m2021-12-14 22:18:24 ERROR (Thread-3) [custom_components.ble_monitor] HCIdump thread: Runtime error while sending scan request on hci1: Event loop stopped before Future completed.. Resetting Bluetooth adapter 00:1A:7D:DA:71:13 and trying again.�[0m
�[31m2021-12-14 22:18:24 ERROR (Thread-3) [root] Uncaught thread exception
Traceback (most recent call last):
File "/config/custom_components/ble_monitor/__init__.py", line 608, in run
self._event_loop.run_until_complete(
File "/usr/lib/python3.9/asyncio/base_events.py", line 640, in run_until_complete
raise RuntimeError('Event loop stopped before Future completed.')
RuntimeError: Event loop stopped before Future completed.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib/python3.9/threading.py", line 954, in _bootstrap_inner
self.run()
File "/config/custom_components/ble_monitor/__init__.py", line 619, in run
reset_bluetooth(hci)
File "/config/custom_components/ble_monitor/bt_helpers.py", line 151, in reset_bluetooth
mac = hci_get_mac([hci])[0]
KeyError: 0�[0m

Closing comment (2021-12-15T06:43:42Z): Duplicate of #295 . Could you please post your issue in #295, also check that topic for some possible solutions.
Repository: cyberbotics/webots

Issue #5780: Test `robot_parallel_step` failing on local machine running in fast mode
Created: 2023-01-25T11:51:16Z
On my machine (Ubuntu 22.04) the robot_parallel_step api test is failing when it is ran in fast mode.
Running it at normal speed works correctly.
I experienced this only in develop branch (R2023b).
I have Webots compiled in debug mode, I will also check compiling in release mode.

Duplicate issue #5835: robot_parallel_step fails when run by test_suite.py with debug build of test and webots
Created: 2023-02-05T04:32:39Z
Describe the Bug
When running the robot_parallel_step test via test_suite.py using a debug build of the test and of webots, I consistently get:
FAILURE with robot_parallel_step: Camera measurement after first pose update is wrong.

This does not occur when running the test from the webots GUI and does not occur if both webots and the test are release builds. I suspect a race condition.
Steps to Reproduce

make -j18 debug
cd tests
make -C api/controllers/robot_parallel_step debug
./test_suite.py --group=api api/worlds/robot_parallel_step.wbt
See failure

Expected behavior
No failure.
System

Fedora 37 Workstation
Graphics Card: NV167 / Mesa Intel® UHD Graphics 630 (CFL GT2)

Closing comment (2023-02-06T07:47:01Z): Same as #5780.
Repository: cyberbotics/webots

Issue #882: Removing Camera with External Window Open Crashes Webots
Created: 2019-09-12T08:58:22Z
Describe the Bug
When a Robots has a camera, if you double-clic ont the camera displayer, it opens in another windows. Afterward, if you delete the camera node, webots.exe stops working.
Steps to Reproduce

start telemax.wbt for example
double-clic on one of the camera displayer to open it in a new windows
delete the camera or the robots
you got an error "Webots.exe .exe has stopped working"

(it occurs even if you previously closed the displayer windows, set the robot's controller to void, disabled the camera...)
Expected behavior
Deleting a camera even while it's working doesn't create any error or warning if you don't open the displayer in a new windows first.
System

Operating System: Windows 7 pro
Graphics Card: NVIDIA GeForce GTX 1060 6GB

Duplicate issue #623: Wrong rendering after opening external overlay window
Created: 2019-06-20T07:03:26Z
After loading many worlds, at some time the rendering becomes much darker than what it should be.
For example starting Webots and running the Guided Tour, at some point I got this appearance for the receiver_noise.wbt simulation:

Then, I quitted and restarted Webots and the rendering was correct:

I could reproduce this behaviour a couple of times (at some point the also the hokuyo.wbt Display overlays were not shown any longer on the scene).
Probably my NVIDIA drivers are not up-to-date, but it would be strange if this is the cause of the issue because it works at the beginning.
System: Windows 10
Graphics card: NVIDIA GeForce GT 640M with 2GB VRAM
OpenGL version: 3.3.0 NVIDIA 418.81
Ambient Occlusion: Medium
Texture Quality: High

Closing comment (2019-12-17T07:22:41Z): I checked and I can reproduce it also on my development environment.
Related to #882 and #302.
Repository: cyberbotics/webots

Issue #3486: Debian package and ROS Noetic
Created: 2021-07-22T08:01:52Z
It seems that linking of the ros controller is not properly done in the Debian package for ROS Noetic:
https://answers.ros.org/question/382842/i-am-getting-error-while-loading-shared-libraries-libboost_systemso1651/
It might come from the fact that the Debian package is generated in Ubuntu 18.04, so the controller got linked with the old Boost library. I am not sure how to overcome this. It seems it wasn't the case before, as the controller wasn't linked against any specific library version.

Duplicate issue #3488: Standard ROS controller crashing on simulation start when using use-ros-control flag
Created: 2021-07-22T11:01:58Z
Bug description
When starting webots simulation with a robot which has a standard ros controller, the ros controller crashes producing the error attached in the screenshot below. The error only occurs when the use-ros-control flag is set.
Steps to Reproduce

Start roscore
Start webots
Load world with a robot with the standard ros controller
Start the simulation
See error

Screenshots

System

Operating System: Ubuntu 20.04.2 LTS
Webots version: R2021b
ROS version: noetic

Additional context
The error doesn't always occur on startup. Most of the time it will, but there are times when it will crash a little bit later.

Closing comment (2021-07-23T09:48:38Z): It might be related to #3486. We compile the Debian package on Ubuntu 18.04, so all controllers are linked against Ubuntu 18.04 libraries.
Also, using the tarball package should solve the problem (https://github.com/cyberbotics/webots/releases/download/R2021b/webots-R2021b-x86-64.tar.bz2).
Repository: cyberbotics/webots

Issue #4144: Speaker test is currently broken
Created: 2022-01-21T15:54:32Z
Describe the Bug
Test speaker.wbt currently fails even on a local machine (Ubuntu 20).
FAILURE with speaker: wb_speaker_is_speaking should return true when TTS is running.
Likely introduced here: #4047

Duplicate issue #4061: Speaker test is broken
Created: 2021-12-21T09:16:34Z
Describe the Bug
I think it is due to this: #4047
It only fails locally because this specific test is disable on the CI

Closing comment (2022-01-21T15:58:37Z): duplicate of #4144
Repository: cyberbotics/webots

Issue #3296: `village_center.wbt` needs some optimizations
Created: 2021-07-02T09:18:14Z
Describe the Bug
World village_center.wbt needs some optimizations.
During the loading it goes through the processes:

Parsing Nodes
Downloading assets
Finalize nodes
Finalize nodes

During step (3), the memory consumption skyrockets to 12 GB (100%). Also, by reloading a few times, it doesn't always appear that step (2) gets consistently faster after caching. Some reloads appear to take as long as the first time.
On two occasions, after reloading a few times (and losing focus with the window while it was loading (not sure this is necessary for it to happen)), the Windows UI ended up crashing. Likely because of the memory usage.
I suspect a specific object might be the culprit as other big worlds don't suffer nearly as much.
This doesn't appear to be a regression however, the memory usage was already huge on master.

Duplicate issue #5166: Scenes/Animations/Simulation of large worlds freezes the computer
Created: 2022-09-02T12:15:32Z
Describe the Bug

Open village_center.wbt
Create a scene
Try to load it. At some point everything seems to freeze and Webots crashes, I assume it's because the computer ran out of RAM (I have 16GB)

Some optimization might be necessary at some point

Closing comment (2023-06-12T15:45:08Z): Duplicate of #3296
Repository: cyberbotics/webots

Issue #2891: Web simulation quick start instructions not working
Created: 2021-03-22T07:24:07Z
As reported by a user the quick start instructions described here are not working: the streaming_viewer doesn't start the Webots instance.
Moreover there is an issues with the ports: the port number logged in the simulation and session output.log files doesn't match the ones printed in the console.
For example in the logs for default configuration I always get port (session: 1999, server:2000) but in the console the printed ports seems randomly chosen (for example 14603 and 14604 or  15175 and 1575).
But when restarting the server I get an error about addresses already used, so I would say that the wrong ones are the random values printed in the console.

Duplicate issue #2966: Streaming server instructions
Created: 2021-04-13T06:57:53Z
Describe the Bug
I am trying to start a streaming server but Webots display on the browser hangs. I am not sure if this is a bug or maybe a documentation issue?
Steps to Reproduce
With the default example:

Follow the instructions: https://cyberbotics.com/doc/guide/web-simulation#quick-start
Open the interface on browser:

file:///usr/local/webots/resources/web/streaming_viewer/index.html


In the Connect to field type:

ws://localhost:1999/session?url=webots://github.com/cyberbotics/webots/branch/develop/projects/languages/python/worlds/example.wbt


Webots just hangs in the "Starting simulation" message
I can see that the session and simulation servers start:

Started default session server (9628)
Started default simulation server (9629)

and that I opened the ports:
python3   10055            root    7u  IPv6  97272      0t0  TCP *:1999 (LISTEN)
python3   10055            root    8u  IPv4  97273      0t0  TCP *:1999 (LISTEN)
python3   10056            root    4u  IPv4  94958      0t0  TCP *:2000 (LISTEN)
python3   10056            root    5u  IPv6  94959      0t0  TCP *:2000 (LISTEN)

With my project:
I also tried to start the servers with my own configuration:

simulation/simulation_config.json:

{
    "port": 2001,
    "projectsDir": "/path/to/my/own/webots/project"
}


session/session_config.json:

{
    "port": 2002,
    "server": "localhost",
    "simulationServers": [
      "localhost:2001"
    ]
}


server.sh:
Everything the same except lines 43-44:

SESSION_CONFIG="config/session/session_config.json"
SIMULATION_CONFIG="config/simulation/simulation_config.json"

Again the same thing I can see the ports are open and when I type ws://localhost:2002 in the Connect to field the interface just hangs again at the same place. For this configuration though it might be something I miss but it looks like it is the same behavior.
Expected behavior
I would like to see the simulated environment on my browser - both for the example and my own world.
System

Operating System: Ubuntu 20.04
Graphics Card: Nvidia Geforce RTX 2060

Closing comment (2021-04-13T07:34:12Z): Related to #2891

Thanks I will keep an eye to that issue until it's closed!
Repository: cyberbotics/webots

Issue #2496: Webots not detecting dedicated GPU ("X.org" as GPU vendor).
Created: 2020-12-02T20:33:20Z
Describe the Bug
Detection of a dedicated GPU seems to have failed on Manjaro Linux. Gives a warning message reporting "X.org" as GPU vendor.
Steps to Reproduce

Go to Add/Remove software on Manjaro.
Search webots.
Build the webots 2020b_rev1-1.
Run webots.

Expected behavior
This warning does not appear and my AMD dedicated GPU is selected.
System
Manjaro Linux x86_64
Kernel: 5.8.18-1-MANJARO
CPU: AMD Ryzen Threadripper 1950X (32) @ 3.400GHz
GPU: AMD ATI Radeon RX Vega 56/64

Duplicate issue #2612: Wrong OpenGL version detected
Created: 2020-12-30T13:29:58Z
Describe the Bug
Hi, I've been trying to run a snap version of Webots on a fresh installation Linux with latest AMD drivers installed. Sadly the simulator won't start, or after a fresh snap installation will start with the welcoming screen, and after that it will quit with the message:
webots  

libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: radeonsi
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: radeonsi
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
FATAL: Webots requires OpenGL 3.3 while only OpenGL 1.4 can be initialized.
Please check your GPU abilities and install the latest graphics drivers.
Please do also check that your graphics hardware meets the requirements specified in the User Guide.

glxinfo tells me that I currently have OpenGL 4.6 installed:
glxinfo | grep OpenGL

OpenGL vendor string: Advanced Micro Devices, Inc.
OpenGL renderer string: AMD Radeon (TM) R9 390 Series
OpenGL core profile version string: 4.6.14756 Core Profile Context 20.45
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 4.6.14756 Compatibility Profile Context 20.45
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: 4.6.14756 Compatibility Profile Context 20.45
OpenGL ES profile shading language version string: 4.60
OpenGL ES profile extensions:

Without the drivers, Webots launch properly, but have graphic options limited.
Steps to Reproduce

Install pro drivers as in https://amdgpu-install.readthedocs.io/en/latest/install-installing.html#installing-the-pro-variant
glxinfo
Install Webots via Snap
Run Webots in terminal
See error

Expected behavior
Webots working properly
System

Operating System: Kubuntu 20.04
Graphics Card: AMD Radeon R9 390 8GB

Closing comment (2021-03-03T08:25:30Z): Could be related to #2496.
Repository: cyberbotics/webots

Issue #4111: "Front View" should be "South View"
Created: 2022-01-12T14:33:37Z
Load sample world "pedestrian", select green pedestrian
view > change view > front view (alt + 2)
The view is always from south to north. The view is not of the front side of the pedestrian.

Rename
"Front View" -> "South View" (from -y to +y of world EastNorthUp (ENU) coordinate system)
"Back View" -> "North View"
"Left View" -> "West View"
"Right View" -> "East View"
Maybe add a true "Front View" (from +x to -x relative to selected object) etc.

Duplicate issue #5144: Viewpoint standard views are misleading
Created: 2022-08-31T08:08:37Z
Currently when using the Viewpoint standard positions this is the result:

Front/Back view: align with y-axis and visible plane is x-z
Right/Left view: align with x-axis and visible plane y-z
Top/Bottom view: align with z-axis and visible plane x-y

These are relative to the world itself and not to a specific object, so X corresponds to "east" and Y to "north".
But given that object uses now the FLU convention, when selecting the "Front" view I would expect the Viewpoint to align with the x-axis and the visible plane to be y-z.
Respectively when selecting the "Right/Left" view I would expect to see the x-z plane.
Is it correct the current implementation or should we change it to follow the FLU convention?
Note that if an object is rotated the views won't be adjusted to the selected object orientation but will still use the world coordinates.

Closing comment (2022-08-31T08:27:21Z): related to: #4111