password reset email not using site_url

System site url is configured.  Validated in database:
 28 | webhook.form_key            | --- b6abdc71254889ed11d2042f79b18f2c+|          |            | 2022-02-02 23:33:43.586245 | 2022-02-02 23:33:43.586245
    |                             |                                      |          |            |                            |
 29 | theme.active                | --- nordic                          +|          |            | 2022-02-02 23:34:10.691352 | 2022-02-02 23:34:10.691352
    |                             |                                      |          |            |                            |
  3 | settings.site_url           | --- https://helpdesk.myrealdomain +|          |            | 2022-02-02 20:08:34.023608 | 2022-02-02 23:50:27.520786
    |                             |                                      |          |            |                            |
 30 | settings.site_tagline       | --- Online Website          +|          |            | 2022-02-02 23:50:27.545871 | 2022-02-02 23:50:27.545871

However, password reset email still uses default - pre-install domain.

Currently using docker install
Container restarted after change.
Don't know if it's related, but one thing I noticed is that the Site Url in admin requires the https:// when other urls do not?

I'm using helpy in docker and encountered the same issue.
If I replace site_url in /helpy/config/settings.yml and restart container it starts working as expected.
I moved settings.yml out of docker container and bind-volumed it:
    helpy:
        image: helpy/helpy:release-2.8.0
        volumes:
            - "./settings.yml:/helpy/config/settings.yml:ro"


Use write locks in license store to avoid deadlocks

Fixes #250

I'll go ahead and merge this in so it can get some early testing with the 2.0 spec updates.


MXNet 0.11.0 Release Feedback: NOTICE file

As discussed in this email thread
All added Notices should be removed from the top level NOTICE file as indicated in this comment:
"Unless the dependencies listed have explicit notice requirements (they don't seem to) nothing needs to be added to the NOTICE file"

Fixed


Request to be added as a WP MicroProfiler New Contributor.

Hello,
I would like to become MP Contributor:
Firstname: Giuseppe
Lastname: Scaramuzzino
Email<EMAIL_ADDRESS>Resources ready to be share:
MicroProfile Rest Client with Quarkus
YouTube video: https://youtu.be/8d8GSRZzdsA
GitHub Repository: https://github.com/GiuseppeScaramuzzino/quarkus-microprofile-restclient
MicroProfile OpenAPI with Quarkus
YouTube video: https://youtu.be/H1Hf9NHQjSc
RESTful Web Service with Quarkus
YouTube video: https://youtu.be/spWnqkbFgH4
Thank you

Happy Friday, Giuseppe,
Your MP WordPress contributor access has been sent.   You are welcomed to start sharing MP content aim at teaching others, helping others adopt, learn, use...  the technology.
Thank you for choosing to share your current MP content.

By the way, should you encounter any issues with Wordpress, do feel free to re-open this ticket ok. !:)


FastReport.OpenSource.Web.MVC memory footprint continuously increasing

We try to evaluate FastReport.OpenSource, so we downloaded the code and ran FastReport.OpenSource.Web.MVC within Visual Studio 2019 (using Ctrl+F5).
Simply cycling through the sample reports makes the memory allocated to the ".NET Core Host' process to increase constantly. It consumed well over 1GB of memory in just a few iterations between all the reports.
This problem does not occur if we repeat the same usage pattern using the FastReport.OpenSource.MVC project.

Hi! We have some fixes in code. We plan to release the changes in early December in version 2021.1.

I have the same issue, I am using version 2021.1.7 and the memory consumption increases on each load of report render in Ubuntu

I have the same issue, I am using version 2021.1.7 and the memory consumption increases on each load of report render in Ubuntu

Hello!
I reproduced this problem
and informed the developers
Best regards
Marat


LE Audio: CSIS ensure that notifications are sent

Is your enhancement proposal related to a problem? Please describe.
In CSIS we don't verify that all notifications are actually sent. Since this may cause issues for remote devices (and is in fact not spec compliant), we should ensure that all notifications (or at least the latest value) is sent as notifications.
Describe the solution you'd like
If a notification fails to be sent, it can either be re-triggered by using a k_work or similar, or the change request can be rejected.
Describe alternatives you've considered
N/A
Additional context
N/A

Closing as already implemented


Bug fix - Retention does not blacklist dataset

Root cause
ConfigurableCleanableDataset was calling the incorrect super constructor super(fs, jobProps, log) instead of super(fs, jobProps, config, log)
Impact
When retention job is configured through config store, each dataset can be blacklisted by setting gobblin.retention.is.blacklisted=true. Since the wrong constructor was being called, this value was never passed to the super class. Hence the dataset was not blacklisted.
@chavdar can you review?

LGTM.


Add Coveralls.io code coverage badge.

Out of curiosity, past changing the branch that is listed in the querystring, is there any reason this isn't being merged?

It's been a while, but IIRC, I couldn't get it to work back then and ran out of time at one point.
Not sure what the current state is, to be honest. Happy to let you take over if you feel like. :-)


Fix undefined function.

Changes
Fixes #5604 by updating function call that was renamed in #5561.
Ideally, this preprocess function should be moved to the theme since it's a bit weird for it to be living in the static content module but being referenced elsewhere. Will fix in a separate PR so we can unblock deploy.
How should this be tested?
Does it explode on an action guide? :boom:

For review: @sergii-tkachenko
/cc @mikefantini

You missed dosomething_campaign_group.module:107

:+1:


Support zero-length arrays in numba.cuda

As an example,
@numba.cuda.jit
def foo():
    x = numba.cuda.local.array(shape=(2, 0), dtype=numba.int64)

foo()

gives ValueError: array length <= 0.
Currently these lines contain a workaround because of this issue:
https://github.com/numba/numba/blob/3399d618b334c75a7c5c1ab85ec02769fb3b4c3b/numba/cuda/cudadrv/devicearray.py#L432-L455

Thanks for the report / request!

See also #5234

#5234 is about arrays with shape () (len(shape) == 0), this issue is about arrays with shape (0,), (0, n) etc (0 in shape).

Yes, I don't think they're duplicates, I was just trying to gather together a few shape-related issues in case someone is looking at fixing up things in these areas.

I think the other one is already fixed :)

Hello everyone! I am new here and I wanted to see if I could work on this as my first issue?

Hi, @eric-wieser , @gmarkall  is this issue still open? Can I contribute in any way?

@AruparnaMaity If you can see a way to fix it, you could open a PR with the fix, if you'd like - note that as per https://numba.discourse.group/t/rfc-moving-the-cuda-target-to-a-new-package-maintained-by-nvidia/2628 new PRs should go to https://github.com/nvidia/numba-cuda
Many thanks in advance!


Add cujo.casa

Hello, I'd love to have my website added to the webring. The link to the directory is in the footer of my homepage (cujo.casa). Thanks in advance!

Hey ditocujo,
Nice website, but it is missing an about page with contact info, and all the projects are offsite links, none is documented on the website itself. In any case, it's currently missing creative works, I try to gather on the webring a collection of links that showcase an interest in arts somewhat, whether it be illustration or design, but it has to be more than code and scripts.


Ensure that numeric precision is included only if not None

This pull request ensures that the numeric_size of the Column is not None before using including it in the column type string representation.

While unioning tables together with the dbt-utils union_table macro, we were running into syntax errors like the following from SQL generated by DBT:
invalid input syntax for integer: none
LINE 54:            "total_tax_due"::numeric(None) as ...`

We were initially inclined to go and add a precision to the source table, but the models where this was happening were themselves based on derivative tables. For example, in the above case, total_tax_due is defined as an aggregate:
...
sum(tax_due) AS total_tax_due
...

So identifying the precision beforehand is nontrivial.

@drewbanin Yes, definitely makes sense. I started down that path, but didn't immediately see a test module to add them to (and was in a bit of a rush :blush:). I went agead and added a test module.
Also thought it'd be nice to see an integration test for this on Postgres. I added a couple numeric fields for the 008_schema_tests_test module. I wasn't sure what I needed to run the integration tests locally, so we'll see whether those break anything.

perfect! Looks great - I'll merge when appveyor passes :)
Thanks again!


dagger develop support for re-naming/re-sdk'ing existing module

(Follow-up to https://github.com/dagger/dagger/pull/6533)
dagger develop currently only allows you to set the name/SDK of a module that does not already have one set.
It's possible to support changing the name/SDK too, but there's a few things to consider here:

If you rename your module, you'd need to also update your code to use that name in the structs, but obviously much better would be if we did that automatically somehow

more thoughts from @helderco here

If you change your SDK, we can't translate your existing code into the new SDK lang, but it's also not clear if we should delete it (maybe fine, but it's scary to delete user files)

Hi @sipsma
I am starting to evaluate the requirements (and changes needed) for this.

building on the suggestion from @helderco here, if we change code generator to generate the modules' main.go as follows:
Note: Foo is the name of the module and InbuiltName is a static name which will be constant across all modules.
(InbuiltName is a random name I selected, we will change it to something more meaningful before merging.)
type Foo struct {
	InbuiltName
}

type InbuiltName struct{}

func (b *Foo) GetInbuiltName() *InbuiltName {
	return &b.InbuiltName
}

// Returns a container that echoes whatever string argument is provided
func (m *InbuiltName) ContainerEcho(stringArg string) *dagger.Container {
	return dag.Container().From("alpine:latest").WithExec([]string{"echo", stringArg})
}

// Returns lines that match a pattern in the files of the provided Directory
func (m *InbuiltName) GrepDir(ctx context.Context, directoryArg *dagger.Directory, pattern string) (string, error) {
	return dag.Container().
		From("alpine:latest").
		WithMountedDirectory("/mnt", directoryArg).
		WithWorkdir("/mnt").
		WithExec([]string{"grep", "-R", pattern, "."}).
		Stdout(ctx)
}

and then also update code generator to generation the func invokeSrc (in dagger.gen.go file) as follows:
...
return (*Foo).GetInbuiltName(&parent).ContainerEcho(stringArg), nil
...

instead of
return (*Foo).ContainerEcho(&parent, stringArg), nil

it seems to work as expected. and I am hoping will make renaming of the module easier.
and when using this module as dependency, we are still able to do dag.Foo()...... 🎉
I am still working on trying out how other sdk will play out but I wanted to publish this update to receive any early feedback that folks might have.
thanks


add other vendors

add plz Vk.com ok.ru tiktok

@avesgit
I guess tiktok doesn't provide share via web
I've added vk and ok in new version, here's example
https://codesandbox.io/s/react-web-share-localized-xmvmzl

@avesgit
I guess tiktok doesn't provide share via web
I've added vk and ok in new version, here's example
https://codesandbox.io/s/react-web-share-localized-xmvmzl

Матн ерфтлы


Issue543 Implement flow tests for swap fees v4

Fixes #543 .
Changes proposed in this PR:

Implemented flow tests for swap fees.
Added helper functions to BPool.

I will merge this as soon as #568 is merged, because I told @trizin about the helper function that we can use for deploying ERC721 token and ERC20 as well.


Use InfiniteQueries instead of Cursors

Changes

User Posts feed uses IQ
User following/ers uses IQ
I promise not all of these lines are significant, I just auto-fix imports and some of the imports were mal-formatted, but sorry for the bloated diff :(

Issue ticket number and link

Can you please create an issue for this?

done


More flags for cert gen

So I added some flags to make the cert gen command more flexible.

@masterzen What do you say?

Thanks for this PR!
The use-a-cli-library branch is still a WIP which as published now uses https://github.com/urfave/cli but its not finished.
I'm still undecided about the cli library to use. urfave/cli is not that bad, but there are some missing features (like having a default command that could map to exec).
I've even completely rewritten the feature (but not published) on top of https://github.com/spf13/cobra and viper, which I find more customizable. One idea of using viper is to have a way to specify profiles in a configuration file (containing various credentials), and being able to simply winrm --profile win2012 exec ipconfig /all and fetch the credentials from the config file (this feature is not implemented yet).
So I propose to leave this PR as is until I settle on a cli lib and publish/merge the code. Then I'll try to adapt the changes to whatever code we'll have at that time.
Does that work for you?

Yeah, It's ok. I will not come back until the library used will be settled.


Could you please offer bazel BUILD files to build the repository?

I can build with tensorflow's BUILD file. But at runtime, the following codes would give "Sementation Fault"
#include <libxsmm.h>
#include <vector>
int main(int argc, char* argv[])
{
  typedef double value_type;
  int batchsize = 1000, m = 13, n = 5, k = 7;
  std::vector<value_type> a(batchsize*m*k), b(batchsize*k*n), c(m*n, 0);
  /* C/C++ and Fortran interfaces are available */
  typedef libxsmm_mmfunction<value_type> kernel_type;
  /* generates and dispatches a matrix multiplication kernel (C++ functor) */
  kernel_type kernel(LIBXSMM_GEMM_FLAG_NONE, m,n,k, 1.0/*alpha*/, 1.0/*beta*/);
  assert(kernel);
  for (int i = 0; i < batchsize; ++i) { /* initialize input */
    a[i*m*k] = static_cast<value_type>(1) / (i % 25);
    b[i*k*n] = static_cast<value_type>(7) / (i % 75);
  }
  /* kernel multiplies and accumulates matrix products: C += Ai * Bi */
  for (int i = 0; i < batchsize; ++i) kernel(&a[i*m*k], &b[i*k*n], &c[0]);
}

my BUILD file is
# Description:
#    LIBXSMM: Library for small matrix-matrix multiplications targeting Intel Architecture (x86).
package(
    default_visibility = ["//visibility:public"],
    licenses = ["notice"],  # Apache 2.0
)

# Description:
#    LIBXSMM: Library for small matrix-matrix multiplications targeting Intel Architecture (x86).

exports_files(["LICENSE.md"])

# Arguments to ./scripts/libxsmm_interface.py, see that file for detailed description.
#  precision: SP & DP
#  prefetch: 1 (auto)
libxsmm_interface_arguments = "0 1"

# Arguments to ./scripts/libxsmm_config.py, see that file for detailed description.
# rely on default arguments
libxsmm_config_arguments = ""

# Arguments to ./scripts/libxsmm_dispatch.py, see that file for detailed description.
#  (dummy argument)
libxsmm_dispatch_arguments = "0"

genrule(
    name = "libxsmm_headers",
    srcs = [
        "src/template/libxsmm.h",
        "src/template/libxsmm_config.h",
    ],
    outs = [
        "include/libxsmm.h",
        "include/libxsmm_config.h",
        "include/libxsmm_dispatch.h",
    ],
    cmd = "$(location :libxsmm_interface) $(location src/template/libxsmm.h) " + libxsmm_interface_arguments + " > $(location include/libxsmm.h);" +
          "$(location :libxsmm_config) $(location src/template/libxsmm_config.h) " + libxsmm_config_arguments + " > $(location include/libxsmm_config.h);" +
          "$(location :libxsmm_dispatch) " + libxsmm_dispatch_arguments + " > $(location include/libxsmm_dispatch.h)",
    tools = [
        ":libxsmm_config",
        ":libxsmm_dispatch",
        ":libxsmm_interface",
    ],
    visibility = [
        "//visibility:public"
    ],
)

cc_library(
    name = "xsmm_avx",
    srcs = glob(
        [
            # general source files (translation units)
            "src/generator_*.c",
            "src/libxsmm_*.c",
        ],
        exclude = [
            # exclude generators (with main functions)
            "src/libxsmm_generator_*.c",
        ],
    ),
    hdrs = glob(
        [
            # general header files
            "include/libxsmm_*.h",
            # trigger rebuild if template changed
            "src/template/*.c",
            "src/*.h"
        ],
        exclude = [
            # exclude existing/generated headers
            "include/libxsmm.h",
            "include/libxsmm_config.h",
            "include/libxsmm_dispatch.h",
        ],
    ) + [
        # source files included internally
        "src/libxsmm_hash.c",
        # generated header files
        "include/libxsmm.h",
        "include/libxsmm_config.h",
        "include/libxsmm_dispatch.h",
    ],
    #copts = [
    #    "-mavx",  # JIT does not work without avx anyway, and this silences some CRC32 warnings.
    #    "-Wno-vla",  # Libxsmm convolutions heavily use VLA.
    #],
    defines = [
        "LIBXSMM_BUILD",
        "LIBXSMM_CTOR",
        "__BLAS=0",
    ],
    includes = [
        "include",
        "src",
        "src/template",
    ],
    linkopts = ["-lpthread"],
    visibility = ["//visibility:public"],
)

py_library(
    name = "libxsmm_scripts",
    srcs = glob(["scripts/*.py"]),
    data = ["version.txt"],
)

py_binary(
    name = "libxsmm_interface",
    srcs = ["scripts/libxsmm_interface.py"],
    deps = [":libxsmm_scripts"],
)

py_binary(
    name = "libxsmm_config",
    srcs = ["scripts/libxsmm_config.py"],
    deps = [":libxsmm_scripts"],
)

py_binary(
    name = "libxsmm_dispatch",
    srcs = ["scripts/libxsmm_dispatch.py"],
    deps = [":libxsmm_scripts"],
)

I build the dynamic library using the following:
wget https://github.com/hfp/libxsmm/archive/1.14.tar.gz
tar xvf 1.14.tar.gz
cd libxsmm-1.14/
make STATIC=0

and the following code gives an segmentation fault error:
#include <libxsmm.h>
#include <vector>

int main(int argc, char* argv[]) {
  float alpha = 1.0;
  float beta = 1.0;
  typedef libxsmm_bfloat16 value_type;
  int batchsize = 1, m = 1, n = 32, k = 32;
  std::vector<value_type> a(batchsize*m*k), b(batchsize*k*n), c(m*n, 0);
  libxsmm_bmmfunction kernel;
  kernel = libxsmm_bmmdispatch(m, n, k, &m, &n, &k, &alpha, &beta, NULL, NULL);
  assert(kernel);
  for (int i = 0; i < batchsize; ++i) { /* initialize input */
    a[i*m*k] = static_cast<value_type>(1);
    b[i*k*n] = static_cast<value_type>(7);
  }
  /* kernel multiplies and accumulates matrix products: C += Ai * Bi */
  for (int i = 0; i < batchsize; ++i) kernel(&a[i*m*k], &b[i*k*n], &c[0]);
}

my BUILD file is as following:
cc_library(
  name = "xsmm_avx",
  srcs = glob(["lib/*.so"]),
  hdrs = glob(
      [
          # trigger rebuild if template changed
          "src/template/*.c",
          "src/*.h",
          "include/*.h",
      ]
  ) + [
      # source files included internally
      "src/libxsmm_hash.c",
  ],
  includes = [
      "include",
      "src",
      "src/template",
  ],
  linkopts = ["-lpthread"],
  visibility = ["//visibility:public"],
)

Would you please tell me where I am wrong ?

@hfp I am worried about that you may not see the message upwards. So excuse me for @ you. Thank you !

You may want to read the following commit message to realize the limitation of what was added. For your convenience, you can find our "Hello World" example equipped with some support for Bazel.

Thank you for your kind and useful replies ! It's so nice of you.
I am looking for a GEMM library for our deep learning applications. I have 2 matrix, one is the kernel which is fixed in inference, the other is the activation which varies time to time. The size is 1 * 512 * 512, and the MM will repeat many times.
I used to use a GEMM library that packs the kernel before computing, and the packed kernel would be used for many times.
Recently I have demand for faster MM and Sparse MM that computed in bfloat16. Could I ask if the libxsmm will make it in your opinion ?
By the way, can you show me a libxsmm_bmmdispatch example ?
Thank you !

Thank you, Yablon for your kind words!

By the way, can you show me a libxsmm_bmmdispatch example ?

For deep learning, the bf16sgemm sample can be interesting. It uses a flavour of our kernel that not only runs a singular GEMM but rather a whole batch of multiplications in one call. The kernel is available in several flavours accepting different input data. The sample code shows the strided flavour ("strd"). This sort of code is especially suitable for code that wants to control the loop-nest running the kernel.

Recently I have demand for faster MM and Sparse MM that computed in bfloat16. Could I ask if the libxsmm will make it in your opinion ?

For further questions, @alheinecke may be also willing to help.

There is a whole collection of other code samples that perform more out-of-the-box tasks related to deep learning (https://github.com/hfp/libxsmm/tree/master/samples/deeplearning). The GxM framework among this set of samples would be also able to run entire CNN topologies (prototxt). Further, you may want to have a look at PlaidML (please note it's the "v1" branch), which uses LIBXSMM when targeting CPUs.

I would look into https://github.com/hfp/libxsmm/blob/master/samples/xgemm/kernel.c for a good bf16 example. The bf16sgemm mentioned above is very specific case for trailing updates / sizes.

hi, @alheinecke, thank you for your reply.
Do I get a code dispatch one in that example ? I got thousands of hundreds of matrix mulplication between a varying A and fixed B. I want to minimize the cost between the same mulplication.

hi, @hfp Thank you ! I have read the example and I will try and compare with my current GEMM library. It's late in night in East Asia now. I would test it tomorrow moring and hope you safe and sound.


Update nushell crates

Description of changes
Updates the nushell crates, and adjusts the code according to the breaking changes.
Relevant Issues
NixOS/nixpkgs#341647

No clue why that test fails

Hi! thank you for updating the deps.
Apparently the parser got updates since 0.88.1 and now it parses things a little different.
I test it on my pc and the result of the test ignore_comments is
        let expected = "# beginning of script comment
let one = 1
def my-func [
    param1:int # inline comment
]{ print(param1)
}
myfunc (one )
# final comment";

(a little space difference in the line myfunc (one )

Yeah I got that far as well, but is that actually the result we want? I wouldn't want my function calls looking like that.

Sure, it can (and should eventually) be fixed, but I prefer to merge this as is and then in another pr fix/improve the formatter logic and after change the tests that looks weird.
Isn't it better?

ok, i'll land it if someone fixes the problem.

Well, I'm fine either way. I don't even use nu, I just wanted to get the development environment working (couldn't for 3 different reasons), and try it.
I might wait with updating the nixpkgs PR until someone fixes it though.


Feature Request: More Traditional Installation Process

Right now, the installation process seems strange to me. Just using PIP to install it appears significantly different from installing other bots, such as https://github.com/xNul/chat-llama-discord-bot or https://github.com/ChobPT/text-generation-webui-discord_bot. I've attempted to execute the command "export DISCORD_TOKEN=your_bots_discord_token" on both Linux and Windows, but it hasn't worked on either platform, despite replacing "your_bots_discord_token" with my actual token. While this is likely a user error on my part, I believe that many people who try to install this bot will experience similar difficulties. Therefore, I would prefer an installation process similar to that of this bot: https://github.com/AndBobsYourUncle/stable-diffusion-discord-bot.

Thanks for the feedback!  I'll take a look.

I would also prefer a more transparent installation process. It makes it easier to tinker with things when you know where everything is stored. I do recognize the value in a simple process, so perhaps having both options available would work.

@Skrownerve what would a more transparent installation process look like?
@TheMelonGod I've added the ability to pass a --discord-token via the command line, which should be included in the 0.1.6 release (probably next week).
As you may well know there are security concerns with passing a secret on a command line, mainly that anyone else who is using the machine and can run ps will be able to see it.  But a few people have struggled with setting the env var, and I know that many of us are just doing this on single-user systems where the security concern is mitigated for other reasons.  So I hope this might help you get started once it's out.

@TheMeIonGod @Skrownerve i found installation like this much better , it just need more openess
Like we can set number of tokens , temperature , other parameters etc
I think it's perfect and easy

You guys are pinging the wrong guy, quit fuckin' emailing me

note for future folks: the person who filed this task has the username of TheMe[capitol i]onGod, not "TheMelonGod" (with a lower case l).
I think the person with the "TheMeLonGod" username would appreciate it if we didn't ping him by accident.
I've fixed the comments above, just for future reference.

My thoughts -- I like the current python install process.  I know it's pretty rough on Windows, but on osx and linux it's pretty standard, and there's lots of tooling to support it.
I do think there are folks who would like to run oobabot who aren't super-comfortable with that, or just don't want to spend the energy to figure it out.  To address those folks, I would like to do one of:

create a plugin to oobabooga
create a docker container where everything's bundled
Both of these would build on the existing python egg, not replace it.

The plugin idea has been suggested by others, and would probably be the easiest, as you have to setup oobabooga anyway, then it would be one click plus some UI config.
This project is still pretty young, though, and I want to spend some time iterating before trying to integrate it.  Development is more costly the bigger the project is, so I think it makes sense to try and keep things as simple as possible for now, and then as the project feature set starts to stabilize, the look to expand.

@chrisrude By "transparent", I just mean more easily accessible files. I'm not too familiar with Python, and most of the projects in AI I've played with have traditional setups where I can dig through the files. Like, even on Linux via WSL, when I install Oobabooga's web UI, I have a file structure I can browse and see every file and make tweaks if I want to (that I have to inevitably stash so I can update to latest because I'm not confident trying to merge others' work with my tweaks).
To put it simply, maybe I'm just not aware of how/where I could inspect the files installed by pip. As of now, I don't know if it's possible, and therefore your install process, while simple, is opaque to me. That being said, it's not bad how it is now. And once you add all the configurations you've been planning I probably wouldn't even need to go digging around anyway.
For an example of a familiar process to me, the one-click installers for Oobabooga's and AUTOMATIC1111/Vladmandic's web UIs seem ideal. They create a venv and install all dependencies in them somewhere I can clearly see and meddle with, and give me clear instructions on how to run it. I have no idea if it's possible to run oobabot from the folder that results from a git clone. I tried and failed.

Thanks for the clarification!
I've just added clearer instructions on how to run from a clone.  Check them out here, and let me know if they help:
https://github.com/chrisrude/oobabot/blob/main/docs/CONTRIBUTING.md#development-environment
My preference is to have most folks run via the pip install process, which is why I haven't documented the dev process in the main readme.  The main reason for this is that oobabot doesn't have great tests, so I've been reliant on just running it (and the helpful reports of folks here!) to uncover bugs in new code.
By having both a git-repo method and a pip install method, the folks who are more excited to try the latest can do so (with the understanding that sometimes things will break), while folks that just want it to work can use pip install, and hopefully run into issues less frequently.


Manual implementation of clasic Ornstein Uhlenbeck process not working

I just tried to implement  the classic Ornstein Uhlenbeck process, creating a custom Drift class:

However, when attempting to solve the model, the following appears:

You need to switch the order of "self" and "x" in the get_drift function and then it should work.  "self" should always be the first argument in python methods, e.g., see this tutorial.


popover positioning is wrong for large(r) values of .popover max-width

it seems that if .popover max-width is set too large (eg over 350px) that the positioning relative to the trigger element is wrong.  i couldn't quite work out what was causing it.  setting a fixed width (rather than max-width) seems to fix the issue.

This is fixed when using the most recent ui-bootstrap and bootstrap css.
http://plnkr.co/edit/0s6RbB?p=preview


Skimming branches

Hi,
I couldn't attend your talk in CAT, but I saw the slides. I am very interested in your tools since my analysis tries to take some nanooad files and try some simple skimming of the files to make our pipeline faster. Your tool can really simplify our lives.

Do you have any example of how can I take an entire dataset (more than one file) remove branches and save a new root file? For this, should I need to run in some sort of computer cluster (like HTCondor), or can I run locally? or with Dask?
My other suggestion/request is if a simple selection can be included while doing the removal of branches. I am not talking about making an entire analysis selection, but perhaps applying some event flags (like a trigger).

Thanks a lot for the help.

Hi @zbilodea
thanks for the reply. What I have in mind is something like this. I understand that now you can keep or drop the full branches. Now, in nanoAOD, there are boolean branches, like HLT_blahblah. So my question is if you can keep or drop a subset of the full branches based on that boolean condition. Is it more clear? I can try to explain more if you need.

Do you mean keep or drop TTree entries based on the per-entry boolean values (skimming), or keep/drop certain branches (slimming) based on which boolean branches are present?

I mean skimming. From what I understand, the current functionality only does slimming (from your definition)

Ah yes I see now! Thank you for clarifying, I will work on adding skimming!

I've added an option for branch skimming, it is the keyword argument "cut" (works like Uproot's "cut" parameter in uproot.iterate() and uproot.arrays()). Let me know if there are any changes I could make to improve this or if any issues come up! I'll add examples to the docs soon but here's one for the case you mentioned:
For using an HLT branch and keeping only branches that start with "Photon_":
hepconvert.copy_root(
        "destination.root",
        "nanoAOD_2015_CMS_Open_Data_ttbar.root",
        keep_branches=["Photon_*"],
        force=True,
        cut="HLT_Photon30",
    )


Bluetooth HCI SPI fault

Describe the bug
A clear and concise description of what the bug is.
I'm attempting to get the samples/bluetooth/hci_spi example working with my particle_argon board and encountering a usage fault. I believe it is coming from my overlay, however, I'm unsure how to verify if it is or if it's something else.
To Reproduce
Steps to reproduce the behavior:
Add the overlay file particle_argon.overlay to samples/bluetooth/hci_spi sample.
cd zephyr/samples/bluetooth/hci_spi
west build -p auto -b particle_argon .
west flash

particle_argon.overlay
&spi1 {
	compatible = "nordic,nrf-spis";
	status = "okay";
	sck-pin = <47>;
	mosi-pin = <45>;
	miso-pin = <46>;
	csn-pin = <31>;
	def-char = <0x00>;

	bt-hci@0 {
		compatible = "zephyr,bt-hci-spi-slave";
		reg = <0>;
		irq-gpios = <&gpio0 30 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>;
	};
};

Logs and console output
If applicable, add console logs or other types of debug information
[00:00:00.250,976] <dbg> bt_hci_raw.bt_hci_driver_register: Registered Controller
*** Booting Zephyr OS build zephyr-v2.6.0-2251-g9b6122d5ac9b  ***
[00:00:00.251,129] <dbg> bt_hci_raw.bt_enable_raw:
[00:00:00.251,647] <dbg> bt_ctlr_hci_driver.prio_recv_thread: sem take...
[00:00:00.251,678] <dbg> bt_ctlr_hci_driver.recv_thread: blocking
[00:00:00.251,678] <dbg> bt_ctlr_hci_driver.hci_driver_open: Success.
[00:00:00.251,708] <inf> bt_hci_raw: Bluetooth enabled in RAW mode
[00:00:00.251,739] <err> os: ***** USAGE FAULT *****
[00:00:00.251,770] <err> os:   Division by zero
[00:00:00.251,770] <err> os: r0/a1:  0x0bad0000  r1/a2:  0x20006b54  r2/a3:  0x00000001
[00:00:00.251,770] <err> os: r3/a4:  0x00000000 r12/ip:  0x00000005 r14/lr:  0x000184cb
[00:00:00.251,770] <err> os:  xpsr:  0x21000000
[00:00:00.251,770] <err> os: Faulting instruction address (r15/pc): 0x00017270
[00:00:00.251,770] <err> os: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
[00:00:00.251,800] <err> os: Current thread: 0x20000950 (unknown)
[00:00:00.757,751] <err> os: Halting system

This overlay also produces the same fault.
&spi1 {
	compatible = "nordic,nrf-spis";
	status = "okay";
	sck-pin = <33>;
	mosi-pin = <34>;
	miso-pin = <40>;
	csn-pin = <42>;
	def-char = <0x00>;

	bt-hci@0 {
		compatible = "zephyr,bt-hci-spi-slave";
		reg = <0>;
		irq-gpios = <&gpio1 11 (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>;
	};
};

On a side note, building the sample using the nrf51dk_nrf51422 board overflows.
cd zephyr/samples/bluetooth/hci_spi
west build -b nrf51dk_nrf51422 .

FAILED: zephyr/zephyr_prebuilt.elf zephyr/zephyr_prebuilt.map /home/parallels/project/zephyr/samples/bluetooth/hci_spi/build/zephyr/zephyr_prebuilt.map
: && ccache /home/parallels/zephyr-sdk-0.14.0/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc   zephyr/CMakeFiles/zephyr_prebuilt.dir/misc/empty_file.c.obj -o zephyr/zephyr_prebuilt.elf  zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj  -fuse-ld=bfd  -Wl,-T  zephyr/linker_zephyr_prebuilt.cmd  -Wl,-Map=/home/parallels/project/zephyr/samples/bluetooth/hci_spi/build/zephyr/zephyr_prebuilt.map  -Wl,--whole-archive  app/libapp.a  zephyr/libzephyr.a  zephyr/arch/common/libarch__common.a  zephyr/arch/arch/arm/core/aarch32/libarch__arm__core__aarch32.a  zephyr/arch/arch/arm/core/aarch32/cortex_m/libarch__arm__core__aarch32__cortex_m.a  zephyr/lib/libc/minimal/liblib__libc__minimal.a  zephyr/lib/posix/liblib__posix.a  zephyr/soc/arm/nordic_nrf/nrf51/libsoc__arm__nordic_nrf__nrf51.a  zephyr/subsys/bluetooth/common/libsubsys__bluetooth__common.a  zephyr/subsys/bluetooth/host/libsubsys__bluetooth__host.a  zephyr/subsys/bluetooth/controller/libsubsys__bluetooth__controller.a  zephyr/subsys/net/libsubsys__net.a  zephyr/subsys/random/libsubsys__random.a  zephyr/drivers/clock_control/libdrivers__clock_control.a  zephyr/drivers/console/libdrivers__console.a  zephyr/drivers/gpio/libdrivers__gpio.a  zephyr/drivers/spi/libdrivers__spi.a  zephyr/drivers/serial/libdrivers__serial.a  zephyr/drivers/entropy/libdrivers__entropy.a  zephyr/drivers/timer/libdrivers__timer.a  modules/hal_nordic/nrfx/libmodules__hal_nordic__nrfx.a  modules/segger/libmodules__segger.a  -Wl,--no-whole-archive  zephyr/kernel/libkernel.a  -L"/home/parallels/zephyr-sdk-0.14.0/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/thumb/v6-m/nofp"  -L/home/parallels/project/zephyr/samples/bluetooth/hci_spi/build/zephyr  -lgcc  zephyr/arch/common/libisr_tables.a  -mcpu=cortex-m0  -mthumb  -mabi=aapcs  -Wl,--gc-sections  -Wl,--build-id=none  -Wl,--sort-common=descending  -Wl,--sort-section=alignment  -Wl,-u,_OffsetAbsSyms  -Wl,-u,_ConfigAbsSyms  -nostdlib  -static  -no-pie  -Wl,-X  -Wl,-N  -Wl,--orphan-handling=warn && cd /home/parallels/project/zephyr/samples/bluetooth/hci_spi/build/zephyr && /usr/bin/cmake -E echo
/home/parallels/zephyr-sdk-0.14.0/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/zephyr_prebuilt.elf section `noinit' will not fit in region `SRAM'
/home/parallels/zephyr-sdk-0.14.0/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.bfd: section .intList VMA [0000000020008000,0000000020008097] overlaps section noinit VMA [0000000020006638,0000000020009651]
/home/parallels/zephyr-sdk-0.14.0/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `SRAM' overflowed by 5714 bytes
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /usr/bin/cmake --build /home/parallels/project/zephyr/samples/bluetooth/hci_spi/build

My west was behind, sample works fine


Connect to custom API endpoint

I would like to add mempool-cli to lightning-shell. The problem is that it tries to connect to mempool.space's API, whereas I would like to pass it an API endpoint to connect to, which would be the API of the mempool instance running on the user's Umbrel node.
Adding this issue here, in case you guys get to it faster. Otherwise I'll probably get to do it eventually. This is a really useful app to have on one's node!

I agree, it's very useful. I'll try to implement it


magika: init at 0.5.0

Description of changes
Magika is  an AI powered fast and efficient file type identification released
by Google (see
https://opensource.googleblog.com/2024/02/magika-ai-powered-fast-and-efficient-file-type-identification.html).
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
[x] sandbox = true

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

Note: this depends on #291461

@mihaimaruseac you also have https://github.com/NixOS/nixpkgs/pull/291461, which is the cause of mass rebuilds.
do you want to proceed with those both PR's ?

yes, you can change to master
master however doesn't yet have required version of python-dotenv
you can track python-dotenv PR here
https://nixpk.gs/pr-tracker.html?pr=291461
this explains about staging branch workflow
https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#staging
from looking at changelog of python-dotenv, you should be able to get magika to work with python-dotenv from master

Forgot about this until now. I see it now python-dotenv bump reached master so I'll rebase this one without any other changes. Thank you

bin/magika seems to be broken
./results/python311Packages.magika/bin/magika
Traceback (most recent call last):
  File "/nix/store/8dd9sqp5vvvjzww0a9iw46vf5jv32vw7-python3.12-numpy-1.26.4/lib/python3.12/site-packages/numpy/core/__init__.py", line 24, in <module>
    from . import multiarray
  File "/nix/store/8dd9sqp5vvvjzww0a9iw46vf5jv32vw7-python3.12-numpy-1.26.4/lib/python3.12/site-packages/numpy/core/multiarray.py", line 10, in <module>
    from . import overrides
  File "/nix/store/8dd9sqp5vvvjzww0a9iw46vf5jv32vw7-python3.12-numpy-1.26.4/lib/python3.12/site-packages/numpy/core/overrides.py", line 8, in <module>
    from numpy.core._multiarray_umath import (
ModuleNotFoundError: No module named 'numpy.core._multiarray_umath'

we should also expose magika as top level attribute via
toPythonApplication function
https://nixos.org/manual/nixpkgs/stable/

Oh, something might have broken during the rebase. I'll take a look later today and rerun all tests to make sure it works again.
Thanks for the help!

Added the toPythonApplication call and checked that I can build it again locally:
[nixpkgs] λ nix-build -A python3Packages.magika
/nix/store/hgmxpa5zv6x8fynca0pk3xsfqmbpy2nk-python3.11-magika-0.5.0
[nixpkgs] λ result/bin/magika CONTRIBUTING.md
2024-03-12 06:15:38.094210972 [W:onnxruntime:Default, onnxruntime_pybind_state.cc:1983 CreateInferencePybindStateModule] Init provider bridge failed.
CONTRIBUTING.md: Markdown document (text)

so python 312 package works
/python312Packages.magika/bin/magika --help
2024-03-13 20:03:45.748844535 [W:onnxruntime:Default, onnxruntime_pybind_state.cc:1983 CreateInferencePybindStateModule] Init provider bridge failed.
Usage: magika [OPTIONS] [FILE]...
but magika is still broken
 /magika/bin/magika --help
Traceback (most recent call last):
  File "/nix/store/8dd9sqp5vvvjzww0a9iw46vf5jv32vw7-python3.12-numpy-1.26.4/lib/python3.12/site-packages/numpy/core/__init__.py", line 24, in <module>
    from . import multiarray
  File "/nix/store/8dd9sqp5vvvjzww0a9iw46vf5jv32vw7-python3.12-numpy-1.26.4/lib/python3.12/site-packages/numpy/core/multiarray.py", line 10, in <module>
    from . import overrides
  File "/nix/store/8dd9sqp5vvvjzww0a9iw46vf5jv32vw7-python3.12-numpy-1.26.4/lib/python3.12/site-packages/numpy/core/overrides.py", line 8, in <module>
    from numpy.core._multiarray_umath import (
ModuleNotFoundError: No module named 'numpy.core._multiarray_umath'

@mihaimaruseac looking at the stack trace of error, it looks like when built for python 3.11 its importing numpy for 3.12
something in the dependecy tree is built for python 3.12 only

I'll take a look. I need to remember to test for multiple versions of Python.
Thank you for the review!

@mihaimaruseac hey, i found what was wrong,
the issue is with shell that nixpkgs-review produces, otherwise magika works for me in python 3.11
currently nix ci only runs builds for python 3.11 and 3.12, support for other versions is nice, but not necessary

Oh, that's a good find. I saw the hash for my version and the hash for yours was different so I was checking to see if maybe my nixos version was causing issues.

@ofborg build python3Packages.magika

aarch64-linux build fails

It seems onnx fails to initialize its runtime, but I thought this would be caught by other packages that depend on it. Unfortunately I cannot debug further, so I've used meta.broken to skip (if I read the manual correctly).

@mihaimaruseac thank you !  almost there  !
can you update last two comm messages to adhere to contribution guidelines ( or squash, up to you )
then we just wait for CI to pass, and i think we are good to merge

Thank you for the patience and reviews. I squashed it back to 2 commits and fixed the last breakage


Get children legal entity by MSP

MSP must be able to get list of children legal entities. According to this we need to have new WS base on logic and spec

[x] implement
[ ] test

https://edenlab.atlassian.net/wiki/spaces/EH/pages/635273505/LE+Reorganization+API

tested


Changes to Procfile are not reflected in app#services view

The command value in app#services route is not updated after changes to the app's Procfile.
Thanks @evan-007

I just pushed a second build with the same config and the command was updated in the dashboard.

Tested this repeatedly on production and am unable to reproduce.  I believe the issue is that we don't reload services from the server on each page view and instead load from memory.  A hard refresh on the services page always seems to render the correct Procfile command.
I'll close this and open a new issue for upgrading to Ember Data 2.0, which has background loading of stale resources.


@nstudio/nativescript-exoplayer renaming and documentation updates

Over the past few months I have noticed some confusion around using video with nativescript. The main issue stems from exoplayer and videoplayer both being used but not clear which should be used or why. The idea would be to potential renaming @nstudio/nativescript-exoplayer using the word "video" but being clear that it is more robust and requires the exo libraries with it.
It would be nice to also include some sort of video section in the UI docs or including it in the plugins section of the official nativescript website. This would ideally solve some confusion around if nativescript supports video and which plugin would be best for your project.
I believe it would be helpful if it is more clear that nativescript can support video and does, as well as give some information around which plugin might be better for the project someone is currently working on. This might also create more interest in PRs for the plugins as they will be more visible.

I'm still very interested in finding a good way to inform the community through the docs about the different video players(as well as improve them so new community members can get started with video quickly). When I started my {N} journey, I was very confused as to which player to use. I tested out random marketplace players and several other that were in the community.
The goal:
Solve confusion around what video player to use for what level of technical need and where to find the plugins. For new comers and for devs that have been around {N} for a bit it can still be confusing.
What I understand now:
The @nstudio/nativescript-exoplayer and @nstudio/nativescript-videoplayer are the two best video solutions.(If there is a better solution for NativeScript I'm all ears!) Both plugins use Apple AV Player for iOS but different players for Android. For Android, @nstudio/nativescript-videoplayer is the "more basic" version as the Android MediaPlayer doesn't have many features. @nstudio/nativescript-exoplayer uses Google ExoPlayer which is the "more advanced" version with much more features and is better for streaming video.
I get the reason for having both plugins, so that devs that just need a slimmed down video player use @nstudio/nativescript-videoplayer. Then the devs that need more features and are fine with the added packages that come with exoplayer, use @nstudio/nativescript-exoplayer.
A possible solution:
I still think there is some value in allowing the choice between the 2 different Android players, having 2 plugins makes sense. Wether they belong under the @nativescript or the @nstudio umbrella idk what would be best. The biggest area of clarity could come from the naming and documenting of the plugins. I wouldn't know how to accomplish this idea entirely but I am putting it out here to get feedback and discussion going.
Create a @nativescript/basic-videoplayer (Apple AVPlayer and Android MediaPlayer) and a @nativescript/advanced-videoplayer (Apple AVPlayer and Google ExoPlayer). Add links in the plugin section of the {N} docs like other plugins have. Then in each repo, add somewhat concise wording to the readme describing what the main features/benefits of each. This could also be partially documented in a blog post or in the {N} docs.
I believe doing something like this would create more community awareness, allow people trying out NativeScript to see how easy it could be to get video going quickly and likely lead to better plugins overall. If this type of idea is unwanted or there are reasons why it shouldn't happen I'd be interested to hear those as well. I'm interested in finding a good solution to move forward with and looking for other's opinions too!
I'm not sure who to chat with so I'm tagging @nstudio @NathanWalker

Great thoughts here @brianrclow thanks for outlining this. I think the naming could be:
Basic: @nativescript/video
Advanced: @nativescript/video-advanced
The advanced naming probably makes sense because the API would also be more advanced and thorough which would likely prove the value of having both since not all cases would need the more advanced player.

Thanks @NathanWalker Yea, I think naming like that would make more sense. What would be the first steps in creating a timeline to accomplish something like this? I would be interested in helping out with documentation and figuring out how to add a few more features to the plugins.

Big help! You could fork https://github.com/NativeScript/plugins
Run ‘npm run setup’ then:
npm run add

video

npm run add

video-advanced

and begin moving the plugins in there - once readmes are updated in there we have nightly scripts that would add them to the docs

Okay great, thanks for the direction. I'll get this started in an upcoming sprint, need to balance paid work and OSS.

@NathanWalker I've forked, created the new packages under the @nativescript scope and started adding in the readme's. Creating a new plugin in that monorepo is pretty slick and clean. Before I get too far, I wanted to ask you some questions:

What would be the best way to transfer the actual plugin code over? Should I literally be copy and pasting?
Would there be a way to still list the contributors if I just bring the code over? I still want to give credit where credit is due. I know that some packages list contributors at the bottom and others do not. Not sure what the best direction to go is.
I also am curious about the backwards compatibility with {N} 6 or 7 and how/if this process could still support the older {N} versions?

Here is where I am currently working on it: https://github.com/brianrclow/plugins/tree/video-advanced
I'm going to continue to add to the readme's and try to understand some of the code better so I can make a smoother transition. Any advice is appreciated, thanks!

Also - I've noticed that all of the commits are using the conventional commit pattern, is there a place where Nativescript has the guidelines around that for community members to understand how to best commit their code? I don't want to do it wrong and mess up things. 😅😅

What would be the best way to transfer the actual plugin code over? Should I literally be copy and pasting?

Your fork looks like great direction - yes, you can copy/paste into that new package, @nativescript/video-advanced in your workspace fork.

2. Would there be a way to still list the contributors if I just bring the code over? I still want to give credit where credit is due. I know that some packages list contributors at the bottom and others do not. Not sure what the best direction to go is.

Best way is for us to mention in the README here for the exoplayer the proper credit and keep the commits here for history. That way it's clear where the credit is due and how to find it. The new package can also link and mention the original for proper history investigations.

3. I also am curious about the backwards compatibility with {N} 6 or 7 and how/if this process could still support the older {N} versions?

The plugin workspace fork you have is only for {N} 7 and above. All plugin workspaces support 7 and above only.

Also - I've noticed that all of the commits are using the conventional commit pattern, is there a place where Nativescript has the guidelines around that for community members to understand how to best commit their code? I don't want to do it wrong and mess up things.

Great question, we try to follow this format: https://www.conventionalcommits.org/en/v1.0.0/
It's a great standard used across broad open source projects. You don't have to adhere precisely all the time as when maintainers merge pull requests, squash/commit option is often used which gives the maintainer the opportunity to reword the commit (squashing all commits from the pull request into one) into an acceptable format for main branch cleanliness.

@NathanWalker @brianrclow about the naming / split of the 2 plugins . wouldn't it be better to make exoplayer an "extension" to the other plugin?
the idea being behind that is to have same base code same api...
the extension would depend on the base plugin and simply override/subclass the android part (would be possible for iOS too).
just my thought

I'll leave my thoughts here as well:
Most of the time, simply crediting the prior art/work in the repo/readme is enough (though do always check the license, and if necessary include a copy of it).
Preserving git history is possible, I have done it before, however it requires quite a bit of git trickery, and it's not perfect. An example where I did this:
https://github.com/NativeScript/nativescript-cli/tree/master/packages/doctor
pulled in from:
https://github.com/NativeScript/nativescript-doctor
The upside is that all the prior commits are preserved, however merge commits now point to incorrect pull requests, since #1 etc now points to the PR#1 in the CLI repo and not the doctor repo. That's something I wasn't able to fix, since rebasing doesn't work on merge commits as far as I could tell from various sources.
Is it worth the trouble? Maybe? Not really...
About organizing and splitting, I'd agree with @farfromrefug's take that it might make sense to have a base plugin with a nice api, and make the underlying player implementation swappable with a single call in main.ts or something simple like that.

I was considering this reciently and I think the license point is important, and depending on the licence does appear to place specific requirements on the copy.  for example the  license governing exoplayer here is apache 2 and explicitly states ( among other things) in section 4 "(a) You must give any other recipients of the Work or Derivative Works a copy of this License".
My reading of this is the contents of https://raw.githubusercontent.com/nstudio/nativescript-plugins/main/LICENSE must be brought accross to the new repo, and furthermore must end up in the npm package. Also there are instructions for indicating what files are changed etc.  so there are requirements placed on any copy by the license.
The reason I was thinking about it was that I was considering similar to this, bringing https://github.com/EddyVerbruggen/nativescript-secure-storage into nativescript plugins and rewriting the android portion to use EncryptedSharedPreferences. ( it is MIT license, which is simplier but also requires the original license travels with the code ).
I find this not very straight forward, but it would seem to me to be important to understand ( which I probably do not fully )

@brianrclow looks like this escalated quickly 🤣  ... some considerations here, great input from everyone.

Thank you all for the feedback!
@NathanWalker I will get started on bringing over exoplayer to @nativescript/video-advanced and I'll add the contributors tot he readme. Support for 7 and above is great, I should probably make that clear and link back to the other repo as well. I can start to use the conventional commit pattern (we already loosely use it at work, so it is familiar).
@farfromrefug I'm not against making the exoplayer an "extension" to the other plugin like you say. I haven't seen this done before though and I wouldn't know how to accomplish that. There is some value in only maintaining "1 iOS side" instead of duplicating that in both the "video" and "video-advanced" versions. How might you suggest going about the extension process? Is there another plugin that follows this I could check out?
@rigor789 Preserving history sounds like it would be a bit of a pain and I'm not sure if I'm up for it. Thanks for sending those links though. I would still want to follow the licenses and give credit to prior work done. As for the plugin extension idea/implementation. Do you have any example of one currently with a similar setup? I think that idea would simplify things further, which is my goal. Having a single plugin that has the capability of changing the Android native implementation sounds like a better solution than 2 plugins that have the same iOS native implementation.
@jcassidyav Good call on the license. It's something I wanted to be careful about. The nativescript-videoplayer license is MIT and the nativescript-exoplayer license is Apache License 2.0. It would appear that the MIT license is easier to deal like you say. I would need to look into what happens if I would bring the 2 plugins together into a single source of "video plugin" truth for NativeScript. Not sure which license to use in that case. Definitely not straight forward though.
I'm very interested in this project, both because of an app I have in production that utilizes video and for the greater community moving forward. I think making video clear to use and adding important features will be a good improvement to the developer experience with NativeScript, especially for newer developers coming from a web background.
I'll definitely need to lean on some community members/maintainers for this as time goes on as I've never written or assisted with a plugin like this before!


Suggest consumable inventory values based on a Procedure

Let's assume that a procedure has been selected before. Rather than requiring the user to setup some template with a given set of items and quantities, why not predict / suggest the the items and quantity based on previous selections, at first generally; but overall for a given procedure. So for instance, the system would suggest the consumables for a PMR (neglected clubfoot treatment) based on other PMR procedures.
Alternatively, that same "predictive" data could suggest templates for creation.

My idea. Not a requirement. Closing for now.


[GSSoC'23] Adding a translator.

Describe the project you want to add with tech stack
We can add a translator which can translate full sentences from one language to another using HTML, CSS and JS.
Expected behaviour
A person can translate the sentence from their native language to another language using this project, we can also provide text to speech option also.
Screenshots (optional)

Additional context (optional )
Can you assign this to me ?

please assign me this issue

can u assign me this isssue


Cannot inject parameters as Environment Variables in datasource section of deployment.toml

Describe the issue:
Environment variable injection seems to not be taken into account in the [[datastore]] section of the deployment.toml.
An Unauthorized error occurs when accessing the WSO2IS_CONSENT_DB, while other databases such as the [database.user] work.
Replacing the $env{MYSQL_PASSWORD} placeholder with the actual content works. Could it be that the [[datastore]] section does not allow environment variables?
How to reproduce:
Configure the following in the deployment.toml, and set a value to the environment variable MYSQL_PASSWORD
[database.user]
    type = "mysql"
    url = "jdbc:mysql://mydb:3306/WSO2IS_SHARED_DB?autoReconnect=true&useSSL=false&allowPublicKeyRetrieval=true"
    username = "wso2carbon"
    password = "$env{MYSQL_PASSWORD}"

[[datasource]]
    id="WSO2CONSENT_DB"
    type = "mysql"
    url = "jdbc:mysql://mydb:3306/WSO2IS_CONSENT_DB?autoReconnect=true&useSSL=false&allowPublicKeyRetrieval=true"
    username = "wso2carbon"
    password = "$env{MYSQL_PASSWORD}"

The users database is accessible while the consent db is not.
Expected behavior:
The $env{MYSQL_PASSWORD} is replaced with the value of the environment variable, and the WSO2IS_CONSENT_DB is being accessed with its value.
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 5.10.0
OS: Linux
Database: MySQL
Userstore: JDBC

Optional Fields
Related issues:
Could it be related to this issue? https://stackoverflow.com/questions/68257033/wso2-mi-injecting-parameters-as-environment-variables-in-xa-datasource-file-doe

Fixed with https://github.com/wso2/product-is/issues/7781


PSR-1

Renamed constant __DEFAULT in uppercase to support PSR-1.
Review https://github.com/artkonekt/enum/pull/3

Closed in favour of #7


Adding google auth to udmif and enhancing IaC

What's the status of this PR?  Is it waiting for review or... ?

It is waiting for review.
Thanks,

It is waiting for review.
Thanks,
Stephane
From: Trevor @.>
Date: Monday, May 16, 2022 at 8:54 AM
To: faucetsdn/udmi @.>
Cc: Stephane Levert @.>, Author @.>
Subject: Re: [faucetsdn/udmi] Adding google auth to udmif and enhancing IaC (PR #314)
What's the status of this PR? Is it waiting for review or... ?
—
Reply to this email directly, view it on GitHubhttps://link.edgepilot.com/s/9496940c/K8DUBa1pHEyJVY0SFWetXw?u=https://github.com/faucetsdn/udmi/pull/314%23issuecomment-1127636595, or unsubscribehttps://link.edgepilot.com/s/691ce5f0/1qchJI8S0Ea5jkgoe7KG8A?u=https://github.com/notifications/unsubscribe-auth/AMIAKT3KX7AV7FGZ5MYHHVTVKJAP3ANCNFSM5UQHARRA.
You are receiving this because you authored the thread.Message ID: @.***>
Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning.


feat: initial working vscode web extension

Partially addresses #5. There are a few cascading changes here that are related, but may not look like it:

Getting the build system unified ran into an issue with vite v4
Upgrading vite to v5 implied upgrades to vitest, sveltekit
vitest had some breaking changes (snapshots, rejected promises)

I confirmed github.dev is using version 0.0.12. I'm getting this error when I click on a link:

I believe the correct URL would be /pi-base/data/properties/P000188.md

Offtopic: one day I should pick your brain on your pattern of using git push -f.

I like a linear history that tells a story, so will try to git commit --amend liberally to make sure that PRs contain individual, atomic commits that could be independently applied. A lot of times this happens entirely on my machine and nobody notices, but if I'm concerned about external build stuff or integration testing, I push regularly along the way (hence a lot of --force pushing). I generally limit that to PRs that are in draft, and try to make additive changes after I reasonably believe someone has reviewed the existing work.

I confirmed github.dev is using version 0.0.12. I'm getting this error when I click on a link:

Just to confirm, you're looking at https://github.dev/pi-base/data and clicking on the link that shows up in the markdown hover preview, right? (Or – if you cmd+click on the actual ID itself or use VSCode's "go to definition", are those working as expected for you?)

... additive changes ...

like 113e67d86603b2bfb234d9cdc56579567c6ab8e9

Well, the link isn't broken, but now it's not even there. 🙃

Yeah, working on debugging it now. I have no idea why it would just silently not show up in the web, but work fine locally. It may take be a bit to get set up with some kind of process for remote debugging; I'm going to move this back to draft for now.

@StevenClontz – alright 53b3c7c30420cea8f7ce48f29fe587058ae03a41 should fix the links in hover text. The published extension seems to be working for me on github.dev but failing to activate entirely in a dedicated codespace. 🫠 Is that also what you're seeing?

github.dev
Missing link (although clicking the link at the top does nothing - that's the same file as the item itself).

Clicking compact here successfully opens the file: 🚀

codespaces
For whatever reason it did not install in my browser automatically (CORS thing seems new too but I haven't looked into it):

one-click install:

Nothing at first:

Refresh helps:

Clicking $T_3$ here works:

This was (squashed) merged in via #160.


What is the recommended value of retryAttempts parameter?

@mrniko We are using redisson with AWS Elasticache. Due to some patch activity done internally we faced an issue and got a recommendation from your end to increase the retryAttempts parameter. Can you let us know what is the recommended value for the same?

that depends on use case.


Add function to check if OpenMP is working

I haven't written in C language for a while. This is how I check if OpenMP is working on the compiled pyccl. Checked on macOS 10.15.7 with Apple Clang with OpenMP disabled and homebrew-installed Clang 15, the function is working as expected even if the environment variable "OMP_NUM_THREAD" is set to 0.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 5 (20.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.08%) to 97.424%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pyccl/pyutils.py
1
5
20.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.08%

Covered Lines:
4841

Relevant Lines:
4969

💛  - Coveralls

Is the add_link_options("LINKER:-lomp") necessary? This should be automatically added if openmp is found. Can you add file(GENERATE OUTPUT "omp_lib_generator.txt" CONTENT $<$<BOOL:${OpenMP_C_FOUND}>:OpenMP::OpenMP_C>) to the CMakeLists.txt and check if there's any output? Setting set( CMAKE_VERBOSE_MAKEFILE on ) also shows the full build command and should show if the openmp library is added to the linker.

This is what I got in the file
OpenMP::OpenMP_C

This is the 1000th tag! 🎉🎉🎉

The c unit tests in ci on ubuntu did not run any tests (or the log did not show it?). Is this behaviour expected?
https://github.com/LSSTDESC/CCL/actions/runs/3237240260/jobs/5304053146#step:10:18

Just want to leave a note for Apple Clang users with homebrew-installed libomp on macOS 10.15. If the installation failed or there are errors when python tries to import pyccl: In the shell, execute export LDFLAGS="-L/usr/local/lib -lomp" and export CFLAGS="-I/usr/local/opt/libomp/include" before pip install . (or python setup.py install).

@hsinfan1996 @tilmantroester can I check where we stand on this PR?

@hsinfan1996 @tilmantroester can I check where we stand on this PR?

The functions checking OpenMP version and threads are done. However, some Apple Clang compilers (e.g. on my machine running MacOS 10.15) cannot link homebrew-installed libomp, but I gave up on fixing this. I am happy with the changes to CMakeLists.txt that @tilmantroester made. If there is no more to add to CMakeLists.txt, then this PR is ready for review.

OK, can we run the tests and check they pass?

@tilmantroester you've paid more attention than me to this. Are you happy to approve?


JAX tracer supporting user-defined tape transformation

In this PR we aim at making it possible to apply user-defined transformations to a tape containing Catalyst quantum operators. The main difficulty is related to the fact that in Catalyst we only trace programs rather than execute them so the operations on tape are: (1) filled with abstract parameters, (2) include control flow operations containing nested tapes.
The approach we are working on would essentially split the tracing process into classical and quantum parts. In order to do so, we store JAX tracing contexts and re-enter them as needed. We described the idea and the associated risks in the internal document.
Tasks:

[x] Prototyping is done
[x] Core tracing framework is implemented
[x] Catalyst extensions are ported to the new tracing framework

[x] Control flow ops (For-loops, WhileLoops, Conditionals, Adjoint)
[x] CustomOps
[x] QubitUnitary
[x] Mid-circuit measurement
[x] Measurements (Sample, ExpVal, Counts, Probs, State)
[x] Observables (Compbasis, Paulis, Hadamard, Hermitian,Tensor,Hamiltonian)
[x] Gradient primitives (Grad, JVP, VJP)

[x] All kinds of execution pipelines are supported

[x] Both qjit and qnode
[x] Just qjit (no quantum parts)
[x] Just qnode (interpretation)

[x] Optimizations are ported

[x] Qubit insert/extract state preservation (quantum register tracing optimisation)
[x] Differentiation-specific procedures (JVP/VJP/Grad) are reviewed and ported

[x] All tests pass locally
[ ] Code is clean

[x] Temporary and unused source files are removed
[x] JAX internals are collected in a separate utility file
[x] Tracing context classes are unified
[ ] Docstrings are ported or created
[ ] Remaining FIXMEs are fixed
[ ] CodeFactor is happy

[x] Latest version of Catalyst is merged into the PR

[x] Main merge conflicts are solves
[x] Tests are fixed

Hi colleagues, I think this PR approaches the ready state. Some docstrings are not here yet, but I think I can ask for technical review already. @dime10 @erick-xanadu


[backport]New style CReLU

#3506

jenkins, test this please.

jenkins, test this please.

@unnonouno It seems like the doctest keeps failing on TestReLU due to strict tolerances.

jenkins, test this please.

LGTM.


"Add code" button and markdown backticks seem to be interfering

This is based on feedback from Abbey. There seems to be something is not quite right when adding/editing the code block.

To create a code block, it looks like you can type three backticks and the programming language and then type your code - but when I type three backticks to end the code block, it doesn't end it - it keeps formatting it like code

pressing the </> button stopped that formatting - but I think we need to enable markdown syntax where a code block can be "finished" by just typing the three backticks. Many of our authors use markdown to write their articles.

To create a code block, it looks like you can type three backticks and the programming language and then type your code - but when I type three backticks to end the code block, it doesn't end it - it keeps formatting it like code

This is because the content is automatically ended with three backticks, meaning you are in the middle of the surrounding backticks.

pressing the </> button stopped that formatting - but I think we need to enable markdown syntax where a code block can be "finished" by just typing the three backticks. Many of our authors use markdown to write their articles.

To exit the code formatting you need to press Command + Enter.

I believe this behaviour is same as the one in Ghost.


Add sample repos to eventing PR query

The query to list the open eventing PRs, misses the sample-source and sample-controller repos. This PR addresses it and adds those repos to the query.

@pierDipi WDYT about adding them too? They are probably not needed for the releases, but keeping them in these cycles in a good shape probably doesn't hurt. Feel free to close it, if you don't see a value...

They are needed for the release

/lgtm


cursor.excutemany  error

Please first make sure you have looked at:

Documentation: https://github.com/mkleehammer/pyodbc/wiki
Other issues

Environment
To diagnose, we usually need to know the following, including version numbers.  On Windows, be
sure to specify 32-bit Python or 64-bit:

Python: Python3.8
pyodbc: 4.0.30
OS: mac os
DB:
driver:ODBC Driver 17 for SQL Server

Issue
Often it is easiest to describe your issue as "expected behavior" and "observed behavior".
('22001', '[22001] [Microsoft][ODBC Driver 17 for SQL Server]String data, right truncation (0) (SQLParamData)')

No error will be reported when using cursor. execute

That error message can have several causes. Please post a minimal reproducible example to illustrate your particular usage case.

The problem has been resolved because of the wrong field type


PR: Change colors for tour dialog in light mode

Description of Changes

[ ] Wrote at least one-line docstrings (for any new functions)
[ ] Added unit test(s) covering the changes (if testable)

[x] Included a screenshot or animation (if affecting the UI, see Licecap)

Changed colors  pf background and buttons in the tour dialog for Spyder's light mode

Issue(s) Resolved

Fixes #14203
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:
Juanis2112

Hello @juanis2112! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/app/tour.py:

Line 1441:11: E111 indentation is not a multiple of four
Line 1442:11: E111 indentation is not a multiple of four
Line 1444:11: E111 indentation is not a multiple of four
Line 1445:11: E111 indentation is not a multiple of four
Line 1506:11: E111 indentation is not a multiple of four

When we designed the tour dialog we didn't actually take into account the colors for the light mode. What do you think about this @isabela-pf. I used two of the colors of the palette for the buttons.

Thanks for catching this! It got buried in a to do list somewhere.
I think in meetings we had talked about still having buttons having light text on dark buttons in light mode (like shown in #13) with buttons being #1A72BB and #60798B. That would look like this:

@isabela-pf, I really like your suggestion!
@juanis2112, please rebase on top of the latest 4.x to get to our tests.

Thanks @isabela-pf. I updated the screenshot according to the latest changes and rebased @ccordoba12.


0.9.8 - Cannot create navigation bin file if import by Create one Blueprint asset

Hi, everyone.
I am new to carla. I am using 0.9.8 and I want to spawn walker on my own map.
What I have done:
When I import my test.fbx into carla Unreal Editor by Create one Blueprint asset, FbxScene blueprint is generated and all StaticMeshes are in it. I cannot generate the pedestrian navigation bin file.
When I import test.fbx into Editor by Create Level Actors, FbxScene is not generated (SceneNode is generated) and I succeed in generating bin file and spawning walkers on sidewalk (using the provided RecastBuilder).
However, I find that the latter import method loses RoadRunnerTrafficJunction information compared to the former method.
My question:
Can I generate pedestrian navigation bin file while importing by Create one Blueprint asset?
I think this should be possible, because all tutorials I found choose Create one Blueprint asset.
I'm confused because in those tutorials' screenshots, road static meshes appeared in World Outliner, while my static meshes are all in FbxScene blueprint class.
Thank you.

I deleted the Sidewalk StaticMesh in FbxScene and added it (it is in Static folder) again in World Outliner.
After that I succeeded in creating pedestrian navigation file and spawning walker on sidewalk.
However, I still want to ask why navigation bin file cannot be created with FbxScene holding the Sidewalk StaticMesh.

@bernatx could you help with this?

Hi,
Have you any file to share so we can test it?
I suppose the FBX has something that has problems when it is imported to Unreal (we use the FBX importer from Unreal).


feat: implement RegisterNodeService for UmeeApp

Description
Integrates new chain query service.
This is a new addon from SDK 0.46.3

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added ! to the type prefix if API or client breaking change
[ ] added appropriate labels to the PR
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

seams we need to merge https://github.com/umee-network/umee/pull/1501 first


Refactor client to reduce sonar bugs

Replacing the System.out with a more delicate printer is more graceful, though I wonder how to do this. Advices are welcomed.


How do nodejs-polars track/maintain feature-parity with py-polars?

Dear @universalmind303
I work on implementing polars for R and very much see nodejs-polars as the example to follow. Especially when using rust-polars core features, not in the public polars crate, I found the solutions in nodejs-polars.
My unit tests likely will catch implementation bugs, but whenever py-polars makes a behavior change, it requires I manually notice this and update/add such behavior too. I was asked what is lifecycle policy of rpolars, and I'm very interested to learn of your thoughts and experiences of maintaining nodejs-polars along the main projects rust-polars and py-polars.
best

related #6

@sorhawell if you plan to keep API and behavioral parity as close as possible to python polars would you consider moving the repo under the pola-rs namespace?
This likely will help discovery and attraction help by the community.

As far as feature parity goes. Ideally i'd like to write some scripts that generate a coverage map between node & python features. We know some features will be much more difficult to support in JS (if not impossible). (lambdas, and interop methods [pandas, arrow]). But until we have some automated way of tracking this, it is a manual task to update the features to match py-polars.

@ritchie46  Thanks, that would be super cool and potentially very helpful :) !

@universalmind303  Yeah maybe such a script would be a good start. I could track what python/rust functions in py-polars directory has been altered between releases. That might be a good checklist functions I should eyeball for changed behavior before bumping the polars dependency version. I try also moving towards similar file structure and file content order as py-polars for the sake of sanity.

Lambdas thread-safety was difficult for me to implement in r-polars as R is very thread unsafe and has no GIL concept. I keep the main thread to communicate with R and handle  all incomming lambdas-requests from the polars threads(pool). If lambda-request buffer is empty the R thread just sleeps or occasionally checks for user-interrupts. Maybe the nodejs lambdas challange is something completely different  :)


ZSH support

Closes #28

   zsh  % echo 1             ✔
fg: no current job

Closing for now, I may reopen this in the future(unlikely)


Work constants are incorrect

Work and Target have an inverse relationship, so min work should equal max target.
println!("{:?}", Target::MAX.to_work());
println!("{:?}", Work::MAINNET_MIN.to_target());
println!("{:?}", Target::MAX);
println!("{:?}", Work::MAINNET_MIN);
println!("{:?}", Work::MAINNET_MIN.to_target().to_compact_lossy().to_consensus());
println!("{:?}", Target::MAX.to_compact_lossy().to_consensus());

Expected:
Work(0x0000000000000000000000000000000000000000000000000000000100010000)
Target(0x00000000ffff00000000ffff00000000ffff00000000ffff00000000fffeffff)
Target(0x00000000ffff0000000000000000000000000000000000000000000000000000)
Work(0x0000000000000000000000000000000000000000000000000000000100010000)
486604799
486604799

Got:
Work(0x0000000000000000000000000000000000000000000000000000000100010001)
Target(0x0000000000000000000000000000000000000000000000000000000100010001)
Target(0x00000000ffff0000000000000000000000000000000000000000000000000000)
Work(0x00000000ffff0000000000000000000000000000000000000000000000000000)
83951617
486604799

This diff is what got me from Got to Expected... without the fix to the inverse function, the Target was slightly off.
diff --git a/bitcoin/src/pow.rs b/bitcoin/src/pow.rs
index 99e50014..09eb9466 100644
--- a/bitcoin/src/pow.rs
+++ b/bitcoin/src/pow.rs
@@ -71,7 +71,7 @@ pub struct Work(U256);

 impl Work {
     /// Lowest possible work value for Mainnet. See comment on [`Params::pow_limit`] for more info.
-    pub const MAINNET_MIN: Work = Work(U256(0x0000_0000_ffff_0000_0000_0000_0000_0000_u128, 0));
+    pub const MAINNET_MIN: Work = Work(U256(0, 0x100010000));

     /// Lowest possible work value for Testnet. See comment on [`Params::pow_limit`] for more info.
     pub const TESTNET_MIN: Work = Work(U256(0x0000_0000_ffff_0000_0000_0000_0000_0000_u128, 0));
@@ -382,8 +382,7 @@ impl U256 {
             return U256::ONE;
         }

-        let ret = !*self / self.wrapping_inc();
-        ret.wrapping_inc()
+        !*self / self.wrapping_inc()
     }

     #[cfg_attr(all(test, mutate), mutate)]

I noticed this when making a fix PR for the next target PR.

Thanks for raising the issue, you are definitely correct that the consts are incorrect since currently this assertion holds
assert_eq!(Work::MAINNET_MIN.0, Target::MAX.0);

Where as, as you correctly point out, it should be
assert_eq!(Work::MAINNET_MIN.to_target().0, Target::MAX.0)

That is my bad, I wrote that.
Anyways, what I'm not so sure about is what the inverse function should be.

I cannot remember where in Core I took the algorithm from
I don't know if the algorithm in the rustdoc is correct or not, I assume I copied it from Core somewhere

The code implements the algorithm in the rustdoc, if we want to change the algo we have to work out what it should be.
Lesson learned: next time we copy stuff from Core we should have a permalink to the code on github.

Lesson learned: next time we copy stuff from Core we should have a permalink to the code on github.

Heh, great lesson :).

Anyways, what I'm not so sure about is what the inverse function should be.

The relationship between work and target is pretty straightforward; they are multiplicative inverses except that one gets multiplied by some particular constant (2^32 I think? Don't remember). It should be easy to find and link to this code in Core.
The complicating factor is in to_compact_lossy which encodes target values in the bits field of blockheaders. As the name implies, this encodes the 256-bit target in a 32-bit binary floating-point format and therefore loses a ton of information. Some values can be encoded exactly. Our min/max values should all be exactly-encodable values.


backport: When the manager started, it reports failed to release lock

Need to backport the fix for #1379

Verified on v1.0.2-rc1
Validation - Passed
Tested with 3 worker nodes, the avg. time taken between the below logs is 2.33 secs. The minimum time taken is 0 sec and max time taken 6 secs.
Tested with 32 worker nodes, the avg. time taken between the below logs is 52.5 secs. The minimum time taken is 0 sec and max time taken 160 secs.
time="2020-08-13T03:58:56Z" level=info msg="Start overwriting built-in settings with customized values"
time="2020-08-13T03:58:56Z" level=info msg="cannot list the content of the src directory /var/lib/rancher/longhorn/engine-binaries for the copy, will do nothing: Failed to execute: nsenter [--mount=/host/proc/9742/ns/mnt --net=/host/proc/9742/ns/net bash -c ls /var/lib/rancher/longhorn/engine-binaries/*], output , stderr, ls: cannot access '/var/lib/rancher/longhorn/engine-binaries/*': No such file or directory\n, error exit status 2"
time="2020-08-13T03:58:56Z" level=info msg="New upgrade leader elected: khushboo-test-lh-wk3"
time="2020-08-13T03:59:01Z" level=info msg="New upgrade leader elected: khushboo-test-lh-wk25"
time="2020-08-13T03:59:05Z" level=info msg="Start upgrading"
time="2020-08-13T03:59:05Z" level=info msg="No API version upgrade is needed"
time="2020-08-13T03:59:06Z" level=info msg="Finish upgrading"


Issue when installing and running

So as far as I can tell I've installed deepspeed, however I'm trying to use accelerate to run this and it seems it's trying to call:
  import deepspeed.ops.transformer as transformer_inference

Which then brings up the error:
AttributeError: module 'deepspeed' has no attribute 'ops'

I found an issue relating to this, the exact title was the attribute error, and it was closed because a response was given to try and use the line pip install git+https://github.com/microsoft/deepspeed.git
When I ran that I got this:
  line 41, in installed_cuda_version
        assert cuda_home is not None, "CUDA_HOME does not exist, unable to compile CUDA op(s)"
    AssertionError: CUDA_HOME does not exist, unable to compile CUDA op(s)

Idk if they are similar issues but whatever it is I really don't understand what the issue is. I'm trying to use wsl2 to run this and maybe that's the problem? Any help would really be appreciated.

CUDA_HOME is your OS environment variable, you need to set it with path to your CUDA installation (check /usr/local/cuda/ folder) and in my experience WSL is always bad choice for CUDA related stuff...


Input range is taking in negative even after a positive value is being assigned as minValue

Even after setting min value for the react input range the slider is accepting negative value, below is the code and the attachment necessary for the issue.

this.state = {
value: { min: 8000, max: 75000 }
}
<InputRange
formatLabel={value => ${this.convertToIndianFormat(value)}kms}
maxValue={100000}
minValue={0}
ref="input_range"
value={this.state.value}
onChange={value => this.setState({ value })}
onChangeComplete={value => this.bindDistanceRange(value.min, value.max, this.cityName, this.sortObject, this.searchText)}
/>

Hi. I'm facing also the same issue. It happens when I double-click slider.

          value.min = value.min <= 0 ? 10 : value.min;

When i added this, or it was like this before (idk). The max value acts the same way, to fix:
`value.max = value.max >= 100 ? 100 : value.max;


Add tabs

Closes #124

Closes #92 #106

Codecov Report

Merging #125 (5efb2d0) into master (ad509d8) will decrease coverage by 1.38%.
The diff coverage is 1.75%.

 Learn more


eigenstates version fails on plain installation

Hello,
when I try to install the module on an empty setup, I reach the following point with the installation:
===> Testing: Ecosystem:ver<0.0.16>:auth<zef:lizmat>
[Ecosystem] # Failed test 'is use-target ok?'
[Ecosystem] # at t/01-basic.rakutest line 23
[Ecosystem] # expected: 'eigenstates:ver<0.0.9>:auth<zef:lizmat>'
[Ecosystem] #      got: 'eigenstates:ver<0.0.10>:auth<zef:lizmat>'
[Ecosystem] # Failed test 'is resolve ok?'
[Ecosystem] # at t/01-basic.rakutest line 43
[Ecosystem] # expected: 'eigenstates:ver<0.0.9>:auth<zef:lizmat>'
[Ecosystem] #      got: 'eigenstates:ver<0.0.10>:auth<zef:lizmat>'
[Ecosystem] # You failed 2 tests of 12

It seems that eigenstates version is hardcoded - I couldn't find the dependency chain that installs it at all - and it got updated since the test version.
What do you think could be a long-term solution to this?
Environment: moar-2022.07 of rakubrew, on Ubuntu 20.04.

Thanks for the report!
Version 0.17 uploaded to zef ecosystem.  zef update && zef install Ecosystem should do the trick now.