Pytest discovery stuck in Output panel

Issue Type: Bug
Behaviour
Expected vs. Actual
Running pytest in the terminal works. Running the discovery command from VS Code directly works:
> ~/.cache/pypoetry/virtualenvs/lol-data-rest-api-m4zklELf-py3.10/bin/python ~/.vscode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . --cache-clear --runxfail -s rest_api/tests

[{"rootid": ".", "root": "/home/tolki/development/mobalab/mobalab_backend", "parents": [{"id": "./rest_api", "kind": "folder", "name": "rest_api", "parentid": ".", "relpath": "./rest_api"}, {"id": "./rest_api/tests", "kind": "folder", "name": "tests", "parentid": "./rest_api", "relpath": "./rest_api/tests"}, {"id": "./rest_api/tests/test_games.py", "kind": "file", "name": "test_games.py", "parentid": "./rest_api/tests", "relpath": "./rest_api/tests/test_games.py"}, {"id": "./rest_api/tests/test_games.py::test_add_note", "kind": "function", "name": "test_add_note", "parentid": "./rest_api/tests/test_games.py"}, {"id": "./rest_api/tests/test_games.py::test_delete_riot_game", "kind": "function", "name": "test_delete_riot_game", "parentid": "./rest_api/tests/test_games.py"}, {"id": "./rest_api/tests/test_games.py::test_get_game_champion", "kind": "function", "name": "test_get_game_champion", "parentid": "./rest_api/tests/test_games.py"}, {"id": "./rest_api/tests/test_games.py::test_insert_and_delete_game", "kind": "function", "name": "test_insert_and_delete_game", "parentid": "./rest_api/tests/test_games.py"}, {"id": "./rest_api/tests/test_games.py::test_update_game", "kind": "function", "name": "test_update_game", "parentid": "./rest_api/tests/test_games.py"}, {"id": "./rest_api/tests/test_get_game_details.py", "kind": "file", "name": "test_get_game_details.py", "parentid": "./rest_api/tests", "relpath": "./rest_api/tests/test_get_game_details.py"}, {"id": "./rest_api/tests/test_get_game_details.py::test_get_all_kills", "kind": "function", "name": "test_get_all_kills", "parentid": "./rest_api/tests/test_get_game_details.py"}, {"id": "./rest_api/tests/test_get_game_details.py::test_get_game_building_kills", "kind": "function", "name": "test_get_game_building_kills", "parentid": "./rest_api/tests/test_get_game_details.py"}, {"id": "./rest_api/tests/test_get_game_details.py::test_get_game_epic_monsters_kills", "kind": "function", "name": "test_get_game_epic_monsters_kills", "parentid": "./rest_api/tests/test_get_game_details.py"}, {"id": "./rest_api/tests/test_get_game_details.py::test_get_game_gold", "kind": "function", "name": "test_get_game_gold", "parentid": "./rest_api/tests/test_get_game_details.py"}, {"id": "./rest_api/tests/test_get_game_details.py::test_get_game_kills", "kind": "function", "name": "test_get_game_kills", "parentid": "./rest_api/tests/test_get_game_details.py"},
(...)

But in the OUTPUT/Python tab the process is stuck and never finds tests.
If I forcefully stop it, the logs are:
[ERROR 2022-2-8 18:31:46.477]: Cancelled discovering pytest tests:
 SyntaxError: Unexpected end of JSON input
    at JSON.parse (<anonymous>)
    at a.runTestDiscovery (/home/tolki/.vscode-server/extensions/ms-python.python-2022.2.1924087327/out/client/extension.js:85:82661)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Promise.all (index 0)
    at E.refreshTestData (/home/tolki/.vscode-server/extensions/ms-python.python-2022.2.1924087327/out/client/extension.js:85:94259)
    at v.refreshTestDataInternal (/home/tolki/.vscode-server/extensions/ms-python.python-2022.2.1924087327/out/client/extension.js:85:85653)
    at async Promise.all (index 0)
    at v.resolveChildren (/home/tolki/.vscode-server/extensions/ms-python.python-2022.2.1924087327/out/client/extension.js:85:86988) {
  stdout: ''
}

Interestingly, the log error looks to be 1 month in the past for some reason.
Steps to reproduce:

Launch VS Code
No Python tests :(

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10.1
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Poetry
Value of the python.languageServer setting: Default

User Settings

defaultLS: {"defaultLSType":"Pylance"}

downloadLanguageServer: true

envFile: "<placeholder>"

venvPath: "<placeholder>"

venvFolders: "<placeholder>"

condaPath: "<placeholder>"

pipenvPath: "<placeholder>"

poetryPath: "<placeholder>"

languageServer: "Pylance"

linting
• enabled: true
• cwd: "<placeholder>"
• Flake8Args: "<placeholder>"
• flake8Enabled: false
• flake8Path: "<placeholder>"
• lintOnSave: true
• banditArgs: "<placeholder>"
• banditEnabled: false
• banditPath: "<placeholder>"
• mypyArgs: "<placeholder>"
• mypyEnabled: false
• mypyPath: "<placeholder>"
• pycodestyleArgs: "<placeholder>"
• pycodestyleEnabled: false
• pycodestylePath: "<placeholder>"
• prospectorArgs: "<placeholder>"
• prospectorEnabled: false
• prospectorPath: "<placeholder>"
• pydocstyleArgs: "<placeholder>"
• pydocstyleEnabled: false
• pydocstylePath: "<placeholder>"
• pylamaArgs: "<placeholder>"
• pylamaEnabled: false
• pylamaPath: "<placeholder>"
• pylintArgs: "<placeholder>"
• pylintPath: "<placeholder>"

sortImports
• args: "<placeholder>"
• path: "<placeholder>"

formatting
• autopep8Args: "<placeholder>"
• autopep8Path: "<placeholder>"
• provider: "black"
• blackArgs: "<placeholder>"
• blackPath: "<placeholder>"
• yapfArgs: "<placeholder>"
• yapfPath: "<placeholder>"

testing
• cwd: "<placeholder>"
• debugPort: 3000
• nosetestArgs: "<placeholder>"
• nosetestsEnabled: undefined
• nosetestPath: "<placeholder>"
• promptToConfigure: true
• pytestArgs: "<placeholder>"
• pytestEnabled: true
• pytestPath: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: false
• autoTestDiscoverOnSaveEnabled: true

terminal
• activateEnvironment: true
• executeInFileDir: "<placeholder>"
• launchArgs: "<placeholder>"

experiments
• enabled: true
• optInto: []
• optOutFrom: []

insidersChannel: "off"

tensorBoard
• logDirectory: "<placeholder>"

Extension version: 2022.2.1924087327
VS Code version: Code 1.65.0 (b5205cc8eb4fbaa726835538cd82372cc0222d43, 2022-03-02T11:12:08.962Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

System Info

Item
Value

CPUs
AMD Ryzen 7 5800X 8-Core Processor              (16 x 3793)

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

Load (avg)
undefined

Memory (System)
31.90GB (12.93GB free)

Process Argv
--crash-reporter-id 0b342376-bcbb-4c08-9c59-05e04abdb7b7

Screen Reader
no

VM
0%

Item
Value

Remote
WSL: Ubuntu

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
AMD Ryzen 7 5800X 8-Core Processor (16 x 3792)

Memory (System)
15.58GB (8.76GB free)

VM
0%

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30448491
dsvsc009:30440023
pythonvspyt640:30442238
vsbas813:30436447
vscscmwlcmt:30438805
vscgsvidc:30447482
helix:30440343

Hi @mrtolkien, thank you for reaching out.
Do you have a sample repo I could use to try and replicate your issue?
Thanks!

This is happening in a private monorepo that has both Jest and Pytest suites configured. The python interpreter is build with poetry and properly gets activated when opening the terminal.
Jest and Pytest used to cohabitate peacefully, but now pytests discovery freezes forever with no feedback on logging.
I'm not entirely sure how to recreate a similar repo to try and reproduce the problem, especially since there's no feedback from the extension.

Still facing this issue, but it's intermittent. Sometimes I'll start VS Code and it'll properly pick up the tests, sometimes it won't.
But most of the time it just stays stuck, with the following feedback in OUTPUT/Python:
> ~/.cache/pypoetry/virtualenvs/lol-data-rest-api-m4zklELf-py3.10/bin/python ~/.vscode-server/extensions/ms-python.python-2022.2.1924087327/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear rest_api/tests
cwd: .

I'm also seeing nothing in the Extensions Log Folder, it's just frozen there forever and impossible to debug. I wish I could give more information honestly, but the exact incriminating command runs perfectly in the terminal already...

I have installed this extension and it finds and runs my tests properly:
https://marketplace.visualstudio.com/items?itemName=LittleFoxTeam.vscode-python-test-adapter
It relies on the same settings coming from python.testing so it's not a configuration issue.
The repo is very big as it's a monorep containing both Typescrip and Python projects, could that be an issue?

Hi @mrtolkien, sorry for the delay!

it's a monorep containing both Typescrip and Python projects, could that be an issue?
Maybe?

What is the output if you run pytest in the terminal (python -m pytest  --rootdir . -s --cache-clear rest_api/tests)?

pytest runs perfectly in the terminal. Running python -m pytest --rootdir . -s --cache-clear rest_api/tests works.
Even the test discovery command works with the python 2022.04  extension:
~/.cache/pypoetry/virtualenvs/lol-data-rest-api-m4zklELf-py3.9/bin/python ~/.vscode-server/extensions/ms-python.python-2022.4.0/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear .
That's what's weird, everything works from a terminal, but for some reason the extension is stuck forever. Is it trying to index files in huge folders, like node_modules? I have added it to my norecursedirs in pytest.ini but it did not have any impact.

Same problem here, the command seems to be stuck.
> ~/.cache/pypoetry/virtualenvs/coral-sistemas-o8TNEM9u-py3.8/bin/python ~/.vscode-server/extensions/ms-python.python-2022.4.0/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear
cwd: .

Executing the command via terminal is returns the path to the tests normally.

Hi @CleitonDeLima, same question as above, what is the output in the terminal? Do you have a sample repo I could use to try and replicate your issue?

Hi @CleitonDeLima, same question as above, what is the output in the terminal? Do you have a sample repo I could use to try and replicate your issue?

Hi @kimadeline
I have this problem in any project, this is the last one I tested.
Running run_adapter in the terminal I get the tests:
 > ~/.cache/pypoetry/virtualenvs/mywallet-RNjgMciX-py3.10/bin/python ~/.vscode-server/extensions/ms-python.python-2022.4.1/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear
[{"rootid": ".", "root": "/mnt/wsl/PHYSICALDRIVE3/Projects/mywallet", "parents": [{"id": "./tests", "kind": "folder", "name": "tests", "parentid": ".", "relpath": "./tests"}, {"id": "./tests/test_views.py", "kind": "file", "name": "test_views.py", "parentid": "./tests", "relpath": "./tests/test_views.py"}, {"id": "./tests/test_views.py::TestTransactions", "kind": "suite", "name": "TestTransactions", "parentid": "./tests/test_views.py"}], "tests": [{"id": "./tests/test_views.py::test_home", "name": "test_home", "source": "./tests/test_views.py:8", "markers": [], "parentid": "./tests/test_views.py"}, {"id": "./tests/test_views.py::TestTransactions::test_get_list", "name": "test_get_list", "source": "./tests/test_views.py:16", "markers": [], "parentid": "./tests/test_views.py::TestTransactions"}, {"id": "./tests/test_views.py::TestTransactions::test_get_create", "name": "test_get_create", "source": "./tests/test_views.py:23", "markers": [], "parentid": "./tests/test_views.py::TestTransactions"}, {"id": "./tests/test_views.py::TestTransactions::test_post_create", "name": "test_post_create", "source": "./tests/test_views.py:28", "markers": [], "parentid": "./tests/test_views.py::TestTransactions"}, {"id": "./tests/test_views.py::TestTransactions::test_update", "name": "test_update", "source": "./tests/test_views.py:42", "markers": [], "parentid": "./tests/test_views.py::TestTransactions"}]}]

vscode returns:
~/.cache/pypoetry/virtualenvs/mywallet-RNjgMciX-py3.10/bin/python ~/.vscode-server/extensions/ms-python.python-2022.4.1/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear
cwd: .

Config System

CPUs
AMD Ryzen 5 2600 Six-Core Processor (12 x 3394)

GPU Status
2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: enabled opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled

Load (avg)

Memory (System)
15.94GB (6.91GB free)

Process Argv
--folder-uri=vscode-remote://wsl+Arch/home/cleiton/Projects/mywallet --remote=wsl+Arch --crash-reporter-id 9aee08db-1535-4d00-a08e-0570dd89def2

Screen Reader
no

VM
0%

A/B experiment info
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
cppdebug:30466689
pynewfile477:30463512

My enabled extensions

Extension
Author (truncated)
Version

html-snippets
abu
0.2.1

Bookmarks
ale
13.2.4

django-html
bib
1.3.0

django
big
1.0.2

font-switcher
eva
4.0.3

auto-rename-tag
for
0.1.10

better-cpp-syntax
jef
1.15.13

vscode-peacock
joh
4.0.1

dotenv
mik
1.0.1

vscode-language-pack-pt-BR
MS-
1.66.2

jupyter-keymap
ms-
1.0.0

remote-containers
ms-
0.231.4

remote-ssh
ms-
0.78.0

remote-ssh-edit
ms-
0.80.0

remote-wsl
ms-
0.66.0

vscode-icons
vsc
11.10.0

codesnap
adp
1.3.4

better-toml
bun
0.3.2

EditorConfig
Edi
0.16.4

vscode-language-pack-pt-BR
MS-
1.66.2

python
ms-
2022.4.1

vscode-pylance
ms-
2022.4.0

jupyter
ms-
2022.3.1000901801

jupyter-keymap
ms-
1.0.0

jupyter-renderers
ms-
1.0.6

vscodeintellicode
Vis
1.2.18

(3 theme extensions excluded)

Notes

The path /mnt/wsl/PHYSICALDRIVE3/ is a virtual volume that I always mount when the system starts (I don't know if this interferes with anything)
I'm using wsl with arch linux (https://github.com/yuk7/ArchWSL)

I'm also getting this issue.
I'm running Ubuntu 20.04.4 LTS on WSL2
the in the VSCode the python log hangs during the test discovery as so,
> /bin/python3 ~/.vscode-server/extensions/ms-python.python-2022.4.1/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear tests
cwd: .

When running the same command in the terminal in VSCode I get the following output,
matthew@studio:~/Source/test_vscode$ /bin/python3 ~/.vscode-server/extensions/ms-python.python-2022.4.1/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear tests
[{"rootid": ".", "root": "/mnt/c/Users/matthew/Source/test_vscode", "parents": [{"id": "./tests", "kind": "folder", "name": "tests", "parentid": ".", "relpath": "./tests"}, {"id": "./tests/test_1.py", "kind": "file", "name": "test_1.py", "parentid": "./tests", "relpath": "./tests/test_1.py"}], "tests": [{"id": "./tests/test_1.py::test_fail", "name": "test_fail", "source": "./tests/test_1.py:4", "markers": [], "parentid": "./tests/test_1.py"}]}]
matthew@studio:~/Source/test_vscode$

This problem occurs in a minimal test environment,
matthew@studio:~/Source/test_vscode$ tree
.
└── tests
    ├── __init__.py
    └── test_1.py

Where test_1.py is,
import pytest

def test_fail():
    assert 0 == 1

I have also attached a tar of the test environment
test_vscode.tar.gz

I have the same problem on OS: Darwin arm64 21.1.0 with VS Code 1.66.2

I ran into this issue and another colleague did as well. In our case, we used to see abort trap: 6 when python test discovery was run due to missing openssl libraries in the path, which would show up as the unparsable json error that was reported at the top of the issue. After we put the libraries in the path (as below), things started working again for us.
ln -s<EMAIL_ADDRESS>/usr/local/lib/libssl.dylib```

We are working on a pytest adapter that does not interfere with pytests own detection. The current test adapter we have seems to be interacting with pytest in a way where it can cause errors when parsing JSON output. (Tracking item: https://github.com/microsoft/vscode-python/issues/19791 )
I will add this issue to that task for verification when it is done.

Hello! We have just finished our testing rewrite and are beginning the roll out to users. I have tested this issue with the re-write and I am not longer reproducing the bug! I used the minimal repro from @matthewghgriffiths.
If any of you would like to try it yourself, you need to be on vscode insiders and then add this setting to your users settings.json "python.experiments.optInto": ["pythonTestAdapter"]. We are in the processes of switching all users to the rewrite but are doing so incrementally so if you do not have insiders, watch our release notes to get updated on when it will begin to hit stable. Let me know if it doesn’t work for you and we can re-open this issue. Thanks!

@eleanorjboyd Great, thank you! With the new, experimental test adapter the test discovery worked quickly!
Note that I also had to set "python.experiments.enabled": true, in the settings, which I had previously set to false.

My bad: I could resolve my issues with test discovery and running tests, simply by selecting: "Python: Configure Tests" from the command palette. Here I could select where to search for tests. Now test discovery works quickly without the experimental adapter.

Great! Glad it got resolved!


Is there any already-trained model available? (3D retrieval)

Hi, thanks for your great work and patient guidance.
I want to know if there is a already-trained model for 3D retrieval available for a test demo? Because I have few computing source in school lab to train a model from zero.
No offence to your work~I will be appreciate if you provided one.

The retrieval model is here:
https://drive.google.com/drive/folders/1yj-ka2pU5vMEAe5sZEF0a5VyYK0cCpYo?usp=sharing
The output of the encoder is a feature vector for each input point cloud. This feature vector can be used for retrieval.

Thanks for your reply!
I can't find test.py code you mentioned in ReadMe, so we should code ourselves, right?

I have uploaded a test.py to SHREC16. This is a file to save the feature vector to disk. The evaluation code is by the SHREC16 official code. http://shapenet.cs.stanford.edu/shrec16/

Sorry to disturb you.
In your code test.py (in shrec16),  you have import SHREC2016Loader from data.shrec2016_loader to load testset, but there's no shrec2016_loader.py in data file. Is the test data loading process the same as the training data loading process (share data.modelnet_shrec_loader code)?
Thanks for your patient, I'm still trying to work it out ~

I think it's right to load test data via data.modelnet_shrec_loader.py because mode is set to be 'test'. So there's maybe some mistakes in test.py (in shrec16) you uploaded lately.
Please correct me if there is anything wrong.


This should round out the rest of the CLI

FYI I punted on the security section for the time being. I need to go work through the material a bit. Moreover, for lifecycle and security we could really use some sort of turn-key demo code that ships either with the desktop install. I might be able to get something together for this in late July or August.

I think you can just merge it into master, that's where everyone else's work is. I'm going to open my own PRs for each chapter for the edit


Use characters

Right now we just use UTF-16 indexing for strings.
We should use characters to index with grapheme clusters. This will guarantee a valid state where formatting is applied in units of grapheme clusters.
We can keep this representation when serializing because it's what makes the most sense for the data we're modelling. I initially planned to convert to UTF-8 because it's the standard encoding for web, but grapheme clusters fit the data better and there's great support for it in most programming languages nowadays.

Fixed in 98f6503.


invalid unordered_map<K, T> key

I have a warrning/error in samp-server.exe !

And if I type any command gives me the Unknown Command
I used a lastest version of Pawn.CMD
P.S: Sorry for my bad english !

Windows?

Yea. I have windows 10.

https://github.com/urShadow/Pawn.CMD/releases/tag/3.3.1


Network Domain is not re-associated when going from HPE -> Non-HPE or Non-HPE -> HPE

When moving from HPE -> Non-HPE or Non-HPE -> HPE, the Spoke is detached from Transit, gateways are destroyed, new gateways are created, and then Spoke is re-attached to Transit.
When re-attaching Spoke to Transit, the assignment of the Network Domain is not occurring.

Fixed in version 1.3.2


Update build steps for Build On Linux

Build on Linux (fake, gcc_release, clang, simulated) periodically
times out, like for
https://github.com/project-chip/connectedhomeip/runs/7996944701?check_suite_focus=true
Fixes #22134
Change overview
The "run tests" step already compiles and runs clang builds several times, so I removed the clang build & test step from
the main compile job. Moved the clang-tidy to run based on the output of one of the sanitizer builds.
Increased the timeout by 30 minute in case the job will take longer still in the future.
Commented out the uploading of the entire /out directory as an artifcat as it seems to take very long (took >50min when clang-tidy failed)
Testing
CI will validate
1.0 Justification: fixes failing CI builds

force-merged because it seems infineon check never finishes. All other tests were green.


Repository

My Introduction
Olaf - A Hardworking CMD Student
Name
Olaf Driessen
Class
TECH 3
About me
I live in Mijdrecht. I'm 21 years old. My hobbies are waterpolo, gaming, chilling with friends and going out to party
Goals
That i know what i'm exatly  doing with the code and that i can explain what i programmed.
Skill level
intermediate. I know the basic stuff but i want to know more about the advanced stuff and be more secure about JS coding
GitHub username
https://github.com/OlafDs
GitHub repository
https://github.com/OlafDs/js-bootcamp

👋 Hi Olaf, the link to your repo has been added to the admin sheet. Thanks! 🎉
What games are you playing? 🎮


shards install : crystal/shards not found

When I execute shards install, even on a just init empty app, I get this error :
Resolving dependencies
Writing shard.lock
Could not execute 'crystal': Error executing process: 'crystal': No such file or directory

On some projects, I have the same message, with shards missing.
I think the problem is that on the VM I use, crystal/shards are in the $HOME/.local/bin folder (it's in $PATH). I can't change that.
My crystal version :
Crystal 1.10.1 [c6f3552f5] (2023-10-13)

LLVM: 15.0.7
Default target: x86_64-unknown-linux-gnu

Does the shell find the correct executables?
What does which crystal and which shards tell you?

Yes, I use crystal as a command in a build script and everything is fine. But not with shards install.

~ $ which crystal
/home/bas/.local/bin/crystal
~ $ which shards
/home/bas/.local/bin/shards

For example :

$ shards init
Created shard.yml
$ shards install
Resolving dependencies
Writing shard.lock
Could not execute 'crystal': Error executing process: 'crystal': No such file or directory
$ crystal
Usage: crystal [command] [switches] [program file] [--] [arguments]
Command:
init                     generate a new project
build                    build an executable
clear_cache              clear the compiler cache
docs                     generate documentation
env                      print Crystal environment information
eval                     eval code from args or standard input
i/interactive            starts interactive Crystal
play                     starts Crystal playground server
run (default)            build and run program
spec                     build and run specs (in spec directory)
tool                     run a tool
help, --help, -h         show this help
version, --version, -v   show version
Run a command followed by --help to see command specific information, ex:
crystal  --help

What happens if you run CRYSTAL=/home/bas/.local/bin/crystal shards install?

You seem to be hitting https://github.com/crystal-lang/shards/blob/master/src/config.cr#L88 and that seems affected by the environment variable CRYSTAL_VERSION. Does env | grep CRYSTAL_VERSION return anything?

@lasso If CRYSTAL_VERSION was set, shards would not try to execute the crystal command. The only purpose for that is to determine the version.

What happens if you run CRYSTAL=/home/bas/.local/bin/crystal shards install?

it's fine

You seem to be hitting https://github.com/crystal-lang/shards/blob/master/src/config.cr#L88 and that seems affected by the environment variable CRYSTAL_VERSION. Does env | grep CRYSTAL_VERSION return anything?

it's empty

If CRYSTAL=/home/bas/.local/bin/crystal shards install works, it seems like an issue with your PATH configuration. Maybe it's not properly forwarded to shards...?
I don't think shards can do anything about this.

If it was not properly forwarded, shards or crystal command wouldn't work. I get a "No such file or directory" only when shards is launching crystal

Let's check that with a simple script that prints $PATH to stderr and fails:
echo 'echo $PATH >&2; exit 1' > test.sh
chmod +x test.sh
CRYSTAL=$PWD/test.sh shards install

Does the output contain /home/bas/.local/bin/?
And what's the output of crystal eval 'puts Process.find_executable("crystal")'?


(DO NOT MERGE) Correcting input params for PA

Haohai/Ruben/Amin need to confirm if the article still makes sense given the change and then we can roll the changes to the other articles referencing the params

Abandoning as we'll take a different approach with docs


How to send location to an specific URL?

hello guys!
Can I use traccar to send my location to something like this URL?
myurl.com/location
If not, do you know an app to do this?
Thanks!

You would have to change the source code if you want to add a path to the URL.

In the version 5.0 you can provide custom URL.


Adding my project Shortly(an url shortner) using vanilla JS

This is an URL shortner Application.

Please link the issue with the PR and in the readme file describe the project and tech stack used

yes mam i update my project at readme.md file. Mam please add my project.

This issue is assigned to someone else. You cannot directly raise a PR

This issue is assigned to someone else. You cannot directly raise a PR. You can wait for sometime. If the person fails to complete the task, then it will be assigned to you, and then only this PR will be accepted.

all projects are assigned in the list, so what can i do now???

This issue is assigned to someone else. You cannot directly raise a PR. You can wait for sometime. If the person fails to complete the task, then it will be assigned to you, and then only this PR will be accepted.

all existing issues projects are assigned in the list, so what can i do now???

You can raise unique issues

This issue is assigned to someone else. You cannot directly raise a PR. You can wait for sometime. If the person fails to complete the task, then it will be assigned to you, and then only this PR will be accepted.

all existing issues projects are assigned in the list, so what can i do now???

Do not work on assigned issues
Create your own unique issues and work on that


Is there convinient way to access list of images per page

Summary
I want to know if there is way to access list of images on page vai PluginAPI, preferably in afterBuild hook.
Basic example
https://developers.google.com/search/docs/advanced/sitemaps/image-sitemaps
Motivation
I want to create sitemap plugin which includes images.

In afterBuild you can access the queue api.afterBuild(({ queue }) => {}, which contains an array of the static and dynamic pages generated, including their file path. Maybe a node.js parser can extract the img elements from these HTML files to create an XML sitemap. Another idea, maybe a Vue plugin can rely on each component to explicitly list the images it will contribute to an image sitemap. During SSR, the plugin can take these values and write a file in /static/ during the build, and this will be auto copied to the dist folder.


Adding normalize_hostname from mod_proxy_cluster master

Supplementary to PR #494

Can one of the admins verify this patch? If it is not dangerous to our systems, juts tell me to "run_tests".  ( without the underscore and quotes :smiley: )

Can one of the admins verify this patch? If it is not dangerous to our systems, juts tell me to "run_tests".  ( without the underscore and quotes :smiley: )


WIP: Omnibus MC only

Needed to unblock https://github.com/PX4/Firmware/pull/10355, but this is also a good excuse to fix these bogus dependencies.
Navigator is currently dependant on the VTOL parameters VT_B_DEC_MSS and VT_B_REV_DEL. Let's either handle this with the VTOL controller publishing a status message, or falling back to the old param API.
I'd vote for an orb based solution if @RomanBapst could assist. I'll be mostly unavailable until next week.
Similar to the way the FW position controller publishes position_controller_status for the L1 distance that's used by navigator as the acceptance radius, we could have the vtol controller publish an appropriate acceptance distance for back transition (how VT_B_DEC_MSS and VT_B_REV_DEL are used). https://github.com/PX4/Firmware/blob/master/src/modules/navigator/mission_block.cpp#L291-L305
Going forward I think we should strictly enforce parameter module boundaries with only a few global exceptions (SYS and CAL?).

Crazyflie can be fixed as well. https://github.com/PX4/Firmware/blob/master/cmake/configs/nuttx_crazyflie_default.cmake#L65

I went for the simple solution (C-API) in https://github.com/PX4/Firmware/pull/10738 to unblock things.


Update nexus

Codecov Report

Merging #190 (91352e1) into master (db56849) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #190   +/-   ##
=======================================
  Coverage   97.81%   97.81%
=======================================
  Files          16       16
  Lines         183      183
  Branches       36       36
=======================================
  Hits          179      179
  Partials        4        4

Impacted Files
Coverage Δ

src/rules/base.ts
100.00% <ø> (ø)

src/rules/interface.ts
100.00% <ø> (ø)

src/rules/logic.ts
100.00% <ø> (ø)

src/rules/operators/and.ts
100.00% <ø> (ø)

src/rules/operators/chain.ts
100.00% <ø> (ø)

src/rules/operators/not.ts
100.00% <ø> (ø)

src/rules/operators/or.ts
100.00% <ø> (ø)

src/rules/operators/race.ts
100.00% <ø> (ø)

src/plugin.ts
88.88% <100.00%> (ø)

Continue to review full report at Codecov.

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


[Design] : Dashboard Design

Create a Design for the Dashboard screen of the wise app having the following pages:

Form listing page
Form submission details page

Submissions for a form
Analytics for a form
Settings page for a form

Figma link : dashboard


Remove deprecated Executor code

I marked the Executor code as deprecated because it is not used in gwt-ol3. I also don't know the sense because there are no tests or documentation about it. Please let me know if anybody needs this. Otherwise I will remove this in the next version.

@lobmarib Could you check this?


[BEAM-12400] MongoDBIO support for update within documents

Current MongoDBIO connector only supports inserts and replace in a collection. In general there will be requirements for updating an existing document - adding a new field, updating an existing field, pushing into an array or set etc. Added support for this.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

can you improve the javadoc as well? It would be helpful if I could see what an example of usage of this transform looksl ike

can you improve the javadoc as well? It would be helpful if I could see what an example of usage of this transform looksl ike

Have added javadoc related to update.

I'll take a look now

Run Java PreCommit

Run Java PreCommit

Can you please help me how to do this? Thanks much

@pareshsarafmdb No worries, it's just a command to run Java PreCommit job. Actually, it fails (you can see the results by clicking on "Details" against Java ("Run Java PreCommit") check):
20:47:11 > Task :sdks:java:io:mongodb:compileJava
20:47:11 /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Phrase/src/sdks/java/io/mongodb/src/main/java/org/apache/beam/sdk/io/mongodb/UpdateField.java:43: error: [argument.type.incompatible] incompatible argument for parameter sourceField of UpdateField.
20:47:11     return new UpdateField(updateOperator, null, destField);
20:47:11                                            ^
20:47:11   found   : null (NullType)
20:47:11   required: @Initialized @NonNull String

I'd recommend to run this command ./gradlew :sdks:java:io:mongodb:check locally before pushing your changes to make sure that everything is fine.

@pareshsarafmdb No worries, it's just a command to run Java PreCommit job. Actually, it fails (you can see the results by clicking on "Details" against Java ("Run Java PreCommit") check):
20:47:11 > Task :sdks:java:io:mongodb:compileJava
20:47:11 /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Phrase/src/sdks/java/io/mongodb/src/main/java/org/apache/beam/sdk/io/mongodb/UpdateField.java:43: error: [argument.type.incompatible] incompatible argument for parameter sourceField of UpdateField.
20:47:11     return new UpdateField(updateOperator, null, destField);
20:47:11                                            ^
20:47:11   found   : null (NullType)
20:47:11   required: @Initialized @NonNull String

I'd recommend to run this command ./gradlew :sdks:java:io:mongodb:check locally before pushing your changes to make sure that everything is fine.

I have done it and verified it again. No issues with the build in local.
BUILD SUCCESSFUL in 3m 4s
58 actionable tasks: 58 executed

@pareshsarafmdb No worries, it's just a command to run Java PreCommit job. Actually, it fails (you can see the results by clicking on "Details" against Java ("Run Java PreCommit") check):
20:47:11 > Task :sdks:java:io:mongodb:compileJava
20:47:11 /home/jenkins/jenkins-slave/workspace/beam_PreCommit_Java_Phrase/src/sdks/java/io/mongodb/src/main/java/org/apache/beam/sdk/io/mongodb/UpdateField.java:43: error: [argument.type.incompatible] incompatible argument for parameter sourceField of UpdateField.
20:47:11     return new UpdateField(updateOperator, null, destField);
20:47:11                                            ^
20:47:11   found   : null (NullType)
20:47:11   required: @Initialized @NonNull String

I'd recommend to run this command ./gradlew :sdks:java:io:mongodb:check locally before pushing your changes to make sure that everything is fine.

I have done it and verified it again. No issues with the build in local.
BUILD SUCCESSFUL in 3m 4s
58 actionable tasks: 58 executed

And If i see the console log the error doesn't seem to be related to changes I made. Can you pls check. @aromanenko-dev

Run Java PreCommit

the precommit seems to be failing due to a static check issue:

... also sorry about the delay! : )

Just added minor stylistic comments.
I still wonder: What happens when users want to update the whole old record into the whole new record?
Finally, I have one more question about a later improvement to consider for this IO - is it worth thinking later about passing a lambda to choose the destination collection?

@pabloem If I understand what if user wants to update with entire source document into a destination document - In that case you have a overloaded method which just takes update operator and dest field. This does full document update. Did I make sense?

test issues are unrelated (at least Java Examples failures). This is on me to review. Sorry about the delay again.

Just added minor stylistic comments.
I still wonder: What happens when users want to update the whole old record into the whole new record?
Finally, I have one more question about a later improvement to consider for this IO - is it worth thinking later about passing a lambda to choose the destination collection?

@pabloem If I understand what if user wants to update with entire source document into a destination document - In that case you have a overloaded method which just takes update operator and dest field. This does full document update. Did I make sense?

Yes thats right,

Thanks, I'm fine with code changes. LGTM.
However, before merging, please, squash all commits and avoid the merge commits - please, use rebase instead.
Also, it's not a good practice to create a PR from master branch, it's much better to use a dedicated feature branch for that. Though, I think we can stand with this for now.

@pareshsarafmdb can you squash your commits? then we'll merge. Thanks!

Run Java PostCommit

squashed using Github's feature

Hello,
I'm sorry to bring up this old discussion but it's the only thing i found so far (i can create an issue if you prefer).
I have a hard time to understand the difference between withFindKey and withUpdateKey can anyone please explain it to me ?
Here is my issue : I have a Mongo document like this
{
 "_id" : objectId,
 "patientId" : "u-u-id",
 "therapyDate" :<PHONE_NUMBER>, // timestamp
 "value": x
 }

I know that the combination (patientId and therapyDate) is unique so i am using the following update configuration :
.withFindKey("patientId")
.withFindKey("therapyDate")
.withUpdateFields( UpdateField.fieldUpdate("$set","value", "value"))

Using this configuration a new document is created instead of updating the existing one. Can you point me to the proper direction to update this kind of documents (not depending on the _id as updatekey) ?
thanks in advance


Add Connection Timeout Handling to JDK Client

Currently request timeouts leverage Reactor's timeout mechanism, this works great in most scenarios other than when a large payload is being sent. The reason this doesn't work well is that the timeout period begins on subscription and ends on an element being emitted, response received from the service in this case, or when the timeout period elapses. Large uploads may take a very long time to finish sending and getting a response from the service, this leads to either errant timeouts on uploads due to the timeout being slow or scenarios where responses are being flaky and the timeout period is very long.
The timeout handling pattern should be updated to push this logic into the HttpClient being used where it is able to monitor the flow of data to either trigger a request timeout, upload taking too long to complete, or a response timeout, server is busy, went down, or dropped connection.

@mssfang this will be part of enable JDK HttpClient in CI and being releasable


Support virtualenvs(with --system-site-packages) from relenv

Signed-off-by: Pedro Algarvio<EMAIL_ADDRESS>

This needs a test case but I don't have the time for that right now


[evcohen/jsx-ast-utils#70] Support OptionalMemberExpression AST nodes

Support patterns like
<div foo={b?.c?.d;} />

I had to update the project from Babel 6.x to Babel 7.x to support this change.

Coverage increased (+0.04%) to 98.889% when pulling cf99ce49c80f27db01d44176cf2e3a25f6e3aa76 on jessebeach:fix-OptionalObjectExpression into a9d415954efedd5f601769d233c3707705fc5972 on evcohen:master.

@ljharb how do you recommend we deal with the optional chaining plugin in Babel 7 which means we need to drop support for Node 4 and 5, since Babel 7 doesn't support them?

Instead of forcing getValue to be injected everywhere, could you use a lazy require?

@ljharb like this in a function block?
const getValue = require('./index.js').default;

I'm worried that this will incur an extra synchronous file read and slow down the process. Passing the function around isn't terrible. Plus I'd have to suppress just as many global require lint warnings as circular import warnings that I was trying to fix with this change:
8:20  error  Unexpected require()  global-require

It would only incur a file read once; after which there's a require cache (which import utilizes since babel just transpiles it to require). You'd certainly have to suppress global-require warnings, true.
As for optional chaining; perhaps we could move the project to babel 7, but make a special travis.yml script to uninstall babel 7 and install babel 6 (and a helper file to handle the conditional requires, and perhaps conditional skips) so we can keep testing in those versions?

As for optional chaining; perhaps we could move the project to babel 7, but make a special travis.yml script to uninstall babel 7 and install babel 6 (and a helper file to handle the conditional requires, and perhaps conditional skips) so we can keep testing in those versions?

@ljharb only the built lib files need to run in Node 4 and 5, right? I wouldn't expect the project to build in Node 4 or 5 as a requirement, since only developers working on this project need to build it. I added a node target to the babelrc to build for Node 4, so that the necessary transforms run.
"presets": [
    [
      "@babel/preset-env", {
        "targets": {
          "node": "4.0",
        }
      }
    ]
  ],

True, so that's another alternative - in travis, we'd have nvm install lts/*, run the build process, and then nvm use "${TRAVIS_NODE_VERSION}". Slightly slower but certainly cleaner.

@ljharb You definitely have more exposure to the wider Node world. Is Node 4/5 support still a hard line?

True, so that's another alternative - in travis, we'd have nvm install lts/*, run the build process, and then nvm use "${TRAVIS_NODE_VERSION}". Slightly slower but certainly cleaner.

@ljharb , We'd need to build the __tests__ directory in Node 6+, switch to Node 4/5, then run Jest with the transforms turned off and pegged to version 23 (but only in Node 4/5); we can use Jest 24+ with Node 6+.
This all sounds doable (although I won't be doing it tonight 😄). But my question is, is it completely necessary? Are other projects maintaining support for Node 4/5? And if yes, how many years will we need to keep up this support in your opinion?

I mean, node < 6 is EOL, and 6 will be EOL soon. But while eslint still supports a version of node, I think we should still support it.
Unfortunately jest and mocha both have dropped support for older nodes, so at this point, I recommend that jest be used for apps, and tape for everything else.
When eslint 6 comes out, I think we could drop support for eslint < 5, which would allow us to drop node < 4. However, I think if a tool is going to force dropping support, then the tool is broken, and the solution isn't to cut off those users.
All of my projects maintain support for node 0.6, for as many decades as that ends up being practical. Humans are more important than tools :-)

@ljharb I set the Node versions back to 4, 5, 6. I spent the whole day trying to get the project to run in a Babel 6 and Babel 7 world, but I was unsuccessful. So for now, I'm going to make "make the project work" in Babel 7, but the code will test Babel 6 (Node 4, 5 and 6). That's where we're stuck until we drop support for Node 4 and 5.

It'd be nice to find a better away around the circular deps, but this LGTM.

Agree, I'm not in love with it either. But inspiration is not arriving to me with consistency lately :)


second load of image often unable to get pixel data in canvas

Reload the following code a few times in your browser.  It often is unable to load pixel data about the loaded image from the canvas on the second re-loading of the image.  Sometimes it fails to get the naturalWidth and naturalHeight of the image on the second load too.
Tested on chrome, safari, and firefox with similar results (with safari suffering the most failures).

Thanks for reporting this issue. Looks like no one else chimed in so I'm closing this one. :door:


upgrade to scip 4.0

@leethargo  I guess I'll need some help here regarding the versioning of CSIP.
Should we go to CSIP 0.3.7 or CSIP 0.4.0 ?
The interface of CSIP didn't change

What does it mean to support the new SCIP, can't we support both?
Does any of the code of CSIP change because of that? If so, then we require the user to install the new SCIP, which I feel is a breaking change, so we should go to 0.4.0.

Well, there is a single line of code changed in CSIP.
I guess we could support both, but why?

Then the update is not a breaking change, and people who update SCIP.jl with Julia's package manager don't end up with a broken system.
On the other hand, users would not even know about the new SCIP...

it is not a breaking change, but it will just not compile with SCIP 3.2.1, or am I missing your point?

Yes, so an update of SCIP.jl will tell them that CSIP is out-of-date, but if the user then deletes CSIP (as instructed) and runs Pkg.build("SCIP") it will fail.

why will it fail? scip 4 is out now ;)

Users still have to download and install it, nothing is automated.

yeah, but that has always been then case, right?

Given that everything is already manual, it's okay with me if an update to SCIP.jl results in a broken system. However, it would be nice to provide a useful error message, e.g., as we do with ECOS. Whoever wants to keep using the old version of SCIP can pin SCIP.jl.

Well, we have that error message in SCIP.jl, but refering to CSIP, not SCIP.
@fserra: Didn't you already have a pull request with a one-line change? We should then also update the README and be explicit about SCIP's version.

yeah sure. So what is it then? 0.4.0 or 0.3.7??

Go for 0.4.0.


Clarified schema.fields property

fixes https://github.com/frictionlessdata/specs/issues/367

Rationale
It's been a while Table Schema has had this ambiguity of the schema.fields property. I think it's a good point to finally clarify that:

fields are strictly order based
fields have to cover all the data columns

Without this clarity it's basically not possible to create a reliable implementation (meaning "no interoperability"). Of course, in the real world, the existent implementation already assumed both points as far as I know.
Comment
Throughout the time, we saw many requests and use cases that had optional fields or a requirement to order fields. Most of them can be handled on the implementation level as an additional feature, but, of course, the Table Schema spec might consider adding a new feature like schema.fieldsMap or something like this but I believe it just needs to be a different thing not schema.fields and also it should be really justified as, in-general, Data Package Standard is for describing data, not for transforming data (while cherry-picking fields is kind of transformation)

For context, the change to SHOULD was introduced with https://github.com/frictionlessdata/specs/pull/707.
I understand that this leaves things dubious, and that should be corrected. But rather than rephrasing to MUST, I would strongly prefer to introduce a property fieldsSync (or similar) as part of v2, so publishers (not the implementation!) can indicate with TRUE that the fields in their data source needs to be synced/mapped to the fields listed fields. The default value can be FALSE to mimic current behaviour. The definition of fieldsSync can indicate that 1) for FALSE the columns in the data sources MUST be provided in same order (and be complete) and 2) for TRUE a header must be present.
Note such fieldSync property is not only for data transformation, but for describing data as well, since it allows communities to define common fields/terms as published/shared Table Schemas. This has three huge benefits:

The community does not need to reinvent common terminology (such as type, name, and fields) to define the fields/terms in their vocabulary. They can just use Table Schema to do so.
By directly referencing a published schema (in schema) rather than verbosely including it as a JSON object, publishers indicate they make use of the shared standard and validation will validate against that standard.
Publishers are nudged to adopt Data Package for their datasets.

With fieldsSync = TRUE, publishers don't have to include all the (sometimes hundreds) defined fields in their data sources and the result of validation doesn't depend on a flag in the implementation. It will depend on the support of fieldsSync in that implementation.

@roll, I guess it's probably best if I suggest this as a separate issue/feature request? The discussion didn't put on on the radar for v2.

I don't like this change, but I don't have an alternate suggestion at the moment. What @peterdesmet suggests is interesting.
I can say:

fields being strictly ordered is IMHO a bad idea. We only had this originally because of the possibility to have duplicate column names in CSV. But, that is extremely uncommon in practice, and brings with it many, many other interoperability issues, so, I don't think we should double down in support for that.
I don't think partial field selection is a transformation - many publishers have streams of data with hundreds of columns and I think it is a reasonable and common use case to select a subset for modeling / validating / loading

Hmmm, I like where this is going, but in my first reading of the proposed fieldSync property I expected to behave in the opposite way: When fieldSync is TRUE, I would expect the order of the fields to be in sync with the csv, not that I would need to sync the fields.
The other disadvantage to making this a flag is that it requires reading the data file to know what fields are being shipped with it. It's no longer the "schema" for my data file (defining "schema" as a description of the data there)... it's now something that I can use to create the schema of my data after I know what columns are in the file. I would prefer not requiring a trip to the data in order to know what to expect there.
That said, I really like @peterdesmet's direction here of creating "libraries" of field types that then can be easily referenced by multiple schemas. Publishers could publish field type libraries for different measures, which could then be referenced across multiple data packages and facilitate connections of the same variables across data sets.
If that's what we're going for, I would prefer a solution that 1) preserved the "schema" as a way to know what I should expect in my table without having to open it (including the ordering of the fields!), and 2) ALSO allowed me to define field metadata by referencing / linking an external (or internal!) "library" or "collection" of fields defined by a publisher. This way I could mix field types from the different publishers in the same schema, along with my own definitions.
Something like this:
{
    "schema": {
      "fields": [
        {
          "name": "myField",
          "type": "string",
          "description": "A locally defined field"
        },
        {
          "name": "publishedMeasureItem1",
          "type": "external",
          "library": "http://www.publisher.com/painMeasures.json",
          "id": "painMeasureItem1"
        },
        {
          "name": "publishedMeasureItem2",
          "type": "external",
          "library": "http://www.publisher.com/painMeasures.json",
          "id": "painMeasureItem2"
        },
        {
          "name": "differentPublishedMeasure1",
          "type": "external",
          "description": "In this case we override the description property of the published measure",
          "library": "http://www.differentpublisher.com/stressMeasures.json",
          "id": "happyScale1"
        }
      ]
    }
  }

Although I don't really like having to do a url-fetch to learn the data type. So alternatively something like this?
{
    "schema": {
      "fields": [
        {
          "name": "myField",
          "type": "string",
          "description": "A locally defined field"
        },
        {
          "name": "publishedMeasureItem1",
          "type": "integer",
          "inherits": {
            "library": "http://www.publisher.com/painMeasures.json",
            "id": "painMeasureItem1"
          }
        },
        {
          "name": "publishedMeasureItem2",
          "type": "integer",
          "inherits": {
            "library": "http://www.publisher.com/painMeasures.json",
            "id": "painMeasureItem2"
          }
        },
        {
          "name": "differentPublishedMeasure1",
          "type": "integer",
          "description": "In this case we override the description property of the published measure",
          "inherits": {
            "library": "http://www.differentpublisher.com/stressMeasures.json",
            "id": "happyScale1"
          }
        }
      ]
    }
  }

Just brainstorming other possibilities, this is not meant to be a complete proposal.
Long of it short, I agree with @roll that we should think about introducing this kind of functionality as a separate feature, and making the schema.fields definition more strict:

the Table Schema spec might consider adding a new feature like schema.fieldsMap or something like this but I believe it just needs to be a different thing not schema.fields and also it should be really justified as, in-general, Data Package Standard is for describing data (emphasis mine)

I'm intrigued by @peterdesmet's idea in https://github.com/frictionlessdata/datapackage/pull/16#issuecomment-1881498631, as I can immediately see the value of the benefits he describes (we've used the existing schema-sync option and a few helper functions to achieve something similar but in a clumsy way). I'll wait to see if others raise concerns, but I believe I could get behind this as a way to ultimately resolve this issue. That said, I definitely agree with @pwalsh that accommodating duplicate column names is not sufficient reason to insist on strict column ordering, and that filtering columns is not really a transformation but rather just a more targeted read.

@peterdesmet
Working on frictionless-py I was always waiteing for a spec-level way to define partial schemas (cherry-picking fields basically). Currently, existent schema_sync is kind an implementation hack TBH as it's not really interoperable
Let's continue proposal refining in https://github.com/frictionlessdata/specs/issues/367

REJECTED by WG (vetoed)


setState when Motion is not mounted

I have a regression 0.3.1 -> 0.4.1
When my Motion component is unmounted while animating, https://github.com/chenglou/react-motion/blob/master/src/Motion.js#L178 triggers setState (it wasn't the case with 0.3.1) with the infamous warning from React in dev mode.
This wouldn't be an issue in itself, but for some reason the code loops like hell, never stops, with 100% CPU and setState warnings keeping coming per the dozen.
I am confident I am in a supported common use case. I just animate a collapse component that can be removed from the DOM at any time.
How can I help?

Eh wow, really?  Because we're testing against setting state after the component's unmounted

Can you show me where the test is so I can troubleshoot a bit myself?
I use a Collapse component forked from react-collapse, maybe you'll see smtg stupid:
import React, { Component } from 'react';
import { Motion, spring } from 'react-motion';
import HeightReporter from 'react-height';

class Collapse extends Component {
  constructor(...params) {
    super(...params);
    this.state = {
      height: -1,
      staticRendering: true,
      startsOpen: this.props.isOpened,
    };
  }

  componentWillMount() {
    this.height = '0.0';
  }

  onHeightReady = height => {
    this.setState({ height, staticRendering: false });
  };

  render() {
    const { isOpened, style, children, springConfig, ...props } = this.props;

    const { height, staticRendering, startsOpen } = this.state;
    const stringHeight = parseFloat(height).toFixed(1);

    // Cache Content so it is not re-rendered on each animation step
    const content = (
      <HeightReporter onHeightReady={this.onHeightReady}>
        {children}
      </HeightReporter>
    );

    if (staticRendering && isOpened) {
      return
{content}
;
    }

    return (
      <Motion
        defaultStyle={{ height: startsOpen ? height : 0 }}
        style={{ height: spring(isOpened ? height : 0, springConfig) }}
      >
        {st => {
          this.height = Math.max(0, parseFloat(st.height)).toFixed(1);

          // TODO: this should be done using onEnd from ReactMotion, which is not yet implemented
          // See https://github.com/chenglou/react-motion/issues/235
          if (!isOpened && this.height === '0.0') {
            return null;
          }

          const newStyle = (isOpened && this.height === stringHeight) ? { height: 'auto' } : {
            height: st.height, overflow: 'hidden',
          };

          return
{content}
;
        }}
      </Motion>
    );
  }
}

Collapse.propTypes = {
  isOpened: React.PropTypes.bool.isRequired,
  children: React.PropTypes.node.isRequired,
  style: React.PropTypes.object, // eslint-disable-line react/forbid-prop-types
  springConfig: React.PropTypes.arrayOf(React.PropTypes.number),
};

Collapse.defaultProps = {
  style: {},
};

export default Collapse;

What is the easiest way nowadays to build a repro online? Do we have templates?

Codepen is fine. Try this template: http://codepen.io/anon/pen/EPLyLW?editors=0010
Relevant test here: https://github.com/chenglou/react-motion/blob/ffb0628fbea1f4d83a69ea0f6ed910ee64383c76/test/Motion-test.js#L149
(I'll check into this this afternoon)

[x] You are awesome

Do not waste any of your free time on this until I find what's what with the test and come up with a repro.

Just tried 0.4.2, no pb.
I tried again with 0.4.1 to be sure, it failed.

Weird... there's been no change to Motion in the latest release beside an obscure new feature.


kernel/common-config: throw on duplicate configuration option definitions

Previously, when a kernel configuration option was defined multiple times (in different sections), only the first value was honored and all subsequent ones were silently ignored. Remove this footgun by throwing in this situation instead.
In addition, fix all instances where an option was in fact defined multiple times. In two cases (RCU_TORTURE_TEST and CRASH_DUMP), the value was effectively the same both times. In the other two cases (SCHEDSTATS and DRM_SIMPLEDRM) the value was in fact different; the one that was actually applied was kept here to prevent a rebuild.
Pinging @K900: SCHEDSTATS and DRM_SIMPLEDRM that were intended to be introduced in https://github.com/NixOS/nixpkgs/pull/296867/files should be revisited, retested and then probably merged along with a round of kernel updates.
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Ugh. Why does everything in this system try to be smart.

@k900 would you mind reopening a PR which re-does the changes to DRM_SIMPLEDRM and SCHEDSTATS?

Done: #298332


How to choose a template (or template_type)

base -> base: Use 'default-generation' or 'AUTO'.
base -> chat & lora: Use 'default' because default is a multi-turn dialogue template and doesn't include special tokens. This avoids poor performance caused by the model not having seen special tokens before.
base -> chat & full: You can randomly choose a multi-turn dialogue template; for example, 'chatml'. Alternatively, you can choose the template corresponding to the chat model. For instance, for qwen2-7b, choose 'qwen'; for llama3-8b, choose 'llama3'.
chat -> chat: Use AUTO.

Hello, I want to perform the second case from base->chat using LoRA. So the recommendation is to use this default template?
register_template(
TemplateType.default,
Template([], ['### Human:\n{{QUERY}}\n\n### Assistant:\n'], ['\n\n'], [['eos_token_id']],
DEFAULT_SYSTEM, ['{{SYSTEM}}\n\n'],
auto_add_bos=True))
Does this way can produce repetition problem after finetuning model?

Examples:
    chatml (with bos):
        prefix: <s>
        prompt: <|im_start|>user\n{{QUERY}}<|im_end|>\n<|im_start|>assistant\n
        chat_sep: <|im_end|>\n
        suffix: <|im_end|>
        system_prefix: <s><|im_start|>system\n{{SYSTEM}}<|im_end|>\n

    <s><|im_start|>system  # prefix or system_prefix
    {{SYSTEM}}<|im_end|>
    <|im_start|>user  # prompt
    {{QUERY}}<|im_end|>
    <|im_start|>assistant
    {{RESPONSE}}<|im_end|>  # chat_sep
    <|im_start|>user  # prompt
    {{QUERY}}<|im_end|>
    <|im_start|>assistant
    {{RESPONSE}}<|im_end|>  # suffix

Hello, I want to perform the second case from base->chat using LoRA. So the recommendation is to use this default template?
register_template( TemplateType.default, Template([], ['### Human:\n{{QUERY}}\n\n### Assistant:\n'], ['\n\n'], [['eos_token_id']], DEFAULT_SYSTEM, ['{{SYSTEM}}\n\n'], auto_add_bos=True))
Could this way produce repetition problem after finetuning model?

To avoid the problem of being unable to stop due to the eos_token not being trained.


Tweet with apksigner certificate hash currently not publicly available

Due to the change of Twitter limiting content access to only logged in Twitter users on June 30, 2023; the tweet with the apksigner certificate hash can only be seen by logging into Twitter.
That tweet was saved once on the Wayback Machine.  I also just saved a capture from the Wayback Machine's copy on archive.today.
I'm not sure if this will be an issue, since "allegedly supposedly" this change is supposed to be "temporary", but only time will tell.

Twitter now lets signed out users to view tweets.  (I waited for a bit to make sure this change will stay for the time being.)
As a precaution, I've made a capture on the Wayback Machine and archive.today just in case something like this happens again.

As a suggestion, I recommend also posting the apksigner certificate hash on the project's Mastodon account.


copy issue from benchrunner

jeromeetienne/tquery issue are ugly and random
go on benchrunner and steal them from there. it is the default ones now

done


Editing keywords removes existing keywords and new keywords aren't added on beta.

On beta.hydroshare.org, if I try to edit the keywords of an existing resource, all keywords are removed, and new keywords aren't saved. If the resource was public, it will be made private. This makes it impossible to make a resource public. This doesn't seem to be an issue on www.
This looks like it might be related to this closed issue:
https://github.com/hydroshare/hydroshare/issues/1743
Is this related to any ongoing updates?

This looks like having connections to what I experienced on park which was deployed using code more recent than what is deployed on www. For details on the problem of adding keywords and making the resource public, see https://github.com/hydroshare/hydroshare/issues/3175 toward the end of the message thread. @sblack-usu Any idea on what code changes since www deploy could have caused this regression issue?

Nothing comes to mind, but we should certainly work this out.  Beta currently has the generic resource migration code in #3101 , which is also caught up to develop, so it could be anything merged since 1.19.1

Just as an update, I'm still running into this issue with beta.hydroshare.org. I've tried it in Safari, Chrome, and Firefox. When I type in a keyword and click add, it's added to the list, but the banner at the top requesting keywords be added doesn't go away, and I'm not getting any error messages. The option to make the resource public also remains greyed out. When I refresh the page, the keyword I added is no longer there, and any other keywords that were there have disappeared too. If the resource was public before editing the keywords, it is switched to private after editing the keywords.
Here's a screenshot showing that I've added keywords, but the banner at the top doesn't update. I've hidden a few fields so everything's visible.

Here's the expected behavior on www.hydroshare.org.

I didn't capture it in the screenshot, but a green banner appears briefly saying the resource can now be made public, and the yellow banner at the top goes away.

https://github.com/hydroshare/hydroshare/issues/3199#issuecomment-468775614


Fix Typo Readme

The original english is actually correct. Changing it to "it will" is actually incorrect.

https://www.thoughtco.com/inversion-definition-1209968


WARN  API  [BlkHdr]: ExecutorService Q is full!

On one of my computers after it had downloaded 57GB worth of the testnet blockchain and the kernel was still busy syncing (but must have been stuck, because the kernel on my other computer on a slower connection got to 65G overnight and they both started at around 53G), it kept showing this message
18-04-23 05:14:53.628 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 05:14:59.954 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 05:14:59.954 INFO  SYNC [sync-ib]: <import-status: node = c33d49, hash = 88ffb4, number = 83059, txs = 106, result = IMPORTED_BEST, time elapsed = 8866 ms>
18-04-23 05:15:08.629 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 05:15:09.342 INFO  SYNC [sync-ib]: <import-status: node = c33d5f, hash = 9d012b, number = 83060, txs = 96, result = IMPORTED_BEST, time elapsed = 9386 ms>
18-04-23 05:15:09.342 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 05:15:09.756 INFO  SYNC [p2p-worker-2]: <import-status: node = 6bd088, hash = 82c5ab, number = 95585, txs = 85, result = NOT_IN_RANGE>
18-04-23 05:15:14.123 INFO  SYNC [sync-ib]: <import-status: node = c33d39, hash = 55859c, number = 83061, txs = 59, result = IMPORTED_BEST, time elapsed = 4776 ms>
18-04-23 05:15:14.123 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 05:15:18.339 INFO  SYNC [sync-ib]: <import-status: node = c33d39, hash = 285b50, number = 83062, txs = 51, result = IMPORTED_BEST, time elapsed = 4216 ms>
18-04-23 05:15:18.339 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 05:15:19.118 INFO  SYNC [sync-ib]: <import-status: node = c33d39, hash = 98d9f0, number = 83063, txs = 11, result = IMPORTED_BEST, time elapsed = 779 ms>
18-04-23 05:15:19.118 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 05:15:23.629 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 05:15:23.940 INFO  SYNC [p2p-worker-6]: <import-status: node = 6bd088, hash = b2bb76, number = 95586, txs = 90, result = NOT_IN_RANGE>
18-04-23 05:15:24.947 INFO  SYNC [sync-ib]: <import-status: node = c33d39, hash = 641808, number = 83064, txs = 71, result = IMPORTED_BEST, time elapsed = 5829 ms>
18-04-23 05:15:24.947 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 05:15:30.453 INFO  SYNC [sync-ib]: <import-status: node = c33d39, hash = c5901c, number = 83065, txs = 73, result = IMPORTED_BEST, time elapsed = 5505 ms>

I restarted it and now it's fine again.

I checked this evening and it was stuck again.
(this is on rock solid, reliable productive hardware)
18-04-23 21:16:29.030 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:16:33.035 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 13a4dc, number = 94142, txs = 38, result = IMPORTED_BEST, time elapsed = 4005 ms>
18-04-23 21:16:33.035 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:16:34.814 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 7693de, number = 94143, txs = 88, result = IMPORTED_BEST, time elapsed = 1779 ms>
18-04-23 21:16:40.987 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 21:16:43.587 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 45f70b, number = 94144, txs = 51, result = IMPORTED_BEST, time elapsed = 8773 ms>
18-04-23 21:16:43.587 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:16:46.715 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:16:46.715 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 1043d0, number = 94145, txs = 35, result = IMPORTED_BEST, time elapsed = 3128 ms>
18-04-23 21:16:55.987 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 21:17:00.234 INFO  SYNC [sync-ib]: <import-status: node = c33d12, hash = 9517b2, number = 94146, txs = 124, result = IMPORTED_BEST, time elapsed = 13516 ms>
18-04-23 21:17:00.393 INFO  SYNC [sync-ib]: <import-status: node = c33d12, hash = d42c68, number = 94147, txs = 32, result = IMPORTED_BEST, time elapsed = 159 ms>
18-04-23 21:17:00.393 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:00.526 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = 02f9a6, number = 94148, txs = 30, result = IMPORTED_BEST, time elapsed = 131 ms>
18-04-23 21:17:00.526 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:04.812 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = e75bf1, number = 94149, txs = 64, result = IMPORTED_BEST, time elapsed = 4286 ms>
18-04-23 21:17:04.812 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:08.585 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = fd0cef, number = 94150, txs = 41, result = IMPORTED_BEST, time elapsed = 3773 ms>
18-04-23 21:17:08.585 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:10.987 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 21:17:21.912 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = 7b1d0b, number = 94151, txs = 100, result = IMPORTED_BEST, time elapsed = 13327 ms>
18-04-23 21:17:21.912 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:25.987 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 21:17:27.733 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = d174cc, number = 94152, txs = 40, result = IMPORTED_BEST, time elapsed = 5820 ms>
18-04-23 21:17:27.733 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:30.527 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = 2b05a0, number = 94153, txs = 29, result = IMPORTED_BEST, time elapsed = 2794 ms>
18-04-23 21:17:30.527 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:31.477 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = e0fc3b, number = 94154, txs = 14, result = IMPORTED_BEST, time elapsed = 950 ms>
18-04-23 21:17:31.477 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:36.952 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = 5711f4, number = 94155, txs = 65, result = IMPORTED_BEST, time elapsed = 5475 ms>
18-04-23 21:17:36.955 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:39.630 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = 9ee062, number = 94156, txs = 35, result = IMPORTED_BEST, time elapsed = 2677 ms>
18-04-23 21:17:39.630 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:40.987 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 21:17:42.424 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = 1d1724, number = 94157, txs = 42, result = IMPORTED_BEST, time elapsed = 2794 ms>
18-04-23 21:17:42.424 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:43.631 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = 4a2aca, number = 94158, txs = 11, result = IMPORTED_BEST, time elapsed = 1207 ms>
18-04-23 21:17:43.631 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:45.965 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:45.965 INFO  SYNC [sync-ib]: <import-status: node = a51215, hash = 0b9485, number = 94159, txs = 36, result = IMPORTED_BEST, time elapsed = 2334 ms>
18-04-23 21:17:48.369 INFO  SYNC [p2p-worker-7]: <import-status: node = 01d8d7, hash = fc9987, number = 102950, txs = 0, result = NOT_IN_RANGE>
18-04-23 21:17:52.541 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = b72ea8, number = 94160, txs = 74, result = IMPORTED_BEST, time elapsed = 6575 ms>
18-04-23 21:17:52.541 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:55.987 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 21:17:56.270 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 5c6c33, number = 94161, txs = 46, result = IMPORTED_BEST, time elapsed = 3729 ms>
18-04-23 21:17:56.270 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:17:57.888 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 7df6ec, number = 94162, txs = 14, result = IMPORTED_BEST, time elapsed = 1618 ms>
18-04-23 21:17:57.888 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:18:04.416 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 5c0e64, number = 94163, txs = 71, result = IMPORTED_BEST, time elapsed = 6528 ms>
18-04-23 21:18:04.416 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:18:10.988 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 21:18:13.234 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 6ddb53, number = 94164, txs = 100, result = IMPORTED_BEST, time elapsed = 8818 ms>
18-04-23 21:18:13.234 WARN  API  [BlkHdr]: ExecutorService Q is full!
18-04-23 21:18:25.988 INFO  CONS [miner_status]: Aion internal miner generating 0.0 solutions per second
18-04-23 21:18:33.182 INFO  SYNC [sync-ib]: <import-status: node = 01d8d7, hash = 3b97ba, number = 94165, txs = 224, result = IMPORTED_BEST, time elapsed = 19948 ms>
18-04-23 21:18:33.182 WARN  API  [BlkHdr]: ExecutorService Q is full!

I restarted the kernel, and it immediately resumed repeating this error message "ExecutorService Q is full!"
I noticed the available storage space was low (2.1G) and it still needed 3G of blockchain compared to my other computer who's kernel is running well.
I increased the storage space by 10G, restarted the kernel and it's been running without any problem.


Implementation of github submodule in components.guides module

The goal is to implement given submodule within the scope of components.guides module and prepare the methods that provide interface for translation. The following objectives are to achieve:

[x] preparation of en.py submodule with bases classes;

[x] preparation of pl.py submodule with inheritance;

The code was checked with the following code:
from dynpy.utilities.documents.guides import GithubSynchroGuide
GithubSynchroGuide(None)


Problems in centOS 6 - 64 bits

Hello,
I have developed a web application with angular, this application uses Google Chart for painting maps. I use phantom for exporting to pdf. The server is apache 2.2. When I deploy the application all the exports to pdf are successfully done. The main issue is when I deploy the same application, in the same server in centOS 6 - 64 bits. Has anyone been experiencing a similar issue? Many thanks in advance.
Kind regards,

Thank you for submitting this ticket!
This issue tracker primarily serves as the tool to report and track bugs, defects, and development tasks.
For the general question, code review request, build problem, or other related discussion, please post it to either:

the official PhantomJS users mailing-list
Stack Overflow (with phantomjs tag)

If you have not read it yet, please check also a few tips on Effective Q&A.


mbed-cli offers no progress indicator for 'update'

Users would benefit from a progress indicator when calling mbed-cli update.

Here is good evidence on why we need a bar with progress indicator: https://github.com/ARMmbed/mbed-cli/issues/367
Our colleague Xiao based in Shanghai is seeing mbed CLI being stuck (network there is really slow)

I don't know if it is relevant, but I was having the same problem - seemingly forever mbed add's.  So much so that I killed and restarted them several times.  Then i used the -vv as per the above suggestion and progress was much much faster (before I got 1 MB downloaded of the mbed-dev repo in about 45 minutes, after it took about 3 minutes to get to 3.2MB.  It is big so it will take a while, but it is moving.

I will commit

@tweety9999 @BruceBuckland @SeppoTakalo PR #593 introduces this. Please try it out and let me know.

Now implemented and available in the official versions of Mbed CLI


Should we use a container model?

Do we want to use a container model where each step could/will be a container that has input and output?
We would need a mechanism to pass these inputs and outputs around.

Yes


Put back margin: 0 for figure.

It's currently needed for mobile view.

Ok, good you've placed a comment.


Ignore BLK100 in flake8 since black is checked

Overview

Ignore BLK100 in flake8 since black is checked.

Details

None

LGTM


fix bugs of showing range from index 0 and number not updating after …

…adding new dashboards

Current coverage is 36.01% (diff: 100%)

Merging #124 into develop will decrease coverage by 0.03%

@@            develop       #124   diff @@
==========================================
  Files           227        227
  Lines         12749      12749
  Methods           0          0
  Messages          0          0
  Branches       2157       2157
==========================================
- Hits           4596       4591     -5
- Misses         7581       7586     +5
  Partials        572        572

Powered by Codecov. Last update 4518334...1532004


feat(barchart): add entry option to customize a bar indicator

SDE-1142
Description
This PR adds the entry option to renderBarIndicators and renderBarIndicators, allowing us to customize bar indicators as needed.
How to test

Run the storybook locally (yarn start)
Navigate to the BarChart component (http://localhost:9001/?path=/story/picasso-charts-barchart--barchart#stacked-with-bar-chart-indicators) and find the example provided

Screenshots

Before.
After.

Development checks

[x] Add changeset according to guidelines (if needed)
[x] Read CONTRIBUTING.md and Component API principles
[x] Make sure that additions and changes on design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.
[x] Self reviewed
[x] Covered with tests

Breaking change

[x] codemod is created and showcased in the changeset
[x] test alpha package of Picasso in StaffPortal

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-bot run package:alpha-release

@toptal-bot run package:alpha-release

@toptal-anvil ping reviewers

@toptal-anvil ping reviewers

@toptal-anvil ping reviewers

@toptal-anvil ping reviewers

@toptal-anvil ping reviewers

Could you please review Happo?
cc: @mkrl @sashuk

@pedromonad Checking!


Feature/uri redirects

@fblundun - can you review this click tracking PR please?

Now in the release branch


Unexpected multivariant output on type errors

Describe the bug
There are different ways of defining a 2-variant input that should all behave the same, but they don't.
To Reproduce
Consider these three Polygolf programs:
1.
{
    $x <- 0;
    print_int $x;
/
    $x <- "x";
    print_int $x;
};

{
    $x <- 0;
/
    $x <- "x";
};
print_int $x;

$x <- {0 / "x"};
print_int $x;

These three programs are equivalent in theory.
Expected behavior
When compiled with -l py -a, we expect
x=0
print(x)

Type error. Operator 'print_int' type error. Expected [-oo..oo] but got [(Ascii 1..1)].
  5     $x <- "x";
  6     print_int $x;
        ^

Actual behavior
Code 1. output is the expected one.
Code 2. outputs
x=0
print(x)

x="x"
print(x)

Code 3. outputs
x=0
print(x)

Type error. Cannot assign (Ascii 1..1) to 0..0.

    ^

I was able to make all 3 examples throw the desired error by deleting this line from getType.ts:
https://github.com/polygolf-lang/polygolf/blob/ecb528177b08f89c1922f3a35a487293ab83f307/src/common/getType.ts#L59
I don't yet understand this caching well enough to know how to properly fix the issue, but this seems to be the source.

I was able to make all 3 examples throw the desired error by deleting this line from getType.ts:
https://github.com/polygolf-lang/polygolf/blob/ecb528177b08f89c1922f3a35a487293ab83f307/src/common/getType.ts#L59
I don't yet understand this caching well enough to know how to properly fix the issue, but this seems to be the source.

Yes, it is the issue. Each node can have a type cached and the cache key is the object reference. Jared's immutable trees implementation encourages reusing of nodes. The assumption is that if the node is reused, it represents the same node and it must have a same type. This assumption is broken when a node is reused in different variants where their types should be independent.
Instantiating the variants should be deep cloning the trees or something. I tried to do that but faced other issues.


Supporting selected option

I implemented the feature as described on #24. Please let me know if this is OK. Thank you!

👍


iOS - purchase notification not happening on iOS 11

Purchase notifications are not happening on iOS 11.
Thanks.

Hey @erjdriver , just to confirm if you deploy the same application on iOS10 device your workflow is working and on iOS11 it does not? Or are you testing on iOS11 only?

Disregard - installed ios 11 and it works.
But I've had some customers go thru the workflow and the app is not getting the callback on successful purchase.


[BUG] RoutedViewHost Example from ReactiveUI Handbook doesn't work as expected

Describe the bug
RoutedViewHost doesn't go back to the default content. Also you must click on Go First button twice in order to enable Go Back button.
Steps To Reproduce
Just follow guide  here https://reactiveui.net/docs/handbook/routing/ and compile Routing example.
Expected behavior
Going back to default content & enable NavigateBack after one click on GoFirst
Screenshots

Environment

OS:       Win 10 build 1803
Version   9.17.4
Device:   PC

Do you happen to have the code that generated this issue in a repository we can access?  Just want to be sure there is no additional code that might be causing issues.  Also going to make the assumption this is WPF and not UWP or WinForms.

@RLittlesII No i don't have this code in online repository. It's just exact code from online Handbook (ReactiveUI website). And yes this is WPF ... i forgot to mention it.

@M0n7y5 I was able to reproduce your issue last night.  I am going to try and find a solution to the issue.  Seems that there is a disconnect for sure in the docs.  The video of the working sample in the docs, is indeed different than what you get by implementing it.
Thank You for reporting this.

To have the behavior from the GIF recording located at https://reactiveui.net/docs/handbook/routing/ the following line of code from the tutorial:
GoBack = Router.NavigateBack;

Should be replaced with this line:
GoBack = ReactiveCommand.CreateFromObservable(
      () => Router.NavigateBack.Execute(Unit.Default));

Although there is a risk to get the IndexOutOfBoundsException. Ideally need to define the canGoBack condition via a call to WhenAnyValue and pass it to the reactive command. Probably we should simply replace the GIF from the tutorial to another one for simplicity, and mention other back button handling scenarios.

        var canGoBack = this.WhenAnyValue(x => x.Router.NavigationStack.Count).Select( cnt => cnt > 0);
        GoBack = ReactiveCommand.CreateFromObservable(() => Router.NavigateBack.Execute(Unit.Default), canGoBack);

Seems to be a workaround.


[FR] add additional payload

Allow to define an additional payload per holiday or special day which should be send if the day is reached.

implemented in 1.0.1


"#error" compile error

Describe the bug
A clear and concise description of what the bug is.
Your two advanced examples have a statement "#error ..."  (see line 52) in a "#ifdef nest, that does not compile.  I can't seem to work around this.    Please explain?
To Reproduce
Steps to reproduce the behavior:

Please see line 52 of the advanced example for AVR

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Arduino Information:

OS: [e.g. Windows, MacOSX, Linux]
IDE [e.g. Arduino IDE, Eclipse, VSCode]
IDE Version [e.g. 1.8.6]
Board [e.g ESP32]

Additional context
Add any other context about the problem here.

The board you are compiling is considered by the library to have low memory. Which board that is, I don't know because you didn't fill out the issue report correctly. When compiling for a "low memory" board, the library automatically goes into minimum mode, which the advanced example for AVR is not compatible with. If you want to use the library in non-minimum mode then you'll need to edit the file src/SerialDebug.h and comment out line 64:
https://github.com/JoaoLopesF/SerialDebug/blob/master/src/SerialDebug.h#L60-L66

Thanks for the explanation and work around, it helps me get acquainted with
the rich features of your debugger.
For what it's worth my board is the Arduino Uno. I did try the  "Other "
example file and it gave a similar compile error.
Thanks very much .
On Sun, Oct 28, 2018, 4:38 AM per1234<EMAIL_ADDRESS>wrote:

The board you are compiling is considered by the library to have low
memory. Which board that is, I don't know because you didn't fill out the
issue report correctly. When compiling for a "low memory" board, the
library automatically goes into minimum mode, which the advanced example
for AVR is not compatible with. If you want to use the library in
non-minimum mode then you'll need to edit the file src/SerialDebug.h and
comment out line 64:
https://github.com/JoaoLopesF/SerialDebug/blob/master/src/SerialDebug.h#L60-L66
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JoaoLopesF/SerialDebug/issues/4#issuecomment-433686701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AltOuBbSOOgZknwC9ngXmUsNWRX7n8Elks5upW0QgaJpZM4X9too
.

Hi, @BCChad and @per1234
@per1234, is correct your response, congrats.
@BCChad, please not use "Others" for Arduino Uno,
due this not use F() to reduce memory.
I will put more info in this #error.
I will close this issue.
thanks a lot.


[(release_3_7_SSE)] cache timezone since timezone.gettimezone is stat…

…ic synchronized and performs poorly

https://support.systematic.com/browse/CURA-40203


Clean up raw sub config types; add note type APIs

Fixes #39. Reworks the types from subConfig.ts into a new set of types for sub config structures and adds a new class, SubConfig, which is to the toolbox wiki page as Usernotes is to the usernotes wiki page. Adds methods for looking up user note types and adds examples of how to apply this to display type info for a given usernote.

Couple issues will have to be made when this gets merged

I didn't write tests for any of this because I'm a bad developer
getAllNoteTypes needs to somehow handle removalReasons.getFrom pointing to reasons from a different subreddit probably. this will require the toolboxclient to be passed to the SubredditConfig constructor so we can fetch config for that second subreddit to look up its notes and that will suck

we ball


i18n(ko-KR): update configuration-reference.mdx

Description (required)

update configuration-reference.mdx
#8766

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ko
reference/configuration-reference.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Feature request: prop to pass context to DndProvider

We need to pass context={window} to the DndProvider that lives in provider.tsx - otherwise we get the error:

Cannot have two HTML5 backends at the same time.

Would it be possible to add an optional prop to TreeApi like dndContext and pass that along?
I can provide a PR if that helps

I think others have been able to get around this by passing a different element to the existing tree prop: dndRootElement?: globalThis.Node | null;

See https://github.com/brimdata/react-arborist/issues/17 and https://github.com/brimdata/react-arborist/pull/33 if they are any help.

@jameskerr we need external dnd context to drag react-arborist tree item to external drop target. currently there is no way to implement this feature in a clean way, I have to use a additional useDrag hook and get a weird result:

If I modify react-arborist source code with external context support, everything works fine.

Let's do it. What modifications did you make? Please submit a PR.

@FindDefinition  How you can change the icon when dragging and dropping? I want my cursor ' grab' and grabing.
Can you support me? Thanks.

This was closed in the latest release. You can now provide the dndManager prop to the Tree component.


DBZ-2324 Fix test failure - TablesWithoutPrimaryKeyIT#shouldProcessFromStreaming

https://issues.redhat.com/browse/DBZ-2324
I went ahead in this PR and created a utility method in TestHelper to allow us to validate the existence of the CDC records prior to allowing the test to proceed and validate the expected connector observations as I think this is going to become a more prominent problem in our SQL Server tests are we uncover more timing-related issues.  If there are better ways to structure that check, I'm welcome to any suggestions.

@gunnarmorling I made the suggested changes, let me know if those are sufficient.

Thx!


docreq: add medium field

add medium field to JSON schema, mappings
and JSON loaders for Document Requests

closes #633

LGTM! 👏


Gallery should validate packages same as Client(?)

It looks like the client is doing some validations that the Gallery does not do when uploading the package. This causes issue when looking up 'Installed' package in VS2015 Nuget Package Management for solution. I am unsure if this is the desired behavior and its a bug on Nuget.Client, and the Nuget.Client should ignore these elements instead.
Steps:

I uploaded a package with following metadata to DEV

<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
    <metadata>
        <id>DeltaX.RandomTest1</id>
        <version>2.0.0</version>
        <authors>shishirh</authors>
        <requireLicenseAcceptance>false</requireLicenseAcceptance>
        <description>Creating a random test package</description>
    </metadata>
</package>

Install the above Package after indexing from VS 2015 Nuget Package manager to my solution.

Go to Installed tab for the Nuget Package Manager it shows 'Error occurred'.

The errors in output:
LicenseUrl cannot be empty.
IconUrl cannot be empty.
ProjectUrl cannot be empty.

Its possible that this could be the issue on VS2015 extension for Nuget package management.

duplicate of https://github.com/NuGet/NuGetGallery/issues/3142

jk that one is related to package id only, but I think there's another issue somewhere about this specifically

@emgarten @rrelyea

Those fields are not required, however the client does fail if they exist but do not contain a valid url. Did DEV modify the nuspec? I don't think the client would fail on the nuspec displayed in the issue here.

@shishirx34 can you try installing the package that you uploaded before uploading to see if the upload process modified the nuspec?

@emgarten - I downloaded the uploaded package from the DEV, and it has the same nuspec as the one shown above. You can see it here: https://dev.nugettest.org/api/v2/package/DeltaX.RandomTest1/2.0.0

Seems like a client bug then, this field isn't required. What version of NuGet are you using?

Nuget Package Manager 3.4.4
Package Manager Console Host Version <IP_ADDRESS>1

@emgarten - do you want me to open the bug on client?

@shishirx34 that would be great, thanks!

Closing this for the client bug opened.


[BUG] Moves key to another DB, the source key was removed if the move failed due to the key exists in the destination db

Problem Descriptions
When i have 2 databases,  i create the same key to both databases, the key exists in both dbs. Then if i move the key from the source db to the destination db using "MOVE" command,  the command will fail (return 0 as i expected). This is a correct behaviour  according to the Redis "MOVE" command specification. However, if the operation failed, it should keep the key in the source DB,  the KEYDB open source code actually deleted the key from the source db when the "MOVE" operation failed.
Tried with the latest Redis OSS, and it is actually NOT deleting the key from the source DB if the MOVE command failed. I believe it is a KeyDB OSS bug.
To reproduce
Here are the steps to reproduce from cli command line:
<IP_ADDRESS>:7001> select 0
OK
<IP_ADDRESS>:7001> set key hello
OK
<IP_ADDRESS>:7001> get key
"hello"
<IP_ADDRESS>:7001> select 1
OK
<IP_ADDRESS>:7001[1]> get key
(nil)
<IP_ADDRESS>:7001[1]> set key Hello
OK
<IP_ADDRESS>:7001[1]> get key
"Hello"
<IP_ADDRESS>:7001[1]> select 0
OK
<IP_ADDRESS>:7001> move key 1
(integer) 0
<IP_ADDRESS>:7001> select 0
OK
<IP_ADDRESS>:7001> get key
(nil)
NOTE: as you can see if the MOVE command failed, cli returns "(integer)0", it indicates that the operation failed, the key in the source db should be kept. However,  "select 0; get key" return '(nil)' and indicates the key from the source db was deleted.
Expected behavior
if key is NOT moved, the key should not be deleted from the source db. (Verified in Redis open source, the behaviour is correct, however it doesn't work the same way in keydb).

@JohnSully  add John to the issue here. tx

@JohnSully here is the commit 118ae701f57897dfa7a47755d1983705ac94755a , please review it. Thanks.

Closing as this was fixed with #498