text:
Should throw an error when no BLE command is sent after a request is received ?

I’m using your proxy with evcc, within in a custom charger and it’s working quite good. Today I observed some strange behavior with current not being adjusted and charge not stopping. When looking at the log, I saw the requests received, but nothing happening and no error:
2024/06/16 14:56:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:5]
2024/06/16 14:58:23 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:4]
2024/06/16 14:58:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:3]
2024/06/16 14:59:23 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:2]
2024/06/16 15:01:24 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:3]
2024/06/16 15:01:24 received command "charge_start" (VIN: MYMODELY) with body: map[]
2024/06/16 15:01:53 received command "wake_up" (VIN: MYMODELY) with body: map[]
2024/06/16 15:02:23 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:5]
2024/06/16 15:03:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:3]
2024/06/16 15:04:23 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:1]
2024/06/16 15:06:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:2]
2024/06/16 15:07:23 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:3]
2024/06/16 15:07:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:4]
2024/06/16 15:08:23 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:2]
2024/06/16 15:08:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:1]
2024/06/16 15:11:03 received command "charge_stop" (VIN: MYMODELY) with body: map[]
2024/06/16 15:14:53 received command "charge_stop" (VIN: MYMODELY) with body: map[]
2024/06/16 15:18:23 received command "charge_stop" (VIN: MYMODELY) with body: map[]
After restarting the container, everything started to work as expected again:
2024/06/16 16:11:50 TeslaBleHttpProxy is loading ...
2024/06/16 16:11:50 TeslaBleHttpProxy is running!
2024/06/16 16:12:27 received command "charge_stop" (VIN: MYMODELY) with body: map[]
2024/06/16 16:12:27 handle command: charge_stop (VIN: MYMODELY)
2024/06/16 16:12:27 Connecting to vehicle...
2024/06/16 16:12:29 sending command "charge_stop"...
2024/06/16 16:12:30 The command "charge_stop" was successfully executed.
Going back in the log I observed there has been some errors before and then at some point it seems the just give up trying to send BLE command until the restart.
2024/06/16 11:34:37 retrying in 6 seconds
2024/06/16 11:34:43 Connecting to vehicle...
2024/06/16 11:34:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:7]
2024/06/16 11:34:53 stop retrying after 3 attempts
2024/06/16 11:34:53 The command "set_charging_amps" was canceled:
2024/06/16 11:34:53 [Error]failed to connect to vehicle (A): failed to find BLE beacon for MYMODELY (S67a76e989a933054C): can't scan: context deadline exceeded
2024/06/16 11:34:54 handle command: set_charging_amps (VIN: MYMODELY)
2024/06/16 11:34:54 Connecting to vehicle...
2024/06/16 11:35:23 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:8]
2024/06/16 11:35:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:7]
2024/06/16 11:42:53 received command "set_charging_amps" (VIN: MYMODELY) with body: map[charging_amps:6]
Do you understand this behavior ? Instead of stopping to send BLE command, shouldn’t error be thrown for every command (and reported to evcc) ? Would it be possible to detect this special state and automatically restart the container ?
Let me know if you know if you need more information or test, I’ll be happy to help!

Thank you for the detailed description.
This behavior should not be possible. I will try to add some more debug logs next week, so we can locate the problem.

I'm having the same issue.
After a while commands are being received but not executed anymore.
If the proxy is restarted everything works again.
Can I enable some logging that could help in this case?
body=map[] 2024/06/29 16:51:24 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:3]
2024/06/29 16:51:49 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:4] 2024/06/29 16:55:05 INFO
received command command=charge_stop VIN= body=map[]
2024/06/29 16:55:21 INFO received command command=charge_stop
VIN= body=map[] 2024/06/29 16:55:49 INFO received command
command=charge_stop VIN= body=map[] 2024/06/29 16:56:05
INFO received command command=charge_stop VIN= body=map[]
2024/06/29 16:56:30 INFO received command command=charge_stop
VIN= body=map[] 2024/06/29 16:56:44 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:2]
2024/06/29 16:57:04 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:3] 2024/06/29 16:57:29 INFO
received command command=charge_stop VIN= body=map[]
2024/06/29 16:57:55 INFO received command command=charge_stop
VIN= body=map[] 2024/06/29 16:58:22 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:2]
2024/06/29 16:58:34 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:3] 2024/06/29 16:59:19 INFO
received command command=set_charging_amps VIN=
body=map[charging_amps:4] 2024/06/29 16:59:29 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:3]
2024/06/29 16:59:44 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:4] 2024/06/29 17:03:54 INFO
received command command=set_charging_amps VIN=
body=map[charging_amps:3] 2024/06/29 17:06:14 INFO received command
command=charge_stop VIN= body=map[] 2024/06/29 17:06:34
INFO received command command=set_charging_amps VIN=
body=map[charging_amps:3] 2024/06/29 17:32:59 INFO received command
command=charge_stop VIN= body=map[] 2024/06/29 17:33:19
INFO received command command=set_charging_amps VIN=
body=map[charging_amps:3] 2024/06/29 17:34:59 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:3]
2024/06/29 17:35:29 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:2] 2024/06/29 17:35:59 INFO
received command command=set_charging_amps VIN=
body=map[charging_amps:3] 2024/06/29 17:36:29 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:3]
2024/06/29 17:36:54 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:2] 2024/06/29 17:37:09 INFO
received command command=set_charging_amps VIN=
body=map[charging_amps:3] 2024/06/29 17:41:49 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:2]
2024/06/29 17:42:19 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:3] 2024/06/29 17:43:39 INFO
received command command=set_charging_amps VIN=
body=map[charging_amps:2] 2024/06/29 17:53:49 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:2]
2024/06/29 17:56:14 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:2] 2024/06/29 18:08:30 INFO
received command command=charge_stop VIN= body=map[]
2024/06/29 18:08:59 INFO received command command=charge_stop
VIN= body=map[] 2024/06/29 18:09:22 INFO received command
command=set_charging_amps VIN= body=map[charging_amps:2]
2024/06/29 18:09:47 INFO received command command=set_charging_amps
VIN= body=map[charging_amps:2]
2024/06/29 18:23:42 INFO received command command=charge_stop VIN= body=map[]

Can you please set the environment variable logLevel to debug and post the log of when this happens?
I wasn’t able to reproduce this.

@gauner1986, are you calling the ble proxy from a custom vehicle or a custom charger in evcc ?
The reason I’m asking that is that I had this issue when using it at the charger level, and after charging a non-Tesla vehicle on my TWC3. Since I switched to using the ble proxy at the vehicle level for, I didn’t experience the issue. So it may be the accumulation of errors when trying to send commands to the no-connected vehicle that may lead to this weird state.
In other words, can you provide more information on the context in which you are using the ble proxy ? This could help, in addition to more detail logs, to find the root cause of that.

I have bumped the log level to debug and am hoping for a sunny day in the next time.
I'm actually not using EVCC at all. I have my own automations in home assistant which do my solar excess charging.
Excerpt of my configuration.yaml
rest_command:
tesla_set_charging_amps:
url: http://pi:8080/api/1/vehicles/VIN/command/set_charging_amps
method: POST
payload: '{"charging_amps": "{{charging_amps}}"}'
content_type:  'application/json'
tesla_set_charge_limit:
url: http://pi:8080/api/1/vehicles/VIN/command/set_charge_limit
method: POST
payload: '{"percent": "{{charge_limit}}"}'
content_type:  'application/json'
tesla_wakeup:
url: http://pi:8080/api/1/vehicles/VIN/command/wake_up
method: POST
tesla_charge_start:
url: http://pi:8080/api/1/vehicles/VIN/command/charge_start
method: POST
tesla_charge_stop:
url: http://pi:8080/api/1/vehicles/VIN/command/charge_stop

Usually if that happens you receive a connection error though. In our error case here there's no feedback to the received commands at all.
I had a case where it just happened in a series of events without any delays:
2024/06/28 16:24:04 INFO The command was successfully executed. command=charge_stop
2024/06/28 16:24:24 INFO received command command=charge_start VIN=VIN body=map[]
2024/06/28 16:24:24 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2]
2024/06/28 16:24:25 INFO handle command command=charge_start VIN=VIN
2024/06/28 16:24:28 INFO The command was successfully executed. command=charge_start
2024/06/28 16:24:29 INFO handle command command=set_charging_amps VIN=VIN
2024/06/28 16:24:32 INFO The command was successfully executed. command=set_charging_amps
2024/06/28 16:24:54 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3]
2024/06/28 16:24:55 INFO handle command command=set_charging_amps VIN=VIN
2024/06/28 16:24:58 INFO The command was successfully executed. command=set_charging_amps
2024/06/28 16:25:15 INFO received command command=charge_stop VIN=VIN body=map[]
2024/06/28 16:25:15 INFO handle command command=charge_stop VIN=VIN
2024/06/28 16:25:24 INFO received command command=charge_stop VIN=VIN body=map[]
2024/06/28 16:26:05 INFO received command command=charge_stop VIN=VIN body=map[]
2024/06/28 16:26:24 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3]
2024/06/28 16:26:35 INFO received command command=charge_stop VIN=VIN body=map[]
2024/06/28 16:26:44 INFO received command command=charge_stop VIN=VIN body=map[]
2024/06/28 16:27:04 INFO received command command=charge_stop VIN=VIN body=map[]
2024/06/28 16:27:19 INFO received command command=charge_stop VIN=VIN body=map[]
2024/06/28 16:30:40 INFO received command command=charge_stop VIN=VIN body=map[]
2024/06/28 16:32:04 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3]
2024/06/28 16:32:24 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3]

Are you using on board ble or a dongle? I had a dongle that would crash
until I rebooted but that’s probably not your issue because that gave errors
On Tue, 2 Jul 2024 at 08:27, gauner1986 @.***> wrote:

Usually if that happens you receive a connection error though. In our
error case here there's no feedback to the received commands at all.
I had a case where it just happened in a series of events without any
delays:
2024/06/28 16:24:04 INFO The command was successfully executed.
command=charge_stop
2024/06/28 16:24:24 INFO received command command=charge_start VIN=VIN
body=map[]
2024/06/28 16:24:24 INFO received command command=set_charging_amps
VIN=VIN body=map[charging_amps:2]
2024/06/28 16:24:25 INFO handle command command=charge_start VIN=VIN
2024/06/28 16:24:28 INFO The command was successfully executed.
command=charge_start
2024/06/28 16:24:29 INFO handle command command=set_charging_amps VIN=VIN
2024/06/28 16:24:32 INFO The command was successfully executed.
command=set_charging_amps
2024/06/28 16:24:54 INFO received command command=set_charging_amps
VIN=VIN body=map[charging_amps:3]
2024/06/28 16:24:55 INFO handle command command=set_charging_amps VIN=VIN
2024/06/28 16:24:58 INFO The command was successfully executed.
command=set_charging_amps
2024/06/28 16:25:15 INFO received command command=charge_stop VIN=VIN
body=map[]
2024/06/28 16:25:15 INFO handle command command=charge_stop VIN=VIN
2024/06/28 16:25:24 INFO received command command=charge_stop VIN=VIN
body=map[]
2024/06/28 16:26:05 INFO received command command=charge_stop VIN=VIN
body=map[]
2024/06/28 16:26:24 INFO received command command=set_charging_amps
VIN=VIN body=map[charging_amps:3]
2024/06/28 16:26:35 INFO received command command=charge_stop VIN=VIN
body=map[]
2024/06/28 16:26:44 INFO received command command=charge_stop VIN=VIN
body=map[]
2024/06/28 16:27:04 INFO received command command=charge_stop VIN=VIN
body=map[]
2024/06/28 16:27:19 INFO received command command=charge_stop VIN=VIN
body=map[]
2024/06/28 16:30:40 INFO received command command=charge_stop VIN=VIN
body=map[]
2024/06/28 16:32:04 INFO received command command=set_charging_amps
VIN=VIN body=map[charging_amps:3]
2024/06/28 16:32:24 INFO received command command=set_charging_amps
VIN=VIN body=map[charging_amps:3]
—
Reply to this email directly, view it on GitHub
https://github.com/wimaha/TeslaBleHttpProxy/issues/6#issuecomment-2201200666,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKH2FP3GXU4BLG6PDHAJEQTZKHJUJAVCNFSM6AAAAABJMWDSZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBRGIYDANRWGY
.
You are receiving this because you commented.Message ID:
@.***>

I'm using a raspberry pi 1 with a USB dongle.

Check dmesg for an issues in there. I found that my UB400 worked fine but
my UB500 would crash on raspian. On Ubuntu on a pi zero 2 w the UB500
worked fine
On Tue, 2 Jul 2024 at 09:00, gauner1986 @.***> wrote:

I'm using a raspberry pi 1 with a USB dongle.
—
Reply to this email directly, view it on GitHub
https://github.com/wimaha/TeslaBleHttpProxy/issues/6#issuecomment-2201325408,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKH2FPZCD4TPB2CT4RQ6ISTZKHNRBAVCNFSM6AAAAABJMWDSZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBRGMZDKNBQHA
.
You are receiving this because you commented.Message ID:
@.***>

Will do. Though last time I had the problem it was enough to simply restart the proxy.

There are no unhandled errors in the program. So maybe the problem is in the ble package itself. It seems the handle loop is blocked without return or error.
Maybe we can find the error with debug log.

I have the same issue on a Raspberry pi Zero W.  When charging, I hit the proxy every 15 seconds with a "set_charging_amps" command.  After several hours, I see repeated "received command", but the commands are not sent to the car, nor is there any other error or informational message.

Any Debug Logs?

I've created a new version with the following improvements that might solve this problem:

The ble connection will be reused for all subsequent requests for 30 seconds
This improvement has been incorporated: https://github.com/teslamotors/vehicle-command/pull/269

The version is under the dev tag on Docker: image: wimaha/tesla-ble-http-proxy:dev
Could you please test this version? Thank you!

Couldn't test a lot in the past few days because of very bad weather in Hamburg.
I'm building myself and running without docker due to system constraints. Did you commit in a special branch?

Yes, you will find it in the branch refactor/performance-optimization: https://github.com/wimaha/TeslaBleHttpProxy/tree/refactor/performance-optimization

Any Debug Logs?

I am now running your "refactor" version, with debug set.  I'll share my experience and the logs, should the issue reoccur.

Interesting behaviour...
I notice that when the proxy throws this error, my car goes to zero amps (as shown on the app and in my energy monitor) and then quickly climbs back up to the target.  When I kill the proxy, the odd behaviour goes away.
Thoughts?
2024/07/07 12:31:46 INFO TeslaBleHttpProxy is loading ... 2024/07/07 12:31:46 DEBU LogLevel set to debug 2024/07/07 12:31:46 INFO TeslaBleHttpProxy is running! 2024/07/07 12:32:04 INFO received command command=set_charging_amps VIN=LRWYHCEL4PC726XYZ body=map[charging_amps:23] 2024/07/07 12:32:05 INFO handle command command=set_charging_amps VIN=LRWYHCEL4PC726XYZ 2024/07/07 12:32:06 WARN failed to connect to vehicle (A): ble: failed to enumerate device services: ATT request failed: input channel closed: io: read/write on closed pipe 2024/07/07 12:32:06 INFO retrying in 3 seconds 2024/07/07 12:32:10 WARN failed to connect to vehicle (A): ble: failed to enumerate device services: ATT request failed: input channel closed: io: read/write on closed pipe 2024/07/07 12:32:10 INFO retrying in 6 seconds 2024/07/07 12:32:19 INFO The command was successfully executed. command=set_charging_amps

It happened again today. This time with debug logs enabled. I'm on 89dba612b2b71a91639b3cc8dee4397979626455.
2024/07/07 15:25:09 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:25:10 INFO connectToVehicle ...
2024/07/07 15:25:10 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:25:10 DEBU Connecting to vehicle (A)...
2024/07/07 15:25:10 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:25:10 DEBU Create vehicle object ...
2024/07/07 15:25:10 DEBU Connecting to vehicle (B)...
2024/07/07 15:25:10 DEBU start VCSEC session...
2024/07/07 15:25:12 DEBU car successfully wakeup
2024/07/07 15:25:12 DEBU start Infotainment session...
2024/07/07 15:25:13 INFO Session started
2024/07/07 15:25:13 DEBU sending command ... command=charge_start
2024/07/07 15:25:14 WARN failed to start charge: car could not execute command: disconnected
2024/07/07 15:25:14 INFO retrying in 3 seconds
2024/07/07 15:25:18 WARN failed to start charge: car could not execute command: disconnected
2024/07/07 15:25:18 INFO retrying in 6 seconds
2024/07/07 15:25:24 ERRO The command was canceled. command=charge_start err="failed to start charge: context deadline exceeded"
2024/07/07 15:25:24 DEBU Disconnect vehicle (A)
2024/07/07 15:25:24 DEBU Close connection (A)
2024/07/07 15:25:26 INFO connectToVehicle ...
2024/07/07 15:25:26 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:25:26 DEBU Connecting to vehicle (A)...
2024/07/07 15:25:26 DEBU Create vehicle object ...
2024/07/07 15:25:26 DEBU Connecting to vehicle (B)...
2024/07/07 15:25:26 DEBU start VCSEC session...
2024/07/07 15:25:27 DEBU car successfully wakeup
2024/07/07 15:25:27 DEBU start Infotainment session...
2024/07/07 15:25:28 INFO Session started
2024/07/07 15:25:28 DEBU sending command ... command=set_charging_amps
2024/07/07 15:25:29 INFO The command was successfully executed. command=set_charging_amps
2024/07/07 15:25:54 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:25:54 DEBU sending command ... command=charge_start
2024/07/07 15:25:54 DEBU Disconnect vehicle (A)
2024/07/07 15:25:54 DEBU Close connection (A)
2024/07/07 15:25:54 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:25:55 INFO connectToVehicle ...
2024/07/07 15:25:55 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:25:55 DEBU Connecting to vehicle (A)...
2024/07/07 15:25:58 DEBU Create vehicle object ...
2024/07/07 15:25:58 DEBU Connecting to vehicle (B)...
2024/07/07 15:25:58 DEBU start VCSEC session...
2024/07/07 15:26:00 DEBU car successfully wakeup
2024/07/07 15:26:00 DEBU start Infotainment session...
2024/07/07 15:26:10 DEBU Disconnect vehicle (B)
2024/07/07 15:26:10 DEBU Close connection (B)
2024/07/07 15:26:10 WARN failed to perform handshake with vehicle (B): context deadline exceeded
2024/07/07 15:26:10 INFO retrying in 3 seconds
2024/07/07 15:26:13 DEBU trying connecting to vehicle attempt=2
2024/07/07 15:26:13 DEBU Connecting to vehicle (A)...
2024/07/07 15:26:19 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:26:19 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:26:28 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:26:28 INFO retrying in 6 seconds
2024/07/07 15:26:34 DEBU trying connecting to vehicle attempt=3
2024/07/07 15:26:34 DEBU Connecting to vehicle (A)...
2024/07/07 15:26:39 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:26:39 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:26:49 ERRO stop retrying after 3 attempts error="failed to connect to vehicle (A): context deadline exceeded"
2024/07/07 15:26:50 INFO connectToVehicle ...
2024/07/07 15:26:50 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:26:50 DEBU Connecting to vehicle (A)...
2024/07/07 15:27:05 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:27:05 INFO retrying in 3 seconds
2024/07/07 15:27:08 DEBU trying connecting to vehicle attempt=2
2024/07/07 15:27:08 DEBU Connecting to vehicle (A)...
2024/07/07 15:27:23 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:27:23 INFO retrying in 6 seconds
2024/07/07 15:27:29 DEBU trying connecting to vehicle attempt=3
2024/07/07 15:27:29 DEBU Connecting to vehicle (A)...
2024/07/07 15:27:44 ERRO stop retrying after 3 attempts error="failed to connect to vehicle (A): context deadline exceeded"
2024/07/07 15:27:45 INFO connectToVehicle ...
2024/07/07 15:27:45 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:27:45 DEBU Connecting to vehicle (A)...
2024/07/07 15:27:59 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:27:59 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3]
2024/07/07 15:28:00 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:28:00 INFO retrying in 3 seconds
2024/07/07 15:28:03 DEBU trying connecting to vehicle attempt=2
2024/07/07 15:28:03 DEBU Connecting to vehicle (A)...
2024/07/07 15:28:18 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:28:18 INFO retrying in 6 seconds
2024/07/07 15:28:19 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:28:19 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:28:24 DEBU trying connecting to vehicle attempt=3
2024/07/07 15:28:24 DEBU Connecting to vehicle (A)...
2024/07/07 15:28:34 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:28:34 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:28:39 ERRO stop retrying after 3 attempts error="failed to connect to vehicle (A): context deadline exceeded"
2024/07/07 15:28:40 INFO connectToVehicle ...
2024/07/07 15:28:40 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:28:40 DEBU Connecting to vehicle (A)...
2024/07/07 15:28:54 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:28:54 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:28:55 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:28:55 INFO retrying in 3 seconds
2024/07/07 15:28:58 DEBU trying connecting to vehicle attempt=2
2024/07/07 15:28:58 DEBU Connecting to vehicle (A)...
2024/07/07 15:29:04 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:29:04 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:29:13 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:29:13 INFO retrying in 6 seconds
2024/07/07 15:29:19 DEBU trying connecting to vehicle attempt=3
2024/07/07 15:29:19 DEBU Connecting to vehicle (A)...
2024/07/07 15:29:34 ERRO stop retrying after 3 attempts error="failed to connect to vehicle (A): context deadline exceeded"
2024/07/07 15:29:35 INFO connectToVehicle ...
2024/07/07 15:29:35 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:29:35 DEBU Connecting to vehicle (A)...
2024/07/07 15:29:50 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:29:50 INFO retrying in 3 seconds
2024/07/07 15:29:53 DEBU trying connecting to vehicle attempt=2
2024/07/07 15:29:53 DEBU Connecting to vehicle (A)...
2024/07/07 15:30:04 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:30:04 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:30:08 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:30:08 INFO retrying in 6 seconds
2024/07/07 15:30:14 DEBU trying connecting to vehicle attempt=3
2024/07/07 15:30:14 DEBU Connecting to vehicle (A)...
2024/07/07 15:30:19 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:30:19 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:30:29 ERRO stop retrying after 3 attempts error="failed to connect to vehicle (A): context deadline exceeded"
2024/07/07 15:30:31 INFO connectToVehicle ...
2024/07/07 15:30:31 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:30:31 DEBU Connecting to vehicle (A)...
2024/07/07 15:30:46 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:30:46 INFO retrying in 3 seconds
2024/07/07 15:30:49 DEBU trying connecting to vehicle attempt=2
2024/07/07 15:30:49 DEBU Connecting to vehicle (A)...
2024/07/07 15:30:49 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:30:49 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:31:04 WARN failed to connect to vehicle (A): context deadline exceeded
2024/07/07 15:31:04 INFO retrying in 6 seconds
2024/07/07 15:31:04 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:31:04 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:31:10 DEBU trying connecting to vehicle attempt=3
2024/07/07 15:31:10 DEBU Connecting to vehicle (A)...
2024/07/07 15:31:19 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:31:19 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:31:25 ERRO stop retrying after 3 attempts error="failed to connect to vehicle (A): context deadline exceeded"
2024/07/07 15:31:26 INFO connectToVehicle ...
2024/07/07 15:31:26 DEBU trying connecting to vehicle attempt=1
2024/07/07 15:31:26 DEBU Connecting to vehicle (A)...
2024/07/07 15:31:49 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:31:49 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:33:39 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:33:39 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3]
2024/07/07 15:34:09 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:34:09 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:35:59 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:35:59 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:39:09 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:39:09 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:39:39 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:39:39 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3]
2024/07/07 15:39:49 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:39:49 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:40:14 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:40:14 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:40:24 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:40:24 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:41:34 INFO received command command=charge_start VIN=VIN body=map[]
2024/07/07 15:41:34 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:42:53 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:43:54 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:44:08 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:44:58 INFO received command command=charge_stop VIN=VIN body=map[]
2024/07/07 15:45:28 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:45:40 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2]
2024/07/07 15:45:59 INFO received command command=charge_stop VIN=VIN body=map[]
2024/07/07 15:47:13 INFO received command command=charge_stop VIN=VIN body=map[]
2024/07/07 15:47:38 INFO received command command=charge_stop VIN=VIN body=map[]
2024/07/07 15:47:59 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:48:09 INFO received command command=charge_stop VIN=VIN body=map[]
2024/07/07 15:48:23 INFO received command command=charge_stop VIN=VIN body=map[]
2024/07/07 15:49:09 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:49:33 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3]
2024/07/07 15:50:28 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5]
2024/07/07 15:51:03 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:51:28 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4]
2024/07/07 15:52:18 INFO received command command=charge_stop VIN=VIN body=map[]
2024/07/07 15:53:28 INFO received command command=charge_stop VIN=VIN body=map[]
2024/07/07 15:53:56 INFO received command command=charge_stop VIN=VIN body=map[]

Thank you for the logs. I can see the part which is blocking. Unfortunately the blocking part is ether in the tesla command repository or in the go ble package.
But I think the teal problem here ist, that the connection can't be established after 18 attempts. Perhaps we should add something, that after 5 failed attempts no new commands are accepted and the proxy waits for a view minutes for the connection issue to be resolved.

Hm. Not sure if this is the only trigger. There were other cases where the connection was fine beforehand.

Got a new occurence. I didn't pay a lot of attention the last few days. There was one connection issue again and then it got stalled for days without recovery:
2024/07/11 11:09:17 INFO The command was successfully executed. command=set_charging_amps 2024/07/11 11:09:21 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:09:21 DEBU sending command ... command=set_charging_amps 2024/07/11 11:09:22 INFO The command was successfully executed. command=set_charging_amps 2024/07/11 11:09:31 INFO received command command=charge_stop VIN=VIN body=map[] 2024/07/11 11:09:31 DEBU sending command ... command=charge_stop 2024/07/11 11:09:32 INFO The command was successfully executed. command=charge_stop 2024/07/11 11:09:45 DEBU Connection Timeout 2024/07/11 11:09:45 DEBU Disconnect vehicle (A) 2024/07/11 11:09:45 DEBU Close connection (A) 2024/07/11 11:10:50 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:10:51 INFO connectToVehicle ... 2024/07/11 11:10:51 DEBU trying connecting to vehicle attempt=1 2024/07/11 11:10:51 DEBU Connecting to vehicle (A)... 2024/07/11 11:10:51 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3] 2024/07/11 11:11:10 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:11:11 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:14:45 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:14:45 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:16:15 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:16:15 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:16:55 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:16:55 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:17:50 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:17:50 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:18:55 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:18:56 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:19:10 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:19:10 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:19:40 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:19:40 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:21:00 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:21:00 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:27:35 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:27:35 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:30:15 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:30:15 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3] 2024/07/11 11:30:25 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:30:25 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:32:00 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:32:00 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:34:25 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:34:25 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:34:40 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:34:40 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:2] 2024/07/11 11:37:35 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:37:35 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3] 2024/07/11 11:38:00 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:38:00 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3] 2024/07/11 11:38:55 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:38:55 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3] 2024/07/11 11:39:35 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:39:35 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3] 2024/07/11 11:39:45 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:39:45 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4] 2024/07/11 11:40:20 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:40:20 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3] 2024/07/11 11:40:35 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:40:35 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:3] 2024/07/11 11:40:45 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:40:45 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4] 2024/07/11 11:41:45 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:41:45 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:5] 2024/07/11 11:42:30 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:42:30 INFO received command command=set_charging_amps VIN=VIN body=map[charging_amps:4] 2024/07/11 11:42:45 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/11 11:43:00 INFO received command command=charge_start VIN=VIN body=map[] .... 2024/07/11 18:07:34 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/12 20:48:45 INFO received command command=charge_stop VIN=VIN body=map[] 2024/07/14 09:28:42 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/14 09:49:01 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/14 10:26:11 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/14 13:14:05 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/14 14:10:05 INFO received command command=charge_stop VIN=VIN body=map[] 2024/07/15 09:31:56 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/15 10:17:05 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/15 10:32:17 INFO received command command=charge_start VIN=VIN body=map[] 2024/07/15 10:33:35 INFO received command command=charge_start VIN=VIN body=map[]
Is there a possibility to monitor a command and kill it if no success event is received in a certain time frame?

I cam back from a week-end and no command are working, even after restarting evcc and TeslaBleHttpProxy and even waking up / starting the car from the phone app.
My setup is interesting because I am migrating and I have two instances of TeslaBleHttpProxy v1.2 running, one on a Raspberry Pi4 (docker image) and one on an Intel NUC (self go compile).
To switch, I change the evcc config and restart. But I have the same problem on both machines... Actually I have another Pi4 and same problem. Also generating new key and trying to register it did work.
So I wonder is the problem is on TeslaBleHttpProxy, or could it be on the car side that sometimes just don't want to communicate at all? I tried to remove all the "Unknow key" to kind of clean, but now I have difficulty to recreate a key.
It is so sad to have seen it working for hours or days and now it fail. I'll sleep on that and try again whenever possible with https://github.com/teslamotors/vehicle-command/ to check the basics.

I tested with vehicule-command after successfully adding a key and then copying that key to ~/TeslaBleHttpProxy/key but I had no success with evcc controling the charge (here trying to stop the charge).
dglaude@dglaude-NUC5PPYB:~/evcc$ sudo journalctl -fau TeslaBleHttpProxy
jui 21 23:51:57 dglaude-NUC5PPYB systemd[1]: Started TeslaBleHttpProxy.
jui 21 23:51:57 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:51:57 INFO TeslaBleHttpProxy 1.2 is loading ...
jui 21 23:51:57 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:51:57 INFO BleControl initialized
jui 21 23:51:57 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:51:57 INFO TeslaBleHttpProxy is running!
jui 21 23:58:47 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:58:47 INFO received command=charge_stop body=map[]
jui 21 23:58:47 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:58:47 INFO connecting to Vehicle ...
jui 21 23:59:02 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:59:02 WARN failed to connect to vehicle (A): context deadline exceeded
jui 21 23:59:02 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:59:02 INFO retrying in 3 seconds
jui 21 23:59:07 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:59:07 can't accept: listner timed out
jui 21 23:59:20 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:59:20 WARN failed to connect to vehicle (A): context deadline exceeded
jui 21 23:59:20 dglaude-NUC5PPYB TeslaBleHttpProxy[434183]: 2024/07/21 23:59:20 INFO retrying in 6 seconds```

The interesting part is that if I try with `vehicule-command` while `TeslaBleHttpProxy` still run, I get error. I had to stop `TeslaBleHttpProxy` then at second attempt I was able to change the charge speed.

```dglaude@dglaude-NUC5PPYB:~/GIT/vehicle-command$ sudo /home/dglaude/go/bin/tesla-control -vin XP7YYYYY1YY999999 -key-file private.pem -ble charging-set-amps 6
Error: failed to find a BLE device: can't init hci: no devices available: (hci0: can't down device: device or resource busy)
dglaude@dglaude-NUC5PPYB:~/GIT/vehicle-command$ sudo systemctl stop TeslaBleHttpProxy.service
dglaude@dglaude-NUC5PPYB:~/GIT/vehicle-command$ sudo /home/dglaude/go/bin/tesla-control -vin XP7YYYYY1YY999999 -key-file private.pem -ble charging-set-amps 6
Error: ble: failed to enumerate device services: ATT request failed: input channel closed: io: read/write on closed pipe
dglaude@dglaude-NUC5PPYB:~/GIT/vehicle-command$ sudo /home/dglaude/go/bin/tesla-control -vin XP7YYYYY1YY999999 -key-file private.pem -ble charging-set-amps 6
dglaude@dglaude-NUC5PPYB:~/GIT/vehicle-command$```

Right now it mean that `vehicule-command` is working and `TeslaBleHttpProxy` is not working anymore. But the key is right and the hardware is capable...

Notice that the key created with `vehicule-command` is visible as unknown in the car UI (in French "Verrouillage" section) and can be renamed.

Some positive progress in my setup.
The whole daylight, we had to manually adjust the power level...
I was about to give a try to an MQTT alternative to this software with the hope that it would solve my problem.
But before that, I moved two Pi4 and my NUC closer to the car, I was already near, but now I am as close as possible without being outside. As a result, my two instances of TeslaBleHttpProxy one on each Pi4 are working as expected (the NUC does not work yet).
Maybe it is not related to the distance, maybe it is just that both machine have been off during the move and the new installation...
Still, it works for me (at least tonight). Either both stop working in a few hours or day... or maybe those few meter made the difference. If you have trouble, please give that a try.
I also suspect that Tesla may have included power saving change in recent software upgrade, and that could include BLE power/sensitivity or make the car harder to wake up for us.

Another occurence. After a timeout again:
Jul 28 16:20:00 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:00 INFO The command was successfully executed. command=charge_start Jul 28 16:20:00 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:00 DEBU sending command ... command=set_charging_amps Jul 28 16:20:01 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:01 INFO The command was successfully executed. command=set_charging_amps Jul 28 16:20:17 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:17 DEBU Connection Timeout Jul 28 16:20:17 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:17 DEBU Disconnect vehicle (A) Jul 28 16:20:17 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:17 DEBU Close connection (A) Jul 28 16:20:25 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:25 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:2] Jul 28 16:20:25 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:25 INFO connectToVehicle ... Jul 28 16:20:25 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:25 DEBU trying connecting to vehicle attempt=1 Jul 28 16:20:25 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:20:25 DEBU Connecting to vehicle (A)... Jul 28 16:21:24 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:21:24 INFO received command command=charge_stop VIN=5YJSA7E54PF503416 body=map[] Jul 28 16:21:32 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:21:32 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:2] Jul 28 16:22:24 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:22:24 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:3] Jul 28 16:22:34 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:22:34 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:4] Jul 28 16:22:59 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:22:59 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:3] Jul 28 16:23:44 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:23:44 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:3] Jul 28 16:24:09 DietPi TeslaBleHttpProxy[536]: 2024/07/28 16:24:09 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:3] .... Jul 28 18:25:46 DietPi TeslaBleHttpProxy[536]: 2024/07/28 18:25:46 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:2] Jul 28 18:26:31 DietPi TeslaBleHttpProxy[536]: 2024/07/28 18:26:31 INFO received command command=charge_stop VIN=5YJSA7E54PF503416 body=map[] Jul 28 18:27:24 DietPi TeslaBleHttpProxy[536]: 2024/07/28 18:27:24 INFO received command command=charge_stop VIN=5YJSA7E54PF503416 body=map[] Jul 28 18:29:14 DietPi TeslaBleHttpProxy[536]: 2024/07/28 18:29:14 INFO received command command=set_charging_amps VIN=5YJSA7E54PF503416 body=map[charging_amps:2] Jul 28 18:34:35 DietPi TeslaBleHttpProxy[536]: 2024/07/28 18:34:35 INFO received command command=charge_stop VIN=5YJSA7E54PF503416 body=map[] Jul 28 18:36:35 DietPi TeslaBleHttpProxy[536]: 2024/07/28 18:36:35 INFO received command command=charge_stop VIN=5YJSA7E54PF503416 body=map[] Jul 28 18:41:28 DietPi TeslaBleHttpProxy[536]: 2024/07/28 18:41:28 INFO received command command=charge_stop VIN=5YJSA7E54PF503416 body=map[]

There are now even more logs with version 1.2.2. Please use this version and report any error logs with this problem. Thank You!!

The Bug ist finally resolved with Version 1.2.4 :-)

Unfortunately it still seems to happen sometimes. :(

Sep 15 12:38:36 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:36 INFO sending command=set_charging_amps body=map[charging_amps:4]
Sep 15 12:38:36 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:36+02:00 [debug] TX: 320208033a1212108f0e67054671d7009f643bff2618dfd79a0310073b08aec6d15756a66ee41ec4c537035207dfc8391437b7dd6a81010a430a4104ed711e034775d6dc32594edc8adb96eed0fba6e09807eec593bc449a9693d9ba476415de3edb6eb53a7cd735e98c961c3e6bdfc99afcbb54ee75bb5b9edd76782a3a0a10781854b66ccb43e863e90a29222647a4120ce2edc231fb788c4aa8bff5c618c903251cdb07002a109b5a4604be2dd78851cb9db2ba9936cf
Sep 15 12:38:37 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:37+02:00 [debug] RX: 321212108f0e67054671d7009f643bff2618dfd73a02080352020a00920310073b08aec6d15756a66ee41ec4c537039a0310815aef109e4cf92a0483e53d2daf6788
Sep 15 12:38:37 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:37 INFO successfully executed command=set_charging_amps body=map[charging_amps:4]

Sep 15 12:38:50 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:50 INFO received command=set_charging_amps body=map[charging_amps:4]
Sep 15 12:38:50 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:50 INFO sending command=set_charging_amps body=map[charging_amps:4]
Sep 15 12:38:50 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:50+02:00 [debug] TX: 320208033a1212108f0e67054671d7009f643bff2618dfd79a0310528f18485052005179132ae9dbc4c0745207f9bd44adadc0a16a81010a430a4104ed711e034775d6dc32594edc8adb96eed0fba6e09807eec593bc449a9693d9ba476415de3edb6eb53a7cd735e98c961c3e6bdfc99afcbb54ee75bb5b9edd76782a3a0a10781854b66ccb43e863e90a29222647a4120c7380b9159570e7c8c422667718ca03252adb07002a10c90e8e367d30e768b4915bb7fb0fe497
Sep 15 12:38:51 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:51+02:00 [warn ] [528f18485052005179132ae9dbc4c074] Terminal transmission error: ATT request failed: input channel closed: io: read/write on closed pipe
Sep 15 12:38:51 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:51 DEBU disconnect vehicle (A)
Sep 15 12:38:51 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:51 DEBU close connection (A)
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:52 INFO connecting to Vehicle ...
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:52 DEBU trying connecting to vehicle attempt=1
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:38:52 DEBU connecting to vehicle (A)...
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:52+02:00 [debug] Reusing existing BLE device
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:52+02:00 [debug] Searching for BLE beacon S131821dd4fdd0f1aC...
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:52+02:00 [debug] Connecting to BLE beacon b0:d2:78:0b:27:9a...
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:52+02:00 [warn ] BLE connection attempt failed: ble: failed to enumerate device services: ATT request failed: input channel closed: io: read/write on closed pipe
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:52+02:00 [debug] Reusing existing BLE device
Sep 15 12:38:52 DietPi TeslaBleHttpProxy[11114]: 2024-09-15T12:38:52+02:00 [debug] Searching for BLE beacon S131821dd4fdd0f1aC...
Sep 15 12:39:00 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:39:00 INFO received command=set_charging_amps body=map[charging_amps:5]
Sep 15 12:39:30 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:39:30 INFO received command=set_charging_amps body=map[charging_amps:5]
Sep 15 12:39:55 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:39:55 INFO received command=set_charging_amps body=map[charging_amps:5]
Sep 15 12:47:50 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:47:50 INFO received command=set_charging_amps body=map[charging_amps:5]
Sep 15 12:48:20 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:48:20 INFO received command=charge_stop body=map[]
Sep 15 12:51:00 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:51:00 INFO received command=charge_stop body=map[]
Sep 15 12:51:20 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:51:20 INFO received command=set_charging_amps body=map[charging_amps:3]
Sep 15 12:51:32 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:51:32 INFO received command=set_charging_amps body=map[charging_amps:4]
Sep 15 12:52:00 DietPi TeslaBleHttpProxy[11114]: 2024/09/15 12:52:00 INFO received command=set_charging_amps body=map[charging_amps:5]

authors: FraBoCH dglaude gauner1986 haroldboom svwhisper wimaha

repo: wimaha/TeslaBleHttpProxy


text:
Waiting for user prompt in unattended mode

Describe the bug
Hi, I'm using the win-acme tool to install the generated certificate by using the script plugin with a custom installation tool. If there is already a renewal defined and the installation script returns an error, a user prompt asking to save the new settings is shown. Since I'm starting the client programmatically in a new Process, it always runs into a timeout while waiting for the mentioned user input.
To Reproduce

Run the tool to ensure an existing renewal configuration
The custom installation script returns an error
Start win-acme programmatically via command "wacs.exe --verbose --closeonfinish --accepttos --emailaddress MyEmail --source manual --host myHost --notaskscheduler --installation script --script myInstallationTool.exe --scriptparameters InstallArgs --validationmode dns-01 --validation script --dnsscript myValidationTool.exe --dnscreatescriptarguments CreateArgs --dnsdeletescriptarguments DeleteArgs"

Expected behavior
The started process returns an error without waiting for user input.
Log
Running the above mentioned command manually via commandline, returns the following output
 [VERB] Process output without data received
 [VERB]Process error without data received
 [EROR] Script finished with exit code 3
 [VERB] Waiting for process to finish...

 Save these new settings anyway? (y/n*) - no

 [EROR] Create certificate failed: Installation plugin Script encountered an error
 [VERB] Exiting with status code -1

Platform:

OS: Windows Server 2019, English]
Version:  2.1.20, 64-bit

Nice catch and thanks for the PR!

This fix is included in the new release: https://github.com/win-acme/win-acme/releases/tag/v2.1.21.1218

source: gharchive/issue

authors: WouterTinus sfclemens

repo: win-acme/win-acme

license_type: permissive

license_source: github-api


text:
Utility classes not being properly generated when extending theme colors

I have the following test windi.config.ts:
theme: {
		extend: {
			colors: {
				test: {
					100: "#096",
				},
			},
		},
	},

I'm finding that some classes are not generated. For example, outline-red-100 works fine, but outline-test-100 (my custom class) does not.
The VSCode's extension still recognizes these classes though:

Am I to generate these variants myself? Am I configuring something wrong?
As far as I've been able to tell based on docs, this is the correct way to do it.

Apologies I should mention this is in a fresh Vite + vue3 + ts project, using the vite-windicss plugin.

Bump. Still an issue. Haven't used Windi in ages, decided to try it again (forgot about this issue), then ran into the issue again.
Adding the class to the safelist in windi.config.ts fixes it, but that is not a great solution

repo: windicss/windicss

license: MIT


text:
web: cancel auto-scroll on mousewheel up

Hello @yuindustries,
Please review the following commits I made in branch nicks/ch2263/scroll:
a6ded38e32463d96a086ec2571b938337ac14cf9 (2019-04-15 12:53:54 -0400)
web: cancel auto-scroll on mousewheel up

(also changed this to use a RAF so that it doesn't consume CPU when the tab isn't focused)

source: gharchive/pull-request

repo: windmilleng/tilt


text:
use post buf

这样弄行不行

http的body没有必要cache吧？我看其他的http处理方式，也就是读出来就完了的，譬如cherrypy.reqeust.body.read()，读出来就没有了的。

那比如，我要在要把http-api中/api接口改成POST方法，我要在SrsGoApiApi::serve_http中根据POST的内容做不同的处理，在SrsGoApiApi::serve_http中我要怎么拿到post body

应该使用body_reader，获取一个可以不断read的接口。

如果你的消息需要再次使用，应该自己做cache的。

repo: winlinvip/simple-rtmp-server

license: mit

license_source: bigquery


text:
Allow table widget to have a minimum and maximum of items

This PR adds the config variables minItems and maxItems for the Table widget and datatable field type. The impetus of this is to allow a table to have no items by setting the minItems to 0 - I have found in my travels that if you have any sort of validation on the table widget, then you must have at least one record, but in my case, I wanted the datatable field to be optional.
I then thought it might be useful to have the opposite, and allow an upper limit for the number of records.
Some rules on the above:

minItems must be 0 or above. By default, it is 1 to match the current functionality. If minItems is 2, then 2 records must be in the datatable at all times (the datatable will have 2 empty records added on load).
maxItems must be either 1 or above, or null to indicate no limit.
minItems must be less than or equal to maxItems, to allow a datatable to have a fixed number of records.

To allow this change to happen, I've decided to change the datasource objects (client and server-side data handling) to use promises - this way, we have a common way of reading the responses, and it will gracefully handle the server-side taking a little longer to make changes to the data.

@bennothommo what's the status of this?

I'm gonna say I think it is complete... Definitely haven't tested it quite some time though.

@bennothommo do we have a docs PR for it?

I will test it first, and then I'll put up a docs PR, in case anything needs to change.

@bennothommo what's the status on this?

Same as before. Still needs docs and testing. Haven't had a need for it yet - I think I did this for my old job.

@der-On or @WebVPF, either of you bored and looking for something to do 😉?

@LukeTowers Bored to the bones :joy_cat: . Sorry I'm currently out on this.

authors: LukeTowers bennothommo der-On

repo: wintercms/winter


text:
Operator precedence is backwards

2 * 3 + 4 currently gives 14 and add : + is interpreted as (add :) + instead of add : (+).

Fixed by f51091109101f9c56da2f979f9240d61b1f81d6c

repo: wipplelang/wipple


text:
Replace deprecated Jackson date handling

Closes #1626

Closing this one due to inactivity. Welcome to reopen, but I wanted it off my list of open pull requests as it's unlikely to be merged soon.

repo: wiremock/wiremock


text:
Add yaml support for stub mapping configuration files

References
#2411

Submitter checklist

[ ] Recommended: Join WireMock Slack to get any help in #help-contributing or a project-specific channel like #wiremock-java
[ ] Recommended: If you participate in Hacktoberfest 2023, maake sure you're signed up there and in the WireMock form
[ ] The PR request is well described and justified, including the body and the references
[ ] The PR title represents the desired changelog entry
[ ] The repository's code style is followed (see the contributing guide)
[ ] Test coverage that demonstrates that the change works as expected
[ ] For new features, there's necessary documentation in this pull request or in a subsequent PR to wiremock.org

@karanjamutahi thanks! Could you please summarize how far it was reviewed during the hackfest? Maybe @Mahoney could take a look as a mntor there. Also, please register for hacktoberfest as mentioned in the PR template

A few questions came up mostly around the many features yaml to test for.
I need to box out some time to knock it off but there shouldn't be too much left to do.

@karanjamutahi Hi! It would be great to get it over the line. Let me know if I could help somehow

authors: karanjamutahi oleg-nenashev


text:
Request - Context menu rounded corners

I think it would look nice if the context menus had rounded corners to match Windows 11 menus.

because of the shadows, it looks weird, and you can’t remove them using qss, as far as I know

authors: dr-baba witalihirsch

repo: witalihirsch/qBitTorrent-fluent-theme


text:
Minor changes - based on suggestions made by F5 S6

User reports that the terminology surround the use of "File Routes" was ambiguous and can cause some degree of confusion as a result.
Having seen where they are coming from, I have added some phrases to help reduce the ambiguity surrounding the terms used.
Also took the opportunity to fix some of the tense and grammar on the page,
See comments: https://discord.com/channels/830184174198718474/853350631389265940/972847968724070491
Raised by; F5 S6

Duly noted, I swear though I cant remember all those spelling mistakes on the pr, 😬
Good to merge,

repo: withastro/docs


text:
View doesn't show after refreshing program in editor

Video: https://v.usetapes.com/4zoLVyb754

Thanks, I can confirm this is a bug. Thanks for the repro!

repo: witheve/Eve


text:
Invalid license test don't test completely

The fails_invalid_license and fails_incorrect_structure only test 1 invalid license string, as the first unwrap() will panic and the test will terminate. The remaining license strings are not tested.

Oof, thanks! Fixed with commit a3cf168.

authors: jethrogb withoutboats

repo: withoutboats/license-exprs


text:
Switch from Mocha to another lib

Hello @rotemmiz @LeoNatan,
I'm not a big fan of Mocha test framework because a lot of things seems to be magic.
When I look at the examples https://github.com/wix/detox/blob/master/detox/test/e2e/a-sanity.js I don't understand where the different methods come from - describe, beforeEach, it, expect -
It's really confusing to understand what comes from the test framework or from Detox, you have to search deep to discover where comes from the magic https://github.com/wix/detox/blob/master/detox/src/ios/expect.js#L357
Is there any plan to be test framework agnostic ?
It will be awesome Detox works with Ava https://github.com/avajs/ava and expose a verbose API.
import DetoxClient, {element, expect} from 'detox';
import test from 'ava';

const DETOX_CONFIG = {
...
};

let client;
test.before(async () => {
    client = DetoxClient.init(DETOX_CONFIG);
    await client.start();
});

test('my passing test', async () => {
    await element(by.id('username')).replaceText('admin');
    await element(by.id('password')).replaceText('admin');
    await element(by.label('loginButton')).tap();
    await expect(element(by.label('Welcome'))).toBeVisible();
});

test.afterEach.always(async () => {
    await client.waitForTestResult();
});

test.after.always(async () => {
    await client.cleanup();
});

Detox is runner agnostic and will work with other runners, such as Jest and Ava.

authors: LeoNatan padupuy

repo: wix/detox


text:
Make bad ..() calls a warning instead of an error

Bad DM code has too much of this. If we ever make a clone of C# pragmas we could consider having it default as an error.

😭

repo: wixoaGit/OpenDream


text:
Add list of words for new generated mnemonic in share xpubs panel

Because the share xpubs is not anymore a install process, no information is stored. If user want to generate a new mnemonic and share it xpubs he must be aware that he has to backup it.

close #1203

I rebase to change:
Beware to store for Beware to backup

Oh sorry, I've just thought, shouldn't the message say "I have backed up the mnemonic" instead of "registered"?

fixed your last comment thanks

repo: wizardsardine/liana


text:
Can't read a single line

My board is spitting out lines separated by "\r\n" at an arbitrary refresh rate x Hz.
I can't seem to read data line by line and flush() doesn't work.
Any idea how to use it?

So, looking at this again, the issue is that readline(data) will get up to the next delimiter, but then you are doing flush() which will drop any other data already in the queue:
https://github.com/wjwwood/serial/blob/master/include/serial/serial.h#L554-L556
The reason being that it flushes the output as well as the input and the input flush ends up doing this:
https://github.com/wjwwood/serial/blob/master/src/impl/unix.cc#L798
tcflush (fd_, TCIFLUSH);

Which does drop data that has been received but not read:
http://pubs.opengroup.org/onlinepubs/7908799/xsh/tcflush.html

If queue_selector is TCIFLUSH it flushes data received but not read.

I would use something like this:
string serialRead(serial::Serial *dev, FILE* f)
{
    string data;
    data = dev->read(dev->available());
    printf(f, "%s", data.c_str());
}

Please comment if you have anything else to add.

authors: spaghetti- wjwwood

repo: wjwwood/serial


text:
MacOS Support

Hi，谢谢你的插件，非常好的想法。
我使用的是MacOS with M1，把项目拉到本地编译会有以下报错：
error: failed to run custom build command for `librime-sys v0.1.0 (https://github.com/lotem/librime-sys#094db695)`

Caused by:
  process didn't exit successfully: `/Users/rain/code/rust/rime-ls/target/release/build/librime-sys-ce57fb0828704e4a/build-script-build` (exit status: 101)
  --- stdout
  cargo:rustc-link-lib=rime

  --- stderr
  wrapper.h:1:10: fatal error: 'rime_api.h' file not found
  wrapper.h:1:10: fatal error: 'rime_api.h' file not found, err: true
  thread 'main' panicked at 'Unable to generate bindings: ()', /Users/rain/.cargo/git/checkouts/librime-sys-fbe83737eec7c58b/094db69/build.rs:15:10
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

我去看了librime-sys这个项目，这个项目没有文档，而我也不是一个ruster，你知道是怎么回事嘛？

这个项目理论上是能在 MacOS 上面跑的，但因为涉及到依赖的 librime 的 C 库，我没有 MacOS 设备，不太清楚 Rime 的动态库在 MacOS 上一般是怎么安装和使用的，只能说一下我的理解，不一定对。
这个编译错误我猜是与我文档里的 Windows 的那个情况类似，没有找到 librime 的头文件。解决方法可以尝试下我文档里写的，安装 librime 后找到 librime 的头文件的位置，clone 一份 librime-sys 到本地，修改代码，然后修改 rime-ls 的 Cargo.toml 的依赖项，指向本地的 librime-sys （大概是这样：librime-sys = { version = "0.1.0", path = "../librime-sys" }），再尝试编译。
librime-sys 我感觉是 Rime 作者的一个实验性的尝试，维护不太积极。
我后续有可能 fork 一份 librime-sys 加上一些环境变量让编译更容易一些。
我也是 Rust 的新手，不太清楚 在 MacOS 上与 C 语言的库进行交互一般是什么样的过程，我预感在最后链接的过程在找动态库的时候可能还会出现一些问题。
不知道 rime-ls 现在的用户里有没有 MacOS 用户，请看到这的高手们帮忙解决一下。

经你的提醒，那我应该是没有安装librime依赖导致的，我去 https://github.com/rime/librime/releases/tag/1.8.5 下载了最新的macos相关的文件，解压之后，把lib文件夹和include文件夹，放到/usr/local目录下，现在编译通过了：

设置好lsp之后，发现 lsplog 里有以下报错：
[ERROR][2023-03-16 00:03:03] .../vim/lsp/rpc.lua:733	"rpc"	"/Users/rain/code/rust/rime-ls/target/release/rime_ls"	"stderr"	'E20230316 00:03:03.691471 671998 deployment_tasks.cc:65] Error reading file information: boost::filesystem::canonical: No such file or directory [generic:2]: "/usr/share/rime-data"\n'

所以这里的 rime 公共目录是什么意思呢？是用户可以随便创建的嘛？还是不同的系统是不一样的？

我是rime的新人，看来是我对此输入法了解的不够到位，我尝试创建了一个~/.local/share/rime-data，并将默认 MacOS Rime的目录~/Library/Rime 下的内容都copy了过去，现在应该是能正常工作了：

不知道我这种用法是否合理？

我理解就是全局配置和用户配置的区别。如果你的电脑装过鼠须管，那么它跟 rime-ls 是并列的关系，两个前端可以共用同一个后端也就是 librime。安装鼠须管时应该是前端和后端会一并安装，有一个公共的目录存放不同前端可以共享的配置，此外每个前端有一个自己的配置目录进行自定义配置。这个目录在 macOS 下的具体位置我就不太清楚了，但应该是不需要复制一份。

好的，那请问，在linux中，/usr/share/rime-data这个rime-ls使用的用户目录是自动产生的嘛？不需要进行额外的配置嘛？存放不同前端可以共享配置的“公共目录“在linux中是什么目录呢？

那 rime 公共目录的东西，rime-ls会去修改嘛？rime公共目录的这个概念，有没有文档可以查阅的？

rime-ls 本质还是调用 librime 提供的一些 API ，据我所知应该不会去修改里面的内容。
文档可以参考 rime 的 wiki 里面的 Shared Data 部分
其他部分的文档也可以看官方的 wiki。
相比其他输入法，Rime 带来很多可定制性，同时也让配置和使用变得极其复杂，对刚接触的人来说是不太友好的。
rime-ls 更多还是面向系统里已经有一个 Rime 输入法，想要复用已有配置的情况。需要一些折腾 Rime 的知识才能用的比较顺畅。如果是第一次接触 Rime 而且输入的需求比较简单，觉得折腾 Rime 这一套东西比较浪费时间，可以尝试下 ds-pinyin-lsp 这个项目，原理类似但会更加开箱即用一些。

ds-pinyin-lsp这个项目，我在尝试你的这个项目之前就尝试了，它背后没有类似rime的这种输入引擎，所以只能应付简单地输入，真正使用还是有些问题的，容易出错。
我稍微折腾了以下，MacOS下，rime的公共目录应该是 /Library/Input Methods/Squirrel.app/Contents/SharedSupport，这个目录下保存这公有的配置，不同的前端可以做自己的配置，通过custom.yaml做 patch。配置好之后，我感觉使用还是蛮方便的。我目前配置的是在markdown文件下启用此ls，通过<leader><space> toggle，然后&补全切换 schema。感觉已经蛮完备了。
非常棒的插件！也谢谢你耐心的指导，感觉这个插件会是一个未来。

谢谢！您过奖了

我还有两个问题想请教一下：

怎么翻页呀？我看README中支持翻页，但是我没看到相关的配置。
关于同步功能，我设置了 sync_dir 为 /Users/rain/Library/Rime/sync 也就是MacOS上的鼠须管输入法的用户目录，我触发了同步操作之后，看上去是吧rime-ls用户目录的配置同步到了上面的那个目录中，这样是OK的吗？怎么看词库有没有同步过来呢？

这个也是遵从输入方案的配置。默认应该是逗号句号和减号等号翻页，想要其他按键在配置的 "key_binder/bindings" 这一项也可以修改，但目前我只把默认的翻页按键作为触发键，其他按键可能不会触发自动的补全，要手动请求补全。
installation.html 里应该会有一个 installation_id，sync 目录下会创建一个同名的目录，里面会有一个 *.userdb.txt 的文件，内容就是用户的词频等信息。同步时应该是会把 sync 目录下其他 id 的 userdb.txt 也一起合起来。

了解了 感谢！

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
SingTingTech, @konalexiou, @iuliandumitru, @phedoreanu, @majora2007, @3bf1114a986ba87e, @Binly42, @kuczmama, @huopd, @alechilczenko, @tphz, @Cyperwu, @hanasono, @sampsonbryce, @keef1212, @laoxiong, @lordlabuckdas, @hexator, @DavidLvSinonet, @jeanthink, @lukewarm20, @cygmris, @Sweet0range, @TonnyRed, @SuperiorBo, @perception30, @coloz, @LordCasser, @jsydenstricker, @yj7778826, @lunady, @Yukaii, @dwaas, @wangyun122, @luoqigong, @Jimmysh, @Abis1, @aejontargaryen, @driver005, @quardz, @SunshineNikola, @JunLu1003, @yichaosun, @Lysander6, @xi086, @nozim, @searchworld, @ioncodes, @devsmart, @mgaerber

authors: jalixdesign rainzm wlh320


text:
doc: add installation guide for NixOS

Related to #32

Thanks.


text:
Travis CI pin hadolint versoin

Fix: Travis CI for wikibase-docker is blocked by hadolint Linting failure
https://phabricator.wikimedia.org/T201995

This should be squashed and merged when CI is green

authors: JonasKress addshore

repo: wmde/wikibase-docker


text:
不支持TSX的组件

报错内容：
[plugin:vite:import-analysis] Failed to parse source for import analysis because the content contains invalid JS syntax. If you are using JSX, make sure to name the file with the .jsx or .tsx extension.
组件的内容
仅仅是一个简单的jsx组件
/packages/test-demo/src/test-demo.vue

报错内容：
[plugin:vite:import-analysis] Failed to parse source for import analysis because the content contains invalid JS syntax. If you are using JSX, make sure to name the file with the .jsx or .tsx extension.
组件的内容
仅仅是一个简单的jsx组件 /packages/test-demo/src/test-demo.vue

知道为什么了，加了一个vite.config.js

vite.config.js是在哪里加的，加的什么内容？兄弟

vite.config.js是在哪里加的，加的什么内容？兄弟

docs/vite.config.ts 中加入@vitejs/plugin-vue-jsx的支持

authors: JACK-ZHANG-coming zhaoFangyi

repo: wocwin/t-ui-plus


text:
How can I configure the serializer for a collection property with backing field?

When I have a class which contains a collection property with a backing field, how can I serialize that?
For example: when I have this class...
public class BackingFieldExample
{
    private readonly IList<string> _values = new List<string>();

    public IReadOnlyCollection<string> Values => this._values.ToList().AsReadOnly();

    public void AddValue(string value) => this._values.Add(value);
}

... and this test with a serializer ...
[Fact]
public void SerializeBackingField()
{
    var e = new BackingFieldExample();

    e.AddValue("first value");
    e.AddValue("second value");

    var serializer = new ConfigurationContainer()
        .ConfigureType<BackingFieldExample>()
        .Create();

    serializer.Cycle(e).Should().BeEquivalentTo(e);
}

... then the Values collection of the deserialized object is empty.

While we haven't really made it a focus to carry over the classic functionality of the XmlSerializer, this is one scenario where we did.  You can make use of the XmlElementAttribute as demonstrated here:
https://github.com/wojtpl2/ExtendedXmlSerializer/blob/2a820ece4eccc4810240229315141d7607291106/test/ExtendedXmlSerializer.Tests/ReportedIssues/Issue255Tests.cs#L15-L40

As it appears that this question was answered, I am going to close it for now.  Please feel free to add another comment and/or re-open if you have any additional comments/question around this issue.

authors: Mike-EEE johanvergeer


text:
Wokwi Docs Chinese (Including, but not limited to board-ssd1306)

board-ssd1306 Reference(Chinese)
Using in Arduino部分連結有問題，重導到 wokwi.com

thanks for reporting, fixed.

fixed?
後來發現，在專案里改語言並不會改變網址
英文版(board-ssd1306 Reference(English))連結是沒錯的，所以把中文版連結改成跟英文版一樣，也許就可以修復問題。

Yes, I changed the Chinese link to match the English version

很奇怪，在wokwi-dht22 Reference(Chinese)，的DHTlib DHT22 test卻可以順利跳轉。

嘗試了一下，但按board-ssd1306：编辑此页面，卻是跳到英文

repo: wokwi/wokwi-docs


text:
[3, 4단계 방탈출 예약 대기] 낙낙(이낙헌) 미션 제출합니다.

안녕하세요 러너덕!!
고민되는 부분이 많다보니 시간이 좀 지체되었습니다!
사용자 id/pw 는 다음과 같습니다.
회원 id/pw
<관리자>
- ID : admin@abc.com
- PW : 1234

<사용자>
- ID : bri@abc.com
- PW : 1234

이번 미션에서는 선택 기능 사항이 있었는데,
예약 취소 시 예약 대기가 존재한다면 자동으로 승격하도록 구현하였습니다.

JPA는 객체지향과 DB 사이의 패러다임 불일치를 해소해 준다고 배웠지만,
실제 미션을 하면서는 이를 많이 느끼지 못했던 것 같아요.
엔티티는 그 자체로 테이블에 매핑되기 때문에 계속 데이터 중심으로 생각하게 되고,
도메인이 아닌 서비스가 대부분의 비즈니스 로직을 수행한다는 느낌이 들었습니다.
레벨 1에서 배운 객체지향이 레벨 2와는 동떨어져 있는 것 같아 더 헤맸던 것 같습니다..!

사용자에게 더 편의성을 주는 추가적인 기능도 넣고 싶고 리팩토링도 더 하고 싶지만,
미션 제출이 너무 늦어질 것 같아 먼저 리뷰 요청 드립니다!!
이번 리뷰도 잘 부탁드립니다!!
감사합니다!

안녕하세요 러너덕!!
다음 미션이 시작하게 되면서 리뷰 반영이 늦어졌습니다..!

안녕하세요 러너덕!!
리뷰 반영 후 다시 pr 요청 드립니다!

이전 미션 리뷰에서 궁금한 점이 하나 있는데요!
@Transactional에 대한 부분입니다!

당시에 리포지토리 테스트를 진행하다가 delete 메소드를 호출했음에도 쿼리가 나가지 않는 현상을 겪었는데요!
이렇게 테스트 진행 시 실제 쿼리가 나가지 않아도 괜찮은 것인지 궁금합니다!
(현재는 deleteById와 같이 JPA에서 기본적으로 제공해주는 메소드는 테스트할 필요성을 느끼지 못해 전부 삭제되어 있는 상태이긴 합니다!)

repo: woowacourse/spring-roomescape-waiting


text:
Conditional.php generates wrong field name

I wanted to add conditional logic, but failed to do so.
This is my set up:
//
// News / Blog items
//
$fields = [
    acf_image([
        'name' => 'banner',
        'label' => 'Banner',
        'wrapper' => ['width' => '100%'],
    ]),
    acf_radio([
        'name' => 'thumbnail_options',
        'label' => 'Image or video on thumbnail',
        'wrapper' => ['width' => '100%'],
        'choices' => ['image' => 'Image',  'youtube' => 'Youtube'],
        'default_value' => '',
        'layout' => 'horizontal',
        'return_format' => 'value',
    ]),
    acf_image([
        'name' => 'thumbnail_image',
        'label' => 'Thumbnail image',
        'wrapper' => ['width' => '50%'],
        'conditional_logic' => array(
            array(
                array(
                    'name' => 'thumbnail_options',
                    'operator' => '==',
                    'value' => 'image',
                ),
            ),
        ),
    ]),
    acf_url([
        'name' => 'thumbnail_video',
        'label' => 'Thumbnail video',
        'wrapper' => ['width' => '50%'],
        'conditional_logic' => array(
            array(
                array(
                    'name' => 'thumbnail_options',
                    'operator' => '==',
                    'value' => 'youtube',
                ),
            ),
        ),
    ]),
];

$location = [
    [
        acf_location('post_type', 'post')
    ],
];

acf_field_group([
    'title' => 'News settings',
    'key' => 'group_news',
    'fields' => $fields,
    'style' => 'default',
    'location' => $location,
    'position' => 'normal',
    'hide_on_screen' => ['featured_image', 'categories'],
]);

It only works if I disable the logic in Conditional.php and change the config like this:
array(
    'field' => 'field_news_thumbnail_options',
    'operator' => '==',
    'value' => 'image',
),

Hmm, have you tried using the acf_conditional_logic function?

I did, but this helper only returns the array I have above:
acf_conditional_logic('thumbnail_options', 'image')
returns
[
    "name" => "thumbnail_options"
    "operator" => "=="
    "value" => "image"
]

I think the real issue lays in Conditional.php or Field.php

What version of this package and PHP are you using?

wordplate/acf: 3.1.0
advanced-custom-fields/advanced-custom-fields-pro: 5.5.14
php: 7.1.0

I created a pull request with a possible fix

Thanks, I'll look into this as soon as I've time to spare!

@MaximVanhove thanks for reporting! I've pushed a fix in f3eb02c65d7961b927a64d4442c83edb96f92e75.
Are you your code in production yet? If not, you could upgrade to the latest beta version 4.0.

No it's still in progress. I'll test the beta soon. Thanks for the great work.

No it's still in progress. I'll test the beta soon. Thanks for the great work.

Okay, great! Just know that the new version is hashing the keys. This means data will be lost but if this is only in a development environment it should be too much of an issue.

I can confirm that this is fixed in 4.0 and no data is lost, but you need to save everything again first.

Okay, great! Thanks for letting us know.

Please take note of this breaking change in version 4.0: 6b8dd35c21563085da11427b467918a4c5b7daa1

authors: MaximVanhove vinkla

repo: wordplate/acf


text:
Specify higher-level parameters in MeasurementSpec rather than SketchConfig resource key.

This allows the Kingdom to select an appropriate protocol and well-known protocol configuration for a given Measurement, abstracting the protocol-specific details from Measurement creation.

This replaces #9.


text:
coding-related research-creation notes

coding-related notes for the dissertation

Reasons why I am not storing threeJS objects in an automerge doc:

automerge cannot store objects which contain functions, see this issue

automerge throws a maximum stack error when objects are too large. I get this when trying to add an op mesh (which is a group of meshes i.e. panel, inlets, outlets, UI, etc.)

mention in patchup! book and dissertation
a usecase for mischmasch is designing gen code for daisy. how can we integrate it

repo: worldmaking/mischmasch


text:
CoreMathImgProc-master

hi~ I open the project "CoreMathImgProc",but i don't know how to make it as jar.

Run gradle build

authors: lmwym woshiwpa

repo: woshiwpa/SmartMath


text:
Import EED-files

Currently, it is only possible to import saved GHEtool files. It would however be useful to be able to import saved files from Earth Energy Designer into GHEtool. Since both programs, more or less, use the same input data, this convergence from EED to GHEtool should be possible.
Two functionalities will be implemented in this issue:

[ ] Load an EED file
[ ] Import an EED file as a new scenario (since every EED file is only one 'scenario' in GHEtool terms)

The framework for this will be implemented in ScenarioGUI: https://github.com/tblanke/ScenarioGUI/issues/89

Framework implemented in ScenarioGUI.

repo: wouterpeere/GHEtool


text:
Seems like sim doesn't consider T7 set bonus (at least 4 piece) for balance druid.

Describe the bug
When I use 4 pieces of t7 the bonus doesn't work. Four pieces give you +5% crit to Wrath and Starfire, but it doesn't seem to work, since the "Crit%" in "Detailed Results" doesn't change with 4 pieces. I was switching only gloves to compare the results of the sim. See the Sim links.
To Reproduce
Steps to reproduce the behavior:

Go to 'Gear'
Use the Sim 1 (4piece) settings via the link I provide.
Click "Simulate"
Click "Detailed results"
Note Crit% of Wrath and Starfire.
Go to 'Gear'
Use the Sim 2 (3piece) settings via the link I provide.
Click "Simulate"
Click "Detailed results"
Note Crit% of Wrath and Starfire.
Compare the results.
It's a bug.

Expected behavior
The Wrath and Starfire Crit% should be increased with 4 pieces of T7.
Sim Links and Screenshots
Sim 1 (4piece):
https://wowsims.github.io/wotlk/balance_druid/#eJztUkFIVFEU/efOODy/TTzDxcvV728KQXj/PT7Yar6uWg5EMFsJRajFR4JKED7iohECFyk4uAvChaBoC4vUqIYwqGTIoGkosBaDG0dX0mZ8/6sLd4K16/C4cM8591x479kOI06SenADBYQUAZPAIug1sAnUgb52BockAuRjB+aAS1bnbnoMmfzd/ocDw4xxdL6AzfnjVyQ+/iA3U35D1RWy03x/iewsnzb8B8On1gzJ+ESZxNR+ygifjPC5ZoSGEdr43lMSle/kwrIv8oPnJBo1uGkzZJnwg1USxfmUm9lbIXMM88RMj5XNOuOoJskLSyTmavHiX824/k7qzmpcZ5/FjuYyia3E8SdhH62RazNI5NOFlgfomiTrP05hhDFwEhRCOXaWQeCWZYW9BQzF/yBrt7HmCTCBq74nlZLaU77WnpZaeVpLX0tPaa+7W0lfyrjZhmDRT+Jf1kl8WyentEXX3lZIvq9QHS0NtJZgFY/fQgVVWO4OtSZdNBi0H/EdweXSTIyN3PUjZjN3ZTDB15x6SeHs6MiFfP+920P3B4bvOMp3bgr2z194PPgbKdHGu/PkyJ6usPes5uTyount4HiinjsESrSNng==

Sim 2 (3piece):
https://wowsims.github.io/wotlk/balance_druid/#eJztUkFIVFEU/efOODy/TTzDxcvV728KQXj/PT7Yar6uWg5EMFsJRajFR4JKED7iohECFyk4uAvChaBoC4vUqIYwqGTIoGkosBaDG0dX0mZ8/6sLd4K16/C4cM8591x479kOI06SenADBYQUAZPAIug1sAnUgb52BockAuRjB+aAS1bnbnoMmfzd/ocDw4xxdL6AzfnjVyQ+/iA3U35D1RWy03x/iewsnzb8B8On1gzJ+ESZxNR+ygifjPC5ZoSGEdr43lMSle/kwrIv8oPnJBo1uGkzZJnwg1USxfmUm9lbIXMM88RMj5XNOuOoJskLSyTmavHiX824/k7qzmpcZ5/FjuYyia3E8SdhH62RazNI5NOFlgfomiTrP05hhDFwEhRCOXaWQeCWZYW9BQzF/yBrt7HmCTCBq74nlZLaU77WnpZaeVpLX0tPaa+7W0lfyrjZhmDRT+Jf1kl8WyentEXX3lZIvq9QHS0NtJZgFY/fQgVVWO4OtSZdNBi0H/EdweXSTIyN3PUjZjN3ZTDB15x6SeHs6MiFfP+920P3B4bvOMp3bgr2z194PPgbKdHGu/PkyJ6usPes5uTyount4HiinjsESrSNng==

Desktop:

OS: Windows 10
Browser: chrome
Version 106.0.5249.121

Additional context
The overall gear stats doesn't rly change. Set with 4 pieces has less Spirit and a bit less of Crit, but the bonus to Wrath and Starfire is massive (+5% crit), so the problem seems to be just in a set bonus issue.

You've got the healing head part equipped buddy.

You've got the healing head part equipped buddy.

Gosh, you're totally right!
Sorry 😅

repo: wowsims/wotlk


text:
WIP: Gettext 5

Roadblock of https://github.com/php-gettext/Twig-Scanner
(back from https://github.com/wp-cli/i18n-command/pull/59)

Should the PR be based on wp-cli:dependabot/composer/gettext/gettext-tw-5.4?
Any particular point to consider before I further improve that PR?

I'll let @schlessera chime in, but I think the PHP 7.2+ requirement of gettext v5 might be a bit of a blocker for us here.

Yes, indeed, moving to the v5 branch of gettext is currently not an option, as WP-CLI is supporting PHP 5.4+ for now (with an imminent bump to PHP 5.6+ upcoming).
See https://make.wordpress.org/cli/2019/01/15/wp-cli-php-requirements-strategy/ about details on how the minimum requirement is decided.
Feel free to hit me up on Slack if you want to discuss options about how best to enable Twig support despite this limitation.

Ok.
Which version of PHP 7.x will be required in v3? 7.1, 7.2, ... ?
Is work on v3 going to be done inside v3 branches for all packages?
If yes, and >= PHP 7.2, then I'd like to anticipate that move (so that I can just require i18n-command:^3 in my composer.json)

@dependabot-preview /reopen please.

Still supporting PHP < 7.2 ?

authors: drzraf schlessera swissspidy


text:
Replace DOS line endings with LF

DOS line endings are not currently stripped from the wp-config files, which results in extra lines being added to the modified file.
Fixes https://github.com/wp-cli/config-command/issues/160

@xknown This is not something that can be solved with a simple str_replace(), I'm afraid.
What the code does with your changes seems worse than before.
Imagine the scenario where you have two regular blank lines in the standard notation for servers:
\n\r\n\r

The logic with this PR will first replace the middle part of that sequence, breaking the two individual blank lines. Then, as it completes, the final result will be this:
\n\n\n\n

So, for the more common configurations, it will end up turning two blank lines into four blank lines.
To solve this properly, we would need to switch away from str_replace() and use a regular expression that considers entire groups in one go and detects the patterns.

@xknown This is not something that can be solved with a simple str_replace(), I'm afraid.
What the code does with your changes seems worse than before.
Imagine the scenario where you have two regular blank lines in the standard notation for servers:
\n\r\n\r

The logic with this PR will first replace the middle part of that sequence, breaking the two individual blank lines. Then, as it completes, the final result will be this:
\n\n\n\n

That's not really the case though, because the str_replace will first replace\n\r (or \r\n) by a single \n. However, I agree that using a regular expression might probably be better to only replace those characters where it makes most sense.

@xknown Indeed, you're right, my bad. I tested this in 3v4l.org and it seems to reliably work with all constellations.

authors: schlessera xknown

repo: wp-cli/wp-config-transformer


text:
NextJS support

Currently, this is not supporting NextJS. Would be great to have it working with NextJS.

Development of SSR support in progress.

SOLVED: SSR support added on version 1.3.0

repo: wpdas/near-social-bridge


text:
Merging latest README and images into main branch

Merging latest README and images into main branch

Closing pull request as unable to merge automatically


text:
[TM-1452] Site polygon filtering

https://gfw.atlassian.net/browse/TM-1452
This implements all of the various types of filters for the site polygons research GET endpoint.

Something is up with my DB definitions that wasn't failing locally. I'll investigate in the morning.

repo: wri/terramatch-microservices


text:
removed markdeep due to not being awesome

Remove Markdeep from the "Converters and Filters" section.
I've reviewed Markdeep and don't find it awesome. There is no active user and developer community.

[ ] Table of contents has been updated (if needed).
[ ] Contents have been sorted alphabetically.

OK then in that case, you can remove the markdeep-thesis example as well.

But you surely saw this: https://doersino.github.io/markdeep-thesis/demo.md.html did you not. This was why I added it in the first place.

But you surely saw this: https://doersino.github.io/markdeep-thesis/demo.md.html did you not. This was why I added it in the first place.

It is indeed an impressive tech demo. I'm just missing an everyday use case.

I agree it seems to be forgotten. We can remove it for now. Relevant thread for similar projects:
https://news.ycombinator.com/item?id=19488561

authors: ashwinvis maehr


text:
Update index.md

aaaaa

aaaaaa

aaaaaa

repo: writingteacher/github-pages-with-jekyll


text:
support for rolling-updates of components

Purpose

Add support for rolling updates for the container images in cell components.

Codecov Report

Merging #69 into master will increase coverage by 0.07%.
The diff coverage is 95%.

@@            Coverage Diff             @@
##           master      #69      +/-   ##
==========================================
+ Coverage   91.71%   91.79%   +0.07%
==========================================
  Files          30       30
  Lines        1618     1657      +39
==========================================
+ Hits         1484     1521      +37
- Misses        116      117       +1
- Partials       18       19       +1

Impacted Files
Coverage Δ

pkg/controller/service/resources/deployment.go
96.96% <95%> (-3.04%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1d8504e...31081eb. Read the comment docs.

authors: codecov-io isurulucky


text:
New GRPC service to serve Gateway STS traffic

Purpose

New GRPC service to serve Gateway STS traffic

the changed has overridden from a force push. Will open a different PR


text:
Secure boot should be turned off in Local Cellery Setup - Ubuntu 18.04

Description:
When installing cellery runtime on local setup on Ubuntu 18.04. Secure boot should turned off which is not included in doc.
Suggested Labels:
Doc improvements
Suggested Assignees:
@MadhukaHarith92
Affected Product Version:
Cellery 0.2.0
Steps to reproduce:
Related Issues:

This should be an issue with my machine. So closing this issue.


text:
Add index type via parameter on annotation

Purpose

Add index type via parameter on annotations

Goals

If there are many types on the same index, this feature can put a custom type saving streams

@jaimesf Thanks for the PR. Really appreciate it. BTW, sorry for the delay in merging this.

authors: jaimesf mohanvive


text:
Fix authenticating through all userstores when the domain is provided

Purpose

Fix iterating through all the userstores when the domain is provided with the username

Issue - https://github.com/wso2/product-is/issues/20473

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/9690297702

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/9690297702
Status: failure

The testSelfRegisterWithInvalidPassword  test failure is intermittent.

authors: ThaminduR jenkins-is-staging


text:
Broken links in Micro Integrator documentation

Description:
On https://wso2.com/integration/micro-integrator/ the below two links are not working.

PREVIOUS RELEASES
ENTERPRISE INTEGRATOR 6.X.X SERIES >
ENTERPRISE INTEGRATOR 7.X.X SERIES >

Suggested Labels:
Micro Integrator

Now EI download packs are removed from the site.

authors: chanikag iloshinik


text:
Update documentation for Streaming Integrator - Business Rules Manager

Purpose

Fixing mistakes in the documentation
Updating screenshots

Goals

Improving documentation

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


text:
Bump Dependencies #325

Bumps dependencies for ${REPOSITORY}.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jenkins-is-staging seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant jenkins-is-staging


text:
Error encountered while processing the large responses in GraphQL

Describe your problem(s)
The below error occurs when the frame length of the response is higher than 65536
TID: [] [] [2022-03-08 11:27:56,507] ERROR
Unknown macro: {org.wso2.carbon.websocket.transport.WebSocketClientHandler} - Error encountered while processing the response io.netty.handler.codec.http.websocketx.CorruptedWebSocketFrameException: Max frame length of 65536 has been exceeded.
at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.protocolViolation(WebSocket08FrameDecoder.java:424)
at io.netty.handler.codec.http.websocketx.WebSocket08FrameDecoder.decode(WebSocket08FrameDecoder.java:286)
at io.netty.handler.codec.ByteToMessageDecoder.decodeRemovalReentryProtection(ByteToMessageDecoder.java:510)
at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:449)

Suggested Labels:
APIM 3.2, GraphQL

Fix is applied.

authors: Menuka-Senevirathne nandika


text:
[DOC] Skip returning the challenge question recovery option, if the user doesn't have challenge questions answer

Need to document the improvement done at [1]
[1] https://github.com/wso2/product-is/issues/8905

Documented in the migration: what has changed document with this PR [2]
[2] https://github.com/wso2/docs-is/pull/2160


text:
[consoleApp] Adding a New IDP via provisioning tab for applications - Crashing

Describe the issue:
When creating an IDP for an application, when finish is clicked without providing any details, the window goes blank.
How to reproduce:
1.Access https://localhost:9443/console
2.Login as super admin
3.Navigate to Develop > Applications > New Application > Vendor Integrations > BOX and add a sample application
4.In the edit view go for the provisioning tab
5. Click + New IDP
6. Click Finish without providing any details
Expected behavior:
The finish button should not be available without the user providing the mandatory details.
Environment information

Product Version: 5.11.0 Beta3
OS: Ubuntu 18.04 LTS
Database: Maria DB 10.4
Userstore: JDBC

Related issue : #10089
This issue was resolved by making the "Provisioning Connector" mandatory.

Making the "Identity Provider" mandatory would fix this issue

This issue has been fixed but the application-create request is sent twice. The first one fails since it is sent without a callback URL.

authors: JeethJJ thivi


text:
Link resident provider section to Resident IDP documentation

In [1] the 6th point is using a resident IDP. Please link this to the resident IDP description as a user who is entering the doc space need to know why the resident IDP is used.
[1] https://docs.wso2.com/display/IS540/Forced+Password+Reset#ForcedPasswordReset-PasswordResetviaRecoveryEmail

Thank you for your contribution!
We are closing this issue since it has not been prioritized for a long time. Chances are that it has already been solved in more recent versions. If not, we will be re-evaluating this when it becomes a priority.

authors: erandidesilva isharak


text:
There is no option to switch to suborgs and No delete option  which are not in 1st pagination page

Describe the issue:
Currently, there is no option or mechanism provided to switch & Delete  to suborganizations that are not present on the first pagination page.
How to reproduce:
Navigate to the organization page with a large number of suborganizations ( more than 10).
Observe that only suborganizations on the first pagination page are accessible.
Expected behavior:
Users should be able to navigate to suborganizations beyond the first pagination page.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: BetaSnapshot 7.0
OS: Mac
Database: H2
Userstore:JDBC

https://github.com/wso2/product-is/assets/39120228/3e8d50db-99df-401c-a1d5-196dd7ff1d5b

This issue is addressed by following PR

https://github.com/wso2/identity-apps/pull/4724

authors: NilukaSripalim PasinduYeshan


text:
[Doc] Missing Outbound User Provisioning Guide for IS 7.0

Is your suggestion related to a missing or misleading document? Please describe.
The documentation lacks an exact guide or detailed documentation for Outbound User Provisioning specific to IS  version 7.0.

duplicated : https://github.com/wso2/product-is/issues/18925