Error «Please setup Connected Services»

Describe the bug
The Toyota integration has stopped working, seems to have happened at the same time as the car was moved (by Toyota) from the «MyT Toyota» app to the «MyToyota» app.
I get this error message in the logs:
2023-10-29 12:27:21.691 ERROR (MainThread) [mytoyota] Please setup Connected Services if you want live data from the car. (JTM**************)

What country are you in? I don't see any my toyota app, only myT on apple app store--Lucian Lazar – Senior Solution ArchitectecoIT Solutions Srl@@.***  +40770558273www https://ecoit.solutionsOn Oct 29, 2023, at 13:31, Tom @.> wrote:
Describe the bug
The Toyota integration has stopped working, seems to have happened at the same time as the car was moved (by Toyota) from the «MyT Toyota» app to the «MyToyota» app.
I get this error message in the logs:
2023-10-29 12:27:21.691 ERROR (MainThread) [mytoyota] Please setup Connected Services if you want live data from the car. (JTM***********)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Norway. I noticed that all the Toyota sensors in HA were unavailable. I opened the MyT app to see what I could see and was met by a notification that car was moved to the MyToyota app and that I should download that. After doing that and logging in, I can see the car and its data in the new MyToyota app, but the HA integration is unsuccessful - with the error message in the OP.

I can’t anymore set up the car in the old MyT app. If I try, it responds with a message saying I have to use the new MyToyota app. I’m wondering if Toyota have set up a new API and are moving cars to the new app (perhaps staged somehow - for example by country).

I have the same behavior here in Germany after my vehicle was migrated to the new MyToyota app last week:
https://play.google.com/store/apps/details?id=com.toyota.oneapp.eu
Since then no connection with the Home Assistant custom component is possible.
Since the custom component was only a reverse engeneering of the old Toyota app by @DurgNomis-drol possible, I don't know if he will find the time again to do that for them new app again. :-(
Maybe we should all write to Toyota via different channels and ask them to finally provide us with an official API!

I just wrote an email to Toyota. Let's see if something comes back:

Official API for Toyota Connected Services?

Simon  Mi., 1. Nov. 2023 um 12:40
An<EMAIL_ADDRESS>Dear Toyota App Team,
the new MyToyota App is in itself a nice revision of the previous MyT App.
However, Toyota seems to have also changed the API here in the background.
This poses problems for developers who offer solutions based on reverse engineering of the old MyT app. They now have to start
all over again.
For example, the Home Assistant Toyota integration, which is used by several thousand people, is no longer functional after a
migration to the new MyToyota API: https://github.com/DurgNomis-drol/ha_toyota/issues/164
As mentioned, the MyToyota app is quite nice, but for those who want to go a step further and integrate their Toyota really "smart"
into the rest of their smart home ecosystem, it is unfortunately insufficient.
So would it please be possible to finally provide us with an official API for Toyota Connected Services?
You would really endear yourselves to some people and really show a will to innovate.
Best regards and many thanks in advance!
Simon

Hi @DurgNomis-drol, sorry to hear that, but totally understandable!
Unfortunately, I currently also have little time and will probably not be able to take care of an adaptation to the new API.
By the way, the migration of the vehicles to the new App/API takes place without any active interactions @DurgNomis-drol.
One morning when I opened the MyT app, it simply told me to use the new app. So it's quite possible that your Aygo will be migrated soon as well ;-)

@CM000n Well then I will try not to open the App 😉 or I will have a winter project on my hand again 😆 🚀

I checked my app, and my corolla has not been moved yet, but from what i can read here, this might happen within the next days.
When this happens, maybe i can provide informations, or also can help to code a library for the new api.
Let us find out, what will happen.

I moved to the new MyTotota app after buying a Corolla this week. I added the HA integration and logged in with my Toyota credentials. I only get one entity: sensor.corolla_numberplate. The rest is not loaded or available.

@nielsvdc This is exactly what I see as well, with a bZ4x

I haven't look in the .apk file like you have, @CM000n, but I played around with the old API a bit and noticed that the "legacy" endpoint https://myt-agg.toyota-europe.com/cma/api/vehicles/${"vin"}/remoteControl/status still includes charge status and remaining distance (for my bZ4x):
{
    "VehicleInfo": {
        "AcquisitionDatetime": "2023-11-07T12:38:17Z",
        "RemoteHvacInfo": {
            "Temperaturelevel": 33,
            "RemoteHvacMode": 0,
            "RemoteHvacProhibitionSignal": 1,
            "SettingTemperature": 22.0,
            "BlowerStatus": 0,
            "FrontDefoggerStatus": 0,
            "RearDefoggerStatus": 0,
            "InsideTemperature": 26
        },
        "ChargeInfo": {
            "EvDistanceInKm": 446.1,
            "GasolineTravelableDistanceUnit": 1,
            "GasolineTravelableDistance": 0,
            "PlugStatus": 45,
            "PlugInHistory": 33,
            "RemainingChargeTime": 65535,
            "EvTravelableDistance": 446.1,
            "EvTravelableDistanceSubtractionRate": 18,
            "ChargeRemainingAmount": 100,
            "SettingChangeAcceptanceStatus": 0,
            "ChargeType": 15,
            "ChargeWeek": 0,
            "ChargeStartTime": "42:35",
            "ChargeEndTime": "42:35",
            "ConnectorStatus": 5,
            "BatteryPowerSupplyPossibleTime": 16383,
            "ChargingStatus": "chargeComplete",
            "EvDistanceWithAirCoInKm": 365.8
        }
    },
    "ReturnCode": "000000"
}

Don't know how long that will last, though.

I haven't look in the .apk file like you have, @CM000n, but I played around with the old API a bit and noticed that the "legacy" endpoint https://myt-agg.toyota-europe.com/cma/api/vehicles/${"vin"}/remoteControl/status still includes charge status and remaining distance (for my bZ4x):

Good finding @uphillbattle !
By the way: I was just about to visit our friends at Toyota Home Assistant Integration for North America to see which endpoints are used there.
I was shocked to see that the Gut repo was shut down with a DMCA notification: https://github.com/widewing/toyota-na
Let's hope Toyota Europe doesn't take similar steps.

Well now I got the email, but I haven't opened the app, and it still seems to work, so I believe it only moves you to the new app if you open the old one 🎉

I can confirm up to now.
Mail with the notification for shutdown of the old app has arrived.
Maybe i have now a weekend-project.

Hi @DurgNomis-drol and @m-dietrich,
I took another look today and I think we are dealing with two problems here:
1. The “Please setup Connected Services …” error
This error occurs because the structure of the data returned by the API has changed. This causes a check to see whether Connected Services are activated in the mytoyota Python lib to fail. I've just created a pull request for this with a possible fix: https://github.com/DurgNomis-drol/mytoyota/pull/240
However, this still needs to be merged and the ha_toyota custom component needs to be adjustet so that it uses the latest version of the mytoyota lib. This may require major adjustments as ha_toyota is currently using an outdated version of the mytoyota lib. What is your assessment of drugnomis here @DurgNomis-drol?
2. Changed API Endpoint for vehicle's trips?
At first I thought we were dealing with a changed API endpoint here.
However, after I used the above fix locally, the following minimal example including the information about the vehicle's journeys also worked:
import asyncio
from pprint import pprint
from mytoyota.client import MyT

username = "USERNAME"
password = "PASSWORD"
brand = "toyota"  # or lexus

# Get supported regions, can be passed to the optional 'region' argument of MyT
# At this moment, only the 'europe' region is supported
pprint(MyT.get_supported_regions())

client = MyT(username=username, password=password, brand=brand)

async def get_information():
    pprint("Logging in...")
    await client.login()

    pprint("Retrieving cars...")
    # Returns cars registered to your account + information about each car.
    cars = await client.get_vehicles()
    pprint(cars)

    for car in cars:

        vehicle = await client.get_vehicle_status(car)
        # Information on vehicle status object continues to work:
        pprint("Vehicle Info..")
        pprint(vehicle._vehicle_info)
        pprint("Connected Services..")
        pprint(vehicle._connected_services)
        pprint("Odometer..")
        pprint(vehicle.odometer)
        pprint("Status..")
        pprint(vehicle._status)
        pprint("Status Legacy..")
        pprint(vehicle._status_legacy)

        pprint(vehicle.dashboard.odometer)

        # Statistics still don't seem to work due to a changed API endpoint?

        data = await asyncio.gather(
            *[
                client.get_driving_statistics(vehicle.vin, interval="day"),
                client.get_driving_statistics(vehicle.vin, interval="isoweek"),
                client.get_driving_statistics(vehicle.vin),
                client.get_driving_statistics(vehicle.vin, interval="year"),
            ]
        )
        pprint(data)

        # Daily stats
        daily_stats = await client.get_driving_statistics(vehicle.vin, interval="day")
        pprint(daily_stats)
        # ISO 8601 week stats
        iso_weekly_stats = await client.get_driving_statistics(vehicle.vin, interval="isoweek")
        pprint(iso_weekly_stats)
        # Monthly stats is returned by default
        monthly_stats = await client.get_driving_statistics(vehicle.vin)
        pprint(monthly_stats)
        # Get year to date stats.
        yearly_stats = await client.get_driving_statistics(vehicle.vin, interval="year")
        pprint(yearly_stats)

loop = asyncio.get_event_loop()
loop.run_until_complete(get_information())
loop.close()

So it seems that we don't have to look for a new API endpoint for the trip statistics (for now).

The attached will get you connected to the new toyota services. You need to enter your username, password and GUID at the top of the file. The problem is the GUID this is your customer ID but I have yet to work out how the toyota app knows what this is! You can find it by logging into My Toyota website and in the developer tools find a request for https://cpb2cs.toyota-europe.com/vehicle/user/<This Will Be Your GUID>/.... It may contain much more than is required but allows to me check the two accounts I have access too.
`import requests
import json
import urllib.parse
import pprint
def pretty_print_POST(req):
print('{}\n{}\r\n{}\r\n\r\n{}'.format(
'-----------START-----------',
req.method + ' ' + req.url,
'\r\n'.join('{}: {}'.format(k, v) for k, v in req.headers.items()),
req.body,
))
USERNAME=""
PASSWORD=""
GUID=""
pp = pprint.PrettyPrinter(indent=4)
session = requests.Session()
headers = {
"accept-api-version": "resource=2.1, protocol=1.0",
"x-brand": "T",
"content-type": "application/json; charset=utf-8",
"accept-encoding": "gzip",
"user-agent": "okhttp/4.10.0",
}
server = "https://b2c-login.toyota-europe.com"
HEADERS[3]
#print("1 ----- 1")
url1 = "/json/realms/root/realms/tme/authenticate?authIndexType=service&authIndexValue=oneapp"
req1 = requests.Request("POST", server + url1, headers=headers)
prep1 = req1.prepare()
resp1 = session.send(prep1)
assert(resp1.status_code == 200)
dict1 = json.loads(resp1.text)
#print(dict1)
HEADERS[5]
#print("\n2 ----- 2")
url2 = "/json/realms/root/realms/tme/authenticate?authIndexType=service&authIndexValue=oneapp"
data2 = {"authId":dict1["authId"],"callbacks":[{"type":"NameCallback","output":[{"name":"prompt","value":"Market Locale"}],"input":[{"name":"IDToken1","value":"GB"}],"_id":0},{"type":"NameCallback","output":[{"name":"prompt","value":"Internationalization"}],"input":[{"name":"IDToken2","value":"en-GB"}],"_id":1},{"type":"NameCallback","output":[{"name":"prompt","value":"UI Locales"}],"input":[{"name":"IDToken3","value":"en"}],"_id":2}]}
req2 = requests.Request("POST", server + url2, data=json.dumps(data2), headers=headers)
prep2 = req2.prepare()
resp2 = session.send(prep2)
assert(resp2.status_code == 200)
dict2 = json.loads(resp2.text)
#print(dict2)
HEADERS[7]
#print("\n3 ----- 3")
url3 = "/json/realms/root/realms/tme/authenticate"
data3 = {"authId":dict2["authId"],"callbacks":[{"type":"NameCallback","output":[{"name":"prompt","value":"User Name"}],"input":[{"name":"IDToken1","value":USERNAME}],"_id":3},{"type":"ChoiceCallback","output":[{"name":"prompt","value":"Prompt"},{"name":"choices","value":["Local","Google","Facebook","Apple"]},{"name":"defaultChoice","value":0}],"input":[{"name":"IDToken2","value":0}],"_id":4}]}
req3 = requests.Request("POST", server + url3, data=json.dumps(data3), headers=headers)
prep3 = req3.prepare()
resp3 = session.send(prep3)
assert(resp3.status_code == 200)
dict3 = json.loads(resp3.text)
#print(dict3)
HEADERS[9]
#print("\n4 ----- 4")
url4 = "/json/realms/root/realms/tme/authenticate"
data4 = {"authId":dict3["authId"],"callbacks":[{"type":"PasswordCallback","output":[{"name":"prompt","value":"Password"}],"input":[{"name":"IDToken1","value":PASSWORD}],"_id":5},{"type":"ChoiceCallback","output":[{"name":"prompt","value":"Prompt"},{"name":"choices","value":["continue","resetpass"]},{"name":"defaultChoice","value":0}],"input":[{"name":"IDToken2","value":0}],"_id":6}]}
req4 = requests.Request("POST", server + url4, data=json.dumps(data4), headers=headers)
prep4 = req4.prepare()
resp4 = session.send(prep4)
assert(resp4.status_code == 200)
dict4 = json.loads(resp4.text)
#print(dict4)
HEADERS[11]
#print("\n5 -----5 ")
url5 = "/oauth2/realms/root/realms/tme/authorize?client_id=oneapp&scope=openid profile write&response_type=code&redirect_uri=com.toyota.oneapp:/oauth2Callback&code_challenge=CfIzFZNt0wD4TtMg49PYvR-xQglTQdqL9blKZx0oqIk&code_challenge_method=S256"
headers5 = headers.copy()
headers5["cookie"] = "iPlanetDirectoryPro=" + dict4["tokenId"]
req5 = requests.Request("GET", server + url5, headers=headers5)
prep5 = req5.prepare()
resp5 = session.send(prep5, allow_redirects=False)
assert(resp5.status_code == 302)
up = urllib.parse.urlparse(resp5.headers["location"])
qs = urllib.parse.parse_qs(up.query)["code"][0]
#print(qs)
HEADERS[13]
#print("\n6 -----6 ")
url6 = "/oauth2/realms/root/realms/tme/access_token"
headers6 = headers.copy()
headers6["content-type"] = "application/x-www-form-urlencoded"
headers6["authorization"] = "basic b25lYXBwOm9uZWFwcA=="
data6={"client_id": "oneapp",
"code": qs,
"redirect_uri": "com.toyota.oneapp:/oauth2Callback",
"grant_type": "authorization_code",
"code_verifier": "vOVtatZC5dAFHPNDSZeWs9wOpchaOv4-B4GwjL2Ky0cVqXP8tfmRtFQOfe5RFw5aXS_cPoFEZcQP9ezggMOPrg"}
req6 = requests.Request("POST", server + url6, data=data6, headers=headers6)
prep6 = req6.prepare()
#pretty_print_POST(prep6)
resp6 = session.send(prep6)
assert(resp6.status_code == 200)
dict6 = json.loads(resp6.text)
#pp.pprint(dict6)
Yeah I think we have the auth token!!!
Can we get telemetetry?
#print("\n7 -----7")
#url7 = "/v4/account"
url7 = "/v2/vehicle/guid"
headers7 = {"x-api-key": "tTZipv6liF74PwMfk9Ed68AQ0bISswwf3iHQdqcF",
"x-device-timezone": "GMT",
"accept": "application/json",
"x-guid": GUID,
"authorization": "Bearer " + dict6["access_token"],
"accept-encoding": "gzip",
"user-agent": "okhttp/4.10.0"}
req7 = requests.Request("GET", "https://ctpa-oneapi.tceu-ctp-prd.toyotaconnectedeurope.io" + url7, headers=headers7)
prep7 = req7.prepare()
#pretty_print_POST(prep7)
resp7 = session.send(prep7)
#assert(resp7.status_code == 200)
dict7 = json.loads(resp7.text)
pp.pprint(dict7)`

This gist will get you connected to the new toyota services. [...]

Good discovery! The system behind https://b2c-login.toyota-europe.com/ is probably from ForgeRock AS and is only used for identity and access management. I don't think that the telemetry data is also available via this endpoint.
By the way: Authentication is still possible via https://ssoms.toyota-europe.com/ ;-)

Yep it is ForgeRock AS and once you have your access token it changes URL from https://b2c-login.toyota-europe.com to https://ctpa-oneapi.tceu-ctp-prd.toyotaconnectedeurope.io. This has many endpoints to pull information from but seems little point moving forward until I have worked out how to automatically get hold of the GUID(customerId). Can post up later what endpoints I've found and data it is responding with.

What is the GUID (customerId) format? I haven't been able to locate the https://cpb2cs.toyota-europe.com/vehicle/user/<This Will Be Your GUID>/... request, but https://ssoms.toyota-europe.com authentication provides both a uuid and a myToyotaId. The latter is a combination of three letters and five digits (abc12345). I take it that the GUID is neither of those?

I start at https://www.toyota.co.uk/customer/portal#/sso/login/autoclose=true which logs you in and shows you your cars. I then click on my car(I have developer tools open) and it loads the details for the car. In the developer tools network view there are two requests for a URL starting with my cars Vin number if you look at the request URL under headers you should see the GUID. Its format is xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.
Hopefully you can find it and then confirm that it is working for you.

I think it is using the UUID from the single sign on as GUID @GitOldGrumpy.
Please have a look at the tojota repo from calmjm:
https://github.com/calmjm/tojota/blob/ed49d83fd6cf2baf1bf528e40c58abd4a461b0c4/tojota.py#L157

I've just had a look the UUID is the GUID but the access token does not work, which is to be expected. Still confused on where the new app pulls this from...

@CM000n Sounds good if this fixes it! But I don't have an answer regarding ha_toyota. Some part of it is ported over on this branch https://github.com/DurgNomis-drol/ha_toyota/tree/v2, but I never finished it. It needs a bit of work to get working. Again, it stalled because I don't have car to test most of the features on. If any one wants to pick it up, they are more then welcome to. And I will help get it working, but right now it is just to much of a task when I can't test most of it locally.

Updated the gist with some of the endpoints I've found but for some reason I'm not authenticated for them all.

Hi, I was migrated also with my Yaris Cross (2023) (works with new status API endpoint) and RAV4 Plugin (2022) (works only with legacy status endpoint) and HA integration stopped working as described here in comments. However when testing API using mytoyota python lib, I was able to get all needed information. Same with calling directly APIs. Unfortunately I didn't stored all API responses to compare but looks like smart info is missing (status info about locks, lights etc.) so maybe for that is now only special API endpoint.
API endpoint for "connected services": https://cpb2cs.toyota-europe.com/vehicle/user/{{uid}}/vehicle/{{VIN_RAV4}}?legacy=true&services=fud,connected
this endpoint returns:
"connected": false,
"connectedService": {"status": "DISABLED"...}
so maybe this is the reason why HA integration states that connected services are offline? anyhow all other APIs worked well:
location: https://myt-agg.toyota-europe.com/cma/api/users/{{uid}}/vehicle/location
ODO: https://myt-agg.toyota-europe.com/cma/api/vehicle/{{VIN_RAV4}}/addtionalInfo
status: https://myt-agg.toyota-europe.com/cma/api/users/{{uid}}/vehicles/{{VIN_RAV4}}/vehicleStatus
legacy status: https://myt-agg.toyota-europe.com/cma/api/vehicles/{{VIN_RAV4}}/remoteControl/status
trips: https://cpb2cs.toyota-europe.com/api/user/{{uid}}/cms/trips/v2/history/vin/{{VIN_RAV4}}/1
trip: https://cpb2cs.toyota-europe.com/api/user/{{uid}}/cms/trips/v2/{{trip_ID}}/events/vin/{{VIN_RAV4}}
driving stats: https://myt-agg.toyota-europe.com/cma/api/v2/trips/summarize?from=2023-01-01&calendarInterval=month
as stated cannot compare API results but one big difference I see is that "status endpoint" for new cars now doesn't show lock/light statuses... results is exactly same as for older vehicle...
I had one issue before with my RAV4 that it didn't show any legacy information which was available in mytoyota lib
(e.g. it showed only EvTravelableDistance but not GasolineTravelableDistance and also all other info available here in json generated by mytoyota python lib was missing...  Thats why I asked in antoher github issue to update HA integration to latest mytoyota plugin... I don't have knowledge how to do it yet. Already tried to force HA use latest mytoyota python lib, but HA integration started to return errors and didn't work at all so there might be some compatibility issues when using latest mytoyota lib (0.9.2) and the one used by HA_toyota integration (0.7.8):
       "VehicleInfo": {             "AcquisitionDatetime": "2023-11-09T13:48:27Z",             "RemoteHvacInfo": {                 "InsideTemperature": 25,                 "RemoteHvacMode": 0,                 "RemoteHvacProhibitionSignal": 1,                 "SettingTemperature": 21.0,                 "BlowerStatus": 0,                 "FrontDefoggerStatus": 0,                 "RearDefoggerStatus": 0,                 "LatestAcStartTime": "2023-11-09T05:39:15Z",                 "TemperatureDisplayFlag": 1,                 "Temperaturelevel": 32             },             "ChargeInfo": {                 "GasolineTravelableDistanceUnit": 1,                 "GasolineTravelableDistance": 507,                 "PlugInHistory": 33,                 "RemainingChargeTime": 65535,                 "EvTravelableDistance": 0.0,                 "EvTravelableDistanceSubtractionRate": 2,                 "ChargeRemainingAmount": 30,                 "SettingChangeAcceptanceStatus": 0,                 "ChargeType": 15,                 "ChargeWeek": 0,                 "ChargeStartTime": "42:35",                 "ChargeEndTime": "42:35",                 "ConnectorStatus": 2,                 "BatteryPowerSupplyPossibleTime": 16383,                 "ChargingStatus": "none",                 "EvDistanceWithAirCoInKm": 0.0,                 "PlugStatus": 12,                 "EvDistanceInKm": 0.0             }         },         "ReturnCode": "000000"

Hi @DurgNomis-drol and @HuffYk,
I just created a tag for testing the update to mytoyota 0.9.2 within the ha_toyota custom integration: https://github.com/DurgNomis-drol/ha_toyota/releases/tag/v2.0.0-testing
The tag uses the V2 branch as a basis.
I think this makes testing easier in combination with HACS. I hope that's okay @DurgNomis-drol?
I also don't have much time at the moment, but I'll see how much of it I can spare for ha_toyota in the meantime :wink:
Unfortunately updating to the new mytoyota version it's a bit of trial and error because we don't have good unit tests for the custom integration and writing them is unfortunately a bit of a PITA. So any help is more than welcome!

Hi @CM000n, did few tests.
Looks like some changes from master branch have to be merged first. e.g. I had to fix deprecated async_setup_platforms with
await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
Maybe some other changes from master should be merged also? I temporary fixed mytoyota lib to overcome "connected services" issue and now HA integration connected successfully, but it received only location for each car nothing else. And in log there are these errors (enabled also debugging):
ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform toyota.binary_sensor: Platform not found (cannot import name 'ToyotaEntityDescription' from 'custom_components.toyota.entity' (/config/custom_components/toyota/entity.py)).

ERROR (MainThread) [homeassistant.components.sensor] Error while setting up toyota platform for sensor
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 359, in _async_setup_platform
await asyncio.shield(task)
File "/config/custom_components/toyota/sensor.py", line 270, in async_setup_entry
ToyotaStatisticsSensor(
File "/config/custom_components/toyota/sensor.py", line 321, in __init__
self.period = description.period
^^^^^^^^^^^^^^^^^^
AttributeError: 'ToyotaSensorEntityDescription' object has no attribute 'period'

not sure if it is because something has to be merged from master what was already fixed or it is connected with new mytoyota lib

Hi @CM000n, did few tests.
Looks like some changes from master branch have to be merged first. e.g. I had to fix deprecated async_setup_platforms with

The master branch ist already merged 😉

If I compare e.g. init.py from master (https://github.com/DurgNomis-drol/ha_toyota/pull/131 ) with v<IP_ADDRESS>-testing there are many changes missing e.g. mentioned
await hass.config_entries.async_forward_entry_setups(entry, PLATFORMS)
introduces in v1.2.11 release (https://github.com/DurgNomis-drol/ha_toyota/pull/126/files )

did some testing with official v1.2.11, I patched mytoyota lib to overcome "connected services" issue and now I was able to receive other sensors:
RAV4 Plugin (2022) - older legacy API (not available status of locks or lights in API)

statistics sensors (current week/month/year)
front/rear defogger
fuel tank
ODO meter
EV battery status (only "none" but it was also before migration)
HVAC (only "Unknown" but it was also before migration)
number plate
location

missing sensors what I remember:

Range (before migration I saw at least EV travel distance)

Yaris Cross (2023) - new API (status of locks and lights is available in API)

statistics sensors (current week/month/year)
fuel tank
ODO meter
location

missing sensors what I remember:

lights/locks statuses

Hi @CM000n
If I compare e.g. __init__.py from master (#131 ) with v2.0.0-testing there are many changes missing e.g. mentioned [...]

Yes, I think some of the incoming and existing changes were lost during the merge when the merge conflicts were resolved.
We need to look at this again in general and sort it out.

I've just had a look the UUID is the GUID but the access token does not work, which is to be expected. Still confused on where the new app pulls this from...

I use e.g. this: https://cpb2cs.toyota-europe.com/vehicle/user/{{uid}}/vehicles and uid is coming from https://ssoms.toyota-europe.com/authenticate as @CM000n wrote...

locate def _has_connected_services_enabled function and replace this:

                _LOGGER.error(
                    "Please setup Connected Services if you want live data from the car. (%s)",
                    censor_vin(self.vin),
                )
                return False

with this:
 return True

That's great! With this "dirty" fix and v1.2.11, I get the data I need: I use the integration for controlling the charging (it's a bZ4x, so an EV), and I can find the "remaining charge" as a attribute to the EV battery status sensor. This temporarily solves the problem for me, but I'm hoping we'll be able to fix the integration properly in the days to come 👍

Hi @CM000n
would it be possible to add back v2.0.0-testing tag ? I would like to test during weekend, but not in my production env (where I installed it yesterday), but rather I created dev env in RPI so would like to install it there from UI rather than manually updating all needed files in shell. thanks!

Hi @HuffYk,
No, the tags don't make much sense, as I found out when so many changes are made. The best way to test this is to pull the latest version of the Repo / V2 branch and manually replace the "toyota" folder in the custom components directory of your Home Assistant installation.

ok understand, no problem

@CM000n let me know if I can do testing. I tried latest V2 and getting this errors in log:
2023-11-12 00:28:57.005 ERROR (MainThread) [homeassistant.components.binary_sensor] Error while setting up toyota platform for binary_sensor
File "/config/custom_components/toyota/binary_sensor.py", line 307, in async_setup_entry
ToyotaBinarySensor(
File "/config/custom_components/toyota/entity.py", line 30, in __init__
self.vehicle: Vehicle = coordinator.data[self.index]["data"]
~~~~~~~~~~~~~~~~^^^^^^^^^^^^
TypeError: list indices must be integers or slices, not Vehicle

and few TypeError: 'NoneType' object is not callable errors I suppose related to 1st one mentioned above.
In UI I'm able to see locations and few sensors all with unavailable or unknown status.

Hi @HuffYk, thank you very much. I am already aware of that. Please see the comment in the associated pull request.
I think we should move further discussions regarding the custom integration update to the new mytoyota version there, as they are no longer directly related to the issue reported here.

Were have we moved discussions too? I can pull from the new endpoints all most all of the information relevant to my cars(which is everything I could get on the old endpoints plus all the trip details) but to move forward need some help getting hold of further endpoints and either integrating the new endpoint into the current mytoyota or creating something new?

Please open an PR in https://github.com/DurgNomis-drol/mytoyota so we can start implementing the new API endpoints


first implementation of annotation track

adds a basic gene track to the Mutations page when a gene coordinate csv (format in screenshot) is provided.

Few issues to iron out:

input annotation file format checks. (I guess it might be better to switch to a standard bed or gtf format file at some point.)
subset annotation data to the same chromosome as tree sequence
restrict y zooming on the genome and tree tracks

https://github.com/tskit-dev/tsqc/assets/25925005/c4e3896e-bf6b-47a7-b99e-ec4a45278e1e

Few minor changes, let's merge then

LGTM! Putting the annotations_file in a global config is a bit icky, but it works for now and I can imagine that being something you just want to set as a default (in your .config/tsqc.conf file, at some point).

sure, that makes sense.


Upgrade Microsoft.WindowsAppSDK.WinUI to preview1

Proposal: please Upgrade Microsoft.WindowsAppSDK.WinUI to preview1

Summary
Upgrade Microsoft.WindowsAppSDK.WinUI to preview1
Rationale
I am upgrading a solution of a customer; I can't move to Microsoft.WindowsAppSDK preview1 because the NuGet package Microsoft.WindowsAppSDK.WinUI still references experimental1.
This is a blocker that prevents the upgrade of dependent packages like WindowsCommunityToolkit and Microsoft.XamlBehaviors.
Scope
This proposal will allow to align multiple NuGet packages to preview1.

Hey @curia-damiano, in Preview 1 we've consolidated to a single NuGet package. You should uninstall all the other NuGet packages and only have Microsoft.WindowsAppSDK as your sole NuGet package! That makes updating in the future even easier as there's just one package to update 😊


Question regarding relation 'has necessary component activity'

Hello @cmungall (I guess)
Maybe this is a ticket for RO, but I want to make sure I formulate the issue correctly:
I thought @dosumis had created the relation 'has necessary component activity'  to capture compounds functions, and for example to deal with the old DNA binding issue regarding to transcription factors (see #16214).
I thought regulates would not be transitive over 'has necessary component'. Which means that:
DNA binding
-- 'is_a' DNA-binding transcription factor activity
----- 'regulates' regulation of DNA-binding transcription factor activity (== 'is_a' regulation of DNA binding)
While:
DNA binding
-- 'has necessary component' DNA-binding transcription factor activity
----- 'regulates'  regulation of DNA-binding transcription factor activity (is NOT a regulation of DNA binding), ie 'regulates' would not be transitive over 'has necessary component'
Currently there are no inference chains; can we add some (Is this a RO ticket?)
(Also, right now it's a child of 'positively regulated by', which seems very odd).
This would be very useful to deal with all compound functions (which is probably everything except for binding).
Thanks, Pascale

It may be best to hammer out precisely what is required on this ticket first.
I'm going to need to allocate a chunk of time to focus on this to give it the response it deserves - can this wait until we see each other at USC?
In the meantime I believe there were some graphical documents (in a ticket?) that illustrated the thinking here - do you happen to have those?

Yes let's discuss at USC. I dont find the graphical documents in a ticket - I see a lot of discussion here
#14012 but no graphics.
Pascale

Resolved here: https://github.com/geneontology/go-ontology/issues/16972


Module resolution: Named imports not supported with import attributes

Demo Repo
https://github.com/mdmower/with-json-tsc
See bottom of post for information.
Which of the following problems are you reporting?
The module specifier resolves at build time, but not at run time
Demonstrate the defect described above with a code sample.
import {compilerOptions} from './tsconfig.json' with {type: 'json'};
Run tsc --showConfig and paste its output here
{
    "compilerOptions": {
        "target": "es2023",
        "lib": [
            "es2023"
        ],
        "module": "nodenext",
        "moduleResolution": "nodenext",
        "resolveJsonModule": true,
        "strict": true,
        "moduleDetection": "force",
        "esModuleInterop": true,
        "allowSyntheticDefaultImports": true,
        "resolvePackageJsonExports": true,
        "resolvePackageJsonImports": true,
        "useDefineForClassFields": true,
        "noImplicitAny": true,
        "noImplicitThis": true,
        "strictNullChecks": true,
        "strictFunctionTypes": true,
        "strictBindCallApply": true,
        "strictPropertyInitialization": true,
        "alwaysStrict": true,
        "useUnknownInCatchVariables": true
    },
    "files": [
        "./index.ts"
    ]
}

Run tsc --traceResolution and paste its output here
Found 'package.json' at 'C:/Users/matt.mower/source/with-json-tsc/package.json'.

There was an error creating your Issue: body is too long, body is too long (maximum is 65536 characters).

Paste the package.json of the importing module, if it exists
{
  "type": "module",
  "scripts": {
    "build": "tsc",
    "start": "node index.js"
  },
  "devDependencies": {
    "@types/node": "^22",
    "typescript": "^5.5"
  }
}

Paste the package.json of the target module, if it exists
N/A
Any other comments can go here
TypeScript 5.3 added support for import attributes. tsc does not warn or error when attempting to use named imports for these kinds of imports. When named imports are used, they are preserved in the produced .js and there is no environment where they are supported.
For example, in the linked demo repository:
import {compilerOptions} from './tsconfig.json' with {type: 'json'};
console.log(compilerOptions);

compiles to:
import { compilerOptions } from './tsconfig.json' with { type: 'json' };
console.log(compilerOptions);

which does not run in Node.js 22 or Chrome 127.
Given that --resolveJsonModule has historically allowed named imports and produces valid CommonJS, it's likely that developers will assume TypeScript can handle named imports when using import attributes as well.
For example, if the linked demo repository is set to output CommonJS instead of ESM, then:
import {compilerOptions} from "./tsconfig.json";
console.log(compilerOptions);

compiles to:
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
const tsconfig_json_1 = require("./tsconfig.json");
console.log(tsconfig_json_1.compilerOptions);

It seems that TypeScript should disallow named imports when import attributes are used, or should downcompile them similar to their handling in CommonJS.

NB: I'm not a module expert. I'd assume import attributes are not the issue here since TS is intentionally agnostic to them. But if you're using esm and importing a json module, I'd think #46434 would warn you if you try named imports. That doesn't seem to be happening; why not?


This module is insecure and therefore useless

This library assumes that it may be behind a proxy, and blindly trusts the request headers: https://github.com/baminteractive/express-ipfilter/blob/5161db16503964b980fa143c8b8d61c436040571/lib/ipfilter.js#L62-L64
Since X-Forwarded-For and CF-Connecting-IP can be added by any client, the fact that the library relies on it makes it useless for access control. To fix the issue, do not use these request headers, and add an option to use these headers ONLY IF set by the developer.

Open to a PR to address this.

I just reported the issue to raise awareness of the problem. I'm not going to submit a PR for the lack of time, even though the patch itself is trivial.
The next user who cares is of course free to submit the PR.


Save the created date when new teams are made

That way teams could be timed out after a certain amount of time and deleted as to not occupy space

Done


MonadRandom-0.5

MonadRandom-0.5 (Brent Yorgey<EMAIL_ADDRESS>@byorgey) is out of bounds for:

[x] avers-<IP_ADDRESS> (>=<IP_ADDRESS> && < 0.5). Tomas Carnecky @wereHamster. @wereHamster. Used by: library, test-suite
[x] diagrams-contrib-<IP_ADDRESS> (>=0.1.8 && < 0.5). Brent Yorgey<EMAIL_ADDRESS>@byorgey. @bergey @byorgey @fryguybob @jeffreyrosenbluth. Used by: library
[ ] vivid-<IP_ADDRESS> (>=0.1 && < 0.5). Tom Murphy<EMAIL_ADDRESS>@amindfv.. Used by: library
[x] monad-http-<IP_ADDRESS> (>=<IP_ADDRESS> && < 0.5). Oleg Grenrus<EMAIL_ADDRESS>@phadej. @futurice. Used by: library

I bumped the upper bounds of avers.

diagrams-contrib upper bound fixed.

A new entry

vivid-<IP_ADDRESS> (>=0.1 && < 0.5). Tom Murphy<EMAIL_ADDRESS>@amindfv.. Used by: library

monad-http fixed

@amindfv vivid has been removed from the nightly builds, and is not currently on track for inclusion in LTS 8. Once a release of vivid compatible with the latest MonadRandom is made available, feel free to open an issue on https://github.com/fpco/lts-haskell/issues to get vivid added to LTS 8.

The following build failures occurred with MonadRandom-0.5:
diversity-<IP_ADDRESS> @GregorySchwartz
[3 of 6] Compiling Math.Diversity.RandomSampling ( src/src-lib/Math/Diversity/RandomSampling.hs, dist/build/Math/Diversity/RandomSampling.o )

src/src-lib/Math/Diversity/RandomSampling.hs:24:45: error:
    Not in scope: type constructor or class <E2><80><98>StdGen<E2><80><99>

src/src-lib/Math/Diversity/RandomSampling.hs:32:52: error:
    Not in scope: type constructor or class <E2><80><98>StdGen<E2><80><99>

random-tree-<IP_ADDRESS> @GregorySchwartz
[1 of 3] Compiling Math.RandomTree.Types ( src/Math/RandomTree/Types.hs, dist/build/Math/RandomTree/Types.o )

src/Math/RandomTree/Types.hs:28:88: error:
    Not in scope: type constructor or class <E2><80><98>StdGen<E2><80><99>

@GregorySchwartz diversity and random-tree hvae been removed from the nightly builds, and are not currently on track for inclusion in LTS 8. Once releases of these compatible with the latest MonadRandom are made available, feel free to open issues on https://github.com/fpco/lts-haskell/issues to get them added to LTS 8.

Hmm, looks like MonadRandom used to re-export StdGen but it doesn't anymore?  Drat.    I could re-add that export to MonadRandom without bumping the major version number according to the PVP, right?  Would diversity and random-tree then be OK with no change, or would we have to deprecate MonadRandom-0.5?

@byorgey I believe that is correct, you can restore the re-export of StdGen as a minor version bump according to the PVP, and then diversity and random-tree would be OK with no change. (Should be a small change to those packages, though, right?) No need to deprecate 0.5 unless you really want to. Stackage will start using 0.5.1 as soon as it is available.

Sure, it would be a small change to those packages as well, but I'd rather not cause things to break unnecessarily.

OK, MonadRandom-0.5.1 is now uploaded to Hackage.  Hopefully this will fix things without any changes needed to diversity and random-tree.

I've restored diversity and random-tree to the build plan. Looks like they work just fine with MonadRandom-0.5.1. 👍


[Flutter Web (MacOS)] Error: MissingPluginException

MissingPluginException(No implementation found for method checkPermissionStatus on channel flutter.baseflow.com/permissions/methods).
Dart code:
child: MobileScanner(     controller: MobileScannerController(         facing: CameraFacing.back,         formats: [BarcodeFormat.qrCode],     ),     onDetect: (barcode, args) {}, ),
index.html code:
`

Example Web

`

The permission_handler package is not supported on macOS. You don't have to check for permissions on macOS and on web.


Update create-subnet walkthrough

Update walkthrough as CLI options have changed

Pages under /subnets/deploy-a-subnet/ need similar updates.


generator: campus user

Implement campus user system role (maybe in invenio-access) and the corresponding Generator. It might be done with some sort of IP treatment over user defined ranges.
Note: This issue has been identified as a self-contained task that could be carried out by a partner.

I think this issue https://github.com/inveniosoftware/invenio-access/issues/168, this issue and the current issue are the same. Let's only keep this one open.

I think this issue #27 and this current issue are the same. Let's only keep this one open.

True, tho the other one was more generic. Sorry I missed the duplicate.


Don't call run() on empty formactions

Fixes https://github.com/newsboat/newsboat/issues/1369.

[ ] I believe I got all relevant places but will put a little more time in trying to find other places where we checked for a nullptr formaction (before we introduced the EmptyFormAction).

Coverage decreased (-0.004%) to 58.535% when pulling 2b889864a45b78a80679822b4c8fac64f4f31be1 on dennisschagt:bugfix/issue-1369 into 119582d72d2dd25993d06b6f809e26944827237e on newsboat:master.


property attribute with @Consume does not work

Fix #3021

97a4591:

Fixed the flawed propertyName.startsWith("on") condition as reported by @aldettinger


Add terminationGracePeriod option, and use it when killing Solr.

Fixes #227
This will use the terminationGracePeriod, minus a few seconds, and give that to Solr as the SOLR_STOP_WAIT value.
That way Solr and Kubernetes are on the same page as to how much time to wait before forcefully stopping Solr.
terminationGracePeriod used to be statically set to 10 seconds. Now it defaults to 30 seconds, but is configurable.

Please add a since 0.3.0 somewhere in the docs for this.


[BUG] Issue with conditional tags

Hey there I have an issue with conditional tags the vscode extension reports an error but theme check deosn't thanks, here is a loom about the issue.
https://www.loom.com/share/1471e9b27acf4ab6896e354699c9ffe8

Yeah so this is caused because we don't have a way to parse IF tags as HTML tag names.
Unfortunately, I don't have a fix for this because I believe it would make the syntax ambiguous. For the prettier plugin to work (and our LiquidHTML parser, which powers the next version of theme check), we kind of need to be slightly more specific about what we accept.
You have a couple of options:

Dangling open/close nodes inside if statements are OK

{% if cond %}
  <some-wrapper with-some-props>
{% else %}
  <some-other-wrapper with-some-other-props>
{% endif %}

{% if cond %}
  </some-wrapper>
{% else %}
  </some-other-wrapper>
{% endif %}

Name and props as variables

{% liquid
  if cond
    assign wrapper = 'some-wrapper'
    assign props = '...'
  else
    assign wrapper = 'some-other-wrapper'
    assign props = '...'
  endif
%}
<{{ wrapper }} {{ props }}>

</{{ wrapper }}>

Thanks!


Policies

Policies are like traits in C++. Similar to how std::iterator_traits work, policies should be used to provide some information about what events can or can't assume.
An example would be whether access to add/remove methods should be synchronized or not.
A way to implement this:

Let's say there is a concept named EventPolicy. This will contain compile-time knowledge of the different policies (e.g. a static constexpr bool synchronized for synchronization).

There should be a default named default_policy which is a class that satisfies the EventPolicy concept and is the "least assuming" policy possible.

There should be a template class called select_policy<T> where T satisfies EventPolicy. select_policy<T> should have a public: template <class Args...> class event (or an alias) which should contain the entire implementation of the event based on the policy T from the parent class.

::slotty::event should be template <class Args...> using event = typename select_policy<default_policy>::template event<Args...>. In this way, existing code need not change. Because of this, default_policy should mirror the behavior of event at the moment so as to not change the behavior of programs.

The new implementation should not break the API (too much). The code has been updated to modern C++. However because of lack of regression tests, nothing can be for sure. Probably should get on that...


Missing styles in production when using renderless component within server component

Environment

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     3.10.3
CLI Version:      3.10.1
Nitro Version:    2.8.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools, experimental
Runtime Modules:  -
Build Modules:    -

Reproduction
https://stackblitz.com/edit/nuxt-starter-sf3hkd?file=components%2FTest.vue,components%2FHero.server.vue,app.vue

npm run build && npm run preview
observe that styles from Test component are missing in build and so not included when page loads

Describe the bug
It's really weird that this happens only with production build, but anyway, when using some renderless component within .server.vue component, the styles (from that renderless component) won't be included in final bundle, so they can't be loaded. I also should mention, that the styles will be included if you move that component out of island, as it should be
Additional context
No response
Logs
No response

The issue still exists and there so many issues with styles on child components that I cannot even think from where to start ... overall there is a big gap in this area.
In my case I have page.server.vue and components inside and I have same issue, which is missing styles of the child-component.
What I have observer is that if lang="ts" is removed then everything works fine ... it totaly doesn't make sense.
Another observation: Having startpage.vue with some styles and child component inside. The child component styles are not being rendered, they can be rendered if:

lang="ts" is removed
startpage.vue styles are removed

nuxt have so many style bugs, sometime lose styles on prod mode, and then dev mode also loss style if upgrade nuxt versions, it's weak!


ARROW-2999: [Python] Disable ASV runs in Travis CI for now

I am doing this partially to assess the impact on CI runtime

Codecov Report

Merging #2383 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2383      +/-   ##
==========================================
- Coverage   84.66%   84.61%   -0.05%
==========================================
  Files         293      293
  Lines       45324    45324
==========================================
- Hits        38372    38352      -20
- Misses       6911     6931      +20
  Partials       41       41

Impacted Files
Coverage Δ

cpp/src/plasma/store.cc
84.98% <0%> (-4.23%)
: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 34d383b...f6caca0. Read the comment docs.

It's https://issues.apache.org/jira/browse/ARROW-2671

Thanks!

@pitrou are you OK with merging this? I do not want the benchmarks to bitrot, so I think this should motivate us to sort out the nightly / on-demand build story

Yes it's fine with me.


Remove "Members" key when parsing lists from AWS response

This fixes #27.
When AWS sends a list as a response, it typically wraps it as {"Members": [A, B, C]}. This breaks our JSON decoding, since our objects do not expect to look up a Members key, and just find the values of [A, B, C] directly.
We are now iterating through dicts -and lists to dive into each sub-structure, and look for any instance of Members, removing it. I've added a few test cases for parsing the dictionaries, which were a great start.
However, I found that pulling in the example cases from #27 directly served as quite helpful test cases, hence the extra Model files I'm including. @noppoMan and @jonnymacs, what do you two think of this copy-pasting from aws-sdk-swift? It's easy to remove, but I kind of like the extra coverage. Happy either way!
Also, if anyone has suggestions for ways to improve the algorithm, please let me know!

This is based off https://github.com/noppoMan/aws-sdk-swift-core/pull/29, so that should probably be merged first.

@jonnymacs did ya have a chance to take a look at how the Ruby SDK handles this?
Looks like the Go SDK does indeed need to handle "nested shapes" and parse 'em out.

We're going to go with #30 instead 💪


addname_update

Added my name under Contributors list!

Added my name under Contributors list!

May I know what role does the maintainer hold??
Thanks & Regards,
Priyanshu Vaishnavi
On Tue, 7 Sep, 2021, 12:16 am welcome[bot], @.***>
wrote:

Hello there! 👋 Welcome to FirstTimers! 🚀
Thank you and congrats 🎉 for opening your first pull request. A
maintainer will get back to you shortly! Join our discord community:-
https://discord.com/invite/QHJ6szbdP6
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CuriousGrids/FirstTimers/pull/19#issuecomment-913809166,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEX6UTAF3U4IYG4MN7TTHDUAUD6VANCNFSM5DQ5PX7Q
.

Thank you for your support!
On Tue, 7 Sep, 2021, 1:42 am welcome[bot], @.***> wrote:

Congrats on merging your first Pull Request! 🎉 All the best for your
amazing open source journey ahead.⚡
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CuriousGrids/FirstTimers/pull/19#issuecomment-913837029,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQEX6UT275DJPMUZTGMEAN3UAUOBNANCNFSM5DQ5PX7Q
.


fix(call-home): use exclusive method to calculate percentile

Changes:

The get_percentile function uses inclusive method of calculating percentiles. This is not the preferred way of calculating percentiles for discrete data sets. This PR changes the implementation to use the exclusive method. This method is more reliable for calculating percentiles between 10 and 90 percentile.
get_percentile returns the generated percentile as an integer without rounding it to the nearest interger. It uses a type cast for the f64, and simply drops the franctional part.
get_percentile returns a 0 for empty data sets. Percentiles for empty data sets are undefined.

While this PR introduces these changes. It doesn't break the existing APIs and doesn't change data types. This needs to be taken up in a different PR with adequate changes in the backed server.

bors merge


No indication of downloading

When downloading manga, there isn't any indication whether it's being downloaded and there is no progress indication

I'll see the feasibility of doing this for a TUI. I did want it added in originally, but this might take longer to implement.

https://github.com/darylhjd/mangadesk/commit/8c5cc30b7642ee2c35c2bf4c68955a155be5b920
User will now be notified when downloads are finished.


Calculate catecholamin dosing

Working on the eICU database and score calculation. Will provide some new concepts to the code base.

Thanks for the contribution. Seems like this depends on two tables which aren't in the PR - are they in another PR or not yet committed?

Since this has gone a bit stale I'll close the PRs. We'd very much welcome the contribution, but it would be best to (1) combine similar/codependent concepts into a single PR and (2) ensure that the concepts are fully reproducible from the raw data released.


fix: adding ability to share state across multiple sibling states

Proposal:
We had a specific case where we wanted to share state across sibling components in storybook that work together such as search bar/listings.
Let me know if you have alternates to help with this.

Thanks for this PR, I', afraid the usecase you had falls outside of the scope of this plugin.


View: Maximize Editor Group disabled when closing sidebar

Version: 1.44.2 (system setup)
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T16:36:23.138Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.16299
The setting View: Maximize Editor Group seems to stay enabled in all cases except after closing the sidebar.
Steps to Reproduce:

Have multiple editor groups (I have 4)
Close sidebar (Explorer/SCM etc.)
Turn on View: Maximize Editor Group and click between editors. Notice each editor expands when selected.
Open sidebar. Click between groups and notice each editor still expands.
Close sidebar. Click between groups and notice editors do not expand.
Turn on View: Maximize Editor Group. Notice each editor expands when selected.

Does this issue occur when all extensions are disabled?: Yes

#70083


Tabs are still 8 spaces

Description
Overview says "- Reduces tabs’ size to 4 spaces instead of 8." but I still see 8
How to replicate the issue + URL
https://github.com/kubernetes/kubernetes/pull/128601/files
https://github.com/thockin/kubernetes/blob/master/cmd/fieldnamedocscheck/field_name_docs_check.go
Extension version
24.10.28
Browser(s) used
Chrome
Token ⚠

[X] I set a token in the options page. I understand that some features require a token to work.

You're missing the rest of the quote of the feature

where GitHub doesn't follow the user’s preferences.

Please check your tab settings in https://github.com/settings/appearance. The feature calls out the spots RGH is overriding it from 8 to 4, https://github.com/refined-github/refined-github/blob/main/source/features/tab-size.css

Indeed there are a lot more details in the CSS file itself.
In short Refined GitHub only sets a new default value, without necessarily overriding the user's setting.

Would you believe I had no idea there were themes with a tabstop setting?  TIL.  Thanks.


XCM execution failed on dest chain when given fee is less than the actually fee spend

According to the Issue reported by Acala, when transfer asset from Khala to Karura, if the fee set in XCM message by Khala XCM module is less than the actually fee spend in karura, XCM execution will failed on Karura.
The reason why this happened is because we have the following code that always set half of the tranfer amount as fee.  So far when we transfer PHA, the actually fee is 0.0512 PHA on Karura, that means if user transfer amount is less than 0.1024, the fee we set in Khala will less than 0.0512, we willl get TooExpensive error on Karura.
	let fee = if T::FeeAssets::get().contains(&asset)
		|| T::NativeAssetChecker::is_native_asset(&asset)
	{
		match asset.fun {
			// So far only half of amount are allowed to be used as fee
			Fungible(amount) => MultiAsset {
				fun: Fungible(amount / 2),
				id: asset.id.clone(),
			},
			// We do not support unfungible asset transfer, nor support it as fee
			_ => return Err(Error::<T>::AssetNotFound.into()),
		}
	} else {
		// Basiclly, if the asset is supported as fee in our system, it should be also supported in the dest
		// parachain, so if we are not support use this asset as fee, try use PHA as fee asset instead
		MultiAsset {
			fun: Fungible(T::DefaultFee::get()),
			id: T::NativeAssetChecker::native_asset_id().into(),
		}
	};

We need to update the fee calculation mechanism to make sure the given fee will never less than actually fee spend on destination chain.

PR#81 is going to solve this problem


Cursor disappears on window resize/fullscreen in Yosemite

From @GoogleCodeExporter on March 16, 2015 9:25
I'm using snapshot 73 in Yosemite. Whenever I resize a window or enter native
fullscreen mode, my cursor disappears for all modes and does not reappear.
Switching modes, entering text, etc. does not bring it back. Thanks!

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 29 Oct 2014 at 5:21
Copied from original issue: douglasdrumond/macvim#518

please feel free to create a new issue if we still have the issue with Snapshot 81.


Bug: blank screen on database connect after OS update

Describe the bug
surrealist runs normally till i try to connect to my server.
the screen goes blank and the console stops outputing
Steps to reproduce
im on linux mint fresh out of the box
im using WEBKIT_DISABLE_DMABUF_RENDERER=1 surrealist to run it
Expected behaviour
i connect to my database and surrealist stops responding to my mouse and clicks
and after some time it goes blank
the console output is
https://pastebin.com/BUSEv10T
Surrealist Environment
surrealist v3.0.0-beta.2 or v2.1.6 (these are the ones i tried)
Additional info
this bug started to occur after a linux mint update

Sorry, my English isn’t very good.
Describe the bug
surrealist runs normally till i try to connect to my server.
the screen goes blank and the console stops outputing
Steps to reproduce
I’m ubuntu on wsl2
im using WEBKIT_DISABLE_DMABUF_RENDERER=1
Surrealist Environment
surrealist v2.1.5
Additional info
this bug started to occur after
In the query input field of Surrealist, I entered the following query:
update register:xxxxxxxxx set attention +=<EMAIL_ADDRESS>What I tried to do to solve it
Updated from ver2.1.5 to ver2.1.6
Delete Surrealist ver2.1.6 and reinstall it.

@simeonnv @shadowInvert Could you check if the developer console contains any errors or other hints as to what could be causing this?

Just for confirmation here, the latest stable release (2.1.6) was working correctly, however it suddenly stopped working after an operating system update?

Just for confirmation here, the latest stable release (2.1.6) was working correctly, however it suddenly stopped working after an operating system update?

I don't know about the others, but yes that's what happened to me, had an update on Ubuntu 24.04 yesterday, and now it doesn't work. (Same issues as stated by the others)

Just for confirmation here, the latest stable release (2.1.6) was working correctly, however it suddenly stopped working after an operating system update?

no it doesn't. I tried it

Is this happening with the .deb, .rpm, or .AppImage installers?
If deb or rpm was used, would it be possible to try the AppImage instead?

For me it's with the .deb files. I'll try the AppImage.

For 2.16 the AppImage runs fine on Pop_OS/Ubuntu but not the .deb.
3.0 beta AppImage loads but when you select Connect it hangs and then you get the white screen of doom.

appimage 2.1.6 works fine on mint

I think I was using version 2.1.5.But it may have been downloaded automatically
The situation where this happened to me was when I tried adding an array to a field in the Surrealist command line, checked it, and then launched Surrealist again about 10 minutes later.
For me it's with the .deb files.
This is the state of the system when Surrealist was launched.

Expand
```
journalctl -xe
9月 11 19:24:08 SHADOW kernel: Code: 41 89 c5 41 f7 dd eb 80 66 0f 1f 44 00 00 b8 ba 00 00 00 0f 0>
9月 11 19:24:08 SHADOW kernel: RSP: 002b:00007ee79c7f3100 EFLAGS: 00000246 ORIG_RAX:<PHONE_NUMBER>000>
9月 11 19:24:08 SHADOW kernel: RAX:<PHONE_NUMBER>000000 RBX: 00007ee79c7fc640 RCX: 00007f002980d9fc
9月 11 19:24:08 SHADOW kernel: RDX:<PHONE_NUMBER>000006 RSI:<PHONE_NUMBER>003fc0 RDI:<PHONE_NUMBER>003f9d
9月 11 19:24:08 SHADOW kernel: RBP:<PHONE_NUMBER>003fc0 R08: 00007ee79c7f31d0 R09: 00007ee79c7f3300
9月 11 19:24:08 SHADOW kernel: R10:<PHONE_NUMBER>000008 R11:<PHONE_NUMBER>000246 R12:<PHONE_NUMBER>000006
9月 11 19:24:08 SHADOW kernel: R13:<PHONE_NUMBER>000016 R14:<PHONE_NUMBER>0000ff R15: 00007ee79c7f4770
9月 11 19:24:08 SHADOW kernel: FS:  00007ee79c7fc640 GS:<PHONE_NUMBER>000000
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_is_feature_enabled: Ioctl failed: -22
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
9月 11 19:25:54 SHADOW kernel: misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
9月 11 19:25:54 SHADOW rtkit-daemon[373]: Supervising 0 threads of 0 processes of 0 users.
9月 11 19:25:54 SHADOW kernel: potentially unexpected fatal signal 6.
9月 11 19:25:54 SHADOW kernel: CPU: 8 PID: 20101 Comm: t Helper Thread Not tainted <IP_ADDRESS>-micr>
9月 11 19:25:54 SHADOW kernel: RIP: 0033:0x7f167e4a29fc
9月 11 19:25:54 SHADOW kernel: Code: 41 89 c5 41 f7 dd eb 80 66 0f 1f 44 00 00 b8 ba 00 00 00 0f 0>
9月 11 19:25:54 SHADOW kernel: RSP: 002b:00007f15eeff0100 EFLAGS: 00000246 ORIG_RAX:<PHONE_NUMBER>000>
9月 11 19:25:54 SHADOW kernel: RAX:<PHONE_NUMBER>000000 RBX: 00007f15eeff9640 RCX: 00007f167e4a29fc
9月 11 19:25:54 SHADOW kernel: RDX:<PHONE_NUMBER>000006 RSI:<PHONE_NUMBER>004210 RDI:<PHONE_NUMBER>0041e9
9月 11 19:25:54 SHADOW kernel: RBP:<PHONE_NUMBER>004210 R08: 00007f15eeff01d0 R09: 00007f15eeff0300
9月 11 19:25:54 SHADOW kernel: R10:<PHONE_NUMBER>000008 R11:<PHONE_NUMBER>000246 R12:<PHONE_NUMBER>000006
9月 11 19:25:54 SHADOW kernel: R13:<PHONE_NUMBER>000016 R14:<PHONE_NUMBER>0000ff R15: 00007f15eeff1770
9月 11 19:25:54 SHADOW kernel: FS:  00007f15eeff9640 GS:<PHONE_NUMBER>000000
</details>

Appimage 3.0 beta 1 works fine on ubuntu 24.04 (haven't tried others)

Appimage 3.0 beta 1 works fine on ubuntu 22.04 with SurrealDB 2.0 but appimage 3.0 beta 2 shows blank screen when I try to connect to the database.

I am on Ubuntu 24.04.1, and can confirm this same issue. After updating from 24.04, surrealist stopped working.
The App opens but just goes blank. I uninstalled Surrealist & reinstalled but still experiencing the issue.

all versions of surrealist after 3.0.0 beta 2 has this issue with the appimages.

Hey everyone, we certainly noticed the significance of this issue and are continuing to look for a solution. We cannot reproduce this issue internally with the devices to our disposal, which has not made it trivial to debug. Additionally the circumstances causing this issue appear to vary greatly, making it additionally difficult to pin down. What we do know is that it only affects Linux devices.
To move things forward I have some additional questions I would like to gather feedback on.

Please try opening the developer tools panel, for which an explanation can be found here. This may lead to further details as to what causes this issue, especially within the Console tab.
Does this only affects the desktop app or also the web app? Is this consistent across different browsers?
Does backing up and deleting the config file ($HOME/.config/SurrealDB/Surrealist/config.json) solve the issue?
Is there a reproducible way to trigger the blank screen?

Hopefully additional insight might lead us closer to the root cause so we can fix this. Thank you all for your help and patience!

@macjuul
OS => Ubuntu 24.04.1 LTS  (gnome 46)
Kernel version => Linux 6.8.0-45-generic

I tried opening the developer panel on Linux using CTRL + shift + i but nothing happens.
This only affects the Desktop app, web app works fine.
I deleted the config file, but issue still persists.
Not sure about this. I have included my OS & kernel version, just in-case. Only thing I can think of is trying this out in a VirtualBox.

I'm also getting a blank screen on my Linux desktop app after the upgrade from 2.1.5 to 3.0.2
I deleted the .config/SurrealDB/Surrealist folder and reinstalled the .deb so I could at least see the startup screen. I'm able to bring up Developer tools here. No errors at this point.
Create Connection As soon as I try to create a ws or http connection to my localhost, the screen goes blank and the Developer tools no longer display so I can't see any errors. I'm using the same connection on my command line and that works fine.
Open the Sandbox is also blank screen.
No errors in surrealist.log.

I use WSL2
cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.5 LTS"
What I did before it happened
I ran the following query in Surrealist:
update register:xxxxxxxxx set attention +=<EMAIL_ADDRESS>What I did after it happened

sudo dpkg -r surrealist  -> I downloaded ver2.1.6  -> blank screen
sudo dpkg -r surrealist  ->  I deleted the .config/SurrealDB/Surrealist  ->  I downloaded ver2.1.6  -> blank screen
sudo dpkg --purge surrealist -> sudo apt-get autoremove  ->
I deleted the .config/SurrealDB/Surrealist  and  .cache/SurrealDB/Surrealist.  -> I downloaded ver2.1.6  -> blank screen

What  I noticed
Shortcuts not working properly after re-downloading the Surrealist_2.1.6_amd64.deb
now
appimage 2.1.6 works fine

@macjuul

what
ver

Linux Mint
22

Cinnamon
6.2.9

Ubuntu
23.04

Kernel
6.8.0-45-generic

Please try opening the developer tools panel, for which an explanation can be found here. This may lead to further details as to what causes this issue, especially within the Console tab.

nothing is happening

Does this only affects the desktop app or also the web app? Is this consistent across different browsers?

only desktop versions. all PWA and Web solutions work fine.

Does backing up and deleting the config file ($HOME/.config/SurrealDB/Surrealist/config.json) solve the issue?

nope

Is there a reproducible way to trigger the blank screen?

Try fresh install on Linux Mint 22 Cinnamon

On Surrealist 3.0.3, the most recent version, this issue still exists. I have tried both the *.deb & AppImage, same!
I'm running GNOME 46 on Ubuntu 24.04.1 LTS.
Issue:
Upon opening the app, the screen becomes completely blank or stops working.

I have the same problem on Fedora 40 with GNOME 46. With both AppImage and rpm, the whole Surrealist interface gets very slow, or shows a blank screen.

Same issue on Linux mint with any version past 3.0.0. To put salt in the wound, rolling back to older releases stopped working after I opened the new version once. The versions that worked before now do not work even after clearing cache and reinstall (I did not update the OS in the meantime).
Related: https://github.com/surrealdb/surrealist/issues/492, but then I got stuck here too.

If some people here can't get it to work with different versions try AppImage "Surrealist 3.0.0", it works for me right now as a workaround. I'm on Ubuntu 24.04.1 LTS , Gnome 46. It works both on X11 and Wayland.

I can confirm that the only 3.x version that works for me is beta1. Whatever broke happened between beta1 and beta2.
Linux Mint 22, RTX on board (I saw somewhere that this might be a factor)

I can confirm that the only 3.x version that works for me is beta1. Whatever broke happened between beta1 and beta2.
Linux Mint 22, RTX on board (I saw somewhere that this might be a factor)

Might be worth noting i'm on RTX 2080 aswell, and if relevant AMD Ryzen 7 7700X

I confirm that beta1 also works for me (AppImage on Fedora 40).

https://github.com/surrealdb/surrealist/issues/276

I have been able to reproduce this error down to version 2.1.0 (I guess that's the first version that updated to webkit2gtk-4.1?)

The developer tools go blank as well.
Only tried the desktop app.
Deleting the config.json information on queries and queryHistory lets me go back to using the app.
Don't know how to reproduce it, but this happened from scratch on an Ubuntu 24.04 fresh install that "inherited" a working config.json from Surrealist 2.0.6

Platform: Desktop
OS: linux
Architecture: x86_64
WebView: Mozilla/5.0 (X11; Ubuntu; Linux x86_64) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.0 Safari/605.1.15
Version: 2.1.0
Flags: featureFlags: false, models_view: true, apidocs_view: true, themes: false, newsfeed: true, database_version_check: true

Hello everyone! I know this has been a frustrating problem for all of you, and while I do not bring a solution yet, I do have some findings to report.
After extensive testing on Windows through WSL 2 Running Ubuntu 22 I have been able to successfully reproduce the crash. I was able to narrow down the cause of this issue to the WebAssembly used by Surrealist, which includes the surrealdb runtime (@surrealdb/wasm) and the SurrealQL support package (@surrealdb/ql-wasm).
Executing this WebAssembly code causes the browser process used by Surrealist (webkit2gtk) to freeze and crash entirely. This is caused by a recent issue in webkit2gtk-4.1 which made it to the live package. Unfortunately at this time it does not appear a solution is available yet.
I hope this gives some context and perspective on the issue at hand, and while we cannot solve it at this time as it is technically caused by an issue external to Surrealist, I will continue to closely monitor and report back on any updates.
Thank you all for your patience!

I found it always visit https://api.cloud.surrealdb.com, and I don't know whether it helps.

"New Connection", fill "localhost:8000"
After Click "Create", it's blocked and soon become blank white.

tail $HOME/.config/SurrealDB/Surrealist/logs/surrealist.log:
2024-10-14 03:45:52 [INFO] Fetching requested resources
2024-10-14 03:45:52 [INFO] Updater: Checking for updates
2024-10-14 03:45:52 [TRACE] checkout waiting for idle connection: ("https", surrealist.app)
2024-10-14 03:45:52 [DEBUG] starting new connection: https://surrealist.app/
2024-10-14 03:45:52 [TRACE] Http::connect; scheme=Some("https"), host=Some("surrealist.app"), port=None
2024-10-14 03:45:52 [DEBUG] resolving host="surrealist.app"
2024-10-14 03:45:52 [DEBUG] connecting to <IP_ADDRESS>:443
2024-10-14 03:45:52 [DEBUG] connected to <IP_ADDRESS>:443
2024-10-14 03:45:52 [TRACE] checkout waiting for idle connection: ("https", api.cloud.surrealdb.com)
2024-10-14 03:45:52 [DEBUG] starting new connection: https://api.cloud.surrealdb.com/
2024-10-14 03:45:52 [TRACE] Http::connect; scheme=Some("https"), host=Some("api.cloud.surrealdb.com"), port=None
2024-10-14 03:45:52 [DEBUG] resolving host="api.cloud.surrealdb.com"
2024-10-14 03:45:52 [DEBUG] connecting to <IP_ADDRESS>:443
2024-10-14 03:45:52 [TRACE] http1 handshake complete, spawning background dispatcher task
2024-10-14 03:45:52 [TRACE] checkout dropped for ("https", surrealist.app)
2024-10-14 03:45:52 [DEBUG] connected to <IP_ADDRESS>:443
2024-10-14 03:45:53 [TRACE] http1 handshake complete, spawning background dispatcher task
2024-10-14 03:45:53 [TRACE] checkout dropped for ("https", api.cloud.surrealdb.com)
2024-10-14 03:45:53 [TRACE] put; add idle connection for ("https", surrealist.app)
2024-10-14 03:45:53 [DEBUG] pooling idle connection for ("https", surrealist.app)
2024-10-14 03:45:53 [INFO] Updater: No updates available
2024-10-14 03:45:53 [TRACE] put; add idle connection for ("https", api.cloud.surrealdb.com)
2024-10-14 03:45:53 [DEBUG] pooling idle connection for ("https", api.cloud.surrealdb.com)
2024-10-14 03:45:53 [INFO] Cloud: Refreshing cloud access token
2024-10-14 03:45:53 [INFO] Cloud: Invalidating active session     <<<--- The Last Line

use ubuntu22.04 on WSL2
use Surrealist_2.1.6_amd64.AppImage
There was a notification in the bottom left of the Surrrealist app notifying me of an update to 3.0.8version, so I cautiously ran it and it became balnk.
Now I can't use the AppImage or deb files.
Can someone tell me how to delete all related files and start over from scratch after the app crashes?
I delete Surrealist/config.json and run it again, this just opens.↓

I confirm that this problem don't exists in version Surrealist_3.0.0-beta.1_amd64.appimage on NixOS
all versions above this will freeze on startup
something happens from Surrealist_3.0.0-beta.1_amd64.appimage to Surrealist_3.0.0-beta.2_amd64.appimage

use ubuntu22.04 on WSL2 use Surrealist_2.1.6_amd64.AppImage
There was a notification in the bottom left of the Surrrealist app notifying me of an update to 3.0.8version, so I cautiously ran it and it became balnk. Now I can't use the AppImage or deb files.
Can someone tell me how to delete all related files and start over from scratch after the app crashes? I delete Surrealist/config.json and run it again, this just opens.↓

Have you tried to download the working AppImage again? And then use the newly downloaded AppImage onward (or until Surrealist implements a fix)

This is the same problem over and over again, and it is unlikely that anyone will be able to solve it because: https://github.com/surrealdb/surrealist/issues/424#issuecomment-2407484597

Surrealist seems to be working as expected now, after I installed an update in the libwebkit2gtk-4.1-0 library for Ubuntu 24.04.
Can somebody else confirm if sudo apt update && sudo apt upgrade fixed this error for them?

Surrealist seems to be working as expected now, after I installed an update in the libwebkit2gtk-4.1-0 library for Ubuntu 24.04.
Can somebody else confirm if sudo apt update && sudo apt upgrade fixed this error for them?

Seems like it works for me aswell (after i update and upgrade), will do more testing of it tomorrow, but if i don't edit this comment by tomorrow it works again

I confirm that updating the libwebkit2gtk-4.1-0 package solved my problems on Linux Mint 22 (6.8.0). I installed the latest version of the application from the file Surrealist_3.0.8_amd64.deb and it works without problems.
🥳

After testing myself I can indeed confirm the latest version of libwebkit2gtk is working and Surrealist is once again compatible. 🎉
For those looking to resolve this issue, simply upgrade your packages and the current installed version of Surrealist should work again.
sudo apt update && sudo apt upgrade


feat: allow passing access key/region to connect

This PR modifies connect to allow users to pass access keys and region directly to the Boto client, instead of reading credentials from standard locations:
aws_access_id = "XXX"
aws_secret_access_key = "YYY"
aurora_cluster_arn = "WWW"
secret_arn = "ZZZ"
region_name = "us-east-2"

engine = create_engine(
    f"postgresql+auroradataapi://{aws_access_id}:{aws_secret_access_key}@/postgres",
    echo=True,
    connect_args=dict(aurora_cluster_arn=cluster_arn, secret_arn=secret_arn, region_name=region_name),
)

This is similar to how PyAthena builds the SQLAlchemy URI.

Thank you for your PR. The preferred way to pass credentials and region information to the client is via environment variables or other AWS Python configuration conventions. Long-lived API credentials are not recommended if your client is running on an AWS-hosted virtual machine. Since this pattern does not allow passing of role or session token credentials, I am not inclined to accommodate it in aurora-data-api. Do you have a specific reason why your application can't use environment variables or built-in role credential fetching?

I am going to close this PR for now. If you have a use case in mind that addresses the question above, please feel free to describe it and we will reconsider.

My company runs (Apache Superset)[https://github.com/apache/superset/] in a multi-tenant setup, so we can't read the credentials from the environment. Each user needs to input their credentials manually when defining a DB connection.


ISS-28 # Local assertion checker util -More flavours

E2e renamed to SpringBoot runner

@respondsid , can you accept  this invitation please?
https://github.com/authorjapps/spring-boot-integration-test/invitations
This takes care of
https://github.com/authorjapps/zerocode/issues/228

Tool or Runner for locally validating assertion vs actual response #228


Create a deploymentMangement goal to deploy the jar files to the remote repsitory

We need a goal to deploy the jar files to the remote dataone repository.

The distributionManagement and profiles parts were added to the pom.xml file. The users can choose the local or remote maven repositories to deploy the jar files.


Use container's RAM limit set by deploy resources limit

Describe the bug
I was having an issue of suddenly crashing meilisearch. I was using the same data sets on another server (2GiB RAM, EC2) there it had no container resource limitation, but on this new server (32 GiB Bare Metal) I deployed meilisearch with resources limitation of '8 GiB RAM Limit'.
To Reproduce

Deploy Meilisearch in a Docker Swarm Environment with Resources Limit (Memory Limit).

    deploy:
      resources:
        limits:
          memory: 8G # 1/4  of the available RAM Host

docker exec -it {containerId} sh
meilisearch --help
It'll show the default meilisearch was going to use for max available, as you can see my case it defaulted to 20 GiB but I've resources limit of 8 GiB Memory.

Expected behavior
It should detect the maximum available memory set by the container and then automatically 2/3 of the memory from the limit instead of the host's total memory.
Workaround
As a workaround I had to redeploy meilisearch with MEILI_MAX_INDEXING_MEMORY: '6 GiB' environment configuration to consider the container's RAM Limit.
Meilisearch version:
v1.8.1 (docker)
Additional context
Architecture: x64
Docker Version: 26.1.3
Docker Mode: Swarm
Server: Bare Metal 6 cores 12 threads / 32 GiB RAM. 512 NVMe Storage.

An open issue regarding this in the sysinfo repo: https://github.com/GuillaumeGomez/sysinfo/issues/207

Hello @iamriajul
Thanks for the report. This is indeed an issue we know
For example when using K8s, by default Meilisearch uses

the RAM of the node
the CPU of the pod

The workaround is indeed to set your limit manually.

@curquiza

The workaround is indeed to set your limit manually.

I was going to report an issue, but I found this comment so I'm asking it here instead: we're trying out Meilisearch in our K8S cluster, and found that it kept on increasing memory usage over time. Up to the point it gets restarted by K8S. We've set the MEILI_MAX_INDEXING_MEMORY environment variable to 1300Mb (the memory resources are set to 1000Mi/1.95Gi), but it still shows a sawtooth graph:

The --help output shows that it's picking up the variable at least:
      --max-indexing-memory <MAX_INDEXING_MEMORY>
          Sets the maximum amount of RAM Meilisearch can use when indexing. By default, Meilisearch uses no more than two thirds of available memory

          [env: MEILI_MAX_INDEXING_MEMORY=1300Mb]
          [default: "10.42 GiB"]

I would have expected the line to drop — or at least stabilise — around the 1.4G mark. Is this not working correctly, or are we doing something wrong here?

@pkruithof which version of Meilisearch? There's a memory leak issue with 1.8 and up. So I'm using 1.7.6 now instead.

Hey @pkruithof 👋
@iamriajul is right there is a leak in v1.8.0 and v1.8.1. We are investigating in this Discord channel and on this GitHub issue. At this point we think we have found the root cause and are deploying a fix soon.
Sorry for the inconvenience 😞

v1.8.3 with the fix has been released @iamriajul


Provide AWS{3,4}Signer that takes a HttpRequestMessage

Or is there some example of how to convert a HttpRequestMessage to an IRequest that the current AWS4Signer uses.
We're calling api-gateway using IAM authorization which requires the execute-api service, and that requires the AWS4Signature that uses HMAC-256. It would be really nice to have some maintained utility that enables one to sign a generic HttpRequestMessage.
I've copied this gist for now, but I am seeing some discrepancies between what is in the aws-sdk-net AWS4Signer.
Is there a better way than the one I am using?

We don't have a better approach now but making a signing code more accessible is something we want to do for these API Gateway cases.

Aye, that sounds good. I'm merging what is in the aws4signer and the gist
for now (since it is missing some steps), let me know if you want to look
at it. The signer will take only a HttpRequstMessage and add the Authorize
headers as your signer does.
On fre. 24. jun. 2016 at 18.12, Norm Johanson<EMAIL_ADDRESS>wrote:

We don't have a better approach now but making a signing code more
accessible is something we want to do for these API Gateway cases.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-net/issues/397#issuecomment-228389000,
or mute the thread
https://github.com/notifications/unsubscribe/AAaEQlo_pieUqMZNvdzK1Pyq48OWjN1Qks5qPAHdgaJpZM4I9jhD
.

This has been added to our feature request list: https://github.com/aws/aws-sdk-net/blob/master/FEATURE_REQUESTS.md

I'm using AWS Elastic Search Service and requests need to be signed.
There is a nuget package which has to implement the signing code but there's bugs in that library.
For example if you try to enable gzip compression it doesn't work and you get the error:
The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.
https://github.com/bcuff/elasticsearch-net-aws
Is gzip compression compatible with v4 signing?

Any update on when signer would be available as a utility in sdk?

Just leaving a +1 for having public API for signing HttpClient requests (or anything really) and not having to use internal namespaces for it.

Having the ability to sign requests for AWS services should be considered a high priority for a production AWS SDK!
We just ran into a big roadblock here because I decided to use signed API GATEWAY for a project and one of our backend systems is in .NET and well, oof :/

The SDK not enabling authenticating IAM against API Gateways is currently being a blocker.


[Bug]: DateRangePicker Calendar not changing month for locales

Tremor Version
3.6.1
Link to minimal reproduction
https://stackblitz.com/edit/stackblitz-starters-2xymze?file=pages%2FDatePickerDemo.js
Steps to reproduce
import * as React from 'react';
import { DateRangePicker, DateRangePickerItem } from '@tremor/react';
import { useState } from 'react';
import { enUS, es } from 'date-fns/locale';

const DatePickerDemo = () => {
  const [value, setValue] = useState({
    from: new Date(2023, 1, 1),
    to: new Date(),
  });

  const [locale, setLocale] = useState('es');

  return (

        Current Locale: {locale}
        <button
          onClick={() => setLocale((prev) => (prev === 'enUS' ? 'es' : 'enUS'))}
          className="bg-blue-400 px-1 rounded ml-2 mt-2 hover:bg-blue-300"
        >
          Toggle Locale
        </button>

        <DateRangePicker
          className="mx-auto max-w-md"
          value={value}
          onValueChange={setValue}
          locale={locale === 'enUS' ? enUS : es}
          color="rose"
          enableSelect={false}
        ></DateRangePicker>

  );
};

export default DatePickerDemo;

What is expected?
When the locale is set to locales other than en, for example: es, the datePicker should show month in locale of es. For example, August should be Agosto.
What is actually happening?
The month remains to be in enUS locale.

What browsers are you seeing the problem on?
Chrome
Any additional comments?
No response

It's an easy to solve bug. I would like to be assigned and fix it quickly.

Hi @jzfrank, thanks for this and helping. I just tagged you.


Can't access gofrp.org

Can't access gofrp.org website in the US network environment and it used to be accessible.

Found possibly similar open issue at [https://github.com/fatedier/frp/issues/3083](FRP repo).

Thanks. Already recoverd.


Switch to next pricing A/B test.

@sderickson code reviewed this before this p/r existed and said it looked good : )


Revisit the transpiler module pages for Runtime API docs

The module pages aren't particularly useful.
https://docs.quantum.ibm.com/api/qiskit-ibm-runtime/transpiler:

https://docs.quantum.ibm.com/api/qiskit-ibm-runtime/qiskit_ibm_runtime.transpiler.passes

https://docs.quantum.ibm.com/api/qiskit-ibm-runtime/qiskit_ibm_runtime.transpiler.passes.basis:

https://docs.quantum.ibm.com/api/qiskit-ibm-runtime/qiskit_ibm_runtime.transpiler.passes.scheduling is really useful though.

What's the solution? To add more information to the docstrings? I wonder if the reason scheduling had so much information is because it's not covered in the rest of the docs, whereas the transpiler is.

Or consider if we should remove any of the pages. In particular, I don't understand why https://docs.quantum.ibm.com/api/qiskit-ibm-runtime/qiskit_ibm_runtime.transpiler.passes.basis is documented


discrepancies between (HRV) zarr files on gcp and downloaded satellite data

Describe the bug
Apparently, I came across a discrepancy between the public (HRV) dataset on gcp and data directly downloaded from EUMETSAT api.
To Reproduce
Steps to reproduce the behavior:

Connect to public satellite data by:

gcs = gcsfs.GCSFileSystem()
zstore = 'gs://public-datasets-eumetsat-solar-forecasting/satellite/EUMETSAT/SEVIRI_RSS/v4/2020_hrv.zarr'
mapper = gcs.get_mapper(zstore)
ds = xr.open_zarr(mapper, consolidated=True)
and plot the data with coastlines:
projection = {     'proj': 'geos',      'lon_0': 9.5,      'h': 35785831,      'x_0': 0,      'y_0': 0,      'a': 6378169,      'rf':<PHONE_NUMBER>97014 }
fig = plt.figure(figsize=(20, 20))
crs = ccrs.Geostationary(     central_longitude=projection['lon_0'],      satellite_height=projection['h'],  )
ax = plt.axes(projection=crs)
ax.coastlines(resolution='10m', alpha=0.5, color='blue')
ds['data'].sel(time=np.datetime64('2020-07-02T07:00:00'), variable='HRV').plot(     ax=ax,      cmap='gray',      add_colorbar=False )
clearly shows that the coastlines are offset with the satelliet observation data (have a look at Libya).
On the other hand, after downloading with the same data with eumdac cli (eumdac download -c EO:EUM:DAT:MSG:MSG15-RSS --start 2020-07-02T06:45 --end 2020-07-02T07:15) and combining the *.NAT files with the methods in scripts/extend_gcp_zarr.py (temporary link here) removes the discrepancy between coastline and satellite observation.
Hence, it appears something is incorrect about the satellite data in the public gc-bucket.
I am guessing here, but could it be that this is because the public zarr file lumps all information over 1 year together with moving spatial dimensions - during the year - of the observations? If this is the case, the data should be temporally divided over move zarr files.
Best regards,
Tomas

Hi,
Sorry about the delayed response, this slipped through the cracks! But yes, there are some issues with the public GCP data because it takes the coordinate information of the first timestep of the year, and applies it to the whole year. Theoretically, the datasets of x_geostationary_coordinates and y_geostationary_coordinates should have the per-timestep coordinates, but the processing seems to have not worked, so they don't actually contain that data.
I will try to fix that processing so that the newer zarrs can have that fixed, although it might take quite a while. Primarily, we need to

[ ] Get the x and y geostationary coordinates for all timesteps in the dataset (per year working backwards seems to make the most sense)
[ ] Replace the current ``x_geostationary_coordinatesandy_geostationary_coordinates` with the actual values

That should allow the images to be shifted to the correct locations for plotting and the like. Sorry for the issue with that data.


A Small Typo Lecture Note 2 #40

Thank you very much for sharing your course material!
I just saw a typo in the first line of page 40 when I was reading lecture note 2. There are two "and" instead of one. This is not misleading anyway. But you probably can change it very easily and quickly.

Thanks!


dynamic tree-sitter grammar import

Is this even possible?
Maybe we can pull the grammar from Github, compile it, and load it as a .so/.dll?
Maybe if tree-sitter-node works again we can import a remote library (grammar) at runtime and use that?

NeoVim has a TreeSitter installer, maybe we can copy it?

Maybe this function?


Add "python3" to possible names for the python binary

Followed lang/python/config.el which already checks for python3
when setting the python-shell-interpreter.
Python version naming is a hot mess:
https://www.python.org/dev/peps/pep-0394/

Looks good to me, thanks!


clean clone in IntelliJ - compile errors

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
If a new intelliJ project is created 'from existing sources', with an empty ~/.m2, the following errors appear in the UI:

This does not occur when cloning at the command line
If the user navigates to the gradle tool window, clicks the 'play' button to execute a gradle task, and enter's 'build' (for 'gradle build') then compile works normally.
It appears intelliJ is executing some task, which is failing, immediately after the clone
cc: @mandy
Expected Behavior
no errors occur after cloning a new project in intelliJ
Steps To Reproduce
as above
Environment
- Egeria:3.11-SNAPSHOT
- OS: macOS
- Java: 18
- Browser (for UI issues):
- Additional connectors and integration:

Any Further Information?
No response

Gradle appears to launch this task during setup:
> Task :prepareKotlinBuildScriptModel UP-TO-DATE
Could not resolve: commons-logging:commons-logging:1.2
Could not resolve: org.slf4j:jcl-over-slf4j:2.0.0

Both of these dependencies ARE present on maven central.
A clean clone/empty m2 running the same task at cli is clean.
I've opened up an IntelliJ issue to understand what intelliJ is doing, and how to resolve -> https://youtrack.jetbrains.com/issue/IDEA-301612/Importing-a-gradle-project-into-intelliJ-gives-errors-after-prepareKotlinBuildScriptModel-CLI-is-clean

will check for gradle only

this still occurs with Build #IU-223.7571.182, built on November 29, 2022

Have looked into this further.
There are more errors reported, such as the use of deprecated features. Our full build is clean from deprecations.
By ensuring we fail the build on any deprecated usage, the intelliJ import now additionally reports warnings such as
Resolution of the configuration :open-metadata-distribution:classpath was attempted from a context different than the project context. Have a look at the documentation to understand why this is a problem and how it can be resolved. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. See https://docs.gradle.org/7.6/userguide/viewing_debugging_dependencies.html#sub:resolving-unsafe-configuration-resolution-errors for more details.

Many times
Switching off ' org.gradle.configureondemand' did not help either.
My conclusion is that IntellIiJ is at fault, and we cannot do anything about this except document
Once imported, gradle works normally - ie by running a build from the gradle plugin
Moving to docs repo


Attatchment referenced in description causes errors

Describe the problem
The field System.Description is placed always in revision index 0 with the latest content from jira.
If an attatchment image is referenced in the 'System.Description' field, the image may not be available when importing rev 0.
The image may not be available at this time, because it is added later.
This is caused, because the export writes the latest description content at revision index 0
This causes failures during the import, because wi-import can't save the rev 0 correctly.
To Reproduce
Steps to reproduce the behavior:

place PRD-1847.json file in a folder called PRO

{
  "Type":  "Task",
  "OriginId":  "PRO-1847",
  "WiId":  -1,
  "Revisions":  [
    {
      "Author"<EMAIL_ADDRESS>      "Time":  "2020-07-08T10:22:59+02:00",
      "Index":  0,
      "Fields":  [
        {
          "ReferenceName":  "System.Title",
          "Value":  "[PRO-1847] Review Test Sets"
        },
        {
          "ReferenceName":  "Microsoft.VSTS.Common.Priority",
          "Value":  ""
        },
        {
          "ReferenceName":  "Microsoft.VSTS.Common.ClosedDate",
          "Value":  "2020-07-21T11:51:27"
        },
        {
          "ReferenceName":  "System.Description",
          "Value":  "<img src=\"https://jira.domain.de/secure/attachment/39350/39350_image-2020-07-14-15-38-48-581.png\" style=\"border: 0px solid black\"/><"
        },
        {
          "ReferenceName":  "System.State",
          "Value":  "To Do"
        }
      ],
      "Links":  [
        {
          "Change":  0,
          "TargetOriginId":  "PRO-590",
          "TargetWiId":  0,
          "WiType":  "System.LinkTypes.Hierarchy-Reverse"
        }
      ],
      "Attachments":  [
        {
          "Change":  0,
          "FileName":  "image-2020-07-08-10-20-01-372.png",
          "Comment":  "Imported from Jira",
          "AttOriginId":  "39067",
          "FilePath":  ".\\PRO\\Attachments\\39067\\image-2020-07-08-10-20-01-372.png"
        }
      ],
      "DevelopmentLink":  null,
      "AttachmentReferences":  true
    },
    {
      "Author"<EMAIL_ADDRESS>      "Time": "2020-07-14T15:38:49+02:00",
      "Index": 1,
      "Fields": [
      ],
      "Links": [
      ],
      "Attachments": [
        {
          "Change": 0,
          "FileName": "image-2020-07-14-15-38-48-581.png",
          "Comment": "Imported from Jira",
          "AttOriginId": "39350",
          "FilePath": ".\\PRO\\Attachments\\39350\\image-2020-07-14-15-38-48-581.png"
        }
      ],
      "DevelopmentLink": null,
      "AttachmentReferences": true
    }
  ]
}

place a image with this name .\PRO\Attachments\39350\image-2020-07-14-15-38-48-581.png

start wi-import.exe

Go to Azure Devops, and see that 3 workitems have been created:

Tool version

Version of the jira-azuredevops-migrator tool  3.0.502

Attachments
Please attach the following files:

wi-import-log.txt
wi-import-log-241220-142509.txt

Screenshots

Duplicate of https://github.com/solidify/jira-azuredevops-migrator/issues/602


New Architecture: Failed to trigger c++ turbo module codegen for android build

Description
I'm following the c++ turbo module setup which is documented here. I'm using expo SDK and I've already pre-build it and get the NativeSampleModule sample running which works pretty smoothly. The Question is when I tried to rename the NativeSampleModule.ts into something else (e.g. FooBar.ts and delete the build cache. The codegen failed instantly with build process complaining there's no template called NativeSampleCxxSpec. I've checked the generated files (android/app/build/generated/source/codegen/jni/Appspec.h) and the original spec template is missing.  My question is how this codegen is performed and how the cxx spec template is generated? I believe this can help uncovering some of toolchain puzzles here.
React Native Version
0.72.4
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: Linux 6.1 Gentoo Linux
CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
Memory: 50.11 GB / 62.66 GB
Shell:
version: 5.1.16
path: /bin/bash
Binaries:
Node:
version: 20.5.1
path: /tmp/yarn--1693289599125-0.5205430889365983/node
Yarn:
version: 1.22.19
path: /tmp/yarn--1693289599125-0.5205430889365983/yarn
npm:
version: 9.8.0
path: /usr/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: AI-231.9011.34.2311.10366083
Languages:
Java:
version: 17.0.6
path: /usr/bin/javac
Ruby:
version: 3.1.4
path: /usr/bin/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.72.4
wanted: 0.72.4
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: true
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Done in 1.52s.
Steps to reproduce

Reproducing the original NativeSampleModule exmaple.
Rename tm/NativeSampleModule.ts into tm/foobar.ts
Run yarn android
Failed.

Snack, code example, screenshot, or link to a repository
I believe this is a toolchain issue and not related to the main javascript part. Therefore, no snack is provided here.

It seems only certain files beginning with Native will be selected?

It seems only certain files beginning with Native will be selected?

That's correct, the codegen picks only files that are called Native* when looking for TurboModule specs

It seems only certain files beginning with Native will be selected?

That's correct, the codegen picks only files that are called Native* when looking for TurboModule specs

Somehow, I missed that part


Socket.io server, notifications and bug fixes

Coverage decreased (-1.7%) to 41.459% when pulling b58c646bddecd67aea36cc0f9496f8ed65038c10 on logout into 1b0a402eedae3f71057025d50c6a22be7c7022a8 on master.


Allow the XMPP bridge to use slack compatible webhooks

This PR tries to work on #1082 by giving the user the possibility to set a webhook for the XMPP bridge to allow user name spoofing.
This requires a prosody server with mod_slack_webhooks installed.
To add a webhook, just add the WebhookURL option to your XMPP section
[...]
[xmpp]
        [xmpp.test]
        [...]
        RemoteNickFormat="{NICK}"
        WebhookURL="https://some.server/msg/abc123"
[...]

This would POST a message to https://some.server/msg/abc123/<channel> when a message is received in the channel <channel>. Setting a webhook disables sending messages via the connected XMPP account on all channels that this account mirrors.
As mentioned in #1082 , using mod_rest may be the better solution, but it would currently require running prosody trunk or the yet unreleased version 0.12, so I settled on mod_slack_webhook.

Thanks!

Thanks!