Synthesis failed for GroupsMigration

Hello! Autosynth couldn't regenerate GroupsMigration. :broken_heart:
Here's the output from running synth.py:
2020-06-06 06:02:18,861 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-06 06:02:19,696 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-06 06:02:19,699 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-06 06:02:19,702 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-06 06:02:19,706 autosynth [DEBUG] > Running: git config push.default simple
2020-06-06 06:02:19,709 autosynth [DEBUG] > Running: git branch -f autosynth-groupsmigration
2020-06-06 06:02:19,712 autosynth [DEBUG] > Running: git checkout autosynth-groupsmigration
Switched to branch 'autosynth-groupsmigration'
2020-06-06 06:02:19,942 autosynth [INFO] > Running synthtool
2020-06-06 06:02:19,942 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/groups_migration/synth.metadata', 'synth.py', '--']
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-06 06:02:19,944 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/groups_migration/synth.metadata synth.py -- GroupsMigration
2020-06-06 06:02:20,176 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-groupsmigration
nothing to commit, working tree clean
2020-06-06 06:02:22,088 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpovzk3ugt/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh GroupsMigration
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpovzk3ugt/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh GroupsMigration
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

13:02:55.139 [info]  FETCHING: https://www.googleapis.com/discovery/v1/apis/groupsmigration/v1/rest

13:02:55.270 [info]  FOUND: https://www.googleapis.com/discovery/v1/apis/groupsmigration/v1/rest
Revision check: old=20181126, new=20181126, generating=true
Creating leading directories
Writing Groups to clients/groups_migration/lib/google_api/groups_migration/v1/model/groups.ex.
Writing Archive to clients/groups_migration/lib/google_api/groups_migration/v1/api/archive.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:02:55.626 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-06 06:02:58,728 synthtool [DEBUG] > Wrote metadata to clients/groups_migration/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/groups_migration/synth.metadata.
2020-06-06 06:02:58,759 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating GroupsMigration. :sob:
Here's the output from running synth.py:
2020-06-07 05:55:57,296 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-07 05:55:58,085 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-07 05:55:58,088 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-07 05:55:58,091 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-07 05:55:58,093 autosynth [DEBUG] > Running: git config push.default simple
2020-06-07 05:55:58,096 autosynth [DEBUG] > Running: git branch -f autosynth-groupsmigration
2020-06-07 05:55:58,099 autosynth [DEBUG] > Running: git checkout autosynth-groupsmigration
Switched to branch 'autosynth-groupsmigration'
2020-06-07 05:55:58,486 autosynth [INFO] > Running synthtool
2020-06-07 05:55:58,486 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/groups_migration/synth.metadata', 'synth.py', '--']
2020-06-07 05:55:58,488 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/groups_migration/synth.metadata synth.py -- GroupsMigration
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-07 05:55:58,699 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-groupsmigration
nothing to commit, working tree clean
2020-06-07 05:56:00,599 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmp0sl7rn58/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh GroupsMigration
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmp0sl7rn58/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh GroupsMigration
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:56:30.936 [info]  FETCHING: https://www.googleapis.com/discovery/v1/apis/groupsmigration/v1/rest

12:56:31.059 [info]  FOUND: https://www.googleapis.com/discovery/v1/apis/groupsmigration/v1/rest
Revision check: old=20181126, new=20181126, generating=true
Creating leading directories
Writing Groups to clients/groups_migration/lib/google_api/groups_migration/v1/model/groups.ex.
Writing Archive to clients/groups_migration/lib/google_api/groups_migration/v1/api/archive.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:56:31.394 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-07 05:56:34,515 synthtool [DEBUG] > Wrote metadata to clients/groups_migration/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/groups_migration/synth.metadata.
2020-06-07 05:56:34,540 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating GroupsMigration. :sob:
Here's the output from running synth.py:
2020-06-08 05:56:27,649 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-08 05:56:28,433 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-08 05:56:28,436 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-08 05:56:28,439 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-08 05:56:28,442 autosynth [DEBUG] > Running: git config push.default simple
2020-06-08 05:56:28,445 autosynth [DEBUG] > Running: git branch -f autosynth-groupsmigration
2020-06-08 05:56:28,449 autosynth [DEBUG] > Running: git checkout autosynth-groupsmigration
Switched to branch 'autosynth-groupsmigration'
2020-06-08 05:56:28,684 autosynth [INFO] > Running synthtool
2020-06-08 05:56:28,684 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/groups_migration/synth.metadata', 'synth.py', '--']
2020-06-08 05:56:28,687 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/groups_migration/synth.metadata synth.py -- GroupsMigration
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-08 05:56:28,896 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-groupsmigration
nothing to commit, working tree clean
2020-06-08 05:56:30,367 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpcz2ucdt8/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh GroupsMigration
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpcz2ucdt8/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh GroupsMigration
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:57:02.474 [info]  FETCHING: https://www.googleapis.com/discovery/v1/apis/groupsmigration/v1/rest

12:57:02.608 [info]  FOUND: https://www.googleapis.com/discovery/v1/apis/groupsmigration/v1/rest
Revision check: old=20181126, new=20181126, generating=true
Creating leading directories
Writing Groups to clients/groups_migration/lib/google_api/groups_migration/v1/model/groups.ex.
Writing Archive to clients/groups_migration/lib/google_api/groups_migration/v1/api/archive.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:57:02.962 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-08 05:57:05,545 synthtool [DEBUG] > Wrote metadata to clients/groups_migration/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/groups_migration/synth.metadata.
2020-06-08 05:57:05,572 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


#Issue-315, Fixed: Textarea toolbar not sending through value on form submission.

The issue occurs because when the toolbar attribute is set to true, the component renders a <div> instead of a <textarea>. Since the <div> element doesn't support a "name" attribute (which is required for form submissions), so the form data is not being sent as expected.
I resolve this, by using a hidden input field that carries the name attribute and holds the content of the Quill editor by some JS modifications.
Thank you.

@mkocansey, I have changed the input to a textarea and made another commit.
Thank you.


Updated LICENSE.txt file - removed Awesome fonts

removed Font Awesome from LICENSE.txt file as it is not used anymore

@epwinchell please review if this is ok to remove.  Thx, Dan

@dclarizio Looks good.


Run backing-image-manager pod as privileged

longhorn/longhorn#6108
See https://github.com/longhorn/longhorn/issues/6108#issuecomment-1593527996 for analysis. Even though it doesn't need privileged for any other reason (currently), backing-image-manager still needs privileged for SELinux.
Need https://github.com/longhorn/longhorn-tests/pull/1426 to test on Jenkins.
This is currently not working as expected (tests are FAILED, instead of ERROR). I will have to return to it tomorrow.

This is currently not working as expected (tests are FAILED, instead of ERROR). I will have to return to it tomorrow.

I missed that backing-image-ds pods also attempt to access the host's disk configuration. While my original change stopped backing-image-manager pods from crash looping, I had to add privileged to backing-image-ds pods as well to actually get tests passing. Running a full suite of tests now, but given that the first backing image tests are already passed, I think these are the changes we need.
eweber@laptop:~/longhorn-tests/test_framework/terraform/aws/rockylinux-k3s-selinux-on> k logs longhorn-test -f
Defaulted container "longhorn-test" out of: longhorn-test, longhorn-test-report
============================= test session starts ==============================
platform linux -- Python 3.9.16, pytest-5.3.1, py-1.11.0, pluggy-0.13.1 -- /usr/bin/python3.9
cachedir: .pytest_cache
rootdir: /integration, inifile: pytest.ini
plugins: order-1.0.1, repeat-0.9.1
collecting ... collected 414 items

test_backing_image.py::test_backing_image_basic_operation PASSED
test_backing_image.py::test_backing_image_content PASSED

@mergifyio backport v1.5.x

@mergify backport v1.4.x v1.3.x


Escape slash and double quotes characters for password in setup.sh

Passwords may contain special characters that may break bash sed command (slashes) or json format (double quotes). This allow those kinds of password to be used safely.
PS. My bash skill is not strong so any advice is appreciated! :)

Thanks for the PR>


Lec4 array ex

I have fixed the semicolon issue in an upcoming commit. But its not letting me to merge the code.

there are still further changes needed. Your pull request include changes made to copy-and-rename folder content, which you are not supposed to do, please remove those changes


Executing user defined setup scripts with wrong user in Oracle Database 18c (18.4.0) Express Edition (XE)

I successfully built a Docker image containing Oracle Database 18c (18.4.0) Express Edition (XE). In addition I have my custom setup script with sql extension, say 01_users.sql with the following statement
CREATE USER INVENTORY_ITEMS IDENTIFIED BY galaxy;

I mounted the local directory containing my custom script according to the documentation from Running scripts after setup and on startup. The script is successfully processed after the database initialization but I got the following error.

ORA-65096: invalid common user or role name

This error is expected since custom scripts with sql extension are being executed with wrong user. In file  runOracle.sh I observed this sqlplus connection to the database.

$ORACLE_HOME/bin/sqlplus / as sysdba

If my understanding is correct this connection is used to log into the CDB root container (CDB$ROOT) database. Instead my scripts should be executed against plugabble database. Indeed when I modify the connection command in runOracle.sh everything works as expected.

Modifying the file runOracle.sh seems the wrong approach for me since this file is mainteined by Oracle team but in the current circumstances I don't see any other options.

Is there any installation/configuration step I missed when running setup scripts?
Should I alter the session in the beginning of my custom script?

I appreciate your help and support.

I added the session control statement at the beginning of each of my custom scripts.
ALTER SESSION SET CONTAINER = XEPDB1;

It was necessary to add this statement in each custom script because the logic in runOracle.sh is performing a new connection for each custom script. With this workaround all operations will be performed inside the only PDB (pluggable database) that XE supports.
I would still like to hear your opinion about this approach.

Hi @rprodan,
You are correct, the SQL scripts are automatically connected to the container database (CDB). Oracle's Multitenant architecture allows for many pluggable databases (PDBs) to be created and users are welcome to create and name their pluggable databases to their liking and for their use cases. As such, the runOracle.sh script cannot make a guess as to which database the script(s) should be run in. A user may want for a SQL script to set a parameter at the container database level, or perhaps create a common user or perhaps even create a brand new pluggable database. Or a user may want to run a SQL script in the pluggable database or other pluggable databases that have been created by another script beforehand.
By default, the scripts connect as SYS to the Oracle instance (the top-level CDB), because from there the user has full control of what to do next and it also does not require a password to be provided.
The ALTER SESSION command is a valid approach.
Another one would be to issue a new connect inside the SQL script for SQL*Plus to establish a new connection, e.g.
conn sys/<password>@//localhost/XEPDB1

or
conn <my user>/<my password>@//localhost/<my PDB name>

Another approach could be to leverage the shell script functionality instead and have that shell script invoke SQL*Plus and run the SQL scripts (or whatever other CLI command).
That way you will not have to touch each individual SQL script file but can establish the connection once and call the scripts directly afterwards (and also in the order that you like).
I hope this helps!

Hello @gvenzl,
first of all, thank you for your answer.
I will definitely consider your recommendations and thus eliminate unnecessary repeatable code segments.
As for me this issue can be closed.


v10 version of action quits with success while not doing anything

Hello!
I'm upgrading my workflow from v3 to v10 and running into a bit of an issue - the action runs and quits with success while not having done anything. What could be wrong?
Here is the workflow run with debugging enabled: https://github.com/Mudlet/Mudlet/actions/runs/4744395516/jobs/8425405550#step:21:1

@vadi2  thanks for reporting this! This is clearly a bug because the action should have triggered an error since it has not done anything as no input has been provided.
The reason is that from v10 the action requires usage of the CMakePresets.json file, you may read the quickstart to see an example.

The documentation made it seem like CMakePresets.json was optional. No way without one?

@vadi2 yes, run-cmake@v10 requires at least one preset to be specified and the usage of CMakePresets.json is mandatory. In your case the action should have triggered an error indeed.

@vadi2 updated the docs and added an error when CMakePresets.json is not used.


feat: Track screen reader status and preferred theme of users

The type of this PR is: Enhancement

This PR resolves []
Description

introduces tracking for users that have screen readers enabled on their devices.
replaces tracking theme preferences for iOS only to both iOS and android

iOS
Android

ios
android

PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[ ] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

track screen reader status and theme status - gkartalis

This PR contains the following changes:

Dev changes (track screen reader status and theme status - gkartalis)

  Generated by :no_entry_sign: dangerJS against 98f0533fb84e9db92765485552024a5b231f3536

I think its best if we add a custom thing in cohesion. Something that allows us to send like
{
  action: "custom-track",
  key: "screen-reader",
  value: "whatever the value is",
}

then we (as devs or teams) we can track things that are not needed in cohesion, and we can freely and easily add or remove these when we want, without needed extra changes in cohesion or bothering the data team.


Failing to Build .NET 7.0 project.

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When deploying a .NET 7.0 app to railway, receiving the following error:
"/nix/store/832ihvqk3vxgqqs5hvcyvg6bxqybky14-dotnet-sdk-6.0.403/sdk/6.0.403/Sdks/Microsoft.NET.Sdk/targets/Microsoft.NET.TargetFrameworkInference.targets(144,5): error NETSDK1045: The current .NET SDK does not support targeting .NET 7.0.  Either target .NET 6.0 or lower, or use a version of the .NET SDK that supports .NET 7.0. [/app/Project-90-API.csproj]"
Can be resolved by adding the .NET 7 SDK to the nix store.
To reproduce

Create a template .NET Core 7.0 Web API.
Upload to github.
Deploy to Railway and wait for build.

Expected behavior
Should build without error. Can be resolved by adding the .NET 7 SDK to the nix store.
Environment
Nixpack v 1.4.0 via Railway
.NET core 7.0

can you send us a link to your project

https://github.com/joshberc/Project-90-API It's a template .NET 7.0 Web API.

can you try set version in global.json?

Updated. Nix output this error upon build: "Install the [7.0.200] .NET SDK or update [/app/global.json] to match an installed SDK."

The deploy process is parsing both the global.json and project settings correctly. This should be resolved be adding the 7.0.200 SDK to /nix/store. @Milo123459 is it possible to add?

Hi there!
I don't know if this might help, but I got 7.0 working on my Ubuntu 22.04 machine when I had issues installing - and switching to - dotnet 7.0 from 6.0.
Here's a shell script I use to get the correct Ubuntu SDK and Runtime.  Perhaps it will help y'all solve this:

# This contact's MS's version of dotnet for ubuntu
# Explanation is here: https://learn.microsoft.com/en-us/dotnet/core/install/linux-ubuntu#2204-microsoft-package-feed

wget https://packages.microsoft.com/config/ubuntu/22.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb

sudo apt-get update
sudo apt-get install -y dotnet-sdk-7.0
sudo apt-get install -y aspnetcore-runtime-7.0

## these are to be removed after installation
sudo apt autoremove aspnetcore-targeting-pack-6.0 dotnet-apphost-pack-6.0 dotnet-targeting-pack-6.0 gir1.2-snapd-1 libllvm13 libllvm13:i386
https://github.com/harriris/external-ballistics-js.git
echo "here'https://github.com/harriris/external-ballistics-js.gits the runtimes & sdks (if any):"

dotnet --list-runtimes
dotnet --list-sdks


Add a missing arg --generate-name to helm install.

The arg --generate-name is required by the helm install command.
Thus users encounter the following error when they try the snippet.
Error: must either provide a name or specify --generate-name

@mazgi : Thanks for your contribution! The author(s) have been notified to review your proposed change. @caya

@mscatyao Thank you for reviewing!
Let me know if I can help you in any way.

@mscatyao I believe this one line pull-request is helpful for all users!
Do you have a few seconds to push the merge button?

@Court72 Could you triage this PR again?
We've been waiting for the review for about one month.

@mscatyao
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
Thanks!

@Court72  thank you for your mention ✨
However, it seems @mscatyao has no activity this month.
https://github.com/mscatyao?tab=overview&from=2022-04-01&to=2022-04-30

@kumudd
Would you be able to review the proposed changes and #sign-off if you approve them?
Can you also update the article's author if mscatyao is no longer the current author?
Thanks!

@KumudD cc @Court72 could you review this?

@jdmartinez36 - Would you be able to review this PR for ingress-controller-install-new.md?

@KumudD @jdmartinez36 @mscatyao cc: @Court72 @ShannonLeavitt could you review this small PR?

@KumudD @jdmartinez36 @mscatyao cc: @Court72 @ShannonLeavitt could you review this PR?

requested approval by email

@KumudD @mscatyao cc: @Court72 @ShannonLeavitt could you review this PR?

I'll open this PR again!
This PR was closed when I created the new fork for this repository; it was my mistake!

@Court72 Thank you so much for your triage.
I've chatted via Teams internally; I would be happy if you could see it.

@greg-lindsay
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

@greg-lindsay cc: @Court72 Look the same as the https://github.com/MicrosoftDocs/azure-docs/pull/90348#issuecomment-1371652392
I don't have permission to merge this repository.
Should I take any action?
https://github.com/MicrosoftDocs/azure-docs/pull/90348#issuecomment-1371652392


Error downloading from OpenRec

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2023.03.04 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
I get an error downloading a video from Openrec (membership video). I am a member to the site, the previous streams (4 so far) I have downloaded without issues. If I retry those now, I get the same error as with this new video. Thanks for your help!
Kind regards,
Marloes
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['--cookies-from-browser', 'chrome', '-vU', 'https://www.openrec.tv/live/wez9mp0158l']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[392389b7d] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2023-02-16-git-aeceefa622-full_build-www.gyan.dev (setts), ffprobe 2023-02-16-git-aeceefa622-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[Cookies] Extracting cookies from chrome
[debug] Extracting cookies from: "C:\Users\marlo\AppData\Local\Google\Chrome\User Data\Default\Network\Cookies"
[debug] Found local state file at "C:\Users\marlo\AppData\Local\Google\Chrome\User Data\Local State"
[Cookies] Extracted 3212 cookies from chrome
[debug] cookie version breakdown: {'v10': 3221, 'other': 0, 'unencrypted': 0}
[debug] Proxy map: {}
[debug] Loaded 1786 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 5590c57bd0433ed239a2deaaf92e2ad6f37fe50f53664c821575cafe106a9421
yt-dlp is up to date<EMAIL_ADDRESS>[openrec] Extracting URL: https://www.openrec.tv/live/wez9mp0158l
[openrec] wez9mp0158l: Downloading webpage
[openrec] wez9mp0158l: Downloading JSON metadata
[openrec] wez9mp0158l: Downloading m3u8 information
ERROR: [openrec] wez9mp0158l: Failed to download m3u8 information: HTTP Error 401: Unauthorized (caused by <HTTPError 401: 'Unauthorized'>); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "yt_dlp\extractor\common.py", line 694, in extract
  File "yt_dlp\extractor\openrec.py", line 81, in _real_extract
  File "yt_dlp\extractor\openrec.py", line 50, in _extract_movie
  File "yt_dlp\extractor\openrec.py", line 23, in _expand_media
  File "yt_dlp\extractor\common.py", line 1919, in _extract_m3u8_formats
  File "yt_dlp\extractor\common.py", line 1941, in _extract_m3u8_formats_and_subtitles
  File "yt_dlp\extractor\common.py", line 882, in _download_webpage_handle
  File "yt_dlp\extractor\common.py", line 839, in _request_webpage

  File "yt_dlp\extractor\common.py", line 821, in _request_webpage
  File "yt_dlp\YoutubeDL.py", line 3742, in urlopen
  File "urllib\request.py", line 531, in open
  File "urllib\request.py", line 640, in http_response
  File "urllib\request.py", line 569, in error
  File "urllib\request.py", line 502, in _call_chain
  File "urllib\request.py", line 649, in http_error_default
urllib.error.HTTPError: HTTP Error 401: Unauthorized

Have you tried opening the site in your browser to refresh your login session?

Hi,
Yes, I can watch the video just fine in my browser. I even rebooted :)
This channel now has 5 video's (1 per month). Before I knew yt-dlp could
also download from OpenRec, I used another tool on Github, openrec. I don't
think this one is still supported but I tried using that tool just now, and
from them I get a 'no public playlist found' error. Maybe OpenRec has
changed something?
[image: image.png]
On Sat, 29 Apr 2023 at 15:30, bashonly @.***> wrote:

Have you tried opening the site in your browser to refresh your login
session?
—
Reply to this email directly, view it on GitHub
https://github.com/yt-dlp/yt-dlp/issues/6946#issuecomment-1528789901,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKWUJ3O7JOVNWEAKWHAJGZTXDUJYFANCNFSM6AAAAAAXQHFEZ4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Have you tried exporting cookies again after refreshing cookies on browser?
P.S. Please try to use GitHub website for replies. We can't see your attachments

I'm sorry, I will reply using the website! I have tried both the --cookies-from-browser and the --cookies command with a freshly generated cookies file using the get cookies.txt locally extension.
The screenshot I wanted to attach in the previous reply:

Well, do what it says and change your format selector!

Hi, the command won't work at all, but it's another tool, it was just to inform that other tools than yt-dlp seem to have troubles downloading from OpenRec too. The complete verbose log for the yt-dlp download command is in the first post.
Openrec has 2 'types' of links: 'live' (https://www.openrec.tv/live/wez9mp0158l) and ' movie' (https://www.openrec.tv/movie/n9ze7nqqxr4). Both links from the same channel. I can download the Movie link, just not the Live links. Last month is was the other way around :) The fixed the Movie link, but now the Live link is broken?

The complete verbose log for the yt-dlp download command is in the first post.

Pls provide new log after cookies were refreshed. I can see from screenshot that error is now different

Hi,
First I tried the 'live' video, the type that raises the error. After that I tried the 'movie' video, from the same channel. That works just fine:
[debug] Command-line config: ['--cookies-from-browser', 'chrome', '-vU', 'https://www.openrec.tv/live/wez9mp0158l']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[392389b7d] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2023-02-16-git-aeceefa622-full_build-www.gyan.dev (setts), ffprobe 2023-02-16-git-aeceefa622-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[Cookies] Extracting cookies from chrome
[debug] Extracting cookies from: "C:\Users\marlo\AppData\Local\Google\Chrome\User Data\Default\Network\Cookies"
[debug] Found local state file at "C:\Users\marlo\AppData\Local\Google\Chrome\User Data\Local State"
[Cookies] Extracted 3270 cookies from chrome
[debug] cookie version breakdown: {'v10': 3280, 'other': 0, 'unencrypted': 0}
[debug] Proxy map: {}
[debug] Loaded 1786 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 5590c57bd0433ed239a2deaaf92e2ad6f37fe50f53664c821575cafe106a9421
yt-dlp is up to date<EMAIL_ADDRESS>[openrec] Extracting URL: https://www.openrec.tv/live/wez9mp0158l
[openrec] wez9mp0158l: Downloading webpage
[openrec] wez9mp0158l: Downloading JSON metadata
[openrec] wez9mp0158l: Downloading m3u8 information
ERROR: [openrec] wez9mp0158l: Failed to download m3u8 information: HTTP Error 401: Unauthorized (caused by <HTTPError 401: 'Unauthorized'>); please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
File "yt_dlp\extractor\common.py", line 694, in extract
File "yt_dlp\extractor\openrec.py", line 81, in _real_extract
File "yt_dlp\extractor\openrec.py", line 50, in _extract_movie
File "yt_dlp\extractor\openrec.py", line 23, in _expand_media
File "yt_dlp\extractor\common.py", line 1919, in _extract_m3u8_formats
File "yt_dlp\extractor\common.py", line 1941, in _extract_m3u8_formats_and_subtitles
File "yt_dlp\extractor\common.py", line 882, in _download_webpage_handle
File "yt_dlp\extractor\common.py", line 839, in _request_webpage
File "yt_dlp\extractor\common.py", line 821, in _request_webpage
File "yt_dlp\YoutubeDL.py", line 3742, in urlopen
File "urllib\request.py", line 531, in open
File "urllib\request.py", line 640, in http_response
File "urllib\request.py", line 569, in error
File "urllib\request.py", line 502, in _call_chain
File "urllib\request.py", line 649, in http_error_default
urllib.error.HTTPError: HTTP Error 401: Unauthorized
C:\Users\marlo>yt-dlp --cookies-from-browser chrome -vU https://www.openrec.tv/movie/n9ze7nqqxr4
[debug] Command-line config: ['--cookies-from-browser', 'chrome', '-vU', 'https://www.openrec.tv/movie/n9ze7nqqxr4']
[debug] Encodings: locale cp1252, fs utf-8, pref cp1252, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>[392389b7d] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg 2023-02-16-git-aeceefa622-full_build-www.gyan.dev (setts), ffprobe 2023-02-16-git-aeceefa622-full_build-www.gyan.dev
[debug] Optional libraries: Cryptodome-3.17, brotli-1.0.9, certifi-2022.12.07, mutagen-1.46.0, sqlite3-2.6.0, websockets-10.4
[Cookies] Extracting cookies from chrome
[debug] Extracting cookies from: "C:\Users\marlo\AppData\Local\Google\Chrome\User Data\Default\Network\Cookies"
[debug] Found local state file at "C:\Users\marlo\AppData\Local\Google\Chrome\User Data\Local State"
[Cookies] Extracted 3270 cookies from chrome
[debug] cookie version breakdown: {'v10': 3280, 'other': 0, 'unencrypted': 0}
[debug] Proxy map: {}
[debug] Loaded 1786 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Available version<EMAIL_ADDRESS>Current version<EMAIL_ADDRESS>Current Build Hash: 5590c57bd0433ed239a2deaaf92e2ad6f37fe50f53664c821575cafe106a9421
yt-dlp is up to date<EMAIL_ADDRESS>[openrec:movie] Extracting URL: https://www.openrec.tv/movie/n9ze7nqqxr4
[openrec:movie] n9ze7nqqxr4: Downloading webpage
[openrec:movie] n9ze7nqqxr4: Downloading JSON metadata
[openrec:movie] n9ze7nqqxr4: Downloading m3u8 information
[openrec:movie] n9ze7nqqxr4: Downloading m3u8 information
[debug] Formats sorted by: hasvid, ie_pref, lang, quality, res, fps, hdr:12(7), vcodec:vp9.2(10), channels, acodec, filesize, fs_approx, tbr, vbr, abr, asr, proto, vext, aext, hasaud, source, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] n9ze7nqqxr4: Downloading 1 format(s): url_audio-1660
[debug] Invoking hlsnative downloader on "https://dco4urblvsasc.cloudfront.net/28682/2868173_vBngtZpZ/game/96kbps.m3u8"
[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 133
[download] Destination: 廣瀬大介のゲーム部屋#03[未公開特別編] [n9ze7nqqxr4].mp4
[debug] File locking is not supported. Proceeding without locking
[download]   8.3% of ~ 224.21MiB at    3.40MiB/s ETA 00:57 (frag 11/133)

Hello,
I'm sorry but I'm not familiar with the way things work on Github, so if I'm being rude or impatient, I apologize! But how do I proceed from here? After posting an issue, you just wait untill someone picks it up (which is of course fine, I understand all of you are just volunteering!), or do I have to make a request somewhere? I've tried several things and my conclusion is that openrec.tv/MOVIE/xxx now works (which didn't in the past) and openrec.tv/LIVE/xxx does not work anymore (it used to). On this channel I've downloaded the LIVE links in the past, got the new openrec.py file a while ago (when I tried to download a MOVIE link for the first time on this channel) and since then I can download the MOVIE link, but now the LIVE links don't work anymore (not the new LIVE links, nor the older LIVE links I've tried to download again).
Please help? Thanks!

@marlouz Are you willing to share your account details if a dev wants to work on this?
This is not to say that I am able to work on it. But if we can label this issue as "can share account" it would be more likely to get picked up by somebody.

@bashonly Hmm, that is a good question, I hadn't thought about that. I'm going to have to think about that one. Thanks for responding!

Simply adding --referer 'https://www.openrec.tv' to the command makes it work for me.


Kenkoooo/try tide

Codecov Report

Merging #348 into master will decrease coverage by 35.1%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master   #348       +/-   ##
=========================================
- Coverage    38.3%   3.2%   -35.11%
=========================================
  Files          96     52       -44
  Lines        2506   1093     -1413
  Branches      182    182
=========================================
- Hits          960     35      -925
+ Misses       1545   1057      -488
  Partials        1      1

Impacted Files
Coverage Δ

...coder-problems-backend/tests/test_simple_client.rs

atcoder-problems-backend/src/sql/models.rs

...der-problems-backend/tests/test_rated_point_sum.rs

...blems-backend/src/crawler/whole_contest_crawler.rs

atcoder-problems-backend/src/s3.rs

...er-problems-backend/src/bin/crawl_whole_contest.rs

atcoder-problems-backend/src/sql/language_count.rs

atcoder-problems-backend/src/utils.rs

atcoder-problems-backend/src/bin/dump_json.rs

atcoder-problems-backend/src/sql/problem_info.rs

... and 26 more

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 71b8c97...97a7249. Read the comment docs.


Oops somethin happened! You're changes weren't saved.

I get that error almost everytime I create or edit something within a project doesn't matter if it's a User Story, a Task or an EPIC.
Interestingly all the changes I execute get saved even though I get that error notification.
Any idea why this happens?

error.log is empty

docker-compose:

version: "3.2"

services:
  database:
    image: postgres:alpine
    container_name: taiga-db
    stop_signal: SIGINT
    volumes:
      - ./data/db:/var/lib/postgresql/data
    expose:
      - "5432"
  server:
    image: devinsolutions/taiga:latest
    container_name: taiga
    depends_on:
      - database
    command:
      - run-server
    healthcheck:
      test: wget -q -t 1 --spider http://localhost:8080/api/v1/
    expose:
      - "8080"
    stop_signal: SIGHUP
    volumes:
      - ./data/media:/srv/taiga-back/media
      - ./conf/settings.py:/etc/opt/taiga-back/settings.py:ro
    labels:
      - "traefik.enable=true"
      - "traefik.port=8080"
      - "traefik.docker.network=reverse-proxy"
      # Entrypoint and TLS
      - "traefik.http.routers.taiga.entrypoints=https"
      - "traefik.http.routers.taiga.rule=Host(`taiga.domain.org`)"
      - "traefik.http.routers.taiga.tls.options=myTLSOptions@file"
      - "traefik.http.routers.taiga.tls.certresolver=le"
      # Middlewares:
      - "traefik.http.routers.taiga.middlewares=taiga@docker"
      # Middleware taiga adds additional headers:
      - "traefik.http.middlewares.taiga.headers.customFrameOptionsValue=SAMEORIGIN"
      - "traefik.http.middlewares.taiga.headers.framedeny=true"
      - "traefik.http.middlewares.taiga.headers.sslredirect=true"
      - "traefik.http.middlewares.taiga.headers.stsIncludeSubdomains=true"
      - "traefik.http.middlewares.taiga.headers.stsPreload=true"
      - "traefik.http.middlewares.taiga.headers.stsSeconds=15552000"

networks:
    default:
       external:
         name: reverse-proxy

settingy.py:

SECRET_KEY = '<secret>'

ALLOWED_HOSTS = [
    '<IP_ADDRESS>',
    'localhost',
    'taiga.domain.org',
]

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.postgresql',
        'NAME': '<dbname>',
        'USER': '<dbuser>',
        'PASSWORD': '<dbuserpass>',
        'HOST': 'database',
        'PORT': '5432',
    }
}

EVENTS_PUSH_BACKEND = "taiga.events.backends.rabbitmq.EventsPushBackend"
EVENTS_PUSH_BACKEND_OPTIONS = {"url": "amqp://guest:guest@broker/taiga"}

Hi. What makes you think it's a problem of the image?

It's just a guess as I didn't modify the example docker-compose.yml and settings.py file in this repo that heavy except the added traefik labels.

It looks like the issue is caused by the two bottom lines in settings.py. Remove EVENTS_PUSH_BACKEND and EVENTS_PUSH_BACKEND_OPTIONS and everything should be fine.


fix SMTP typo

SMTP (Simple Mail Transfer Protocol) has been typo'd to SMPT

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

Please unsubscribe me from your mailing
On Wed, Mar 10, 2021 at 5:45 PM KC Cross @.***> wrote:

Merged #4313
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4313 into
public.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/microsoft-365-docs/pull/4313#event-4439723310,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOGLPB4M4ZJN5ANVIT4SJGTTC7SANANCNFSM4YRCEXWA
.


C projects should use CC flags rather than CXX flags

In CMAKE, the *CXX* flags are for C++ only, so C files are not compiled with anything that falls under CXX flags. CC flags should be used for flags that are applicable to both C and C++

I think it should use CMAKE_C_FLAGS* rather than CMAKE_CC_FLAGS*, see https://cmake.org/cmake/help/latest/variable/CMAKE_LANG_FLAGS.html.

Huh, I could have sworn that Cmake used CCFLAGS. Maybe I'm thinking of normal make? Thanks for the tip, will fix

Just waiting on the build then we can get this in 👍

Looking good! 👍


Bump null-label version to support Terraform 0.13

what

Bumped the pinned version of null-label to the version that supports Terraform 0.13

why

Module doesn't work on 0.13 without this change :)

/test all

@Makeshift Thanks for the contribution! Released as 0.26.0.

Out of interest, am I able to run the /test all command to make your lives easier, or are they scoped to Cloudposse team members? @Gowiem

@Makeshift I believe (not totally sure) that others can run them. Give it a shot next time!


feat(messages): allow links leading out of the player

currently any links are blocked by managerBeforeUnload
We should probably create a directive that can be applied to links. Alternatively we my want to add a property to tasks that turns it off for the duration of a single trial.

supported on 0.1


Missing VCRUNTIME140_1.dll

Hi, I have a problem when I launch the version 2.0 executable, it sends me an error. Miss the following dll:
VCRUNTIME140_1.dll
Any suggestions?

Most people probably already have VC++ runtimes installed, but if it's a necessary dependency, maybe it should be included in the readme.
Were you able to fix this by installing 2017/2019 Visual C++ redistributable? Also, were you using Windows 10, or was it an older version like Windows 7?
The more info, the better. Someone might have a similar problem in the future, and details in this thread could help.


Add +/- as prefix to other shortcuts

example
+W - first day of last (w)eek
-H - last day of last mont(h)


Handle mixed-cased filter terms in keyboard shortcut dialog

Fixes #3400
Uses .toLowerCase() on the filter term so it works.

Coverage decreased (-0.006%) to 67.337% when pulling f2dde705efbed1840e48d4b94d977b35148c2ab3 on keyboard-filter-case into 264047dc0c22a51ce728316c4b6cad8d65fccf73 on master.


WIP(*): Improve Forms section of the editor

After changes made, the editor will be as found at https://stunning-malasada-43f4d2.netlify.app/
Closes #4
WIP:

Enable the addition of imports into a namespace
Deletion of namespaces, declarations, and property from form
Addition of properties through form
Codegen support

Goals completed :

Addition of namespaces, declarations through form

https://user-images.githubusercontent.com/76606666/208243336-afd0085a-d6b3-4024-8431-5588d0ddc8c7.mov

Enable access to default, IsOptional,regex part of an attribute through the form itself

https://user-images.githubusercontent.com/76606666/208243299-33eaa753-745a-4e86-b5f9-cad53de15ac2.mov

Automatic changes to imports when the name of a namespace being imported is changed through forms.

https://user-images.githubusercontent.com/76606666/208243409-b18b4b49-f3b1-4f07-8db2-ea96dc45d4c8.mov

Acess to range attribute through forms

https://user-images.githubusercontent.com/76606666/208243519-7f1b6c9e-5493-49a8-b03c-d5feb15ea3fa.mov

Can you add a button/icon to allow a user to close a dialog box without submitting the form, please? Right now, I can't implicitly close it by clicking the background.
Also can you fix the DCO sign-off, please?
https://github.com/accordproject/lab-concerto-editor-web/pull/5/checks?check_run_id=10378671773

If you sign the DCO and I can merge this...
https://github.com/accordproject/lab-concerto-editor-web/pull/5/checks?check_run_id=11467642723

Fixed DCO issues and added close button(Screenshot below) @mttrbrts  @dselman


ogame.get_attacks not working

Calling ogame.get_attacks() results in a TypeError. Doesn't allow filter and ResultSet.

I also ran into this. It is a py2 vs py3 issue, since the filter function returns a filter object rather than a list. To fix it you can search for 'filter' and write list(events = filter(...)) LG

obsolete code


Implementing nested User objects in Chat model without additional models

Amplify CLI Version
12.10.1
Question
Hello everyone,
I've encountered an issue in my project that I'm struggling to resolve. I'm working with two models, Chat and User, and my goal is to enhance the query response for a chat by including the chat owners' details directly within the response, rather than just their IDs.
To elaborate, I'd like to set up the Chat.owners field such that when a Chat object is queried, it returns the owners as fully fleshed-out User objects (nested) instead of merely their IDs. Directly swapping out owners: [ID] with owners: [User] doesn't seem to work as I had hoped.
I'm looking for a workaround that would allow me to achieve this without the necessity of adding another model into the mix.
Below is the current schema setup:
type Chat @model
  @auth(rules: [
    { allow: owner },
    { allow: owner, ownerField: "owners" },
    { allow: private, provider: iam }
  ]) {
    id: ID!
    owners: [ID] # I wish to return User here, but it is not possible to replace ID with User
}

type User @model
  @auth(rules: [
    { allow: owner }
    { allow: private, operations: [read]},
    { allow: owner, ownerField: "id" }
  ]) {
    id: ID!
    firstName: String
    lastName: String
  }

I'm also trying to ensure that I can still define authorization rules effectively while implementing this change.
Any advice, solutions, or pointers towards what I might be missing or could try would be greatly appreciated!
Best regards,
M.

Hey, 👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

Appreciate it! Looking forward to see the repo's reaction! 😄

Hi @maziarzamani, you could define explicit relationships between the Chat and User models and that would allow you to fetch the users who own a chat if you have a @hasMany on Chat or chats that the user owns from User type if you use a @belongsTo.  Refer the docs


Edit the things app/page

It currently has a "url to your thing", except it is not actually a valid url...

I went ahead and just removed it as an app. This is a good thing because now I added a default message that tells the owner how to install an app.


Regression test failure

Recently regression tests have been failing. It seems to happen after a fuzzing run ends with Failed. I've seen in 3 separate orgs now.
Here's an example.
https://travis-ci.org/bookmoons/jaeger/jobs/582957346
running regression...
INFO: Seed: 46614417
INFO: 65536 Extra Counters
Not a directory: seed_dir/empty; exiting
2019/09/10 01:42:01 Waiting for container
2019/09/10 01:42:01 fuzzer exited with 1
The command "./scripts/travis/fuzzit.sh local-regression" exited with 1.

That "not a directory" line is present in all failures, always with the same path.
Not a directory: seed_dir/empty; exiting

Deleting the target and creating a new one with a different name resolves the error. The "not a directory" line disappears and the build succeeds. Recreating with the same name doesn't work, it seems to preserve the settings and whatever state is causing the error.
Status of the last fuzzing job always seems to be Failed. The end of the worker log always has a Killed line.
https://app.fuzzit.dev/orgs/jaeger/targets/deserialize-zipkin/XrYqKhDNLJ7K9jO1bwCK
FUZZER: #29677	NEW    ft: 1096 corp: 76/688b lim: 14 exec/s: 899 rss: 378Mb L: 14/14 MS: 3 ChangeBit-CrossOver-CrossOver-
FUZZER: #29684	NEW    ft: 1099 corp: 77/702b lim: 14 exec/s: 899 rss: 378Mb L: 14/14 MS: 2 ChangeByte-ChangeBinInt-
FUZZER: #29698	NEW    ft: 1102 corp: 78/716b lim: 14 exec/s: 899 rss: 378Mb L: 14/14 MS: 4 EraseBytes-ChangeBinInt-EraseBytes-CrossOver-
FUZZER: #29710	NEW    ft: 1114 corp: 79/730b lim: 14 exec/s: 873 rss: 720Mb L: 14/14 MS: 2 InsertRepeatedBytes-CrossOver-
FUZZER: #29712	REDUCE ft: 1117 corp: 80/744b lim: 14 exec/s: 873 rss: 720Mb L: 14/14 MS: 2 CMP-ChangeBinInt- DE: "\xff\xff\xff\xff"-
Killed

Thinking about where it's happened, seems like it's only been Rust packages.

No, that's wrong. 1 is Rust, 1 is Go.

The error seems to reappear after doing that target recreation. The new job eventually shows status Failed with a Killed line in the log, and the error starts happening in fuzz regression again.

There's another example from cranelift. The fuzz regression phase fails with the same error.
https://dev.azure.com/bookmoons/cranelift/_build/results?buildId=32

I think an update of the CLI is needed to https://github.com/fuzzitdev/fuzzit/releases/tag/v2.4.44

Upgrading the client fixed this everywhere. Thanks a lot @yevgenypats.


V4 Planned Changes

Apologies if these plans are already tracked somewhere, but I wanted to put together a list of the changes I'm hoping to see in the next major version. What do you think?

Upgrade to eslint-utils v3
New Node engine requirement of "node": "12.* || 14.* || >= 16.*" (Node 10 end-of-life 2021-04 and Node 15 end-of-life 2021-06-01)
Switch to pure ES modules? I haven't investigated how/if this would work yet
Update rule options:

Update consistent-output rule option default to always since it's always best practice to assert the output:

As of ESLint 7, the output property is required for test cases that provide an autofix
And even when test cases don't autofix, it's still best practice to assert that there's no autofix with output: null

Add meta.hasSuggestions property to meta-property-ordering rule (https://github.com/not-an-aardvark/eslint-plugin-eslint-plugin/pull/119)

Add new recommended rules:

I would actually add ALL existing rules. I've used all of this plugin's rules successfully in a number of my eslint plugins, and I find them pretty much all useful and agreeable. Only about 1/3 of existing rules are enabled as recommended right now, and I see this as a missed opportunity, since most people only bother to enable the recommended rules. Enabling more rules means more exposure/battle-hardening of the rules and more benefit to users.

I would actually add ALL existing rules. I've used all of this plugin's rules successfully in a number of my eslint plugins, and I find them pretty much all useful and agreeable.

The problem you've got is "pretty much".
The recommended set needs to be unopinionated.
The last thing you want is for someone to disable a rule that's recommended.
Examples of rules that are opinionated: require-meta-type, report-message-format, test-case-property-ordering, test-case-shorthand-strings.
Speaking from experience with @typescript-eslint - you want the recommended set to just be an unopinionated set of rules that catch problems.

there is already a preset so you can extend like:
extends: ["plugin:eslint-plugin/all"]

@bradzacher if the goal is to leave "opinionated" or "stylistic" rules (i.e. about the ordering of properties) out of the recommended config, I'd be fine with that.
Here are the rules I would specifically advocate for being added to the recommended config because they improve rule usability or facilitate eslint plugin development:

Rule
Why it could make sense in the recommended config

consistent-output
asserting output is required by ESLint 7 when there's an autofix, and even when there's no autofix, it's still valuable to assert that there's no autofix

no-deprecated-context-methods
we should help people avoid deprecated APIs

prefer-object-rule
the old rule style is deprecated

prefer-output-null
it's significantly easier to distinguish if a test case has an autofix or not when using output: null

prefer-placeholders
the rule doc explains benefits

prefer-replace-text
improved readability

require-meta-docs-description
it's easier for users to understand rules when they have descriptions

require-meta-docs-url
it's easier for users to understand rules when they provide a link to their documentation

require-meta-has-suggestions
this new property will be required for suggestable rules in ESLint 8

require-meta-schema
enforcing rule schemas reduces the risk of users configuring a rule incorrectly, and even rules that have no options should provide schema: [] so that eslint can validate that no options are passed to them

require-meta-type
this enables users to choose what type of rule they want to run (based on the three types used by eslint core: problem, suggestion, or layout). However, if users commonly use types other than these, then I agree it would make sense to exclude this rule.

agreed with @bradzacher .
eslint has set a very high bar to eslint:recommended (https://github.com/eslint/eslint/issues/14673). I think better to adopt the similar policy in the plugin. I'm 👍 to the following rules:

consistent-output
no-deprecated-context-methods
prefer-object-rule
require-meta-has-suggestions
require-meta-type

Sounds good. Can I ask why you would exclude these ones:

require-meta-docs-url
require-meta-schema

I consider these two especially high impact in that they both improve external-facing rule usability by helping developers understand lint rules (by providing an IDE documentation link) and ensuring developers configure rules correctly.

yes, it is a best practice, and should be enabled in most cases, but there are some exceptions, e.g. internal-rules: https://github.com/eslint/eslint/tree/master/tools/internal-rules

Example: none of the ~400 internal rules at Facebook have a schema defined, because they take no options. Nor do they have a docs url defined, because we have our own infra for dealing with rule docs.

Having no rule options is totally fine. The require-meta-schema rule doc explains that schema: [] should be specified for rules that do not have options in order to enforce that no options are accidentally passed to such rules, and rules that specify schema: [] are allowed by this rule.

Thanks to both of you for bringing up some use cases where a plugin might not want to specify rule URLs. Those are helpful.

I have an update to share regarding the require-meta-schema rule. I have recommended to the ESLint team that schemas should be required for rules with options and they are interested in this idea so I'll be opening an RFC for it targeting ESLint 9.
With this change, rules without options will no longer need to specify schema: [], as that will be the default behavior. That means we can update the require-meta-schema rule to only require the schema property for rules that actually have options (which is the same as how require-meta-fixable only requires the fixable property for rules with fixers).
As a result of this change, we should be able to enable the require-meta-schema rule as recommended in eslint-plugin-eslint-plugin v4.

As eslint v8.0.0 will be released in a few weeks, we can start merging these PRs, and made a prerelease version. thoughts? @bmish

@aladdin-add I believe all PRs for the next release are ready, except for #179 which I can try to get to soon. A prerelease version is a good idea.

Two more notes:

We should release a minor version first with these two non-breaking changes: #178 and #179 (once implemented).
We should also consider including TypeScript support (#176) in this release. TS support will build on top of ESM rule support (#177) and I could give it a try, but #177 needs to be merged first for me to do so.

Open question: I have added a requireSchemaPropertyWhenOptionless option (default true to maintain current behavior) to require-meta-schema to address the above concerns. We have a few paths going forward:

Leave option enabled for v4 release. Disable it once ESLint changes their default behavior to require schemas for rules with options (since then it will no longer be necessary to specify schema: [] for rules without options).
Disable the option in v4 release.

re requireSchemaPropertyWhenOptionless: I'm fine either way. which one do you prefer?

I personally think we should enforce the more strict behavior (keep requireSchemaPropertyWhenOptionless enabled by default) for now until it becomes no longer necessary (as a result of a potential future ESLint change).

I realized that a lot of our existing rules need to be updated to handle suggestions. I think it's pretty important that we correct this gap in coverage in this major release, as the suggestions feature has been available for nearly 2 years now. I've opened issues to track these gaps, and I will try to open PRs to address these in the coming days. The changes required should not be that large.

#190
#191
#192
#193

👍 nice catch!

@bmish I've tested it in a few plugins - all working fine, an excellent job! 🎉
just pushed 4.0.0 - let's wait and see if need patch releases. 😄


Armor weight

Description
Armor pieces have individual weights that can slow down or speed up a player depending on how heavy the armor piece or material is
Configuration
weight:
helmet: 17
chestplate: 45
leggings: 25
boots: 13
player-weight: 100
player-weight - armor weight = new weight which is turned into speed

You can already slow a user down by using the GENERIC_MOVEMENT_SPEED attribute. Here is the wiki. I also included this example ```yaml
Attributes:

GENERIC_MAX_HEALTH 5 feet               # gain 2.5 hearts
GENERIC_KNOCKBACK_RESISTANCE 0.25 feet  # take 25% less knockback
GENERIC_MOVEMENT_SPEED -0.07 feet       # go very slow


Add Chi routes, document the new structure

Thanks @ezr-ondrej for your review! I've addressed your feedback, also answering your open questions below:

I've got a question to the project layout: Why did you chose to separate this into two distinct go projects?

Just trying the creation of multiple modules at the same time, but finally I decided to follow the standard project structure to be more coherent.


CORS preflight changes

This allows any headers specified by the request as well as explicitly allowing POST and OPTIONS methods, corrects Issue #2.
Also fixes Issue #1

Changes merged in house on master c44d11


Vulnerability in gson version 2.8.6

Is your enhancement request related to a problem? Please describe.
gson version 2.8.6 is vulnerable to desirealization of untrusted data, as shown here:
https://security.snyk.io/vuln/SNYK-JAVA-COMGOOGLECODEGSON-1730327
Describe the solution you'd like
Upgrade gson version to 2.8.9

i can work on it. :)


548 add an endpoint which delete an imported asset

Codecov Report
Patch coverage: 20.83% and project coverage change: -0.39% :warning:

Comparison is base (7f8a310) 39.82% compared to head (729a572) 39.44%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #565      +/-   ##
==========================================
- Coverage   39.82%   39.44%   -0.39%
==========================================
  Files          18       19       +1
  Lines        1155     1179      +24
==========================================
+ Hits          460      465       +5
- Misses        649      668      +19
  Partials       46       46

Files Changed
Coverage Δ

internal/handler/wallet/delete_asset.go
17.39% <17.39%> (ø)

internal/handler/wallet/api.go
90.00% <100.00%> (+0.34%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Error while run gatsby build

Everything works fine when i run the develop script but when I run build this error occurs:
ERROR #95313
Building static HTML failed
See our docs page for more info on this error: https://gatsby.dev/debug-html
543 |   className: PropTypes.string,
544 |   scrollToRef: PropTypes.shape({

545 |     current: PropTypes.instanceOf(Element)
|                       ^
546 |   })
547 | };
548 |

WebpackError: ReferenceError: Element is not defined

design-react-kit.es.js:545
node_modules/design-react-kit/dist/design-react-kit.es.js:545:23

header.js:1
src/components/header.js:1:1

404.js:1
src/pages/404.js:1:1

sync-requires.js:8
node_modules/$virtual/sync-requires.js:8:53

Changing line 545 from current: PropTypes.instanceOf(Element) to current: PropTypes.any I get no more errors but I'm not sure at all this is a proper solution.
Can you help me please?

It's a design-reeact-kit issue: the fix is on the way => https://github.com/italia/design-react-kit/pull/604

The fix is now released: 8a52c46139153ec2c7fe9899bf55b14048a7a7ae
In case of existing projects, just bump design-react-kit and bootstrap-italia dependencies as in the commit.


Using temp dir for unix socket instead of vttest.

Turns out in our internal test environment, the file systems for these
files can't have unix sockets. This also makes it consistent with the
other tests in the directory.

Oh that's great -- thanks. I've had this little nit on my list for a bit of time too and this looks good to me.


do not retry unmute if mute never expires

it seems currently the mute state stuck in awaiting_expiry and loop every hour even if it does not have to.
let me know if I should add migration like
update users_block set state = 'sent' where mute=true and expires is null;

The bug here appears to be that there is a sent state at all - I intended for all mutes to live in awaiting_expiry even if they aren't expirable when I wrote this. This patch isn't sufficient by itself to get to the end effect of not checking these states; I'd instead want to see:

The state renamed to something like permanent
create_local_mute updated to correctly move a mute out of that state back into new if it has its duration updated at all

Yeah, with the create_local_mute patch I think that's good for now - and you're right, the sharing of the model with Block does complicate things somewhat.


(mkdocs) change minimum python version to 3.5

Description
see meta section in https://pypi.org/project/mkdocs/, mkdocs doesn't work with python<=3.5.
Motivation and Context
If a user has only python2 installed it will create an error because mkdocs support only Python >=3.5. This PR changes the minimum to 3.5.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[ ] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[x] All files are up to date with the latest Contributing Guidelines
[ ] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

:white_check_mark: Package verification completed without issues. PR is now pending human review


do not force color theme on extension activation.

Color theme for the whole visual studio code experience is a very sensitive thing to be changing without express consent from the user. Please make the themes available, but do not activate any theme without interaction.

I rest my case... #52

This may be a "feature" of vscode.  @davidlaym, does this only happen while developing an extension in vscode?
Possible explanation:
https://github.com/microsoft/vscode/issues/88169

No, just by normal usage loading a project (multi-root workspace). It happened on the first install of the extension, it changed my color theme. Second time it happened when opening vscode again another day (I think the extension had an update) and it just changed my theme with the d2 dark one. I have opened vscode after a reboot for example and my theme has been respected.
I do not develop extensions, just nodejs apis and react-native apps.

This sounds/smells like a conflict between extensions.  Can you run, "Help: Start Extension Bisect", to automatically run through turning extensions on and off to determine which one it might be?

It hasn't come up again in these 2 weeks, so I think it was some odd behavior that came up a couple of times after install. I have updated vscode and all, so I think is no-repro for me now. Going to close the issue and if I find something else, will come back and expand.
Thanks for your help!


Connect ci and Azure publishing procedure

What this PR does / why we need it:
The ci fetch now the configuration for the Azure publishing procedure from SecretServer correctly.
Release note:

@ccwienk Can you please try out? I tested it locally and it fetch the configuration now correctly from the SecretServer, but please double check.
One TODO is still there. The configuration of the mail receipts which should be notified in case something went wrong during the publishing process.

@dkistner : as for the email recipients, we might just add a list to cicd.yaml, using any of github-usernames, github-team-names, and email-addresses (the first two in particular to allow people to add themselves w/o publishing their email addresses, which not everybody may want - wdyt?

Hmm yes sound like a great idea to use github-team-names. I assume this will not work out of the box. Should we open an issue for that and bring it in with a subsequent pr?


mucp NewService param bug

https://github.com/micro/go-micro/blob/ac2a5a04a2d034c5034c507c0b6b534c6a97b87b/service/mucp/mucp.go#L20
I think this should be micro.NewService(options...)

Yes you're right

I have committed a fix.


Remove just one enum

Problem
This is my proposal for fixing #1107 . I've only done it for one stdlib function, tangentialArcTo -- if y'all like it, I'll apply this idea to the rest of the stdlib.
Previously, if users want to put a tag on the arc, the function's parameters change type.
// Tag missing: first param is array
tangentialArcTo([x, y], %)
// Tag present: first param is object
tangentialArcTo({to: [x, y], tag: "myTag"}, %)

Solution
My proposal in #1006 is that KCL should have optional values. This means we can change the stdlib tangentialArcTo function to use them. In this PR, the calls are now like
// Tag missing: first param is array
tangentialArcTo([x, y], %)
// Tag present: first param is array still, but we now pass a tag at the end.
tangentialArcTo([x, y], %, "myTag")

sounds good to me if @Irev-Dev  is good with it!

Yeah sounds good to me.
Adam and I had a chat earlier as to whether data-last was worth clinging to, but we don't think so.
The only yellow flag I want to throw up is that there are ast-mods that will need to change for this. but I'm happy to tackle the second half of the PR to fix that up.

As a general philosophy I really like the idea of as little as possible existing as a built-in, and building as much as we can using the language itself. I like the idea of variadic functions (so long as we document, autocomplete, and are able to statically lint) so this all def seems cool by my eye. I reckon it may even help with discoverability and readability, since the function that "does the thing" will have a number of different documented definitions for variations on a theme.
Removing this function would be a breaking change  -- abet not a super disruptive one since we've made no stability promises in our preview builds, so now's the time to do this type of stuff before the equities become more complex and we have to more seriously consider language stability (yes the irony given my popoff on API/ABI stability holding projects back generally yesterday is not lost on me :) )

(Also, assuming this is actually talking about variadic functions and not just this "tag last" model specifically as a special case, in which case, still for it)

as little as possible existing as a built-in, and building as much as we can using the language itself.

Agreed, this is why I think optional parameters have to be a KCL concept instead of using Rust enums that KCL can't access or use.

I like the idea of variadic functions (so long as we document, autocomplete, and are able to statically lint) so this all def seems cool by my eye.

I wouldn't really say they're variadic, I'd say they're just functions where some parameters are optional. Functions will always have a fixed list of parameters with their own name and docs, but some of them can be declared as optional and will default to nil.

The only yellow flag I want to throw up is that there are ast-mods that will need to change for this. but I'm happy to tackle the second half of the PR to fix that up.

Thanks @Irev-Dev that would be awesome

Sorry I think I mis-understood. Because this is just for tangentialArcTo there's no ast-mods involving that fn, so there's no hold up from me. We should be able to merge this one.


observations related to menu

Steps to reproduce:
on desktop:
1)go to home page
2) scroll down and notice that menu bar does not appear
3) now scroll up a little and notice that menu bar appears
on mobile:

scroll down slowly
notice that menu bar at the top gets hidden once we reach the contact section and then the footer

Actual result:
1)on desktop, menu bar does not appear while scrolling down (i.e not sticky)
2) on mobile, it gets hidden when we reach contact section/footer on the pages
Expected result: please check this one.

Reported by: Vinod<EMAIL_ADDRESS>Source URL: https://kensway.webflow.io/
Issue details: Open in Marker.io
Device typedesktopBrowserChrome <IP_ADDRESS>Screen Size1366 x 768OSWindows 10 (10.0.0)Viewport Size1366 x 641Pixel Ratio@1x

mobile video:
https://drive.google.com/file/d/1qzU9ZIXU2K2Kbq7aFgYPH8PzK7quHRBr/view?usp=sharing


linux-pam: fix cross-compilation from darwin

Description of changes
Tested on aarch64-darwin with nix build .#legacyPackages.x86_64-darwin.pkgsCross.gnu64.linux-pam

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[x] 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/)
23.11 Release Notes (or backporting 23.05 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.

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

Tag for backport to 23.11 please.


Use i.ytimg.com instead of img.youtube.com

img.youtube.com sends third-party cookies.

Happy to accept a PR for this.

This is in develop now. I'll release shortly once I fix a few small bugs.

Fixed in v3.5.3 👍


Expose the receiver queue size to client consumer stats

Motivation
Currently, we log the receiver queue size. But we don't expose the receiver queue size to the client consumer stats. We should expose it.

I will work on it


Hotfix-Github Actions Cant release new build

I have tested the code and it is working as intened now


CDPAM-1721: Start using CCM v2 from RPMs in CB VM images

Switches mode to start consuming an RPM instead of raw binary.
Also starts using systemd unit service configuration from the RPM.
Updates configuration to latest format.
Other related changes:

CDPAM-1647: Update setup scripts to set and pass relevant proxy parameters
Starts trying to read proxy configuration from EnvironmentFile at /etc/cdp/proxy.env.
Does not fail if the values are absent.
CDPAM-1658: Update cloudbreak-images to consume latest jumpgate-agent
Updates agent version to latest

I think the naming should be sync with the decision here: https://cloudera.slack.com/archives/C01D48PH4TE/p1621597838016100
so if the backend side will use ccmv2_jumpgate, then the folders in the images repo should reflect this also. or we should just stick with ccmv2 as all this will be installed for the clusters too, as it's in the base part.
I will convert this to draft just to make sure no one merges it accidentally


Install Size comparison

I would like to add a row to compare the npm install size of TS vs Flow.
Would you like me to use the versions listed in the readme (TypeScript 2.6 and Flow 0.65) or use the latest versions?

TypeScript
Flow

Install Size (old)

Install Size (latest)

Sure, let's add it! Would be better to specify the versions instead of "old" though.
Thanks


naming convention for STATE constants on Week 2 - TheActivityClass.java

Hi guys,
Based on http://developer.android.com/training/basics/activity-lifecycle/recreating.html
Shouldn't we be using STATE_* for the naming conventions of our states?
It's a small issue but I think the codes you put there
private static final String RESTART_KEY = "restart";
private static final String RESUME_KEY = "resume";
private static final String START_KEY = "start";
private static final String CREATE_KEY = "create";

ought to be
private static final String STATE_RESTART_KEY = "restart";
private static final String STATE_RESUME_KEY = "resume";
private static final String STATE_START_KEY = "start";
private static final String STATE_CREATE_KEY = "create";

Hi @fedmich no need to change that code above since all of them do have the "KEY" at the end , basically if you do STATE_!_KEY , "KEY" becomes redundant/pointless since STATE is already defining the group , or else you can do STATE_RESTART then git rid of the word "KEY" , alternatives use ENUM.


OricToken

Blockchain Platform with
SELF-STABILIZING PROPERTY GOVERNANCE
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x] Image size: 256 by 256 px

OricToken Upload

Upload

Also, you can use these graphics to say that your ERC20 token fully compatible with Trust Wallet (https://trustwallet.com/logo-assets). Tokens will show up automatically once the user receives them.
Feel free to share this on social media and tag Trust Wallet:

Twitter: @trustwalletapp

Facebook: @trustwalletapp


Set Sender ID

On your sns_client object you can do
sns_client.set_sms_attributes({ 'DefaultSenderID' => 'SomeSenderId' })

It's built into the AWS-SDK. Hope that helps!

Thank you, indeed it helps! i hope i can implement this feature soon, thank you again.

Solved in #c817571


Chrome 56 breaks refresh()

The latest update of Chrome (56, 8 feb 2017) breaks something in the plugin, making the page scroll when an animation comes to an end.

can you give more detail?

Steps to reproduce:

create an element and attach Stickit onto it;
create an element with a CSS animation, no matter what type of animation you add;
execute the animation on the latter element while the other element is sticked, see the page scrolling at random bits.

I did not perform a complete debug only because I don't have much spare time. Note that this is the expected behavior (Stickit performs the same calculations in older versions of Chrome). However, the latest Chrome update might have broken some values.


Add ExcludeOfficeIPs flag for policy

Provide a general summary of your changes in the title above. You should
remove this overview, any sections and any section descriptions you
don't need below before submitting. There isn't a strict requirement to
use this template if you can structure your description and still cover
these points.
Description
Describe your changes in detail through motivation and context. Why is
this change required? What problem does it solve? If it fixes an open
issue, link to the issue using GitHub's closing issues keywords1.
Has your change been tested?
Explain how the change has been tested and what you ran to confirm your
change affects other parts of the code. Automated tests are generally
expected and changes without tests should explain why they aren't
required.
Screenshots (if appropriate):
Types of changes
What sort of change does your code introduce/modify?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] This change is using publicly documented (api.cloudflare.com or developers.cloudflare.com) and stable APIs.

Codecov Report

Merging #1205 (dc84128) into master (c07adfc) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1205   +/-   ##
=======================================
  Coverage   49.36%   49.36%
=======================================
  Files         128      128
  Lines       12430    12430
=======================================
  Hits         6136     6136
  Misses       4890     4890
  Partials     1404     1404

Impacted Files
Coverage Δ

devices_policy.go
49.47% <ø> (ø)

dlp_profile.go
37.93% <ø> (ø)

dns.go
72.72% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[terra-list] Add programmatic support for single/multi-select

UXPLATFORM-7595
Summary
Adds a new prop that configures the correct accessibility settings for single/multi select lists. The values is an enum of 'none', 'single-select', 'multi-select'.
Deployment Link

https://terra-core-deployed-pr-#.herokuapp.com/
Testing
Testing in progress.
Additional Details

Thank you for contributing to Terra.
@cerner/terra

Fails

:no_entry_sign:
Please include a CHANGELOG entry for each changed package this PR. Looks like a CHANGELOG is missing for:

terra-toggle-section-header

  Generated by :no_entry_sign: dangerJS against ce7a2df14b36396f3832c1feb7aa692c2f7aaf67

Fails

:no_entry_sign:
Please include a CHANGELOG entry for each changed package this PR. Looks like a CHANGELOG is missing for:

terra-action-header

  Generated by :no_entry_sign: dangerJS against 7e684cd9e1559e90fdc68151d6595f5e5b7b5405

Fails

:no_entry_sign:
Please include a CHANGELOG entry for each changed package this PR. Looks like a CHANGELOG is missing for:

terra-action-header

  Generated by :no_entry_sign: dangerJS against 051210d99a78e32bf6291ada0527218f47f54aec

+1 from me :)


Error on data when trying to access sheet with frozen row/col

The Json object only populates the first cell+ column if the first row is a frozen row

@JasonZheng20 interesting. i'll spend some time testing this and get back with a workaround and/or bug fix.

@JasonZheng20 i'm unable to reproduce this. can you share the google doc with me for me take a look at this specific case?

i cannot reproduce it either, tried freezing sequential and both, one or multiple rows and columns

thanks for testing, @robertvasile.
closing due to inactivity. in the issue re-arises/persists, @JasonZheng20, feel free to reopen.


How to become a product manager at big tech companies?

For this one question. We recorded an entire podcast series.
Do check-out bit.ly/productfm


Eagerly fetch app list when the widget interstitial screen is shown

Task/Issue URL: https://app.asana.com/0/414730916066338/1168625961103601
Tech Design URL:
CC:
Description:
Eagerly fetch app list for interstitial
Steps to test this PR:

Launch interstitial from widget
Enter query; verify this works as intended and app list available quickly for filtering

Internal references:
Software Engineering Expectations
Technical Design Template

@CDRussell, I'll also review tomorrow.


Move HTTP send operations away from the zedagent main event loop

Zedagent main event loop is responsible for handling pubsub updates along with sending messages to the controller. HTTP send is synchronous call and can stall the whole main event loop for up to 6 minutes (overall send timeout).
This badly affects the system responsiveness which can be observed in air-gaped environment (no connectivity to the controller), when the queue is stuck waiting for send to be completed and no other pubsub updates are handled.
Three things are done in this PR:

Introduced connect() ("dial" in terms of Go) timeout, which is much less than the send() timeout (helps to fail faster).
All direct HTTP send() calls are moved away from the main event loop and executed in dedicated goroutines.
(second commit) Also make sure that VMs (such as Local Profile Server or Local Operator Console) are not delayed by NIM testing DPC. In offline mode connectivity probes will take longer (until dial timeout elapsed).

@milan-zededa @rouming we need to complete this before the build on Monday. I'll set up a brief call on friday morning CET

@milan-zededa @rouming we need to complete this before the build on Monday. I'll set up a brief call on friday morning CET

@eriknordmark I'm on this task right now. I hope I will finish it on Friday, but can't give 100%. Let's discuss the status on the call tomorrow.

Closing in a favor of this #3207 PR.


Error: Argument list too long

Hi. I ran maegatk for 4 samples. For three I got this error:
/bin/sh: /usr/bin/ls: Argument list too long
ERROR: Could not import any samples from the user specification; check flags, logs and input configuration; QUITTING

The tool split the bam file as it should, but did not create any log files or folders.
I tried maegtk and maegatk. Both failed with the same error. When I tried mgatk, it worked fine.

Can you specify the commands that you used on mgatk versus maegatk?

I pretty much used the same commands, see below.
maegatk bcall \
       --ncores $NCORES \
       --snake-stdout \
       --min-barcode-reads 3 \
       --nsamples 1024 \
       --barcode-tag "CB" \
       --umi-barcode "UB" \
       --input $bams_use \
       --output $output_path \
       --alignment-quality 30 \
       --mito-genome "gene_annotation/refdata-gex-GRCh38-2020-A/fasta/genome.fa"

mgatk tenx \
       --ncores $NCORES \
       --snake-stdout \
       --nsamples 1024 \
       --barcodes $cells_use \
       --barcode-tag "CB" \
       --umi-barcode "UB" \
       --input $bams_use \
       --output $OUTPUT$sample_use \
       --alignment-quality 30 \
       --mito-genome gene_annotation/refdata-gex-GRCh38-2020-A/fasta/genome.fa

Right so in maegatk, each cell get split into its own .bam file because that's how I could get the consensus read collapse to work. The mgatk tenx mode is written where it doesn't produce that number of bams (it only produces as many parallel cores as you let it process). The other difference that I see is that you subset which barcodes to use in the mgatk call but not the maegatk call, so you are probably processing many barcodes that aren't real cells.

I ran maegatk again with the --barcodes parameter set. Now, it worked.

Hello, I also encountered the same problem, but I set the parameters of -b and -bt.

Since it's not 10x data, I can't run mgatk in 'tenx' mode. I tried to run mgatk bcall but that too failed. Unlike the maegatk run,mgatk runs without error, but produces an unexpected output file:

I don't know what caused it.


Add development environment setup instructions

Coverage increased (+0.4%) to 79.079% when pulling f66a41f5173484d21a2f04120f9a22e49f324bd9 on env-example into 7b2d4e995bd6369e241185bcf7a42f0b50d25893 on master.


Cannot update article title using Back button

Since we no longer allow editing on the Details page, I tried to use the Back button to go back in the workflow to the Basics step and update there.
I used the Back button, updated the article title, then clicked back through the workflow to the Details page, but am still seeing the old, original title (not the updated one). As a user, I would assume changing the title back at the start of the workflow/before submitting would update the title on the Details page.

https://github.com/eclipse-pass/pass-ui/pull/1234


Blank page after creating build via create react app

Trying to create build on both localhost and server via create react app (npm run build), however its showing blank page with no error. Nothing is rendered inside <div id="root">

npm run build
<EMAIL_ADDRESS>build

react-scripts build

Creating an optimized production build...
Compiled successfully.
File sizes after gzip:
889.64 kB  build\static\js\main.e6edb506.js
96.26 kB   build\static\css\main.894dcfcd.css
1.68 kB    build\static\js\787.e170219d.chunk.js
The bundle size is significantly larger than recommended.
Consider reducing it with code splitting: https://goo.gl/9VhYWB
You can also analyze the project dependencies: https://goo.gl/LeUzfb
The project was built assuming it is hosted at ./.
You can control this with the homepage field in your package.json.
The build folder is ready to be deployed.
Find out more about deployment here:
https://cra.link/deployment

I've added "homepage" attribute in package.json
"homepage": "."
I tried downgrading node js version, but in vain.
Hope-ui-react template version: 2.0.0
Node js version: 18.17.0

Hi ,
Check your .env.production file  and update path to /
Example
PUBLIC_URL="/hope-ui/react/build"
to
PUBLIC_URL="/"


Update Arbitrum docs to use Arbiscan

We should switch the explorer for the Arbitrum feeds to arbiscan
https://arbiscan.io/

Their explorer doesn't support rinkeby but I opened a PR for mainnet for now


Documentation fix for match-declaration-order option for object-literal-sort-keys

follow-up of #2829:

It might be confusing that match-declaration-order applies to single-line literals but alphabetic ordering does not. We should at least document this subtle difference in the behavior (especially since alphabetic ordering is the fallback when a contextual type is not found).

☠ TSLint's time has come! ☠
TSLint is no longer accepting most feature requests per #4534. See typescript-eslint.io for the new, shiny way to lint your TypeScript code with ESLint. ✨
It was a pleasure open sourcing with you all!

🤖 Beep boop! 👉  TSLint is deprecated 👈 (#4534)  and you should switch to typescript-eslint! 🤖
🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋