Request: Example on how to send data to template configuration through an automation

Is your feature request related to a problem? Please describe.
Reading through the README.md I am unable to understand how I am supposed to populate the template in an automated way.
The README.md currently contains the following example:

For wifi access with template
Name: My wifi access
Content: WIFI:T:WPA2;S:MyNetworkName;P:{{states("input_text.wlan_password")}};H:true;

but the README.md does not describe how {{states("input_text.wlan_password")}} is supposed to be sent to the integration to achieve the dynamic update of the QR Code.
Describe the solution you'd like
I would like an example, showing an automation in Home Assistant that update the QR Code image by sending new data to its template .

The QR code updates automatically when the value of the template changes. That means to change the content you have to change the value of input_text.wlan_password with an automation, as soon as the value is changed the QR code changes too.
Example:
description: "Example"
mode: single
trigger: []
condition: []
action:
  - service: input_text.set_value
    data:
      value: New Value
    target:
      entity_id: input_text.wlan_password

I will add a note in the README.md to clarify this.


How do we migrate settings for OCIO configs?

Since the OCIO config settings point to files in the installation directory, how do we update them when releasing new versions?

This isn't an issue for releases since they install to the same directory, but this can happen when switching between development versions and releases. In that case it's probably fine to just reset the settings.


Support refine/ZodEffects in useFormInputProps

Passing a ZodEffects (output of using refine) into useFormInputProps will result in inputProps function that cannot find any of your keys.
I believe the problem is here where it is assuming there is a schema.shape when there may actually be a schema._def.schema.shape:
https://github.com/kiliman/remix-params-helper/blob/e7e2c24f340622bce8a2ef8f61ee76bbe8281196/src/helper.ts#L185
Current work around:
  const realSchema = schema instanceof ZodEffects ? schema._def.schema : schema;
  const inputProps = useFormInputProps(realSchema);

Thanks. Yeah, the internal Zod schema can get very complex. Since I don't use every feature of Zod, I'll handle edge cases like this as they come up.

@conform-to/react with @conform-to/zod supports more complex zod schemas, but that packages feels a bit complex for what I'm doing. I really like the simplicity of useFormInputProps, but I also need refine.

Yes, remix-params-helper was meant as a simple interface, so it only supported features that I actually used and not everything that zod can do.
See #32 for more info.


CATALOG_VERSION is now CHANNEL-[md5sum of catalog-manifests contents]

Fixes https://github.com/openshift/osd-operators-registry/issues/7

/hold

/lgtm

/lgtm


Update molecular interaction data (STRING DB)

External public data relating to molecular interactions will be updated and made available in this release. Molecular interaction data, such as direct physical and indirect functional associations, will be updated by integrating the latest STRING database.
#390

10/14 update: Maulik will modify PPI scripts to bring in data from STRING DB.  On target for November Release, per Maulik.

#390

Per the Semi-Annual Report, we will compare existing PATRIC PPIs and functionality to STRING DB

11/18: Maulik will look into what STRING DB does next week and come up with summary recommendations.

11/23: Maulik has not yet had a chance to look.

12/2: Not in for November

available on production.


Disable help content test for Microsoft.Powershell.Archive module

The published help content filename is missing '.psm1', but the help still
works. The bug is in PlatyPS and needs to be fixed to re-enable this test.

@Francisco-Gamino Please have a look.

Thanks @adityapatwardhan . Could you please add a work item to enable this later? Other than that, LGTM.


Feat: deterministic generation

The structs themselves were made deterministic in the previous MR. Fields were still generated in an arbitrary location within the struct.
This PR sorts the props before recursing through the fields which results in an identical result for each generation.
Closes #35

Looks good to me, the deterministic generation goes a bit over my head.

Given the same input you should expect the same output every time.


Changed loops order in from_fn_generic

Hi!
First, thank you for your librairies, they are great!
After investigating the performances of the code from a friend on the forum, I realized that the from_fn function was quite slow due to the fact that matrices are stored by columns, but the iteration is done by rows.
I also added a benchmark to see the performance improvements:
Original version:
test core::matrix::mat100_from_fn :     7,736 ns/iter (+/- 246)
test core::matrix::mat500_from_fn : 1,085,050 ns/iter (+/- 192,820)

This PR version:
test core::matrix::mat100_from_fn:   2,796 ns/iter (+/- 189)
test core::matrix::mat500_from_fn: 650,736 ns/iter (+/- 16,264)

Good catch. Thanks!


Name releases to the AppStore consistent

Current Implementation

The final release often have numbers like 1.15.1 or 1.14.3, even if it's the first version, wich schould mean it's .0.
Suggested Enhancement

Name the releases in a consistent way.
Expected Benefits

Some (older) people get confused by every small inconsistency, and think, that there device has a bug. I don't know, why they are named so inconsistent, but if it's not hard to change it, i would prefer changing it to consisting numbers.

I think this inconsistency is caused by the following:
If the version (for example version 2.0) is submitted to the App Store for review & the App Store review team finds bugs, etc. or the development team finds bugs they have to bump the version to a .minor (for example 2.0.1) version when they fix the bug.
If then in the next review round another mistakes comes up they have to increase the version number again (to for example version 2.0.2).
I hardly believe that anyone gets confused by this, since other apps (take a look at WhatsApp) sometimes even have .patch versions up to 90 or higher.
The versioning of CWA is also explained here: https://github.com/corona-warn-app/cwa-documentation/blob/master/cwa-versioning.md

The differnce between WhatsApp is, I think, that at WhatsApp it's obvious, that the logic there is not to just increment one part of the number.

@jucktnich
Yeah, idk, maybe WhatsApp wasn't the best example 😀
But so or so I think this is really nothing that could be changed for the reasons I explained above (but if you want to release a version with known bugs because you don't want to fix them because you want a "clean" version number 😉)

I don't think that's better, I just thought if there was no reason, it would be worth it to change (I know people wich got confused, but better a clean version and confused people as vice versa)

Totally agree with you that this should be avoided if there's no reason @jucktnich!
If you consider this as technically not feasible I suggest to close this issue.


Adding footer in FAQs page

I think it will be better if we add the footer section in the FAQs page too
Please do assign this issue to me. @soham0005

@nksmanya you can work on it, do reach out if you have any doubts
Happy Coding!

hey @soham0005 could you assign me this issue as i see its not attempted.

@nksmanya Any updates?

I am working on it.
I will soon let you know.

I have a trouble in opening the FAQs page...
The page is not opening for me. It is just keep on loading.
I have been trying for 3 to 4 days!

@nksmanya the bug is solved, you can add footer


Attempting to add Perl interface to Apache CI.

@lxn2 @mli
Hello there,
I've added perl tests to the Jenkinsfile however the CI does not picking them up, could you please see if anything else is needed to trigger the tests ?
Thanks in advance.

Hi @sergeykolychev sorry for the delay. The reason the CI wasn't picking it up is because the default action is for it to pick up the Jenkinsfile from the branch, and not from your PR. It's a pain point Jenkinsfile developers are going through. One thing we might be able to do is merge your code into a different (new) branch in order to test your changes. If it looks good, we make a pull request from that branch to the master branch.
@mli thoughts?

@lxn2 Anything else you need from me before this is mergeable ?

@lxn2 @mli I think we can just merge it and in the case it fails somehow I'll submit a fix.

@lxn2 @mli @domdivakaruni
Guys, I'd really appreciate some attention to this pull; inability to see current state of the perl api caused me to miss this issue for example: https://github.com/apache/incubator-mxnet/issues/7080

@lxn2 is it possible to re-enable travis test after mxnet is successfully migrated to apache? Otherwise many cpp/perl tests are not run at all

@sergeykolychev can you fix the conflicts?

@lxn2 the branch is fully up to date.

I still cannot rebase due to conflicts....

@lxn2 which conflicts,
It says:
This branch has no conflicts with the base branch
Only those with write access to this repository can merge pull requests.


Fully qualify WP_Filesystem

small backslash, big 🐛
@Kubitomakita

Hmm on which PHP version is it failing?
I'm going to add the test matrix to check as well

On reading with my eyes version :)
The cause is namespace Micropackage\Filesystem;

You may use @phpstan to detect countless problems in the code.
/**
 * @method bool chown( string $file, string|int $owner, bool $recursive = false )
 */

Adding magic methods helps static analysis.

Well, in general, I'd agree, but it's not failing in this case :)
Just pushed new test action and tested from PHP 5.6 up to 7.4: https://github.com/micropackage/filesystem/actions/runs/36284024
I have used this package already in one project and works fine as well.

I see!
That is not a class instantiation but a call to a global function.
The casing misled me.


Solution needed to this HackerRank problem

A simple solution with a brief explanation of the logic for this problem:  Drawing book

Hi @hannasalam  can i work on this issue .

Sure,
This issue is open to all.(multiple solutions in different languages are welcome)

Hi @hannasalam  please assign me this issue I have solved it.

Hi I would like to give the solution in python

Please assign to me . i will solve in Javascript

@raikiran07 @parth93QA @Manoj-Suru @sumitmohite0501 This issue is open for all. You can contribute. Make sure the follow the contribution guidelines. And you can contribute questions other than this also to the repo.

Hi @hannasalam  . I created a pull request to resolve this issue .


Adding an error 404 page

Adding an custom error-404 page
when someone visits a random page on UMatter they are redirected to a default error 404 page.
like this :

I would like to contribute as a GSSOC contributor by adding a custom error 404 page with better ui for a user to navigate out of there or to find the page that they were looking for.

kindly assign me this issue

@him-raw99 u r assigned....go ahead :)

hi, you just merged my PR I think you should close this issue now

thanks for the opportunity @Mansi168

it is closed :)
good luck !


symbolic languages like Chinese, Korean and Japanese needs to to be update

symbolic languages like Chinese, Korean and Japanese needs to to be update because the old fonts are not used much anymore and there's some new character too

I'm interested in the Japanese and Chinese models. I have only done small scale training in the past (years ago) for Japanese to use locally and testing. Are there any good resources on how I can improve the models with additional fonts?
And for example, what to look at during the training?


add function of temperature in the GCEED part.

This PR enables to treat function of temperature in the GCEED part. To use the function, please modify input files as follows.

&system
  iperiodic = 0
  al = 16d0, 16d0, 16d0
-  nstate = 5
+  nstate = 10
  nelem = 2
  natom = 4
  nelec = 10
+  temperature_k = 300.d0
/

@tt-ims san, could you check this PR?

Same PR is given on #357. So I remove this one.


Refined Storage controllers breaking randomly (even if chunkloaded)

Issue description:
What happens: Placing a RS controller in the end and in the overworld causes one or both to randomly just break. Even if both are chunkloaded.
What you expected to happen: Them to not break after being placed.
Steps to reproduce:

Create RS system in overworld, chunkload, also set up a wireless receiver, transmitter, network card, and interdimensional upgrade.
Create RS system in the end, chunkload, wireless receiver, transmitter, network card, and interdimensional upgrade.
Link everything up as you would to get it all working.
Wait at least a couple mins and the controller will have broken.

This only happens when you link a network card to a network receiver in the over world, then you take that card and stick it in a wireless transmitter in the end with a dimensional upgrade.
...
Version (make sure you are on the latest version before reporting):

Minecraft: 1.12.2
Forge: 2555
Refined Storage: 1.5.30

Does this issue occur on a server? [yes/no] SP world
If a (crash)log is relevant for this issue, link it here: None
[pastebin/gist/etc link here]

Uehlbran never explained the "feature" that causes this. Could someone please explain?

Ok, if anyone else has this problem, the trick is thus: the controller is breaking cause the network can only have one controller. The receiver is supposed to receive power from the transmitter and does not need an independent power source or controller.

I still don't understand the issue... mine keeps breaking i am so confused on this


What is the reason LD_PRELOAD=libtcmalloc.so is no longer used?

What is the reason LD_PRELOAD=libtcmalloc.so is no longer used?

Google blocked it to force users to use HIGH-RAM runtime shape, they are still playing their little dishonest games

Google blocked it to force users to use HIGH-RAM runtime shape, they are still playing their little dishonest games

can i use the preinstalled libtcmalloc.so.4? what's the difference?

https://github.com/googlecolab/colabtools/issues/3858
maybe it's a compatibility issue between the old tcmalloc build and the new glibc in the upgraded runtime.

googlecolab/colabtools#3858 maybe it's a compatibility issue between the old tcmalloc build and the new glibc in the upgraded runtime.

it's weird that they still haven't addressed the issue of inexplicable high RAM usage when loading SD, fixing libtcmalloc was the community way to overcome that issue, and now that can't be done.

googlecolab/colabtools#3858 maybe it's a compatibility issue between the old tcmalloc build and the new glibc in the upgraded runtime.
more info: see https://bugzilla.redhat.com/show_bug.cgi?id=1569391 google-perftools_2.5-2.2ubuntu3_all.deb is very old. the missing hook was added in 2.6.2

I backported the fix to gperftools 2.5 and recompiled it and it seems to work in the new runtime. anyone interested can give a try:
%cd /content/
!gdown 1-4-h0HsJfAS9wz96qlGQIeul3uHHs2xm && rm -rf gperftools;tar zxvf gperftools_2.5.1.tar.gz
%env LD_PRELOAD=/content/gperftools/libs/libtcmalloc_minimal.so

use it at your own risk!
(note: gperftools >= 2.6.2 works too. but it doesn't control memory usage well. so patching 2.5 is the best way i know of at the moment. If you have any better suggestions/solutions, please let me know.)

googlecolab/colabtools#3858 maybe it's a compatibility issue between the old tcmalloc build and the new glibc in the upgraded runtime.
more info: see https://bugzilla.redhat.com/show_bug.cgi?id=1569391 google-perftools_2.5-2.2ubuntu3_all.deb is very old. the missing hook was added in 2.6.2

I backported the fix to gperftools 2.5 and recompiled it and it seems to work in the new runtime. anyone interested can give a try:
%cd /content/
!gdown 1-4-h0HsJfAS9wz96qlGQIeul3uHHs2xm && rm -rf gperftools;tar zxvf gperftools_2.5.1.tar.gz
%env LD_PRELOAD=/content/gperftools/libs/libtcmalloc_minimal.so

use it at your own risk!
(note: gperftools >= 2.6.2 works too. but it doesn't control memory usage well. so patching 2.5 is the best way i know of at the moment. If you have any better suggestions/solutions, please let me know.)

great work!

googlecolab/colabtools#3858 maybe it's a compatibility issue between the old tcmalloc build and the new glibc in the upgraded runtime.
more info: see https://bugzilla.redhat.com/show_bug.cgi?id=1569391 google-perftools_2.5-2.2ubuntu3_all.deb is very old. the missing hook was added in 2.6.2

I backported the fix to gperftools 2.5 and recompiled it and it seems to work in the new runtime. anyone interested can give a try:
%cd /content/
!gdown 1-4-h0HsJfAS9wz96qlGQIeul3uHHs2xm && rm -rf gperftools;tar zxvf gperftools_2.5.1.tar.gz
%env LD_PRELOAD=/content/gperftools/libs/libtcmalloc_minimal.so

use it at your own risk!
(note: gperftools >= 2.6.2 works too. but it doesn't control memory usage well. so patching 2.5 is the best way i know of at the moment. If you have any better suggestions/solutions, please let me know.)

great work!, can you please elaborate the procedure so I can try to do it in-notebook (for security reasons)

@TheLastBen are you implementing this into an update or pr soon?

googlecolab/colabtools#3858 maybe it's a compatibility issue between the old tcmalloc build and the new glibc in the upgraded runtime.
more info: see https://bugzilla.redhat.com/show_bug.cgi?id=1569391 google-perftools_2.5-2.2ubuntu3_all.deb is very old. the missing hook was added in 2.6.2

I backported the fix to gperftools 2.5 and recompiled it and it seems to work in the new runtime. anyone interested can give a try:
%cd /content/
!gdown 1-4-h0HsJfAS9wz96qlGQIeul3uHHs2xm && rm -rf gperftools;tar zxvf gperftools_2.5.1.tar.gz
%env LD_PRELOAD=/content/gperftools/libs/libtcmalloc_minimal.so

use it at your own risk!
(note: gperftools >= 2.6.2 works too. but it doesn't control memory usage well. so patching 2.5 is the best way i know of at the moment. If you have any better suggestions/solutions, please let me know.)

great work!, can you please elaborate the procedure so I can try to do it in-notebook (for security reasons)

sure. the patch for 2.5:
`%%writefile /content/1.patch
diff --git a/Makefile.am b/Makefile.am
index f18bf4f..10cc9d6 100755
--- a/Makefile.am
+++ b/Makefile.am
@@ -102,6 +102,7 @@ if HAVE_OBJCOPY_WEAKEN
WEAKEN = $(OBJCOPY) -W malloc -W free -W realloc -W calloc -W cfree
-W memalign -W posix_memalign -W valloc -W pvalloc
-W malloc_stats -W mallopt -W mallinfo \

    -W aligned_alloc \
    -W _Znwm -W _ZnwmRKSt9nothrow_t -W _Znam -W _ZnamRKSt9nothrow_t \
    -W _ZdlPv -W _ZdaPv \
    -W __Znwm -W __ZnwmRKSt9nothrow_t -W __Znam -W __ZnamRKSt9nothrow_t \

diff --git a/src/libc_override_gcc_and_weak.h b/src/libc_override_gcc_and_weak.h
index ecb66ec..1f19e01 100644
--- a/src/libc_override_gcc_and_weak.h
+++ b/src/libc_override_gcc_and_weak.h
@@ -143,6 +143,7 @@ extern "C" {
void* calloc(size_t n, size_t size) __THROW     ALIAS(tc_calloc);
void cfree(void* ptr) __THROW                   ALIAS(tc_cfree);
void* memalign(size_t align, size_t s) __THROW  ALIAS(tc_memalign);

void* aligned_alloc(size_t align, size_t s) __THROW ALIAS(tc_memalign);
void* valloc(size_t size) __THROW               ALIAS(tc_valloc);
void* pvalloc(size_t size) __THROW              ALIAS(tc_pvalloc);
int posix_memalign(void** r, size_t a, size_t s) __THROW
diff --git a/src/libc_override_redefine.h b/src/libc_override_redefine.h
index 72679ef..89ad584 100644
--- a/src/libc_override_redefine.h
+++ b/src/libc_override_redefine.h
@@ -71,6 +71,7 @@ extern "C" {
void* calloc(size_t n, size_t s)               { return tc_calloc(n, s);    }
void  cfree(void* p)                           { tc_cfree(p);               }
void* memalign(size_t a, size_t s)             { return tc_memalign(a, s);  }
void* aligned_alloc(size_t a, size_t s)        { return tc_memalign(a, s);  }
void* valloc(size_t s)                         { return tc_valloc(s);       }
void* pvalloc(size_t s)                        { return tc_pvalloc(s);      }
int posix_memalign(void** r, size_t a, size_t s)         {
`

apply the patch and build:
%cd /content !rm -rf gperftools; wget https://github.com/gperftools/gperftools/releases/download/gperftools-2.5/gperftools-2.5.tar.gz && tar zxf gperftools-2.5.tar.gz && mv gperftools-2.5 gperftools !apt install -qq libunwind8-dev %cd /content/gperftools !patch -p1 < /content/1.patch !./configure --enable-minimal --enable-libunwind --enable-frame-pointers --enable-dynamic-sized-delete-support --enable-sized-delete --enable-emergency-malloc --enable-aggressive-decommit-by-default; make !mkdir -p libs && cp -a .libs/libtcmalloc*.so* libs

googlecolab/colabtools#3858 maybe it's a compatibility issue between the old tcmalloc build and the new glibc in the upgraded runtime.
more info: see https://bugzilla.redhat.com/show_bug.cgi?id=1569391 google-perftools_2.5-2.2ubuntu3_all.deb is very old. the missing hook was added in 2.6.2

I backported the fix to gperftools 2.5 and recompiled it and it seems to work in the new runtime. anyone interested can give a try:
%cd /content/
!gdown 1-4-h0HsJfAS9wz96qlGQIeul3uHHs2xm && rm -rf gperftools;tar zxvf gperftools_2.5.1.tar.gz
%env LD_PRELOAD=/content/gperftools/libs/libtcmalloc_minimal.so

use it at your own risk!
(note: gperftools >= 2.6.2 works too. but it doesn't control memory usage well. so patching 2.5 is the best way i know of at the moment. If you have any better suggestions/solutions, please let me know.)

great work!, can you please elaborate the procedure so I can try to do it in-notebook (for security reasons)

sure. put the patch for 2.5 in one cell:
%%writefile /content/1.patch
diff --git a/Makefile.am b/Makefile.am
index f18bf4f..10cc9d6 100755
--- a/Makefile.am
+++ b/Makefile.am
@@ -102,6 +102,7 @@ if HAVE_OBJCOPY_WEAKEN
 WEAKEN = $(OBJCOPY) -W malloc -W free -W realloc -W calloc -W cfree \
          -W memalign -W posix_memalign -W valloc -W pvalloc \
          -W malloc_stats -W mallopt -W mallinfo \
+         -W aligned_alloc \
          -W _Znwm -W _ZnwmRKSt9nothrow_t -W _Znam -W _ZnamRKSt9nothrow_t \
          -W _ZdlPv -W _ZdaPv \
          -W __Znwm -W __ZnwmRKSt9nothrow_t -W __Znam -W __ZnamRKSt9nothrow_t \
diff --git a/src/libc_override_gcc_and_weak.h b/src/libc_override_gcc_and_weak.h
index ecb66ec..1f19e01 100644
--- a/src/libc_override_gcc_and_weak.h
+++ b/src/libc_override_gcc_and_weak.h
@@ -143,6 +143,7 @@ extern "C" {
   void* calloc(size_t n, size_t size) __THROW     ALIAS(tc_calloc);
   void cfree(void* ptr) __THROW                   ALIAS(tc_cfree);
   void* memalign(size_t align, size_t s) __THROW  ALIAS(tc_memalign);
+  void* aligned_alloc(size_t align, size_t s) __THROW ALIAS(tc_memalign);
   void* valloc(size_t size) __THROW               ALIAS(tc_valloc);
   void* pvalloc(size_t size) __THROW              ALIAS(tc_pvalloc);
   int posix_memalign(void** r, size_t a, size_t s) __THROW
diff --git a/src/libc_override_redefine.h b/src/libc_override_redefine.h
index 72679ef..89ad584 100644
--- a/src/libc_override_redefine.h
+++ b/src/libc_override_redefine.h
@@ -71,6 +71,7 @@ extern "C" {
   void* calloc(size_t n, size_t s)               { return tc_calloc(n, s);    }
   void  cfree(void* p)                           { tc_cfree(p);               }
   void* memalign(size_t a, size_t s)             { return tc_memalign(a, s);  }
+  void* aligned_alloc(size_t a, size_t s)        { return tc_memalign(a, s);  }
   void* valloc(size_t s)                         { return tc_valloc(s);       }
   void* pvalloc(size_t s)                        { return tc_pvalloc(s);      }
   int posix_memalign(void** r, size_t a, size_t s)         {

in another cell, apply the patch and build:
%cd /content
!rm -rf gperftools; wget https://github.com/gperftools/gperftools/releases/download/gperftools-2.5/gperftools-2.5.tar.gz && tar zxf gperftools-2.5.tar.gz && mv gperftools-2.5 gperftools
!apt install -qq libunwind8-dev
%cd /content/gperftools
!patch -p1 < /content/1.patch
!./configure --enable-minimal --enable-libunwind --enable-frame-pointers --enable-dynamic-sized-delete-support --enable-sized-delete --enable-emergency-malloc --enable-aggressive-decommit-by-default; make
!mkdir -p libs && cp -a .libs/libtcmalloc*.so* libs

Can you check it ?
it's throwing error.

@TheLastBen are you implementing this into an update or pr soon?

it has been implemented

googlecolab/colabtools#3858 maybe it's a compatibility issue between the old tcmalloc build and the new glibc in the upgraded runtime.
more info: see https://bugzilla.redhat.com/show_bug.cgi?id=1569391 google-perftools_2.5-2.2ubuntu3_all.deb is very old. the missing hook was added in 2.6.2

I backported the fix to gperftools 2.5 and recompiled it and it seems to work in the new runtime. anyone interested can give a try:
%cd /content/
!gdown 1-4-h0HsJfAS9wz96qlGQIeul3uHHs2xm && rm -rf gperftools;tar zxvf gperftools_2.5.1.tar.gz
%env LD_PRELOAD=/content/gperftools/libs/libtcmalloc_minimal.so

use it at your own risk!
(note: gperftools >= 2.6.2 works too. but it doesn't control memory usage well. so patching 2.5 is the best way i know of at the moment. If you have any better suggestions/solutions, please let me know.)

great work!, can you please elaborate the procedure so I can try to do it in-notebook (for security reasons)

sure. put the patch for 2.5 in one cell:
%%writefile /content/1.patch
diff --git a/Makefile.am b/Makefile.am
index f18bf4f..10cc9d6 100755
--- a/Makefile.am
+++ b/Makefile.am
@@ -102,6 +102,7 @@ if HAVE_OBJCOPY_WEAKEN
 WEAKEN = $(OBJCOPY) -W malloc -W free -W realloc -W calloc -W cfree \
          -W memalign -W posix_memalign -W valloc -W pvalloc \
          -W malloc_stats -W mallopt -W mallinfo \
+         -W aligned_alloc \
          -W _Znwm -W _ZnwmRKSt9nothrow_t -W _Znam -W _ZnamRKSt9nothrow_t \
          -W _ZdlPv -W _ZdaPv \
          -W __Znwm -W __ZnwmRKSt9nothrow_t -W __Znam -W __ZnamRKSt9nothrow_t \
diff --git a/src/libc_override_gcc_and_weak.h b/src/libc_override_gcc_and_weak.h
index ecb66ec..1f19e01 100644
--- a/src/libc_override_gcc_and_weak.h
+++ b/src/libc_override_gcc_and_weak.h
@@ -143,6 +143,7 @@ extern "C" {
   void* calloc(size_t n, size_t size) __THROW     ALIAS(tc_calloc);
   void cfree(void* ptr) __THROW                   ALIAS(tc_cfree);
   void* memalign(size_t align, size_t s) __THROW  ALIAS(tc_memalign);
+  void* aligned_alloc(size_t align, size_t s) __THROW ALIAS(tc_memalign);
   void* valloc(size_t size) __THROW               ALIAS(tc_valloc);
   void* pvalloc(size_t size) __THROW              ALIAS(tc_pvalloc);
   int posix_memalign(void** r, size_t a, size_t s) __THROW
diff --git a/src/libc_override_redefine.h b/src/libc_override_redefine.h
index 72679ef..89ad584 100644
--- a/src/libc_override_redefine.h
+++ b/src/libc_override_redefine.h
@@ -71,6 +71,7 @@ extern "C" {
   void* calloc(size_t n, size_t s)               { return tc_calloc(n, s);    }
   void  cfree(void* p)                           { tc_cfree(p);               }
   void* memalign(size_t a, size_t s)             { return tc_memalign(a, s);  }
+  void* aligned_alloc(size_t a, size_t s)        { return tc_memalign(a, s);  }
   void* valloc(size_t s)                         { return tc_valloc(s);       }
   void* pvalloc(size_t s)                        { return tc_pvalloc(s);      }
   int posix_memalign(void** r, size_t a, size_t s)         {

in another cell, apply the patch and build:
%cd /content
!rm -rf gperftools; wget https://github.com/gperftools/gperftools/releases/download/gperftools-2.5/gperftools-2.5.tar.gz && tar zxf gperftools-2.5.tar.gz && mv gperftools-2.5 gperftools
!apt install -qq libunwind8-dev
%cd /content/gperftools
!patch -p1 < /content/1.patch
!./configure --enable-minimal --enable-libunwind --enable-frame-pointers --enable-dynamic-sized-delete-support --enable-sized-delete --enable-emergency-malloc --enable-aggressive-decommit-by-default; make
!mkdir -p libs && cp -a .libs/libtcmalloc*.so* libs

Can you check it ? it's throwing error.

looks like you need to switch to the fallback runtime (check https://github.com/googlecolab/colabtools/issues/3778) to compile it, then save the compiled .so to your gdrive/somewhere else, and redownload the compiled .so in your new runtime to use it


What if I create a my-own dataset?

Hello, I reread your paper, and I'd like to try deploying your model in my work. But I need to create a domain dataset. So what should I prepare for the dataset?

Hi,
We have not created the dataset for the task. We have used that standard dataset. You could refer respective paper of the dataset in the section (4.1 Dataset) of the paper.


Upgrade to 0.7.0-Beta

Description
<Just!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
Just upgraded to Ver 0.7.0-Beta
Got this error on startup:-
Lnd has unexpectedly quit!
Error code:
1
Error signal:
Unknown
Error message:
Unknown
Expected Behavior
Zap wallet to start normally.
Actual Behavior
Zap wallet failed to start.
Possible Fix

Steps to Reproduce

Context

Your Environment

Zap version: 0.7.0-Beta
Operating System and version: windows 10

Hi, can you tell me what version of Zap you were upgrading from please? Thanks. Also, if you quit and restart the app do you get the same problem? Thanks

Hi!
Yes - Upgraded from the previous version 0.6.2-Beta and I still get the same message when I quit and restart the app.

Interesting. Well, this error is coming directly from lnd (which was upgraded from 0.8 to 0.10 in this release). My first thought is that lnd's upgrade process didn't fully complete for some reason though I've not seen it happen before.
Can you try downloading 0.6.2 again and see if that still runs?

Going back to ver 0.6.2-Beta gives this error  -
Lnd has unexpectedly quit!
Error code:
1
Error signal:
Unknown
Error message:
Unable to open channeldb: channel db cannot revert to prior version

Re-installed 0.7.0 and still getting the same fail message.

Could you update to 0.7.0 again, start zap, and then review your lnd logs which you can find at %APPDATA%\Zap\lnd\bitcoin\mainnet\wallet-1\logs\bitcoin\mainnet\lnd.log (wallet-1 may vary depending on how many wallets you have created).

OK - This is the latest log entry -
2020-07-11 23:10:05.545 [INF] CNCT: ChannelArbitrator(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): starting state=StateDefault, trigger=chainTrigger, triggerHeight=638831
2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): new block (height=638831) examining active HTLC's
2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): checking commit chain actions at height=638831, in_htlc_count=0, out_htlc_count=0
2020-07-11 23:10:05.545 [DBG] CNCT: Starting ChannelArbitrator(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0), htlc_set=(map[contractcourt.HtlcSetKey]contractcourt.htlcSet) (len=2) {
(contractcourt.HtlcSetKey) LocalHtlcSet: (contractcourt.htlcSet) {
incomingHTLCs: (map[uint64]channeldb.HTLC) {
},
outgoingHTLCs: (map[uint64]channeldb.HTLC) {
}
},
(contractcourt.HtlcSetKey) RemoteHtlcSet: (contractcourt.htlcSet) {
incomingHTLCs: (map[uint64]channeldb.HTLC) {
},
outgoingHTLCs: (map[uint64]channeldb.HTLC) {
}
}
}
2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): new block (height=638831) examining active HTLC's
2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): checking commit chain actions at height=638831, in_htlc_count=0, out_htlc_count=0
2020-07-11 23:10:05.545 [DBG] BTCN: Sending getdata (witness block<PHONE_NUMBER>000000000f446237471c4dae978f1a50bd95604f0078d78dfb838a) to <IP_ADDRESS>:8333 (outbound)
2020-07-11 23:10:05.545 [INF] CNCT: ChannelArbitrator(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): starting state=StateDefault, trigger=chainTrigger, triggerHeight=638831
2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): new block (height=638831) examining active HTLC's
2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): checking commit chain actions at height=638831, in_htlc_count=0, out_htlc_count=0
2020-07-11 23:10:05.545 [INF] DISC: Authenticated Gossiper is starting
2020-07-11 23:10:05.545 [INF] BRAR: Starting contract observer, watching for breaches.
2020-07-11 23:10:05.545 [DBG] DISC: Requesting online notification for peer=023692c62d1da4bcb34a5b611520101f7047e0376124556dd72c16fd3d7870c0b2
2020-07-11 23:10:05.545 [INF] NTFN: New block epoch subscription
2020-07-11 23:10:05.545 [INF] CRTR: Examining channel graph for zombie channels
2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): new block (height=638831) examining active HTLC's
2020-07-11 23:10:05.545 [DBG] CNCT: ChannelArbitrator(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): checking commit chain actions at height=638831, in_htlc_count=0, out_htlc_count=0
2020-07-11 23:10:05.545 [DBG] DISC: Skipping retransmission of channel without AuthProof:<PHONE_NUMBER>25434880
2020-07-11 23:10:05.599 [DBG] RPCS: [ListPayments]
2020-07-11 23:10:05.600 [DBG] RPCS: [listpeers] yielded [] peers
2020-07-11 23:10:05.697 [DBG] RPCS: [ListPayments]
2020-07-11 23:10:05.697 [DBG] RPCS: [ListPayments]
2020-07-11 23:10:05.697 [DBG] RPCS: [pendingchannels]
2020-07-11 23:10:05.697 [DBG] RPCS: [ListPayments]
2020-07-11 23:10:05.698 [DBG] RPCS: [walletbalance] Total balance=0.00021323 BTC (confirmed=0.00021323 BTC, unconfirmed=0 BTC)
2020-07-11 23:10:05.698 [DBG] RPCS: [channelbalance] balance=0.00007849 BTC pending-open=0 BTC
2020-07-11 23:10:05.699 [DBG] RPCS: [listchannels] fetched 2 channels from DB
2020-07-11 23:10:05.795 [DBG] CHDB: ChanUpdatesInHorizon hit percentage: 0.000000 (0/11366)
2020-07-11 23:10:05.797 [DBG] CRTR: ChannelID(636264289390034945) is a zombie, collecting to prune
2020-07-11 23:10:05.798 [DBG] CRTR: ChannelID(697133253116166145) is a zombie, collecting to prune
2020-07-11 23:10:05.798 [DBG] CRTR: ChannelID(697159641292865536) is a zombie, collecting to prune
2020-07-11 23:10:05.798 [DBG] CRTR: ChannelID(679111158015787009) is a zombie, collecting to prune
2020-07-11 23:10:05.799 [INF] CRTR: Pruning 4 zombie channels
2020-07-11 23:10:05.820 [DBG] INVC: Adding 0 pending invoices to the expiry watcher
2020-07-11 23:10:05.820 [INF] INVC: New invoice subscription client: id=0
2020-07-11 23:10:05.821 [DBG] LNWL: ChannelPoint(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): starting local commitment: (*lnwallet.commitment)(0xc0037b6000)({
height: (uint64) 140,
isOurs: (bool) true,
ourMessageIndex: (uint64) 20,
theirMessageIndex: (uint64) 120,
ourHtlcIndex: (uint64) 0,
theirHtlcIndex: (uint64) 20,
txn: (*wire.MsgTx)(0xc002426680)({
Version: (int32) 2,
TxIn: ([]*wire.TxIn) (len=1 cap=1) {
(*wire.TxIn)(0xc002a2c720)({
PreviousOutPoint: (wire.OutPoint) d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0,
SignatureScript: ([]uint8) {
},
Witness: (wire.TxWitness) ,
Sequence: (uint32)<PHONE_NUMBER>
})
},
TxOut: ([]*wire.TxOut) (len=1 cap=1) {
(*wire.TxOut)(0xc00244edc0)({
Value: (int64) 18469,
PkScript: ([]uint8) (len=22 cap=22) {
00000000  00 14 58 b8 56 b9 86 e7  84 3f ba 52 49 53 fc 97  |..X.V....?.RIS..|
00000010  79 76 d2 1e 97 3b                                 |yv...;|
}
})
},
LockTime: (uint32) 538404438
}),
sig: ([]uint8) (len=71 cap=71) {
00000000  30 45 02 21 00 a7 bc 6a  2e 84 37 82 a9 64 14 d8  |0E.!...j..7..d..|
00000010  da d4 6f 86 61 55 2c 12  86 00 57 7a bc e1 4d c0  |..o.aU,...Wz..M.|
00000020  4f fd d1 eb df 02 20 71  71 3c 29 a8 7b c8 a3 ca  |O..... qq<).{...|
00000030  77 90 53 53 ae 17 b0 61  01 13 62 1e 6d 40 3b af  |w.SS...a..b.m@;.|
00000040  d4 43 00 a2 cf c4 60                              |.C....`|
},
ourBalance: (lnwire.MilliSatoshi) 0 mSAT,
theirBalance: (lnwire.MilliSatoshi) 18469000 mSAT,
fee: (btcutil.Amount) 0.00006531 BTC,
feePerKw: (chainfee.SatPerKWeight) 9021 sat/kw,
dustLimit: (btcutil.Amount) 0.00000573 BTC,
outgoingHTLCs: ([]lnwallet.PaymentDescriptor) ,
incomingHTLCs: ([]lnwallet.PaymentDescriptor) ,
outgoingHTLCIndex: (map[int32]*lnwallet.PaymentDescriptor) ,
incomingHTLCIndex: (map[int32]*lnwallet.PaymentDescriptor)
})
2020-07-11 23:10:05.821 [DBG] LNWL: ChannelPoint(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): starting local commitment: (*lnwallet.commitment)(0xc0039c0000)({
height: (uint64) 15,
isOurs: (bool) true,
ourMessageIndex: (uint64) 8,
theirMessageIndex: (uint64) 7,
ourHtlcIndex: (uint64) 4,
theirHtlcIndex: (uint64) 3,
txn: (*wire.MsgTx)(0xc0024267c0)({
Version: (int32) 2,
TxIn: ([]*wire.TxIn) (len=1 cap=1) {
(*wire.TxIn)(0xc002a2c840)({
PreviousOutPoint: (wire.OutPoint) d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0,
SignatureScript: ([]uint8) {
},
Witness: (wire.TxWitness) ,
Sequence: (uint32)<PHONE_NUMBER>
})
},
TxOut: ([]*wire.TxOut) (len=2 cap=2) {
(*wire.TxOut)(0xc002426800)({
Value: (int64) 4803,
PkScript: ([]uint8) (len=22 cap=22) {
00000000  00 14 1e b6 bb a7 ec 30  04 77 2e ca bf 0b 94 97  |.......0.w......|
00000010  8b 1f ec b4 16 e2                                 |......|
}
}),
(*wire.TxOut)(0xc002426820)({
Value: (int64) 7849,
PkScript: ([]uint8) (len=34 cap=34) {
00000000  00 20 2a bc 69 db cc 2c  b2 d2 70 52 b0 c9 d8 89  |. *.i..,..pR....|
00000010  4d dd 03 1b 05 6d 8a 12  9f cd 82 fd ef 7d 84 36  |M....m.......}.6|
00000020  69 92                                             |i.|
}
})
},
LockTime: (uint32) 538077644
}),
sig: ([]uint8) (len=71 cap=71) {
00000000  30 45 02 21 00 c5 46 ac  02 5b 63 30 27 11 8e d9  |0E.!..F..[c0'...|
00000010  5d 4b ac 64 3a 0c 2f 26  d9 40 05 14 35 2d 7a 8f<EMAIL_ADDRESS>00000020  8f 8b c4 a4 eb 02 20 23  21 2e 8e d0 c5 d0 3b c1  |...... #!.....;.|
00000030  12 47 de 6a 4b 43 8f 15  71 6f f7 82 96 97 b2 93  |.G.jKC..qo......|
00000040  3e 44 24 59 d5 87 f9                              |>D$Y...|
},
ourBalance: (lnwire.MilliSatoshi) 7849995 mSAT,
theirBalance: (lnwire.MilliSatoshi) 4803005 mSAT,
fee: (btcutil.Amount) 0.00007347 BTC,
feePerKw: (chainfee.SatPerKWeight) 10149 sat/kw,
dustLimit: (btcutil.Amount) 0.00000573 BTC,
outgoingHTLCs: ([]lnwallet.PaymentDescriptor) ,
incomingHTLCs: ([]lnwallet.PaymentDescriptor) ,
outgoingHTLCIndex: (map[int32]*lnwallet.PaymentDescriptor) ,
incomingHTLCIndex: (map[int32]*lnwallet.PaymentDescriptor)
})
2020-07-11 23:10:05.822 [INF] CHFT: Adding 2 channels to event store
2020-07-11 23:10:05.822 [INF] CHBU: Starting chanbackup.SubSwapper
2020-07-11 23:10:05.823 [DBG] LNWL: ChannelPoint(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): starting remote commitment: (*lnwallet.commitment)(0xc0039c00c0)({
height: (uint64) 140,
isOurs: (bool) false,
ourMessageIndex: (uint64) 20,
theirMessageIndex: (uint64) 120,
ourHtlcIndex: (uint64) 0,
theirHtlcIndex: (uint64) 20,
txn: (*wire.MsgTx)(0xc0024266c0)({
Version: (int32) 2,
TxIn: ([]*wire.TxIn) (len=1 cap=1) {
(*wire.TxIn)(0xc002a2c780)({
PreviousOutPoint: (wire.OutPoint) d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0,
SignatureScript: ([]uint8) {
},
Witness: (wire.TxWitness) ,
Sequence: (uint32)<PHONE_NUMBER>
})
},
TxOut: ([]*wire.TxOut) (len=1 cap=1) {
(*wire.TxOut)(0xc00244ee00)({
Value: (int64) 18469,
PkScript: ([]uint8) (len=34 cap=34) {
00000000  00 20 fc 67 28 12 49 43  2b 25 3f b5 19 fe 85 a2  |. .g(.IC+%?.....|
00000010  cf 2f f2 4a 55 64 b1 e1  89 ed c6 4e 82 04 63 4e  |./.JUd.....N..cN|
00000020  20 19                                             | .|
}
})
},
LockTime: (uint32) 538404438
}),
sig: ([]uint8) {
},
ourBalance: (lnwire.MilliSatoshi) 0 mSAT,
theirBalance: (lnwire.MilliSatoshi) 18469000 mSAT,
fee: (btcutil.Amount) 0.00006531 BTC,
feePerKw: (chainfee.SatPerKWeight) 9021 sat/kw,
dustLimit: (btcutil.Amount) 0.00000573 BTC,
outgoingHTLCs: ([]lnwallet.PaymentDescriptor) ,
incomingHTLCs: ([]lnwallet.PaymentDescriptor) ,
outgoingHTLCIndex: (map[int32]*lnwallet.PaymentDescriptor) ,
incomingHTLCIndex: (map[int32]*lnwallet.PaymentDescriptor)
})
2020-07-11 23:10:05.823 [DBG] LNWL: ChannelPoint(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0): Restoring 0 dangling remote updates
2020-07-11 23:10:05.823 [DBG] LNWL: ChannelPoint(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): starting remote commitment: (*lnwallet.commitment)(0xc001e96a80)({
height: (uint64) 15,
isOurs: (bool) false,
ourMessageIndex: (uint64) 8,
theirMessageIndex: (uint64) 7,
ourHtlcIndex: (uint64) 4,
theirHtlcIndex: (uint64) 3,
txn: (*wire.MsgTx)(0xc002426840)({
Version: (int32) 2,
TxIn: ([]*wire.TxIn) (len=1 cap=1) {
(*wire.TxIn)(0xc002a2c8a0)({
PreviousOutPoint: (wire.OutPoint) d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0,
SignatureScript: ([]uint8) {
},
Witness: (wire.TxWitness) ,
Sequence: (uint32)<PHONE_NUMBER>
})
},
TxOut: ([]*wire.TxOut) (len=2 cap=2) {
(*wire.TxOut)(0xc002426880)({
Value: (int64) 4803,
PkScript: ([]uint8) (len=34 cap=34) {
00000000  00 20 33 76 be 66 60 e6  5c d3 a1 6a e0 0d 06 b5  |. 3v.f`...j....|
00000010  cb 02 46 57 d9 d1 d4 7c  47 8d 34 6b bc e7 9e 6e  |..FW...|G.4k...n|
00000020  5f 0c                                             |_.|
}
}),
(*wire.TxOut)(0xc0024268a0)({
Value: (int64) 7849,
PkScript: ([]uint8) (len=22 cap=22) {
00000000  00 14 f8 37 9f b9 d7 8e  66 75 13 c4 81 c2 ba b7  |...7....fu......|
00000010  e3 11 aa 91 21 6f                                 |....!o|
}
})
},
LockTime: (uint32) 538077644
}),
sig: ([]uint8) {
},
ourBalance: (lnwire.MilliSatoshi) 7849995 mSAT,
theirBalance: (lnwire.MilliSatoshi) 4803005 mSAT,
fee: (btcutil.Amount) 0.00007347 BTC,
feePerKw: (chainfee.SatPerKWeight) 10149 sat/kw,
dustLimit: (btcutil.Amount) 0.00000573 BTC,
outgoingHTLCs: ([]lnwallet.PaymentDescriptor) ,
incomingHTLCs: ([]lnwallet.PaymentDescriptor) ,
outgoingHTLCIndex: (map[int32]*lnwallet.PaymentDescriptor) ,
incomingHTLCIndex: (map[int32]*lnwallet.PaymentDescriptor)
})
2020-07-11 23:10:05.823 [DBG] FNDG: ChannelPoint(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0) with chan_id=aeaff2ae6b6fcfc20e57df9ef2ef67f39939ad6ac5b7a83af3f8d1823137e3d2 not found in opening database, assuming already announced to the network
2020-07-11 23:10:05.823 [DBG] LNWL: ChannelPoint(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0): Restoring 0 dangling remote updates
2020-07-11 23:10:05.824 [DBG] FNDG: ChannelPoint(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0) with chan_id=cc05c273a6586925d67c199709cf1fca1a8fcdd08a7bc774024325ec01573dd1 not found in opening database, assuming already announced to the network
2020-07-11 23:10:05.826 [WRN] CHBU: Replacing disk backup for ChannelPoint(d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0) w/ newer version
2020-07-11 23:10:05.826 [WRN] CHBU: Replacing disk backup for ChannelPoint(d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0) w/ newer version
2020-07-11 23:10:05.828 [INF] CHBU: Updating backup file at C:\Users\mariu\AppData\Roaming\Zap\lnd\bitcoin\mainnet\wallet-1\data\chain\bitcoin\mainnet\channel.backup
2020-07-11 23:10:05.830 [INF] CHBU: Swapping old multi backup file from C:\Users\mariu\AppData\Roaming\Zap\lnd\bitcoin\mainnet\wallet-1\data\chain\bitcoin\mainnet\temp-dont-use.backup to C:\Users\mariu\AppData\Roaming\Zap\lnd\bitcoin\mainnet\wallet-1\data\chain\bitcoin\mainnet\channel.backup
2020-07-11 23:10:05.831 [ERR] LTND: Unable to start server: unable to refresh backup file: unable to update multi backup: rename C:\Users\mariu\AppData\Roaming\Zap\lnd\bitcoin\mainnet\wallet-1\data\chain\bitcoin\mainnet\temp-dont-use.backup C:\Users\mariu\AppData\Roaming\Zap\lnd\bitcoin\mainnet\wallet-1\data\chain\bitcoin\mainnet\channel.backup: Access is denied.
2020-07-11 23:10:05.831 [INF] RPCS: Stopping RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping ChainRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping VersionRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping WatchtowerClientRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping SignRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping AutopilotRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping WalletKitRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping WatchtowerRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping RouterRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] RPCS: Stopping InvoicesRPC Sub-RPC Server
2020-07-11 23:10:05.831 [INF] INVC: Cancelling invoice subscription for client=0
2020-07-11 23:10:05.832 [DBG] BTCN: Received block (hash<PHONE_NUMBER>000000000f446237471c4dae978f1a50bd95604f0078d78dfb838a, ver 545259520, 2632 tx, 2020-07-11 21:52:11 +0100 BST) from <IP_ADDRESS>:8333 (outbound)
2020-07-11 23:10:05.832 [INF] BTCN: Canceling block subscription: id=1
2020-07-11 23:10:05.832 [DBG] BTCN: Error finding spends for d13d5701ec25430274c77b8ad0cd8f1aca1fcf0997197cd6256958a673c205cc:0: neutrino shutting down
2020-07-11 23:10:05.832 [ERR] NTFN: Failed getting UTXO: neutrino shutting down
2020-07-11 23:10:05.832 [DBG] BTCN: Error finding spends for d2e3373182d1f8f33aa8b7c56aad3999f367eff29edf570ec2cf6f6baef2afae:0: neutrino shutting down
2020-07-11 23:10:05.832 [ERR] NTFN: Failed getting UTXO: neutrino shutting down
2020-07-11 23:10:05.866 [ERR] BTCN: utxo scan failed: neutrino shutting down
2020-07-11 23:10:05.883 [DBG] BTCN: Stopping block notifications subscription manager
2020-07-11 23:10:05.883 [ERR] LNWL: Neutrino rescan ended with error: rescan block subscription was canceled
2020-07-11 23:10:05.883 [INF] BTCN: Block manager shutting down
2020-07-11 23:10:05.934 [INF] BTCN: Address manager shutting down
2020-07-11 23:10:06.258 [INF] LTND: Shutdown complete

Hmm, I thought that Windows file locking problem was fixed in lnd.
C:\Users\mariu\AppData\Roaming\Zap\lnd\bitcoin\mainnet\wallet-1\data\chain\bitcoin\mainnet\channel.backup: Access is denied.

What Windows file locking problem are you referring to? I've not heard of this before. I'm not so familiar with Windows but from the logs it looks like a file permissions issue. Can you check the permissions on that file and ensure that it is readable by lnd?
It sounds related to this recent lnd change https://github.com/lightningnetwork/lnd/pull/4379

I seem to remember Lightning Labs Lightning App having a similar issue.
https://github.com/lightninglabs/lightning-app

Any fix or workaround for this issue yet?

To me this sounds like either a file permissions on your machine, or a bug in lnd.
Did you check the file permissions?
You could try moving that channel.backup file out of the way and restarting the app. I think that will cause lnd to recreate the channel backup file though I'm not certain about that. You might want to ask in the lnd slack.

I was running ver 0.6.2 with no problem. I didn't change any permissions on my system (why would I?). I just upgraded to ver 0.7.0 and I got this error.
What file permissions do I need to check and where do I find the channel backup file so I can move it?

The path to the file that lnd is having trouble reading is detailed in your error message:

C:\Users\mariu\AppData\Roaming\Zap\lnd\bitcoin\mainnet\wallet-1\data\chain\bitcoin\mainnet\channel.backup

OK - found it and moved it.
My zap wallet started up fine.
Do I need to put the backup file back to the original location?
Will I need to do this every time I upgrade to a new version?

Great!

Do I need to put the backup file back to the original location?

After moving the file and starting up lnd again I expect lnd will have recreated the file for you. Can you check if the file has been recreated at its original location?

Will I need to do this every time I upgrade to a new version?

It's unlikely. I've actually never seen a case of this needing to be done. I think it relates to the change in lnd that I referenced earlier in this thread.

Yes - the backup file has been recreated.
OK - no worries - but if I get the same problem on a future update, I will know what to do.
Thanks for your help.

Good stuff. Thanks for confirming.

Fix in LND merged.
https://github.com/lightningnetwork/lnd/pull/4456


Dump chr9 from K562 is empty

Hi, I am trying to download chr9 from K562 but I am getting an empty file.  I already downloaded other chromosomes and I didn't get any error, only with this one.
My command  was:
java -jar juicer_tools.jar dump observed KR https://hicfiles.s3.amazonaws.com/hiseq/k562/in-situ/combined.hic 9 9 BP 10000 K562_chr9_norm_KR.txt

Please ask on the forum and we’ll respond there. This is not a Juicebox
bug.
aidenlab.org/forum.html
On Wed, May 2, 2018 at 12:56 PM Luciagrmz<EMAIL_ADDRESS>wrote:

Hi, I am trying to download chr9 from K562 but I am getting an empty file.
I already downloaded other chromosomes and I didn't get any error, only
with this one.
My command was:
java -jar juicer_tools.jar dump observed KR
https://hicfiles.s3.amazonaws.com/hiseq/k562/in-situ/combined.hic 9 9 BP
10000 K562_chr9_norm_KR.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/theaidenlab/Juicebox/issues/730, or mute the thread
https://github.com/notifications/unsubscribe-auth/ABWiW8couZlVUQF7BWpdx3keQHZidvERks5tueU2gaJpZM4Tvz7R
.

--
Neva Cherniavsky Durand, Ph.D.
Staff Scientist, Aiden Lab
www.aidenlab.org


Intune Company Portal as SSO broker on macOS

Is this statement still current?
"The SSO through authentication broker isn't available on macOS."
https://learn.microsoft.com/en-us/azure/active-directory/develop/apple-sso-plugin

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

ID: 465a721b-4702-fd4c-953e-cc6fde14de5e
Version Independent ID: 7a16f182-99dc-a125-0b42-e1185e533667
Content: Configure SSO on macOS and iOS - Microsoft Entra
Content Source: articles/active-directory/develop/single-sign-on-macos-ios.md
Service: active-directory
Sub-service: develop
GitHub Login: @henrymbuguakiarie
Microsoft Alias: henrymbugua

@pmeuser
Thanks for your feedback! We will investigate and update as appropriate.

@pmeuser
I'm going to assign this to the document author so they can take a look at it accordingly
@henrymbuguakiarie
Could you Please review this and update as appropriate.

Hello @pmeuser,
Thank you for your feedback.
I have updated the doc to fix the issue, as the statement in question is not current.


[BUG] customHandler for errors is not working as expected

Describe the bug
Not really sure if a bug or suggestion but here it goes.
According to the docs one can specify a custom error handler in the config to extend the functionality of error handling.
In my case, the responses of my API need to be formatted in a very specific way, so, the base error handler for when (in example) a bearer token is required but not provided, is insufficient.
I thought this was the case covered by the customHandler for errors, but now I see it's not working. If I get a SecurityError, I don't have any control over how the response looks
To Reproduce
Steps to reproduce the behavior:

Set up an API endpoint that has a BearerAuth security specified
Configure a customHandler for errors in the config
Call the endpoint without specifying any auth header
The customHandler is not called, and instead a generic response is thrown

Expected behavior
The customHandler should be called overriding any generic response

Merged into the develop branch, will be available in the next release.

Was this released?


Restructure the links of the week to make them easier to maintain in the IDE

Closes #250
First was going to add an extra method to return the correct file path, but found out if could simply be solved by providing the full path in the Links ID

I highly recommend not changing the ID.

Are you sure? I don't see a direct link to the links using the ID, in the tweets I'm always linking to https://www.jfx-central.com/home

Ah, you are right. The LOTW are an exception in this respect. All other entries can be referenced directly via their ID, e.g.: https://www.jfx-central.com/library/flexganttfx where flexganttfx would be the ID used in libraries.json. OK, then I guess we are fine there.


[Core] Enable Memory Tiering for vLLM

This is the following PR of #7697. This PR introduces 3 major functionalities:

Context Caching with TTL support is also a huge drive for memory demand.
Blockwise swapping for DRAM and Disk (Partially)
Layered transfer between DRAM and HBM.
Initial Disk Support

Some detailed explanations:

Context caching:
a. Usage:
We add CachingParams  to specify the TTL of the context caching. Within TTL we guarantee that the Context Caching will remain in the instance (won't be discarded)
Example usage of offline inference:

caching_params = CachingParams(ttl=args.ttl)
cache_output = llm.caching(LONG_PROMPT, caching_params=caching_params)

Example usage of online serving (a new endpoint is added: v1/caching):
 url += "/v1/caching"
 payload["ttl"] = ttl

and send the payload to the URL
b. Implementation:
The scheduler.schedule() checks and frees the expired context caching
LLMEngine._process_model_outputs() moves the context caching requests to SequenceStatues.FIXED, which won't be freed within TTL

Blockwise swapping for DRAM and Disk (partially)
Usage:
Add --enable-memory-tiering flag

Implementation:
Prefix matching is changed in 2 places: 1. can_allocate() now considers the prefix matching to calculate the necessary new blocks 2. In prefilling, we check whether the block resides in DRAM or Disk if so we fetch them in
Block allocation is changed for prefilling and decoding. When we allocate a new block that was computed, we check whether there is free space in DRAM and disk. We swap the block out if there is enough space. Note that this can also have a cascading effect (e.g. GPU -> CPU, CPU -> Disk) which we also handle
rmap is introduced to track which seq is mapped to the block since the context caching blocks have to exist during the TTL. The context caching only blocks are swappable (because if they are not used they will occupy the whole HBM) so we need to find the sequences that mapped to a certain block in eviction.

Layered transfer between HBM and DRAM:
Usage:
Add --enable-layered-transfer flag

Implementation:
We create another CUDA stream for transferring. In attention calculation, the calculation waits for this dedicated CUDA stream and invokes the data transfer for the next layer in this dedicated CUDA stream. Then, it starts calculating the current layer.

Disk support (Temtative)
Usage:
Add --enable-disk-swap flag and pass the config file by --disk-swap-config swap.cfg

Implementation
Right now disk still uses block abstract and the same granularity. The swap manager is separated into the stateful part (SwapDeviceManager) and stateless part (SwapDeviceClient) because the scheduler and the works use different processes, and it is hard to share states between them (we can do it. It Just takes more time). The stateful part manages the block allocation which the stateless part is responsible for transmission (Like the separation between CacheEngine and BlockManager).
Right now each block and each layer will create a file. I will optimize it later.
Supporting status:

Only BlockManagerV1 is supported.  BlockManagerV2 is WIP.
Disk does not support layered transfer now as I am still exploring the interface
Disk only supports TP=n case as PP=n requires sharing between multiple schedulers.

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Great idea, but it seems there are performance issues at this stage. In my testing, the execution time of the function scheduler.schedule() has increased more than tenfold compared to vllm 0.6.1.post2, even with only prefixcaching enabled. Is there an optimization plan for this issue?

Great idea, but it seems there are performance issues at this stage. In my testing, the execution time of the function scheduler.schedule() has increased more than tenfold compared to vllm 0.6.1.post2, even with only prefixcaching enabled. Is there an optimization plan for this issue?

Hi, every glad to see you are interested. Did you run my branch for your test? And did you see an end2end slow down because of scheduling? I have not looked into scheduling logic yet but I guess this is because I put a lot of policy decisions in the block_manager which is invoked by scheduler at multiple places.

Great idea, but it seems there are performance issues at this stage. In my testing, the execution time of the function scheduler.schedule() has increased more than tenfold compared to vllm 0.6.1.post2, even with only prefixcaching enabled. Is there an optimization plan for this issue?

Hi, every glad to see you are interested. Did you run my branch for your test? And did you see an end2end slow down because of scheduling? I have not looked into scheduling logic yet but I guess this is because I put a lot of policy decisions in the block_manager which is invoked by scheduler at multiple places.

Yes, I run v0.6.1.post2_tiering branch. I separately counted the scheduling time. When enable_caching = True, the scheduling time increases. When enable_memory_tiering = True, both the scheduling time and the execution time of execute_worker increase, indicating that the performance loss caused by scheduling is greater. Do you have any ideas for optimizing scheduling? Perhaps you can refer to some methods in the CacheAttention paper to optimize pipelines.
I would also like to ask, does context caching fix the input content in the video memory for a period of time? Can you briefly explain the usage scenarios of context caching? thk

Great idea, but it seems there are performance issues at this stage. In my testing, the execution time of the function scheduler.schedule() has increased more than tenfold compared to vllm 0.6.1.post2, even with only prefixcaching enabled. Is there an optimization plan for this issue?

Hi, every glad to see you are interested. Did you run my branch for your test? And did you see an end2end slow down because of scheduling? I have not looked into scheduling logic yet but I guess this is because I put a lot of policy decisions in the block_manager which is invoked by scheduler at multiple places.

Yes, I run v0.6.1.post2_tiering branch. I separately counted the scheduling time. When enable_caching = True, the scheduling time increases. When enable_memory_tiering = True, both the scheduling time and the execution time of execute_worker increase, indicating that the performance loss caused by scheduling is greater. Do you have any ideas for optimizing scheduling?

Yeah, I know one reason that can explain why the latency of scheduling increases in both cases. I enabled one small optimization when checking whether the seq can be allocated or not. The original vLLM simply compares the required blocks of a seq with the available free blocks to decide whether this seq can be allocated or not. My code performs a prefix matching to get the exact required blocks so the decision is less conservative. I did not cache the hash value of blocks now so we did one additional hash compute whose cost is O(L^2). I am planning to cache it later.
I guess the execute time increases because of some additional logic of check whether the layered transfer is enabled or not, I am not sure this will lead to huge increase. How much was the increase you saw at this place>

Perhaps you can refer to some methods in the CacheAttention paper to optimize pipelines. I would also like to ask, does context caching fix the input content in the video memory for a period of time? Can you briefly explain the usage scenarios of context caching? thk

Right now, vLLM does not have a good support for prefix caching in multi modality because the video part is filled with the default placeholder and is only updated when the video model finishes execution. We will support the prefix caching for multi modality later this year.
Right now, the context caching only supports caching a prompt for ttl time. The code guarantees for this time, the context caching will exist in the system. We will consider add a file interface later so the context caching can be generated from uploaded files.
Sorry for my late reply. I hope this helps you,

Great idea, but it seems there are performance issues at this stage. In my testing, the execution time of the function scheduler.schedule() has increased more than tenfold compared to vllm 0.6.1.post2, even with only prefixcaching enabled. Is there an optimization plan for this issue?

Hi, every glad to see you are interested. Did you run my branch for your test? And did you see an end2end slow down because of scheduling? I have not looked into scheduling logic yet but I guess this is because I put a lot of policy decisions in the block_manager which is invoked by scheduler at multiple places.

Yes, I run v0.6.1.post2_tiering branch. I separately counted the scheduling time. When enable_caching = True, the scheduling time increases. When enable_memory_tiering = True, both the scheduling time and the execution time of execute_worker increase, indicating that the performance loss caused by scheduling is greater. Do you have any ideas for optimizing scheduling?

Yeah, I know one reason that can explain why the latency of scheduling increases in both cases. I enabled one small optimization when checking whether the seq can be allocated or not. The original vLLM simply compares the required blocks of a seq with the available free blocks to decide whether this seq can be allocated or not. My code performs a prefix matching to get the exact required blocks so the decision is less conservative. I did not cache the hash value of blocks now so we did one additional hash compute whose cost is O(L^2). I am planning to cache it later.
I guess the execute time increases because of some additional logic of check whether the layered transfer is enabled or not, I am not sure this will lead to huge increase. How much was the increase you saw at this place>

Perhaps you can refer to some methods in the CacheAttention paper to optimize pipelines. I would also like to ask, does context caching fix the input content in the video memory for a period of time? Can you briefly explain the usage scenarios of context caching? thk

Right now, vLLM does not have a good support for prefix caching in multi modality because the video part is filled with the default placeholder and is only updated when the video model finishes execution. We will support the prefix caching for multi modality later this year.
Right now, the context caching only supports caching a prompt for ttl time. The code guarantees for this time, the context caching will exist in the system. We will consider add a file interface later so the context caching can be generated from uploaded files.
Sorry for my late reply. I hope this helps you,

Thanks for reply, the time of execute_worker (data movement) takes up about 20% of the entire inference time (GPU: H100, the proportion should be lower  for other types of GPU) , I hope this data can help you

Hello, Thanks for the data! I am actually working on it now to reduce this part. I need to get the access to the H100 to test it.

Hi, I think the idea is quite good and I have tested this PR on A100 GPU, but seems has issue like below:  Do you know why this happened? Thanks!
I just use 'pip install -e .' to build the vllm on my local machine and use python benchmarks/benchmark_context_caching.py for the test.

Let me have a look what is happening. It is likely I changed some APIs internally.

Hi! I have an idea. Can we support a key-value database similar to valkey (Redis over RDMA)? Among them, the key is the hash value of the token. In this way, the data in this database can be completely shared by multiple vllm instances.

Hello, Thanks for the data! I am actually working on it now to reduce this part. I need to get the access to the H100 to test it.

Hi, I think the idea is quite good and I have tested this PR on A100 GPU, but seems has issue like below:  Do you know why this happened? Thanks!
I just use 'pip install -e .' to build the vllm on my local machine and use python benchmarks/benchmark_context_caching.py for the test.

I met the same error on V100.  Thanks!


Zoning

Forgive me as I've only had this device a few days.  My vacuum can do a large section of my home before depleting the battery.  Unfortunately it seems like it follows the same pattern of cleaning each time so the master bedroom is usually missed.  I may be wrong but that's how it appears.
Someone posted about creating a zone in the WeBack app and the robot will then clean that zone.  Is it possible to create a zone using this software and then instruct the robot to clean that zone?  I see the working state has changed to 'PlanningRect' when it is doing the zone cleaning.
I think this would be a worthy addition as I'd prefer more control over what the robot does.  It seems to like to clean our dining room (the charging base is located here) first, but this room is not used nearly as much as other rooms.  Being able to tell it to clean this room less often and rooms like the living room, kitchen, and bathrooms would be fantastic.
Your thoughts?

I can't make it because my robot is not support map saving and zone cleaning features. I think we should wait for someone who has this type of vacuum cleaner will add support for this set of features (at least run cleaning on already saved zone). Or until someone will by this type of vacuum for me :D

Haha.  Understood.  So far this Tesvor S6 works pretty well but as with everything I'd like to force it to do more :)

Me again.  I've got a question that you may or may not be able to answer.  I'd like to be able to send the robot to a particular room.  I can use the Weback app and draw out a 'zone' and when I click done it will go to that zone and clean it.  The state changes to 'PlanningRect' .  I see from your GH page that there are these:
PLANNING_RECT("PlanningRect"),
PLANNING_LOCATION("PlanningLocation"),

I am assuming that one of these is the location to be cleaned and the other is the command to send the robot to that location and clean it.
I've installed your python library and am able to identify the rectangle that I created for my kitchen:
'planning_rect_x': [55, 55, 146, 146],
'planning_rect_y': [103, 175, 175, 103],
Can you please tell me how I might send this data as well as the PLANNING_RECT("PlanningRect"),
command to start the bot?  Can I do this via MQTT?
I think once I can do this for one room, I'll just need to create a rectangle for another room, query and save those values.  At that point I should be able to script something for each room and have Home Assistant or Node Red call those scripts as needed.
Thanks again.

@opravdin
Okay.  Success.  I did as described above.  I created the room rectangle in Weback app, then ran the script to pull the attributes and got the coordinates of the room.  I repeated this for another room and recorded those coordinates.  I then issued the command like this:
payload = {
    'state': {
        'desired': {
            "working_status": "PlanningRect",
            "planning_rect_x": [115, 115, 189, 189],
 	    "planning_rect_y": [106, 176, 176, 106]
        }
    }
}

The robot went to the first room and started cleaning.  I then stopped the robot, changed the values for the room coordinates and resissued the modified command above.  The robot went to the second room and started cleaning.
I can now create a script that will send the robot to various rooms.
My question does remain to if there is an easier way to communicate with the robot via MQTT.  Could you consider a way to allow for sending custom payloads like what I've shown through the integration somehow?  I am not a programmer so I don't know how hard/easy this would be but it would certainly be cool to have this capability.  I know it does not benefit you directly as your vacuum doesn't use lidar for location awareness.

@dinki
Thank you for investigation! I will mention it in the readme file.
Related to HASS: you can use custom command to send any payload you like to your robot. This feature is mentioned in this section of readme: https://github.com/opravdin/weback-hass#custom-commands
Check this integration example (fan_status is passed straight to MQTT payload):
- alias: Automatic set fan high
  trigger:
  - entity_id: vacuum.livingroom
    from: 'off'
    platform: state
  condition: []
  action:
  - entity_id: vacuum.livingroom
    data:
      command: anything
      params:
        fan_status: Strong
    service: vacuum.send_command

Fantastico!  I'll give it a try in a bit.   Here's the steps to follow to get the map coordinates:

In the Weback app, click the map (?) icon and select 'Zone'
Click 'Add' and drag the rectangle to the area you want to define and resize it.
Click 'Finish' and let the robot start the cleaning process

Run this script to pull the values while the robot is running.  You will need to change your credentials:
from weback_unofficial.client import WebackApi
import boto3
import json
import pprint

# Method 1: make this package keep session itself
client = WebackApi('+1-youremail_or_phonenumber', 'your_password')
session = client.get_session() # Returns Amazon Session from boto3 package

print (session)

devices = client.device_list()
device_name = devices[0]['Thing_Name']

client = session.client('iot-data')
resp = client.get_thing_shadow(thingName=device_name)
shadow = json.loads(resp['payload'].read())
print("Attributes:")
pp = pprint.PrettyPrinter(indent=1)
pp.pprint(shadow['state']['reported'])

You will then see the values for the room you've defined in the attributes:
'planning_rect_x': [55, 55, 146, 146],
'planning_rect_y': [103, 175, 175, 103],

Note these coordinates.  Stop the robot then repeat the procedure for any additional rooms noting the coordinates of each.
Important:  You will will need to stop the robot before you attempt to send it to an area via script.
You can now add this to the bottom of the script posted above to test if it worked.  Be sure to change the coordinates to what you have found.
# Start up vacuum cleaner
client = session.client('iot-data')
topic = f"$aws/things/{device_name}/shadow/update"
# See more MQTT commands below
payload = {
    'state': {
        'desired': {
            "working_status": "PlanningRect",
            "planning_rect_x": [115, 115, 189, 189],
 	    "planning_rect_y": [106, 176, 176, 106]
        }
    }
}
resp = client.publish(topic=topic, qos = 0, payload = json.dumps(payload))
print(resp)

The robot should then go to that room and start cleaning if all goes well.
I'll explore the automation example provided above and see if I can pass the required parameters to do this via an automation.  Hopefully this will work in the same way and individual automations can be created as needed.  I'll report back on what I find.

Well that was easy!  This automation sends the robot to my office and cleans it:
- id: '1527474342232'
  alias: Test Vac
  trigger:
    entity_id: vacuum.tesvor_s6_70_66_55_37_aa_c0
    from: 'off'
    platform: state
  action:
    entity_id: vacuum.tesvor_s6_70_66_55_37_aa_c0
    data:
      command: anything
      params:
        fan_status: Strong
        planning_rect_x: [252, 252, 322, 322]
        planning_rect_y: [217, 276, 276, 217]
        working_status: PlanningRect

    service: vacuum.send_command

Thanks again for your work on this.  You've just made my robot a whole lot smarter.  I'm planning on adding this to my Node Red Alexa skill so that I can say 'Alexa vacuum living room/office/bed room/etc'.  Very cool indeed!

i'm having this error...
the credentials are right.. i also create another account with cell phone number just in case, but the problem presist..
Logger: homeassistant.setup
Source: custom_components/weback/init.py:47
Integration: weback
First occurred: 10:04:49 PM (1 occurrences)
Last logged: 10:04:49 PM
Error during setup of component weback
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 248, in _async_setup_component
result = await task
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/weback/init.py", line 47, in setup
devices = weback_api.device_list()
File "/usr/local/lib/python3.8/site-packages/weback_unofficial/client.py", line 75, in device_list
session = self.get_session()
File "/usr/local/lib/python3.8/site-packages/weback_unofficial/client.py", line 137, in get_session
raise Exception(f"Could not authenticate. {weback_data['Fail_Reason']}")
Exception: Could not authenticate. account or password is incorrect
any idea?

Stumbled upon an issue with SSL certificate for the endpoint is being used. Altering this line fixed the issue:
client = session.client('iot-data', verify=False)

Could not authenticate.
"account or password is incorrect"
credentials are correct


fix: reload precompiled modules

steps to see what's the problem
colorscheme nightfox
colorscheme duskfox
colorscheme nightfox

Thanks for the catch. I I left my debug variable on in my config so I did not catch this. LGTM


chore(deps): update dependency node-sass to v6

This PR contains the following updates:

Package
Type
Update
Change

node-sass
devDependencies
major
^4.12.0 -> ^6.0.0

Release Notes

sass/node-sass
v6.0.1
Compare Source
Dependencies

Remove mkdirp (@jimmywarting, #3108)
Bump meow to 9.0.0 (@ykolbin, #3125)
Bump mocha to 9.0.1 (@xzyfer, #3134)

Misc

Use default Apline version from docker-node (@nschonni, #3121)

Supported Environments

OS
Architecture
Node

Windows
x86 & x64
12, 14, 15, 16

OSX
x64
12, 14, 15, 16

Linux*
x64
12, 14, 15, 16

Alpine Linux
x64
12, 14, 15, 16

FreeBSD
i386 amd64
12, 14, 15

*Linux support refers to major distributions like Ubuntu, and Debian
v6.0.0
Compare Source
Breaking changes

Drop support for Node 10 (@nschonni)
Remove deprecated process.sass API  (@xzyfer, #2986)

Features

Add support for Node 16

Community

Fix typos in Troubleshooting guide (@independencyinjection, #3051)
Improve dependabot configuration (@nschonni)

Supported Environments

OS
Architecture
Node

Windows
x86 & x64
12, 14, 15, 16

OSX
x64
12, 14, 15, 16

Linux*
x64
12, 14, 15, 16

Alpine Linux
x64
12, 14, 15, 16

FreeBSD
i386 amd64
12, 14, 15

*Linux support refers to major distributions like Ubuntu, and Debian
v5.0.0
Compare Source
Breaking changes

Only support LTS and current Node versions (@nschonni)
Remove deprecated process.sass API  (@xzyfer, #2986)

Features

Add support for Node 15
New node-gyp version that supports building with Python 3

Community

More inclusive documentation (@rgeerts, #2944)
Enabled dependabot (@nschonni)
Improve release automation (@nschonni)

Fixes

Bumped many dependencies (@nschonni)

Supported Environments

OS
Architecture
Node

Windows
x86 & x64
10, 12, 14, 15

OSX
x64
10, 12, 14, 15

Linux*
x64
10, 12, 14, 15

Alpine Linux
x64
10, 12, 14, 15

FreeBSD
i386 amd64
10, 12, 14, 15

*Linux support refers to major distributions like Ubuntu, and Debian

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you check the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: @uportal/waffle-menu/package-lock.json
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/eslint
npm ERR!   dev<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   @uportal/api-template-vue
npm ERR<EMAIL_ADDRESS>npm ERR!     node_modules/@uportal/api-template-vue
npm ERR!       workspace @uportal/api-template-vue from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">= 1.6.0 < 7.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@vue/cli-plugin-eslint
npm ERR!   dev<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   @uportal/api-template-vue
npm ERR<EMAIL_ADDRESS>npm ERR!     node_modules/@uportal/api-template-vue
npm ERR!       workspace @uportal/api-template-vue from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR!


Using path on socket

How could I use path in the URL, example: wss:micro_services/ws-3030/?id="xxxxxxx"
where my path is /ws-3030/
but currently /socket.io is added

hi. maybe you want not socket.io but raw websockets?
for websockets you can use https://ktor.io/docs/client-websockets.html
if you want socket.io but with specific path - you can send PR with this improvement


Fix typos (year) in a few license headers.

@Rikkola I think it's your code, could you take a look please?

drools-wb
(master) https://github.com/droolsjbpm/drools-wb/commit/b8720bf80
(6.3.x) https://github.com/droolsjbpm/drools-wb/commit/9c7d96416

@zkrejcov Thanks.


Request for Example on Full Parameter and Training for LLM Model

Hi,
Could you please provide an example of a large language model (LLM) with full parameters and training?
This would be incredibly helpful for understanding how to effectively train and utilize LLMs within the MLX framework.
Thank you very much!

full parameters and training?

Do you mean fine-tuning all the parameters of an LLM? There is a PR for that you could check out if so: #645

Not fine-tuning. I mean pre-train the model.

Like llama model, I want to add some tokens and retrain it.

Based on your comment it sounds like you want to fine tune the model. But are you saying you want an example which trains something like a Llama model from scratch? That is very computationally expensive.

Yes. Because mac studio is much cheaper than nvida
On a Mac with 192G memory, I want to try to see if I can train a model like llama from scratch.


DOCS: Split integrations/llm_cache page into separate pages

Privileged issue

[X] I am a LangChain maintainer, or was asked directly by a LangChain maintainer to create an issue here.

Issue Content
https://python.langchain.com/v0.2/docs/integrations/llm_caching/ should be a section with one page per integration, like other components.

I'd be happy to contribute to this.

@baskaryan @efriis is this being worked on? If not, I would like to pick this up as a first issue. LMK!


file autoindex multiple downloads issue

Hello!
could you please help is it possible to use this library when multiple large file download exist.
Or just replace it by asyncio.
thank you

Hello,
Yes you can use this library for this usage.
Good job with AutoIndex

Thank you!


Permissions are too broad

"Access your data for all websites"
I've seen another addon requiring access only to a certain domain name
That should require only access to tradingview.com

This add-on does not access your personal information. And the reason for setting the permissions this way is, that some other trading related websites are using Tradingview as their charting package. If the permissions are limited to tradinvgiew.com, then this plugin won't work on those websites.

but it's only for tradingview, isn't it?

The extension can be used on any website that uses Tradingview as its charting provider.

ok interesting


decker: 1.39 -> 1.40

Description of changes
https://github.com/JohnEarnest/Decker/compare/v1.39...v1.40
Aside from the constant clicking noise to be fixed in later versions of SDL2, it's all good.

Things done

Built on platform(s)

[x] 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
[x] 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

[x] Fits CONTRIBUTING.md.

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

Done in #297793.


[AutoPR] datafactory/resource-manager

Created to accumulate context: datafactory/resource-manager

(message created by the CI based on PR content)

@zikalino Something went wrong - why are all these files getting deleted?


added delegate functions to collect logs of user events

I tried to collect logs by customizing the TLPhotosPickerViewController.
But because focusedCollection and collections properties are private, I cannot differentiate whether user selected camera cell, selected cell or deselected cell. And I also cannot get information on collection when user tapped a album because of same reason.
I think others also need to collect logs on the user event.
I will be so grateful if I can collect the logs on user events.

I separated log interface at delegate. I think it have to only have pickers actions.


Get-DbaSqlProductKey - SqlInstances Parameter

Before submitting a bug report:

[x] Ensure you are able to reproduce it on the latest released version (we release often)
[x] Verified this bug is not already reported in an issue
[x] Verified errors are not related to permissions
[x] Can reproduce in a clean PowerShell session (clean = powershell -NoProfile)

Steps to Reproduce
Get-DbaSqlProductKey -SqlInstances 'Server1', 'Server2

Expected Behavior
Return versions only for the default instances on Server1 and Server2.
Actual Behavior
If there are disabled instances on Server2 it attempts to connect to them and gets can't connect messages. If Server1 has multiple instances, it will return information for all instances not just Server1.
Environmental data

PowerShell:
PSVersion                      5.1.14393.2248
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14393.2248
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
SQL Server: Multiple versions

Maybe SqlInstances needs to be renamed to ComputerName and a new SqlInstance parameter needs to be added that is more in alignment with the rest of the commands.

This is a command that has never had our new standards applied so it needs a large amount of work.

Ha, it is even still using the write commands for verbose, does not use the CMS commands or object type...would almost say that needs to be completely rewritten to utilize more commands and internal functions we have available now... // @potatoqualitee


Makefile outdated

Hey, when I am trying to make install, it is displaying

Could you update it?

Hi @m0rd4n! I'm no longer actively developing this exporter. If you know how to fix it, I will gladly welcome any merge request from you though:)


Add BetterGUI

also fix #2

Thank you for contributing, I guess I have to add them manually xd

For future reference, please keep everything in alphabetical order.


republish app as public on play store

Package name org.gooddollar needs to be replaced to org.gooddollar.wallet

[ ] Change package in android/ios source to org.gooddollar.wallet
[ ] Do we need a new android signing key?
[ ] Create new app and  licenses on apple
[ ] Update secrets on github
[ ] Check/modify facetec license
[ ] Check/modify  microsoft appcenter
[ ] Check/modify torus dependency on package name
[ ] Update branch.io
[ ] Update google analytics
[ ] Update sentry / amplitude

it seems that we can delete the published managed app and then publish a new app with the same package name as public app
steps:

[ ] backup current store listing
[ ] Wait for the app to finish the review by the google play team
[ ] unpublish app (Setup > Advanced setting > App availability and click the unpublished button)
[ ] wait for 24 hours
[ ] request google play support to permanently delete the app
[ ] publish the new app with the backed-up store listing data

store listing texts:
app-name: GoodDollar
short description: The World's First Digital Basic Income
Full description: GoodDollar is an app that allows you to receive FREE digital currency to your phone every day!
assets:
youtube link: https://youtu.be/ceSerJAVq7k
assets drive folder: https://drive.google.com/drive/folders/1WWkvTZKqEE8hwhY7JHSpDhQWzFIUWFzz
still missing: feature graphic, app icon

google support ticket number: 9-3675000031466

@julianpolcode @serdiukov-o-nordwhale i've unpublished the app
will send request tomorrow to delete it

The store setting are now filled. Please proceed with listing.

@sirpy @tzvister
Could you update the status of the app in the Google Play ?
I'm not able to find the 9-3675000031466 ticket. It seems it's available for @omerzam only.
But i see two updated from You guys after Omer left us. Could you please clarify:

What 'The store setting are now filled.' does means ? Did Google deleted app and it was recreated with proper settings (so it could now be public) ?

I see no automatic releases done by the Appcenter, so it looks like the app was recreated. Btw i see a release 1713 (1.29.1-5) inside 'Internal testing'. Does it was added manually after app was re-created ?

Who (i suppose @patpedrosa?) should i ask regarding the different app settings / store listing options i would need to fill ?

Which kind of the tracks should we configure ? E.g. production for public app, open testing for upcoming production version, closed testing for staging, internal testing for dev, ... ?

Hadar R  4:12 PM

I believe I've invited you to new app on play
yes we need to setup app center to play. and plan for using app center hot code push
yes @patpedrosa .
currently setup open testing of production. make sure not to do the same mistake we did in previous app. be ready to release to production track

move code push to the separate issue

@johnsmith-gooddollar @sirpy @tzvister if my help is required here let me know
I'll be happy to assist


Next Collateralization ratio displayed incorrectly

What happened:
The next collateralization ratio in the light wallet only ever shows the current ratio. The correct one is on Defiscan.
What you expected to happen:
Correct representation of the next Collateralization ratio
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
System: IOS

Hi, this one will be fixed on the next app update. Thanks!


[SourceKit] Don't build an AST if no semantic info is requested

Currently, we were building an AST on document open or edit even if

key_enablesyntaxmap = 0
key_enablesubstructure = 0
key_enablediagnostics = 0 and
syntax tree transfer mode is off

In those cases we were just ignoring the result.
If all of the options are 0, don’t build an AST.
rdar://85847659

@swift-ci Please smoke test


Specify Correlation with Somatic Alteration Module

Identify what should go into correlation with somatic alteration module.

Driver Mutations. Include Eduard in discussions as needed.
Copy Number Alterations. Include Galen in discussions as needed.
Pathways. Include Farshad and Francisco in discussions as neede

Moving to CRI-iAtlas/iatlas-planning/issues/3


Voice not changed using SSML

I have created a bot in node JS using the RollerSkill demo codes and enabled the speech API. I tried to change the voice of bot from a male's voice to a female voice using SSML settings, but it didn't make any changes. Is it a implementation issue or an emulator issue?
The SSML is the following:
<speak version="1.0" xml:lang="en-US"><voice name="Microsoft Server Speech Text to Speech Voice (en-US, ZiraRUS)" gender="Female" xml:lang="en-US">I'm roller,
the dice rolling bot. You can say 'roll some dice' or play one of the games I know how to play.</voice></speak>

The emulator only passes received messages to the WebChat control, which it its own GitHub project. I think you'll have better luck asking your question over at https://github.com/Microsoft/BotFramework-WebChat/issues

duplicate of https://github.com/Microsoft/BotBuilder/issues/3231

This issue does not pertain to the emulator itself, so I will close it.


Won't run. SyntaxError Unexpected token

I downloaded it, ran npm i, and npm start. This is the output:
ERROR in ./index.js
Module build failed: SyntaxError: Unexpected token (6:7)

  4 | import Presentation from "./presentation";
  5 |
> 6 | render(<Presentation/>, document.getElementById("root"));
    |        ^
  7 |

 @ multi webpack-hot-middleware/client babel-polyfill ./index

What versions of node and npm are you using @agarrharr? I just downloaded fresh and built with no problems - node v8.1.3, npm v5.1.0 for me.

IME (OSX 10.10.5) dies with same error under:
$ node -v; npm -v
v8.2.1
5.3.0

Also IME (Mint Linux 18) works just fine with:
$ node -v; npm -v
v6.9.4
3.10.10

Actually, I don't know what changed, but it works now.
$ node -v; npm -v
v6.11.1
5.3.0

Had the same problem after I copied all the files to a different folder. Turned out I forgot to copy all .* files, such as .babelrc.


(chores) ci: use suggestion from SonarCloud to improve analysis time

I did not see any improvement from using this flag on my own CI, but let's see how it works on the Apache one.


chore: try to setup docker build for aws-lc

This supports https://github.com/leanprover/LNSym/pull/101 by trying to setup a docker build to get the ELF crypto_test binary on both ubuntu and macOS.

Retired in favour of https://github.com/leanprover/LNSym/pull/101


Corrected formatting and line endings in readme and examples

Pull Request (PR) description
Corrected formatting and line endings in README.md and example scripts.
This Pull Request (PR) fixes the following issues
None
Task list
No functional changes.

[ ] Added an entry under the Unreleased section of the change log in the README.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[X] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Thanks you for sending in the PR, but this repo will be deprecated in the next release as the resource have been moved to ComputerManagementDsc. I suggest updating the resource here if needed https://github.com/PowerShell/ComputerManagementDsc/tree/dev/DSCResources/MSFT_RemoteDesktopAdmin
/cc @gaelcolas @PlagueHO


Trust dialog paths are not using label service

Drive letter on Windows are uppsercase:

@bpasero we are not using the label service for the path portion because the path needs to be editable by the user. i.e. They should be able to edit the string directly and we should be able save that into our list. In the local case, the default behavior is to use the file picker, but if you are editing a remote path that you are not connected to, you need to be able to edit the string. I consider this change but I'm a little nervous that we might get some UI representation that is not safe for editing.

Fair, we have methods to only fix the drive letter casing, so maybe safer to just do that.

I believe I solved this a part of a separate issue.

Assigning to Jan for verification

I still see lowercase drive letters: