fix(module:input):fix nz-input's nzSize not work when nz-input not set nzDisabled property

fix(module:input):fix nz-input's nzSize not work when nz-input not set nzDisabled property
PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

if I do not set 'nzDisabled' property on nz-input ,'nzSize' will not work fine.

Issue Number:#208
What is the new behavior?
if I only set nzSize like 'nzSize'="'large'", nz-input can work fine.
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Coverage decreased (-0.004%) to 40.348% when pulling d91da3b756d5e91231d16407f3f5d25f187aff0f on gsbybb:input_size_bug into 414241c4baeca50434c867648a8bb5cb0e8159bc on NG-ZORRO:master.


.transformReplace() does not return the amount specified.

What happens:
The amount returned was not correct.  Regardless of what number I used in transformReplace (ranging from 3 to 8), it always returned twice that minus 2.  However, this ONLY occurs when you craft with a single item.  For instance, if you place a single item (an Item Stack of 1) in the crafting grid to be replaced with another after completing the recipe, it will replace said item in the crafting grid with the wrong amount.
If, however, you place a stack higher than one in the crafting grid and complete the recipe, the specified amount of the item you expected will be placed in your inventory.  It only occurs when the last item crafted is replaced inside the crafting grid.
EXTRA: Upon further testing for workarounds, there are several other odd behaviors.  I tried making the recipe output the 8x items while transforming the item in the grid one-to-one.  In THIS way, if I place a full stack (64) of the item into the grid, and shift-click to craft all, it returns 8 stacks of the item as expected (if there is inventory space), but deletes the rest, and also only returns 63 of what should have been a one-to-one conversion.  One simply disappears when you craft all at once.
What you expected to happen:
The recipes in question were expected to return 8 of the specified block/item.
Script used:
https://pastebin.com/fqHDYWnR
Minetweaker.log file:
https://pastebin.com/hrGMQ8uZ

Affected Versions (Do not use "latest"):

Minecraft: 1.9  &  1.11.2
Forge: 12.17.2051 & 13.20.2282
Crafttweaker:  1.9-2.3.2 & 1.11.2-3.0.24

Your most recent log file where the issue was present:
https://pastebin.com/f3nwnQ59

I'm seeing similar behavior on 1.10

Fixed in later versions (aka 1.12)

You sure?  The number of items returned is now double that which is entered.  For example, when I want 8 of an item to be returned from a transformReplace, I get 16.  To compensate, I entered 4.  However, this doesn't work when operating on a full stack.  Instead of getting 8 stacks back, I get 4 stacks, plus 4.
What you expected to happen:
The recipes in question were expected to return 8 of the specified block/item.
Script used:
https://pastebin.com/GhvqHh4c
Minetweaker.log file:
https://pastebin.com/v71306vn

Affected Versions (Do not use "latest"):

Minecraft:  1.12.2
Forge: <IP_ADDRESS>07
Crafttweaker:  1.12.2-4.1.0

Your most recent log file where the issue was present:
https://pastebin.com/U4dpV9Em


Support hire Stream Kanban

PR includes

[x] Feature

Related issues

QA Instructions, Screenshots, Recordings
https://github.com/user-attachments/assets/77489a3a-4b09-4e09-80c8-147481ca4694


Windows installer enhanced.

The installer should create a folder entry in the programs menu along with the uninstaller.
Perhaps the installer should also prompt for install location instead of defaulting to user/local.

perhaps some of the existing options would achieve this? https://www.electron.build/configuration/nsis


Chrome or Edge (Webkit) Out of Memory (oom) crash within seconds of WASM bevy builds

Bevy version
Tested with Main branch with commit ab83336f along with release-0.6.1 @ 6acf932c
Operating system & version
Windows 10 21H2
Chrome 98.0.4758.102 (Official Build) (64-bit)
What you did
Essentially followed the WASM section of the examples readme.
I used these commands to build the text_debug example, without the --no-default-features flag, or else it wouldn't build. Modified index.html to point to wasm_example.js after building. Launched with basic-http-server examples/wasm
 cargo build --example text_debug --target wasm32-unknown-unknown
 wasm-bindgen --out-name wasm_example  --out-dir examples/wasm/target --target web target/wasm32-unknown-unknown/debug/examples/text_debug.wasm

What you expected to happen
Expected The text_debug example to launch and render in the browser.
What actually happened
It would launch and render for a few seconds, while being very stuttery then the tab would crash from and out of memory error.
Additional information
It would happen with any of the example projects.
Came across this reddit post describing this workaround which I tested working:
set in Cargo.toml
[profile.dev]
opt-level = 2

Creating this issue since I didn't see one yet as requested in
https://www.reddit.com/r/rust/comments/s06vx3/how_to_get_a_developerfriendly_workflow_with_bevy/hs0228d/

For wasm, I would recommend building either with --release, or with opt-level = 3.
Does it work with the commands from the readme?
https://github.com/bevyengine/bevy/blob/28ba87e6c8f48a6b41b6743b748a72d41728523c/examples/README.md?plain=1#L398-L399
It has been updated in main but not yet for the other branches

Thanks for the quick response.
Building with --release runs in chrome without out of memory crashes without needing to put opt-level = 2 or opt-level = 3 in the Cargo.toml
I'm using portable VSCode on Windows 10 with the codelldb plugin on the autogenerated launch.json, but modified to include wasm target and added the --release to reflect the example readme. It doesn't use codelldb for debugging, only as a makeshift method to quickly compile and bind for wasm, then launch basic-http-server to listen on all interfaces <IP_ADDRESS>:4000
        {
            "type": "lldb",
            "request": "launch",
            "name": "Run WASM example 'sprite'",
            "cargo": {
                "args": [
                    "build",
                    "--example=sprite",
                    "--package=bevy",
                    "--release",
                    "--target=wasm32-unknown-unknown"
                ],
                "filter": {
                    "name": "sprite",
                    "kind": "example"
                }
            },

            "program": "cmd.exe",
            "args": ["/s", "/c", "echo Starting wasm-bindgen... ${cargo:program}  && wasm-bindgen --out-name wasm_example --out-dir examples/wasm/target --target web ${cargo:program} && echo Starting basic http server with wmic to prevent vscode terminal blocking on child process... && >nul wmic process call create 'cmd /c basic-http-server -a <IP_ADDRESS>:4000 examples/wasm','%cd%'"],
            "cwd": "${workspaceFolder}"
        }

Observed the same behavior as described in #3867 where it didn't crash in debug builds (with no explicit optimization levels) if i had the dev tools open.

Hi everyone, I am running into a similar issue as well.
Bevy version
0.6.0
Operating system & version
Ubuntu 20.04
What you did

cargo new new_project
Copied the code for https://bevyengine.org/examples/game/breakout/ into main.rs
Added bevy = "0.6" into Cargo.toml
Followed the tutorial here https://bevy-cheatbook.github.io/platforms/wasm.html#quick-start to start a minimal local webserver

What you expected to happen
The game not to crash on the browser
What actually happened
Exactly as described by @JCBuck . It would launch and render for a few seconds, while being very stuttery then the tab would crash from and out of memory error.
Additional information

I am using brave browser
Doesn't crash if I build w/ --release or opt-level = 3


Possibility of using pretrained weights for neck and heads ? #100

Greetings,
Is it possible to initialize neck and heads with pre-trained weights just like how it is possible for backbone ? If not, then how can I modify the config/scripts to achieve it ?
Thanks

You could try to modify the init_cfg and use similar config as those in backbone.


error while installing chatterbot

I got this error everytime I try to install chatterbot.
Collecting spacy<2.2,>=2.1
Using cached spacy-2.1.9.tar.gz (30.7 MB)
Installing build dependencies ... error
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> [375 lines of output]
Collecting setuptools
Using cached setuptools-65.0.2-py3-none-any.whl (1.2 MB)
Collecting wheel<0.33.0,>0.32.0
Using cached wheel-0.32.3-py2.py3-none-any.whl (21 kB)
Collecting Cython
Using cached Cython-0.29.32-py2.py3-none-any.whl (986 kB)
Collecting cymem<2.1.0,>=2.0.2
Using cached cymem-2.0.6-cp310-cp310-win_amd64.whl (36 kB)
Collecting preshed<2.1.0,>=2.0.1
Using cached preshed-2.0.1.tar.gz (113 kB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting murmurhash<1.1.0,>=0.28.0
Using cached murmurhash-1.0.8-cp310-cp310-win_amd64.whl (18 kB)
Collecting thinc<7.1.0,>=7.0.8
Using cached thinc-7.0.8.tar.gz (1.9 MB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting blis<0.3.0,>=0.2.1
Using cached blis-0.2.4.tar.gz (1.5 MB)
Preparing metadata (setup.py): started
Preparing metadata (setup.py): finished with status 'done'
Collecting wasabi<1.1.0,>=0.0.9
Using cached wasabi-0.10.1-py3-none-any.whl (26 kB)
Collecting srsly<1.1.0,>=0.0.6
Using cached srsly-1.0.5.tar.gz (86 kB)
Installing build dependencies: started
Installing build dependencies: finished with status 'done'
Getting requirements to build wheel: started
Getting requirements to build wheel: finished with status 'done'
Installing backend dependencies: started
Installing backend dependencies: finished with status 'done'
Preparing metadata (pyproject.toml): started
Preparing metadata (pyproject.toml): finished with status 'done'
Collecting numpy>=1.7.0
Using cached numpy-1.23.2-cp310-cp310-win_amd64.whl (14.6 MB)
Collecting plac<1.0.0,>=0.9.6
Using cached plac-0.9.6-py2.py3-none-any.whl (20 kB)
Collecting tqdm<5.0.0,>=4.10.0
Using cached tqdm-4.64.0-py2.py3-none-any.whl (78 kB)
Collecting colorama
Using cached colorama-0.4.5-py2.py3-none-any.whl (16 kB)
Building wheels for collected packages: preshed, thinc, blis, srsly
Building wheel for preshed (setup.py): started
Building wheel for preshed (setup.py): finished with status 'error'
error: subprocess-exited-with-error
    python setup.py bdist_wheel did not run successfully.
    exit code: 1

    [21 lines of output]
    running bdist_wheel
    running build
    running build_py
    creating build
    creating build\lib.win-amd64-3.10
    creating build\lib.win-amd64-3.10\preshed
    copying preshed\about.py -> build\lib.win-amd64-3.10\preshed
    copying preshed\__init__.py -> build\lib.win-amd64-3.10\preshed
    creating build\lib.win-amd64-3.10\preshed\tests
    copying preshed\tests\test_counter.py -> build\lib.win-amd64-3.10\preshed\tests
    copying preshed\tests\test_hashing.py -> build\lib.win-amd64-3.10\preshed\tests
    copying preshed\tests\test_pop.py -> build\lib.win-amd64-3.10\preshed\tests
    copying preshed\tests\__init__.py -> build\lib.win-amd64-3.10\preshed\tests
    copying preshed\counter.pyx -> build\lib.win-amd64-3.10\preshed
    copying preshed\maps.pyx -> build\lib.win-amd64-3.10\preshed
    copying preshed\counter.pxd -> build\lib.win-amd64-3.10\preshed
    copying preshed\maps.pxd -> build\lib.win-amd64-3.10\preshed
    copying preshed\__init__.pxd -> build\lib.win-amd64-3.10\preshed
    running build_ext
    building 'preshed.maps' extension
    error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
    [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
    ERROR: Failed building wheel for preshed
    Running setup.py clean for preshed
    Building wheel for thinc (setup.py): started
    Building wheel for thinc (setup.py): finished with status 'error'
    error: subprocess-exited-with-error

    python setup.py bdist_wheel did not run successfully.
    exit code: 1

    [166 lines of output]
    running bdist_wheel
    running build
    running build_py
    creating build
    creating build\lib.win-amd64-3.10
    creating build\lib.win-amd64-3.10\thinc
    copying thinc\about.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\api.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\check.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\compat.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\describe.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\exceptions.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\i2v.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\loss.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\misc.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\rates.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\t2t.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\t2v.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\v2v.py -> build\lib.win-amd64-3.10\thinc
    copying thinc\__init__.py -> build\lib.win-amd64-3.10\thinc
    creating build\lib.win-amd64-3.10\thinc\tests
    copying thinc\tests\conftest.py -> build\lib.win-amd64-3.10\thinc\tests
    copying thinc\tests\strategies.py -> build\lib.win-amd64-3.10\thinc\tests
    copying thinc\tests\test_api_funcs.py -> build\lib.win-amd64-3.10\thinc\tests
    copying thinc\tests\test_util.py -> build\lib.win-amd64-3.10\thinc\tests
    copying thinc\tests\util.py -> build\lib.win-amd64-3.10\thinc\tests
    copying thinc\tests\__init__.py -> build\lib.win-amd64-3.10\thinc\tests
    creating build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_about.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_affine.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_beam_search.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_check_exceptions.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_difference.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_feature_extracter.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_hash_embed.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_imports.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_linear.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_loss.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_mem.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_model.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_ops.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_pickle.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_pooling.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_pytorch_wrapper.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_rates.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\test_rnn.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    copying thinc\tests\unit\__init__.py -> build\lib.win-amd64-3.10\thinc\tests\unit
    creating build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\test_affine_learns.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\test_basic_tagger.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\test_batch_norm.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\test_feed_forward.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\test_mnist.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\test_pickle.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\test_roundtrip_bytes.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\test_shape_check.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    copying thinc\tests\integration\__init__.py -> build\lib.win-amd64-3.10\thinc\tests\integration
    creating build\lib.win-amd64-3.10\thinc\tests\linear
    copying thinc\tests\linear\test_avgtron.py -> build\lib.win-amd64-3.10\thinc\tests\linear
    copying thinc\tests\linear\test_linear.py -> build\lib.win-amd64-3.10\thinc\tests\linear
    copying thinc\tests\linear\test_sparse_array.py -> build\lib.win-amd64-3.10\thinc\tests\linear
    copying thinc\tests\linear\__init__.py -> build\lib.win-amd64-3.10\thinc\tests\linear
    creating build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\__init__.py -> build\lib.win-amd64-3.10\thinc\linear
    creating build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\mem.py -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\pooling.py -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\train.py -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\util.py -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\vec2vec.py -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\vecs2vec.py -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\vecs2vecs.py -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\_lsuv.py -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\__init__.py -> build\lib.win-amd64-3.10\thinc\neural
    creating build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\datasets.py -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\hpbff.py -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\load_nlp.py -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\visualizer.py -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\wrappers.py -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\__init__.py -> build\lib.win-amd64-3.10\thinc\extra
    creating build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\affine.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\attention.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\batchnorm.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\convolution.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\difference.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\elu.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\embed.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\encoder_decoder.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\feature_extracter.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\feed_forward.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\function_layer.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\hash_embed.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\layernorm.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\maxout.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\model.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\multiheaded_attention.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\relu.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\resnet.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\rnn.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\selu.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\softmax.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\static_vectors.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    copying thinc\neural\_classes\__init__.py -> build\lib.win-amd64-3.10\thinc\neural\_classes
    creating build\lib.win-amd64-3.10\thinc\extra\_vendorized
    copying thinc\extra\_vendorized\keras_datasets.py -> build\lib.win-amd64-3.10\thinc\extra\_vendorized
    copying thinc\extra\_vendorized\keras_data_utils.py -> build\lib.win-amd64-3.10\thinc\extra\_vendorized
    copying thinc\extra\_vendorized\keras_generic_utils.py -> build\lib.win-amd64-3.10\thinc\extra\_vendorized
    copying thinc\extra\_vendorized\__init__.py -> build\lib.win-amd64-3.10\thinc\extra\_vendorized
    creating build\lib.win-amd64-3.10\thinc\extra\wrapt
    copying thinc\extra\wrapt\decorators.py -> build\lib.win-amd64-3.10\thinc\extra\wrapt
    copying thinc\extra\wrapt\importer.py -> build\lib.win-amd64-3.10\thinc\extra\wrapt
    copying thinc\extra\wrapt\wrappers.py -> build\lib.win-amd64-3.10\thinc\extra\wrapt
    copying thinc\extra\wrapt\__init__.py -> build\lib.win-amd64-3.10\thinc\extra\wrapt
    copying thinc\linalg.pyx -> build\lib.win-amd64-3.10\thinc
    copying thinc\structs.pyx -> build\lib.win-amd64-3.10\thinc
    copying thinc\typedefs.pyx -> build\lib.win-amd64-3.10\thinc
    copying thinc\cpu.pxd -> build\lib.win-amd64-3.10\thinc
    copying thinc\linalg.pxd -> build\lib.win-amd64-3.10\thinc
    copying thinc\structs.pxd -> build\lib.win-amd64-3.10\thinc
    copying thinc\typedefs.pxd -> build\lib.win-amd64-3.10\thinc
    copying thinc\__init__.pxd -> build\lib.win-amd64-3.10\thinc
    copying thinc\compile_time_constants.pxi -> build\lib.win-amd64-3.10\thinc
    copying thinc\linalg.cpp -> build\lib.win-amd64-3.10\thinc
    copying thinc\structs.cpp -> build\lib.win-amd64-3.10\thinc
    copying thinc\typedefs.cpp -> build\lib.win-amd64-3.10\thinc
    copying thinc\linear\avgtron.pyx -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\features.pyx -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\linear.pyx -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\serialize.pyx -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\sparse.pyx -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\avgtron.pxd -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\features.pxd -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\serialize.pxd -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\sparse.pxd -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\__init__.pxd -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\avgtron.cpp -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\features.cpp -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\linear.cpp -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\serialize.cpp -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\linear\sparse.cpp -> build\lib.win-amd64-3.10\thinc\linear
    copying thinc\neural\ops.pyx -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\optimizers.pyx -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\_aligned_alloc.pyx -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\cpu.pxd -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\ops.pxd -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\__init__.pxd -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\ops.cpp -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\optimizers.cpp -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\neural\_aligned_alloc.cpp -> build\lib.win-amd64-3.10\thinc\neural
    copying thinc\extra\cache.pyx -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\eg.pyx -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\mb.pyx -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\search.pyx -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\cache.pxd -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\eg.pxd -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\mb.pxd -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\search.pxd -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\__init__.pxd -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\cache.cpp -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\eg.cpp -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\mb.cpp -> build\lib.win-amd64-3.10\thinc\extra
    copying thinc\extra\search.cpp -> build\lib.win-amd64-3.10\thinc\extra
    running build_ext
    error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
    [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
    ERROR: Failed building wheel for thinc
    Running setup.py clean for thinc
    Building wheel for blis (setup.py): started
    Building wheel for blis (setup.py): finished with status 'error'
    error: subprocess-exited-with-error

    python setup.py bdist_wheel did not run successfully.
    exit code: 1

    [21 lines of output]
    BLIS_COMPILER? None
    running bdist_wheel
    running build
    running build_py
    creating build
    creating build\lib.win-amd64-3.10
    creating build\lib.win-amd64-3.10\blis
    copying blis\about.py -> build\lib.win-amd64-3.10\blis
    copying blis\benchmark.py -> build\lib.win-amd64-3.10\blis
    copying blis\__init__.py -> build\lib.win-amd64-3.10\blis
    creating build\lib.win-amd64-3.10\blis\tests
    copying blis\tests\common.py -> build\lib.win-amd64-3.10\blis\tests
    copying blis\tests\test_dotv.py -> build\lib.win-amd64-3.10\blis\tests
    copying blis\tests\test_gemm.py -> build\lib.win-amd64-3.10\blis\tests
    copying blis\tests\__init__.py -> build\lib.win-amd64-3.10\blis\tests
    copying blis\cy.pyx -> build\lib.win-amd64-3.10\blis
    copying blis\py.pyx -> build\lib.win-amd64-3.10\blis
    copying blis\cy.pxd -> build\lib.win-amd64-3.10\blis
    copying blis\__init__.pxd -> build\lib.win-amd64-3.10\blis
    running build_ext
    error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
    [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
    ERROR: Failed building wheel for blis
    Running setup.py clean for blis
    Building wheel for srsly (pyproject.toml): started
    Building wheel for srsly (pyproject.toml): finished with status 'error'
    error: subprocess-exited-with-error

    Building wheel for srsly (pyproject.toml) did not run successfully.
    exit code: 1

    [71 lines of output]
    running bdist_wheel
    running build
    running build_py
    creating build
    creating build\lib.win-amd64-cpython-310
    creating build\lib.win-amd64-cpython-310\srsly
    copying srsly\about.py -> build\lib.win-amd64-cpython-310\srsly
    copying srsly\util.py -> build\lib.win-amd64-cpython-310\srsly
    copying srsly\_json_api.py -> build\lib.win-amd64-cpython-310\srsly
    copying srsly\_msgpack_api.py -> build\lib.win-amd64-cpython-310\srsly
    copying srsly\_pickle_api.py -> build\lib.win-amd64-cpython-310\srsly
    copying srsly\__init__.py -> build\lib.win-amd64-cpython-310\srsly
    creating build\lib.win-amd64-cpython-310\srsly\cloudpickle
    copying srsly\cloudpickle\cloudpickle.py -> build\lib.win-amd64-cpython-310\srsly\cloudpickle
    copying srsly\cloudpickle\__init__.py -> build\lib.win-amd64-cpython-310\srsly\cloudpickle
    creating build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\exceptions.py -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\util.py -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\_ext_type.py -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\_msgpack_numpy.py -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\_version.py -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\__init__.py -> build\lib.win-amd64-cpython-310\srsly\msgpack
    creating build\lib.win-amd64-cpython-310\srsly\tests
    copying srsly\tests\test_json_api.py -> build\lib.win-amd64-cpython-310\srsly\tests
    copying srsly\tests\test_msgpack_api.py -> build\lib.win-amd64-cpython-310\srsly\tests
    copying srsly\tests\test_pickle_api.py -> build\lib.win-amd64-cpython-310\srsly\tests
    copying srsly\tests\__init__.py -> build\lib.win-amd64-cpython-310\srsly\tests
    creating build\lib.win-amd64-cpython-310\srsly\ujson
    copying srsly\ujson\__init__.py -> build\lib.win-amd64-cpython-310\srsly\ujson
    creating build\lib.win-amd64-cpython-310\srsly\tests\cloudpickle
    copying srsly\tests\cloudpickle\cloudpickle_file_test.py -> build\lib.win-amd64-cpython-310\srsly\tests\cloudpickle
    copying srsly\tests\cloudpickle\testutils.py -> build\lib.win-amd64-cpython-310\srsly\tests\cloudpickle
    copying srsly\tests\cloudpickle\__init__.py -> build\lib.win-amd64-cpython-310\srsly\tests\cloudpickle
    creating build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_buffer.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_case.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_except.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_extension.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_format.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_limits.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_memoryview.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_newspec.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_numpy.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_pack.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_read_size.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_seq.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_sequnpack.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_stricttype.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_subtype.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\test_unpack.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    copying srsly\tests\msgpack\__init__.py -> build\lib.win-amd64-cpython-310\srsly\tests\msgpack
    creating build\lib.win-amd64-cpython-310\srsly\tests\ujson
    copying srsly\tests\ujson\test_ujson.py -> build\lib.win-amd64-cpython-310\srsly\tests\ujson
    copying srsly\tests\ujson\__init__.py -> build\lib.win-amd64-cpython-310\srsly\tests\ujson
    copying srsly\msgpack\_packer.pyx -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\_unpacker.pyx -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\buff_converter.h -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\pack.h -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\pack_template.h -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\sysdep.h -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\unpack.h -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\unpack_define.h -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\msgpack\unpack_template.h -> build\lib.win-amd64-cpython-310\srsly\msgpack
    copying srsly\ujson\JSONtoObj.c -> build\lib.win-amd64-cpython-310\srsly\ujson
    copying srsly\ujson\objToJSON.c -> build\lib.win-amd64-cpython-310\srsly\ujson
    copying srsly\ujson\ujson.c -> build\lib.win-amd64-cpython-310\srsly\ujson
    copying srsly\ujson\py_defines.h -> build\lib.win-amd64-cpython-310\srsly\ujson
    copying srsly\ujson\version.h -> build\lib.win-amd64-cpython-310\srsly\ujson
    running build_ext
    building 'srsly.msgpack._unpacker' extension
    error: Microsoft Visual C++ 14.0 or greater is required. Get it with "Microsoft C++ Build Tools": https://visualstudio.microsoft.com/visual-cpp-build-tools/
    [end of output]

    note: This error originates from a subprocess, and is likely not a problem with pip.
    ERROR: Failed building wheel for srsly
  Failed to build preshed thinc blis srsly
  ERROR: Could not build wheels for srsly, which is required to install pyproject.toml-based projects
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error
× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.

Try this:
https://github.com/gunthercox/ChatterBot/issues/2262#issuecomment-1210893149


Completion list is not filtered correctly when typing a number after a hyphen

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.81.0-insider
OS Version: macOS 12.5.1

Steps to Reproduce:

Create a new untitled text file
Set the language mode to JavaScript
Paste the following code:let example = {
  'test-1': true,
  'test-2': true,
}

On the next line type example['test-1
Once you've typed the quote character you should see completions for the test-1 and test-2 properties, but after typing 1 the list is not filtered correctly:

Interestingly, @cagan123-alt is seeing this issue on v1.80.0, but I can only reproduce it in the Insiders release (v1.81.0-insider)

@jrieken Any suggestions on what I should set on my completions to get filtering working correctly:

@jrieken Any suggestions on what I should set on my completions to get filtering working correctly:

That's a real good question. It might be some word definition problem

Wait, it seems that the prefix isn't updated once the 1 has been typed

This is what happens: when typing 1 we believe a new word has started. That's because of the language specific word definition and that's totally OK. We now run the normal filter logic and would proceed by retriggering suggestions but because numbers aren't consider valid trigger words we do nothing and the UI doesn't refresh

Bug is acknowledged but a good fix needs some thinking

@jrieken Do you think the issue below is also the same bug? Completion item is not filtered corerctly as well when some string starts with a hyphen.
https://github.com/microsoft/vscode-discussions/discussions/1006


"main.py" execute error

Hello.
I got some problem when execute your codes.
me~~~$ python3 main.py ./20170512-110547/ ./pics/
Couldn't import dot_parser, loading of dot files will not be possible.
2018-01-23 16:37:29.142315: I tensorflow/core/platform/cpu_feature_guard.cc:137] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
2018-01-23 16:37:29.541278: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1030] Found device 0 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:02:00.0
totalMemory: 10.91GiB freeMemory: 10.45GiB
2018-01-23 16:37:29.880962: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1030] Found device 1 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.62
pciBusID: 0000:03:00.0
totalMemory: 10.91GiB freeMemory: 10.32GiB
2018-01-23 16:37:30.222775: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1030] Found device 2 with properties:
name: GeForce GTX 1080 Ti major: 6 minor: 1 memoryClockRate(GHz): 1.721
pciBusID: 0000:81:00.0
totalMemory: 10.91GiB freeMemory: 10.32GiB
2018-01-23 16:37:30.222992: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1045] Device peer to peer matrix
2018-01-23 16:37:30.223055: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1051] DMA: 0 1 2
2018-01-23 16:37:30.223067: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1061] 0:   Y Y N
2018-01-23 16:37:30.223075: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1061] 1:   Y Y N
2018-01-23 16:37:30.223083: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1061] 2:   N N Y
2018-01-23 16:37:30.223103: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1120] Creating TensorFlow device (/device:GPU:0) -> (device: 0, name: GeForce GTX 1080 Ti, pci bus id: 0000:02:00.0, compute capability: 6.1)
2018-01-23 16:37:30.223113: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1120] Creating TensorFlow device (/device:GPU:1) -> (device: 1, name: GeForce GTX 1080 Ti, pci bus id: 0000:03:00.0, compute capability: 6.1)
2018-01-23 16:37:30.223122: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1120] Creating TensorFlow device (/device:GPU:2) -> (device: 2, name: GeForce GTX 1080 Ti, pci bus id: 0000:81:00.0, compute capability: 6.1)
Model directory: ./20170512-110547/
Metagraph file: model-20170512-110547.meta
Checkpoint file: model-20170512-110547.ckpt-250000
WARNING:tensorflow:The saved meta_graph is possibly from an older release:
'model_variables' collection should be of type 'byte_list', but instead is of type 'node_list'.
/usr/local/lib/python3.5/dist-packages/scipy/misc/pilutil.py:479: FutureWarning: Conversion of the second argument of issubdtype from `int` to `np.signedinteger` is deprecated. In future, it will be treated as `np.int64 == np.dtype(int).type`.
  if issubdtype(ts, int):
/usr/local/lib/python3.5/dist-packages/scipy/misc/pilutil.py:482: FutureWarning: Conversion of the second argument of issubdtype from `float` to `np.floating` is deprecated. In future, it will be treated as `np.float64 == np.dtype(float).type`.
  elif issubdtype(type(size), float):
Traceback (most recent call last):
  File "main.py", line 227, in <module>
    main(parse_arguments(sys.argv[1:]))
  File "main.py", line 141, in main
    id_dataset = id_data.get_id_data(args.id_folder[0], pnet, rnet, onet, sess, embeddings, images_placeholder, phase_train_placeholder)
  File "/u/data/arith/face/FaceRecognition/id_data.py", line 31, in get_id_data
    id_dataset[i].embedding = emb[i, :]
IndexError: index 5 is out of bounds for axis 0 with size 5

I didn't solve this problem.
Could you help me?

I haven't worked on this for quite some time but I'll take a look on it as soon as I can. Seems to be a fairly simple problem

I haven't actually looked at it yet but these are two different problems.
@Sayak1711: are you using any grayscale images?
@Namori3: How did you structure your id-folder with all the images?

Traceback (most recent call last):
File "main.py", line 227, in
main(parse_arguments(sys.argv[1:]))
File "main.py", line 141, in main
id_dataset = id_data.get_id_data(args.id_folder[0], pnet, rnet, onet, sess, embeddings, images_placeholder, phase_train_placeholder)
File "F:\fr_tensor\FaceRecognition\id_data.py", line 31, in get_id_data
id_dataset[i].embedding = emb[i, :]
IndexError: index 41 is out of bounds for axis 0 with size 41

Yes @habrman  I was using grayscale images

@sayak1711 it should now be working with the original photo now as well

I'm closing this issue since I can't reproduce the problem that @namori3 had and the other problem is solved.


Rename branch master to main

GitHub has a renaming feature at https://github.com/OpenTechFund/hypha/settings/branches. It will update all PR:s and any branch protection rules.
All developers with local checkouts will however need to update their local copies.

@OpenTechFund/hypha-devs @OpenTechFund/hypha-maintainers  I plan to do this on Friday this week (2021-01-22).
Read more at https://github.com/github/renaming

@OpenTechFund/hypha-devs @OpenTechFund/hypha-maintainers  I plan to do this on Friday this week (2021-01-22).
Read more at https://github.com/github/renaming

This will be done for Hypha, OTF and Reset repos.

This will be done for Hypha, OTF and Reset repos.

This is now completed.

This is now completed.


Can not skip control object when get all names in dimension service

Describe the bug
skip_control_dims does not work, set it to True, but still seen the control objects in response.
To Reproduce
tm1.dimensions.get_all_names(skip_control_dims=True)
Expected behavior
No control object
Version
TM1py [the latest]
Additional context
no.

The feature has been added in May this year f417b4b9dbd7e29d20c09f1c1239af0a0e3ddbc0 by @adscheevel
It's not included in the PyPI release of TM1py.
You can upgrade to the current master branch for now. We will release a new version of TM1py to PyPI soon.


Split up dashboard page

The dashboard page is very long - https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/dashboard
I think it should be split up into its own section with multiple pages inside the Fundamentals section. Pages:

.NET Aspire dashboard

Dashboard overview
Using dashboard UI (this page will still be quite long, plus it will get longer in P6 with browser login instructions)
Standalone dashboard (right now it just links to a sample, should have more detail)
Configuration (content can come from https://github.com/dotnet/aspire/tree/main/src/Aspire.Dashboard#net-aspire-dashboard)
Security considerations

I like it. How would you differentiate between the overview and the using articles? Overview is a simple introduction with links to other content, and the using is essentially the existing content we have now - less an overview?

Overview would have the most important information:

What is the dashboard
How to get it/use it
Links to other articles

I'd like to aim for preview 6. That preview will have some significant auth changes and has links in UI and console messages to docs.

I think you'd probably want an auth section which shows how to set it up and host it securely. Particularly in the OIDC scenario.


feat(Toggle): add tolerance area for touchmove

Solves: https://github.com/nikgraf/belle/issues/66

Great job Nik


Trying to extract from old IBM PC/IX diskette image

Hello @ponchofiesta,
Your project looks just like what I needed - a utility to extract files from an AIX backup format disk image. Unfortunately, I know very little about the BFF file format, and don't have an AIX system with which to play with.
I'm trying to extract the files from (any of) the floppy disk images from an old IBM PC/IX v1.0 distribution. When I try it, I just get the following (on macOS):
$ ./bffextract -tv disk10.img
 Mode  UID  GID  Size  Modified  Filename

Any ideas on what might be the issue? I have attached the disk image in case that helps. I took a quick look at the disk image with a hex editor and it seems to have the right magic number (0xEA6B):

Thank you!
disk10.img.zip

Hi @ghaerr ,
I had a look into this file. It looks like this disk image is about 40 years old. I wasn't able to get useful files out of it. Maybe the BFF format from AIX 1.0 differs to much from current AIX versions. Even a recent AIX version wasn't able to extract the disk image. Sorry

Thanks @ponchofiesta for looking at this. I did manage to get another image of the system (PC/IX) booted which has a header file of the C structures used for the backup/restore format. It's not a big deal but I may try writing a little C extraction program, just for the fun of it. It would seem that IBM's PC/IX used the same magic number(s) but not the same actual structures as AIX.
Thank you!

Interesting. I was not able to find header files for the current backup format. Maybe you can adapt bffextract to get the archives extracted.


Offering dummy content (yaml files) as a way of starting a project

As a user I don't have always yaml files at hand to start a project, or I just want to play with Monokle right away very quickly. I would like to be able to start a project with some dummy content (yaml files) that the tool itself provides and have my project created and filled with resources & code instantly.

I want it to include some errors so I can play around with them
I want to have it as a starting option
I want to have it also as a new project option so I access it anytime.

Hi @julioramosest
Monokle Desktop gives you option to open any public git repo and play around. Also there is a demo repo available which you can get started with https://github.com/kubeshop/monokle-demo.
Feel free to check it out and share your feedback.
Thanks!


Failing to download packages

Getting to "Downloading packages to /mnt/lfs/sources...", sits there for a couple of minutes then returns me to the terminal prompt. No errors or warnings.
Checking system dependencies... done.
Creating image file... done.
Creating basic directory layout... done.
Downloading packages to /mnt/lfs/sources...

Ubuntu 21.10

Hmm weird. It might be that wget is quietly erroring out, since I have it using the --quiet option. Are there any files inside of the pkgs/ directory after you try running it? It caches the downloads there first before copying them onto the image file.

Just downloaded and ran your code it again, it downloads 91 files:  8x .patch,  1x .pcf.gz,  3x .tar.bz2,  36x .tar.gz,  43x .tar.xz
I removed the --quiet option and all the files requested downloaded OK.
Just before the command prompt return, I get the following standard wget exit message:
FINISHED --2022-04-06 08:10:54--
Total wall clock time: 3m 45s
Downloaded: 91 files, 449M in 2m 7s (3.54 MB/s)

Ok thanks for that. It appears zlib has recently been updated to version 1.2.12 (as Bango88 pointed out) due to a security vulnerability. I've updated the listing in pkgs.sh, so this should be all fixed now.

That worked, it's getter further now.  Thank you.
Might want to look at having a minimum version check and not exact.  You will be updating your version file constantly otherwise :)

cool.
Also I recently made the version check step much less aggressive and brittle. Now you have to specify --check and it will output the minimum and maximum version requirements based on the listing in https://www.linuxfromscratch.org/lfs/view/stable/chapter02/hostreqs.html, as well as output the current versions on your system. However, it no longer compares the versions for you. We all have to use our EYEBALLS now... which is lame but it was too hard to get it to work 100% of the time.


Dataloader not working with GraphQL subscriptions

When trying to query dataloaded relationships via a GraphQl subscription, you get the following:
 "message": "Cannot read property 'typeormGetConnection' of undefined",
I believe it is because the ApolloServerLoaderPlugin is not being passed to the WS server:
        async serverWillStart() {
          return {
            async drainServer() {
              subscriptionServer.close();
            },
          };
        },
      },
      ApolloServerLoaderPlugin({
        typeormGetConnection: getConnection,
      }),

anyone have an ideas on this?

Same issue here. The data loader doesn't get passed to a subscription. Any ideas on how to fix this?

So I figured that because the subscription server is no longer built-in in Apollo V3, it would be worh a try to manually add the missing _tgdContext to the subscription context. I took a look in ApolloServerLoaderPlugin.ts and just copy their code. Here is how to add _tgdContext to the subscription server, in order to load all relations.
const serverCleanup = useServer(
  {
    schema, // Your executable schema
    context: (ctx: any) => {
        Object.assign(ctx, {
          _tgdContext: {
            requestId: uuidv4(),
            typeormGetConnection: TypeORM.getConnection, // same getConnection method passed to the ApolloServerLoaderPlugin
          },
        });
       return ctx;
    },
  },
  wsServer // your wsServer created with WebSocketServer
);

Then do the same as the OP, and copy the following the ApolloServer plugins array:
{
  async serverWillStart() {
    return {
      async drainServer() {
        await serverCleanup.dispose();
      },
    };
  },
},

Hope this helps anyone.


Compilation failed

Hi Ramiro
I have managed somehow to install the extension (living in the same folder with a basic .qmd file - created from New file -> quarto file). After about 8 min. of installing and updating (LaTex?) packages I received a message:
updating tlmgr
updating existing packages
compilation failed- error
Undefined control sequence.
l.3 \setcitestyle
{}
What could be the source of this error?

It is difficult for me to understand what went wrong without an example. Can you provide your qmd for me to replicate the issue?

Thank you Ramiro .. here part of a screeshot to give you more context. First part, the entire .qmd file. Below, rendering results

Hi @schneiderpy :
I only see the snapshot. Could you send me the qmd? Thanks!

[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
Remitente
notificado con
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
14/10/23,
15:44:04
El sáb, 14 oct 2023 a las 15:37, Ramiro Magno @.***>)
escribió:

Hi @schneiderpy https://github.com/schneiderpy :
I only see the snapshot. Could you send me the qmd? Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/ramiromagno/wiley-njd/issues/7#issuecomment-1763120866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASTA3F5YDIR4XSA44WIQGK3X7LLVLANCNFSM6AAAAAA57PM7IA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@ramiromagno/wiley-njd
@.***>  could
you be so kind and check if the rendering produces a "nul" file?
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
Remitente
notificado con
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
14/10/23,
15:46:17
El sáb, 14 oct 2023 a las 15:45, Andreas Schneider (<
@.***>) escribió:

[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11& Remitente
notificado con
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11& 14/10/23,
15:44:04
El sáb, 14 oct 2023 a las 15:37, Ramiro Magno @.***>)
escribió:

Hi @schneiderpy https://github.com/schneiderpy :
I only see the snapshot. Could you send me the qmd? Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/ramiromagno/wiley-njd/issues/7#issuecomment-1763120866,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASTA3F5YDIR4XSA44WIQGK3X7LLVLANCNFSM6AAAAAA57PM7IA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @schneiderpy:
Your replies directly from email seem to be scrambled. Could you reply from within GitHub instead? And attach the qmd?

qmd is not supported

Okay, just zip it then.

or you should pass me your email .. to attach the .qmd file

lince.zip

Thank you


Repository cleanup

.DS_Store files are only configuration files for Mac OS and thus junk files for other operating systems and the .import/ directories can be recreated so long the original files and the .import files exist.

Thanks for the effort!

I am confused because the .DS_Store file at the top of the directory reappeared at my last push despite that it is still in the .gitignore.  Do you know why that would happen?

Actually, I have no idea why that happened   ¯\(ツ)/¯

I used **/.DS_Store instead and it seemed to do the trick!


Added more interfaces

added CLASS interface to CMB angular power spectrum
added COFFE interface to redshift-averaged multipoles
added the ability to install CLASS and COFFE as extra (optional) dependencies
minor changes to documentation

Codecov Report

Merging #47 (c07dd52) into master (1a5f8b8) will decrease coverage by 0.13%.
The diff coverage is 90.90%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master      #47      +/-   ##
==========================================
- Coverage   99.33%   99.20%   -0.13%
==========================================
  Files          12       12
  Lines        2394     2404      +10
==========================================
+ Hits         2378     2385       +7
- Misses         16       19       +3

Impacted Files
Coverage Δ

fitk/__init__.py
100.00% <ø> (ø)

fitk/derivatives.py
99.32% <90.90%> (-0.68%)
:arrow_down:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Closing in favor of #53 as that one is more atomic.


using any passed Redis instance

Describe the bug
One can pass a Redis instance when a new Store is created. And, although self.redis_store is initially set to that value, it is brutally overwritten by a new Redis instance created from the passed config.
This makes it harder to pass in a Mock Redis instance for creating unit tests. It is also unexpected behavior.
To Reproduce
import redis

from pydantic_redis import RedisConfig, Store

my_redis_client = redis.Redis(host='localhost', port=6379, db=0)

redis_config = RedisConfig(host='localhost', port=6379, db=1)

store = Store(
    name="my_redis_store",
    redis_config=redis_config,
    redis_store=my_redis_client,
)

assert store.redis_store == my_redis_client, "Unexpectedly the Redis store I passed is not used"

Expected behavior
I would expect the Redis store that I passed in, to be used rather than another one.

Oops 🙊. We probably should have made the redis_store property a read-only property.
The expectation was the RedisConfig was the only way to initialize the redis instance.

For passing a mock redis instance, @wasperen2 , in your use case, are you able to use the way it was done in the test/conftest.py file?
i.e.

Set aside an unused port
Create a fake redis instance using "redislite" running on that port
Initialize the Store or AsyncStore with its "RedisConfig.port" equal to the port from step one

As per my comments, can we please reconsider this and stick with the option to do Dependency Injection (https://en.wikipedia.org/wiki/Dependency_injection)? Having that ability makes your package play better with larger systems where injecting core services is common. This results in more cohesive code and a more standard way of deploying and testing.

(it would also not introduce a breaking change :))

@wasperen2 I think we should close the current issue first, which is the ambiguity problem. #35 closes this sufficiently because it is in line with the original idea of how the store were to be initialized (as can be seen in all current examples and tests).
We can then take your suggestion for ability to pass in a pre-constructed redis instance as new feature request.
If you haven't already, please create a new issue with this feature request so that we can weigh its return-on-investment.


[WelcomeUX] Scrollbar is not a good thing for playaround sometimes

Testing #18091
Take snippet as example

Before users type try, we can see five lines with an ending line end. After users insert the snippet

The ending line end is missing, which makes it somehow useless. Scrollbar is the catch.

Fixed with #18899


chore: bdd-sbhg-1587141874 to 0.0.1

chore: Promote bdd-sbhg-1587141874 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


[HIGH] [API Reliability] The app assumes its offline when its on spotty connection

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation: https://expensify.slack.com/archives/C05LX9D6E07/p1717393020259779
Action Performed:
Break down in numbered steps
'm on a pretty good wifi network in that I can access the web normally for almost everything else.  But I can't get online with NewDot -- and it doesn't really seem to be trying.  I'm in a hotel so I feel like maybe it took a second to get through the wifi authentication, and perhaps it tried once and failed, and now it's not trying again?  I would think that it should try every minute or so even when it thinks it can't connect.  I'm going to try to refresh to see if that fixes it...  Yep, refresh fixed it.  So I think retrying every minute or so would also "fix" this

Expected Result:
Describe what you think should've happened
Actual Result:
Describe what actually happened
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence

View all open jobs on GitHub
Issue OwnerCurrent Issue Owner: @parasharrajat

I'm afraid we can't find the root cause here (easily) - I wasn't able to reproduce this in any way, the net-info module works as expected and picks up any changes well for me.
What do we mean by retrying every minute or so would also "fix" this? Do I get this right that we can call NetInfo's refresh method inside of this if statement? This should notify all the subscribers and eventually switch back to the 'online' state that will get reflected on the UI. I can't imagine how we will test this though in a real life apart from seeing that it will we-check the connection state.
const intervalID = setInterval(() => {
        // Offline status also implies backend unreachability
        if (isOffline) {
+            NetInfo.refresh();
            return;
        }

Overall, I see the lack of components <-> remote data bounding being problematic here as we have to manually tell when to re-fire requests - this works as expected for failing ones.
@mountiny I will open up a PR with this update tomorrow morning, I think we can test a build against this behaviour, see if it retries picking up the connection correctly.

Looks good to me. @JmillsExpensify can we get this added to testRail? thanks.

I think $500 for the HIGH newdot-quality task is reasonable, we need to encourage people to work on these

Thanks, that makes sense. @JmillsExpensify can we please issue the payment here?

Not overdue, waiting for payment to complete. CC @JmillsExpensify

$500 approved for @parasharrajat

Contract paid out and regression test created, so I'm closing out this issue.


Help needed with OpenWRT port

Here, eventually.
https://github.com/openwrt/packages/pull/15685

addressed there...

Just a pointer...


Deprecate AWS integration packages in favor of Spring Cloud AWS ports

We're waiting for the Spring Cloud AWS 3.2 release to officially deprecate our event externalization implementations for SQS and SNS. /cc @maciejwalkowiak
Required steps

Log a deprecation warning on startup if a deprecated module is used
Update reference documentation to list the modules as deprecated and point to the Spring Cloud AWS equivalents

Hey @odrotbohm 👋
I would like to contribute to this issue.
As far as I understand, the goal is to:

log a warning once sns/sqs is used - ex. in a beans initialization in both starters?
update of reference documentation - adding new section in appendix with Deprecated modules section?

Sorry for the late reply. Feel free to go ahead and prepare the PR. Just be aware that we can only merge it, once Spring Cloud AWS has shipped a release version containing the replacements.

@mslowiak – I've assigned you the ticket and removed the label. Please let me know if your plans change, and you do not want to go forward with this.

@odrotbohm
Happy to work on that, but I am in vacay mode till 13/09 👍

Apologies for a delay - I've been having tough time past months and couldn't focus on finishing the release.
Spring Cloud AWS 3.2.0 with Modulith integration has been released yesterday: https://github.com/awspring/spring-cloud-aws/releases/tag/v3.2.0

Uhh, that's perfect timing, Maciej! Thanks for the heads-up. Just enough time for us to get the deprecation in for the release candidate, end of October.
@mslowiak – Do you think that schedule works out for you?

That's merged. Thanks again, both Maciej and Marcin! 🫶


Clicking 'X' To Close Multiple Tabs Sequentially Seems Broken

Using the mouse to close tabs doesn't work in all cases.

Small work-around: use the middle-click to close buttons which doesn't require precisely hitting the X.  Middle clicking anywhere closes a tab.
The X not working consistently is due to the tab width being calculated based on filename and therefore not always aligning from tab-to-tab.

The issue isn't "tabs arent the same width", the X button literally just doesnt work if you dont move your mouse after clicking one.
Repro:

cmd+N like 4 times from the new tab pane
prepare your mouse /trackpad position so you can click without moving it a single pixel
click and don't move the mouse, try to click the x again, the button will respond but the tab wont close

Fixed in 3.1.3703-dev.


[19.03] php: 7.1.27 -> 7.1.29, 7.2.16 -> 7.2.18, 7.3.3 -> 7.3.5

Motivation for this change
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

I was trying to find the exact range of rebuilds which would qualify something for staging instead of master but didn't notice it in the nixpkgs manual... @etu do you know what the ranges are, or where I can find?

I think up to 500 is in general ok, but I'm not sure there's written guidelines more than "huge rebuilds".
But if we consider the nature of the rebuilds that PHP upgrades cause it should in general not be that large because of the nature of the language. Many rebuilds will be "3 builds of compser, 3 builds of phpcbf, 3 builds of phpcs, etc". Which are really small.

Thanks for the info @etu!


chore: log v2 upgrade

Closes https://github.com/celestiaorg/celestia-app/issues/3627
Testing
Confirmed the log shows up during an upgrade
4:29PM INF upgrading from app version 1 to 2
4:29PM INF executed block height=2 module=state num_invalid_txs=0 num_valid_txs=0
4:29PM INF adding a new module: interchainaccounts
4:29PM INF created new capability module=ibc name=ports/icahost
4:29PM INF port binded module=x/ibc/port port=icahost
4:29PM INF claimed capability capability=2 module=icahost name=ports/icahost
4:29PM INF adding a new module: minfee
4:29PM INF adding a new module: packetfowardmiddleware
4:29PM INF adding a new module: signal

Do we want a log at the end when the upgrade has been completed or people just wait for the next block to be produced

Hmm good point. We can add a log in BeginBlock so that it shows up when the next block is produced.


Don't publish unnecessary BUILD files in the node package

I use version 1.4.1 of grpc.
I have a repository and build with bazel.
Also I have a dependency to grpc and install grpc with npm.
When I want to build my repository, bazel fails over BUILD files in node_modules/grpc
I expected no BUILD files in the published grpc node package.

@murgatroid99  : did this get fixed after all?

I think it was fixed when the referenced PR was merged, but it looks like it was unfixed by some changes to this repo.


Von-Neumann entropy

*I wrote the Von-Neumann entropy function following what was done on qutip
Closes DYN-129.

Thanks for your PR @baptistehoyau! We're in the process of migrating the repository to JAX, we'll come back to your work when we're done (early January). Have a great end of the year 😊

Replaced by #534.


Remove unused userbar views

The userbar was built within the iframe, with Django views that render the iframe's content.

It first appeared in edd757c5787fd971f620902f6421cc1b51a2b76b.
Then further refactored in 637899f6c2b82a27bc774121be2dac5c97f6f94c and 5e17881f2d85e8f153c88fdf3bb35e4eecdfcc07. Take note of the latter in particular, where the view was split into for_frontend and for_moderation views.
There was a discussion in #2164 which suggested refactoring of the userbar to not use an iframe.
#2201 did away with the refactoring, removed the iframe and the wagtailadmin/userbar/frame.html template.
Unfortunately, the refactoring did not remove the Django views for the iframe's content, leaving the code unused for 7+ years.

I believe the views are not used anywhere by us and they're very unlikely to be used by developers. As far as developers are concerned, they've been using the {% wagtailuserbar %} tag which abstracts the implementation details, including whether it used the iframe or not.
I suggest we remove:

The whole file for the views https://github.com/wagtail/wagtail/blob/main/wagtail/admin/views/userbar.py
The URLs https://github.com/wagtail/wagtail/blob/a1bd357092bc7107c3d41477536f471a1f3f307d/wagtail/admin/urls/init.py#L135-L146
The tests https://github.com/wagtail/wagtail/blob/a1bd357092bc7107c3d41477536f471a1f3f307d/wagtail/admin/tests/test_userbar.py#L362-L483

Hi @laymonage .
I will be taking up this task. Hoping to present a positive report in a short while.

@wanjugucode there is already a PR for this: #10971.


Ingress cannot configure multiple paths of same backend

Bug description:
Affected area (please mark with X where applicable):

Install                        [ ]
Gateway API - GatewayClass     [ ]
Gateway API - Gateway          [ ]
Gateway API - HTTPRoute        [ ]
Gateway API - TLSRoute         [ ]
Gateway API - TCPRoute         [ ]
Gateway API - UDPRoute         [ ]
Gateway API - PolicyReference  [ ]
Ingress                        [x]
Egress                         [ ]
MultiCluster                   [ ]
PIPY Control Plane             [ ]
PIPY Script/Config             [ ]
CLI Tool                       [ ]
Metrics                        [ ]
Certificate Management         [ ]
Sidecar Injection              [ ]
Logging                        [ ]
Debugging                      [ ]
Tests                          [ ]
Demo                           [ ]
CI System                      [ ]

Expected behavior:
It can route requests to different paths of same backend svc configured in Ingress.
Steps to reproduce the bug (as precisely as possible):

Deploy httpbin deployment and service.

apiVersion: v1
kind: ServiceAccount
metadata:
  name: httpbin
---
apiVersion: v1
kind: Service
metadata:
  name: httpbin
  labels:
    app: httpbin
    service: httpbin
spec:
  ports:
  - name: http
    port: 14001
  selector:
    app: httpbin
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: httpbin
spec:
  replicas: 1
  selector:
    matchLabels:
      app: httpbin
  template:
    metadata:
      labels:
        app: httpbin
    spec:
      serviceAccountName: httpbin
      nodeSelector:
        kubernetes.io/arch: amd64
        kubernetes.io/os: linux
      containers:
      - image: kennethreitz/httpbin
        imagePullPolicy: IfNotPresent
        name: httpbin
        command: ["gunicorn", "-b", "<IP_ADDRESS>:14001", "httpbin:app", "-k", "gevent"]
        ports:
        - containerPort: 14001

Apply Ingress

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: httpbin
spec:
  ingressClassName: pipy
  rules:
  - host: httpbin.org
    http:
      paths:
        - path: /headers
          pathType: Prefix
          backend:
            service:
              name: httpbin
              port:
                number: 14001
        - path: /get
          pathType: Prefix
          backend:
            service:
              name: httpbin
              port:
                number: 14001

try to access /headers and /get, but can not reach /get
check route config but path /get not there

{
   "trustedCAs": [],
   "certificates": {},
   "routes": {
      "/mesh/*": {
         "service": "fsm/fsm-repo-service:repo",
         "rewrite": [
            "^/mesh/?",
            "/"
         ]
      },
      "httpbin.org/headers/*": {
         "service": "httpbin/httpbin:http"
      }
   },
   "services": {
      "fsm/fsm-repo-service:repo": {
         "balancer": "round-robin",
         "upstream": {
            "endpoints": [
               {
                  "ip": "<IP_ADDRESS>",
                  "port": 6060
               }
            ]
         }
      },
      "httpbin/httpbin:http": {
         "balancer": "round-robin",
         "upstream": {
            "endpoints": [
               {
                  "ip": "<IP_ADDRESS>",
                  "port": 14001
               }
            ]
         }
      }
   }
}

How was FSM installed?:
helm
Anything else we need to know?:
Bug report archive:

Environment:

FSM version (use fsm version): 0.2.0
Kubernetes version (use kubectl version): 1.23
Size of cluster (number of worker nodes in the cluster): one node
Others:

Thanks, it's confirmed to be an issue. Fixed now, please test against v0.2.1-alpha.1 and let us know if there's any problem.


mercurialFull: skip an unstable experimental test, add maintainer

Motivation for this change
This disables a broken/unstable/experimental test for the mercurialFull
package. It also adds myself as a maintainer for mercurial.
@ofborg build mercurial mercurialFull
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)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg build mercurial mercurialFull


The thickness of font is not consistent.

Prerequisites

[X] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Sometimes, when I type some variables or keywords (e.g. const, extern), I found that the thickness of font is not consistent.
Steps to Reproduce
I don't know how to reproduce this issue by specific steps. I just write the code and then it happens sometimes.  I have changed it to several different font type. But it didn't work.

Reproduces how often: 60%
Versions
OS : Windows 7 (64-bit)
Version : 1.15.0
UI Theme : One Dark
Syntax Theme : Monokai (by kevinsawicki)
The fonts I have already tried :

Droid Sans Mono
DejaVu Mono
Code New Roman
Source Code Pro
CamingoCode

Additional Information
No
I appreciate any help. Thanks.

Can you zoom in on the different parts of the code using Magnifier and share the screenshots here?  You can access Magnifier using the Windows+= shortcut.

#10185

Hi 50Wliu,
Thanks for your comment! I have tried to use the Windows Magnifier. But when I used the PrintScreen, the part where I zoomed in was not able to be captured. I don't know why, sorry. However, after the zoom in, I could still obviously see that the thickness of code were different .
Hi Chrisvio,
Thanks for the information, I will keep following these issues.

Hmm, that's odd, it worked for me:

Anyway, even if it isn't for you, does the inconsistent font look like the above picture, or with less variation in color, like the one below?

Hi 50Wliu,
I captured the screen successfully after the zoom in. You can check it on below image.
It looks like the second one which you post.

Ok, thanks for the response.  This is due to Chromium not applying subpixel antialiasing on the text and instead falling back to grayscale antialiasing.  There's not much we can do about this other than upgrade to newer Chromium/Electron versions and seeing if their antialiasing strategy has improved.
We're in the progress of updating to Electron 1.6 right now, which at least for me has provided significant improvements in the crispness of the text.


[New] Query feature table

Description
This PR implements Query feature table in Features category.
URL to README:
Linked Issue(s)

swift/issues/3577

Please resolve the merge conflicts.


Feat Request: Cats

banned

How will we keep the cats from eating the robins?

How will we keep the cats from eating the robins?


Determine debug mode based on per script/source instead of ScriptContext

Check if Utf8SourceInfo is in debug mode or not instead of ScriptContext
Utf8SourceInfo constructor now takes isLibraryCode flag instead of calling SetIsLibraryCode as it is always known where a source is library code or not while creating Utf8SourceInfo
Renamed all IsInDebugMode functions to IsInDebugMode so that it is explicit what are we checking and to identify all places this change applies
Remove isByteCodeDebugMode from FunctionBody

Hi @agarwal-sandeep, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Sandeep Agarwal). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@akroshg please take a look

Hi @agarwal-sandeep, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Sandeep Agarwal). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Awesome to see this issue is taken care of.
I am going to take a look at the code change.

Looks good to me.

@dotnet-bot test this please

@dotnet-bot test this please


Seeing Error putting key <nnnn> into map <XYZ>: Thread interrupted while waiting for write lock

This ought to be debug as it is expected behaviour as the task has been killed.
Also, some of the catch blocks for InterruptedExceptions are not resetting the interrupt flag.

Fixed in > 7.0-beta.210


Health propery for worker

I want to check the health of a worker (SCV, Probe or Drone) with the health property. But the return value is constant 45.0 (for an SCV), even if the SCV got damage.
The value is correct when I do the same with the marine.
Is there some kind of trick or is there a bug?

I assume you store your units to a variable - the units inside that variable will not be updated (position, health, energy, orders too I suppose).
Instead, you have to use self.units to update your tracked units.
If you only track one units, e.g. self.scout_scv then you need to do this each step:
self.scout_scv = self.units.find_by_tag(self.scout_scv.tag)
Note: self.scout_scv will be None if it died.
If you track multiple units, you can store them in a set (fastest), list or dict:
self.my_army_tags = self.units(MARINE).tags
Then each step you have to do:
my_army = self.units.tags_in(self.my_army_tags)
Dead units will not show up in my_army. So len(my_army) may be less than len(self.my_army_tags).


Deep cloning a document and it's embedded documents

I have recently encountered some strange behavior regarding cloning a document object that contains embedded documents. The use case here is to create a copy of the original document with new identity, but exactly same details.
It seems that $newDocument = clone $originalDocument does not clone the embedded documents. $documentManager->persist($newDocument); works find and also embedded documents are copied at that point. However, if an embedded document of $newDocument is modified before (or after persisting), the change is coupled also to the $originalDocument.
Consider the following test case (added to be a part of EmbeddedTest.php)
	public function testCloneParentAndModifyEmbeddedWithoutChangeInOriginal()
    {
        $address = new Address();
        $address->setAddress('20780 Kaarina');

        $user = new User();
        $user->setUsername('vmattila');
        $user->setAddress($address);

        $this->dm->persist($user);
        $this->dm->flush();
        $this->dm->clear();

        $user = $this->dm->createQueryBuilder('Documents\User')
            ->field('id')->equals($user->getId())
            ->getQuery()
            ->getSingleResult();
        $this->assertNotNull($user);

		// Cloning user
		$newUser = clone $user;
		$newUser->setId(null); // Nulling identity of the user
		$this->assertEquals('20780 Kaarina', $newUser->getAddress()->getAddress());

		// Changing address for the new user
		$newUser->getAddress()->setAddress('20100 Turku');
		$this->dm->persist($newUser);
        $this->dm->flush();

		$this->assertEquals('20100 Turku', $newUser->getAddress()->getAddress());
		$this->assertEquals('20780 Kaarina', $user->getAddress()->getAddress());
    }

The test fails, because $newUser->getAddress()->setAddress('20100 Turku'); will couple the change also to $user->getAddress()->setAddress('20100 Turku');.
This behaviour might be expected (is it?) - but a little bit confusing. It would be useful if Doctrine would provide helpers to make a "deep copy" of the document.

#1252 aims to make situation better but is not enough given there's no Doctrine in provided scenario between reusing same embedded document and changing it's value.

#1259 is closest we can get to it automatically, as soon as document is persisted the changes to reused embedded documents are no longer shared.


Normalising the results from the /aviser/stats/timeline-endpoint

When working with the timeline-endpoint it would be helpful to have a normalised results as well as the counts
Eg:
Q: krig
Granularity: month
startTime: 1864
endTime: 1864

Results in:
"timestamp","editions","articles","pages"
"1864",492,1035,828
"1864",507,1036,835
"1864",450,856,687
"1864",434,804,666
"1864",392,702,584
"1864",494,1028,805
"1864",467,963,753
"1864",467,945,751
"1864",361,614,523
"1864",359,610,526
"1864",349,588,497
"1864",354,560,501
"total",5126,9741,7956

Ideally the csv-structured would look like this:
"timestamp","editions","articles","pages", "editions_percentage", "articles_percentage","pages_percentage"

As mentioned in #16, normalisation can be tricky. Maybe best solved by having an explicit Normalising query parameter with the possibilities

*:* (Smurf compatible)
recordBase:doms_aviser (only articles)

A better explanation of the possibilities is needed.


Convert into Synchronous

Can I filter bitmap with synchronous mode?

The previous version doesn't support asynchronous mode so you can use version "0.1.0" instead of "0.7.0".


moved packer.h to texpacker.h so it doesn't interfere with cracklib

Hey, there's one additional reference to packer.h in the makefile. I'd also suggest, for the sake of consistency and a matter of personal preference, that we rename it to texpack.h instead and that we rename packer.cpp to texpack.cpp aswell - the sauce of the program named after the project. Sounds good?

Sure, I just wanted to quickly rename the it and I didnt think ot through too thoroughly


add Ministry of Education - Oman

@maz1987in This domain does not belong to a university, nor to a college. I have to close the request without merging. Please ensure that you are familiar with this repository rules located at the bottom of this page before submitting a new request.

@philipto The domain belonging to the Ministry of Education in Oman and all teachers in the country is having this domain.
So could you please consider this request again?

@philipto Thanks,
Do I have to submit anything more to approve this request?

@maz1987in We reconsidered the request and decided that the domain can be added to the repository as an exception.
Please spread the word about the free license availability among teachers. We expect many of them registering and teaching students using the tools that are convenient for them. Shall you have any questions, please feel free to email us at<EMAIL_ADDRESS>Pull request merged.
Thank you!


Specify what to show when < 2 reviews are available

[ ] Article teaser shows N reviews. This text doesn't make sense if there is 0 reviews or 1 review around.
[ ] Article teaser shows the most recent review. In case there are 0 reviews, the behavior is undefined.

0 reviews - listing when first version published

0 reviews - listing when updated/new version

1 review - when review is added:

2+ reviews - when review is added

reviewed and updated


enhanced image: does not work, and fails when vite server origin is configured

Describe the bug
when I configure vite locally as I did in the stackblitz reproduction, I get the following error:
11:09:18 PM [vite] Error when evaluating SSR module /src/routes/(public)/+page.svelte:
Error while preprocessing /workspaces/test/src/lib/client/components/Article.svelte - Failed parsing string to object: {sources:{avif:"http://crispy-enigma-9766jxxrgv9cp4g5.github.dev/@imagetools/2ac042bb202f73feca839531fb859688259f4f48 592w, http://crispy-enigma-9766jxxrgv9cp4g5.github.dev/@imagetools/14c4f9b364da02812278fe5d9f709af0f4e4b7be 1184w",webp:"http://crispy-enigma-9766jxxrgv9cp4g5.github.dev/@imagetools/e8a54b4d54c1776abfba0f5fa44502bd1eaee197 592w, http://crispy-enigma-9766jxxrgv9cp4g5.github.dev/@imagetools/9c5f751f9ee17884bbf4f0fc7a004b03c2340593 1184w",png:"http://crispy-enigma-9766jxxrgv9cp4g5.github.dev/@imagetools/55dded0d1210d835e7da60786c4791bbf00ea91f 592w, http://crispy-enigma-9766jxxrgv9cp4g5.github.dev/@imagetools/81e6df6384588527fdb816b61720532ce1b6e8cb 1184w"},img:{src:"http://crispy-enigma-9766jxxrgv9cp4g5.github.dev/@imagetools/81e6df6384588527fdb816b61720532ce1b6e8cb",w:1184,h:1008}}
    at parseObject (file:///workspaces/test/node_modules/.pnpm/@sveltejs+enhanced-img@0.4.1_rollup@4.24.0_svelte@5.2.7_vite@5.4.11_@types+node@22.9.1_/node_modules/@sveltejs/enhanced-img/src/preprocessor.js:236:9)

In the reproduction, enhanced:img elements do not get transformed at all. I followed the steps to set enhanced image up as described here: https://svelte.dev/docs/kit/images, but maybe I messed up. I now believe that maybe the latest version of enhanced:img is incompatible with the version of svelte the reproduction has (or my local environment?) I am not sure honestly.
Reproduction
https://stackblitz.com/edit/sveltejs-kit-template-default-zvdgag?file=src%2Froutes%2F%2Bpage.svelte
Logs
No response
System Info
System:
    OS: Linux 6.5 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
    CPU: (2) x64 Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz
    Memory: 4.02 GB / 7.74 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 22.11.0 - /usr/local/share/nvm/versions/node/v22.11.0/bin/node
    Yarn: 1.22.22 - /usr/bin/yarn
    npm: 10.9.0 - /usr/local/share/nvm/versions/node/v22.11.0/bin/npm
    pnpm: 9.14.2 - /usr/local/share/nvm/versions/node/v22.11.0/bin/pnpm
  npmPackages:
    @sveltejs/adapter-auto: ^3.3.1 => 3.3.1
    @sveltejs/adapter-vercel: ^5.4.7 => 5.4.7
    @sveltejs/enhanced-img: ^0.4.1 => 0.4.1
    @sveltejs/kit: ^2.8.1 => 2.8.1
    @sveltejs/vite-plugin-svelte: ^4.0.1 => 4.0.1
    svelte: ^5.2.0 => 5.2.7
    vite: ^5.4.11 => 5.4.11

Severity
blocking all usage of SvelteKit
Additional Information
No response

The issue seems to be with StackBlitz. The image doesn't render either in this StackBlitz reproduction (without the vite server origin option configured): https://stackblitz.com/~/github.com/eltigerchino/sveltejs-kit-template-default-bu3iay

I'm going to close this since there's nothing we can do about stackblitz
Also, make sure you're on the latest imagetools as this was fixed in https://github.com/JonasKruckenberg/imagetools/issues/568


null safety

https://github.com/theyakka/qr.flutter/issues/127

@vishnuagbly done

@vishnuagbly Hi I wonder what should I do now? Seems that the PR has not been merged yet

@lukef can you review and merge this pull request.

Shall I close #128 in favor of this PR?

@jonas-zebari As long as the null safety feature can be released soon ;)

closed by https://github.com/theyakka/qr.flutter/pull/130


Add a feature for use with nightly that allows marking BitFlag::empty as a const fn

Not sure if there's interest in having this, but I'd find it useful since it'd let me set empty() as an associated const on a trait.

I also came across a use for this with bits(). If there's interest in this problem I can add that to this PR.


[BROWSER] Yandex Browser

** Describe the browser and provide any links if available **
Browser name: Yandex Browser - freeware Russian Chromium-based browser made by Yandex
URL: https://browser.yandex.com

Profile support: yes
usual path: Yandex/YandexBrowser

Windows: AppData/Local/Yandex/YandexBrowser/User Data

Some aliases: yandex-browser-stable, yandex-browser-beta

** List the platforms supported by the browser to be added **
Platforms: Windows, Linux, Mac OS

@NoPlagiarism Is the browser supported on linux? If so, can you provide the path?


How to keep stream data static

I have 4 Streams, ex: S1, S2, S3, S4, and here data for streams S2, S3, S4 will be static(means data which will be given to these streams once in 6 months OR will be given only once for life long). In this situation, I want to execute a RULE (with JOIN) where S1's data will be coming everyday 'n' number of times and at the same time the S2, S3, S4 data needs to be used .
how could i approach to this ?

Hi @sujith1994 Table should work for your scenario.

Hi @ngjaying . i have achieved my functionality through external functions. Thanks for the help


Feature request: search kill ring

I would like to have functionality that allows browsing the kill-ring and selecting the candidate via searching all previous kills.  The functionality I would like is similar to counsel-yank-pop from the ivy framework.
The following snippet gets me almost all the way there:
(defun selectrum-yank-pop ()
  (interactive)
  (insert
   (selectrum-read "Search kill ring: "
                   (mapcar 'identity kill-ring))))

What's missing is:

[ ] having a threshold for long candidates so they don't take up too much space
[ ] Only having unique candidates in the list; the kill-ring has the fonitified strings in there, so I don't know how complicated it is to make the entries unique

Do you think that this function should be included in the repo or is this out of scope?

FYI: I created the my-yank-pop function for my own use: https://github.com/raxod502/selectrum/wiki/Useful-Commands.

I don't think there's a need to include such commands in Selectrum proper. The wiki is a fine place for them. Does the linked implementation solve your problem? I didn't see anything about truncating long candidates, but I think that could be done easily by taking substrings and then attaching the original strings as a text property which can be extracted after completion.

Sounds fair to me.  That approach sounds feasible, I'd also include truncating based on the lines (e. g. no longer than three lines), but that doesn't change the general approach.
Thanks for the clarification and the hint!

I'd also include truncating based on the lines (e. g. no longer than three lines)

This can be implemented based on my code. You see there's a cl-remove-duplicates form that builds the list of candidates. What you need to do is:

Move it to the let* form.

Build another list, whose elements are truncated candidates, and their selectrum-candidate-full text properties are full candidates. You can use whatever text property you want but this one fits the usage well, plus it makes pressing M-w on a candidate copies the full candidate.

completing-read the newly built list.

Get the full candidate from the text property, and insert it.

For calculating the lines of a candidate, you'll need to create a function that loops string-match on the candidate to count the newline chars in it.
If any of these seems hard for you, don't hesitate to tell me. I could write a full working code for you tomorrow.

@AmaiKinono Very cool. Does it scroll down from the first candidate (or at least much higher than the currently selected candidate) when pressing <down> to go to the next candidate for you, or is that an issue with my setup?

@noctuid This looks like a problem described in the docstring of selectrum--ensure-current-candidate-centered. Also see #12.

@AmaiKinono May I ask how can I remove this feature This doesn't delete the text just pasted if the previous command is 'yank'. from the wiki version?

@isolet It's actually not a feature, but a lack of feature ;) Based on the implementation of yank-pop, I think you need to:

See if the previous command is yank.
If it is, call yank-undo-function or delete-region between point and mark.

Just see how yank-pop does it, it's actually straightforward.


Add Kubernetes as a generic plugin at root level

🔖 Feature description
Not sure if this feature is already available, can we add kubernetes as a generic plugin at rool level(to the left menu bar) instead of tightly coupling it with component?
🎤 Context
In my use case i want to see cluster info for all apps not just for one component.
✌ Possible Implementation
No response
👀 Have you spent some time to check if this feature request has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
None

The plugin is designed that way at the moment; nobody has built a usable index page for it yet.
However, I'm not sure what that index page would show. Especially in a large org with tens of thousands of apps etc. It'll be both a technical and design related exercise to make a usable landing page for that.


Adding extra gem to also validate the metadata.json file.

Rake validate currently errors with a "Warning: License Indentifier Apache 2.0 is not in the SPDX list. message" .  Adding a dash to the license in metadata.json fixes this.
closes pull request #73

I was unable to reproduce this due to having an older version of the puppetlabs_spec_helper gem in my environment. After finding mention of it in the changelog, I updated the gem and got the error.
$ bundle exec rake validate
[DEPRECATION] `last_comment` is deprecated.  Please use `last_description` instead.
[DEPRECATION] `last_comment` is deprecated.  Please use `last_description` instead.
[DEPRECATION] `last_comment` is deprecated.  Please use `last_description` instead.
[DEPRECATION] `last_comment` is deprecated.  Please use `last_description` instead.
ruby -c lib/puppet/provider/grafana_dashboard/grafana.rb
Syntax OK
ruby -c lib/puppet/provider/grafana.rb
Syntax OK
ruby -c lib/puppet/provider/grafana_datasource/grafana.rb
Syntax OK
ruby -c lib/puppet/type/grafana_datasource.rb
Syntax OK
ruby -c lib/puppet/type/grafana_dashboard.rb
Syntax OK
---> syntax:manifests
---> syntax:templates
---> syntax:hiera:yaml
Warning: License identifier Apache 2.0 is not in the SPDX list: http://spdx.org/licenses/
Errors found in metadata.json

Everything is working now, thanks for the submission!


Retryable Writes are not supported

Step six of the documentation is missing additional parameters in the block of code. The most important of which is the retrywrites parameter. If this parameter is missing writing to the DB will fail with the rest of the code listed in the documentation.
The other two parameters are useNewUrlParser and useUnifiedTopology.
See the mongoose documentation here for what these properties do: https://mongoosejs.com/docs/deprecations.html
mongoose.connect("mongodb://"+process.env.COSMOSDB_HOST+":"+process.env.COSMOSDB_PORT+"/"+process.env.COSMOSDB_DBNAME+"?ssl=true&replicaSet=globaldb",` {
  auth: {
    user: process.env.COSMODDB_USER,
    password: process.env.COSMOSDB_PASSWORD
  }
  useNewUrlParser: true,
  useUnifiedTopology: true,
  retrywrites: false,
})
.then(() => console.log('Connection to CosmosDB successful'))
.catch((err) => console.error(err));

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

ID: 59571387-86d7-72d7-2c96-6a8e75ee8b1e
Version Independent ID: d24f0ef2-188f-5603-915e-0a69c2d9b17a
Content: Connect a Node.js Mongoose application to Azure Cosmos DB
Content Source: articles/cosmos-db/mongodb-mongoose.md
Service: cosmos-db
Sub-service: cosmosdb-mongo
GitHub Login: @timsander1
Microsoft Alias: tisande

@bradleyGamiMarques Thank you for the feedback. We are actively investigating and will get back to you soon.

@bradleyGamiMarques  Really appreciate you for pointing out the issue, we have updated the document content accordingly.
The changes should be live once the PR is approved.
We will proceed to close this issue now.
If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


Kim Leal

When creating a new PR, please do the following and delete this template text:

Reference the issue number if there is one:
Fixes #Issue_Number

The "Fixes #nnn" syntax in the PR description causes
GitHub to automatically close the issue when this PR is merged.

Suggest reviewers if you know who should review the PR, using the GitHub Reviewers UI.

@kimBrasileiro,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla2.dotnetfoundation.org.
It will cover your contributions to all .NET Foundation-managed open source projects.
Thanks,
.NET Foundation Pull Request Bot