8.7.1 Using a hash is ignored when not using a hash based routing

I do not use the hash based routing, but it looks like the path gets ignored when creating a match.
Here is an example to illustrate, in my app I navigate to the path:
/appointments?#start=2021-01-01&appointmentId=1
However the match on the uses has the following structure:
{
    data: null,
    params: null,
    queryString: "",
    route: { ... },
    url: "appointments"
}

There is no information in the match at all about the hash url, when before this was available in the query option that used to be available. Is there any way to get the hash information? It would be ideal if we didn't read the url in the browser ourselves because I think it may not be consistently there (especially because we are using a separate router for legacy paths).
Would it make sense to get the hash part included in the match?
Cheers,
Felix

Hm ... this seems a bit weird to me. I mean the string after the # sign could be accessed via location.hash. And this is supported well on all browsers so should be good enough to use it directly. Navigo ignores the string after # on purpose and if we have to change the API and make that part of the Match object it will be probably just:
{
  hash: location.hash
}

So I guess it is the same as you directly using location.hash.
P.S.
by the way Navigo heavily relies on location.hash. So if that's not working in your context (like node, deno, a browser on a mobile device) then I guess this whole library will not work properly.

Hm ... this seems a bit weird to me. I mean the string after the # sign could be accessed via location.hash. And this is supported well on all browsers so should be good enough to use it directly. Navigo ignores the string after # on purpose and if we have to change the API and make that part of the Match object it will be probably just:
{
  hash: location.hash
}

So I guess it is the same as you directly using location.hash.
P.S.
by the way Navigo heavily relies on location.hash. So if that's not working in your context (like node, deno, a browser on a mobile device) then I guess this whole library will not work properly.

Yeah that makes sense actually - I am using two routers but one is to support legacy as we migrate things, but both are still working off the url, so I think this will work fine. I appreciate your response! I will close this issue.

Yeah that makes sense actually - I am using two routers but one is to support legacy as we migrate things, but both are still working off the url, so I think this will work fine. I appreciate your response! I will close this issue.

Actually, I know what the issue is now that I tried to implement this again. I am using the navigate method to change the url. So you get something like this:
navigo.navigate('/appointments?#start=2021-01-01&appointmentId=1')

Navigo calls the hook before changing the url in the browser, so I cannot use location.hash in this case during the hook, because the url has not been set in the browser yet? Maybe I am using this wrong though....
Cheers,
Felix

Actually, I know what the issue is now that I tried to implement this again. I am using the navigate method to change the url. So you get something like this:
navigo.navigate('/appointments?#start=2021-01-01&appointmentId=1')

Navigo calls the hook before changing the url in the browser, so I cannot use location.hash in this case during the hook, because the url has not been set in the browser yet? Maybe I am using this wrong though....
Cheers,
Felix

Just to expand on this a little, I am using the navigo.on({ path: { as: name, uses: func }  }) to setup the routes, so the func here is the hook method that gets called before the url is set.

Just to expand on this a little, I am using the navigo.on({ path: { as: name, uses: func }  }) to setup the routes, so the func here is the hook method that gets called before the url is set.

I see. Interesting case @ajorkowski. I'll take a step back and will ask what's the main goal. It looks (for me) that you need to do some stuff before to get the route resolved that depend on the hash. Is it possible to solve the problem with a bit of composition. For example now you have:
> navigate to appointments?#start=2021-01-01&appointmentId=1
> work A that needs "start=2021-01-01&appointmentId=1"
> route resolving
> work B

What about
> work A that needs "start=2021-01-01&appointmentId=1"
> navigate to appointments
> route resolving
> work B

or
> navigate to appointments
> route resolving
> work A that needs "start=2021-01-01&appointmentId=1"
> work B

I mean by extracting your tasks in separate functions isn't it possible to fulfill your needs with calling those functions in right order.

I see. Interesting case @ajorkowski. I'll take a step back and will ask what's the main goal. It looks (for me) that you need to do some stuff before to get the route resolved that depend on the hash. Is it possible to solve the problem with a bit of composition. For example now you have:
> navigate to appointments?#start=2021-01-01&appointmentId=1
> work A that needs "start=2021-01-01&appointmentId=1"
> route resolving
> work B

What about
> work A that needs "start=2021-01-01&appointmentId=1"
> navigate to appointments
> route resolving
> work B

or
> navigate to appointments
> route resolving
> work A that needs "start=2021-01-01&appointmentId=1"
> work B

I mean by extracting your tasks in separate functions isn't it possible to fulfill your needs with calling those functions in right order.

I guess I could rearrange how the functions work... but if I go by your steps I don't understand how I would say do navigate to appointments without using the navigo library? How could I navigate to appointments?#start=2021-01-01&appointmentId=1 and have that in the url without refreshing the page and without using the navigate method, and making sure the history is all correct etc?
If I have some way of setting the url first then it would work, but isn't the point that I can give navigo a path and it is supposed to resolve this using the rules I have and set the url with history kind of thing? This would take away the utility of it I guess?
P.S. This is just an example route, where possibly this route could be changed to query parameters, but there are some parameters which I wouldn't want to get sent to the server if possible (like temporary access tokens #token=...).

I guess I could rearrange how the functions work... but if I go by your steps I don't understand how I would say do navigate to appointments without using the navigo library? How could I navigate to appointments?#start=2021-01-01&appointmentId=1 and have that in the url without refreshing the page and without using the navigate method, and making sure the history is all correct etc?
If I have some way of setting the url first then it would work, but isn't the point that I can give navigo a path and it is supposed to resolve this using the rules I have and set the url with history kind of thing? This would take away the utility of it I guess?
P.S. This is just an example route, where possibly this route could be changed to query parameters, but there are some parameters which I wouldn't want to get sent to the server if possible (like temporary access tokens #token=...).

As for what I am trying to do - when I go to any page like appointment/:id or appointments?id=:id etc I have a react component and it just needs to know those parameters in the url/query/hash, so that it can change what information it will show. With the hash I could potentially wait until the component itself and use location.hash, but the problem is that I cannot use the navigate method with a url with a hash, because all that will end up in the actual browser will be the url without the hash, so I cannot access location.hash even in the react component.

As for what I am trying to do - when I go to any page like appointment/:id or appointments?id=:id etc I have a react component and it just needs to know those parameters in the url/query/hash, so that it can change what information it will show. With the hash I could potentially wait until the component itself and use location.hash, but the problem is that I cannot use the navigate method with a url with a hash, because all that will end up in the actual browser will be the url without the hash, so I cannot access location.hash even in the react component.

I see. Maybe I wasn't clear with my pseudo snippets above. What I meant was rearranging the bits that need to read from the hash so you let Navigo changes the URL and inside the handler you consume the has via location.hash.
In general this one /appointments?#start=2021-01-01&appointmentId=1 seems weird to me. The hash makes sense to be an id of a DOM element so the browser can scroll to it. What stops you to write /appointments?start=2021-01-01&appointmentId=1 (without a hash) and use match.params?

I see. Maybe I wasn't clear with my pseudo snippets above. What I meant was rearranging the bits that need to read from the hash so you let Navigo changes the URL and inside the handler you consume the has via location.hash.
In general this one /appointments?#start=2021-01-01&appointmentId=1 seems weird to me. The hash makes sense to be an id of a DOM element so the browser can scroll to it. What stops you to write /appointments?start=2021-01-01&appointmentId=1 (without a hash) and use match.params?

But that's what I'm trying to get at - There is no way for Navigo to change the url in the browser with a hash in it? If you try and navigate to a url with a hash it will be removed so you end up with a hash-less url in the browser bar. This means I would have to store what would normally become the hash part internally somewhere instead of it being in the url so I can look it up instead of using location.hash? That might actually work, though the problem is that the history (which is set by navigo) won't have the hash, so it kind of breaks there - pressing back etc on the browser would break.
As for your second point. In this specific case there isn't anything stopping us from changing to use params - it's just a weird legacy thing that we are eventually going to replace... Though that isn't now unfortunately because there are live links out there that are using this format.
Saying that, I think there are times when having a hash is valuable instead of using a query string, and that is the fact that hashes do not get sent to the server. So I have something like /viewbill?#token=... would only make a request for /viewbill to the server, reducing the surface area the token is available.
I think having a library that is supposed to handle urls should probably also handle hashes, because they have a different role than query params in the browser in this way (not just a redundant way to represent params in urls), but that's just me. It's just unfortunate that all of a sudden it's not supported because it's what I need at this point - it's all good we will just have to lock the version - I only started this thread because I just thought maybe it was overlooked as opposed to it being a philosophical difference in the lib!
Thanks for your help working through this though!

But that's what I'm trying to get at - There is no way for Navigo to change the url in the browser with a hash in it? If you try and navigate to a url with a hash it will be removed so you end up with a hash-less url in the browser bar. This means I would have to store what would normally become the hash part internally somewhere instead of it being in the url so I can look it up instead of using location.hash? That might actually work, though the problem is that the history (which is set by navigo) won't have the hash, so it kind of breaks there - pressing back etc on the browser would break.
As for your second point. In this specific case there isn't anything stopping us from changing to use params - it's just a weird legacy thing that we are eventually going to replace... Though that isn't now unfortunately because there are live links out there that are using this format.
Saying that, I think there are times when having a hash is valuable instead of using a query string, and that is the fact that hashes do not get sent to the server. So I have something like /viewbill?#token=... would only make a request for /viewbill to the server, reducing the surface area the token is available.
I think having a library that is supposed to handle urls should probably also handle hashes, because they have a different role than query params in the browser in this way (not just a redundant way to represent params in urls), but that's just me. It's just unfortunate that all of a sudden it's not supported because it's what I need at this point - it's all good we will just have to lock the version - I only started this thread because I just thought maybe it was overlooked as opposed to it being a philosophical difference in the lib!
Thanks for your help working through this though!

@ajorkowski can you please try new 8.8.0 version. I added a hashString field into the Match object.
https://codesandbox.io/s/navigo-example-jrui8
import Navigo from "navigo";

document.getElementById(
  "app"
).innerHTML = `<a href="/user/xxx/save?foo=bar#anchor-here" data-navigo>click me</a>`;

const router = new Navigo("/");

router.on("/user/:id/:action", function (match) {
  document.getElementById("app").innerHTML = `
${JSON.stringify(
    match,
    null,
    2
  )}
`;
});

Clicking the link shows the following:
{
  "url": "user/xxx/save",
  "queryString": "foo=bar",
  "hashString": "anchor-here",
  "route": {
    "name": "user/:id/:action",
    "path": "user/:id/:action",
    "hooks": {}
  },
  "data": {
    "id": "xxx",
    "action": "save"
  },
  "params": {
    "foo": "bar"
  }
}

@ajorkowski can you please try new 8.8.0 version. I added a hashString field into the Match object.
https://codesandbox.io/s/navigo-example-jrui8
import Navigo from "navigo";

document.getElementById(
  "app"
).innerHTML = `<a href="/user/xxx/save?foo=bar#anchor-here" data-navigo>click me</a>`;

const router = new Navigo("/");

router.on("/user/:id/:action", function (match) {
  document.getElementById("app").innerHTML = `
${JSON.stringify(
    match,
    null,
    2
  )}
`;
});

Clicking the link shows the following:
{
  "url": "user/xxx/save",
  "queryString": "foo=bar",
  "hashString": "anchor-here",
  "route": {
    "name": "user/:id/:action",
    "path": "user/:id/:action",
    "hooks": {}
  },
  "data": {
    "id": "xxx",
    "action": "save"
  },
  "params": {
    "foo": "bar"
  }
}

Awesome, this looks like it will work really well. I will try to use the new 8.8 version and let you know how it goes. Probably won't get to it until next week however.

Awesome, this looks like it will work really well. I will try to use the new 8.8 version and let you know how it goes. Probably won't get to it until next week however.

Hey @ajorkowski. Can we close this issue?

@krasimir Yes I can confirm works great, I was able to upgrade navigo with these changes :) I'll close it now.


delete badcat theme

Hi, Christian.
Look at this link.

https://github.com/emanuelrosa/badcat/tree/master/autoload/airline/themes

I think badcat theme should remove this repo.
Could you check this Pull Request?
Related PR
#200

I think this merge is destructive for this repo theme diversity and backward compatibility, you should add some information to prevent people waste time a lot of time to find this issue to fix the problem, maybe check the theme is removed from vim-airline-themes and show hint, or in document highlight how to find the upstream.


[P4_Symbolic] Modified  p4_symbolic/symbolic/expected/conditional_nonlattice.smt2 [Evaluate parsers symbolically.]

Keyword Check:
~/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/tools/keyword_checks.sh .
Keyword check Passed.
Build Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel build $BAZEL_BUILD_OPTS ...
INFO: Analyzed 634 targets (0 packages loaded, 0 targets configured).
INFO: Found 634 targets...
INFO: Elapsed time: 0.812s, Critical Path: 0.00s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
Test Result:
/sonic/src/sonic-p4rt/sonic-pins$ bazel test $BAZEL_BUILD_OPTS --cache_test_results=no ...
INFO: Analyzed 634 targets (0 packages loaded, 0 targets configured).
INFO: Found 423 targets and 211 test targets...
INFO: Elapsed time: 231.016s, Critical Path: 118.50s
INFO: 265 processes: 320 linux-sandbox, 18 local.
INFO: Build completed successfully, 265 total actions
//dvaas:port_id_map_test                                                 PASSED in 0.8s
//dvaas:test_run_validation_golden_test                                  PASSED in 0.8s
//dvaas:test_run_validation_test                                         PASSED in 0.8s
//dvaas:test_run_validation_test_runner                                  PASSED in 0.1s
//dvaas:test_vector_stats_diff_test                                      PASSED in 0.1s
//dvaas:test_vector_stats_test                                           PASSED in 0.0s
//dvaas:test_vector_test                                                 PASSED in 0.6s
//dvaas:user_provided_packet_test_vector_diff_test                       PASSED in 0.1s
//dvaas:user_provided_packet_test_vector_test                            PASSED in 0.1s
//gutil:collections_test                                                 PASSED in 0.5s
//gutil:io_test                                                          PASSED in 0.5s
//gutil:proto_matchers_test                                              PASSED in 0.6s
//p4rt_app/tests:resource_limits_test                                    PASSED in 2.7s
//p4rt_app/tests:response_path_test                                      PASSED in 6.7s
//p4rt_app/tests:role_test                                               PASSED in 1.5s
//p4rt_app/tests:state_verification_test                                 PASSED in 3.5s
//p4rt_app/tests:vrf_table_test                                          PASSED in 2.9s
//p4rt_app/tests/lib:app_db_entry_builder_test                           PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                                 PASSED in 0.1s
//p4rt_app/utils:table_utility_test                                      PASSED in 0.7s
//sai_p4/instantiations/google:clos_stage_test                           PASSED in 0.5s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test PASSED in 0.0s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test        PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_build_test      PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_cc_test         PASSED in 0.7s
//sai_p4/instantiations/google:sai_p4info_fetcher_test                   PASSED in 0.8s
//sai_p4/instantiations/google:sai_p4info_test                           PASSED in 1.2s
//sai_p4/instantiations/google:sai_pd_proto_test                         PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                          PASSED in 0.6s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 1.5s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 1.0s
//sai_p4/instantiations/google/tests:p4_fuzzer_integration_test          PASSED in 3.7s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.6s
//sai_p4/tools:packetio_tools_test                                       PASSED in 0.8s
//tests:thinkit_gnmi_interface_util_tests                                PASSED in 1.0s
//tests/lib:p4info_helper_test                                           PASSED in 0.9s
//tests/lib:p4rt_fixed_table_programming_helper_test                     PASSED in 0.8s
//tests/lib:packet_generator_test                                        PASSED in 26.6s
//tests/lib:switch_test_setup_helpers_golden_test                        PASSED in 0.1s
//tests/lib:switch_test_setup_helpers_golden_test_runner                 PASSED in 0.1s
//tests/qos:gnmi_parsers_test                                            PASSED in 0.1s
//tests/qos:gnmi_parsers_test_runner                                     PASSED in 0.1s
//thinkit:bazel_test_environment_test                                    PASSED in 0.5s
//thinkit:generic_testbed_test                                           PASSED in 1.0s
//thinkit:mock_control_device_test                                       PASSED in 0.5s
//thinkit:mock_generic_testbed_test                                      PASSED in 0.7s
//thinkit:mock_mirror_testbed_test                                       PASSED in 0.6s
//thinkit:mock_ssh_client_test                                           PASSED in 0.0s
//thinkit:mock_switch_test                                               PASSED in 0.7s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 0.7s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 0.9s
Stats over 5 runs: max = 0.9s, min = 0.7s, avg = 0.7s, dev = 0.1s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 44.6s
Stats over 50 runs: max = 44.6s, min = 0.8s, avg = 3.5s, dev = 10.3s
Executed 211 out of 211 tests: 211 tests pass.
INFO: Build completed successfully, 265 total actions

/azp run

Co-authored-by: Srikishen Pondicherry Shanmugam<EMAIL_ADDRESS>

/azp run


How to eanble and use Incubating Falco Rules or Sandbox Falco Rules?

What to document
Hello,  everyone!  I 've read the offical documents about rules. I want to use some rules of incubating &  sandbox rules. I only find how to disable some rules of Stable rules(  https://falco.org/docs/rules/controlling-rules/#disable-default-rules). But I didn't find documents about how to selectively use some rules of incubating &  sandbox rules.  Could you kindly supply these documents url? Thanks a lot!

https://falco.org/docs/reference/rules/default-rules/
By default, only the stable rules are loaded by Falco, you can install the sandbox or incubating rules by referencing them in the Helm chart:

helm install falco falcosecurity/falco \
--set "falcoctl.config.artifact.install.refs={falco-rules:3,falco-incubating-rules:4,falco-sandbox-rules:4}" \
--set "falcoctl.config.artifact.follow.refs={falco-rules:3,falco-incubating-rules:4,falco-sandbox-rules:4}" \
--set "falco.rules_files={/etc/falco/k8s_audit_rules.yaml,/etc/falco/rules.d,/etc/falco/falco_rules.yaml,/etc/falco/falco-incubating_rules.yaml,/etc/falco/falco-sandbox_rules.yaml}"

Where the option falcoctl.config.artifact.install.refs governs which rules are downloaded at startup, falcoctl.config.artifact.follow.refs identifies which rules are automatically updated and falco.rules_files indicates which rules are loaded by the engine.

Or something like this in your helm values file:
falco:
  rules_files:
    - /etc/falco/falco_rules.yaml
    - /etc/falco/falco_rules.local.yaml
    - /etc/falco/falco-incubating_rules.yaml
    - /etc/falco/rules.d

falcoctl:
  config:
    artifact:
      install:
        refs:
          - falco-rules:3
          - falco-incubating-rules:4
      follow:
        refs:
          - falco-rules:3
          - falco-incubating-rules:4

https://falco.org/docs/reference/rules/default-rules/
By default, only the stable rules are loaded by Falco, you can install the sandbox or incubating rules by referencing them in the Helm chart:

helm install falco falcosecurity/falco \
--set "falcoctl.config.artifact.install.refs={falco-rules:3,falco-incubating-rules:4,falco-sandbox-rules:4}" \
--set "falcoctl.config.artifact.follow.refs={falco-rules:3,falco-incubating-rules:4,falco-sandbox-rules:4}" \
--set "falco.rules_files={/etc/falco/k8s_audit_rules.yaml,/etc/falco/rules.d,/etc/falco/falco_rules.yaml,/etc/falco/falco-incubating_rules.yaml,/etc/falco/falco-sandbox_rules.yaml}"

Where the option falcoctl.config.artifact.install.refs governs which rules are downloaded at startup, falcoctl.config.artifact.follow.refs identifies which rules are automatically updated and falco.rules_files indicates which rules are loaded by the engine.

Or something like this in your helm values file:
falco:
  rules_files:
    - /etc/falco/falco_rules.yaml
    - /etc/falco/falco_rules.local.yaml
    - /etc/falco/falco-incubating_rules.yaml
    - /etc/falco/rules.d

falcoctl:
  config:
    artifact:
      install:
        refs:
          - falco-rules:3
          - falco-incubating-rules:4
      follow:
        refs:
          - falco-rules:3
          - falco-incubating-rules:4

Thanks your rely. I'll read these docs and try it.


Describe demo in QuickStart format

An example: https://s3.amazonaws.com/quickstart-reference/mongodb/latest/doc/MongoDB_on_the_AWS_Cloud.pdf
Our reference should have:
About This Guide
Overview
Quick Links
AWS Services
Architecture Overview
Relevant Architectural Constructs
Deployment
What We'll Cover
Step 1. Prepare an AWS Account
Step 2(a). Launch the Quick Start into Your AWS Account
Step 3. Connect to Jenkins and other resources
Testing the reference implementation
Security
Additional Resources
Appendix
Send Us Feedback

This will be the master ticket for all the documentation.  Each major section of the documentation will be broken into it's own ticket and assigned accordingly.


Include code examples

Either in the README, the Wiki or an examples directory. This is an amazing combo of software/hardware but for developers to really "get it" they'll need a little more help to go off of to kickstart their own instances.

Thank you for your request! We've added code examples to the README.
Also, we have demo projects both for Capacitor and Cordova that can really help to kickstart a new project.


Add readthedocs plugin configuration

Codecov Report

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

@@           Coverage Diff           @@
##           master      #35   +/-   ##
=======================================
  Coverage   67.32%   67.32%
=======================================
  Files          41       41
  Lines        1007     1007
  Branches      100      100
=======================================
  Hits          678      678
  Misses        241      241
  Partials       88       88

Flag
Coverage Δ

#unittests
67.32% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Event in codeunit 233

I need in codeunit 233 the event:
if not ConfirmManagement.GetResponseOrDefault(Text000, true) then
exit;

NEW EVENT>>>>>>>>
OnBeforePostJournalBatch(GenJnlBatch);
<<<<<<<<<<<<<<<<<

Find('-');
repeat
[IntegrationEvent(false, false)]
local procedure OnBeforePostJournalBatch(var GenJournalBatch: Record "Gen. Journal Batch")
begin
end;
Thanks!

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


bump version in main branch

as part of 0.9.0 release

doctest seems flaky, have seen this come and go. Should hopefully be resolved when we delete datapipes/torchdata


Update documentation for roles API (versions 0.9 and 0.10)

Roles API input is different for opendistro 0.9 and 0.10. This needs to be updated in the documentation (https://opendistro.github.io/for-elasticsearch-docs/docs/security-access-control/api/#create-role)
Related Issue:
https://github.com/opendistro-for-elasticsearch/security/issues/456

We recently added old documentation version to the docs, which has the old API: https://opendistro.github.io/for-elasticsearch-docs/docs/other/#old-documentation-versions
We won't host every version, just the final minor version for each major version. In this case, we never tagged a 0.10 version of the docs, so 0.9 is the latest. I suspect we're closing in on the final 1.x version.


Boost 1.73

A new version was released in april, any change of an update? https://www.boost.org/users/history/version_1_73_0.html

@sergey-shandar In the meantime also https://www.boost.org/users/history/version_1_74_0.html is available.

And now also https://www.boost.org/users/history/version_1_75_0.html.

We gave up, are now using the conan package manager.

@gummif I'm sorry that I was not able to update the packages for about one year. Honestly, other package managers (like conan or vcpkg) could be better for C++ than nuget.


Add more configuration options for mappings

In particular:

g:coqtail_noimap to disable all insert-mode mappings
g:coqtail_map_prefix to customize <leader>c

This will avoid annoying delays when <leader> is mapped to something common like <SPACE> (https://github.com/whonore/Coqtail/issues/93#issuecomment-656762958).

I don't think Coqtail should add insert-mode mappings to the leader per default. Using space as the leader is very popular, and the typing delay that it causes is quite intrusive. I think the setting should be to enable the insert-mode leader bindings.
I do think insert mode bindings are very useful, but maybe they could exists with less intrusive defaults? What about adding them with CTRL-C as the prefix in insert mode?

I see your point, but I'm hesitant to change the default in case there are people using the current insert-mode mappings. I'll think about it some more and add some set of configuration options soon (enable/disable insert mappings, change the prefix, maybe change the prefix for just insert mappings).


FilamentImageLibraryPlugin not found

Class "OuterWeb\FilamentImageLibrary\Filament\Plugins\FilamentImageLibraryPlugin" not found
I'm lost, I followed the documentation step by step, including the installation and configuration of 'outer-web/image-library', but it keeps reporting errors, I'm not sure if it's just me?

Hmm, I use this package for my personal project too, but I have not (yet) had this issue?
Just making sure:
You have outerweb/filament-image-library installed in your composer.json?
You have use Outerweb\FilamentImageLibrary\Filament\Plugins\FilamentImageLibraryPlugin; in your FilamenServiceProvider file?
Maybe a composer dump-autoload could help you?

Hello,
Hmm, I use this package for my personal project too, but I have not (yet) had this issue?
Just making sure:
You have outerweb/filament-image-library installed in your composer.json?
You have use Outerweb\FilamentImageLibrary\Filament\Plugins\FilamentImageLibraryPlugin; in your FilamenServiceProvider file?
Maybe a composer dump-autoload could help you?
Hoping you can resolve your issue!
Kind regards

thx, I'll try again later on your suggestion.

i have te same issue and the composer dump-autoload didn't resolve it

@faydanube any solution found?

Hello @faydanube and @tsalim13 ,
I found the problem! Well not in code, but in the README.md
It should be Outerweb\FilamentImageLibrary\Filament\Plugins\FilamentImageLibraryPlugin
The readme had OuterWeb\FilamentImageLibrary\Filament\Plugins\FilamentImageLibraryPlugin (Note the wrongly capitalized W in my company name Outerweb.)
Sorry for the confusion! Hope this solves your issue.
You can always re-open this issue if this did not fix it.
Thank you for your patience as I am a solo developer with a main and side job.

Sorry for the confusion! Hope this solves your issue.

thx.


[Oculus Quest] Headset not found V9

So from yestarday until now i can't manage to make ALVR find my quest, i tried a bunch o things that are write here but nothing works for me, or maybe i was doing them wrong, so i need a little help please.

for the quest please try this fork:
https://github.com/JackD83/ALVR

for the quest please try this fork:
https://github.com/JackD83/ALVR

I was trying already but are the same things.


pandoc swallows  tags

HTML5 <audio> tags are apparently filtered out when using the version of pandoc installed on readthedocs.org, while <video> tags are fine, see e.g. http://nbsphinx.readthedocs.io/en/0.2.10/markdown-cells.html#HTML-Elements-(HTML-only).
When using conda to build (using the conda-forge channel BTW), everything is fine.

@mgeier did this comment fixed your issue? https://github.com/spatialaudio/nbsphinx/issues/69#issuecomment-262350287, can I close this one?

@humitos Thanks for following up on this!
The mentioned comment is unrelated and didn't fix it, but in the meantime there seems to have been a long-awaited upgrade of packages on RTD, and with the currently installed version of pandoc it works!
Thanks!


rngd: Start early during boot and encrypted swap entropy fix [WIP]

Motivation for this change
Intended to fix entropy starvation during boot (fixes #71204)
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @abbradar

Interesting, thanks! I'll be able to review this in the upcoming week.
(Sorry for the absence, had a fun traveling accident which greatly prolonged my vacation :D)

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/what-are-your-goals-for-20-03/4773/15

Squashed a commit and rebased onto the current master

I believe this is ready for review/merging

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/97


Site down

Seeing this error for every build page.

We're sorry, but something went wrong.
If you are the application owner check the logs for more information.

http://travis-lite.com/
Now points to 'Heroku | Welcome to your new app'


Website Agent Keep Events timer not working?

I have a Website Agent setup to check every hour and to keep events for 1 hour.  Once the previous payload/event's "Expires in" timer reaches the end, it reverses and just starts increasing in time.  Not sure if this is a bug or not.  I have tried setting the Website Agent mode to both "merge" and "all" and it still does it.

Hi @jonathanl01,
did you modify EVENT_EXPIRATION_CHECK in your .env file? Per default the expiration check just runs every 6 hours. When you set it to something like 15m the events should be purged as expected.

@dsander I did not know this, I'm just running a local instance on Docker to test it out and set the "Keep events" setting for the Website Agent to 1 hour. Thank you.


Full build grunt

Hi,
have some problem with grunt build
using
grunt

have some errors
Warning: Command failed: C:\Windows\system32\cmd.exe /s /c "../flex_sdk_4.6/bin/
mxmlc -strict=false -compiler.debug -warnings=true src/flash/FlashMediaElement.a
s -o local-build/flashmediaelement.swf -define+=CONFIG::cdnBuild,false -define+=
CONFIG::debugBuild,false -library-path+="../flex_sdk_4.6/lib" -include-libraries
+=src/flash/flashmediaelement.swc -include-libraries+=src/flash/flashls.swc -use
-network=true -source-path src/flash -target-player 10.0 -headless-server -stati
c-link-runtime-shared-libraries"
'..' is not recognized as an internal or external command,
operable program or batch file.
 Use --force to continue.

--force

didn't help, but i think it's not good point to use it
thanks

I'm guessing this a l/unix vs. windows command style. I'm not sure what the
windows version shoudl be...
On Mon, Aug 24, 2015 at 3:26 AM, Uladzislau Harbachou <
<EMAIL_ADDRESS>wrote:

Hi,
have some problem with grunt build
using
grunt
have some errors
Warning: Command failed: C:\Windows\system32\cmd.exe /s /c "../flex_sdk_4.6/bin/
mxmlc -strict=false -compiler.debug -warnings=true src/flash/FlashMediaElement.a
s -o local-build/flashmediaelement.swf -define+=CONFIG::cdnBuild,false -define+=
CONFIG::debugBuild,false -library-path+="../flex_sdk_4.6/lib" -include-libraries
+=src/flash/flashmediaelement.swc -include-libraries+=src/flash/flashls.swc -use
-network=true -source-path src/flash -target-player 10.0 -headless-server -stati
c-link-runtime-shared-libraries"
'..' is not recognized as an internal or external command,
operable program or batch file.
Use --force to continue.
--force
didn't help, but i think it's not good point to use it
thanks
—
Reply to this email directly or view it on GitHub
https://github.com/johndyer/mediaelement/issues/1568.

--
John Dyer - http://j.hn/

i'll try to build on ubuntu. If build passed,i'll try to fix on windows.
Thanks

@uharbachou Is this still an issue?

@uharbachou Closing this issue since no answer has been posted in more than 2 weeks. If you'd like to reopen this, let us know. Thanks!


cherry-pick #109 from paper-input

We should bring in the changes from this commit:
https://github.com/Polymer/paper-input/commit/67770602863f0802b862102c2f684ea7f91d5f9c

This might be more complex than I initially thought - that commit depends on other changes that we haven't rolled yet. I'll see if cherry-picking a couple commits could work, but it might be necessary to do a more agressive roll of the elements...

We might need to roll the elements anyways, specifically for core-resizable which was designed to resolve some annoying issues with core-list-dart.

yeah, I think so too.


Error sequence not created when creating an Inbound Endpoint

Description:
When creating an Inbound endpoint, we need to specify the injecting sequence and error sequence. When an inbound is created, the VSCode plugin will create an empty sequence with the given name for injecting sequence. But a sequence with the error sequence identifier is not created.
Plugin version : v1.0.0 (pre-release)

The latest release v1.0.1 has resolved the issue. Please reopen if the problem persists.


Not possible to add new currency

PHP Version
latest
Shopware Version
latest
Expected behaviour
Be able to add a new currency or you add worlds currencies, https://en.wikipedia.org/wiki/List_of_circulating_currencies

But the button is not there

Actual behaviour
No button exist to add new currency. We are in trail mode and testing Shopware 6. We plan to install it on our servers.
The currency we need to add is Nigerian Naira. https://en.wikipedia.org/wiki/Nigerian_naira
How to reproduce
Go to
https://YOURSTORE.shopware.store/admin#/sw/settings/currency/index?limit=25&page=1&sortBy=currency.name&sortDirection=ASC&naturalSorting=true

Can't reproduce this behavior, possibly a role issue I guess. Since the version isn't clear (latest) I would propose to close this issue.

There is a limitation for cloud shops that currently no additional currencies can be added. In the self hosted on prem version no such limitation apply.


Process 'command 'bash'' finished with non-zero exit value 127

I download v27.225 zip, yarn install and In Windows Git Bash Running a command like react-native run-android fails with an error like:
> Task :app:buildStaticWebviewAssets FAILED
32 actionable tasks: 3 executed, 29 up-to-date

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:buildStaticWebviewAssets'.
> Process 'command 'bash'' finished with non-zero exit value 127

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 14s

error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:buildStaticWebviewAssets'.
> Process 'command 'bash'' finished with non-zero exit value 127

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 14s

    at makeError (D:\ASProject\zulip-mobile-27.225\node_modules\execa\index.js:174:9)
    at D:\ASProject\zulip-mobile-27.225\node_modules\execa\index.js:278:16
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async runOnAllDevices (D:\ASProject\zulip-mobile-27.225\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:109:5)
    at async Command.handleAction (D:\ASProject\zulip-mobile-27.225\node_modules\@react-native-community\cli\build\index.js:192:9)
info Run CLI with --verbose flag for more details.

the Git Bash path has already  to be added to to PATH in the System environment，JDK version is 11,i have no idea ,please help me

Have you installed rsync? See our notes for Windows setup:
https://github.com/zulip/zulip-mobile/blob/main/docs/howto/build-run.md#per-platform-notes
That's one issue that's tripped up several people when trying to build the app on Windows, and task :app:buildStaticWebviewAssets is the step it would fail at.
If you're having trouble setting that part up, this thread has the latest advice we know:
https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/Execution.20failed.20for.20task.20'.3Aapp.3AbuildStaticWebviewAssets'.2E/near/1487513
Because this app is now in maintenance mode, though, as we build the new Zulip mobile app in Flutter, I'm afraid we won't be able to spend time helping debug.
(If this were a codebase we still intended to spend much time developing, we'd probably replace the rsync logic with something else — rsync works great, but setting it up has been a recurring pain for people on Windows, and we're not actually using it for that much.)

Have you installed rsync? See our notes for Windows setup: https://github.com/zulip/zulip-mobile/blob/main/docs/howto/build-run.md#per-platform-notes
That's one issue that's tripped up several people when trying to build the app on Windows, and task :app:buildStaticWebviewAssets is the step it would fail at.
If you're having trouble setting that part up, this thread has the latest advice we know: https://chat.zulip.org/#narrow/stream/243-mobile-team/topic/Execution.20failed.20for.20task.20'.3Aapp.3AbuildStaticWebviewAssets'.2E/near/1487513
Because this app is now in maintenance mode, though, as we build the new Zulip mobile app in Flutter, I'm afraid we won't be able to spend time helping debug.
(If this were a codebase we still intended to spend much time developing, we'd probably replace the rsync logic with something else — rsync works great, but setting it up has been a recurring pain for people on Windows, and we're not actually using it for that much.)

thanks，I fixed the problem  after  install rsync !

Great, and thanks for confirming that solved it for you.
I've also just added an entry for this in the troubleshooting section of our instructions (93aeee9c6e376225071ff62705a453fb3de07a19), so hopefully that'll help the next person who runs into this to find the solution more quickly.


Considering using resvg-js instead of svg2png?

Have you considered using resvg-js instead of svg2png? resvg-js is almost the fastest and most compatible SVG library.
In some scenarios,resvg-js is even faster than sharp.
Benchmark
Running "resize width" suite...
  resvg-js(Rust):
    12 ops/s, ±22.66%   | fastest 🚀

  sharp:
    9 ops/s, ±64.52%    | 25% slower

  skr-canvas(Rust):
    7 ops/s, ±3.72%    | 41.67% slower

  svg2img(canvg and node-canvas):
    6 ops/s, ±16.94%    | slowest, 50% slower

See also https://github.com/RazrFalcon/resvg#svg-support

svg2png is a devDependency so I personally don't worry much about it. Also, upstream, we need to remove phantomjs and that PR gets rids of svg2png upstream. Here, I wouldn't mind using a solution that's used upstream and works fine cross platform.
Also, do note that I don't have the bandwidth to maintain everything myself. I just pushed some recent patches here to update some stuff with the hopes that we'll be able to release svg-sprite v2.0.0 upstream.

Great, upstream has been migrated to resvg-js: https://github.com/svg-sprite/svg-sprite/pull/554

Closing this since it's related to upstream.


Wut a problem when i input mui. on javascript Mode.

Issue Type: Bug
when I use mui. in javascript mode than autocomplete make mui. to MutationEvent. its difficult for me to use mui.confim().
plz fix that if that was a problem.
VS Code version: Code 1.29.1 (bc24f98b5f70467bc689abf41cc5550ca637088e, 2018-11-15T19:13:36.375Z)
OS version: Windows_NT x64 10.0.17134

You can try this in Settings
"editor.suggestOnTriggerCharacters": false,

thank you ...

/duplicate of https://stackoverflow.com/questions/48609354/visual-studio-code-autocomplete-when-i-press-key-any-way-to-disable/48609930


Supporting repeated eigenvalues

Current version gives some division by 0 errors if there are repeated diagonal entries. It would be nice to automatically detect this case to print warning/fall back on regular Eigensystem

BTW, "near equal" eigenvalues don't seem to pose a problem for this algorithm, so adding small numerical noise to break ties seems like a workaround


Icons have changed

My website https://www.yelah.co.za/ and all my icons are reference other icons instead of their original icons.
My instagram icon is now the linkedin icon
My twitter icon is now the wikipedia icon
I am using your cdn

Yes, I had this same issue!

please use the version number when using the icons
<EMAIL_ADDRESS>


Update FAQ

Reminder to self
Add an answer to the following questions:

When do I need to top up my validator's balance?
What's the difference between exiting and withdrawing?

Resolved via #175


Add finish.html that relates to #14

Add the finish page which is issue number #14.

@RhodesPeter pls assign me if you want me to merge

Oops I made you a reviewer instead, I've assigned you now.

I have made these alterations @des-des.


variable of "or" in pooling.cl

in some version OpenCL driver or compiler, the word of "or" is a key word of languages. So the compilation of this kernel may fail due to the variable name in pooling.cl. just change it to whatever you like, and the compilation will be smoothily

Fixed in d420ce6a609db458e81d600e7d3f0b9c1454edfb
I fixed some time ago it but forgot to update the pointer to dlprimitives backend. (i.e. submodule)


Dynamic Query Parameter Support for the UAEPass Connector

Is your suggestion related to an experience ? Please describe.
UAEPass support multiple query parameters including a ui_locale parameter [1] which can be used to set the language. The customer has a requirement to change the language of UAEPass depending on the user's choice.
At the moment, it is not possible provide these additional query parameters dynamically in the UAEPass connector.
In OIDC IDP configurations, it is possible to add additional query parameters [2] and pass them from login request.
It is possible to improve the UAEPass connector to support the same.
Describe the improvement
Improve the UAEPass connector to support dynamic query parameters.
[1] - https://docs.uaepass.ae/guides/authentication/web-application/1.-obtaining-the-oauth2-access-code#query-parameters
[2] - https://is.docs.wso2.com/en/latest/references/idp-settings/oidc-settings-for-idp/#additional-query-parameters

According to OIDC IDP configurations [1], it is possible to add additional query parameters dynamically

using login request
using  conditional authentication script

Both needs to be supported by UAEPass authenticator. This can be achieved by extending OpenIDConnectAuthenticator correectly.
[1] https://is.docs.wso2.com/en/latest/references/idp-settings/oidc-settings-for-idp/#additional-query-parameters


Convert to TypeScript

This is loosely related to https://sanity-io-land.slack.com/archives/C9Z7RC3V1/p1601637650136800
I probably should have opened an issue instead, but I got the impression that this would be a welcome change, so I proceed.
If the team has any suggestions/ideas/wishes how things should be done, please leave a comment under! Thanks :slightly_smiling_face:

[x] convert files
[x] fix all TS errors
[ ] get tests working
[ ] create multiple bundles

Some of the tests are failing, and I need some feedback/help to fix those. Also to fix the bundling part, I am not totally sure how it should be set up so multiple bundles are created for different environments.

@rexxars @bjoerge @saasen This is ready for review!


tox deps: install both numpy and scipy

Hi,
I got an issue when put both numpy&scipy to tox.ini for my test:
[tox]
envlist = py27
skipsdist = true
[testenv]
setenv =
PYTHONPATH = .
commands = py.test -s -v ..........
deps = numpy
scipy
pytest
matplotlib
openpyxl
tox will always install scipy first which will go for numpy installation dependence.
Is there any way to force numpy before scipy?
Thanks.

This should work already with a recent scipy version. numpy is added to install_requires and setup_requires if it is not present already. Can you put the full log from tox in a gist and link to it?

No reply, so closing.


Glue Catalog Security token issue

Describe the bug
There is an issue connecting to AWS Glue Catalog when using SAML2 and connecting to AWS.
To Reproduce
Steps to reproduce the behavior:

Configure Athena to use SAML authentication
Run soda analyze ...
3 ...

Context

OS:
Python Version: 3.7
Soda SQL Version:
Warehouse Type:

Notes: https://aws.amazon.com/blogs/security/how-to-implement-a-general-solution-for-federated-apicli-access-using-saml-2-0/


Drop broken and superseded CiliumInternalIP restoration logic

This old logic does work only when the IPAM is configured in clusterpool mode, as in all other cases we attempt the restoration from a plain k8s node resource, which does not contain the CiliumInternalIP information.
Hence, let's drop this obsolete logic, which is now superseded by the one introduced in c67d4eeea73c.
Related: https://github.com/cilium/cilium/issues/29019, https://github.com/cilium/cilium/pull/29460
/cc @tommyp1ckles, @gandro

/test

/test

Removing the review requests for Louis and Tom, as sig-agent has already been covered.


Fixes #333

I fixed the issue with DynamoDB streams and also introduced a check if it is already existing to prevent rescheduling stream events (dynamodb, kinesis) on every update. I made the experience that it takes up to 10 minute until a newly added stream processes the first event. All other events still are removed and re-added on every update.
As you predicted, this was a lot of trial and error, I hope I did not break anything existing. I tested manually against S3, DynamoDB and CloudWatch events.
Also, I am fairly new to Python, so let me know if I did something weird.

Coverage decreased (-0.3%) to 79.805% when pulling 078d1d35d397fbd0b1b6d637d4af28b0ef840c58 on safesoftware:bugfix/dynamdb-streams into 4a59fa9b88848da97a8a30f997bdbcb479b2f7a3 on Miserlou:master.

Coverage decreased (-0.3%) to 79.816% when pulling 078d1d35d397fbd0b1b6d637d4af28b0ef840c58 on safesoftware:bugfix/dynamdb-streams into 4a59fa9b88848da97a8a30f997bdbcb479b2f7a3 on Miserlou:master.

Coverage decreased (-0.3%) to 79.816% when pulling b1308a5b01e303d24b97b35b2cd19473c927ebd8 on safesoftware:bugfix/dynamdb-streams into 4a59fa9b88848da97a8a30f997bdbcb479b2f7a3 on Miserlou:master.

I found one more issue, will push the fix in a bit and re-open the pull request.


[BEAM-551] Fix handling of default values for RVPs

Found a bug here, fixed an added a regression test.
R: @dhalperi

LGTM,


Point to new code hosting link

The project has moved to a new organization on GitHub. This change
modifies all the links and git remotes to point to the new location.

All GitHub links are updated in the documents.
The CircleCI badge is updated to point to the new pipeline setup.
All CI tests have been updated to use the git remote of the new
location.
All documentation for PyPI distribution are updated to point to
the new url.
Informational messages for document generation are updated with
the new url.
Dates on the copyright are updated.

Signed-off-by: Nisha K<EMAIL_ADDRESS>

Looks good. Will merge once CI tests finish.


move gyro-arb-wsteth-weth vault to aura

Pool was added to Aura with additional ARB incentives from Lido:
New Strat: 0xD84f2DDC1C9789109e810e8f24c582c6Fb630368
Prod Vault: 0xA9Fa0C33cE278952309229FbE202A5E6108491B0
API: https://github.com/beefyfinance/beefy-api/pull/1498

Harvest on deposit is modified with onlyOwner instead of onlyManager? Why that change? I see you added the profit locking but we still need to be able to switch the HoD with the keeper

Harvest on deposit is modified with onlyOwner instead of onlyManager? Why that change? I see you added the profit locking but we still need to be able to switch the HoD with the keeper

sorry that was a mistake, got them mixed up; here's the strat with correct modifiers: 0xD84f2DDC1C9789109e810e8f24c582c6Fb630368


Update _nav.scss

fix the the position of logo.svg (not in the middle of the navigation_bar)

It is in the middle of Nav correctly in my cases. Can you show me the case or screenshot that logo is not in the middle?


[tests-only][full-ci]forward-port added test for getting details of a single group

Description
This PR forward port PR https://github.com/owncloud/ocis/pull/5641
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[x] Tests only (no source changes)

Checklist:

[ ] Code changes
[ ] Unit tests added
[x] Acceptance tests added
[ ] Documentation ticket raised:

E2E tests failed: https://drone.owncloud.com/owncloud/ocis/20014/84/1
:boom: To see the trace, please open the link in the console ...

npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20014/tracing/alice-can-share-this-weeks-meal-plan-with-all-parents-alice-2023-3-8-06-11-13.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20014/tracing/alice-can-share-this-weeks-meal-plan-with-all-parents-brian-2023-3-8-06-11-45.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20014/tracing/alice-can-share-this-weeks-meal-plan-with-all-parents-carol-2023-3-8-06-11-49.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20014/tracing/file-alice-2023-3-8-06-17-06.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20014/tracing/user-login-can-be-managed-in-the-admin-settings-admin-2023-3-8-06-13-35.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20014/tracing/user-login-can-be-managed-in-the-admin-settings-admin-2023-3-8-06-13-40.zip
npx playwright show-trace https://cache.owncloud.com/public/owncloud/ocis/20014/tracing/user-login-can-be-managed-in-the-admin-settings-alice-2023-3-8-06-13-39.zip


Limit reached after 2 failed call drops

Hi,
I was testing the verification and found after 2 failed call drops, I am getting the below error:
"2 : Invalid verification status: Phone number limit reached"
If I put the other phone number, then I am getting the below error:
"2 : Invalid verification status: Request id limit reached"
So, ideally, we should get the OTP verification in case of missed call verification failed. And, what is the time limit for retrying verification after the above errors?

Invalid verification status: Phone number limit reached : You get this error when you have exhausted the verification limit allowed on a particular number
Invalid verification status: Request id limit reached : This error comes when you have exhausted the verification limits allowed on a particular device.
If you receive the above errors during testing, the limit gets auto reset after 24 hours.

Invalid verification status: Phone number limit reached : You get this error when you have exhausted the verification limit allowed on a particular number
Invalid verification status: Request id limit reached : This error comes when you have exhausted the verification limits allowed on a particular device.
If you receive the above errors during testing, the limit gets auto reset after 24 hours.

Thanks @singhalyogesh for the answers.
But, in which case or at what point I should expect the OTP verification? Because I tried multiple times but every time it is missed call. As currently, we are developing so we need to test the OTP verification also.

Thanks @singhalyogesh for the answers.
But, in which case or at what point I should expect the OTP verification? Because I tried multiple times but every time it is missed call. As currently, we are developing so we need to test the OTP verification also.

@bajajsahil  You would receive an OTP if you deny the phone permissions needed for drop call flow

@bajajsahil  You would receive an OTP if you deny the phone permissions needed for drop call flow

Thanks @singhalyogesh. It worked.
One last question - is there any way I can delete the verification data from the device so that I don't get the verifiedBefore event?

Thanks @singhalyogesh. It worked.
One last question - is there any way I can delete the verification data from the device so that I don't get the verifiedBefore event?

@bajajsahil You can send us the testing mobile number you are using during development phase. We can whitelist your number at our end to prevent it from going into "verified before" state to help you test out the verification scenarios. Please raise a ticket with your app details and testing number here ( https://developer.truecaller.com/contact ) with the query type as "Technical Integration"

@bajajsahil You can send us the testing mobile number you are using during development phase. We can whitelist your number at our end to prevent it from going into "verified before" state to help you test out the verification scenarios. Please raise a ticket with your app details and testing number here ( https://developer.truecaller.com/contact ) with the query type as "Technical Integration"

Awesome. Thanks @singhalyogesh.

Awesome. Thanks @singhalyogesh.


Status of the project

Hi!
What is the status of this project? Is it still being maintained?
Last commit is from almost 1 year ago, and since then there has been important issues like Node 14 support (#349) or Jest 26 support (#351) with no comment from the maintainers.

looks like this project is dead ☹

How can I help?
El sáb., 5 jun. 2021 5:13 p. m., Jordan Harband @.***>
escribió:

@Kikobeats https://github.com/Kikobeats its very much not dead; i just
haven’t had time yet to get to it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/enzymejs/enzyme-matchers/issues/353#issuecomment-855253824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHOGV4EMB6XKFRV6HMFIULTRI5I7ANCNFSM4Y5IK2SA
.

@ljharb if you give us the right permissions, we can push the project forward!
There are some easy PR that can be merged and keep the project up to date.

agree. we are stuck right now because of the out of dated js dom.
that isn't working with react 17.
also in order for something to work, we needed this package
@wojtekmaj/enzyme-adapter-react-17

@ljharb Hi, Could you update jest-environment-jsdom in jest-environment-enzyme to 27.2.2 version to support the new jest?

@LexaDel no, because i have zero association to jest-environment-enzyme, and this project (as well as enzyme itself) has no relation to jest.

@LexaDel it's on my list of stuff to do.

any updates on this?

@ljharb Thanks for doing this! Can imagine how much work it would be. Do you have a timeline for react 17 and node support?

I do not have a timeline for react 17 support; i don’t know what “node support” it’s lacking.

I do not have a timeline for react 17 support; i don’t know what “node support” it’s lacking.

Sorry, the node support I added by mistake 😅  That's all working as it should.
Thanks for the quick reply (:


score can now be computed for all lambdas

this addresses issue #58

Coverage decreased (-1.3%) to 92.657% when pulling b9b716c3226a3d6ea12dfed41eacb86df690e0aa on score-all-lambdas into e1a373f79a40d756c623979ce745c8fa2b60ecaa on master.

@pavanramkumar you need to rebase


added my name to it

Just as discussed , added my name to the guestbook . Would love to complete the whole git version control lifescycle

Thank you!


Very basis support for doctest <dir>

This is not very sophisticated, but its a place to start.  The content of the directory should be in the path for example.
Thoughts?

I think I prefer #85, but will leave this open for now.


Debug: ListView got bad scroll event

I'm seeing (lots of) these errors in dev console from listView:
listView.ts:1098 Got bad scroll event: Object
gb @ listView.ts:1098

Maximum call stack size exceeded: RangeError: Maximum call stack size exceeded
    at M.c (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1910:3082)
    at M.renderElement (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1910:39416)
    at d.renderElement (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:614:9038)
    at R.renderElement (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:613:34504)
    at ce.renderElement (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:227:2077)
    at g.X (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:15455)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:14596
    at I.transact (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:3161)
    at g.W (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:14472)
    at g.gb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:19479)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:49184)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at E.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:17241)
    at E.setScrollPositionNow (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:16239)
    at n.setScrollPosition (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:54434)
    at g.setScrollTop (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:17124)
    at g.tb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:23777)
    at g.gb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:19545)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:49184)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at E.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:17241)
    at E.setScrollPositionNow (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:16239)
    at n.setScrollPosition (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:54434)
    at g.setScrollTop (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:17124)
    at g.tb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:23777)
    at g.gb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:19545)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:49184)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at E.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:17241)
    at E.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:15983)
    at n.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:50599)
    at g.setScrollTop (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:17062)
    at g.tb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:23777)
    at g.gb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:19545)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:49184)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at E.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:17241)
    at E.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:15983)
    at n.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:50599)
    at g.setScrollTop (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:17062)
    at g.tb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:23777)
    at g.gb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:19545)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:49184)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at E.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:17241)
    at E.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:15983)
    at n.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:50599)
    at g.setScrollTop (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:17062)
    at g.tb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:23777)
    at g.gb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:19545)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:49184)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at E.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:17241)
    at E.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:15983)
    at n.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:50599)
    at g.setScrollTop (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:17062)
    at g.tb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:23777)
    at g.gb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:19545)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:49184)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)
    at E.n (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:17241)
    at E.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:15983)
    at n.setScrollDimensions (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:50599)
    at g.setScrollTop (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:17062)
    at g.tb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:23777)
    at g.gb (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:194:19545)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.z (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1972)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2188)
    at o.value (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:190:49184)
    at d.y (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:1902)
    at d.fire (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:87:2119)

Version: 1.85.0-insider
Commit: ef71b038ad2518e32514b6cc3a4df9f94c096e65
Date: 2023-11-23T05:47:58.884Z
Electron: 25.9.4
ElectronBuildId: 25127168
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.1.0

Deminified:
Maximum call stack size exceeded: RangeError: Maximum call stack size exceeded
at ./workbench/contrib/debug/browser/baseDebugView.ts:192:7
at ./workbench/contrib/debug/browser/replViewer.ts:242:8
at ./base/browser/ui/tree/asyncDataTree.ts:108:16
at ./base/browser/ui/tree/abstractTree.ts:415:16
at ./base/browser/ui/list/listWidget.ts:1225:12
at ./base/browser/ui/list/listView.ts:926:12
at ./base/browser/ui/list/listView.ts:862:10
(./base/browser/ui/list/rowCache.ts:80:3)
at ./base/browser/ui/list/listView.ts:853:13
at ./base/browser/ui/list/listView.ts:1092:8
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1151:8
at ./base/common/event.ts:1175:8
at ./base/browser/ui/scrollbar/scrollableElement.ts:202:18
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1171:8
at ./base/common/scrollable.ts:393:17
at ./base/common/scrollable.ts:303:7
at ./base/browser/ui/scrollbar/scrollableElement.ts:604:20
at ./base/browser/ui/list/listView.ts:1016:25
at ./base/browser/ui/list/listView.ts:1446:10
at ./base/browser/ui/list/listView.ts:1095:9
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1151:8
at ./base/common/event.ts:1175:8
at ./base/browser/ui/scrollbar/scrollableElement.ts:202:18
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1171:8
at ./base/common/scrollable.ts:393:17
at ./base/common/scrollable.ts:303:7
at ./base/browser/ui/scrollbar/scrollableElement.ts:604:20
at ./base/browser/ui/list/listView.ts:1016:25
at ./base/browser/ui/list/listView.ts:1446:10
at ./base/browser/ui/list/listView.ts:1095:9
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1151:8
at ./base/common/event.ts:1175:8
at ./base/browser/ui/scrollbar/scrollableElement.ts:202:18
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1171:8
at ./base/common/scrollable.ts:393:17
at ./base/common/scrollable.ts:268:7
at ./base/browser/ui/scrollbar/scrollableElement.ts:289:19
at ./base/browser/ui/list/listView.ts:1013:26
at ./base/browser/ui/list/listView.ts:1446:10
at ./base/browser/ui/list/listView.ts:1095:9
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1151:8
at ./base/common/event.ts:1175:8
at ./base/browser/ui/scrollbar/scrollableElement.ts:202:18
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1171:8
at ./base/common/scrollable.ts:393:17
at ./base/common/scrollable.ts:268:7
at ./base/browser/ui/scrollbar/scrollableElement.ts:289:19
at ./base/browser/ui/list/listView.ts:1013:26
at ./base/browser/ui/list/listView.ts:1446:10
at ./base/browser/ui/list/listView.ts:1095:9
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1151:8
at ./base/common/event.ts:1175:8
at ./base/browser/ui/scrollbar/scrollableElement.ts:202:18
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1171:8
at ./base/common/scrollable.ts:393:17
at ./base/common/scrollable.ts:268:7
at ./base/browser/ui/scrollbar/scrollableElement.ts:289:19
at ./base/browser/ui/list/listView.ts:1013:26
at ./base/browser/ui/list/listView.ts:1446:10
at ./base/browser/ui/list/listView.ts:1095:9
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1151:8
at ./base/common/event.ts:1175:8
at ./base/browser/ui/scrollbar/scrollableElement.ts:202:18
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1171:8
at ./base/common/scrollable.ts:393:17
at ./base/common/scrollable.ts:268:7
at ./base/browser/ui/scrollbar/scrollableElement.ts:289:19
at ./base/browser/ui/list/listView.ts:1013:26
at ./base/browser/ui/list/listView.ts:1446:10
at ./base/browser/ui/list/listView.ts:1095:9
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1151:8
at ./base/common/event.ts:1175:8
at ./base/browser/ui/scrollbar/scrollableElement.ts:202:18
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1171:8
at ./base/common/scrollable.ts:393:17
at ./base/common/scrollable.ts:268:7
at ./base/browser/ui/scrollbar/scrollableElement.ts:289:19
at ./base/browser/ui/list/listView.ts:1013:26
at ./base/browser/ui/list/listView.ts:1446:10
at ./base/browser/ui/list/listView.ts:1095:9
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1151:8
at ./base/common/event.ts:1175:8
at ./base/browser/ui/scrollbar/scrollableElement.ts:202:18
at ./base/common/event.ts:1140:12
at ./base/common/event.ts:1171:8

Have you made changes here for your debug visualizers @connor4312? Guessing that rendering a repl row causes a list scroll for some reason.

No, I haven't made any code changes for visualizers yet. Only theory.
This also seems to be entirely contained within the listView/scrollableElement, the recursive call doesn't hit debug code...

I'm having trouble reproducing this. @ulugbekna

do you have any user settings pertaining to scrolling?
are there any actions you take that trigger this?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


Could this support two spaces for list indentation?

Example:

Test 1.

Blah.
Blah.

Test 2.

1. Test 1.
  - Blah.
  - Blah.
2. Test 2.

Because GitHub support two spaces indentation list.
Could markdown-it also support two spaces for list indentation?
Or how can I customize the indentation rules?
Thank you very much!

Could markdown-it also support two spaces for list indentation?

http://spec.commonmark.org/0.24/#list-items. Your question should be asked at commonmark forum. This project implements CM spec without deviations.

Or how can I customize the indentation rules?

You can rewrite "list" component of this parser, it's possible to override it with external implementation.

Thanks for such a quick response!
Sure, http://talk.commonmark.org/t/could-also-support-two-spaces-for-list-indentation/2022
I've checked the "list" component of the parser.
I must say it's kinda hard to overwrite a block-level rule because there is too much need to know.
I will try, still not sure where exactly the list indentation size variable is.

OK, I get it now.
CommonMark have strong and reasonable reason why they chose 4-spaces rule instead of others.
http://spec.commonmark.org/0.24/#motivation


Add Azure.Storage meta-package

@tg-msft @AlexGhiondea
Fixes https://github.com/Azure/azure-sdk-for-net/issues/8728

We have decided to not ship this at this point so I'm closing the PR.


feat: GetMapsIdsByName

Currently, the library allows you to get a map from an eBPF program loaded by themselves. If a map is already created, you cannot get it. This function aims to get a list of maps Ids by name already created.

Closing this in favour of #378. @aymericDD I would appreciate your review. Thanks.


System CUDA and Pytorch CUDA problem

Hi nerfstudio guys, thanks for your excellent library!
I have a minor question, it is usually required that we have a consistent system CUDA toolkit version and Pytorch runtime CUDA version to compile cuda extensions.
For example, in diff-gaussian-rasterization compilation, using CUDA 12.1 + Pytorch (cuda 11.8)  will raise the following error:
File "/yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/utils/cpp_extension.py", line 387, in _check_cuda_version
    raise RuntimeError(CUDA_MISMATCH_MESSAGE.format(cuda_str_version, torch.version.cuda))
RuntimeError:
The detected CUDA version (12.1) mismatches the version that was used to compile
PyTorch (11.8). Please make sure to use the same CUDA versions.

This can also happen when build gsplat from source via
pip install git+https://github.com/nerfstudio-project/gsplat.git

But I find CUDA 12.1 + Pytorch (cuda 11.8) works when using pip install gsplat and build the CUDA code on the first run (JIT). In the ~/.cache/torch_extensions/py310_cu118/gsplat_cuda/build.ninja, it still uses the system nvcc. How can JIT succeed in bypass the misalignment in System CUDA and Pytorch CUDA version?

build.ninja
ninja_required_version = 1.3
cxx = c++
nvcc = /usr/local/cuda/bin/nvcc

cflags = -DTORCH_EXTENSION_NAME=gsplat_cuda -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -I/yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/gsplat/cuda/csrc -isystem /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/include -isystem /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/include/torch/csrc/api/include -isystem /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/include/TH -isystem /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /yiflu/miniconda3/envs/gs_env_tmp/include/python3.10 -D_GLIBCXX_USE_CXX11_ABI=0 -fPIC -std=c++17 -O3
post_cflags =
cuda_cflags = -DTORCH_EXTENSION_NAME=gsplat_cuda -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -I/yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/gsplat/cuda/csrc -isystem /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/include -isystem /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/include/torch/csrc/api/include -isystem /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/include/TH -isystem /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/include/THC -isystem /usr/local/cuda/include -isystem /yiflu/miniconda3/envs/gs_env_tmp/include/python3.10 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 --compiler-options '-fPIC' -O3 --use_fast_math -std=c++17
cuda_post_cflags =
cuda_dlink_post_cflags =
ldflags = -shared -L/yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/torch/lib -lc10 -lc10_cuda -ltorch_cpu -ltorch_cuda -ltorch -ltorch_python -L/usr/local/cuda/lib64 -lcudart

rule compile
  command = $cxx -MMD -MF $out.d $cflags -c $in -o $out $post_cflags
  depfile = $out.d
  deps = gcc

rule cuda_compile
  depfile = $out.d
  deps = gcc
  command = $nvcc  $cuda_cflags -c $in -o $out $cuda_post_cflags

rule link
  command = $cxx $in $ldflags -o $out

build rasterization.cuda.o: cuda_compile /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/gsplat/cuda/csrc/rasterization.cu
build projection.cuda.o: cuda_compile /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/gsplat/cuda/csrc/projection.cu
build sh.cuda.o: cuda_compile /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/gsplat/cuda/csrc/sh.cu
build ext.o: compile /yiflu/miniconda3/envs/gs_env_tmp/lib/python3.10/site-packages/gsplat/cuda/csrc/ext.cpp

build gsplat_cuda.so: link rasterization.cuda.o projection.cuda.o sh.cuda.o ext.o

default gsplat_cuda.so

Great question -- I never thought it would work with misaligned CUDA + Pytorch versions lol. I always just make them aligned. Would love to learn it as well if anyone knows why

Yes, I always use same version. CUDA 11.8 and Torch 2.0.1+cu118. It was success to build gsplat==1.0.0 from latest github source in my experiment. But I also curious why it works when it was different.


Release date for <IP_ADDRESS>

Release date for <IP_ADDRESS> should be 11/11/2019 instead of 8/11/2019

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

ID: 57f5478b-3132-21d0-a420-a1140db235de
Version Independent ID: 266bbd16-2117-f680-6493-e183eb09fdbc
Content: Azure AD Connect: Version release history
Content Source: articles/active-directory/hybrid/reference-connect-version-history.md
Service: active-directory
Sub-service: hybrid
GitHub Login: @billmath
Microsoft Alias: billmath

actually looks like should be 11/8/2019 based on https://www.microsoft.com/en-us/download/details.aspx?id=47594 - guessing someone did day/month/year instead of month/day/year

@Jeremy919 Thank you for pointing  out the typo . We have initiated a pull request and this will be changed.

@J-Fedor You are absolutely correct. I have corrected the same and this shall be visible in the next release cycle in 24-48 hours. We will now close this issue.
Thank you.


Page: 7604 "Base Calendar Entries Subform", Event: OnUpdateBaseCalendarChanges

Hi,
Can the following event please be modified.
Page: 7604 "Base Calendar Entries Subform"
Event: OnUpdateBaseCalendarChanges
Change to:
[IntegrationEvent(false, false)]
local procedure OnUpdateBaseCalendarChanges(var BaseCalendarChange: Record "Base Calendar Change";CustCalendarChange: Record "Customized Calendar Change")
We wish to modify the current record of the page.
Kind Regards Nic

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


[SP-5334] Backport of PDI-18396 - Job 'ZIP File' step generates wrong file path if period/dot in parent folder name (8.3 Suite)

Attention: This is the outcome of an automated process!
Merge Masters: @pentaho-lmartins and @smmribeiro
Cherry-picks:

https://github.com/Pentaho/pentaho-kettle/commit/8422c706cf37856c6cfa62d235703f6056dbdb12

:white_check_mark: Build finished in 18m 54s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3532, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message

:white_check_mark: Build finished in 25m 40s
Build command:
mvn clean verify -B -e -Daudit -amd -pl engine

:ok_hand: All tests passed!
Tests run: 3535, Failures: 0, Skipped: 7    Test Results

:information_source:  This is an automatic message


As an expert user, I am able to investigate when a data file load failed

... so that I don't lose my whole database due to a small mistake I made.

Perhaps an extension: Consider making a backup of the corrupted data. This could be useful for advanced users accidentally making an incorrect change, which results in the whole save file to be overwritten.


Factored request part out of the definition endpoint

Overview
This addresses #375 by creating a separate endpoint for it.
Description
This follows the same pattern as definitions/submissions in the presentation package.
How Has This Been Tested?
Unit tests.

Codecov Report

Merging #443 (b44257f) into main (7047be5) will decrease coverage by 0.06%.
The diff coverage is 8.82%.

:exclamation: Current head b44257f differs from pull request most recent head 8f5dcbf. Consider uploading reports for the commit 8f5dcbf to get more accurate results

@@            Coverage Diff             @@
##             main     #443      +/-   ##
==========================================
- Coverage   21.39%   21.33%   -0.06%
==========================================
  Files          48       49       +1
  Lines        5366     5437      +71
==========================================
+ Hits         1148     1160      +12
- Misses       4034     4093      +59
  Partials      184      184

Impacted Files
Coverage Δ

pkg/server/router/presentation.go
2.96% <0.00%> (-0.78%)
:arrow_down:

pkg/server/server.go
81.99% <100.00%> (+0.61%)
:arrow_up:

... and 3 files with indirect coverage changes


Issue 255

If int = 0 then it's not recognized as a value and not pass the required validator
https://github.com/wtforms/wtforms/issues/255#issuecomment-559493117

Could you provide a more detailed title for the pull request?
Additionally, your changes cause some existing test cases to fail.

Also, can you add some unit tests please?

I don't understand the implications of this change, given the existing documented behavior of the two required validators. Recommend closing this if we don't receive the requested fixes or a response in a couple days.

The implication is to allow 0 as an acceptable value for IntegerField and FloatField.
It is related to this issue : https://github.com/wtforms/wtforms/issues/255
I will try to find a better solution in the next days without the tests failing.

That's just a restatement of the original comment on this PR. I'm talking about the implications of changing the behavior of this validator from "is not False" to "is not None". Remember, this is used for more than integers. The difference between DataRequired and InputRequired are already documented, and discussed at length in the linked issue.


Implement and Test WebSocket.Order

as a developer, I want to be able to sign on order live updates
TODO:

New subscription in BitmetSocketSubscriptions
Test that shows that subscription works
Use models from REST API, if web scoket model is different - create a new one under Models/Socket

Do you still need help ? As I see there is already order subscription on socket.

@MaDeRkAn looks like it was done, closing...


Try make check on OS X

Closes #1
Ping @aleksandervines this may work...

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Failed :/ Though this was much more promising! instead of 37/40 failed tests, it failed on 4/224

Most of the other failures was b/c conda could not find those libs at test-time. So that is fixed. The remaining errors now are "real" errors that we need to address though.

I don't know the first thing about theses tests, so it may be worth reporting them upstream to get some advice.
177: trans test_array_5.xml scale(a,0.001)  test_array_5.xml.1.func_base FAILED (DMRTest.at:483)
178: trans test_array_5.xml scale(b,0.001)  test_array_5.xml.2.func_base FAILED (DMRTest.at:484)
179: trans test_array_5.xml scale(c,0.001)  test_array_5.xml.3.func_base FAILED (DMRTest.at:486)
180: trans test_array_5.xml scale(d,0.001)  test_array_5.xml.4.func_base FAILED (DMRTest.at:487)

Yes. It failed exactly the same on my mac now, so I got some log files to work with, though I can't get anything useful out of those I think. I will report the issue upstream.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


Fix for [#43] document not found.

An addition for #48: createCanvas is not enough, need to pass createImage to work with embedded images.

Thanks!


More shared source updates

These are more changes that need to be in main before I can proceed with the AutoRest updates in https://github.com/Azure/autorest.csharp/pull/3281

API change check
API changes are not detected in this pull request.


Create docker image

Create docker container which has

egeria base image (set to same level as dependencies)
this connector

Add support to actions:

merge
release

Following the same approach as used for HMS, Strimzi, and event schema repositories.
The intent is to make it easier to deploy a specific container for a dedicated egeria platform and server.
This request was brought up in the cloud native workgroup for those other repositories as offering value short term.
It's still possible to use the jar directly, and there is still a request for an uber-container with all connectors.
@cmgrote ok with you if I add this?
Now, in support, I note most of our repos are gradle based. I suggest making a switch to gradle build as a prereq for this. (I can propose a PR if you're ok with it in principle?)

Definitely fine with both, and also very appreciative of any PR's you want to send through with the changes 🙏


(cloud-merge) Support BE smooth upgrade

Proposed changes
Issue Number: close #xxx

run buildall

run buildall

run buildall