text:
Setting "Press state" to true does not trigger

Hi there!
First of all thanks a lot for this adapter! unfortunately, this does not work for with my system. Or i am doing something wrong.
Changing the state does not trigger any movement of the Switchbot bot arm. BLE identifies device correctly so far. Using Admin 5. any issues known?
Thanks upfront!

Hi @1tb2
have you already checked the log and the adapter settings?

Wait while scanning devices (seconds) / Wartezeit während der Gerätesuche (Sekunden)
Delay while retrying to  (milliseconds) / Auf Geräte warten (Millisekunden)

You may need to change these values

Hi mrbungle64, hi all,
thanks for the feedback. today I played around with the settings but nothing changed. I reinstalled and changed settings on proxmox vm. but nothing changed. finally I installed "Bluetooth-Niedrigenergie (BLE)" just to check if all functions are available and everything works.
--> With parallel installation on "BLE"-Adapter, also the Switchbot is working. as soon I uninstall or stop the adapter in iobroker. Switchbot is not movin anymore.
This of course is not a real fix but maybe it helps to understand the root cause. at least a workaround...
Thanks for support!
1TB2

Hi mrbungle64, hi all,

Hi @1tb2
thanks for the information 👍🏻

thanks for the feedback. today I played around with the settings but nothing changed. I reinstalled and changed settings on proxmox vm. but nothing changed. finally I installed "Bluetooth-Niedrigenergie (BLE)" just to check if all functions are available and everything works.
--> With parallel installation on "BLE"-Adapter, also the Switchbot is working. as soon I uninstall or stop the adapter in iobroker. Switchbot is not movin anymore.

Sounds very interesting.
I also had already installed the ble adapter but without a running instance (therefore the instance was not started)
Is it reproducible that starting and stopping the ble adapter affects whether it is possible to move the Switchbot "Bot"?

This of course is not a real fix but maybe it helps to understand the root cause. at least a workaround...
Thanks for support!
1TB2

Gleiches Problem hier.
Gerät wird angezeigt aber bei "Tasten-Druck" keinerlei Reaktion oder Funktion.

@1tb2
Does the problem still exist?

Is it reproducible that starting and stopping the ble adapter affects whether it is possible to move the Switchbot "Bot"?

Still waiting for feedback 😉

@m0uh85

Gleiches Problem hier. Gerät wird angezeigt aber bei "Tasten-Druck" keinerlei Reaktion oder Funktion.

Gibt es ein paar mehr Infos für mich? 😉

@m0uh85

Gleiches Problem hier. Gerät wird angezeigt aber bei "Tasten-Druck" keinerlei Reaktion oder Funktion.

Gibt es ein paar mehr Infos für mich? 😉

Gerne...  doch :)
Version: 0.2.3
Node.js v12.22.7
also Objekte sind alle richtig angelegt und erreichbar.... betätige ich unter Control bei "Press" den Button - tut sich nix
Zeitstempel ändert sich aber unter Bestätigt der Zeitstempel bleibt gleich.
Habe auch probiert den BLE Adapter mal zu installieren, aber gleiches Problem.
LOG:

switchbot-ble.0
2021-11-15 18:36:55.595
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-15 18:36:54.023
warn
Will try again in 5000 milliseconds ...

switchbot-ble.0
2021-11-15 18:36:54.022
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: undefined

switchbot-ble.0
2021-11-15 18:36:48.736
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-15 18:36:47.034
warn
Will try again in 5000 milliseconds ...

switchbot-ble.0
2021-11-15 18:36:47.033
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: undefined

@m0uh85
Probier mal bitte folgendes auf dem System wo der ioBroker installiert ist:
cd /opt/iobroker/node_modules/switchbot/
node

const Switchbot = require('switchbot');
const switchbot = Switchbot('e1:b1:f4:7b:67:0b');
switchbot.press();

@1tb2 @m0uh85
I just released version 0.3.0
Please try if it's working now

Also kurzes Feedback von meiner Seite. Als ich deine Eingabe getestet habe kam bei den beiden
const Switchbot = require('switchbot');
const switchbot = Switchbot('e1:b1:f4:7b:67:0b');
Jeweils irgendwas mit undefined (kann ich dir leider nicht mehr genau sagen hab ich heute Nacht im halb schlaf getestet.) ABER
switchbot.press();
wurde ausgeführt und hat funktioniert. So danach hab ich es über den iobroker getestet... hat auch funktioniert. Heute Morgen hab ich so 12-15 Schaltvorgänge getestet alle haben funktioniert.
Seeeeeeeeeehr komisch!
Werde jetzt trotzdem mal updaten und schauen wie es läuft die Tage....

switchbot-ble.0
2021-11-16 19:45:40.132
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Now connecting. Wait for a few seconds then try again.

switchbot-ble.0
2021-11-16 19:45:09.175
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Now connecting. Wait for a few seconds then try again.

switchbot-ble.0
2021-11-16 19:44:26.989
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Now connecting. Wait for a few seconds then try again.

switchbot-ble.0
2021-11-16 19:44:09.807
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-16 19:43:47.331
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-16 19:43:31.557
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: TypeError: Cannot read property 'press' of undefined

switchbot-ble.0
2021-11-16 19:43:23.219
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-16 19:43:15.417
info
Device e1:b1:f4:7b:67:0b pressed

@m0uh85
Änder' mall bitte "Wartezeit für erfolgreiches Bewegen vom Arm des Bots" auf 10 Sekunden (falls noch nicht geschehen)

switchbot-ble.0
2021-11-16 20:26:36.699
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-16 20:26:20.892
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-16 20:25:49.616
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-16 20:25:27.566
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-16 20:20:12.244
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-16 19:54:33.549
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-16 19:53:58.870
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-16 19:53:40.025
info
Device e1:b1:f4:7b:67:0b pressed

@m0uh85
Die Fehler (No service was found) werden von der Library gemeldet.
Ich habe noch mal 15 und 20 Sekunden als Auswahl hinzugefügt.

0.3.1 - 20 Sekunden:

switchbot-ble.0
2021-11-17 10:03:19.032
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-17 10:03:03.533
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-17 10:02:42.833
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-17 10:01:31.803
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Failed to discover services and characteristics: DISCONNECTED

switchbot-ble.0
2021-11-17 08:47:35.606
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-17 08:33:22.388
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-17 08:18:26.191
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-17 08:16:46.858
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-17 08:11:42.118
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-17 08:07:39.676
info
Device e1:b1:f4:7b:67:0b pressed

@m0uh85
Ich denke dass ich das Problem gefunden habe ...
Gibt dann so bald wie möglich ein Update.
Aktuell sollte es am besten sein, wenn man den Wert von "Wartezeit während der Gerätesuche" auf 1 Sekunde stellt und das "Intervall für die Gerätesuche" auf 15 Sekunden.

@m0uh85
Ich habe eben die Version 0.3.2 veröffentlicht.
Damit sollte es nun deutlich zuverlässiger funktionieren. Bei einem Fehler wird der Befehl erneut ausgeführt.
"Intervall für die Gerätesuche" kann nun wieder auf deutlich unter 60 Sekunden (z.B. 15 Sekunden)

@mrbungle64 ich update schnell und schreib dann schnell ein Blockly das der Taster alle 15 Minuten mal betätigt wird. Melde mich dann am Nachmittag mit dem Ergebnis.

Intervall für die Gerätesuche (Sekunden): 15
Wartezeit während der Gerätesuche (Sekunden): 1
Wartezeit für erfolgreiches Bewegen vom Arm des Bots (Sekunden): 20
oder soll ich andere Werte testen?

switchbot-ble.0
2021-11-18 09:00:02.414
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 08:45:02.468
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 08:42:47.669
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 08:40:27.098
info
Device detected: e1:b1:f4:7b:67:0b

9:15 & 9:30 & 9:45 Uhr wurde nicht ausgeführt.... zwischenzeitlich habe ich auch 3-4x manuell gedrückt und keine Funktion. Im Log habe ich keine Warn- bzw. Fehlermeldung.

Also wie du siehst läuft es zwar nicht fehlerfrei ABER nach einem Error wird der Bot dann trotzdem ausgelöst.
Was vllt. cool wäre, wenn man diese Info "Device e1:b1:f4:7b:67:0b pressed" also Rückmeldung per Objekt - State bekommen würde.

switchbot-ble.0
2021-11-18 12:45:03.823
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 12:30:02.973
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 12:15:07.502
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 12:15:04.283
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-18 12:00:06.373
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 11:45:10.153
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 11:45:06.093
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Failed to discover services and characteristics: DISCONNECTED

switchbot-ble.0
2021-11-18 11:45:03.698
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-18 11:45:01.713
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-18 11:30:09.274
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 11:30:02.151
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-18 11:15:05.428
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 11:00:06.982
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 11:00:04.043
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Failed to discover services and characteristics: DISCONNECTED

switchbot-ble.0
2021-11-18 11:00:01.763
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Failed to discover services and characteristics: DISCONNECTED

switchbot-ble.0
2021-11-18 10:45:02.784
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 10:30:04.272
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 10:15:07.678
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 10:15:03.983
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Failed to discover services and characteristics: DISCONNECTED

switchbot-ble.0
2021-11-18 10:15:01.364
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Failed to discover services and characteristics: DISCONNECTED

switchbot-ble.0
2021-11-18 10:00:07.261
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 09:57:07.779
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 09:52:25.077
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 09:52:09.499
info
Device detected: e1:b1:f4:7b:67:0b

Sieht doch bisher ganz OK aus :)

switchbot-ble.0
2021-11-18 18:30:02.683
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 18:15:07.713
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 18:15:03.753
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Failed to discover services and characteristics: DISCONNECTED

switchbot-ble.0
2021-11-18 18:00:03.555
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 17:45:03.085
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 17:30:02.873
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 17:15:06.861
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 17:15:01.792
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-18 17:00:03.336
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 16:45:02.797
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 16:30:02.393
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 16:15:02.862
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 16:00:02.776
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 15:45:06.032
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 15:45:02.175
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: No service was found.

switchbot-ble.0
2021-11-18 15:30:03.191
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 15:15:02.992
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 15:00:02.377
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 14:45:05.128
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 14:45:01.913
warn
Error while running deviceAction press for device e1:b1:f4:7b:67:0b: Error: Failed to discover services and characteristics: DISCONNECTED

switchbot-ble.0
2021-11-18 14:30:02.758
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 14:23:28.359
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 14:15:02.700
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 14:00:05.331
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 13:45:03.273
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 13:30:02.982
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 13:15:02.680
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 13:00:02.800
info
Device e1:b1:f4:7b:67:0b pressed

switchbot-ble.0
2021-11-18 12:49:09.985
info
Device e1:b1:f4:7b:67:0b pressed

@m0uh85

Sieht doch bisher ganz OK aus :)

Ja, sieht so aus als wären die alle erfolgreich gewesen 👍🏻

Was vllt. cool wäre, wenn man diese Info "Device e1:b1:f4:7b:67:0b pressed" also Rückmeldung per Objekt - State bekommen würde.

Hast du eine Idee wie man das abbilden könnte?

@m0uh85
Ich habe eben Version 0.3.3
Die Anzahl der Wiederholungen ist nun auf 15 begrenzt und die Protokollierung sollte ein bisschen detaillierter und klarer sein.


text:
Cache not renewing

Even though cache settings were changed, catalogues don't refresh on daily basis on android devices. Same applies to metadata, it's always the same until the app cache is cleared. What is going on?
EDIT: Cache refreshes on neither of the platforms (Web, Win, Lin, And)!

Actually I didn't look at the PR you made right you only changed the TLL of the mongo cache, you didn't change the http headers cache.

source: gharchive/issue

authors: mrcanelas oleglucic

repo: mrcanelas/tmdb-addon

license_type: permissive

license_source: github-api


text:
Install without composer?

Hi, is it possible to use this / install it without composer and if so... may I humbly ask how?
I read that this wasn't a problem in earlier versions and I ask because I get the message

"You must set up the project dependencies, run the following commands: curl -sS https://getcomposer.org/installer | php php composer.phar install"

and the only thing I found was an old entry at google code that suggested to install composer.

Hi, I also try to create the file "autoload" without "composer"
Best Regards

You can install it with Composer locally then copy the files--including the vendor directory--to your host.

I have installed composer and everything works wonderfully,
thanks

authors: ParkerD13 gtraxx mrclay

repo: mrclay/minify

license_source: bigquery


text:
sm16208s+sm5166 panel, ICN2037BP+RUC7258D panel

I need to buy an outdoor panel and want it to work with the library.
I asked sellers and sent them list of supported ICs asking for panels that use the same ones or similar and got recommended this panel, seller says it uses sm16208s and sm5166. They also say that "Equivalent to 138 lines decoding It is the most commonly used line decoding".
Will it work? If not, can I get a recommendation on some 160mm high outdoor screen that is tested and will work?
I also can report on some other panels I already tested:
This 80x40 flex screen does work well (I have a chain of two) with mxconfig.driver = HUB75_I2S_CFG::DP3246_SM5368; setting. I would use it but I need outdoor version...
This 80x40 outdoor screen doesn't work at all, it's all black no matter what settings I use. Can't tell what ICs it uses as the board is waterproofed.
Edit:
Chips on the working (flex, indoor 80x40) panel:
DP245D
DP5125D
3018SDP
It works with DP3246_SM5368 driver config.
You can safely add these to the supported ICs section.

sm5166. They also say that "Equivalent to 138 lines decoding It is the most commonly used line decoding".

true, sm5166 chip is a "type138" line decoder

Will it work?

Any of outdoor panels, even with supported chips - need to configure the order of the pixel output, which is not so easy to do in this library. I configured such panels for several people and described the scheme of the geometric function in the discussion #622.
Most panels are quite easy to configure, but sometimes there are very complex cases; it is impossible to predict the result without testing on hardware.

I will probably buy few different models and test which one works best.
I also got response from another seller, they have solutions with ICN2037BP+RUC7258D and LS9930CS+RUC7258D. Are these combinations worth checking?

they have solutions with ICN2037BP+RUC7258D and LS9930CS+RUC7258D. Are these combinations worth checking?

The first option should work, the second definitely won't, LS9930CS - unsupported driver

Ok so seller informed me that they have two versions of the 80x40 outdoor module I talked about in the first comment. One is ICN2037BP+RUC7258D and the second one is LS9930CS+RUC7258D, and you get a random one... They sent me pictures of ICN2037BP module and it has slightly different pcb layout so it makes sense that mine must be LS9930CS, and that's why it doesn't display anything...

Got the ICN2037BP+RUC7258D panel - it works but as expected, the order of pixels is messed up. Was such order observed before (might save me some time)? I will try to configure it.
The module is 80x40, it goes by 16-wide lines, two at the time, renders half of the screen, then stops (probably renders off-screen), then proceeds to re-render the top side (Idk if you can see it on video, but pixels get a bit brighter), then it proceeds to do the same to lower half.
https://github.com/user-attachments/assets/40c36d18-87cb-4673-bc6f-3c47ef6893a9

please show the code that produced this video

I drew it with such function:
void testPixels() {
  virtualDisp->clearScreen();
  int h = virtualDisp->height();
  int w = virtualDisp->width();
  int col = 0;
  int cnt = 0;
  for (int i = 0; i < h; i++) {
    for (int j = 0; j < w; j++) {
      virtualDisp->drawPixel(j, i, RED);
      delay(100);
    }
  }
}

Screen init part:
HUB75_I2S_CFG mxconfig(
  panel_x,
  panel_y,
  rows * cols);
dmaDisplay = new MatrixPanel_I2S_DMA(mxconfig);
dmaDisplay->setLatBlanking(4);
dmaDisplay->begin();
dmaDisplay->setBrightness8(200);  // 0-255, values higher than 200 may introduce ghosting
virtualDisp = new VirtualMatrixPanel((*dmaDisplay), rows, cols, panel_x, panel_y, chain_type);
virtualDisp->clearScreen();
virtualDisp->setCursor(0, 0);

panel_x = 80
panel_y = 40
These don't matter, I use VirtualMatrixPanel only because I used a chain before testing the new screen:
num_rows = 1
num_cols = 1
chain_type = CHAIN_BOTTOM_RIGHT_UP

Please show a full code

I use VirtualMatrixPanel only because I used a chain

No, it is not correct. You must use a VirtualMatrixPanel even for a single panel if you have a i.e. QuarterScanPanel type. What is the scan factor of your 80x40 matrix?

I use VirtualMatrixPanel only because I used a chain

No, it is not correct. You must use a VirtualMatrixPanel even for a single panel if you have a i.e. QuarterScanPanel type. What is the scan factor of your 80x40 matrix?

I know, what I meant is for now it doesn't do anything.
Panel is 1/10 scan, so a "four-scan". It's part of larger code so I think I will make a minimal example instead of sharing that, tested and produces the same output:
#include <ESP32-HUB75-MatrixPanel-I2S-DMA.h>
#include <ESP32-VirtualMatrixPanel-I2S-DMA.h>

// Display settings
#define PANEL_RES_X 80
#define PANEL_RES_Y 40
#define NUM_COLS 1
#define NUM_ROWS 1
#define PANEL_CHAIN NUM_COLS * NUM_ROWS
#define VIRTUAL_MATRIX_CHAIN_TYPE CHAIN_BOTTOM_RIGHT_UP

// Colors
#define WHITE virtualDisp->color565(255, 255, 255)
#define BLACK virtualDisp->color565(0, 0, 0)
#define RED virtualDisp->color565(255, 0, 0)
#define GREEN virtualDisp->color565(0, 255, 0)
#define BLUE virtualDisp->color565(0, 0, 255)

MatrixPanel_I2S_DMA *dmaDisplay = nullptr;
VirtualMatrixPanel *virtualDisp = nullptr;

void testPixels() {
  virtualDisp->clearScreen();
  int h = virtualDisp->height();
  int w = virtualDisp->width();
  for (int i = 0; i < h; i++) {
    for (int j = 0; j < w; j++) {
      virtualDisp->drawPixel(j, i, RED);
      delay(100);
    }
  }
}

void setupScreen(int panel_x, int panel_y, int rows, int cols, PANEL_CHAIN_TYPE chain_type) {
  HUB75_I2S_CFG mxconfig(
    panel_x,
    panel_y,
    rows * cols);

  dmaDisplay = new MatrixPanel_I2S_DMA(mxconfig);
  dmaDisplay->setLatBlanking(4);
  dmaDisplay->begin();
  dmaDisplay->setBrightness8(200);  // 0-255, values higher than 200 may introduce ghosting
  virtualDisp = new VirtualMatrixPanel((*dmaDisplay), rows, cols, panel_x, panel_y, chain_type);
  virtualDisp->clearScreen();
  virtualDisp->setCursor(0, 0);
}

void setup() {
  setupScreen(PANEL_RES_X, PANEL_RES_Y, NUM_ROWS, NUM_COLS, VIRTUAL_MATRIX_CHAIN_TYPE);
}

void loop() {
  testPixels();
  delay(2000);
}

In mxconfig I changed panel_y to panel_y/2 - now it render continously, doesn't go "off-screen" half way through as before. Still renders in two places at the same time.

now it render continously,

Could you show the video after the change?

Here: mxconfig set to panel_x, panel_y/2. Only other change is delay 100->10.
https://github.com/user-attachments/assets/77e2f649-4d06-4947-868b-77b5d10a9b13
I also tried to set set mxconfig to panel_x*2, panel_y/2, now it renders only one pixel at a time as it should, but only left side (with masonry shape in the middle) was rendered.
Then I tried following #622 - set mxconfig to panel_x*2, panel_y/2 and used setPhysicalPanelScanRate to use my own code:
        if ((coords.y & 10) == 0)
        {
            coords.x += ((coords.x / panelResX) + 1) * panelResX;
        }
        else
        {
            coords.x += (coords.x / panelResX) * panelResX;
        }
        coords.y = (virt_y / 20) * 10 + (virt_y & 9);

It left underndered horizontal strips.

OK! I'm close now, had to change math a bit, since the resolution is not in powers of 2.
    else if (panel_scan_rate == FOUR_SCAN_40PX_HIGH)
    {
        if ((coords.y / 10) % 2 == 0)
        {
            coords.x += ((coords.x / panelResX) + 1) * panelResX;
        }
        else
        {
            coords.x += (coords.x / panelResX) * panelResX;
        }
        coords.y = (coords.y / 20) * 10 + (coords.y % 10);
    }

I've set the pixel base to 16.
uint8_t pxbase = 16;
if ((coords.y / 10) % 2 == 0)
{
    coords.x += ((coords.x / pxbase) + 1) * pxbase;
}
else
{
    coords.x += (coords.x / pxbase) * pxbase;
}
coords.y = (coords.y / 20) * 10 + (coords.y % 10);

Almost there:
https://github.com/user-attachments/assets/a96f0d2d-31e1-4e01-9da7-de5a10944e06

Amazing results :)
Just a little bit left to success.

Yeah, I fixed that and then tried to display some multicolor image and realised that the shift is different on different color channels, which is very weird.

I fixed that

Could you explain how did you fixed it? Show the code?

According to the video, it's seems that the first CLK edge or first data pulse is lost.
Probably it could be fixed by changing a data output parameters, say clkphase or tuning the line
dmaDisplay->setLatBlanking(4);

May be @mrcodetastic could help

clkphase setting?

sorry, I don't know.
this is just a guess

I'll be working on it later today. Will give update for that. I'm using cystom board that has matched length for RGB lanes and works perfectly on other, indoor display.
My guesses are:

Power - I'm using 5V3A psu, on other board I observed some ghosting on parts of the screen, after hours of tinkering I decided to turn the voltage adjustment knob on the psu - it started working perfectly on about 6V. I tried doing the same on this board, some pixels aligned but other stayed shifted. Maybe I will try adding a capacitor?
Damage - I think it's rather unlikely but to mount the custom board (it plugs directly to hub75) I had to remove some of the black plastic on the back, maybe it damaged the panel's pcb?
Quirky panel, will try changing clkphase and if it doesn't work I will try to modify code to only shift red...

Update on power - for some reason my PSU outputs 5.7V on lowest V adj. setting. Maybe this is too far from the 5V?

Do you have a 3.3->5v logic level shifter between the ESP32 and the panel? Sorry if this has been asked before.

No, I asked if it would have any benefit in #703

In your case we need to test everything, so it could be worth to test a using of level shifter

license: MIT


text:
Adding the exercise solutions

Except milestone projects and the time series notebook everything is present

Woohoo!!!! Thank you thank you thank you :) - will link these in the README

source: gharchive/pull-request

repo: mrdbourke/tensorflow-deep-learning


text:
Add config and logic to force user to confirm YES or NO to executing 'unsafe' scripts in PRODUCTION env

Verbs like create/change/remove and SQL like update, insert, delete statements + DDL clauses

This has been implemented and will be present in next release

repo: mrglassdanny/vscode-moca-client


text:
Adding a checkBox to Allow Device Specific Shell Handling (Mobile and Desktop)

Hello, Thanks for this great tools @mrlacey a great utilities to start .net MAUI journey .
Would you like to consider adding the ability to added to the project a Mobile and desktop Shell based on this Tutorial project sample  https://github.com/naweed/Maui.Device-Specific-Views-Sample    credits to @naweed (thanks also for his great tutorial)

The consequences of adding such a thing adds a lot of (ongoing) behind-the-scenes effort and testing.
If/when doing this, I think it should be part of a general-purpose alternative navigation solution that is capable of doing more than just distinguishing between mobile & desktop versions. It should be general purpose and easily further extensible too.

Regarding The test, I could help and report. Also I completly agree with you I think you got the bigger picture. I was trying to reproduce what I saw in DotNet PodCast app with Mobile and Desktop Shell when I found the tutorial and as your tools was my starting point I tried to suggest it as a feature :)

A nice idea but I can't see this ever being added here.
Closing this issue to help tidy up the backlog. Feel free to reopen if there are new reasons to add something like this in the future.

repo: mrlacey/MauiAppAccelerator


text:
Build Failure on Android After Updating react-native-mmkv with React Native 0.75.2

Hello,
I've encountered a build issue after updating the react-native-mmkv library. My project, which uses React Native version 0.75.2, fails to build on Android, throwing the following errors:
info 💡 Tip: Make sure that you have set up your development environment correctly, by running npx react-native doctor. To read more about the doctor command visit: https://github.com/react-native-community/cli/blob/main/packages/cli-doctor/README.md#doctor

C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPlatformContextModule.java:7: error: cannot find symbol
public class MmkvPlatformContextModule extends NativeMmkvPlatformContextSpec {
                                               ^
  symbol: class NativeMmkvPlatformContextSpec

C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPackage.java:19: error: cannot find symbol
    if (name.equals(MmkvPlatformContextModule.NAME)) {
                                             ^
  symbol:   variable NAME
  location: class MmkvPlatformContextModule

C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPackage.java:20: error: incompatible types: MmkvPlatformContextModule cannot be converted to NativeModule
      return new MmkvPlatformContextModule(reactContext);
             ^

C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPackage.java:31: error: cannot find symbol
              MmkvPlatformContextModule.NAME,
                                       ^
  symbol:   variable NAME
  location: class MmkvPlatformContextModule

C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPackage.java:33: error: cannot find symbol
                      MmkvPlatformContextModule.NAME,
                                               ^
  symbol:   variable NAME
  location: class MmkvPlatformContextModule

C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPackage.java:34: error: cannot find symbol
                      MmkvPlatformContextModule.NAME,
                                               ^
  symbol:   variable NAME
  location: class MmkvPlatformContextModule

C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPlatformContextModule.java:15: error: method does not override or implement a method from a supertype
    @Override
    ^

C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPlatformContextModule.java:21: error: method does not override or implement a method from a supertype
    @Override
    ^
Note: C:\Users\Alex\Desktop\BuildThis\MyProject\node_modules\react-native-mmkv\android\src\main\java\com\mrousavy\mmkv\MmkvPackage.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
8 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-mmkv:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
> Run with --info option to get more log output.
> Run with --scan to get full insights.

BUILD FAILED in 27s
info Run CLI with --verbose flag for more details.

Faced the same problem, configuring newArchEnabled=true in android/gradle.properties also seems to fail to compile

Confirm to have no issues with new arch on RC, but 3.0.1 fails to build on Android.

same error +

This is a duplicate of

https://github.com/mrousavy/react-native-mmkv/issues/726
https://github.com/mrousavy/react-native-mmkv/issues/725
https://github.com/mrousavy/react-native-mmkv/issues/722
and https://github.com/mrousavy/react-native-mmkv/issues/718

They were all visible in the issues page, please don't spam issues or create duplicates. We already have enough of them.
I am working on a fix and will release it soon - in the meantime you can sponsor me on GitHub to buy me a coffee or say "thanks". 😃❤

released in react-native-mmkv 3.0.2 :rocket:

Thank you! Version 3.0.2 solves this problem perfectly.

@mrousavy it stopped working on web

@gituser8796 PRs appreciated

Still am able to see the same error even with version 3.0.2

> Task :react-native-mmkv:compileDebugJavaWithJavac FAILED /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPlatformContextModule.java:7: error: cannot find symbol public class MmkvPlatformContextModule extends NativeMmkvPlatformContextSpec {                                                ^   symbol: class NativeMmkvPlatformContextSpec /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPlatformContextModule.java:15: error: method does not override or implement a method from a supertype     @Override     ^ /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPlatformContextModule.java:21: error: method does not override or implement a method from a supertype     @Override     ^ /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPackage.java:19: error: cannot find symbol     if (name.equals(MmkvPlatformContextModule.NAME)) {                                              ^   symbol:   variable NAME   location: class MmkvPlatformContextModule /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPackage.java:20: error: incompatible types: MmkvPlatformContextModule cannot be converted to NativeModule       return new MmkvPlatformContextModule(reactContext);              ^ /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPackage.java:31: error: cannot find symbol               MmkvPlatformContextModule.NAME,                                        ^   symbol:   variable NAME   location: class MmkvPlatformContextModule /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPackage.java:33: error: cannot find symbol                       MmkvPlatformContextModule.NAME,                                                ^   symbol:   variable NAME   location: class MmkvPlatformContextModule /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPackage.java:34: error: cannot find symbol                       MmkvPlatformContextModule.NAME,                                                ^   symbol:   variable NAME   location: class MmkvPlatformContextModule Note: /Users/nitinpatelm/workspace/latlong/latlong_anuga_app/node_modules/react-native-mmkv/android/src/main/java/com/mrousavy/mmkv/MmkvPackage.java uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. 8 errors
"react-native-mmkv": "^3.0.2",
"react-native": "^0.75.2",

me either

same error with @nitinpatelm

Thank you! Version 3.0.2 solves this problem perfectly.

What version react-native you use ?

Any solution?

Same error on latest React native
better to move on Asyncstorage

I just downgraded the version to 2.12.2 and it's working fine

Facing same issue.
`
"react-native-mmkv": "^3.0.2",
"react-native": "0.75.3",
`

@bobanminic96 make sure you are using new architecture, mmkv 3.x only works with new architecture, if you are still on the old architecture you need to use 2.12.2

Had the same issue the problem was i was using react-native version 0.74.2 and my mmkv version was 3.0.2, fixed it by changing the mmkv version to 2.12.2

I encountered a build error related to NativeMmkvPlatformContextSpec when building the app using React Native version 0.75.4 and react-native-mmkv version 3.0.2. The issue was resolved by enabling the new architecture (newArchEnabled=true in gradle.properties).

enabling newArchEnabled=true works fine. with
"react-native-mmkv": "^3.0.2",
"react-native": "0.75.4",

enabling the new architecture in android/gradle.properties works fine for me as well:
newArchEnabled=true
    "react-native": "0.75.4",
    "react-native-mmkv": "^3.0.2",

Basically, if you use the react-native version 0.75.x you must set the react-native-mmkv version to 3.X.X.
If you are using a version of react-native below 0.75.x I recommend you use "react-native-mmkv": "2.12.2"
Example:
If:
"react-native": "0.75.0",
"react-native-mmkv": "3.0.2",

If:
"react-native": "0.74.5",
"react-native-mmkv": "2.12.2",

I also recommend activating newArchEnabled which is located at: ./android/gradle.properties
That way:
newArchEnabled=true
Furthermore, within gradle.properties I recommend specifying jdk-17 (if you don't have version 17, download it):
org.gradle.java.home=C:/Program Files/Java/jdk-17

in 3.0.2, there is no NativeMmkvPlatformContextSpec importing and no field NAME in MmkvPlatformContextModule.java, why do you expect it can be compiled?

enabling the new architecture in android/gradle.properties works fine for me as well: newArchEnabled=true
    "react-native": "0.75.4",
    "react-native-mmkv": "^3.0.2",

Yes, it works. But not all of us are comfortable using new Architecture. I think considering keeping the option for the old architecture would be good.

I think considering keeping the option for the old architecture would be good.

Read the README.md. That's why I said in there you can use v2 if you are on old arch.

For anyone still facing this issue, here's how i fixed it
Downgraded to
 "react-native-mmkv": "^2.12.2",
"react-native": "0.74.6",
can't upgrade RN safely so have to stick to this, also setting newArch = true resulted in other build failures

Use ^2.12.2 version of mmkv  Works on any rn versions

repo: mrousavy/react-native-mmkv


text:
🐛  FrameHostObject error iOS 16.6.1 & Xcode 14

What's happening?
The camera shows up correctly however when i use frameProcessor i got the following issue

Reproduceable Code
Swift Plugin code
import VisionCamera

@objc(HeartBeatFrameProcessorPlugin)
public class HeartBeatFrameProcessorPlugin: FrameProcessorPlugin {
  public override init(options: [AnyHashable: Any]! = [:]) {
    super.init(options: options)
  }

  public override func callback(_ frame: Frame, withArguments arguments: [AnyHashable: Any]?) -> Any? {
    let imageBuffer = CMSampleBufferGetImageBuffer(frame.buffer)

    if let arguments, let imageBuffer {
      let width = CVPixelBufferGetWidth(imageBuffer)
      let height = CVPixelBufferGetHeight(imageBuffer)
      let count = arguments.count

      print(
        "ExampleSwiftPlugin: \(width) x \(height) Image. Logging \(count) parameters:"
      )

      for key in arguments.keys {
        let value = arguments[key]
        let valueString = String(describing: value)
        let valueClassString = String(describing: value.self)
        print("ExampleSwiftPlugin:   -> \(valueString) (\(valueClassString))")
      }
    }

    return [
      "example_str": "SwiftTest",
      "example_bool": false,
      "example_double": 6.7,
      "example_array": ["Good bye", false, 21.37]
    ]
  }
}

Worklet TS code
import { VisionCameraProxy, Frame } from 'react-native-vision-camera'

const plugin = VisionCameraProxy.initFrameProcessorPlugin('hertbeat')

export function hertbeat(frame: Frame) {
  'worklet'
  if (plugin == null) {
    throw new Error("Failed to load Frame Processor Plugin!")
  }
  return plugin.call(frame)
}

const handleFrameProcessor = useFrameProcessor((frame: Frame) => {
        'worklet'
        runAtTargetFps(5, () => {
            'worklet'
            const data = hertbeat(frame);
        })
    }, []);

<Camera
                    torch="on"
                    frameProcessor={handleFrameProcessor}
                    pixelFormat={Platform.OS === 'ios' ? 'rgb' : 'yuv'}
                    device={device}
                    isActive={true}
                    style={{
                        width: 250,
                        height: 250
                    }}
                    onError={onError}
                />

### Relevant log output

Frame under useFrameProcessor
```js
{ width: 0,
  height: 0,
  bytesPerRow: 0,
  planesCount: 0,
  orientation: 'landscape-right',
  isMirrored: false,
  timestamp: NaN,
  pixelFormat: 'unknown',
  toString: [Function: toString],
  toArrayBuffer: [Function: toArrayBuffer],
  isValid: true,
  incrementRefCount: [Function: incrementRefCount],
  decrementRefCount: [Function: decrementRefCount] }

2023-11-21 16:21:34.026406-0600 heartbeatVisionApp[5506:400917] SocketStream read error [0x2811a7520]: 1 54
2023-11-21 16:21:37.094195-0600 heartbeatVisionApp[5506:400934] SocketStream read error [0x2811ac8c0]: 1 54
2023-11-21 16:21:40.125073-0600 heartbeatVisionApp[5506:400916] SocketStream read error [0x2811a80a0]: 1 54
2023-11-21 16:21:42.622540-0600 heartbeatVisionApp[5506:400929] [javascript] Running "heartbeatVisionApp" with {"rootTag":1,"initialProps":{}}
2023-11-21 16:21:42.639359-0600 heartbeatVisionApp[5506:400916] [connection] nw_socket_handle_socket_event [C9:1] Socket SO_ERROR [61: Connection refused]
2023-11-21 16:21:42.639521-0600 heartbeatVisionApp[5506:400934] [connection] nw_connection_get_connected_socket_block_invoke [C9] Client called nw_connection_get_connected_socket on unconnected nw_connection
2023-11-21 16:21:42.639552-0600 heartbeatVisionApp[5506:400934] TCP Conn 0x2811a7520 Failed : error 0:61 [61]
2023-11-21 16:21:42.639889-0600 heartbeatVisionApp[5506:400934] [connection] nw_connection_copy_connected_local_endpoint_block_invoke [C9] Client called nw_connection_copy_connected_local_endpoint on unconnected nw_connection
2023-11-21 16:21:42.639902-0600 heartbeatVisionApp[5506:400934] [connection] nw_connection_copy_connected_remote_endpoint_block_invoke [C9] Client called nw_connection_copy_connected_remote_endpoint on unconnected nw_connection
2023-11-21 16:21:42.730568-0600 heartbeatVisionApp[5506:400929] [javascript] Loading react-native-worklets-core...
2023-11-21 16:21:42.732293-0600 heartbeatVisionApp[5506:400929] [javascript] Worklets loaded successfully
2023-11-21 16:21:42.734154-0600 heartbeatVisionApp[5506:400929] VisionCameraProxy: Creating Worklet Context...
2023-11-21 16:21:42.734908-0600 heartbeatVisionApp[5506:400929] VisionCameraProxy: Worklet Context Created!
2023-11-21 16:21:42.820450-0600 heartbeatVisionApp[5506:400929] Looking up Frame Processor Plugin "hertbeat"...
2023-11-21 16:21:42.820487-0600 heartbeatVisionApp[5506:400929] Frame Processor Plugin "hertbeat" found! Initializing...
2023-11-21 16:21:42.868026-0600 heartbeatVisionApp[5506:400708] [native] VisionCamera.didSetProps(_:): Updating 12 props: [onViewReady, cameraId, torch, onError, width, onInitialized, enableBufferCompression, onCodeScanned, height, enableFrameProcessor, pixelFormat, isActive]
2023-11-21 16:21:42.868042-0600 heartbeatVisionApp[5506:400708] [native] VisionCamera.configure(_:): Updating Session Configuration...
2023-11-21 16:21:42.868112-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.withSessionLock(_:): Beginning CameraSession configuration...
2023-11-21 16:21:42.868135-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.configureDevice(configuration:): Configuring Input Device...
2023-11-21 16:21:42.868181-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.configureDevice(configuration:): Configuring Camera com.apple.avfoundation.avcapturedevice.built-in_video:0...
2023-11-21 16:21:42.868246-0600 heartbeatVisionApp[5506:400915] [native] VisionCamera.configure(_:): Beginning AudioSession configuration...
2023-11-21 16:21:42.868253-0600 heartbeatVisionApp[5506:400915] [native] VisionCamera.configureAudioSession(configuration:): Configuring Audio Session...
2023-11-21 16:21:42.868378-0600 heartbeatVisionApp[5506:400915] [native] VisionCamera.configure(_:): Committed AudioSession configuration!
2023-11-21 16:21:42.874498-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.configureDevice(configuration:): Successfully configured Input Device!
2023-11-21 16:21:42.874506-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.configureOutputs(configuration:): Configuring Outputs...
2023-11-21 16:21:42.874512-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.configureOutputs(configuration:): Adding Video Data output...
2023-11-21 16:21:42.874758-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.configureOutputs(configuration:): Successfully configured all outputs!
2023-11-21 16:21:42.875265-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.withSessionLock(_:): Committed CameraSession configuration!
2023-11-21 16:21:42.875271-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.withDeviceLock(_:): Beginning CaptureDevice configuration...
2023-11-21 16:21:42.876469-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.withDeviceLock(_:): Committed CaptureDevice configuration!
2023-11-21 16:21:43.045353-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.withDeviceLock(_:): Beginning CaptureDevice configuration...
2023-11-21 16:21:43.046908-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.withDeviceLock(_:): Committed CaptureDevice configuration!
2023-11-21 16:21:43.046923-0600 heartbeatVisionApp[5506:400916] [native] VisionCamera.onSessionInitialized(): Camera initialized!
(lldb)

### Camera Device

```json
{
  "hasTorch": true,
  "id": "com.apple.avfoundation.avcapturedevice.built-in_video:0",
  "position": "back",
  "minZoom": 1,
  "isMultiCam": false,
  "name": "Back Camera",
  "hasFlash": true,
  "maxZoom": 121.875,
  "hardwareLevel": "full",
  "neutralZoom": 1,
  "supportsFocus": true,
  "supportsRawCapture": false,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsLowLightBoost": false,
  "sensorOrientation": "landscape-right"
}

Device
iPhone 13 iOS 16.6.1
VisionCamera Version
3.6.6
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[ ] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

I found that is not my plugin, but the console.log(frame) somehow its not returning valid date when output comes, when i removed that log it works.

i’m not sure about ios but on android rgb pixel format is not supported anymore, i think it’s not supported on ios as well, try to use yuv instead and see what happens

@rodgomesc rgb is supported in iOS, just tested it, not sure if you look at my previous answer, but removing the logs did the trick. im gonna close this issue.

authors: dante-cervantes-rocketlab rodgomesc

repo: mrousavy/react-native-vision-camera


text:
🛑 OCA Padlet is down

In 668bb04, OCA Padlet (https://oca.padlet.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: OCA Padlet is back up in 5308e2f.

repo: mrvinceo/ocaUptime


text:
Assertion `status == 0’ failed

node: …/src/binding.cc:186: static void Pcap::cb_packets(uv_poll_t*, int, int): Assertion `status == 0’ failed.

I think socker errors need to be peroperly handled similar to the cases reported earlier

Can you provide a reproducible test for this? What platform did you encounter this on?

Sorry for the delay in reply. The platform is:
libpcap 1.6.2-2
Linux raspberrypi 4.9.35-v7+

This is used as part of complex application. Thus I'll try to to create an isolated test case. The problem occurs. However, I am wondering why status != 0 isn't handled gracefully. A similar assertion issue had occurred on Windows earlier.

What node version are you using?

Also, does simply commenting out the offending line out fix the issue or cause other problems? It would be interesting to know what the status value is when it's not zero.... it should correspond to an libuv error.

authors: mscdex mwittig

repo: mscdex/cap

license: mit


text:
🛑 Do53 Roost IPv4 UDP is down

In d02705d, Do53 Roost IPv4 UDP (http://107.189.10.142:9202) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv4 UDP is back up in 93b9150 after 49 minutes.

repo: mschirrmeister/upptime-loopx


text:
🛑 Do53 Roost IPv4 UDP is down

In 2f6d97a, Do53 Roost IPv4 UDP (http://107.189.10.142:9202) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv4 UDP is back up in 1a8407c after 15 minutes.


text:
🛑 Do53 Roost IPv6 TCP is down

In e8e7d5b, Do53 Roost IPv6 TCP (http://107.189.10.142:9205) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv6 TCP is back up in d5f756c after 17 minutes.


text:
🛑 Do53 Roost IPv4 TCP is down

In ae316ea, Do53 Roost IPv4 TCP (http://107.189.10.142:9203) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv4 TCP is back up in 0038e8f after 25 minutes.


text:
🛑 Do53 Roost IPv6 TCP is down

In c6a8e78, Do53 Roost IPv6 TCP (http://107.189.10.142:9205) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Do53 Roost IPv6 TCP is back up in 25a0e47 after 52 minutes.


text:
Cannot download some books in Readmoo

This book cannot be downloaded.
https://readmoo.com/book/210095766000101
And it seems that all books in this series cannot be downloaded, I have tried multiple books, none of them success.
https://readmoo.com/installment/885
If you want some logs, you can add them and I could fetch the logs for you. As for now, I do not find any logs related to this and not really look into the code yet.

Hi @NomadThanatos ,
I figured out the problem is that regex expression in exporter cannot find root path.
And I fixed this problem in latest master branch already.
Could you reinstall the extension from latest master and try download the book from that series?
If there is any problem still, please let me know.
Thanks.

The fix solves this problem.

license: WTFPL


text:
Add Azure Databricks and AZTK

Fixes #599

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/data-guide/technology-choices/batch-processing.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/data-guide/technology-choices/batch-processing.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/data-guide/technology-choices/batch-processing.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/data-guide/technology-choices/batch-processing.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

authors: MikeWasson VSC-Service-Account

repo: mspnp/architecture-center


text:
allow MSP430 DCO frequency to be up to 9MHz

This is a quick-and-dirty fix for msp430 Series-2 based mote (e.g. Zolertia Z1) clock speed in simulations.
For now, attempts to configure DCO frequency higher than 4.9 MHz in Cooja lead to ACLK speed being reduced to 16384. The outcome is that Contiki system clock on simulated Z1 motes runs twice slower than expected.
Due to some implementation idiosyncrasies, the problem with Z1 clock speed in simulations appeared only after applying this pull request to Contiki: https://github.com/contiki-os/contiki/pull/606 (it fixes a different clock frequency related bug):
Related: issue #35.

Great! Should also fix https://github.com/mspsim/mspsim/issues/44, right?

Hi Simon,
yes, you describe the same problem, and this patch is sufficient to get the clock speed back to normal.
issue #35 explains what exactly goes wrong.

Excellent, thank!
On 14 May 2015 10:32, "Atis Elsts" notifications@github.com wrote:

Hi Simon,
yes, you describe the same problem, and this patch is sufficient to get
the clock speed back to normal.
issue #35 https://github.com/mspsim/mspsim/issues/35 explains what
exactly goes wrong.
—
Reply to this email directly or view it on GitHub
https://github.com/mspsim/mspsim/pull/38#issuecomment-101970805.

This should now be fixed by #46 so I am closing this.

authors: atiselsts joakimeriksson simonduq

repo: mspsim/mspsim


text:
🛑 files.mstdn-social.com is down

In 1907052, files.mstdn-social.com (https://files.mstdn-social.com/index.html) was down:

HTTP code: 0
Response time: 0 ms

Resolved: files.mstdn-social.com is back up in 771b5cf.


text:
🛑 BN/SEM is down

In c27a6a0, BN/SEM (https://socialem.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: BN/SEM is back up in af21870.

repo: mswd-io/upptime


text:
🛑 YourCotton is down

In ca6853e, YourCotton (https://cottonfabric.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: YourCotton is back up in 634e149 after 10 minutes.


text:
Strip commas from wordlist items

I suggest removing the commas as the newline separator already separates words from each other.

Dear @eliashaeussler, thanks so much for your contribution!
Although I would certainly agree that newline usually does not require a comma, the requirements for custom skribbl.io wordlists differ:

Minimum of 10 words. 1-32 characters per word! 20000 characters maximum. Separated by a , (comma)

That is why I suggest to keep the commas as is. 🎄
Cheers
Martin

You're right. Stupid me. Anyway, thanks for this great repo 💛

authors: eliashaeussler mteu

repo: mteu/skribbl-xmas-wordlist


text:
Tagging images and containers

Scope
Explore tagging images and containers in a versioned manner so that it is easier to detect what "version" of the container someone is running going forward in response to #7.
Implementation
Working with image tags makes working with docker compose slightly more complicated. This PR adds environment/docker-environment-common.sh to help abstract that complication away. Now, instead of lengthy and complicated docker compose -f ... commands,  you can use:

environment/docker-environment-common.sh build
environment/docker-environment-common.sh up
environment/docker-environment-common.sh start
environment/docker-environment-common.sh stop
environment/docker-environment-common.sh logs
environment/docker-environment-common.sh down
./environment/docker-environment-common.sh version
./environment/docker-environment-common.sh tags

The Docker image tag takes the form datascience-notebook:${hash of the current commit in Git}. This is specified by image: datascience-notebook:$TAG in compose.yml; $TAG is set by the build command in environment/docker-environment-common.sh and saved in environment/image-tags.
You can see your container's version with ./environment/docker-environment-common.sh version, provided Docker is running and the container is built and running.
If the org.opencontainers.image.version value for your container matches that of a fellow researcher, you should be working from the same version of the Docker code.
Things to note
The tag refers to the latest commit. That's mostly good. When it might go weird is if work is done on a branch over time (leading to commits) and someone needs to rebuild the containers or set up on a new machine, they'll have a different image tag even if the environment hasn't actually changed...
If that behavior does not work, lead researchers can elect to either
~1. Hard code a value for ${TAG} in environment/compose.yml~ This probably won't work because $TAG won't be set in environment/docker-environment-common.sh...
2. Possibly (untested) – change the retrieve_tag() function in environment/docker-environment-common.sh to (replacing x.x.x with the desired tag):
function retrieve_tag() {
  TAG="x.x.x"
  export TAG
}

This will more closely control the tag values across commits – the downside to this is that researchers will have to remember to manually change the tag value when the environment is changed.
TODO: add description of how implemented....
Future Work
None at this time
Testing

From the project directory, check out this branch.
Rebuild the containers and bring them up again: ./environment/docker-environment-common.sh build and ./environment/docker-environment-common.sh up
Open JupyterLab in the browser OR reload JupyterLab in the browser.
Check the image and container tags

To be completed by the person testing

[ ] Docker image is tagged
[ ] Docker container is tagged

Special considerations for making this live

Remove log information from wiki; it's in the environment/README.md now.
Add any required documentation around how to update the tag information, if applicable

Alternate idea: docker container ls -a will show you when you created the containers with something like this:
CONTAINER ID   IMAGE                                   COMMAND                  CREATED        STATUS                     PORTS                                                                     NAMES
c594073843c5   f095a4018bd7                            "tini -g -- start-no…"   3 weeks ago    Exited (255) 2 weeks ago   0.0.0.0:10000->8888/tcp, :::10000->8888/tcp                               environment_datascience-notebook_1

You should be able to see in GitHub when the Docker files were last updated for your project – would combining that information with the "created" date of the container be sufficient to understand whether a given researcher is running the latest version of the container?

Alternate idea: docker container ls -a will show you when you created the containers with something like this:
CONTAINER ID   IMAGE                                   COMMAND                  CREATED        STATUS                     PORTS                                                                     NAMES
c594073843c5   f095a4018bd7                            "tini -g -- start-no…"   3 weeks ago    Exited (255) 2 weeks ago   0.0.0.0:10000->8888/tcp, :::10000->8888/tcp                               environment_datascience-notebook_1

You should be able to see in GitHub when the Docker files were last updated for your project – would combining that information with the "created" date of the container be sufficient to understand whether a given researcher is running the latest version of the container?

Whoops, meant to tag @BeniamG there!


text:
🛑 https://takaful.salfeet.plo.ps is down

In cdc49e2, https://takaful.salfeet.plo.ps (https://takaful.salfeet.plo.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://takaful.salfeet.plo.ps is back up in e942839.

repo: mtitservice/site


text:
🛑 https://mtit.pna.ps is down

In b954145, https://mtit.pna.ps (https://mtit.pna.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://mtit.pna.ps is back up in da3e6db.


text:
🛑 https://minfo.ps is down

In 1c7c219, https://minfo.ps (https://minfo.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://minfo.ps is back up in 8c5eac2.


text:
🛑 https://gcc2.mtit.pna.ps is down

In 422a402, https://gcc2.mtit.pna.ps (https://gcc2.mtit.pna.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://gcc2.mtit.pna.ps is back up in e658892.


text:
🛑 https://reports.mtit.pna.ps is down

In f71a1ca, https://reports.mtit.pna.ps (https://reports.mtit.pna.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://reports.mtit.pna.ps is back up in a443f55.


text:
🛑 https://db.hcys.ps is down

In 1bbbf0a, https://db.hcys.ps (https://db.hcys.ps) was down:

HTTP code: 0
Response time: 0 ms

Resolved: https://db.hcys.ps is back up in 0f42a11.


text:
Player 3.0 plays better than 3.1 but its notes are out of sync for a period (about 30 seconds for me) after loadPlugin completes

After replacing Player.js 0.3 with 0.3.1, the player loads a midi file right away and in sync, but there are more audio cuts/clicks.
Player.js 0.3 audio sounds better than 0.3.1, but is out of sync for the first 30 seconds.
Could this be a compatibility issue between other files? Please let me know if you need anything else posted.
Thanks,

may have just been an overload


text:
Updated PR template

What type of PR is this? (check all applicable)

[X] ♻ Refactor
[ ] ✨ Feature
[ ] 🐛 Bug Fix
[X] 👷 Optimization
[X] 📝 Documentation Update
[ ] 🔖 Release
[X] 🚩 Other

Description
Updated the PR template.
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings (if there are UI changes)

Added to documentation?

[ ] 📜 readme
[X] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

@mudit023 Can I tell you a new idea here in this pull request ?

@mudit023 Can I tell you a new idea here in this pull request ?

Make A landing Page for our templates(I will make it using react js)

@mudit023 Can I tell you a new idea here in this pull request ?

Make A landing Page for our templates(I will make it using react js)

@Programing-School yeah do it.

Let's discuss it on slack


text:
[IconButton] changing size via style prop moves icon

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
Icon should be in the center of the IconButton
Current Behavior
changing the size of an IconButton moves the icon so the ripple effect is above the actual icon

Steps to Reproduce
After updating to material-ui version 3.1.0 the icons of iconbuttons are not centered if size changed via style props.
Link:
https://codesandbox.io/s/ykro436z5j

update to new Material-Ui Versions (Icons and Core)
change size of IconButton via style props (height, width)

Context
We have a table where you have buttons to edit/delete the row, to decrease the row-height, we changed the size of the buttons.  So more rows per page can be shown.

Your Environment

Tech
Version

Material-UI
v3.1.0

Material-UI Icons
v3.0.1

React
v16.5.1

GoogleChrome
v69.0.3497.100

This is caused by #12865.
The IconButton no longer has a fixed height, and is now padding: 12px. Instead of changing the height/width, change the padding.
AND/OR
The Icon now has a fontSize prop that can be set to small.
The snippet below will get close to the 35px x 35px size you aim for.
<IconButton style={{ padding: 7 }}>
  <Edit fontSize="small" />
</IconButton>

authors: JoshuaLicense cstadlinger

repo: mui-org/material-ui


text:
ToolTip is not display on Rating anymore

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
When using a Tooltip on a  custom IconContainerComponent
 IconContainerComponent={p => (
          <IconContainer
            {...p}
            possibleValues={possibleValues}
          />
        )}

function IconContainer(props) {
  const { value, possibleValues, ...other } = props;
  return (
    <Tooltip
      disableFocusListener
      disableTouchListener
      enterNextDelay
      enterDelay={10}
      placement="top"
      title={possibleValues[value - 1] || ""}
    >
      <span {...other} />
    </Tooltip>
  );
}

The tooltip is not shown
Expected Behavior 🤔
Tooltip visible
Context 🔦
is working on  "@material-ui/lab": "4.0.0-alpha.32" but not in the last version      "@material-ui/lab": "^4.0.0-alpha.46"

@sabativi The support was dropped in #19103.

I have added the waiting for users upvotes tag. I'm closing the issue as we are not sure people are looking for such feature. So please upvote this issue if you are. We will prioritize our effort based on the number of upvotes.

authors: oliviertassinari sabativi


text:
Material-UI: The value provided to useAutocomplete is invalid.None of the options match with  You can use the getOptionSelected prop to customize the equality test.

i have the same warning but i already added getOptionSelected, it make infinity console warning
Material-UI: The value provided to useAutocomplete is invalid.
None of the options match with `{"id":"geonames:6429478","name":"Périgueux"}`.
You can use the `getOptionSelected` prop to customize the equality test.

the code:

  let {
    getRootProps,
    getInputLabelProps,
    getInputProps,
    getListboxProps,
    getOptionProps,
    groupedOptions,
    getOptionSelected,
    focused,
    setAnchorEl,
    anchorEl,
    inputValue
  } = useAutocomplete({
    value: selectedOption || {},
    options: options,
    getOptionLabel: (option) => {
      return option.name || "";
    },
    getOptionSelected: (option, value) =>{
       console.log({value,option});
       // I added id comparaison because in option.name accent char are replaced ( éàè....)
        return  option?.name.toLowerCase() === value?.name.toLowerCase() || option?.id === value?.id
    },
    selectOnFocus: true
  });

the log from getOptionSelected :
option: {
  id: "geonames:6616167",name: "Mareuil en Perigord"
}
value: {
  id: "geonames:6616167",
  name: "Mareuil en Périgord"
}

Any idea please ?

Looking into possible solutions in #21985, I've gone the route of adding the interfaces manually until it's fully supported in the library.

Hi @alainib,
I'm having the same issue. Did you manage to solve this? Thanks :)

Hi @alainib,
I'm having the same issue. Did you manage to solve this? Thanks :)

try with this :
let {
    getRootProps,
    getInputLabelProps,
    getInputProps,
    getListboxProps,
    getOptionProps,
    groupedOptions,
    getOptionSelected,
    focused,
    setAnchorEl,
    anchorEl,
    inputValue
  } = useAutocomplete({
    value: selectedOption || {},
    options: options,
    getOptionLabel: (option) => {
      return option.name || "";
    },
    getOptionSelected: (option, value) => {
      return option?.id === value?.id || option?.name.toLowerCase() === value?.name.toLowerCase();
    },
    selectOnFocus: true
  });

authors: alainib mithi-aeronology tbremer


text:
[icons] Remove unpopular icons?

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
The @mui/icons-material package has significantly grown in size in the last few months. Google is adding more icons. in v4, we had around 1.1k icons https://v4.mui.com/components/material-icons/, in v5 we are already at 1.9k icons.
More icons put stress on the infrastructure. #12432 is one example, but it also challenges the Netlify build and more. I wonder if it would make sense to remove icons that are low in popularity.
Examples 🌈
Who needs this icon? https://fonts.google.com/icons?selected=Material+Icons+Outlined:assignment_returned&icon.query=currency+franc

Motivation 🔦
https://github.com/mui-org/material-ui/pull/29328#issuecomment-968165315

Alternatively (or additionally) to what you're proposing, we can move the icons package to a separate repository. The icons don't change often and it doesn't make sense to include them in every build.

Better more icons then less, sometimes you just pick one which has similar to needed shape and don't care what does it actually mean.
Anyway tree shaking will cut not used icons from your app.

@michaldudak Could we exclude it from CI without moving it to its own repo?

It would depend on the problem that we want to fix. For instance, some people scan all the icons in the search of one that might fit their use case when the search yields no results (I have done this countless times). Removing icons that are never used would remove noise.
IMHO, we don't yet have a strong enough pain to solve to push this issue forward. I have used the "on hold" label to signal that. So far, it's simply a solution proposal, for an unknown problem.

authors: YuriGor mbrookes michaldudak oliviertassinari


text:
[ci] Fail when demos are only available in TS

git diff does not include untracked files. This means demos that are only available in TS are not flagged properly.
TODO:

[x] Figure out what to do with the dangling TS demos (separated in #15427 but I re-united these poor fellows): 101d75acb271d576bbabc3bacae0843d9fd26803

A nice rebase issue spotted!


text:
[TablePagination] Support unknown total count

This PR  add the possibility to show server side pagination for an unknown number of rows if count -1 is provided.
This will enable the data grid component to be server side rendered without knowing the total amount of rows and the 'labelDisplayedRows' does not have to overwritten for this usecase.

[x] I have followed (at least) the PR section of the contributing guide.

Awesome, I can't wait to put this feature at use in the data grid. For the translations, I believe that the community will jump in if we successfully make it use the feature. So I wouldn't worry too much about it.


text:
[core] Add support #rrggbbaa pattern in hexToRgb function

Fix #20497

[x] I have followed (at least) the PR section of the contributing guide.

@dellink Thanks

authors: dellink oliviertassinari


text:
[docs] Improve draggable dialog demo wording

[x] I have followed (at least) the PR section of the contributing guide.

@Sanskar95 Thanks for a great first contribution to Material-UI 😄 🎉

@Sanskar95 Thanks for a great first contribution to Material-UI 😄 🎉

@joshwooding my pleasure, looking forward to contribute more


text:
Fix example code, replace "useState" for "useRef"

Small error I noticed today in the docs: https://material-ui.com/components/menus/#simple-menu

Got confused with the naming of the variables, closing


text:
[TextField] Make the position prop required in InputAdornment

[x] I have followed (at least) the PR section of the contributing guide.

Part of #20012

Did you find the context on why? I can't find the motivation back

Oh yes, I remember, it's because we don't use the context to infer the placement from the startAdornment or endAdornment prop. All the demo provide the prop anyway. It sounds good. It's not really a breaking change, more a cleanup. And in the future, we can consider using the context.

Actually, the prop is already required in the .d.ts file in v4. It was made optional in v5 here. I think we don't need to update the migration guide. Just adding an isRequired in v4 is fine.


text:
[docs] Migrate Autocomplete demos

Migrates Autocomplete demos to emotion. One of https://github.com/mui-org/material-ui/issues/16947
Preview: https://deploy-preview-26127--material-ui.netlify.app/components/autocomplete/

Actually, I like how unstyled components are using the CSS template string, and customization on the core component the JS Object syntax.

authors: mnajdova oliviertassinari


text:
[docs] Fix TextField demo layout

[x] I have followed (at least) the PR section of the contributing guide.

Fix #26703
Preview https://deploy-preview-26710--material-ui.netlify.app/components/text-fields/#layout

I would propose we significantly simplify the demo. We can start by only rendering the default variant of the TextField. The other ones adds nothing for the developers (maybe a bit for maintainers as a visual regression test, but adding margin is soo generic that I doubt we need to care).

@oliviertassinari Should we apply the same for similar demos of text field and keep only the default variant?

Should we apply the same for similar demos of text field and keep only the default variant?

I'm not sure. The reason why I proposed it here is because the outer margin is invariant to the style of the inner element.

I added fullWidth demo to preserve the info from the previous version.

authors: oliviertassinari siriwatknp vicasas


text:
[docs] Missing line on Composition page in "Composing multiple components"

Docs feedback
How can we improve Base UI documentation?
In the "Composing multiple components" section on the Composition page, there is a missing line that is not showing in the code example. The line is <Menu.Item render={<a href="base-ui.com" />}> (source here). Perhaps the prettier-ignore comment on the line above is causing it to be skipped somehow?

It's not just that line it looks like. The entire page's code blocks have issues seemingly due to the prettier-ignore as you point out!
It appears to be a regression from #1187

authors: DanielGibbsNZ atomiks

repo: mui/base-ui


text:
[Base] Configuration for globalStateClasses

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
Hi all,
I was looking for the ability of changing the global state class names. Given that I'm using the unstyled components @mui/base, would make sense to have my own names.
They seem hardcoded in the https://github.com/mui-org/material-ui/blob/master/packages/mui-base/src/generateUtilityClass/generateUtilityClass.ts
Is there workaround or roadmap to add this capability?
Examples 🌈
No response
Motivation 🔦
No response

Hi @jcdesousa. Yes, we are considering allowing to change (or even disable) autogenerated class names. We don't have a specific ETA for this, though.

I've started a POC to address this issue: #34380

I was looking for the ability of changing the global state class names. Given that I'm using the unstyled components @mui/base, would make sense to have my own names.

@jcdesousa we would love to understand in more depth the problem. What are you are trying to solve exactly? Is this about:
a. Making your DOM look cleaner in the dev tools? Meaning that you are happy to take the extra time hit of adding the necessary className for a cleaner DOM
b. You would like to "brand" these class names, something unique to your design system
c. Something else?
We have been discussing this topic internally multiple time, but without a clear problem statement and value proposition of making it configurable, we take the risk of making the majority of the developers worse off, e.g because of the extra bundle size, or docs area surface, or time spent not working on something else. So your feedback would be great! Thanks.

authors: jcdesousa michaldudak oliviertassinari

repo: mui/material-ui


text:
[Backdrop styling issue] - Some of the components rendered in "Backdrop" do not render with correct styles passed as props.

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Some of the components rendered in "Backdrop" do not render with correct styles passed as props. For example, a checkbox is placed in the Backdrop component with the color prop set as "success", but it's not changing the color to green.
Also Icon button colors or variants are not being affected with those props passed to it.
Expected behavior 🤔
Needs to be rendered with correct styles.
Steps to reproduce 🕹
Steps:

Context 🔦
No response
Your environment 🌎

`npx @mui/envinfo`
  Using chrome

It doesn't look like this bug report has enough info for one of us to reproduce it.
Please provide a CodeSandbox (https://material-ui.com/r/issue-template-latest), a link to a repository on GitHub, or provide a minimal code example that reproduces the problem.
Here are some tips for providing a minimal example: https://stackoverflow.com/help/mcve

I have the same issue. The children element of  couldn't be correctly rendered. If I remove the , it's rendered OK.

authors: Siying-Liang farrukh28 mnajdova


text:
TypeError: Using styled TextField in slots

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
I'm getting a type error in v5.12.3 when using a styled component in slots.
Here is the example code
import "./styles.css";
import styled from "@emotion/styled";
import { TextField } from "@mui/material";
import { DesktopDatePicker, LocalizationProvider } from "@mui/x-date-pickers";  // DesktopDatePicker v6.3.0
import dayjs from "dayjs";
import "dayjs/locale/de";
import { AdapterDayjs } from "@mui/x-date-pickers/AdapterDayjs";

export const FilterTextField = styled(TextField)`
  margin: 0 4px 0 0;

  .MuiInputBase-root {
    background-color: transparent;
  }

  input[type=time] {
    width: 150px;
  }
`;

export default function App() {
  return (
    <div>

      <LocalizationProvider dateAdapter={AdapterDayjs} adapterLocale="de">
      <DesktopDatePicker
        slots={{
          textField: FilterTextField
        }}
        onChange={(event) => console.log("onChange")}
        value={dayjs("2023-05-03")}
        slotProps={{
          textField: {
            inputProps: { disabled: true, value: "2023-05-03" },
            hiddenLabel: true,
            size: "small",
            variant: "filled",
            placeholder: "placeholder",
            error: false
          }
        }}
        minDate={dayjs()}
        maxDate={dayjs().add(2, "year")}
      />
  </LocalizationProvider>
    </div>
  );
}

I am using the styled component FilterTextField as a slot in DesktopDatePicker.
Current behavior 😯
The type error occurs at
 slots={{
          textField: FilterTextField
        }}

and is the following
TS2322: Type 'StyledComponent<{ variant?: TextFieldVariants | undefined; } & Omit<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps, "variant"> & { ...; }, {}, {}>' is not assignable to type 'ComponentType<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps> | undefined'.
  Type 'StyledComponent<{ variant?: TextFieldVariants | undefined; } & Omit<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps, "variant"> & { ...; }, {}, {}>' is not assignable to type 'FunctionComponent<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps>'.
    Types of property 'propTypes' are incompatible.
      Type 'WeakValidationMap<{ variant?: TextFieldVariants | undefined; } & Omit<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps, "variant"> & { ...; }> | undefined' is not assignable to type 'WeakValidationMap<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps> | undefined'.
        Type 'WeakValidationMap<{ variant?: TextFieldVariants | undefined; } & Omit<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps, "variant"> & { ...; }>' is not assignable to type 'WeakValidationMap<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps> | undefined'.
          Type 'WeakValidationMap<{ variant?: TextFieldVariants | undefined; } & Omit<OutlinedTextFieldProps | StandardTextFieldProps | FilledTextFieldProps, "variant"> & { ...; }>' is not assignable to type 'WeakValidationMap<FilledTextFieldProps>'.
            Types of property 'variant' are incompatible.
              Type 'Validator<TextFieldVariants | null | undefined> | undefined' is not assignable to type 'Validator<"filled"> | undefined'.
                Type 'Validator<TextFieldVariants | null | undefined>' is not assignable to type 'Validator<"filled">'.
                  Type 'TextFieldVariants | null | undefined' is not assignable to type '"filled"'.
                    Type 'undefined' is not assignable to type '"filled"'.

When using TextField instead of FilterTextField there is no problem. Changing the variant or not specifying it doesn't solve the problem.
Expected behavior 🤔
No type error.

The TextFieldProps type was updated in the latest version of Material UI i.e., v5.12.3, in https://github.com/mui/material-ui/pull/36737, while @mui/x-date-pickers is still dependent on previous Material UI version 5.12.2. See https://github.com/mui/mui-x/blob/dfe2a9a9a2dec87e15d2a9486189bf2e494100be/package.json#L89.
The Date and Time Pickers package has a peer dependency on @mui/material. Hence, there is a type mismatch. MUI related dependencies gets updated in the weekly dependency updates in MUI X. For example, https://github.com/mui/mui-x/pull/8554. So the types should be compatible in the next @mui/x-date-pickers release.

Tagging @mui/x to update Material UI.


text:
Couldn't execute the function successfully

C02YG0S3JGH8:dictionary viggy28$ python main.py
Enter word: abandoned
Traceback (most recent call last):
File "main.py", line 36, in
word = input("Enter word: ")
File "", line 1, in
NameError: name 'abandoned' is not defined
C02YG0S3JGH8:dictionary viggy28$ less data.json
C02YG0S3JGH8:dictionary viggy28$ python main.py
Enter word: contaminated
Traceback (most recent call last):
File "main.py", line 36, in
word = input("Enter word: ")
File "", line 1, in
NameError: name 'contaminated' is not defined

I think you have add the json file


text:
fix: remove profile.Version() and export Version constant instead

Remove Version() and  export the Version constant directly, so we can retrieve the version at compile time.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (7fe073c) to head (ec52799).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #173   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           42        42
  Lines         3471      3471
=========================================
  Hits          3471      3471

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

authors: codecov-commenter muktihari

repo: muktihari/fit


text:
Test Vectors

From a discussion in #230, it would be helpful to have test vectors for all of these keys. One possible solution would be a column next to description that either contains the test vectors directly, or points to an external document where they can be found.

I can't find the issue right now, but one of them in here talks about converting the primary entry-point to be a JSON doc, which would be much easier to extend with fields like "fixtures" rather than just adding more ordered columns. I think there was some agreement about making it compile-to-CSV so table.csv remains intact as is but the table.json is what we edit to add new entries.

authors: expede rvagg

repo: multiformats/multicodec


text:
Use separate git repositories for processor specs

Is your feature request related to a problem? Please describe.
I would like to use your RISCV processor implementation, but have my own forks as well.
Describe the solution you'd like
Using a separate git repo with a submodule in this one would be much preferred to a dirty merge.
Describe alternatives you've considered
I could just copy that section of your source, but that wouldn't credit you fairly or link back for possible updates.

https://github.com/mumbel/ghidra_riscv
Think it works, got an .so loaded into the 9.1.x BETA (ghidra-sre.org)

Superb, thank you!

authors: VTCAKAVSMoACE mumbel

repo: mumbel/ghidra


text:
Same tests

Files test/core/range/floating_point.wren and /test/core/range/from.wren same

Good catch!

authors: SteveVanzuriak munificent

repo: munificent/wren


text:
Use specific filesystem storage disk for image upload

Hello and thank you for your awesome work on this package!
I just updated to the latest version in order to get the image upload feature on the editor. However, I don't know if it's possible to upload images to a specific disk defined in Laravel's config/filesystems.php?
For example, I'm working on a blog and would like to have my image hosted on my s3 bucket which is defined in my config/filesystems.php:
<?php

return [
    'disks' => [
        // ...

        's3' => [
            'driver' => 's3',
            'key' => env('AWS_ACCESS_KEY_ID'),
            'secret' => env('AWS_SECRET_ACCESS_KEY'),
            'region' => env('AWS_DEFAULT_REGION'),
            'bucket' => env('AWS_BUCKET'),
            'url' => env('AWS_URL'),
        ],
];

Is this possible yet? It would be very helpful as it would allow us to profit from CDN cache on the blog posts featuring images.
Thank you

A straightforward way to do this without changing this package is to extend Http/Controllers/TinyImageController.php and implement your own logic in the upload function.

A straightforward way to do this without changing this package is to extend Http/Controllers/TinyImageController.php and implement your own logic in the upload function.

How do you do this, please?
I created a copy of Http/Controllers/TinyImageController.php in my App/Http/Controllers folder, and named it TinyImageControllerOverride.php
I made my changes to read the disk from a config entry, but my project doesn't seem to pick up the new controller, it still uses the vendor package controller. It's the first time I have tried to extend a vendor controller - I'm not sure where I'm going wrong.

Any help appreciated.

So I found a solution:
In my NovaServiceProvider, I used the bind method to switch out the controller.

This is what I ended up doing
class TinyImageController extends BaseTinyImageController
{
    public function upload(Request $request): JsonResponse
    {
        $validator = $this->validateRequest($request);
        if ($validator->fails()) {
            return response()->json(['error' => $validator->errors()->first()]);
        }

        reset($_FILES);
        $temp = current($_FILES);
        if (is_uploaded_file($temp['tmp_name'])) {
            // Process the image mine returns full url as I am uploading to CDN
            return response()->json(['location' => $imageUrl]);
        } else {
            return response()->json(['error' => 'Failed to move uploaded file.']);
        }
    }
}

And then for the /upload route
Route::post('/upload', [TinyImageController::class, 'upload'])->name('tinymce.upload')->middleware(TinymceMiddleware::class);

Wouldn't it just be a question of adding a config var of disk, which would replace the hardcoded public string in TinyImageController?

authors: JmzTaylor Oskar-Mikael WillyReyno sutcliffe121


text:
More straightfwd readme

What this PR does ?
Fixes

Merged another one following your feedbacks.

authors: erickhun maxence-charriere

repo: murlokswarm/app


text:
Support for unverified SSL

Is there any chance that support for request URI's that use SSL but have unverified certs can be added?
I tried to add myself, but it seems that my ruby knowledge isn't good enough :(

My latest pull request should address this quite nicely. When creating your JSON to initialize the object include :verify_ssl => "false"  like below
authjson = { :username => 'admin', :password => 'admin', :ip => '172.16.192.175', :verify_ssl => "false"}.to_json

Closing this one based on latest pull from Craig.

authors: jaxxstorm murraju nctiggy

repo: murraju/ucslib


text:
🛑 KD Home is down

In 718cbec, KD Home (http://kadambarid.in) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KD Home is back up in 8bf0848.

repo: muse-amuse/status


text:
Seems to be completely broken, example code doesn't work

The example code (refactored):
def log_events(event: Event) -> None:
    print(event)

async def main():
    logging.basicConfig(level=logging.DEBUG)
    async with ClientSession() as session:
        async with HomeAssistantClient("wss://xxx/api/websocket", get_secret("xxx"), session) as client:
            await client.subscribe_events(log_events)
            await client.start_listening()

Log:
DEBUG:hass_client:Connecting to Home Assistant Websocket API on wss://xxx/api/websocket
INFO:hass_client:Connected to Home Assistant xxx (version 2024.6.2)
DEBUG:hass_client:Publishing message:
{'event_type': '*', 'id': 2, 'type': 'subscribe_events'}
### no messages at all ###
### CTRL-C ###
DEBUG:hass_client:Closing client connection

While manual connection works flawlessly:
async def main():
    async with ClientSession() as session:
        socket = await session.ws_connect("wss://xxx/api/websocket", heartbeat=55, max_msg_size=1024 * 1024)

        version_msg = await socket.receive_json()
        version = version_msg["ha_version"]
        print(version)

        auth_command = {
            "type": "auth",
            "access_token": get_secret("xxx"),
        }
        await socket.send_json(auth_command)

        auth_result = await socket.receive_json()
        if auth_result["type"] != "auth_ok":
            raise AuthenticationError(auth_result.get("message", "Authentication failed"))

        await socket.send_json({'id': 1, 'type': 'subscribe_events', 'event_type': '*'})
        while True:
            message = await socket.receive_json()
            if message is None:
                break
            print(message)

It doesn't detect the result message (deadlock?):
When I comment out the waiting it starts to receive the messages, so it is a bug.
    async def send_command(self, command: str, **kwargs: dict[str, Any]) -> CommandResultData:
        """Send a command to the HA websocket and return response."""
        future: asyncio.Future[CommandResultData] = self._loop.create_future()
        if "message_id" in kwargs:
            message_id = kwargs.pop("message_id")
        else:
            message_id = await self._get_message_id()
        message = {"id": message_id, "type": command, **kwargs}
        self._result_futures[message_id] = future
        await self._send_json_message(message)
        # try:
        #     return await future
        # finally:
        #     self._result_futures.pop(message_id)

DEBUG:hass_client:Publishing message:
{'event_type': '*', 'id': 2, 'type': 'subscribe_events'}

DEBUG:hass_client:Received message:
WSMessage(type=<WSMsgType.TEXT: 1>, data='{"id":2,"type":"result","success":true,"result":null}', extra='')

DEBUG:hass_client:Received message:
.............

This project is still a WIP but thanks for fixing the issues !

I've started to implement it, but started to write nearly the same code, so it was waaay simper to fix this than to write it myself. :)
And closing this issue, the example was broken, not the library.

authors: lmagyar marcelveldt

repo: music-assistant/python-hass-client


text:
Another componentGrp => componentList

Change MEI 3.0 componentGrp to MEI 4.0 componentList element in FRBR components example. (Sorry, missed this one when fixing the other)

thanks again :-)

authors: kepper musicog

repo: music-encoding/guidelines


text:
add quarter-tone accidentals to data.ACCIDENTAL.IMPLICIT

From pd...@virginia.edu on March 14, 2013 17:20:36
The values in data.ACCIDENTAL.IMPLICIT are used by accid.ges, which captures a performed accidental.  Providing quarter-tone values makes it easier to "detune" a sounded note.
Original issue: http://code.google.com/p/music-encoding/issues/detail?id=149

From pd...@virginia.edu on March 14, 2013 14:24:04
This issue was closed by revision r870 .
Status: Fixed

repo: music-encoding/music-encoding


text:
🛑 Musikwerk DB is down

In 08b9161, Musikwerk DB (https://db.musikwerk-stuttgart.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Musikwerk DB is back up in ce3d32d after 21 minutes.

repo: musikwerk-stuttgart/upptime


text:
Missing functionality for clearing video data without releasing

Our app's architecture allows for an ExoPlayer to outlive the scope of a single video. For example, one ExoPlayer might go through the following state changes:
exoPlayer.prepare()
[ start View of some video ]
exoPlayer.setMediaItem([mediaId = 1])
[ play media for 10 seconds ]
[ user clears video; end playback]
exoPlayer.removeMediaItem([mediaId = 1])
[ wait some time ]
[ start new View of same video ]
exoPlayer.setMediaItem([mediaId = 1])

Currently, I don't believe that the Mux stats SDK can properly handle this behavior. If I do nothing, then the first "view" (from the user's perspective) and second "view" are combined into a single View in the MUX dashboard, with a massive pause in between, which is not reflective of the user experience (where there was two distinct playback sessions that occurred). I can call videoChange(CustomerVideoData()) after exoPlayer.removeMediaItem, but I'm not sure if that does what I would expect.
Ideally, I'd be able to call something like muxStats.clearVideo() after exoPlayer.removeMediaItem, which would prevent the Mux stats from being reported during the exoPlayer's downtime.
In a similar vein, we might also use this ExoPlayer instance for non-MUX playback, in which case I'd like to avoid reporting data during that session. From an API standpoint, being able to disable/enable stat collection without calling muxStats.release() would be ideal.
I'm aware that I could release() the Mux Stats after calling removeMediaItem, but that poses a couple of problems. Firstly, it would not be ideal to repeatedly recreate a MuxStats instance for the same ExoPlayer instance, and secondly, your documentation states that the MuxStats instance needs to be created prior to calling prepare() on the Player. Therefore, releasing and recreating an instance during the same ExoPlayer life-cycle would violate those expectations.

@cole-smith In v1.5.0 of the SDK, you should be able to find disable and enable() methods on MuxStatsSdkMedia3.
When disabled, the SDK should end the current view and go dormant until enable() is called again. enable() will start a new view, and apply the CustomerData you provide to it.
Please feel free to reach out if you have any problems!

authors: cole-smith daytime-em


text:
COD cash shipment option

Added the COD cash option to the shipment options, including an addition to the readme.
Description
You can set an amount of EUR for COD cash the customer can pay using cash on delivery.
The amount of cash can be set directly when creating a parcel
or with the setCODCash method:
$parcel = new \Mvdnbrk\MyParcel\Resources\Parcel([
    ...
    'options' => [
        'cod_cash' => 5,
        ...
    ],
]);

$parcel->setCODCash(5);

Motivation and context
This change adds a new feature.
How has this been tested?
This has been tested by comparing the XML sent to DHL with the documentation provided by DHL. A test shipment was also created and verified in the DHL backend.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My pull request addresses exactly one patch/feature.
[x] I have created a branch for this patch/feature.
[x] Each individual commit in the pull request is meaningful.
[x] All new and existing tests passed.
[x] If my change requires a change to the documentation, I have updated it accordingly.
[x] My code follows the code style of this project.

Thanks, could you add tests for this?

Tests have been added

Could you merge?

repo: mvdnbrk/dhlparcel-php-api


text:
Deprecate mvnd.builder.rule* and mvnd.builder.rules.provider.* features

Related #264

Looks good, though the 1.3 version number looks a bit strange. That should propably be 0.3

Indeed, thanks for noticing!

repo: mvndaemon/mvnd


text:
🛑 Hold My Pics is down

In 2c98995, Hold My Pics (https://holdmypics.com/) was down:

HTTP code: 503
Response time: 130 ms

Resolved: Hold My Pics is back up in ffc107b after 6 minutes.

repo: mvwicky/holdmyuptime


text:
Fix Issue #30 - Upgrade to Python 3

Upgrade pybo to using Python 3, as Python 2 is past its sunset.
@dreamflasher did all the hard work (see #31), all I did is simply updating .travis.yml to tell the CI pipeline to use Python 3.8.

As indicated by the tests, it seems there are quite a bit of code to be upgraded. Will report back.

Upon further investigation, it appears that simply bumping the CI Python version will not fix the build error, as pybo has a dependency reggie that is still running on Python 2 (see https://travis-ci.org/github/mwhoffman/pybo/builds/750753278).
Closing the pull request for now as it does not add extra value beyond what #31 already does.

repo: mwhoffman/pybo


text:
Need to move to autoconf

You need to realize not everyone is going to have the same configuration as you
and that most people are dumb. Please create an autoconf system or at least
explain in the read me about library and include paths. You should have liblua
as a library for this as it won't build without it.

COMMON_LDFLAGS=-llua

That's all I did, and I had to change/add a few of the header include paths and
library include paths. Most people cannot do this. You could also autodetect
where lua modules are installed.

If you need help figuring out how to do so, try Google and look at examples of
other lua modules.

Original issue reported on code.google.com by GRMrGe...@gmail.com on 7 Jan 2012 at 1:40

Closing this ancient issue. autoconf is rare among Lua modules, and most people who need to build modules don't generally struggle. We also have luarocks these days.
However if anyone wants to contribute better documentation that they think would be useful, feel free!


text:
'Cancel' for PromiseKit: fix for #1026, plus cleanup

Fix "Typechecking timeout compiling tests in v7 #1026" by specifying the closure return type in DispatcherTests
Remove unnecessary "#if swift" checks in the cancellable code and tests

Hmmmm, dunno why the code coverage check is failing...

CodeCOV is a little flakey at times

repo: mxcl/PromiseKit


text:
Swift 2.0 beta5

• Update MessageUI naming
• Make PMKAlertController error and cancellation conform to new standards

I incorrectly pushed to this branch which compounded the original changes I was trying to get integrated.  I will break them out into their own branches/PRs for clarity.


text:
README and OpenAPI updates

Standardizes readme with sections and a code example consistent with the
other language libraries. Also adds a section explaining how to generate
the library using the npm openapi-generator-cli tool. Also includes
recent updates to our OpenAPI spec.

:shipit:

:shipit:

repo: mxenabled/mx-platform-node


text:
Not Working With Eclipse

Hi i've downloaded this and copy and pasted it in eclipse and made all the changes required and added all the libraries and project is showing no error but when i run it app is carshing and logcat is showing error on MainActivity's setcontentview with error in this attached file.
Please Help
log.txt

you need android.support.v7.design.widget.CoordinatorLayout. check it in your library .


text:
Delete .github/workflows/work_flow_watch.yml

Which Issue(s) This PR Fixes(Closes)

Fixes #issue_id
Brief Description

How Did You Test This Change?

🚀Thanks for your contribution🎉. CodeRabbit will review your code first🔥

repo: mxsm/rocketmq-rust