text:
Fcmila RGB-LED-Lampe wurde erfolgreich geflasht, Tasmota läuft, aber keine Funktionen wie AN / AUS möglich

Hallo,
ich habe folgendes Problem: ich habe nach dieser Anleitung https://www.heise.de/ct/artikel/Tuya-Convert-IoT-Geraete-ohne-Loeten-vom-Cloud-Zwang-befreien-4283623.html meine Fcmila LED bulb erfolgreich geflasht, die Lampe leuchtet weiß und ist über die IP-Adresse erreichbar. Mit Tasmota lässt sich alles einstellen, aber es geht kein An, kein Aus, keine Farbe, noch sonstiges. Sonoff B1 Modul oder ähnliche funktionieren auch nicht. Bei GPIO ... ist überall - None (00) -
Kann ich diese Lampe jetzt weg schmeißen oder gibt es noch Hoffnung mit Tasmota?
PS: Update geht auch alles.

Moin Nuggelbeb,
da muss ich, ohne sehr vorwurfsvoll wirken zu wollen, an den Artikelhinweis erinnern:"Sie sollten sich im Klaren sein, was es heißt, eine alternative Firmware zu flashen." Aber auch ich kenne den Drang, schnell loslegen zu wollen und dabei gelegentlich mal etwas zu wenig zum Thema zu lesen ;)
Du musst die Lampe jetzt natürlich nicht wegschmeißen, es gibt noch Hoffnung. Erstmal musst du das Geräteprofil auf "Generic" ändern, um alle GPIOs zuweisen zu können. Danach probierst Du nach und nach die GPIOs durch, bis Du für alle drei Farben den jeweiligen GPIO gefunden hast (so wie hier ganz unten "RGBW colour bulbs" https://github.com/arendst/Sonoff-Tasmota/wiki/Mirabella-Genio-Bulb). Es wäre toll, wenn Du dich anschließend nochmal mit den GPIOs hier melden würdest, damit wir diese ins Wiki aufnehmen können. Der nächste mit dieser Lampe muss dann nicht mehr suchen.
Gruß
Andi

Hi @Nuggelbeb
You can try the latest development build. We just implemented support for this type of RGB controller. https://github.com/arendst/Sonoff-Tasmota/pull/4991

mmm.,,, ich bin Anfänger und habe keine Ahnung
Also, habe das eingegeben und die Farbe blau ist schaltbar. (also nicht Schrott)
Modultyp = generisch
D3 GPIO0 => Keine
TX GPIO1 => Keine
D4 GPIO2 => Keine
RX GPIO3 => Keine
D2 GPIO4 => PWM1 (37)
D1 GPIO5 => PWM4 (40)
D6 GPIO12 => PWM2￼ (38)
D7 GPIO13 => PWM5 (41)
D5 GPIO14 => PWM3￼ (39)
D8 GPIO15 => Keine￼
D0 GPIO16 => Keine
Was muss ich da probier?

You'll need the latest development build to get this working and set the module type to SYF05

@kueblc  Sorry, ich bin das erste Mal hier auf GitHub, kenne mich noch nicht so richtig aus.
Wo finde ich das letzte Entwicklungsbuild? Das downloade ich dann und füge es in Tasmota als Update ein?

I recommend this guide on the Sonoff-Tasmota wiki for building the firmware. You can then use the firmware upgrade function in the web portal to upload your custom build.
It's safest to do your own build from source as you'll know exactly what's in the binary, plus you'll be able to predefined settings for your device and network.
If you have trouble with this I can build and upload a binary for you, but best learn to fish than to have a fish!

Ok, builden habe ich herausgefunden über Atom, aber was muss im Verzeichnis "Sonoff Tasmota" geändert werden?

You can customize your build in sonoff/my_user_config.h. Specify your WiFi credentials, your MQTT server, make sure USE_SM16716 is enabled, and turn off anything you don't need to save space. You'll want to keep the final binary below 512kb. You may also wish to modify platformio.ini to specify wish version to build, otherwise it'll build all of them and will take a long time.

Sry, aber welche letzte Binärdatei?

It will be in .pioenvs/sonoff(-DE)/firmware.bin

Okay firmware.bin ist fertig und auch geflasht. Aber die Fcmila LED bulb taucht nicht auf. Was stelle ich da noch ein?

Set the module type to SYF05 and you should be able to toggle power and change brightness via web portal, and also set color via MQTT.

Leider geht nichts. Sie schaltet nicht und Farbwechsel ist mit MQTT auch nicht möglich. Sie flackert ganz leicht.
ioBroker zeigt

Does the web page toggle not work at all? Does a slider appear?
Can you try to set GPIO13 to SM16716 PWR?
Also, try to send commands from the web console, such as color ff0000 or white 50.

mit GPIO13 - SM16716 PWR`geht An/Aus
Schieberegler ist da - aber geht nicht

Befehle von der Webkonsole

keine Änderung

Bei -white 50- geht sie aus
07:46:16 MQT: stat/sonoff/RESULT = {"POWER":"ON","Dimmer":49,"Color":"0,0,0,124","HSBColor":"0,0,0","Channel":[0,0,0,48]}

Okay sounds like your model is slightly different. Can you post any model numbers you can find on the bulb?
Let's go back to try to figure out the GPIOs then we can remap the SM16716 pins correctly. You said you were able to get a blue light before. Was that a light blue like a cold white or was it deep blue?
With model set to generic and GPIOs set to PWM channels like you had before, you can address each one individually with the command channel<x> <0-100> as in channel1 100. See if you can figure out what GPIO has which effect. Let us know the results!

Hallo, erst einmal möchte ich mich bedanken für die sehr gute Hilfe. Für mich ist das alles noch Neuland. Dabei dachte ich, dass es einfach ist und schnell geht, aber naja.
Anbei sende ich erstmal ein Bild von der Lampe. Die Eingaben mache ich dann etwas später.

Hmm interesting, this indeed looks very different from https://github.com/gsimon75/Tasmota-SYF05-Notes/blob/master/led_board.jpg.
You can clearly see the ESP microcontroller on the right, same board as the LEDs and drivers, instead of on a dedicated board as Tuya distributes. From your picture front left I can identify a SLM211A constant current driver, which takes a PWM from the microcontroller. I'm not able to make out the large 8 pin chip in the back.
I don't see an SM16716 chip anywhere on here so that would explain why the SYF05 module isn't working for you. Once we identify the rear chip we'll have a better understanding of what this needs to drive the LEDs correctly.

Also die Lampe ist laut Verpackung eine Fcmila Bulb LED.

Die Daten des Chips:
BHB31
25Q8CCSI
PP3338
Vielleicht können Sie mir doch noch helfen oder mir sagen, an wen ich mich wenden kann.
Danke nochmal.

Happy to help! Looks like the mystery chip is just some flash memory, not relevant for us.
Have you tried testing the individual GPIOs with channel<x> <level>? Any findings?

Leider nein.
Bei channel1 100 wird sie weiß, gibt man channel1 50 ein geht die Helligkeit runter. Weitere channels bringen keine Veränderung, nur die Anzeige - Command: unknown -
06:47:42 CMD: channel1 100
06:47:42 MQT: stat/sonoff/RESULT = {"POWER":"ON","Dimmer":100,"Color":"255,0,0,0,255","HSBColor":"0,100,100","Channel":[100,0,0,0,100],"CT":500}
06:48:37 CMD: channel1 50
06:48:37 MQT: stat/sonoff/RESULT = {"POWER":"ON","Dimmer":100,"Color":"127,255,0,0,255","HSBColor":"90,100,100","Channel":[49,100,0,0,100],"CT":500}

I have the same bulb    if set Tasmota to generic 18
GPI/O 4  PWM 1= white  and PWM3= blue
GPI/O 12 =green
GPI/O 13 =blue
GPI/O 14 = red
if set Tasmota to  Arilux LC11 Module
You can  change (some) colors with the cold/warm slider, brightness with the dark/bright slider
and toggle on/off.
I have a backup of the original firmware if it might be useful,but cant seem to attach files here ?

Can someone add this info to the  Queo compatible devices  Wiki  entry please
ChipID: 61dd05
MAC: B4:E6:XX:XX:XX:XX
SdkVersion: 1.5.3(aec24ac9)
BootVersion: 4
BootMode: 1
FlashMode: 1M DOUT @ 40MHz
FlashChipId: 1440c8
FlashChipRealSize: 1048576
FlashChipSize: 1048576
FlashChipMode: 3
system_upgrade_userbin_check: user2 0x81000

Trying a color picker wheel from Node-Red   can only get white and red and adjust brightness of them.
08:15:10 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":8,"Color":"000000050E","HSBColor":"0,0,0","Channel":[0,0,0,1,5],"CT":402}
08:15:11 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":7,"Color":"000000050C","HSBColor":"0,0,0","Channel":[0,0,0,1,4],"CT":402}
08:15:11 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":6,"Color":"000000040A","HSBColor":"0,0,0","Channel":[0,0,0,1,3],"CT":402}
08:15:11 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":5,"Color":"0000000309","HSBColor":"0,0,0","Channel":[0,0,0,1,3],"CT":402}
08:15:11 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":4,"Color":"0000000207","HSBColor":"0,0,0","Channel":[0,0,0,0,2],"CT":402}
08:15:11 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":4,"Color":"0000000207","HSBColor":"0,0,0","Channel":[0,0,0,0,2],"CT":402}
08:15:14 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":3,"Color":"0000000205","HSBColor":"0,0,0","Channel":[0,0,0,0,1],"CT":402}
08:15:14 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":2,"Color":"0000000103","HSBColor":"0,0,0","Channel":[0,0,0,0,1],"CT":402}
08:15:15 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":3,"Color":"0000000205","HSBColor":"0,0,0","Channel":[0,0,0,0,1],"CT":402}
08:15:15 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":8,"Color":"000000050E","HSBColor":"0,0,0","Channel":[0,0,0,1,5],"CT":402}
08:15:15 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":9,"Color":"0000000610","HSBColor":"0,0,0","Channel":[0,0,0,2,6],"CT":402}
08:15:15 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":10,"Color":"0000000712","HSBColor":"0,0,0","Channel":[0,0,0,2,7],"CT":402}
08:15:15 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":10,"Color":"0000000712","HSBColor":"0,0,0","Channel":[0,0,0,2,7],"CT":402}
08:15:20 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"F952FF0000","HSBColor":"298,68,100","Channel":[97,32,100,0,0],"CT":499}
08:15:22 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"FF40860000","HSBColor":"338,75,100","Channel":[100,25,52,0,0],"CT":499}
08:15:23 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"FF16D40000","HSBColor":"311,91,100","Channel":[100,8,83,0,0],"CT":499}
08:15:24 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"FB27FF0000","HSBColor":"299,85,100","Channel":[98,15,100,0,0],"CT":499}
08:15:25 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"4662FF0000","HSBColor":"231,73,100","Channel":[27,38,100,0,0],"CT":499}
08:15:26 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"537BFF0000","HSBColor":"226,67,100","Channel":[32,48,100,0,0],"CT":499}
08:15:29 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"FFFFFF0000","HSBColor":"0,0,100","Channel":[100,100,100,0,0],"CT":499}
08:15:30 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"9CFF560000","HSBColor":"95,66,100","Channel":[61,100,33,0,0],"CT":499}
08:15:33 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":94,"Color":"62EF000000","HSBColor":"95,100,94","Channel":[38,93,0,0,0],"CT":499}
08:15:34 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"FF2B800000","HSBColor":"336,83,100","Channel":[100,16,50,0,0],"CT":499}
08:15:38 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":4,"Color":"0A01050000","HSBColor":"333,90,4","Channel":[3,0,1,0,0],"CT":499}
08:15:41 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON","Dimmer":100,"Color":"61C5FF0000","HSBColor":"202,62,100","Channel":[38,77,100,0,0],"CT":499}
08:15:46 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"OFF"}
08:15:46 MQT: stat/Queo_Fcmila/POWER = OFF
08:15:48 MQT: stat/Queo_Fcmila/RESULT = {"POWER":"ON"}
08:15:48 MQT: stat/Queo_Fcmila/POWER = ON

Leider nein.
Bei channel1 100 wird sie weiß, gibt man channel1 50 ein geht die Helligkeit runter. Weitere channels bringen keine Veränderung, nur die Anzeige - Command: unknown -
06:47:42 CMD: channel1 100
06:47:42 MQT: stat/sonoff/RESULT = {"POWER":"ON","Dimmer":100,"Color":"255,0,0,0,255","HSBColor":"0,100,100","Channel":[100,0,0,0,100],"CT":500}
06:48:37 CMD: channel1 50
06:48:37 MQT: stat/sonoff/RESULT = {"POWER":"ON","Dimmer":100,"Color":"127,255,0,0,255","HSBColor":"90,100,100","Channel":[49,100,0,0,100],"CT":500}
tele/sonoff/STATE = {"Time":"2019-02-13T06:47:52","Uptime":"0T10:20:14","Vcc":3.403,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":19,"POWER":"ON","Dimmer":100,"Color":"255,0,0,0,255","HSBColor":"0,100,100","Channel":[100,0,0,0,100],"CT":500,"Scheme":0,"Fade":"ON","Speed":1,"LedTable":"OFF","Wifi":{"AP":1,"SSId":"**********","BSSId":"E8:DF:70:C1:1F:8A","Channel":11,"RSSI":100}}

@Nuggelbeb Did you return the module to Generic and set the GPIO pins to PWMs? What were the settings you used?

I have a backup of the original firmware if it might be useful,but cant seem to attach files here ?

@johng2001 You can post it if you place it inside a .zip file first.

Can someone add this info to the Queo compatible devices Wiki entry please

The wiki is open to edits from the public.

@kueblc Ich habe jetzt folgendes eingestellt

und da bekomme ich

Lampe lässt sich ein- und ausschalten. Mit unterstem Schieberegler heller und dunkler machen und mit dem oberen Schieberegler (kalt, warm) die Farbe zwischen rot und blau wechseln. Leider fehlt die Farbe Gelb. Warum? Müssen noch andere GPIO´s belegt werden?

An easy way to figure it out is to set each GPIO to a relay (1-8).  Then you turn each relay on and off and see what color shows on the bulb.  Once you figure that out, you set to PWM.
PWM1 = Red
PWM2 = Green
PWM3 = Blue
PMW4 = Cold White (I think)
PWM5 = Warm White (I think)
The whites could be swapped.

An easy way to figure it out is to set each GPIO to a relay (1-8). Then you turn each relay on and off and see what color shows on the bulb. Once you figure that out, you set to PWM.
PWM1 = Red
PWM2 = Green
PWM3 = Blue
PMW4 = Cold White (I think)
PWM5 = Warm White (I think)
The whites could be swapped.

mit welchen GPIO muss ich anfangen ?

Ah well this makes it tremendously straightforward :smile:
Set GPIO04 to PWM4, GPIO12 to PWM2, GPIO13 to PWM3, GPIO14 to PWM1. Then you should be able to set color with color <hex> via MQTT or the web portal, turn it on and off, and dim.

Ich bin raus. Lampe ist nicht mehr erreichbar. Programmiermodus - 3 x An/Aus - geht auch nicht und Serial geht auch nicht. Aber sie leuchtet weiß und blau blinkert.

I tried more things and managed to get Node-Red color picker working (I think) correctly
though the colors are correct they seem a bit dimer ( as if white is always mixed in )
Generic 18
???      I/O   2  = PWM 4
White   I/O   4  = PWM 5
Green  I/O  12 = PWM 2
Blue     I/O  13 = PWM 3
Red     I/O  14 = PWM 1
adjust the cold/warm slider  to bring back  pure white
dark/bright  works as expected.

I tried more things and managed to get Node-Red color picker working (I think) correctly
though the colors are correct they seem a bit dimer ( as if white is always mixed in )
Generic 18
???      I/O   2  = PWM 5
White   I/O   4  = PWM 4
Green  I/O  12 = PWM 2
Blue     I/O  13 = PWM 3
Red     I/O  14 = PWM 1
adjust the cold/warm slider  to bring back  pure white
dark/bright  works as expected.

Don't worry @Nuggelbeb, it's just reset it's configuration. Check to see if it's broadcasting a WiFi AP called sonoff-XXXX. Connect and reconfigure your WiFi settings at 192.168.4.1.
What caused it to reset?

@johng2001 Do you have both cold and warm white LEDs in this bulb? When you define 5 PWMs, PWM4 is CW and PWM5 is WW.

I tried both PWM 4 and 5  into I/O 4 , the white looks the same to me... also  as long as  the remaining PWM is put into  any one of the unused I/O's  then  cold/warm slider can be used to bring back white
and  dark/bright slider  works as expected  from tasmota web page.
to get the colors I  use ( because it works and is easy)  Node-Red color picker  to send MQTT commands.
still can't attach files here (maybe my version of Firefox is not supported)

Best settings so far for me.
GPIO 2 PWM 4   (any unused I/O just to get slider + PWM 4 or 5 can be swapped seems same result)
pwm 4 should = cold white
GPIO 4 PWM 5 = white							pwm 5 should = warm white
GPIO 12 PWM 2 = green							pwm 2 should = green
GPIO 13 PWM 3= blue							pwm 3 should = blue
GPIO 14 PWM 1  = red							pwm 1 should = red
in node red color picker   format HEX + show  hue and lightness slider.
use cold/warm slider in Tasmota to return to White  obviously there is a MQTT command but
enough for now.

Don't worry @Nuggelbeb, it's just reset it's configuration. Check to see if it's broadcasting a WiFi AP called sonoff-XXXX. Connect and reconfigure your WiFi settings at 192.168.4.1.
What caused it to reset?

Ja, ich habe bei den GPIOs rumgespielt und dann ging nichts mehr. Dann habe ich sie nicht mehr im Netz gefunden, auch unter 192.168.4.1 ist sie nicht zu finden. Hardwareseitig geht auch nichts mehr, Lötpins sind abgerissen und ging ja vorher auch nur über W-Lan.

If it still blinks, it's not dead! When you compiled your firmware, what was the value of WIFI_CONFIG_TOOL and WIFI_CONFIG_NO_SSID?

(These are found in my_user_config.h)

#define WIFI_CONFIG_TOOL       WIFI_RETRY
#define WIFI_CONFIG_NO_SSID    WIFI_WPSCONFIG

If your router supports WPS, press the button on your router and then power your bulb. It should hopefully reconnect and you'll be able to redo your configuration. If you know what combination of GPIO settings caused the last reset, let us know so we can avoid that again.

Leider hat das auch nichts gebracht. Die Lampe ist im 7. Himmel.
Ich glaube, ich habe auf GPIO 0 - Relay 1 oder so eingestellt. Leider weiß ich es nicht mehr, habe zu viel rumgespielt.

my node red setup for this bulb  flashed with Tasmota
[{"id":"fa350b71.b8ea2","type":"ui_switch","z":"27b0e016.c0e5a8","name":"","label":"ON / OFF","tooltip":"","group":"517aae8c.06068","order":18,"width":0,"height":0,"passthru":true,"decouple":"false","topic":"cmnd/Queo_Fcmila/power","style":"","onvalue":"on","onvalueType":"str","onicon":"","oncolor":"","offvalue":"off","offvalueType":"str","officon":"","offcolor":"","x":136,"y":2342.75,"wires":[["c0484a50.12baf"]]},{"id":"c0484a50.12baf","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"","qos":"","retain":"","broker":"2902344d.99c694","x":444,"y":2341.25,"wires":[]},{"id":"45da852.2fbdefc","type":"ui_slider","z":"27b0e016.c0e5a8","name":"Set Brightness","label":"SET BRIGHTNESS","tooltip":"","group":"517aae8c.06068","order":2,"width":0,"height":0,"passthru":true,"outs":"all","topic":"","min":"1","max":"100","step":1,"x":132.75,"y":2401.5,"wires":[["2e6aad51.34d77a"]]},{"id":"2e6aad51.34d77a","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/Dimmer","qos":"","retain":"","broker":"2902344d.99c694","x":548,"y":2461.75,"wires":[]},{"id":"f1ccb0ee.c896","type":"mqtt in","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/Dimmer","qos":"2","broker":"2902344d.99c694","x":849,"y":2457.25,"wires":[[]]},{"id":"ae8b953d.e7bf8","type":"ui_colour_picker","z":"27b0e016.c0e5a8","name":"Color Picker","label":"COLOR PICKER","group":"517aae8c.06068","format":"hex","outformat":"string","showSwatch":true,"showPicker":true,"showValue":true,"showHue":true,"showAlpha":true,"showLightness":true,"dynOutput":"false","order":1,"width":0,"height":0,"passthru":true,"topic":"","x":135.75,"y":2472.5,"wires":[["a461755b.a3599"]]},{"id":"73089cc.5176a64","type":"ui_dropdown","z":"27b0e016.c0e5a8","name":"Select Color","label":"SELECT COLOR","tooltip":"","place":"CHOOSE","group":"517aae8c.06068","order":4,"width":0,"height":0,"passthru":true,"options":[{"label":"RED","value":"eb0000","type":"str"},{"label":"GREEN","value":"00b80c","type":"str"},{"label":"BLUE","value":"0000CD","type":"str"},{"label":"WHITE","value":"0xFFFFFF","type":"str"},{"label":"ORANGE","value":"f52100","type":"str"},{"label":"PURPLE","value":"FF00FF","type":"str"},{"label":"YELLOW","value":"FFFF00","type":"str"},{"label":"AQUA","value":"00FA9A","type":"str"},{"label":"MAROON","value":"8B0000","type":"str"}],"payload":"","topic":"","x":140.75,"y":2536.5,"wires":[["a461755b.a3599"]]},{"id":"a461755b.a3599","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/color","qos":"","retain":"","broker":"2902344d.99c694","x":550,"y":2541.5,"wires":[]},{"id":"741c5d43.7f3b9c","type":"mqtt in","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/color","qos":"2","broker":"2902344d.99c694","x":849,"y":2541.75,"wires":[[]]},{"id":"d1a578a5.54674","type":"ui_button","z":"27b0e016.c0e5a8","name":"","group":"517aae8c.06068","order":5,"width":0,"height":0,"passthru":true,"label":"cycle color","tooltip":"","color":"","bgcolor":"","icon":"","payload":"3","payloadType":"str","topic":"cmnd/Queo_Fcmila/scheme","x":158.75,"y":2756.5,"wires":[["e3ae9a81.e6e7e"]]},{"id":"e3ae9a81.e6e7e","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"","qos":"","retain":"","broker":"2902344d.99c694","x":425.75,"y":2757.5,"wires":[]},{"id":"e1ffc018.53d6d","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/scheme","qos":"","retain":"","broker":"2902344d.99c694","x":648.75,"y":2755.25,"wires":[]},{"id":"1308eda3.df1dc2","type":"ui_button","z":"27b0e016.c0e5a8","name":"","group":"517aae8c.06068","order":6,"width":0,"height":0,"passthru":false,"label":"Rapid cycle color","tooltip":"","color":"","bgcolor":"","icon":"","payload":"4 speed 2","payloadType":"str","topic":"cmnd/Queo_Fcmila/scheme","x":181.75,"y":2828.25,"wires":[["6558acac.d4f3ec"]]},{"id":"6558acac.d4f3ec","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"","qos":"","retain":"","broker":"2902344d.99c694","x":425.5,"y":2827.5,"wires":[]},{"id":"3d0731d5.43c99e","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/scheme","qos":"","retain":"","broker":"2902344d.99c694","x":651.5,"y":2828.5,"wires":[]},{"id":"517aae8c.06068","type":"ui_group","z":"","name":"FCmilla Smart Bulb","tab":"43155387.db55dc","order":1,"disp":true,"width":"6","collapse":false},{"id":"2902344d.99c694","type":"mqtt-broker","z":"","broker":"localhost","port":"1883","clientid":"","usetls":false,"compatmode":true,"keepalive":"60","cleansession":true,"birthTopic":"","birthQos":"0","birthPayload":"","willTopic":"","willQos":"0","willPayload":""},{"id":"43155387.db55dc","type":"ui_tab","z":"","name":"FCmilla Lamp Bedroom","icon":"dashboard","order":3,"disabled":false,"hidden":false}]

My Node red settings for this bulb ( mistake in first try)
[{"id":"fa350b71.b8ea2","type":"ui_switch","z":"27b0e016.c0e5a8","name":"","label":"ON / OFF","tooltip":"","group":"517aae8c.06068","order":18,"width":0,"height":0,"passthru":true,"decouple":"false","topic":"cmnd/Queo_Fcmila/power","style":"","onvalue":"on","onvalueType":"str","onicon":"","oncolor":"","offvalue":"off","offvalueType":"str","officon":"","offcolor":"","x":136,"y":2342.75,"wires":[["c0484a50.12baf"]]},{"id":"c0484a50.12baf","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"","qos":"","retain":"","broker":"2902344d.99c694","x":444,"y":2341.25,"wires":[]},{"id":"45da852.2fbdefc","type":"ui_slider","z":"27b0e016.c0e5a8","name":"Set Brightness","label":"SET BRIGHTNESS","tooltip":"","group":"517aae8c.06068","order":2,"width":0,"height":0,"passthru":true,"outs":"all","topic":"cmnd/Queo_Fcmila/Dimmer","min":"1","max":"100","step":1,"x":132.75,"y":2401.5,"wires":[["2e6aad51.34d77a"]]},{"id":"ae8b953d.e7bf8","type":"ui_colour_picker","z":"27b0e016.c0e5a8","name":"Color Picker","label":"COLOR PICKER","group":"517aae8c.06068","format":"hex","outformat":"string","showSwatch":true,"showPicker":true,"showValue":true,"showHue":true,"showAlpha":true,"showLightness":true,"dynOutput":"false","order":1,"width":0,"height":0,"passthru":true,"topic":"","x":135.75,"y":2472.5,"wires":[["a461755b.a3599"]]},{"id":"73089cc.5176a64","type":"ui_dropdown","z":"27b0e016.c0e5a8","name":"Select Color","label":"SELECT COLOR","tooltip":"","place":"CHOOSE","group":"517aae8c.06068","order":4,"width":0,"height":0,"passthru":true,"options":[{"label":"RED","value":"eb0000","type":"str"},{"label":"GREEN","value":"00b80c","type":"str"},{"label":"BLUE","value":"0000CD","type":"str"},{"label":"WHITE","value":"0xFFFFFF","type":"str"},{"label":"ORANGE","value":"f52100","type":"str"},{"label":"PURPLE","value":"FF00FF","type":"str"},{"label":"YELLOW","value":"FFFF00","type":"str"},{"label":"AQUA","value":"00FA9A","type":"str"},{"label":"MAROON","value":"8B0000","type":"str"}],"payload":"","topic":"","x":140.75,"y":2536.5,"wires":[["a461755b.a3599"]]},{"id":"a461755b.a3599","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/color","qos":"","retain":"","broker":"2902344d.99c694","x":550,"y":2541.5,"wires":[]},{"id":"2e6aad51.34d77a","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/Dimmer","qos":"","retain":"","broker":"2902344d.99c694","x":548,"y":2461.75,"wires":[]},{"id":"f1ccb0ee.c896","type":"mqtt in","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/Dimmer","qos":"2","broker":"2902344d.99c694","x":849,"y":2457.25,"wires":[[]]},{"id":"741c5d43.7f3b9c","type":"mqtt in","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/color","qos":"2","broker":"2902344d.99c694","x":849,"y":2541.75,"wires":[[]]},{"id":"c1b85ead.2a1ae","type":"comment","z":"27b0e016.c0e5a8","name":"built in tasmote color cycle","info":"","x":202.75,"y":2726.75,"wires":[]},{"id":"d1a578a5.54674","type":"ui_button","z":"27b0e016.c0e5a8","name":"","group":"517aae8c.06068","order":5,"width":0,"height":0,"passthru":true,"label":"cycle color","tooltip":"","color":"","bgcolor":"","icon":"","payload":"3","payloadType":"str","topic":"cmnd/Queo_Fcmila/scheme","x":158.75,"y":2756.5,"wires":[["e3ae9a81.e6e7e"]]},{"id":"1308eda3.df1dc2","type":"ui_button","z":"27b0e016.c0e5a8","name":"","group":"517aae8c.06068","order":6,"width":0,"height":0,"passthru":false,"label":"Rapid cycle color","tooltip":"","color":"","bgcolor":"","icon":"","payload":"4 speed 2","payloadType":"str","topic":"cmnd/Queo_Fcmila/scheme","x":181.75,"y":2828.25,"wires":[["6558acac.d4f3ec"]]},{"id":"e3ae9a81.e6e7e","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"","qos":"","retain":"","broker":"2902344d.99c694","x":425.75,"y":2757.5,"wires":[]},{"id":"6558acac.d4f3ec","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"","qos":"","retain":"","broker":"2902344d.99c694","x":425.5,"y":2827.5,"wires":[]},{"id":"3d0731d5.43c99e","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/scheme","qos":"","retain":"","broker":"2902344d.99c694","x":651.5,"y":2828.5,"wires":[]},{"id":"e1ffc018.53d6d","type":"mqtt out","z":"27b0e016.c0e5a8","name":"","topic":"cmnd/Queo_Fcmila/scheme","qos":"","retain":"","broker":"2902344d.99c694","x":648.75,"y":2755.25,"wires":[]},{"id":"517aae8c.06068","type":"ui_group","z":"","name":"FCmila Smart Bulb","tab":"43155387.db55dc","order":1,"disp":true,"width":"6","collapse":false},{"id":"2902344d.99c694","type":"mqtt-broker","z":"","broker":"localhost","port":"1883","clientid":"","usetls":false,"compatmode":true,"keepalive":"60","cleansession":true,"birthTopic":"","birthQos":"0","birthPayload":"","willTopic":"","willQos":"0","willPayload":""},{"id":"43155387.db55dc","type":"ui_tab","z":"","name":"FCmila Lamp Bedroom","icon":"dashboard","order":3,"disabled":false,"hidden":false}]

Unfortunately sounds like @Nuggelbeb's bulb is bricked, so no amount of configuration assistance would resolve this. Closing, if there's any further questions please open a new issue on the relevant project.

Hi in witch mode should the bulb are for the the tuya converter?Fast or short blinking?

Работает отлично

repo: ct-Open-Source/tuya-convert


text:
meta server address:http://apollo.meta

apollo-portal 启动的时候报错

一样的问题

debug一下看看，看看配置是否正确读到了

source: gharchive/issue

authors: hongjie6688 nobodyiam xysjun

repo: ctripcorp/apollo

license_type: permissive

license_source: github-api


text:
feat(doc): Add Chuanqing Zhang to be a committer.

Fixes: no

Main Issue: no
Motivation

I contributed a lot of code to the CubeFS. I want to add myself(Chuanqing Zhang) as a committer to do more things.
In the future, I would first like to see the project code improve stability and security by continuously optimizing legacy issues. Then I will consider improving its performance and scalability, for example by providing support for rdma to improve communication performance, by providing support bitmap ino allocator, by providing support rocksdb instead btree in metanode.
rocksdb branch:https://github.com/cubefs/cubefs/tree/metanode_rocksdb (This branch has already been merged into the rocksdb development branch : https://github.com/cubefs/cubefs/tree/metanode_rocksdb_dev)
raft rdma branch:https://github.com/cubefs/cubefs/tree/online_0701_verbs_server
Modifications

Update the maintainers documentation.
Types of changes

[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Bugfix (non-breaking change which fixes an issue)
[x] Documentation Update (if none of the other choices apply)
[ ] So on...

Verifying this change

[ ] Make sure that the change passes the testing checks.

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

This can be verified in development debugging
This can be realized in a mocked environment, like a test cluster consisting in docker

(or)
This change MUST reappear in online clusters, or occur in that specific scenarios.
Does this pull request potentially affect one of the following parts:

[ ] Master
[ ] MetaNode
[ ] DataNode
[ ] ObjectNode
[ ] AuthNode
[ ] LcNode
[ ] Blobstore
[ ] Client
[ ] Cli
[ ] SDK
[ ] Other Tools
[ ] Common Packages
[ ] Dependencies
[ ] Anything that affects deployment

Documentation

[x] doc
[ ] doc-required
[ ] doc-not-needed
[ ] doc-complete

Review Expection

[ ] in-two-days
[x] weekly
[ ] free-time
[ ] whenever

Matching PR in forked repository

PR in forked repository:

+1

+1

+1

+1

source: gharchive/pull-request

authors: bladehliu leonrayang mervinkid zhangchuanqing5658

repo: cubefs/cubefs


text:
Build Documentation

The documentation to build this file and where to place the compiled file is lacking, and not intuitive to someone without experience in C++. I suggest adding expanded instructions on how to use the build script or what cmake commands should be used.

We are aware of this issue an work on providing pre-compiled binaries for linux also in Q2.
In the mean-time, https://github.com/cubert-hyperspectral/cuvis.python/issues/11 provides some further insights into what needs to be done at what step.
The build script is used by the automatic build process to provide pre-compiled versions for windows and is not designed to work on linux without modifications.

Automated script can be found here
There will be a more elegant way to do this in the future (precompiled pyil and install via pip).
I will leave this issue open until then.

authors: birkholz-cubert nhanson2 robertCubert


text:
Always prompt for missing nodes

电脑重启就提示节点丢失  重新安装完成正常使用  之后   下次电脑关机重开之后又提示节点丢失            When I reboot my computer, I get a message that the node is missing, I reinstall it and it works fine, and then the next time I shut down and reboot my computer, I get a message that the node is missing again.

Are you having: ERROR: This installation is not allowed in this security_level. Please contact the administrator.?
in .logs


text:
Revert "Exclude Rails 4.2 + ruby-head (2.6) build"

Summary
This reverts commit e4b7e5fd11f042c5fc532b9798a0ae5faf130e61.
Details
This PR restores Rails 4.2 + ruby-head (2.6) build.
BigDecimal.new has been replaced with deprecation rather than deletion.
% ruby -rbigdecimal -ve 'BigDecimal.new(42)'
ruby 2.6.0dev (2018-12-24 trunk 66524) [x86_64-darwin17]
-e:1: warning: BigDecimal.new is deprecated; use BigDecimal() method instead.

Motivation and Context
Follow up of https://github.com/cucumber/cucumber-rails/pull/400#issuecomment-447177153.
Checklist:

[ ] I've added tests for my code.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

The build failure of this PR is expected to be fixed by #403.

I rebased this PR and CI was fixed.

repo: cucumber/cucumber-rails

license: mit

license_source: bigquery


text:
Gherkin: Comments after tags not present in GherkinDocument.getCommentsList()

Summary
Comments on the same line as a tag cannot be retrieved from the list of comments.
Applies to tags on both Features and Scenarios.
Example:
# I can find this comment
@myTag #but not this one
Feature: Make comments available through the parser

# comment to be found
@myOtherTag #inaccessible comment
Scenario: If a tag is followed by a comment, the comment should be accessible through the parser.

Expected Behavior
All comments, including the ones following a tag on the same line, should be present in GherkinDocument.getCommentsList().
Current Behavior
Comments after a tag on the same line are inaccessible via the parser.
Context & Motivation
I want to import the complete file contents.
We often use comments after tags to simulate "tags with spaces", so these comments contain valuable information.
Your Environment

Version used: io.cucumber.gherkin 17.0.2
Operating System and version: Windows 10, JDK 11.0.7 amd64
Link to your project: private

Normally Gherkin allows you to make full line comments only.
Commenting after tags on the same line was specially hacked in because many IDEs allowed this and it caused confusion. But since the current Gherkin parser uses the lines as tokens, it is not easy to handle these "special" comments as normal ones. So I'm afraid there is no easy fix for that. I encourage everyone to NOT use this kind of commenting... I recommend using the @tags_with_spaces style instead.
Maybe @mpkorstanje can add something to this.

I agree these comments don't adhere to the grammar. Unfortunately, I have limited influence how the files are written.
As a workaround, we could have a flag that disables the hack that allows such comments.
Then they would be reported as parsing errors, and we at least know we're losing some content.

As this is deep in the grammar level, the usual cucumber settings cannot be applied there... so it is not easy to make a setting for that (the grammar/parser can be also used even without cucumber)

As trade-offs go I think we currently have the right one. The user experience should weight much higher then being able to build a a feature file from the AST.
Though I do see some room in the current AST to allow the comments on tag lines to be presented included. The location element uses both lines and columns. So perhaps the tag comments can be included as comments starting at a non-zero column?
  message Comment {
    // The location of the comment
    Location location = 1;
    // The text of the comment
    string text = 2;
  }

/**
 * Points to a line and a column in a text file
 */
message Location {
  uint32 line = 1;
  uint32 column = 2;
}

@mpkorstanje I think the AST would be able to handle the comments (BTW the normal comments do not necessarily start at column 0 or 1, but the column value indicates the position of the # sign within the line), the more problem is how the token scanner can feed the comment token back to the parser... Anyway. I totally agree with you that we have the right trade-off.

authors: enikao gasparnagy mpkorstanje

repo: cucumber/cucumber


text:
Related Tools: add tool "features2" to create HTML and PDF documentation from Cucumber features

add tool for creates HTML and PDF based documentation from Cucumber features

Hi @deovan,
Thanks for your making your first contribution to Cucumber, and welcome to the Cucumber committers team! You can now push directly to this repo and all other repos under the cucumber organization! 🍾
In return for this generous offer we hope you will:

✅ Continue to use branches and pull requests. When someone on the core team approves a pull request (yours or someone else's), you're welcome to merge it yourself.
💚 Commit to setting a good example by following and upholding our code of conduct in your interactions with other collaborators and users.
💬 Join the community Slack channel to meet the rest of the team and make yourself at home.
ℹ Don't feel obliged to help, just do what you can if you have the time and the energy.
🙋 Ask if you need anything. We're looking for feedback about how to make the project more welcoming, so please tell us!

On behalf of the Cucumber core team,
Aslak Hellesøy
Creator of Cucumber

authors: aslakhellesoy deovan

license: MIT


text:
Fix tests

🤔 What's changed?

Fixed a failing test around output from find getting .NET project paths
Refactored that code a bit to remove duplication of the buggy bit
Fixed a failing test for GPG key
Added a self-test for the test runner to make this less likely to happen again.
Refactored the test runner, while I had my attention on it

⚡ What's your motivation?
When we introduced shellcheck (#46), I inadvertently changed the test runner so it didn't actually pick up on failures anymore! I didn't notice this as the build was green and I didn't think to check it. This was fixed in https://github.com/cucumber/polyglot-release/commit/a2f92f5e5ad8e0490bb22acf0b774c582a7b315d but there's no guarantee it won't happen again.
Green build; working app!
🏷 What kind of change is this?

:bug: Bug fix (non-breaking change which fixes a defect)

♻ Anything particular you want feedback on?
Is there a simpler way to get find to return a clean relative path instead of ./Project.sln?
📋 Checklist:

[x] I agree to respect and uphold the Cucumber Community Code of Conduct
[x] I've changed the behaviour of the code

[x] I have added/updated tests to cover my changes.

This text was originally generated from a template, then edited by hand. You can modify the template here.

I broke protocol and just merged this, following the "doesn't make it any worse" principle.

Still happy to receive feedback though!

repo: cucumber/polyglot-release


text:
Defaults doesn't resolve struct values

Defaults doesn't resolve struct values. This issue first appeard in version 0.3.0-beta.2. The non-concrete value doesn't resolve even if its needed, for example in a function call.
What version of CUE are you using (cue version)?

$ cue version
cue version 0.3.0-beta.3 linux/amd64

Does this issue reproduce with the latest release?
yes
What did you do?
a:y: "y"

test1: *a.x | 1
test2: *a.y | 1

What did you expect to see?
a: {
    y: "y"
}
test1: 1
test2: "y"

What did you see instead?
Non concrete value, even if I used -c option.
a: {
    y: "y"
}
test1: a.x
test2: "y"

seems like a regression caused by a recent algorithmic change.

seems like a regression caused by a recent algorithmic change.

This issue has been migrated to https://github.com/cue-lang/cue/issues/700.
For more details about CUE's migration to a new home, please see https://github.com/cue-lang/cue/issues/1078.

authors: abraverm cueckoo mpvl

repo: cuelang/cue


text:
🛑 DDL Service is down

In eeada81, DDL Service (https://dl.culturecloud.gq) was down:

HTTP code: 0
Response time: 0 ms

Resolved: DDL Service is back up in 4811975.

repo: culturecloud/status


text:
Support cuTENSOR 0.2

This PR aims to support new APIs for tensor reduction added in cuTENSOR 0.2.
cuTENSOR C APIs for tensor reduction are exposed in cupy/cuda/cutensor.pyx. In addition, a bit abstracted API reduction() is also exposed in cupy/cutensor.py so that python developers can use it easily. An example is in cupy/example/cutensor.
Please note that you need to set an environment variable CUTENSOR_PATH when you build CuPy with cuTENSOR enabled.
$ cd (to where cupy is installed)
$ CUTENSOR_PATH=/path/to/cutensor python setup.py install

pfnCI, test this please.

Jenkins CI test (for commit 871bdb41c1130595e9e0003c8805913706edd096, target branch master) failed with status FAILURE.

Btw, cutensorGetCudartVersion API sounds nice to detect installation errors. I think it's good if other CUDA libraries provide the equivalent too. I sometimes heard users using cuDNN built for different version of CUDA and get errors like CUDNN_STATUS_INTERNAL_ERROR (which we are almost impossible to diagnose).

Thanks for your comments. I've just updated the PR. Could you check it again?

pfnCI, test this please.

Jenkins CI test (for commit c9d0def8c4eada8a579e469c11da0116bc205473, target branch master) succeeded!

Thank you for merging the PR!

authors: anaruse chainer-ci kmaehashi

repo: cupy/cupy


text:
Fix overflow of index calculation in random generator API

Closes #8241.
cc/ @emcastillo

/test mini

/test slow


text:
Phrase-level undo command

The problem
As we become more adventurous with long command phrases, it becomes more painful to undo a command phrase that has gone wrong.  We'd like to be able to undo everything done by a single phrase, even if it corresponds to many edits, potentially across multiple editors
The solution
We should probably implement this one as a separate extension.  Seems more generic than just for cursorless
M1: The basics

[ ] Take snapshot of document upon opening it, and after any change in an open editor
[ ] Any time talon sends pre-phrase signal, set a flag, and then any time a document changes mark the previous version so that we can snap back to it
[ ] When user issues a "phrase-level undo", extension will repeatedly issue undo commands in each editor that has had a change until its contents match snapshot.  Need some mechanism to keep this from getting out of hand if something is amiss and for whatever reason the document never matches the snapshot
[ ] Keep a sequence of these "phrase-level actions" so can undo multiple in a row

M2: Other types of actions

[ ] Keep track of editor selections and undo those
[ ] Keep track of editor visible ranges and undo scroll
[ ] Allow extensions to register reverse actions. That way can undo other side effects, make it easier to handle scroll, and not add spam to cursorless selection history tracking

M3 Unopened documents
Handle changes to documents that are not open in an editor

[ ] Extensions can signal that they are about to change a document that is not open
[ ] Any time a document changes that is not open, if it has been signalled by an extension, we handle it like an open editor, except that we can't use undo action; we have to just restore the snapshot
[ ] If a document changes that is not open and hasn't been signalled by an extension, we refuse to handle it as an undo because it could be a git command or something and we don't want to mess something up.  Or I guess we could warn

M4 Undo tree

[ ] Add an undo tree so that if user issues an undo, then does something, that creates a branch.  Can steal a display from a git log plugin or something

Coming from vim, I'm looking forward to the undo tree! I think the only pain point with Cursorless so far is the undo'ing an accidental command! It's surprisingly easy to have many words accidentally get inserted, and I'm used to being able to just press u to undo everything.
Thank you for Cursorless!

Coming from vim, I'm looking forward to the undo tree! I think the only pain point with Cursorless so far is the undo'ing an accidental command! It's surprisingly easy to have many words accidentally get inserted, and I'm used to being able to just press u to undo everything.

Yeah undo tree is def the biggest thing I miss from my vim days. You get drunk on the confidence it gives you

Thank you for Cursorless!

You're welcome! Glad you're finding it helpful ☺

authors: pokey tankorsmash

repo: cursorless-dev/cursorless


text:
Remove default/test parameters from simulation pipelines

Description

Remove default/test parameters from simulation pipelines
Remove "test" parameter from simulation pipelines
Add test for case when no parameters are enterred for sim
Clarify logging for when no parameters are enterred
Add docstrings for pipelines/simple and pipelines/common
Define test parameters within each pipeline test

Closes #222
Hygiene checklist

[x] Changelog entry
[x] Everything public has a Numpy-style docstring
(modules, public functions, classes, and public methods)
[x] Commit history is cleaned-up with minor changes squashed together
and descriptive commit messages following Tim Pope's style

Cute Animal Picture

Note:
The volume-limited arb CI doesn't pass for this PR or the current main.
In both cases, the strict equality test for per-run D (i.e., the D recorded at the beginning of each run) fails, so I suspect this merely reflects the fixes in #239

repo: curveresearch/curvesim


text:
fix: for test case failure due to file path

Fix for test case failure in auto compiled files

Pull request title looks good 👍!
If this pull request gets merged, it will cause a new release of the software. Example: If this project's latest release version is 1.0.0. If this pull request gets merged in, the next release of this project will be 1.0.1. This pull request is not a breaking change.
All merged pull requests will eventually get deployed. But some types of pull requests will trigger a deployment (such as features and bug fixes) while some pull requests will wait to get deployed until a later time.
To merge this pull request, add the label Ready to merge to this pull request and I'll merge it for you.

This project uses a special format for pull requests titles. Expand this section to learn more (expand by clicking the ᐅ symbol on the left side of this sentence)...

This project uses a special format for pull requests titles. Don't worry, it's easy!
This pull request title should be in this format:
<type>: short description of change being made

If your pull request introduces breaking changes to the code, use this format:
<type>!: short description of breaking change

where <type> is one of the following:

feat: - A feature is being added or modified by this pull request. Use this if you made any changes to any of the features of the project.

fix: - A bug is being fixed by this pull request. Use this if you made any fixes to bugs in the project.

docs: - This pull request is making documentation changes, only.

refactor: - A change was made that doesn't fix a bug or add a feature.

test: - Adds missing tests or fixes broken tests.

style: - Changes that do not effect the code (whitespace, linting, formatting, semi-colons, etc)

perf: - Changes improve performance of the code.

build: - Changes to the build system (maven, npm, gulp, etc)

ci: - Changes to the CI build system (Travis, GitHub Actions, Circle, etc)

chore: - Other changes to project that don't modify source code or test files.

revert: - Reverts a previous commit that was made.

Examples:
feat: edit profile photo
refactor!: remove deprecated v1 endpoints
build: update npm dependencies
style: run formatter

Need more examples? Want to learn more about this format? Check out the official docs.
Note: If your pull request does multiple things such as adding a feature and makes changes to the CI server and fixes some bugs then you might want to consider splitting this pull request up into multiple smaller pull requests.

:tada: This PR is included in version 1.0.1-alpha.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

authors: ami-aman ami-ci ami-oss-ci

repo: customerio/customerio-reactnative


text:
Precision annotation for bounding boxes, using SAM or SAM2

Actions before raising this issue

[X] I searched the existing issues and did not find anything similar.
[X] I read/searched the docs

Is your feature request related to a problem? Please describe.
Today, when we want to annotate objects precisely with bounding boxes, it is necessary to zoom in on the object to be almost pixel-perfect, especially for small objects.
This is extremely time-consuming.
The idea of this feature is to be able to annotate quickly and precisely with bounding boxes.
I've already proposed this feature on https://github.com/cvat-ai/cvat/pull/8243 and https://github.com/cvat-ai/cvat/issues/8231
Describe the solution you'd like
The idea is to make an imprecise bounding box around the object to be annotated. The bounding box is sent to the SAM or SAM2 model, which segments the main object from the bounding box it receives. Finally, the precise bounding box is recreated by taking the extremum coordinates at the top, left, bottom, right.
This would allow very quick and precise annotating, without having to zoom in on the image (very useful for precise annotation of small objects for example).
Describe alternatives you've considered
In my free time, I made a python script using this logic with SAM to make precision annotation, taking as input an annotation json (COCO format I think) and which output a json in the same format, with the precise bounding boxes recalculated.
I could make it available to you if necessary.
Additional context
Many other ideas can arise from this idea, such as:

Automatically correct the annotations of an imprecisely annotated dataset (whose bounding boxes are larger than the object). This dataset can come from the internet for example, as you can find plenty of them on Roboflow.

Quickly and roughly annotate a few objects (without correcting the precision), train a model which will be poorly performing in its metrics, but which will be capable of producing imprecise bounding boxes (larger than the object), and finally automatically correct the precision of these automatically generated bounding boxes. This would enable accurate self-labeling models to be obtained in a short time.

Hello,

Annotate masks/polygons using SAM/SAM2 (e.g. including bounding box as input, what was recently supported in https://github.com/cvat-ai/cvat/pull/8270)
Run shapes converter to convert annotated shapes to rectangles (on app.cvat.ai) or postprocess final polygons with your own scripts

So, reconsidering the feature that I am proposing, with the "shape converters" part, it would be interesting to have the "rectangle to SAM masks" option. Because currently, the "rectangle to mask" option creates a square mask, like the bbox...
This could make it possible to process and make accurate datasets with imprecise annotations in one go.

repo: cvat-ai/cvat


text:
Novel View Synthesis

I appreciate your work, but I have some simple problems.
1.When I use re10k to Novel View Synthesis, I get outputs/test/output/re10k/ file where has lots of files.

The photos in each folder are different, and there are three 256X256 color photos in each folder.
I want to know, are these three pictures the final output of the project? What do they represent respectively?
2.When I use re10k to Pose Estimation, the command
python -m src.eval_pose +experiment=re10k +evaluation=eval_pose checkpointing.load=./pretrained_weights/mixRe10kDl3dv.ckpt dataset/view_sampler@dataset.re10k.view_sampler=evaluation dataset.re10k.view_sampler.index_path=assets/evaluation_index_re10k.json，mixRe10kDl3dv.ckpt is need to be replaced by re10k.ckpt？
I use re10k.ckpt and program stuck here without moving.

The three images saved in each folder are novel views of our method. The one you show does not work well because it is a dynamic scene and we did not design it for that purpose.
Both mixRe10kDl3dv.ckpt and re10k.ckpt should work. In our paper, we also report results using these two checkpoints. The code is already printing out the AUC results, so it should have completed. I'm not sure why it didn't finish as expected, can you provide more details?

Thinks，it needs time.

authors: HHollowAU botaoye

repo: cvg/NoPoSplat


text:
Regarding - Decoders

Hello @Zzh2000 @pengsongyou,
First and foremost, thanks a lot for your NICE project :)
I have a question regarding the decoders,

Could you provide any further instruction/code for the Point Cloud Encoder-Decoder network that is trained
for obtaining the pretrained decoder part?

[I can't find/figure out] the part of the code where you fixed the weights for Mid-&Fine-level decoders, as given in the paper.

Any pointers will be helpful.

I am sorry if these questions are naive or if the answer already appears on the git but I could not find a clear solution.
Thank you very much.

Hi,
thanks for your interest in our work!

The Point Cloud Encoder-Decoder network is modified upon the ConvOnet, you can check https://github.com/autonomousvision/convolutional_occupancy_networks and our supplementary for more details.
There is no explicit code for fixing the decoder weights. We fix the weight just by not adding it to the optimizer.

Best,
Zihan

repo: cvg/nice-slam


text:
add space after attribute selectors

hey there! thanks so much for building this project. I noticed when using attribute selectors there's no space after the closing ] causing the browser to ignore the rule. this PR changes [my-id="1234"].class to [my-id="1234"] .class

Oh, good point. Thank you! :)

authors: cwdoh kauffecup


text:
Route potentiometer to IOREF instead of a fixed power rail

That is the actual purpose of IOREF, a value of 3.3V won't be a full ADC reading on a 5V Arduino if the pot is fixed to 3.3V max.

Same might make sense for other parts..

I think I should do the same with the thermistor. I'm not sure about the photodiode, though. What do you think @aShure ?

Yes. Simply all devices that feed into the ADC should have the same voltage output that the controller runs on. Less than the controller's voltage is possible too, but one would lose resolution and a scale in software is needed then.

great! I opened a new issue for the other ADC components

authors: aShure cwjpalmer


text:
Error when running

Hi,
I'm doing the following invocation:
python ./bin/pitch-shifter.py -s ./samples/0a7c2a8d_nohash_0.wav -o out.wav -c 4096 -e .9 -p -7 -b .8
I would attach the 0a7c2a8d_nohash_0.wav file mentioned, but .wav file types are not supported.  However, you can get it here.
When I run it the command, I get the following error:
Namespace(blend=0.8, chunk_size=4096, debug=False, no_resample=False, out='out.wav', overlap=0.9, pitch=-7.0, source='./samples/0a7c2a8d_nohash_0.wav')
Traceback (most recent call last):
  File "./bin/pitch-shifter.py", line 73, in <module>
    main(args)
  File "./bin/pitch-shifter.py", line 37, in main
    mono_samples = ps.stereoToMono(audio_samples)
  File "/Users/paulreiners/Dropbox/projects/pitch-shifter-py/pitchshifter/utilities.py", line 44, in stereoToMono
    [(sample[RIGHT] + sample[LEFT])/2 for sample in audio_samples],
TypeError: 'int' object has no attribute '__getitem__'

Any idea what I'm doing wrong here?  The command works fine with the sample file, sample1.wav.

Hey! is there any chance your wav is mono? I assume a stereo input and then convert it to mono because otherwise it becomes hard to run. This should be handled differently most likely

Hey I should have fixed this in the latest updates and I also added some additional examples. Actually committed the requirements.txt file. etc

Also I tested it against your file.

authors: cwoodall paul-reiners

repo: cwoodall/pitch-shifter-py


text:
More front-matters

If I create a new article , it will generate only with title date tags, can it be possible to have more front-matters, or it will be better to have cumtomization!
Now:

What I want:

Maybe you could try create a new article command, It will read scaffolds folder, all your template will list.
Unfortunately, it is only support title and date variables.

我才发现是成都的老哥 哈哈哈哈 那就说中文了
我说的东西 以后能实现吗？ 更新一下？

能不能准确的描述一下你的需求？我没太理解。。。
现在的模板能不能满足你的需求？

现在模板只有title date tags 这三个，我希望能有多一点的选项，或者可以自定义就更好了

hexo 的模板功能有没有用过？可以自定义的，放在 scaffolds 文件夹里面，然后用 create a new article 命令就可以看到模板名称了

Hexo 模板

嗯嗯 好的  麻烦你了  谢谢

没事~


text:
Device not supported

Your app is not working in my device.
App Version: 2.2.0 (20)
Build Type: release
Manufacturer: Xiaomi
Model: 21091116I
Device: pissarroin
Light Levels: 1
Software: Android 13 (33)

Thanks for the report.
Your phone will be excluded.


text:
Create CONTRIBUTING.md

Linked to cyberark/community#30

@izgeri Done

repo: cyberark/ansible-conjur-host-identity


text:
Secrets Provider (P2) - Research, Update and Removal of Deployment

A valid solution requires that the Secrets provider be decoupled from customer applications (AKA not sitting with each app in same pod).
As part of this research, we also need to evaluate the lifecycle for the solution, supporting the upgrade and removal of the secrets provider deployment.
Solution doc: https://ca-il-confluence.il.cyber-ark.com/pages/viewpage.action?pageId=319161469#/

Due to the volume of potential apps running on > 2000 clusters, my company is definitely interested in this.

authors: cbarga sigalsax


text:
"SyntaxError: invalid syntax" when running any command with "gclient"

I was attempting to test out the WepGPU implementation Dawn, but I've run into an issue. When I run gclient sync, python fails with a syntax error.
gclient sync
Traceback (most recent call last):
  File "/usr/local/bin/gclient", line 6, in <module>
    from depot_tools import gclient
  File "/usr/local/lib/python3.6/dist-packages/depot_tools/gclient.py", line 199
    print 'Overwriting Var("webkit_trunk") with %s' % new_url
                                                  ^
SyntaxError: invalid syntax

I installed gclient with the following command:
sudo pip3 install gclient
The directory '/home/user/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
The directory '/home/user/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.
Collecting gclient
  Downloading https://files.pythonhosted.org/packages/a6/63/c87ffca3801f7f48011c38ae9fc3bffca43d0a8ec58f4fe4e05458d2c35f/gclient-0.7.2.tar.gz (328kB)
    100% |████████████████████████████████| 337kB 495kB/s
Installing collected packages: gclient
  Running setup.py install for gclient ... done
Successfully installed gclient-0.7.2

I'm running Linux Mint 19.1. Running pip3 --version gives me pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6).

This package is seriously out of date. Someone should take it over on pypi.

repo: cybertk/gclient


text:
ManyToMany error Transaction can't be finished. Some relations can't be resolved🐛

What happened?

У меня есть две сущности `User` и `Tag` со связью `ManyToMany`.
Если в обоих сущностях указать связь ManyToMany, то возникает ошибка  Transaction can't be finished. Some relations can't be resolved
Для воспроизведения ошибки, я взял ваш тест Cycle\ORM\Tests\Functional\Driver\Common\Relation\ManyToMany\ManyToManyRelationTest и добавил в метод getSchemaArray() связь ManyToMany для Tag::class:

I have two entities User and Tag related with the ManyToMany relation
If the ManyToMany relation is specified in both entities, then an error will be thrown with the message Transaction can't be finished. Some relations can't be resolved
To reproduce that case you can use the Cycle\ORM\Tests\Functional\Driver\Common\Relation\ManyToMany\ManyToManyRelationTest test case and add the ManyToMany relation for the Tag::class (in the getSchemaArray() method) as below:
         Tag::class => [
                ...
                Schema::RELATIONS => [
                    'users' => [
                        Relation::TYPE => Relation::MANY_TO_MANY,
                        Relation::TARGET => User::class,
                        Relation::SCHEMA => [
                            Relation::CASCADE => true,
                            Relation::THROUGH_ENTITY => TagContext::class,
                            Relation::INNER_KEY => 'id',
                            Relation::OUTER_KEY => 'id',
                            Relation::THROUGH_INNER_KEY => 'tag_id',
                            Relation::THROUGH_OUTER_KEY => 'user_id',
                        ],
                    ],
                ],
            ],

Результат выполнения теста `testUnlinkManyToManyAndReplaceSome()`:

After  testUnlinkManyToManyAndReplaceSome() calling you will see that error:
Cycle\ORM\Exception\TransactionException : Transaction can't be finished. Some relations can't be resolved:
Create new `tag_context`
 - tag.users:tag_context (Cycle\ORM\Relation\ShadowBelongsTo)
 /app/vendor/cycle/orm/src/Exception/TransactionException.php:40
 /app/vendor/cycle/orm/src/Transaction/UnitOfWork.php:104
 /app/vendor/cycle/orm/src/Transaction.php:48
 /app/app/src/Example/Functional/Driver/Common/BaseTest.php:248
 /app/app/src/Example/Functional/Driver/Common/Relation/ManyToMany/ManyToManyRelationTest.php:403

Version
ORM 2.0.0
PHP 8.0

I have the same issue. It works if I use as in the documentation, but if I want to get the users from a Tag, I have to add the ManyToMany relation to Tag entity. I can query the relation, but when I want to store a new User with Tag, then I get the following error:
Transaction can't be finished. Some relations can't be resolved:
  Create new `userTag`
   - tag.users:userTag (Cycle\ORM\Relation\ShadowBelongsTo)

@albertborsos can you show the ORM Schema (relations tag.users and users.tag)?

I just updated my error for this ticket 😊  For real, I have articles and tags. here is my schema.php
<?php

declare(strict_types=1);

use Cycle\ORM\Relation;
use Cycle\ORM\SchemaInterface as Schema;

return [
    'article' => [
        Schema::ENTITY => 'App\\Entity\\Article',
        Schema::MAPPER => 'Cycle\\ORM\\Mapper\\Mapper',
        Schema::SOURCE => 'Cycle\\ORM\\Select\\Source',
        Schema::REPOSITORY => 'App\\Repository\\ArticleRepository',
        Schema::DATABASE => 'database',
        Schema::TABLE => 'article',
        Schema::PRIMARY_KEY => ['id'],
        Schema::FIND_BY_KEYS => ['id'],
        Schema::COLUMNS => [
            'id' => 'id',
            'externalId' => 'external_id',
            'source' => 'source',
            'title' => 'title',
            'link' => 'link',
            'imageUrl' => 'image_url',
            'publishedAt' => 'published_at',
            'createdAt' => 'created_at',
        ],
        Schema::RELATIONS => [
            'tags' => [
                Relation::TYPE => Relation::MANY_TO_MANY,
                Relation::TARGET => 'tag',
                Relation::LOAD => Relation::LOAD_PROMISE,
                Relation::SCHEMA => [
                    Relation::CASCADE => true,
                    Relation::NULLABLE => false,
                    Relation::WHERE => [],
                    Relation::ORDER_BY => [],
                    Relation::INNER_KEY => ['id'],
                    Relation::OUTER_KEY => ['id'],
                    Relation::THROUGH_ENTITY => 'articleTag',
                    Relation::THROUGH_INNER_KEY => 'article_id',
                    Relation::THROUGH_OUTER_KEY => 'tag_id',
                    Relation::THROUGH_WHERE => [],
                    '4' => null,
                ],
            ],
        ],
        Schema::SCOPE => null,
        Schema::TYPECAST => [
            'id' => 'int',
            'publishedAt' => 'datetime',
            'createdAt' => 'datetime',
        ],
        Schema::SCHEMA => [],
        Schema::LISTENERS => [
            [
                'Cycle\\ORM\\Entity\\Behavior\\Listener\\CreatedAt',
                [
                    'field' => 'createdAt',
                ],
            ],
        ],
        Schema::TYPECAST_HANDLER => null,
    ],
    'articleTag' => [
        Schema::ENTITY => 'App\\Entity\\ArticleTag',
        Schema::MAPPER => 'Cycle\\ORM\\Mapper\\Mapper',
        Schema::SOURCE => 'Cycle\\ORM\\Select\\Source',
        Schema::REPOSITORY => 'Cycle\\ORM\\Select\\Repository',
        Schema::DATABASE => 'database',
        Schema::TABLE => 'article_tag',
        Schema::PRIMARY_KEY => ['id'],
        Schema::FIND_BY_KEYS => ['id'],
        Schema::COLUMNS => [
            'id' => 'id',
            'createdAt' => 'created_at',
            'article_id' => 'article_id',
            'tag_id' => 'tag_id',
        ],
        Schema::RELATIONS => [],
        Schema::SCOPE => null,
        Schema::TYPECAST => [
            'id' => 'int',
            'createdAt' => 'datetime',
            'article_id' => 'int',
            'tag_id' => 'int',
        ],
        Schema::SCHEMA => [],
        Schema::LISTENERS => [
            [
                'Cycle\\ORM\\Entity\\Behavior\\Listener\\CreatedAt',
                [
                    'field' => 'createdAt',
                ],
            ],
        ],
        Schema::TYPECAST_HANDLER => null,
    ],
    'tag' => [
        Schema::ENTITY => 'App\\Entity\\Tag',
        Schema::MAPPER => 'Cycle\\ORM\\Mapper\\Mapper',
        Schema::SOURCE => 'Cycle\\ORM\\Select\\Source',
        Schema::REPOSITORY => 'App\\Repository\\TagRepository',
        Schema::DATABASE => 'database',
        Schema::TABLE => 'tag',
        Schema::PRIMARY_KEY => ['id'],
        Schema::FIND_BY_KEYS => ['id'],
        Schema::COLUMNS => [
            'id' => 'id',
            'name' => 'name',
        ],
        Schema::RELATIONS => [
            'articles' => [
                Relation::TYPE => Relation::MANY_TO_MANY,
                Relation::TARGET => 'article',
                Relation::LOAD => Relation::LOAD_PROMISE,
                Relation::SCHEMA => [
                    Relation::CASCADE => true,
                    Relation::NULLABLE => false,
                    Relation::WHERE => [],
                    Relation::ORDER_BY => [],
                    Relation::INNER_KEY => ['id'],
                    Relation::OUTER_KEY => ['id'],
                    Relation::THROUGH_ENTITY => 'articleTag',
                    Relation::THROUGH_INNER_KEY => 'tag_id',
                    Relation::THROUGH_OUTER_KEY => 'article_id',
                    Relation::THROUGH_WHERE => [],
                    '4' => null,
                ],
            ],
        ],
        Schema::SCOPE => null,
        Schema::TYPECAST => [
            'id' => 'int',
        ],
        Schema::SCHEMA => [],
        Schema::TYPECAST_HANDLER => null,
    ],
];

And the error what I got:
In TransactionException.php line 40:

  Transaction can't be finished. Some relations can't be resolved:
  Create new `articleTag`
   - tag.articles:articleTag (Cycle\ORM\Relation\ShadowBelongsTo)

#0 /var/www/app/vendor/cycle/orm/src/Transaction/UnitOfWork.php(104): Cycle\ORM\Exception\TransactionException::unresolvedRelations(Array, Object(Cycle\ORM\Service\Implementation\RelationProvider))
#1 /var/www/app/vendor/cycle/orm/src/Transaction.php(48): Cycle\ORM\Transaction\UnitOfWork->run()
#2 /var/www/app/vendor/yiisoft/yii-cycle/src/Data/Writer/EntityWriter.php(30): Cycle\ORM\Transaction->run()

@albertborsos can you add this value in the schema?
$schema['tag'][Schema::RELATIONS]['articles'][Relation::SCHEMA][Relation::INVERSION] = 'tags';

@roxblnfk I get the same error.

@roxblnfk is there any way I can configure this inversion value via php attributes? I did not find it in the documentations. Thanks

@roxblnfk is there any way I can configure this inversion value via php attributes? I did not find it in the documentations. Thanks

Right now there is no simple way yet
Hard way: you can add custom SchemaModifier implementation

Thanks!
With this modification:
    public function modifySchema(array &$schema): void
    {
        $this->merge($this->schema['value'], $schema);
    }

it generates the expected schema, but still not works.
I tried to add the inverted inversion to Article, but I still get the same error.

@roxblnfk I found out what was the issue.
I use yii3 and the yiisoft/yii-demo app uses Yiisoft\Yii\Cycle\Data\Writer\EntityWriter class from yiisoft/yii-cycle:2.0.x-dev and EntityWriter use Cycle\ORM\Transaction which is deprecated...

The real exception occured in src/Transaction/Pool.php:L261 with Pool has gone into an infinite loop. exception message
Can I help to resolve this with some data from xdebug?
I can send more details from these objects.
$item = {Cycle\ORM\Transaction\Tuple} [8]
$pool = {SplObjectStorage} [1]
$entity = {App\Entity\ArticleTag Cycle ORM Proxy} [3]
$this = {Cycle\ORM\Transaction\Pool} [9]
$tuple = {Cycle\ORM\Transaction\Tuple} [8]
$stage = {int} 2
$hasUnresolved = true

Can I help to resolve this with some data from xdebug?

If you can make a PR with a test that reproduces the problem, that would be a great help

the same problem

Can you confirm that bug has been fixed?

@roxblnfk looks good now.

authors: TiaNex-Com albertborsos only-viktor roxblnfk

repo: cycle/orm


text:
Improve installation documentation

It's not clear that you first need to clone the project and cd into it before running the go get mentioned here.
I wanted to install it, and after reading the docs, I simply copy-pasted the given command, and got the following error:
$ go mod edit -replace github.com/hashicorp/terraform=github.com/cycloidio/terraform@v1.1.9-cy && go get github.com/cycloidio/terracost
go: go.mod file not found in current directory or any parent directory; see 'go help modules'

Then I figured out I may need to clone the repo first and cd into it, which did the trick.
(Also, I know it's a bit the cherry on top of the cake, but providing a brew formula would be awesome for macOS users 😅)

Closing as I realized it's a "pure" go package. Somehow I didn't realize that, for some reason I expected to be able to run it in the CLI (that said, it would make testing the library so much easier!)

(that said, it would make testing the library so much easier!)

Yes that's one of the thing I'm working on, to have a CLI to be able to use it directly if need be

authors: Thomas-lhuillier xescugc

repo: cycloidio/terracost


text:
WiFi not available

Stratux version:

Stratux config:
SDR

[ ] single
[ x] dual

GPS

[ x] yes
[ ] no
type:

AHRS

[ ] yes
[ x] no

power source:
Power Bank
usb cable:

EFB app and version: (e.g., WingX Pro7 8.6.2)
Fore Flight
EFB platform: (e.g., iOS 9.2)
iOS 11
EFB hardware: (e.g., iPad Mini 2)
iPad New

Description of your issue:
Yesterday while flying everything was fine. I was connected and receiving weather and traffic. The red LED was lit and the green LED was flashing indicating a WiFi connection. In the second hour of flight the Stratux fell off WiFi. The green LED was steady on and I am now unable to see it in the list of available WiFi devices. Is this fixable or a hardware issue that needs to be replaced?

I believe a flashing green light IS BAD, at least in the more recent versions of the Stratux software. There is also a flashing green light on most GPSs when it has a fix. Make sure that's not what you're seeing flashing.

Current status is solid green and red. there is no flashing. When powered up both lights are steady on. When I try to connect via WiFi the stratux is no longer listed. It was when I started the flight then it dropped off and I have been unable to connect again with any device. I have not updated any software on the Stratux. Thanks so much for your help.

When something similar happened to me, it turned out the SD card was
corrupted and broken. I could read the directory, but I could not reflash
it. I had to buy a new SD card. Once I installed that, my Stratux worked
normally again.
On Thu, Dec 14, 2017 at 11:10 AM, dmireles24 notifications@github.com
wrote:

Current status is solid green and red. there is no flashing. When powered
up both lights are steady on. When I try to connect via WiFi the stratux is
no longer listed. It was when I started the flight then it dropped off and
I have been unable to connect again with any device. I have not updated any
software on the Stratux. Thanks so much for your help.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cyoung/stratux/issues/687#issuecomment-351775486, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANY40bwy02B_PpoHUwMNZDfSyUoyp3Brks5tAVZ6gaJpZM4RBHGo
.

ill try the sd card idea. I just dont want to buy a new Raspberry and it be the card.

Okay I just reflashed the SD card. All is working well. Thanks for the help.

repo: cyoung/stratux


text:
Add latest chrome 86 and node 14

Follow up on #382. Adding a browsers image with the latest node and chrome 86.

I think there is already a newer version of Node, so I will close this for now

authors: bahmutov jakubzitny

repo: cypress-io/cypress-docker-images


text:
Some questions about hass-livebox-component

Hi,
I'm using hass-livebox-component and have a few questions.
I did a basic install of hass-livebox-component. No problem, the Livebox component entities have been created on HA.
Orange-Livebox integration also created two entities for my PC:

device_tracker.mypc
switch.desktop_mypc_wan_access

My questions are:

Why did Orange Livebox integration create these two entities for my PC?
Why not for other wifi devices connected to the livebox?
I want to track my smartphone, at-home and not-at-home. How can I create a HA device_tracker entity for my smartphone like hass-livebox-component did automatically for my PC?

Thanks for your help.

Why did Orange Livebox integration create these two entities for my PC?
The first object allows you to track your device and the second authorizes or not the equipment to access the Internet
Why not for other wifi devices connected to the livebox?
Now the livebox goes back to all WiFi or Wired equipment, you should see your phone. All devices you see in the box must be seen in HA
If you don't see your phone, check to see if you see it in your box and if so. Give me your diagnostic file

Hi,
Sorry, I'm an idiot!
Behind my livebox I have an ASUS router in access point mode! My wifi devices are connected to my ASUS router not to my Livebox...
Thanks for your help.

authors: cyr-ius monpelaud

repo: cyr-ius/hass-livebox-component


text:
Connection SDK library is not using shared scripting engine

This feature was added later because every call into Photoshop was executing a fresh new script engine which also means executing all startup scripts and this causes about 80ms delay per each call. But connection SDK is slower anyway per one call. CEP panel is a bit faster.
You can compare python photoshop protocol with connection made by adobe.
Script type of message has constant 2 and script in shared engine 10. And in python library, this is missing.
https://github.com/kyamagu/photoshop-connection/blob/master/src/photoshop/protocol.py#L17
https://github.com/adobe-photoshop/generator-core/blob/24a2c4e38aef79adb42869f200778ab52de4ef36/lib/photoshop.js#L67

Thanks a lot for the heads up. Adding a photoshop tag in case there's someone able to improve the connection to Photoshop.

One more thing... using not shared engine also means that all variables in the global PS scripting context will be wiped out once call is done. Otherwise, you could cache there something useful for all your calls.

authors: cyrildiagne jardicc

repo: cyrildiagne/ar-cutpaste


text:
Implement reversed C++ iteration

Normal C++ iteration using the .begin/.end methods is supported in for-loops. Reversed iteration witn .rbegin/.rend should be supported using the reversed() function.

implement transformation in Optimize.py, IterationTransform._transform_reversed_iteration(), maybe setting a flag attribute that changes the direction of the IterationNode.
Generate the correct C++ code from IteratorNode in ExprNodes.py.
Add tests in tests/run/cpp_iterators.pyx.

I'm willing to attempt to implement this Issue. However, I'm still pretty new to cython development. Could you give me a few more thoughts, pointers, or examples that would help me understand how to go about it? I'd especially be interested in what the tests to go into tests/run/cpp_iterators.cpp would look like since I don't think the file currently exists.

Sorry, wrong file name. I updated the description a little, but would suggest that you work on your other pull request first.

I absolutely will work on the other one first. Just trying to gather a few opportunities. I have a vested interest in better understanding and contributing to cython's development.

Closed in https://github.com/cython/cython/commit/d329339ba05ac76e0a83f539f173996e80cc89e1

authors: Yoshi325 da-woods scoder

repo: cython/cython


text:
[DEV] Support for public version identifiers (PEP440)

Is your feature request related to a problem? Please describe.
Hi,
Downstream projects using Cython as a development dependencies might need to check Cython version for nightly build. Currently, there is no way to programmatically assess if the an installed version of Cython comes from an (alpha) release or from the source because the version number is not incorporating this information:
https://github.com/cython/cython/blob/ac56a661b6d670b69f24fb92408dd852a583b08d/Cython/Shadow.py#L4
PEP 440 introduced public version identifiers and in particular Development release segment which allow knowing programmatically that packages have been installed from a development version.
Describe the solution you'd like.
Use public version identifiers with a Development release segment.
That is change:
https://github.com/cython/cython/blob/ac56a661b6d670b69f24fb92408dd852a583b08d/Cython/Shadow.py#L4
for:
 __version__ = "3.0.0a12.dev0"

https://github.com/cython/cython/pull/5205/ has been opened accordingly.
Describe alternatives you've considered.
None.
Additional context
For scikit-learn, this limitation was recently met in https://github.com/scikit-learn/scikit-learn/pull/25300#discussion_r1064966103.

This broke installing Cython from the master branch e.g. with:
pip install https://github.com/cython/cython/archive/master.zip

I think similar errors can be seen in the CI.
It does not look like Cython knows what to do with dev0
Full traceback:
Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-req-build-nw3q1z65/setup.py", line 317, in <module>
          run_build()
        File "/tmp/pip-req-build-nw3q1z65/setup.py", line 245, in run_build
          setup(
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/__init__.py", line 87, in setup
          return distutils.core.setup(**attrs)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 148, in setup
          return run_commands(dist)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/core.py", line 163, in run_commands
          dist.run_commands()
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 967, in run_commands
          self.run_command(cmd)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/dist.py", line 1214, in run_command
          super().run_command(command)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
          cmd_obj.run()
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/wheel/bdist_wheel.py", line 299, in run
          self.run_command('build')
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/dist.py", line 1214, in run_command
          super().run_command(command)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
          cmd_obj.run()
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/command/build.py", line 136, in run
          self.run_command(cmd_name)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/cmd.py", line 313, in run_command
          self.distribution.run_command(command)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/dist.py", line 1214, in run_command
          super().run_command(command)
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/dist.py", line 986, in run_command
          cmd_obj.run()
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 339, in run
          self.build_extensions()
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 448, in build_extensions
          self._build_extensions_serial()
        File "/home/lesteve/miniconda3/envs/scratch/lib/python3.9/site-packages/setuptools/_distutils/command/build_ext.py", line 473, in _build_extensions_serial
          self.build_extension(ext)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Distutils/build_ext.py", line 122, in build_extension
          new_ext = cythonize(
        File "/tmp/pip-req-build-nw3q1z65/Cython/Build/Dependencies.py", line 1134, in cythonize
          cythonize_one(*args)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Build/Dependencies.py", line 1280, in cythonize_one
          result = compile_single(pyx_file, options, full_module_name=full_module_name)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Compiler/Main.py", line 604, in compile_single
          return run_pipeline(source, options, full_module_name)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Compiler/Main.py", line 528, in run_pipeline
          err, enddata = Pipeline.run_pipeline(pipeline, source)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Compiler/Pipeline.py", line 397, in run_pipeline
          data = run(phase, data)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Compiler/Pipeline.py", line 374, in run
          return phase(data)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Compiler/Pipeline.py", line 52, in generate_pyx_code_stage
          module_node.process_implementation(options, result)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Compiler/ModuleNode.py", line 206, in process_implementation
          self.generate_c_code(env, options, result)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Compiler/ModuleNode.py", line 475, in generate_c_code
          self.generate_module_preamble(env, options, modules, result.embedded_metadata, h_code)
        File "/tmp/pip-req-build-nw3q1z65/Cython/Compiler/ModuleNode.py", line 783, in generate_module_preamble
          code.putln('#define CYTHON_HEX_VERSION %s' % build_hex_version(__version__))
        File "/tmp/pip-req-build-nw3q1z65/Cython/Utils.py", line 624, in build_hex_version
          digits.append(int(digit))
      ValueError: invalid literal for int() with base 10: 'dev0'

authors: jjerphan lesteve


text:
[BUG] cython does not build with cpython main branch.

Describe the bug
Cython fails to build itself on cpython main:
  gcc -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/home/tcaswell/.virtualenvs/bleeding/include -I/home/tcaswell/.pybuild/bleeding/include/python3.12 -c /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c -o build/temp.linux-x86_64-cpython-312/home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.o
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c: In function ‘__pyx_f_6Cython_8Compiler_7Parsing_p_dict_or_set_maker’:
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:31385:9: warning: ‘Py_OptimizeFlag’ is deprecated [-Wdeprecated-declarations]
  31385 |         if (unlikely(!Py_OptimizeFlag)) {
        |         ^~
  In file included from /home/tcaswell/.pybuild/bleeding/include/python3.12/Python.h:48,
                   from /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:31:
  /home/tcaswell/.pybuild/bleeding/include/python3.12/cpython/pydebug.h:13:37: note: declared here
     13 | Py_DEPRECATED(3.12) PyAPI_DATA(int) Py_OptimizeFlag;
        |                                     ^~~~~~~~~~~~~~~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c: In function ‘__Pyx_PyErr_ExceptionMatchesInState’:
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84939:32: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  84939 |     PyObject *exc_type = tstate->curexc_type;
        |                                ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c: In function ‘__Pyx_ErrRestoreInState’:
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84952:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  84952 |     tmp_type = tstate->curexc_type;
        |                      ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84953:23: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_value’
  84953 |     tmp_value = tstate->curexc_value;
        |                       ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84954:20: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  84954 |     tmp_tb = tstate->curexc_traceback;
        |                    ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84955:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  84955 |     tstate->curexc_type = type;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84956:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_value’
  84956 |     tstate->curexc_value = value;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84957:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  84957 |     tstate->curexc_traceback = tb;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c: In function ‘__Pyx_ErrFetchInState’:
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84963:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  84963 |     *type = tstate->curexc_type;
        |                   ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84964:20: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_value’
  84964 |     *value = tstate->curexc_value;
        |                    ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84965:17: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  84965 |     *tb = tstate->curexc_traceback;
        |                 ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84966:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  84966 |     tstate->curexc_type = 0;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84967:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_value’
  84967 |     tstate->curexc_value = 0;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:84968:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  84968 |     tstate->curexc_traceback = 0;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c: In function ‘__Pyx_IterFinish’:
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:85724:32: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  85724 |     PyObject* exc_type = tstate->curexc_type;
        |                                ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:85728:31: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_value’
  85728 |             exc_value = tstate->curexc_value;
        |                               ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:85729:28: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  85729 |             exc_tb = tstate->curexc_traceback;
        |                            ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:85730:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  85730 |             tstate->curexc_type = 0;
        |                   ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:85731:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_value’
  85731 |             tstate->curexc_value = 0;
        |                   ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:85732:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  85732 |             tstate->curexc_traceback = 0;
        |                   ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c: In function ‘__Pyx__GetException’:
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86515:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  86515 |     local_type = tstate->curexc_type;
        |                        ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86516:25: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_value’
  86516 |     local_value = tstate->curexc_value;
        |                         ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86517:22: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  86517 |     local_tb = tstate->curexc_traceback;
        |                      ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86518:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  86518 |     tstate->curexc_type = 0;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86519:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_value’
  86519 |     tstate->curexc_value = 0;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86520:11: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  86520 |     tstate->curexc_traceback = 0;
        |           ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86526:24: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_type’
  86526 |     if (unlikely(tstate->curexc_type))
        |                        ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:1279:43: note: in definition of macro ‘unlikely’
   1279 |   #define unlikely(x) __builtin_expect(!!(x), 0)
        |                                           ^
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c: In function ‘__Pyx_Raise’:
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86861:34: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  86861 |         PyObject* tmp_tb = tstate->curexc_traceback;
        |                                  ^~
  /home/tcaswell/source/p/cython/cython/Cython/Compiler/Parsing.c:86864:19: error: ‘PyThreadState’ {aka ‘struct _ts’} has no member named ‘curexc_traceback’
  86864 |             tstate->curexc_traceback = tb;
        |                   ^~
  error: command '/lib/ccache/bin/gcc' failed with exit code 1

I believe that this is caused by feec49c40736fc05626a183a8d14c4ebbea5ae28 via https://github.com/python/cpython/pull/101607 working on https://github.com/python/cpython/issues/101578 .  Rolling back to 027adf42cd85db41fee05b0a40d89ef822876c97 (the previous commit) does fix cython building itself.
Code to reproduce the behaviour:
pip inst -v --no-build-isolation .

Expected behaviour
No response
Environment
OS: [e.g. Linux, Windows, macOS] linux
Python version [e.g. 3.10.2] main (2f62a5da949cd368a9498e6a03e700f4629fa97f)
Cython version [e.g. 3.0.0a11] master (94bea6677)
Additional context
No response

This is now blocking building Cython with Python 3.12.0a6.

(This also affects building other packages, not just Cython itself.)

The footprint of this in cython seems to be:
$ ack '.curexc'
Cython/Compiler/Nodes.py
10230:# type/value/tb in PyThreadState->curexc_*.  When being caught by an
10231:# 'except' statement, curexc_* is moved over to exc_* by
10248:    # the exception from tstate->curexc_* to tstate->exc_*, which prevents

Cython/Debugger/libpython.py
2507:                inf_type = tstate['curexc_type']
2508:                inf_value = tstate['curexc_value']

Cython/Utility/Exceptions.c
4:// type/value/tb in PyThreadState->curexc_*.  When being caught by an
5:// 'except' statement, curexc_* is moved over to exc_* by
32:#define __Pyx_PyErr_Occurred()  $local_tstate_cname->curexc_type
69:    PyObject *exc_type = tstate->curexc_type;
113:    tmp_type = tstate->curexc_type;
114:    tmp_value = tstate->curexc_value;
115:    tmp_tb = tstate->curexc_traceback;
116:    tstate->curexc_type = type;
117:    tstate->curexc_value = value;
118:    tstate->curexc_traceback = tb;
125:    *type = tstate->curexc_type;
126:    *value = tstate->curexc_value;
127:    *tb = tstate->curexc_traceback;
128:    tstate->curexc_type = 0;
129:    tstate->curexc_value = 0;
130:    tstate->curexc_traceback = 0;
306:        PyObject* tmp_tb = tstate->curexc_traceback;
309:            tstate->curexc_traceback = tb;
374:    local_type = tstate->curexc_type;
375:    local_value = tstate->curexc_value;
376:    local_tb = tstate->curexc_traceback;
377:    tstate->curexc_type = 0;
378:    tstate->curexc_value = 0;
379:    tstate->curexc_traceback = 0;
385:    if (unlikely(tstate->curexc_type))

Cython/Utility/ObjectHandling.c
242:    PyObject* exc_type = tstate->curexc_type;
246:            exc_value = tstate->curexc_value;
247:            exc_tb = tstate->curexc_traceback;
248:            tstate->curexc_type = 0;
249:            tstate->curexc_value = 0;
250:            tstate->curexc_traceback = 0;

and it is all behind a CYTHON_FAST_THREAD_STATE guard.
I started to look at how to fix this, but did not make it very far.

authors: hrnciar hroncok tacaswell