sap.m.MultiCombox gap between icon and border

OpenUI5 version: 1.76.0
Browser/version (+device/version): Chrome 80.0.3987.149 (Official Build) (64-bit)
URL (minimal example if possible): https://openui5.hana.ondemand.com/#/entity/sap.m.MultiComboBox/sample/sap.m.sample.MultiComboBox
Steps to reproduce the problem:

Open SuggestPopover via Icon
Select first entry '10" Portable DVD player'
See gap between icon and border

What is the expected result?
No gap between Icon and Border
What happens instead?
There is a small gap between the Icon and the border
Any other information? (attach screenshot if possible)
Tokenizer inside of the MultiComboBox has a non-round pixel width which seems to be the issue here.
It's not reproducible for all items, because it depends on the length of the text.

Please down port to 1.71.x and also for the sapui5 version.

Hi @4lexBaum,
As I still do not see a deviation from the spec, may I ask you to specify in further detail what exactly looks like a gap. Ideally, can you highlight it in the image?
Thanks,
Diana

Hi @kineticjs,
I highlight the little gap, see:

Best Alex

Hello @4lexBaum ,
Thank you for sharing this finding. I've created an internal incident<PHONE_NUMBER>. The status of the issue will be updated here in GitHub.
Regards,
Diana

Hi @kineticjs ,
thanks for fixing this issue!
Is this fix also available in 1.71.x and also for the sapui5 version?
Best Alex


Add 12 new drink recipes

Several recipes being added and one new measurement type

I think we added these commit by commit w/ cherry-picks yesterday, right @smolakoala? If so, I think we should close this.


layer: Add max_events_per_span API

Motivation
As described in https://github.com/MaterializeInc/materialize/issues/17497, there is a slow OOM when enabling open-telemetry tracing at the debug level. Through some investigation it turns out this OOM is caused by an underlying library, h2, having a long running span. Specifically, h2 keeps a debug span open for the entire lifetime of a Connection. This is problematic because the OpenTelemetryLayer continuously appends events onto this span, and we don't flush them until the span closes, which is never does, so we end up using more and more memory until we OOM.
Solution
This PR adds a new configurable field to OpenTelemetryLayer that allows you to configure the maximum number of otel::Events that will be recorded for a single span. When we go over this max we drop the oldest events, and report that events were dropped.

Looks pretty good, I just have a few comments! After those comments, I'd definitely attempt to pr this against upstream!

Thanks! Def will try to upstream this after merging!


Unable to figure out how and where cookies.json needs to be stored

The problem
python src/edge.py --debug
2023-03-19 15:05:07,094 - apscheduler.scheduler - INFO - Scheduler started
2023-03-19 15:05:07,095 - telegram.ext._application - INFO - Application started
and nothing there after. I am presuming I did not set up cookies.json correctly as there was no instruction about it.
Version of Edge-GPT-Telegram-Bot
edge-gpt-telegram-bot v0.1.0
Operating system running Edge-GPT-Telegram-Bot
Linux
Running on your machine? Running on docker?
VM in GCP
Additional information & file uploads
No response

You more likely didn't set up your webhook correctly. Can you change "webhook": false in config.json?

Relevant part of my config.json:
"webhook": false,
"log_level": "INFO",
"ip": "vps_ip",
"listen": "<IP_ADDRESS>",
"port": "vps_port",
"cert": "cert_path",
"assemblyai_token": "assemblyai_token"

I set up none of these.

Yeah, then change webhook to false. I'll change the template value to false so people can just run the bot without prior configuration.

webhook is actually set to false as you can see.
starting in debug mode also shows only this-
python src/edge.py --debug
2023-03-19 15:11:54,919 - apscheduler.scheduler - INFO - Scheduler started
2023-03-19 15:11:54,920 - telegram.ext._application - INFO - Application started
and no other thing

set log_level to DEBUG, without more information, I can't figure out the problem

Thanks for the tip. With the debug log I can see that my TG update is coming, so the problem is in probably the EdgeGPT portion. Here is a dump of the logs- https://pastebin.com/LkgGyvun

I should say that I have created cookies.json by copy pasting the exact output of cookie editor chrome extension in cookies.json in config folder as per instruction in EdgeGPT docs.

Mmm, have you unlocked the bot? I don't see any update in the logs. And yes, the whitelist isn't working currently, sorry. I removed it in a previous commit and haven't implemented it yet again

Ohh... that must be it. lol. I presumed the whitelist works.

Yes... my bad. I'll cherry pick the commit from openai branch

Yep started working! Thanks so much!!

Don't forget to regenerate to bot token!

I've released a new version with whitelist working, sorry! https://github.com/scmanjarrez/EdgeGPT-Telegram-Bot/releases/tag/0.1.2