Explain 'uniqueTokenPerInterval'

Hello,
the API of your lib looks really simple.
Yet, I struggle to understand uniqueTokenPerInterval.
Can you please add an example to the documentation?

Yeah, that could probably be documented better.
Lets say you are using ip addresses to rate limit. This value is then the amount of different ip addresses the specific lambda container could see in the interval before it would start forgetting rate limits for the first ip addresses it has seen in the interval.
It is only really relevant if you use long interval windows and have a lot of different rate limit tokens aka users.
Does that make sense?

Yeah, that could probably be documented better.
Lets say you are using ip addresses to rate limit. This value is then the amount of different ip addresses the specific lambda container could see in the interval before it would start forgetting rate limits for the first ip addresses it has seen in the interval.
It is only really relevant if you use long interval windows and have a lot of different rate limit tokens aka users.
Does that make sense?

@simlu Hey Lukas,
it makes complete sense. 👌 Thank you.

@simlu Hey Lukas,
it makes complete sense. 👌 Thank you.


Fix execution when pasting multiple SQL statements into the REPL

Hi there,
this topic has been tweaked within #223, #274 and #300 in the past. Now, we are revisiting it again within #349.
This commit only adjusts splitting multiple statements separated by the newline character "\n" again. It might be followed up by further adjustments for also splitting SQL statements on the boundaries of the semicolon character ";".
Let's check how CI will respond to that amendment.
With kind regards,
Andreas.

Let's check how CI will respond to that amendment.

While it does not fail on SQL statements spanning multiple lines per se, it croaks on SQL statements spanning multiple lines which define UDF functions. Bummer.
https://github.com/crate/crash/blob/8e4b6d0e6efdf76cc64ad291115c2c8c68ed7dc8/tests/test_integration.py#L667-L676
Most probably, @mfussenegger tried to tackle that edge case within 280a2e4, where he stated:

Add udf function body handling to REPL multi-line detection logic

If we're in a function body of a UDF definition, a `;<CR>` should not trigger the command.

However, the corresponding PR #300 was closed.

I've added an option --multiline to enable accepting multiple SQL statements on the REPL. Feel free to add suggestions about a better naming for that option.
When crash will gain an SQL parser which can handle both multiple SQL statements and UDF functions at the same time, we might be able to remove that option again.
Synopsis
$ crash --multiline

Copy & paste:
-- Easy
SELECT 1;

-- Math
SELECT 40+2;

Hi @amotl
Thanks for looking again at multiline input support for crash.
Did you also consider using sqlparse for splitting/parsing the input SQL statements? That would mitigate the problem of the semicolon character inside UDFs.
$ cat multiline.py:

import sqlparse
import sys

def main():
    stmts = sqlparse.split(sys.stdin)
    for stmt in stmts:
        print("--------------")
        print(stmt)

main()

$ cat udf.sql:
SELECT 1;
CREATE OR REPLACE FUNCTION fib(LONG)
RETURNS LONG
LANGUAGE JAVASCRIPT
AS 'function fib(i) {
  if (i == 0) return 0;
  else if (i == 1) return 1;
  else return fib(n - 1) + fib(n - 2);
}';
-- comment
SELECT 1;

$ python multiline.py < udf.sql
--------------
SELECT 1;
--------------
CREATE OR REPLACE FUNCTION fib(LONG)
RETURNS LONG
LANGUAGE JAVASCRIPT
AS 'function fib(i) {
  if (i == 0) return 0;
  else if (i == 1) return 1;
  else return fib(n - 1) + fib(n - 2);
}';
--------------
-- comment
SELECT 1;

Hi @chaudum,

Did you also consider using sqlparse for splitting/parsing the input SQL statements?

Not specifically, but yes: When touching this topic, I also thought that there should be a mature SQL parsing library for Python which already does the right thing in any condititions.
So, thanks a stack for sharing sqlparse. I believe we should replace the hand-rolled SQL parsing routines within one of the next iterations.
With kind regards,
Andreas.

I closed https://github.com/crate/crash/pull/300 because I realized that it doesn't work for all cases.
I don't really like adding a dedicated --multiline parameter, I think copy & pasting of multiple statements should "just work". I second @chaudum input that we should probably go with sqlparse for the line-splitting logic (or copy & vendor the relevant logic)

I closed https://github.com/crate/crash/pull/300 because I realized that it doesn't work for all cases.
I don't really like adding a dedicated --multiline parameter, I think copy & pasting of multiple statements should "just work". I second @chaudum input that we should probably go with sqlparse for the line-splitting logic (or copy & vendor the relevant logic)

Thanks.

I don't really like adding a dedicated --multiline parameter.

I didn't like it as well but it was the only thing I have been able to quickly whip up.

I second @chaudum input that we should probably go with sqlparse for the line-splitting logic.

Me too!

Thanks.

I don't really like adding a dedicated --multiline parameter.

I didn't like it as well but it was the only thing I have been able to quickly whip up.

I second @chaudum input that we should probably go with sqlparse for the line-splitting logic.

Me too!

Hi again,
thanks all for your valuable information and feedback on this matter. We will use it to implement a solution for the problem. In the meanwhile, let me refer dear readers back to GH-349, and close this one.
With kind regards,
Andreas.


Add skip gradle check that doesn't run gradle checks but passes the run gradle check requirement.

Is your feature request related to a problem? Please describe.
We often make PRs such as https://github.com/opensearch-project/OpenSearch/pull/812 that are a README change or similar trivialities. This wastes a costly and time-consuming run gradle check.
Describe the solution you'd like
Admins should be able to comment run gradle check or skip gradle check which will respectively run or skip gradle check and satisfy the gradle check requirement. It should also be clear which one was chosen when looking at a PR.
Describe alternatives you've considered
Just always run gradle checks. In that case I'd want to be able to [skip gradle check] in the commit message.
Additional context
Related to https://github.com/opensearch-project/OpenSearch/issues/597

Closing now that #13498 is implemented


AFNetworkActivityIndicatorManager visibilityDelay property

A property called visibilityDelay added to
AFNetworkActivityIndicatorManager. It controls the time to wait before
showing the network activity indicator.  This is added to be able to
prevent showing the activity indicator for short periods of time as
suggest iOS Human Interface Guidelines.
https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG/Controls.html#//apple_ref/doc/uid/TP40006556-CH15-SW44

Thanks for the PR! We actually avoid flickering by having the indicator remain on the screen a little while longer. You can see the code here.
:beers:


Automatically check if rescaling is a dict that all channels which are required are present

otherwise this throws an error after a lot of computation has already been performed

should be completed in new version. Missing channels from dictionary are not rescaled per default.
User also receives a print message explicitly stating this behaviour.

implemented in code_refacotring branch.


common-api-c++-dbus: remove deprecated patches

These patches were moved from version 3.1.5 to 3.1.10 by Oleksander.
I am quite sure that one of these patches is not applicable (0001-Adds-required-dependencies-to-pc-file.patch). For the second one I cannot be sure, so I would appreciate some feedback from @jonte and Oleksander (I cannot reference his user for some reason). Was this relevant for the project you were working on? Thanks!

Thanks for the description.

@GordanM Sorry, but I am not familiar with this change :-/ We are not using CommonAPI, so I think, from our current project's perspective, it is safe to remove this patch.

@jonte thanks for the feedback!


Interested in connecting for work?

Hi,
I saw your profile on upwork. Possible to share your contact details? email would do. We could work together on fixed price projects, if you're interested.
Best regards,
Manoj<EMAIL_ADDRESS>

sure lets disucss. connect me on<EMAIL_ADDRESS>

and here is my whatsap number +923415897489


Allow securityContext to be configured via values.yaml

We require this to be a configurable value in the DaemonSet pods

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


[Q] How to turn off debug-internal.log?

It seems to cause performance issues since I use NFS which may be backed by blob storage and append will trigger full rewrite.

I figure out a workaround as the following:
# CWD is the parent of the file that executes wandb.init
mkdir wandb # can be skipped if there is one
ln -s /dev/null wandb/null

from pathlib import Path
wandb.init(
    settings=wandb.Settings(
        log_internal=str(Path(__file__).parent / 'wandb' / 'null'),
    )
)

We cannot use /dev/null directly, otherwise wandb will make dir /dev and fail.

Hi @YouJiacheng thank you for this question and the provided workaround. May I ask what performance issues is the debug-internal.log file is causing and if the above would solve your issue? You could also do something similar for debug.log file by setting the log_user argument.

Hi @YouJiacheng just following up on this issue, has this been resolved for you and would there be anything else we could help with? thanks!


Make server capabilities configurable

Public-Facing Changes
None
Description

Allows to pass in server capabilities as argument

Does this mean the websocket_server code will need to look at this list of capabilities to decide what features to toggle on/off?

Does this mean the websocket_server code will need to look at this list of capabilities to decide what features to toggle on/off?

+1, seems like it could make sense to have a server configuration where you can toggle client publishing on/off, and the server translates that to a capability? Or what were you envisioning?

Does this mean the websocket_server code will need to look at this list of capabilities to decide what features to toggle on/off?

Yes, the server will have to check if an operation is allowed to be called based on its capabilities. Is this what you mean?

Closing as this got merged with #114


kubescape: 2.2.6 -> 2.3.0

Diff: https://github.com/kubescape/kubescape.git/compare/refs/tags/v2.2.6...v2.3.0
Changelog: https://github.com/kubescape/kubescape/releases/tag/v2.3.0
Description of changes

Things done

Built on platform(s)

[ ] 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/)
23.05 Release Notes (or backporting 22.11 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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 229561 run on x86_64-linux 1

1 package built:

kubescape


feat(Explorers): deprecate services that don't respond anymore

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


KNMI-data assigned to stress periods wrongly

Right now we make an error, when we add recharge  from the KNMI-server to a model dataset. The recharge from the next stress period is assigned to the current stress period. See the code in read\knmi.py:
model_recharge = pd.Series(index=ds.time.data, dtype=float)
for j, ts in enumerate(model_recharge.index):
    if j < (len(model_recharge) - 1):
        model_recharge.loc[ts] = (
            timeseries.loc[ts : model_recharge.index[j + 1]].iloc[:-1].mean()
        )
    else:
        model_recharge.loc[ts] = timeseries.loc[ts:end].iloc[:-1].mean()

The index of the pandas Series timeseries  is equal to the end of the period that the data describes. Therefore I will change this into the following code:
model_recharge = pd.Series(index=ds.time.data, dtype=float)
for j, ts in enumerate(model_recharge.index):
    if j == 0:
        start = ds.time.start
    else:
        start = model_recharge.index[j - 1]
    mask = (timeseries.index > start) & (timeseries.index <= ts)
    model_recharge.loc[ts] = timeseries[mask].mean()

Keep in mind this will change model output in the next version.

Fixed


[Bots][Codeupdate][1471520]

Updated the C# codes under [C#/.NET]. Please review.

Docs Build status updates of commit fead8a6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit fead8a6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 222abc4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 222abc4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1a03c9d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1a03c9d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5c12877:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5c12877:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b547b2c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b547b2c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 192b2d3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 192b2d3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b2dae32:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b2dae32:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit bc8682f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit bc8682f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1f56c5b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 18, Column 252: [Warning-bookmark-not-found] Cannot find bookmark '#proactively-install-your-app-using-graph' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 25, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#create-the-conversation' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 26, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#get-the-conversation-id' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 27, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#send-the-message' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 29, Column 26: [Warning-bookmark-not-found] Cannot find bookmark '#examples' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1f56c5b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 18, Column 252: [Warning-bookmark-not-found] Cannot find bookmark '#proactively-install-your-app-using-graph' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 25, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#create-the-conversation' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 26, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#get-the-conversation-id' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 27, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#send-the-message' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 29, Column 26: [Warning-bookmark-not-found] Cannot find bookmark '#examples' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit eae39c9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 18, Column 252: [Warning-bookmark-not-found] Cannot find bookmark '#proactively-install-your-app-using-graph' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 25, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#create-the-conversation' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 26, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#get-the-conversation-id' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 27, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#send-the-message' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 29, Column 26: [Warning-bookmark-not-found] Cannot find bookmark '#examples' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit eae39c9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 18, Column 252: [Warning-bookmark-not-found] Cannot find bookmark '#proactively-install-your-app-using-graph' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 25, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#create-the-conversation' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 26, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#get-the-conversation-id' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 27, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#send-the-message' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 29, Column 26: [Warning-bookmark-not-found] Cannot find bookmark '#examples' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit aae631c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 18, Column 252: [Warning-bookmark-not-found] Cannot find bookmark '#proactively-install-your-app-using-graph' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 25, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#create-the-conversation' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 26, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#get-the-conversation-id' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 27, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#send-the-message' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 29, Column 26: [Warning-bookmark-not-found] Cannot find bookmark '#examples' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit aae631c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 18, Column 252: [Warning-bookmark-not-found] Cannot find bookmark '#proactively-install-your-app-using-graph' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 25, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#create-the-conversation' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 26, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#get-the-conversation-id' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 27, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#send-the-message' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 29, Column 26: [Warning-bookmark-not-found] Cannot find bookmark '#examples' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3d30b20:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 18, Column 252: [Warning-bookmark-not-found] Cannot find bookmark '#proactively-install-your-app-using-graph' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 25, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#create-the-conversation' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 26, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#get-the-conversation-id' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 27, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#send-the-message' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 29, Column 26: [Warning-bookmark-not-found] Cannot find bookmark '#examples' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3d30b20:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 18, Column 252: [Warning-bookmark-not-found] Cannot find bookmark '#proactively-install-your-app-using-graph' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 25, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#create-the-conversation' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 26, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#get-the-conversation-id' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 27, Column 4: [Warning-bookmark-not-found] Cannot find bookmark '#send-the-message' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 29, Column 26: [Warning-bookmark-not-found] Cannot find bookmark '#examples' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f14718e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f14718e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7bfb147:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7bfb147:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 137e566:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 137e566:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a2f0165:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit a2f0165:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5396fa2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 5396fa2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit bce4e63:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit bce4e63:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f381d7a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit f381d7a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

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

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d11f948:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:bulb:Suggestion
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 90, Column 5: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: https://docs.microsoft.com/graph/api/userteamwork-post-installedapps?view=graph-rest-1.0&tabs=http. Otherwise, remove the view parameter.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1575c58:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:bulb:Suggestion
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 90, Column 5: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /graph/api/userteamwork-post-installedapps?view=graph-rest-1.0&tabs=http. Otherwise, remove the view parameter.

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 13f9c0a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 099787b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:warning:Warning
View
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md

Line 29, Column 200: [Warning-bookmark-not-found] Cannot find bookmark '#references' in 'bots/how-to/conversations/send-proactive-messages.md'.
Line 55, Column 388: [Warning-bookmark-not-found] Cannot find bookmark '#references' in 'bots/how-to/conversations/send-proactive-messages.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 91b7f22:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 1f219c8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit cdbf802:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c4ed7f7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/send-proactive-messages.md
:white_check_mark:Succeeded
View

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 in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[New API] : Custom Captcha Generator API

Brief Description 🤓
A custom Captcha Generator is a security tool designed to create unique and unpredictable tests that differentiate between human users and automated bots. This generator leverages various challenge types, such as distorted text, image recognition, mathematical problems, and logic puzzles, to ensure robust protection against automated attacks. By implementing a diverse range of customizable Captcha challenges, it enhances the security of web applications, reduces the risk of spam and abuse, and improves user experience with intuitive and accessible verification methods.
How will you develop it?🤩
The Custom Captcha Generator is a security tool designed to create unique and unpredictable tests to differentiate between human users and automated bots. This project will be developed using HTML, CSS, and JavaScript, ensuring a seamless integration into web applications with a focus on user-friendly design and robust functionality.
Please assign this to me under GSSOC24.
Deployment
None
Select the open source program you are contributing to
Other
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINES of this project.

Greetings @PradnyaGaitonde🎀 ! , We are excited to have you dive into another issue with us!🚀
Your involvement in our project has been invaluable, and we're confident that your skills and insights will help us conquer this challenge😇.  Use command /gssoc24 to self assign the issue.  This issue represents an exciting opportunity for us to improve and enhance our project, and we are thrilled to have you on board.
We request you to follow CONTRIBUTING GUIDELINES.
Looking for your PR soon!
In case of any issues, you can contact us on Discord.❣

/gssoc24

Hey @PradnyaGaitonde ! I wanted to inform you that we have closed issue.Thank you for your understanding, and we look forward to your continued engagement with our repository🤗.
In case of any issues, you can contact us on Discord.
Thank you! ❣
Happy Coding! ✨
Will See you soon❣


Provide some logging for debug purposes

I'm not sure on this, but having a logging service set up should not hurt anyway.
When this kind of a log file could be useful? The application is based on hooking to system events and emitting some other system events, and without any means to test itself in ordinary runtime. Thus, logging of ordinary stuff just makes little sense. What does make sense, is logging exceptions, that's for sure.

Seems like using Trace is just enough.
Just need to add some time markers, and ability to output Trace to a file.
Use cases:

when developer has a bug to fix, and can actually reproduce it - this way s/he is able to track the issue down just via Visual Studio output screen;
when end user has a bug (not reproducible on dev machine) - we can give that user a "debug" version of the app, and ask him to launch it and reproduce the issue, and afterwards to send us the Trace file;

Seems legit.


Upgrade CocoaPods to v0.38.0

\c @alloy

Thank you for the contribution. It was merged directly as 7ea6d8f300793ec51daf230498502cd9571bccb3 to keep commit history cleaner. Your contribution is still credited to you.

:+1: thanks!


Update known-issues.md

EW-3421
https://community.cloudflare.com/t/cannot-convert-formdata-to-urlsearchparams-in-workers-script/184810
Checking with user manuelmeurer to confirm if it's OK to use his code as a work around.

I don't think is an issue with a modern compatibility date. url_standard should fix this, which has been default since 2022-10-31.

Confirmed to be fixed by the user via updating the compatibility date: https://community.cloudflare.com/t/cannot-convert-formdata-to-urlsearchparams-in-workers-script/184810/8?u=kiannh


Issues with jumio_mobile_sdk_flutter 4.0.0:  No type Named 'SDK' in module 'Jumio'

Describe the bug
I have download jumio4.0.0 source code and open sample app  on flutter 2.5.3 and dart 2.14.4
application is running on android device but on ios is give error in JumioModuleFlutter  class
To Reproduce
Steps to reproduce the behavior:

Install flutter 2.5.3 with dart version 2.14.4
download Jumio 4.0.0 sourceCode.zip
3.Open Example project  Run on iphone 11 PRO Simulator  (IOS 15.2)
See error

Expected behavior
To build application
Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

Device: Simulator Iphone 11 pro
IOS : 15.2
Logs:

** BUILD FAILED **
Xcode's output:
↳
Command CompileSwiftSources failed with a nonzero exit code
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:5:34: error: no type named 'SDK' in module 'Jumio'
fileprivate var jumio: Jumio.SDK?
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:6:36: error: no type named 'ViewController' in module 'Jumio'
fileprivate var jumioVC: Jumio.ViewController?
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:5:34: error: no type named 'SDK' in module 'Jumio'
fileprivate var jumio: Jumio.SDK?
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:6:36: error: no type named 'ViewController' in module 'Jumio'
fileprivate var jumioVC: Jumio.ViewController?
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:57:46: error: no type named 'IDResult' in module 'Jumio'
private func getIDResult(idResult: Jumio.IDResult) -> [String: Any] {
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:84:50: error: no type named 'FaceResult' in module 'Jumio'
private func getFaceResult(faceResult: Jumio.FaceResult) -> [String: Any] {
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:93:37: error: no type named 'DefaultUIDelegate' in module 'Jumio'
extension JumioModuleFlutter: Jumio.DefaultUIDelegate {
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:94:27: error: no type named 'SDK' in module 'Jumio'
func jumio(sdk: Jumio.SDK, finished result: Jumio.Result) {
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:94:55: error: no type named 'Result' in module 'Jumio'
func jumio(sdk: Jumio.SDK, finished result: Jumio.Result) {
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:105:50: error: no type named 'Result' in module 'Jumio'
private func handleResult(jumioResult: Jumio.Result) {
^
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:15:17: error: module 'Jumio' has no member named 'SDK'
jumio = Jumio.SDK()
^~~~~ ~~~
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:21:34: error: cannot infer contextual base in reference to member 'EU'
jumio?.dataCenter = .EU
~^~
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:23:34: error: cannot infer contextual base in reference to member 'SG'
jumio?.dataCenter = .SG
~^~
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:25:34: error: cannot infer contextual base in reference to member 'US'
jumio?.dataCenter = .US
~^~
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:33:27: error: type of expression is ambiguous without more context
guard let jumio = jumio else { return }
^~~~~
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:47:29: error: type of expression is ambiguous without more context
guard let jumioVC = jumioVC else { return }
^~~~~~~
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:49:43: error: cannot infer contextual base in reference to member 'fullScreen'
jumioVC.modalPresentationStyle = .fullScreen
~^~~~~~~~~~
/Users/ebadahmed/Downloads/mobile-flutter-4.0.0/ios/Classes/JumioModuleFlutter.swift:134:43: error: type of expression is ambiguous without more context
guard let error = jumioResult.error else { return }
~~~~~~~~^

Hello @ebadahmed93
did you make sure to run flutter pub get to actually get the SDK plugin first, as mentioned:
here --> https://github.com/Jumio/mobile-flutter/tree/master/example#usage
and here --> https://github.com/Jumio/mobile-flutter#setup
If yes and this issue still occurs, please contact Jumio support.

I have already followed the procedures but error remain same.
I will contact jumio support.

I have the same problem。
Xcode version: 13.2.1
flutter version: 2.10.1

I have the same problem。 Xcode version: 13.2.1 flutter version: 2.10.1

I am facing this issue only in simulator (tested on IOS 15.2, 14.5)
It is working on real device.
@wangyaboIOS Kindly give it a try with real device and  update if error still occurs.

Hello @wangyaboIOS, @ebadahmed93
please be aware that as of version 4.0.0, iOS simulator is required to run the latest iOS version.
--> https://github.com/Jumio/mobile-sdk-ios#general-requirements

Hello @ebadahmed93
Hello, if you want to run on the emulator, please configure Xcode.

Hello @ebadahmed93
if you want to run on the emulator, please configure Xcode.


Consider tag / releases to pair with ICAv2 release cycles.

Great to see this up and running!
Would be great to be able to version-control the ica-sdk-python in a given project to match an ICAv2 release cycle

Yes, will implement with v2.19 update coming this week!

Added for v2.20 and will do this moving forward

Thanks @kcutler0,
I think a tag like v2.20 would be better than v2.20-release but up to you, so long as it is consistent.


Module not found error

i have vue 3 project. uses webpack and laravel mix. I cant use this library on my project.
package.json
"ol": "^9.1.0",
"ol-contextmenu": "^5.4.0",
"ol-ext": "^4.0.18",
"vue3-openlayers": "^9.0.0",

app.js
import 'vue3-openlayers/styles.css';
import OpenLayersMap from 'vue3-openlayers';
app.use(OpenLayersMap /*, options */);

i installed library with no problem. but i got 90 errors when i run the project. errors are like these

Hey @oguzhankidik would you like to share your solution/ what was wrong?

Hey @oguzhankidik would you like to share your solution/ what was wrong?
i added these lines to webpack.config.js.

module: {
        rules: [
            {
                test: /\.m?js$/,
                resolve: {
                    fullySpecified: false,
                },
            },
        ],
    },


Are em's supported?

The readme was a bit confusing on this point; the example uses ems, but the docs say that ems are not supported.

I believe ems aren't supported for line-height (the idea being that you should use unit-less line-height, but all units are supported for font-size.
(right, @tptee?)

That's correct, thanks @alexlande!
I'll update the docs soon!


Adding new strata codes to TS_DepthStratum

Hi Guys,
I'm working my way through uploading the Canadian survey data, and so far, I have focused on our longest-running "Summer Survey". For this survey, all of our data lands in the strata you have listed here (http://vocab.ices.dk/?CodeTypeRelID=99&CodeID=201797).
Could you please add the following as additional valid Canadian Maritimes strata?
'396','397','398','399','400','401','402','403','404','405','406','407','408','409','410','411',
'516','517','518','519','520','521','522',
'551','552','553','554','555','556','557',
'5Z3','5Z4','5Z5','5Z6','5Z7','5Z8'

Need confirmation from the requester if he actually needs the codes

@cekv I hadn't seen this one, what is the status? should I take it?

@odontaster I think we should close this issue, since this is something the Canadiens requested long ago, but then said they did not need them anyways. I think it ended here just in case they changed their minds, but it seems like they have not - so it should be closed I think.
You could contact Mike McMahon to make sure he does not need them - only if you want :)


Laravel Debugbar prints JS to the screen when you redirect back with an email input.

Hi,
Just a heads up if you are using Laravel Debugbar with Email-Obfuscator:
When you redirect()->back()->withInput(); and an email is auto filled in, then a bunch of code (objects/arrays) is printed at the bottom of the page. When I disable debugbar, everything works as expected.
I'm not sure if this can or should be fixed (might be more of a Debugbar issue?).
I can always load the package in production only.
This is what Debugbar adds to the page... It gets printed out starting at and id <> '1', because the obfuscated email value causes syntax errors in their javascript).
phpdebugbar.addDataSet({
    "__meta": {
        //..
    },
    "queries": {
        "nb_statements": 4,
        "nb_failed_statements": 0,
        "accumulated_duration": 0.00141,
        "accumulated_duration_str": "1.41ms",
        "statements": [{
            // ...
        }, {
            // ...
        }, {
            "sql": "select count(*) as aggregate from `users` where `email` = 'gro.neyemrev@navi' and `id` <> '1'", "params"
:
["gro.neyemrev@navi", "1"
],
// ...

Could you check out the master branch and report back please?
Note that I haven't tested it myself, it is a wild guess.

Nice! As far as I can tell, everything works as expected now :)

New release rolled out (v1.0.3).

Thanks!


css fixes in tier page

From user:

when editing tiers if there are quite a few different amounts you can't see the amounts you are trying to edit:

Similarly, when contributing it looks a bit wrong if there are more than 3 options to choose from (and the higher amounts are seemingly impossible to see/ select :-/ )  I seem to remember these various amounts previously being listed horizontally as opposed to vertically and when that was the case I don't think this was an issue:

For the first issue, what about we limit to 5 different options max?

this is fixed.


Poor performance on Android

Hi there!
First I want to thank you for this awesome plugin. It works fine, and do its job. Thanks!
The only thing bugging me is the perfomance; I'm using it as an accordion, 0.8 version with RN 0.41, and when I tap the accordion header, it takes a little while to close the current active and open the new one. I noticed it's not FPS related.. the FPS does drop down from 60fps to 43fps in my case, but I really don't think it is the cause to feel a little bit sluggish.
I first thought it could be related with the size of the text rendering inside the accordion, but changing the accordion content to a simple text string does not make it fluid; at best just make it a little bit quicker.
Right now I think the blame is on me, because no one else reported it here, but I've no idea what can be causing it.
Any help?
Thanks a lot!

I got the same problem. It takes about half a second until the item starts to expand. The animation is relatively smooth. The only problem is the time it takes to start.
Thanks for help

I too have a similar issue. In my collapsible, it renders some component with a collapsible in itself. The inner component's collapsible works fine. But the outer one is heavy. I learned that when I change the state in the component, I actually re-render everything therefore making it slow. Not sure if that's the same with everyone else.

How did you use it anyway? The  component itself generates n sub-components based on your section length. And yes it does affect the performance.
The only solution I can think about right now is implementing a ListView with a Touchable and Collapsible as row item. But with this way the "accordion" nature is lost.

Hi,
I'm having the same problem but worst: the animation takes time to start (transitionToHeight called late) + the animation FPS is very low, on both iOS and Android (run inside an Expo app, published or in debug mode)
My code is pretty simple (I use Glamorous-native View, but with plain ReactNative views it's not better)

class PendingShootings extends React.PureComponent {
  state = {
    collapsed: false,
  };
  toggle = () => {
    this.setState({collapsed: !this.state.collapsed});
  };

  render() {
    return (
      <View>
        <TouchableWithoutFeedback onPress={this.toggle}>
          <View
            height={80}
            backgroundColor={Colors.tertiary}
            padding={10}
            alignItems="center"
            justifyContent="center"
          >
            <Texts.Normal white>Vous avez un shooting a confirmer</Texts.Normal>
          </View>
        </TouchableWithoutFeedback>
        <Collapsible
          collapsed={this.state.collapsed}
          align="center"
          duration={1000}
        >
          <CollapsedView/>
        </Collapsible>
      </View>
    );
  }
}

class CollapsedView extends React.PureComponent {
  render() {
    return (
      <View
        height={80}
        borderTopColor={Colors.primary}
        borderTopWidth={1}
        backgroundColor={Colors.tertiary}
        padding={10}
        alignItems="center"
        justifyContent="center"
      >
        <Texts.Normal white>Accepter ou refuser?</Texts.Normal>
      </View>
    );
  }
}

Any idea what could be the problem? I've even tried to copy-paste the Collapsible example in my app and also got this problem, so I'll try with the exact same example to see if I'm able to run at least the example fine...

I've opened another issue because I encounter a more general performance problem affecting iOS + Android on latest Expo client: https://github.com/oblador/react-native-collapsible/issues/96

Hello!
I've experienced the same issue, so I run a couple of tests.
I changed a little the config of the Android emmulator and managed to get the appropriate results.
 In dual core config it runs pretty smooth.
Although in either case Perf Monitor doesn't show any issues.
I do not understand why on earth do I need a dual-core config to expand a single section containing a simple sentence =)
Here are the screenshots

The only difference in config is here:

Also, try running your app in release mode. On Android the performance difference between debug and release is usually huge.

Closing this as inactive as there's been no activity for over 30 days. If the problem re-occurs on the latest version of react-native-collapsible then ping me to reopen or create a new issue.

I am also facing same issue. I have also testing in release mode.

how did this issue fix?

how did this issue fix?


Use ServiceGraphBuilder in Misk Hibernate Module

Usages of DependentService have been removed frommisk-hibernate.
The configure blocks have been reorganized in HibernateModule and the testing modules to install services in order of the linear dependency chain they form. This has been done in an attempt to improve readability.

Holding off on merging this PR for now.


Dub won't recognize dub.json

As soon as I execute dub in my directory where my dub.json is located in, dub spits out a weird(ly printed -- immutable(FilenameAndFormat)("dub.json", json) - just emitting "dub.json" isn't enough?) error message:
$ dub
Error executing command run:
no package file was found, expected one of the following: [immutable(FilenameAndFormat)("dub.json", json), immutable(FilenameAndFormat)("package.json", json)]

DUB version 0.9.22+198-g83b2926, built on Feb 17 2015

Could you put the content of your dub.json ?
I get the same error, with the following:
{
    "name": "rest",
    "dependencies": {
        "userman":  { "path": "../" }
    },
    "versions": [ "VibeDefaultMain" ]
}

It turns out my path dependency was wrong (should have been "../../"), but this error message is not informative at all (btw it prints that weird message because it works with an array of FileAndFormat).

I've fixed the error message now. Judging by the (DUB) source code, it's very likely that this was caused by the same issue as in @Geod24's example.

Wow indeed, that was the ../../ part which caused dub to fail. Just tested it.
Still, because this might cause some path overlappings or so, dub should recognize and/or handle this path so it'll take the dub.json located in .

Or..hold on, it actually is interpreting ./dub.json already, it just won't find the dependency's dub.json.. didn't think that way around.

Yes exactly, it was indeed very confusing. It becomes clear now with the new error message, though.

Nice then. Thanks! :)


[bug] spline velocity multiplication perturbs spline

https://github.com/osrf/rmf_core/blob/master/rmf_traffic/src/rmf_traffic/Spline.cpp#L114
This LOC shows a scalar multiplication to velocities of the spline and therefore perturbs the spline when used for collision. The current workaround is to set trajectories to 1s.

Given a trajectory like this, and submitting it into the DetectConflict routine:
rmf_traffic::Trajectory t2;
t2.insert(time, Eigen::Vector3d(-2, 2, 0), Eigen::Vector3d(0, -2, 0));
t2.insert(time + 10s, Eigen::Vector3d(2, 2, 0), Eigen::Vector3d(0, 2, 0));

CHECK(rmf_traffic::DetectConflict::between(profile_circle, t1, profile_circle_with_circle_offset, t2));

This flows into the detect_invasion function where we start construct the spline https://github.com/osrf/rmf_core/blob/master/rmf_traffic/src/rmf_traffic/DetectConflict.cpp#L505.
This then flows into the compute_parameters function https://github.com/osrf/rmf_core/blob/master/rmf_traffic/src/rmf_traffic/Spline.cpp#L97 where delta_t multiples the start and end velocities resulting in (0,-20,0) and (0,20,0).
to_fcl is then called https://github.com/osrf/rmf_core/blob/master/rmf_traffic/src/rmf_traffic/Spline.cpp#L259 and it flows into the compute_knots function https://github.com/osrf/rmf_core/blob/master/rmf_traffic/src/rmf_traffic/Spline.cpp#L222 where we compute v0 and v1, which turn out to be (0,-20,0) and (0,20,0). These are plugged into the conversion to fcl splines, and give me incorrect results when used for collision.
we should divide the v0 and v1 by delta_t in the compute_knots function; but what perplexes me is the need to multiply the velocities of the spline in the first place.

These are plugged into the conversion to fcl splines, and give me incorrect results when used for collision.

You haven't included enough code to demonstrate an incorrect continuous collision detection result.
As for the rest of the matter, the first thing to note is that the API of FCL is specifically designed to operate over a time range of t=[0.0, 1.0]. If we have any time range other than [0.0, 1.0], then we need to transform the spline coefficients into an equivalent spline that has that time range.
The simplest way to justify the transformation is to say "This is how FCL was made, so our hands are tied and we have to do this transformation." But looking at it holistically, we'd want to do this transformation anyway for our own benefit. Taking the position and velocity end conditions and transforming them into cubic spline coefficients is far far easier if you first transform your time coordinate to fit within the range of t=[0.0, 1.0]. I'm sure this is why FCL chose to have this constraint itself.
To understand the reason this multiplication needs to happen, we have to look at some vector calculus, which I'll simplify here.
Let's suppose x(t) is our function of position over time (we'll think of x as a scalar value rather than a vector value for simplicity, but the following math is all the same).
For x(t), the valid range of t is t=[ti, tf] where ti is the initial time of our spline and tf is the final time of our spline.
We need to transform this into a new function ξ(u) where u=[0.0, 1.0].
We want a continuous linear mapping from the values of u to the values of t. We'll call this mapping τ(u) where τ(0) = ti and τ(1) = tf. Since this is a linear mapping, we can easily derive the whole formula: τ(u) = (tf - ti)u + ti
With this mapping we can define ξ(u) := x(τ(u))
To calculate the coefficients of the spline ξ(u), we'll need its endpoint conditions, meaning ξ(0), ξ(1), ξ'(0), and ξ'(1). The positions are trivial:
ξ(0) = x(τ(0)) = x(ti)
ξ(1) = x(τ(1)) = x(tf)
ξ(u) has the same endpoint positions as x(t). However, let's look at its velocities. First let's take the derivative of ξ(u):
ξ'(u) = d[ x(τ(u)) ] / du = d[ τ(u) ]/du * d[ x(τ(u)) ]/dτ = τ'(u) * x'(τ(u))
We can compute τ'(u) from its formula above: τ'(u) = tf - ti
So this means that the velocity endpoint conditions for ξ'(u) are:
ξ'(0) = (tf - ti) * x'(τ(0)) = (tf - ti) * x'(ti)
ξ'(1) = (tf - ti) * x'(τ(1)) = (tf - ti) * x'(tf)
In other words, the velocities at the endpoints of ξ(u) are equal to the velocities at the endpoints of x(t) multiplied by the time range of x(t).
I can't rule out that an implementation error may have happened somewhere in the code, but multiplying by Δt is mathematically sound here. You're going to need to offer more analysis if you really believe there's an error.

I think there's a difference in that the code computes knots for a new, different spline, and it does not map ranges onto the existing spline like what's being described.
The following picture features a green spline with starting velocity (0,0,-2) and ending velocity (0,0,2),

And this picture features a green spline with starting velocity (0,0,-20) and ending velocity (0,0,20)

You can see that there's a huge difference.
Regarding more sample code, give me some time to clean up the test cases.

Alright, here are the test cases.
Case 1: rmf_core
Clone these branches into your workspace:
https://github.com/osrf/rmf_core/tree/robot_multigeom_showcase
https://github.com/ddengster/fcl/tree/0.6.1-fix-conservative-adv
then run
clear && cb --packages-up-to rmf_traffic --cmake-args -DCMAKE_BUILD_TYPE=Release && ./build/rmf_traffic/test_rmf_traffic
You will see a test failure at line 88.
The test case showcases a stationary robot vs a robot going through the DetectConflict function.
Both trajectories are computed at 10 seconds offset, if you change it to 1 second you should get the same results as test case 2.
Case 2: fcl
Clone this branch:
https://github.com/ddengster/fcl/tree/bug_showcase
then build fcl and run the test
mkdir build
cd build
make test_fcl_collision
./test/test_fcl_collision

Check the function test_conversative_advancement_with_offset in the file test/test_fcl_collision.cpp
We have a couple of functions copied in from rmf_traffic - compute_knots and to_fcl. I start with the exact same points and run the collision test.
Now even if the test 2 doesn't comply with the 10 second trajectory case, it should be known that given test case 1's code, and verified by visualizations I should expect a collision.

I can't know for sure, but based on how both splines are being displayed at t=0.5, I very strongly suspect both of these splines have a default time range of t=[0.0, 1.0]. In that case, yes, changing the velocity will change the curvature of the spline.
For your visualizer to be applicable here, you need it to be able to work over an arbitrary time range, and then you need to compare the spline with velocities of +/-20 with a time range of t=[0.0, 1.0] to a spline with velocities of +/-2 with a time range of t=[0.0, 10.0].

The simplest way to justify the transformation is to say "This is how FCL was made, so our hands are tied and we have to do this transformation." But looking at it holistically, we'd want to do this transformation anyway for our own benefit. Taking the position and velocity end conditions and transforming them into cubic spline coefficients is far far easier if you first transform your time coordinate to fit within the range of t=[0.0, 1.0]. I'm sure this is why FCL chose to have this constraint itself.

If this is a remapping, why wouldn't a simple variable range remapping t suffice?
As I see it, the code does this:

User decides on points and velocities for a cubic hermite spline
The code computes points and velocities at start and end times.
the code converts those points to knots
the knots get fed into FCL's SplineMotion, constructing a new b-spline

The main contention is on point 2 and its aftereffects. Multiplying the velocities causes the knots to get adjusted, resulting in incorrect splines. While the math might make sense to you, geometrically it just doesn't make sense.

I recommend you adjust your visualizer to work with arbitrary time ranges, and then we can revisit this concern.

Also keep in mind that the position values of the knots will depend on the time range of the spline. Those knot positions are easiest to calculate for time ranges that are strictly t=[0.0, 1.0], which is why the transformation is used in the first place.

If you want a geometric understanding of it, think about it this way:
Let's say you move from point A to point B while following some arc. You have some kind of velocity at the beginning of the arc and some other velocity at the end, and it takes you 10 seconds to get from point A to point B.
Now you want to follow the same exact arc, but you want to get from point A to point B in 1 second instead of 10 seconds. Every step of the way, you want to follow the same exact arc, you just want to do it in 1/10 of the time scale. For that to be possible, your velocity needs to be 10x as much every step of the way.

Let's say you move from point A to point B while following some arc. You have some kind of velocity at the beginning of the arc and some other velocity at the end, and it takes you 10 seconds to get from point A to point B.

Would you expect the space covered to look different as you adjust the timings of the trajectory? What would the the geometry of the space covered look like? It seem really weird that changing a timing variable would do something like that.
These examples and results illustrate this.
    const rmf_traffic::Time time = std::chrono::steady_clock::now();
    Eigen::Vector3d pos = Eigen::Vector3d(0, 0, 0);
    Eigen::Vector3d vel = Eigen::Vector3d(0, 0, 0);
    rmf_traffic::Trajectory t1;
    t1.insert(time, pos, vel);
    t1.insert(time + 1s, pos, vel);

    rmf_traffic::Trajectory t2;
    t2.insert(time, Eigen::Vector3d(-2, 2, 0), Eigen::Vector3d(0, -2, 0));
    t2.insert(time + 1s, Eigen::Vector3d(2, 2, 0), Eigen::Vector3d(0, 2, 0));

    CHECK(rmf_traffic::DetectConflict::between(profile_circle, t1, profile_circle_with_circle_offset, t2)); //collision

    const rmf_traffic::Time time = std::chrono::steady_clock::now();
    Eigen::Vector3d pos = Eigen::Vector3d(0, 0, 0);
    Eigen::Vector3d vel = Eigen::Vector3d(0, 0, 0);
    rmf_traffic::Trajectory t1;
    t1.insert(time, pos, vel);
    t1.insert(time + 10s, pos, vel);

    rmf_traffic::Trajectory t2;
    t2.insert(time, Eigen::Vector3d(-2, 2, 0), Eigen::Vector3d(0, -2, 0));
    t2.insert(time + 10s, Eigen::Vector3d(2, 2, 0), Eigen::Vector3d(0, 2, 0));

    CHECK(rmf_traffic::DetectConflict::between(profile_circle, t1, profile_circle_with_circle_offset, t2)); //no collision

Would you expect the space covered to look different as you adjust the timings of the trajectory? What would the the geometry of the space covered look like? It seem really weird that changing a timing variable would do something like that.

Yes, if you change the duration of a spline without changing its velocities, you may (and most likely will) change the space that it covers (an obvious exception would be a trivial stationary trajectory).
Try to imagine yourself running from Point A to Point B and then back to Point A. For your first run, you need to spend exactly 10 seconds running from A -> B -> A. For your second run, you need to spend exactly 1 second running from A -> B -> A. Can you imagine any plausible way to do that without running any faster? If you try to run at the same speed both times, then you won't be able to make it all the way to Point B before you have to return to Point A. That's what you're seeing in your tests where you're ending up with different arcs.

Try to imagine yourself running from Point A to Point B and then back to Point A. For your first run, you need to spend exactly 10 seconds running from A -> B -> A. For your second run, you need to spend exactly 1 second running from A -> B -> A. Can you imagine any plausible way to do that without running any faster? If you try to run at the same speed both times, then you won't be able to make it all the way to Point B before you have to return to Point A. That's what you're seeing in your tests where you're ending up with different arcs.

To do the 1 second run, you would have to take the 'shorter path' since you can't adjust your speed. By this logic, if you want to do a hour you'd have to take the quite a detour of the spline motion. Do you not see a problem there?

If you want to cover the same path but spend an hour doing it, then you need to go much slower, which is why we're multiplying the velocities by the time scale.
If you want to spend an hour moving at the same velocities, then yes, the new spline you've created will take a very long detour compared to the spline with the shorter timescale.

If you want to cover the same path but spend an hour doing it, then you need to go much slower, which is why we're multiplying the velocities by the time scale when we transform to the unitary time scale.

If you multiply velocities by the time scale and use it to reconstruct a new spline, the motion is different.

If you want to spend an hour moving at the same velocities, then yes, the new spline you've created will take a very long detour compared to the spline with the shorter timescale.

If I'm writing trajectory code, given how the trajectory api is done I'd expect the motion of a cubic hermite spline without compensating for the duration. Otherwise given the current methods the planner could test for splines completely outside of the area depending on the duration given for the trajectory.
There's also a contradiction in that if geometry being changed, it is not a remapping as mentioned.

It seems like you're missing the detail that the velocities and the time scale need to be transformed simultaneously and in proportion to each other in order to correctly remap the spline from one time scale to another.

It seems like you're missing the detail that the velocities and the time scale need to be transformed simultaneously and in proportion to each other in order to correctly remap the spline from one time scale to another.

I'm concerned about the expected and resultant 'collision geometry' being used. Considering that in the examples that there is one completely stationary robot and one moving robot we can completely discard the notion of velocity and corner ourselves into just looking at the geometry.
Then the debate becomes why we are using the newly made, adjusted splines that could go out of bounds when the intention submitted is the motion of a cubic hermite spline.

Then the debate becomes why we are using the newly made, adjusted splines that could go out of bounds when the intention submitted is the motion of a cubic hermite spline.

The whole point that I'm making is that when we transform the velocities and the time scales proportionally to each other, we get an equivalent (meaning it follows the same arc) spline transformed to the new time scale. If you adjust the time scale but not the velocity, then you get a non-equivalent (meaning it follows a different arc) spline.

The whole point that I'm making is that when we transform the velocities and the time scales proportionally to each other, we get an equivalent (meaning it follows the same arc) spline transformed to the new time scale.

I believe there is a huge flaw in this reasoning. If you happen to have any material that describes this, please share it. The way we're plugging values into FCL tells me that we're assuming a spline in the global space and checking for collisions in that space.

Here's a video to illustrate the reason we need to scale both time and velocity together when transforming the time coordinate to a unary scale:

Note that the trajectories are intentionally offset from each other when displayed so both can always be seen at the same time. Both trajectories have the same exact path through space, but since they operate on different time scales they also need to move at different velocities. If you do not change the velocities proportionally to the change in time scale when you transform the spline, then you will get distortions in the spline's path, like this:
Here are the same two trajectories, except the green trajectory's endpoint velocities are not scaled proportionally to its time scale. Instead it has 1/20th the time scale of the red trajectory but equivalent velocities at its endpoints:

I'll be closing this issue now, since there is not a bug.


Help interpreting output

Hello,
I ran Genomescope 2.0 on two HiFi datasets for two plant genomes. In both cases I get unexpected results and I am unsure of how to interpret them.
Genome 1:
http://genomescope.org/genomescope2.0/analysis.php?code=EUqq9F7CPpVQzDObKuPJ
Genome size is about what I estimated by flow cytometry, but there is a tall error peak. The coverage is lower, though. Are these sequencing errors (shouldn't be that high in HiFi reads, I think)? Could it be due to sample contamination?
Genome 2:
http://genomescope.org/genomescope2.0/analysis.php?code=1q4UixxtZ4acEF5YCQmQ
Genome size is lower than what I estimated by flow cytometry. Also, there are only 20% unique seqs. Since I am not 100% sure of ploidy, I ran the model as if it was polyploid as well:
http://genomescope.org/genomescope2.0/analysis.php?code=MrIaUcE0wQuyNdqlEcGA
Can we infer ploidy from this analysis? Do the four peaks suggest tetraploidy?
Thank you for your help,
Lara

Hi Lara,
On Tue, May 10, 2022 at 3:31 PM Lara Pereira @.***>
wrote:

Hello,
I ran Genomescope 2.0 on two HiFi datasets for two plant genomes. In both
cases I get unexpected results and I am unsure of how to interpret them.
Genome 1:
http://genomescope.org/genomescope2.0/analysis.php?code=EUqq9F7CPpVQzDObKuPJ
Genome size is about what I estimated by flow cytometry, but there is a
tall error peak. The coverage is lower, though. Are these sequencing errors
(shouldn't be that high in HiFi reads, I think)? Could it be due to sample
contamination?

Yes, this looks weird to me. I would guess that first peak (around 10x
coverage) is likely to be contamination of some kind. You could try
assembling with hifiasm and then screening the contigs for those
around this level. Then Id BLAST those contigs to see what they might be

Genome 2:
http://genomescope.org/genomescope2.0/analysis.php?code=1q4UixxtZ4acEF5YCQmQ
Genome size is lower than what I estimated by flow cytometry. Also, there
are only 20% unique seqs. Since I am not 100% sure of ploidy, I ran the
model as if it was polyploid as well:
http://genomescope.org/genomescope2.0/analysis.php?code=MrIaUcE0wQuyNdqlEcGA
Can we infer ploidy from this analysis? Do the four peaks suggest
tetraploidy?

Yes, the 4 peaks strongly suggests tetraploid. The haplotypes are quite
distinct so I would expect hifiasm to do a good job separating out the 4
haplotypes. Then I would try running BUSCO to look for core genes and
expect most core genes will be in multiple copies (even though they are
supposed to be just once).
Good luck!
Mike

Thank you for your help,
Lara
—
Reply to this email directly, view it on GitHub
https://github.com/schatzlab/genomescope/issues/75, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABP343D7X3JALRZ7SNJILLVJK2RNANCNFSM5VSTWAZQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

If I could tag onto this before it is closed, could you also explain the percentages of ploidy at the top of the plot, please?
Am I right to think that the "aaaa" at >90% indicates tetraploidy at a level of >90% of the length of the genome?
And also, is the distinction between "aaaa", "aabb", "aabc", etc, based on the ratios of observed levels of hetrozygosity?
Many thanks,
Mike


Fix VPC model is_default requires

is_default? requires attribute IsDefault to be defined. This is different to requiring ruby code with Kernel#require

Opened PR upstream instead


Error on skyplane init for azure

Repro Instructions
I ran skyplane init. I pressed enter instead of Y/n for the CLI promps. For AWS, this loaded the default AWS credentials, but for Azure, an error trace printed.
 [Y/n]:
    Loaded AWS credentials from the AWS CLI [IAM access key ID: ...XP4ETK]
    AWS region config file saved to /Users/sarahwooders/.skyplane/aws_config

(2) Configuring Azure:
    Do you want to configure Azure support in Skyplane? [Y/n]:
Traceback (most recent call last):
  File "/Users/sarahwooders/repos/skyplane/env/bin/skyplane", line 33, in <module>
    sys.exit(load_entry_point('skyplane', 'console_scripts', 'skyplane')())
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/typer/main.py", line 214, in __call__
    return get_command(self)(*args, **kwargs)
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/Users/sarahwooders/repos/skyplane/env/lib/python3.7/site-packages/typer/main.py", line 500, in wrapper
    return callback(**use_params)  # type: ignore
  File "/Users/sarahwooders/repos/skyplane/skyplane/cli/cli.py", line 516, in init
    cloud_config = load_azure_config(cloud_config, force_init=reinit_azure, non_interactive=non_interactive)
  File "/Users/sarahwooders/repos/skyplane/skyplane/cli/cli_impl/init.py", line 100, in load_azure_config
    or AzureAuthentication.infer_subscription_id(),
  File "/Users/sarahwooders/repos/skyplane/skyplane/compute/azure/azure_auth.py", line 157, in infer_subscription_id
    return subprocess.check_output(["az", "account", "show", "--query", "id"]).decode("utf-8").replace('"', "").strip()
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 411, in check_output
    **kwargs).stdout
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 488, in run
    with Popen(*popenargs, **kwargs) as process:
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 800, in __init__
    restore_signals, start_new_session)
  File "/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/subprocess.py", line 1551, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: 'az': 'az'

@abiswal2001 Please take a look at this

This error looks like you don't have the Azure CLI installed, can you run which az?

Yes, azure init is running cli commands to create credentials so if the cli isn't installed a bug will occur. I can clean this up and print a more clear message to indicate as such @parasj ?

That's a reasonable plan. I think we should set it up to quickly check if the az CLI is installed during init if the user opts for the automated setup.
I pushed a quick PR for this here: https://github.com/skyplane-project/skyplane/pull/567