Moved notice to line 3. Removed the code 'may break unexpectedly' com…

…ment

@rgardler-msft, I did all the checks I know to confirm I only changed 1 file. So, unsure why this README change did not pass CI check?

@jasonmesser7 can you take a look at this. CircleCI is reporting:
#!/bin/bash -eo pipefail
az login \
  --service-principal \
  --tenant $AZURE_SP_TENANT \
  -u $AZURE_SP \
  -p $AZURE_SP_PASSWORD

argument --tenant/-t: expected one argument

Looks like $AZURE_SP_TENANT is not set. Probably a glitch in the request but we should be aware of what happened in case we see it multiple times.

I'm going to go ahead and merge anyway. The file looks great and its a trivial change.

@rgardler-msft I suspect this is something CircleCI does within a PR to protect the project and the credentials/service principles from malicious attackers. When the PR was merged it into main the test ran correctly and passed on CircleCI.
What I suspect is that CircleCI doesn't give permission in the PR to access the core projects environment variables. For example, what if in the PR someone decided to try and attack Azure by deploying 1 million VMs in the test file. If a PR had access to our environment variables and thus service principle, then a malicious attack could simply create a PR and spend on Azure through our SP.
We may need to update the Readme to specify that in order for a PR to pass the tests a user will have to set up CircleCI in their fork with a service principle from their own Azure subscription.
I suspect why we didn't have this issue before is because all of the other PR's were from branches on the main project we were working on as a contributor and Colins was the first outside PR since CircleCI was set up.

Lets not worry about it for now. We will move to GitHub actions in the future and the solution may be different at that point.
In the interim we can run any code change merges through local tests before merging.
Ross

From: jasonmesser7 @.>
Sent: Friday, August 12, 2022 10:49
To: Azure/simdem @.>
Cc: Ross Gardler (HE/THEY) @.>; Mention @.>
Subject: Re: [Azure/simdem] Moved notice to line 3. Removed the code 'may break unexpectedly' com… (PR #131)
@rgardler-msfthttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frgardler-msft&data=05|01|ross.gardler%40microsoft.com|66bc5e05c8284ea0364d08da7c8afb48|72f988bf86f141af91ab2d7cd011db47|1|0|637959233606390809|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=OlA%2F5uwkO76l%2BSJCe6MooH20YElmQq5lZLafPUcTAjw%3D&reserved=0 I suspect this is something CircleCI does within a PR to protect the project and the credentials/service principles from malicious attackers. When the PR was merged it into main the test ran correctly and passed on CircleCI.
What I suspect is that CircleCI doesn't give permission in the PR to access the core projects environment variables. For example, what if in the PR someone decided to try and attack Azure by deploying 1 million VMs in the test file. If a PR had access to our environment variables and thus service principle, then a malicious attack could simply create a PR and spend on Azure through our SP.
We may need to update the Readme to specify that in order for a PR to pass the tests a user will have to set up CircleCI in their fork with a service principle from their own Azure subscription.
I suspect why we didn't have this issue before is because all of the other PR's were from branches on the main project we were working on as a contributor and Colins was the first outside PR since CircleCI was set up.
—
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fsimdem%2Fpull%2F131%23issuecomment-1213365407&data=05|01|ross.gardler%40microsoft.com|66bc5e05c8284ea0364d08da7c8afb48|72f988bf86f141af91ab2d7cd011db47|1|0|637959233606390809|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=B1k4wH6%2BbRqFT1WTurdYb9jDWBXEjHgINS77yXxNW%2F0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAZ5Z7CSFP756YXUG73OXGHLVY2FB5ANCNFSM56JW5HDQ&data=05|01|ross.gardler%40microsoft.com|66bc5e05c8284ea0364d08da7c8afb48|72f988bf86f141af91ab2d7cd011db47|1|0|637959233606390809|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=7UYc7T4Osfq6k2JfShRhR4WTOa5XZxghqk1bQedPDzQ%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.***>


Fix missing type argument @ Reducer

[ ] There exists an issue discussing the need for this PR
[ ] I added new tests for the issue I fixed or built
[ ] I used pnpm run commit instead of git commit

Thanks!


CI should build and run tests

The CI jobs should be updated to build and run the tests. The Linux jobs should be easy, with a small tweak to the make command used to build the project. It's already setup so a make check will build and run tests, which depend on the project itself, and so will compile and link the project library automatically.
For AppVeyor, we may want to build a config file to be added to version control. Initially the AppVeyor job was setup using the web interface, with no files added to version control. That made for an easy setup process, but it less transparent than a config file. Additionally, a config file would make it easier for a project fork to setup their own CI solutions.
Finally, getting the tests to run on AppVeyor means I'd have an easy way to investigate test failures or warnings that only affect a Windows environment.

I took a quick shot at this and then quickly realized Google Test wasn't installed by default in the Linux environments. Further, because of the refusal to ship binaries with the Google Test library, it makes it kind of a pain to install the dependency.
CircleCI may be easiest, by using a custom Dockerfile, based on the currently used gcc:8 image, but with extra setup to install and compile Google Test. The extra layer needed for the Docker image should be fairly minimal, so it should add much to image download and launch time.
For TravisCI, this seems like more of a pain. TravisCI has no ability to customize the Docker image. If we use the faster booting Docker images, there is no root access. They have a special module to allow installing apt packages without root access, so that part is fine, but there is no ability to globally install Google Test libraries afterwards. Hence we would need to compile and store the binaries elsewhere. That could work, in that we could compile them to the project's build folder, and access the libraries from there, it's just a bit awkward, and might require some updates to the build scripts or environment to account for the moved library location.
Alternatively, we could go for the full VM option, rather than the Docker image. That would allow for root access, which enables compiling and installing global libraries for Google Test. Unfortunately, using a full VM adds 30 seconds of startup time to each build, and TravisCI builds are already slow.

I looked up pricing on TravisCI, CircleCI, and AppVeyor. Unfortunately, the absolute cheapest package is $30 / month on AppVeyor. TravisCI and CircleCI are both a fair amount more expensive than this. While I'm not opposed at spending some money if it helps the build process, $360+ / year is a fair amount more than I wanted to see. Too bad there isn't some room for something better than free but less than $100 / year. And I guess this would only get us Windows Builds with AppVeyor and not even Linux.
I think if we stick with the free packages, we should just bite the time bullet and expect long lead build times.
-Brett

Yeah, I think we should just stick with the free package for these projects. There are a few ways we could tweak the build time, and it may be worth experimenting with and learning about that topic in its own right.

In terms of reducing load, we are duplicating effort between TravisCI and CircleCI, which are both doing g++ Linux builds. We can potentially eliminate some job duplication between them.
We can also look at caching options for dependencies. For the TravisCI builds, that includes Apt packages. For Linux builds on both TravisCI and CircleCI, that includes Google Test.
We could investigate rolling builds. That would require caching. In particular, we cache the build output folder. Essentially we re-use build outputs from the last build, so it only needs to re-build files that have changed. This could leave cruft around when renaming files, since old object files would likely still exist under the old name. I don't see any obvious problems that would affect the build, though caching of stale data could slow down the caching over time.

In terms of differences, there are a couple. I noticed TravisCI is setup to do pull request builds and branch builds, while CircleCI is only doing branch builds. The TravisCI builds are building with both g++ and clang, while CircleCI is only building with g++.
Additionally, TravisCI offers a free tier for MacOS builds for open source projects. The other CI providers only have paid options for MacOS builds.
The TravisCI builds use a horribly outdated version of Linux, which requires a lot of setup time to update needed packages. This is done for each build.

In terms of where I see things might go, perhaps we could use AppVeyor for Windows builds, CircleCI for Linux builds, and TravisCI for MacOS builds (once the <filesystem> issue is sorted out).
To support that, we could add a pull request build to CircleCI, and make it build for both g++ and clang.

At any rate, the immediate task is just to find a way to install Google Test to the CI machines and get tests running.

Oh, and one more option I forgot to mention. We could potentially run our own CI server. GitHub offers arbitrary web hooks, so it could inform any server we want of new commits that need to be built.
By running our own CI server, we could not only use an optimized Docker image, but also have the server guaranteed to already be caching that image. On CircleCI we have a 35 second startup time (which includes image download), and a 17 second run time. By caching the Docker image, we could reduce that 35 second startup time to probably less than 3 seconds.
Further, running our own server means we could set the number of concurrent jobs it would run. Depending on the hardware we could run as many concurrent tasks as we want. We could probably even exceed the number of cores on the CPU since there's likely going to be some waiting on file I/O.
In particular, I have a server that sits in a basement and is on 24/7. It has plenty of disk space for Docker images, and a dual core processor that could run concurrent builds. The downside being I'm not physically present to restart the machine if it gets knocked out by a power outage or something, which occasionally happens, and can be a few days before I notice and ask someone to restart it.
Would love to learn how to setup something like that, though it's not going to be happening today, or for this issue.

This issue has been closed by PR #170 and PR #171, which have now both been merged.


Regex bomb in URL_REGEX

Need to find a better one and test it on long and complex urls.

Tested on production environment for two weeks now, seems to be perfectly working. Closing it.


Python 2 Support?

Is there anyway to run this with python2?

Hola @JeremySMorgan ! Thanks for your interest.
It is not possible to run pyntcloud with python2 out of the box. The lack of support for Python2 is intended, although I would be happy to help with indications to anyone who really needs to run this on Python2.
I think that trying to add python2 support to the full API would be an unjustifiable effort instead of using python3, but, if you really need to use python2 you could try to isolate the parts of the code that you really want to use and use a tool like https://wiki.python.org/moin/3to2 as first step. I can't guarantee that this will work out of the box but it will probably leave you with less work to do.
If you follow along with trying to run pyntcloud on python2, don't hesitate to open new issues as you encounter new problems.


color for geheim and erdgas very similar

I would suggest to increase perceptual difference between the two - maybe by making the color for geheim fully transparent, i.e., background color?

get it right in black and white ;)


How to get the code started

Hi,
Currently, I have been trying to run the pre-trained model but what is the correct way to key in the code.  ''python tools/train.py configs/swin/upernet_swin_base_patch4_window7_512x512_160k_ade20k.py --options model.pretrained=upernet_swin_base_patch4_window7_512x512.pth'' Above is my code but it shows invalid syntax. I could not find any mistake about the code I key in. Could anyone pls help me with the keying of the correct code? Thank You

Hi, @yvonneng996 . Could you please post the error message?
In addition, if you would like to finetune on the ADE dataset, you should run a command like
python tools/train.py \
  configs/swin/upernet_swin_base_patch4_window7_512x512_160k_ade20k.py \
  --options \
  model.pretrained=swin_small_patch4_window7_224.pth

swin_base_patch4_window7_224.pth is the model pre-trained on ImageNet. We use this model as the initialization for ADE finetuning.

This is the error that always prompt me whenever I click run.
Just to check with u, I need to use the pretrained model on ImageNet instead of the "upernet_swin_base_patch4_window7_512x512.pth". May I check with u when do I need to use this model "upernet_swin_base_patch4_window7_512x512.pth"?
Thank You so much of the reply.

This is the error that always prompt me whenever I click run.

It seems that you are running in jupyter notebook. Could you try this in a terminal?

when do I need to use this model "upernet_swin_base_patch4_window7_512x512.pth"?

upernet_swin_base_patch4_window7_512x512.pth has already finetuned on ADE20K. So, you can do inference with this model directly. In addition, if you would like to training on another segmentation dataset, you may use this model as initialization.

Hi impiga,
Sure understand. Do I try this in cmd terminal or anaconda terminal? I have tried as what u recommend and I try to run it in the terminal but it shows "no such file or directory". Should I download the model provided in the github and specify the folder path directory? and for the config I also need to download the code also?

Thank you


[HTM5] IE11 text measuring and formatting fix #1273

The root of the problem is text measuring mechanism that depends on browser.
IE 11 return rounded values for Context.measureText, because of that summ of pixels for every character in the text line and width of text line by itself will be different.

I am not certain what the best solution is here, I am concerned that using a single measurement per text group will result in poor word wrap support. One possible solution (performance willing) is to measure (at least on IE) each increasing letter ("h" then "he" then "hel"...) rather than each letter individually, and use those values to determine the correct advance.
Another solution might be to use a DIV to do something similar, I wonder how performance and accuracy compare between a DOM element and canvas measureText 😕

@MSGhero What conflicts are you talking about?

If this gets merged, my own PR would have merge conflicts

This one ? https://github.com/openfl/openfl/pull/1186 ? Oh I see. It's important that everything merge correctly. I also need your PR :)

The PR fixes some of my bugs but not each of them. I've still some disappearing space and overlap characters. I think there are some problem with rangeIndex and spaceIndex which generate wrong offsetX for TextLayoutGroup (that's just a guess I don't have any proof).
Also I've found that if I round the values of  Context.measureText. These bugs now appear in Chrome, Opera,etc.
I think we need to round all values when using Context.measureText. I know that it will currently break some text in html5 project that doesn't target IE11.
But we will be sure to have similar rendering across browser.
Then we can fix the remaining overlap characters bugs.

Lucas, I'm still working on it.
We must not round values, because it's producing side effect, sum of widths of each character in word "Hello" will be definitely not the same as width of word by itself.
Imagine that you have a long sentence where each character has a decimal part in the width. For example: each character has width 6.12px, every 10 characters mistake of measuring will be grow by 1.2 px, and so on.
So final measuring of whole sentence and rounded width of characters will be different for a lot of pixels - that's the reason why in IE 11 measureText gives not the same values for characters and sentences.

Well, I've made some research and found that my PR broke all text input functionality, and it's not that simple, I have another solution that will not broke any previous functionality, I'll test it today and try to implement in new PR.

If it makes you feel better, text input is already super broken. Input is such a different beast that I want to tackle that once the current set of textfield PRs get completed and merged.
But they probably will never get merged because they each break input even more 😅

@loudoweb , I'm totally found the solution and going to change this PR, tomorrow I'll commit it.

Awesome! Thanks!

It's better to close this one and check #1308


Support for Pendulum

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Attempting to use datetime sources other than (and better than) stdlib results in errors under pydantic 2.0
This is a regression from 1.x
pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for <class 'pendulum.datetime.DateTime'>. Set `arbitrary_types_allowed=True` in the model_config to ignore this error or implement `__get_pydantic_core_schema__` on your type to fully support it.

Example Code
from pydantic import BaseModel
from pendulum import DateTime

class Example(BaseModel):
    last_modified: DateTime

Python, Pydantic & OS Version
python -c "import pydantic.version; print(pydantic.version.version_info())"
             pydantic version: 2.4.2
        pydantic-core version: 2.10.1
          pydantic-core build: profile=release pgo=true
                 install path: /home/REDACTED/.cache/pypoetry/virtualenvs/REDACTED-XAw2sOhv-py3.10/lib/python3.10/site-packages/pydantic
               python version: 3.10.11 (main, Apr 20 2023, 14:14:57) [GCC 9.4.0]
                     platform: Linux-5.15.0-84-generic-x86_64-with-glibc2.35
             related packages: typing_extensions-4.8.0 pydantic-settings-2.0.

Hi, would it be possible to add the Time object as well?

Hi, would it be possible to add the Time object as well?

probably, PRs are welcome.

Is pendulum.DateTime now supported? I'm not seeing a mention of it on the official docs. I also get the following error:
pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for <class 'pendulum.datetime.DateTime'>. Set `arbitrary_types_allowed=True` in the model_config to ignore this error or implement `__get_pydantic_core_schema__` on your type to fully support it.

Here is the piece of code that triggers this on my Pydantic class:
import pendulum

created_at: Optional[pendulum.DateTime] = Field(default=None)

Setting arbitrary_types_allowed on the configuration fixes this issue.
class Config:
    arbitrary_types_allowed = True

I made sure that the pydantic-extra-types package is installed.


user-agent header always the same in cloudflare pages

Describe the bug
When deploying to cloudflare pages, the "user-agent" header in the Handle Hook seems to always have the same value.
It works as expected while running in dev or preview in local.
It tried disabling prerendering and disabling ssr but it changes nothing.
I don't even know if the problem is comming from the cloudflare adapter, cloudflare itself, or sveltekit
Reproduction
hooks.ts
export const handle = async ({ event, resolve }) => {
    if (event.request.headers.has("user-agent")) {
        event.locals.userAgent = event.request.headers.get("user-agent");
    }
    return await resolve(event);
};

export const getSession = (event) => {
    return event.locals;
}

index.svelte
<script>
    import { session } from "$app/stores";
</script>

{$session.userAgent}

Deploy to cloudflare pages
It setted up a pages just to test this behaviour if you want to see the result for yourself : https://test-bug-cloudflare.pages.dev/
No matter the device, the same text is printed.
Logs
No response
System Info
System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 AMD Ryzen 7 5800X 8-Core Processor
    Memory: 20.25 GB / 31.93 GB
  Binaries:
    Node: 16.14.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.5.3 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.22000.120.0), Chromium (98.0.1108.43)
    Internet Explorer: 11.0.22000.120
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.34
    @sveltejs/kit: next => 1.0.0-next.316
    svelte: ^3.47.0 => 3.47.0

Severity
serious, but I can work around it
Additional Information
No response

Actually that was the first time, second time(after I changed it) it was the same as the first time. And the CF cache header is HIT, so for some reason it gets cached.

Isn't that weird that Cloudflare caches the page for different devices ? Seems it's cached even for different IPs : I have the same result on my phone with 4G.

It's per region (colocation) only, probably

But I'm not sure how you turned it on, because it's not in your code

It should somewhere in their panel

No problem, cc @lukeed maybe he can help you


Swift test suite: renamed files with inconsistent names

Avoid dots on file names. Use camel case instead.
Compatibility with
https://github.com/krzysztofzablocki/KZLinkedConsole

LGTM

LGTM


When opening a thread with new posts, take me directly to the earliest post I have not viewed

SEE TITLE DANG

Rob Park likes it :)


How to make it run on IE?

astroturf components do not work in IE with this plugin, it chokes on const camelCase = str => arrow function. How do i make gatsby transpile astroturf's runtime?

ok looks like gatsby does not polyfill the dev env. production build works fine

Does Gatsby's dev environment usually work fine IE? Do you only have problems with astroturf?


Softlinking explorer.exe has weird behavior.

Your Windows build number:  Version 1903 (OS Build 18362.329)

What you're doing and what's happening:  (Copy&paste the full set of specific command-line steps necessary to reproduce the behavior, and their output. Include screen shots if that helps demonstrate the problem.)

What's wrong / what should be happening instead:
I expect command line explorer . to behave the same as explorer.exe . after softlinking \usr\bin\explorer to explorer.exe. However, two issues emerged.

I have to use sudo to call explorer, otherwise, nothing would happen.
sudo explorer . leads to the System32 folder instead of home directory folder of WSL.

This is a duplicate to this issue: https://github.com/microsoft/WSL/issues/3999 which has already been fixed! :)
Thank you for filing.


Penalty shootouts: reducing sensitivity of goal line check

Reducing risks of false positive by requesting one continuous second of rule
infringement to penalize the robot. This should fix #162
The initial problem is highlighted by doing slight modifications of the test.

In penalty_shootouts: roughly 5 cm of difference allowed along x-axis

Goalkeeper red: slightly behind (x=-4.51) and slightly tilted backward

Robot is incorrectly considered as penalized

Goalkeeper blue: slightly in front of initial position

Additionally, links toward team files in penalty_shootouts2 are fixed.

This pull request has been tested on the 3 penalty shootout tests with 0 errors and is not expected to affect other tests. It does not change the rule but mainly its implementation.


Harmonize attributes returned by model_info, dataset_info and space_info

Suggested by @sgugger.
If you do dir(model_info("albert-base-v1"), you get:
'author',
 'cardData',
 'config',
 'disabled',
 'downloads',
 'gated',
 'id',
 'lastModified',
 'library_name',
 'likes',
 'mask_token',
 'model-index',
 'modelId',
 'pipeline_tag',
 'private',
 'securityStatus',
 'sha',
 'siblings',
 'spaces',
 'tags',
 'transformersInfo',
 'widgetData'

which have 3 types of syntax (-, _, and camelCase).
Would be good to harmonize this in a more pythonic way (e.g snake_case). Let's keep both syntax possible for backward compatibility  but only have the snake_case one in repr.

(see also this comment  -private link-: we should handle id and modelId consistently)

that being said i think it's nice to have the same attributes in the Python wrapper as in the actual API


User Timeline  (Twitter::Error::Unauthorized) —  Error raised when supplied user credentials are not valid.

Hello,
I have this issue when I cycle like 100 or 200 Twitter accounts like this:
`
client = Twitter::REST::Client.new do |config|
config.consumer_key        = "xxx"
config.consumer_secret     = "xxx"
config.access_token        = "xxx"
config.access_token_secret = "xxx"
end
#begin loop here 100 or 200 accounts
client.user_timeline(user.uid,{:count=>50}).each do |tweet|
save_tweet(tweet)
end
#end loop
`
It authenticate well using the credentials initially. But after a while it gives that error:
"Twitter::Error::Unauthorized"
I have tried to rescue from that error, wait a couple of minutes and then call Client.new again, but not luck, same error ... I'm no getting close to the rate limits, just 200 o 300 accounts timelines to check.
Any help here thanks!

Anyone can help with this error?

@brusacco We're seeing a similar issue with fetch_mentions_timeline. Have you made any progress in your understanding of the problem?

Hello, in my particular case, the error was because some accounts where private ones, sorry for not getting back on this ... but after filtering those ones, we have no more problems.


Update Profile.js

This naming 'isUser' may not fit. But the fix will work.
In the original version, users can still see the 'follow' button even though they are not signed in.

Thanks!


Token expiration

Hi all,
I'm trying to implement a JWT authentication flow in my vapor server. Before I was using a different library and doing everything manually, but now I decided to use jwt-provider and I'm struggling with token expiration
I configured the PayloadAuthenticationMiddleware for an endpoint and I created the token as below
var jsonPayload = JSON(.object(payload))
try jsonPayload.set(
  ExpirationTimeClaim.name,
  Date().addingTimeInterval(30 * 60)
)

let jwt = try JWT(
  payload: jsonPayload,
  signer: signer
).createToken()

return jwt

I was expecting that the middleware was able to check the token validity (expiration date), but it's not doing it, so I'm checking the expiration in the object initialization as below:
public init(json: JSON) throws {
  let expirationDate = try json.get(ExpirationTimeClaim.name) as Date
  guard Date().compare(expirationDate) == .orderedAscending else {
    throw Abort(.forbidden, identifier: "EXPIRED_TOKEN")
}

  id = Identifier(try json.get("id") as Node)
  email = try json.get("email")
}

Is this the correct way? Is there a better one? How to include the check in the middleware?

You can simplify the creation of the token a bit:
let token = try JWT(
    payload: ExpirationTimeClaim(date: Date().addingTimeInterval(30 * 60)),
    signer: signer
)

To include expiration time checking in the middleware, include an instance of ExpirationTimeClaim without specifying a date. This way it will check using the time of each incoming request.
let authMiddleware = PayloadAuthenticationMiddleware(claims: ExpirationTimeClaim())

I didn't test this code but it should work (or be close).


[Serialization] Drop decls whose types can't be deserialized.

Proof-of-concept. This shouldn't be common—renames are far more likely, and those we can track—but occurs when the swift_wrapper attribute (the implementation of NS_STRING_ENUM) is active in Swift 4 but not in Swift 3.
Note that this only checks the canonical interface type of the declaration, because the non-canonical type may contain references to the declaration's generic parameters.

@swift-ci Please smoke test

@swift-ci Please smoke test


prometheus-operator restart complaining about namespaces

What did you do?
installed kube-prometheus.
What did you expect to see?
no error messages during prometheus-operator startup.
What did you see instead? Under which circumstances?
when I kill the operator pod and it gets restarted, it is complaining about all the existing namespaces with the following error. After a while the error messages are gone.
level=error ts=2018-09-27T09:06:44.594291197Z caller=operator.go:734 component=prometheusoperator msg="get namespace to enqueue Prometheus instances failed: namespace \"monitoring\" does not exist" err=null

Environment
dev

Prometheus Operator version:

    Image:         quay.io/coreos/prometheus-operator:v0.23.2
    Image ID:      docker-pullable://quay.io/coreos/prometheus-operator@sha256:8211b3eb30cb8591ddf536f1cf62100f5c97659c14d18dd45001acf94dafd713

Kubernetes version information:

kubectl version
Client Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.3", GitCommit:"a4529464e4629c21224b3d52edfe0ea91b072862", GitTreeState:"clean", BuildDate:"2018-09-09T18:02:47Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.4", GitCommit:"5ca598b4ba5abb89bb773071ce452e33fb66339d", GitTreeState:"clean", BuildDate:"2018-06-06T08:00:59Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Kubernetes cluster kind:

kubespray

Manifests:

apiVersion: apps/v1beta2
kind: Deployment
metadata:
  labels:
    k8s-app: prometheus-operator
  name: prometheus-operator
  namespace: monitoring
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: prometheus-operator
  template:
    metadata:
      labels:
        k8s-app: prometheus-operator
    spec:
      containers:
      - args:
        - --kubelet-service=kube-system/kubelet
        - --logtostderr=true
        - --config-reloader-image=quay.io/coreos/configmap-reload:v0.0.1
        - --prometheus-config-reloader=quay.io/coreos/prometheus-config-reloader:v0.23.2
        image: quay.io/coreos/prometheus-operator:v0.23.2
        name: prometheus-operator
        ports:
        - containerPort: 8080
          name: http
        resources:
          limits:
            cpu: 200m
            memory: 200Mi
          requests:
            cpu: 100m
            memory: 100Mi
        securityContext:
          allowPrivilegeEscalation: false
          readOnlyRootFilesystem: true
      nodeSelector:
        beta.kubernetes.io/os: linux
      securityContext:
        runAsNonRoot: true
        runAsUser: 65534
      serviceAccountName: prometheus-operator

Prometheus Operator Logs:

for every existing namespace the following message many times ( but not the same count for all nmaepsaces ) ..
level=error ts=2018-09-27T09:06:44.594291197Z caller=operator.go:734 component=prometheusoperator msg="get namespace to enqueue Prometheus instances failed: namespace \"monitoring\" does not exist" err=null

Curious. This sounds like the namspace informer is in an inconsistent state with an event that came in. @squat @mxinden maybe we're not waiting for an initial sync correctly?
@nrobert13 does this happen randomly in the logs or just once (or a few times) at startup and then stops?

I'll give this a spin to try and reproduce and report back. If it happens after killing, then it should also happen randomly on first start as these are the same for us since we keep no state.

I am also getting this same error. This is happening on pod startup, and re-creating the pod does not fix the issue, the operator just crashLoops from here.

Correct me if I am wrong, but from @nrobert13's description, it does not seem like the operator is crashlooping but rather logging non-critical errors an eventually stabilizing, which differentiates it from your experience, @quikstrike.

@nrobert13 sorry for the delay. The root of the issue is that release v0.23.2 did not include the recent fixes to synchronize object caches before running the informers [0]. The result is that the operator will log an error if it tries to operate on an object that is not yet in the cache. This is non-fatal; the operator will simply try again later. Eventually, the cache will catch up and the operator will function normally.
This issue is already fixed in master and will be available in the next release. I'll close this issue for now as the issue is already fixed and is simply awaiting a new release.
[0] https://github.com/coreos/prometheus-operator/pull/1813

sorry for the delay, thanks to everyone.

@squat You are correct about my experience. Should I create a new ticket to address my issue? It wasn't clear from your last message if your reply also addressed my issue. I'm happy to open another ticket for the sake of keeping things clean. Let me know.


Build fails with clang++ 15.0.1

Build fails at the following line of code when using clang++ 15.0.1 due to error fatal error: variable 'count' set but not used [-Wunused-but-set-variable]
https://github.com/raspberrypi/libcamera-apps/blob/dd97618a25523c2c4aa58f87af5f23e49aa6069c/apps/libcamera_jpeg.cpp#L42

I'm a bit surprised at this warning, given count is incremented in the same statement... but the compiler is probably correct given it is never referenced in the loop.
Feel free to change this to for (;;) to fix this.

I've merged the patch so will close this issue. Thanks!


Maven freeze!

Hello, I download and try you project, when execute the command "mvn package" the process always freeze!

Sorry for the inconvenience! But it was the Avast!


[BUG]Incorrect link name conversion

After using this plugin, some links may be converted to this format

After using the links plugin to convert to MD format, it causes the nested link names to be too long

At this point, I need to manually delete the link name to automatically correct it, which is too troublesome

Request to fix this issue

@EpicJayQQ753285662 you didn't follow the bug template

Also, it has been converted into an incorrect format, and I will also make the necessary modifications once I detect it again

@EpicJayQQ753285662 you didn't follow the bug template

what?


Item and Block tagging standardization

obligatory xkcd comic

Dearest @ExcessiveAmountsOfZombies, @FoundationGames, and @DawnTeamMC;
I was skimming through fabric's discord earlier and came across mention of someone using our mods in a pack. Their one complaint was that there was no integration between them. For example, all of our mods add tomatoes, yet none of them are compatible in recipes. That's really annoying and I feel kinda bad for the end user.
Fortunately (or unfortunately depending on how you look at it), croptopia seems to have mostly set the standard for us! In the coming weeks I'll be putting my items in the c: tags, and I reach out to you all to implore you (or your teams) to do the same. If there are any gray areas as to where an item should go, or what a tag should be named, let's discuss it here. If you want to make issues in your own repos to document progress please tag this issue in it as I'd like to be clued into what's going on in the community.
Cheers!

The fabric wiki is slightly outdated in regards to Croptopia's tags, I (and ayutac) recently finished standardizing to the proper c: tags. you can find them all here
As I support forge I also use sub-directories to match forges convention, and then have my recipes reference the base directory tag. anything marked with #${dependent} is changed to c: or forge: whenever the jar is built.

@ExcessiveAmountsOfZombies Thanks! This is a really good reference to go off of. I'll be doing so in the near future. I don't know what happened but I managed to completely miss that you were the dev of Croptopia when writing the initial issue. Regardless, I'm glad I absentmindedly tagged you, as your insight is useful.


Spacing Between Words "Japanese" Recognition

Hi,
while i made some Images Recognition for the Japanese language i found that the resulted Japanese text has different spacing between its characters, i have no background in Japanese but in the original documents or images the spacing is different meaning some times its more like spaces between English letters and other times the space similar to the space between English words, while in the resulted text all spaces are similar between all characters.
Thanks

As suggested in https://github.com/tesseract-ocr/tesseract/issues/1009
use -c preserve_interword_spaces=1 to remove extra spaces
Also see https://github.com/tesseract-ocr/tesseract/issues/991

@Shreeshrii  Thanks

Hi,
just adding information, this -c preserve_interword_spaces=1 argument works good with Japanese (i didn't try it with English) but for Arabic its better not to use it, since the Arabic language has Cursive  writing system, so i detected a text with both cases, with the argument and without it, when i used the argument for Arabic some of the words were detected correctly but are joined to the next word which is incorrect, but without that argument the same words didn't  join to the next word

Fixed via https://github.com/tesseract-ocr/tessdata_fast/pull/7
@zdenop  Please close this issue, after PR is merged in tessdata_fast.


Crash at createDxgiFactory on Wine-staging 3.5

I've tried to run DXVK  on wine-staging 3.5 using the version from https://repos.wine-staging.com/alesliehughes/.
Traceback
I have dxvk and shaderc compiled from source from master trees.
I'm on Kubuntu 17.10, nvidia drivers 390.48 from graphics-drivers ppa.
Software information
dxgi-factory.exe
System information

GPU: GTX 950M
Driver: 390.48
Wine version: 3.5-staging
DXVK version: compiled from master

Log files

d3d11.log: empty
dxgi.log: empty

Sounds more like a driver/wine issue than anything else. Do you have the Intel Vulkan driver installed? If so, you might need to remove it or set VK_ICD_FILENAMES to the Nvidia driver's json file..

No I don't have them installed.

Must be an issue with wine's Vulkan implementation.

I've tried it again with 3.6-Staging and 3.6-Devel and it crashed again, should I file a bug report to them?

Wine 3.10-staging every sample is crashing with the same error message: 002e:err:d3dcompiler:compile_shader HLSL shader parsing failed.

You'll have to use native d3dcompiler DLLs for games that use them.


Question

is this libary available at gradle?  Or how can i use the libary in my project? Sorry im new in Java. Thanks for Help.

Hi, this library is not in any public Maven or Gradle repository (yet).
You can use it by cloning the project, building it from command line (mvn clean install) and then adding it as Gradle dependency: implementation 'sk.mimac.fingerprint:fingerprint-sensor:1.0.2-SNAPSHOT'


Could you add how to use this library

Could you add how to use this library

(This is how i did it, point is, you have to compile the repo)
Download the repo.
cd into it and use go build . or however you wanna build it
the just run it and it will show you this help screen:
Usage: gobfuscate [flags] pkg_name out_path
  -enckey string
        rename encryption key
  -keeptests
        keep _test.go files
  -noencrypt
        no encrypted package name for go build command (works when main package has CGO code)
  -nostatic
        do not statically link
  -outdir
        output a full GOPATH
  -verbose
        verbose mode
  -winhide
        hide windows GUI


A problem about training.

Hello, thanks for your great work. However, when I run your train.py file, I have some problems as follows. Could you help me to solve this problem. Thanks!
Traceback (most recent call last):
File "train.py", line 218, in
train()
File "train.py", line 141, in train
d_fake = generator_step(net_d, out2, net_loss, optimizer)
File "/userhome/point-cloud/VRCNet/utils/train_utils.py", line 42, in generator_step
total_gen_loss_batch.backward(torch.ones(torch.cuda.device_count()).cuda(), retain_graph=True, )
File "/opt/conda/lib/python3.6/site-packages/torch/tensor.py", line 120, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph)
File "/opt/conda/lib/python3.6/site-packages/torch/autograd/init.py", line 93, in backward
grad_tensors = _make_grads(tensors, grad_tensors)
File "/opt/conda/lib/python3.6/site-packages/torch/autograd/init.py", line 29, in _make_grads
+ str(out.shape) + ".")
RuntimeError: Mismatch in shape: grad_output[0] has a shape of torch.Size([1]) and output[0] has a shape of torch.Size([]).

Hi,
I am having the same issues. I use python 3.8, PyTorch 1.8.1 and Cuda 11.
Does anyone have a fix for this?
Thanks

Hi,
I find that the issue may occur when trained with only one gpu, you can try more than two.
Best regards.

Hi,
thanks for your input, it helped fix the issue. If you only have one GPU, PyTorch outputs the resulting loss as a scalar, not a vector of losses, but the command torch.ones(...) always creates a vector for the gradients.
The edge case can be caught by either not using torch.ones(...) or squeezing the result by changing line 134 in train.py to:
net_loss.backward(torch.squeeze(torch.ones(torch.cuda.device_count())).cuda())

It helps, thanks!


Create block index views in FixturesConsole and MigrateConsole

Corresponds to https://github.com/vivid-planet/comet-starter/pull/222

Title should probably be "Create block index views after fixtures and migrations"

@thomasdax98 what's the status here?


about running bash script in macos

Good Morning,
I am trying to run trail using bash script as mentioned in readme bash scripts/trail.sh experiment_dir
using command
bash scripts/trail.sh output/
but getting the error
scripts/trail.sh: line 23: conditional binary operator expected
Similarly, I also get another error
scripts/trail.sh: line 37: conditional binary operator expected
Could you please let me know how can i run this bash script or trail.

Hi, we did not test TRAIL on MacOS. I suggest you try it first on a linux machine.

Thank you for the response. Sorry I did not see it earlier.


Pusher http compatibility

It looks like there's some incompatibilities with the pusher/echo client.
Above is trying to make a POST request to the url, however only GET & HEAD is allowed

That makes sense (probably should be in the docs though?)
For some reason the websocket connection is indeed not established on the server (works fine locally)
websockets:serve command shows no output whatsoever (except for the listening message), firewall is open, SELinux set correctly; tried permissive & firewall off just to be sure; any ideas what might be causing it?
(using apache + let's encrypt, ports & hosts set correctly; ssl config (in config/websockets.php) contains the local_cert)

Yeah that should be in the docs (considering the many issues about it...).
That can have a million reasons really :)
Make sure you are using the certificate files (https://github.com/beyondcode/laravel-websockets/issues/92#issuecomment-455192084) this bit a few people already and also you have both the local cert and pk config option set.
If certificate is all good check if there are any message in the developer console of the browser that might give some insight in could be breaking.
If there is no output at all in your browser console make sure you are not using a port that is not allowed by the browser (more about that here: https://alex.bouma.me/installing-laravel-websockets-on-forge/#a-note-about-ports).

looks like my firewall was really acting up, opening port 6001 & disabling the firewall didn't seem to have been applied. so it's no longer timing out (thanks good old telnet for discovering that 😅 )
However, still no errors whatsoever, but it's cancelling out instead 😅
Note: as webmin generates the let's encrypt certificates, I don't have a "fullchain" as per the linked comment; however Let's Encrypt should be a recognized CA so I'm not sure if related. (and without logs/errors it's very hard to debug)

Looking at this it does still look like a certificate error: https://stackoverflow.com/questions/31664366/chrome-failing-to-connect-to-websocket-server-opcode-1-handshake-was-cancele. I don't think you need to do anything the accepted answer says, but do need to make sure the certificate is correct.
Maybe you could try to create your own fullchain.pem combining the contents of letsencrypt-cert.pem, letsencrypt-ca.pem (in that order), however it does look like /etc/letsencrypt/live/ could contain your domain name as folder and could have the fullchain.pem file inside of there looking at webmin threads.
There is currently no error if you supply an invalid or incomplete certificate (https://github.com/beyondcode/laravel-websockets/issues/92#issuecomment-455564110) so that definitely doesn't help, but of a hit and miss right now :)

Running the concatenationin a cron should help with that (you need to restart your websocket server each the the certificate changes anyhow), but this is more a problem with webmin than this package I think (except the error reporting for an incorrectly configured certificate ofcourse).

The concatenated version ended up with a failed: Error in connection establishment: net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH
and SSL_ERROR_NO_CYPHER_OVERLAP on firefox
further investigations lead me... nowhere 😅
I'll create a cert using certbot for l-w I guess.
Either way, I do believe having an option to include the intermediate certificates as a parameter instead of requiring to provide a combined file would be a more lenient solution; there's several CA's that don't provide a combined file, similar to what apache requires

Above is a working configuration, to combine them I tried
cat letsencrypt-cert.pem letsencrypt-ca.pem > letsencrypt-combined.pem
along with the pk defined separately and
cat letsencrypt-key.pem letsencrypt-cert.pem letsencrypt-ca.pem > letsencrypt-combined.pem
with no success
Thanks for the help so far, the issue might be broader than this package indeed; though I do believe if the configuration works for apache it should arguably work out for this too.

Now I'm all out of ideas too, great problem! If you do find something it would be really useful to leave here or PR a documentation change to include your findings!

Thanks for the help so far, the issue might be broader than this package indeed; though I do believe if the configuration works for apache it should arguably work out for this too.

Well the current config for this package works for NGINX, so I guess arguments could be made for every server software that handles SSL just a bit differently (don't even get me started about IIS).
As a general note, I would always place your websockets server behind a reverse proxy like NGINX (or I believe Apache can do the same) so the websockets server doesn't have to handle SSL at all and offload those CPU cycles to more competent and faster applications designed for that work, this way you also don't have to worry about restarting your websockets server when a certificate or config changes but restarting the proxy server (be it Apache or NGINX) is enough. This also has the benefit if your app being able to speak in plain text to the websockets server making it slightly faster. For inspiration: I wrote this blog for Forge & NGINX, that might give you some ideas on how to replicate it for Apache if you want to go that route.

Hello @jlsjonas .
I have this problem with laravel websockets and it has taken my time. I still get this error on web browser and I don't know what must be changed. can you help me fix this problem by explaining more about your solution?
Here is my error.

WebSocket connection to 'wss://domain:6001/app/ABCDEFG?protocol=7&client=js&version=4.3.1&flash=false' failed: Error in connection establishment: net::ERR_SSL_VERSION_OR_CIPHER_MISMATCH
I will send my configs if you need.


Mobile version

Make a mobile version of the editor. Might be nice when using a tablet?

Sonias Notes:

Button-press animation isn’t really necessary for mobile version (takes a long time and is delayed)
Waveform size is inconsistent across browsers in mobile (very small in Firefox, larger in Chrome) but not in desktop versions (Firefox, Edge/Chrome)
Firefox:

“Generating waveform” initially, then shows “Waveform could not be generated” for a short time before the waveform actually does appear

(Chrome produced waveform much more quickly, but still had the same “could not be produced” message before the waveform eventually appeared)

Long button press (hold and release) leads to “held-down” button and no action (e.g. holding down ‘cut’ does not cut that segment)


Oracle stored procedure

Excuse me, How to obtain the output parameters of the Oracle stored procedure?

go's database/sql driver can't provide way to output something into user app.
#55
So you need to insert into temporary table.

Thank you very much your answer

cc @mattn
output parameter bindig is implemented at branch djadala,
https://github.com/djadala/go-oci8/tree/djadala
but it is based on old version of go-oci8.
Someone must port to last version.
Sorry for bad git history, you must inspect only last (may be 10) commits.
Itself output binding require go1.8+ , see file go18.go, and is based on simple concept of binding pointers, only integers, strings & bools are supported.
regards,
Djadala

Is this now good with adding of SQL out? Can this be closed?

@mattn Close this?


[pt] Localize otel-localized announcement page to Portuguese (Brazil)

Waiting for #4996 to be merged.
Add localization for annoucement page for OTel localization.
Issue: https://github.com/open-telemetry/opentelemetry.io/issues/4922 and https://github.com/open-telemetry/opentelemetry.io/issues/4863

@pedroespindula The announcement should go live today ideally. Could you have a look at the feedback please?

@pedroespindula The announcement should go live today ideally. Could you have a look at the feedback please?

Hi. This PR will need to be rebased, have conflicts resolved, and then force-pushed.

Hey, @theletterf and @chalin!
Thanks for the heads up! I have updated the PR according to the feedbacks and rebased the PR. Also, I made the PR Ready for Review.
Also, thanks for the review @lgfa29!
Cc: @edsoncelio

LGTM 🆗
Parabéns pela iniciativa @pedroespindula 👏

/fix:format

@open-telemetry/docs-pt-approvers - please (GH) approve

@emdneto

@open-telemetry/docs-maintainers - any idea why @open-telemetry/docs-pt-approvers / maintainers isn't a choice in the Reviewers request dropdown?

Merging on @emdneto's approval.


Is it possible to set the pin mode of the DHT22 pin?

Is it possible to set the pinMode for the pin used by SimpleDHT to use the internal pullup?
Also, is the internal pullup enough for the DHT22? (I looked at what datasheets I could find, but, didn't see any specification. )

#36


Compile to WASM

Go can compile to WASM (GOOS=js GOARCH=wasm), and WASM can be packaged into images and executed on K8s clusters using krustlet: https://developer.okta.com/blog/2022/01/28/webassembly-on-kubernetes-with-rust
So, maybe ko can build a WASM executable, and put it in a multiarch image, alongside the other ko-built archs.
This wouldn't work for Go executables that need to call into their base images (I don't think WASM images have multiple layers, and the environment isn't very linux-ey...yet?), but it should mostly maybe kinda work if they're just static binaries, which is exactly ko's sweet spot.
An example WASM image that kruslet can apparently run: https://explore.ggcr.dev/?image=webassembly.azurecr.io%2Fhello-wasm%3Av1 -- note media types and the annotation.
Questions:

What OCI platform does kruslet expect when it's given a multiplatform image? js/wasm?

How should users express this? ko build ./ --wasm to additionally produce a WASM image in the index?

What OCI platform does kruslet expect when it's given a multiplatform image? js/wasm?

Kruslet doesn't appear to support pulling from indexes at all, only OCI artifacts with the WASM media types. So this is probably not going to be something worth shoehorning into ko.
This might still make sense as a separate Go-specific pipeline for building WASM images, a la wasm-to-oci with fewer steps, but it won't coexist alongside regular OCI images.

Reopening as I still think this is an idea worth pulling on.

cf: Istio's WASM plugins are also packaged as OCI images (building tutorial, spec)
TL;DR: In this case, the format seems to be:

the image must be a single-arch OCI image (not index)
the image must contain one layer
the layer must contain a file named plugin.wasm (entrypoint is ignored)
and optionally a runtime-config.json

This seems fine for Istio, there's not a lot of use cases for multi-platform WASM and non-WASM plugins there I think, but it's something to consider as folks have gone down this path before and made certain decisions.

ref: Similar discussion in buildpacks, to allow buildpacks to run and produce a wasm image instead of the standard OCI image: https://github.com/buildpacks/lifecycle/issues/820
In this case, it would be either-or, and buildpacks wouldn't create a single multi-platform index containing the wasm image and the standard linux/amd64 (e.g.) image. But maybe if that was supported somewhere, they could.


[HashLink] Explicit cast from the OpenGLRenderer class

While I was debugging my project, I got a crash telling me that a FloatVector was getting casted to i32, which I don't really understand?
Here is the crash log:

This seems to only happen on the HashLink target.
What do?

I would guess that i32 means Int. So something seems to be trying to cast Vector<Float> to Int, for some reason.
It seems to be related to drawing graphics, so you might try commenting out some of your code with drawing commands to see if you can narrow it down. Like graphics.drawRect() or graphics.lineTo(), etc.

Thanks, I'll check it out.


Check YAML files if any

Run yamllint to check and score all YAML files in the repository.

Is it worth for this project?

A Python project could be using YAML for its configuration, so I thought so. However, since we have already closed the issue about shell scripts (which are more likely to be used), I think we should close this one as well.


Display chapters on tvOS using custom overlays?

We can probably display chapters at the bottom using custom overlays (accessible with the dedicated button on the left).

Also see #249.


RangeError: invalid string length

Trying to save a *.hpp file and getting this error every time:
RangeError: Invalid string length
    at Object.stringify (native)
    at /Users/vision/.atom/packages/linter/lib/validate.coffee:53:25
    at Array.forEach (native)
    at Object.module.exports.Validate.messages (/Users/vision/.atom/packages/linter/lib/validate.coffee:27:14)
    at MessageRegistry.set (/Users/vision/.atom/packages/linter/lib/message-registry.js:36:16)
    at /Users/vision/.atom/packages/linter/lib/linter.coffee:35:17
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:125:28)
    at /Users/vision/.atom/packages/linter/lib/indie-registry.js:27:20
    at Function.module.exports.Emitter.simpleDispatch (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:25:14)
    at Emitter.module.exports.Emitter.emit (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/event-kit/lib/emitter.js:125:28)
    at Indie.setMessages (/Users/vision/.atom/packages/linter/lib/indie.js:15:18)
    at /Users/vision/.atom/packages/linter-gcc/lib/main.js:75:35

Could you open the developer console with Ctrl+Shift+I, copy the linter-gcc command, paste it into a terminal, run it, and post the output here?

Command output as requested:
21:10:23 ~ >/usr/bin/g++ -c -Wall -std=c++11 -fmax-errors=0 /Users/vision/git/sim/lib/rocket.hpp clang: warning: argument unused during compilation: '-fmax-errors=0'
The error has also become intermittent, but I can change the file by just adding or removing an empty line and resaving and it may or may not happen again.

Restarting Atom also makes the error go away for a while, but it comes back after working for some period of time.

I am concerned that your code is generating an error message that is just too long for linter to handle, a template error perhaps? Are you happy to post a sample of your C++ code so I can test it?

Same bug here, quite often :/
I got it with C code, not C++. And gcc isn't showing any error while compiling the file with the same command-line than linter-gcc.

Ok. Let me try to reproduce the error and I will post a fix asap.

Could someone give me a code sample that's causing the error?

When i have the error, reopening atom is usually enough to not having it again. So giving you a code that's causing the error will not be helpfull, as it will not cause the error on your side.

This is very strange. I thought it was related to the error messages being very long, but it looks like that's not the case. I've deliberately linted source files that generate long error messages and everything works fine.

Having some news : when the "invalid string length" bug occurs, the errors pops every time i'm saving a file even if it's not the file that caused the error, and even if the file doesn't have any error.

I'm having the same issue, any update on this?  It only started to occur after I upgraded atom to 1.5.3.  I've also kept up to date on linter-gcc, and it started breaking just today, so it must have been in a recent update that it started happening.

I have the same problem. After few hours of code writing i got long error. New errors come when i press Command-S to save(and lint) project. After I relaunch Atom, no errors, but after some time I have same errors. I have no errors if I disable or remove linter-gcc.
My project:
https://github.com/XSmile2008/BigTrackArduino

I got the error 4 times in a hour now, it's very frustrating :s
Is there a solution yet ?

Hello all. I think I have identified the problem. Need to play some more to make sure it's fixed. The issue seems to be that atom reports the settings tab as an 'editor' as well. I need to make sure that linter-gcc doesn't try to lint it when that happens.

Ok it seems the editor problem is secondary. The main issue is that linter stringifies its messages using JSON.stringify in the latest release here. This problem is not present in the latest commit, however, so all we need is for the latest commit to be published as a release.
@steelbrain could you help us here? Are you planning on publishing a new release soon?

I am planning on publishing a new release soon but the workaround should work well for you, the only penalty should be performance and even that won't be anything major, worst case scenario you miss a frame which isn't too bad for a workaround IMHO

Sounds good. Workaround details:

Open Atom's package manager, find the linter package
Click Settings, then View Code
Open the file lib/validate.coffee
Goto line 53:

result.key = JSON.stringify(result)

Add the following line immediately before it:

result.key = null

Save the file, and restart Atom.

Let me know if the workaround fixes the problem. Once the new version of linter is released, this issue will be fixed.

This is not really the workaround, the workaround I suggested should be done by the providers and not the end users themselves, I suggested JSON.parse(JSON.stringify(messages))
Another approach to solve this would be to solve only the text instead of message objects and then do
const messages = []
for (const message of this.errors) {
  messages.push({type: 'Error', text: message.text, range: message.range})
}

@steelbrain but the issue is that the base linter does the stringification, not linter-gcc. linter-gcc simply passes the messages to linter. Any ideas as to how to work around this problem?

Change this line to module.exports.linter_gcc.setMessages(JSON.parse(JSON.stringify(require("./utility").flattenHash(module.exports.messages))));

@steelbrain thanks for the help. The workaround has been implemented. Please update linter-gcc.

A friend of mine just got the error again :s He's on 0.6.8 update !

Has he restarted Atom? A restart is necessary to reload the package.

I have run tests with the BigTrackArduino project, and the issue before was that one of the message objects passed to linter would grow in size if you opened more than one file. This could continue until the object was too big for node to handle. Now, the size of all objects remains the same no matter how many files you open/save.

Ah maybe not, he can't remember ! Indeed, i don't have the error now ^^
Thanks for the patch !

No problem. Glad it's all working again. I will update linter-gcc again once linter has been updated.


Improvement: Refactor Flask Backend for Maintainability

The current implementation of the Flask backend has grown large and disorganized while resolving various issues and adding features. To improve maintainability and readability, a comprehensive refactor is necessary. This aims to encapsulate responsibilities into dedicated classes and remove redundant code.
Objectives:

Add a VideoProcessor class to encapsulate video download and processing logic.
Move methods like download_youtube_video(), and process_video_with_cpp() into the new VideoProcessor class. Rename methods for clarity, e.g. download_youtube_video() should be download_media().
Add a Utils class to encapsulate repeated operations, for file paths, sanitization, and cleanup.
Improve overall readability of the Flask application, by moving larger functionality into dedicated modules/classes.

Note: The primary goal here is to improve maintainability. Feel free to add suggestions or ideas for further modularizing the code if you notice other areas that could benefit from this effort.

"Would love to work on this, could you assign it to me?"

Hi @VarunParab, thanks for your interest!
I've assigned the issue to you. Resolving this will unblock several other issues, so many thanks for taking it on!
If you'd like to discuss any details as you work through it, please don't hesitate to reach out.

Hi @omeryusufyagci, I've submitted a pull request addressing the issue. Please let me know if any further changes or clarifications are needed. Looking forward to your feedback!


Update VerifyAttestation logic

Update VerifyAttestation to ignore pubkey if cert exists
Update hash validation on the signing hash algorithm in VerifyQuote
Signed-off-by: Jiankun Lu<EMAIL_ADDRESS>

LGTM


Nice!

Just wanted to drop-in and say thanks for this, it's a nice idea :-)
Keep up the good!

Hey @lirantal! Thanks for the kind words! Appreciate the enthusiasm. 👍 😄


Oculus Touch controllers disabled on startup (Oculus rift cv1)

Hi there,
When the game starts, the main screen show up without the touch controllers being responsive.  I can't pick anything on the menu, no lasers beam show up.  The only buttons that reacts are the system menu and home button.
The only in-game action that works is quitting the game.
I followed the guide, ran the install of Vortex (fresh, no QModManager to clear out), BepInEx for Subnautica and finally unzipped the content of the SubmersedVR file into my game folder.
I have 2 log files for you:
LogOutput1.log
LogOutput2.log
LogOutput1.log: I started the game from the Steam Library after having set the advanced option "-vrmode openvr"
LogOutput1.log: 2nd try, still with the advanced option set to "-vrmode openvr" but this time I loaded up the SteamVR Home and started the game from there.
I noticed a warning msg in the logs:
[Warning:SubmersedVR] Game was not started in VR. Don't load and apply SubmersedVR patches.
That seems to indicate that the BepInEx and SubmersedVR install were successful but some config element prevents the game from being considered "started from VR"...
When I somehow managed to run the game in normal mode from whithin my VR headset (don't ask me how I pulled that one off!), I could use the controllers a bit and the fire was visible (which is nice) but I could not move using the thumbsticks and neither could I access the PDA so I figured that was not a good idea.
Keep me posted and thank you very much for your efforts.
I love the game and find it over-the-top immersive in VR so I'm not really interested in playing it in normal mode.
However, running the game without your mod means no save game at all which is not a practical solution.

Yeah, the mod is still not getting loaded. Make sure you start the game in VR Mode. The logs don't give me more information unfortunately. It should do that when you launch from the dashboard so not sure why its not.
Also I never used Vortex tbh, just installed BepInEx and the mod like described in the README.
You should choose the second option when starting the game:

If you remembered it previously you can change it by clicking on the game and change the launch options there:

Thanks!
I did both of these before reporting the issue but I'll give it another shot.
Another thing I noticed:   On my setup, the Oculus apps has to be up-and-running for SteamVR to detect the deadset.
I don't know if that would be a problem for the mod.

Hey there again,
I found this article on the net in Unity forums.

Is it possible that the latest Steam or Oculus drivers does not support the flag your mod use to evaluate if the HMD is up-and-running?
What's the new XR SDK plug-in system?
Does it somewhat reflects that the old ways of handling XR have been made obsolete?


An option to add a SharePoint Framework Web Part as a Tab

Describe the solution you'd like
I would like to have the option to specify a SharePoint Framework web part as an alternate option for a tab (or as a new tab option)

Added in 2.8.0


Pose Landmarker Jittering

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
No
OS Platform and Distribution
Mac OS X 13.0.1
MediaPipe Tasks SDK version
0.10.0
Task name (e.g. Image classification, Gesture recognition etc.)
Pose Landmark Detection
Programming Language and version (e.g. C++, Python, Java)
Javascript
Describe the actual behavior
I have switched over from the legacy mediapipe library to the new mediapipe solutions. The landmarks are jittering more than expected when I use the VIDEO runningMode on GPU or CPU with any of the pose_landmarker tasks.

Describe the expected behaviour
The legacy mediapipe pose estimation detection offered a smoothing parameter (smoothLandmarks) to reduce the jittering, which worked quite well. I have not been able to find this option in the new mediapipe solutions library.

Standalone code/steps you may have used to try to get what you need
The jittering can be observed on the official mediapipe solutions demo page:

https://mediapipe-studio.webapps.google.com/demo/pose_landmarker

Other info / Complete Logs
Here is my sample code to instantiate the PoseLandmarker:

const vision = await FilesetResolver.forVisionTasks(
    // path/to/wasm/root
    "https://cdn.jsdelivr.net/npm/@mediapipe/tasks-vision@latest/wasm"
  );
  window.poseLandmarker = await PoseLandmarker.createFromOptions(
    vision,
    {
      baseOptions: {
        modelAssetPath: `/models/pose_landmarker_${model_type}.task`,
        delegate: "GPU",
      },
      runningMode: "VIDEO"
    }
  );

@scottxp,
Could you please elaborate your query with complete details and if you can share any captured jitter image to understand the issue better?

I am encountering a similar issue in Python.
It seems that there is no landmarks smoothing in the mediapipe v0.10.1
In the following two videos we can see the effect.
The video that uses mediapipe 0.10.1 the landmarks jitter a lot more than in the second video, which uses mediapipe 0.8.11.
The videos are basically a single image that is fed to the mediapipe solution and task in a loop.
The same effect also happens when using webcam.
https://github.com/google/mediapipe/assets/16905449/02381e1a-0514-41a9-81e0-20f6a6eeeced
https://github.com/google/mediapipe/assets/16905449/2310a792-dfd0-450d-a9ec-689ba28f7682
My assumption is that the difference lies in the graph that is used in pose estimation.
In version 0.8.11 it uses the following graph that has a smoothing calculator: https://github.com/google/mediapipe/blob/release/mediapipe/modules/pose_landmark/pose_landmark_cpu.pbtxt#L216
While in 0.10.1 it builds a different graph that basically contains PoseLandmarkerGraph calculator and a FlowLimiterCalculator. The PoseLandmarkerGraph calculator consists of two sub graphs, that I assume don't have any smoothing calculator in them.
https://github.com/google/mediapipe/blob/91a3c54d558af8c4a0807d2bdd47e875a3c1e87a/mediapipe/tasks/cc/vision/pose_landmarker/pose_landmarker_graph.cc#L219
Maybe it would be possible to enhance the graph that is created in mediapipe 0.10.1, and add the smoothing calculator. I will try doing that, but I'm not sure if the input and output streams will be compatible.

https://github.com/google/mediapipe/assets/879510/cd51f61e-5f96-48a5-9685-f6e04bdcf435
LEFT<EMAIL_ADDRESS>RIGHT<EMAIL_ADDRESS>As described by @igorbasko01, there does not appear to be any landmark smoothing in mediapipe 0.10.1. You can see the jittering landmarks in the video on the left while the video on the right does not jitter. These were captured and processed simultaneously using the same webcam stream but different mediapipe libraries.
Here is the code for the video on the LEFT:
const vision = await FilesetResolver.forVisionTasks(
  "https://cdn.jsdelivr.net/npm/@mediapipe/tasks-vision@latest/wasm"
);
window.poseLandmarker = await PoseLandmarker.createFromOptions(
  vision,
  {
    baseOptions: {
      modelAssetPath: "/models/pose_landmarker_full.task",
      delegate: "GPU",
    },
    runningMode: "VIDEO"
  }
);

And here is the code for the video on the RIGHT:
window.poseDetector = await poseDetection.createDetector("BlazePose", {
      runtime: "tfjs",
      enableSmoothing: true,
      modelType: "full",
      solutionPath = 'https://cdn.jsdelivr.net/npm/@mediapipe/pose'
});

I have attempted to implement a Python version of the OneEuroFilter, closely modeled after the C++ version found at this mediapipe implementation: https://github.com/google/mediapipe/blob/bed624f3b6f7ad5d25b5474c516561c537f10199/mediapipe/util/filtering/one_euro_filter.cc#L14
I've also replicated the same parameters for this Python OneEuroFilter, including setting the frequency to 30, which corresponds to the number of frames per second (FPS). I used the parameters that can be seen here: https://github.com/google/mediapipe/blob/c8c5f3d062f441eb37738c789a3550e7280ebefe/mediapipe/modules/pose_landmark/pose_landmark_filtering.pbtxt#L115
During the callback, I apply this filter to the Normalized Landmarks of the PoseLandmarkerResult. Notably, I created a distinct filter for each axis of each landmark.
Unfortunately, the jittering issue seems to persist, and I'm unable to observe any significant improvements.
For a closer look, you can find my Python filter implementation and usage in this gist: https://gist.github.com/igorbasko01/c51980df0ce9a516c8bcc4ff8e039eb7
I would greatly appreciate any help in addressing this issue or any advice on potential workarounds.

Pose landmarking is not implemented yet according to the C++ Source Code:
https://github.com/google/mediapipe/blob/df3f4167aed857c891395b4bab851a8a4f8024f8/mediapipe/tasks/cc/vision/pose_landmarker/pose_landmarker_graph.cc#L312
That being said, there is a new MultiWorldLandmarksSmoothingCalculator in the code, it's just not used anywhere yet:
https://github.com/google/mediapipe/blob/df3f4167aed857c891395b4bab851a8a4f8024f8/mediapipe/calculators/util/multi_world_landmarks_smoothing_calculator.h#L57
Assuming it's functional, it might be possible to plug in the landmarks from the pose landmarker graph to get the smoothed landmarks, at least in C++.

Hey @Silverlan
Thanks for the suggestion !
Can you please elaborate a bit more on what exactly did you do, and how did you add the MultiWorldLandmarksSmoothingCalculator.

Hey @Silverlan Thanks for the suggestion ! Can you please elaborate a bit more on what exactly did you do, and how did you add the MultiWorldLandmarksSmoothingCalculator.

I use the C++ API. I can describe my steps, but I don't know the approach for the other APIs.

Added //mediapipe/calculators/util:multi_world_landmarks_smoothing_calculator as dependency to my project so I can use the MultiWorldLandmarksSmoothingCalculator calculator.
Added the MultiWorldLandmarksSmoothingCalculator calculator to my graph with the one_euro filter (velocity filter did not work for me):

{
auto& smoothCalculator = graph.AddNode(
"MultiWorldLandmarksSmoothingCalculator");
auto* options = &smoothCalculator.GetOptions<mediapipe::LandmarksSmoothingCalculatorOptions>();

auto* filter = options->mutable_one_euro_filter();
filter->set_beta(smoothingFilterSettings.beta);
filter->set_disable_value_scaling(smoothingFilterSettings.disableValueScaling);
filter->set_frequency(smoothingFilterSettings.frequency);
filter->set_min_cutoff(smoothingFilterSettings.minCutoff);
filter->set_derivate_cutoff(smoothingFilterSettings.derivateCutoff);
filter->set_min_allowed_object_scale(smoothingFilterSettings.minAllowedObjectScale);

worldLandmarks >>
smoothCalculator.In("LANDMARKS");
trackingIdsInput >>
smoothCalculator.In("TRACKING_IDS");
smoothCalculator.Out("FILTERED_LANDMARKS").SetName(outputName) >>
graph[::mediapipe::api2::Output< std::vector<mediapipe::LandmarkList>>(graphOutputName)];
}

Make sure to add this node after the PoseLandmarkerGraph (or HandLandmarkerGraph) node. Then use the WORLD_LANDMARKS output of the PoseLandmarkerGraph for the LANDMARKS input of the MultiWorldLandmarksSmoothingCalculator node.

For the TRACKING_IDS input you have to create a std::vector<int64_t> with the exact same size as the number of poses. I just have one pose, so I just initialized it with std::vector<int64_t> trackingIds {0}, then you can use that as input:

std::vector<int64_t> trackingIds = { 0 };
auto packetTrackingIds = mediapipe::MakePacket<std::vector<int64_t>>(trackingIds);

The one_euro filter properties are critical, with the default settings I didn't notice any reduction in jitter at all. The values below worked for me:

smoothingFilterSettings.beta = 10.0
smoothingFilterSettings.minCutoff = 0.05
smoothingFilterSettings.derivateCutoff = 1
smoothingFilterSettings.disableValueScaling = false
smoothingFilterSettings.frequency = 30.0
smoothingFilterSettings.minAllowedObjectScale = 1e-0

You'll probably have to tweak them and play around with them though.

It won't work without this step:
You have to set a timestamp for all input packets:

auto msTime = cap.get(cv::CAP_PROP_POS_MSEC); // Time in miliseconds
auto mcTime = msTime *1000.f; // Time in microseconds

auto packetImg = mediapipe::MakePacket<mediapipe::Image>(*image);
packetImg = packetImg.At(mediapipe::Timestamp(mcTime));

auto packetArea = mediapipe::MakePacket<mediapipe::NormalizedRect>(MakeNormRect(0.5, 0.5, 1.0, 1.0, 0));
packetArea = packetArea.At(mediapipe::Timestamp(mcTime));

std::vector<int64_t> trackingIds = { 0 };
auto packetTrackingIds = mediapipe::MakePacket<std::vector<int64_t>>(trackingIds);
packetTrackingIds = packetTrackingIds.At(mediapipe::Timestamp(mcTime));

auto outputPackets = taskRunner.Process(
{ {"image", packetImg},

{"norm_rect",packetArea},

{"tracking_ids",packetTrackingIds}
});

The FILTERED_LANDMARKS output of the MultiWorldLandmarksSmoothingCalculator node is your smoothed world landmarks.

Source Code:
https://github.com/Silverlan/mediapipe_pragma_wrapper/blob/5d75a9cb7b6647522d33a8e2d8a30d82ad2b5dff/mediapipe/examples/desktop/mediapipe_pragma_wrapper/mediapipe_pragma_wrapper.cc#L645
Hope that helps!

Thanks a lot @Silverlan
I will try and use your example and see if I can also use it in Python.

@scottxp,
Could you please confirm that this is still an issue or it has been resolved from your end. Thank you!

@igor-basko I would be very interested in your python fix for this issue.

@kuaashish This is still an issue for me using the javascript library.

still an issue for me (android&python)

this is still an issue, confirmed on the javascript library

still an issue Ubuntu Python

Has anyone made any progress on a python solution that removed the jitter?

@scottxp,
We are pleased to announce the release of the latest version of MediaPipe, version 0.10.7, which addresses the jittering issue observed in the Pose Landmarker.
This issue has been documented in the release notes under "Fixed Pose Landmarker jittering issue." We kindly request you to build using this updated version and inform us of any persisting issues from your perspective. Thank you

@kuaashish this is not doing anything different in JavaScript with version 0.10.7:
await PoseLandmarker.createFromOptions(vision, {
            baseOptions: {
                modelAssetPath: 'https://storage.googleapis.com/mediapipe-models/pose_landmarker/pose_landmarker_lite/float16/latest/pose_landmarker_lite.task',
                delegate: "GPU"
            },
            runningMode: "VIDEO",
            smoothLandmarks: true,
            numPoses: 1
        });

In python mediapipe 0.10.7 it seems to work when i use runningMode VIDEO and use the detector.detect_for_video function but in JavaScript with runningMode VIDEO and poseLandmarker.detectForVideo is still jittering

checked affirmative, jitter in JavaScript still persist, regardless in runningMode VIDEO or LIVE_STREAM

I confirm the problem is still there
Until the problem is fixed I am using smoothing on my side, proposed by chatgpt: https://gist.github.com/mupakoz/c7b3183914b52a08eebbc61599af7e1b
@npinochet @yiucheung0512 @WiCanIsCool @scottxp maybe it helps you

The jittering issue has long been a problem and I hope they can fix this so we can use it in motion capture.  I just ran accross a possible solution for the javascript version, but I have not tried it yet. https://github.com/yousufkalim/mediapipe-pose-smooth

It's not the landmarker models - it is the single shot detector of the pipeline. @igor-basko, @Silverlan you can prove this by feeding looped image video frames directly through the face_mesh landmarker models.
The BlazeFace detectors return detection box non-reliably - they will return deviating boxes each frame on loopt image.
The issue must be fixed on model level. BlazeFace detector is "blazingly" fast, taking 2ms on edge devices, and it returns several landmarks as well. The issue must be fixed at that or landmarker level - no amount of messing with kalman filters will help post-recognition.

This seems solved with version 0.10.9

I have the same problem on android.
I am working with NextJS 14 and this is my current version: "@mediapipe/tasks-vision": "^0.10.9",
This is how I create the PoseLandmarker:
export const loadPoseLandmarkerModel = async (): Promise<Uint8Array> => {
    const response = await fetch(`/static/models/pose_landmarker_lite.task`);
    if (!response.ok) {
        throw new Error(`Failed to load pose landmarker model file: ${response.statusText}`);
    }
    const buffer = await response.arrayBuffer();
    return new Uint8Array(buffer);
};

export const createPoseLandmarker = async (runningMode: "VIDEO" | "IMAGE"): Promise<PoseLandmarker | null> => {
    const vision = await FilesetResolver.forVisionTasks(
        "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>    );

    const model = await loadPoseLandmarkerModel();

    return PoseLandmarker.createFromOptions(vision, {
        baseOptions: {
            modelAssetBuffer: model,
            delegate: "GPU",
        },
        runningMode: runningMode,
        numPoses: 1,
    });
};

Here is the result on Android:
https://github.com/google/mediapipe/assets/91951421/552b4f84-0893-4af2-91c0-e5e5d5d60eda
Am I doing something wrong?

Hello, try 0.10.9 like below
https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>

Also check out MediaPipe version number on your package.json

The following code works for me.
import { FilesetResolver, PoseLandmarker } from "@mediapipe/tasks-vision";

export const createPoseLandmarker = async (runningMode: "VIDEO" | "IMAGE"): Promise<PoseLandmarker | null> => {
    const vision = await FilesetResolver.forVisionTasks(
        "https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>    );

    const poseLandmarker = await PoseLandmarker.createFromModelPath(
        vision,
        "https://storage.googleapis.com/mediapipe-models/pose_landmarker/pose_landmarker_lite/float16/1/pose_landmarker_lite.task"
    );

    await poseLandmarker.setOptions({
        runningMode: runningMode,
        numPoses: 1,
    });

    return poseLandmarker;
};

I updated the link: https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>(like @hiroMTB suggested)
Removed the delegate: "GPU"

On the last point I did some tests and the result was that when the delegate prop has "GPU" the tracking is not optimal and is jittering a lot and when I remove the prop is working fine.
I also receive this exception on initialization:

In the end is working fine, a bit slower than on my iOS device but it's getting the job done!
Thanks a lot for the help!

Grad it helped.
GPU inference works fine on my side but I'm on macOS chrome. Maybe try clearing cache. I also see a mysterious error around delegate option and it appears and disappears depends on the day.

I tested it with mediapipe==0.10.9 on Python (Windows). It jitters a lot less than version 0.10.1.
But I think that it still jitters a bit more than in the 0.8.11 version. You can see the comparison in the previous comment:
https://github.com/google/mediapipe/issues/4507#issuecomment-1600617343
https://github.com/google/mediapipe/assets/16905449/d87fb441-b60e-4bd2-ac09-da5473b4c74d

@igorbasko01, try a movie
The jitter with Python versions still exists both from the landmarker and detector. It seems they updated the detector so the larger jitter amplitudes are removed on static image, however there's still some on moving image from both.
Maybe someone can test the models used in graph standalone and see if jitter can be addressed separately for them for streaming application if mediapipe team is not interested in bringing those into open source solutions?

I have attempted to implement a Python version of the OneEuroFilter, closely modeled after the C++ version found at this mediapipe implementation: https://github.com/google/mediapipe/blob/bed624f3b6f7ad5d25b5474c516561c537f10199/mediapipe/util/filtering/one_euro_filter.cc#L14
I've also replicated the same parameters for this Python OneEuroFilter, including setting the frequency to 30, which corresponds to the number of frames per second (FPS). I used the parameters that can be seen here: https://github.com/google/mediapipe/blob/c8c5f3d062f441eb37738c789a3550e7280ebefe/mediapipe/modules/pose_landmark/pose_landmark_filtering.pbtxt#L115
During the callback, I apply this filter to the Normalized Landmarks of the PoseLandmarkerResult. Notably, I created a distinct filter for each axis of each landmark.
Unfortunately, the jittering issue seems to persist, and I'm unable to observe any significant improvements.
For a closer look, you can find my Python filter implementation and usage in this gist: https://gist.github.com/igorbasko01/c51980df0ce9a516c8bcc4ff8e039eb7
I would greatly appreciate any help in addressing this issue or any advice on potential workarounds.

@igor-basko01 Hi, if you don't mind, the code you've uploaded seems incomplete, do you mind uploading enough / the full codes used? I'm unable to get pose_landmarks_list[idx] as 'NormalizedLandmark' object is not iterable
Thanks!

Hey @Gnoot01
I've created a fully working example here: https://github.com/igorbasko01/mediapipe-jitter
Try using it instead of the gist.
Let me know if you have any issues with it.

@igorbasko01 Hi thanks so much for your quick response! Visually, I wasn't able to see it working to a great extent (if any) as well unfortunately, but to test it more quantitatively, I can suggest creating a stillness scorer by getting the euclidean distances of all points and plotting it. The stillness should be higher if the filter is working.
An example: https://towardsdatascience.com/towards-a-more-applicative-pose-estimation-bf18bc311228

Holistic_landmark could be an option, it still uses the legacy model with smoothing. The main concern is the performance overhead of detecting hands/face/pose together.
FilesetResolver.forVisionTasks("https://cdn.jsdelivr.net/npm/@mediapipe/tasks-vision@0.10.15/wasm").then(
      async (vision) => {
        holisticLandmarkerRef.current = await HolisticLandmarker.createFromOptions(vision, {
          baseOptions: {
            modelAssetPath:
              "https://storage.googleapis.com/mediapipe-models/holistic_landmarker/holistic_landmarker/float16/latest/holistic_landmarker.task",
            delegate: "GPU",
          },

          runningMode: "VIDEO",
        })
    })


Refactor extract common logic in to Tablet::_get_segment_column_iterator

Proposed changes
extract common logic from Tablet::fetch_value_through_row_column, Tablet::fetch_value_by_rowids, Tablet::lookup_row_data to Tablet::_get_segment_column_iterator
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall


APP-3158: Update docstring

Ticket
APP-3158
Description
Update docstring
Dependencies
List the other pull requests that should be merged before/along this one.
Checklist

[ ] Referenced a ticket in the PR title and in the corresponding section
[ ] Filled properly the description and dependencies, if any
[ ] Unit tests updated or added
[ ] Docstrings added or updated
[ ] Updated the documentation in docs folder

Is there a way we can unit test this change?

My bad the change is just really about a comment so no unit test for that :)
But providing a bit of context for the change still stands (for instance just explaining that invoking resp = bot_client.get_stream_client().update_room(sid, kwargs=room_obj)
would not work and that the previous doc was misleading)


Refactor event formats

The events broadcasted by Telephonist.Event are currently really large tuples. It's generally considered a good practice to have tuples of no more than 3-4 elements, and there are several pushing 5.

This was fixed by #19.


Syntax error in ABAPGit Plugin

We cloned ABAPGit Plugins repository from Github to SAP system ITX and got syntax error in the plugin classes “Type "ZIF_ABAPGIT_DEFINITIONS" is unknown “. Refer attached docume
ABAPGit Plugin Issue.docx
nt.

closing, moved to https://github.com/larshp/abapGit/issues/1207

Its resolved. Thanks


fix: use finer-grained locking when listing releases for diff

isReleaseInstalled will call helm list which can take a bit of time. in order to allow parallelism, we need to use a finer mutex lock.

@steved Please fic DCO

@steved what's benifits when this PR be merged? thanks so much.

This really only becomes a problem with larger sets of releases, but with --skip-diff-on-install each release will be checked serially:
$ time ~/src/helmfile/helmfile apply --concurrency 4 --skip-deps --skip-diff-on-install
Listing releases matching ^sleep3$
Listing releases matching ^sleep2$
Listing releases matching ^sleep$
Listing releases matching ^sleep1$
sleep3	default  	12      	2024-02-13 15:46:46.306856 -0800 PST	deployed	sleep-0.0.0	0.0.0

sleep1	default  	12      	2024-02-13 15:46:46.305619 -0800 PST	deployed	sleep-0.0.0	0.0.0

sleep2	default  	12      	2024-02-13 15:46:46.303212 -0800 PST	deployed	sleep-0.0.0	0.0.0

sleep	default  	12      	2024-02-13 15:46:46.303146 -0800 PST	deployed	sleep-0.0.0	0.0.0

Comparing release=sleep, chart=sleep/
Comparing release=sleep1, chart=sleep/
Comparing release=sleep2, chart=sleep/
Comparing release=sleep3, chart=sleep/

real	0m1.456s
user	0m3.753s
sys	0m0.623s

$ helmfile --version && time helmfile apply --concurrency 4 --skip-deps --skip-diff-on-install
helmfile version 0.154.0
Listing releases matching ^sleep2$
sleep2	default  	12      	2024-02-13 15:46:46.303212 -0800 PST	deployed	sleep-0.0.0	0.0.0

Listing releases matching ^sleep$
sleep	default  	12      	2024-02-13 15:46:46.303146 -0800 PST	deployed	sleep-0.0.0	0.0.0

Listing releases matching ^sleep1$
sleep1	default  	12      	2024-02-13 15:46:46.305619 -0800 PST	deployed	sleep-0.0.0	0.0.0

Listing releases matching ^sleep3$
sleep3	default  	12      	2024-02-13 15:46:46.306856 -0800 PST	deployed	sleep-0.0.0	0.0.0

Comparing release=sleep, chart=sleep/
Comparing release=sleep1, chart=sleep/
Comparing release=sleep2, chart=sleep/
Comparing release=sleep3, chart=sleep/

real	0m1.392s
user	0m3.709s
sys	0m0.478s

@steved got it. thanks so much.


Added crossing orbits function to pykima

:tada:
Proposed changes
Added crossing orbits function to pykima
Types of changes

[x] New feature (non-breaking change which adds functionality)

Tests
Tested locally

Coverage remained the same at 0.0% when pulling c653abd5f2b500818a20d3a575ac8d0e5cf123f4 on Matt-Standing:crossing into 7f012e992bb5048370dbe510f3b34b0aab02fb5d on j-faria:master.

Coverage remained the same at 0.0% when pulling c653abd5f2b500818a20d3a575ac8d0e5cf123f4 on Matt-Standing:crossing into 7f012e992bb5048370dbe510f3b34b0aab02fb5d on j-faria:master.

Coverage remained the same at 0.0% when pulling c653abd5f2b500818a20d3a575ac8d0e5cf123f4 on Matt-Standing:crossing into 7f012e992bb5048370dbe510f3b34b0aab02fb5d on j-faria:master.

Thanks a lot, Matt! :tada:
I'll try to merge this and create a pykima script with this functionality.

This currently needs a bit more documentation, but I think the functionality is there


implement greenlock express into http server and cert service

No content

Issue created by BlueBubbles Bot in the BlueBubbles commnity on behalf of @zach in #android-requests.

This is not possible. Spent a handful of hours on it. Since we don't use port 80 or 443, we can't auto-gen certs


Add getRelated method.

Is your feature request related to a problem? Please describe.
There's no simple way to load in all related entities in Druxt.
Describe the solution you'd like
Add a getRelated method to the DruxtClient and DruxtStore
Use the JSON:API related endpoints.
Describe alternatives you've considered
N/A
Additional context
https://demo-api.druxtjs.org/en/jsonapi/node/article/e4ced3c1-e14b-48f1-8c0a-c909e808de68/field_tags

Above commits are incorrectly tagged :|

@d34dman Have you implemented a similar method with your drupal-js-dsk?

@Decipher not yet. And to be honest, didn't even plan this far yet.
Atm, am working on an architectural overhaul after some user feedback and difficulty in using the project. (Especially around state and session management).

No stress, just wanted to make sure not to duplicate effort.


[WIP] CI Test Coverage Calculation

Fixes: #845
Please let me know of any major conceptual errors.

I will work on fixing the test cases in a while.

I have created a new workflow for downloading the artifacts. These artifacts are uploaded in ci-test-local.yml and ci-test-ginko.yml. I am assuming ginko is the go lang tool used for creating the code coverage report. Please let me know if i need to make any further changes. I have signed the dco. @daemon1024

This makes a lot of sense. Thanks a lot!

Thank you! I have a lot to learn.

Hey @rahulk789, this looks good to me in general. But the coverage workflow didn't run for some reason. Can you check why is that the case?

I did notice that, I will work on it tomorrow.

No hurries! Appreciate you working on this and seeing it through 👌🏽

I am sorry for running the workflows so many times. Is there a way to check for syntax errors locally? Debugging has been a really hectic task for me. Sorry for the inconvenience again.

Can checkout https://github.com/nektos/act, but I am not sure if it would fulfill the usecase.
that said feel free to create PRs here and experiment no worries.

there's also https://github.com/rhysd/actionlint should be able to help with preliminary tests.

Thanks a lot! I will look into it.

Update:
I am still working on this, there seems to be a problem in downloading the artifacts from other workflows which is why the code coverage workflow isnt running (there was also a small problem in the wokrflow_run which i think i fixed.

Also one last thing you can try to check is to run it as part of the same workflow. As mentioned in https://about.codecov.io/blog/uploading-code-coverage-in-a-separate-job-on-github-actions/. If needed we can move the ginkgo tests as a seperate job in the same workflow.

Also one last thing you can try to check is to run it as part of the same workflow. As mentioned in https://about.codecov.io/blog/uploading-code-coverage-in-a-separate-job-on-github-actions/. If needed we can move the ginkgo tests as a seperate job in the same workflow.

This makes so much sense to me since wouldn't we save resources and time for testing by running both the tests on different runtimes in one go instead of multiple workflows creating separate runtimes?

Hey @rahulk789, Thanks for being persistent with working on this. This seems a bit complicated than expected.
Let's take a step back and try to do this in a different way. We should probably setup a seperate repo and experiment things there for faster feedback loop.
I would suggest

Setup a sample go repo.
Right 2 test suites
Run both test suites in different workflows.
Push the results to CodeCov.

See how we can manage the coverage accordingly. This is a bigger work item, it's fine if you want to work on something else. If you are interested I am happy to help out here if needed.
WDYT?

I am ready to do this, i shall link you the repo once i have made some progress, although it would take me some time.

I have been getting new silly errors. I will give you a ping once I'm done. I was wondering If it was okay to run ci-test-local and then run the ci-test-ginkgo workflow and finally run ci-test-coverage workflow  ( I really could not find documentation on running a workflow after 2 or more workflows have all completed. [Unlike the "needs" keywords in jobs which runs when all the given jobs are completed, in workflow_run , the "workflows" keyword starts the workflow after Any of the workflows are completed in the list of workflows and not after all are completed.] )
Thanks a lot for your patience.

https://github.com/rahulk789/codecoverage
working on this, getting silly errors, will get back when its done

https://github.com/kubearmor/KubeArmor/issues/845#issuecomment-1416655375

Working on this one. Please assign.


Issue: Export fails at "fetch URL contents"

Hi together,
I came across a strange bug. I followed this list here before posting: https://staticword.press/t/troubleshooting-failed-static-site-generation/25. I also looked for similar issues but found none.
The error:

It occurred after I changed the permalink settings from "Plain" (?p5 or something like this) to any other supported format.
Here is a screenshot from my Diagnostics page:

I'm running a WordPress 5.8 within a Docker container if that helps to debug. I have not set any optional Permalink settings (Category base, Tag base). I also deleted the WP2Static cache after changing the permalink settings. I'm running WP2Static with Version 7.1.7-dev I retrieved from Pete Wilcock's post about the WP2Static. Also here is a screenshot of my configuration:

Does anyone have an idea what might cause this issue? I'd be very grateful and thank you to everyone who takes the time to take a look at this :)
Best regards
Christoph

I've investigated further and could find one exeception:
PHP Fatal error: Uncaught WP2StaticGuzzleHttp\\Exception\\ClientException: Client error:GET http://wordpress.protos-cloudsolutions.de/http://wordpress.protos-cloudsolutions.de/wp-sitemap.xmlresulted in a404 Not Found response:\n<!doctype html>\n<html lang="en-US" >\n<head>\n\t<meta charset="UTF-8" />\n\t<meta name="viewport" content="width=device-width (truncated...)\n in /var/www/html/wp-content/plugins/wp2static/vendor/leonstafford/wp2staticguzzle/src/Exception/RequestException.php:113\nStack trace:\n#0 /var/www/html/wp-content/plugins/wp2static/vendor/leonstafford/wp2staticguzzle/src/Middleware.php(69): WP2StaticGuzzleHttp\\Exception\\RequestException::create()\n#1 /var/www/html/wp-content/plugins/wp2static/vendor/leonstafford/wp2staticpromises/src/Promise.php(204): WP2StaticGuzzleHttp\\Middleware::WP2StaticGuzzleHttp\\{closure}()\n#2 /var/www/html/wp-content/plugins/wp2static/vendor/leonstafford/wp2staticpromises/src/Promise.php(153): WP2StaticGuzzleHttp\\Promise\\Promise::callHandler()\n#3 /var/www/html/wp-content/plugins/wp2static/ve in /var/www/html/wp-content/plugins/wp2static/src/DetectSitemapsURLs.php on line 125, referer: http://wordpress.protos-cloudsolutions.de/wp-admin/admin.php?page=wp2static
The URL in question exists: http://wordpress.protos-cloudsolutions.de/wp-sitemap.xml but gets concatenated with the host again.

Thanks for digging further, @cklingspor! There is an outstanding issue related to Sitemap detection/crawling in the core plugin, with some workarounds people have found:
This may help, sorry I can't give you a specific right now, but wil be sorting out this particular sitemap/robots related issue as soon as I can:
https://github.com/leonstafford/wp2static/issues?q=is%3Aissue+is%3Aopen+sitemap
Hopefully, this is the same issue and you can find a workable solution

@cklingspor should be fixed in latest develop branch now. Please let me know if persists

Hi Leon, thank you for getting back to me. I will check once I have the time and let you know. Have a great day!


test(sync): tmp basic mock

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Which docs this PR relation:
Ref #
Which toolchain this PR adaption:
No Breaking Change
Special notes for your reviewer:
CI Switch
ci-runs-only: [Chaos CI, Cargo Clippy, Coverage Test, E2E Tests, Code Format, Unit Tests, Web3 Compatible Tests]

Codecov Report

Merging #570 (08e9d25) into main (9c144d4) will increase coverage by 0.00%.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##             main     #570   +/-   ##
=======================================
  Coverage   17.10%   17.11%
=======================================
  Files         139      139
  Lines       18794    18794
=======================================
+ Hits         3215     3216    +1
+ Misses      15579    15578    -1

Impacted Files
Coverage Δ

core/consensus/src/synchronization.rs
0.00% <0.00%> (ø)

core/mempool/src/pool.rs
89.65% <0.00%> (+0.57%)
:arrow_up: