No down notifications for push monitor

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
I have a push monitor configured for a 1min interval. It appears that since upgrading, it no longer sends notification for missed heartbeats:

You'll notice that between 8:14 and 8:21 there were no pings, but no down notifications were sent either.
I wonder if it has something to do with the failed SMTP notifications shown in the logs below, but I have the same issue on all my monitors and those send the gotify notifications just fine
👟 Reproduction steps
Configure a push monitor as below:

Ping the URL every minute for a while
Stop pinging the URL
👀 Expected behavior
Get a down notification
😓 Actual Behavior
Only get up notifications
🐻 Uptime-Kuma Version
1.10.2
💻 Operating System and Arch
Docker on Ubuntu 20.04
🌐 Browser
Firefox
🐋 Docker Version
20.10.10, build b485636
🟩 NodeJS Version
No response
📝 Relevant log output
onitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP
Monitor #21 'Backups': Failing: No heartbeat in the time window | Interval: 60 seconds | Type: push
Cannot send notification to SMTP

I got probably another issue, also with this kind of sensors, so it can be related somehow: My push notification is keep in Pending state (I expect Failed state after one pending), although there are no signals in set interval. No notification is being sent.
Monitor #27 'Home - AP2': Pending: No heartbeat in the time window | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: push
…
…
Monitor #27 'Home - AP2': Pending: No heartbeat in the time window | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: push

In my case, it seems it's still Retry: 1 - I'm not sure, but it looks like it isn't counting retries.

Usually your smtp block the down mail for unknown reason.
Search this repo for more info. I remember someone had same problem with you.

@louislam the problem is that i don't get a down notification to gotify either
smtp doesnt work for any other monitor either, but i get the gotify notifications for those
only the push monitor doesnt work

Just test it again, I still cannot reproduce your problem. Not quite sure what is missing here.

Not sure what the issue was before, but restarting the container seems to have fixed it. Closing for now...

@louislam there definitely seems to be some kind of issue with the push monitor logic that allows it to get into a bad state. It went down, then came back up, and now its spamming me with Up notifications every time it gets a ping...
I'm calling the url: api/push/7oxXeSwthj?msg=OK&ping=$PING

Also not sure why there are gaps in the graph...

Gaps are either a pending beat or a single up beat that is not connected as a line. I think this suggests that somehow more than 1 beat is produced every minute, which would be consistent with your observation that notification is constantly getting triggered, which would happen on every down-to-up transition.

Is there a way to log the raw http requests so I can see exactly what's coming through? The cron job is set to ping every minute...

I seem to be having this issue as well. I setup a new PUSH monitor and before i triggered my first GET to the URL i did get a down alert, triggered my GET to the URL and got an up alert then I didn't trigger another GET to the URL and haven't received an alert but can see in the WebUI that its down but the history doesn't call it out.

Finally addressed the issue, it should be fixed in the next release

This might still be broken, I am no longer receiving down alerts if I intentionally stop the job hitting the URL. The monitor still says up.

I'm using matrix for the notifications and only receive the UP notifications, no DOWN. Using version 1.11.1 in docker.

I'm not sure if we should crate a new issue or if @louislam can reopen this one?

I'm using matrix for the notifications and only receive the UP notifications, no DOWN. Using version 1.11.1 in docker.

this is fixed in 1.11.3! Thanks!

I'm using matrix for the notifications and only receive the UP notifications, no DOWN. Using version 1.11.1 in docker.

this is fixed in 1.11.3! Thanks!

It should not be related, the logic is the same as 1.11.1.

I'm not sure if we should crate a new issue or if @louislam can reopen this one?

I remember that I tested it a month ago, it should be working, but it could possibly be another hidden issue.
If you find a way to reproduce the issue, feel free to open a new issue.

Something really bad is still happening. Note that its going down and up within the same second...
I just updated to the latest version again I'll report back if I still see the problem.

@louislam fyi - still a problem as of  1.11.3. Going to try 1.12.1

I think maybe there is a hidden issue. Let me know if anyone know how to reproduce.

Try this @louislam - configure monitor, restart Uptime Kuma (might not be required), cause a failure and it will alert, bring service back up and it will go green. after that it will not detect future failures. Seems is always works on first failure after a restart of Uptime Kuma but after that first failure no more alerts.

@louislam I think you might have a race condition. Or maybe a conditional that's not mutually exclusive.
If the ping happens exactly 60s after the last one, it causes both an Up and a Down. Interestingly, the other ones are technically correct because the ping comes 61s later.
Can you add a grace period? So if I set it to 60s, it will actually wait for 60s+1s, for example? (I know I can just set the checking to 60s, but its confusing because I have a cronjob set to run it every minute, and its just because the times aren't perfectly in sync + latency)
Here is my dashboard:

And here are my http logs:
[25/Mar/2022:17:54:05 -0700]  "GET /api/push/xxxx?msg=OK&ping=92.177 HTTP/1.1" "-" "curl/7.74.0" TLSv1.3 TLS_AES_256_GCM_SHA384 200 5567
[25/Mar/2022:17:55:05 -0700] 9 "GET /api/push/xxxx?msg=OK&ping=92.196 HTTP/1.1" "-" "curl/7.74.0" TLSv1.3 TLS_AES_256_GCM_SHA384 200 5567

[25/Mar/2022:17:58:05 -0700] "GET /api/push/xxx?msg=OK&ping=90.552 HTTP/1.1" "-" "curl/7.74.0" TLSv1.3 TLS_AES_256_GCM_SHA384 200 5567
[25/Mar/2022:17:59:06 -0700]  "GET /api/push/xxx?msg=OK&ping=91.308 HTTP/1.1" "-" "curl/7.74.0" TLSv1.3 TLS_AES_256_GCM_SHA384 200 5567

Yeah I was right. There is a race condition! You have the monitor running on a setTimeout that is totally independent of the call of the push URL. That means that beat() and router.get("/api/push/:pushToken") can both get called at the same time in seconds (e.g. both at 17:15:02), but if beat() happens first, it will mark the monitor as down, then it will immediately mark it as up when router.get() is run.
https://github.com/louislam/uptime-kuma/blob/12237dec6e3809404a1c84df394b232431b0f5f0/server/model/monitor.js#L309-L329
https://github.com/louislam/uptime-kuma/blob/12237dec6e3809404a1c84df394b232431b0f5f0/server/model/monitor.js#L468-L475
https://github.com/louislam/uptime-kuma/blob/12237dec6e3809404a1c84df394b232431b0f5f0/server/routers/api-router.js#L20-L84
The other issue (I think) is that the call to the push URL does not reset the setTimeout. So if, for example, beat() runs at 16:17:04, it will run again at 16:18:04, no matter what. But if I call the push URL at 16:17:05, I'll probably call it again at 16:18:05, which is 60s later - totally valid! But again, it will get marked as down then up 1s later.
I think the right thing to do, though it may be a little difficult with the way you have the architecture set up, is to do the first setTimeout on monitor.start(), but every other setTimeout should be run from router.get("/api/push:pushToken"). Also, the timeout probably needs to have an extra second, like setTimeout(safebeat, (interval + 1)*1000). That way any push URL call in the entire 1s window of 16:17:04, for example, will keep the monitor "Up".
Let me know if you have any questions!

This is still relevant. My PUSH sensors are only sending DOWN notifications to Discord, and not thé UP. While the status goes back to UP in the chart & the bars, the history does not record the UP state and no notification goes through. This persists after reboot of the application, after deleting all the events/heartbeats of the probe. What’s more is that I don’t feel like the retries / interval works as expected - with 3 retries, 60 in the interval values & pushes sent every 60sec, I get notified as soon as a single push is sent with DOWN - shouldn’t it be after 3?

@scr4tchy this particular issue was definitely fixed. Can you try running v1.17.1 and see if things work as expected? If they do, it's a regression.

docker-compose.yml
version: '3.3'
services:
  status:
    image: louislam/uptime-kuma:1.17.1-alpine
    container_name: status
    restart: unless-stopped
    volumes:
      - ./data/status:/app/data

main.py
import asyncio
import aiohttp
import yaml
from datetime import datetime, timedelta

async def check(check, cfg, session):
    # Check
    t = datetime.now()
    try:
        async with session.get(url=check["url"]) as resp:
            status = "up" if resp.status == 200 else "down"
            msg = str(resp.status)
    except Exception as e:
        status = "down"
        msg = "EXCEPT"
        print("Unable to get url {} due to {}.".format(check["url"], e.__class__))
    dt = (datetime.now() - t).total_seconds()

    # Push
    try:
        await session.get(url="{}/{}?status={}&ping={}&msg=OK".format(cfg["push_url"], check["id"], status, dt))
    except Exception as e:
        print("Unable to push status due to {}".format(e.__class__))

async def main():
    # Load config
    with open("./config.yaml", 'r') as f:
        cfg = yaml.load(f, Loader=yaml.FullLoader)

    # Loop
    while True:
        t_next = datetime.now() + timedelta(seconds=30)

        async with aiohttp.ClientSession(timeout=aiohttp.ClientTimeout(total=10)) as session:
            await asyncio.gather(*[check(c, cfg, session) for c in cfg["checks"]])

        # Wait until next interval.
        print("Sleeping until %s" % t_next)
        await asyncio.sleep((t_next - datetime.now()).total_seconds())

asyncio.run(main())

config.yaml
push_url: https://status.xxx.xx/api/push
checks:
  - id: <id>
    url: http://service:8080

import asyncio
import aiohttp
import yaml
from datetime import datetime, timedelta

async def check(check, cfg, session):
    # Check
    t = datetime.now()
    try:
        async with session.get(url=check["url"]) as resp:
            status = "up" if resp.status == 200 else "down"
            msg = str(resp.status)
    except Exception as e:
        status = "down"
        msg = "EXCEPT"
        print("Unable to get url {} due to {}.".format(check["url"], e.__class__))
    dt = (datetime.now() - t).total_seconds()

    # Push
    try:
        await session.get(url="{}/{}?status={}&ping={}&msg={}".format(cfg["push_url"], check["id"], status, dt, msg))
    except Exception as e:
        print("Unable to push status due to {}".format(e.__class__))

async def main():
    # Load config
    with open("./config.yaml", 'r') as f:
        cfg = yaml.load(f, Loader=yaml.FullLoader)

    # Loop
    while True:
        t_next = datetime.now() + timedelta(seconds=30)

        async with aiohttp.ClientSession(timeout=aiohttp.ClientTimeout(total=10)) as session:
            await asyncio.gather(*[check(c, cfg, session) for c in cfg["checks"]])

        # Wait until next interval.
        print("Sleeping until %s" % t_next)
        await asyncio.sleep((t_next - datetime.now()).total_seconds())

asyncio.run(main())

It might've been due to pushing heartbeats continuously, with status=up,  status=down during downtime and then status=up again as soon as the service went back up. It would send notifications every single time a status=down was received, ignoring the retry configuration, and would never send a notification once up again. Skipping pushes during downtime may be fixing it, as I tested it once and didn't receive duplicated but did receive an up notification.

Yeah this is unrelated to this issue then. I believe the retry only applies if the heartbeat is missed completely. Similarly, it probably sends a notification on every down heartbeat on purpose. But if you can send multiple down heartbeats, I'm not sure why you need uptime-kuma at all...


Unhandled JS Exception: undefined is not an object (evaluating '_reactNativeMediaMeta2.default.get')

I am using your lib for getting thumbnail from local video, I have URI like this "file:///Users/xyz164/Library/Developer/CoreSimulator/Devices/6332F702-2D51-4451-86DD-5CF87EC2FF8E/data/Containers/Data/Application/C9438FBF-4FAA-4120-80EC-28D1568105E9/Documents/trim.AAF142E3-7318-4685-83F3-0E1E63E929A9.MOV"
and pass to your class and getting error ios.
Please help me out.

Do you successfully linked the iOS native module?
react-native link react-native-media-meta

@jhen0409  Yes, I have linked the iOS native module properly.

@vvkaghera have you solved this issue?

Just remove prefix file:// from your path.


plugin failed to load .netstandard2.0 library dll

I am building a program using DotSpatial as frontend, I have the compiled binary runtime version: v4.0.30319 and Version: <IP_ADDRESS>5
The issue is with this plugin I am building that would need to use rdotnet DLL that is built on netstandard2.0, when I put the rdotnet DLL in my plugin's folder, the program (DemoMap) wouldn't launch and gives the following error message, then just quit:
System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types.
I verified by removing that DLL from the output folder, then it will launch. I've compiled my plugin on both 4.5 and 4.7.2 .net framework, same failure. This leads to the question can DotSpatial uses libraries built for netstandard?

Actually can DotSpatial be compiled for netstandard2.0 platform? it seems Microsoft is pushing for things to be on netstandard to be cross platform....

Try to compile DotSpatial on .Net 4.7.x or 4.8 and then include your plugin. I think DotSpatial is compiled against an older version of .Net that can't work with netstandard dlls.

I'll try that, is it feasible to compile DotSpatial on netstandard2.0 platform?

I haven't done anything with .net Standard yet. But I think it can't handle winforms, so you might have trouble compiling all of DotSpatial against .net Standard.

You know what's weird is that my previous application that is on .net framework 3.5 worked fine with this same netstandard library without problem. It appear to be the way DotSpatial is "loading" this library at the launching of the whole program that is failing, I wonder if that loading process can be examined per this issue... anyway, I will try recompile DotSpatial on higher version of .net framework...

I've tried recompiling dotspatial on 4.6.1 and 4.7.2, but both still failed to load that netstandard 2.0 dll. To reproduce the load problem, simply put this dll inside any of the plugins, for example the About plugin folder, then try to run DemoMap and see it fail. Please let me know if you can find a solution.

@jany-tenaj I was able to make the netstandard2.0 DLL work with the current 4.5.2 DotSpatial libraries! What I did was the following: 1) make the plugin itself to be .net 4.7.2 (it apparently can take in 4.5.2 DLLs); 2) trace the dependency of that netstandard2.0 DLL, it needs Dynamicinterop and Microsoft.Win32.Registry DLLs. So once these two were added into the plugin dependencies, it works now. So, I didn't have to compile DotSpatial to a higher .net framework version.


Proposal for Makefile

@NicolaDonelli
Addressed the last comment about --checks flags. If it is fine, just merge it yourself into your branch and squash all commits of your PR. I will approve the PR and then we can merge on main


Changing the plugin icon in the settings results in the icon disappearing

I'm able to reproduce this by changing to an alt icon and when quitting and re-launching Runelite, the icon is empty until you change it back and back again.


why such a lag time to get images into ocellus

today 2023-06-08  I only get images from 2023-05-26. Why such a long time lag, whilst you have a model question to get the images from yesterday?
https://ocellus.info/?page=3&size=30&resource=images&checkinTime=since(06-06-2023)

This is because of a mistake on my part, sorry about that. I will let you know as soon as I have a fix implemented and tested

hi @myrmoteras this is fixed for now although I intend to continue to work on the fix to make it more robust. Just one note… the date format is yyyy-mm-dd, so the following URL that you provided above has the date wrong. I show both, the wrong version first and the correct version after. Hope this helps
// wrong version
https://ocellus.info/?page=1&size=30&resource=images&checkinTime=since(06-06-2023)

// correct version (note, the year comes first, then the month, then the day)
https://ocellus.info/?page=1&size=30&resource=images&checkinTime=since(2023-06-06)


LF-22299: Adding support for Share and Load More button text translation

https://livefyre.atlassian.net/browse/LF-22299
Oh, how I hate passing around opts.
#review

I'm handling this in my translations pull


Modifying models regression

regenerating moscap models regression in model_reg file

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@RehabSayed-G Also, moving forward, could you please only commit one model regression python file at a time?


BUG: SubscribeToPositionUpdatesAsync - incorrect enum

I have an issue with SubscribeToPositionUpdatesAsync():
Wrong URL or channel:positions,instType:0 doesn't exist. Please use the correct URL, channel and parameters referring to API document.

my best guess is that the instrument type enum is invalidly parsed as int rather than as string. In the official documentation, they seem to use the string in all capital for several Operations:
{
    "code": "0",
    "data": [
        {
            "cTime": "1654177169995",
            "ccy": "BTC",
            "closeAvgPx": "29786.5999999789081085",
            "closeTotalPos": "1",
            "instId": "BTC-USD-SWAP",
            "instType": "SWAP",
            "lever": "10.0",
            "mgnMode": "cross",
            "openAvgPx": "29783.8999999995535393",
            "openMaxPos": "1",
            "realizedPnl": "0.001",
            "fee": "-0.0001",
            "fundingFee": "0",
            "liqPenalty": "0",
            "pnl": "0.0011",
            "pnlRatio": "0.000906447858888",
            "posId": "452587086133239818",
            "posSide": "long",
            "direction": "long",
            "triggerPx": "",
            "type": "1",
            "uTime": "1654177174419",
            "uly": "BTC-USD"
        }
    ],
    "msg": ""
}

I have added a temporary workaround in my fork:
https://github.com/forReason/OKX.Api/blob/master/OKX.Api/Common/Enums/OkxInstrumentType.cs
the fork is not how it should be implemented.. It seems you want to use the [Map] attribute for ApiSharp?
Unfortunately, I dont exactly know what the issue is and I would expect the issue to pop up on other ends as well.
I cant judge yet, since the Project is just starting.
For my quick and Dirty solution is a Custom json converter, which converts the Enum Value to upper case and it works.
Thats unfortunately all I can do with my limited knowledge. I love your Project.

I'll fix this issue tonight.

Fixed in v5.4.1025 with ApiSharp Update. Thanks for feedback.


Container Apps seems to be missing appProtocol

Hi All,
I would like to create an application that uses gRPC instead of HTTP (as supported by Dapr). It however seems that port and id can be passed but protocol cannot even though the dapr docs state that --app-protocol can be passed to switch between http or grpc
Note: Protocol is crucial as the Python SDK doesn't support HTTP for anything else than Actors. So, for most workers in the AI space, gRPC will have to be used.
Potential fix: add appProtocol to the CommonDefinitions.json but then this has to be added in the backend I suppose?
https://github.com/Azure/azure-rest-api-specs/blob/c0a3d9e02bef53de9b9dcd43e9be3a460d96a4e0/specification/web/resource-manager/Microsoft.Web/stable/2021-03-01/CommonDefinitions.json#L828-L853

Any update?

@XavierGeerinck Apologies for the late reply. Thanks for reaching out to us and sharing this feedback. I have marked our Service Team in this issue.
@AzureAppServiceCli @antcp Could you please look into this ask ?


[WIP] Fix broken CI

Summary
This PR fixes the broken CI.
Summary of the changes:

Update the tox version -> tox==4.11.0
Update the virtualenv version to match the new tox version -> virtualenv==20.19.0
Fix unit test test_qlibrary_3_options.py (line 291, line 490, and lines 499-502)
Fix the style of BridgeFreeJJ.py and test_qlibrary_3_options.py for the lint test

Details
The main problem with the CI was that tox wasn't able to set up the test environment. If we look at the errors, tox finds an error when calling the prepare_metadata_for_build_editable function. We had that problem because we were pinning tox to use an old version, and the pyproject-api version that we are using (pyproject-api==1.6.1) is not able to work with old versions of tox. The solution for this first problem was to change the CI to use a more recent version of tox. This update forces us to also use a more recent version of virtualenv because of the tox requirements.
Useful links to find more information about the problem:

https://www.github.com/tox-dev/tox/issues/3110
https://www.github.com/pypa/setuptools/issues/4031

Once we have the CI working again, we can discover another error, but this time with two tests in test_qlibrary_3_options.py. The two tests were also fixed and extended to validate two more attributes of the default options of transmon_cross in transmon_cross.py that weren't taken into account before.
The last change is regarding the lint test for the files BridgeFreeJJ.py and test_qlibrary_3_options.py.

Hello @zlatko-minev! The CI is now working, but I have a question about test_qlibrary_3_options.py. To make the CI work, I changed two tests (line 291, line 490, and lines 499-502) because they were expecting fewer default options of transmon_concentric and transmon_cross than the ones they actually have. Was that intentional? In that case, I'll change them back! Thank you in advance!


⚠ Bofrost.fr has degraded performance

In cbe2d2d, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1047 ms

Resolved: Bofrost.fr performance has improved in 6a96d5b after 9 minutes.


missing annotations

In the gapfilled model, the annotations are most of the times missing.
Here is the SBO checks from MEMOTE in the originally modelSEEDpy built GEM and after gapfilling it with DNNGIOR:

I suggest a post-annotation step based on the non-gapfilled model.

As far as I know it should be done in the model_refinement function (in dnngior/build_model.py) where it uses the aliases assign all relevant annotations. We could add
 if hasattr(reaction, 'annotation'):
                    mc.reactions.get_by_id(reaction.id).annotation = reaction.annotation

at line 113 (where it copies the gpr) but that could be a less clean option.
I am working on some things in the develop branch where I can add this so it would be fixed when we merge my new features.

Sounds good to me since that way it would just inherit the annotations of the draft model.
Let me know if  I could do anything to help. :small_airplane:


WMTheme: support macOS

Note the AppleAccentColor part was not tested because the AppleAccentColor doesn't exist in the plist file

Ok, I misunderstood.
However I'd say that the existing code is not optimised.
void ffStrbufAppendS(FFstrbuf* strbuf, const char* value)
{
    if(value == NULL)
        return;

    for(uint32_t i = 0; value[i] != '\0'; i++)
    {
        if(i % 16 == 0)
            ffStrbufEnsureFree(strbuf, 16);
        strbuf->chars[strbuf->length++] = value[i];
    }

    strbuf->chars[strbuf->length] = '\0';
}

Reallocating in a loop is really not a good idea because memory allocating is slow. It's always better to pre-calculate the required buffer size.
memcpy is always faster than hand coded plain loop ( if compiler failed to optimise the loop to a memcpy call ). A well coded memcpy ( such as the one provided in glibc ) uses SIMD instructions copies 16 ( with SSE2 ) or 32 ( with AVX ) bytes per loop, and can be about 10~20 times faster than hand coded plain loop which copies only 1 byte per loop. The larger the buffer is, the faster memcpy can be.

Quick benchmark: https://quick-bench.com/q/rv4D5N9zynZRRcWb2Td7y0BVneI

Makes sense. Thanks for looking into this.

ffStrbufAppendS can be further optimised by make it inline-able.
static inline void ffStrbufAppendS(FFstrbuf* strbuf, const char* value)
{
    if(value == NULL)
        return;

    ffStrbufAppendNS(strbuf, (uint32_t)strlen(value), value);
}

If the value is a string literal, its length can be known at compile time. In which case (uint32_t)strlen(value) can be completely optimised away.
// Before compiling
ffStrbufAppendS(&strbuf, "123456789");

// After compiling
ffStrbufAppendNS(&strbuf, 9, "123456789");

With the current implementation it might even make sense to force inline it.

Quick test: https://gcc.godbolt.org/z/z3rrn9vfa

I don't know enough much about that, but i don't think this applies to fastfetch, because the method implementation is in another compilation unit. Might not be a problem with IPO tho. If we want to make sure it is getting inlined, we'd have to implement it as inline method in the header.

Yes. A inline-able function must be in the header. Just move them into FFstrbuf.h you are done.


Fix sensitivity not always being applied.

Minor change to allow scroll sensitivity to be taken into account when options flipAxes or scrollYToX are being used.

Hi @iclanzan, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

:+1: Nice catch! Thank you for the contribution!


Enable people to specify their own documentation/required files.

Currently, this probot has hardcoded requirements that either a README or a docs/ are modified for the notification to not trigger. Because projects have varying standards on what they name their documentation or where changes need to go on each pull request, this doesn't work in all situations.
This pull request adds a config option called updateDocsTargetFiles that allows someone to optionally configure different paths to check for docs updates on. It also modifies the tests to pass (because we now get repo content 100% of the time as opposed to only if docs aren't modified).

Thanks!

!! You're welcome @hiimbex! Probot is love, probot is life!


Integration doesn't work when IPv6 is configured.

The problem
When HA is configured with native IPv6 address this integration doesn't work at all.
Version of Easee integration having the issue?
0.9.57
Version of Home Assistant Core having the issue?
2024.3.1
Anything in the logs that might be useful for us?
No response
Additional information
No response

Is there nothing in the logs?

We will not be able to help you unless you provide more information.
But, you can try the latest release (v0.9.58) since it does use different libs than earlier versions.
No idea if it might help, but it is kind of useless to try to debug the older versions since they are a bit different.

I will try and get back.

I updated to latest bit no difference..
Below you can see debug logging when HA uses dualstack:
2024-03-18 00:51:48.066 DEBUG (MainThread) [custom_components.easee.controller] Connection to easee login timed out
2024-03-18 00:51:48.067 DEBUG (MainThread) [custom_components.easee.controller] Controller deleted
2024-03-18 00:51:53.341 DEBUG (MainThread) [custom_components.easee] Setting up Easee component version 0.9.58
2024-03-18 00:51:53.341 INFO (MainThread) [pyeasee.easee] Easee python library version: 0.8.0
2024-03-18 00:51:53.341 DEBUG (MainThread) [pyeasee.easee] getting token for user: +46XXXXXXXXX
2024-03-18 00:52:16.269 ERROR (MainThread) [metno] Access to https://aa015h6buqvih86i1.api.met.no/weatherapi/locationforecast/2.0/complete returned error 'TimeoutError'
one interesting thing is that if you do a nslookup on "aa015h6buqvih86i1.api.met.no" it only resolves an ipv4 address, so it should not even try communicate on IPv6.
/N

Easees servers does not have IPV6 adress either, but I assume your intention is that IPV4 should work from your HA machine too...? I.e. you did say "dual stack" so that implies that both IPV4 and IPV6 should work, right?
Can you verify that it is actually possible to create a IPV4 connection from your HA machine?
For example by using this command locally on it (i.e. connect to it with ssh and type command):
nc -w 10 -v api.easee.com 443

If it works, you would get this response: api.easee.com (<IP_ADDRESS>:443) open
Otherwise nc: api.easee.com (<IP_ADDRESS>:443): Operation timed out
(The actual IP adress might be different, since it is hosted by amazon and they might route you to a different server).


Lack of ability to store Tags on OrchestrationInstance

Currently SqlOrchestrationService does not process and store Tags on orchestration instance creation. While it is a key to store extensional data shared within an orchestration instance.

@cgillum Can we get an update on this? Also, how do we set the extension data?

I can confirm that this support is currently missing. To implement it, we'll need to decide on the best way to store this data in SQL (serialized blob vs. structured key-value rows) and then update the appropriate SqlUtils code to read/write this data to/from the tables.


Running a function on app start?

I am making a slack app the makes polls. We're using redis to keep track of polls in progress so they persist through a restart of the app (server goes down, code is published, etc.). Because polls have an amount of time they are allowed to run for I want to close the polls that should have ended while the bot was down as well as re-add the currently running ones to threads to they can end at the appropriate time. Is there a way to run the given function when the app starts? I feel like this is super easy and I'm just making it more difficult than it is. Thanks!
Reproducible in:
The slack_bolt version
slack-bolt==1.15.1
slack-sdk==3.19.1
Python runtime version
Python 3.9.13
Steps to reproduce:
def cleanup():

    if r.exists('polls'):

        polls = json.loads(r.get('polls'))
        for index, poll in enumerate(polls):

            timer = poll['timer']
            end_time = int(poll['timestamp']) + (int(timer) * 60)
            print(end_time)
            print(time.time())
            if end_time > time.time():
                endPoll(WebClient, index)
                polls.pop(index, None)
                r.set('polls', json.dumps(polls))
            else:
                add(WebClient, index, int(end_time - time.time()))

Expected result:
Run the given function when the app starts
Actual result:
Trying to bind it to app.start predictably throws an error as it overrides the function
Requirements
Please read the Contributing guidelines and Code of Conduct before creating this issue or pull request. By submitting, you are agreeing to those rules.

Hi @IronicTrout thanks for writing in!
If I understand correctly you should be able to accomplish this between the app creation and calling start(), The App object has property client of type WebClient that can be used in your cleanup() function.
Here is an example of an app.py that illustrates this
import os
import logging

from slack_bolt import App
from slack_bolt.adapter.socket_mode import SocketModeHandler
from slack_sdk import WebClient

from listeners import register_listeners

# Initialization
app = App(token=os.environ.get("SLACK_BOT_TOKEN"))
logging.basicConfig(level=logging.DEBUG)

# Register Listeners
register_listeners(app)

def cleanup(client: WebClient):

    if r.exists('polls'):

        polls = json.loads(r.get('polls'))
        for index, poll in enumerate(polls):

            timer = poll['timer']
            end_time = int(poll['timestamp']) + (int(timer) * 60)
            print(end_time)
            print(time.time())
            if end_time > time.time():
                endPoll(client, index)
                polls.pop(index, None)
                r.set('polls', json.dumps(polls))
            else:
                add(client, index, int(end_time - time.time()))

# Start Bolt app
if __name__ == "__main__":
    cleanup(app.client)
    SocketModeHandler(app, os.environ.get("SLACK_APP_TOKEN")).start()

Let me know if this resolves your issue 🗺

Oh awesome, I think the problem I had was not putting the cleanup() call before SocketModeHandler(), which caused the function not to be called. Sorry if this is a silly question, but Is there a reason for that?

When .start() is called the app sets up a connection with Slack and then actively listens for incoming requests. This "listening" keeps the main python process busy, it is similar to the busy waiting concept of operating systems.
Multithreading and asynchronous processing are options that can get around this concept, but I don't feel like your issue is a use case for these.
This is a good question, someone may stumble on this thread at some point and find it helpful 🥇

Gotcha. That makes perfect sense. Thank you so much!


use InvariantCulture for using on all countries

Hello
the generated XML was was depend from current culture, I have fix it and now the XML can also use in Germany :)
Regards
Joerg

Thanks for your contribution


fixing onbaording steps for restore wallet flow

Description
I broke the import wallet flow onboarding header string b/c I changed the string name in onboarding.json. Fixing it by referencing the correct string.
Tested
manually tested
Related issues

Fixes #1258

Hey @lisaqyli is, We have verified this issue using Latest Android Internal Build V1.21.0 and updated status in the test Quality tool.
Test Quality Tool Link:
(Android 11):

https://valora.testquality.com/project/12128/plan/22175/run/151573/result/2540363

Device: OnePlus 7T(11.0)
CC: @MuckT
Thanks.


Launcher not initializing properly

Just posting this here because I think this is a launcher issue, not a MSYS2 issue.
https://github.com/msys2/MSYS2-packages/issues/2140#issuecomment-1332411943

Can you please describe here what is the perceived issue with msys2-launcher? I read the linked ticket and I couldn't figure it out.


Add link to gatsby-plugin-use-dark-mode

there's an issue with Node 11 (which I'm using because I specified "latest" in travis.yml. I'll fix this so it can build


Add _redirects file

Fix 404 issue.
https://docs.netlify.com/routing/redirects/

This PR will fix routing resolution issues caused by direct access paths.

Thanks for taking your time to fix this issue @simonguo , really appreciate it.


Update watchfaces.json with BinaryBlocks

Watchface that display the time in binary.
Can display hands to help users, has light and dark theme, and can vibrate the time in Morse code.

Very cool!


Looking for Citrix Hypervisor Alternatives with full GPU support

Am i able to use NVIDIA Full GPU Passthrough and vGPUs with Bareflank just as on Citrix's Hypervisor?

No, Bareflank is not that kind of hypervisor. It's an SDK for creating hypervisors.

No, Bareflank is not that kind of hypervisor. It's an SDK for creating hypervisors.


🐛 [firebase_ml_vision] Galaxy Tab A7 face recognition doesn't work

Bug report
Describe the bug
I've been using face recognition feature on Android "Mobile Phones", IOS and it works probably.
Also I've even tried it on another tablet "Galaxy Tab A -SM-T295" and it works just fine.
But when I'm trying it on "Galaxy Tab A7 - SM-T505N" It's doesn't even work or even give any errors.
Have been trying all orientations, rotations, landscape modes, portrait modes but nothing really works.
Steps to reproduce
Steps to reproduce the behavior:
Run Example on "Galaxy Tab A7 - SM-T505N" and it won't work
Expected behavior
That it would work fine
Flutter doctor
Click To Expand
[√] Flutter (Channel stable, 2.0.1, on Microsoft Windows [Version 10.0.18363.1646], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2019 16.9.0)
[√] Android Studio (version 4.1.0)
[√] IntelliJ IDEA Community Edition (version 2020.3)
[√] VS Code (version 1.55.1)
[√] Connected device (4 available)
• No issues found!

I'd recommend switching to the alternatives now;

for on-device vision APIs; switch to Google's standalone ML Kit library via google_ml_kit
for cloud vision APIs; the recommended approach now is to use Firebase
Authentication and Functions, which gives you a managed, serverless gateway to the Google Cloud Vision APIs. For an example Functions project see the vision-annotate-images sample project. You'd deploy this project for example and then call the cloud function from your app with your image data to get the annotation result.

Apologies for any inconvenience here and best of luck switching over the the new APIs. firebase_ml_custom is not affected by this deprecation.
Thanks

@markusaksli-nc Have tried google_ml_kit example on the tablet and got the same issue, sorry forgot to mention that.

Well for issues with that plugin you should report them in their plugin repository. Since Google removed the ML Vision APIs from Firebase our plugin is discontinued and there's nothing we can really do to help you.

@markusaksli-nc  Okay, Thanks for help anyway.


Add feature filename in the report

Is your feature request related to a problem? Please describe.
It is difficult to retrieve a scenario when reading the report
Describe the solution you'd like
Add the feature filename when displayed a scenario or a feature to facilitate maintenance.

Done in v2.5.0


Fix sphinx version

Re-enables fail_on_warning. I dunno why that was removed just days after it was added.
Fixes sphinx version to 2.2.1 which is what we us locally
Updates requirements.in and requirements.txt
tested on LLNL CZ

@biagas. I have the RTD working again. But, having fail_on_warning removed, some warnings crept back in...
/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/envs/18762/lib/python3.8/site-packages/sphinx/util/nodes.py:151: FutureWarning:
   The iterable returned by Node.traverse()
   will become an iterator instead of a list in Docutils > 0.16.
  for classifier in reversed(node.parent.traverse(nodes.classifier)):
/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/checkouts/18762/src/doc/building_visit/Linux_X11_Qt.rst:13: WARNING: Bullet list ends without a blank line; unexpected unindent.
/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/checkouts/18762/src/doc/building_visit/Linux_X11_Qt.rst:17: WARNING: Bullet list ends without a blank line; unexpected unindent.
/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/checkouts/18762/src/doc/building_visit/Linux_X11_Qt.rst:4: WARNING: Duplicate explicit target name: "x11 requirements".
/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/checkouts/18762/src/doc/building_visit/Spack.rst:311: WARNING: Include file '/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/checkouts/18762/scripts/spack/configs/olcf/spock/compilers.yaml' not found or reading it failed
/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/checkouts/18762/src/doc/building_visit/Spack.rst:315: WARNING: Include file '/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/checkouts/18762/scripts/spack/configs/olcf/spock/packages.yaml' not found or reading it failed
/home/docs/checkouts/readthedocs.org/user_builds/visit-sphinx-github-user-manual/checkouts/18762/src/doc/dev_manual/UpdatingPlugins.rst.rst:51: WARNING: line number spec is out of range(1-698):

Does any of the above look familiar?

@brugger1 did you by chance forget got commit these...
scripts/spack/configs/olcf/spock/packages.yaml
scripts/spack/configs/olcf/spock/compilers.yaml

@markcmiller86 have you updated from develop? @brugger1 and I both made changes yesterday.

The references with spock in the path were fixed on develop yesterday. I just checked the public documentation and it is correct. I'm not sure why you are seeing that failure.

The files
scripts/spack/configs/olcf/spock/packages.yaml
scripts/spack/configs/olcf/spock/compilers.yaml

were deleted and the references to them removed.

Ok, @biagas may be right...I may have forgotton a git pull before doing the work.

@markcmiller86 Is this designed to fix something other than having the RTD version of sphinx match our local versions (from build_visit) ?

Yes

Yes

Yes, there is something more being fixed? If so, what?

Yes

Yes, there is something more being fixed? If so, what?

@biagas, were the bullets in the introductor comment insufficient?

I found and fixed the issue with how collapsibles were getting rendered to html. The problem was that in newer versions of sphinx a .. container:: <foobar> was getting wrapped in <p>...</p> elements putting it on its own line. So, I had to add CSS styling to undue the effects of that. To do that, you need to peek at the generated html to understand how its naming the <div> classes being used and then target a CSS style. I put those into custom.css

Yes

Yes, there is something more being fixed? If so, what?

@biagas, were the bullets in the introductor comment insufficient?

At the time you asked for a review, the collapsibles weren't fixed, so I was just wondering if there was more coming or if you were finished and review ready.

How about changing the collapsible arrow to come before instead of after the header in these lines:
https://github.com/visit-dav/visit/blob/2e13e25d2bcb5471856b0647c38a8d7d75972578/src/doc/_static/custom.css#L23-L29

Done. Take a look.

How about changing the collapsible arrow to come before instead of after the header in these lines:

Done. Take a look.

I like it better, how about you?

I like it better, how about you?

No pref. Happy with it either way.

Ok, I think blank-lines issue is fixed with last commit. Good now?

I don't recall the specific error message or reason why we removed fail on warning -- I recall one time an overall problem was our develop docs where not being built for some reason due to it. This resulted in our public docs being behind what they should have been.  This may have been a long time ago.
It also could be an accident that I removed it b/c I had to heal read the docs for multiple projects and I missed the fact that I squashed it.

Can’t recall now. I saw them for sure when I first started on this yesterday PM.
Details have scrolled off my history (10,000 lines)
Then, discovered fail_on_warning had been disabled.
Anyways, fixed now?
"Kathleen Biagas" wrote:
@biagas commented on this pull request.

In src/doc/building_visit/Linux_X11_Qt.rsthttps://urldefense.us/v3/__https:/github.com/visit-dav/visit/pull/18762*discussion_r1230090043__;Iw!!G2kpM7uM-TzIFchu!0A5Q_vFCNWdwPvmSB-SMKsQ_qimnm_4q-a-F7OCtDgk_i_OIqa4sa9rXHD2IZl0xbEJ-EVTDLf6xXVMd4UZfmjXj6T0$:

For Qt 6 (only on develop branch)

Qt6's X11 Requirements <https://doc.qt.io/qt-6/linux-requirements.html>__https://urldefense.us/v3/__https:/doc.qt.io/qt-6/linux-requirements.html*3E*60____;JSU!!G2kpM7uM-TzIFchu!0A5Q_vFCNWdwPvmSB-SMKsQ_qimnm_4q-a-F7OCtDgk_i_OIqa4sa9rXHD2IZl0xbEJ-EVTDLf6xXVMd4UZfGnvxFmA$ page.

Also, if warnings are treated as errors on RTD, why didn't the build fail?
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https:/github.com/visit-dav/visit/pull/18762*discussion_r1230090043__;Iw!!G2kpM7uM-TzIFchu!0A5Q_vFCNWdwPvmSB-SMKsQ_qimnm_4q-a-F7OCtDgk_i_OIqa4sa9rXHD2IZl0xbEJ-EVTDLf6xXVMd4UZfmjXj6T0$, or unsubscribehttps://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/ABLUUZBPIBD6HIJ7M6T7W6TXLIINJANCNFSM6AAAAAAZFKVQP4__;!!G2kpM7uM-TzIFchu!0A5Q_vFCNWdwPvmSB-SMKsQ_qimnm_4q-a-F7OCtDgk_i_OIqa4sa9rXHD2IZl0xbEJ-EVTDLf6xXVMd4UZfVmVYEsg$.
You are receiving this because you were mentioned.Message ID: @.***>

Oh, I think I was getting it with 4.4.1 too...at least that is what I was running then.
Mark
"Miller, Mark C." wrote:
Can’t recall now. I saw them for sure when I first started on this yesterday PM.
Details have scrolled off my history (10,000 lines)
Then, discovered fail_on_warning had been disabled.
Anyways, fixed now?
"Kathleen Biagas" wrote:
@biagas commented on this pull request.

In src/doc/building_visit/Linux_X11_Qt.rsthttps://urldefense.us/v3/__https:/github.com/visit-dav/visit/pull/18762*discussion_r1230090043__;Iw!!G2kpM7uM-TzIFchu!0A5Q_vFCNWdwPvmSB-SMKsQ_qimnm_4q-a-F7OCtDgk_i_OIqa4sa9rXHD2IZl0xbEJ-EVTDLf6xXVMd4UZfmjXj6T0$:

For Qt 6 (only on develop branch)

Qt6's X11 Requirements <https://doc.qt.io/qt-6/linux-requirements.html>__https://urldefense.us/v3/__https:/doc.qt.io/qt-6/linux-requirements.html*3E*60____;JSU!!G2kpM7uM-TzIFchu!0A5Q_vFCNWdwPvmSB-SMKsQ_qimnm_4q-a-F7OCtDgk_i_OIqa4sa9rXHD2IZl0xbEJ-EVTDLf6xXVMd4UZfGnvxFmA$ page.

Also, if warnings are treated as errors on RTD, why didn't the build fail?
—
Reply to this email directly, view it on GitHubhttps://urldefense.us/v3/__https:/github.com/visit-dav/visit/pull/18762*discussion_r1230090043__;Iw!!G2kpM7uM-TzIFchu!0A5Q_vFCNWdwPvmSB-SMKsQ_qimnm_4q-a-F7OCtDgk_i_OIqa4sa9rXHD2IZl0xbEJ-EVTDLf6xXVMd4UZfmjXj6T0$, or unsubscribehttps://urldefense.us/v3/__https:/github.com/notifications/unsubscribe-auth/ABLUUZBPIBD6HIJ7M6T7W6TXLIINJANCNFSM6AAAAAAZFKVQP4__;!!G2kpM7uM-TzIFchu!0A5Q_vFCNWdwPvmSB-SMKsQ_qimnm_4q-a-F7OCtDgk_i_OIqa4sa9rXHD2IZl0xbEJ-EVTDLf6xXVMd4UZfVmVYEsg$.
You are receiving this because you were mentioned.Message ID: @.***>


Env problem during pre-build step

Hey! Are env variables not available during the heroku-prebuild step?
Even though they are there after the app goes live (i can see tem with printenv), when running the prebuild im getting a validation error cause they arent there.
This is my env configuration file with zod:
import { config } from 'dotenv'
import { expand } from 'dotenv-expand'

import { ZodError, z } from 'zod'

const stringBoolean = z.coerce
  .string()
  .transform((val) => {
    return val === 'true'
  })
  .default('false')

const EnvSchema = z.object({
  NODE_ENV: z.string().default('development'),
  DATABASE_URL: z.string(),
  DB_MIGRATING: stringBoolean,
  DB_SEEDING: stringBoolean,
  APP_SECRET: z.string(),
})

export type EnvSchema = z.infer<typeof EnvSchema>

expand(config())

try {
  EnvSchema.parse(process.env)
} catch (error) {
  if (error instanceof ZodError) {
    let message = 'Missing required values in .env:\n'
    error.issues.forEach((issue) => {
      message += issue.path[0] + '\n'
    })

    const e = new Error(message)
    console.log(process.env)

    e.stack = ''
    throw e
  } else {
    console.log(error)
  }
}

export default EnvSchema.parse(process.env)

Very straight forward and works fine when the start script runs. Just the build that fails, I cant migrate and seed my db because of it. Here is my package.json with the commands:
{
  "name": "hono-backend",
  "scripts": {
    "dev": "bun run --watch src/index.ts",
    "db:generate": "drizzle-kit generate",
    "db:migrate": "cross-env DB_MIGRATING=true bun run src/db/migrate.ts",
    "db:seed": "cross-env DB_SEEDING=true bun run src/db/seed.ts",
    "db:studio": "drizzle-kit studio",
    "route:test": "bun db:seed && bun test",
    "heroku-prebuild": "bun db:migrate && bun db:seed",
    "build": "bun --target bun build ./src/index.ts --outdir ./build",
    "start": "bun build/index.js"
  },
  "dependencies": {
    "@hono/zod-validator": "^0.2.2",
    "dotenv": "^16.4.5",
    "dotenv-expand": "^11.0.6",
    "drizzle-orm": "^0.31.2",
    "drizzle-zod": "^0.5.1",
    "hono": "^4.4.8",
    "postgres": "^3.4.4",
    "reflect-metadata": "^0.2.2",
    "typedi": "^0.10.0",
    "zod": "^3.23.8"
  },
  "devDependencies": {
    "@eslint/js": "^9.5.0",
    "@types/bun": "latest",
    "cross-env": "^7.0.3",
    "drizzle-kit": "^0.22.7",
    "eslint": "9.x",
    "eslint-config-prettier": "^9.1.0",
    "globals": "^15.6.0",
    "prettier": "^3.3.2",
    "typescript-eslint": "^7.14.1"
  }
}

The error I get is that DATABASE_URL and APP_SECRET are missing during the prebuild step. But they are in the console and show up with printenv once the app starts

No, Heroku don't provide them. Instead, you need to manually read them from disks in files, as per in ./bin/compile

Ok, so there's actually a way I can export those env vars as per the docs. Try again now... does it work?

Hey! Thanks for replying. Couldn't try it yesterday, ended up using a procfile with the generate and seed on the release command. When I have the opportunity all try it out without it again!

Have a chance to try it out yet?

I'm going to assume this is fixed, but re open if not.


[poco] Fix dependency libmariadb

Export INTERFACE_INCLUDE_DIRECTORIES in libmariadb
Fix using libmariadb on option ENABLE_DATA_MYSQL

Fixes #14713.

@yuntong613 Can you please test this PR?
Thanks.

-- Using cached C:/GitRepository/vcpkg/vcpkg-master/downloads/pocoproject-poco-3fc3e5f5b8462f7666952b43381383a79b8b5d92.tar.gz
-- Extracting source C:/GitRepository/vcpkg/vcpkg-master/downloads/pocoproject-poco-3fc3e5f5b8462f7666952b43381383a79b8b5d92.tar.gz
-- Applying patch static_pcre.patch
-- Applying patch arm64_pcre.patch
-- Applying patch fix_dependency.patch
CMake Error at scripts/cmake/vcpkg_apply_patches.cmake:55 (message):
Applying patch failed.  error: corrupt patch at line 231
Call Stack (most recent call first):
scripts/cmake/vcpkg_extract_source_archive_ex.cmake:142 (vcpkg_apply_patches)
scripts/cmake/vcpkg_from_github.cmake:150 (vcpkg_extract_source_archive_ex)
ports/poco/portfile.cmake:3 (vcpkg_from_github)
scripts/ports.cmake:136 (include)

@yuntong613 Did you pull my changes?

Build error clear.
There is another link error when use libmariadb in poco.
In the file Poco/Data/MySQL/MySQL.h ,Line 57, poco link libmysql Automatically, On VS2017 will  compile an error —— libmysql.lib not found，it seems need a patch when poco use libmariadb
//
// Automatically link Data library.
//
#if defined(_MSC_VER) && !defined(POCO_NO_AUTOMATIC_LIBS)
#if !defined(MySQL_EXPORTS)
#pragma comment(lib, "PocoDataMySQL" POCO_LIB_SUFFIX)
#endif
#pragma comment(lib, "libmysql")
#endif

Yes,I did poll. The error was happened on using poco library in my program. vcpkg auto link PocoData,PocoDataMySQL ,and poco will auto link libmysql.lib, not libmariadb.lib.
In file poco source code — poco/data/mysql/mysql.h

@yuntong613 Most dependencies are hard code in it's source files. Will fix today.

@yuntong613 Can you pull and test again?

I have tried the file changes.
Windows and Linux would build well, and be easy to use.
thank you.

Thanks @JackBoosY!


Basic statemachine (PoC stage)

[x] Add CLI to compile .scdl file into XState object
[x] Implement semantics for self-transition
[x] Implement semantics for triggered transition

Other tools that you can use at your disposal:

cute: python list/dict comprehension
serde: json serialization (since it also support wasm-bindgen, utilize HashMap not Struct to make implementing REPL in the next iteration easier) ✔
clap::SubCommand::from_yaml() (also follow up the progress of clap_derive)
using heaptrack in Rust ✔
syntect: crate for syntax highlighting or use prettyprint 😎 ✔

Just for fun tools:

check unsafe code
expand macros

I mess up and accidentally force push it 😢.
The data is still in the git-notes but it might be hard to traverse and re-apply it.
Here is the previous graph (can also be viewed in the gh-actions comment by clicking edited):


Update eslint peerdep

Greenkeeper didn't upgrade the peer dependency of the ffe-linting packages to eslint.

I changed the OR-ing of the peerDependencies entries to a greater-than-range. Currently our linting packages support these older versions of eslint and plugins, so I don't see any need to drop backward support yet.


Create blurred visualization

The blurred vis is needed when the string vis multiforms switch to a higher level.

Do we need this with our latest concept?

At the moment its not necessary. We said we would use the brush for unaggregated vis.

Yes, so the strategy is to not show the label if the row height is too small. However, the slim rows (that are empty) should still be brushable.

Will be handled as part of the vis labeling issue (#173)


issue detected in edit-result.php

Showing Garage value after updating a student result.

Problem Solved in edit-result.php in line : 211 [update button Issue in add-result.php]


README.md update elaborating usage.

We need a more elaborate README.md on Usage section

with v0.0.6, we can close this issue.


Cannot run on IOS

It probably won't work with recent RN versions. See the note in the readme, you can do most of what this does with the built in WebView now

This is the error message
/Users/xmc/Desktop/RNprojects/RN_iOS_App/node_modules/react-native/React/Base/RCTConvert.h:13:9: 'CSSLayout/CSSLayout.h' file not found with  include; use "quotes" instead
may be required to introduce what files, I do not understand IOS development, I hope you help solve the next.

As I said this won't work with recent RN versions and there's no much point in using anymore anyway.

That problem has been solved, and now there is a new problem. I hope you can help me to solve the next.


Seeking feedback: QEP 179, Turning Plugin Management into Actual Package Management

I hope this is the right place to ask - my apologies if it is not: I am currently running a QGIS Enhancement Proposal (QEP) for turning plugin management into actual package management. As part of this process, I am looking for projects within the QGIS ecosystem which could significantly benefit from the proposed ideas and concepts. Because my QEP heavily references conda, the QGIS conda-forge package projects feels like a natural candidate.
In a nutshell, I am proposing to allow to package QGIS plugins as regular Python wheels and/or conda packages - with all relevant packaging features such as proper Python package dependencies and binary extensions. As a "side effect", this work could be the foundation for advanced tool-chains and deployment solutions based on conda / conda-forge and QGIS. If you find this work interesting and potentially relevant for this project, I am rather curious about your opinion. Among other issues, there appears to be some serious doubt about the existence of actual use cases for the proposed changes in QGIS among its core developers. Besides, the proposed work may also "confuse (plugin) developers". Feedback is therefore highly welcome.

This is the right place and thanks for bringing this up!
My opinion strictly as a packager I have to say that this is an awesome idea! However, I'm not a heavy QGIS user to comment if this makes sense for them.
What I can say is: if you aim for PyPI/wheels we should be good on the conda side. There is nothing conda specific that would prevent us to just use the published PyPI package here. In fact, it would be easier b/c we can specify non-python dependencies easier them PyPI.

@s-m-e if you don't mind, I am closing this down. Please open it up again if you think it makes sense.

@s-m-e if you don't mind, I am closing this down. Please open it up again if you think it makes sense.


Update readme file

This PR updates the README file in three ways:

It converts it from text to GitHub-flavoured Markdown syntax (better formatting when viewing it on GitHub).
It adds instructions for how to build and run the code on Linux using Mono.
It reflects the fact that the MSR resources for Naiad are no longer monitored or updated, and redirects questions to the GitHub issue tracker.

Oops, didn't mean to bring in all the other changes too. Will cherry-pick and make another PR.


application_id & skip_provider_registration deprecated

Purpose

switch to resource_provider_registrations = "none" as skip_provider_registration is deprecated in latest azurerm provider
switch to client_id as application_id is deprecated in latest azuread provider

Does this introduce a breaking change?
[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

install latest terraform
follow README.md steps

What to Check
Verify that the following are valid

creates expected resources

Other Information

@microsoft-github-policy-service agree

On 23 Dec 2024, at 9:52 AM, microsoft-github-policy-service[bot] @.***> wrote:
@briancornally https://github.com/briancornally please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]
Options:
(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.
@microsoft-github-policy-service agree
(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"
Contributor License Agreement
http://www.opensource.org/
—
Reply to this email directly, view it on GitHub https://github.com/Azure-Samples/azure-devops-terraform-oidc-ci-cd/pull/6#issuecomment-2559231411, or unsubscribe https://github.com/notifications/unsubscribe-auth/AELMFZN3DJ2ZNTNRVEGEQPT2G7FLLAVCNFSM6AAAAABUCVM4FKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZGIZTCNBRGE.
You are receiving this because you were mentioned.


tessedit_char_whitelist doesn't seems to work

Hi
I'm running engine in eng+rus mode and tried to set tessedit_char_whitelist variable either using SetVariable method (also tried to convert passing string to UTF-8) or using config file (with UTF-8 without BOM encoding). But both ways not working and I'm still getting symbols like "|" and "$".
String itself looks like that:
0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZабвгдежзийклмнопрстуфхцчшщъыьэюяАБВГДЕЖЗИЙКЛМНОПРСТУФХЦЧШЩЪЫЬЭЮЯ

Can you provide an example source image? Also does this still happen when just using the official Tesseract executable with config file?

Closing due to no response and I haven't been able to reproduce at this time. If this is still an issue please reopen the issue.


Point marker size in meter

I gather from the doc that the size: item that applies to points is interpreted as pixels units.
I would like to have a round marker that has a fixed sized with respect to the ground, no matter the zoom level.
Is there anyway to achieve that?

You are correct, point features can only be sized in pixels. To create a feature that covers a fixed area on the ground, you may be better off creating a polygon feature with the dimensions you want. Would this work for your use case?

Another feature request describing the same issue in https://github.com/tangrams/tangram-es/issues/1121.

@karimnaaji Thanks, I did a quick check of open issues before but somehow missed that one.
@matteblair I agree I could use a polygon as a workaround with enough vertices so it looks like a circle but that sounds rather contorted.
I am ok to close that thread then and follow up there.


Godot always freezes when I press the export project button for Android using a Gradle build.

Tested versions
Reproducible in: v4.3.stable.official [77dcf97]
System information
Godot v4.3.stable - macOS 12.5.0 - Vulkan (Mobile) - integrated Apple M2 - Apple M2 (8 Threads)
Issue description
I am experiencing a freeze crash when trying to export my project to Android using the Gradle build system in Godot. The editor crashes without displaying any error messages, making it difficult to determine whether the issue is due to a configuration mistake or a bug. Even after I close Godot, my Mac overheats
Export Setup Details:

JDK:

Version: OpenJDK 17.0.12
Runtime Environment: Temurin-17.0.12+7 (build 17.0.12+7)
JVM: OpenJDK 64-Bit Server VM Temurin-17.0.12+7 (build 17.0.12+7, mixed mode)

Android Development Tools:
- Android Studio: 2024.1.1
- Android SDK Platform-Tools: Version 35.0.2
- Android SDK Build-Tools: Version 34.0.0
- Android SDK Platform: Version 34
- Android SDK Command-line Tools: Latest version
- CMake: Version <IP_ADDRESS>88404
- NDK: Version 23.2.8568313

config.gradle file in Android Build Template

ext.versions = [
 - androidGradlePlugin: '8.2.0',
 - compileSdk         : 34,
 - minSdk             : 21,
 - targetSdk          : 34,
 - buildTools         : '34.0.0',
 -  kotlinVersion      : '1.9.20',
 - fragmentVersion    : '1.7.1',
 -  nexusPublishVersion: '1.3.0',
 -  javaVersion        : JavaVersion.VERSION_17,
 - ndkVersion         : '23.2.8568313',
 - splashscreenVersion: '1.0.1'

]
Steps to reproduce

Open any project in Godot.
Go to Project > Export.
Select Android and configure the export settings.
Enable Gradle Build
Click on Export Project.

Minimal reproduction project (MRP)
N/A

I experience similar problems on linux


Fix: safe creation monitor - receipt can be undefined

What it solves
Part of #3569
While testing the creation a Safe on Polygon, I've noticed that an error was thrown in the creation tx monitor.
How this PR fixes it
Checks for null/undefined.
How to test it
It's not happening consistently.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.003%) to 35.325%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/routes/opening/index.tsx
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.003%

Covered Lines:
3403

Relevant Lines:
8704

💛  - Coveralls


454: Update AppVeyor to test against current Node release

Added Node-10 to list of Node versions against which to test.
Additionally renamed file to be more like TravisCI config file.
Fixes #454

Your call. AppVeyor gives 2 tasks free, so adding 9 will increase time to complete by several minutes. While I'm aware that 9 is still active til October, no reason not to be on 10.

AppVeyor gives 2 parallel tasks free and there are 3 even-numbered Node production releases, so adding Node-9 will increase time to validate commits/PRs by several more minutes.

I agree, I'd prefer to not add too many Node.js versions to test on Appveyor as it takes more time than travis. Moreover, testing on Appveyor is to check that the package works as expected on Windows which is somewhat independent of the Node.js version.

Agreed!

Merged with PR #453.


Add workaround for PF3 with PF4 issues.

Deploy preview for koku ready!
Built with commit bde39b1b5e96a6ace133894bc17618eb84157b5c
https://deploy-preview-91--koku.netlify.com

Deploy preview for project-koku ready!
Built with commit bde39b1b5e96a6ace133894bc17618eb84157b5c
https://deploy-preview-91--project-koku.netlify.com

Codecov Report

Merging #91 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #91   +/-   ##
=======================================
  Coverage   84.46%   84.46%
=======================================
  Files         103      103
  Lines         998      998
  Branches      107      107
=======================================
  Hits          843      843
  Misses        145      145
  Partials       10       10

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 d9cf401...bde39b1. Read the comment docs.


Stratos UI

Stratos, the Cloud Foundry UI that can also do Kubernetes and Helm, is a UI we've invested heavily in and that can be built as an electron app. We should look at how to incorporate it into RD. This includes:

Should we incorporate it with reasons?
How do we pull it in and make it part of RD?
Exposing through the menu next to Dashboard
What elements should be available? Should CF be displayed by default? Is this configurable?

Closing as stratos and the UI to look at k8s resources is no longer in scope for mvp or just following that. We will revisit the UI in the future but how and when we do that are not yet determined. I would expect it to be after Rancher 2.6.


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

I just made issue #313 about this, and there are two other pull requests for the same issue. SL4A isn't being developed anymore from this repository, so don't expect this to be merged.


[Fixes #33] Predicate literals

Also cleaned up order a bit for clarity.

See #33

I suggested another keyword type in https://github.com/ericelliott/rtype/issues/33#issue-118834814 because I thought you can create a function interface:
// interface NumberTransformer (Number) => Number

// addOne: NumberTransformer
export const addOne = (number) => number + 1;

// double: NumberTransformer
export const double = (number) => number * 1;

I suggested another keyword type in #33 (comment) because I thought you can create a function interface...

Nope. This is not a valid function interface:
interface NumberTransformer (Number) => Number

It should be written like this:
NumberTransformer(Number) => Number

or like this:
interface NumberTransformer {
  (Number) => Number
}

Personally I don’t like
NumberTransformer(Number) => Number // interface is implied for bare signatures

– how’s that different to
// NumberTransformer(Number) => Number
export const NumberTransformer = (a) => a;

?

But definitely :+1: to
interface NumberTransformer {
  (Number) => Number
}

– how’s that different to

It's different because the idiomatic way to use signatures inline is to use a tool like JSX. The trouble with commented signatures is that they're not live code, and they're likely to fall out of sync (which is a problem with lots of JSDoc annotations).

Ahh, OK – I think I misunderstood your original comment. Sorry!

(I didn’t mean using comments for annotating function signatures.)


UTCI thermal stress :: monthly barcharts

Hi @giobetti , can you provide more description and details about this task, like what the requirements are. Thank you very much!

Giovanni was referring to this chart, which has already been implemented so we can close the issue.


stac_load returns artefacts and NaN

Hello,
I am using odc-stac 0.3.1 and working with data from the Planetary Computer, similar like this:
    catalog = pystac_client.Client.open( "https://planetarycomputer.microsoft.com/api/stac/v1")

    query = catalog.search(
        intersects=aoi,
        collections=["sentinel-2-l2a"],
        datetime = "2017-06-02/2017-06-02"
    )
    items = list(query.get_items())
    items = [planetary_computer.sign(item) for item in items]

    ds = stac_load(
        items=items,
        bands=["B04"],
        resolution=60,
        crs='EPSG:32632',
        groupby="solar_day",
    )

I noticed strange behaviour from stac_load which produces artefacts as follows:

The stac items in this case have different source CRS which however should be handled by stac_load. Also I tried to input only items that share the same CRS, which did not prevent from producing aboves artefacts. The underlying original image data as downloaded from the Planetary Computer (e.g. by downloading item.assets["B04"].href) look OK.
A further problem (not sure if interrelated) arises when producing outputs with 100 m resolution (i.e. stac_load(..., resolution=100) which have unexpeced nodata, see white pixels (NaN):

...while original 10m resolution data looks as follows:

I am grateful for any hint or idea what is causing this behaviour.

It's a known issue with rasterio==1.3.0, has been fixed in rasterio but not in any released version yet
https://github.com/rasterio/rasterio/pull/2512

Thank you for your answer. I downgraded rasterio to <1.3.0 and things are working now again.


Removing the multipart tutorial row +

Now that the multi-part tutorials are distributed, I'm removing the multi-tutorial row
Also added shortcut for the Turkey Day tutorial
I'll wait for approval before I merge

It works correctly, it just looks like the layout changed.  Fixing in my next PR.


Doesn't work

After last update of home assistant, doesn't work. Say "Entity is currently unvailable". Versione of HA 9.0

Doens't work.. or i don't know how add appear on front .. (main principal)


Invalid argument :- while connecting twemproxy through nodejs loopback app

Here is a sample error which I got while connecting to twemproxy through my nodejs loopback app.
For Redis connection, I am using node redis library.
While connecting to twemproxy through redis-cli and mentioning port as 12212 , it is working fine, but not while connecting through the app.
[2016-03-14 17:34:19.576] nc_core.c:198 recv on c 7 failed: Invalid argument
[2016-03-14 17:34:19.576] nc_core.c:237 close c 7 '<IP_ADDRESS>:52485' on event 00FF eof 0 done 0 rb 14 sb 0: Invalid argument
[2016-03-14 17:34:19.576] nc_client.c:147 close c 7 discarding pending req 11 len 14 type 0
[2016-03-14 17:34:19.833] nc_proxy.c:386 accepted c 7 on p 6 from '<IP_ADDRESS>:52486'
[2016-03-14 17:34:19.833] nc_proxy.c:292 accept on p 6 not ready - eagain
[2016-03-14 17:34:19.834] nc_connection.c:346 recv on sd 7 14 of 16336
[2016-03-14 17:34:19.834] nc_redis.c:1098 parsed unsupported command 'info'
[2016-03-14 17:34:19.834] nc_redis.c:1686 parsed bad req 12 res 1 type 0 state 5
00000000  2a 31 0d 0a 24 34 0d 0a  69 6e 66 6f 0d 0a         |*1..$4..info..|
[2016-03-14 17:34:19.834] nc_core.c:198 recv on c 7 failed: Invalid argument
[2016-03-14 17:34:19.834] nc_core.c:237 close c 7 '<IP_ADDRESS>:52486' on event 00FF eof 0 done 0 rb 14 sb 0: Invalid argument
[2016-03-14 17:34:19.834] nc_client.c:147 close c 7 discarding pending req 12 len 14 type 0
[2016-03-14 17:34:20.090] nc_proxy.c:386 accepted c 7 on p 6 from '<IP_ADDRESS>:52487'
[2016-03-14 17:34:20.090] nc_proxy.c:292 accept on p 6 not ready - eagain
[2016-03-14 17:34:20.091] nc_connection.c:346 recv on sd 7 14 of 16336
[2016-03-14 17:34:20.091] nc_redis.c:1098 parsed unsupported command 'info'
[2016-03-14 17:34:20.091] nc_redis.c:1686 parsed bad req 13 res 1 type 0 state 5

@nkgupta1989 twemproxy can't support "info" command

Closing This issue, sucessfully able to connect to redis using twem proxy after the below changes in the redis connection.
connection = redisClient.createClient(global.config.redis.port, global.config.redis.host,{no_ready_check: true});
//adding no_ready_check, this will ensure that an info query is not send.
//And removing the select db number command, as that is not supported.
//connection.select(global.config.redis.db);


Screen text is not invalidated on "screen" detached

I have ssh+screen setup. When I detach screen, sometimes Terminal (last release) resets the current line, but keeps the old text on the screen. I'm still figuring out a proper repro.

@vadimkantorov When you're in this state, if you select the text that's left over from screen, will it just disappear on it's own? That might help us debug the source of this.

Version: 0.11.1121.0.
Thanks for advice about selection - I'll check

Are you using SSH 7.7? They’ve got a bug that causes this exact behavior, as well as occasionally duplicating the MOTD when you log in.

I use WSLv1 + Ubuntu 18.04.2 LTS + OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n  7 Dec 2017 (output of ssh -V)

@DHowett-MSFT I've the same issue since I've used the new terminal.
I'm over SSH connection and the terminal usually repeat last line. and sometimes it's placing the mouse within previous text and once typing it's overwriting it.

On "Version: 0.11.1191.0":

@zadjii-msft selection does not disappear:

Maybe this happens when ssh connections breaks

Well it's totally expected if the ssh connection breaks - screen wouldn't have a chance to clean up the terminal's state if the connection was broken abruptly.

Puzzling, I just tried a bunch of different versions of OpenSSH and I can only repro it with Win32-OpenSSH_7.7.

(working, 8.2)

(working, 8.1)

(failing, windows ssh, under tap)

It's unfortunately impossible to restore the terminal's state properly when the application on the other end hangs up and leaves it inconsistent. Screen restores the cursor position (and the main buffer) as part of teardown, and if it never actually tears down on the wire the terminal will always be left in a weird state.

@DHowett-MSFT
But i never lost the SSH connection. let me explain for you what exactly i do. maybe it's will help.

I'm using Windows New Terminal with PowerShell profile. and this before i connect to my server via SSH.

Now am connected to the server.

Now i started screen and detached it.

As you can see am still connected but the detached  lines repeated twice but sometimes not. and there's a time when it's override the last recent CMD.

@DHowett-MSFT Oh, it's happened now.
see it

This is the problem. This was resolved with https://github.com/PowerShell/Win32-OpenSSH/issues/1253 which should be released as part of the Win32_OpenSSH update coming later in the Windows release cycle. :smile:

Here what i meant with overriding

I understand. Thank you.

@DHowett-MSFT  you welcome.


change_beta intervention- perform basic testing

From @CWiswell-IDM :

Run a simulation that consumes the change_beta intervention and look at the outputs.
Run the same simulation without the change_beta intervention, and look at the outputs.
Expected: They should be meaningfully different (for example, if change_beta significantly lowers beta, there should be less infections in the first case than the second)
Ad-hoc test of intervention parameters

Looks good! Tests are in here, but I'm not ready to PR yet:
https://github.com/amath-idm/covasim/tree/unittest_interventions

Basically tested!
test_brutal_change_beta_intervention: If you set beta to 0, no more infections occur
test_change_beta_days: If you give a list of days equal to a list of changes, the multipliers are applied on the days specified.
test_change_beta_multipliers: If you run a series of simulations with the only difference being the amount to which you change beta, you get less infections the lower beta is (at crude levels of 1.0, 0.8, 0.6, 0.4, 0.2, this isn't meant to be 0.4000 is less than 0.4001).
test_change_beta_layers:

For clustered and hybrid population types, it is possible to disable the contact layers one at a time. When all four contact layers are disabled, no more transmission occurs.
For random population types, you may disable contact layer 'a', which has a similar (same?) effect as change beta without the layer parameter.

areas remaining to be explored:

change beta with synthpops layers. This has been tested locally, but without synthpops being part of the covasim package this has to be kept seperate.
multiplier effects of layering change beta without layers on top of change beta with layers, etc.


Gh 839 create timestamp set property

Codecov Report

Merging #950 into develop will decrease coverage by 0.61%.
The diff coverage is 72.24%.

@@              Coverage Diff              @@
##             develop     #950      +/-   ##
=============================================
- Coverage      63.56%   62.94%   -0.62%
- Complexity       956      977      +21
=============================================
  Files            480      486       +6
  Lines          13900    14139     +239
  Branches        1577     1596      +19
=============================================
+ Hits            8835     8900      +65
- Misses          4428     4587     +159
- Partials         637      652      +15

Impacted Files
Coverage Δ
Complexity Δ

...ches/binaryoperator/HyperLogLogPlusAggregator.java
66.66% <ø> (ø)
2 <0> (ø)
:arrow_down:

...inaryoperator/RBMBackedTimestampSetAggregator.java
100% <100%> (ø)
3 <3> (?)

.../bitmap/serialisation/RoaringBitmapSerialiser.java
71.42% <100%> (ø)
5 <2> (ø)
:arrow_down:

...uk/gov/gchq/gaffer/time/RBMBackedTimestampSet.java
66.66% <66.66%> (ø)
27 <27> (?)

...serialisation/RBMBackedTimestampSetSerialiser.java
68.75% <68.75%> (ø)
4 <4> (?)

...e/serialisation/BoundedTimestampSetSerialiser.java
69.81% <69.81%> (ø)
6 <6> (?)

...a/uk/gov/gchq/gaffer/time/BoundedTimestampSet.java
74.24% <74.24%> (ø)
22 <22> (?)

.../binaryoperator/BoundedTimestampSetAggregator.java
81.25% <81.25%> (ø)
6 <6> (?)

...java/uk/gov/gchq/gaffer/proxystore/ProxyStore.java
0% <0%> (-69.5%)
0% <0%> (-30%)

...uk/gov/gchq/gaffer/proxystore/ProxyProperties.java
0% <0%> (-44.83%)
0% <0%> (-17%)

... and 7 more

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 a335a7a...c6c1c8a. Read the comment docs.

I'll close this for now while I make a couple of changes:

Make the main method that generates the serialised sizes a unit test.
Add an example for the wiki.
Rename RBMBackedTimestampSetAggregator to RBMBackedTimestampSetUnionAggregator.
Add an aggregator that merges two RBMBackedTimestampSets together, but only keeps the most recent N timestamps.


plugin budget: bug in link-generation in Cost breakdown

I don't know where to post, here or in kanboard/plugin-budget.
In kanboard/plugin-budget there was no response.
I found the solution and want to share it with you.
https://github.com/kanboard/plugin-budget/issues/7
Regards
Martin

Thanks to report this issue, it's fixed in the master branch of the plugin.


[BUG] Gearboxes will output 0 torque most of the time when powering light props

Short Description
It seems that when a gearbox is powering a light prop (<200-ish?), it will not apply any torque unless the prop dips below a certain RPM. The source of the issue is on entities/gearbox/init.lua on line 800:
for Wheel, Link in pairs(self.Wheels) do
	local RPM = CalcWheel(self, Link, Wheel, SelfWorld)

	Link.ReqTq = 0

	if self.GearRatio ~= 0 then
		local Clutch = Link.Side == 0 and self.LClutch or self.RClutch
		local OnRPM = ((InputRPM > 0 and RPM < InputRPM) or (InputRPM < 0 and RPM > InputRPM))

		if Clutch > 0 and OnRPM then

			local Multiplier = 1
			if self.DoubleDiff and self.SteerRate ~= 0 then
				local Rate = self.SteerRate * 2

				-- this actually controls the RPM of the wheels, so the steering rate is correct
				if Link.Side == 0 then
					Multiplier = math.min(0, Rate) + 1
				else
					Multiplier = -math.max(0, Rate) + 1
				end
			end

			Link.ReqTq = (InputRPM * Multiplier - RPM) * InputInertia * Clutch

			self.TotalReqTq = self.TotalReqTq + math.abs(Link.ReqTq)
		end
	end
end

OnRPM returns false and Link.ReqTq is set to 0, applying no torque to its attached wheels.
Branch and Version
Master, up to date as of posting this.
How to Reproduce
Link a light prop up to an engine, and it will start to spin erratically.
Screenshots/Additional Information
I was able to replicate this bug with 3 vehicles:

I can provide the dupe files if needed. None of them switch gears or use brake/clutch/steer, the only gearboxes in use are differentials and double differentials, but the issue seems to happen for any gearbox.
Video of the tank:
https://youtu.be/NG4omZTKJPo
Video of the quadcopter: (much more dramatic)
https://youtu.be/jy6cHfwHfRU

Related to/same issue as #134, it's been talked about and most likely would need an overhaul of the whole mobility system to fix this easily. Hopefully it's looked into soon.

Ah, somehow I missed that when looking over issues. Hopefully this should still provide some more insight on the problem.


Input to reshape is a tensor with 43095 values, but the requested shape requires a multiple of 3042

when I run yolo.py, I meet the problem like title. Can you teach me how to solve the problem? Thank you.

Your model has 80 classes but your class file has one class. Check if it is a mistake.


[🌟] Give option to not use original file name in output file

Description
On iOS, picking a video will create a temporary file in cache with name <Original file name>. When the original file name has white space, the file name that is stored in cache contains white space. However the resulting Asset.uri encodes the file path so that white spaces are replaced with %20.
For example:
Original file name: My Video.mp4
Output file path: <Temporary directory>/My Video.mp4
Output Asset.uri: file://<Temporary directory>/My%20Video.mp4
This causes issues when using the Asset.uri in libraries such as react-native-fs or ffmpeg-kit-react-native, because the encoded uri does not actually exist; instead the version with white spaces exists.
This issue is not seen in android b/c the output file does not use the original file name.
Proposed Solution
Add an option such as omitOriginalFileName: true and have the output file not include the original file name.
Test Solution
Validate output file does not contain original file name.

I have the same problem, not sure what solution would be best for this though


fix(UI): remove the ButtonSpacer

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #48759

This PR was opened to remove the ButtonSpacer and replace it to modified Spacer helper.

We could potentially give the spacer a few standard sizes to use - maybe small = 5px, medium = 15px, large = 30px.

This sounds good to me, but I think it should be done in a second pr, because spacer is used in different prs and the longer this isn't merged, the more old styled spacers will be added

Thanks for your review, @moT01.
I agree with your idea that gives the spacer a few standard sizes (it might also be ex-large = 45px).
In this PR, I only focused to remove ButtonSpacer and modify the Spacer helper so it can use instead the one.
And I can try to open the following PR to improve the code to optimize the spacing flexibility regarding spacer size and make spacing consistent.

Thanks for taking care of this @mmatsumoto1026, I agree with Tom assessment.
We would preferably need just a few even sizes, but that is for another pr.


[Android] CameraRoll groupTypes not supported on Android

Hi, when define groupTypes for CameraRoll in react-native 45.1 it throws me groupTypes not supported on Android.
Is implementation of groupTypes for Android planned in the near future ?
Thank for answer.
Enviroment

react-native: 0.45.1
node: 8.0.0
yarn: 0.27.5

Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information, or the list of reproduction steps is not complete. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!


New feature - Co-existence with ShareAlbum plugin?

PiwigOpenIdConnect plugin works well and is great to support login of administrator or frequent/authorize Piwigo user accounts.  Unfortunately, when the plugin is enabled it disables the use of other very useful Piwigo plugin: ShareAlbum.   Are there any design changes in PiwigOpenIdConnect that could allow it to co-exist with ShareAlbum?

Hi - I ran into the same problem, and fixed it by adding this to the refresh_login function in main.inc.php
function refresh_login($user)
{
global $conf;
if ((pwg_get_session_var(SHAREALBUM_SESSION_VAR))) {
	return;
}

It simply skips the Open ID login if the album has been accessed from a ShareAlbum link

Great. The extra condition did the trick. With this fix, I was able to re-activate the Openid plug-in.
Thank you very much!
-------- Original Message --------
On Mar. 7, 2022, 17:37, singletrackdev wrote:

Hi - I ran into the same problem, and fixed it by adding this to the refresh_login function in main.inc.php
function refresh_login($user)
{
global $conf;
if ((pwg_get_session_var(SHAREALBUM_SESSION_VAR))) {
return;
}
It simply skips the Open ID login if the album has been accessed from a ShareAlbum link
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>


kan.unicharambigs seems to be copy of eng.unicharambigs

Reviving an old issue - see https://github.com/RaghavBhardwaj/tesseract-ocr/issues/801

I am shocked to notice that kan.unicharambigs contains only English script
instead of kannada script . I had expected kan.unicharambigs will contain
kannada script only.

Suggest building of https://github.com/tesseract-ocr/langdata/blob/master/kan/kan.unicharambigs based on https://storage.googleapis.com/google-code-attachments/tesseract-ocr/issue-801/comment-6/kan.DangAmbigs.txt and review by someone who knows kannada.

Unicharambigs isn't used by LSTM training or recognition.


Display pool name in add pool dialog on Prepare Sequencing Run page

Greg H. and I just observed this:

The pool name column actually has the pool id in it.

Greg H. states this is a must-have for soft launch, as without it lab personnel won't be able to figure out which pools to add.

Turns out this was a side-effect of the in-progress work for issue 251; all better now :)


Change "did you earn money from home" second question to radio button

Remove - 'Please Describe How You Earn Money Or What Business You Run' and turn open text to radio button


Jamba-instruct is not a valid model

We'll need to update Tokencost with Jamba-instruct. The model name in our dictionary is `ai21.jamba-instruct-v1:0`. Will raise an issue on that PR.
Originally posted by @areibman in https://github.com/AgentOps-AI/agentops/issues/382#issuecomment-2454067449

jamba-instruct is EOL on November 14, 2024. Do we still want to do this?
Source: https://docs.ai21.com/reference/jamba-instruct-api-ref


Finally done removing custom fixed width integer aliases

Description
Last PR in a series following #2192, #2196, and #2199.

SFMLBuildMaster: Build this please.

Added some missing headers in extended CI pipeline jobs.

SFMLBuildMaster: Build this please.

Added another missing header only caught in the extended CI pipeline.

https://us04web.zoom.us/j/73938690065?pwd=4ars7cgAjQNCTXxy1H4ewGaGFytYs3.1

SFMLBuildMaster: Build this please.


Change Process Wizard does not appear

In step 3 of this guide, there is no ellipsis available to run the Change Process Wizard - the only fields visible on the Projects page for the process are "Name" and "Description".  Was this article written using a pre-release version of Azure DevOps?

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2b35f891-bcd6-da03-9c07-a5ac494ab5cc
Version Independent ID: dcb0faba-7b49-0e9b-f430-2e2e43ed62d9
Content: Change process from Agile to Scrum - Azure Boards
Content Source: docs/organizations/settings/work/change-process-agile-to-scrum.md
Product: devops
GitHub Login: @danhellem
Microsoft Alias: kaelli

@KathrynEE I was able to repro the difference between current service experience and what the docs discuss. Could you double check?

@thomps23, @benbeaton , @danhellem - I believe that this feature is currently turned on for only a few customer accounts. It will become generally available in a few weeks. Dan - can you confirm?

I have the same issue, are there certain permissions i would need in able to see the change process wizard?

This feature is in preview only right now. I updated the docs accordingly. If you wish to participate in the preview please email me directly at<EMAIL_ADDRESS>and we can get you setup.


Add OWNERS file

Add owners file so we can confiure prow/tide correctly.

/approve
Second test

Green button merge is required.


MSRuleCleaner: properly evaluate tape transfers

Fixes #11363
Status
ready
Description
As it can be seen in the code changes, the reason we were accumulating workflows in non-archived status comes from the fact that we were never executing the block of code that evaluates output tape transfers, thus always mapping them to incomplete.
These changes have been directly made to the MSRuleCleaner pod (ms-rulecleaner-78d7c79d8-nsqf8) and I can confirm that workflows started getting properly archived once again.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
This bug has been inserted less than a month ago with the changes that I provided here:
https://github.com/dmwm/WMCore/pull/11357
I am very sorry about that!
External dependencies / deployment changes
None

test this please


Ensure Cobertura output conforms to DTD 0.4

Currently the output is not usable on VSTS builds because the XML does not conform to the spec outlined here: http://cobertura.sourceforge.net/xml/coverage-04.dtd.
This modifies the XML structure so the output is considered valid per the spec.

Coverage remained the same at 97.523% when pulling a6296f28271a8b5ad25a0ada5cef46ab44136f5c on salbahra:patch-1 into bc84c315271a5dd4d39bcefc5925cfb61a3d174a on gotwarlost:master.

Hope this has been resolved elsewhere as I'm closing this PR after so many years of no movement.


feat:🚀 adding @iplab/ngx-file-upload

adding @iplab/ngx-file-upload

LGTM

Thanks @pragadeesh2050 🙌


Adding logging info in readme in exchange server

What does this PR do?
Adding logging info in readme in exchange server
Motivation
Added log integration for exchange server, so updating the exchange server README to include logging.
Additional Notes
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

Once https://github.com/DataDog/logs-backend/pull/12491 is complete, I will update this one.