Missing mapStoredMessagesToChatMessages and mapChatMessagesToStoredMessages

We are currently building a ChatMessageHistory that will be used with Prisma. This PrismaChatMessageHistory will be used in the ConversationalRetrievalQAChain. For getting and adding the messages the 'langchain/stores/message/utils' mapStoredMessagesToChatMessages and mapChatMessagesToStoredMessages must be used to convert the messages to the appropriate format. However these functions cannot be used:
TS2307: Cannot find module  langchain/stores/message/utils  or its corresponding type declarations.
Is there a reason this module cannot be found?

Module 'langchain/src/stores/message/utils' can also not be found, BaseMessage and StoredMessage are imported by the module langchain/schema. Both functions are are very small, but I would like to use the langchain functions instead of creating/copying my own.
export function mapStoredMessagesToChatMessages(
  messages: StoredMessage[],
): BaseMessage[] {
  return messages.map(mapStoredMessageToChatMessage);
}

and
export function mapChatMessagesToStoredMessages(
  messages: BaseMessage[],
): StoredMessage[] {
  return messages.map((message) => message.toDict());
}

for future ppl stumbling upon this error for other projects ( because i think this one is really a bug and should be fixed )
but i had the same issue while implementing a custom message store; and what fixed for me was using these imports instead.
`import {
mapChatMessagesToStoredMessages,
mapStoredMessagesToChatMessages

} from "langchain/dist/stores/message/utils";
import {BaseMessage, StoredMessage} from "@langchain/core/messages";
`
instead we gotta add that sweet sweet /dist/ to the path and stuff seems to work has a workaround.


Shortcut for creating new file or folder

Not sure if this exists already, but it would be handy to be able to create a new file or folder in whatever directory you're currently within (in the quick explorer) with a keyboard shortcut.
From what I see the only way to do it currently is to select the folder you want to create the new file or folder in, open the context menu with a keybind (\), then use arrow keys to select the new file/folder option. Not too bad, but I use this all the time so the extra 5 keypresses every time get a bit annoying. Also, a bit unintuitive imo to need to have a folder highlighted in the explorer in order to have these context menu options -- I think being inside the folder and then creating the file/folder would be more intuitive (I understand this is how the built in explorer's context menu options work, just giving more reasoning why this feature would be nice).

I'll take a look at something like this for the next major QE release.  I'm thinking about allowing a certain amount of hotkey customization, so I can think about adding extra commands then, too.


scipy.org down

it seems that www.scipy.org is down. Is there a known problem? Is there a mirror site?

Yes, known issue - tracked at https://github.com/numpy/numpy/issues/8779 But since the other issues are closed it keeps being asked.

The website is a different bug tracker anyway.


Adding constraint improves objective.

Hi there,
I am currently using this solver for a scheduling problem, which I have modelled as a routing problem, where my objective is to maximise. As with routing problems, I have a set of nodes to visit and have created a "Virtual Node", for where the route start and ends. I have added constraints to ensure that at the start of the route, we must go from the virtual node to an uplink node, something specific to my problem. I have done this by introducing two sets of constraints.
  for (k, s) in K.iter().enumerate() {
        let (mut vars, mut coefs) = get_empty_vars_and_coefs();
        for i in (0..N.len())
            .into_iter()
            .filter(|&n| uplink_indicies.contains(&n))
        {
            for p in 0..N[i].get_vtw(s).unwrap().len() {
                vars.push(x[k][virtual_indicies[0]][0][i][p].clone());
                coefs.push(1.0);
            }
        }
        model.add_cons(vars, &coefs, 1.0, 1.0, "start_virtual_to_uplink");
    }

    for (k, s) in K.iter().enumerate() {
        let (mut vars, mut coefs) = get_empty_vars_and_coefs();
        for i in (0..N.len())
            .into_iter()
            .filter(|&n| !uplink_indicies.contains(&n))
        {
            for p in 0..N[i].get_vtw(s).unwrap().len() {
                vars.push(x[k][virtual_indicies[0]][0][i][p].clone());
                coefs.push(1.0);
            }
        }
        model.add_cons(vars, &coefs, f64::MIN, 0.0, "start_virtual_to_uplink");
    }

x is my variable where x[k][i][p][j][q] = 1 if vehicle k goes from node i, in window p to node j, in window q. In the first set of constraints, I define that each vehicle must travel from the virtual node to an uplink node, and in the second constraints, I say they cannot go from the virtual node to any other type of node. Along with these constraints I have the other necessary constraints for a routing problem.
However, I am finding that when I have both of these constraints, I am getting an objective value of 4, whereas when I drop the first set of constraints, the solver is returning the optimal objective as 0. This has been bugging me because how can removing a set of constraints make the objective worse?
I understand that without having all of the code this isn't much to go on, however I was wondering if anyone has come across this before or if there is something potentially wrong with my formulation?
Thanks
Karl

Hi Karl!
SCIP by default has a mimization objective sense. In case you don't have it yet, maybe you need to set it to maximize?
model.set_obj_sense(ObjSense::Maximize);

Hi @mmghannam,
Thanks for the quick reply. Yeah I have set the sense this way, think I got this from an example somewhere
   // Create model     let mut model = Model::new()         .hide_output()         .include_default_plugins()         .create_prob("test")         .set_obj_sense(ObjSense::Maximize);

with_constraints.txt
without_constraint.txt
Hi, here are the logs for both with and without constraints

This doesn't look too good (in the version with constraints) but also explains this behavior. SCIP returned an infeasible solution. You should probably file an issue on the SCIP repo, but an lp file would be helpful here. You can get the file after creating the model using the write("PATH", "lp") method.
[linear] <s_less_F_if_y>: <s_0_7_0_0>[C] (+4.54747351e-13) -1.79769313e+308<y_0_7_0_0>[B] (-6.8790666e-16) <= 0;
;
violation: right hand side is violated by 1e+20

@mmghannam I have just raised an issue on the SCIP repo with the lp file as suggested. Thanks for your help with this, ill comment here if any solution is found. 👍🏻

Cool, thanks @karlsb1871! I'll close this for now, feel free to reopen if it turns out the problem is related to russcip.

@mmghannam just to update you. I raised this issue with the SCIp repo and as you suggested the error was coming from a big M constraint, where I set the coefficient to the upper bound of a variable, which I had set to f64::MAX because there was not real upper bound on the variable. Just thought I would update you in case an issue like this arises in the future 👍🏻


Can't parse DeriveInput containing an expression-position macro invocation without full feature

The input to a derive macro may contain an expression-position macro invocation (Expr::Macro) via MetaNameValue. Without full feature, the parsing of Expr stops at the ! sign, resulting in an "unexpected token" error:
#[doc = concat!("a", "b")]
#[derive(serde::Serialize)]
pub struct TestStruct {}

error: unexpected token
 --> example/src/lib.rs:3:15
  |
3 | #[doc = concat!("a", "b")]
  |               ^

Downstream issue: https://github.com/serde-rs/serde/issues/2413, https://github.com/yvt/svgbobdoc/issues/7

I believe this was fixed already in yesterday's release.


3/16/2021 Publish

Docs Build status updates of commit 8b4fcbe:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

2017-03-09-profile/docs-ref-autogen/ext/arcappliance/arcappliance/create.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/ext/arcappliance/arcappliance/delete.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/ext/arcappliance/arcappliance/deploy.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2017-03-09-profile/docs-ref-autogen/ext/vm-repair/vm/repair.yml
:white_check_mark:Succeeded
View (azure-cli-2017-03-09-profile)

2018-03-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/create.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/delete.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/deploy.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2018-03-01-hybrid/docs-ref-autogen/ext/vm-repair/vm/repair.yml
:white_check_mark:Succeeded
View (azure-cli-2018-03-01-hybrid)

2019-03-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/create.yml
:white_check_mark:Succeeded

2019-03-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/delete.yml
:white_check_mark:Succeeded

2019-03-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/deploy.yml
:white_check_mark:Succeeded

2019-03-01-hybrid/docs-ref-autogen/ext/vm-repair/vm/repair.yml
:white_check_mark:Succeeded

2020-09-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/create.yml
:white_check_mark:Succeeded

2020-09-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/delete.yml
:white_check_mark:Succeeded

2020-09-01-hybrid/docs-ref-autogen/ext/arcappliance/arcappliance/deploy.yml
:white_check_mark:Succeeded

2020-09-01-hybrid/docs-ref-autogen/ext/vm-repair/vm/repair.yml
:white_check_mark:Succeeded

latest/docs-ref-autogen/acr/scope-map.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/acr/token.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ams/asset.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/arcappliance/arcappliance/create.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/arcappliance/arcappliance/delete.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/arcappliance/arcappliance/deploy.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/ext/vm-repair/vm/repair.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/mariadb/server.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/mysql/flexible-server.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/mysql/server.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/postgres/flexible-server.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

latest/docs-ref-autogen/postgres/server.yml
:white_check_mark:Succeeded
View (azure-cli-latest)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Uml 804 enable encrypted brute force cache Part 1 - create replication group

Purpose
Creates the account-wide replication group for elasticache on redis, which will replace the current cluster.
Fixes UML-804
Approach
1 of 3 PR's, each will need to be merged in turn.

create the new replication group.
enable encryption at rest and encryption in transit

Further PR'S will:

associate the cache to app using a primary endpoint
remove the old cluster

Learning

Terraform for Elasticache and redis: https://www.terraform.io/docs/providers/aws/r/elasticache_replication_group.html
Note: this is more to prove the concept at this stage from basic terraform, will investigate the module approach further
background: https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Replication.Redis.Groups.html
investigating this approach: https://github.com/tmknom/terraform-aws-elasticache-redis

Checklist

[x] I have performed a self-review of my own code
[ ] I have added relevant logging with appropriate levels to my code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[x] I have added tests to prove my work (i have run terraform plan)
[ ] The product team have tested these changes

Coverage remained the same at 81.526% when pulling 7610a726da0a7c952cf8f2206cfd259ee651fff3 on UML-804-enable-encrypted-brute-force-cache into 83b3fc569f841853e1172e5cefa8fea4e19d29fb on master.


chore: Prepare 3.5.1

Detail

Prepare patch release to ship fix #2607 for #2605

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: 30f01939881ab17fda371221031510cb9cec84f1
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubDistributedCodeBuild6-jWcl5DLmvupS
Commit ID: 30f01939881ab17fda371221031510cb9cec84f1
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: GitHubCodeBuild8756EF16-4rfo0GHQ0u9a
Commit ID: b19b85395705372bc55ec5a0b8960fe4a9e249db
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


feat: Add ability to use different versions of templates

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] All commits are signed-off.

Summary
This change provides a template versioning solution that works as follows:

A template version to use is specified when running either docs|folders|headers.

If no version specified the latest version will be used by default.
Otherwise use the templates from the specified version.

Backward compatibility.

Version 0.0.1 will be reserved for the template versions prior to this change.
If the old template path is detected (i.e. without the template version), then the filesystem will be updated to the new path with the version.
Upon first run, old template versions prior to this change will be placed to the folder 0.0.1.
If templates have no headers then 0.0.1 version will be used.

Versioning organization.

Template and instance version is added to both: in the file system (via path) and in the headers or metadata.

Instance version validation.

Markdown:

When validating the instance the header will be used to validate the version by checking both Version and x-trestle-template-version

Drawio:

When validating the instance the metadata will be used to validate the version by checking both Version and x-trestle-template-version

Validating old trestle workspace after this change will result in the following structure:
.trestle
- author
-- __global__
--- 0.0.1
---- {old_templates}
-- task_docs or task_headers or task_folders
--- 0.0.1
---- {old_templates}

Key links:

Sonar coverage

Closes #761

I'm getting some strange log errors if I run the following:
mkdir trestle_test
cd trestle_test
trestle init
trestle author docs setup -tn my_task
trestle author docs create-sample -tn my_task

The last operation gets the following message that does not make much sense to me:
No templates outside of the version folders. with no other context.

This message is okay, the No templates outside of the version folders. is the information message that there are no "old templates". I should probably move it to debug level though.

trestle_test.zip
I attached a test trestle repo here where I created two templates (0.1.0) and (0.0.1).
0.1.0 does not seem to get recognised:
trestle author docs validate -tn my_task --template-version=0.1.0 -v
2021-11-09 20:04:50,312 trestle.core.commands.author.common:71 ERROR: Specified template version is invalid, please select other version.
```,
or

trestle author docs create-sample -tn my_task --template-version=0.1.0 -v
2021-11-09 20:05:29,233 trestle.core.commands.author.common:71 ERROR: Specified template version is invalid, please select other version.
This behaves as expected:

trestle author docs validate -tn my_task --template-version=0.0.1
No templates outside of the version folders.
New headers of level 1 were added to the markdown instance: /Users/chris/Desktop/trestle_test/my_task/sample_010_template.md.
INVALID: my_task/sample_010_template.md
VALID: my_task/sample.md
VALID: my_task/my_task_000.md
VALID: my_task/my_task_001.md
VALID: my_task/my_task_002.md

However this does not

trestle author docs validate -tn my_task
No templates outside of the version folders.
New headers of level 1 were added to the markdown instance: /Users/chris/Desktop/trestle_test/my_task/sample_010_template.md.
INVALID: my_task/sample_010_template.md
VALID: my_task/sample.md
VALID: my_task/my_task_000.md
VALID: my_task/my_task_001.md
VALID: my_task/my_task_002.md
Under this scenario where a template version was not passed I would expect an optimistic test of the available templates.

@butler54 - what you've got in your example is certainly not what the code expects - but I view that as showing places where this PR is missing changes and tests that it needs - I'm thinking through how to address these gaps.

Given the current implementation the two cases above are expected behaviour. For the second case if no version is specified then it will default to the latest template version in Trestle resources (which in this case 0.0.1).
As of the first case:
In my understanding, template versions is something that is coming from Trestle (hence x-trestle-header-version). The user is expected to generate the folders inside of the .trestle/author via execution of the setup command. And then modify it as they wish. Therefore the check on the available version is done by checking what templates versions are available inside the Trestle internal resource folder not the workspace. Since currently the only version inside Trestle is 0.0.1 a call for all other templates versions will fail. In this way, versioning is entirely managed by Trestle.
On the other hand, if we would like to put template versioning in user's hands then I can modify the code slightly to do the check on what versions are available inside .trestle/author/{task} folder rather than in Trestle resources.  In this case, upon the setup command execution, user can specify any version and Trestle will create that folder with a generic template in it.
From my perspective, I think both ways are valid. Former restricts users in the number of possible template versions and ensures that users use setup to create a task. Later gives more freedom to the users and allows them to manually create different template versions for each task.
If the later is what you had in mind, I can slightly modify the code to reflect that.

@butler54 @jayhawk87 I have modified the logic for the template versioning.
Overall the logic is now as follows:

User can create any version of the template for the task as follows:

trestle author docs setup -tn -tv=11.12.123

This will initialize a folder with a template that has 'x-trestle-version-template' set to the provided version.

User then can select which template to use to create samples:

trestle author docs create-sample -tn my_task -tv=11.12.123

This will create a sample task with header or metadata set to a version of a template.

Finally user can validate samples for selected template:

trestle author docs validate -tn my_task_3 -tv=0.0.23 -hv

Set template version to 0.0.23.
Versions of the template 0.0.23 and instance 11.12.123 are different
YAML header mismatch between template /Users/enikon/Projects/trestle_test/.trestle/author/my_task_3/0.0.23/template.md and instance /Users/enikon/Projects/trestle_test/my_task_3/my_task_3_001.md
INVALID: my_task_3/my_task_3_001.md
VALID: my_task_3/my_task_3_000.md

if no version provided the latest version for this task will be used:

trestle author docs validate -tn my_task_3 -tv=0.0.23 -hv

Set template version to 11.12.123.
VALID: my_task_3/my_task_3_001.md
Versions of the template 11.12.123 and instance 0.0.23 are different
YAML header mismatch between template /Users/enikon/Projects/trestle_test/.trestle/author/my_task_3/11.12.123/template.md and instance /Users/enikon/Projects/trestle_test/my_task_3/my_task_3_000.md
INVALID: my_task_3/my_task_3_000.md

if folder contains any old templates without the version (i.e. prior to this change) they will be moved to the folder with version 0.0.1

Tested for the examples above and the output is now as expected:
trestle author docs validate -tn my_task --template-version=0.0.1 -v
Set template version to 0.0.1.
New headers of level 1 were added to the markdown instance: /Users/enikon/Projects/trestle_test/my_task/sample_010_template.md.
INVALID: my_task/sample_010_template.md
VALID: my_task/sample.md
VALID: my_task/my_task_000.md
VALID: my_task/my_task_001.md
VALID: my_task/my_task_002.md

and for other
trestle author docs validate -tn my_task
Set template version to 0.1.0.
VALID: my_task/sample_010_template.md
Headings in the instance: /Users/enikon/Projects/trestle_test/my_task/sample.md were removed.
INVALID: my_task/sample.md
Headings in the instance: /Users/enikon/Projects/trestle_test/my_task/my_task_000.md were removed.
INVALID: my_task/my_task_000.md
Headings in the instance: /Users/enikon/Projects/trestle_test/my_task/my_task_001.md were removed.
INVALID: my_task/my_task_001.md
Headings in the instance: /Users/enikon/Projects/trestle_test/my_task/my_task_002.md were removed.
INVALID: my_task/my_task_002.md

Okay I think I have one more request. I think that validate needs to be able to take multiple template versions for validation.
Why:
If I have a repo I need to be able to ask 'does my document validate with ANY of my acceptable versions'. The biggest issues I have here is when we do this with A CI pipeline the only useful flag we have for pass failure is the return code.
E.g. this can't be a human reading that A & B use version 0.0.1 and C uses 0.1.0 and that is okay. It needs to be the output of the command?

@butler54 - I agree with you because I'm thinking through what happens when I recurse through a document tree ...


Theorem environment support

Can you add some native supports for theorem enviroment? E.g.,
\begin{theorem}[Name]
\end{theorem}

\begin{solution}
\end{solution}

@dualer thank you for your suggestion. We will add it soon.

This has been added in 'mathpix-markdown-it` , see https://github.com/Mathpix/mathpix-markdown-it/blob/master/doc/theorems.md

Thank you for mentioning that @dualer

When will it be added into this extension?

@dualer it will be added in the next 24 hours (probably less than in 3 hours).

When will it be added into this extension?

This has just been updated

https://marketplace.visualstudio.com/items?itemName=mathpix.vscode-mathpix-markdown

In the latest version, i.e. v0.1.5, this function no longer works.

@dualer I've just tested it - everything is working correctly:

Did you reload window after install extension?

@OlgaRedozubova  I have done what you say, but it still doesn't work.

@dualer I tested it on different devices and it works for me.
What version of vsCode are you using?
Are there any additional extensions installed for you?
Could you share md content with me that doesn't work for you?


Properly set theme default configuration

Instead of properly setting the default value for admin.themes.enabled in the admin interface, we temporarily set it in the Opencast configuration. That's not a great workaround and it has a few problems, but I let us backport the admin interface to r/15.x to fix the major problems there.
Not that 15 is our legacy release and we already have a two 16.x versions out, it's time to properly set the default value.

Are you going to do a PR fixing it in the mainline repo as well?  From 16.x:
# Enable themes in the admin interface.
# Format: boolean
# Default: true
prop.admin.themes.enabled=false

Immediate issues:

Non-commented default
Default setting does not match listed default
Listed default does not match UI default

:D


jQuery version 2

In section External dependencies, you write that jQuery version 2 is required, but on https://github.com/select2/select2/releases its written that for Select2 4.0.0 the supported environments requires jQuery 1.7.2+.
Is this a documentation bug?

No it's not.

You can also define nested configurations, which are typically needed for options such as AJAX. Each level of nesting should be separated by two dashes (--) instead of one. Due to a jQuery bug, nested options using data-* attributes do not work in jQuery 1.x.

We use nested options like data-ajax-url.
You can try it under 1.x, but officially we don't support it.


Implement a way to update session in state using tokens

Feature request
Using supabaseClient.auth.setSession() seems to be the only way to use an access token and/or refresh token to manually update the client's knowledge of your auth session, however this does not affect the React context's session state. All of the Supabase client / Supabase context / GoTrue client functions that might achieve this appear to be private / internal.
I'd propose exposing the setSession function on the useSession or useSessionContext to solve for this, although having a loginWithAccessToken function on GoTrue that triggers "SIGNED_IN" listeners would also do the trick.
Is your feature request related to a problem? Please describe.
This has come about because I'm trying to use Supabase auth inside a Capacitor app. Because the Auth UI opens in a new app pane, when it re-opens the app with the token URLs it doesn't reload the app and subsequently trigger GoTrue's initialize function. Login works when using live reload inside Capacitor (perhaps due to it re-rendering the app root on visibilityChange?) but not when using a compiled app.
Describe the solution you'd like
Expose a function to update the session state in React context.
Describe alternatives you've considered
This could potentially be achieved further up the chain (in supabase-js or gotrue-js). My specific issue is around having up to date session data in context state though.

@floatingdino This functionality was merged in gotrue-js a couple of days ago. The version will likely be bumped in the supabase-js client this week.
https://github.com/supabase/gotrue-js/pull/581

Closing as this seem to have been resolved and OP hasn't replied since.


Update README

Please don't assume that the user is installing to their home folder.

Thanks, that is indeed a mistake. I have merged your edit!

Thank you, great project nonetheless.


define more TCP_ sockopts on bsd

seee #978
sources for sockopt numbers:

openbsd: i can't find them, so maybe they dont exist.
dragonfly: https://github.com/DragonFlyBSD/DragonFlyBSD/search?utf8=✓&q=TCP_KEEPINTVL&type=
netbsd: https://github.com/IIJ-NetBSD/netbsd-src/search?utf8=✓&q=TCP_KEEPINTVL&type=

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @alexcrichton (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

@bors: r+
Thanks!

:pushpin: Commit 09c7181 has been approved by alexcrichton

:hourglass: Testing commit 09c718164cabc312f9eca04e44e04c52af94d26c with merge 66190b3df0b89c4f7dc5c130ccef8f08f99d7295...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 66190b3df0b89c4f7dc5c130ccef8f08f99d7295 to master...


Inventory

Description

can't see the "New Item Glow". can you make it more glow or varaible, thx...
Version Number

Steps to Reproduce

Step 1
Step 2
Step 3
Step 4

Expected Behavior

Actual Behavior

Only KkthnxUI Enabled

Additional Information

Error Log

Can you test build https://github.com/Kkthnx-Wow/KkthnxUI/commit/c724f62e95c74a86de19576b88d3ab54194af552

get this error:
Stack: Interface\AddOns\KkthnxUI\Config\Elements\BadBuffs.lua:8: unexpected symbol near '<'

get this error: Stack: Interface\AddOns\KkthnxUI\Config\Elements\BadBuffs.lua:8: unexpected symbol near '<'

I am not seeing how you are getting this?

i have downloaded the file BadBuffs.lua and overwrite the original, under G:\World of Warcraft_retail_\Interface\AddOns\KkthnxUI\Config\Elements.
then i started wow again a get this error...

i use: KkthnxUI_SL-10.3.2-Release.zip

ups.. my fault. i have now the whole new file and tested and it works :-)
realy sry^^
i works and looks nice, i can see the new loot :-)
thx again.


Unable to Load Texture2D Assets

For some android games that function on Unity, the Texture 2D sprites are unreadable. How can this be fixed?

I'm getting the same issue when trying to export some Texture2D files from Darkest Dungeon 2


:bug: Fix lint issues: gofumpt linter

Please check if the PR fulfills these requirements

[ n/a] Tests for the changes have been added (for bug fixes / features)
[x] PR title follows the guidelines defined in  https://github.com/ossf/scorecard/blob/main/CONTRIBUTING.md#pr-process

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Code quality improvement

What is the current behavior? (You can also link to an open issue here)
This PR fixes issues from the gofumpt linter (various style rules).

What is the new behavior (if this is a feature change)?
n/a

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:

The Validate job failed here because the differing test cases made the dupl linter fail due to repeated code. In my opinion for test cases like this, it's perfectly fine to repeat code. If you agree with this, I'll add nolint directives to this PR.

The Validate job failed here because the differing test cases made the dupl linter fail due to repeated code. In my opinion for test cases like this, it's perfectly fine to repeat code. If you agree with this, I'll add nolint directives to this PR.

Sounds good. Please do it. Thanks

I believe the Validate job failed this time due to the issue in PR #392. Once that one is merged, this PR should be good to merge.


PRMID

Practical Deep Raw Image Denoising on Mobile Devices is published in ECCV2020, not CVPR 2020.

Got it. Thanks.


Candidate patch for #1043

This PR introduces a before_adjusting=True parameter on stream_generator(), and makes before_adjusting=False when r/all is the target of a stream, in an attempt to patch issue #1043.
This solution is an alternative to removing before adjusting altogether.
Some cassettes need to be updated before all tests can pass.

This PR looks good, and I like the simplification you've made. My curiosity is really if we need the before adjusting at all. If it still works with smaller subreddit's, and the only efficiency loss pertains to retrieving more data, I think that's totally reasonable, as we're only talking about a few KB. Alas, the complexity added isn't really that high so I'm fine with this as well, but I typically a big proponent for simplicity and I think I over-engineered this feature to begin with by attempting to be smart with the before param.
Aside from updating the necessary cassettes I we'll need docstring updates for the parameter, and I'd like to start including (added in PRAW X.X.X). when we add new features. Since this won't yet be released I think we can write (added in PRAW [unreleased]) and we can then add a sed replacement for [unreleased] with the version number as part of the release process.

Dropping the before adjusting for now is an equally sensible fix if you want to go with that.
The ideal streaming solution would involve using before adjusting, but it needs to be done in a way that accounts for the rate of activity in the target listing. I’ll figure out that way as I get around to implementing new stream in #1025.
Closing is PR in favour of the other plan. I’m not going to produce another PR for #1043 since the decided plan is easily implemented.


Feature request: automatic or relative indentation

Helm templating is really brittle due to the need to specify exact number of spaces to indent.
The problem and preferred solution  is described here: https://github.com/helm/helm/issues/3854#issuecomment-1307173074
If .toYaml cannot be fixed for some reason,  maybe due to backwards compatibility then perhaps at least add new functions for relative indenting, e.g. relindent  and relnindent that take offset relative to beginning of template call.

Unfortunately go templates don't provide enough context to do such a thing.
https://pkg.go.dev/text/template#FuncMap
When adding custom functions through FuncMap, those functions don't get any position data.

Ok, this may sound silly, but here's a way you could do it that would be less subject to human error where you calculate the relative indent by passing the preceding string.
https://helm-playground.com/#t=LQhQG92ACATBTAZgSwHb2gIgE7wDZoKoAuATJtMAL5URTQCGss0AFHvKm7gObwAeAMUJZoAagoA6aAEoZ0UpRp0YnFtVp1oAEhYAuALzRJANQZ4ArvADOk5MXgBba9GWwGxBntDRojgJ4A1vD%2B3r6%2Bwf7unnrQkNDEAPYAmgyOeDosAD7QqIScxGxohaxoAMaWCFi4BKhEZBQU4ZHRXqJyrrRAA&v=LQhQEsBcFMFsGcBcACA2gIgGbgE70ugDTLrzQDGA9gHYAm6AuqEA

Lol, this is so much worse.
I was kinda hoping this ticket would inspire some golang enthusiast to improve or fork text/template :)
I just attempted to do it myself but can't even compile it (never touched go before) :(
Although I think I see a potential way to implement it without modifying text/template.
Template.tree has information about source position  so perhaps one could find toYaml or relindent nodes there and adjust their arguments before calling Template.Execute.

Template.tree has information about source position so perhaps one could find toYaml or relindent nodes there and adjust their arguments before calling Template.Execute.

This (on the face) seems like a reasonable proposal. If the template function can know the source position (indent) when called, then it could prepend that whitespace to its output.
It would need to be a new function (toYaml couldn't be changed like this, it would break existing callers). And I like the idea of it being a helper e.g. relIndent (like you suggest). And... someone would need to find time to implement.

Right, but the template engine doesn't pass (or make available any other way) that information to the functions when they're called. Short of changing go, this just isn't possible. Since changing go falls outside the scope of what can be done in helm, I'm going to go ahead and close this. Thanks for the idea though. I learned a bit when I dug through the go source.
If go's templating engine ever gets a feature like this, feel free to propose this again.

Possibly text/template is just a poor choice for the task and it should be replaced with something that does understand that we're producing YAML and not an unstructured text.


Word filtering based on Document Frequency

An argument min_df  was added into every topic model's __init__ since 0.6.0 version.


With more information while sending logs

Description (required)
Fixes #1961
What changes did you make and why?
Have added the following:

App version > will help us identify which version of the app is having the issue
Username > will help us check if the issue is user specific
network connection type (wifi/cellular-4g/cellular-3g/cellular-2g/no-internet) > will help us check if the issue is with user's network connection
the device manufacturer and model > some of the crashes are specific to some device models. Will help us identify if that could be the issue
Android version > will help us identify if the issue is specific to an android version

Tests performed (required)
Tested on betaDebug
Screenshots showing what changed (optional - for UI changes)

Codecov Report

Merging #2222 into master will increase coverage by 0.39%.
The diff coverage is 80.28%.

@@            Coverage Diff            @@
##           master   #2222      +/-   ##
=========================================
+ Coverage    5.88%   6.28%   +0.39%
=========================================
  Files         231     234       +3
  Lines       11597   11659      +62
  Branches     1081    1085       +4
=========================================
+ Hits          683     733      +50
- Misses      10856   10864       +8
- Partials       58      62       +4

Impacted Files
Coverage Δ

...nrw/commons/utils/model/NetworkConnectionType.java
100% <100%> (ø)

...r/free/nrw/commons/utils/model/ConnectionType.java
100% <100%> (ø)

.../fr/free/nrw/commons/logging/CommonsLogSender.java
93.1% <100%> (+26.43%)
:arrow_up:

...n/java/fr/free/nrw/commons/utils/NetworkUtils.java
59.25% <56.52%> (-18.52%)
:arrow_down:

...java/fr/free/nrw/commons/utils/DeviceInfoUtil.java
75% <75%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b447612...0db41d9. Read the comment docs.

Thanks for the review @domdomegg. Have addressed the comments.
Does log file never attach for you? Have you provided storage write permissions to the app? Can you check your phone's storage and see if there's a folder for CommonsApp logs.

Looks good to me, thanks @maskaravivek :). @sivaraam has mentioned that the log files don't automatically attach for him, as well. But if everything else works, shall we merge and address that in another issue?

I've created #2265 for the logs not getting attached issue.


Update CODEOWNERS

Distributes blasten's ownership among other team members for now
Adds missing ecosystem-level owners

I just tried to divide the plugins evenly; feel free to suggest/make any changes to who gets which plugins.

Landing manually since submit-queue isn't updating.


Create bubblesort.java

Description 📜
-Added the Bubblesort algorithm in JAVA. A very famous algorithm.

Corrections # <546>

Contribution domain 📊
<! ---- Delete the options that are not relevant.
And to mark the checkbox, but x inside them, for example [x] like this ----->

[X] Others

Checklist ✅
<! ---- Delete the options that are not relevant.
And to mark the checkbox, but x inside them, for example [x] like this ----->
O.

[X] I've commented on my code, particularly in hard-to-understand areas.

<! ---- Delete the options that are not relevant.
And to mark the checkbox, but x inside them, for example [x] like this ----->
Screenshots / Gif (optional) 📸

Kindly add your working projects only, not any small program or piece of code.
This is not a DSA repo 👍


Create catalog load script

Description of changes:
Utility script to load/reload the category and product DDB tables from local yaml files.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Ran script locally using all arguments


Can't seem to add my figma or change my inputs

Extension – Figma File Search
Author: @michaelwschultz

Description

Error:

Steps To Reproduce

The current behavior
The expected behavior
Raycast version
Version: 1.28.0

@a842322 not sure exactly what you mean here. I'm assuming you had some trouble adding your Figma credentials.
You can update your credentials in the Extensions section of the settings panel.
Most likely you need to verify that you've added your Team ID correctly. The easiest way to do that is to click on your team in Figma.
Then grab the ID that comes after figma.com/files/team/**YOUR ID HERE*** in the URL.
Hopefully these screenshots help.

I'm going to close this issue as the issue template hasn't been filled and it's impossible to investigate.


Library crashes Raspberry Pi

HX711 version:
Python version:
Operating System:
Buster - Raspberry pi 4

Description
I am using the example. As soon as the print message "Reset HX711" is printed, the Raspberry Pi shutdown. This happens if I don't have any device connected or not.
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

For me this sounds like a hardware or connection issue. Do you have the possibility to run the HX711 on another RasPi and/or another HX711?

Having a similar issue on a RPI 1B
$ ./HX710B_low_pressure.py  /home/pi/.local/lib/python3.7/site-packages/hx711/__init__.py:60: RuntimeWarning: This channel is already in use, continuing anyway.  Use GPIO.setwarnings(False) to disable warnings.   GPIO.setup(self._pd_sck, GPIO.OUT)  # pin _pd_sck is output only /home/pi/.local/lib/python3.7/site-packages/hx711/__init__.py:61: RuntimeWarning: This channel is already in use, continuing anyway.  Use GPIO.setwarnings(False) to disable warnings. client_loop: send disconnect: Broken pipe
I then need to powercycle the pi

Ah, looks like GPIO 5 and 6 are not available on this model board. switched to gpio 17 and 21 which has allowed the init to complete. I have other errors now, of course. Perhaps update the example to use gpio that are available on all pi boards?


Update Union rejected idea to include _T base class

We should update the rejected ideas section for Union types to include the _T base class method that has been proposed before and highlight the challenges that it has

https://docs.google.com/presentation/d/1r4fOm4WKjUNBLmsA6oQtOCsu1By0XJLO0KNzQisevgY/edit#slide=id.g142115553c0_1_38

Fixed in af5c09a


mono not work

ubuntu@my-ip:~/ASF/ArchiSteamFarm-<IP_ADDRESS>$ ./cc.sh
INFO: Mono environment setup executed!
INFO: Mono version: 4.8.1 | Required: 5.0.0+
ERROR: You've attempted to build ASF with unsupported Mono version!

Please review the guidelines for contributing to this repository.

https://github.com/JustArchi/ArchiSteamFarm/blob/master/CONTRIBUTING.md

If my issue is not meeting contributing guidelines specified above, especially if it's a question or technical issue, please close my issue immediately - I won't complain.

You program no compiling on linux


Uncaught TypeError: Path must be a string. Received null

[Enter steps to reproduce:]

... Selected a file to rename by adding .html as file-type extension.
... Then this Uncaught TypeError 'error' showed up

Atom: 1.21.1 ia32
Electron: 1.6.15
OS: Microsoft Windows 7 Professional
Thrown From: Atom Core
Stack Trace
Uncaught TypeError: Path must be a string. Received null
At path.js:7

TypeError: Path must be a string. Received null
    at assertPath (path.js:7:11)
    at Object.join (path.js:468:7)
    at MoveDialog.module.exports.MoveDialog.onConfirm (~/AppData/Local/atom/app-1.21.1/resources/app/node_modules/tree-view/lib/move-dialog.js:41:36)
    at HTMLDivElement.Dialog.atom.commands.add.core:confirm (~/AppData/Local/atom/app-1.21.1/resources/app/node_modules/tree-view/lib/dialog.js:81:32)
    at CommandRegistry.handleCommandEvent (~/AppData/Local/atom/app-1.21.1/resources/app/src/command-registry.js:381:36)
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (~/AppData/Local/atom/app-1.21.1/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:621:22)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (~/AppData/Local/atom/app-1.21.1/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:412:28)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (~/AppData/Local/atom/app-1.21.1/resources/app/src/window-event-handler.js:100:42)
    at HTMLDocument.<anonymous> (~/AppData/Local/atom/app-1.21.1/resources/app/src/window-event-handler.js:3:65)

Commands
     -1:27.1.0 tree-view:show (atom-workspace.workspace.scrollbars-visible-always)
     -0:41.4.0 tree-view:move (span.name.icon.html5-icon.medium-orange)
     -0:36.6.0 core:confirm (input.hidden-input)

Non-Core Packages
atom-beautify 0.30.5
atom-ide-ui 0.5.2
browser-plus 0.0.98
busy-signal 1.4.3
color-picker 2.2.5
file-icons 2.1.13
highlight-selected 0.13.1
hyperclick 0.0.0
ide-typescript 0.6.2
intentions 1.1.5
js-hyperclick 1.11.1
json-schema 0.1.15
language-babel 2.76.1
less-than-slash 0.17.0
lines 0.13.1
linter 2.2.0
linter-csslint 2.0.0
linter-eslint 8.4.0
linter-htmlhint 1.3.4
linter-jshint 3.1.6
linter-jsonlint 1.3.0
linter-ui-default 1.6.10
minimap 4.29.7
minimap-linter 2.1.1
multi-cursor 2.1.5
open-in-browser 0.5.2
pigments 0.40.2
todo-show 2.1.0

Thanks for taking the time to contribute!
Based on the stack trace, I think this is a duplicate of https://github.com/atom/tree-view/issues/700 so you can subscribe there for updates if you'd like.

We noticed that this is a duplicate of https://github.com/atom/tree-view/issues/700. You may want to subscribe there for updates.
Because we treat our issues list as the Atom team's backlog, we close duplicates to focus our work and not have to touch the same chunk of code for the same reason multiple times. This is also why we may mark something as duplicate that isn't an exact duplicate but is closely related.
For information on how to use GitHub's search feature to find out if something is a duplicate before filing, see the How Can I Contribute? section of the Atom CONTRIBUTING guide.


The following settings shouldn't exist: galaxy_role_file

Testing latest commits.
Receiving following error on vagrant up.

There are errors in the configuration of this machine. Please fix
the following errors and try again:
ansible provisioner: The following settings shouldn't exist: galaxy_role_file

I've force updated requirements. Not sure if this is a Vagrant issue?

Never mind. Was a dot release behind on vagrant.

👍 Thanks, I hit this same issue. Vagrant upgrade fixed it.


Reduce html size

Relates to #7796
This covers events.
Where EventPromos and/or event json-ld is rendered, we will now only return the required data from getServerSideProps, rather than the data needed to render the entire event.

I wonder if there's a more descriptive name than EventBasic - struggling to think of one though. EventCard?

Yeah, I was struggling. It's also used for the json-ld on the page not just the card...


Authority

See linked RFC document →
RFC proposing an authority system.

In general, you can see my suspicious comments about the proposed Authority model, its coverage, immediate use-case, durability etc.
I might be missing a bigger context here but nevertheless, I'd like to see more concrete materials in those sections.
I'm not saying "no", I'm saying "maybe" and I want to say "yes", hopefully :)

I moved the SupportedAuthorityAttribute from the appendix back into the main RFC. This attribute is useful even if we do not have per NetworkBehaviour authority. It was moved into the appendix by mistake.

Closing this for now as needs more discussion


Introducing the new replay container

Requires https://github.com/FAForever/faf-java-commons/pull/151
To do:

[ ] Show the game options
[ ] Show the game version outside of the game options

I don't entirely understand what testEnrich is testing


No sell order created on GNO listing

Hey, buy order created this morning for GNO but no subsequent sell order was triggered.  Unfortunately I don’t have any logs as I was running it in the background.  Did anyone else experience this?

This error was already mentioned in #19, with included logs.

Hi - I don’t think that’s the same issue, #19 is around buying late.  Mine also bought late, but then never sold and looks like it might have bombed out when trying to sell as it was no longer running.  Will run again in the foreground see what happens next time.   I reddit user also posted this morning that they bought but no sell order was triggered.

Might bought high in the first second and then didn't sell. Looks like the idea was good, but it just instantly shoots up in price causing high buy orders. Can probably still be used for minor gains if the sell bug gets fixed.

My run also did not create a sell order and spammed 'volume'.
When looking up the order to sell, it tries to access the field 'volume', which does not exist in order.json.
My guess that it should be 'executedQty' instead.
Also, it is somewhat slow to write/read order.json from disk between buy and sell.

I also got the 'volume' spam.

^ here too

As Op states the Script runs fine, which seems somewhat impossible in my current understanding, can someone confirm the script runs succesfully when NOT in test mode?

@CyberPunkMetalHead FYI on the qty/volume issue on real orders.

Thanks, yes issue is there for live orders. That's because the trades.json schema for live and test orders are different. I will work on fixing this soon.


fix fix recursive get schema cache bug

Proposed changes
Issue Number: close #xxx
Problem summary
Error:
java.lang.IllegalStateException: Recursive load of

This is because when calling getFullSchema() of ExternalCatalog.
it will call
schemaCache.loadSchema()` -> catalog.getSchema() ->
HMSTable.getDlaType() -> HMSTable.makesureInitialized() -> initPartitionColumns() -> getFullSchema();

Which is recursive.
I refactor this logic by moving get schema logic into ExternalTable
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[ ] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[ ] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[ ] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[ ] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 34.44 seconds
load time: 487 seconds
storage size:<PHONE_NUMBER>8 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230203172213_clickbench_pr_90360.html


Clean build output

Issue type
Polishing
Problem description
Epic to address cleaning up the various warnings and messages output during the Gradle build, such as the project health warnings.
Context (optional)
No response
### Tasks
- [ ] https://github.com/gradle/gradle/pull/27934
- [ ] https://github.com/gradle/gradle/pull/27937
- [ ] https://github.com/gradle/gradle/pull/27938
- [ ] https://github.com/gradle/gradle/pull/27939

Next to check: dependency-management


fix: Add bindings.knative.dev/include label to SinkBinding sources

This PR makes sure the Eventing webhook will select the source resources, in order to inject the sink information.
This is necessary for Knative environments, that are configured with SINK_BINDING_SELECTION_MODE=inclusion. See:

https://knative.dev/v0.20-docs/eventing/sources/sinkbinding/
https://github.com/knative/operator/blob/c60e62bb86ff318c44d1520927d2182659cfdeb5/docs/configuration.md#specsinkbindingselectionmode

Fixes #2184.
Release Note
fix: Add bindings.knative.dev/include label to SinkBinding sources

I should also fix #1945.


Add a CHANGELOG.md

We should add a CHANGELOG to the htmlhint folder and update it for each release. This will show in the VS Code Extension UI.
https://code.visualstudio.com/api/working-with-extensions/publishing-extension#marketplace-integration

Closed with #53


ciliumenvoyconfig: Qualify internal listener references

Fix CiliumEnvoyConfig parsing by:

check for duplicates after resource name has been qualified
qualify internal listener references in endpoint addresses

Internal listener references are now properly qualified with namespace and CEC name.

/test


Feature Request: List of properities to ignore

I've been using this for 5 minutes, and I see huge possibilities!  I'm going to put a couple of Feature Requests in here, and will seperate them into seperate notes.
Settings: list of properities to ignore when Pulling in properties from notes to canvas.
For example, all of my notes have a property tags which I don't necessarily want on the canvas.

"I've been using this for 5 minutes" - lol.
I'll look forward to your suggestions! And your first one here is an obvious "should have been here all along" suggestion. Great call. That'll be next up.

Done. Great suggestion. Should have been the way I went the first time.

Thanks!  The more I was thinking about this, the logic may may run better the other way, or both.
So a list of properties to exclude, and/or a list of only properties to include.  In addition to the use case I posed with always wanting to exclude tags (for example, I can see folks want to include only properties x, y and z.
Kind of like the DENY_ALL _FROM / ALLOW_ALL_FROM logic used elsewhere.  I hope I'm explaining this well, and I know user documentation for this sort of inner / outer join logic can be a challenge.

Basically, a whitelist approach as an alternative to a blacklist approach. That makes sense. Technically it would be dead simple to switch from blacklist to whitelist, but including the option to use either would be a tiny bit more scaffolding than I have time for right now. I'll definitely add it on the v1.3 release at some point in the next half year or so. Thanks for the suggestions.


Switching from Travis CI to GitHub Actions

@J08nY just a notification, once we merge, you can delete the workflow on your Travis account, if everything goes well.


Define the Automatic-Module-Name manifest attribute by default for better compatibility with the Java module system

problem
Depending on an artifact published with sbt from maven can lead to "exception: Unable to derive module descriptor" because of the cross-version suffix in the jar name, see https://github.com/lampepfl/dotty/issues/12899 for details.
expectation
I think sbt should define a valid Automatic-Module-Name by default (see the discussion in https://github.com/lampepfl/dotty/issues/12899), probably based on the organization name + project name, but taking into account that according to https://docs.oracle.com/javase/specs/jls/se16/html/jls-7.html#jls-7.7 :

A module name consists of one or more Java identifiers (§3.8) separated by "." tokens.

So invalid characters must be ignored or substituted by a ".".
Users should still be able to override the Automatic-Module-Name, e.g. using a setting key.

Sounds good. I'd call categorize this to a feature enhancement rather than a bug report since it's never been our intent to support or prevent the use of Java 9 Modules.

According to:

This will happen in projects which use together Scala, Maven, and Java 9+

So it seems that this leads to issues even when no one is explicitly trying to use java 9 modules, just compiling code on java 9+.


question about ROS workspace

Hello, I find the part about ros in your code was submitted two years ago, some of the steps are vague to me, such as the part I circled with a red box in the figure below, especially the two weights.pth files acquisition. I do not find the weights.pth of the turtlebot-end model in the downloaded models. Could you please update the readme.txt inside this ros folder to be more clear if possible? thank you

I have updated the readme.

ok， thank you.
I will try it.

Now my robot can move, but I still have a puzzle：Is the functional package map_collector in ros folder used for collecting images in real environment? How should we use it? Can you add steps for using it? Thank you.

map_collector should collect a grid-world map automatically, but it relies on more precise location information. On my robot, the odometry was not precise enough and I had to reset the turtlebot often to get enough precision.

I'm really sorry about that because the current situation is pressing for me. I need to know how did you get the dataset in the real world? Do you still have the code for this part? Especially the grid and positions in the dataset? I'd love to know where they come from? if only use the code of map_collector, can you tell me how to use it ?

I don't remember correctly, but I think I was using the following file: https://github.com/jkulhanek/robot-visual-navigation/blob/master/ros/src/map_collector/src/controller.py and manually running it with different coordinates I believe. I think I generated the list of coordinates I wanted to collect and then just executed this file.

I am sorry I omitted some scripts needed to build the hdf5 dataset. I added the scripts now. The map_collector package should generate an info.txt file as well as images and depths folder. Then you should run the https://github.com/jkulhanek/robot-visual-navigation/blob/master/scripts/build_grid_dataset.py and https://github.com/jkulhanek/robot-visual-navigation/blob/master/scripts/compile_grid_dataset.py scripts to get the final dataset.

I consulted my colleague and we came up with the following instructions on how to collect the dataset:

Activate local environment with all python dependencies installed (follow README in the root of this repository).

Copy this repository to turtlebot.

Run the following in both your local repository and the turtlebot's copy of the repository
cd ros
catkin_make
source devel/setup.bash

Run the following command (in the background) that will start the service collecting the images and storing them to /mnt/data/dataset. You can change this path in https://github.com/jkulhanek/robot-visual-navigation/blob/e2317b9b23f8c1f655770259f2e52dbf97db691d/ros/src/map_collector/src/collector.py#L7
roslaunch map_collector/launch/start.launch &

Prepare a list of coordinates for the robot to collect. Note that the robot will be collecting them only in the direction of its movement so we recommend to do a snake-like path through the grid to collect all images from all positions. Each position is specified by
the --by {x} {y} argument. Run this command as many times as you want until you collect the entire dataset.
 rosrun map_collector controller.py \
 --by 1 2
 --by 2 2
 --by 3 2
 --goal 4 2

Copy the dataset from /mnt/data/dataset to your local computer, activate a python environment and run the following commands from the root of this repository to get the final .hdf5 dataset:
python scripts/build_grid_dataset.py {path to the dataset folder}
python scripts/compile_grid_dataset.py {path to the dataset folder}.hdf5

The final dataset should be located at {path to the dataset folder}_compiled.hdf5.

Please let me know if it works.

Tomorrow I'll try it.

This figure is plotted by visualize.py in map_collector and the red points are missed, the blue is the actual points of robot,  there is question about it:
should I plot this figure according to my own real environment? Does it mean that I need change the code of required_points function for this figure?

Can you tell me the idea of generating these points by using the required_points function? It's so hard to understand the steps of get images and depths

The reason for generating the points is for you to visualize if the robot is correctly placed on the grid. It has nothing to do with collecting the images. I updated the readme with the steps needed to collect the images.

Are these points obtained through using the required_points function critical to the movement of the robot while acquiring the image? When using controller.py to move the robot, should the input position coordinates like"--by x y" be the coordinates of the generated point in the figure?

The figure is there only to guide you to which points you should collect. If you set the figure correctly, then yes, --by x y should be the coordinates of the points.  But the figure is not required.

So that means I can also control the robot to reach a certain point in the environment through the keyboard to obtain images in the environment?

You control the robot by running the controller.py script.

Images are collected automatically. You don't need to specify the actual grid points. Just run along the discrete points you want to collect and the scripts will take care of aligning the collected images to the correct grid points.

ok, I understand this now.
but what's the  main idea of getting the discrete points? or How should I to set those discrete points?
Is there any rule for getting them? Do you get those discrete points accodring to your office layouts? is the outline of the outermost layer of points similar to your office environment？

There is no rule. Set the points as you wish. I don't know your end goal, so I don't know what data you need to collect. In our case, we set the points according to the office layout.

How do you install the deepmind_lab? I have tried to intsall it , but didn't success.

I believe that after adding the scripts to generate the dataset and updating the readme the issue about the ROS workspace is resolved now. Therefore I am closing this issue. If you still have some problems please open a new issue.
@GongYanfu regarding your dmlab inquiry, please refer to the dmlab docs or open an issue in the appropriate repository.

Are these points obtained using the required_points function critical to the movement of the robot while acquiring the image? When using controller.py to move the robot, do the input position coordinates use the coordinates of the generated point in the figure?
At 2022-07-14 16:37:13, "Jonáš Kulhánek" @.***> wrote:
The reason for generating the points is for you to visualize if the robot is correctly placed on the grid. It has nothing to do with collecting the images. I updated the readme with the steps needed to collect the images.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Fix #226, quasi do not need a last statement value

Less code, more tests, less bugs :).

Less code, less bugs :).

I'm not sure why the tests are failing

Me neither. I re-ran them and now they pass. Merged, thanks!


Sort columns using a dropdown select [Griddle v1.3.1]

Hello, i am trying to achieve sorting in a variety of ways using a dropdown select with the following options for example:

Date
Price [asc]
Price [desc]

How can i connect the selected way of sorting with the column sorting and remove the arrows next to the column headings? Thanks in advance!

I have tried to do this also.  My implementation works by calling the onSort event, which I have because I implemented external control.  However when I am using the Local plugin I do not use my onSort implementation.  I have no idea how to get my custom Sort component to work with the Local plugin.

I just figured it out.  If I am using the local plugin I dispatch a GRIDDLE_SET_SORT action.
import { actions } from 'griddle-react';
const { setSortColumn } = actions;
...
function mapGriddleDispatchToProps(dispatch) {
  return {
    setSortColumn: (sortProperties) => dispatch(setSortColumn(sortProperties))
  };
}

The sortProperties looks like this:
{
  id: 'myColumn',
  sortAscending: true
}


Fix/types

Updates based on feedback for #183
@MilanKovacic here it is, sorry for the delay.

Closing in favor of #197.


OPSEXP-1862: preliminary repository chart

Ref: OPSEXP-1862
Initial implementation:

deployment with support for:

persistence
db config
env vars

configmap properties
basic helm features

would you mind squashing all commits from the second to the last? <3 (so I get here a diff of only the changes between the initial import commit and yours)

Done, though the "initial commit" may already contain some slight compared to a vanilla chart


Added jodosha/vim-godebug to Documentation/EditorIntegration.md

Added jodosha/vim-godebug to Documentation/EditorIntegration.md

Thanks @jodosha for the integration!

Thank you for Delve!
https://lucaguidi.com

On 07 feb 2017, at 22:05, Derek Parker<EMAIL_ADDRESS>wrote:
Merged #722.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


update doc for llama3

Motivation
as titled

[x] https://github.com/InternLM/lmdeploy/pull/1461
[x] https://github.com/InternLM/lmdeploy/pull/1453

ref https://github.com/InternLM/lmdeploy/issues/1459
Modification
as titled
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit tests to ensure the correctness.
If the modification has a dependency on downstream projects of a newer version, this PR should be tested with all supported versions of downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

The compatibility verification is all OK with main branch.
# TurboMind
python3 -m lmdeploy serve api_server /workdir/Meta-Llama-3-8B

# PyTorch
python3 -m lmdeploy serve api_server /workdir/Meta-Llama-3-8B --backend pytorch

# KV Cache Int8
python3 -m lmdeploy serve api_server /workdir/Meta-Llama-3-8B --quant-policy 8

# KV Cache Int4
python3 -m lmdeploy serve api_server /workdir/Meta-Llama-3-8B --quant-policy 4

# AWQ
python3 -m lmdeploy lite auto_awq /workdir/Meta-Llama-3-8B --calib-dataset 'ptb' --calib-samples 128 --calib-seqlen 2048 --w-bits 4 --w-group-size 128 --work-dir /workdir/Meta-Llama-3-8B-AWQ
python3 -m lmdeploy serve api_server /workdir/Meta-Llama-3-8B-AWQ

# press
python3 benchmark/profile_restful_api.py --server_addr <IP_ADDRESS>:23333 --tokenizer_path /workdir/Meta-Llama-3-8B --dataset /workdir/ShareGPT_V3_unfiltered_cleaned_split.json --concurrency 128 --num_prompts 1000


Update import paths from github.com/go-gitea to code.gitea.io

LGTM

Current coverage is 3.16% (diff: 100%)

Merging #135 into master will increase coverage by 0.02%

@@            master      #135   diff @@
========================================
  Files           33        33
  Lines         7845      7845
  Methods          0         0
  Messages         0         0
  Branches         0         0
========================================
+ Hits           246       248     +2
+ Misses        7579      7578     -1
+ Partials        20        19     -1

Powered by Codecov.  Last update c040f2f...9a7aba3

There, Travis is fine now. Ready to merge (just needs one more lgtm)

Why this was merged with one lgtm?

Because lgtm seems bugged or misconfigured. It use a simple contains operation to find the word lgtm without checking that the comment author is different of the PR author

I don't understand how travis could succeed on that. IMHO we should revert these changes

Everything just broke.

It seems very strange i can go build without error but my IDE cant resolve any new dependency path.

I cannot go get.

We need to revert or fix that asap. And we need a proper drone pipeline

fix import would be better than revert commit cause other PRs has been merged since.


feat(http1): add support for receiving trailer fields

Closes #2703
In https://github.com/hyperium/hyper/pull/3375 we were strict about sending trailers per RFC 7230. In this PR, I have been much more accepting of trailers. Is this the behavior we want?
Some questions:

If the client does not send TE: trailers but the server sends trailer headers, should trailers be parsed and passed along?
If the server does not include a trailers: ... header indicating which trailer headers are being returned, should trailers be parsed and passed along? I think this one is almost certainly "yes".
If the server includes trailers with invalid header names, such as Content-Length: 5, should that still be parsed and passed along?

@seanmonstar Please feel free to assign me any relevant issues. I already some blog posts on sending trailers:

https://hermanradtke.com/streaming-body-trailing-headers-axum-0-6/
https://hermanradtke.com/streaming-body-trailing-headers-hyper-1-0-and-axum-0-7/

I had planned on writing one for receiving trailers. I had a note to ask you if you wanted this sort of content in examples, the hyper.rs guides, etc.


Please add requirements.txt with versions and fix xgboost model loading

I can't load xgboost model
I tried on lastest(1.5.2) version. Python version 3.10.

My venv packages

What about requirements.txt file? This is file with required packages and versions
https://note.nkmk.me/en/python-pip-install-requirements/

Requirements.txt has been uploaded, sorry for not creating a separate virtual environment due to the competition time. This is the python package in my system, including the version of the Python package used in the competition

pyodbc==4.0.26
xgboost==1.5.2
Flask==1.0.2
pandas==0.24.2
numpy==1.19.5

Since the model is called with the new version, no joblib package is needed

Nice, thank you!


want to know how to code combine the holistic models and hand models in part of the wrist

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
None
OS Platform and Distribution
Windows in VS CODE
MediaPipe version
Version: <IP_ADDRESS>
Bazel version
No response
Solution
make the conbintion the point of the wrist in holistic and hand. how to change the code  make me know plz
Programming Language and version
python
Describe the actual behavior
holistic in part of hand and hand in part of hand are showing each other in one camera
Describe the expected behaviour
No response
Standalone code/steps you may have used to try to get what you need
No response
Other info / Complete Logs
No response

Hi @jmjang000,
Can you clarify the statement "code combine the holistic models and hand models in part of the wrist"?
Additionally, could you provide more details about your inquiry, such as the specific steps you are following from the documentation, the comprehensive support you are seeking from us, and any reference images or error logs that would help us better understand and address the issue at hand?
Thank you!

I hope to make like this photo
So we need a coded file!

Hi @jmjang000,
Apologies for the delay in response. Could you please confirm whether you still require assistance in resolving this issue or if it has been resolved from your end?
Thank you!!

Hi @jmjang000,Hi @jmjang000,
Apologies for the delay in response.답변이 늦어져서 죄송합니다. Could you please confirm whether you still require assistance in resolving this issue or if it has been resolved from your end? 이 문제를 해결하는 데 여전히 도움이 필요한지 아니면 해결되었는지 확인해 주시겠습니까?
Thank you!!고마워!!

First of all, I'm sorry for the late response. I haven't solved the problem yet. Do you have any data that can be helpful?


create build-image component - [closed]

In GitLab by @liyanq528 on Nov 21, 2017, 09:42
Merges 20171121 -> dev

In GitLab by @wknet123 on Nov 13, 2019, 10:10
closed


After updating to v2024.7.4: No weather data to parse for mapping 0

What happened?
I updated to the latest version coming from the previous stable version a few months old. I’m using my own weatherstation sensors only. Since reboot I get every hour:
2024-07-11 01:29:36.469 WARNING (MainThread) [custom_components.smart_irrigation] [async_update_all] No weather data to parse for mapping 0
2024-07-11 02:29:36.470 WARNING (MainThread) [custom_components.smart_irrigation] [async_update_all] No weather data to parse for mapping 0
2024-07-11 03:29:36.471 WARNING (MainThread) [custom_components.smart_irrigation] [async_update_all] No weather data to parse for mapping 0
2024-07-11 04:29:36.472 WARNING (MainThread) [custom_components.smart_irrigation] [async_update_all] No weather data to parse for mapping 0
How to reproduce
Wait an hour, it will happen every hour as hourly update is configured.
Relevant log output
2024-07-11 01:29:36.469 WARNING (MainThread) [custom_components.smart_irrigation] [async_update_all] No weather data to parse for mapping 0
2024-07-11 02:29:36.470 WARNING (MainThread) [custom_components.smart_irrigation] [async_update_all] No weather data to parse for mapping 0
2024-07-11 03:29:36.471 WARNING (MainThread) [custom_components.smart_irrigation] [async_update_all] No weather data to parse for mapping 0
2024-07-11 04:29:36.472 WARNING (MainThread) [custom_components.smart_irrigation] [async_update_all] No weather data to parse for mapping 0

Which version are you running?
V2024.7.4
Diagnostics file

[X] I have attached a diagnostics file

Additional information
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2024.7.2",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.12.4",
"docker": true,
"arch": "x86_64",
"timezone": "Europe/Amsterdam",
"os_name": "Linux",
"os_version": "6.6.33-haos",
"supervisor": "2024.06.2",
"host_os": "Home Assistant OS 12.4",
"docker_version": "26.1.4",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"kia_uvo": {
"documentation": "https://github.com/Hyundai-Kia-Connect/kia_uvo",
"version": "2.26.0",
"requirements": [
"hyundai_kia_connect_api==3.22.0"
]
},
"pyscript": {
"documentation": "https://github.com/custom-components/pyscript",
"version": "1.5.0",
"requirements": [
"croniter==1.3.8",
"watchdog==2.3.1"
]
},
"zidoo": {
"documentation": "https://www.github.com/wizmo2/zidoo-player",
"version": "2.0.1",
"requirements": []
},
"afvalbeheer": {
"documentation": "https://github.com/pippyn/Home-Assistant-Sensor-Afvalbeheer",
"version": "5.3.5",
"requirements": [
"rsa",
"pycryptodome"
]
},
"buienalarm": {
"documentation": "https://github.com/gieljnssns/buienalarm-sensor-homeassistant/tree/master",
"version": "1.9",
"requirements": [
"pybuienalarm==0.1.1"
]
},
"smart_irrigation": {
"documentation": "https://github.com/jeroenterheerdt/HASmartIrrigation",
"version": "v2024.7.4",
"requirements": []
},
"easee": {
"documentation": "https://github.com/nordicopen/easee_hass",
"version": "0.9.59",
"requirements": [
"pyeasee==0.8.1"
]
},
"hacs": {
"documentation": "https://hacs.xyz/docs/configuration/start",
"version": "1.34.0",
"requirements": [
"aiogithubapi>=22.10.1"
]
}
},
"integration_manifest": {
"domain": "smart_irrigation",
"name": "Smart Irrigation",
"codeowners": [
"jeroenterheerdt"
],
"config_flow": true,
"dependencies": [
"http",
"panel_custom"
],
"documentation": "https://github.com/jeroenterheerdt/HASmartIrrigation",
"iot_class": "local_push",
"issue_tracker": "https://github.com/jeroenterheerdt/HASmartIrrigation/issues",
"requirements": [],
"version": "v2024.7.4",
"is_built_in": false
},
"setup_times": {
"null": {
"setup": 0.0001160898245871067
},
"b0a728f53e166f1e6513da60a7130f51": {
"wait_import_platforms": -5.429051163839176,
"config_entry_setup": 5.539903113152832
}
},
"data": {
"use_weather_service": false,
"weather_service": null,
"store": {
"config": {
"calctime": "23:55",
"units": "metric",
"use_weather_service": false,
"weather_service": null,
"autocalcenabled": true,
"autoupdateenabled": true,
"autoupdateschedule": "hours",
"autoupdatedelay": "0",
"autoupdateinterval": "1",
"autoclearenabled": true,
"cleardatatime": "23:59",
"starteventfiredtoday": false,
"continuousupdates": false
},
"mappings": [
{
"id": 0,
"name": "Davis Vantage Pro Weerstation",
"mappings": {
"Dewpoint": {
"source": "sensor",
"sensorentity": "sensor.davis_vantage_pro2_dauwpunt",
"unit": ""
},
"Evapotranspiration": {
"source": "sensor",
"sensorentity": "sensor.davis_vantage_pro2_verdamping",
"unit": ""
},
"Humidity": {
"source": "sensor",
"sensorentity": "sensor.davis_vantage_pro2_luchtvochtigheid",
"unit": ""
},
"Precipitation": {
"source": "sensor",
"sensorentity": "sensor.davis_vantage_pro2_regenhoveelheid_dag",
"unit": ""
},
"Pressure": {
"source": "sensor",
"sensorentity": "sensor.davis_vantage_pro2_barometer",
"unit": "millibar"
},
"Solar Radiation": {
"source": "sensor",
"sensorentity": "sensor.davis_vantage_pro2_zonnestraling",
"unit": "W/m2"
},
"Temperature": {
"source": "sensor",
"sensorentity": "sensor.davis_vantage_pro2_buitentemperatuur",
"unit": ""
},
"Windspeed": {
"source": "sensor",
"sensorentity": "sensor.davis_vantage_pro2_windsnelheid_gemiddeld",
"unit": "km/h",
"aggregate": "average"
}
},
"data": [
{
"retrieved": "2024-07-11T00:06:37.868737"
}
],
"data_last_updated": "2024-07-11T00:06:37.868792"
}
],
"modules": [
{
"id": 2,
"name": "Passthrough",
"description": "Geeft waarde van ET sensor as verandering terug.",
"config": {},
"schema": []
}
],
"zones": [
{
"id": 0,
"name": "Voortuin",
"size": 80.0,
"throughput": 9.0,
"state": "automatic",
"bucket": -1.3966115997900619,
"old_bucket": 0,
"delta": 0,
"duration": 745,
"module": 2,
"multiplier": 1.0,
"explanation": null,
"mapping": 0,
"lead_time": 0.0,
"maximum_duration": 7200.0,
"maximum_bucket": 50,
"last_calculated": "2024-07-10T23:55:00.847141",
"last_updated": "2024-07-11T00:06:37.868792",
"number_of_data_points": 0
},
{
"id": 1,
"name": "Achtertuin Links",
"size": 50.0,
"throughput": 6.0,
"state": "automatic",
"bucket": -1.3966115997900619,
"old_bucket": 0,
"delta": 0,
"duration": 698,
"module": 2,
"multiplier": 1.0,
"explanation": null,
"mapping": 0,
"lead_time": 0.0,
"maximum_duration": 7200.0,
"maximum_bucket": 50,
"last_calculated": "2024-07-10T23:55:01.279282",
"last_updated": "2024-07-11T00:06:37.868792",
"number_of_data_points": 0
},
{
"id": 2,
"name": "Achtertuin Rechts",
"size": 155.0,
"throughput": 18.0,
"state": "automatic",
"bucket": -1.3966115997900619,
"old_bucket": 0,
"delta": 0,
"duration": 722,
"module": 2,
"multiplier": 1.0,
"explanation": null,
"mapping": 0,
"lead_time": 0.0,
"maximum_duration": 7200.0,
"maximum_bucket": 50,
"last_calculated": "2024-07-10T23:55:01.707422",
"last_updated": "2024-07-11T00:06:37.868792",
"number_of_data_points": 0
}
]
}
}
}

You have to go to SmartIrrigation settings in Integrations in HA, click Configure and check 'Use weather service'. Next you have to go to SI in sidebar and in 'Sensor groups' tab you have to select 'Weather service' where you don't use sensors.

So why do i need to actiivate weatherservice if i don't use it? I'm using only weatherstatyion sensors already available.
As soon as i enable continous updates the following my log is flooded with the following errors:
2024-07-11 10:11:37.147 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/config/custom_components/smart_irrigation/init.py", line 499, in async_sensor_state_changed
await self.async_continuous_update_for_mapping(
File "/config/custom_components/smart_irrigation/init.py", line 557, in async_continuous_update_for_mapping
await self.async_calculate_zone(
File "/config/custom_components/smart_irrigation/init.py", line 969, in async_calculate_zone
f"calculate_zone: modinst.name: {modinst.name} and forecast_days: {modinst._forecast_days}"
^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Passthrough' object has no attribute '_forecast_days'

I completely removed the integration and set it up again, but the same issues return..

@collateral87 please open a separate issue.

@posixx so without the experimental feature on you are not getting any updates? did the update actually run (if you go into the UI for smart irrigation you can check when it was last updated / calculated).
Now, when you turned on the experimental feature, you are clearly hitting a bug, so thanks for reporting that.

I switched from passthrough to PyETO with solrad behaviour to not calculate and forecast 3 days. That way continous updates works. I see you have released v2024.7.5; does this fix both issues? The "No weather data to parse for mapping 0" warning every hour AND "AttributeError: 'Passthrough' object has no attribute '_forecast_days'" warning?

Yes, it should fix both.

Yes it seems the warnings are gone; using passthrough again as my weatherstation has a ET sensor.
one question about the pressure sensor: Davis weatherstation uses configured height of station placement for sea-level pressure display so it can be compared with other stations. So the value it shows is the pressure as was the station placed on sea-level. Using your sensor configuration; would this be absolute or relative setting?

that's relative: https://ambientweather.com/faqs/question/view/id/1591/

Jeroen,
My log was flooded with the following errors:
2024-07-13 06:59:06.754 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:06.908 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:07.060 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:16.516 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:16.684 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:16.864 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:26.036 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:26.192 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:26.357 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:46.365 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:46.372 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:46.619 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:46.646 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:46.901 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
2024-07-13 06:59:46.930 ERROR (MainThread) [custom_components.smart_irrigation.calcmodules.passthrough] No Evapotranspiration data specified for Passthrough module
This started right after the daily calculation and till the last time above, From then on it disappeared. Could this be due to the ET sensor being reset to 0 at 0:00h?
Also another observation; yesterday it rained 17mm during the day, but still, the calculation added 1,6 mm to the bucket? I would expect to have 17mm substracted from the stock bucket value?

Yes, definitely a bug: as soon as my ET sensor is reset to 0.0 eventlog is flooded again probably until sensor > 0.0

Also after changing pressure to relative I get every hour:
2024-07-14 01:47:24.950 ERROR (SyncWorker_46) [homeassistant] Error doing job: Task exception was never retrieved (None)
Traceback (most recent call last):
File "/config/custom_components/smart_irrigation/init.py", line 745, in _async_update_all
relative_to_absolute_pressure(
File "/config/custom_components/smart_irrigation/helpers.py", line 411, in relative_to_absolute_pressure
absolute_pressure = pressure * (T0 / temperature) ** (g * M / (R * 287))
TypeError: unsupported operand type(s) for *: 'NoneType' and 'float'

Oh and I disabled continuous updates because of the flooding and now no calculation is done at the end of the day. Could be related to the problem above?


User cannot specify a fixed TFJob name

/kind bug
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
User cannot specify a fixed TFJob name, the TFJob name is used to be a generate name always even if user specified that. If so k8s will add one suffix.
https://github.com/kubeflow/fairing/blob/7e4c23c47a6b0544a722d04e1f9910c2f283a4f6/kubeflow/fairing/deployers/tfjob/tfjob.py#L80
What did you expect to happen:
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Fairing version: (use python -c "import kubeflow.fairing; print(kubeflow.fairing.__version__)"): 0.7.1
Kubeflow version: (version number can be found at the bottom left corner of the Kubeflow dashboard):
Minikube version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

NOTE: If you are using fair from master, please provide us the git commit hash.

/assign


Localization issue - untranslated text in Japanese

Describe the Bug with repro steps

Access to Power Automate.

Navigate to "Create" in the left pane.

Click "Automated cloud flow" > Enter any Flow name > Choose your flow’s trigger.

Click "Create" button.

A new design flow edit display will appear.

If it is not a new design, turn on the "New designer" toggle in the upper right corner of the screen.

Click on the flow shown on the edit display.

[Expected Result]
パラメーター
概要
[Corresponding English Text]
Parameters
About
What type of Logic App Is this happening in?
Power Automate
Are you using new designer or old designer
New Designer
Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
Workflow JSON
No response
Screenshots or Videos

Browser
Edge
Additional context
No response

The Testing tab label is also not localized:

I realized we have 2 of this issue. Closing this one in favor of tracking here: #3805


Correct the responsive design and allow user to config mediaCondition

Check if widthMedia exist and set media if it exist because deskop != default
Use editor.Config.mediaCondition to make sure that user config mediaCondition will be use

@Ju99ernaut


Black pixels around every object in generated dataset

Because the edge pixels of every object may have been lighter than the color threshold (some mix of the color of the object and the color of the background - black), the edge pixels were not filtered out. Every generated object image in the dataset includes black outlines around the object. We could use alpha matting or a similar technique to remove this outline - similar to this post and this post.

Added extra lines to remove the dark object outlines in commit f606d8f.
A side by side comparison of with and without outline removal:


Publish exporters documentation

We can use https://readthedocs.org/ like OpenTelemetry

Docs available in https://opentelemetry-azure-monitor-python.readthedocs.io/en/latest/index.html


[Mod] Knes

Mod info

Mod name: Knes
Author(s): Well
License: CC BY-NC-ND 4.0
Homepage: https://forum.kerbalspaceprogram.com/index.php?/topic/164035-191-knes-172-time-to-explore
Download: https://spacedock.info/mod/1470/Knes

https://forum.kerbalspaceprogram.com/index.php?/topic/164035-191-knes-172-time-to-explore/&do=findComment&comment=3342931

I don't use CKAN. I don't know how it works, and i don't care about it.
I don't have the time for supporting that.
But, If that respect my licence, make what you want

That sounds like it's OK with the author. :heavy_check_mark: