v1.2.6, Browserify and Ampersand-localforage

Since this weekend our build system chokes on the updated version of localforage. Using Browserify and ampersand-localforage we get this error:
13:31:18 [13:31:30] Browserify Error { [SyntaxError: Unexpected token (144:10) while parsing /home/.../node_modules/ampersand-sync-localforage/node_modules/localforage/src/localforage.js while parsing file: /home/.../node_modules/ampersand-sync-localforage/node_modules/localforage/src/localforage.js]
The version before just worked fine with the current ampersand-localforage/browserify :-(  Any hints on what we can change maybe on our side?

No, this is my fault, sorry :cry:
When we did the refactor into es6 we removed support for including src/localforage.js and require people to include the fully built version in dist. I've never officially supported including the source files but I think it's always worked until now and a lot of people have been doing it--but it causes us headaches :smile:
I should have marked this as a version bump to 1.3 and didn't. I'll push 1.2.7 soon and it should continue working. Then I'll push 1.3, which won't work as you've been using but should work with the dist/ version.
Sorry about all this. Should be fixed soon.

Me sorry too :(

Uploaded a new release to GitHub and npm. This should be fixed now, but there will be a new release later today: 1.3 that will not support loading src/localforage and will only work with the dist/localforage.js version.

We  also have to change the "browser" field in package.json to target the
dist file as well.
On Mon, Aug 3, 2015, 14:57 Matthew Riley MacPherson <
<EMAIL_ADDRESS>wrote:

No, this is my fault, sorry [image: :cry:]
When we did the refactor into es6 we removed support for including
src/localforage.js and require people to include the fully built version
in dist. I've never officially supported including the source files but I
think it's always worked until now and a lot of people have been doing
it--but it causes us headaches [image: :smile:]
I should have marked this as a version bump to 1.3 and didn't. I'll push
1.2.7 soon and it should continue working. Then I'll push 1.3, which won't
work as you've been using but should work with the dist/ version.
Sorry about all this. Should be fixed soon.
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/localForage/issues/413#issuecomment-127209459
.

--
Thodoris Greasidis
Computer, Networking &
Communications Engineer

Good to know, I’ll do that in the 1.3 version. I’ll release that at some point today :-)

tofumatt

On Mon, Aug 3, 2015 at 1:09 PM, Thodoris Greasidis
<EMAIL_ADDRESS>wrote:

We  also have to change the "browser" field in package.json to target the
dist file as well.
On Mon, Aug 3, 2015, 14:57 Matthew Riley MacPherson <
<EMAIL_ADDRESS>wrote:

No, this is my fault, sorry [image: :cry:]
When we did the refactor into es6 we removed support for including
src/localforage.js and require people to include the fully built version
in dist. I've never officially supported including the source files but I
think it's always worked until now and a lot of people have been doing
it--but it causes us headaches [image: :smile:]
I should have marked this as a version bump to 1.3 and didn't. I'll push
1.2.7 soon and it should continue working. Then I'll push 1.3, which won't
work as you've been using but should work with the dist/ version.
Sorry about all this. Should be fixed soon.
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/localForage/issues/413#issuecomment-127209459
.

--
Thodoris Greasidis
Computer, Networking &
Communications Engineer
Reply to this email directly or view it on GitHub:
https://github.com/mozilla/localForage/issues/413#issuecomment-127211641

Since ampersand-sync-localforage uses
"localforage": "^1.0.0",
will it also try to get v1.3 then and break again?

Hmm, it might.
Should we just declare this as version 2.0 given it’s a big refactor? I’m okay with that.

tofumatt

On Mon, Aug 3, 2015 at 1:12 PM, Veeck<EMAIL_ADDRESS>wrote:

Since ampersand-sync-localforage uses
"localforage": "^1.0.0",
will it also try to get v1.3 then and break again?
Reply to this email directly or view it on GitHub:
https://github.com/mozilla/localForage/issues/413#issuecomment-127213806

Sounds like a good idea since other users of ampersand-sync-localforage might be surprised too :-)

Yeah. Means I might delay the release a few days and go through anything else I might want to change in a big version bump. :-)

tofumatt

On Mon, Aug 3, 2015 at 1:15 PM, Veeck<EMAIL_ADDRESS>wrote:

Sounds like a good idea since other users of ampersand-sync-localforage might be surprised too :-)
Reply to this email directly or view it on GitHub:
https://github.com/mozilla/localForage/issues/413#issuecomment-127215417

Just pointing to the dist file in package.json should be enough I think.
On Mon, Aug 3, 2015, 15:15 Veeck<EMAIL_ADDRESS>wrote:

Sounds like a good idea since other users of ampersand-sync-localforage
might be surprised too :-)
—
Reply to this email directly or view it on GitHub
https://github.com/mozilla/localForage/issues/413#issuecomment-127215417
.

--
Thodoris Greasidis
Computer, Networking &
Communications Engineer

Maybe I could try to fix it myself and open a pull request to the original ampersand-sync-localforage, but who knows when it will get merged :-)


v2.0.0: Migrate cameradar server to cameradar-app repo

Fixes #165
Fixes #146
Fixes #141
Closes project 2.1.0

Pull Request Test Coverage Report for Build 546

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 97.586%

Totals

Change from base Build 544:
0.0%

Covered Lines:
283

Relevant Lines:
290

💛  - Coveralls


Fix bug in how the containing polygon is found

Hi @frapa. Thanks again for this library. I found another bug and this time I've been able to fix it myself 🎉
This PR adds a new test for a failing pathfind that I discovered in https://github.com/46bit/rtt/issues/15#issuecomment-686721166. NavMesh.findPath was returning null despite a trivial solution.
This PR then fixes that bug. I found that _findContainingPolygon was not finding the polygons containing the points, and so concluded there was no path. The old code looks strange to the eye. After looking at how the polygon bounds are calculated, I think the old code was just wrong.
The rest of the testsuite still passes with this fix in place.

Hi @46bit!
Ad last time, I'm on holiday right now, so it will take me some time to review this.
Anyways, thanks for the PR! I'm glad you found a way to fix the bug and add a test, and I am really happy you're contributing.
Unfortunately I've also not used the library a lot and I am aware there are still some rough edges. The more we use it, the quicker we'll iron out the issues.

Hi @frapa, no worries, enjoy your holiday. Since I started using this fix I haven't found any more problems with nav2d so I think it's nearly sorted :)

@46bit Thanks again for the PR. I will close this as I fixed it myself allowing the user to override the settings. I copied your test into my commit and changed the logic in a slightly different way. There is now a NavMesh.pointQuerySize param that can be set if the default of 0.01 does not work well with your mesh (this settings, if set positive and not zero, should only impact performance and not functionality).
Release on npm is underway.

Brilliant, that sounds like a better fix.


improvement: Debounce mo.ui.text and text_area

📝 Summary
Debounce mo.ui.text and mo.ui.text_area either until Enter is pressed (or Ctrl+Enter for text area), or by a given number of milliseconds. Completes #2218.
🔍 Description of Changes

If debounce === true, then only emit values on Enter key down (Ctrl + Enter for text area)
If typeof debounce === "number", then delay emit by that value in milliseconds
Both mo.ui.text and mo.ui.text_area have debounce set to True by default now

Feel free to check out the example notebook in the _smoke_tests directory. When debounce === False, noticed some flickering when the value from an input/textarea is printed in a different cell; may need to address in a separate issue.
📋 Checklist

[x] I have read the contributor guidelines.
[x] For large changes, or changes that affect the public API: this change was discussed or approved through an issue, on Discord, or the community discussions (Please provide a link if applicable).
[ ] I have added tests for the changes made.
[x] I have run the code and verified that it works as expected.

📜 Reviewers
@akshayka OR @mscolnick

this PR is 🔥


Fieldsets in front-end forms

Is there a way to add fieldset to a front-end form? how?

I did a new RawHTMl fieldset duplicating the spacer fieldset and elimnating all the HTML and solved the issue. It works


Custom user themes

What should be added?
Customizable user themes in addition to the four pre-existing themes already present in the program. Depending on which of these is easier to implement, these themes could either be written in a format like CSS, or in a way similar to how Blender's themes are managed.
Why should it be added?
To give users more freedom when customizing their Chatterino user interface.

Related to #1041 and #1837

Related to #1041 and #1837

Themes (beta) are implemented since v2.4.6 - you can read more about how it works here https://wiki.chatterino.com/Themes/
For further feedback on Themes you can make a new issue


Where does library JS code live in our current package setup?

Closing this as we're moving to a component-based folder structure—non-React javascript should live with its relevant component.


fish not working on WSL with blank output

Having trouble with fish on the latest Windows 10 Pro Insider Preview. Trying to run it causes nothing to be rendered; text can be still entered into the prompt but nothing else is shown.
Steps to reproduce:

Have at least Insider build 17127

Install any distro of Linux on WSL (tried with both Ubuntu and openSUSE)

Install any version of fish 2.2+ (tried the default fish 2.2.0 xenial package on Ubuntu, 2.7.1 on both openSUSE and Ubuntu, and compiling 3 directly from source, all same result)

run fish

I've also tried a fresh install of 10 Insider build 17115, fish works as expected there. Once I upgraded it to 17127, it stopped displaying properly. strace gave me nothing useful, only a blank file. Not sure if this is related, but I also can't terminate any instances, both fish and strace with fish once they're started. I've tried:

killall fish

Task Manager (click End task > End process seems to have no effect)

taskkill /im fish /f in Admin CMD (gives Access is denied error for processes)

build 17127

This is likely related to #3034 and #3039 like the one below you.

The unkillable processes definitely looks similar to those issues; I was getting high CPU usage as well. Are the rendering issues related as well?

Yeah, it's #3036 which first manifested when I was trying to get fish working under 1723.
@gyroknight roll back to 1720.


Use class attribute for container namespace_separator setting

This is necessary to work with the latest dry-container, which (for dry-rb-wide dependency graph reasons) has switched from dry-configurable to simple dry-core class attributes for its config.

@timriley nice catch 🎉
I'm wondering if we should add some specs for Importer?

How come this doesn't make any test crash?


[sai-gen] Add support for generating SAI stats APIs for counters.

Problem
DASH has scaling requirement that requires technology providers to support huge number of objects, e.g. 8M of CA-PA mappings. If we need to add counters for these objects by using generic SAI counters, we will generate large number of counter ids, which might not be ideal.
Also some counters we are collecting are not data path counters, but more like hit counts, which is not what generic SAI counter is modeling.
For these cases, we can support generating the counters as SAI stats and leverage existing SAI stats API design for querying the counters back.
What we are doing in this change
This change updated sai_api_gen.py with 2 changes:

Rename as_attr to attr_type for supporting more types of counter generation.
Updated the counter generation logic and its templates for generating SAI stats APIs.

This feature will be used in the incoming fast path API generations.
Take metering bucket as an example to illustrate this change, say we updated its counters to capture both packet and bytes, change its type to stats, then add another counter for tracking all traffic, not on metering bucket level:

This will results in the both metering bucket counter being generated as stats enum:

Once an table as any stats enum, we will generate the stats APIs:

On port level, it will generate the overall counters:

However, we are not generating a working libsai at this moment, which is the same as the counters today. This work will be postponed to later time.

Here is the preview of the fast path SAI API change that built on top of this feature (for header generation only):

DASH p4: https://github.com/r12f/DASH/commit/ee0a078b1a2c504517763bd7905b540678cd1cb9
SAI API: https://github.com/r12f/SAI/commit/d0e29049664945a78e3569193d9280fde04654a3

thanks for the review, Marian! will get this merged and sharing the fast path SAI update out.


borken vapid. borken notifications.

helo,,,,,,,,,,,,,,,,,,,,,,,,,,
url for generating vapid is borken...
code & api requires 500+ iq to understand, pls fix so u can test send notifications on page easy & fetch list send notifications to specific simplified user ids like phone numbers       :   !!!!
also notofications no work brave web browser if no use google paranoid security settings, pls fix i have many other sites they work
other than that very good i have fork https://github.com/ttttttttttttttttttttttttttttttttttttttx/n
:beers:

Hi, I'm not sure what you mean that the API required 500+ IQ? Can you specific what is confusing for you?
Also, this app is meant for standalone usage, feel free to modify this project however you please. :)


java-websocket for ssm frame

How to create a server in the web project built by SSM framework, I am a beginner, but I still don't know how to create it.
If there is such a web project, can I refer to it
I'm really in a hurry

You should add more information about your problem. What is SSM? How is it related to websockets? What exactly is not working?


Missing extensions?

I read #94 and assumed that it would auto-install PHP extensions depending on the ext- options in composer.json, but it doesn't seem to be working for me in my gitlab workflow. Instead I get:
Using docker image sha256:6e10fb20dffb5507d748d3890244fa471476b98e7576d760076de00b07e44607 for lorisleiva/laravel-docker:8.0 with digest lorisleiva/laravel-docker@sha256:68dedfc04c88d6b7633260d3d0b2428f168c16e81b56721e8217093158f94910 ...
55$ composer install --prefer-dist --no-ansi --no-interaction --no-progress --no-scripts
56Installing dependencies from lock file (including require-dev)
57Verifying lock file contents can be installed on current platform.
58Your lock file does not contain a compatible set of packages. Please run composer update.
59  Problem 1
60    - Root composer.json requires PHP extension ext-mysqli * but it is missing from your system. Install or enable PHP's mysqli extension.
61To enable extensions, verify that they are enabled in your .ini files:
62    -
63    - /usr/local/etc/php/conf.d/docker-php-ext-bcmath.ini
64    - /usr/local/etc/php/conf.d/docker-php-ext-calendar.ini
65    - /usr/local/etc/php/conf.d/docker-php-ext-exif.ini
66    - /usr/local/etc/php/conf.d/docker-php-ext-gd.ini
67    - /usr/local/etc/php/conf.d/docker-php-ext-imagick.ini
68    - /usr/local/etc/php/conf.d/docker-php-ext-intl.ini
69    - /usr/local/etc/php/conf.d/docker-php-ext-pcntl.ini
70    - /usr/local/etc/php/conf.d/docker-php-ext-pdo_mysql.ini
71    - /usr/local/etc/php/conf.d/docker-php-ext-pdo_pgsql.ini
72    - /usr/local/etc/php/conf.d/docker-php-ext-redis.ini
73    - /usr/local/etc/php/conf.d/docker-php-ext-soap.ini
74    - /usr/local/etc/php/conf.d/docker-php-ext-sodium.ini
75    - /usr/local/etc/php/conf.d/docker-php-ext-xdebug.ini
76    - /usr/local/etc/php/conf.d/docker-php-ext-zip.ini
77You can also run `php --ini` inside terminal to see which files are used by PHP in CLI mode.

My composer.json contains:
    "require": {
        "php": "^8.0",
        "ext-exif": "*",
        "ext-gd": "*",
        "ext-imagick": "*",
        "ext-mysqli": "*",
        "ext-pdo": "*",
        "ext-pdo_mysql": "*",
        "ext-sodium": "*",

which I note does not include some of the extensions listed in the error, though I guess they may pulled in by deps.
Is there something else I need to do?

I managed to solve this by adding a line to my composer stage's script:
- install-php-extensions mysqli

however, I was under the impression that this image had some kind of mapping that would automatically enable extensions listed in the composer.json file?


Is MLIR to ONNX supported?

Love this project that brings ONNX to the MLIR world. I was wondering if MLIR onnx dialect -> onnx proto is supported?

We/IBM have no direct need for it but in general, having such functionality could open the space of onnx to onnx transformations via a strong compiler platform (aka MLIR).
If a team was interested in picking up this challenge, we would be receptive. However, this piece would have to be updated from time to time as the ONNX standard changes, so it would be a project that needs a long term commitment, as we don't want to add a lot of functionality that increase our footprint of code that is partially implemented and/or not up to date.
If others are interested in such functionality and would be willing to dedicate resources, feel free to chime in here.

I'm also interested in this functionality.

However, this piece would have to be updated from time to time as the ONNX standard changes

Just to clarify, we are talking about just ONNX MLIR -> ONNX protobuf, correct?


Coalesced memory read for a slightly faster LLM interence

Background
I enjoyed reading the posts related to this tweet: https://twitter.com/awnihannun/status/1776275621926375498
I'd like to contribute to the MLX side in the challenge with Llama.cpp, even if it's just a small improvement. :)
Proposed changes
This PR modifies the way scales and biases are read from memory, making the access more coalesced.
Although the data in these variables are sparsely arranged for a SIMD thread, they can be read in a more adjacent manner when considering all SIMD threads together.
Performance Benchmarks
Performance improved around 0.2% with this change.

Machine: M3MAX (128GB)
LLM: mistral-7b (4Q)
Client: https://github.com/ml-explore/mlx-examples
Command: python -m mlx_lm.generate --model mlx_model --prompt "write a quicksort algorithm in c++" --max-tokens 256
Before: main(tag: v0.9.1)
After: this PR

Token Processing Speed (tokens per second, higher is better, 15 runs):

Before
After
Speedup

Median
68.554
68.680
0.18%

Mean
68.557
68.734
0.26%

Min
68.210
68.592
0.56%

Max
68.800
69.087
0.42%

Checklist

[x] I have read the CONTRIBUTING document
[x] I have run pre-commit run --all-files to format my code and installed pre-commit prior to committing changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have updated the necessary documentation (if needed)

Additional Notes

All tests passed.
Applying clang-format to quantized.metal resulted in significant formatting changes. To avoid overwhelming diffs, I opted to bypass the linting step for this file.

I spent quite some time playing with it and it is really really hard to figure out if there is any performance benefit. I changed the unrolled read to a constexpr forloop that would get rid of the static assertion and run 100 generations using the for loop twice (one of them the pointer advancement is done later), this PR and v0.9.1 .
I get the following graph.

I believe that it doesn't really matter and that the variation has to do with whatever throttling or any other operation that is happening on the machine at the time. There is absolutely no reason the for loop should be faster than the unrolled loop and even if it is, it is a tiny amount.
@youknow04 let me know what you think.

Thank you for your detailed feedback and insights. Let me address each of your points:

Tiny performance gain issue
Matrix-vector multiplication is a fundamental operation and the core computational load in Transformers.
Optimizing this primitive operation can indeed have a persistent effect on all variants.

Faster for loop issue
First, I should mention that this is only my second time programming in Metal, so I don't have expertise in the Metal framework itself.
However, I have done such low-latency optimizations many times, and unrolling is not always faster than a for loop, especially when the unrolled code is too long.
The code itself should be in memory, so larger code size implies more memory overhead, such as cache misses.
But I didn't expect the for loop to be faster than the unrolled version here.
I appreciate your intensive checking.

Experiment issue
I don't think it's a throttling issue because I manually tested each run with checks.
I tested performance with GPU monitoring, ran the LLM when GPU utilization was idle, executed each run with enough rest to prevent throttling issues, and the cooling fan was not triggered in my M3MAX (128G) for all tests.

I think we now need the LLN(Law of Large Numbers) to test this tiny gain in the LLM.
MLX is still in its early stages, and you must have a lot of work to do.
I want to support the MLX team and really don't want to take your time for this hacky gain.
I will make the test code for intensive test and share the result again.

I tried to reproduce the results using the following steps:

reboot my mac
runsudo sysctl iogpu.wired_lwm_mb=100000
run following python script

this is randomized script to prevent possible biases.

Used python code to reproduce
```python
import json
import os
import random
import statistics
import subprocess
import time
from dataclasses import dataclass
MLX_LM_PATH = os.getcwd()
MLX_PATH = os.path.expanduser("~/workspace/mlx")
NUM_BATCH = 32
NUM_ITER = 999
RESULT_FILE = "result.jsonl"
@dataclass
class Target:
branch: str
commit_hash: str
targets = [
Target("main", "bddf23f175726a57f0e443cd45518c0757daa166"),
Target("coalesced-mem", "ab58e3718a3e31687e3ef5e8914034855990454f"),
Target("coalesced-mem-unroll-t", "28057ab228de7d1b1042622559b4a1ef7ba14a12"),
# Target("coalesced-mem-for-1", "893a6327b7ec1d2b391c6e8e27822fecbf5d0e04"),
# Target("coalesced-mem-for-2", "af9a0269a35ce68409e4f4f5e09d6f82da55c835"),
]
def run_command(command: list[str]):
return subprocess.check_output(command).decode("utf-8")
def setup_mlx(target: Target):
os.chdir(MLX_PATH)
run_command(["git", "switch", target.branch])
print(f"installing mlx[{target.branch}]")
run_command(["pip", "install", "."])
pip_list_result = subprocess.check_output(["pip", "list"]).decode("utf-8")
if f"+{target.commit_hash[:8]}" not in pip_list_result:
    raise RuntimeError(f"wrong MLX version installed. {target.branch}")
os.chdir(MLX_LM_PATH)

def show_result():
parsed: dict[str, list[float]] = {t.branch: [] for t in targets}
with open(RESULT_FILE, "r") as f:
for line in f:
result = json.loads(line)
for r in result:
parsed[r["branch"]].append(float(r["tps"]))
for branch, tps_values in parsed.items():
    mean_tps = statistics.mean(tps_values)
    median_tps = statistics.median(tps_values)
    print(f"{branch}: Mean = {mean_tps}, Median = {median_tps} Min = {min(tps_values)}, Max = {max(tps_values)}")

if name == "main":
show_result()
exit()
os.chdir(MLX_LM_PATH)
for i in range(NUM_ITER):
    r_samples = random.sample(targets, len(targets))
    print(f"{i}th iteration with {r_samples}")
    sample_result: list[dict[str, str|float]] = []
    for target in r_samples:
        setup_mlx(target)
        for b in range(NUM_BATCH):
            time.sleep(2)  # to prevent throttling
            llm_result = run_command(["python", "-m", "mlx_lm.generate", "--model", "mlx_mistral7b-8q", "--prompt", "'write a quicksort algorithm in c++'", "--max-tokens", "128"])
            tps = float(llm_result.split("Generation: ")[1].split(" tokens-per-sec")[0])
            sample_result.append({
                "branch": target.branch,
                "iter": i,
                "batch": b,
                "tps": tps,
            })
    with open(RESULT_FILE, "a") as f:
        f.write(json.dumps(sample_result)+"\n")
    show_result()

and got this result

- `main`: v0.9.1
- `coalesced-mem`: this pr
- `coalesced-mem-unroll-t`: this PR with https://github.com/ml-explore/mlx/pull/803
- `coalesced-mem-for-1`: this PR using one for loop
- `coalesced-mem-for-2`: this PR using tow for loop

# Result Summary:
- After `rebooting` and the `iogpu.wired_lwm_mb` setting, all inference speeds increased, and the speed gap between different configurations was reduced.
- The rank order remained consistent.
- The combination of this PR and https://github.com/ml-explore/mlx/pull/803 shows the best performance.
- We now have clean results, and throttling or other operational issues have minimal impact due to randomization and the LLN.
- This PR delivers improved performance, and it is even faster when combined with https://github.com/ml-explore/mlx/pull/803.

In my opinion, for truly low-latency code, complex implementations are inevitable.
we also have room for improvement when we choose this direction.

@angeloskath let me know what you think.

It seems you have no interest in this PR.
I will close this.


[PROPOSAL]: Add a note at the top of the guide that only Linux is support currently..

Proposal
Users will spend time following instructions on native windows as it's not called out that it's only linux arch supported currently
Self-service

[ ] I'd be willing to do some initial work on this proposal myself.

Oh is that why I can't seem to install it on windows? Cuz it's not supported? That would have been nice to know before I spent an hour trying to figure this out. FTR I'm not savvy with any of this, following directions and stumbling through the dark.
In case there's interest, my error on windows:
Processing c:\colossalai
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'error'
error: subprocess-exited-with-error
python setup.py egg_info did not run successfully.
exit code: 1
[24 lines of output]
Traceback (most recent call last):
File "", line 2, in
File "", line 34, in
File "C:\colossalai\setup.py", line 120, in
build_cuda_ext = check_cuda_availability(CUDA_HOME) and check_cuda_torch_binary_vs_bare_metal(CUDA_HOME)
File "C:\colossalai\setup.py", line 63, in check_cuda_availability
_, bare_metal_major, _ = get_cuda_bare_metal_version(cuda_dir)
File "C:\colossalai\setup.py", line 16, in get_cuda_bare_metal_version
raw_output = subprocess.check_output([cuda_dir + "/bin/nvcc", "-V"], universal_newlines=True)
TypeError: unsupported operand type(s) for +: 'NoneType' and 'str'
torch.version  = 1.13.0+cpu
Warning: Torch did not find available GPUs on this system.
If your intention is to cross-compile, this is not an error.
By default, Colossal-AI will cross-compile for Pascal (compute capabilities 6.0, 6.1, 6.2),
Volta (compute capability 7.0), Turing (compute capability 7.5),
and, if the CUDA version is >= 11.0, Ampere (compute capability 8.0).
If you wish to cross-compile for a single specific architecture,
export TORCH_CUDA_ARCH_LIST="compute capability" before running setup.py.
[end of output]
note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed
Encountered error while generating package metadata.
See above for output.

Hi @georgeunidev and @myndxero  Thank you for your feedback.
Colossal-AI is only Linux arch supported currently.
Support for window is in our plans, but not a high priority, as most projects are linux-based
@georgeunidev Would you please submit a PR to point this out in the repo README?
We very much welcome contributions from the open source community, thanks.

Hi @georgeunidev and @myndxero Thank you for your feedback. Colossal-AI is only Linux arch supported currently. Support for window is in our plans, but not a high priority, as most projects are linux-based
@georgeunidev Would you please submit a PR to point this out in the repo README? We very much welcome contributions from the open source community, thanks.

I think that's really important, Because most people probably only have windows system like me, It's such an excellent project.Most people should not be rejected by this question.

Updated. Thanks.


Audio Captcha Generator

Audio Captcha Generator
Added a new functionality of Generating Captcha using Audio.
pygame
captcha
tkinter

Thanks for contributing ⭐
#327
But try to make a pr for one issue at a time as it may consider spam for hacktoberfest , so I am removing your expense-tracker commit

Thanks for contributing ⭐ #327
But try to make a pr for one issue at a time as it may consider spam for hacktoberfest , so I am removing your expense-tracker commit

Thanks a lot @Mrinank-Bhowmick I will consider it.


Interaction with objects

Is there an option to spawn custom objects (e.g. cubes, balls...) with which our agents would be able to interact, fully leveraging Bullet engine?

This is in our development plan and with high priority. Stay tuned! :smile:

Haha, you are quick, thanks :smile:

Does it support this feature now?


How to get original files URLs?

Is it possible to avoid export to local files and get the original selected assets URL instead?

This is not possible since SDK30 on Android. You may want to check the FAQ for an explanation. Thank you.


C3: Improve bindings DX in hono template

What this PR solves / how to test
The hono template has been updated as follows:

Bumps create-hono to 0.7.0
Automatically installs dependencies and specifies the detected package manager to avoid interactive prompts
Adds a wrangler.toml file with commented out examples of all available bindings to match other templates.
Adds a cf-typegen package script to automatically regenerate types for Bindings from wrangler.toml

Example of resulting project with an added kv example: https://github.com/jculvey/cf-hono-example.
Author has addressed the following

Tests

[ ] TODO (before merge)
[ ] Included
[x] Not necessary because: existing coverage sufficient

Changeset (Changeset guidelines)

[ ] TODO (before merge)
[x] Included
[ ] Not necessary because:

Public documentation

[ ] TODO (before merge)
[ ] Cloudflare docs PR(s): https://github.com/cloudflare/cloudflare-docs/pull/...
[x] Not necessary because: Improvements are backwards compatible

@jculvey Looking at your generated repo at ..., everything on env is now unknown, so for example:
c.env.ddd

in your repo doesn't throw any errors, it just reports as unknown. Vs with a more traditional bindings definition, you end up with a useful error that tells you it doesn't exist on env:
Property 'ddd' does not exist on type 'CloudflareBindings'.ts(2339)

Is this the intent here? I feel like the DX is much worsened when everything on env is unknown.

@Cherry  thanks for catching this!
In short, no, the intent here wasn't just to regress the type safety of env 😅 .
In short we're trying to simplify the process of consuming the type definition generated by wrangler types for hono to bring it in line with the rest of the C3 templates.
Unfortunately If you try to assign the result of that command directly to Bindings you end up with this error:

As you point out, if the generated CloudflareBindings was a type and not an interface, there wouldn't be an issue.
What I was trying to accomplish was to augment the existing type with the generated one:

Agreed this is worse DX. I'll make a PR to patch this up. Thanks again for the report!

Thanks @jculvey! 🧡


Brand-new GPT Coding Assistant - Codey

🚀 Just unleashed my brand-new GPT Coding Assistant, and it's a game-changer!
Link : https://chat.openai.com/g/g-SuWVXlmkP-codey

Merged


kube3d: 5.4.4 -> 5.4.8

Description of changes

Updated k3d to 5.4.8
Have to jump through some hoops to get k3d to compile
https://github.com/k3d-io/k3d/issues/1237
Added back a k3sVersion since the fallback value is really old
Things done

Built on platform(s)

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

[X] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[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

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

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

[X] Fits CONTRIBUTING.md.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/1937

Added back a k3sVersion since the fallback value is really old

First, I don't have much context because I don't use this.
Doesn't it work with current k3s version?
If it does, why not k3s.version?

https://github.com/k3d-io/k3d/blob/main/version/version.go#L40-L41
https://github.com/k3d-io/k3d/blob/main/Makefile#L32-L33
There is another k3s version value set to latest but it's separate to k3d, it's in the tools tool
https://github.com/k3d-io/k3d/blob/main/tools/version/version.go#L6-L7

@06kellyjac does it make sense to update this to https://github.com/k3d-io/k3d/releases/tag/v5.4.9? thanks!

@06kellyjac does it make sense to update this to https://github.com/k3d-io/k3d/releases/tag/v5.4.9? thanks!

5.5.1 has been relesed, if its not to much work, we should try do this part of this PR

I have added 5.5.1 in an overlay, which could help avoid work duplication. See below:
{ lib
, buildGoModule
, fetchpatch
, fetchFromGitHub
, installShellFiles
, k3sVersion ? "1.25.6-k3s1"
}:

let
  hasVPrefix = ver: (builtins.elemAt (lib.stringToCharacters ver) 0) == "v";
  k3sVersionSet =
    if k3sVersion != null then
      if hasVPrefix k3sVersion then throw "k3sVersion should not have a v prefix" else true
    else
      false;
in
buildGoModule rec {
  pname = "kube3d";
  version = "5.5.1";

  src = fetchFromGitHub {
    owner = "k3d-io";
    repo = "k3d";
    rev = "v${version}";
    sha256 = "sha256-cXUuWR5ALgCgr1bK/Qpdpo978p3PRL3/H6j1T7DKrT4=";
  };

  patches = [
    (fetchpatch {
      url = "https://github.com/k3d-io/k3d/commit/d7fee0ef4e90b04be889423bd61aa8517c55cf79.patch";
      hash = "sha256-yXaATIiuXmVi2cFvLDauCG4+ZhOx8MQyAhI53GnPlBE=";
    })
  ];

  # the committed vendor dir is out of sync
  # https://github.com/k3d-io/k3d/issues/1237
  deleteVendor = true;
  vendorSha256 = "sha256-QhB23oGiiRBF4c+FcdN3/PCuBjPtU+EqIRPqEzKRgTY=";
  # needs go workspaces to successfully compile due to docker/cli dependency
  proxyVendor = true;

  nativeBuildInputs = [ installShellFiles ];

  excludedPackages = [ "tools" "docgen" ];

  ldflags =
    let t = "github.com/k3d-io/k3d/v5/version"; in
    [ "-s" "-w" "-X ${t}.Version=v${version}" ] ++ lib.optionals k3sVersionSet [ "-X ${t}.K3sVersion=v${k3sVersion}" ];

  preCheck = ''
    # skip test that uses networking
    substituteInPlace version/version_test.go \
      --replace "TestGetK3sVersion" "SkipGetK3sVersion"
  '';

  postInstall = ''
    installShellCompletion --cmd k3d \
      --bash <($out/bin/k3d completion bash) \
      --fish <($out/bin/k3d completion fish) \
      --zsh <($out/bin/k3d completion zsh)
  '';

  doInstallCheck = true;
  installCheckPhase = ''
    runHook preInstallCheck
    $out/bin/k3d --help
    $out/bin/k3d --version | grep -e "k3d version v${version}" ${lib.optionalString k3sVersionSet "-e \"k3s version v${k3sVersion}\""}
    runHook postInstallCheck
  '';

  meta = with lib; {
    homepage = "https://github.com/k3d-io/k3d/";
    changelog = "https://github.com/k3d-io/k3d/blob/v${version}/CHANGELOG.md";
    description = "A helper to run k3s (Lightweight Kubernetes. 5 less than k8s) in a docker container - k3d";
    longDescription = ''
      k3s is the lightweight Kubernetes distribution by Rancher: rancher/k3s

      k3d creates containerized k3s clusters. This means, that you can spin up a
      multi-node k3s cluster on a single machine using docker.
    '';
    license = licenses.mit;
    maintainers = with maintainers; [ kuznero jlesquembre ngerstle jk ricochet ];
    platforms = platforms.linux ++ platforms.darwin;
    mainProgram = "k3d";
  };
}

@06kellyjac, the patch I applied in the file is to solve a vendor error. Using it, the build has succeeded.

@06kellyjac  should commit message be changed to match attribute name ?

Looks like this is obsoleted by #246131, right?

Looks like this is obsoleted by #246131, right?

yes you are right,
I think its because of attribute rename, duplicate PR wasn't noticed. I hope @06kellyjac contribution efforts are not unnoticed

Thanks.
It also looks like https://github.com/k3d-io/k3d/issues/1237 can be marked as resolved as #246131 only needs to turn off GOWORK ?

I'd assume so yeah.


PR: Put the sys.prefix in the config search path

Description of Changes
This change puts sys.prefix on the config search path. With this change we have the option of providing a centrally managed spyder installation which can be pre-configured without setting global (machine-wide) config.
The use case that this comes from:

I want to be able to provide a spyder installation to a large number of users (200+) who have all got a specific NFS drive mounted on their Linux (Centos) machines. I therefore cannot setup a config in /etc/, and cannot control the user's ~/.config; I therefore want to be able to put a config in {sys.prefix}/etc/spyder/spyder.ini and it affect the global config (which can be overridden by the user config, should a user so choose).

In my case, I wanted to provide a spyder installation which is pre-configured to use a specific interpreter by default (different from the spyder interpreter). I therefore put the following config file in place:
$ which spyder
/home/pelson/github/spyder/spyder/env/bin/spyder

$ cat /home/pelson/github/spyder/spyder/env/etc/spyder/spyder.ini
[main_interpreter]
custom_interpreter = /tmp/spyder-kernel-env/bin/python
executable = /tmp/spyder-kernel-env/bin/python
default = False
custom = True

$ rm -rf ~/.config/spyder-py*

$ spyder   # correctly uses the configured environment (/tmp/spyder-kernel-env/bin/python)

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:
@pelson

Hey @pelson, nice to see you here and thanks a lot for your contribution!
We'd like to include it in our next release in the Spyder 5 series. For that, please make your branch to derive from our 5.x branch (instead of master), with the following commands:
git checkout 5.x
git checkout feature/sys_prefix_config
git rebase --onto 5.x master feature/sys_prefix_config
git push -f origin feature/sys_prefix_config

Other than that, the change seems sensible, so I'm ok with it.

nice to see you here and thanks a lot for your contribution!

Good to see you also! It has been a long time!

We'd like to include it in our next release in the Spyder 5 series

Great, I've rebased. :+1:

:partying_face: - thank you for reviewing/merging so quickly. Happy to have my first commit on spyder! :+1:

No prob, hope more commits will in the future!


Update Travis CI configs

Description

removed social_media_url from .podspec as it was causing issues when executing pod lib lint (for some reason it wasn't able to reach twitter account url)
updated Travis CI .yml to use latest Xcode and simulation device

It was a formal PR, more for visibility and to see 💚 Travis CI. Merging this config changes using my Admin power 💪


feat: add --no-hmr flag

Closes #673

Hmm... looks like I broke react-refresh integration with these changes. Taking a look...


subctl join not detecting dedicated gateway being deployed on AWS

What happened:
Deployed an AWS OCP cluster and ran subctl cloud prepare aws which deployed a gateway, but subctl join doesn't offer this gateway as an option.
Output of subctl cloud prepare aws:
 ✓ Initializing AWS connectivity
 ✓ Retrieving VPC ID
 ✓ Retrieved VPC ID vpc-0dfeaf4396d42084a
 ✓ Validating pre-requisites
 ✓ Validated pre-requisites
 ✓ Creating Submariner gateway security group
 ✓ Created Submariner gateway security group mkolesni-0-12-testday-rvxmz-submariner-gw-sg
 ✓ Adjusting public subnet mkolesni-0-12-testday-rvxmz-public-us-east-1d to support Submariner
 ✓ Adjusted public subnet mkolesni-0-12-testday-rvxmz-public-us-east-1d to support Submariner
 ✓ Deploying gateway node for public subnet mkolesni-0-12-testday-rvxmz-public-us-east-1d
 ✓ Deployed gateway node for public subnet mkolesni-0-12-testday-rvxmz-public-us-east-1d
 ✓ Retrieving VPC ID
 ✓ Retrieved VPC ID vpc-0dfeaf4396d42084a
 ✓ Validating pre-requisites
 ✓ Validated pre-requisites
 ✓ Opening port 4800 protocol udp for intra-cluster communications
 ✓ Opened port 4800 protocol udp for intra-cluster communications
 ✓ Opening port 8080 protocol tcp for intra-cluster communications
 ✓ Opened port 8080 protocol tcp for intra-cluster communications

When running subctl join, getting this prompt:
* broker-info.subm says broker is at: https://api.mkolesni-0.12-testday1.devcluster.openshift.com:6443
? Which node should be used as the gateway?  [Use arrows to move, type to filter]
> ip-10-0-138-11.ec2.internal
  ip-10-0-155-102.ec2.internal
  ip-10-0-165-223.ec2.internal

The gateway node has this DNS name: ip-10-0-53-110.ec2.internal
What you expected to happen:
subctl join should detect that cloud was prepared and skip the prompt
How to reproduce it (as minimally and precisely as possible):
Run subctl cloud prepare aws followed by subctl join
Anything else we need to know?:
The gateway node takes some time to deploy, so if given some wait time then subctl join does indeed detect the gateway and skip the prompt entirely. We need to see if this is simply something we need to document or somehow introduce detection that there's an ongoing gateway deployment (maybe in cloud prepare)
Environment:

Diagnose information (use subctl diagnose all):
Gather information (use subctl gather)
Cloud provider or hardware configuration: AWS
Install tools: openshift-install
Others:

The title of the issue could be misleading; this is basically a timing issue.. I agree we can improve the UX, but the functionality is working as expected if you wait/re-run the join command after a few minutes.


Script release creation

Spun off from issue #12
The release creation/upload is quite manual at the moment. In #12 I created I accidentally forgot to specify the target release option.
I propose one, maybe two, enhancement(s):

Create a shell script in the project to run the Bob makei command with our desired arguments (e.g. TGTRLS=V7R3M0).

Optionally, a second script that uses the Github API to create the release and upload the save file.

Found that the developer working on Bob actually has something very similar. We could probably adapt it quite easily:
https://github.com/TongkunZhang/bob-release-tools

Note to self - current manual build instructions:

Clear library REPLBOB (since that's what our bash script currently relies upon)
Run the build with makei build -t 'all package' -o TGTRLS=V7R3M0
sftp to the machine to transfer the save file locally (get /QSYS.LIB/REPLBOB.LIB/RPGLEREPL.FILE)
Create a new release through the Github UI and tag the new release
Attach the save file manually to the release in the browser


Error message in Object Detection

Tutorial Select
Prepare Custom Model
Feedback
I have two points.

Please make the error messages more user-friendly. I was working with OD example and got and got an error. The error message had a lot of things but not easy to find out what or where the error occurred. Then after reading the message many times, I decided to do a trying search in the files using a variable name I found in the error message. I could find the variable and manage the issue.
Advise the user where to find the additional assets not listed in the web project. For instance, in the OD example, after the inference process, I have a screen where the button "Take another picture" is exactly over the close button of my cell phone. So, when I try to take another picture, the app closes. So, I need to change the position of this button but could not find it in the files listed on the web page. I am guessing will need to try to search in the files stored in github.

Hi @zenetio, first of all, thank you for your feedback!

Absolutely! Please let us know what the error message and provide steps to reproduce the error/issue! This will help us identifying the issue and provide more user friendly error message with actionable feedback.
What is the device model on which you are seeing the issue? If you can, please provide a screenshot that shows the button underneath the close button.

Thank you!

Hi @raedle ,

In file objectDetector.js I changed the variable name from bounds to boxes and then I got a compilation error. The error message was not clear to clarify where and why I was getting the error. I think it could be more assertive.
My device is a Samsung Galaxy S9.  You can see in the screenshot that the OD app is drawing the button message exactly over the device button.

If I understand correctly, you changed the following code in the ObjectDetector.js from

// Adjust bounds to image size
const bounds = [
  x * imageWidth,
  y * imageHeight,
  boxWidth * imageWidth,
  boxHeight * imageHeight,
];

const match = {
  objectClass: COCO_CLASSES[maxIndex],
  bounds,
};

to
// Adjust bounds to image size
const boxes = [
  x * imageWidth,
  y * imageHeight,
  boxWidth * imageWidth,
  boxHeight * imageHeight,
];

const match = {
  objectClass: COCO_CLASSES[maxIndex],
  boxes,
};

Is that correct?

Thanks for reporting the issue. If you are using the Expo Snack editor, you can change the marginBottom for the resetButton style in screens/ResultScreen.js to a higher number.

Full example for screens/ResultScreen.js:
import * as React from "react";
import { useEffect, useRef, useState } from "react";
import {
  FlatList,
  StyleSheet,
  Text,
  TouchableOpacity,
  View,
  Platform,
} from "react-native";
import { Canvas } from "react-native-pytorch-core";

const objectColors = [
  "#FF3B30",
  "#5856D6",
  "#34C759",
  "#007AFF",
  "#FF9500",
  "#AF52DE",
  "#5AC8FA",
  "#FFCC00",
  "#FF2D55",
];

const textBaselineAdjustment = Platform.OS == "ios" ? 7 : 4;

export default function ResultsScreen({ image, boundingBoxes, onReset }) {
  const [ctx, setCtx] = useState(null);
  const [layout, setLayout] = useState(null);

  // This is a drawImage function wrapped in useCallback (for improving render performance)
  useEffect(
    () => {
      if (ctx != null && layout != null && image != null) {
        ctx.clearRect(0, 0, layout.width, layout.height);

        // Scale image to fit screen
        const imageWidth = image.getWidth();
        const imageHeight = image.getHeight();
        const scale = Math.max(
          layout.width / imageWidth,
          layout.height / imageHeight
        );
        const displayWidth = imageWidth * scale;
        const displayHeight = imageHeight * scale;
        const offsetX = (layout.width - displayWidth) / 2;
        const offsetY = (layout.height - displayHeight) / 2;
        ctx.drawImage(image, offsetX, offsetY, displayWidth, displayHeight);

        // draw bounding boxes and label them, if provided
        if (boundingBoxes) {
          ctx.font = `13px monospace`;
          ctx.fillStyle = "#000";
          ctx.textAlign = "left";

          boundingBoxes.forEach((boundingBox, index) => {
            const { objectClass, bounds } = boundingBox;
            const x = offsetX + bounds[0] * scale;
            const y = offsetY + bounds[1] * scale;
            const w = bounds[2] * scale;
            const h = bounds[3] * scale;

            const boxColor = objectColors[index % objectColors.length];
            ctx.strokeStyle = boxColor;
            ctx.lineWidth = 3;
            ctx.beginPath();
            ctx.rect(x, y, w, h);
            ctx.stroke();

            const textHorizontalPadding = 10;
            const textWidth =
              objectClass.length * 6 + 2 * textHorizontalPadding;
            ctx.strokeStyle = "#000";
            ctx.lineWidth = 25;
            ctx.lineCap = "round";
            ctx.beginPath();
            const textStartX = x + w / 2 - textWidth / 2;
            ctx.moveTo(textStartX, y);
            ctx.lineTo(textStartX + textWidth, y);
            ctx.stroke();

            ctx.fillStyle = "#fff";
            ctx.fillText(objectClass, textStartX, y + textBaselineAdjustment);
          });
          ctx.invalidate();
        }
      }
    },
    [ctx, layout, image, boundingBoxes] // dependencies for useCallback
  );
  return (
    <View style={styles.container}>
      <Canvas
        style={StyleSheet.absoluteFill}
        onLayout={(event) => {
          setLayout(event.nativeEvent.layout);
        }}
        onContext2D={setCtx}
      />
      <View style={styles.bottomContainer}>
        <TouchableOpacity onPress={onReset} style={styles.resetButton}>
          <Text style={styles.buttonLabel}>Take another picture</Text>
        </TouchableOpacity>
      </View>
    </View>
  );
}

const styles = StyleSheet.create({
  container: {
    flex: 1,
  },
  bottomContainer: {
    position: "absolute",
    width: "100%",
    bottom: 0,
    left: 0,
    justifyContent: "center",
    alignItems: "center",
  },
  resetButton: {
    backgroundColor: "white",
    paddingHorizontal: 16,
    paddingVertical: 8,
    borderRadius: 20,
    marginBottom: 38,
  },
  buttonLabel: {
    color: "black",
    fontSize: 16,
    fontWeight: "bold",
  },
});

Hi @raedle,
Yes, I changed the name bounds to boxes in objectDetector.js but I had no idea that I had to do the same in ResultScreen.js as well. That is the reason why I got the issue and the error message was not so friendly to help fix.
Regarding the "Take another picture" button, I changed the marginBottom value and now I can use it.
Thanks for the help.


Handle time-range start & end string that contain timezone postfixes like +00:00

Currently when configuring a time-range it handles converting a ISO8601 time string to a ISO8601 time string without seperators, this works pretty well:
timeRange?.start.replace(/[-:.]/g, '')

// "2018-10-17T20:49:00Z".replace(/[-:.]/g, "")
// "20181017T204900Z" = neat

Based on which Date library or formatting you use however, I believe there are a couple of valid isodate strings that this library should support:

2018-10-17T20:49:00+00:00 (Long form UTC, I believe this should auto-convert to Z) - currently this becomes the invalid string: 20181017T204900+0000.
2018-10-17T20:49:00+08:00 (Local time, must not be used rfc5545) - currently becomes 20181017T204900+0800. My thoughts are this should strip the +0800 part OR maybe even throw an error that the user passed a non-UTC timestamp.

👍 Great library - willing to help contribute the above, let me know what you think.

What I recommend doing is to use Date object, or whatever datetime libraries that have toISOString() function and pass the result here instead of using raw timeString. Since this is not a datetime library, I'm not quite willing to add too much datetime logic.

I can agree with that; however changing the string out for a date would be a breaking change - in addition you'd still need to postprocess toISOString() to get valid input.
// note, regex unmerged for clarity - removes milliseconds and seperator characters.
date.toISOString().replace(/\.[0-9]{3}/, '').replace(/[-:.]/g, '')

All ISO8601 should be supported in v1.1.0 now, and non-ISO8601 format will cause an error be thrown. Since time range is now validated.


presets as external JSON files

would be handy to have presets exist outside the code, for a number of reasons.

user could define their own preset, save it to disk, and have ardent "recognize" it as an option
presets "in" the code are somewhat obscured to the user (e.g., how to make a preset if you have to edit the code?)
presets which exist outside the code are somewhat more explicit to the user as to what the options are if they do decide to create their own.

As a first step you could just move them out of the code and make them JSON files which can be loaded in from a given directory, however that doesn't solve all issues above (as in, hard to find by the user).  Documentation is probably needed for that.
https://github.com/neurodata/ardent/blob/62e45babf143aa12ace0b0d33eb7e93baf6b6a28/ardent/presets/registration_parameters.py#L4-L8

oh yeah,
after years of trying this,
presets in code has always failed.
clear documentation and a json file, i suspect, will be much easier for
them.
On Fri, Aug 23, 2019 at 11:37 PM Ben Falk<EMAIL_ADDRESS>wrote:

would be handy to have presets exist outside the code, for a number of
reasons.

user could define their own preset, save it to disk, and have
ardent "recognize" it as an option
presets "in" the code are somewhat obscured to the user (e.g., how
to make a preset if you have to edit the code?)
presets which exist outside the code are somewhat more explicit to
the user as to what the options are if they do decide to create their own.

As a first step you could just move them out of the code and make them
JSON files which can be loaded in from a given directory, however that
doesn't solve all issues above (as in, hard to find by the user).
Documentation is probably needed for that.
https://github.com/neurodata/ardent/blob/62e45babf143aa12ace0b0d33eb7e93baf6b6a28/ardent/presets/registration_parameters.py#L4-L8
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/ardent/issues/3?email_source=notifications&email_token=AAAKG4XDQ7JW6OZFPQ5HRKTQGCUF5A5CNFSM4IPFA7Y2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHFB4YA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAKG4QXMSRKORP7Q7AH3TDQGCUF5ANCNFSM4IPFA7YQ
.

--
the glass is all full:  half water, half air.
(i will be on paternity leave for most of september and october)
neurodata.io


ci(eo): move host build files

Description

Move host build files to build/infrastructure/eo

References

https://github.com/Energinet-DataHub/energy-origin-issues/issues/244

Energinet-DataHub/.github/.github/workflows/version-increment-check.yaml does not currently allow renaming or moving YAML files.
Either we extend this reusable workflow or we have to force merge this PR and pray.


Add index.js etc. files to allow requiring stuff without need to refer to dodo/lib and ES6 future proofing exports

// before
require('dodo/lib/logger');

// after
require('dodo/logger');

maybe some deprecation warnings could be given when old style is used...
Also use only ES6 compatible module.exports for now, so export always object containing named exports and ES5 people has to bare the pain of actually requiring stuff with explicit name var BadRequest = require('dodo/errors').BadRequest

Done by @reskontr some time ago 👍


I can't use this project simply by dragging into my workspace

The copy-frameworks target fails when I am building through Xcode.

@drkibitz Thank you for a nice suggestion!
I thought about using it for my project, so I thought it would be fine if I could build with Carthage and CocoaPods.
I think I will challenge to be able to add even with drap and drop!
If something troubles happens, please let me talk.

@ryokosuge The only thing that needs to happen is removing the copy-frameworks run phase in this project. If you read the Carthage documentation for developing frameworks, it actually mentions to not include this phase for your framework. It's meant for App development.

@ryokosuge can we remove the copy-frameworks step?
This is causing a lot of headaches and I ended up forking it to remove it myself?
I can submit a PR, but I would like some feedback before I do that?


No error printed on invalid semantic version

This leads to confusing errors when we aren't setting versions correctly. E.g:
$ helm search repo --debug -l coder-nightly
No results found

See
https://github.com/helm/helm/blob/fc9b46067f8f24a90b52eba31e09b31e69011e93/pkg/repo/index.go#L187-L196

Thanks for raising the issue @ammario. Can you describe in more detail what you mean by "confusing errors"? What do you expect to happen?
I am asking to get a better understanding of your issue as search command works as expected for me.

@ammario Do you use helm lint on your chart before packaging it?

Do you use helm lint on your chart before packaging it?

Interesting... It appears that it is OK to package a chart with an invalid semver. That does not appear to be expected behaviour.
/tmp ><> helm create test-8864
Creating test-8864
/tmp ><> cd test-8864/
/tmp/test-8864 ><> vim Chart.yaml
/tmp/test-8864 ><> cat Chart.yaml
apiVersion: v2
name: test-8864
description: A Helm chart for Kubernetes
type: application
version: foo
appVersion: 1.16.0
/tmp/test-8864 ><> helm package .
Successfully packaged chart and saved it to: /tmp/test-8864/test-8864-foo.tgz

helm lint catches it though.
/tmp/test-8864 ><> helm lint .
==> Linting .
[ERROR] Chart.yaml: version 'foo' is not a valid SemVer
[INFO] Chart.yaml: icon is recommended

Error: 1 chart(s) linted, 1 chart(s) failed

I thought that was one of the scenarios we were supposed to catch on helm package, as the rest of Helm relies on the package being a valid semver to perform things like automatic upgrades to the latest version by default.
We cannot capture and return error output on helm search. It is intentional for Helm to silently ignore packages that are not valid semver. If one package in the repository index is failing a semver check, the entire chart userbase cannot pull any charts from that repository.

So.... Looking at this further, I'd propose we do not look at addressing the helm search case, but instead look at the ways where a user can package a Helm chart with an invalid semver. That should prevent users from packaging and uploading invalid charts in the first place.

@bacongobbler I understand and agree with that DoS angle. I think your proposal of enforcing SemVer in the helm package step is a great solution.

Fixed in #8933.


[bug]: Dependencies in pyproject.toml have module conflicts.

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
amd
VRAM
8GB
What version did you experience this issue on?
main
What happened?
There are multiple dependencies mentioned in the requirements.txt file(the  -> means the indirect dependencies):
opencv-python
mediapipe->opencv-contrib-python
albumentations->opencv-python-headless
basicsr->opencv-python
gfpgan->opencv-python
realesrgan->opencv-python
albumentations->qudida->opencv-python-headless

The official spec  mentioned that the opencv-python package is for the desktop environment, while opencv-python-headless is for the server environment. The documentation also states that these packages (opencv-python,  opencv-contrib-python, opencv-python-headless) cannot be installed simultaneously (the exact wording is: “There are four different packages (see options 1, 2, 3, and 4 below) and you should SELECT ONLY ONE OF THEM.”). This is because they both use the same module name cv2.
During the installation process using pip, the package installed later will override the cv2 module from the previously installed package (specifically, the modules within the cv2 folders that exist in both packages). Furthermore, the dependency graph even includes different versions of these two packages. It is certain that the common files with the same path in these two packages contain different contents. Therefore, there may be functional implications when using them. However, without analyzing the specific code and function call hierarchy of this project, it can be stated that issues related to overwriting and module conflicts do exist.
Steps to Reproduce
pip install InvokeAI
Screenshots
No response
Additional context
Desired Change
Indeed, it is not an ideal behavior for modules to be overwritten, even if they are not actively used or if the overwritten module is the one being called. It introduces uncertainty and can cause issues in the long run, especially if there are changes or updates to the overwritten modules in future development. It is generally recommended to avoid such conflicts and ensure that only the necessary and compatible dependencies are declared in the requirements to maintain a stable and predictable environment for the project.
We believe that although this project can only modify direct dependencies and indirect dependencies are a black box, it is possible to add additional explanations rather than directly declaring both conflicting packages in the requirements.txt file. Or maybe you can check the dependencies and remove the redundant dependencies from the requirements.txt.
Adding extra explanations or documentation about the potential conflicts and the need to choose only one of the conflicting packages can help developers understand the issue and make informed decisions. Including a clear instruction or warning in the project’s documentation can guide users to choose the appropriate package based on their specific requirements.
Contact Details
No response

@lstein some notes about dependency webs ^

There is no longer a requirements.txt file. Do you mean pyproject.toml?

realesrgan

There is no longer a requirements.txt file. Do you mean pyproject.toml?
I'm not sure what to do about this, because some of the conflicts are out of our control. For example:
realesrgan->opencv-python
albumentations->qudida->opencv-python-headless

We need both realesrgan and albumentations, but they're going to fight over opencv.
Suggestions to fix?

Thank you for your response. I mean in pyproject.toml and it's my fault. The conflict in the indirect dependency is really annoying, maybe you can fix it by uninstalling all four opencv related packages after installing the dependency and reinstalling one version of them. Of course, it's possible to leave it alone, since at least no related errors have been reported yet. But it's not a permanent solution, since other projects have encountered cases where the cv2.imshow() function doesn't work properly. Or you can follow the spec that uses the --no-binary option.

Our dependencies have changed substantially since this issue was raised. I don't believe it is a problem now.

I don't think it's fixed. I tried to pip install it using the command pip install "InvokeAI[xformers]" --use-pep517 --extra-index-url https://download.pytorch.org/whl/cu121
and it still downloaded and installed them at the same time.

Sorry, I misunderstood the issue. Yes, it's still a problem, but I'm not sure if it has any functional impact, given the application should be run in its own venv and it hasn't caused problems for us.
To add a bit of detail, here is a representation of the dependency graph for the 3x opencv packages:
❯ pipdeptree -r -p opencv-python
opencv-python==<IP_ADDRESS>
├── controlnet_aux==0.0.7 [requires: opencv-python]
│ └── InvokeAI==4.0.1 [requires: controlnet_aux==0.0.7]
├── facexlib==0.3.0 [requires: opencv-python]
│ └── InvokeAI==4.0.1 [requires: facexlib]
├── invisible-watermark==0.2.0 [requires: opencv-python >=<IP_ADDRESS>]
│ └── InvokeAI==4.0.1 [requires: invisible-watermark==0.2.0]
└── InvokeAI==4.0.1 [requires: opencv-python==<IP_ADDRESS>]

❯ pipdeptree -r -p opencv-python-headless
opencv-python-headless==<IP_ADDRESS>
└── albumentations==1.4.3 [requires: opencv-python-headless >=4.9.0]
└── InvokeAI==4.0.1 [requires: albumentations]

❯ pipdeptree -r -p opencv-contrib-python
opencv-contrib-python==<IP_ADDRESS>
└── mediapipe==0.10.7 [requires: opencv-contrib-python]
└── InvokeAI==4.0.1 [requires: mediapipe==0.10.7]

I understand this could cause problems for users who have customized opencv installations but I don't think there's any way to really resolve the transitive dependency conflicts without making upstream changes.
In the end, invoke is a standalone application and if the conflicts don't cause functional issues for the us, there is fortunately no need to take action here.

Sorry, I misunderstood the issue. Yes, it's still a problem, but I'm not sure if it has any functional impact, given the application should be run in its own venv and it hasn't caused problems for us.
To add a bit of detail, here is a representation of the dependency graph for the 3x opencv packages:
❯ pipdeptree -r -p opencv-python
opencv-python==<IP_ADDRESS>
├── controlnet_aux==0.0.7 [requires: opencv-python]
│ └── InvokeAI==4.0.1 [requires: controlnet_aux==0.0.7]
├── facexlib==0.3.0 [requires: opencv-python]
│ └── InvokeAI==4.0.1 [requires: facexlib]
├── invisible-watermark==0.2.0 [requires: opencv-python >=<IP_ADDRESS>]
│ └── InvokeAI==4.0.1 [requires: invisible-watermark==0.2.0]
└── InvokeAI==4.0.1 [requires: opencv-python==<IP_ADDRESS>]

❯ pipdeptree -r -p opencv-python-headless
opencv-python-headless==<IP_ADDRESS>
└── albumentations==1.4.3 [requires: opencv-python-headless >=4.9.0]
└── InvokeAI==4.0.1 [requires: albumentations]

❯ pipdeptree -r -p opencv-contrib-python
opencv-contrib-python==<IP_ADDRESS>
└── mediapipe==0.10.7 [requires: opencv-contrib-python]
└── InvokeAI==4.0.1 [requires: mediapipe==0.10.7]

I understand this could cause problems for users who have customized opencv installations but I don't think there's any way to really resolve the transitive dependency conflicts without making upstream changes.
In the end, invoke is a standalone application and if the conflicts don't cause functional issues for the us, there is fortunately no need to take action here.

Yeah, you're right. Thank you for your reply.
But it may also be because the call chain is particularly deep and there may be some implicit bugs.
Anyway, we can leave it alone for now since it has not led to problems.

No worries. I'm going to close this as a nofix. We can address issues if they arise.


[oneDNN] Windows CI Set python path env vars if not already set

resubmit of https://github.com/tensorflow/tensorflow/pull/55523

Tagging @learning-to-play and @mihaimaruseac for this PR.


'exports' is undefined

Even though we have transpiled through webpack we are getting the above mentioned error @ line
exports.__esModule = true; in client.js file. What could be the issue?

I could solve this issue.


REDO: Fixed aws_vpn_gateway_route_propagation for default route table

Redo of PR https://github.com/terraform-aws-modules/terraform-aws-vpc/pull/94

cd exampled/complete-vpc

terraform init

Initializing modules...
- module.vpc
  Getting source "../../"

Error: resource 'aws_vpn_gateway_route_propagation.default' config: unknown resource 'aws_default_route_table.this' referenced in variable aws_default_route_table.this.*.id

Always run examples/complete-vpc to verify that it works.

@antonbabenko That's my mistake, good catch. I had assumed the PR was basically ready to go. I do have a question though. The offending reference you found is from this block:
resource "aws_vpn_gateway_route_propagation" "default" {
  count = "${var.create_vpc && var.propagate_default_route_tables_vgw && (var.enable_vpn_gateway || var.vpn_gateway_id != "") ? 1 : 0}"
  route_table_id = "${element(aws_default_route_table.this.*.id, count.index)}"
  vpn_gateway_id = "${element(concat(aws_vpn_gateway.this.*.id, aws_vpn_gateway_attachment.this.*.vpn_gateway_id), count.index)}"
}

And specifically the reference to aws_default_route_table.this.*.id is the culprit. You mentioned here (https://github.com/terraform-aws-modules/terraform-aws-vpc/pull/94#issuecomment-392361682) that aws_default_route_table was removed, yet this PR wants to add propagate_default_route_tables_vgw as a variable.
Are we adding aws_default_route_table back in? Or using another method? I'm not sure the history of the original PR; perhaps there was a reason it went stale.

Closing since this is not needed / supported anymore.


Add support for .NET Standard

Customer reported issue.
Currently you can't install the Microsoft.Azure.Mobile.Client package to a netstandard project because certain dependencies are incompatible producing the following error:
Microsoft.Azure.Mobile.Client 2.1.0 is not compatible with .NETStandard,Version=v1.3.
Microsoft.Bcl 1.1.10 is not compatible with .NETStandard,Version=v1.3.
Microsoft.Net.Http 2.2.29 is not compatible with .NETStandard,Version=v1.3.
Some packages are not compatible with .NETStandard,Version=v1.3.
Need to add support for .Net standard

Bump. Same issue here. Tried to update to .net standard, but can't seem to get past this frustrating oversight

looking forward to this.
Usually one can still add a reference to PCL nugets from .NETStandard, but it appears that azure mobile apps contains a conflicting HttpClient reference which cannot be resolved. Therefore cannot upgrade to .NETStandard until this is fixed.

I'm getting this error when using version 3.0.3 on a netstandard1.1 project:
1>CSC : error CS1703: Multiple assemblies with equivalent identity have been imported: 'C:\Users\antao.nuget\packages\Microsoft.Net.Http\2.2.29\lib\portable-net40+sl4+win8+wp71+wpa81\System.Net.Http.dll' and 'C:\Users\antao.nuget\packages\System.Net.Http\4.3.0\ref\netstandard1.1\System.Net.Http.dll'. Remove one of the duplicate references.

I have a branch that I'm working on now - if anyone wants to try building it - fork adrianhall/azure-mobile-apps-net-client branch netstandard11 - I'm still testing, but early availability for those that want to take a peek.

Copying the discussion from the PR:
@twsouthwick One thing to consider since you are planning on having this a major change: Do you want support for the same platforms, or are you okay dropping support for older platforms (such as WinPhone 8.0)?
@adrianhall I think we want to move to .NETStandard 1.2 or 1.3 - I'm ok with dropping support for Windows 8.0 and Windows Phone 8.0 in the v4.0.0 release (which is what this will become)
@twsouthwick Ok. After looking more at the code (and having done multiple conversions to .NET Standard), I'm not sure about the original direction I took with this. The project right now is bundling two libraries with every platform: a platform specific and a portable. Instead of doing this, have you thought about using shared projects and having a single library for each platform, but have it the same name? Or can you get all that you need from .NET Standard and are hoping to eliminate any platform specific code?
@adrianhall It's more of a platform intent. We need to support Xamarin.iOS, Xamarin.Android, Xamarin.Forms (Windows 8.1, Windows Phone 8.1, UWP, iOS, Android), UWP, Windows Phone 8.1 and Windows 8.1.
There are two problematic areas that always come up - the first is identity. We use Xamarin.Auth for the Xamarin components and native web forms for the others. The second is the offline sync cache, which uses SQLitePCLRaw for the offline store.
We need a single library, so the same code can be used in a cross-platform solution (e.g. when we have a Xamarin Forms app that covers UWP, iOS and Android.

I think @aalmada is running into #82 specifically, so that may also be a predecessor step to going full on .NETStandard.

Release 4.0.0-alpha - .NETStandard 1.4 release.


common component used for client logo

Notion card

https://www.notion.so/saeloun/Use-Avatar-common-component-for-displaying-client-images-on-the-client-list-page-eeaf5ac8410049c8af80b41cff89491a

Summary

Common avatar component used for client page.
Accounts aging header spacing fixed for mobile view.

Preview

Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Refactor (non-breaking and retains same functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist:

[x] I have manually tested all workflows
[x] I have performed a self-review of my own code
[ ] I have annotated changes in the PR that are relevant to the reviewer
[ ] I have added automated tests for my code

@Shruti-Apte Please see the loom video https://www.loom.com/share/9450976bde704f8694d8443164974a95 cc @supriya3105

@Shruti-Apte This is some weird behavior on deleting logo https://www.loom.com/share/926d4a2f7cab48b0a2feaf4a579151ff

@apoorv1316 Please test this again and approve if everything is working fine.

@Shruti-Apte On the new client modal image is not showing up after attaching. https://www.loom.com/share/264e34c8af5644b0883028a9dbc729bb


"Progressive" hydraulic and water quality steps

This feature enables API users to use runH and runQ in a stepwise fashion. It is mostly implemented as of 434d78c6ed8b5e4a95380e634798406188ef48e9 with modifications and fixes since then.
The feature should be tested and documented before rolling into a release, so I'm targeting this for v2.1

bumping this from 2.1 since it seems to introduce discrepancies w/r/t/ old simulation results.

perhaps this feature is fine for inclusion in 2.1 -- i ran a Net3 hyd/wq simulation and ran a diff on the hex dump of the binary results files from both the 2.00.12 and the 2.1 version at 7dfd7f748d8ff2e24163c0f7a28325667614152e and the files are exactly the same except for the version number in the header section, as expected. we should probably test this more thoroughly though.

I think Net 3 is source tracing and not 'real' quality.
On Sep 15, 2015 6:39 PM, "Sam Hatchett"<EMAIL_ADDRESS>wrote:

perhaps this feature is fine for inclusion in 2.1 -- i ran a Net3 hyd/wq
simulation and ran a diff on the hex dump of the binary results files from
both the 2.00.12 and the 2.1 version at 7dfd7f7
https://github.com/OpenWaterAnalytics/EPANET/commit/7dfd7f748d8ff2e24163c0f7a28325667614152e
and the files are exactly the same except for the version number in the
header section, as expected. we should probably test this more thoroughly
though.
—
Reply to this email directly or view it on GitHub
https://github.com/OpenWaterAnalytics/EPANET/issues/12#issuecomment-140435557
.

good point - what networks / quality settings should we use to standardize the regression testing?

I think I tested with net 1.
On Sep 15, 2015 6:58 PM, "Sam Hatchett"<EMAIL_ADDRESS>wrote:

good point - what networks / quality settings should we use to standardize
the regression testing?
—
Reply to this email directly or view it on GitHub
https://github.com/OpenWaterAnalytics/EPANET/issues/12#issuecomment-140441704
.

If we chose to include progressive stepping we should develop an example for testing and for demo/training. Also changes to toolkit API means we should update toolkit help files. Make sense?

@michaeltryby Makes a lot of sense. We started a documentation issue, maybe you know if there is an editable version of the help file?

I have tested again Net1 and Ne2 with the 2.0.12 Toolkit and the latest 2.1 version. Tested with ENepanet function.
The report files are here:
Net1 2.0.12
Net1 2.1
Net2 2.0.12
Net2 2.1
I don't see differences in the quality results. In net 2  there are some, very small, numerical differences. Maybe it's the size of floats?

@samhatchett and @eladsal So I guess the issue here is that progressive stepping hasn't undergone thorough testing?
We could make it an option in the CLE and run the entire test-suite using it and then look for any differences. How does that sound?

@samhatchett and @eladsal I dug into this a little deeper and I have discovered that while the hydraulics and water quality progress concurrently, the report and binary output file writing capabilities are not functioning.

@samhatchett and @eladsal how are the various save flags supposed to be set for this feature to work?

I suppose the answer depends on what you mean by "work" - the toolkit produces results (accessible via the API getters) - but I don't know the status of writing report and binary results files. Really the purpose of the "Progressive" feature was to avoid those considerations altogether.

There is discussion of this thread about comparing report and binary files. What is that about then?

So this feature as it was envisioned breaks report and binary files.

No @michaeltryby - this feature, as envisioned, ignores them. The fact that they are produced at all is perhaps convenient for testing purposes. Using this feature in concert with save flags is an edge case that we've not really explored yet (to your question).

Well then I guess this feature, isn't fully baked then.

Since I'm re-coding the water quality module to address the mass balance error issue #160 I was plannng to include the "progressive" (needs a better name - maybe synchronous) option as part of that work. I will try to make it produce results the same as the sequential option.
One reason results might differ (very slightly) in the current code is that when the sequential option reads a flow off of the hydraulic results file for a CLOSED link that flow was saved to the file as 0 but with the synchronous method it will have some non-zero value.

Concurrent might be a better name.


Invalid line number is reported in line-continuation

Example
let g:v = {'a': 1}
let g:a = deepcopy(
      \ g:v["a"])

otuput
vint_check.vim:2:13: Prefer single quoted strings (see Google VimScript Style Guide (Strings))

Line 3 should be reported as an error but line 2 is reported.

vint version 0.3.0

Thanks for reporting the bug.
The cause of this bug is in vim-vimlparser.
I'm gonna report the bug to vim-vimlparser.

I see, thanks.

Reported: https://github.com/ynkdir/vim-vimlparser/issues/16

The bug will be fixed by the next release v0.3.1.


Delineate day and schedule name in custom events modal

Right now, the days and schedules look like they're part of the same list. I think that there should be labels/headings to indicate the two. I think it would look better as well in addition to being quicker to parse.

This is a screenshot my implementation of the form, what do you think?

I think only a heading or dividing line is necessary, not both. That matters on mobile especially because of the limited space. On that note, you might want to check how it looks on mobile. Otherwise, it looks good and pretty clean 👍

It's not too bad; it overflows + scrolls, weird sizing, but legible at least.

I don't like dealing with UI, much less mobile UI lol. But any feedback/concrete UI decisions are appreciated -- especially for the Alpha branch since I can do whatever I want there

Maybe we can do something similar to how Zotcourse allows users to create a custom event:

A lot of space seems to be saved by abbreviating the days of the week, so maybe by doing this, there won't be any overflowing or weird scrolling.
I can try to find a good way to implement this!

@teresa-liang That looks pretty good!

Goal: finish in 2 weeks (10/19)


python310Packages.wasabi: 1.1.0 -> 1.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.wasabi is: A lightweight console printing and formatting toolkit
meta.homepage for python310Packages.wasabi is: https://github.com/ines/wasabi
meta.changelog for python310Packages.wasabi is: https://github.com/ines/wasabi/releases/tag/v1.1.1
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.1.1 with grep in /nix/store/1g8bghs17mvh8r46m9yl3hwj7iynnv0x-python3.10-wasabi-1.1.1
found 1.1.1 in filename of file in /nix/store/1g8bghs17mvh8r46m9yl3hwj7iynnv0x-python3.10-wasabi-1.1.1

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.spacy
python310Packages.spacy-loggers
python310Packages.spacy-transformers
python310Packages.textacy
python310Packages.thinc
python310Packages.wasabi
python311Packages.thinc
python311Packages.wasabi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1g8bghs17mvh8r46m9yl3hwj7iynnv0x-python3.10-wasabi-1.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.wasabi https://github.com/r-ryantm/nixpkgs/archive/dea63f8d76c944b8613493729c3b3d579fa95ae3.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1g8bghs17mvh8r46m9yl3hwj7iynnv0x-python3.10-wasabi-1.1.1
ls -la /nix/store/1g8bghs17mvh8r46m9yl3hwj7iynnv0x-python3.10-wasabi-1.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

7 packages failed to build:

python310Packages.spacy
python310Packages.spacy-loggers
python310Packages.spacy-transformers
python310Packages.textacy
python310Packages.thinc
python311Packages.thinc
python311Packages.wasabi

1 package built:

python310Packages.wasabi

Maintainer pings

Please reopen.


Add JSON support to the MySQL backend

This is a small change, based on what the PostgreSQL code looks like. There is no #define for the type, though, and for old library versions the enum is not available either, so I have put the constant instead, as with MYSQL_TYPE_NEWDECIMAL

Looks good to me


quantize_into_bins_with_labels

Oui Paul, I hope you are doing well. We met on December 2023 and discussed this function. If You would find some time, I would appreciate if I could contribute one more function. Thanks, Bart.

Hi @bartfigas.
Thanks for your contribution.
I am merging now.
I will adapt a bit to give the possibility to give labels when value is lower than the lower bound.
You will have then the possiblity to pass

['Fail', 'Wait for result exam', 'Pass', 'Pass with mention'] OR
['lower than very bad', 'Fail', 'Wait for result exam', 'Pass', 'Pass with mention', 'genius']

If value is lower than the lower bound you'll have:

UNDEFINED_INF if first case
lower than very bad if second case

It is deployed and running!
Thanks a lot @bartfigas
Don't hesitate to contribute again !


use upstream_cluster_raw for json access log

Fixes https://github.com/istio/istio/issues/54219

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Dual Stack
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

In response to a cherrypick label: new pull request created: #54225

In response to a cherrypick label: new pull request created: #54226

In response to a cherrypick label: new pull request created: #54227

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio/istio#release-1.22 from head istio-testing:cherry-pick-54224-to-release-1.22: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-54224-to-release-1.22."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio/istio#release-1.23 from head istio-testing:cherry-pick-54224-to-release-1.23: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-54224-to-release-1.23."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio/istio#release-1.22 from head istio-testing:cherry-pick-54224-to-release-1.22: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-54224-to-release-1.22."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio/istio#release-1.23 from head istio-testing:cherry-pick-54224-to-release-1.23: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-54224-to-release-1.23."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio/istio#release-1.24 from head istio-testing:cherry-pick-54224-to-release-1.24: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-54224-to-release-1.24."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}

In response to a cherrypick label: new pull request could not be created: failed to create pull request against istio/istio#release-1.24 from head istio-testing:cherry-pick-54224-to-release-1.24: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for istio-testing:cherry-pick-54224-to-release-1.24."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"}


Adjust PAWN function to support 1D matrix for convenience

Say a user was assessing the mean of some scenario outcome
μ_tac = mean(ADRIA.metrics.scenario_total_cover(rs), dims=:timesteps)
ADRIA.sensitivity.pawn(rs, μ_tac)

Previously, this would fail with an error as μ_tac would be a matrix (i.e., $1 \times N$) rather than a vector which the method expects.
The change also supports transposed matrices:
μ_tac = mean(ADRIA.metrics.scenario_total_cover(rs), dims=:timesteps)'  # note the transpose!
ADRIA.sensitivity.pawn(rs, μ_tac)

The above μ_tac would be an $N \times 1$ matrix (again, instead of a vector).
The PR supports implicit conversion to vector simply for convenience.
Originally, the user was expected to convert to vector explicitly prior to use:
μ_tac = vec(mean(ADRIA.metrics.scenario_total_cover(rs), dims=:timesteps))

which is a little tedious to remember to do every time.
This PR also expands and updates the docstring to detail all methods and provide additional contextual information of the method.

All done, ready for second review.

I think I've fixed all line length issues, let me know if I missed anything again.


Have a way to create packages for Archivematica from existing born-digital content

[ ] Uncatalogued
[ ] Catalogued collections
[ ] V drive

Trudy sent me the spreadsheet of the 65 catalogued collections they want to export, and I've been able to grab all the files from Preservica for those collections, bar four. (I've downloaded them using the Preservica API, but I haven't compared to Preservica's checksums.)
Four files from the Dr. Dave King archive threw 500 errors when I tried to download them:
8d3477db-12a9-460f-afc3-283727bdc9eb PPKIN/2042/4/1/5
2308c98b-e8ac-4e40-b6d0-3d59d0755dfa PPKIN/2042/5/1/1/5
15bb086c-3d89-4e5e-bb14-202c848e958b PPKIN/5/1/3/5
705c0d12-b986-486b-8149-ec93e3088209 PPKIN/2042/7/1/6

Possibly significant: all four of these are an index.html page.
I haven't assembled Archivematica packages for these yet, but I do have the metadata.csv, so I think it's just zipping them up and uploading them to S3. 247GB in total.

^^ Jonathan was able to get all four of those files from Preservica from me, it seems to be a bug in the API that meant I couldn't download them.


Update 2025-01-28-src.md

fixed scheduling and added registration details in description
TODO: Describe your changes here..

I'll review + add some pulsar changes saskia's requesting in person.

[x] saskia moved it into the subtopic
[ ] my pulsar part needs better LOs/KPs
[ ] set priority on the tutorials to ensure they're sorted next to each other in the Cloud group
[ ] add the use cases to the top of the pulsar to help learners know if it is for them.
[ ] set priority on all to move 'galaxy on the cloud' to the top.


Implement InChI to SMILES conversion

Implement InChI to canonical SMILES conversion using RDkit.
Close #5.

@xtrojak can we add some unit tests and the isomeric smiles version as well? That would be great!

@xtrojak can we add some unit tests and the isomeric smiles version as well? That would be great!

Done both.

To fix the CI, we need to merge main to this branch after #140 is merged.


Update 2015-04-25-welcome-to-open-source-design.markdown

updated all permal links to shorter urls as discussed in events issue #26
also added a redirect of the old links to the new perma links

HTML Proofer is not able to check the new permalinks and therefore fails.

Awesome, tested locally and they work - let's see on live!

Hopefully they are doing live the same job as local :D

Oh, we have to enable it in the config too! So that the redirects work.
gems:
  - jekyll-redirect-from


Delete the IntegrationEventContext once consumed

Depends on https://github.com/Activiti/Activiti/pull/1536.

Codecov Report

Merging #6 into develop will increase coverage by 0.06%.
The diff coverage is 100%.

@@              Coverage Diff              @@
##             develop       #6      +/-   ##
=============================================
+ Coverage      59.19%   59.25%   +0.06%
  Complexity        54       54
=============================================
  Files             56       56
  Lines            620      621       +1
  Branches          12       12
=============================================
+ Hits             367      368       +1
  Misses           248      248
  Partials           5        5

Impacted Files
Coverage Δ
Complexity Δ

...nnel/ServiceTaskIntegrationResultEventHandler.java
71.42% <100%> (ø)
3 <2> (?)

Continue to review full report at Codecov.

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

@erdemedeiros @ryandawsonuk good to merge.. unfortunately I'm on a train and compiling and testing this is impossible.


Preview page hotkeys not working after preview is modified mid query

Info

Operating System:
Shell: bash
Terminal: iterm2
nvim --version: 0.7.2
fzf --version: 0.30.0

Relevant config (I didn't want to post the entire config as it's large but posted relevant piece below):
require('fzf-lua').setup({
  keymap = {
    -- These override the default tables completely
    -- no need to set to `false` to disable a bind
    -- delete or modify is sufficient
    builtin = {
      ["<C-]>"]        = "toggle-preview-cw",
    },
    fzf = {
     -- fzf '--bind=' options
      ["ctrl-f"]      = "half-page-down",
      ["ctrl-b"]      = "half-page-up",
      ["ctrl-a"]      = "beginning-of-line",
      ["ctrl-e"]      = "end-of-line",
      ["ctrl-d"]      = "preview-page-down",
      ["ctrl-u"]      = "preview-page-up",
    },
  },
})

Description
When I go into files and hit the toggle-preview-cw button, I am unable to use my hotkey for preview-page-down or up. Those keys get "unbind" so to speak. Is this intentional?

When I go into files and hit the toggle-preview-cw button, I am unable to use my hotkey for preview-page-down or up. Those keys get "unbind" so to speak. Is this intentional?

When using the keymap table the default options don't get merged with your table, that's intentional due to keymaps being a highly customizable and personal perference, this helps prevent the need to specify [<bind>] =false to disable a default bind.
FzfLua has 2 different previewer types, "builtin", which uses neovim's builtin window and "fzf" which uses fzf's native previewer functionality inside the terminal, that's why you have 2 different keybind sets, depending on the one you use you'll can have different binds (that's also why the different format in their config, one set is neovim style binds and the other is fzf binary style binds).
The fact you're able to use toggle-preview-cw tells me you're using one of the "builtin" previewers with a neovim window as this funcionality isn't implemented for native fzf previewers.
In the above config you posted there are no binds for preview page up|down for the builtin previewers, that's why it doesn't work and is unrelated to pressing the bind fortoggle-preview-cw, to restore this functionality also specify the preview up|down binds under keymap.builtin:
require('fzf-lua').setup({
  keymap = {
    builtin = {
      ["<C-]>"]  = "toggle-preview-cw",
      ["<C-d>"]  = "preview-page-down",  -- Add this lines
      ["<C-u>"]  = "preview-page-up",    -- Add this line
    },
    fzf = {
        -- these stay the same as you use them for example with `git_` providers
    },
  },
})

Oh, I'm following now. Thank you so much. That makes a lot of sense.


mailutils tests fail on stdenv-updates after switch to GCC 4.8.

I haven't looked too deeply into it, but couldn't find anything obvious on the web.
The test failures:
Running /tmp/nix-build-mailutils-2.2.drv-0/mailutils-2.2/imap4d/testsuite/imap4d/fetch.exp ...
FAIL: FETCH 3 BODY[1.MIME]
FAIL: FETCH 4 BODY[2.2.1]
FAIL: FETCH 4 BODY[2.2.1.TEXT]
FAIL: FETCH 4 BODY[2.2.TEXT]
FAIL: FETCH 5 BODY[2.TEXT]

Full build output: https://gist.github.com/falsifian/ad1fd6fbc097b5a4d321
The offending commit is e9b30710, which switches stdenv to GCC 4.8.0.

This is passing now, closing.


Unicode icons issue

For an unknown reason, I can only see 4 Unicode icons under the “Icon Theme file content” paragraph of the “Icon Theme” subsection within the “Theme” section (see the attached picture) on LSD Readme page.
I have tested this issue across several browsers, including Vivaldi, Brave, Microsoft Edge, and Firefox, all of which exhibit the same problem. I am using a MacBook Air with the M3 chip, running the latest version of macOS Sequoia (15.1.0).
Additionally, I tried accessing the page on a Windows 11 machine using Google Chrome and Microsoft Edge, but the issue persists across these platforms as well.
Does anyone have any idea why this might be happening and how I can resolve it getting all the icons to show up?
Thanks in advance for your help!

I don't know, but I think that I have a similar issue:

lsd 1.1.5
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

I don't know, but I think that I have a similar issue:

lsd 1.1.5
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

Yout need a Nerd Font

I don't know, but I think that I have a similar issue:

lsd 1.1.5
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

You need a Nerd Font and set the font family of your terminal to that font.

https://github.com/getnf/getnf

oes anyone have any idea why this might be happening and how I can resolve it getting all the icons to show up?
Thanks in advance for your help!

Maybe you need a Nerd Font and set the font family of your terminal to that font.

https://github.com/getnf/getnf

I don't know, but I think that I have a similar issue:

lsd 1.1.5
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

Maybe you need a Nerd Font and set the font family of your terminal to that font.

https://github.com/getnf/getnf

Thanks for your comment, but not. I installed a nerd fonf but nothing. Also I tested it with Debian 11, and nothing.

Thanks for your comment, but not. I installed a nerd fonf but nothing. Also I tested it with Debian 11, and nothing.

Which terminal are you using? You have to configure your terminal to use that font after you install it.
I prefer Hack Nerd Font and Comic Code

I'm using Terminator 2.1.0 and maybe this is the problem.. but in my theme changer I can see the font and is loaded.. but in the preferences of Terminator not.. maybe is a problem with Terminator.. but is weird because other programs can see the font..

I'm using Terminator 2.1.0 and maybe this is the problem.. but in my theme changer I can see the font and is loaded.. but in the preferences of Terminator not.. maybe is a problem with Terminator.. but is weird because other programs can see the font..

Some icons are not showing in my Terminator too, but I never use Terminator.

Maybe you can try wezterm.

mmm, I don't know, change the terminal only to try to resolve the issue? with me we are two user with different terminals that maybe haven the problem. Maybe this is not the way.. Well, I was only notifying that. On the other hand wezterm seems that not have everything that I have with Terminator, and also works on new OSs.. I have my PC for production and it is a Debian stable were wezterm doesn't works. But don't worries, I can live without lsd. I'll waiting..

Thanks so much for the help @Fengzi21, as @Fengzi21 mentioned, the font settings cause this, and for Terminator, there is nothing we can do.
maybe you could try another nerd font theme @hpsaturn and see whether it helps.