Redirects to the login page

I am constantly redirected to the login page, am I doing something wrong? added only value
`
def upload_tiktok(film_data):
cookies_list = [
{
'name': 'sessionid',
'value': '650333bbe17gdrslk7658a66777a89a9b677f',
'domain': '.tiktok.com',
'path': '/',
'expiry': '30/01/2024, 18:37:59 PM'
}
]
video_path = film_data.video
description = film_data.description
upload_video(video_path, description=description, cookies_list=cookies_list)

`

Use cookies.txt which is the format for each cookie. I will make a better note of that, but you need more than you sesionid to get authentication to work properly.

Use cookies.txt which is the format for each cookie. I will make a better note of that, but you need more than you sesionid to get authentication to work properly.

Thanks for pointing out the problem)
I haven't worked with python yet, it's hard to grasp everything.
Now I get another error, I see that the video is loading, but there is an error at the end
`
[21:27:40] Failed to upload D:\Python\tiktok\public\films\test\test.mp4
[21:27:40]
A video failed to upload
Message:
Stacktrace:
GetHandleVerifier [0x00DB6EE3+174339]
(No symbol) [0x00CE0A51]
(No symbol) [0x009F6FF6]
(No symbol) [0x00A29876]
(No symbol) [0x00A29C2C]
(No symbol) [0x00A5BD42]
(No symbol) [0x00A47054]
(No symbol) [0x00A5A104]
(No symbol) [0x00A46DA6]
(No symbol) [0x00A21034]
(No symbol) [0x00A21F8D]
GetHandleVerifier [0x00E54B1C+820540]
sqlite3_dbdata_init [0x00F153EE+653550]
sqlite3_dbdata_init [0x00F14E09+652041]
sqlite3_dbdata_init [0x00F097CC+605388]
sqlite3_dbdata_init [0x00F15D9B+656027]
(No symbol) [0x00CEFE6C]
(No symbol) [0x00CE83B8]
(No symbol) [0x00CE84DD]
(No symbol) [0x00CD5818]
BaseThreadInitThunk [0x75857BA9+25]
RtlInitializeExceptionChain [0x771FBD2B+107]
RtlClearBits [0x771FBCAF+191]
`


Add uri-js dependency

The stac-node-validator step in the test had started to fail with the error:
><EMAIL_ADDRESS>check-examples
> stac-node-validator . --lint --verbose --schemaMap https://stac-extensions.github.io/authentication/v1.1.0/schema.json=./json-schema/schema.json

node:internal/modules/cjs/loader:1042
  throw err;
  ^

Error: Cannot find module 'uri-js'
Require stack:
- /mnt/c/Users/james/Documents/github/authentication/node_modules/stac-node-validator/iri.js
- /mnt/c/Users/james/Documents/github/authentication/node_modules/stac-node-validator/index.js
- /mnt/c/Users/james/Documents/github/authentication/node_modules/stac-node-validator/bin/cli.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1039:15)
    at Module._load (node:internal/modules/cjs/loader:885:27)
    at Module.require (node:internal/modules/cjs/loader:1105:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at Object.<anonymous> (/mnt/c/Users/james/Documents/github/authentication/node_modules/stac-node-validator/iri.js:1:19)
    at Module._compile (node:internal/modules/cjs/loader:1218:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1272:10)
    at Module.load (node:internal/modules/cjs/loader:1081:32)
    at Module._load (node:internal/modules/cjs/loader:922:12)
    at Module.require (node:internal/modules/cjs/loader:1105:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/mnt/c/Users/james/Documents/github/authentication/node_modules/stac-node-validator/iri.js',
    '/mnt/c/Users/james/Documents/github/authentication/node_modules/stac-node-validator/index.js',
    '/mnt/c/Users/james/Documents/github/authentication/node_modules/stac-node-validator/bin/cli.js'
  ]
}

Node.js v18.13.0

Adding uri-js as a dependency resolves the issue. I am not sure what introduced this bug.

This issue might be affecting other extension repos. I posted in gitter here: https://matrix.to/#/!keYKZtlQXulQARQNzG:gitter.im/$lsKfGEX86-euBc41lfCpp1IW8vS0qy73BR7RSEYexbg?via=gitter.im&via=matrix.org&via=chard.com

Let me check this on the Validator side... :)

The dependency was missing in the validator, I've released a v1.3.1 bugfix release. This PR shouldn't be needed any longer.

The dependency was missing in the validator, I've released a v1.3.1 bugfix release. This PR shouldn't be needed any longer.

Nice, thank you!

I also just reran the failed jobs and they don't fail any longer.


Why is it called createRouteAction instead of just createAction?

Still learning SolidJS and SolidStart. One thing that is confusing me is the name createRouteAction. I understand createRouteAction is executed on the client side.

Can't I call that function in a component? What I mean is, can't I call it in non-page component?
Can't I call it without a Form?

Suppose i have I global like button in every page, that doesn't need any input params.
import { createRouteAction } from "solid-start/data";
import { createSignal } from "solid-js";

// Global signal, that I should also use in other places
export const [globalLike, setGlobalLike] = createSignal(0);

export function LikeButton() {
  const [liking, like] = createRouteAction(async () => {
    fetch("/increase-like")
    // Should parse response....but for the sake of simplicity
    .then((likes) => setGlobalLike(likes) )
  });

 if ( liking.pending ) return
Liking
;
 return
Likes are {globalLike()}

}

Would this be wrong? Is this not a best practice?
In this situation, this is not a route action, right? Unless I'm misunderstanding the purpose of createRouteAction
Wouldn't make more sense to just call it createAction ?
While we are at it, is this best practice?
import { createRouteAction } from "solid-start/data";
import { createSignal } from "solid-js";

// Global signal, that I should also use in other places
export const [globalLike, setGlobalLike] = createSignal(0);

// Extract liking logic from the component
export const [liking, like] = createRouteAction(async () => {
    fetch("/increase-like")
    // Should parse response....but for the sake of simplicity
    .then((likes) => setGlobalLike(likes) )
  });

export function LikeButton() {
 if ( liking.pending ) return
Liking
;
 return
Likes are {globalLike()}

}

I'm going to move this one to discussions. But there was some debate here.

It was unclear if we were going to backport a generic action to Solid so we didn't want to just use createAction because well this extra behavior is based on how it interacts with specific data related to the route. Ie it invalidates the route data on completion.

Because of the way it interacts with route data (ie knows location) it needs to be declared in the component flow. It can't be declared outside of components like server$ can. I don't think this matters a ton for naming but it's why the choice was route.

We needed to differentiate from createServerAction$. I'm leaning more and more to wondering if we shouldn't have just have left the combining to the end user. Ie.. have createRouteAction + server$ applied manually. It's more to type and to explain but it means less primitives and less overlap. If we did go that way I'd strongly lean towards renaming createQuery and createAction. But I'm not in a rush to make that decision (and easy to have a deprecation path if we go that way).

As for your questions:
You can call action in your components. And you can use it without forms. The latter was very much a design goal. Forms give us progressive enhancement but they are definitely bulkier to deal with. You can set your goal.
Using signals global like that is not recommended for SSR generally since you could share state between requests. It's often recommended to use context. Or even jump in the routeData. As I mentioned you can't hoist createRouteAction itself outside of the component but you could export the underlying function and use that elsewhere.
The idea here isn't so much to use these like API routes but as RPCs for the specific UI you are working on. If you have underly data model/API logic I'd extract it. The real expectation is most would lean towards createServerAction$ and it just all be wired up always working on the server without an API. However, there is flexibility here.


Move translations that are not required by the identity-apps to a separate extension.

Describe the issue:
Currently in the identity apps there are some translations that are not required by the apps in the identity apps. Therefore to reduce the bundle size of the pack it is better to move it to a separate folder.

Closing as it is done


Add devices/stm32g491.yaml

This is a companion PR to https://github.com/stm32-rs/stm32-rs/pull/488 which should be merged first.
Otherwise the CI mmap checker breaks, on missing vendor svd file for stm32g491 in master

Sorry for creating so many PR's, just want to make the review process smooth :)

No problem, thanks for all the work! I'll try to get these reviewed in the next few days.

Thanks a lot for this and #488! I've merged both commits in #492 along with a few other tweaks for the new SVD file.

Thanks !! :)


Floating banner in the Branding page is missing

Setup
Rancher version: 2.6.5-rc2
Browser type & version: Chrome
Describe the bug
Floating banner for user changes is missing in the branding page from global settings >> Branding page
For more context: Issue number 5 from https://github.com/rancher/dashboard/issues/3529

Verified on v2.6-head 650cb0b
Floating banner is added in branding page:


implemented threadpool mechanics when loading images

Hi,
I noticed that the loading of the images is not implemented with threads.
Using threadpool with 4 threads improved the loading time for me by a factor of 2-3, when the images are located locally on the machine SSD.
If the images are located on a network drive the the loading time is better by a factor of 3-4.
This is particularly important when there are many images in the dataset and the RAM memory is "limited" ( for me 400 images could not fitt in my 48 GB memory) and the user have to use num_images_to_sample_from and num_times_to_repeat_image fields. In this case the training becomes very IO intensive ( you keep loading images throughout the training).
Thanks

Feel free to merge when ready.


Group hierarchy limited to 1 since v3.0.0

To achieve a pure, non cyclic data result, version 3.0.0 introduced the DescribedDataField. Fields can only be added to groups without there groups. So the hierarchy is limited to 1. This should be at least extended, ideally unlimited defined by PropertyStructureDescription. The resulting data structure needs to remain non cyclic so it can be easily converted to JSON.

described_field.DescribedDataFieldGroup.addGroupEntries might be the right place to look at as a starting point.


[Task]: Improve Enrichment docs

What needs to happen?
There are a few targeted fixes needed for the Enrichment docs:

https://beam.apache.org/documentation/transforms/python/elementwise/enrichment/ should mention BigQuery
https://beam.apache.org/documentation/transforms/python/elementwise/enrichment/ should describe how we do batching and how we do caching (with_redis_cache)
https://github.com/apache/beam/blob/master/examples/notebooks/beam-ml/bigtable_enrichment_transform.ipynb and https://github.com/apache/beam/blob/master/examples/notebooks/beam-ml/vertex_ai_feature_store_enrichment.ipynb should elaborate a little more on what a cross-join means in this context (maybe a picture would be nice?)
In https://github.com/apache/beam/blob/master/examples/notebooks/beam-ml/bigtable_enrichment_transform.ipynb the example handler with composite row key support link is dead

Issue Priority
Priority: 2 (default / most normal work should be filed as P2)
Issue Components

[X] Component: Python SDK
[ ] Component: Java SDK
[ ] Component: Go SDK
[ ] Component: Typescript SDK
[ ] Component: IO connector
[ ] Component: Beam YAML
[ ] Component: Beam examples
[ ] Component: Beam playground
[ ] Component: Beam katas
[X] Component: Website
[ ] Component: Infrastructure
[ ] Component: Spark Runner
[ ] Component: Flink Runner
[ ] Component: Samza Runner
[ ] Component: Twister2 Runner
[ ] Component: Hazelcast Jet Runner
[ ] Component: Google Cloud Dataflow Runner

@claudevdm this would be good to pick up at some point when you have space (don't drop other things, just when this fits in nicely)


Remove deprecated HCL actions?

I was excited to come across these awesome actions, but it appears that some of the links use the now deprecated HCL syntax-based actions.
Would it make sense to remove or move the actions that use HCL to give emphasize ones that use the current YAML syntax?
Related: https://help.github.com/en/articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax

@nathany said...
some of the links use the now deprecated HCL syntax-based actions.

As per the link that you posted, HCL syntax isn't quite at the deprecated stage yet, but I do agree that we might want to separate, or at least highlight, that a particular action uses a particular format.
Is this something that you would like to take a stab at?

Support for the HCL syntax in GitHub Actions will be deprecated on September 30, 2019.

The Actions should continue to work however the workflow setups won’t and should be updated.

@clarkbw that is good to know!  Thank you for confirming that.
@nathany based on this knowledge, I don't see any immediate need to alter the list as it currently stands.  Do you?

Yeah, I think the list should make mention of this. I'll work on this unless someone else wants to take it.

@sdras that would be great if you could, thank you!
While you are here, can I ask if you saw this: https://github.com/sdras/awesome-actions/issues/95  Thanks!

For what its worth, I think that even though the HCL syntax is not yet deprecated, it should be considered at least outdated. It had a short shelf-life, and sifting through the list just to find out many things are not relevant, is just adding to the confusion.
I believe the approach to updating this repo should be to separate the HCL to the bottom of the list, or to a separate document, and keep the list clean, focusing exclusively on the new syntax.

@DannyBen did you want to take a stab at doing this?

I thought @sdras was on the case, no?

That was back in August last year, and since then, the help wanted label has been added, so I am going to say that it is open for contributions.

Ok - I promise to take a look and see if I have the time for it. There are tons of links there, each needs to be carefully reviewed and migrated. No promises, but I might find the time during the weekend.
Do we prefer adding a "(HCL)" (or other) marker neear HCL only items, or do we prefer a completely separate list? The former will probably be easier, since the latter might create weird lists (since they will lose many if not all items).


1.0 as a string should be a valid version for a dataset

Dataverse uses MAJOR.MINOR for dataset versions like 1.0, 1.1, 2.0. I believe this should be valid. I'm aware that the validator wants MAJOR.MINOR.PATCH (output below) and that under the Version section, the Croissant 1.0 spec says the same (Semantic Versioning 2.0.0).
I'm also aware that 1.0 as number instead of a string is considered valid (thanks @goeffthomas for pointing this out), but I don't see this in the spec and I think versions should be strings (1.0.0 isn't a number anyway). I see from #593 and #594 that just 1 as a number is also valid but this isn't a solution for Dataverse.
Below is the warning I see as of 1.0.3 from the validator when testing my work-in-progress Croissant file (also below). The relevant line in the JSON is, of course, the following:
    "version": "1.0",

So! Can we consider 1.0 valid?
Thanks for your consideration!
$ mlcroissant validate --jsonld croissant.json
W0315 16:45:48.010244<PHONE_NUMBER>99424 datasets.py:32] Found the following 1 warning(s) during the validation:
  -  [Metadata(Cars)] Version doesn't follow MAJOR.MINOR.PATCH: 1.0. For more information refer to: https://semver.org/spec/v2.0.0.html
I0315 16:45:48.010346<PHONE_NUMBER>99424 validate.py:53] Done.
$
$ cat croissant.json
{
    "@context": {
        "@language": "en",
        "@vocab": "https://schema.org/",
        "citeAs": "cr:citeAs",
        "column": "cr:column",
        "conformsTo": "dct:conformsTo",
        "cr": "http://mlcommons.org/croissant/",
        "data": {
            "@id": "cr:data",
            "@type": "@json"
        },
        "dataBiases": "cr:dataBiases",
        "dataCollection": "cr:dataCollection",
        "dataType": {
            "@id": "cr:dataType",
            "@type": "@vocab"
        },
        "dct": "http://purl.org/dc/terms/",
        "extract": "cr:extract",
        "field": "cr:field",
        "fileProperty": "cr:fileProperty",
        "fileObject": "cr:fileObject",
        "fileSet": "cr:fileSet",
        "format": "cr:format",
        "includes": "cr:includes",
        "isEnumeration": "cr:isEnumeration",
        "jsonPath": "cr:jsonPath",
        "key": "cr:key",
        "md5": "cr:md5",
        "parentField": "cr:parentField",
        "path": "cr:path",
        "personalSensitiveInformation": "cr:personalSensitiveInformation",
        "recordSet": "cr:recordSet",
        "references": "cr:references",
        "regex": "cr:regex",
        "repeated": "cr:repeated",
        "replace": "cr:replace",
        "sc": "https://schema.org/",
        "separator": "cr:separator",
        "source": "cr:source",
        "subField": "cr:subField",
        "transform": "cr:transform",
        "wd": "https://www.wikidata.org/wiki/"
    },
    "@type": "sc:Dataset",
    "conformsTo": "http://mlcommons.org/croissant/1.0",
    "name": "Cars",
    "version": "1.0",
    "citeAs": "https://doi.org/10.5072/FK2/EKY1NP",
    "distribution": [
        {
            "@type": "cr:FileObject",
            "name": "stata13-auto.dta",
            "encodingFormat": "application/x-stata-13",
            "md5": "7b1201ce6b469796837a835377338c5a",
            "sha256": "see md5",
            "contentUrl": "stata13-auto.dta"
        }
    ],
    "license": "http://creativecommons.org/publicdomain/zero/1.0",
    "datePublished": "2024-03-13",
    "dateModified": "2024-03-13"
}

Over at https://github.com/gdcc/dataverse-exporters/commit/3e95c977722e1b83a3b584bbecc4e77bc628c60f I pushed a commit to simply append ".0" to the version of Dataverse datasets, but I'm pretty grumpy about it because it's really suboptimal for us. Here's the comment I left in the code:

We append ".0" to our version string to make the Croissant
validator happy and to comply with the Croissant spec but we
would rather not.

Here's what the spec says:

"The recommended versioning scheme to use for datasets is
MAJOR.MINOR.PATCH, following Semantic Versioning 2.0.0." --
https://mlcommons.github.io/croissant/docs/croissant-spec.html#version

If a Dataverse user sees 1.0.0 they will hopefully know that they
must remove the final ".0" to see the actual version of the
dataset they want. Note that as of Dataverse 6.1, if you navigate
to 1.0.0 you will be redirected to the latest published version,
which is possibly quite different than version 1.0 of the
dataset! For example you will be redirected to version 4.0 (as of
this writing) if you try to navigate to
https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/TJCLKP&version=1.0.0

This is suboptimal, of course. The API will simply show the error
"Illegal version identifier '1.0.0'" if you try to access version
1.0.0 of a dataset via API. Here's an example
https://dataverse.harvard.edu/api/datasets/:persistentId/versions/1.0.0?persistentId=doi:10.7910/DVN/TJCLKP

Either way, a version of 1.0.0 is not helpful to a Dataverse
user. The GUI may send you to an old version. The API will bark
at you that version is illegal.

We opened https://github.com/mlcommons/croissant/issues/609 to
argue that 1.0 is a perfect valid version for a dataset.
Hopefully in the future we can stop appending ".0"!

By the way, it's technically possible to make the Croissant
validator happy by passing 1.0 as a float. However, this is not
compliant with the Croissant spec which (again) wants 1.0.0. We
are sticking with strings because they are a more sane way to
represent a version and they're what SemVer uses, even allowing
"-alpha", etc.

Today I played around with where to put the real version of a Dataverse dataset (e.g. "1.0") but I can't find a good place without triggering schema.org violations.
Again, users need to real version number if they want to use Dataverse APIs successfully, as described in my comment above.
Right now my Croissant implementation appends an extra ".0" but I'd rather just put "1.0" and be able to configure the Croissant validator to ignore the warning, so I just opened this related issue:

#643

@ccl-core Can you please take a look at this issue?

Hi @pdurbin , thank you for reporting this issue!
Just to clarify, 1.0 is a valid version: the validation script is just throwing a warning.
The mlcroissant library takes already care of the version casting, so you should be able to use your croissant file with 1.0 version.
Unless your issue is about the warning itself: do you think that the warning message is wrong or incomplete?

@ccl-core thanks for getting back to me.
First, in terms of validity, the spec implies that ANY string is valid, right? "foobar" and "supercalifragilisticexpialidocious" are both valid versions. This is because version in schema.org can be "Number" or "Text".
The table below summarizes my understanding of the how the validator and the spec treat the following values. (I put strings in quotes and left quotes off numbers.)
Current state

Value
Validator
Spec

"1.0.0"
no warnings ✅
recommended ✅

1.0 or 1
no warnings ✅
valid 🤷♀

"1.0"
warning ❌
valid 🤷♀

"foobar"
warning ❌
valid 🤷♀

This feels off to me. I think a step in the right direction would be to allow the validator to not throw a warning for "1.0" (as a string), just like how it doesn't throw a warning for 1 or 1.0 (as numbers). Further, perhaps the spec should be updated to mention that 1 and 1.0 (as numbers) get special treatment (at least by the validator). And perhaps "1.0" (as a string) would get the same special treatment in the future. Here's an updated table:
Option 1: treat "1.0" like 1.0

Value
Validator
Spec

"1.0.0"
no warnings ✅
recommended ✅

1.0 or 1
no warnings ✅
special treatment mentioned 👀

"1.0"
no warnings ✅
special treatment mentioned 👀

"foobar"
warning ❌
valid 🤷♀

If you're thinking, "just use 1.0 as a number instead of a string", the reason I'm reluctant to do this is that if Dataverse ever does switch from MAJOR.MINOR to MAJOR.MINOR.PATCH (as Croissant recommends) it would mean switching the type from number to string, which would be a breaking change for our users. I'd rather use strings in our Croissant export from the start so we can more easily switch from "1.0" to "1.0.0" in the future. I think we all know that in the real world, versions are usually strings, not numbers. SemVer is a good example.
Option 2: pass a flag to ignore version warnings
Another perfectly valid option could be to allow people like me who don't want to see the warning about version to pass a flag to the validator to suppress the "Version doesn't follow MAJOR.MINOR.PATCH" warning. I'm happy to see you're working on this (thanks!):

#658

I imagine it will resolve the issue I opened:

#643

With this option, I still think it would be good to update the spec to explain that 1 and 1.0 are given special treatment (no warnings shown):

Value
Validator
Spec

"1.0.0"
no warnings ✅
recommended ✅

1.0 or 1
no warnings ✅
special treatment mentioned 👀

"1.0"
warning ❌
valid 🤷♀

"foobar"
warning ❌
valid 🤷♀

I hope this helps! Thanks again!

Drive-by comment: I dislike the fact that versions can be numbers... As numbers, there is no difference between 1 and 1.0, even though we may consider them to be different values in terms of versions.
For the next version of Croissant, I wonder if we should constrain version to always be a string and recommend that it follows one of the patterns: "x", "x.y" or "x.y.z", where x y and z are integers, and maybe allow other strings but issue a (suppressible) warning if it doesn't follow one of these patterns.
What do you all think?

@benjelloun yeah, it sounds like we're in agreement that versions should be strings, not numbers.
In the schema.org world, I'm not familiar with how best to constrain a field like version that allows both Text and Number. I suppose we could have cr:version that has its own rules.
If we want to stick with SemVer, please keep in mind that it's not just integers and dots (periods). You'll see examples like "1.0.0-alpha" and "1.0.0+21AF26D3" in the spec (under "MAY" for pre-release and build metadata).

We can constrain sc:version by changing its documentation in our spec, and validate the field for datasets that specify that they comply with Croissant 1.0.
Indeed, for SemVer we would need some regexp like https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string


[REQUEST] Enable flagging of a development-only dataset (not ready for public trip planning)

What problem is your feature request trying to solve?
I'd like to publicly post datasets which contain features which are under development and not ready for public trip planning and also have a central place for  data consumers to be able to find development datasets for specific features (i.e. Flex, etc.) to enable them to test their tools.
Describe the solution you'd like

Extension of the schema to add a flag for development-only.  e.g. an optional field (defaults to False) where you can note: development_only = true
Extension of the schema to add an enumeration of which feature(s) this feed uses.  e.g. features = [fares,flex`]
Decision on whether/how this would interact with "publication-ready" datasets for the same feeds (i.e. different feed id? )
An auto-summary of feeds for different features so that developers can easily find "all the datasets with fares".

Describe alternatives you've considered
Posting a California-only testbed summary of datasets at gtfs-dev.calitp.org
How will we know when this is done?
As a consumer, I can find a list of all the development feeds with various features.
As a producer, I can add development-only feeds and be confident they aren't going to be used for active trip planning.

In order to get the ball rolling and people the datasets they need to start testing, I've added a really basic PR  to implement the above – with the major caveat that I used existing code as a template and didn't do a thorough review of the logic!

Since it can easily get lost in the PR comments, I want to highlight this proposed list of features as I originally suggested here.:

For the list of features, as a first implementation I suggest flex-v1, flex-v2, fares-v1, fares-v2, pathways and occupancy. The classifier structure would be helpful for UI (display all the sources implementing a version of “Fares”), but is not well suited for this use case (indicating that a source features “Fares” is misleading since v1 and v2 are incompatible). Since consumers are interested in finding specific feature versions, this list seems like a good starting point. Happy to discuss further if needed.

Closing this issue now that #171 has been merged.


Default cluster filter doesn't cover clusterName alias attributes.

Summary
External metrics queries are being filtering by the clusterName by default unless the removeClusterFilter parameter is set. This automatic default filter is adding the where clusterName=<cluster name> clause to the query. The issue is that the clusterName attribute has some aliases depending on the source of the data and type, following some examples:

Metrics coming from Pixie isk8s.cluster.name
Metrics transformed to Dimensional Metrics k8s.clusterName

Because of this reason the current filter only work for metrics comming from the Infra Agent or on-host integrations when using samples.
Desired Behavior
All aliases are contemplated in the filter and is transparent for the point of view of configuration.
Possible Solution
We could add a where condition that covers all alias like:
where (clusterName=<cluster name> OR k8s.cluster.name=<cluster name> OR k8s.clusterName=<cluster name>)
Additional context
The current workaround is to disable the cluster filter by  activating removeClusterFilter, and to use custom filters depending on the source.

I don't really understand what component needs to be enabled for clusterName to work.
For example, my helm chart values are the following:
newrelic-infrastructure:
  enabled: true
nri-prometheus:
  enabled: false
nri-metadata-injection:
  enabled: true
kube-state-metrics:
  enabled: true
  collectors:
    certificatesigningrequests: false
    ingresses: false
nri-kube-events:
  enabled: false
newrelic-logging:
  enabled: false
newrelic-pixie:
  enabled: false
pixie-chart:
  enabled: false
newrelic-infra-operator:
  enabled: false
newrelic-k8s-metrics-adapter:
  enabled: true

newrelic-infrastructure component is enabled, however, in NRQL I can see only k8s.clusterName filter is available.
This is annoying because I use external metrics and have to set removeClusterFilter: true and specify k8s.clusterName explosively in each HPA definition

I don't really understand what component needs to be enabled for clusterName to work.

Hi @tsurankov , the attribute clusterName is used on the Samples, for instance in the From K8sPodSample, that same attribute is called different k8s.clusterName when you use the dimensional metrics From Metric. So if the NRQL you are using to calculate the metrics is based on samples you shouldn't need to removeClusterFilter: true when metrics are all from the same cluster.
The next best step is to visit New Relic Support, where you can engage the New Relic Support Community or open a support ticket depending on your support level. The support team is best positioned to assist with your specific needs.
Please provide a link to this GitHub issue when submitting your community post or support ticket.
Thanks!


Added nested tensors  input support for several nn functions

Enabled several nn functions to work with nested tensors.
Covered:

max_pool2d
batch_norm
relu
interpolate
cross_entropy
dropout

Tested via unit tests
Todo:

add grad tests
move the implementations to C++ for performance improvements.

@cpuhrsch, as discussed offline, since last review:

updated tests to use both NT constructors
updated interpolate test to use different size types (None, tuple, int)

Autograd testing will come as a follow up pr due to a bug with as_nested_tensor.

@cpuhrsch, should be ready. Grad checks were added to the integration test


Routerlink attribute not working in custom cell

Description
Routerlink not working in custom cell
Steps to reproduce
I am trying to setup  "routerLink"  attribute for the HTML generated for one of the cell for custom renderer has been added. Event is not getting fired when element is clicked on the UI element. Is there is work around to this?
Your environment

Wrapper version:
Latest chrome
Mac OS

Context
We are implementing File upload feature. Here user can click to a cell which is custom rendered to upload a file. So when user clicks on this custom rendered cell we would like to navigate to the route which handles the file operation,  with relevant parameter fetched from  row data.

Hello @swistach
Is there any way to write routerLink in table cell?
I tried write routerlink directly and used html renderer, but it's not working.

Hey @SarfaleSiddharth
that's a feature request that is currently on hold.

Hello @AMBudnik
Thanks for the update
Any idea, when we can have this feature active? or any other alternative workaround for this?

We are currently focusing on adding new formulas to Handsontable so it's really hard to tell. I will make sure to update you once we get this done.


updated readme descriptions and links

Updated descriptions of links to include which ones redirect to HF
Updated links to scripts within the repo

@egrace479 question on readme - when referencing terminal commands to run the scripts, for example line 79 detector2cvat --video path_to_videos --save path_to_save does the detector2cvat need to have a .py at the end? or is this not needed for scripts part of the pyproject? thanks!


📎 Implement noUselessStringRaw - clippy/needless_raw_strings

Description
Implement clippy/needless_raw_strings.
Want to contribute? Lets you know you are interested! We will assign you to the issue to prevent several people to work on the same issue. Don't worry, we can unassign you later if you are no longer interested in the issue! Read our contributing guide and analyzer contributing guide.
The implementer could take some inspirations from the implementation of existing rules such as noUselessEscapeInRegex.

Isn't this a linter for Rust syntax? Isn't the current linter of Biome for JS?

Isn't this a linter for Rust syntax? Isn't the current linter of Biome for JS?

JavaScript has a String.raw function: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/String/raw
I presume the rule should trigger when using the function on normal strings (no template literals)

Sorry this was not clear from the description.
The rule is intended to report template literals tagged with String.raw without any escape sequence.
Example of code to report:
String.raw`a simple ${a} string`

Examples of code to not report:
String.raw`\n ${a}`

@Conaclos can you provide more direction to the contributors? For example, why this rule exists, when to use it, and the end user should do to fix the code when the rule is triggered

why this rule exists

Raw strings don't handle escape sequence like in regular strings (including untagged template literals) do.
For instance the following raw string:
String.raw`\n`;

is equivalent to the following string:
"\\n";

Raw strings are only useful in that regard.
Thus, if you use a raw string without any escape-like sequence, they are useless.
Because the following raw string:
String.raw`a`;

is equva;lent to the regual rstring:
"a";

the raw string is useless.

when to use it

We could basically always use this rule.

and the end user should do to fix the code when the rule is triggered

Simply turn the raw string into a template literal or even a string if there is no template placeholder:
- String.raw`a`;
+ "a";
- String.raw`a ${v}`;
+ `a ${v}`;

thanks for your reply, i'd like to work this~


Document how to integrate owncloud

After some research we discovered this is not an easily pluggable extension, closing this issue.


Implementing the entire PREP pipeline

Hi! We'd like to implement the entire PREP pipeline, which will include:

Bug fixing of Noisydata class
Feature enhancement by adding filtering, line noise removal and robust referencing.
Integrating all the steps into one function

Hi @Nick3151 - that sounds great to me. Who is "we"? How do you want to work on this?

And maybe we could get pyprep merged into MNE in the future.

sounds very good, let's continue the discussion in https://github.com/mne-tools/mne-python/issues/7049

@sappelhoff How do you feel that these folks, @Nick3151 and two others work on a PR into the forked version of this in https://github.com/NeuroDataDesign/pyprep and then we submit a PR here?
Or should we directly try to address the fixes mentioned here and in the discussion in mne-tools/mne-python#7049 with a direct PR in the main repo?
Let us know your thoughts.

I think your first suggestion works well. That way you can work independently of any GitHub rights you may need to move forward.
It'd be great to tag me occasionally when there is new stuff you integrate, ... that way I won't be too overwhelmed once you make a PR from your fork to this repo :-)


Activation Function and Loss Function in Neural Network:

Explaining about activation and loss functions in neural network.
I agree to follow this project's Code of Conduct
I'm a GSSoC'24 contributor
I want to work on this issue

Please assign me this issue.

Hello @sanjay-kv , please assign this issue to me as I have already worked on this kind of problem in the past.


How To Apply Custom Algorithm On CanonicalizationMethod?

Hey guys!
Can anyone help me on applying this signature pattern? I read the documentation, but I can't understand it correctly.
Should this work?
sign.canonicalizationAlgorithm = "http://www.w3.org/TR/xmldsig-core/"
Thanks in advance!

I think the canonicalization algorithm you want is http://www.w3.org/TR/2001/REC-xml-c14n-20010315. It is not officially supported yet but you might find a workaround in #102 .

Can u help on how to workaround this @yaronn ?
Should it be something like this into signed-xml.js:
`var SignedXml = require('xml-crypto').SignedXml;
var fs = require('fs');
function MyCanonicalization() {
/given a node (from the xmldom module) return its canonical representation (as string)/
this.process = function(node) {
//you should apply your transformation before returning
return "< x/>"
}
this.getAlgorithmName = function() {
return "http://www.w3.org/TR/2001/REC-xml-c14n-20010315"
}
}
SignedXml.CanonicalizationAlgorithms["http://MyCanonicalization"] = MyCanonicalization
`
And my signature route.js is like:
         var sig = new SignedXml()         sig.addReference("//*[local-name(.)='xxx' and namespace-uri(.)='http://www.portalfiscal.inf.br/nfe']")         sig.signingKey = fs.readFileSync("./certificates/test.pem")         sig.canonicalizationAlgorithm = "http://www.w3.org/TR/2001/REC-xml-c14n-20010315";         sig.computeSignature(xml, {             location: { reference: "//*[local-name(.)='xxx']", action: "after" }         });         return sig.getSignedXml()
How can I make this work properly?
Thanks in advance!

Fixed in #116


passing context to services, creating constants and native error

@henrybarreto please fix the CI error so we can merge it.

It is ready to merge


InstallGuide: update Esri software references to 10.4.1

Edited Word doc 07 Sept 2016.

Fixed in v.next. Closing issue.


[vx.dev] implements #4

[vx.dev] This PR implements #4, created by vx.dev.

[vx.dev]: This code snippet creates a responsive one-page thank you website for Eli Cohen, featuring a modern and simple design language. The page includes an avatar, a prominent name display, a thank you alert, a video frame, and a button to acknowledge the contribution. It also has a playful element with a heart icon and a tooltip for the GitHub logo.


List of things I noticed

[ ] Packet accepts any value, even if it's larger or smaller than the types min/max values. IMO it should be capped to the max value and be set to 0 if the value is smaller than the min value. All unused energy should be returned to whoever tried to set it.

[ ] Energystorage has a int getCurrentEnergy() method that returns the amount of the blocks primary energy type and a EnergyType getPrimaryEnergyType method. I would suggest that we replace them with a Map<EnergyType, Integer>. This would allow one block to store multiple kinds of energy. (e.g. A battery that can store different Voltages)

I don't know what you're talking about with Packet - we've dispensed with first-class Packets and if there's a class lying around for that still we should kill it.
A battery doesn't have shelves that it puts different energy voltages into. There's a chemical reaction at the anode that yields free electrons. Voltage is just the difference in electric potential between the anode and the other end of the electric circuit, it'll always be the same (except irl as the anode is exhausted the potential drops, this is how we measure battery fullness)
We can skip a lot of those mechanics when they're easier and more fun for players, and better match what players expect out of a battery. So we'd have to apply those tests to storing multiple voltage types:
simplicity test:
Storing multiple voltage types in a block is more complicated than storing one voltage type.
fun test:
This is subjective, but I feel like this will require multiple bars or gauges on one battery, and perhaps even managing different power caps for each type. It seems awfully fussy and un-fun.
user expectations test:
Let's say we have a battery that we're filling with MV. An LV grinder sits next to the battery's output face, so the battery will push energy into it. If the battery has different shelves, then its MV shelf is full and its LV shelf is empty. The grinder remains powered down.
My expectations, generally, are that it's an MV battery, it will accept all MV and LV power and convert it to MV, and it will present MV to any consumer. This will result in the LV grinder frying; or, it's an LV battery, and as we try to push MV into it, it fries. Eventually if not addressed, explodes. The grinder remains powered down.

The codebase has changed enough that these issues might actually be solved now. An energy component could potentially handle multiple types, but has a primary type. Multiple components can be provided to LibBlockAttributes to advertise those multiple types. Information is exposed on whether types can be freely converted and which types will be harmful to the component.
The default implementation now does type conversions when possible, calculates harm, and enforces minimum and maximum transfer sizes. So we've kind of accidentally wrapped this one up :)


Add incremental builds support

Problem
Even with minimal change in CHIP, the whole library is rebuild what a 'little bit' time consuming.
Proposed Solution
Add support for incremental builds so when a CHIP is changed, the minimal set of files is rebuilt.

Duplicated with #55


MiqScheduleWorker continuously dies.

Environment: Development
OS: OSX Sierra (10.12.1)
Running rake evm:start off of master.
User scheduled jobs never run as the MiqScheduleWorker is constantly killed off due to the worker hitting memory constraints.
editing config/settings.yml :schedule_worker :memory_threshold to a higher value solves the problem and user schedules run as expected.
I have not verified this is an issue on an appliance.

@miq-bot add_label core


The pipes created during parsing instead of lexing

As mentioned in the issue below, Koto aims to provide type hints:
https://github.com/koto-lang/koto/issues/298
However, while parsing the statements like "List<List>", the ">>" at the end parsed as a "pipe operator" due to maximal munch principle. This pull request is preventing this situation and fixes the behavior of the parser.

Thanks @Tarbetu!


update ibm cloud operator to versions 0.1.2

Signed-off-by: Paolo Dettori<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ ] Has you operator nested directory structure?
[ ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Is your submission signed?

Updates to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Submit operators to both upstream-community-operators and community-operators at once
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file a PR against this repo and explain your need
2 For more information see here

@pdettori, it fails on following:
error adding operator bundle : UNIQUE constraint failed: operatorbundle.csv

@J0zi  thank you. Is there any way to figure out which resource is duplicated ? I can't see anything obvious as the list of files added in community-operators/community-operators/ibmcloud-operator/0.1.2/ is:
Type	Name	Latest commit message	Commit time
..
	ibmcloud_operator.v0.1.0.clusterserviceversion.yaml	update ibm cloud operator to versions 0.1.2	3 days ago
	ibmcloud_operator.v0.1.1.clusterserviceversion.yaml	update ibm cloud operator to versions 0.1.2	3 days ago
	ibmcloud_operator.v0.1.2.clusterserviceversion.yaml	update ibm cloud operator to versions 0.1.2	3 days ago
	ibmcloud_operator_v1alpha1_binding.crd.yaml	update ibm cloud operator to versions 0.1.2	3 days ago
	ibmcloud_operator_v1alpha1_service.crd.yaml

I might have found the issue ... but it seems like the PR brought along changes outside the IBM Cloud operator folder ... I am going to close this one and reopen a new clean PR


Perpetuals recent trades table

This supposed to be perpetual swaps or margin trading?

@creed-victor It's a sub-feature for the new perpetuals page.


now button not appear in auto apply prop

Describe the bug
now button does not appear in auto apply prop
To Reproduce
Steps to reproduce the behavior:

Set autp apply prop
set show now button

Expected behavior
now button should appear
Desktop & mobile (please complete the following information):

Browser [e.g. chrome, safari]
Library version [e.g. 3.0.0]

Thank you for your great work.


get_multiple doesn't document result order

The implementation of get_multiple does not document that the returned list's order is not guaranteed. Additionally, we might want to add another function such as get_multiple_ordered that performs the additional step of sorting the results to match the input request, minus any missing items.
Originally inspired by a question by @martpie in https://github.com/khonsulabs/bonsaidb/issues/237#issuecomment-1987342741

I can maybe work on a PR if you don't have the bandwidth :)

I'm not currently focused on this project but don't mind tackling this once I get back to BonsaiDb. But I'm also more than happy to accept a PR!


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>
.travis.yml

chore(travis): merge from template .travis.yml

Coverage remained the same at 45.366% when pulling 431d98414b6dc28ed74594825b64f7ef973296fc on template-sync-1 into 4e57e8704efaf75492c0f02d07e356898fa18728 on master.

:tada: This PR is included in version 5.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Convert bigtext to text, decode it in base64 and convert the result to Media

I have a XMLport that (used to) export and import pictures as base64 encoded in CSIDE with the usage of dotnet.
Picture - Export::OnBeforePassVariable()
CLEAR(Picture);
IF "Button Setup".Picture.HASVALUE THEN BEGIN
  lnet_MemoryStream := lnet_MemoryStream.MemoryStream;
  "Button Setup".Picture.EXPORTSTREAM(lnet_MemoryStream);
  lnet_SysArray := lnet_MemoryStream.GetBuffer;
  Picture.ADDTEXT(lnet_Convert.ToBase64String(lnet_SysArray));
END;

Picture - Import::OnAfterAssignVariable()
IF Picture.LENGTH <> 0 THEN BEGIN
  lnet_MemoryStream := lnet_MemoryStream.MemoryStream(lnet_Convert.FromBase64String(Picture));
  "Button Setup".Picture.IMPORTSTREAM(lnet_MemoryStream,'test2');
END;
CLEAR(Picture);

'Picture' in the XMLPort is a textelement of texttype BigText.
To replicate this functionality in AL, I have imported cod10 type Helper from the CAL-Open-Library.
There I make use of the ConvertValueFromBase64 and ConvertValueToBase64 functions in order to get rid of the dotnet usage.
However I am stuck with the exact procedure:
XMLport stores Base64 Encoded image in BigText PictureImport
Read the value and copy it to a text variable (PicDataBASE64).
Call TypeHelper.ConvertValueFromBase64 with PicDataBASE64 as parameter to receive PicData as text.
Convert PicData to media in the field "Button Setup".Picture.
textelement(PictureImport)
                {
                    TextType = BigText;
                    XmlName = 'Picture';

                    trigger OnAfterAssignVariable();
                    var
                        tempblob: Record TempBlob;
                        TypeHelper: codeunit "Type Helper";
                        PicInStream: InStream;
                        lstr_Out: OutStream;
                        lstr_OutBASE64: OutStream;
                        PicDataBASE64: Text;
                        PicData: Text;
                    begin
                        if PictureImport.LENGTH > 0 then begin
                            tempblob.Blob.CreateInStream(PicInStream);
                            PictureImport.Read(PicInStream);
                            PicInStream.ReadText(PicDataBASE64);
                            PicData := TypeHelper.ConvertValueFromBase64(PicDataBASE64);

                            tempblob.Blob.CreateOutStream(lstr_Out);
                            lstr_Out.WriteText(PicData);

                            "Button Setup".Picture.ExportStream(lstr_Out);
                        end;
                        CLEAR(PictureImport);
                    end;
           }

So any tips how I can do this?

Hi @SirBETE . Could you please repeat your question? What exactly are you asking?

The exact procedure of how to read from bigtext and write to a media is unclear.
The MS documentation isn't so usefull...

Why not use the Base64 functions on TempBlob, like FromBase64String?
The function doesn't accept a BigText, so you need to read the BigText into a local text variable.
Function FromBase64String will do the decoding and fill the blob with the binary value. From their you can read it with an outstream or copy it, or whatever your want.

Thanks!
Didn't knew there was such a function on TempBlob.
Code for future reference:
                textelement(PictureImport)
                {
                    TextType = BigText;
                    XmlName = 'Picture';

                    trigger OnAfterAssignVariable();
                    var
                        TempBLOB: Record TempBlob;
                        PicInStream: InStream;
                        PicDataBASE64: Text;
                    begin
                        if PictureImport.LENGTH > 0 then begin
                            PictureImport.GetSubText(PicDataBASE64, 1); //Bigtext > text
                            TempBLOB.FromBase64String(PicDataBASE64); //text > BLOB
                            TempBLOB.Blob.CreateInStream(PicInStream);
                            "Button Setup".Picture.ImportStream(PicInStream, 'pic'); //BLOB > Media
                        end;
                        CLEAR(PictureImport);
                    end;
                }


Deleting whitespace-only S3 objects keys fails

S3 allows most unicode characters as parts of object keys. This includes whitespace characters. S3 also allows whitespace-only object keys. However when using whitespace-only object keys with moto, moto fails when trying to delete such a key. Here is a minimal example to reproduce this behavior:
import boto3
from moto import mock_s3

with mock_s3():
    resource = boto3.resource("s3")
    bucket = resource.create_bucket(
        Bucket="test",
        CreateBucketConfiguration={"LocationConstraint": "eu-central-1"},
    )
    key_name = " "
    bucket.put_object(Key=key_name, Body=b"")
    bucket.delete_objects(Delete={"Objects": [{"Key": key_name}]})

Traceback (most recent call last):
  File "/some/dir/.config/JetBrains/PyCharmCE2021.1/scratches/scratch_1.py", line 12, in <module>
    bucket.delete_objects(Delete={"Objects": [{"Key": key_name}]})
  File "/some/dir/lib/python3.8/site-packages/boto3/resources/factory.py", line 520, in do_action
    response = action(self, *args, **kwargs)
  File "/some/dir/lib/python3.8/site-packages/boto3/resources/action.py", line 83, in __call__
    response = getattr(parent.meta.client, operation_name)(*args, **params)
  File "/some/dir/lib/python3.8/site-packages/botocore/client.py", line 386, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/some/dir/lib/python3.8/site-packages/botocore/client.py", line 691, in _make_api_call
    http, parsed_response = self._make_request(
  File "/some/dir/lib/python3.8/site-packages/botocore/client.py", line 711, in _make_request
    return self._endpoint.make_request(operation_model, request_dict)
  File "/some/dir/lib/python3.8/site-packages/botocore/endpoint.py", line 102, in make_request
    return self._send_request(request_dict, operation_model)
  File "/some/dir/lib/python3.8/site-packages/botocore/endpoint.py", line 136, in _send_request
    while self._needs_retry(attempts, operation_model, request_dict,
  File "/some/dir/lib/python3.8/site-packages/botocore/endpoint.py", line 253, in _needs_retry
    responses = self._event_emitter.emit(
  File "/some/dir/lib/python3.8/site-packages/botocore/hooks.py", line 356, in emit
    return self._emitter.emit(aliased_event_name, **kwargs)
  File "/some/dir/lib/python3.8/site-packages/botocore/hooks.py", line 228, in emit
    return self._emit(event_name, kwargs)
  File "/some/dir/lib/python3.8/site-packages/botocore/hooks.py", line 211, in _emit
    response = handler(**kwargs)
  File "/some/dir/lib/python3.8/site-packages/botocore/retryhandler.py", line 183, in __call__
    if self._checker(attempts, response, caught_exception):
  File "/some/dir/lib/python3.8/site-packages/botocore/retryhandler.py", line 250, in __call__
    should_retry = self._should_retry(attempt_number, response,
  File "/some/dir/lib/python3.8/site-packages/botocore/retryhandler.py", line 269, in _should_retry
    return self._checker(attempt_number, response, caught_exception)
  File "/some/dir/lib/python3.8/site-packages/botocore/retryhandler.py", line 316, in __call__
    checker_response = checker(attempt_number, response,
  File "/some/dir/lib/python3.8/site-packages/botocore/retryhandler.py", line 222, in __call__
    return self._check_caught_exception(
  File "/some/dir/lib/python3.8/site-packages/botocore/retryhandler.py", line 359, in _check_caught_exception
    raise caught_exception
  File "/some/dir/lib/python3.8/site-packages/botocore/endpoint.py", line 197, in _do_get_response
    responses = self._event_emitter.emit(event_name, request=request)
  File "/some/dir/lib/python3.8/site-packages/botocore/hooks.py", line 356, in emit
    return self._emitter.emit(aliased_event_name, **kwargs)
  File "/some/dir/lib/python3.8/site-packages/botocore/hooks.py", line 228, in emit
    return self._emit(event_name, kwargs)
  File "/some/dir/lib/python3.8/site-packages/botocore/hooks.py", line 211, in _emit
    response = handler(**kwargs)
  File "/some/dir/lib/python3.8/site-packages/moto/core/models.py", line 368, in __call__
    status, headers, body = response_callback(
  File "/some/dir/lib/python3.8/site-packages/moto/s3/responses.py", line 265, in bucket_response
    response = self._bucket_response(request, full_url, headers)
  File "/some/dir/lib/python3.8/site-packages/moto/s3/responses.py", line 317, in _bucket_response
    return self._bucket_response_post(request, body, bucket_name)
  File "/some/dir/lib/python3.8/site-packages/moto/s3/responses.py", line 855, in _bucket_response_post
    return self._bucket_response_delete_keys(request, body, bucket_name)
  File "/some/dir/lib/python3.8/site-packages/moto/s3/responses.py", line 947, in _bucket_response_delete_keys
    bucket_name, undo_clean_key_name(key_name), version_id=version_id
  File "/some/dir/lib/python3.8/site-packages/moto/s3/utils.py", line 105, in undo_clean_key_name
    return quote(key_name)
  File "/some/dir/lib/python3.8/urllib/parse.py", line 839, in quote
    return quote_from_bytes(string, safe)
  File "/some/dir/lib/python3.8/urllib/parse.py", line 864, in quote_from_bytes
    raise TypeError("quote_from_bytes() expected bytes")
TypeError: quote_from_bytes() expected bytes

The problem is apparently using xmltodict.parse with its default settings, which strips whitespaces, resulting in None as value if the value contained only whitespaces:
>>> import xmltodict
>>> xmltodict.parse(b'<Delete xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Object><Key> </Key></Object></Delete>')
OrderedDict([('Delete', OrderedDict([('@xmlns', 'http://s3.amazonaws.com/doc/2006-03-01/'), ('Object', OrderedDict([('Key', None)]))]))])

A fix would be to disable stripping whitespaces when parsing XML and that also sounds reasonable to me, however I'm not sure if that'd break something else:
>>> import xmltodict
>>> xmltodict.parse(b'<Delete xmlns="http://s3.amazonaws.com/doc/2006-03-01/"><Object><Key> </Key></Object></Delete>', strip_whitespace=False)
OrderedDict([('Delete', OrderedDict([('@xmlns', 'http://s3.amazonaws.com/doc/2006-03-01/'), ('Object', OrderedDict([('Key', ' ')]))]))])

Also as xmltodict.parse is used in various parts of moto it might make sense to revisit the default of stripping whitespace everywhere where it's used, as even if the value not only contains whitespaces, stripping them might result in a different behavior than how the AWS APIs behave.

Thanks for raising this @Dunedan, and for providing the cause/solution.
Marking it as a bug.


Suspending PC and restarting causes parts of vscode to become glitchy

VSCode Version: 1.44.2
OS Version: Linux pop-os 5.4.0-7626-generic #30~1588169883~20.04~bbe668a-Ubuntu SMP Wed Apr 29 21:00:02 UTC  x86_64 x86_64 x86_64 GNU/Linux
V8: 7.8.279.23-electron.0
Commit:  ff915844119ce9485abfe8aa9076ec76b5300ddd

Steps to Reproduce:

Suspend PC
Reopen PC

Does this issue occur when all extensions are disabled?: Yes/No
Yes
Screenshot -> https://postimg.cc/14rJp08P

Looks same as #69665


Figure out why can't the Airnode be deployed to the ap-northeast-3 AWS region

Regarding https://github.com/api3dao/airnode/issues/1429#issuecomment-1269827278

I've confirmed Airnode can be deployed to ap-northeast-3 with a blockchain request, HTTP gateway request, and HTTP signed data gateway request. CloudWatch logs were showing up under the ap-northeast-3 region as expected. It's possible the previous error in the referenced comment was transient or AWS has increased the number of services in the region since the test.

One could only wish for periodic CI across all supported regions


mobile-detect pixel size device change

This is more of a question then a problem. Can please somebody tell at what screen size will mobile-detect report tablet, mobile. For example, if width is below 320px it's mobile. I cannot find this information.
Thank you

http://hgoebl.github.io/mobile-detect.js/doc/MobileDetect.html

maxPhoneWidth | number |  | 600 | only for browsers specify a value for the maximum width of smallest device side (in logical "CSS" pixels) until a device detected as mobile will be handled as phone. This is only used in cases where the device cannot be classified as phone or tablet.See Declaring Tablet Layouts for Android.If you provide a value < 0, then this "fuzzy" check is disabled.


How to receive calls?

Before adding this issue, make sure you do the following to make sure this is not a duplicate:

Search through the repo's previous issues
Read through the readme at least once
Search the docs for the feature you're looking for

Just describe the feature

?????????????????????????????????????????????????????????????????????????????????????????????????????????????


How can one suggest new entries?

Hello,
I would like to know how I could suggest new domains to block? They would go in the porn category.
I'm familiar with Github, so making a PR is fine, but since this repo relies on external sources, I'd like to be sure this repo is the right place to do so.

Hi @ColinMaudry, thanks for the good question.
The porn data sources are found in the extensions folder for porn.  So opening an issue with @clefspeare13 (issues) or @sinfonietta (issues) should get prompt attention as both are regular updaters.

@StevenBlack is there any way you could add in the readme a link to who to suggest edits to since I've opened a thread like this before and have seen others also.

@Jezza-x3 good idea!

And with a PR, could it work this way:

I fork StevenBlack/hosts
I update hosts/extensions/porn/clefspeare13/hosts and hosts/extensions/porn/sinfonietta/hosts with the new entries
I make a PR in which I tag @sinfonietta and @clefspeare13
They validate it and merge it

Deal?

The way it works is,

Host file sources update their lists as they wish.
Every few days this repo updates itself to include their changes.

Therefore for Github-based sources, either open an issue there, or fork/push to source repos.
Alternately if you have more than a passing interest in this, you could become a source of hosts.  In that case, fork this repo, and add yourself either to the data folder for general malware, or to the extensions folder for specialty lists like porn, gambling, etc.
Good?

Awesome. :+1:


DBZ-8346 Use DebeziumSinkRecord instead of Kafka Connect's SinkRecord inside Debezium sink connectors

pt.1 Refactor TableId to CollectionId and related classes/variable name changes and refactoring, introduce debezium-sink package

relates to https://issues.redhat.com/browse/DBZ-8346

@jpechane looks like the failing MongoDB 7.0 test was a hiccup kind of issue from the 7.0 image. Tests worked now after another restart this morning and local tests with -Dversion.mongo.server=7.0' were green too.
I'll be adding the second commit with the DebeziumSinkRecord interface and related implementations later.

@jpechane I have added the second commit to add DebeziumSinkRecord. Local tests were all good now. Waiting for CI now.

@jpechane I have added a hopefully working Field#withDeprecatedAliases() method to allow defining deprecated alias configs. The change is deep with the changes done to the Field and Configuration classes. I hope the logic is still okay and won't harm previous code. We need to carefully check the addition in the extra 3rd commit.

The change is deep with the changes done to the Field and Configuration classes. I hope the logic is still okay and won't harm previous code. We need to carefully check the addition in the extra 3rd commit.

Can we add a test?

@rk3rn3r LGTM, thanks a lot! I left just few comments, the most important relates to config option names. When addresd the PR can be merged.

@jpechane if we're concerned with configuration option names being changed without leaving deprecated predecessors, wouldn't the same apply to the changes made to TableNamingStrategy and ColumnNamingStrategy. The contracts are completely different and the old ones are not left in-place with default methods to make the transition easy. As is, any user who customized those public hooks won't be able to upgrade without changes.

@Naros if those things are an issue it should be easy to provide old contracts that call the new functionality, but I think we never guaranteed compatibility on the code API layer, did we?

@Naros if those things are an issue it should be easy to provide old contracts that call the new functionality, but I think we never guaranteed compatibility on the code API layer, did we?

Hi @rk3rn3r since these are contracts that can be supplied by user/customers, we need an adapter layer to make sure that in a micro-release that these continue to function as-is with warnings that notify the user they should consider porting their code to use the new contracts and we'll remove the adapter/deprecation layer bits in 3.1.

@Naros do you mean config options or really the old class names?

@rk3rn3r Hi, generally if we providea way for the user to inject his own code (even if it is not yet matured into API module) we must not break the contract in microreleases. For that reaosn a code that was written with the old interfaces must still compile and be runnable. Ideally there will be a compatibility/legacy layer that would ensure the old contract is still available and will be removed later in one of minor releases.

@rk3rn3r Applied, thanks a lot!


delivery pipeline

@zoeself register

@zoeself register

@h1alexbel I've just registered this ticket as a task and will assign it to someone soon. Thanks!

@h1alexbel this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-09-20T15:09:18.801966.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@h1alexbel Don't forget to close this ticket before the deadline (2023-09-20T15:09:19). You are past the first half of the allowed period.

@h1alexbel Looks like you've missed the task deadline (2023-09-20T15:09:19). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@lisitsaaa Looks like you've missed the task deadline (2023-09-30T15:29:53). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@erstediy this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-11-19T14:33:06.370792.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@erstediy Don't forget to close this ticket before the deadline (2023-11-19T14:33:06). You are past the first half of the allowed period.

@erstediy Looks like you've missed the task deadline (2023-11-19T14:33:06). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@LeonovAlexProg this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-11-29T15:01:51.368182.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@LeonovAlexProg Don't forget to close this ticket before the deadline (2023-11-29T15:01:51). You are past the first half of the allowed period.

@l3r8yJ this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-12-09T15:32:18.953475.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@l3r8yJ Don't forget to close this ticket before the deadline (2023-12-09T15:32:19). You are past the first half of the allowed period.

@l3r8yJ Looks like you've missed the task deadline (2023-12-09T15:32:19). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@PavelRyauzov this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-12-19T16:01:53.069781.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@PavelRyauzov Don't forget to close this ticket before the deadline (2023-12-19T16:01:53). You are past the first half of the allowed period.

@PavelRyauzov Looks like you've missed the task deadline (2023-12-19T16:01:53). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@iColdLight this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2023-12-29T16:30:47.703147.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@iColdLight Don't forget to close this ticket before the deadline (2023-12-29T16:30:48). You are past the first half of the allowed period.

@iColdLight Looks like you've missed the task deadline (2023-12-29T16:30:48). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@NikiTuz18 this is your task now, please go ahead. Deadline (when this ticket should be closed) is 2024-01-08T17:00:06.599024.
Estimation here is 60 minutes, that's how much you will be paid.
Remember, you don't have to solve everything in this ticket - you can solve it partially and leave todo markers in the code, which will become future tasks.
If you have any questions don't ask me, I'm not a technical person. Open new tickets instead.
If you don't have time or simply don't want to work on this, you can always resign.

@NikiTuz18 Don't forget to close this ticket before the deadline (2024-01-08T17:00:07). You are past the first half of the allowed period.

@NikiTuz18 Looks like you've missed the task deadline (2024-01-08T17:00:07). You are now resigned from this task.
Please stop working on it, you will not be paid. I will assign it to someone else soon.

@h1alexbel I couldn't find any assignee for this task. This is either because there are no contributors with role DEV available or because the project does not have enough funds.
Please, make sure there is at least one available contributor with the required role and the project can afford to pay them.

@h1alexbel I couldn't find any assignee for this task. This is either because there are no contributors with role DEV available or because the project does not have enough funds.
Please, make sure there is at least one available contributor with the required role and the project can afford to pay them.

@h1alexbel I couldn't find any assignee for this task. This is either because there are no contributors with role DEV available or because the project does not have enough funds.
Please, make sure there is at least one available contributor with the required role and the project can afford to pay them.


System setup.

Hi all gurus,
I have a hard time in setting this Zenbot system so, that it is doing some trading for me.
I followed the guide as described on https://github.com/carlos8f/zenbot

git clone https://github.com/carlos8f/zenbot.git
I have copied conf-sample.js to conf.js and changed it to my polonium credentials.
Since I have docker installed (seemed a logical step to me; trusting the guide). I executed:
cd zenbot
docker-compose build
docker-compose up
Then I should be able to get a list of selectors with the command zenbot list-selectors, but all I get at this step is: -bash: zenbot: command not found.

Pff what else is there to say.. I have a localhost-site running at localhost:27017. But that only shows me a text line with: "It looks like you are trying to access MongoDB over HTTP on the native driver port."
I was expecting that nice graphics etc.
Another point is what I don't get is that at some point I need to 'read' the history of the market; but I can't use the zenbot in a command box whatsoever.
As you can see; there are quite some open issues left to get it working.
I can provide you with more info (if there's any) but I'm not aware of posting... lol
Many thanks if you find some time to help me out.

There's a lot of things that you might want to consider studying and learning... Port 27017 is the mongo db port, so you should not be accessing it via the browser.
Maybe start reading the mongodb manual, then follow to the nodejs manual. Then, maybe, come back to this project.

Hehe, seems I have some homework to do. And all I was thinking that I was on the right way.
I made too many assumptions, like trusting that all would work well after going through the steps.
I will check the documentation of the mentioned software.
Thanks!

It's your best shot. Indeed, I also think the documentation needs the improve, but Carlos and his team and putting a lot of effort on getting bugs fixed and more features released (they released version 4, I believe).
The project is awesome and I am studying the code and the Docker/Composer configuration because it is also not working for me and, I would like to help exactly there if I can
Cheers and good luck.
Ps: I installed this on my MacOS yesterday (no Docker) and it's working just fine. If you're on Windows, Carlos said on his page for version 3 that he doesn't support that. Cheers.

I am on a mac as well. The docker part just confused me a bit at the installation. Maybe working without docker is easier..
 I am doing similar work, though in another expertise. So I'm back to level n00b here. ;-)

I found out that executing npm link gave an issue; zenbot wasn't placed into /usr/local/bin/
I can now finally use the zenbot 'command'..

This is what I get now. It looks like a live stream from the coin, but nothing to be traded.

Do you still have a specific issue here that you need help with, or did you resolve most of your problems?


A wild unit test appeared

It used unittest

Related to issue #298

retest this please

Sorry, I'm not sure what you mean

"retest this please" is a message to our Jenkins continuous integration. It triggers a new build. If you were on our cool gpkitci e-mail list, you would know this PR was failing our CI tests due to #299, but is now passing since #299 is fixed  :)

+1 for merging once inline comments from this and #298 are addressed.


Add handwrite prescription support (image translation API)

I would suggest looking at these projects for possible integration. But they might compromise patient privacy, which should be checked before integration.
Pillow
tessdoc
opencv
tensorflow
pytorch

I'm taking this issue.
This might take some time, but I'll take care of that between tests.

This feature won't be integrated into the project.
After discussing the matter with @royashcenazi, we have identified two main issues with the feature:
The primary problem is that when capturing pictures, most cameras also capture a significant amount of irrelevant information alongside the relevant data. Unfortunately, the project does not currently possess the capability to filter out only the relevant information, and it is unlikely to support such a service in the foreseeable future.
The second issue is that the image recognition aspect of the feature is too resource-intensive and heavy, causing performance and efficiency problems within the project.


Is there a way to save torrent files?

I see you can make a Metadata object from file. Would it be possible to implement creating it from a MagnetLink and then having a save method for creating a torrent file?

This project had been dropped as i no longer had any need for it. I have come back to it over the last few days and will be doing some tidying up and adding torrent file read/write.


Open browser automatically when in dev mode

I remember there was a library in https://github.com/vaadin/skeleton-starter-flow-spring which would open the browser after the app booted up, by  Arthur.

This is the library: https://github.com/vaadin/open

Actually Vaadin 23+ offers DevModeHandlerManager.launchBrowserInDevelopmentMode(url) which can be obtained via DevModeHandlerManager.getDevModeHandler(). Vaadin doesn't call it automatically since Vaadin does not generally know which hostname and port Jetty has been started on.

Can't use DevModeHandlerManager.getDevModeHandler() since Vaadin-Boot would not receive the Vaadin Service directly. We'll call Open.open(url) directly instead.

Fixed in Vaadin-Boot 10.2


taxon constraint of term GO:0103012

Hi,
The term GO:0103012 ferredoxin-thioredoxin reductase activity can currently only be annotated to taxon Viridiplantae. However, Cyanobacteria have this activity also, please see UniProt entry Q55389 annotated by me and for example PubMeds 14769790 and 17611542, and IPR024707 present in the UniProt entry. Even the GO term itself in QuickGO has mentioned PubMed 14769790 as reference.  I think some algae (for example Rhodophyta and Cryptophyceae) can also be annotated to this term since they have chloroplasts. Could you please check and help to widen the taxon constraint?
Thank you!
Best wishes,
Kati (from PIR)

Also added
GO:0030386	ferredoxin:thioredoxin reductase complex	NCBITaxon:1117	Cyanobacteria

Fixed. @laihokati Do you want to check here: https://github.com/geneontology/go-ontology/blob/master/src/taxon_constraints/only_in_taxon.tsv
to see if there are terms that have only_in_ Viridiplantae that should also have cyanobacteria ?
Thanks, Pascale


nucleo-f756zg: rtos aware debugging not working

Describe the bug
In this video (50:30) it is shown how to debug a reel-board using gdb.
To Reproduce
The following commands are issued:
cd zephyr/samples/philosophers
west build -b nucleo_f756zg
west build --target guiconfig (set OPENOCD support)
west debug
(gdb) c

Output looks fine

If I interrupt, it looks like this, seemingly no threads detected by gdb?

Expected behavior
However I'm expecting something like this (as shown in the video)

I've checked my Konfig, but the problem remains.

Impact
I can't really start developing with Zephyr.
Environment (please complete the following information):

OS: MacOS
Board: Nucleo-F756ZG
Commit SHA: f3d9808012

@maksimdrachov Thread awareness support was only merge relatively recently in openocd (http://openocd.zylin.com/#/c/4988/).
Can you check you're using a version that embed this patch ?

Hmm you're right
Upgraded openocd to the latest commit:

I've removed the previous install to make sure there was no chance of the older version being used. Used the following commands:
brew uninstall openocd
brew install openocd --HEAD

Serial output seems to be working as expected:

However the same issue remains:

Any other suggestions?
Should I take this to openocd?
Are there any tools you could recommend that work with STM32 and Zephyr?

@maksimdrachov Ok, thanks for having had a try. I'll have a check on my side as well.
As an alternative, you should be able to use pyocd.
Also, you could use Segger, but please note that it currently dos not work for some targets, so I'd not advise it right now.

@maksimdrachov One additional piece of info:
In the video you mention, pycocd is the debugger in use.
For openocd, one additional config can be required (to be added in /support/openocd.cfg)
# Enable Zephyr thread awareness.
$_TARGETNAME configure -rtos Zephyr

But I've not been able to test yet.

Ok, I'll try to test 👍

It works! Big thanks!
The proposed (working) solution can be seen in the screenshot below:

ok, great. We need need to set this by default. I'll raise an issue for that.

@maksimdrachov I'm closing current issue.


Translate theme

Your current Sonic version
1.3.3
Describe this feature
Hello friends! How to translate default theme to russian or english language?
Additional information
Please help!

Sorry about that. The project is currently only available in Chinese as we’re still working on i18n support.


Better error reporting on URI not found

When a URI is not found, should give a proper error page.

Seems to not be run into anymore.  But the views/ methods should have proper error pages if somehow they are reached and no item can be found.

This is fixed.


Sort scripts alphabetically

Fix #47

Thank you for your help, and congrats on your first pr to this repo!!🎉
If you like this repo don't  forget to 🌟


Lost temperature chart

Hi!
Using Beszel 0.3 with Ubuntu 24 / CasaOS 0.4.11, Intel(R) N100 (4c / 4t)
Suddenly the temperature chart disappeared, I tried to reinstall but nothing works
Any ideas?
Thanks

Do your system_stats records in PocketBase have a t property?
If not, it's a problem with the agent reading sensors. It gets the values from these directories, so make sure there are files showing up in at least one of them.
ls /sys/class/hwmon/hwmon*/temp*_input
ls /sys/class/hwmon/hwmon*/device/temp*_input
ls /sys/class/thermal/thermal_zone*/

Also check that the sensors command shows sensors, and restart the agent if you haven't.

Do your system_stats records in PocketBase have a t property?
If not, it's a problem with the agent reading sensors. It gets the values from these directories, so make sure there are files showing up in at least one of them.
ls /sys/class/hwmon/hwmon*/temp*_input
ls /sys/class/hwmon/hwmon*/device/temp*_input
ls /sys/class/thermal/thermal_zone*/

Also check that the sensors command shows sensors, and restart the agent if you haven't.

No t section in system stats: {
"cpu": 1.32,
"d": 467.35,
"dp": 7.49,
"dr": 0,
"du": 33.21,
"dw": 0.05,
"m": 15.4,
"mb": 12.45,
"mp": 16.67,
"mu": 2.57,
"nr": 0,
"ns": 0,
"s": 4,
"su": 1.06
}
Already restarted the agent. I'll check the files laters.
Thanks for the support 🫡

Hello, I am having the same problem.
Hub: v0.4.0
Agent: v0.4.0
OS: Ubuntu 24.04 / Docker 27.3.1
System_stats records in PocketBase dosen't have a t property.
{
  "cpu": 0.6,
  "d": 454.37,
  "dp": 1.72,
  "dr": 0,
  "du": 7.43,
  "dw": 0.01,
  "m": 7.48,
  "mb": 0.49,
  "mp": 4.53,
  "mu": 0.34,
  "nr": 0,
  "ns": 0,
  "s": 4
}

sensors has return information.
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:            N/A

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +27.8°C

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +40.0°C  (high = +105.0°C, crit = +105.0°C)
Core 0:        +39.0°C  (high = +105.0°C, crit = +105.0°C)
Core 1:        +39.0°C  (high = +105.0°C, crit = +105.0°C)
Core 2:        +39.0°C  (high = +105.0°C, crit = +105.0°C)
Core 3:        +39.0°C  (high = +105.0°C, crit = +105.0°C)

nvme-pci-0400
Adapter: PCI adapter
Composite:    +39.9°C  (low  =  -0.1°C, high = +71.8°C)
                       (crit = +89.8°C)

If not, it's a problem with the agent reading sensors. It gets the values from these directories, so make sure there are files  showing up in at least one of them.
ls /sys/class/hwmon/hwmon*/temp*_input
ls /sys/class/hwmon/hwmon*/device/temp*_input
ls /sys/class/thermal/thermal_zone*/

$ ls /sys/class/hwmon/hwmon*/temp*_input
/sys/class/hwmon/hwmon0/temp1_input  /sys/class/hwmon/hwmon2/temp1_input  /sys/class/hwmon/hwmon3/temp2_input  /sys/class/hwmon/hwmon3/temp4_input
/sys/class/hwmon/hwmon1/temp1_input  /sys/class/hwmon/hwmon3/temp1_input  /sys/class/hwmon/hwmon3/temp3_input  /sys/class/hwmon/hwmon3/temp5_input

$ ls /sys/class/hwmon/hwmon*/device/temp*_input
ls: cannot access '/sys/class/hwmon/hwmon*/device/temp*_input': No such file or directory

$ ls /sys/class/thermal/thermal_zone*/
/sys/class/thermal/thermal_zone0/:
available_policies  cdev0_weight      cdev1_weight      cdev2_weight      cdev3_weight      cdev4_weight  hwmon0           k_i   mode    power      sustainable_power  trip_point_0_temp  trip_point_1_temp  trip_point_2_temp  trip_point_3_temp  trip_point_4_temp  trip_point_5_temp  uevent
cdev0               cdev1             cdev2             cdev3             cdev4             device        integral_cutoff  k_po  offset  slope      temp               trip_point_0_type  trip_point_1_type  trip_point_2_type  trip_point_3_type  trip_point_4_type  trip_point_5_type
cdev0_trip_point    cdev1_trip_point  cdev2_trip_point  cdev3_trip_point  cdev4_trip_point  emul_temp     k_d              k_pu  policy  subsystem  trip_point_0_hyst  trip_point_1_hyst  trip_point_2_hyst  trip_point_3_hyst  trip_point_4_hyst  trip_point_5_hyst  type

/sys/class/thermal/thermal_zone1/:
available_policies  emul_temp  integral_cutoff  k_d  k_i  k_po  k_pu  mode  offset  policy  power  slope  subsystem  sustainable_power  temp  type  uevent

/sys/class/thermal/thermal_zone2/:
available_policies  integral_cutoff  k_i   k_pu  offset  power  subsystem          temp               trip_point_0_temp  trip_point_1_hyst  trip_point_1_type  trip_point_2_temp  trip_point_3_hyst  trip_point_3_type  trip_point_4_temp  trip_point_5_hyst  trip_point_5_type  uevent
emul_temp           k_d              k_po  mode  policy  slope  sustainable_power  trip_point_0_hyst  trip_point_0_type  trip_point_1_temp  trip_point_2_hyst  trip_point_2_type  trip_point_3_temp  trip_point_4_hyst  trip_point_4_type  trip_point_5_temp  type

/sys/class/thermal/thermal_zone3/:
available_policies  k_d   k_pu    policy  subsystem          trip_point_0_hyst  trip_point_1_hyst  trip_point_2_hyst  trip_point_3_hyst  trip_point_4_hyst  trip_point_5_hyst  trip_point_6_hyst  trip_point_7_hyst  type
emul_temp           k_i   mode    power   sustainable_power  trip_point_0_temp  trip_point_1_temp  trip_point_2_temp  trip_point_3_temp  trip_point_4_temp  trip_point_5_temp  trip_point_6_temp  trip_point_7_temp  uevent
integral_cutoff     k_po  offset  slope   temp               trip_point_0_type  trip_point_1_type  trip_point_2_type  trip_point_3_type  trip_point_4_type  trip_point_5_type  trip_point_6_type  trip_point_7_type

/sys/class/thermal/thermal_zone4/:
available_policies  emul_temp  integral_cutoff  k_d  k_i  k_po  k_pu  mode  offset  policy  power  slope  subsystem  sustainable_power  temp  trip_point_0_hyst  trip_point_0_temp  trip_point_0_type  type  uevent

/sys/class/thermal/thermal_zone5/:
available_policies  integral_cutoff  k_po  offset  slope              temp               trip_point_0_type  trip_point_1_type  trip_point_2_type  trip_point_3_type  trip_point_4_type  trip_point_5_type  trip_point_6_type  trip_point_7_type
emul_temp           k_d              k_pu  policy  subsystem          trip_point_0_hyst  trip_point_1_hyst  trip_point_2_hyst  trip_point_3_hyst  trip_point_4_hyst  trip_point_5_hyst  trip_point_6_hyst  trip_point_7_hyst  type
hwmon2              k_i              mode  power   sustainable_power  trip_point_0_temp  trip_point_1_temp  trip_point_2_temp  trip_point_3_temp  trip_point_4_temp  trip_point_5_temp  trip_point_6_temp  trip_point_7_temp  uevent

/sys/class/thermal/thermal_zone6/:
available_policies  emul_temp  integral_cutoff  k_d  k_i  k_po  k_pu  mode  offset  policy  power  slope  subsystem  sustainable_power  temp  trip_point_0_hyst  trip_point_0_temp  trip_point_0_type  trip_point_1_hyst  trip_point_1_temp  trip_point_1_type  type  uevent

Is there any way to fix this?
Thanks!

@timmyhbk Strange. Did you also have temperatures at one point and lose them, or did the temperatures never come in at all?
I'll try to add a debug log level to the agent in the next release to help with situations like this.

Sorry for not explaining it clearly. This machine was just installed today and has never displayed the temperature.
I have another PVE machine that has been used for a while, and it also has never displayed the temperature (installed directly as a binary on Proxmox).

On my side, I had the temperature at first

I just added 3 systems to beszel. 2 openwrt 23.05 and one ubuntu 22.04. Thermal reading only working on one.

Ubuntu has no thermal values altough sensors shows the thermals

# cat /sys/class/hwmon/hwmon*/temp*_input
27800
38850
38850
39850
44000
44000
44000
43000
42000
42000
42000
cat: /sys/class/hwmon/hwmon3/temp1_input: No data available
# cat /sys/class/hwmon/hwmon*/device/temp*_input
cat: '/sys/class/hwmon/hwmon*/device/temp*_input': No such file or directory
# cat /sys/class/thermal/thermal_zone*/temp
27800
cat: /sys/class/thermal/thermal_zone1/temp: No data available
44000

First OpenWrt has no thermals, but sensors shows them

# cat /sys/class/hwmon/hwmon*/temp*_input
cat: read error: Network is down
56000
46000
# cat /sys/class/hwmon/hwmon*/device/temp*_input
cat: can't open '/sys/class/hwmon/hwmon*/device/temp*_input': No such file or directory
# cat /sys/class/thermal/thermal_zone*/temp
49400
49000
49400
49400
48700
49400
49400
50000
49700
49700
49700
49700

Second OpenWrt has thermals (i dont have lm-sensors installed)

# cat /sys/class/hwmon/hwmon*/temp*_input
cat: can't open '/sys/class/hwmon/hwmon*/temp*_input': No such file or directory
# cat /sys/class/hwmon/hwmon*/device/temp*_input
cat: can't open '/sys/class/hwmon/hwmon*/device/temp*_input': No such file or directory
cat /sys/class/thermal/thermal_zone*/temp
56028

Noticably the third system which has thermals are the only one without any relevant files in hwmon subdirectory, also the only one not throwing error iterating trough all of those files besides "no such files".
I hope this helps finding the problem and fixing it.

Maybe an Ubuntu update broke something?

Seeing the same issue as timmyhbk, ls /sys/class/thermal/thermal_zone*/ and ls /sys/class/hwmon/hwmon*/temp*_input showing results. Sensors also showing results.
sensors
iwlwifi_1-virtual-0
Adapter: Virtual device
temp1:            N/A

nvme-pci-0600
Adapter: PCI adapter
Composite:    +46.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +46.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +50.9°C  (low  = -273.1°C, high = +65261.8°C)

acpitz-acpi-0
Adapter: ACPI interface
temp1:        +16.8°C  (crit = +20.8°C)
temp2:        +27.8°C  (crit = +105.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Package id 0:  +32.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:        +31.0°C  (high = +80.0°C, crit = +100.0°C)
Core 4:        +27.0°C  (high = +80.0°C, crit = +100.0°C)
Core 8:        +27.0°C  (high = +80.0°C, crit = +100.0°C)
Core 12:       +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 16:       +28.0°C  (high = +80.0°C, crit = +100.0°C)
Core 20:       +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 24:       +28.0°C  (high = +80.0°C, crit = +100.0°C)
Core 28:       +27.0°C  (high = +80.0°C, crit = +100.0°C)
Core 32:       +28.0°C  (high = +80.0°C, crit = +100.0°C)
Core 33:       +28.0°C  (high = +80.0°C, crit = +100.0°C)
Core 34:       +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 35:       +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 36:       +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 37:       +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 38:       +29.0°C  (high = +80.0°C, crit = +100.0°C)
Core 39:       +29.0°C  (high = +80.0°C, crit = +100.0°C)

nvme-pci-0100
Adapter: PCI adapter
Composite:    +43.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +43.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +47.9°C  (low  = -273.1°C, high = +65261.8°C)

nvme-pci-0200
Adapter: PCI adapter
Composite:    +46.9°C  (low  = -273.1°C, high = +81.8°C)
                       (crit = +84.8°C)
Sensor 1:     +46.9°C  (low  = -273.1°C, high = +65261.8°C)
Sensor 2:     +50.9°C  (low  = -273.1°C, high = +65261.8°C)

Running on Debian, in docker with agent 0.4.0. I have never had temperatures.
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 12 (bookworm)
Release:        12
Codename:       bookworm

No 't' stats either
{
  "cpu": 1.13,
  "d": 914.38,
  "dp": 1.79,
  "dr": 0,
  "du": 15.53,
  "dw": 0.03,
  "efs": {
    "pool01": {
      "d": 899.19,
      "du": 37.53,
      "r": 0,
      "w": 0
    },
    "pool02": {
      "d": 16623.97,
      "du": 9205.86,
      "r": 0,
      "w": 0
    },
    "sdb1": {
      "d": 915.82,
      "du": 3.66,
      "r": 0,
      "w": 0.03
    },
    "sdc1": {
      "d": 3666.45,
      "du": 306.96,
      "r": 0,
      "w": 0
    }
  },
  "m": 62.59,
  "mb": 17.4,
  "mp": 61.94,
  "mu": 38.76,
  "nr": 0.01,
  "ns": 0,
  "s": 0.95,
  "su": 0.01
}

The sensor data is collected using the gopsutil sensors package.
There will be a LOG_LEVEL=debug option for the agent in the next release -- likely tomorrow or Sunday -- that will print all sensor data and any errors retrieving it.
If you want to troubleshoot on your own before then, you can try this code and report back.
package main

import (
	"context"
	"fmt"

	"github.com/shirou/gopsutil/v4/sensors"
)

func main() {
	temperatures, err := sensors.TemperaturesWithContext(context.Background())
	if err != nil {
		panic(err)
	}
	for _, temp := range temperatures {
		fmt.Printf("%s: %.1f\n", temp.SensorKey, temp.Temperature)
	}
}

First time building go so took a bit of tinkering to test it and maybe I did something wrong. nevertheless it's not something I expected:
# go mod init local/sensors
go: creating new go.mod: module local/sensors
go: to add module requirements and sums:
        go mod tidy
# go mod tidy
go: finding module for package github.com/shirou/gopsutil/v4/sensors
go: found github.com/shirou/gopsutil/v4/sensors in github.com/shirou/gopsutil/v4 v4.24.8
# go build
# go build
# ./sensors
panic: Number of warnings: 1

goroutine 1 [running]:
main.main()
        /tmp/test/main.go:13 +0x145

Is there anything else i could try or do differently?

@Rhyn Thanks, that's helpful. This should print the error:
package main

import (
	"context"
	"fmt"

	"github.com/shirou/gopsutil/v4/host"
	"github.com/shirou/gopsutil/v4/sensors"
)

func main() {
	temperatures, err := sensors.TemperaturesWithContext(context.Background())
	if err != nil {
		err.(*host.Warnings).Verbose = true
		panic(err)
	}
	for _, temp := range temperatures {
		fmt.Printf("%s: %.1f\n", temp.SensorKey, temp.Temperature)
	}
}

# ./sensors
panic:  Error 0: read /sys/class/hwmon/hwmon3/temp1_input: no data available

goroutine 1 [running]:
main.main()
        /tmp/test/main.go:14 +0x156

Thanks, can you change panic(err) to fmt.Println(err)?
I think it should actually still populate the sensors that work and log it below if we don't panic.
May be an easy fix.

# ./sensors
        Error 0: read /sys/class/hwmon/hwmon3/temp1_input: no data available

acpitz: 27.8
nvme_composite: 38.9
nvme_sensor_1: 38.9
nvme_sensor_2: 38.9
coretemp_package_id_0: 42.0
coretemp_core_0: 42.0
coretemp_core_1: 42.0
coretemp_core_2: 42.0
coretemp_core_3: 41.0
coretemp_core_4: 41.0
coretemp_core_5: 41.0

This should be fixed now in 0.5.0.
If they still don't come in for you, let me know and I'll reopen the issue.
I also added a SENSORS environment variable to whitelist select sensors if you want.


2023-07-13 (13 July 2023) - Morphir Project Meeting

Date
Thursday 13 July 2023 - 11am ET / 3pm UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene, roll call, welcome new people (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve previous meeting minutes - https://github.com/finos/morphir/issues?q=is%3Aissue+is%3Aclosed+label%3Ameeting
[ ] Add Items Here
[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info

https://zoom.us/j/95452540437?pwd=TEk0bitJcVFsK3lrWVZCYmxyTm5LZz09
Meeting ID: 954 5254 0437
Passcode: 778814

Dial-in

Find your local number: https://zoom.us/u/aFGSSGV9x

Github Repo: https://github.com/finos/morphir/
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Damian Reeves @ Capital One

Edward Peters @ Capital One

Michelle Chan @ Capital One

Stephen Goldbaum @ Morgan Stanley

Ronald Ssebalamu / FINOS


python310Packages.aws-sam-translator: 1.46.0 -> 1.47.0

Description of changes

https://github.com/aws/serverless-application-model/releases/tag/v1.47.0
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

was updated in 0b7ef2dcbd6db3b6a9b7aefaa8e9fabd4efab677/#181620