[Android4.1-4.3][v0.39]WebView source={{html}} show all html string without parse html if 'baseUrl' is set

Description
use source={{baseUrl: 'xx', html:
Hi
}}
Android4.3 looks like treat webview as , will output all html string in View,
use html=xxx or source={{html:xxx}} works
Reproduction
very simple code will reproduce:
export default class RootComponent extends Component {
  render() {
    // return this.render2();
    return this.render1();
  }
  // warn, but works!! except can not alert
  render2 () {
    return (
      <WebView
        // html="
H1
" // or the following works
        source={{html: "
H1
"}}
      />
    )
  }
  // will show all html string in View like <Text> label
  render1 () {
    return (
      <WebView
        source={{
          baseUrl: 'http://test.com',
          html="
H1
"
        }}
      />
    )
  }
}

Solution
Additional Information

React Native version: [v0.39]
Platform: [Android4.1-4.3, not test Android4.4]
Operating System: [MacOS]

And, Android4.3 webview can not use: window.alert('something')

I can confirm this happens on RN 0.39 on my Galaxy S3 with Android 4.3.

same issue

Same thing happened in the NativeScript project, looks like the solution is quite simple
https://github.com/NativeScript/NativeScript/issues/1038

Closing this issue because it has been inactive for a while. If you think it should still be opened let us know why.

@hramos could you reopen it, cause it is still not fixed?


Document how to pre-configure account preferences for new users

There's been a number of asks to pre-configure account settings for new users (e.g. ability to view First Name, Last Name, theme color, time format settings, etc.).
I think this can be done via APIs, and potentially we could add it to the bulk load system in Enterprise Edition later.
We should have some guidance on what's available today.

This is an interesting suggestion. @dontoisme, I'm passing it on to you for reference/consideration.


fix(connector): redirection status is requires_payment_method for failed payments created through stripe

Bug Description
The payment status of a failed redirection payment using stripe says requires_payment_method instead of failed.
Expected Behavior
The status should be failed, with appropriate error message if possible
Actual Behavior
The status is requires_payment_method
Steps To Reproduce
Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.

Create a payment through stripe which requires a redirection flow
Fail the payment when prompted during redirection
The status should be visible in the url.

Context For The Bug
Attaching the redirect url for reference which has this bug
http://google.com/success?status=requires_payment_method&payment_intent_client_secret=pay_QU75MkmagL59TuG2dAdn&amount=6545
Environment
Are you using hyperswitch hosted version? No
If yes, please provide the value of the x-request-id response header for helping us debug your issue.
If not (or if building/running locally), please provide the following details:

Operating System or Linux distribution: Mac
Rust version (output of rustc --version): 1.66.0
App version (output of cargo r -- --version): 0.2.0-48af156-2023-01-11T10:11:56Z

Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

Have you read the Contributing Guidelines?

[X] I have read the Contributing Guidelines

Are you willing to submit a PR?
Yes I am willing to submit a PR!

This shouldn't be failed status. Stripe sends the status as requires_payment_method with last_payment_error. So  we should cascade their behavior and keep the status as requires_payment_method with error_message same as last_payment_error.

@Abhicodes-crypto are we handling this in retries? Can you comment on the status that hyperswitch should have in this case?

Having the payment status flagged as "requires_payment_method" is important because it allows the SDK or merchant client app to make additional attempts at confirming the payment.
On the other hand, if the status is categorized as "failed," this would indicate that the payment has definitively failed and cannot be retried without obtaining a new client secret. Such an approach would result in a poor user experience for the customer.

Since this is the expected behaviour, I will close this issue.


with ingress fails to install chart due to invalid spec

minikube@earth ~> cat values.yml
ingress:
  enabled: true
  host: "test"

minikube@earth ~> helm upgrade -f values.yml my-backstage backstage/backstage
W1209 12:51:58.794453   34716 warnings.go:70] unknown field "spec:rules"
Error: UPGRADE FAILED: failed to create resource: Ingress.extensions "my-backstage" is invalid: spec: Invalid value: []networking.IngressRule(nil): either `defaultBackend` or `rules` must be specified

just trying to test a local deployment and coming across ingress configuration issue. not quite sure how to resolve it. any guidance?

Its caused by the {{- end -}} on ingress line 28, patch inbound.


Add more language copy

This is the new PR from this original PR https://github.com/thedevdojo/auth/pull/36
@m0ham4d, here is the new PR that we'll try to merge into main.

@tnylea Im ready to make more updates on this repo
let me know if everything was ok

BTW, I added a quick fix to a few places. Looks like one of the configs had this in it:
'dont_have_an_account?' => 'Don\'t have an account?',

With a ? in the key, so it wasn't working correctly. Got that updated 😉 so pull the latest on your end when you want to make additional updates 😊

Yes, i will continue adding additional change to my PR 🙂↔

Perfect! If you need my help with any merge conflicts, let me know. I've released a small update since the last version 😉


Snapshots not being updated

Refer to #396 and https://github.com/helium/blockchain-http/issues/396#issuecomment-1103936930
When trying to access the latest snapshot using url https://snapshots.helium.wtf/mainnet/hotspots/network/2023-06-05.json.gz, I get an access denied error. All snapshots up to 2023-06-02 work, but from 2023-06-03 they do not.

The old Helium L1 was halted on April 16, 2023.. All account state was moved to the Solana blockchain.

What would be the new alternative to these snapshots?


Suggestions have no color

Issue Type: Bug
Does this issue occur when all extensions are disabled? Yes
The pop-up showing e.g. the type of a property or the signature of a method for suggestions has no color. I'm not entirely sure
if this was actually ever the case but I'm certain this shouldn't be like this.
Function signatures especially can get really blown up by TypeScript and having the entire signature be one single color and line makes it hard to differentiate between the individual parameters and return types.
Take the following screenshot for example, even the automatic import notice is the same color and directly inline with the actual information:

So in case this isn't a bug, please consider this a feature request to enhance the information pop-up by:

applying the normal theme to the code to allow for better scanning of signatures and type information
seperating additional text like auto-import notices from the actual content
consider using more of the available space to allow the information to wrap at more suitable spots (see the image above where it wraps inside words like "Co|mponent", "Option|s" or "an|y")

The last could maybe also enable the signature to extend to it's full length, because afaik there is currently no way to prevent it from hiding stuff as "... x more ..." or just plain "...". Furthermore, the last point also applies to the hover pop-up, which manages to show color and has some visual seperation and does wrap (although it leaves quite some margin on the right) but still leaves out details at some point:

VS Code version: Code 1.58.2 (c3126316369cd610563c75b1b1725e0679adfb3, 2021-07-14T22:10:15.214Z)
OS version: Windows_NT x64 10.0.19041
Restricted Mode: No

System Info

Item
Value

CPUs
AMD Ryzen 5 1600 Six-Core Processor             (12 x 3194)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.93GB (5.94GB free)

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt639:30300192
pythontb:30283811
vspre833:30321513
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscus158:30321503
pythonvsuse255:30335481
vscod805:30301674
pythonvspyt200:30331937
vscextlangct:30333562
binariesv615:30325510
bridge0708:30335490

This is a duplicate. Unfortunately, I don't recall the exact issue number nor its title :flushed: Anyways, searching for issues with the same labels will likely help you :point_right:
https://github.com/microsoft/vscode/issues?utf8=✓&q=is%3Aopen+label%3A"feature-request"+label%3A"new release"+label%3A"suggest"

@jrieken are you sure? Because none of the 23 open issues with matching feature-request and suggest labels has any resemblance with the problem described here.


fix typo on MyInputProps example on README

just a simple typo fix on the README example
PS: I'm not sure what's the diff on the last line, probably a newline at the end; sorry, doing this edit through GitHub website itself

Thanks!


Disable click event when dragging embla carousel

it's ok no problems i found solution by using pointerDown pointerUp
embla.on('pointerDown', (eventName) => {     console.log('function happen');   });
embla.on('pointerDown', (eventName) => {     console.log('function happen');   });
here is code for all who search for it too.
import { setupPrevNextBtns, disablePrevNextBtns } from "./prevAndNextButtons";
import { setupDotBtns, generateDotBtns, selectDotBtn } from "./dotButtons";

let time = 200;

let t = setTimeout(test, time);

function test() {
  console.log('embla timeout started');
}

function disablePointerEvents() {
  let elemArr = document.querySelectorAll('.drop-link');
    for(let i = 0; i < elemArr.length; i++) {
      elemArr[i].classList.add('disabled');
    }
}
function enablePointerEvents() {
  let elemArr = document.querySelectorAll('.drop-link');
    for(let i = 0; i < elemArr.length; i++) {
      elemArr[i].classList.remove('disabled');
    }
}

const setupEmblaCarousel = (emblaNode, options) => {
  const viewPort = emblaNode.querySelector(".embla__viewport");
  const prevBtn = emblaNode.querySelector(".embla__button--prev");
  const nextBtn = emblaNode.querySelector(".embla__button--next");
  const dots = emblaNode.querySelector(".embla__dots");
  const embla = EmblaCarousel(viewPort, options);
  const dotsArray = generateDotBtns(dots, embla);
  const setSelectedDotBtn = selectDotBtn(dotsArray, embla);
  const disablePrevAndNextBtns = disablePrevNextBtns(prevBtn, nextBtn, embla);

  setupPrevNextBtns(prevBtn, nextBtn, embla);
  setupDotBtns(dotsArray, embla);

  embla.on("select", setSelectedDotBtn);
  embla.on("select", disablePrevAndNextBtns);
  embla.on("init", setSelectedDotBtn);
  embla.on("init", disablePrevAndNextBtns);

  embla.on('pointerDown', (eventName) => {

    clearTimeout(t);
    t = setTimeout(disablePointerEvents, time);

  });

  embla.on('pointerUp', (eventName) => {

    clearTimeout(t);
    t = setTimeout(enablePointerEvents, time);

  });

};

const options = { loop: false };
const emblaNodes = [].slice.call(document.querySelectorAll(".embla"));
const emblaCarousels = emblaNodes.map(emblaNode =>
  setupEmblaCarousel(emblaNode, options)
);

sorry about that!
if you know better way to do it please tell me!
best reggards from Vlad!

Hello @vladtabachuk,
Thank you for your question. Maybe this is a simpler approach:
import { setupPrevNextBtns, disablePrevNextBtns } from "./prevAndNextButtons";
import { setupDotBtns, generateDotBtns, selectDotBtn } from "./dotButtons";

const setupEmblaCarousel = (emblaNode, options) => {
  const viewPort = emblaNode.querySelector(".embla__viewport");
  const prevBtn = emblaNode.querySelector(".embla__button--prev");
  const nextBtn = emblaNode.querySelector(".embla__button--next");
  const dots = emblaNode.querySelector(".embla__dots");
  const embla = EmblaCarousel(viewPort, options);
  const dotsArray = generateDotBtns(dots, embla);
  const setSelectedDotBtn = selectDotBtn(dotsArray, embla);
  const disablePrevAndNextBtns = disablePrevNextBtns(prevBtn, nextBtn, embla);

  // Store drop links in an array
  const dropLinks =  [].slice.call(emblaNode.querySelectorAll('.drop-link'));

  setupPrevNextBtns(prevBtn, nextBtn, embla);
  setupDotBtns(dotsArray, embla);

  embla.on("select", setSelectedDotBtn);
  embla.on("select", disablePrevAndNextBtns);
  embla.on("init", setSelectedDotBtn);
  embla.on("init", disablePrevAndNextBtns);

  // Prevent default on click if embla doesn't allow click
  dropLinks.forEach(dropLink => {
    dropLink.addEventListener('click', (event) => {
      if (!embla.clickAllowed) event.preventDefault();
    });
  });
};

const options = { loop: false };
const emblaNodes = [].slice.call(document.querySelectorAll(".embla"));
const emblaCarousels = emblaNodes.map(emblaNode =>
  setupEmblaCarousel(emblaNode, options)
);

Give it a try and let me know if it helps.
Best,
David

Thank you so much mister!

it does not work for me, may be i use wrong api version? can you please tell me where can i get embla-carousel.umd.js of latest version?

Try including this, it should give you the latest version:
<script<EMAIL_ADDRESS>

Cool! i'll try

Still not working

how can i implement pointer event none for a.droplink while carousel is moving?

i can try something like this to do
if carousel move and i click on link it should add classname to a.drop-link  =>  dropLink.classList.add('disabled'); and after 100 ms for example  dropLink.classList.remove('disabled'); what do you think?

cant realy do it because pointer-events: none; disables all events and it happen after i click;

Hi @vladtabachuk,
embla.clickAllowed() has been stable for a long time now. Please create a CodeSandbox with your setup that demonstrates the issue. It’s hard for me to guess what could be wrong when I don’t have the whole picture. That will enable me to debug your code instead of guessing what could be wrong 🙂.
Kindly
David

Sir, i got positive resoults, this code doing better job!
import { setupPrevNextBtns, disablePrevNextBtns } from "./prevAndNextButtons";
import { setupDotBtns, generateDotBtns, selectDotBtn } from "./dotButtons";

let time = 100;

let t = setTimeout( ()=>{}, time)

const setupEmblaCarousel = (emblaNode, options) => {
  const viewPort = emblaNode.querySelector(".embla__viewport");
  const prevBtn = emblaNode.querySelector(".embla__button--prev");
  const nextBtn = emblaNode.querySelector(".embla__button--next");
  const dots = emblaNode.querySelector(".embla__dots");
  const embla = EmblaCarousel(viewPort, options);
  const dotsArray = generateDotBtns(dots, embla);
  const setSelectedDotBtn = selectDotBtn(dotsArray, embla);
  const disablePrevAndNextBtns = disablePrevNextBtns(prevBtn, nextBtn, embla);

  // Store drop links in an array
  const dropLinks =  [].slice.call(emblaNode.querySelectorAll('.drop-link'));
  const emblaSlidesInner =  [].slice.call(emblaNode.querySelectorAll('.embla__slide__inner'));

  setupPrevNextBtns(prevBtn, nextBtn, embla);
  setupDotBtns(dotsArray, embla);

  embla.on("select", setSelectedDotBtn);
  embla.on("select", disablePrevAndNextBtns);
  embla.on("init", setSelectedDotBtn);
  embla.on("init", disablePrevAndNextBtns);

  // Prevent default on click if embla doesn't allow click
  emblaSlidesInner.forEach(slide => {
    slide.addEventListener('mouseup', ()=> {
      dropLinks.forEach(dropLink => {
        dropLink.classList.remove('disabled');
        console.log('all classes disabled removed');
      });
    });
  });

  dropLinks.forEach(dropLink => {
    dropLink.addEventListener('mousedown', (event) => {

      clearTimeout(t);
      t = setTimeout( ()=>{

        if (!embla.clickAllowed()) {

          dropLink.classList.add('disabled');
          console.log('disabled add');

        }

      }, time);

    }, false);

  });
};

const options = { loop: false };
const emblaNodes = [].slice.call(document.querySelectorAll(".embla"));
const emblaCarousels = emblaNodes.map(emblaNode =>
  setupEmblaCarousel(emblaNode, options)
);

I want to explain why i using such strange method, its because of my custom routing system, my web site is Single Web Page App, so i have this kind of router that triggering when i click links so i need disable pointer events on mousedown and enable it on mouse up
this code is inside my app.js -- central controller for my website it already listens all that have data-link attribute
window.addEventListener("popstate", router);

document.addEventListener("DOMContentLoaded", () => {
    document.body.addEventListener("click", e => {
        if (e.target.matches("[data-link]")) {
            e.preventDefault();

            //console.log(e.target.href);
            if (e.target.href == undefined) {
                navigateTo(e.target.parentNode.href);
            } else {
                navigateTo(e.target.href);
            }
            //design part

            //navigateTo(e.target.href);
            //console.log(e.target);
        }
    });

    router();
});

its hard to setup my routing system on codeSendbox sorry sir, all i want to say its using this event to trigger click on links
window.addEventListener("popstate", router);

document.addEventListener("DOMContentLoaded", () => {
    document.body.addEventListener("click", e => {
        if (e.target.matches("[data-link]")) {
            e.preventDefault();

            if (e.target.href == undefined) {
                navigateTo(e.target.parentNode.href);
            } else {
                navigateTo(e.target.href);
            }

        }
    });

    router();
});

import { setupPrevNextBtns, disablePrevNextBtns } from "./prevAndNextButtons";
import { setupDotBtns, generateDotBtns, selectDotBtn } from "./dotButtons";

let time = 210;

let t = setTimeout( ()=>{}, time);

const setupEmblaCarousel = (emblaNode, options) => {
  const viewPort = emblaNode.querySelector(".embla__viewport");
  const prevBtn = emblaNode.querySelector(".embla__button--prev");
  const nextBtn = emblaNode.querySelector(".embla__button--next");
  const dots = emblaNode.querySelector(".embla__dots");
  const embla = EmblaCarousel(viewPort, options);
  const dotsArray = generateDotBtns(dots, embla);
  const setSelectedDotBtn = selectDotBtn(dotsArray, embla);
  const disablePrevAndNextBtns = disablePrevNextBtns(prevBtn, nextBtn, embla);

  const dropLinks =  [].slice.call(emblaNode.querySelectorAll('.drop-link'));

  setupPrevNextBtns(prevBtn, nextBtn, embla);
  setupDotBtns(dotsArray, embla);

  embla.on("select", setSelectedDotBtn);
  embla.on("select", disablePrevAndNextBtns);
  embla.on("init", setSelectedDotBtn);
  embla.on("init", disablePrevAndNextBtns);

  document.addEventListener('mouseup', ()=> {
    dropLinks.forEach(dropLink => {
      dropLink.classList.remove('disabled');
      console.log('removed');
    });
  });

  dropLinks.forEach(dropLink => {
    dropLink.addEventListener('mousedown', (event) => {
      clearTimeout(t);
      t = setTimeout( ()=>{
            dropLink.classList.add('disabled');
            console.log('added');
      }, time);
    });
  });

};

const options = { loop: false };
const emblaNodes = [].slice.call(document.querySelectorAll(".embla"));
const emblaCarousels = emblaNodes.map(emblaNode =>
  setupEmblaCarousel(emblaNode, options)
);

So this what i came up for now, it works ok

Hi @vladtabachuk,
This piece of code you shared is why my suggestion didn’t work:
document.body.addEventListener("click", e => {
  if (e.target.matches("[data-link]")) {
    e.preventDefault();

   if (e.target.href == undefined) {
     navigateTo(e.target.parentNode.href);
    } else {
      navigateTo(e.target.href);
    }
  }
});

Because what you’re doing here is programmatically navigating when a user clicks on a link. You can’t run this script on link click if embla.clickAllowed() returns false, otherwise it will navigate regardless of what Embla says.
I hope that makes sense.
Best,
David

Yes, You exactly right i programaticly navigating pages, if you want i can send you simplified version of this routing system, maybe you want to explore it, its very simple, but i suggest you not to waste time on my problem, im doing good so far, thank you for feedback you realy NICE GUY, you can write me message on email and i'll send you archive simplified version of this routing system<EMAIL_ADDRESS>so you can rework it or may be learn something from it

@davidjerleke
Hello. I am using carousel in React. I use useEmblaCarousel hook but how can I refer clickAllowed property?

@donghoon-song clickAllowed has been removed because it’s handled automatically now.

Hi, @davidjerleke, but hasn't this then reverted back to the original issue of disabling click events while dragging? I just stumbled upon this problem myself, so I'm going through github issues to try and track down some known solution. The simple solution right now for me was to utilize scroll and settle events:
.on('scroll', () => this.disableClick = true)
.on('settle', () => this.disableClick = false);

and then toggle pointer-events: none css/class based on this for the slides.
However, this approach has an issue that scroll event takes a long time to phase out in the end with micro-movements, i.e. slides barely move but, technically, they are still "scrolling". This effect means, that for a second or even more, slider has almost stopped, but is still un-clickable. I would want to somehow enable click sooner.
I'm still experimenting with some timeout hacks and such, but just curious if there isn't some better way altogether.
I did notice that I can click while carousel ir scrolling and it would stop and settle, enabling for me click events. However, in this case user has to click again, to actually navigate to the link (essentially requiring a double-click).

@EdgarsJoja what version are you using?

@EdgarsJoja v8 is definitely handling that automatically. And I haven't had any issues at all with this since the first v8.0.0-rc01 so it doesn't seem likely that this is related to Embla.

just in case this is of use to someone else... there was indeed an issue with external code.
I'm using Embla in Livewire project, and those slides had wire:navigate directive. This was causing issues. Ideally, would want to keep wire:navigate, but not a complete dealbreaker as well, if I cannot somehow fix it...
Sry for the false alarm.

There is a really simple way to do this by using the property:
"watchDrag: false"
Among the options that the carousel accepts


Implement filtering by category

@rnyak , please start the initial investigation and get back

This may have to be moved to the systems repo. @karlhigley , please take a look

This development may be required once we merge this PR https://github.com/NVIDIA-Merlin/Merlin/pull/496


Fix script name to open chrome

A previous commit renamed the apple script to open chrome from
chrome.applescript to openChrome.applescript. That created
a minor bug. Even when chrome was open with the client app,
npm start would open the client app in a new Safari tab on
macOS instead of re-using the open tab in chrome.

Ah, good catch. Thanks!


real_time

Firstly,thanks your work very much, I'm study the TFA module recently. I have some problems in the script. 1. the shape of ZF is [1 D] where the script is [T D] 2. the time_seq is the number that add before input x, so why is this done in real time and how the value (32 in script) of time_seq should be set and what it relates to?  Thank you again!

so the time_seq is the number of history frames used by nn.AvgPool1d()? I find causal conv2d script have the same operation (pad one frame before), so I set smaller time_seq will not affect causality but scan less historical information.
In addition, I would like to ask about the 1x1 conv, to my knowledge, the kernel_size is 1x1 but there is 3x1 in the script. I'm read some papers which add conv 1x1 to the skip connection (DCCRN+),So, the 1x1 conv can not change the input shape, I don't know if you've done the corresponding experiments and give me some useful advice.

so the time_seq is the number of history frames used by nn.AvgPool1d()? --> Yes!
so I set smaller time_seq will not affect causality --> what does this mean?
Could you please explain the question below in more detail? Sorry, I didn't understand the question.

so I set smaller time_seq will not affect causality --> it means pad any size(>0) of time_seq before input x, the system is causality.
1x1 conv used in skip connection ---> the kernel size is 1x1? I think the output's channel and freq should be the same of input because it will add to the decoder. if use 1x1 kernel size, what's the point of doing this operation. or there is other operation after 1x1 conv like BN and activate function?

First of all, I didn't use any convolutional filter for skip-connection.
What part did you see and say?

1x1 conv down_ sample where the kernel size is not 1x1.

down_sampling is not used as a filter for skip connections. It is the module used to encode. It has the same input and output channels and simply compresses the frequency axis in half for down-sampling.
If you don't understand, I recommend taking a look at the Nested Unet structure. References to this are also in the README.
And there is no particular reason why the kernel size is (3x1).


CICD-426 - add cf cli autoscaling plugin and enable option to rolling-deploy

Adding support for Autoscaling cf cli plugin. Updated dockerfile to add the autoscaling plugin to the cf cli and updated the rolling deploy to check for the autoscale.yml file in the application repo.
More info: https://merrillcorporation.atlassian.net/wiki/spaces/Product/pages/418775452/PCF+Autoscaling+using+CF+CLI

VERSION will also need to be manually bumped. which has changed and will likely change, so a sync is needed.

@kaltepeter Thanks for all the great feedback.  I will adjust and test.

closing until updated.


Project status? Doesn't seem maintained

It seems like this package isn't maintained anymore. Am I mistaken?
A few PR are hanging, nothing useful has been merged since oct 2019.

Hi @Vadorequest, I solved PR, such as formatting the day and time and configuring the time zone and adjusting the log levels, also adding the display of the line and column that makes the log, all configurable.
https://www.npmjs.com/package/signale-logger

Hi @Vadorequest, I solved PR, such as formatting the day and time and configuring the time zone and adjusting the log levels, also adding the display of the line and column that makes the log, all configurable.
https://www.npmjs.com/package/signale-logger

It is a brand-new one? I could not see github fork subtitle in the repos.

Looking at https://www.npmjs.com/package/signale-logger versions, it does seem like a whole new package on NPM.

Hello @Vadorequest @davidkhala , signale-logger is the last version of signale (1.4.0) to which I applied some PR that requested and were on hold, and as I had an urgency to use it I decided to upload it to npm, when they do the PR of the earrings (in signale) , I estimate that this package I will deprecate it.

Thanks for the clarification!

I'm on the fence about using this. Is there any indication that this library is still maintained?

hello @jakobrosenberg , the original library has not been updated for a long time and has some PR pending, if you want, you can use the fork I made from the original and implement some improvements they requested.
https://www.npmjs.com/package/signale-logger

@rudemex thanks for maintaining a fork.
I wish the author would assign a maintainer, release a statement or reply to this issue.

@rudemex maybe we should create a public organization to host a fork and enable more contributors to join.
We could create a signale github org and use the @signale npm fork (if available).

hi @stephanebachelier , how are you? i created a project that has available to implement PR following the requirements of the original project, it is also deployed in npm and yarn, i don't think it is necessary to create an organization, and the project with signale is occupied by the original.
I'm following up the project, I have some pending tasks to solve, but PR is welcome.
Repo Signale-logger: https://github.com/rudemex/signale-logger

Hi @rudemex,
The idea is not mine. I've already seen it in other open-source repositories when the maintainer was missing.
Some contributors and/or users have decided to create an organisation to open the project to a community of contributors to avoid the « single contributor syndrome ». If the fork is maintained by a single contributor, who might not available or missing at some point, - which might be expected on a long term basis -, the same problem surfaces again.
IMO, an open organisation, such as a Github org, seems more appropriated.

@stephanebachelier yes, it's not a bad idea, but I think it will generate conflict to have many dependencies created in npm on the same project, my repo is public and I can add collaborators, so you can give a maintenance to the project.
If you think so, I'll add you as a collaborator.

Is this repo still alive?

@hustcer After reading through this issue, it seems there's a community fork at https://github.com/rudemex/signale-logger (h/t @rudemex)


V1.3 release conflict?

Hi geky
I've downloaded the V1.3 at end of March and now there is a new version 1.3 including the bugfix of the lookahead.
By the way if you look at the releases page the V1.3 is dated February the 20th.
Is there a multiple V1.3? Does it make sense to generate a V1.4?
Thanks in advance.

Hi @davidefer,
The release script is currently set up to copy any bug fixes into the most recent release. The idea is if you download a specific release you will also get any bug fixes related to the release.
The minor version number is only incremented when a feature is added, it's still backwards compatible but more likely to introduce bugs and may require additional work to update if the user wants to take advantage of new features.
If you need to specify a frozen point in history, you can use the github commit hash.
Let me know if this concerns you.

We're looking at improving this over here https://github.com/ARMmbed/littlefs/issues/79


v1.6.0 seems to break babeling styled-component's own code

Hey, everyone
First of all, thanks for all the amazing work you do! :)
We have recently upgraded to version^1.6.0 of babel-plugin-styled-components , when we started to see the following error:
TypeError: Property left of AssignmentExpression expected node to be of a type ["LVal"] but instead got "CallExpression"
    at Object.validate (/Users/robin.drexler/Development/babel-styled/node_modules/@babel/types/lib/definitions/utils.js:128:13)
    at Object.validate (/Users/robin.drexler/Development/babel-styled/node_modules/@babel/types/lib/validators/validate.js:17:9)
    at NodePath._replaceWith (/Users/robin.drexler/Development/babel-styled/node_modules/@babel/traverse/lib/path/replacement.js:194:9)
    at NodePath.replaceWith (/Users/robin.drexler/Development/babel-styled/node_modules/@babel/traverse/lib/path/replacement.js:178:8)
    at /Users/robin.drexler/Development/babel-styled/node_modules/babel-plugin-styled-components/lib/visitors/desugarStyled.js:37:14
    at PluginPass.MemberExpression (/Users/robin.drexler/Development/babel-styled/node_modules/babel-plugin-styled-components/lib/index.js:16:40)
    at newFn (/Users/robin.drexler/Development/babel-styled/node_modules/@babel/traverse/lib/visitors.js:193:21)
    at NodePath._call (/Users/robin.drexler/Development/babel-styled/node_modules/@babel/traverse/lib/path/context.js:53:20)
    at NodePath.call (/Users/robin.drexler/Development/babel-styled/node_modules/@babel/traverse/lib/path/context.js:40:17)
    at NodePath.visit (/Users/robin.drexler/Development/babel-styled/node_modules/@babel/traverse/lib/path/context.js:88:12)

We dug into it a bit and found that it seems to be caused by desugarStyled.js as it tries to transpile styled.js in styled-components which then fails.
We also noticed a significant slowdown when the new plugin version is used. We uncommented the MemberExpression visitor and it got a lot faster again.
We have created a small repository where you can reproduce the issues described.
In this repository, we have put a file input.js which inlcudes the esm version of styled-components and nostyled.js that has the same content but with the line removed which causes the error.
https://github.com/robin-drexler/styled-components-babel-issue
git clone  git@github.com:robin-drexler/styled-components-babel-issue.git
cd styled-components-babel-issue
yarn

You can run yarn broken to see the error.
yarn slow to get a successful but slower result.
yarn fast which removes  babel-plugin-styled-components and is faster.
I used node v10.3.0 and yarn 1.7.0
Let me know if there is more info to provide. :)

Hmm thank you. I'll take a look today or tomorrow

@robin-drexler pushed a fix for the hard error in 1.6.1. Not sure about the slowdown though... perhaps it's due to the SSR option being on by default now? You can disable it by passing "ssr": false to the plugin.

@probablyup Thanks for the timely fix!
Regarding the slowdown: Setting ssr to true or false does not seem to make any difference. It's always about 9 seconds on my machine.
Removing the MemberExpression reduces the time to 0.7 seconds.

With 1.6.x version I've got on node error during the build:
function _templateObject5(){var data=_taggedTemplateLiteral(["\n      @media screen and (max-width: 360px) {\n        ",";\n      }\n    "]);_templateObject5=function _templateObject5(){return data;};return data;}function _templateObject4(){var data=_taggedTemplateLiteral(["\n      @media screen and (max-width: 540px) {\n        ",";\n      }\n    "]);_templateObject4=function _templateObject4(){return data;};return data;}function _templateObject3(){var data=_taggedTemplateLiteral(["\n      @media screen and (max-width: 767px) {\n        ",";\n      }\n    "]);_templateObject3=function _templateObject3(){return data;};return data;}function _templateObject2(){var data=_taggedTemplateLiteral(["\n      @media screen and (max-width: 1536px) {\n        ",";\n      }\n    "]);_templateObject2=function _templateObject2(){return data;};return data;}function _templateObject(){var data=_taggedTemplateLiteral(["\n      @media all and (-ms-high-cont

TypeError: styled_components__WEBPACK_IMPORTED_MODULE_0__ is not a function


Intersect Function Error and a performance question

OrientDB Version: 2.2.16
Java Version: 1.8.0_40-b27
OS: OS X Yosemite
I am trying the GratefulDeadConcerts database that is coming with OrientDB installation and I came up with a problem. When I write a simple query that intersects followed_by relations between two songs there is no problem (select intersect(in('followed_by')) from [9:2,9:4]) but when I want to intersect three of them with this query --> select intersect(in('followed_by')) from [9:2,9:4,9:6] OrientDB throws exception: java.lang.ClassCastException:java.util.HashSet cannot be cast to java.util.Iterator. I think It is a bug.
Another question is for the performance of intersections. Consider Catalog system. I want to fetch Catalogs with Brand Samsung which belongs to Accessories category but There may be thousands of Catalogs with Brand Samsung and millions of catalogs belongs to Accessories category. What would be the correct model to be able search and find results and can intersection function be considered for these cases? I tried intersect function with two vertexes having million edges but the elapsed time was too long (about 30 seconds)
Thanks in advance.

Any answers?

Hi @ozgursucu
Sorry, I still had no chance to check it (but I'd say the ClassCastEx is a bug)
I'll let you know asap
Thanks
Luigi

Hi @ozgursucu
I just pushed a fix on 2.2.x branch. The fix will be released with 2.2.18, scheduled for next Wednesday
Thanks
Luigi

Thanks @luigidellaquila.
And what about the performance?

Any answers about the performance?

Hi @ozgursucu
As a rule of thumb, the performance depends on how many records you have to fetch, so I suggest you to start from the vertex that has less connected edges and then evaluate the other side of the relationship.
In this case you should start from the brand and then filter based on the other side of the relationship.
When you have a vertex that is in the middle or two supernodes this is particularly expensive, unfortunately there is no silver bullet to fix it.
Thanks
Luigi

Hi @luigidellaquila
Does intersect function simply compare the rids? Then would select intersect(in('catalogLink')) from [12:0,18:9,15:0] where 12:0 have 100000 catalogLink, 18:9 10000 catalogLink, 15:0 20000 catalogLink be a slow query?

Yes it does, I'll double-check it, but it should be efficient enough to avoid deep comparing the docs
Thanks
Luigi

Hi @luigidellaquila
Did you have any chance to check the efficiency?

Hi @ozgursucu
I checked the function, it does not perform deep compare, but it works on iterators that can come from previous steps, so in some cases they can trigger record deserialization.
So I cannot guarantee 100% that it always works on RIDs
Thanks
Luigi

Hi @luigidellaquila
How can it be possible to prevent record deserialization so that it just works on RIDs and avoid deep comparison?

Hi @luigidellaquila
Would you please answer the last question above?

Hi @ozgursucu
I'm afraid there is not a final answer for this, it depends a lot on internal behaviors, so you don't have much control on that...
Luigi


Update to angular ui bootstrap v0.13.3

This updates the typings to v.0.13.3 as well as removes some settings that were missed in prior updates.

@xt0rted thanks mate!


Custom page size only works for first page

I set a custom page size for pdf export larger than 8.5 x 11 and the generated pdf only retained this page size for the first page. Subsequent pages revert to the standard document size.

I believe this was resolved in https://github.com/nhmkdev/cardmaker/releases/tag/v.<IP_ADDRESS>-unstable.v.a4
What build are you running? You could try in one of the newer pre-releases if you're running <IP_ADDRESS>.

Closing out.


prefer 'predicted' time over 'scheduled'

Checklist

[X] I have filled out the template to the best of my ability.
[X] This only contains 1 feature request (if you have multiple feature requests, open one feature request for each feature request).
[X] This issue is not a duplicate feature request of previous feature requests.

Is your feature request related to a problem? Please describe.
The sensor value currently reflects the next scheduled departure for a stop. The API includes information on the 'predicted' departures when realtime information is known, but this library doesn't make use of that data
Describe the solution you'd like
prefer 'predicted' timings when available
Describe alternatives you've considered
the predicted values could be an alternate piece of information rather than primary value of the exposed sensor if that's easier
Additional context
An example API response of the arrivalsAndDepartures struct looks like
{
	"0": {
		"actualTrack": "",
		"arrivalEnabled": true,
		"blockTripSequence": 0,
		"departureEnabled": true,
		"distanceFromStop": -3890.458987405673,
		"frequency": null,
		"historicalOccupancy": "",
		"lastUpdateTime":<PHONE_NUMBER>000,
		"numberOfStopsAway": -2,
		"occupancyStatus": "",
		"predicted": true,
		"predictedArrivalInterval": null,
		"predictedArrivalTime":<PHONE_NUMBER>000,
		"predictedDepartureInterval": null,
		"predictedDepartureTime":<PHONE_NUMBER>000,
		"predictedOccupancy": "",
		"routeId": "40_100479",
		"routeLongName": "Lynnwood - Angle Lake",
		"routeShortName": "1 Line",
		"scheduledArrivalInterval": null,
		"scheduledArrivalTime":<PHONE_NUMBER>000,
		"scheduledDepartureInterval": null,
		"scheduledDepartureTime":<PHONE_NUMBER>000,
		"scheduledTrack": "",
		"serviceDate":<PHONE_NUMBER>000,
		"situationIds": [
			"40_6165",
			"40_6336",
			"40_5396"
		],
		"status": "default",
		"stopId": "40_99603",
		"stopSequence": 14,
		"totalStopsInTrip": 23,
		"tripHeadsign": "Lynnwood City Center",
		"tripId": "40_LLR_2024-09-14_Jun27_Fall2024_Weekday_100479_1040",
		"tripStatus": {
			"activeTripId": "40_LLR_2024-09-14_Jun27_Fall2024_Weekday_100479_1040",
			"blockTripSequence": 0,
			"closestStop": "40_99605",
			"closestStopTimeOffset": -18,
			"distanceAlongTrip": 32619.724848587546,
			"frequency": null,
			"lastKnownDistanceAlongTrip": 0,
			"lastKnownLocation": {
				"lat": 47.64974594116211,
				"lon": -122.3036880493164
			},
			"lastKnownOrientation": 0,
			"lastLocationUpdateTime":<PHONE_NUMBER>000,
			"lastUpdateTime":<PHONE_NUMBER>000,
			"nextStop": "40_990002",
			"nextStopTimeOffset": 132,
			"occupancyCapacity": -1,
			"occupancyCount": -1,
			"occupancyStatus": "",
			"orientation": 91.69393153837532,
			"phase": "in_progress",
			"position": {
				"lat": 47.65203300158957,
				"lon": -122.30374689569551
			},
			"predicted": true,
			"scheduleDeviation": 136,
			"scheduledDistanceAlongTrip": 32619.724848587546,
			"serviceDate":<PHONE_NUMBER>000,
			"situationIds": [
				"40_6165",
				"40_6336",
				"40_5396"
			],
			"status": "SCHEDULED",
			"totalDistanceAlongTrip": 52703.57686586333,
			"vehicleFeatures": [],
			"vehicleId": "40_13 [283-317-309-324]"
		},
		"vehicleId": "40_13 [283-317-309-324]"
	}
}

when predicted deviates from scheduled, this is used in the official applications to indicate that an arrival is early or delayed.

it's a good idea. I am no longer using this integration since I don't live in Seattle anymore. But I am happy to accept PRs or if someone else wants to fork/maintain this, that would be awesome.


Socket Connect hangs until timeout runs out in mirrored mode.

Windows Version
Microsoft Windows [Version 10.0.22631.2715]
WSL Version
<IP_ADDRESS>  and 2.0.14 tested
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Ubuntu 22.04
Other Software
No response
Repro Steps
Call this script in mirrored mode as normal user or sudo (try both):
import socket
import time
import os

def is_port_in_use(port):
    with socket.socket(socket.AF_INET, socket.SOCK_STREAM) as s:
        # s.settimeout(2)  # set timeout directly

        print(f"Socket type: {s.type}")
        print(f"Socket family: {s.family}")
        print(f"Socket timeout: {s.gettimeout()} seconds")
        # Get and print socket options
        print(f"SO_REUSEADDR option: {s.getsockopt(socket.SOL_SOCKET, socket.SO_REUSEADDR)}")
        print(f"SO_KEEPALIVE option: {s.getsockopt(socket.SOL_SOCKET, socket.SO_KEEPALIVE)}")
        print(f"TCP_NODELAY option: {s.getsockopt(socket.IPPROTO_TCP, socket.TCP_NODELAY)}")
        print("checking: ", port)
        print("Timeout: ",s.gettimeout())
        return s.connect_ex(("localhost", port)) == 0

print("Uid: ", os.getuid())
start_time = time.time()
print("Is Port in use:", is_port_in_use(6006))
print("--- Runtime: %s seconds ---" % (time.time() - start_time))

Expected Behavior
It directly checks if the socket is in use or not.
Actual Behavior
Sometimes it takes over 132 seconds to return True or False. In not mirrored mode it always directly returns. I came across this issue using ros, where the roscore takes about 2 minutes to start, or starting tensorboard takes around 2 minutes aswell, so i build this script to reproduce the error.
If it directly returns true or false in mirrored mode, i start the script as sudo and then the problem occurs again.
What is interesting, is that if i set the socket timeout to a specific second, then it will return after that. Its like its blocked for the default timeout.
Diagnostic Logs
Without networking mode mirrored:
❯ python3 test_connect.py
Uid:  1000
Socket type: 1
Socket family: 2
Socket timeout: None seconds
SO_REUSEADDR option: 0
SO_KEEPALIVE option: 0
TCP_NODELAY option: 0
checking:  6006
Timeout:  None
Is Port in use: False
--- Runtime: 0.0001404285430908203 seconds ---
With networking mode mirrored:
❯ python3 test_connect.py
Uid:  1000
Socket type: 1
Socket family: 2
Socket timeout: None seconds
SO_REUSEADDR option: 0
SO_KEEPALIVE option: 0
TCP_NODELAY option: 0
checking:  6006
Timeout:  None
Is Port in use: False
--- Runtime:<PHONE_NUMBER>8111877 seconds ---
Sometimes it works as fast as without mirrored. But sometimes not, even tho it results in the port is not in use.
If it works directly, starting the script with sudo will result again in this timeout.
With networking mode mirrored and setting timeout to a second with:
s.settimeout(1) before the connect_ex call
❯ python3 test_connect.py
Uid:  1000
Socket type: 1
Socket family: 2
Socket timeout: 1.0 seconds
SO_REUSEADDR option: 0
SO_KEEPALIVE option: 0
TCP_NODELAY option: 0
checking:  6006
Timeout:  None
Is Port in use: False
--- Runtime: 1.001239538192749 seconds ---
Or with settimeout to 2 seconds:
❯ python3 test_connect.py
Uid:  1000
Socket type: 1
Socket family: 2
Socket timeout: 2.0 seconds
SO_REUSEADDR option: 0
SO_KEEPALIVE option: 0
TCP_NODELAY option: 0
checking:  6006
Timeout:  2.0
Is Port in use: False
--- Runtime: 2.0022153854370117 seconds ---

Could you please follow the steps below and attach the diagnostic logs? https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues

Please follow the networking diagnostic script. https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues
It should create a folder like [WslNetworkingLogs-date_ver.zip]

WslNetworkingLogs-2023-12-07_21-14-32.zip
Updated

I have the same issue with WSL <IP_ADDRESS>

Still the same problem with 2.1.0

same problem here with 2.1.0.
It is frustrating because some applications expect a conneciton refused when performing port checks with telnet

When I go through windows telnet localhost [port] the access is very slow, but when I go through telnet <IP_ADDRESS> [port] or telnet native ip [port] it is very fast, I think it might be because there is a problem with localhost resolution, so I found a blog I looked at the prioritization policy for IPv6
netsh interface ipv6 show prefixpolicies
Default policy
Priority    label  prefix

    50      0  ::1/128
    40      1  ::/0
    35      4  ::ffff:0:0/96
    30      2  2002::/16
     5      5  2001::/32
     3     13  fc00::/7
     1     11  fec0::/10
     1     12  3ffe::/16
     1      3  ::/96

I've changed the order of their priorities
PS: required Administrator
netsh int ipv6 set prefix ::/96 50 0
netsh int ipv6 set prefix ::ffff:0:0/96 40 1
netsh int ipv6 set prefix 2002::/16 35 2
netsh int ipv6 set prefix 2001::/32 30 3
netsh int ipv6 set prefix ::1/128 10 4
netsh int ipv6 set prefix ::/0 5 5
netsh int ipv6 set prefix fc00::/7 3 13
netsh int ipv6 set prefix fec0::/10 1 11
netsh int ipv6 set prefix 3ffe::/16 1 12

Modified policy
Priority    label  prefix

    50      0  ::/96
    40      1  ::ffff:0:0/96
    35      2  2002::/16
    30      3  2001::/32
    10      4  ::1/128
     5      5  ::/0
     3     13  fc00::/7
     1     12  3ffe::/16
     1     11  fec0::/10

now telnet <IP_ADDRESS> [port]  is getting fast
But I don't know what other problems such a change would cause
It can be reset by the following command
netsh interface ipv6 reset
PS: reboot your system

When I go through windows telnet localhost [port] the access is very slow, but when I go through telnet <IP_ADDRESS> [port] or telnet native ip [port] it is very fast, I think it might be because there is a problem with localhost resolution, so I found a blog I looked at the prioritization policy for IPv6
netsh interface ipv6 show prefixpolicies
Default policy
Priority    label  prefix
----------  -----  --------------------------------
        50      0  ::1/128
        40      1  ::/0
        35      4  ::ffff:0:0/96
        30      2  2002::/16
         5      5  2001::/32
         3     13  fc00::/7
         1     11  fec0::/10
         1     12  3ffe::/16
         1      3  ::/96

I've changed the order of their priorities PS: required Administrator
netsh int ipv6 set prefix ::/96 50 0
netsh int ipv6 set prefix ::ffff:0:0/96 40 1
netsh int ipv6 set prefix 2002::/16 35 2
netsh int ipv6 set prefix 2001::/32 30 3
netsh int ipv6 set prefix ::1/128 10 4
netsh int ipv6 set prefix ::/0 5 5
netsh int ipv6 set prefix fc00::/7 3 13
netsh int ipv6 set prefix fec0::/10 1 11
netsh int ipv6 set prefix 3ffe::/16 1 12

Modified policy
Priority    label  prefix
----------  -----  --------------------------------
        50      0  ::/96
        40      1  ::ffff:0:0/96
        35      2  2002::/16
        30      3  2001::/32
        10      4  ::1/128
         5      5  ::/0
         3     13  fc00::/7
         1     12  3ffe::/16
         1     11  fec0::/10

now telnet <IP_ADDRESS> [port] is getting fast
But I don't know what other problems such a change would cause
It can be reset by the following command netsh interface ipv6 reset PS: reboot your system

not work for me.

When I go through windows telnet localhost [port] the access is very slow, but when I go through telnet <IP_ADDRESS> [port] or telnet native ip [port] it is very fast, I think it might be because there is a problem with localhost resolution, so I found a blog I looked at the prioritization policy for IPv6
netsh interface ipv6 show prefixpolicies
Default policy
Priority    label  prefix
----------  -----  --------------------------------
        50      0  ::1/128
        40      1  ::/0
        35      4  ::ffff:0:0/96
        30      2  2002::/16
         5      5  2001::/32
         3     13  fc00::/7
         1     11  fec0::/10
         1     12  3ffe::/16
         1      3  ::/96

I've changed the order of their priorities PS: required Administrator
netsh int ipv6 set prefix ::/96 50 0
netsh int ipv6 set prefix ::ffff:0:0/96 40 1
netsh int ipv6 set prefix 2002::/16 35 2
netsh int ipv6 set prefix 2001::/32 30 3
netsh int ipv6 set prefix ::1/128 10 4
netsh int ipv6 set prefix ::/0 5 5
netsh int ipv6 set prefix fc00::/7 3 13
netsh int ipv6 set prefix fec0::/10 1 11
netsh int ipv6 set prefix 3ffe::/16 1 12

Modified policy
Priority    label  prefix
----------  -----  --------------------------------
        50      0  ::/96
        40      1  ::ffff:0:0/96
        35      2  2002::/16
        30      3  2001::/32
        10      4  ::1/128
         5      5  ::/0
         3     13  fc00::/7
         1     12  3ffe::/16
         1     11  fec0::/10

now telnet <IP_ADDRESS> [port] is getting fast
But I don't know what other problems such a change would cause
It can be reset by the following command netsh interface ipv6 reset PS: reboot your system

not work for me.

Are you using powershell or cmd on windows ？

CMD

Powershell

@linG5821
We have a different issue. The problem is that the port is not listening, not that it is refusing connections immediately.

I did find problems with changing the default NIC policy in practice
I mapped ports when using Docker, I tried '<IP_ADDRESS>:port' and 'localhost:port' both were accessible, but I used the Intranet ip 'ipv4ip:port' and couldn't access it, when I reset the network, Intranet ip 'ipv4ip:port' and '<IP_ADDRESS>:port' are accessible, and access to 'localhost:port' comes back to the issue itself.

Still the same issue with <IP_ADDRESS>

Still the same issue on 2.1.5. @chanpreetdhanjal is there any way to help? I have a workaround for ROS but it's a bit annoying on tensorboard to wait that long after fetching plots.

Someone from our team is looking at it. We will get back to you as soon as we make further progress. Thank you for your patient.

Can't believe MS team still not resolve this bug. It's pretty annoying problem, especially when I am going to using the vscode JS debug terminal in WSL2 mirrored network mode.

We are actively looking at it as per other items in our priority list. Will provide an update as soon as we have something tangible to share.

To update this thread: there are 2 possible issues.

when attempting to connect by name "localhost", the IPv6 address ::1 is likely resolved first (v4 vs. v6 is configurable in Linux). Linux does not support the option for IPv6 that we use to allow sending localhost traffic to the host - it's only supported with IPv4. So unfortunately we cannot use the :;1 address to connect from the Linux container to the host.

when a connection is attempted by IPv4 <IP_ADDRESS> to the host, but nothing is listening on the host, a RST is returned. We see that something has attempted to port-forward that response because the Linux stack eventually sees this with a different source port (which of course is dropped). We're currently working with Linux folks as we have tracked the response through a kernel debugger to the point where we send it over the vmBus to the Linux container.

Sorry, the RST issue is taking much longer to root cause than expected :(
Hope this helps

Has there been any progress on this issue?

we have spent a lot of cycles debugging down the windows stack, through vswitch, to the vm - this has been really difficult and we don't yet have a culprit. we are fixing some Docker related issues - once that goes out, we'll return back to finding this bug.

when a connection is attempted by IPv4 <IP_ADDRESS> to the host, but nothing is listening on the host, a RST is returned. We see that something has attempted to port-forward that response because the Linux stack eventually sees this with a different source port (which of course is dropped). We're currently working with Linux folks as we have tracked the response through a kernel debugger to the point where we send it over the vmBus to the Linux container.

indeed, when capturing packets on Windows and Linux (WSL), the port is wrong.
Windows host                                  linux(WSL)
       HV interface     FSE switch         loopback0
syn    222 <- 60844                         222 <- 60844
         00:11:22:33:44:55 <-------------- 00:15:5d:bd:df:a8

rst    222 -> 60844                         222 -> 45634
                                                   ^^^^^???
00:15:5d:61:13:45  ----------------------> 00:15:5d:bd:df:a8

destination MAC address Windows sent the packet to is loopback0 (WSL).
MAC address received by Linux (WSL) is the one sent by Windows.
if both perceptions are correct, then maybe something is going on inside the FSE switch?
hostAddressLoopback=true & eth0 address will back to destination port Windows sent it to, which is fine.
i think it is basically the same mechanism, but the behavior is different.

I'm having the same issue. Just got upgraded to Win11 22H2 and have been waiting to try mirrored networking. It did not take long to find this issue. Please fix.

same issue with <IP_ADDRESS>

Any updates on resolutions or workarounds for this issue?

Same issue here using WSL <IP_ADDRESS> just updated

its now about WSL
its about hyper-v adaptors
I fixed it:
Run powershell as Administrator
wsl --shutdown
win + R keys to run
"C:\WINDOWS\System32\mmc.exe" "C:\WINDOWS\System32\virtmgmt.msc" in run and Enter
stop service
now in powershell Enter: Get-HNSNetwork | ? Name -Like * | Remove-HnsNetwork
start service from old mmc.exe command
run wsl

its now about WSL its about hyper-v adaptors
I fixed it:
Run powershell as Administrator wsl --shutdown win + R keys to run "C:\WINDOWS\System32\mmc.exe" "C:\WINDOWS\System32\virtmgmt.msc" in run and Enter stop service now in powershell Enter: Get-HNSNetwork | ? Name -Like * | Remove-HnsNetwork start service from old mmc.exe command run wsl

does not work for me :/


[bug]: universe_roots cache-hit ratio, gross underperformance

Background
This issue relates to the cache performance of universe_roots with respect to interacting with the DB cache. Based on the logs from Lab's universe, the hit-to-misses ratio for this cache is exhibiting under performance. Remediating the issue will ensure performance and efficiency of universe functionality.

│ 2024-04-01 23:32:09.632 [INF] TADB: db cache universe_roots: 260271 hits, 2225329 misses, 10.47% hit ratio

Steps to reproduce [edit at will]

Initialize a universe
Let the universe_roots cache be populated with roots
Observe the cache usage over a period of time (e.g., minutes)
Check the cache hit-to-misses ratio in the logs or monitoring dashboard

Expected result:
The hit-to-misses ratio should be higher than [?80%]
Actual result:
The cache hit-to-misses ratio is insufficient -- at ~10%.
Ramification question: Do the missed hits cause additional/supplemental/superfluous requests?
Possible solutions:

Analyze the current cache configuration to identify any optimization opportunities.
Investigate if inefficiencies in the caching logic that need to be fixed.

Please provide feedback or suggestions for further improvement after reviewing this issue.

to be answered:
Are the elements that are being missed, actually being cached?

From offline discussion, I think cache was just too small. Worst-case size is 2x # of asset IDs / groups since there are issuance and transfer roots.

This was also slow to populate for me locally, which caused a timeout on the CLI command universe roots.
Running 0.4.0 rc3, with the old "full sync" mode (I think?) connected to the testnet LL universe server:
2024-07-10 13:29:40.121 [INF] TADB: populating root cache...
2024-07-10 13:35:45.524 [INF] TADB: populating root cache...
2024-07-10 13:37:20.565 [DBG] TADB: Populating 512 root nodes into cache, took=1m35.040313762s

I think the cache gets dumped repeatedly during the process of sync for being too small?
Even after a successful universe roots call, future calls claim to be repopulated the root cache and take the same amount of time.

Doubling the page size universe.MaxPageSize helped a lot; not sure what % of the data returned is coming out of cache now though.

The hard coded max page size of 512: https://github.com/lightninglabs/taproot-assets/blob/d70bccd2714a3f808e070a080c510cf396a11284/universe/interface.go#L38-L42

The ''populating root cache" you see comes from this section: https://github.com/lightninglabs/taproot-assets/blob/d70bccd2714a3f808e070a080c510cf396a11284/tapdb/multiverse.go#L713-L732
Are those the remote Universe sever's logs, or your own?
In that case, it tries to read the cache based on the query, but then falls back to reading from the DB to populate. Def agree we can increase the max page size here though, as with 100k+ assets, 512 roots at a time isn't much (needed for the full-full sync).

After digging a bit more, I think we need to rethink the root cache design. So the allRoots field which stores an LRU cache that maps a rootPageQuery to the response.
The mainnet universe has around 170k assets, we have a page size of 512, so that's ~335 queries to grab all the roots. The inner cache we have stores a mapping from rootPageQuery to the slice of roots, this has a max size of 50k. Therefore, during the course of a single request, we'll purge most of the cache, then end up with the last 50k items in the cache. The next client comes along, and then we do the same thing all over again.
Based on the above analysis, I think we should just re-design this portion of the cache entirely. If we just cached the entire set of roots, then it's ~26MB, which is pretty manageable (32+8+32+32+32+1)* 172000). We can then maintain the entire set of roots in memory, and use the RootNodesQuery struct to slice into that, storing the amounts by ID somewhere else (cheaper to read w/o it, as it adds extra joins). For reverse, we offset the index.
The final thing we need to resolve with this design sketch is how we handle invalidation. For non grouped assets, the root is effectively immutable. For grouped assets, each time we insert a new issuance proof, we may need to update it. Then we also need to factor in the transfer roots, which can change for all asset types with each new transfer.

The ''populating root cache" you see comes from this section:
https://github.com/lightninglabs/taproot-assets/blob/d70bccd2714a3f808e070a080c510cf396a11284/tapdb/multiverse.go#L713-L732
Are those the remote Universe sever's logs, or your own?

All the log snippets I posted were from my client.
I agree that just having all roots in memory makes sense; I think for invalidation, the DB queries to insert new data should already provide the ID that is also being used in the cache?
Rather, since we're using the same ID / integer for the DB and the query from the client, we should be able to query the DB for the entry representing the asset group, fetch the ID, and update only that entry.
Decoupling the page / request sizes for the RPC calls and the actual queries would also make sense IMO, but that would be less relevant if we're just keeping all roots in memory.

Logging at the original PR was useful to see all the 'touch points' for where the cache is actually populated, accessed, or invalidated:
https://github.com/lightninglabs/taproot-assets/pull/626/

During a recent deployment, the team observed that behavior where the universe would fill the cache again on each request. "cache eviction cycling"

Slice into slab

Guggero made progress on this today


DataTable useStaticWidth title/description style bug

will try to do a PR
edit: seems like this is an upstream issue and it will probably not get merged here if I "simply" fix it

they fixed it upstream 😄

not released yet, seems like they also have a pre-release version so it might take a while

Fixed in v0.44.3


Cursorpointer/title cursor pointer pritam mukherjee

i had made the signed off syntax although the ddco chek is failed please check it and also check the code i had changes and merge it under hacktoberfest 2023

@Pritam-2002 raising up the PR directly without raising out a prior issue into fitbody will not me merged .
Sorry but this is against the rules of Contributing into a project.

@abhay-raj19  #43 there is already a issue regarding this thats why  i made the pr

it was been already been raised up the @singhaman09


"npm run dev" fails on "Lazy Loading Modules" tutorial

"npm run dev" fails on "Lazy Loading Modules" tutorial
Example name
firebase-hn
Describe the bug
https://nextjs.org/learn/excel/lazy-loading-modules/setup
On the above page I tried running "npm run dev" and I get the following error:
`
ModuleNotFoundError: Module not found: Error: Can't resolve '@firebase/app' in '
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Go to https://nextjs.org/learn/excel/lazy-loading-modules/setup
Modify package.json to allow build to work (https://github.com/zeit/next.js/issues/5688)
Follow instruction on tutorial
See error

Expected behavior
I expect that when I execute "npm run dev" that the command will complete and the server will run.
System information

OS: Mac OS 10.14.3 (18D109)
Version of Next.js: [e.g. 6.0.2]

Additional context
Had to update firebase version to get npm install to work
https://github.com/zeit/next.js/issues/5688

Hi,
We are in the process of updating the examples.
To make that example work, first update the dependencies in package.json file to make sure all libraries are up to date:
  "dependencies": {
    "cross-env": "^5.2.0",
    "express": "^4.16.4",
    "firebase": "^5.8.6",
    "next": "^8.0.3",
    "react": "^16.8.4",
    "react-dom": "^16.8.4",
    "webpack-bundle-analyzer": "^3.1.0"
  }

Then in the lib/load-db.js file replace this line:
const firebase = require('firebase')

with:
  const firebase = require('firebase/app');
  require('firebase/database');

These changes made the example work correctly for me.


Use apostrophe

https://next.carbondesignsystem.com/libraries/carbon-components-angular

here too. Probably in all cases where there’s “Carbon’s”
https://next.carbondesignsystem.com/libraries/carbon-react

It’s also in the small text on the Libraries page

Here
https://next.carbondesignsystem.com/libraries/ibm-cloud-cognitive

tracking straight quote bugs in this #1378 design issue that will be globally resolved in #721


Changelog and update to 2.2.3

Current coverage is 92.99%

Merging #1261 into master will not affect coverage as of f510124

@@            master   #1261   diff @@
======================================
  Files           84      84
  Stmts         5265    5265
  Branches       956     956
  Methods          0       0
======================================
  Hit           4896    4896
  Partial         11      11
  Missed         358     358

Review entire Coverage Diff as of f510124

Powered by Codecov. Updated on successful CI builds.


Hyperparameter optimization 1: Using Grid Search to Optimize Hyperparameters

Proposed title of article
Machine Learning Hyperparameter Optimization 1: Using Grid Search to Optimize Hyperparameters
Introduction paragraph(s):
Unlike parameters, hyperparameters are set before training a machine learning model. These hyperparameters need to be optimized in order to adapt a model to a dataset. However, the optimal hyperparameter settings on one dataset are unlikely to be optimal on another. This makes the task of hyperparameter optimization that much trickier. This is the first of a series of articles where we dive deep into the key techniques to optimize hyperparameters.
Grid search refers to a technique used to identify the optimal hyperparameters for a model. Unlike parameters, finding hyperparameters in training data is unattainable. As such, to find the right hyperparameters, we create a model for each combination of hyperparameters. Grid search is thus considered a very traditional hyperparameter optimization method since we are basically “brute-forcing” all possible combinations. The models are then evaluated through cross-validation. The model boasting the best accuracy is naturally considered to be the best.
The example given below is a basic implementation of grid search. We simply first specify the hyperparameters we seek to examine. Then we provide a set of values to test. After this, grid search will attempt all possible hyperparameter combinations with the aid of cross-validation. Let’s break down this process into the steps below.
Key takeaways:
The reader should understand

The theory behind Grid Search
The role of cross-validation in hyperparameter optimization
The implementation of Grid Search through a simple step by step example

References:
https://scikit-learn.org/stable/modules/grid_search.html#grid-search
https://scikit-learn.org/stable/modules/generated/sklearn.model_selection.GridSearchCV.html
https://scikit-learn.org/stable/glossary.html
https://machinelearningmastery.com/hyperparameter-optimization-with-random-search-and-grid-search/
https://blog.usejournal.com/a-comparison-of-grid-search-and-randomized-search-using-scikit-learn-29823179bc85
https://medium.com/datadriveninvestor/an-introduction-to-grid-search-ff57adcc0998

Good topic @collins-a. However, please structure this as a standalone article (i.e. "Using Grid Search to Optimize Hyperparameters") vs. the first in a series of articles. We can't guarantee that all suggested future articles will be published. Thank you.


When processing the ABI, put array values into the memory_map

Problem
Currently when checking if a value is in an array, one checks the memory_map then one checks the MemArray. The only reason for it to be in the MemArray is if it was taken from the ABI.
Solution
We can avoid this edge case by loading values from the ABI into the memory_map
Alternatives considered

Additional context

This was fixed by @guipublic in #771


Rerun fails when using cucumber

When using cucumber framework, in a scenario of a failure in one of the steps, the rerun is not performed and I get an error regarding missing suite name:

@itayTipalti thanks for reporting. Can you provide a reproducible example?
Any contributions are appreciated.

@christian-bromann
I used the project which is generated using the npx tool. then I added the rerun service to the wdio.conf.js and after it I just added (like in the picture) a failure on purpose to activate the retry. I got an error doing so.

@christian-bromann
it doesn't work only in wdio7

There is a V6 version 1.6.x and a V7 version 1.7.2 (is latest)

@itayTipalti Can we close this?

yes, thanks @mikesalvia


Square brackets test pushes "blue" away from context start

The results of these tests are skewed by the insertion of tokens between red and blue. Not by the brackets themselves.
I have done tentative tests, with alternating [red],blue | blue, [red] | [[red]], blue | blue, [[red]] ...
and the tentative results are flat within error.
Until I (or you) can run a longer experiment, I would suggest adding a disclaimer to your findings.

Thanks for bringing this to my attention.
I've re-run the analysis with "red" at the end of prompt rather than the middle.
There does not seem to be a consistent effect.
Please confirm whether you agree with what I've written in the updated readme file.

Yes, I'd say that is agreeable.


tests: Adds an RTDS integration test for Envoy Mobile

This test does a simple verification that the RTDS protocol within the
xDS family is working correctly.  A subsequent PR will improve upon the
test coverage.
As part of this change, the common parts of running a Envoy Mobile
client integration test were refactored out into a new
BaseClientIntegrationTest class.  Both ClientIntegrationTest and
RtdsIntegrationTest inherit from BaseClientIntegrationTest.
NB: the parameterized test currently fails when using IPv6.  This will
be debugged and fixed in a subsequent PR.
Signed-off-by: Ali Beyad<EMAIL_ADDRESS>Risk Level: Low
Testing: Test only PR
Docs Changes: N/A
Release Notes: N/A

cc @alyssawilk since I can't seem to assign reviewers through the UI

/retest

This looks awesome. Other than one trivial nit, it LGTM.

Thanks for the review Ryan!

/retest

Looks good to me - nice cleanup of the tests. Thanks!

Thanks for the review Mike!


binder: primary key should by-default be non-null

This is my first pr to this repo 😁，If there are something i miss plz fell free to tell me.
close #632

cc @Shmiwy now the pk won't be nullable any more. I guess this would make things easier on storage layer.


Dev

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (12c3e8a) 77.24% compared to head (c59a43b) 81.16%.

Files
Patch %
Lines

lymph/models/unilateral.py
77.77%
4 Missing :warning:

lymph/models/bilateral.py
78.57%
3 Missing :warning:

lymph/diagnose_times.py
75.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #67      +/-   ##
==========================================
+ Coverage   77.24%   81.16%   +3.92%
==========================================
  Files           7        7
  Lines        1270     1285      +15
==========================================
+ Hits          981     1043      +62
+ Misses        289      242      -47

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Use Gatsby's gatsby-link

This is how I changed it. Feel free to just close this :)

@m-allanson This is still failing to build with a JSONStore error. Maybe we can do a quick mind-meld with @pieh and @kyleamathews to try and hunt down either what I did wrong (so we can document it and hopefully add an error message with links to a fix) or find the bug in V2 that's causing this.

(Also, thank you so much for submitting this. I should have led with that. I appreciate you.) 😄


MusicVAE: Add training hparams to configs, add hierarchical encoder configs, and update README.

I haven't changed max beta at all but I've used various numbers of free bits.  I'll address it one way or another when I make the checkpoints available.


Update SmartThings_IM6001-WLP01.md

Tried with my HA/ZHA - v2021.2.2 on Nortek/HubZ usb controller.  Reports leak, temp, battery.  Detected as Samjin device and working fine

thank you


Resiliparse does not Compile under Ubuntu 18

It seems like resiliparse does not compile under Ubuntu 18, it fails with this error message:
  building 'fastwarc.warc' extension
  creating build/temp.linux-x86_64-cpython-37
  creating build/temp.linux-x86_64-cpython-37/fastwarc
  gcc -pthread -B /opt/conda/compiler_compat -Wl,--sysroot=/ -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -fPIC -I/opt/conda/include/python3.7m -c fastwarc/warc.cpp -o build/temp.linux-x86_64-cpython-37/fastwarc/warc.o -std=c++17 -O3 -Wall -Wno-deprecated-declarations -Wno-unreachable-code -Wno-unused-function
  cc1plus: warning: command line option ‘-Wstrict-prototypes’ is valid for C/ObjC but not for C++
  fastwarc/warc.cpp:1348:3: error: ‘LZ4F_cctx’ does not name a type; did you mean ‘LZ4F_cctx_s’?
     LZ4F_cctx *cctx;
     ^~~~~~~~~
     LZ4F_cctx_s
  fastwarc/warc.cpp:1349:3: error: ‘LZ4F_dctx’ does not name a type; did you mean ‘LZ4F_dctx_s’?
     LZ4F_dctx *dctx;
     ^~~~~~~~~
     LZ4F_dctx_s
  error: command '/usr/bin/gcc' failed with exit code 1
  ----------------------------------------
  ERROR: Failed building wheel for fastwarc

It seems like the lz4 version that comes from the package repository in ubuntu 18 is in the wrong version?
When I install lz4 from source, it works:
git clone https://github.com/lz4/lz4
cd lz4
make
make install

Since installing lz4 from source resolves the problem, this might not have the highest priority.

You need to install liblz4-dev. If that doesn't work, then your LZ4 version is too old.

Yes, I installed liblz4-dev.
I just wanted to mention that the default version in ubuntu 18 does not work.


Conditional Test Hex Colours stopped working after version 5.4.0. it was working until 5.3.4

Conditional Text Hex Colours stopped working after version 5.4.0. it was working until 5.3.4
Hello Doug, A big Thanks for this EXCELLENT module. I would like to flag that before the hex colours used to work in versions 5.3.4, it stopped working after that.
Please see the code below:
` $batchname = 'Maintenance25'
$text2 = New-ConditionalText 'Completed' -ConditionalTextColor White -BackgroundColor '#00b359' # green back ground with white fonts. Worked in 5.3.4
$text1 = New-ConditionalText 'Failed' -ConditionalTextColor White -BackgroundColor '#FD625E' #red background with white fonts. Worked in 5.3.4
$paramExportExcel = @{
Path = ".$($batchname)_CutoverReport.xlsx"
Show = $false
AutoSize = $true
TableName = 'CutoverReport'
TableStyle = 'Light1'
FreezeTopRow = $true
BoldTopRow = $true
WorkSheetname = 'CutoverReport'
ConditionalText = $text1, $text2
IncludePivotTable = $true
PivotRows = 'Status'
PivotData = 'Status'
IncludePivotChart = $true
ChartType = 'PieExploded3D'
}
$results | Export-Excel @paramExportExcel # $results has some data`
Please see the Screenshot attached

Hey Rana,
I submitted a pull request for a fix on this. In the meantime you can convert your colours ahead of time using the cast as below:
$text2 = New-ConditionalText 'Completed' -ConditionalTextColor White -BackgroundColor ([System.Drawing.Color] '#00b359')
$text1 = New-ConditionalText 'Failed' -ConditionalTextColor White -BackgroundColor ([System.Drawing.Color] '#FD625E')

Kind regards,
Mitch

I made a change for compatibility with PS6 , but that meant you must pass a name, not a hex value. @miitchyy  has found a way to put back the support for Hex values without breaking PS6 compatibility. I've commented on the pull request, so have a look at that for more detail.

Hey Rana,
I submitted a pull request for a fix on this. In the meantime you can convert your colours ahead of time using the cast as below:
$text2 = New-ConditionalText 'Completed' -ConditionalTextColor White -BackgroundColor ([System.Drawing.Color] '#00b359')
$text1 = New-ConditionalText 'Failed' -ConditionalTextColor White -BackgroundColor ([System.Drawing.Color] '#FD625E')

Kind regards,
Mitch

Many Thanks :-)


Disambiguation based on PartialOrd between choices of a certain node type.

@eternaleye suggested that instead of having only "validators", that remove "invalid" choices from the SPPF, a more general approach involves PartialOrd, or more specifically, a function taking two Handle<X> and returning an Option<Ordering>, where disambiguation means "find the largest X".
When the ordering between two choices is equal, that means it's still ambiguous (i.e. the default for node types with no user-provided disambiguation logic), while None means neither choice is valid.
Validity can be embedded by mapping all possible pairs of validities to partial orderings:
impl<T: Validate> Disambiguate for T {
    fn disambiguate(a: Handle<Self>, b: Handle<Self>) -> Option<Ordering> {
        match (a.validate(), b.validate()) {
            (false, false) => None,
            (false, true) => Some(Ordering::Less),
            (true, false) => Some(Ordering::Greater),
            (true, true) => Some(Ordering::Equal),
        }
    }
}

I think you might have to project into a partial order from a relation that lacks transitivity, because I feel like a rock-paper-scissors relationship is likely. The ideal properties would be a (upper-)semilattice, which has the additional property that for any two elements x and y, there exists a z such that z > x and z > y. (So z is a l.u.b. of {x,y}.)
If the goal is just to select a likely parse rather than the most likely parse, there probably isn't any harm in extending the partial order to a total order if it's convenient to do so. But that's somehow unsatisfying, isn't it...
A copy+paste of my note to Eddy: I am interested to know how a probabilistic model would perform. So you have a set of parse trees and want to find the "correct"/intended parse tree. Ahead of time you gather statistics about how language structures relate to each other locally by analyzing, say, all of crates.io. Check each parse tree against the statistical model to find the most likely. What I'm describing is syntactic, but it could in principle include other attributes like type, scope, some complexity metric, proximity... And your notion of validators is complementary, not mutually exclusive. In ML we tend to just dump all the factors into one big bucket and study the principle components of the resulting space. We can then remove any factors that appear useless or project to a lower-dimensional space. But, I mean, that's something you'd do, if you do it at all, only after you have a framework to implement any of this.


Wavenet

It was mentioned in the paper "Our model resembles WaveNet (Oord et al., 2016a) in the use of tree-structured dilated convolutions. However, our principle-guided design has distinct skip-connection structures and filter sharing patterns, resulting in significantly better parameter efficiency and performance...Additionally, the link we establish between wavelets and tree-structured dilated causal convolutions offers the first principled justification for the effectiveness of WaveNet in modeling raw audio waveforms, an exemplary case of lengthy sequences with multiscale structure."
Do you have any ablations on the difference in performance in any specific tasks or tests? Also any specific audio samples? Overall very interesting paper!

Hi @pranavmalikk,
We did not include WaveNet results in the paper because we find it very difficult to have a fair setup. There are so many choices we need to make before we setup such a comparison:

First of all, WaveNet has no official open-source implementation and many details are unclear from the paper. Existing re-implementations all differ to some extent (in the way of initialization/bias/latent dimension choices), which one should we use?
WaveNet is originally developed for generation. Shall we modify it with a mean-pooling and then compare on the classification tasks in our paper?
WaveNet does not use mixing layers and normalization. Shall we keep those components and only replace MultiresLayer with a WaveNet block? Or do we want to compare the whole MultiresNet with a WaveNet? In each choice, how should we choose the hyper-parameters of WaveNet?

If you can be specific about these questions, I am happy to run an ablation and post the results here.


bug(autocomplete): Autocomplete menu inside sidenav doesn't respect parent placement

Reproduction

Expected Behavior
Autocomplete options should stick to it's parent element,
or should close the menu when scrolling.
Actual Behavior
It doesn't keep track when scrolling.
Environment

Angular:
CDK/Material: 10.1.3
Browser(s): Chrome 85.0.4183.83 - 64 bits
Operating System: Windows 10 (OS Build 19041.450)

Example: https://tdssoftware.github.io/query-view/clientes
Repo: https://github.com/TdsSoftware/query-view

Possible duplicate of #10079.
Possible solution to your problem: https://github.com/angular/components/issues/10079#issuecomment-619887760.

Yeah, you're right, closing it.


⚡ Remove ghost buttons on inventory page

💭 Introduction: The inventory page, with all the API endpoints has 4 buttons, namely 'first 50', 'previous 50', 'next 50', 'last 50'. The 'first 50' and 'last 50' buttons are hidden, but still accessible.
🎯 Requirements:

A basic understanding of vue.js

✅ Task summary: Remove the 'first 50' and 'last 50' buttons entirely. One check to keep in mind is that the same table component being used in many different places. Please ensure that the functionality of all other tables is not broken, due to this change.
🙋🏼♂ Questions:
If you have questions, need any help, or just want to hang out, make sure to join us on our Discord server.

Hi! I would like to work on this issue. Please assign this to me.

HI @akshatvirmani assigned this to you! Happy hackfesting 😃

sorry @akshatvirmani this issue is actually closed. can you pick another one?


chore(deps) bump lua-resty-openssl to 0.6.11

Summary
[0.6.11] - 2021-01-21
fix

aux/nginx: only show warning message when function is being called 9964a6d
openssl: not load ssl modules by default 390ad79
ssl: add function to free the verify callback function 62dc81a

[0.6.10] - 2021-01-12
feat

pkcs12: allow to define algorithm to encrypt key and cert b9678ce
pkcs12: check on cert and key mismatch 5953cc2
pkcs12: encode and decode for pkcs12 1467579
pkey: add is_private function to check if it's a private key eb6cc1c
ssl: add the ssl and ssl_ctx module 40f3999

fix

ecx: return nil, err in set_parameters 98acaee
pkey: use named_curve encoding for EC group 1e65d9d

CI seems to fail on flaky tests 🤔

CI seems to fail on flaky tests 🤔


Basic start of Broker Transition Solution Documentation

Basic start of Broker Transition Solution Documentation
Description
Basic start of Broker Transition Solution Documentation

Looks good, just need the translation to Norwegian.

Norwegian translated pages have now been added.


Ninja build of GEOSgcm breaks under Ninja

In trying out the Ninja build of GEOSgcm, the following error is emitted:
ninja: error: build.ninja:111198: multiple rules generate<EMAIL_ADDRESS>
I'll try and figure this out as I'm not sure what it's complaining about. I do not see it being generated more than once.

Could it be an I/O race condition?


Api gateway service retry wrapper

'TooManyRequestsException' sometimes seen when calling the APIGateway to deploy a complicated stack. Added an api-gateway-retry-wrapper utility that is used in place of the APIGateway to retry requests that fail with this exception.
Defaults:
max retries: 8,
min retry interval (milliseconds): 2000,
retry window (milliseconds): 5000
(so it retries up to 8 times at a random point between 2 and 7 seconds after each failure).

I'll merge this when I'm back. Chances are though that this will only push the issue. My best advice is to use DependsOn in your template to avoid creating too many resources at once. This will help for plenty of use cases though so it's a good update.
Would you mind checking the failures in Travis?


fix incorrect and broken links.

(1) fixed incorrect and broken links.
(2) removed some special characters in gl option.
(3) tweaked #114: replace semicolon with comma.
(4) added missing symbols.

@susiwen8 Please help me to review, thank you!

I think these are okay, no need to use websitePath. It will be handled correctly when switch the language.


[Minor?] Firestore Linq throw InvalidCastException: Specified cast is not valid.

Please fill in the following fields:
Unity editor version: 2018.4
Firebase Unity SDK version: 6.12
Firebase plugins in use (Auth, Database, etc.): FireStore
Please describe the issue here:
QuerySnapshot implement IEnumerable<DocumentSnapshot> so I expect that it could iterate with itself directly. But it just throw exception
QuerySnapshot query = await fireStoreQuery.GetSnapShotAsync();
var docs0 = query.Documents.ToArray(); // fine
var docs1 = query.ToArray(); // throw exception

So should firebase fix this exception or remove the IEnumerable interface from this class?
Please answer the following, if applicable:
What's the issue repro rate?
100%
InvalidCastException: Specified cast is not valid.
(wrapper castclass) System.Object.__castclass_with_cache(object,intptr,intptr)
Firebase.Firestore.QuerySnapshot.GetEnumerator () (at Z:/tmp/tmp.1TQduATzsL/firebase/firestore/client/unity/proxy/QuerySnapshot.cs:144)
Firebase.Firestore.QuerySnapshot.System.Collections.IEnumerable.GetEnumerator () (at Z:/tmp/tmp.1TQduATzsL/firebase/firestore/client/unity/proxy/QuerySnapshot.cs:149)
System.Linq.Enumerable+<OfTypeIterator>d__32`1[TResult].MoveNext () (at <fbb5ed17eb6e46c680000f8910ebb50c>:0)
System.Linq.Enumerable.TryGetFirst[TSource] (System.Collections.Generic.IEnumerable`1[T] source, System.Boolean& found) (at <fbb5ed17eb6e46c680000f8910ebb50c>:0)
System.Linq.Enumerable.FirstOrDefault[TSource] (System.Collections.Generic.IEnumerable`1[T] source) (at <fbb5ed17eb6e46c680000f8910ebb50c>:0)
FirebaseManager+<TestFireStore>d__6.MoveNext () (at

Thanks for pointing this out. This is supposed to work :-). We'll reproduce and get a fix into an upcoming release, though I can't promise it's going to be the next one.

Update: we have fixed the issue and hope it would be a part of the next release. Thanks for reporting it!

Reopening until the release with the fix goes out.

The fix for this issue was released in the 6.13.0 release.


Validation fails for optional TextValidator with min/max string lengths

Issue: When a TextValidator input is NOT required but has validation of minStringLength and maxStringLength, validation fails when field is left blank. Screenshots for clarity.
UI:

Console:

@BrittanyDufort Hi
Please check 1.0.0 version, issue should be fixed

closed due no activity


Error: OSError: Pypi lookup failed

Context
I tried to deploy model in Amazon Lambda. But there's an error while deploying my model with packages. This is log:
Calling update for stage dev..
Creating zappa-permissions policy on yolov3-gun-detec-dev-ZappaLambdaExecutionRole IAM Role.
C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\myenv\lib\site-packages_distutils_hack_init_.py:33: UserWarning: Setuptools is replacing distutils.
warnings.warn("Setuptools is replacing distutils.")
Downloading and installing dependencies..

markupsafe==2.1.2: Using locally cached manylinux wheel
pillow==9.4.0: Using locally cached manylinux wheel
pyyaml==5.4.1: Using locally cached manylinux wheel
charset-normalizer==3.0.1: Using locally cached manylinux wheel
numpy==1.24.2: Using locally cached manylinux wheel
opencv-python==<IP_ADDRESS>: Using locally cached manylinux wheel
Packaging project as gzipped tarball.
ERROR: To modify pip, please run the following command:
C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\myenv\Scripts\python.exe -m pip install --quiet --target C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\handler_venv\Lib\site-packages wheel==0.38.4 placebo==0.9.0 boto3==1.26.64 cfn-flip==1.3.0 PyYAML==5.4.1 argcomplete==1.9.3 zappa==0.56.1 click==8.1.3 requests==2.28.2 s3transfer==0.6.0 certifi==2022.12.7 urllib3==1.26.14 toml==0.10.2 jmespath==0.9.3 Werkzeug==2.2.2 tqdm==4.19.1 kappa==0.6.0 Unidecode==1.3.6 idna==3.4 python-slugify==1.2.4 colorama==0.4.4 botocore==1.29.65 pip==23.0 hjson==3.0.1 troposphere==4.3.0 durationpy==0.5 python-dateutil==2.6.1 MarkupSafe==2.1.2 six==1.16.0 charset-normalizer==3.0.1 setuptools
Oh no! An error occurred! :(

==============
Traceback (most recent call last):
File "C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\myenv\lib\site-packages\zappa\cli.py", line 3044, in handle
sys.exit(cli.handle())
File "C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\myenv\lib\site-packages\zappa\cli.py", line 519, in handle
self.dispatch_command(self.command, stage)
File "C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\myenv\lib\site-packages\zappa\cli.py", line 572, in dispatch_command
self.update(
File "C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\myenv\lib\site-packages\zappa\cli.py", line 980, in update
self.create_package()
File "C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\myenv\lib\site-packages\zappa\cli.py", line 2434, in create_package
venv=self.zappa.create_handler_venv(use_zappa_release=use_zappa_release),
File "C:\Users\fazyl\Desktop\Yolov3_Gun_Detector\myenv\lib\site-packages\zappa\core.py", line 502, in create_handler_venv
raise EnvironmentError("Pypi lookup failed")
OSError: Pypi lookup failed

In forums said that it possibly can be problem of versions of pip-tools, but in later versions of zappa it doesn't included.

Expected Behavior

My Flask app needs to be deployed and packages installed.
Actual Behavior

It gives error of packages problem.
Possible Fix

Steps to Reproduce

Your Environment
Zappa version used: 0.56.1
Operating System and Python version: 3.9
The output of  "pip freeze":
argcomplete==1.9.3
aws-configure==2.1.8
awscli==1.27.65
boto3==1.26.64
botocore==1.29.65
certifi==2022.12.7
cfn-flip==1.3.0
charset-normalizer==3.0.1
click==8.1.3
colorama==0.4.4
docutils==0.16
durationpy==0.5
Flask==2.2.2
future==0.16.0
hjson==3.0.1
idna==3.4
importlib-metadata==6.0.0
itsdangerous==2.1.2
Jinja2==3.1.2
jmespath==0.9.3
kappa==0.6.0
lambda-packages==0.20.0
MarkupSafe==2.1.2
numpy==1.24.2
opencv-python==<IP_ADDRESS>
pep517==0.13.0
Pillow==9.4.0
pip-tools==6.1.0
placebo==0.9.0
pyasn1==0.4.8
python-dateutil==2.6.1
python-slugify==1.2.4
PyYAML==5.4.1
requests==2.28.2
rsa==4.7.2
s3transfer==0.6.0
six==1.16.0
text-unidecode==1.3
toml==0.10.2
tomli==2.0.1
tqdm==4.19.1
troposphere==4.3.0
Unidecode==1.3.6
urllib3==1.26.14
Werkzeug==2.2.2
wsgi-request-logger==0.4.6
zappa==0.56.1
zipp==3.12.1

Zappa version used:
Operating System and Python version:
The output of pip freeze:
Link to your project (optional):
Your zappa_settings.json:

Any update? same error...

I am having the same problem too. One thing I realized is that if I set  "slim_handler" to false or just don't define it in my zappa_settings.json the error goes away, but then there comes a problem of the project being too large, which I do not know how to fix either.

Pypi lookup failed is a general error.  This can occur when your dependencies can't be resolved, or pypi is not reachable.
I think we can add more error info, so it's easier to debug the issue.

Any solutions yet? Im having the same problem

I used python 3.8. It has worked for me somehow.


Feat/database structure

LGTM.
Requesting @riodeuno review for entity explorer related changes
and @mohanarpit for further db related testing


Unable to compile

With Microsoft Visual Studio 2019, I get the following compile errors:
Error	CS1514	{ expected	GameSpeedUnlockMod	C:\Users\David\Downloads\GameSpeedUnlockMod-main\GameSpeedUnlockMod\Mod.cs	5	Active
Error	CS1513	} expected	GameSpeedUnlockMod	C:\Users\David\Downloads\GameSpeedUnlockMod-main\GameSpeedUnlockMod\Mod.cs	12	Active
Error	CS1617	Invalid option '10' for /langversion. Use '/langversion:?' to list supported values.	GameSpeedUnlockMod	C:\Users\David\Downloads\GameSpeedUnlockMod-main\GameSpeedUnlockMod\CSC	1	Active

Is there any specific Visual Studio version required?

You may need the .NET 6 SDK to have C# 10 support.
I'm not using VS to build it.


Heightfield issue:  Make sure they are ordered CCW around the normal, using the right hand rule.

Hello,
I give a try to CANNON.Heightfield but I meet an issue during step(). I can see the javascript console log below in red, I suspect this message below is important. Issue seen on Cannon.js 0.6.0 (git extract from a couple of days).
.faceNormals[1] = Vec3(0,0,-1) looks like it points into the shape? The vertices follow. Make sure they are ordered CCW around the normal, using the right hand rule. (23:54:00:901 | error)
at ConvexPolyhedron.computeNormals (www/js/libs/cannon.js:7125:21)
at Heightfield.getConvexTrianglePillar (www/js/libs/cannon.js:8437:12)
at Narrowphase.(anonymous function).Narrowphase.convexHeightfield (www/js/libs/cannon.js:10590:21)
at Narrowphase.(anonymous function).Narrowphase.boxHeightfield (www/js/libs/cannon.js:10525:10)
at Narrowphase.getContacts (www/js/libs/cannon.js:9439:34)
at World.internalStep (www/js/libs/cannon.js:11243:22)
at World.step (www/js/libs/cannon.js:11088:14)
at xxx (www/js/main.js:178:17)
.vertices[5] = Vec3(-0.25,0.75,5.5) (23:54:00:902 | warning)
at www/js/libs/cannon.js:7127
.vertices[4] = Vec3(0.75,-0.25,5.5) (23:54:00:903 | warning)
at www/js/libs/cannon.js:7127
.vertices[3] = Vec3(-0.25,-0.25,5.5) (23:54:00:903 | warning)
at www/js/libs/cannon.js:7127
Right, it seems (-0.25,0.75,5.5) (0.75,-0.25,5.5) (-0.25,-0.25,5.5) are not in CCW order (right handed).  Please find my (simplified) code below:
var grid_size = 10;
var matrix = new Array(2*grid_size);
for( var i=0; i<2*grid_size; i++)
{
    matrix[i] = new Array(2*grid_size);
    for( var j=0; j<2*grid_size; j++ )
    {
        matrix[i][j] =  i - j;
    }
}

var hfShape = new CANNON.Heightfield(matrix, { elementSize:1 });
var hfBody = new CANNON.Body({mass: 0});
hfBody.addShape(hfShape);

The issue disappears if I guarantee Y heights are smaller (fix code: matrix[i][j] =  i - j - 10;)

Has this been resolved I am still having this issue.

If this issue comes with any other cannon body then check scale value of body. for me when it was negative bcoz the object in blender was in -ve x, y &z. which caused the issue. I fixed by setting scale value to positive


Backport-299552-to-release-23.11

(cherry picked from commit 810348fab3a624a36ea9c1f46751cc4ca41cad7e)
Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Sorry, for the ping, cherry-picked, but VS code selected all these commits for some reason when creating the PR.


exp/services/recoverysigner: add sign endpoint

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[ ] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[ ] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Add account list endpoint that returns a list of accounts the authenticate user has access to.
Why
A user will need to be able to ask a recovery signer server what accounts are stored that it is allowed to recover. A user will use this endpoint to discover what accounts it has.
Merging
This PR should be merged to master after #2267 and contains changes from that PR that will disappear from this PR when that PR is merged. I'll move this PR out of draft state after that PR is merged.
Known limitations
N/A

👀 in 5 mins. Taking a short break

Nothing it too concerning except this comment regarding the json format we use. (This, however, applies to all the endpoints.).

Do you think we should ping the frontend team about the snake_case vs CamelCase?

@marcelosalloum Good call, I'll talk to them about it today.


facemesh canonical face model and uv visualization

Looks like the face mesh model in the new mediapipe solution has been updated. e.g. There were 468 landmarks before, and now there is 478.
I would be interested to get the canonical face model as well as a uv visualization map. The old data can be found here: https://github.com/google/mediapipe/tree/master/mediapipe/modules/face_geometry/data
But I couldn't find corresponding materials for the new version. Can you provide those? Thanks a lot.

Any updates on this?
Thanks

Is there anybody who knows that? If you have any information about that reply pls. Also is there any way to get 3D points from the new model? Thanks.

Hi guys, I found something which I want to share. You know Mediapipe released a new face mesh model which provides a face transformation matrix. This matrix includes a rotation matrix and a translation vector. That means if we know intrinsic parameters(it can be obtained with https://docs.opencv.org/4.x/dc/dbb/tutorial_py_calibration.html) and transformation matrix we can find 3D points for each point on the face mesh with the reprojection method. Am I right?
If you have any information about that please reply

I figured the landmarks are the same as the old model. The 10 extra landmarks are for the iris (newly added)
Not sure they are using the same canonical face model or not. Hope that someone can confirm.