Refactor generate release notes script for enhanced release process

Summary

Refactor generate release notes script (i.e., generate-release-notes.sh) to fit with the enhanced release process being worked on in branch feature/shinkansen.
NOTE: This pull request will be merged into branch feature/shinkansen.
Implementation details

Take in options/flags instead of having set arguments with a specific order for AL2 NVIDIA version, AL2 CUDA version, and AL1 containerd version
Make AL2 NVIDIA version and AL2 CUDA version options optional, as with the enhanced release process AL2 GPU AMIs may not necessarily be released during every AMI release
Define new option/flag --exclude-ami to specify what AMI variants are excluded in a given release, as with the enhanced release process any given AMI variant may not necessarily be included
Only generate release notes for AMI variants that are included as part of the release
Take into account information / file structure changes made to release variables as part of https://github.com/aws/amazon-ecs-ami/pull/167
Update script usage information according to the changes made

Testing

Manually pulled in the most recent release variables information from branch main and then tested:

generating release notes for 20231219 release using ./generate-release-notes.sh --al2-gpu-nvidia-ver 535.129.03 --al2-gpu-cuda-ver 12.2.2 --al1-containerd-ver 1.4.13 command and comparing the generated release notes against the expected release notes using diff. No differences were found

Generated output
### Source AMI release notes
---
* [Amazon Linux 2023 release notes](https://docs.aws.amazon.com/linux/al2023/release-notes/relnotes.html)
* [Amazon Linux 2 release notes](https://docs.aws.amazon.com/AL2/latest/relnotes/relnotes-al2.html)
* [Amazon Linux release notes](https://aws.amazon.com/amazon-linux-ami/2018.03-release-notes)

### Changelog
---
https://github.com/aws/amazon-ecs-ami/blob/main/CHANGELOG.md#20231219

### Amazon ECS-optimized Amazon Linux 2023 AMI
---
#### AMD64
- AMI name: al2023-ami-ecs-hvm-2023.0.20231219-kernel-6.1-x86_64
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: al2023-ami-minimal-2023.3.20231218.0-kernel-6.1-x86_64
- Distribution al2023 release: 2023.3.20231218

#### ARM64
- AMI name: al2023-ami-ecs-hvm-2023.0.20231219-kernel-6.1-arm64
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: al2023-ami-minimal-2023.3.20231218.0-kernel-6.1-arm64
- Distribution al2023 release: 2023.3.20231218

#### Neuron
- AMI name: al2023-ami-ecs-neuron-hvm-2023.0.20231219-kernel-6.1-x86_64
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: al2023-ami-minimal-2023.3.20231218.0-kernel-6.1-x86_64
- Distribution al2023 release: 2023.3.20231218

### Amazon ECS-optimized Amazon Linux 2 AMI
---
#### AMD64 (Kernel 4.14)
- AMI name: amzn2-ami-ecs-hvm-2.0.20231219-x86_64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-x86_64-ebs

#### ARM64 (Kernel 4.14)
- AMI name: amzn2-ami-ecs-hvm-2.0.20231219-arm64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-arm64-ebs

#### Neuron (Kernel 4.14)
- AMI name: amzn2-ami-ecs-inf-hvm-2.0.20231219-x86_64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-x86_64-ebs

#### GPU (Kernel 4.14)
- AMI name: amzn2-ami-ecs-gpu-hvm-2.0.20231219-x86_64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- NVIDIA driver version: 535.129.03
- CUDA version: 12.2.2
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-x86_64-ebs

#### AMD64 (Kernel 5.10)
- AMI name: amzn2-ami-ecs-kernel-5.10-hvm-2.0.20231219-x86_64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-x86_64-ebs

#### ARM64 (Kernel 5.10)
- AMI name: amzn2-ami-ecs-kernel-5.10-hvm-2.0.20231219-arm64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-arm64-ebs

### Amazon ECS-optimized Amazon Linux AMI
---
The Amazon ECS-optimized Amazon Linux AMI is deprecated as of April 15, 2021. After that date, Amazon ECS will continue providing critical and important security updates for the AMI but will not add support for new features.

- AMI name: amzn-ami-2018.03.20231219-amazon-ecs-optimized
- ECS Agent version: [1.51.0](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.51.0)
- Docker version: 20.10.13
- Containerd version: 1.4.13
- Source AMI name: amzn-ami-minimal-hvm-2<IP_ADDRESS>31218.0-x86_64-ebs

generating release notes using the  --exclude-ami option/flag and confirming that the excluded AMI variants specified using that option are not included in the generated output

Example test
Input
./generate-release-notes.sh --al2-gpu-nvidia-ver 000.00.00 --al2-gpu-cuda-ver 00.0.0 --al1-containerd-ver 0.0.0 --exclude-ami al2023neu,al2inf

Output
### Source AMI release notes
---
* [Amazon Linux 2023 release notes](https://docs.aws.amazon.com/linux/al2023/release-notes/relnotes.html)
* [Amazon Linux 2 release notes](https://docs.aws.amazon.com/AL2/latest/relnotes/relnotes-al2.html)
* [Amazon Linux release notes](https://aws.amazon.com/amazon-linux-ami/2018.03-release-notes)

### Changelog
---
https://github.com/aws/amazon-ecs-ami/blob/main/CHANGELOG.md#20231219

### Amazon ECS-optimized Amazon Linux 2023 AMI
---
#### AMD64
- AMI name: al2023-ami-ecs-hvm-2023.0.20231219-kernel-6.1-x86_64
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: al2023-ami-minimal-2023.3.20231218.0-kernel-6.1-x86_64
- Distribution al2023 release: 2023.3.20231218

#### ARM64
- AMI name: al2023-ami-ecs-hvm-2023.0.20231219-kernel-6.1-arm64
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: al2023-ami-minimal-2023.3.20231218.0-kernel-6.1-arm64
- Distribution al2023 release: 2023.3.20231218

### Amazon ECS-optimized Amazon Linux 2 AMI
---
#### AMD64 (Kernel 4.14)
- AMI name: amzn2-ami-ecs-hvm-2.0.20231219-x86_64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-x86_64-ebs

#### ARM64 (Kernel 4.14)
- AMI name: amzn2-ami-ecs-hvm-2.0.20231219-arm64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-arm64-ebs

#### GPU (Kernel 4.14)
- AMI name: amzn2-ami-ecs-gpu-hvm-2.0.20231219-x86_64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- NVIDIA driver version: 000.00.00
- CUDA version: 00.0.0
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-x86_64-ebs

#### AMD64 (Kernel 5.10)
- AMI name: amzn2-ami-ecs-kernel-5.10-hvm-2.0.20231219-x86_64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-x86_64-ebs

#### ARM64 (Kernel 5.10)
- AMI name: amzn2-ami-ecs-kernel-5.10-hvm-2.0.20231219-arm64-ebs
- ECS Agent version: [1.79.2](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.79.2)
- Docker version: 20.10.25
- Containerd version: 1.6.19
- Source AMI name: amzn2-ami-minimal-hvm-2.0.20231218.0-arm64-ebs

### Amazon ECS-optimized Amazon Linux AMI
---
The Amazon ECS-optimized Amazon Linux AMI is deprecated as of April 15, 2021. After that date, Amazon ECS will continue providing critical and important security updates for the AMI but will not add support for new features.

- AMI name: amzn-ami-2018.03.20231219-amazon-ecs-optimized
- ECS Agent version: [1.51.0](https://github.com/aws/amazon-ecs-agent/releases/tag/v1.51.0)
- Docker version: 20.10.13
- Containerd version: 0.0.0
- Source AMI name: amzn-ami-minimal-hvm-2<IP_ADDRESS>31218.0-x86_64-ebs

incorrect usage (i.e., not passing in AL2 GPU NVIDIA version when AL2 GPU release is required and/or AL2 GPU CUDA version is provided, not passing in AL2 GPU CUDA version when AL2 GPU release is required and/or AL2 GPU NVIDIA version is provided, not passing in AL1 containerd version when AL1 release is required, etc.)

Example test
Input
./generate-release-notes.sh --al2-gpu-cuda-ver 00.0.00 --exclude-ami al2023,al2023arm,al2023neu,al1

Output
Error: AL2 GPU CUDA version or AL2 GPU NVIDIA version is empty when releasing AL2 GPU

Usage:
  ./generate-release-notes.sh

Options:
--al2-gpu-nvidia-ver  (Optional) AL2 GPU NVIDIA version. If specified, then --al2-gpu-cuda-ver option is also required to be specified.
--al2-gpu-cuda-ver    (Optional) AL2 GPU CUDA version. If specified, then  --al2-gpu-nvidia optin is also required to be specified.
--al1-containerd-ver  (Optional) AL1 containerd version.
--exclude-ami         (Optional) comma separated list of AMI variants that are excluded in the release.

Example:
  ./generate-release-notes.sh --al2-gpu-nvidia-ver 000.00.00 --al2-gpu-cuda-ver 00.0.0 --al1-containerd-ver 0.0.0 --exclude-ami al2023neu,al2inf

New tests cover the changes: no
Description for the changelog

Refactor generate release notes script for enhanced release process
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@mye956:

nit: Perhaps we can include a main function. It's a bit hard to trace through the code and might be more helpful in debugging. Thoughts?
nit (non-blocking): Could we also keep all of the functions grouped up for better readability? (i.e. get_ami_details)

Thanks for your comment! That's reasonable, the main reason I had not included these were to follow the current convention / layout of the script and add any such enhancements in a separate pull request. However, upon second thought, it shouldn't take too much effort to include in scope defining a main function and group the commands living outside of a function into more granular functions. I will add these changes in.


add addtional RTD info

resolves #56
submitted for initial review and comment

note: I did not do the base object, since I'm looking for feedback on how far I missed the mark on these three.  I anticipate directions to complete the base, if we feel that should be done.....

Hello :), thanks for the add I could take a look adn we could work together, there is one thing that needs to be added in order to show the documentation in the __init__ in read the docs. at the moment, the docs are like this

in order to show the changes that you are doing, we need to add the following line in conf.py in the docs directory, in https://github.com/adafruit/Adafruit_CircuitPython_PN532/blob/0061f33008bf02381232ba1c7aec960ab98af18d/docs/conf.py#L41
autoclass_content = "both"
This would generate the documentation after merging the changes that you are proposing like this:

You could check the effect of building the docs locally. If you have any question please feel free either here or in discord :)

@jposada202020  you mentioned building the docs locally and reviewing - what process does that?  If you can even point to a link I'm willing to dig a bit more.

@jposada202020 I have a problem running the sphinx-build command.  It seems not to see items imported inside the try block.  Moved the first two outside just to test (digitalio.DigitalInOut and circuitpython-typing.ReadableBuffer.   It then fails because the typing library isn't found.  so it appears it's not quite as straightforward as the docs are suggesting.  Any ideas?

@tcfranks are you working in a virtual environment? there could be two problems according to my experience:
Update sphinx to 6.X.X. in the library docs directory requirements.txt we request sphinx>=4.0.0
Also as you could see in the requirements.txt you have the following requirements. So you can install them in your virtual environment
Adafruit-Blinka
adafruit-circuitpython-busdevice
adafruit-circuitpython-typing
pyserial
typing-extensions~=4.0

I have reproduced the error that your are having, eliminating typing-extensions from my virtual environment.
(venv) j@j:~/PycharmProjects/Adafruit_CircuitPython_PN532/docs$ sphinx-build -E -W -b html . _build/html
Running Sphinx v6.1.3
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading intersphinx inventory from https://docs.circuitpython.org/projects/busdevice/en/latest/objects.inv...
loading intersphinx inventory from https://docs.circuitpython.org/en/latest/objects.inv...
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 3 source files that are out of date
updating environment: [new config] 3 added, 0 changed, 0 removed
reading sources... [100%] index

Warning, treated as error:
autodoc: failed to import module 'adafruit_pn532' from module 'adafruit_pn532'; the following exception was raised:
Traceback (most recent call last):
  File "/home/j/circuitpython projects/venv/lib/python3.10/site-packages/sphinx/ext/autodoc/importer.py", line 60, in import_module
    return importlib.import_module(modname)
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/home/j/PycharmProjects/Adafruit_CircuitPython_PN532/adafruit_pn532/adafruit_pn532.py", line 159, in <module>
    class PN532:
  File "/home/j/PycharmProjects/Adafruit_CircuitPython_PN532/adafruit_pn532/adafruit_pn532.py", line 166, in PN532
    irq: Optional[DigitalInOut] = None,
NameError: name 'DigitalInOut' is not defined

(venv) j@j:~/PycharmProjects/Adafruit_CircuitPython_PN532/docs$ pip install typing-extensions
Collecting typing-extensions
  Using cached typing_extensions-4.5.0-py3-none-any.whl (27 kB)
Installing collected packages: typing-extensions
Successfully installed typing-extensions-4.5.0
(venv) j@j:~/PycharmProjects/Adafruit_CircuitPython_PN532/docs$ sphinx-build -E -W -b html . _build/html
Running Sphinx v6.1.3
loading intersphinx inventory from https://docs.python.org/3/objects.inv...
loading intersphinx inventory from https://docs.circuitpython.org/projects/busdevice/en/latest/objects.inv...
loading intersphinx inventory from https://docs.circuitpython.org/en/latest/objects.inv...
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 3 source files that are out of date
updating environment: [new config] 3 added, 0 changed, 0 removed
reading sources... [100%] index
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [100%] index
generating indices... genindex py-modindex done
writing additional pages... search done
copying static files... done
copying extra files... done
dumping search index in English (code: en)... done
dumping object inventory... done
build succeeded.

The HTML pages are in _build/html.
(venv) j@j:~/PycharmProjects/Adafruit_CircuitPython_PN532/docs$

It seems that It did not like very much my space add, and now the CI is failing because of that. could you check on your end. thanks

@kattni this is the project - or do you need my side of the branch?

Thank you!


Delete properties to make functions more similar

Fixes #15.
Properties present in to but not in from are deleted. This allows a better behavior when using arrow functions vs non-arrow functions (which have a different Function#prototype).
I've also tried to improve the documentation a little.

Fixed.


Longest substring without repeating charachters

Link : https://leetcode.com/problems/longest-substring-without-repeating-characters/
Create a file in 'Strings/Medium' folder  and add your code .
Dont forget to check the 'CONTRIBUTING.md' File for guidelines

Hello, can I take this issue ?

Sure


Full Enum support and reader's iterator returns Result

Full support for Enum; closes #5; closes #6
Also make the reader's iterator return a result of Value so to able to communicate errors

    Support Enum when reader schema is missing

    In order to do so we added the symbol string to the Enum value type and
    replaced any instance of value String passed as input with the new enum
    except if the users specify it in their input.

    This commit also adds a test to cover the above case.


Catch up with latest server changes

This PR brings the 4.0 driver implementation to work with the latest snapshot server. Included changes are as follows;

Connections to the server are now plain text by default, and needs to be explicitly configured to enable Tls12. When encryption is turned on, the default trust manager now verifies trust based on the underlying system certificate store.
IAsyncSession.LastBookmark is now exposed as a Bookmark class. This class holds a list of bookmark strings inside, either retrieved from the server as a result of a transaction completion or by the user supplied initial bookmark list.
Session construction through Driver.AsyncSession, Driver.RxSession and Driver.Session methods now accept an options builder of type Action<SessionOptions> which is used to configure options applicable to the requested session instance. The current SessionOptions.Database property and SessionOptions.ForDatabase method does not have an implementation yet.

/azp run


Integrating axis titles with per-axis scaling

Similar to #671, modifying the solution to be based on "per-axis scaling" enabled PlotLayer version.

@Firenze11 can you create your PR against master?

@shaojingli Sure. Will need to edit the demo app to adapt to the new API as @Pessimistress pointed out.


updated templates

This pull request involves significant changes to the ADOGenerator project, including the removal of numerous JSON template files and the addition of new methods for creating and managing teams in the project service. Below is a summary of the most important changes.
Template File Removals:

Removed various team and work item template files from the project, including TeamArea.json, BoardColumns.json, CardFields.json, and others. (src/ADOGenerator/ADOGenerator.csproj)
Deleted the Dashboard.json, Work in Progress.json, EnableEpic.json, EpicfromTemplate.json, ImportSourceCode.json, ProjectSettings.json, ProjectTemplate.json, ContosoShuttle-code.json, TeamArea.json, and Teams.json files from the ContosoShuttle template directory. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

Code Changes:

Renamed the CreateTeams method to CreateTeams1 in ProjectService.cs and added a new CreateTeams method with enhanced functionality for creating and configuring teams based on JSON templates. [1] [2]

This pull request primarily involves the removal of outdated documentation and redundant files. The most significant changes include the deletion of the "Getting Started" section from the README.md file and the removal of an HTML file generated by Doxygen.
Documentation updates:

README.md: Removed the "Getting Started" section, which included links to various documentation files and resources.

File cleanup:

Report/html/class_templates_generator_tool_1_1_configuration-members.html: Deleted the entire HTML file generated by Doxygen, which contained a member list for the TemplatesGeneratorTool.Configuration class.


Experiment with custom react reconciler for tvml

How'd this work out ? The only reason I don't use the react tvOS implementation is that it can't render the nice templates that are built in. ( to my knowledge )

For now everything forks great. Also integration with redux and other libs works as expected. Need to test some edge cases and integrate with routing. I’m planning to release new major release in two weeks or less 😉

You can check my experiments in this PR https://github.com/a-ignatov-parc/tvos-soap4.me/pull/36

Awesome sauce


Added support for rename script command and has mechanism method

Added support for RENAMESCRIPT command according to https://www.ietf.org/rfc/rfc5804.txt
Also added has auth method which permits to check if server supports a given method

@josaphatim Please 1.0.4 when this is merged in.


ABC-214: fix permalinks to direct messages

Summary
This simplifies the changes introduced in ABC-160 to simply check that
the channel exists instead of also checking that the channel team id
matches the current team. The additional check was redundant, since the
set of channels available are already constrained to the current team;
it was also wrong, since direct messages and group messages aren't
actually assigned team ids, leading to the regression in question.
Note that this check (before and even now) only works if you have access
to the two teams in question. If you try to open a malformed permalink
referencing a team for which you don't have access or that doesn't
exist, none of the router code in  executes (team is null),
and a different path is executed that doesn't try to evaluate the
permalink. Fixing that appears to be non-trivial and out of scope for
this change.
Ticket Link
https://mattermost.atlassian.net/browse/ABC-214
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] Ran make check-style to check for style errors (required for all pull requests)
[x] Ran make test to ensure unit and component tests passed

@crspeller, if you have any advice re: the limitations of permalink checking above, let me know. This is my first exposure to react-router, and this seems like one of the challenges of allowing "side effects from views". I fell in love with the https://github.com/redux-saga/redux-saga library to externalize/"purify" side effects for precisely these kinds of challenges.


Unable to grab password from keepass when trying to authenticate dropbox

plugin requires me to sign in to my dropbox account to authenticate but i could not access my password for dropbox which was stored inside keepass.

Sorry, I cannot help you with this problem. Try to recover your Dropbox password via "Forgotten Password" function.

i dont need help with the problem as i had a work around, but maybe thinking about parent detection so you can use the login details stored in keepass when trying to authenticate through keepass which is what you designed the plugin to do.

Ok, now I understand. I will think about it.


Update pty.js

ptyjs fails to build on node 6 :) didnt test on old versions  of node -- can you give it a look?

Thanks for that! We had bumped this to 0.3.1 but it got rolled back by mistake.

np!


brew.sh: fixes for UTF-8

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Fix Homebrew detection mechanism of usable locale.
Order of locales https://github.com/Homebrew/brew/pull/8047#issuecomment-662722092:

The user's current locale if it's UTF-8
C.UTF-8
en_US.UTF-8
First available UTF-8 locale
C

brew style is failing due to shellcheck: https://github.com/Homebrew/brew/pull/8072/checks?check_run_id=904644217

brew style is failing due to shellcheck: https://github.com/Homebrew/brew/pull/8072/checks?check_run_id=904644217

Yeh, my bad -- I noticed that but had to leave and left the PR without a note that I'll continue working on it.
By the way, brew style doesn't fail for me in a Homebrew/brew Docker container, which is weird.

Ready for a second review.

Thank you for this PR, Maxim!

Thanks for the reviews, @MikeMcQuaid and @sjackman!


Stop scroll propagation in L.Layers.Control in chrome>55

Fixes #5277.

If it is fixed this way, it it will be necessary to fix similar usages in several other places (zoom buttons size, touch tolerances, ...) and in third-party plugins and custom components that rely on this flag.
In my opinion it is better to fix Browser.touch detection which was changed in
a1371507bfe898eac1dabbb34c8f7692195e74d9 and works incorrectly in last Chrome version.
a1371507bfe898eac1dabbb34c8f7692195e74d9 removes deprecated "navigator.pointerEnabled" condition from Browser.pointer flag. We can use navigator.maxTouchPoints mentioned in #5189.


llvm40 build fails – force official repo pkg install?

I am referencing the official quaterly repositories in FreeBSD conf but the pkg version of llvm40 provided in quarterly does match the one in the ports tree.
So, synth is kicking off a build, which (goes without saying) fails. It's not a synth fault. The problem seems to be caused by the swap and disc reqirements of llvm40's build process. To be honest, I've never managed to build this gigantic monster even with make.conf. No matter how much swap and disc space I provide.
So I am wondering, is there any way to force an official pkg install on one or more ports in synth?
BTW: synth is awesome and I think there should be an option for donations.

On Ravenports on FreeBSD, I have to do the following to build llvm40:

Provide an additional swapfile to increase swap to something like 20G
Limit jobs on llvm to 2 (on Linux, it has to be limited to 1)

The reason for the last is a "freeze" that occurs during linking which is only avoidable if llvm isn't building with many multiple jobs.
as far as using "official" ports instead, there's an option on synth to "prefer" freebsd packages, but it's not quarterly packages, it's the trunk ports.  And it will affect all of them.
You could always "fool" synth by pre-downloading the package and putting it in the repository directory manually.  As long as the dependencies are in place, synth will assume good and won't touch it.

Thank you so much your advice and help. I think I need to buy a box dedicated entirely to building llvm.

Forgot to close the "issue".

Got it to work now.
I ran
just-build lang/gcc6 first
Then I disabled the lldb-debugger for llvm40.
With this in place building of llvm40 worked.

interesting.


Security: Storage of issues should be authenticated [90h]

In CodeChecker 5.8 users to the viewer can be authenticated, however issue storage cannot be authenticated, because the storage uses direct database connection.
CodeChecker check -n myProject -b "make -j 4" --dbname myProjectdb --dbaddress localhost --dbport 5432
Instead of db location, the users will need to define a CodeChecker server and user name [-u USERNAME] [--host HOST] [-p PORT]. Authentication and authorization then will be performed based on LDAP user name / password.
Implementation

[x]  Move storage server API implementation into the viewer server (20h) (assuming single thread impl)
[x]  Remove db start from check command, store command (8h)
[x]  Remove storage session managment (Client.py) (8h)
[x]  Rewrite store client to use HTTP, remove db arguments cmd line, add arguments for codechecker server access, login (16h)
[ ]  remove check command (4h)
[x]  add/update test cases (32h)

90h

check command is kept for now (might be removed later) but the database arguments are deprecated.
User login is handled as before with the CodeChecker cmd login command so no username needs to be provided for the store and check commands.


Remove unused clock field in SchemasResources

Modifications
Remove unused clock field in SchemasResources
Documentation
Need to update docs?

[x] no-need-doc
little optimize

Cherry-picking to branch-2.8 to simplify conflict resolution.


WII U Pro Controller detected but cannot be used

I tried to use the WII U Pro Controller on Linux Mint 17. The detection works but when I use it with xwiishow, only actions on Led On/Off can be used. States of buttons, pad and analog pads doesn't work.
Kernel version : 3.13.0-24-generic
Linux : Linux Mint 17 - 64 bit version
Dmesg output :
[   44.347449] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[   44.347459] Bluetooth: HIDP socket layer initialized
[   47.202763] wiimote 0005:057E:0330.0005: unknown main item tag 0x0
[   47.202857] wiimote 0005:057E:0330.0005: hidraw4: BLUETOOTH HID v0.01 Gamepad [Nintendo RVL-CNT-01-UC] on 00:15:83:0c:bf:eb
[   47.202870] wiimote 0005:057E:0330.0005: New device registered
[   48.254449] wiimote 0005:057E:0330.0005: detected device: Nintendo Wii U Pro Controller
Xwiishow list output :
Listing connected Wii Remote devices:
Found device #1: /sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/bluetooth/hci0/hci0:1/0005:057E:0330.0005
End of device list
I attached too the output of the command "xwiishow 1"

Issue can be closed ;) The issue was indeed the bluetooth usb key that causes the issue. For users, I suggest you to test a bluetooth usb key before buying it ;)

I seem to have the same issue described here: When I run "sudo xwiishow 1" I can only change LEDs status and don't see modified status of buttons and axes.
I also have a WII U Pro Controller connected with a USB Bluetooth dongle (bought in Germany at company Conrad and this usb dongle was recommended for use with raspberry pi).
My os is OSMC and the Wii U Pro Controller is connected. My original idea was to make the controller work in Kodi (and additionally Nvidia Gamestreaming using the moonlight add-on). Within Kodi the Wii U Pro Controller can only move the mouse (however not a really controlled way). All other buttons do not seem to work. Therefore I have two questions:

Is the root cause the usb bluetooth dongle and what usb bluetooth dongle should be used to work with the Wii U Pro Controller?

How can I adjust the mapping (for example for KODI) of the Wii U Pro Controller keys? Is there a configuration file I have to set up or manipulate?

I have figured out that "sudo xwiishow 1" is working as expected when I stop the mediacenter kodi (OSMC): "sudo systemctl stop mediacenter". Therefore please forget what I have asked for in my previous comment. I can confirm that the bluetooth dongle I am using is working.
The only thing now I have to figure out now is why running kodi makes the Wii U Pro Controller buttons not work anymore. If you have any idea what I could have missed I would be glad.

The mediacenter probably grabs the input devices. Nothing you can do. This basically prevents anyone else from getting events from the device. No idea why they do it, though..

okay, at the moment I try to understand how this "keymap.xml feature" of kodi works. However, I am not sure if this will result in a solution for my idea (controlling kodi with the Wii U Pro controller),
At the moment the situation is like this: the left joystick controls the mouse (in an actually weird way - the pointer always goes back into the upper left corner of the screen when I release the left joystick).
I have seen (mentioned in other comments) that you have to tell the system that this device should not be handled as a mouse. Do you have an idea what I could do so that kodi does handle this device correctly?


[FLOC-3448] Merge release 1.7.1 back into master

Merge to get the release notes and the tag back into master. Merge resolved in favor of master so the release branch only patch is effectively removed from this merge.

Looks good to me. Merge when http://build.clusterhq.com/boxes-flocker?branch=merge-release-1.7.1-FLOC-3448 is all-green.


Community Call, April 2021

Time: 20th April, 15:00 CEST
Duration: 1 hour scheduled, no recording, in English
Invitations: Open for all, message me your email address on Slack, and I'll forward you the invite
Agenda

Welcome
Short update on "Open Source Namespaces" (#4592)
Data serialization progress (#4654, #4689) and discuss what should be next
ABAP code review, https://github.com/SAP/styleguides/tree/main/abap-code-review
merging to default branch for contributors

If time permits:

remove "Make Online" / "Make Offline" features?
GUI support: Windows/Java/HTML GUI

feel free to add more topics in the comments below

https://github.com/SAP/styleguides/tree/main/abap-code-review

merging to default branch for contributors

Short update on "Open Source Namespaces" (#4592)
Data serialization progress (#4654, #4689) and discuss what should be next

Hi,
i couldn't make it to the call this week.
Do you have somewhere a little "protocol" of the meeting concerning the topics discussed?
I would be interested :)
BR

We keep the meeting informal, there will be another call in a months time or so


Improve mux tracing

This PR consist of three patches, the last one is not at all about tracing:

network-mux: replaced 'Dying' with MuxTraceTerminating
Mux is not dying anymore when a mini-protocol terminates, let's reflect that
in the trace.
network-mux: sligtly nicer Show instance for MuxTrace
network-mux: filling completionVar should never block
~Might be controverial!~ It is sensible to throw an exception if it blocks.

bors merge

bors merge

bors merge


Response.BufferAsync should return ValueTask<byte[]>, not ValueTask

Description
Currently Response.BufferAsync() returns ValueTask<string> which is wrong when the response contains image data.
Here is the original puppeteer code (not the puppeteer-sharp, but the one from Google) which stores the response data (base64/utf8 strings) to a Buffer object. The Buffer object internally is like array of bytes.
if (!this._contentPromise) {
  this._contentPromise = this._bodyLoadedPromise.then(async error => {
    if (error)
      throw error;
    const response = await this._client.send('Network.getResponseBody', {
      requestId: this._request._requestId
    });
    return Buffer.from(response.body, response.base64Encoded ? 'base64' : 'utf8');
  });
}
return this._contentPromise;

Here is the current puppeteer-sharp code. It converts the uft8/base64 strings to plain string which is wrong, because it mangles the image data.
                    _buffer = response.Base64Encoded
                        ? Encoding.UTF8.GetString(Convert.FromBase64String(response.Body))
                        : response.Body;

What we need to do is to convert the utf8/base64 string to byte[]. This way, the image data (encoded in base64 string) will not be mangled. It should look like this:
                    _buffer = response.Base64Encoded
                        ? Convert.FromBase64String(response.Body)
                        : Encoding.UTF8.GetBytes(response.Body);

Of course then the following line
public ValueTask<string> TextAsync() => BufferAsync();

should be also amended to something like this
public async ValueTask<string> TextAsync() => Encoding.UTF8.GetString(await BufferAsync());

Complete minimal example reproducing the issue
The following code is written in C# 7.3 and should be able to store every image from the website to the disk. The thing is, I can't do that because the data parameter is not byte[], but string.
    class Program
    {
        static string[] imageMimeTypes = { "image/jpeg", "image/png", "image/webp", "image/bmp", "image/gif" };

        static async Task Main(string[] args)
        {
            await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision);
            var browser = await Puppeteer.LaunchAsync(new LaunchOptions
            {
                Headless = true
            });
            var page = await browser.NewPageAsync();
            page.Response += Page_Response;

            await page.GoToAsync("https://anywebsite.that.contains.images");
        }

        private static void Page_Response(object sender, ResponseCreatedEventArgs e)
        {
            string contentType = null;

            if (e.Response.Headers.ContainsKey("content-type"))
                contentType = (string)e.Response.Headers["content-type"];

            if (e.Response.Headers.ContainsKey("Content-Type"))
                contentType = (string)e.Response.Headers["Content-Type"];

            if (imageMimeTypes.Any(t => t == contentType))
            {
                string fileName = null;
                var lastSlashIndex = e.Response.Url.LastIndexOf('/');
                if (lastSlashIndex != -1)
                    fileName = e.Response.Url.Substring(lastSlashIndex + 1);
                else
                    fileName = e.Response.Url;

                e.Response.BufferAsync().AsTask().ContinueWith(async (data) =>
                File.WriteAllBytes($@"c:\Temp\{fileName}", await data));
            }
        }
    }
...

Expected behavior:
Should be able to store base64 encoded images to disk in a raw byte form
Actual behavior:
Can't do that, because current implementation converts both utf8 and base64 strings to string which corrupts the image data.
Versions

Which version of PuppeteerSharp are you using?
1.9.0
Which .NET runtime and version are you targeting? E.g. .NET framework 4.6.1 or .NET Core 2.0.
.NET Core 2.1

Additional Information
N/A

Good catch @miroslavp. I'll take a look at it.


The value of similarity matrix may be wrong

Chapter8 Collaborative filtering in the neighborhood
8.4 Amazon's algorithm to precalculate item similarity
Sim("MIB", "ST") was 0.016 with the following calculation .

However, in the Similarity matrix explained later, a completely different value is set, Sim (MIB, ST) is 0.63.
Table 8.4

.

I've noticed the same issue. Have you figured out?


[Issue-3468] Improve condition for Marketing campaign

Pr for issue #3468

🚀 Deployed on https://pr-3471--sw-web-runner.netlify.app


Neka-separate searchbar form as component

What type of PR is this? (check all applicable)

[ ] Feature
[ ] Refactor
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[x] Other (please specify here: )

Description of what this Pull Request does
Separate search bar form as individual component
Related Tickets & Documents

Closes #55
Closes #62
Related Issues:

QA Instructions, Screenshots, Recordings

Added/updated tests?

[ ] Yes
[ ] Not Yet, and here is why: explain here
[ ] I need help with tests
[x] No, and here is why: Have not started using tests

Hey @istoga Remember to add a screenshot of the component to the description. Also, if you have time it would be good if you could highlight each suggestion in a color to indicate that the mouse is hovering :). Maybe when you get to working on the final design

@jjleigh @annonymousauthority can someone please approve and merge this PR for me? Thanks in advance!


Minor testfix for "should endWith"-tests

Really just a small fix.
There were two cases in which the "should endWith"-test used startWith instead of endWith

Thanks.


fix list-dependencies option

bug report
https://bugs.launchpad.net/kolla/+bug/1606450

Thank you for contributing to openstack/kolla!
openstack/kolla uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


To-do's

Need black metal pick-axed for the meadows base
Bees in the farm
Monolith gates for all base entrances.

Completed


Set ventilation off does not work

Hi
I have a ventilation unit which I control with cmd4. The set from 0% to 100% does work well!. However when I shutdown (or 0%) the ventilation button in Homekit the script is not triggered. I can see "[1/19/2022, 8:55:44 AM] [Cmd4] Setting (Cached) Ventilatie On false" in the Homebridge logs. Is this something related to a cache setting?
v1.3.9
Timezone	GMT+0100
OS	Raspbian GNU/Linux Buster (10)
Node.js Version	v14.18.3
Npm Version	v6.14.15
{             "platform": "Cmd4",             "name": "Cmd4",             "outputConstants": false,             "accessories": [                 {                     "type": "Fan",                     "displayName": "Ventilatie",                     "on": "TRUE",                     "rotationDirection": "CLOCKWISE",                     "rotationSpeed": 100,                     "name": "Ventilatie",                     "manufacturer": "VENTRO",                     "model": "VENTRO-275",                     "polling": [                         {                             "characteristic": "rotationSpeed",                             "interval": 10,                             "timeout": 9000                         }                     ],                     "serialNumber": "2894745",                     "outputConstants": true,                     "stateChangeResponseTime": 3,                     "state_cmd": "/opt/ventilatie.sh"                 } }

Never mind. The on characteristic should be defined...

Hmmmm
Now I see
[1/19/2022, 10:24:45 AM] [Cmd4] getValue: On function for: Ventilatie returned an empty string "". Perhaps your device is busy?
in the logs. I indeed do not return anything on this because the only relevant char is rotationSpeed. When setting rotationSpeed to 0 it is off. Is there a way to handle this?

Never mind again ;-) Fixed it, bug in my script

closed

Hi,
Sorry, I have been indisposed for awhile. Now that I know of this, I will
investigate.
Ttyl,
John
On Wed, Jan 19, 2022 at 3:05 AM arkadicolson @.***>
wrote:

Hi
I have a ventilation unit which I control with cmd4. The set from 0% to
100% does work well!. However when I shutdown (or 0%) the ventilation
button in Homekit the script is not triggered. I can see "[1/19/2022,
8:55:44 AM] [Cmd4] Setting (Cached) Ventilatie On false" in the Homebridge
logs. Is this something related to a cache setting?
v1.3.9
Timezone GMT+0100
OS Raspbian GNU/Linux Buster (10)
Node.js Version v14.18.3
Npm Version v6.14.15
{ "platform": "Cmd4", "name": "Cmd4", "outputConstants": false,
"accessories": [ { "type": "Fan", "displayName": "Ventilatie", "on":
"TRUE", "rotationDirection": "CLOCKWISE", "rotationSpeed": 100, "name":
"Ventilatie", "manufacturer": "VENTRO", "model": "VENTRO-275", "polling": [
{ "characteristic": "rotationSpeed", "interval": 10, "timeout": 9000 } ],
"serialNumber": "2894745", "outputConstants": true,
"stateChangeResponseTime": 3, "state_cmd": "/opt/ventilatie.sh" } }
—
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/123, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3ANG4XCUMHHZJ6653UWZWGJANCNFSM5MJG4M2Q
.
You are receiving this because you were assigned.Message ID:
@.***>

Hi,
So you had closed this and I never noticed.  I think you figured out that
"On" was not polled, thus always retrieved from cache.
Ttyl,
John
On Wed, Feb 9, 2022 at 4:46 AM John Talbot @.***> wrote:

Hi,
Sorry, I have been indisposed for awhile. Now that I know of this, I will
investigate.
Ttyl,
John
On Wed, Jan 19, 2022 at 3:05 AM arkadicolson @.***>
wrote:

Hi
I have a ventilation unit which I control with cmd4. The set from 0% to
100% does work well!. However when I shutdown (or 0%) the ventilation
button in Homekit the script is not triggered. I can see "[1/19/2022,
8:55:44 AM] [Cmd4] Setting (Cached) Ventilatie On false" in the Homebridge
logs. Is this something related to a cache setting?
v1.3.9
Timezone GMT+0100
OS Raspbian GNU/Linux Buster (10)
Node.js Version v14.18.3
Npm Version v6.14.15
{ "platform": "Cmd4", "name": "Cmd4", "outputConstants": false,
"accessories": [ { "type": "Fan", "displayName": "Ventilatie", "on":
"TRUE", "rotationDirection": "CLOCKWISE", "rotationSpeed": 100, "name":
"Ventilatie", "manufacturer": "VENTRO", "model": "VENTRO-275", "polling": [
{ "characteristic": "rotationSpeed", "interval": 10, "timeout": 9000 } ],
"serialNumber": "2894745", "outputConstants": true,
"stateChangeResponseTime": 3, "state_cmd": "/opt/ventilatie.sh" } }
—
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/123, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABSBCX3ANG4XCUMHHZJ6653UWZWGJANCNFSM5MJG4M2Q
.
You are receiving this because you were assigned.Message ID:
@.***>

Yes indeed, I figured it out myself as you say with polling ;-)
Best regards
Arkadi Colson
On 9/02/2022 19:39, John Talbot wrote:

WAARSCHUWING: Deze mail is afkomstig van buiten Smartbit. Klik niet
op links en open geen bijlagen, tenzij je deze mail verwacht en hij
afkomstig is van een betrouwbare bron.
Hi,
So you had closed this and I never noticed. I think you figured out that
"On" was not polled, thus always retrieved from cache.
Ttyl,
John
On Wed, Feb 9, 2022 at 4:46 AM John Talbot @.***> wrote:

Hi,
Sorry, I have been indisposed for awhile. Now that I know of this, I
will
investigate.
Ttyl,
John
On Wed, Jan 19, 2022 at 3:05 AM arkadicolson @.***>
wrote:

Hi
I have a ventilation unit which I control with cmd4. The set from 0% to
100% does work well!. However when I shutdown (or 0%) the ventilation
button in Homekit the script is not triggered. I can see "[1/19/2022,
8:55:44 AM] [Cmd4] Setting (Cached) Ventilatie On false" in the
Homebridge
logs. Is this something related to a cache setting?
v1.3.9
Timezone GMT+0100
OS Raspbian GNU/Linux Buster (10)
Node.js Version v14.18.3
Npm Version v6.14.15
{ "platform": "Cmd4", "name": "Cmd4", "outputConstants": false,
"accessories": [ { "type": "Fan", "displayName": "Ventilatie", "on":
"TRUE", "rotationDirection": "CLOCKWISE", "rotationSpeed": 100, "name":
"Ventilatie", "manufacturer": "VENTRO", "model": "VENTRO-275",
"polling": [
{ "characteristic": "rotationSpeed", "interval": 10, "timeout":
9000 } ],
"serialNumber": "2894745", "outputConstants": true,
"stateChangeResponseTime": 3, "state_cmd": "/opt/ventilatie.sh" } }
—
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/123, or
unsubscribe

https://github.com/notifications/unsubscribe-auth/ABSBCX3ANG4XCUMHHZJ6653UWZWGJANCNFSM5MJG4M2Q

.
You are receiving this because you were assigned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/ztalbot2000/homebridge-cmd4/issues/123#issuecomment-1034076824,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABT22SFWEFN6A4WDURT4BDTU2KYGZANCNFSM5MJG4M2Q.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close
state.Message ID:
@.***>


Installed on Win7 - get fast scrolling window

Just installed on Win7. I ran the command in the readme -
zippydl -d https://xxxxx.zippyshare.com/v/xxxxxxxx/file.html

I get a fast scrolling window that shows this command line over and over. Any tips on what's  happening?

can you give me screenshot ??
please check url zippyshare that file exist

Here is a screenshot -

try to open with Windows PowerShell

I've never used powershell, should it work different than cmd?

just to make sure the bug is not in the cmd


Pulsing Text

Windows Terminal version
1.21.3231.0
Windows build number
10.0.19045.0
Other Software
No response
Steps to reproduce
Open Terminal
Expected Behavior
Not pulsing
Actual Behavior

Not sure what causes this, but turning on Software Rendering stops the pulsing text.  Terminal is the only application this happens with, regular PS, CMD, WSL, etc all work fine.
nvidia 3060 with latest drivers

I forgot to note: The pulsing stops while the window loses focus.

Well, that's odd. Can you please do the following?

Update to the latest drivers:

Regular (recommended): https://www.nvidia.com/en-us/drivers/details/235904/
For improved stability: https://www.nvidia.com/en-us/drivers/details/235906/

Reboot
Make a screen recording. I can recommend:

Simple: https://github.com/mmozeiko/wcap
More powerful: https://getsharex.com/
Built into Windows: Search for "Snipping Tool"

Good news.  I've narrowed the problem to an... incompatibility? with Wallpaper Engine.
As I was preparing to take more recordings, I maximized a explorer window to use as a background and the pulsing text stopped.
Doing that paused Wallpaper Engine animations, for whatever reason it interferes with Terminal.

Thanks for digging in more! I wonder what's up with that... and if there's anything we can do about it.


Run tests on Windows 2019

#1830 fyi I tried this previously

Thanks, this is specifically to reproduce a bug that only occurs on older Windows versions.


rancher-agent - not recognising self-signed certificate - x509: certificate has expired or is not yet valid

BUG

Successfully started a Rancher server on a docker, but unable to neither

import an existing Kubernates cluster on a local VM environment
    NOR

unable successfully initiate rancher-agent on a plain node to create a new cluster.

In both the cases, the rancher-agent is unable to register or communicate with the server due to "x509: certificate has expired or is not yet valid" error.
Example error log in case of docker based agent installation on a new node:
time="2020-02-14T22:48:25Z" level=info msg="Connecting to wss://rancher.devdomain.com/v3/connect/register with token lbgrlgncrmcm4729kkw5mxjcrg7wq97flcwpwwtr624gxggh64xq68"
time="2020-02-14T22:48:25Z" level=info msg="Connecting to proxy" url="wss://rancher.devdomain.com/v3/connect/register"
time="2020-02-14T22:48:25Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="x509: certificate has expired or is not yet valid"
time="2020-02-14T22:48:25Z" level=error msg="Remotedialer proxy error" error="x509: certificate has expired or is not yet valid"

Steps to reproduce (least amount of steps as possible):
Step 1: Start the rancher instance
docker run -d --restart=unless-stopped \
	-p 80:80 -p 443:443 \
	rancher/rancher:latest

Step 2: Login to rancher admin UI
Step 3: Add a new cluster by selecting either install agent on VM node or importing existing cluster.
sudo docker run -d --privileged --restart=unless-stopped --net=host -v /etc/kubernetes:/etc/kubernetes -v /var/run:/var/run rancher/rancher-agent:v2.3.5 --server https://rancher.devdomain.com --token lbgrlgncrmcm4729kkw5mxjcrg7wq97flcwpwwtr624gxggh64xq68 --ca-checksum f34af2e0e4a88872bde8d1fa88485a185534577925f1fed222650c15c3a27732 --node-name master --internal-address <IP_ADDRESS> --etcd --controlplane --worker
Result:
On the rancher-agent docker logs:
INFO: Arguments: --server https://rancher.devdomain.com --token REDACTED --ca-checksum f34af2e0e4a88872bde8d1fa88485a185534577925f1fed222650c15c3a27732 --node-name master --internal-address <IP_ADDRESS> --etcd --controlplane --worker
INFO: Environment: CATTLE_ADDRESS=<IP_ADDRESS> CATTLE_INTERNAL_ADDRESS=<IP_ADDRESS> CATTLE_NODE_NAME=master CATTLE_ROLE=,etcd,worker,controlplane CATTLE_SERVER=https://rancher.devdomain.com CATTLE_TOKEN=REDACTED
INFO: Using resolv.conf: search lan kube.devdomain.com nameserver <IP_ADDRESS> nameserver <IP_ADDRESS>
INFO: https://rancher.devdomain.com/ping is accessible
INFO: rancher.devdomain.com resolves to <IP_ADDRESS>
INFO: Value from https://rancher.devdomain.com/v3/settings/cacerts is an x509 certificate
time="2020-02-14T22:55:06Z" level=info msg="Rancher agent version v2.3.5 is starting"
time="2020-02-14T22:55:06Z" level=info msg="Option worker=true"
time="2020-02-14T22:55:06Z" level=info msg="Option requestedHostname=master"
time="2020-02-14T22:55:06Z" level=info msg="Option customConfig=map[address:<IP_ADDRESS> internalAddress:<IP_ADDRESS> label:map[] roles:[etcd worker controlplane] taints:[]]"
time="2020-02-14T22:55:06Z" level=info msg="Option etcd=true"
time="2020-02-14T22:55:06Z" level=info msg="Option controlPlane=true"
time="2020-02-14T22:55:06Z" level=info msg="Listening on /tmp/log.sock"
time="2020-02-14T22:55:11Z" level=info msg="Connecting to wss://rancher.devdomain.com/v3/connect/register with token lbgrlgncrmcm4729kkw5mxjcrg7wq97flcwpwwtr624gxggh64xq68"
time="2020-02-14T22:55:11Z" level=info msg="Connecting to proxy" url="wss://rancher.devdomain.com/v3/connect/register"
time="2020-02-14T22:55:12Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="x509: certificate has expired or is not yet valid"
time="2020-02-14T22:55:12Z" level=error msg="Remotedialer proxy error" error="x509: certificate has expired or is not yet valid"
time="2020-02-14T22:55:22Z" level=info msg="Connecting to wss://rancher.devdomain.com/v3/connect/register with token lbgrlgncrmcm4729kkw5mxjcrg7wq97flcwpwwtr624gxggh64xq68"
time="2020-02-14T22:55:22Z" level=info msg="Connecting to proxy" url="wss://rancher.devdomain.com/v3/connect/register"
time="2020-02-14T22:55:22Z" level=error msg="Failed to connect to proxy. Empty dialer response" error="x509: certificate has expired or is not yet valid"
time="2020-02-14T22:55:22Z" level=error msg="Remotedialer proxy error" error="x509: certificate has expired or is not yet valid"

Environment information

Rancher version rancher/rancher:latest

Cluster information

Cluster type (Custom/Imported):

Machine type (VM)

Docker version (use docker version):
Client: Docker Engine - Community
Version:           19.03.6

It was due to time sync issue between the rancher server and other agent nodes.  After syncing the time the problem was resolved.


Lwjgl3: GL3 core profile hint only mandatory on OS X.

Fixes #3932.

Thanks!

The Mesa drivers on Linux do not support Compatibility Profile GL either, but do support Core Profile GL4+ (depending on the driver, GPU, and mesa version).


Todo's not recognized in .jsx files

Title says it all. Any simple way to resolve?

Sure, You can add...
languages: {
  ".jsx":          {"name": "jsx", "symbol": "//", "block": cBlock}
}

to .imdone/config.json or you could just wait a few minutes and I'll add it to languages.js. :sunglasses:

Done!  It's in 1.1.45.

Nice, thanks for the update.


Add support for MDCSS

Generated style guide.
https://github.com/jonathantneal/mdcss

Skipping this, seems cool but unnecessary for the types of projects this is used on.


Replace __id parameters with id

We merged https://github.com/artsy/metaphysics/pull/1756 today, but needed to update emission to remove __id references.
Things I did:

Find and replace __id with id
Sync schema

Fails

:no_entry_sign:
No CHANGELOG added.

:no_entry_sign:
Missing Test Files:

src/lib/Components/ArtworkGrids/RelayConnections/__tests__/ArtistForSaleArtworksGrid-tests.tsx
src/lib/Components/ArtworkGrids/RelayConnections/__tests__/ArtistNotForSaleArtworksGrid-tests.tsx
src/lib/Components/FilteredInfiniteScrollGrid/__tests__/ArtworksGridPaginationContainer-tests.tsx

If these files are supposed to not exist, please update your PR body to include "#skip_new_tests".

  Generated by :no_entry_sign: dangerJS


CLOUDSTACK-8721: Fixed Setting details of VM through API results in removal of all other details except the one passed in API

cloudstack-pull-requests #945 failure is because of some random error in git fetching

@anshul1886 I want to test this but haven't used the 'details' feature before. In what format am I supposed to send the key/value pairs? If you have a CloudMonkey or Marvin example, that would be great. I'll then verify it in my lab. Thanks!

@remibergsma Using cloudmonkey we can pass as shown below
update virtualmachine id=00f19661-da81-40b2-a07c-e46967421195 details[0].keyboard=fr
Here detail which we want to update has key "keyboard" and its value is "fr"
And using API
http://localhost:8096/api/?command=updateVirtualMachine&id=00f19661-da81-40b2-a07c-e46967421195&details[0].keyboard="fr"

Thanks @anshul1886 will test it soon.

@anshul1886 Tested your code, works just fine! LGTM.
The only thing I noticed: excisting key/values are removed, then added again. So the net result is OK. It just inserts them again (the auto-increment goes up) but that wasn't introduced by your code as far as I can see.

Ping, update on this?

@bhaisaab What else is needed here?

@anshul1886 can you read and reply to some of the comments?

@bhaisaab Lost in discussion and got only end result that all we need is here.

@anshul1886 the only concern here is that this sort of breaks the API behaviour as in the past the details would set details (removing old details).
LGTM; we can merge once anyone else can review/test this.

@remibergsma @bhaisaab Remi has already tested this and has given the LGTM.

ah, I see merging now :)


Fix fatal syntax

Hi there!
The fatal syntax here was incorrect and made the Morty tool unhappy (cf. this issue). This should fix it. Not tested.

LGTM. I'm merging this into dev, will be part of the upcoming master release


linja: Add option to hard-code the path to ninja

We are currently working on a new version (branch lean3). It does not depend on ninja anymore.


Using exp to create exponentials causes error?

As mentioned in issue #272, using the smart constructor exp in the following manner is causing the following error:

For now, GlassBR uses the following to get the correct result:  ae50e45.
Need to find out why exp (defined in Expr.hs) cannot be used in this context.

I have a feeling I know what the problem is and will take care of it as soon as I'm back from my appointment.


TypeError: Uncaught error: Future#fork expected the computation...

This looks similar to this issue in Futurize: Return void from computation
I'm getting this when I try to run the fourInstableFutures example from the Readme.md.
Here's the original code that throws the error (copied and pasted from Readme.md):
const fourInstableFutures = Array.from(Array(4).keys()).map(
  i => Future(
    (rej, res) => setTimeout(
      () => Math.random() > 0.8 ? rej('failed') : res(i),
      20
    )
  )
);

const stabalizedFutures = fourInstableFutures.map(Future.fold(S.Left, S.Right))

Future.parallel(2, stabalizedFutures).fork(console.error, console.log);

Putting void in front of setTimeout makes the error go away:
const fourInstableFutures = Array.from(Array(4).keys()).map(
  i => Future(
    (rej, res) => void setTimeout(
      () => Math.random() > 0.8 ? rej('failed') : res(i),
      20
    )
  )
);

const stabalizedFutures = fourInstableFutures.map(Future.fold(S.Left, S.Right))

Future.parallel(2, stabalizedFutures).fork(console.error, console.log);

Thanks for the heads-up! That piece of the documentation has been written before cancellation was introduced. I'll update the example!


[release-0.12] Removing initial slow cloudmonkey call to verify connection to cloudstack

Issue #, if available:
Description of changes:
Manually cherrypick changes from #4016 into release branch to unblock e2e tests
Testing (if applicable):
Unit tests pass
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Program running problem using C# API

@comeCU commented on Wed Aug 08 2018
[When I used this C# API on visual studio2017, he threw these exceptions, I was very confused and hoped to give me some help. Here are some exception screenshots:]

⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: 021ecbd2-8976-64a4-ca95-0009a1c02692
Version Independent ID: 47011e64-0198-6fac-cd07-0334f350f59c
Content: 使用自定义影像服务预测终结点 - Azure 认知服务
Content Source: articles/cognitive-services/Custom-Vision-Service/use-prediction-api.md
Service: cognitive-services
GitHub Login: @anrothMSFT
Microsoft Alias: anroth

Hi team,
I moved this one here because the user is having issues with the code.

@CeciAc Hi, I can not reproduce that bug, it works for me well. So I don't thinks there is something wrong with the source code. For making it clearer, can you please provide more information about this issue? Thanks a lot!

@YutongTie-MSFT Hi,thank you for your help.This is my test code as shown in the C# API,I want to get a json data.
Operating environment：visual studio 2017

using System;
using System.IO;
using System.Net.Http;
using System.Net.Http.Headers;
using System.Threading.Tasks;

namespace CSPredictionSample
{
    static class Program
    {
        static void Main()
        {
            Console.Write("cc05.jpg");	// my image file
            string imageFilePath = Console.ReadLine();

            MakePredictionRequest(imageFilePath).Wait();

            Console.WriteLine("\n\n\nHit ENTER to exit...");
            Console.ReadLine();
        }

        static byte[] GetImageAsByteArray(string imageFilePath)
        {
            FileStream fileStream = new FileStream(imageFilePath, FileMode.Open, FileAccess.Read);
            BinaryReader binaryReader = new BinaryReader(fileStream);
            return binaryReader.ReadBytes((int)fileStream.Length);
        }

        static async Task MakePredictionRequest(string imageFilePath)
        {
            var client = new HttpClient();

            // Request headers - replace this example key with your valid subscription key.
            client.DefaultRequestHeaders.Add("Prediction-Key", "***");	//my Prediction-Key

            // Prediction URL - replace this example URL with your valid prediction URL.
            string url = "***";	//my Prediction URL

            HttpResponseMessage response;

            // Request body. Try this sample with a locally stored image.
            byte[] byteData = GetImageAsByteArray(imageFilePath);

            using (var content = new ByteArrayContent(byteData))
            {
                content.Headers.ContentType = new MediaTypeHeaderValue("application/octet-stream");
                response = await client.PostAsync(url, content);
                Console.WriteLine(await response.Content.ReadAsStringAsync());
            }
        }
    }
}

@CeciAc @YutongTie-MSFT Ah, I got it, I made a mistake, maybe I should learn C#. Anyway, thank you very much!

@comeCU @CeciAc Glad to hear your problem solved! Thanks for feedback here. I am closing the issue, please feel free to reopen it if you have further issues.


Hot reloading issues fixed

Moved react-hot-loader to the top component
i18n seperated into two for components to access directly without creating dependency to json files.
ConnectedApp function bug fixed.

Following the hot-loading issues at #2793 @julienben
I worked on react-hot-loader a year ago as I was asking questions on how to do it #2255 here :) My experience on it I can tell several things

React Hot Loader isn't necessary actually. HMR works just as fine without it. It helps you to preserve states only. See this. With hooks in the game it might be be needed more so included in this pull request. I didn't keep track on what is changed in hot loaders lately. So considering it might be helpful it won't hurt to use it.

Changes in the json translation files also aren't hot loaded in master branch either. When I debugged it, it turns out React Components depending on i18n.js file ruining it. Because json files are updated and HMR sees that LanguageProvider uses it but LanguageProvider doesn't declare how to handle it. So i separated dependencies into two files. Now app.js only depends on i18n.js and module.hot.accept expects it.

Issue with lazy loading (code-splitting). With the current code splitted components react-hot-loader has no benefit over webpack HMR. Because of this. In my tests when the lazy component is hot loaded it does render the component again firing useEffect((), []) hook, and other non-zero dependency hooks. Basically what HMR does alone. If you make components not lazy loaded it works super fine. Zero dependency hooks aren't fired.

Note: I just added a file called locales.js to separate the dependency on i18n.js file. Better naming could be possible or putting it in some file else.

Number 1: A year ago I was troubled with it too and decided not to use it. Since HMR almost does the same job. But RHL has benefits like hooks states etc. The catch here is we cannot see those benefits with lazy loaded components. My opinion we keep RHL in case people are not lazy loading their components (not dynamically importing) and they wanna use full featured hot reloading stuff with hooks.
ps: RHL's react-dom extension displays the hot loading errors in the view instead of the console. Which is much better because people will immediately see the errors if hot reloading isn't working as expected.
Number 2: Thanks :))
Number 3: For me I think its working as like other hot loaded components
Hmm I dont see it happening. I see console logs like
[HMR] Checking for updates on the server...
process-update.js?e135:125 [HMR] Updated modules:
process-update.js?e135:127 [HMR]  - ./app/translations/en.json
process-update.js?e135:127 [HMR]  - ./app/i18n.js
process-update.js?e135:132 [HMR] App is up to date.

It keeps the state. For instance github user input field is preserved. You will see a github users reloading action because of the useEffect hook. As I mentioned due to the lazy loaded components hooks fire again and causes load_repo action. It gives a feeling of full page reload. Can you double check ? (or do you mean by 'full page reload' like re-rendering the component? For me, it means like refreshing a browser page)
Number 4: Ok sure i will. I missed that totally ;)

Coverage remained the same at 100.0% when pulling 43726529dba536f47cf48b452dc156786d15e7c4 on Can-Sahin:hot-reloading-fixes into 27538f1595620b235eae2ae4251305da82dc386a on react-boilerplate:dev.

oh yeah i missed that tiny changes. I just did :)

If you look at .travis.yml, you'll see that we run generate-templates-for-linting.js before testing in Travis. It's a way to check that the generators are putting out valid code. One of the steps there is to add 'fr' as a language. After we finish though, the files are restored as they were before.

As you can see it's not backing up and restoring locales.js, hence the error you're seeing in Travis. I'm not sure where we decide which files to back up and restore. Looking into it on my side but either way it'll be an easy fix.

Got it. This is the fix:

Do that and Travis should work.


Prepare a kind-based kubernetes deployment script for our local tilt-based development environment

It would be nice to be able to deploy/destroy kind cluster (single and multi node) from a script, that then can be used to deploy aperture with tilt for local development.

This was done.


Question: How to load vector of struct with Env provider?

Question
I'm trying to read config with both the Yaml and Env provider.
I allow users to provide me a json string (which should be an array) in the environment variables. Yet, it doesn't work, because a string is received and it's not detected as a sequence.

(suggestion) Should Env provider use serde_json when reading a custom type?
Is there a better approach for this? I tried creating a custom deserializer, but it doesn't get called at all. Worth mentioning that my deserializer for an enum field is properly called, yet omitted in this example.

This works for simpler types.
pub struct Config {
    pub array: Vec<String>,
}

// where APP_ARRAY=[1,2,3]
// ends up as a vector containing ["1", "2", "3"]

While
#[derive(Clone, Debug, PartialEq, Deserialize)]
pub enum SomeEnum {
     First,
     Second,
}

#[derive(Clone, Debug, PartialEq, Deserialize)]
pub struct Item {
     pub name: String,
     pub inner_enum: SomeEnum
}

#[derive(Debug, PartialEq, Deserialize)]
pub struct Config {
    pub array: Option<Vec<Item>>,
}

Would fail when loading it:
#[test]
    fn test_from_env() {
        figment::Jail::expect_with(|jail| {
            jail.clear_env();
            jail.set_env(
                "APP_ARRAY",
                r#"[{"name":"first-name","inner_enum":"First"},{"name":"second-name", "inner_enum":"Second"}]"#,
            );
            let config = Figment::new().merge(Env::prefixed("APP_")).extract().expect("should work");
            assert_eq!(
                config,
                Config {
                    array: Some(vec![
                        Item { name: "first-name".to_string(), inner_enum: SomeEnum::First },
                        Item { name: "second-name".to_string(), inner_enum: SomeEnum::Second }
                    ]),
                }
            );
            Ok(())
        });
    }

thread 'config::tests::test' panicked at src/config/mod.rs:...:
should parse config: ParseError("invalid type: found string \"[{...omitted...}]\", expected a sequence for key \"ARRAY\" in `APP_` environment variable(s)")

I ended up doing the following and it worked, but I'm not sure if this is the recommended solution:
// ... omitted code

fn deserialize_array<'de, D>(deserializer: D) -> Result<Option<Vec<Item>>, D::Error>
where
    D: Deserializer<'de>,
{
    // Deserialize the JSON value using serde_json::Value
    let value: JsonValue = Deserialize::deserialize(deserializer)?;

    match value {
        JsonValue::String(s) => {
            let values: Vec<Item> = serde_json::from_str(&s).expect("should have been serialized");
            return Ok(Some(values));
        }
        JsonValue::Array(a) => {
            let mut values = Vec::new();
            for v in a {
                let item: Item = serde_json::from_value(v).expect("should have been serialized");
                values.push(item);
            }
            return Ok(Some(values));
        }
        _ => {
            return Ok(None);
        }
    }
}

#[derive(Debug, PartialEq, Deserialize)]
pub struct Config {
     #[serde(deserialize_with = "deserialize_array")]
     pub array: Option<Vec<Item>>,
}

// This now works for both
let path = config_directory.join("config.yaml");
let figment = Figment::new()
    .merge(Yaml::file(path))
    .merge(Env::prefixed("APP_"));

The syntax is documented here: https://docs.rs/figment/latest/figment/providers/struct.Env.html

Dict: in the form {key=value} (e.g, APP_VAR={key="value",num=10})
Array: delimited by [] (e.g, APP_VAR=[true, 1.0, -1])

Combine these to get: APP_ARRAY='[{name=foo,inner_enum=First},{name=bar,inner_enum=Second}]'


chore(deps): update shared deps to get new version of gax

Should fix race condition in Batcher.close() and add ability to extend UserAgent

Closing in favor of the automatic variant: #443


[MacOs][Bug][Terminal] sed: illegal option -- r before executing commands

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

VS Code Version: 1.71.0 - 784b0177c56c607789f9638da7b6bf3230d47a8c
OS Version: macOS 10.15.7

  System:
    OS: macOS 10.15.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 192.07 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.20.0 - ~/.nvm/versions/node/v14.20.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 6.14.17 - ~/.nvm/versions/node/v14.20.0/bin/npm

Steps to Reproduce:

Open the integrated terminal, then select the Terminal tab.
open a new terminal using bash.
The following message appears before executing  every command:

sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]

Example
$ echo 'hi'
sed: illegal option -- r
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]
hi

It's likely that this issue is caused by https://github.com/microsoft/vscode/commit/e55863c5c1fc4515bd99e9cd4fb415788000a8b1#diff-3d4a2862d6125445f81871e00c3b6d60fa24ef567bdf20c2a185f151a1f86129R125

The problem is indeed the sed -r in https://github.com/microsoft/vscode/blob/784b0177c56c607789f9638da7b6bf3230d47a8c/src/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh#L125
I guess that the fix should be to use just sed and Basic Regular Expressions. The command should be:
s/ *[0-9][0-9]*  *//
(two spaces before the last *).

Same issue at my side.

me too! has this problem

ugrasma erkek her seyi gordum ayip len sana bide
6 Eyl 2022 Sal 05:10 tarihinde mouday @.***> şunu yazdı:

me too! has this problem
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/159864#issuecomment-1237583272,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A2YGMKSGGAB3NENJ4XFS5TLV42R2DANCNFSM6AAAAAAQDCA7CQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

/duplicate https://github.com/microsoft/vscode/issues/159946

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

Any update on this?

Having the exact same issue.

Should i write the whole code as you typed? Should i put in users directory or where?

The fix for this is coming in 1.71.2, not sure on the release date currently.

In the meantime, you can use the setting "terminal.integrated.shellIntegration.enabled": false, to disable those freaking errors

The solution is to edit the file /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh on line 125 and use the -E flag instead of -r (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac -r is not a valid option, hence the issue.
(i.e.:)
			__vsc_current_command="$(builtin history 1 | sed -E 's/ *[0-9]+ +//')"

The solution is to edit the file /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh on line 125 and use the -E flag instead of -r (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac -r is not a valid option, hence the issue.
(i.e.:)  __vsc_current_command="$(builtin history 1 | sed -E 's/ *[0-9]+ +//')"

OK well done thank you

OK well done thank you
You're welcome :)

worked!!!
thanks

worked

This worked for me as well! Thank you so much!!!!!!!! This error was incredibly annoying!

worked well!!
Thank you so much!

Fantastic!

Thank you so much!! It's worked on my machine.

Glad that it helped you guys :)

thank you, it worked!

Still getting this problem on MacOS 10.14.6.
Any ETD for patch release?
Incredibly annoying.

Thanks.

The solution is to edit the file /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh on line 125 and use the -E flag instead of -r (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac -r is not a valid option, hence the issue.
(i.e.:)  __vsc_current_command="$(builtin history 1 | sed -E 's/ *[0-9]+ +//')"

OK well done thank you

Thanks.

Found solution, it helped me
https://stackoverflow.com/a/73601736/3977725

The solution is to edit the file /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/contrib/terminal/browser/media/shellIntegration-bash.sh on line 125 and use the -E flag instead of -r (since both serve the same purpose - enable use of extended regular expressions - on linux). On Mac -r is not a valid option, hence the issue.
(i.e.:)  __vsc_current_command="$(builtin history 1 | sed -E 's/ *[0-9]+ +//')"

Thank a lot
it Worked!

Thank you!!!

I can't reproduce it in 1.71.2 👍
Version: 1.71.2
Commit: 74b1f979648cc44d385a2286793c226e611f59e7


Fix map scale when changing the metric

As reported by several users including @samwebsite, the map scale is not working. A workaround has been deployed to make it fixed, and we need it to be dynamically updated as you change the metric.

Issue description fixed @samwebsite - that's progress.


elementHandle.screenshot clip object uses wrong y value

problem
calls to elementHandle.screenshot use the incorrect y value, resulting in invalid images
Steps to reproduce

scroll an element into view
get an element handle
call elementHandle.screenshot
observe chrome scroll to the top of the doc, at y: 0, and capture content from there

we use the boundingBox object as a input to clip, but when scrolled into view, boundingBox.y is ~0 (or a small value), and Page.screenShot seems to expect an absolute y value, from top of doc

example!  https://www.youtube.com/edit?video_id=TcGYq5d3n4c
puppeteer calls:
// Page.js
const result = await this._client.send('Page.captureScreenshot', { format, quality: options.quality, clip })

What is the expected result?

a screenshot of the requested element

What happens instead?

a screenshot of the correct dimensions, but at the top of my document, not over my actual element.
or, in other words, a screenshot of the correct dimensions in the viewport, BUT, the viewport has moved

ah ha!  see: https://chromedevtools.github.io/devtools-protocol/tot/Page/#type-VisualViewport
confirmed, pup's clip values need to be patched

... https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-captureScreenshot
^^ would be handy too :)

working on a PR now

see #1323

see #1323

My problem was i was setting the Viewport after goTo(), when change it it worked for me perfectly
`const puppeteer = require('puppeteer');
async function run(url) {
let browser = await puppeteer.launch({ headless: true });
let page = await browser.newPage();
const VIEWPORT = { width: 1360, height: 780}
boxes2 = [];
await page.setViewport(VIEWPORT);
await page.goto(url, { waitUntil: 'domcontentloaded'});
await page.waitFor('table');
await page.waitForSelector('table');
const el = await page.$$('table');
for(let i = 0; i < el.length; i++){
// await console.log(el[i].getBoundingClientRect());
await el[i].screenshot({
path: 'link_' +i+ '.png',
})
}
// await processScreens(el, page);
await page.close();
await browser.close();
}
const url = "https://github.com/puppeteer/puppeteer/issues/1315";
run(url);
`


More RecipientTypeDetails updates

Learn Build status updates of commit 46616a6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/Get-CASMailbox.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Get-User.md
:white_check_mark:Succeeded
View (exchange-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


update to discord.js v13

events are not properly getting reflected when players signup/withdrawal

first stab at support is done, hopefully .... let's test this puppy in the wild


cublas implemetation?

Duplicates

[X] I have searched the existing issues

Summary 💡
for llama, there's a flag called --gpu-layers N, basically oflloads some layers to the gpu for processing
Examples 🌈

from ooba
Motivation 🔦
since cpu is super slow, gpu would be nice

You have to set some environment variables before llama-cpp-python installation so that it get compiled with cublas support. Follow the instructions here: https://pypi.org/project/llama-cpp-python/


test: lwm2m: Raise POSIX_MAX_FDS for native_sim

LwM2M interoperability test binary requires a bit
more file descriptors than the default 4.
Interoperability tests got broken in PR https://github.com/zephyrproject-rtos/zephyr/pull/72834 this fixes it.

@SeppoTakalo could you rebase against latest upstream, it should fix the doc build failure.

Rebased


Interfaces for 2.0 (WinRM and Shell)

This is a proposal for 2.0, though it could be possible to add new interfaces in 1.4.x as long as the old interfaces are still around (possibly deprecated).
I think it'd be nice to add Shell and Command classes along with Output (added in #103). I hinted towards this in #114 (selecting FileManagers) and #103 (comparing w/ mixlib-shellout), so figured I'd write up an actual proposal.
The WinRM class would represent a WinRM connection. Once you have a connection you can create objects that will interact with that session, like winrm.file_manager (see example in #114) or winrm.shell:
winrm = WinRM.new(connection_opts)
default = winrm.shell
ps = winrm.shell(:powershell)
cmd = winrm.shell(:cmd)
wql = winrm.shell(:wql)
bash = winrm.shell(:bash) # Seems odd, but could be useful for WinRM->Cygwin

The default shell could be a generic or "multi-shell" for people that let's you switch back and forth between different shells, closer to backwards-compatible with the current interface. So these would all be equivalent:
# Option 1 - generic shell w/ cmd, powershell and wql commands
winrm.shell.powerscript(command)
# Option 2 - dedicated PowerShell
ps = winrm.shell(:powerscript)
ps.run(command)

However, since the Shell represents a session I think the second approach is a better usage pattern:

It would make it possible to implement shell-specific methods (on WinRM::Shell subclasses like WinRM::PowerShell), like PowerShell#import_module.
It could provide better session management. Hopefully instantiating a new WinRM::PowerShell would behave just like launching a new PowerShell window - variable assignments and imported modules will be remembered across commands within a session, but not across sessions:

session1 = winrm.shell(:powershell)
session2 = winrm.shell(:powershell)
session2.run('$foo = "bar"')
session1.run('Write-Host $foo') # nothing
session2.run('Write-Host $foo') # "bar"

session1.import_module(WinRM::PowerShellModules::Cryptography)
# re-usable powershell code shipped
# as a ruby module as a separate gem!
#
# Maybe even `session1.include(WinRM::PowerShellModules::Cryptography)`,
# so it could add both PowerShell modules and Ruby methods to the shell.
command = 'Encrypt-String "Something to encrypt" "P@ssw0rd"'
session1.run(command) # works
session2.run(command) # Encrypt-String not found...

In the example above, imagine that shell.import_module(WinRM::Extensions::Cryptography) imports this module into the powershell session.
I think all of this has a few advantages:

WinRM.new is easier to remember than WinRM:: WinRMWebService.new
You can add WinRM.new and leave WinRM:: WinRMWebService.new as a (possibly deprecated) backwards-compatible interface.
Allows custom shells, like Bash/CSH/ZSH for Cygwin, or Chocolatey.
A base Shell class with CmdShell, PowerShell, and WQLShell subclasses will be easier to read than having WQL code in WinRM::WinRMWebService.
The #shell method could allow for shell-specific features (like PowerShell#import_module in the example above).

Custom shell example that would make me :smile:
require "winrm/extensions/chocolatey"

chocolatey = winrm.shell(:chocolatey)
chocolatey.install_chocolatey unless chocolatey.installed?
chocolatey.install("git")

if chocolatey.installed? "ruby"
  ruby_version = chocolatey.version("ruby")
  puts "Time to upgrade Ruby?" unless ruby_version.found != ruby_version.latest
else
  chocolatey.install("ruby -x86")
  chocolatey.install("ruby2.devkit -x86")
end

Of course, in this case you may be better off with doing that all in PowerShell, but there's cases where something like that could be useful.

:+1: breaking apart WinRMWebService into multiple classes.
I like the idea of being able to open a PowerShell session and call run multiple times, however it might present some challenges getting the output back. Currently if you start a cmd/powershell process via WinRM and leave it running, the call to get the output will never finish. This is why in rwinrm we have a secondary thread that constantly polls for output from the WinRM service.

this was fixed via #191


Create a CustomElement definition

It should be possible to define <custom-element></custom-element> elements, and append them to other elements. We probably need to:

Define a new CustomElement type
Give it a constructor which takes a name
Enable it to define custom attributes
Enable all existing elements which have children to also take a CustomElement as a child

We should do this using Declarative Shadow DOM.
References

Declarative Shadow DOM | Chrome Developers
Experimental Spec
<template> tag on MDN
Declarative Shadow DOM | Webkit

Example
Given this HTML:
<host-element>
    <template shadowrootmode="open">

Shadow Content

        <slot></slot>
    </template>

Light content

</host-element>

We should be able to write this Rust code:
CustomElement::new("host-element")
    .template(|t| t
        .shadow_root_mode(ShadowRootMode::Open)
        .style("shadow styles)
        .h2(|h2| h2.text("Shadow Context"))
        .slot(|_|))
    .h2(|h2| h2.text("Light Content");

Added the "help wanted" label to this. This should be fairly self-contained, and probably a fun one to pick up.


Update DynamicPartitionKafkaRDD.scala

change config name spark.streaming.kafka.metadata to more meaningful mobius.streaming.kafka.CSharpReader.enabled

Current coverage is 75.58%

Merging #388 into master will increase coverage by +0.24% as of e8ca814

@@            master    #388   diff @@
======================================
  Files           46      46
  Stmts         4689    4689
  Branches       419     419
  Methods
======================================
+ Hit           3533    3544    +11
- Partial        179     180     +1
+ Missed         977     965    -12

Review entire Coverage Diff as of e8ca814

Powered by Codecov. Updated on successful CI builds.


Feature Request: Basic Load Balancer

Is your feature request related to a problem? Please describe.
For deployment to a custom VNET, allow usage of the basic load balancer.
Describe the solution you'd like.
For test setups and scenarios where there are many open ports which are not as busy, the basic load balancer can reduce the cost significantly. Especially considering that the 2 rules are already used for HTTP/HTTPS without question. Consider deployment of an app such as https://github.com/traccar/traccar with numerous ports open.
For production setup, the standard load balancer remains the recommended way and could also be the default.
Describe alternatives you've considered.
The only alternative is to deploy an AKS cluster but that results in lots of maintenance work.
Another alternative is to allow creation of public TCP apps without the VNET requirement which is not possible today.

Thanks @mburumaxwell, I've added this feature request to our backlog discussions.


Feature Request

Since Universal still isn't an option, maybe a Service Worker could improve loading time.
Google provides a module called Service Worker Precache, which you can find here:
https://github.com/GoogleChrome/sw-precache
It could be added to the webpack build process.

I'll look into this... just starting to experiment with service workers now.

I'm going to add this and push notifications in a few days, I'm already running it on my project, just want to be sure about the configuration before adding it to this starter. I'll probably also advise people in the readme to not to use the universal branches until Universal migrates over to core and angular 4 is released and stop updating those branches until then.

I'll leave people to add this themselves. Precache has a lot of drawbacks and I've stopped using it as it's very easy for clients to be stuck with a corrupt version of your site or for their browser to keep loading an old version of your site after you've made updates.


Update api.html

Fixed a type on where distinct was spelled "distict".

Thanks for pointing this out. api.html is generated code. The corresponding raw text is somewhere in the lib directory - if you can find it I'll be happy to merge the PR :)

Thanks for the tip on where to find it!


[Helper] copy paste ruestion.  not bug

env:
mac os all version
copy need Fn+mouse left. what need I doing if Iwant modify.

new est lib not support python2.7.    only modify pip3 ++>pip ,can work ?

Sorry, but I do not understand what your question is.

I want modify  copy word  from  mitm .    On macOS  the keymap this Fn+mouse left.  I want modify . what can I do?

update keymap

@mhils


Fix commit status cache which missed target_url (#30426)

Fix #30421
Backport #30426

Was automatic backport not possible here?

Was automatic backport not possible here?

Yes, both failed.

Interesting that the main branch has diverged here already.


WIP: port mermaid v10.0.3

Changelog:

Using mermaid 10.0.3 (alpha) 2,7MB
Reading from relative path rootPath + "mermaid-min.js"
On load error, fallback to remote location<EMAIL_ADDRESS>
TODO:

wait for final release of 10.0.3

mermaid v10.1 has been released without support for CommonJS modules; must port to ESM.


[CI] Upgrade gulp to v5

Closes #4225 by superseding it

Waiting on:

#4235

/fix:all

Works locally, and on GitPod, but not under GH actions :-/ ... will need to investigate further when I have the time. Putting in draft in the meantime.

Finally all green! Merging ✨


[DEV-12007] Fix - Adapt code to fresh @prezly/sdk

Initiated from #488

Hey @e1himself, can we merge this please? 🙏🏻


feat: pwa registration

Closes #637
Related to #716 #719
Description
I am new with CSP stuff, but I think this might be a clue https://qubyte.codes/blog/content-security-policy-and-service-workers.
TLDR; SW is not using image-src policy but using connect-src policy instead. Since we don't have connect-src it fallback to default-src wich is only limited to self / origin of the domain itself. So, it refuses to "connect"

Mas @zainfathoni tried to add Cloudinary url to script-src (at #719 ) but ofc it doesn't work, we need to add to connect-src.
So I tried to add res.cloudinary.com to connect-src and deploy to my personal netlify account for preview (yes, I'm dumb. brb making a Draft PR for deploy preview). And it works (and it caches cloudinary img assets)
https://hardcore-noyce-3b9626.netlify.app/

Current Tasks

[x] implement @mazipan PWA registration (#705 )
[x] Add CSP rules for cloudinary assets

PWA lighthouse report

Need help from @zainfathoni and others also to test the preview domain.
I believe the error can not be catch by Lighthouse test.
We need to check manually.

I just checked https://deploy-preview-762--wargabantuwarga.netlify.app/ and got mixed result.
Most images were successfully fetched and cached by the SW as intended.
Some other images (hero_banner and sembako-cta) were not.

I initially thought it had something to do with images rendered via Next's Image component, but the telemedicine banner, which also uses Image component, was fetched correctly.
🤔


The child process does not spawn successfully Error: spawn mongodump ENOENT

Description
Hi.
I have a GitHub Action set up to backup a database. This GitHub Action has been running for months without incident, but now it has stopped working.
After a bit of research I have found the problem. runs-on: ubuntu-latest was using Ubuntu 20.04 until last week but now use Ubuntu 22. This change causes the GitHub Action to fail (I tested this by modifying my code to use the previous Ubuntu version).
Working Action:

Non Working Action:

Error with Ubuntu 22:

Platforms affected

[ ] Azure DevOps
[X] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[X] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[ ] Windows Server 2022

Image version and build link
20221119.2
Is it regression?
20221027.1
Expected behavior
I expect that the GitHub Action should not fail or at least find a "migration guide" to adapt my code to the latest image of Ubuntu.
Actual behavior
The GitHub Action fail.
Repro steps
Execute the GitHub Action.
This is my code (just relevant parts)
name: Create a backup of the database

on:
  workflow_dispatch:
  schedule:
    - cron: '35 4 2-27/6 * *'
    - cron: '17 6 1 * *'

jobs:
  getBackup:
    runs-on: ubuntu-latest
    env:
      MONGO_URI: ${{ secrets.MONGO_URI }}
    steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v3
      with:
        node-version: '16'
    - run: npm install
    - run: npm run get_backup

	const timeout = 2 * 60 * 1000; // Two minutes
	const date = getDate();

	const backupChildProcess = spawn('mongodump', [
		`--uri=${databaseURI}`,
		`--archive=./backups/${date}.gz`,
		'--gzip'], { timeout: timeout });

	backupChildProcess.on('exit', (code, signal) => {
		if (code || signal) {
			logger.error(`child process exited with code ${code} and signal ${signal}`);
			core.setFailed(`child process exited with code ${code} and signal ${signal}`);
			return;
		}

		logger.info('The database has been successfully backed up');
		core.notice(`The database has been successfully backed up. Created file: ./backups/${date}.gz`);
	});

	backupChildProcess.on('error', (err) => {
		logger.error('The child process does not spawn successfully', err);
		core.setFailed('The child process does not spawn successfully');
	});

@marko-zivic-93 I've moved this issues from runner-images as it is purely setup-node or its toolcache, but not relevant to the image at all.

Hello @didaquis, thanks for you input we started to investigate the issue

@dmitry-shibanov What you want me to try is something like this?
jobs:
  getBackup:
    runs-on: ubuntu-latest
    env:
      MONGO_URI: ${{ secrets.MONGO_URI }}
    steps:
    - uses: actions/checkout@v3
    - uses: actions/setup-node@v3
    - run: npm install
    - run: npm run get_backup

I take this opportunity to comment that the script does work if I run it on my local machine using Node 16.

Hello @didaquis, we confirmed the problem is with  the ubuntu-22.04 image itself - it does not contain mongodb cli for some reason. Give us, please, a little more time to suggest the workaround.

@didaquis, you have to this step to your pipeline in order to have it running on 22.04
      - run: |
          sudo wget -qO - https://www.mongodb.org/static/pgp/server-6.0.asc | sudo apt-key add -
          sudo echo "deb [ arch=amd64,arm64 ] https://repo.mongodb.org/apt/ubuntu focal/mongodb-org/6.0 multiverse" | sudo tee /etc/apt/sources.list.d/mongodb-org-6.0.list
          sudo apt-get update
          sudo apt-get install -y mongodb-org
          mongodump --version

According to MongoDB docs mongodb is not supported on Ubuntu-22.04 but the quick test showed the snippet above still able to install mongo cli tools from the official mongo repo
@mikhailkoliada i'll reassign this ticket to you to handle the further modification of the runner image

I am closing this, mongodb for ubuntu 22.04 is not yet released (it is in beta) as soon as it is, we will add it to the images.

Hi @mikhailkoliada, just a question. It looks like Ubuntu 22 support is now official from MongoDB team. https://www.mongodb.com/docs/manual/tutorial/install-mongodb-on-ubuntu/#platform-support
Does that mean that mongodb is already included in the images?


Invalid type casting with parens

The following two expressions produce different results:
// @flow
var x = (1000: number);
var y: number = 1000;
x += 'test'; // NO ERROR
y += 'test'; // ERROR

7: y += 'test';
   ^ string. This type is incompatible with
5: var y: number = 1000;
          ^ number

Sanity check:
x();

6: x();
   ^ function call. Function cannot be called on
6: x();
   ^ number

This is expected. Since x has no type annotation, its type can change:
var x = (1000: number);

(x: number);

x += 'test';

(x: string);


Call to a member function resize() on null

I'm getting following error when using (webp: test.webp)

Call to a member function resize() on null
\site\plugins\kirby3-webp-master\snippets\webp.php:30

Kirby 4.0.0-rc.4
PHP 8.1.23

Thanks @afbora - i will archive this plugin now since Kirby supports WebP natively.

OK. I'll move to archived this plugin now for getkirby.com directory (will be removed when K4 released).


File names like cancelRequest(for/).md are not recognized by Jekyll

I'm trying to feed the Markdown files generated by swift-doc to Jekyll and it is not happy about certain file names.
~> bundle exec jekyll serve
Configuration file: /Users/kean/Develop/kean.github.io/_config.yml
            Source: /Users/kean/Develop/kean.github.io
       Destination: /Users/kean/Develop/kean.github.io/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
jekyll 3.8.5 | Error:  Invalid scheme format: cancelRequest(for

The name of the file in question is cancelRequest(for/).md. It was produced for a global function.

This should be fixed by the changes in #258.


Example jupyter notebook (Brightspace) → error: acceleration + cannonball_radiation_pressure

After a fresh (and wrinkle-free) install of TudatPy following Brightspace and readthedocs steps, I ran the example jupyter notebook from the Survey/Announcement on the NumAstro Brightspace page.
Upon execution, this immediately throws the error below, but if I’m not mistaken, the fix is easy:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-2-0f8b7fcdb525> in <module>
     78     Sun=
     79     [
---> 80         propagation_setup.acceleration.cannonball_radiation_pressure_(),
     81         propagation_setup.acceleration.point_mass_gravity()
     82     ],

AttributeError: module 'tudatpy.kernel.simulation.propagation_setup.acceleration' has no attribute ‘cannonball_radiation_pressure_'

Changing
propagation_setup.acceleration.cannonball_radiation_pressure_()
to
propagation_setup.acceleration.cannonball_radiation_pressure()
by removing the final underscore before the parentheses results in all the plots being produced as expected.
At the risk of borking things, I have already taken the liberty of removing the underscore and altering the source file on Brightspace. I believe, therefore that this issue can immediately be closed, but a second-opinion confirmation would be nice.

Problem with the code on brightspace, thanks for the reporting @transferorbit!