feat: artist artwork for small image

I changed/moved a lot of code because the main.go was getting a bit large, hope that's okay.
Happy to keep this in my fork if it isn't something you want for yourself. 😅

I also changed the labels for the images, the big image label is now the album name, the small image is the artist name (reflecting what both images represent).

this looks awesome, thank you!


any plan for supporting Net5?

No See.
https://github.com/JimBobSquarePants/ImageProcessor/issues/806#issuecomment-651039303


sys_clock.h: remove deprecated sys_clock_timeout_end_calc()

This has been deprecated and unused for a while.

Anyone can tell me what the failing compliance check is actually about?


Problem with react-schedule using this component

on react native with react-schedule-selector using styled components i have problem
TypeError: undefined is not an object (evaluating '_styledComponents.default.h2.withConfig')

This seems like a usage issue where your default export is styled-components, i.e. the web version and not styled-components/native. You can import from the latter if you're looking to use it with React Native explicitly.
Please refer with usage questions to Stack Overflow, as you're more likely to get quicker and helpful answers there ❤ Repository issues on GitHub are great for that, issues, things that need to be resolved in the library itself, or can't be resolved by anyone but the maintainers. While I (and many others on other repos) are happy to eventually answer usage questions, styled-components is a busy repo and mostly stable and slow moving towards new releases, so you're not likely to get fast responses here


chrome version 90 window.speechSynthesis.speak(msg) is not work

office live demo https://mdn.github.io/web-speech-api/speak-easy-synthesis/. is not work

the same ,not work
the code .......
if (synth.speaking) {
console.error('speechSynthesis.speaking');
return;
}

same here. chrome 89.x, firefox, opera and edge all work fine

In my project  ,  I have solved this problem .

use cancel method

can you show me code ?

https://stackoverflow.com/questions/67224912/speechsynthesis-speaking-api-is-not-fine-in-chrome-version-90

can you show me code demo ,see you page ,i find none

you should use speechSynthesis.cancel() before you use speechSynthesis speaking . if you test MDN Demo , you can run code speechSynthesis.cancel() on console.

In chrome 90.x I found MDN Demo sometimes work but sometimes not, and I tried adding speechSynthesis.cancel() in my project but it still doesn't work as expected...

in windows, some chrome 90.x is working, some chrome 90.x is not working.

https://stackoverflow.com/questions/67224912/speechsynthesis-speaking-api-is-not-fine-in-chrome-version-90

这个链接已经失效了，请问你是怎么解决的呢？
this URL has expired. can you tell me the resolve? thanks.

this should not be closed, it is still broken...


configure production deploy with xDai chain

add xDai protocol configuration for production to config to ready for production deploy
add point-to-point connections for every chain to config

done ✅


[QUESTION] How do I build macos Intel and simultaneously Apple Silicon

How do I build macos Intel and simultaneously Apple Silicon in action

Pass --target universal-apple-darwin to args, and it will build a universal, ie: Intel + Apple Silicon build.
You will likely need to install the appropriate arch support before that:
      - name: Install Rust x86_64 Support (macOS)
        run: rustup target add x86_64-apple-darwin

Pass --target universal-apple-darwin to args, and it will build a universal, ie: Intel + Apple Silicon build.
You will likely need to install the appropriate arch support before that:
      - name: Install Rust x86_64 Support (macOS)
        run: rustup target add x86_64-apple-darwin

Thanks Reply.
If you want to build x86_64-apple-darwin and aarch64-apple-darwin, you can refer to the following code,
jobs:
  release:
    permissions:
      contents: write
    strategy:
      fail-fast: false
      matrix:
        platform:
          # - os: ubuntu-latest
          #   rust_target: x86_64-unknown-linux-gnu
          - os: macos-latest
            rust_target: x86_64-apple-darwin
          - os: macos-latest
            rust_target: aarch64-apple-darwin
          # - os: windows-latest
          #   rust_target: x86_64-pc-windows-msvc
    runs-on: ${{ matrix.platform.os }}
	steps:
		- name: Rustup add target
			run: rustup target add ${{ matrix.platform.rust_target }}
		- name: Build the app
			uses: tauri-apps/tauri-action@v0
			with:
				args: "--target ${{ matrix.platform.rust_target }}"


:checkhealth makes the plugin look broken

When you run checkhealth efm-ls.nvim only shows errors, the oks are hidden
If you show OK "stylua": V1.0 etc it will give the happy feelings
Also if the executables aren't required for the plugin to function (e.g. phpcs shouldn't be needed when working in lua) then imo it should be a warning not an error

I will look into showing OK messages for tools that are in your system.


Updated tests for recoveryservices_backup

Added tests for list_jobs and get_jobs_details APIs with version 2017-07-01
Updated test record files
Added test for disable protection with retain data

@DheerendraRathor,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

Codecov Report

Merging #1355 into master will increase coverage by 0.1%.
The diff coverage is n/a.

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

Thanks @DheerendraRathor ! I release the package now


ng command not found in macOS

I installed angular using npm install -g @angular/cli. It was installed successfully, however, i am getting ng command not found error upon running. How do I solve this issue?

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


Improving MacOS M1 CPU/GPU prints

Description
Adding better support for Apple Silicon (M1) CPU and GPU prints
OLD:
CPU: Apple M1 Max
GPU: Apple M1 Max

NEW:
CPU: Apple M1 Max (10)
GPU: Apple M1 Max (24)

This is accurate for me as I have the 10c CPU and 24c GPU model
Features

Fix core-count not displaying on Apple Silicon (M1) devices (arm64)
Add GPU core count for Apple Silicon (M1) devices

Issues
TODO

(Although… for "GPU", I just see GPU: Apple M1 Max by default. Is there an option to test GPU core counts?)

Hmm... Interesting, it works for me to highlight the core count. You should be able to run this simple command and see what your machine returns:
chipset=$(system_profiler SPDisplaysDataType | awk '/Chipset Model/ { printf "%s %s %s", $3, $4, $5 }') && cores=$(system_profiler SPDisplaysDataType | awk '/Total Number of Cores/ { printf "%d", $5 }') && gpu="${chipset} (${cores})" && echo $gpu
For me, this returns Apple M1 Max (24)
Once this (pretty heavy) command gets run the first time, it gets cached into /Library/Caches/neofetch/gpu so the command doesn't need to be run again. So also try deleting this file and running ./neofetch again :)

Once this (pretty heavy) command gets run the first time, it gets cached into /Library/Caches/neofetch/gpu so the command doesn't need to be run again. So also try deleting this file and running ./neofetch again :)

Re-tested just now and this works great. Seems like the cache ought to be invalidated automatically in some cases (the neofetch script timestamp is greater than the cached value, so bugfixes actually take effect?) but I do in fact have 32 GPU cores:

Thank you for your contribution!
This PR is merged into hyfetch since this repo (dylanaraps/neofetch) seems no longer maintained.
HyFetch is a fork of neofetch with LGBTQ pride flags, but the repo also maintains an updated version of the original neofetch, addressing many pull requests that are not merged in the original repo.
Read the "Running Updated Original Neofetch" section for more info!

For some reason this is not working in my Mac :(

Any idea why I'm not seeing core count?


Bump Java's maximum version to 20

I haven't tried if it actually works - let's see what the CI says.

I would intuitively say that testing the lower and upper bounds are enough.
Or to diversify a bit we could take one of the two Java 20 jobs and turn it back into a Java 17 job (say, Linux with Java 17 and Windows with Java 20)?

I've just added a commit to change the E2E tests to use Java 17, so that we have a diversity of java versions (11, 17, 20) in the CI.


DC Address Inconsistency

Hey folks,
We've noticed that in the legislators-current.yaml file the address fields for DC offices are inconsistent w/r/t whether HOB is spelled or abbreviated. For example, sometimes address is given as "address: 511 Hart Senate Office Building Washington DC 20510" (Sherrod Brown) and in other cases "address: 114 Cannon HOB; Washington DC 20515-2203" (for Justin Amash).
I'm thinking of going through and standardizing them in the 511 Hart Senate Office Building Washington DC 20510 format, with "[House/Senate] Office Building" always spelled out. It seems pedantic but I've learned HOB is a term for us swamp creatures and not people outside the Beltway :)
I do notice you have scripts automatically updating the data, so I don't want to go through and standardize it only to have that mess with things (or get overwritten the next day).
Any thoughts on this?
Thanks,
Michele Hansen
Geocodio

Hi Michele! Good to see you on Github!
The address field comes in via a script and would be overwritten next time the script is used to collect the addresses. Do all House addresses use HOB and all Senate addresses spell it out? Or is it a mess?
We could add a simple string replacement at:
https://github.com/unitedstates/congress-legislators/blob/master/scripts/house_contacts.py#L71
to normalize it so all of the addresses spell it out. (I agree spelling it out would be a good idea.)
If it's that the House addresses are themselves inconsistent, we could also ask the House to clean up the data.

Hi Josh,
From doing a visual check, it looks like all House addresses use HOB in the address field (and "House Office Building" in the office field).
Looks like Senate always spells out Senate Office Building in all fields (for reasons that became understandable once I typed "SOB" into the search bar).
The string replacement, then, would probably do the job.

I've posted the change in PR #554. Thanks for the suggestion!

Thanks, Josh!
On Fri, Mar 9, 2018 at 3:03 PM, Joshua Tauberer<EMAIL_ADDRESS>wrote:

Closed #550
https://github.com/unitedstates/congress-legislators/issues/550 via #554
https://github.com/unitedstates/congress-legislators/pull/554.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/unitedstates/congress-legislators/issues/550#event-1514031790,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGKr1Ogn51utoWi3U8HVDcR_7S-XtTsHks5tcuAsgaJpZM4SHdBw
.

--
Michele Hansen


Fix attribute.critical type in PatientPlanSummaryResource

Fix type for PatientPlanSummaryResource.attributes.critical to be a free-form object and match following response type:
{
    effective_from: Date,
    effective_to: Date,
    blood_pressure: {
        data: {
            minimum: {
                systolic: {
                    value: Number
                },
                diastolic: {
                    value: Number
                }
            },
            maximum: {
                systolic: {
                    value: Number
                },
                diastolic: {
                    value: Number
                }
            }
        }
    },
    blood_glucose: {
        data: {
            minimum: {
                value: Number
            },
            maximum: {
                value: Number
            }
        }
    }
}

Free form object was used due to assumption that PatientPlanSummaryResource.attributes.critical is not limited to have only blood_glucose and blood_pressure metrics.
https://github.com/TwineHealth/TwineClient/issues/6124

@waisbrot It is an assumption. Model schema is an array which then transforms to a HashMap in response. Which keys are out of type control.
Business logic on client side (which manages critical metrics now) can be changed in future and some metrics can become critical which were not previously. This seems to me a disadvantage of specifying the values now. Since we couple client side business logic to the data which API could return.

Sorry, just a small correct on the first statement above regarding array to HashMap transformation. It's actually not a transformation. PatientPlanSummary API looks for the first item in critical item collection that corresponds a certain search criteria and returns it. But anyway managing critical metrics is on the Client end.


Dockstore quick start

Feature Request
Desired behaviour
Look for a good place to put a quick start based on https://github.com/ngs-docs/2017-cloud-workflows-misc/blob/master/install-and-run-with-dockstore.md in the documentation.
This is a good companion to #271 to be done at the same time.
Courtesy of @ctb

Related to #273 and #271

Parts of the cloud docs are now integrated with our quick start to make setup a bit easier/more intuitive.


[Outlook] (manifest) new preview JSON manifest

Docs Build status updates of commit b2bdb00:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

docs/toc.yml
:x:Error

Details

docs/quickstarts/outlook-quickstart-json-manifest.md
:warning:Warning

Details

docs/develop/json-manifest-overview.md
:bulb:Suggestion

Details

docs/toc.yml

Line 615, Column 4: [Error: yaml-syntax-error] While parsing a block mapping, did not find expected key.

docs/quickstarts/outlook-quickstart-json-manifest.md

Line 106, Column 48: [Warning: file-not-found - See documentation] Invalid file link: '../develop/create-addin-commands'.

docs/develop/json-manifest-overview.md

Line 74, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 99, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.
Line 112, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
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.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 7cfd80b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ebe9fbc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 012e571:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 078bf56:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5acdc18:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 0271d21:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 4ef7a6b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 45ab3c3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b09e2cb:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8d90bd3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 23f65df:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3be0222:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 2187ffc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 168e016:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 767759b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 1733c04:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 98b584f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 3c1de53:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 39f7efc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit a764fb2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 53a08de:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit e1ffc24:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit f06f962:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/develop/add-in-manifests.md
:white_check_mark:Succeeded
View

docs/develop/json-manifest-overview.md
:white_check_mark:Succeeded
View

docs/images/yo-office-outlook-json-manifest.png
:white_check_mark:Succeeded
View

docs/quickstarts/outlook-quickstart-json-manifest.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

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 docs.microsoft.com contributor guidesPost your question in the Docs support channel


System button with default title/change in runtime not localized correctly

Issue
System button with default title/change in runtime not localized correctly
Localize Environment

Localize version: (2.1.0)
Xcode version: 10.1 (10B61)
Swift version: 4.0
Platform(s) running Localize: iOS
macOS version running Xcode: 10.14.2 (18C54)

Localize Config
Localize.update(fileName: "Localization")
Localize.update(defaultLanguage: "en-US")
Localize.update(language: "en-VN")

What did you do?
I had a button (from storyboard) with default title is "Start Reading". In the runtime, that button can be change to "Resume chap.1" for example. It work perfect until I hit that button, the title fade to "Start Reading" instead of "Resume chap.1". The title only change when click and hold the finger on it, after releasing, it fade back to correct title "Resume..." The button I use is system type
Button type: Default system type
Default title: "Start Reading"
Runtime title: "Resume chap.1"
Click & hold button: Fade to "Start Reading"
Release button: Fade to "Resume chap.1"

Any update on this issue, guy?

Facing the same issue but on third party SDK button. Button string gets converted from Continue to <#Continue#>
Any update on this?

Hi, I have a similar problem, and the reason is that the Autolocalize Flag is set to the true, adding a button on the storyboard and connecting it to the code and settitle (.. for: .normal), even if I do it, it highlights the title written on the storyboard.


Update changelog to reflect the readdition of meta package

See b7f196d
Breaking Change
Is this a breaking change? Did you modify or delete any public APIs in such a way that the package user has to make changes in their code to upgrade to the new version?
No

Release failed 😕


Create a process for updating dependencies (from 118)

Problem Description:
The frontend does not have a process for updating packages based on vulnerabilities or on latest releases.
Expected Behavior/Solution:
A process for updating packages should be created.
Requirements:
TBD
Needed for promotion:
If an item on the list is not needed, it should be crossed off but not removed.

[ ] ~Wireframe/Mockup - Mike~
[ ] ~Committee discussions - Sarah~
[ ] ~Feasibility/Team discussion - Sarah~
[ ] ~Backend requirements - TBD~
[ ] Frontend requirements - Kam
[ ] Questions:
When to update packages?
What determines a package's priority to be updated (criticality, etc)?
What testing will be performed once a package is updated to ensure there are no dependency issues?

UAT/LUX Examples:
N/A
Dependencies/Blocks:
N/A
Related Github Issues:
N/A
Related links:
N/A
Wireframe/Mockup:
N/A

@kamerynB Do these questions need to be brought up at an IT meeting?

@roamye No they are more for me. I've been part of dev teams that have had processes in place for updating packages so that was me asking questions to myself on how I can use previous knowledge for this task. 😄

dev mtg 10/21:

one of the purposes of this issue is to eliminate any current/future security risks.

Yarn has a tool to help upgrade packages:
https://classic.yarnpkg.com/lang/en/docs/cli/upgrade-interactive/

@prowns @jffcamp I would like to discuss this in the next frontend meeting. I have a document outlining what this process should look like.

@prowns @jffcamp This issue is marked for review but does not require UAT review. The review will take place internally with Peter, Seong, and Xinjian.

Approved by UAT

unreviewable. closing as all issues in this milestone are in PROD.
@kamerynB


Import not working

[x] I confirm that this is an issue rather than a question.

Bug report
I replaced my old self compiled version with Alpha 5 on a fresh installed Rasbian and try to import my backup. Hyperion restarts but nothing is imported.
Steps to reproduce
Click on Import and wait
What is expected?
Imported settings
What is actually happening?
nothing beside a restart
System

Hyperion Server:

Build:       (HEAD detached at e3587923) (Paulchen-Panther-2e83c587/e3587923-1587148622)
Build time:  Apr 17 2020 19:15:25
Git Remote:  https://github.com/hyperion-project/hyperion.ng
Version:     2.0.0-alpha.5
UI Lang:     auto (BrowserLang: de)
UI Access:   default
Avail Capt:  dispmanx,v4l2,framebuffer,qt

Hyperion Server OS:

Distribution: Raspbian GNU/Linux 10 (buster)
Arch:         arm
Kernel:       linux (4.19.97-v7+ (WS: 32))
Browser:      Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:75.0) Gecko/20100101 Firefox/75.0

"Merged" with issue: #804


have a test

想测试一下这个问题

Hi @Frankzhaopku, we detect non-English characters in the issue. This comment is an auto translation from @collabobot to help other users to understand this issue.
We encourage you to describe your issue in English which is more friendly to other users.

have a test
I want to test this question


regressing weights per column

Related issues

Description
Fixed sub-optimal mapping of conductances to weights for fusion by regressing weights per column
Details

FYI.  I am going to update the CHANGELOG and VERSION with this same PR.


[FLINK-15290][streaming] Configure user defined function with global …

…configuration

What is the purpose of the change
Make the global configurations available to user defined functions.
Brief change log

Use GlobalConfiguration.loadConfiguration when opening the user function

Verifying this change
TBD
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: no
The S3 file system connector: no

Documentation
NA

Thanks @lirui-apache , LGTM.

CC: @KurtYoung

Can you change title?

I think we should not GlobalConfiguration.loadConfiguration in RichInputFormat.configure.
We should get this TABLE_EXEC_HIVE_FALLBACK_MAPRED_READER option in client side, must have FLINK_CONF_DIR in client side.
In HiveTableSource.getDataStream, we can get the option and pass it to HiveTableInputFormat.

@JingsongLi Updated to read the configurations on client side.


Strange results in wifi 802.11

Hello,
I know I was the one who submitted the code in first place, and as far as I know, I implemented it according to the IEEE 802.11 standard.
According to the IEEE 802.11 section <IP_ADDRESS> the data is coded with a convolutional encoded of rate 1/2. Higher rates are achieved by then puncturing. In the receiver side, there is depuncturing by adding a dummy "zero" on the place of the omitted zeros.
This works good in some MCS (0,1,2,3,4) where the parameters have coding of 1/2 and 3/4 and modulation BPSK, QPSK and 16-QAM.
Graph with the BER vs SNR bellow (message size was 600bits, 2000 runs each SNR):

When higher MCS are tried (5, 6,7, 8, 9) the behaviour becomes strange as can be seen in a similar plot for those MCS bellow (same conditions of experiment):

The first and more visible problem is with MCS 6, after a particular SNR (about 24) the BER stops decreasing at the same rate as others MCS (it still decreases but only slightly, maybe rounding differences).
Second the MCS 7 achieves better BER than MCS 5 at most SNRs, notice both are 64-QAM, the only difference are the punturing performed. Similar behaviour happens with MCS 9 in relation with MCS 8.

Does someone have any idea why this simulation results are happening?
Some error in code or some error in my interpretation of the results?
If it helps debug, I notice some warnings in my console:

/commpy/commpy/modulation.py:131: RuntimeWarning: divide by zero encountered in double_scalars
demod_bits[i * self.num_bits_symbol + self.num_bits_symbol - 1 - bit_index] = log(llr_num / llr_den)

This is maybe related with the problem with MCS 6 at SNRs over 25, I can easily replicate this issue.
Also, I can add code if it helps. :-)

Hi Eduardo,
I agree that there does appear to be a glitch somewhere. I don't feel competent enough on WiFi to spot a bug on that area. I can try to check if it is coming from the remainder (simulation, coding, modulation, etc).
Could you share the file that produces the faulty graphs? Besides, do you have any reference that gives the expected curves so that we can tell if it works as expected or not?

Hi BastienTr,
Sorry for the time to reply, I was reproducing the problem in a easier way to show and debug.
The issue is the strange behaviour with the parameters: modem 64 QAM, and performing puncturing 3/4 ([1, 1, 1, 0, 0, 1]).
Different modems (16 QAM) or different puncturing levels (i.e. 5/6 [1, 1, 1, 0, 0, 1, 1, 0, 0, 1]) don't manifest the issue.
To illustrate, I show where the behaviour of 16QAM with different coding rates (1/2 was no puncturing, the other coding rates are achieved with first coding at 1/2 and then puncturing):

The expected behaviour is starting with a BER of about 0.5 and with the increase of SNR, it will decrease until zero. The higher coding rate, the higher the BER for a same SNR.
The same test (adjusted for higher SNRs) with 64QAM the behaviour is the following:

With coding rates of 1/2 and 5/6 the behaviour is the expected. Coding 3/4 manifests the strange behaviour.
The code to test the results is bellow (used multiprocessing just to speed up, but behaviour also occurs if no multiprocess is used):
# Authors: CommPy contributors
# License: BSD 3-Clause

import math
import time
from datetime import timedelta
from itertools import product

import matplotlib.pyplot as plt
import numpy as np
from p_tqdm import p_map

import commpy.channelcoding.convcode as cc
import commpy.channels as chan
import commpy.links as lk
import commpy.modulation as mod
import sys

# =============================================================================
# Convolutional Code 1: G(D) = [1+D^2, 1+D+D^2]
# Standard code with rate 1/2
# =============================================================================

# Number of delay elements in the convolutional encoder
memory = np.array(7, ndmin=1)

# Generator matrix
g_matrix = np.array((133, 171), ndmin=2)

# Create trellis data structure
trellis1 = cc.Trellis(memory, g_matrix)

is16 = False
if len(sys.argv) > 1 and sys.argv[1] == "16":
    is16 = True

modem = mod.QAMModem(64)
if is16:
    modem = mod.QAMModem(16)
# modem = mod.PSKModem(2)

# AWGN channel
channels = chan.SISOFlatChannel(None, (1 + 0j, 0j))

puncture_matrix34 = [1, 1, 1, 0, 0, 1]
puncture_matrix56 = [1, 1, 1, 0, 0, 1, 1, 0, 0, 1]
code_rate34 = 3 / 4
code_rate56 = 5 / 6

# Modulation function
def _modulate(bits):
    bits2 = cc.conv_encode(bits, trellis1, 'cont')
    return modem.modulate(bits2)

# Modulation function
def modulate_punturing34(bits):
    # bits2 = cc.conv_encode(bits, trellis1, 'cont', puncture_matrix=puncture_matrix)
    bits2 = cc.conv_encode(bits, trellis1, 'cont')
    bits2 = cc.puncturing(bits2, puncture_matrix34)
    return modem.modulate(bits2)

# Modulation function
def modulate_punturing56(bits):
    # bits2 = cc.conv_encode(bits, trellis1, 'cont', puncture_matrix=puncture_matrix)
    bits2 = cc.conv_encode(bits, trellis1, 'cont')
    bits2 = cc.puncturing(bits2, puncture_matrix56)
    return modem.modulate(bits2)

# Receiver function (no process required as there are no fading)
def receiver(y, h, constellation, noise_var):
    return modem.demodulate(y, 'soft', noise_var)

# Decoder function
def _decoder(msg):
    return cc.viterbi_decode(msg, trellis1, decoding_type='soft')

# Decoder function
def decoder_puncturing34(msg):
    msg2 = cc.depuncturing(msg, puncture_matrix34, math.ceil(len(msg) * code_rate34 * 2))
    return cc.viterbi_decode(msg2, trellis1, decoding_type='soft')

# Decoder function
def decoder_puncturing56(msg):
    msg2 = cc.depuncturing(msg, puncture_matrix56, math.ceil(len(msg) * code_rate56 * 2))
    return cc.viterbi_decode(msg2, trellis1, decoding_type='soft')

def perf(model_):
    if model_[1] == 0:
        code_rate = code_rate34
        modulate = modulate_punturing34
        decoder = decoder_puncturing34
    elif model_[1] == 1:
        code_rate = code_rate56
        modulate = modulate_punturing56
        decoder = decoder_puncturing56
    else:
        code_rate = 1 / 2
        modulate = _modulate
        decoder = _decoder

    model = lk.LinkModel(modulate, channels, receiver,
                         modem.num_bits_symbol, modem.constellation, modem.Es,
                         decoder, code_rate)

    SNRs = np.arange(model_[0], model_[0] + 1) + 10 * math.log10(modem.num_bits_symbol)
    return {"code_rate": model_[1], "SNR": SNRs[0],
            "res": model.link_performance_full_metrics(SNRs, 10, 0, 600, code_rate, stop_on_surpass_error=False)}

models = list(product(np.arange(5, 20), [0, 1, 2]))
if is16:
    models = list(product(np.arange(0, 15), [0, 1, 2]))

start = time.time()
data = p_map(perf, models)
print(str(timedelta(seconds=(time.time() - start))))

print("16 QAM" if is16 else "64QAM")
print("SNRs", list(map(lambda x: x[0] + 10 * math.log10(modem.num_bits_symbol), filter(lambda x: x[1] == 0, models))))
rate12 = list(map(lambda x: x["res"][0][0], sorted(filter(lambda x: x["code_rate"] == 2, data), key=lambda x: x["SNR"])))
rate34 = list(map(lambda x: x["res"][0][0], sorted(filter(lambda x: x["code_rate"] == 0, data), key=lambda x: x["SNR"])))
rate56 = list(map(lambda x: x["res"][0][0], sorted(filter(lambda x: x["code_rate"] == 1, data), key=lambda x: x["SNR"])))
print("1/2", rate12)
print("3/4", rate34)
print("5/6", rate56)

# plt.semilogy(SNRs, BERs_no_punturing[0], 'o-', SNRs, BERs_puncturing[0], 'o-')
# plt.grid()
# plt.xlabel('Signal to Noise Ration (dB)')
# plt.ylabel('Bit Error Rate')
# plt.legend(('W/o Punturing', 'W/punturing'))
# plt.show()

Thanks for the minimal example Eduardo.
I can't have a look this week. I'm overwhelmed by some PhD staff... I'll try to look closer in the next weeks.

Hi, guys!
Frankly speaking, I am not so confident, but it seems like issue of convolutional codes implementation. I saw something similar when use MatLab: https://www.mathworks.com/matlabcentral/fileexchange/72392-exact-vs-approximate-llr-calculation?s_tid=prof_contriblnk
Hopefully, I have not increased discussion entropy now! :)

Hi kirlf, every guess is a good as any!
It was in some way related with the convolutional codes, but not an issue with the implementation (as far as I know).
I found the issue and I'm making a PR as soon as travis passes the tests (they pass in my machine, so it should be soon).
The issue was with the send chunk after coding and puncturing not being divisible by the number of bits of the modulation!
There was code that tried to select the correct send chunk in order to avoid the issue, but was only taking in to account the modulation, without looking at the code rate!  (Creating issues even if the send chunk chosen was perfect for after coding rate being divisible by the modulation!)
The fix is slightly adjusting the code to select a good send chunk. Making sure the chunk is both divisible by the modulation after applying the code rate, and divisible by the code rate after demodulating at the receiver side.

I have written the following test to check it actually fixed it (click to expand):
# Authors: CommPy contributors
# License: BSD 3-Clause

import math
import time
from datetime import timedelta
from fractions import Fraction
from itertools import product

import matplotlib.pyplot as plt
import numpy as np
from p_tqdm import p_map

import commpy.channelcoding.convcode as cc
import commpy.channels as chan
import commpy.links as lk
import commpy.modulation as mod
import sys

# =============================================================================
# Convolutional Code 1: G(D) = [1+D^2, 1+D+D^2]
# Standard code with rate 1/2
# =============================================================================

# Number of delay elements in the convolutional encoder
memory = np.array(7, ndmin=1)

# Generator matrix
g_matrix = np.array((133, 171), ndmin=2)

# Create trellis data structure
trellis1 = cc.Trellis(memory, g_matrix)

is16 = False
if len(sys.argv) > 1 and sys.argv[1] == "16":
    is16 = True

modem = mod.QAMModem(64)
if is16:
    modem = mod.QAMModem(16)
# modem = mod.PSKModem(2)

# AWGN channel
channels = chan.SISOFlatChannel(None, (1 + 0j, 0j))

puncture_matrix34 = [1, 1, 1, 0, 0, 1]
puncture_matrix56 = [1, 1, 1, 0, 0, 1, 1, 0, 0, 1]
code_rate34 = Fraction(3, 4)
code_rate56 = Fraction(5, 6)

# Modulation function
def _modulate(bits):
    bits2 = cc.conv_encode(bits, trellis1, 'cont')
    return modem.modulate(bits2)

# Modulation function
def modulate_punturing34(bits):
    # bits2 = cc.conv_encode(bits, trellis1, 'cont', puncture_matrix=puncture_matrix)
    bits2 = cc.conv_encode(bits, trellis1, 'cont')
    bits2 = cc.puncturing(bits2, puncture_matrix34)
    return modem.modulate(bits2)

# Modulation function
def modulate_punturing56(bits):
    # bits2 = cc.conv_encode(bits, trellis1, 'cont', puncture_matrix=puncture_matrix)
    bits2 = cc.conv_encode(bits, trellis1, 'cont')
    bits2 = cc.puncturing(bits2, puncture_matrix56)
    return modem.modulate(bits2)

# Receiver function (no process required as there are no fading)
def receiver(y, h, constellation, noise_var):
    return modem.demodulate(y, 'soft', noise_var)

# Decoder function
def _decoder(msg):
    return cc.viterbi_decode(msg, trellis1, decoding_type='soft')

# Decoder function
def decoder_puncturing34(msg):
    msg2 = cc.depuncturing(msg, puncture_matrix34, math.ceil(len(msg) * code_rate34 * 2))
    return cc.viterbi_decode(msg2, trellis1, decoding_type='soft')

# Decoder function
def decoder_puncturing56(msg):
    msg2 = cc.depuncturing(msg, puncture_matrix56, math.ceil(len(msg) * code_rate56 * 2))
    return cc.viterbi_decode(msg2, trellis1, decoding_type='soft')

def perf(model_):
    if model_[1] == 0:
        code_rate = code_rate34
        modulate = modulate_punturing34
        decoder = decoder_puncturing34
    elif model_[1] == 1:
        code_rate = code_rate56
        modulate = modulate_punturing56
        decoder = decoder_puncturing56
    else:
        code_rate = Fraction(1, 2)
        modulate = _modulate
        decoder = _decoder

    model = lk.LinkModel(modulate, channels, receiver,
                         modem.num_bits_symbol, modem.constellation, modem.Es,
                         decoder, code_rate)

    SNRs = np.arange(model_[0], model_[0] + 1) + 10 * math.log10(modem.num_bits_symbol)
    nbits = model_[2]
    return {"code_rate": model_[1], "SNR": SNRs[0], "size": nbits,
            "res": model.link_performance_full_metrics(SNRs, 10, 0, nbits, code_rate, stop_on_surpass_error=False)}

SNR = 30
if is16:
    SNR = 25

psizes = list(range(10, 1500, 10))
# psizes = [10]
models = list(product([SNR], [0, 1, 2], psizes))

start = time.time()
data = p_map(perf, models)
# data = [perf([20, 0, 10])]
print(str(timedelta(seconds=(time.time() - start))))

for psize in psizes:
    rate12 = list(map(lambda x: x["res"][0][0],
                      sorted(filter(lambda x: x["code_rate"] == 2 and x["size"] == psize, data), key=lambda x: x["SNR"])))
    if rate12[0] > 0:
        print("FAILED, rate 1/2, size %d, BER %f" % (psize, rate12[0]))
    rate34 = list(map(lambda x: x["res"][0][0],
                      sorted(filter(lambda x: x["code_rate"] == 0 and x["size"] == psize, data), key=lambda x: x["SNR"])))
    if rate34[0] > 0:
        print("FAILED, rate 3/4, size %d, BER %f" % (psize, rate34[0]))
    rate56 = list(map(lambda x: x["res"][0][0],
                      sorted(filter(lambda x: x["code_rate"] == 1 and x["size"] == psize, data), key=lambda x: x["SNR"])))
    if rate56[0] > 0:
        print("FAILED, rate 5/6, size %d, BER %f" % (psize, rate56[0]))

I didn't add to the suite of tests, because it takes a huge amount of time.

it takes a huge amount of time.

I'm running some tests and... well you were right :sweat_smile:. I keep in touch when computations and tests end.

it takes a huge amount of time.

I'm running some tests and... well you were right sweat_smile. I keep in touch when computations and tests end.

If it helps, in my 48 core running machine was something like 20 minutes! (all cores used)

Then I must trust you, this will be too much for my 4-cores laptop.

You can run a smaller set, instead of calculating for every send chunk between 10, 20, ...1500, just select a few!


Interpolations are not normalized

Describe the bug
Source of the problem can be seen after saving a translation with lokalize (23.08.1) where the following happens:
       <trans-unit id="ExampleId" datatype="html">
-        <source>ID: <x id="INTERPOLATION" equiv-text="{{nextId | async}}"/></source>
-        <target state="signed-off">ID: <x id="INTERPOLATION" equiv-text="{{nextId | async}}"/></target>
+        <source>ID: <x equiv-text="{{nextId | async}}" id="INTERPOLATION"/></source>
+        <target state="signed-off">ID: <x equiv-text="{{nextId | async}}" id="INTERPOLATION"/></target>
       </trans-unit>

Interpolations in source/target are not normalized when converted to strings which will be compared. This can result in reset state of the translated targets or other constant changes when modifying translations.
Expected behavior
The order of attributes in the x tags makes no change to the comparison result. The normalization process could simply sort the attributes.
Version (please complete the following information):

Angular: 17.1.2
OS: Ubuntu 23.10
nodejs: 20.11.0
ng-extract-i18n-merge version: 2.9.1

@mbey-mw thanks for this issue and the PR!
There are two points I am not sure about - maybe you already thought about it:

Does the attribut order actually change? If so, when?
The proposed solution will update all existing attributes, leading to huge changes for all users - would it be possible to change only the actual comparison - e.g. in Merger.normalize

Order of the Attributes
The order of the attributes changes in our translated files when they are saved. lokalize does it as described in the bug. Maybe other tools do this as well - in the end it shouldn't make a difference which tool you use.
In our workflow, we simply run ng-extract-i18n-merge before submitting the translations, and the linter checks this. Only normalized files should be stored in the repository.

Breaking Change?
When comparing two XML nodes, the order of the attributes can change without the "value" of the node changing - in contrast to the order of the sub-nodes. This is the technical challenge when comparing sources and targets. If the XML file is viewed as a text file, a comparison cannot adequately resolve this. It is therefore necessary to always store the same normalized version of the files in Git - which is why Merger.normalize does not seem to be the right place.
It is also about the content of the source and target tags that is generated when the files are read in. This is regarded as a string and not as a collection of child elements - this would entail a major modification of the software.
Since the problem of missing normalization has not yet been reported as such, the attribute order of the source file (messages.xlf) seems to be mostly appropriate. In order to minimize changes to this assumed normal case, you could specify an order for certain attributes and only sort the others alphabetically.
In our XLIFF 1.2 files, there are only x tags where attributes are generated in the following order: ctype, equiv-text, id. In the tests there are ph tags with attributes id, equiv, disp. This could be used to specify a sequence. Should this be a configurable setting?

Alternatively, an option to switch on attribute sorting could also be introduced. How would that be? Default value would be false / off. -> ´sortNestedTagAttributes´


Can't lock a submission?

I can only see the status while logged in on a subreddit I mod but can't lock the thread? Am I missing something?

The feature is not available. Would you like to implement it?

Oh! Got mixed up somewhere in there then. I'll have a look. This is what is supposed to be added then:
r.request_json("https://api.reddit.com/api/lock", data={'id': 't3_xxxxx'})

@lodjuret Not exactly. A function on the submission class (Or just a new class to handle locks, and let submissions inherit it), and figure out how to pass the id in properly

Well yeah I just looked at the API and did the call with request_json. That call fails when I'm logged in over Oauth and not via the old .login(). Why?

@lodjuret what's the error?

Here. I'm getting a submission from a private subreddit so I would need to be authenticated but it throws a not logged in error on the latter request.

submission = submission = r.get_submission(submission_id='3gpdpi')
submission.author
Redditor(user_name='blablabla-')
r.request_json("https://api.reddit.com/api/lock", data={'id': submission.fullname})
Traceback (most recent call last):
File "", line 1, in
File "", line 2, in request_json
File "/usr/local/lib/python2.7/dist-packages/praw/decorators.py", line 139, in raise_api_exceptions
raise error_list[0]
praw.errors.NotLoggedIn: Please log in to do that. on field None

Compare with the marknsfw api call:

r.request_json("https://api.reddit.com/api/marknsfw", data={'id': submission.fullname})
Traceback (most recent call last):
File "", line 1, in
File "", line 2, in request_json
File "/usr/local/lib/python2.7/dist-packages/praw/decorators.py", line 139, in raise_api_exceptions
raise error_list[0]
praw.errors.NotLoggedIn: Please log in to do that. on field None
submission.mark_as_nsfw()
{}

The last call works.

That call fails when I'm logged in over Oauth and not via the old .login(). Why?

The methods that require OAuth specify that they do. Only in such cases the necessary OAuth parameters are sent, hence why calling r.request_json("https://api.reddit.com/api/lock", data={'id': 't3_xxxxx'}) is not likely to work by it self. If you define a method, and decorate it with the appropriate restrict_access call, then things should work.

I believe I've just implemented this. However, I'm quite new. Are there some tests I should be running?


Update @angular-eslint/template/i18n to ignore common nimble and sl-lib attributes

Justification
Update @angular-eslint/template/i18n to ignore common nimble and sl-lib attributes (and excludes tests of the name *.spec.ts with inline templates).
fixes #83
Implementation
A new file template/options.js is added to list all well-known attributes that should not be localized for using in NI javascript codebases. This includes common nimble attributes, systemlink-lib-angular attributes, and attributes from commonly used third-party libraries.
This list is used to modify the @angular-eslint/template/i18n eslint rule to ignore any attribute in the list by default. If apps need to change this to ignore only nimble attributes, they have the option to do that by overriding the rule's config in their app's eslintrc.
Testing

I have made modifications to the angular test project to include attributes on the two sample templates that should either be ignored or not ignored and verified the eslint rule modification is being correctly applied in each.
Added a test to verify custom attributes can be added to ignore lists by apps.

This made it into SystemLinkShared with no pipeline failures 🎉


Clicking on Photo or "PROVE IT" on USer Profile Brings User to /campaigns

As a non-admin user coming from Japan: if I click the photo or "PROVE IT buttons on these campaigns on my user profile:

I get brought to /campaigns when I should be brought to the action page or prove it section of the campaign

looks like that url is missing the country prefix

@weerd do you mind taking a look at this?

Seems like the %23 is messing with the URL, which technically shouldn't since it's just the escaped #. If I switch it to a # it goes to the right page.


Proposal: show 404 pages for inactive offers

Offers that are suspended are not visible in the list view, but will still be shown as detail page.
I wonder whether this is intended, or accidentally.
One of my clients requested to hide such pages (as I've done in the project code).
With this PR I'd hope to receive feedback on whether this should be the default, or not.

Agree. How about you @mvantellingen ?

Agreed, merging 👍


Add warning about using this repo

@xzyfer noticed someone recommending curling from this repo on SO, so I thought I'd add a warning

It's also worth noting these binaries very out of date. We should probably kill off this repo now. Thoughts @am11 @saper?

I think old versions were pointing at this (maybe), so that would be my only trouble with killing it entirely

Yeah you're right. It'd be good to get stats on version fragmentation. Any version that references this repo hasn't been supported for a long time now.

Maybe just nuke all the bindings in the current branch too

I think we can get some data out of npm around installation numbers.
We should use npm deprecate to make npm produce a deprecation warning on installation of older versions.

Removing the binaries from master also makes sense.
Noting that only binaries  <= 3.8.0 are available here

:100: Makes sense to add the deprecate on the old packages

Agree on issuing the npm deprecate warning for older version. 👍
At some point, the idea was to also treat this repo as binaries backup store, in case one of us accidentally deletes the binary from the release assets. If there is not even that usage anymore, then nuking the repo makes sense.
Probably, would make sense to do a commit removing everything, keeping the readme around for a while noting "we are pulling the plug on this repo, update to newer version of node-sass". Then wait for a couple of weeks before R.I.P'ing the repo.

I think we could keep offering this repo for the very purpose of having a local binary cache. It needs some work to be useful for this purpose (various releases would need to be unpacked into version directories) but maybe with an unpack script and some hopefully minimal node-sass installer changes it could be become quite useful and let us close this long-standing request with node-sass

What has changed with Node-Sass that this is now deprecated?
From my understanding when you npm install node-sass it will check your OS/Arch/Node versions and download the correct binding from this repo.
I'm running Node-Sass from inside of NW.js, which has different version of Node than what I have installed globally. So I need to manually copy the correct version into the node_modules/node-sass/vendor/OS-Arch-NodeV folder.
I've been using this repo as a source for my copy of the bindings so I can do automated builds for different platforms.
Relevant files files from my project:

https://github.com/scout-app/scout-app/tree/master/scout-files/_assets/node-sass_v3.8.0
https://github.com/scout-app/scout-app/blob/master/scout-files/_scripts/libsass-fix.js

From my understanding when you npm install node-sass it will check your OS/Arch/Node versions and download the correct binding from this repo.

I couldn't find the exact version, but it's been using the GH releases downloads since at least 3.2.0


Redesign HealthStatus (again)

This change brings back the ability to return Healthy/Degraded/Unhealthy
in a HealthCheckResult. We tried making this pass/fail in 2.2.0-preview3
and folks writing health checks for their own use pointed out (rightly
so) that it was too limited.
It's still possible for the app developer to configure the failure
status of a health check, but it requires the health check author to
cooperate.
I also got rid of HealthStatus.Failed since it raises more questions
than it answers. It's really not clear that it's valuable for a health
check for behave different when throwing an unhandled exception.
We would still recommend that a health check library handle exceptions
that they know about and return context.Registration.FailureStatus.

/cc @unaizorrilla

Hi @rynowak
I try to adapt all HealthChecks / UI  to this new HealthCheckResult status soon!

Hi @rynowak
Committed HealthStatus re-design on AspNetcore.Diagnostics.HealthChecks repo.
https://github.com/Xabaril/AspNetCore.Diagnostics.HealthChecks/commit/051947206d4837608de92f84c02979515868a5ce
Versions 2.2.0-rtm-35613 on MyGet right now.


Way of providing parameters to the steps

It would be great if we could provide date as a table:
    When I add a new code {number}
      | number |
      [ 123456 |

As defined here
https://docs.cucumber.io/cucumber/api/#data-tables

I didn't find the docs. I found examples here
https://github.com/TheBrainFamily/cypress-cucumber-preprocessor/blob/master/cypress/support/step_definitions/dataTable.js


[Feature] Python agent support generic ASGI/WSGI middleware instrumentation

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Currently the web frameworks supported in the Python agent are instrumented individually, yet we lack the ability to trace generic requests from the ASGI and WSGI middleware level, which enables the auto tracing of any framework that follows these two protocols.
Middlewares: So essentially each request go down each middleware and go back in reverse order as they return.
Then as a result, we should have a SkyWalkingASGI(WSGI)Middleware that can be added to any framework, tracing should automatically work.
New contributors are welcome to try this out. Upon completion please file a PR to here so people know we have this feature: https://github.com/florimondmanca/awesome-asgi#monitoring.
Use case
User should be able to trace any ASGI/WSGI compatible libraries even if the framework itself is not instrumented.
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

please assign me

You could go ahead, we don't have anyone working on this.


Implement sensors

Make it easier to create a body that ignores collision and tells whether it is intersecting another body.

I'll consider it, it's also worth checking out this related issue #65 as my thoughts are similar on this.

+1

+1
I've implemented something like this in my project using collision filters to avoid the actual collision but then using Query to check for other bodies on sleep to avoid the performance hit of constantly polling. This works for my specific case where bodies move incrementally and have "fields of influence" that handle non-physics/matterjs related interactions.
I'd much prefer this process to happen in real time so I'd definitely love a sensor feature!

This is now available as of 0.9.2, by setting the body.isSensor to true. Thanks guys.

Just a heads up that this isn't yet in the API docs

Any idea how someone can access sensor documentation since it's not in the docs?


update/ecommerce-spec-v2

This PR changes the ecommerce V1 syntax Action + Object to the new V2 syntax, Object + Action.
This PR will be waiting on a few blockers, a refactor of the Analytics-Events repo to be more concise and readable as we add more events to our spec and for similar changes to be made to all other integrations currently using V1 syntax.
There are some Order Completed tests that aren't passing for revenue matching reasons that will need to be fixed.

I found the reason that these tests aren't passing and it is because facade is explicitly checking for completed order as the event before aliasing revenue from total https://github.com/segmentio/facade/blob/144cf373bb92c2128e512cf10ff9ad4952a5b2ca/lib/track.js#L230-L232
This will need to be changed for revenue to properly be aliased from total.


Update library in the background instead of using a popup window

The 'Keep Library in Sync' tick box can make using playnite a little cumbersome, since a popup will lock you out of interacting with the rest of the window for a bit while it works. It usually doesn't take more than a second but it is consistently delayed after closing/launching a game on my end, and can end up taking longer depending on network conditions. It can catch someone off guard if they're trying to switch games and become a major annoyance after a while. Hopefully it's not too much trouble to find some way to work around this :)

Added an option to hide the dialog in https://github.com/sharenite/playnite-sharenite/releases/tag/0.8


Fixed little typos in convolutional-networks.md

Fixed little typos in convolutional-networks.md:

They are made up of => they are made up of
The whole network still express => The whole network still expresses
From the raw image pixels => from the raw image pixels
vastly reduces the amount of parameters => vastly reduce the amount of parameters

thanks!


Rewrite _example/ web app to gotemplates

I want to make example page more pretty.

[ ] add base layout
[ ] move to go templates
[ ] add example static route
[ ] autogen userId for registration (security first registration without userName)
[ ] refactor main (extract all generic stuff outside)
[ ] maybe add debug window with store state, idk
[ ] add multi passkey support UI (ref: #3)

https://github.com/leapkit/leapkit/ looks lovely! I definitely should try it out. However, in this particular project, I’d like to keep the number of dependencies as small as possible.


Report combined coverage, and switch to codecov

It makes more sense to measure combined coverage (combined across
different interpreters), because the code itself may have corner cases
for particular python versions (e.g. if Python 2.7 then do something).
Also, the commit switches to codecov from coveralls. It looks like it
works a bit quicker, and provides a better UI & UX.

Current coverage is 97.46%

Merging #161 into master will not affect coverage as of 5348915

@@            master    #161   diff @@
======================================
  Files           17      17
  Stmts          553     553
  Branches         0       0
  Methods          0       0
======================================
  Hit            539     539
  Partial          0       0
  Missed          14      14

Review entire Coverage Diff as of 5348915

Powered by Codecov. Updated on successful CI builds.


Debug why playsounds sometimes break

Symptom is that editing/adding/removing works, web interface works, module is enabled, WebSocket also works (e.g. showemote still goes through), but it's not possible to make the bot publish a playsound payload either through the "Play on stream" test button OR the !#playsound command
The play on stream endpoint also does not return any error.
Also issue is not alleviated by disabling/enabling the module.

@RAnders00 Did f174983 end up fixing this issue?

Not sure, but there have been no reports of that error since, so I think this can be closed.


Unable to use new decorators in vue with vite and babel

Vue version
3.3.8
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-cbe6hz
Steps to reproduce
Build the given reproduction using npm run build and see this error:
error during build:
Error: [vue/compiler-sfc] Cannot use the decorators and decorators-legacy plugin together

Even though in vite.config.ts, the vue plugin's config lists the decorators babel plugin, it is not being considered in the following code.
vue({
  script: {
    babelParserPlugins: ['decorators'],
  },
}),

The following code seems to be the cause of it: https://github.com/vuejs/core/blob/main/packages/compiler-sfc/src/script/context.ts#L167.
Since it is never checked if user has passed the decorators plugin before adding the decorators-legacy one, both the plugins end up being pushed in the array
What is expected?
no error on build
What is actually happening?
Error on build
System Info
System:
    OS: Windows 10 10.0.19044
    CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12800H
  Binaries:
    Node: 18.15.0 - ~\portable_apps\.nvm\versions\node\v18.15.0\bin\node.EXE
    npm: 9.5.0 - ~\portable_apps\.nvm\versions\node\v18.15.0\bin\npm.CMD

Any additional comments?
It seems like the plugins array check to see if it includes 'decorators' is a mistake, since that will always come out to be true. It should check in the userPlugins array instead

How would I know which version this fix will be part of?


perf: hoist option logic, reduce code paths in handler

Small refactor
What kind of change does this PR introduce?
perf
Did you add tests for your changes?
N/A
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
N/A

Please note that this change has no perf-impact because it is called once (or a few times)

@ooflorent i agree it's not a dramatic perf impact. But, at least from how I've read the code..this handler is used on every chunk. right?


Bug: The slider inside toggle button moves outside

Description
When user clicks on the toggle button for dark or light mode, the slider button moves out of the box border
Proposed Solution
The inner toggle button shouldn't move outside the external button
Screenshots

Browser 🥦
Google Chrome
Checklist ✅

[X] I checked and didn't find similar issue
[X] I have read the Contributing Guidelines
[ ] I am willing to work on this issue (leave this unchecked for no).

Hi @ItsRoy69, Iam ready to do this, could you please assign it to me?

Go for it

@ItsRoy69 kindly check the below snip, where the slider will not move outside of the bar, hope to hear from you soon.
https://github.com/WikiPortal/DoodleCollab/assets/82110100/fd49d8e0-de74-40eb-ac33-e95b636589ee

I have made changes in your existing toggle bar,
Verified by reducing the speed of 0.5x ( 00:08 in the video),
kindly check and update back so that I can push it.
https://github.com/WikiPortal/DoodleCollab/assets/82110100/c73e48e1-4f86-4160-a746-89da70ae6ebc

LGTM, make a PR


Added the ability to provide credentials under the form of a custom

(useful for third party authentication in some matrix deployments).
Hi, for some matrix instances (for example Thalès Citadel), it is necessary to use an auth string that is somewhat different.
This PR for letting users define their own auth-string.
Shall changes be needed, please do not hesitate to let me know.

Hi @clouetb - thank you for the PR. You may know that this library is not the suggested Python SDK for Matrix - you should consider using https://github.com/poljar/matrix-nio, which is far more actively maintained. It's also more feature-rich.

Hi,
I realized this after sending my PR on matrix-python-sdk (which was the one
proposed by Thalès...).
Then I proposed another PR on matrix-nio :
https://github.com/poljar/matrix-nio/pull/105 which was accepted;
Anyway, thank you for your reply.
On Mon, Mar 2, 2020 at 3:56 PM Ben Parsons<EMAIL_ADDRESS>wrote:

Hi @clouetb https://github.com/clouetb - thank you for the PR. You may
know that this library is not the suggested Python SDK for Matrix - you
should consider using https://github.com/poljar/matrix-nio, which is far
more actively maintained. It's also more feature-rich.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/matrix-org/matrix-python-sdk/pull/314?email_source=notifications&email_token=AAE33BIAI2HFD6SGT53EPU3RFPCJTA5CNFSM4K6XNWGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENPTMKQ#issuecomment-593442346,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAE33BNJ2UDF4465O5X4GBLRFPCJTANCNFSM4K6XNWGA
.


Update scene-understanding-SDK.md

Docs Build status updates of commit 05b1be3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/scene-understanding-SDK.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Feature/db/bbfb Fix light mode carousel

👷 Deploy Preview for zeti-tlp-dev processing.

Name
Link

🔨 Latest commit
bdd81eda1f94148abfbc88bb7d4ed52c336179d5

🔍 Latest deploy log
https://app.netlify.com/sites/zeti-tlp-dev/deploys/66aceba06300e2000844d1cb


i18n(de): sharing-state.mdx translation

What kind of changes does this PR include?

Translated content

Description

Translate sharing-state.mdx to german

LGTM!


Adaptive cards Monaco Editor is not getting loaded with the Angular

Problem Description
Hi Team,
I'm trying to integrate the Adaptive card designer with the Angular application. I make a one-live solution for it but in that, I'm facing one problem I'm not able to load Monaco editor in that.
So anyone can provide a real way to integrate the Adaptive cards with the Angular App?
https://stackblitz.com/edit/angular-ivy-mfde8r?file=src/app/app.component.ts
Card JSON
So anyone can provide a real way to integrate the Adaptive cards with the Angular App?
https://stackblitz.com/edit/angular-ivy-mfde8r?file=src/app/app.component.ts

Screenshot

I've not done this personally, but it should be possible to pass in an instance of monaco to designer.monacoModuleLoaded():
https://github.com/microsoft/AdaptiveCards/blob/71aeddce59f56dfb918b9199550fe0a9eef414b1/source/nodejs/adaptivecards-designer/src/card-designer.ts#L1343-L1346
Poking around with a web search, it looks like there are a number of recommendations for getting monaco inside an Angular app more generally, so maybe one of those approaches will work in getting it loaded?


Unified and customizable JSON serialization settings

C# generated client template is not committed!

Looks good...

We also need a GenerateUpdateJsonSerializerSettingsMethod setting (default: true) to implement it in the base class. Ill do that...

Sounds good


Username or password is incorrect (LoginException('BadAuthentication'))'

Thank u for your good work. Complete noob here, I can't see the password when I type or paste and it showed 'Username or password is incorrect (LoginException('BadAuthentication'))' when I pressed enter. And I Double checked when I typed the app password.

@Jimmy2times - hi! the pw field is hidden for protection. However, try to copy and paste the app pw (which you need to recreate again) into notepad or word and then hand type it into the pw field very slowly and carefully. Be sure the app pw has no spaces or dashes. It should be 16 digits.

@djsudduth HI, I tried every solution other issues mentioned. It did not work. I can see in my connection logs that there was a request to 'android.clients.google.com:443 ' after I pressed enter. So does that mean the script is running normally? It's probably my google account's faulty setting since I'm the only one encountered this issue, will check again later, thanks again.

@Jimmy2times - sorry it didn't work for you. Another option for you is to install Virtualbox with a fresh Linux install and shared disk - you can run KIM there (probably too much effort but you could try it).  Or, you could try installing pyenv and see if a new environment with python solves it.
PS - The next version of KIM will have export markdown from the Google Takeout backups from Keep which won't require the API call.


Fix register_webhook not returning response

register_webhook isn't returning its response which contains the id for the new webhook

@Solije Could you rebase this please?

Sure thing.

@TomAFrench I just realised I haven't merged any of these lmao. Will properly review, update, and merge tonight.


High Availability

Do not merge; Currently for unit testing purpose.

@yatli,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@TaviTruman yeah exactly, the queue will force the completion of tasks. Partitioner and replicator are wip now. Will be ready in one day or two!

@TaviTruman agreed that we should move to powershell.. Batch is like relic nowadays :)

implement HealthReport for Azure

good work people. this feature branch is now complete and coming back to master.


Bunch of bug fixes where stream id had to be passed into compose_actions.start instead of stream name.

reload: Fix bug where stream input is unexpectedly cleared on reload.
Earlier, we preserved the stream name across reloads, and to restore the compose state, passed that to compose_actions.start, which since c3fe96a, considers the stream id, and not its name.
This caused a bug where on server initiated reload, the stream input would not retain its value and be unexpectedly cleared.
This is fixed by preserving the stream id across reloads, instead of its name, and passing that to compose_actions.start instead.
compose: Pass in stream_id to compose when editing scheduled message.
Earlier, we only passed in the stream name which isn't considered in compose_actions.start when populating the recipient.
There was no visible bug since we first narrow to the correct stream and then call compose_actions.start, but this was brittle since it would not work if we open the compose box before narrowing.
left-sidebar: Fix "New topic" button in stream popover.
Now we pass in the stream's id to compose_actions.start() (not its name), so that the compose box opens with the correct stream selected.
Fixes: Issues described here

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

@N-Shar-ma thanks for finding these! Please check my work on the tweaks I made to the second commit -- I've done no manual testing. But I think this is the right version of this PR.
@evykassirer FYI since these were regressions from 846b470b99b9ce707b72ca6ac5f583cf14f26248.

Have reverted the 2nd (now, only) commit to its original form, should pass CI now!

Merged, but see https://github.com/zulip/zulip/pull/27695#discussion_r1393484614 for a low priority refactor we should try to avoid forgetting about.

@timabbott The follow up PR with the refactor is ready! #28474


Finish compatibility with sf4

SF4 requires mark all commands as a services.
All services are marked as private by default. Driver factory should be marked as public="true" in this case.

Also, I'm prepared flex recipe for this bundle: https://github.com/symfony/recipes-contrib/pull/155.
Will merge it after merging this PR

:+1:

@spike31 could you please tag new version to complete flex recipes support.


Problem: Semaphore starts tasks very often.

Issue
Semaphore starts tasks randomly. Some of them are running forever.

Impact
Service (scheduled tasks, alerts)
Installation method
Docker
Database
MySQL
Browser
Firefox
Semaphore Version
v2.10.22-e44910d-1721658561
Ansible Version
No response
Logs & errors
No response
Manual installation - system information
No response
Configuration
No response
Additional information
No response

I had the same thing happen on the latest version of Semaphore. It seems there might be an issue with the cron generation.
Toggle the "Show Cron format" and make sure it matches what you want the schedule to be.
You can also use https://crontab.guru/#_** to generate the cron and paste it into semaphore.

There are two different cron specifications. One is the origingal one that has been in use since inception of cron https://en.wikipedia.org/wiki/Cron and the other one, is what is used in most popular cron library for go lanuguage https://pkg.go.dev/github.com/robfig/cron?utm_source=godoc#hdr-CRON_Expression_Format I can see that robfig/cron is present in go.mod So which cron expression format is used here?

Looks like its working correctly if I create the cron without the GUI


refactor and tidy dds::participant

Codecov Report

Merging #159 (e649e31) into master (c9a96f5) will increase coverage by 0.07%.
The diff coverage is 50.00%.

:exclamation: Current head e649e31 differs from pull request most recent head 36eae75. Consider uploading reports for the commit 36eae75 to get more accurate results

@@            Coverage Diff             @@
##           master     #159      +/-   ##
==========================================
+ Coverage   70.39%   70.47%   +0.07%
==========================================
  Files          88       88
  Lines        8013     8006       -7
==========================================
+ Hits         5641     5642       +1
+ Misses       2372     2364       -8

Impacted Files
Coverage Δ

src/dds/participant.rs
76.31% <50.00%> (+1.63%)
:arrow_up:

Continue to review full report at Codecov.

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

:+1:


combine complementary DataArrays

I have a list of DataArrays with three dimensions.
For each item in the list, two of the dimensions are a single value but the combination of all items would yield the full combinatorial values.
Code Sample
    import itertools
    import numpy as np
    import xarray as xr

    ds = []
    for vals_dim1, vals_dim2 in itertools.product(list(range(2)), list(range(3))):
        d = xr.DataArray(np.random.rand(1, 1, 4),
                         coords={'dim1': [vals_dim1], 'dim2': [vals_dim2], 'dim3': range(4)},
                         dims=['dim1', 'dim2', 'dim3'])
        ds.append(d)

Expected Output
I then want to combine these complimentary DataArrays but none of what I tried so far seems to work.
The result should be a DataArray with shape |2x3x4| and dimensions dim1: |2|, dim2: |3|, dim3: |4|.
The following do not work:
    # does not automatically infer dimensions and fails with
    # "ValueError: conflicting sizes for dimension 'concat_dim': length 2 on 'concat_dim' and length 6 on <this-array>"
    ds = xr.concat(ds, dim=['dim1', 'dim2'])

    # will still try to insert a new `concat_dim` and fails with
    # "ValueError: conflicting MultiIndex level name(s): 'dim1' (concat_dim), (dim1) 'dim2' (concat_dim), (dim2)"
    import pandas as pd
    dims = [[0] * 3 + [1] * 3, list(range(3)) * 2]
    dims = pd.MultiIndex.from_arrays(dims, names=['dim1', 'dim2'])
    ds = xr.concat(ds, dim=dims)

    # fails with
    # AttributeError: 'DataArray' object has no attribute 'data_vars'
    ds = xr.auto_combine(ds)

Output of xr.show_versions()

INSTALLED VERSIONS
------------------
commit: None
python: 3.6.4.final.0
python-bits: 64
OS: Linux
OS-release: 4.4.0-43-Microsoft
machine: x86_64
processor: x86_64
byteorder: little
LC_ALL: None
LANG: None
LOCALE: None.None
xarray: 0.10.2
pandas: 0.22.0
numpy: 1.14.2
scipy: 1.0.0
netCDF4: 1.3.1
h5netcdf: None
h5py: None
Nio: None
zarr: None
bottleneck: None
cyordereddict: None
dask: None
distributed: None
matplotlib: None
cartopy: None
seaborn: None
setuptools: 38.5.1
pip: 10.0.1
conda: None
pytest: 3.4.2
IPython: 6.2.1
sphinx: None

I answered on your StackOverflow post: https://stackoverflow.com/questions/50095019/combine-complementary-dataarrays
Let me know if that makes sense -- this is legitimately a little trickier than it should be.


opcode1negate push -1 on to the stack

[x] issue #3
[x] follows contribution guide
[x] code change includes tests

Implemented code for opcode 1 negate that number -1 is pushed onto the stack.

The test is failing because of the below error.
String literals can only include ASCII characters. on this
let expected_stack = array!["\x81"];
\x81 is a hexadecimal representation of a character with the code 129, which is not an ASCII character.


Fix Dashboard 4.2.0 issues

Problem
Following issues are reported on WSO2 Monitoring Dashboard

[ ] Unable to override the authorization endpoint when configuring SSO for MI dashboard - https://github.com/wso2/api-manager/issues/1525
[ ] User list limitated by 1500 entries  - https://github.com/wso2/api-manager/issues/1674
[ ] Faulty CAR Files are not listed in the Dashboard or over the CLI - https://github.com/wso2/api-manager/issues/1662

Solution

Affected Component
MIDashboard
Version
4.x.x
Implementation
No response
Related Issues
No response
Suggested Labels
No response

Fixed: User list limited by 1500 entries issue: https://github.com/wso2/product-mi-tooling/pull/348

Fixed : Page Reload issue : https://github.com/wso2/product-mi-tooling/pull/349

Fixed : Faulty CAR Files are not listed in the Dashboard or over the CLI : https://github.com/wso2/product-mi-tooling/pull/350
Please find the sample preview attached.

As per the code review, we have changed the FAULTY CAPP view as follows.


Ensure spec files are up to date before executing

Resolves #54
Problem
Whenever there's a bug or unclear test message that we want to update after students have already started we can't affect students spec files (unless we do something fancy like write a script that re-writes their spec file and have them run a command that downloads and runs it haha)
Solution
Enhance rails grade check to see if the local spec folder/files are up to date with the latest version stored on appdev-projects/upstream version. If they do match, the normal rails grade thing happens. If they don't match, the updated files are downloaded and then the specs are run and submitted to Grades.
Using the GitHub's REST API, a new method can make a GET request to the content endpoint. Next, we need to find the spec sub folder name (usually features, but sometimes scripts or models). Once the sub folder name is known, we can find the actual spec file names and commit SHA's from the API. We can then run git status -suno to see if any spec files have uncommitted changes. Additionally, we can compare the commit SHA of the upstream spec file to the local commit SHA using git ls-files -s PATH_TO_FILE.
If the spec file has uncommitted changes or the commit is different from upstream then the upstream version is downloaded and replaces the local one.
This way, students still just run rails grade and if we need to make an update, they just have to run rails grade again and not some funky command that we make up each time.

Ref

The proposed process to ignore local changes to the spec folder is to:

git fetch upstream

To get the latest changes from the appdev-projects repo. Assumes, that there is an upstream branch already. Gitpod will automatically track upstream.

rm -rf spec/*

Remove all files in the spec/ folder so any new files are ignored.

git remote show upstream | grep 'HEAD branch' | cut -d' ' -f5.chomp

This finds the default branch in the upstream repo, in case we find a situation where some are using main vs master

git checkout upstream/#{default_branch} spec/ -q

Copy the contents of the spec folder from the upstream default branch to the local spec folder.

Notes

I haven't tested the performance speed, but it does seem to slow down the test runs.
Also need to update ruby_grade_runner

@raghubetina I made some significant updates that I think increase the performance and make the code more flexible. Could you provide some additional review when you get the chance?
I had a question about how flexible grade_runner should be in this kind of situation. Specifically, should we assume that a student is running this on Gitpod? If not, should grade_runner be responsible for assigning the upstream branch if it hasn't been created?

@jelaniwoods Nice, this is looking great!

I had a question about how flexible grade_runner should be in this kind of situation. Specifically, should we assume that a student is running this on Gitpod? If not, should grade_runner be responsible for assigning the upstream branch if it hasn't been created?

Since I expect/hope to have DPI students install locally soon (for their own learning but also because we're paying for Gitpod, which will soon switch to usage-based billing for teams), it would be nice (but not urgent) to support both Gitpod and local.

If not, should grade_runner be responsible for assigning the upstream branch if it hasn't been created?

I think that's reasonable, if it hasn't already been created.
Basically, when students clone to their own machine, it's quite common for them to clone to a custom folder name (e.g. rps-rcav-2 when they want to start over from scratch). So we should be able to handle that.
A less likely scenario is that their fork on GitHub is not named the same thing as our repo. I'm okay with assuming that their fork has the same name as our repo, so we can infer the appdev-projects/... reponame from their fork's name.


Housekeeping

Added license headers
README updates
Moved sample files to their own folder

Also, part of the housekeeping is migrating the COS assets, so you'll have to migrate and update the links as well. Can be done in a separate PR if you prefer

The COS assets were updates in a previous PR

Oh woops my bad, must've looked at the wrong file then. Thank you @bdwyer2


google.assistant.embedded.v1alpha1 is deprecated

google.assistant.embedded.v1alpha1 is deprecated. Will google.assistant.embedded.v1alpha2 available soon?

v1alpha2 is now available in the project


General: Support for RoyalRender

Feature

Warning
This PR is still in heavy development.

Adding support for RoyalRender. More description coming 🚧

This has been tested on client site quite well now, so we can merge once the conflict is resolved. @kalisp can you please make sure it is clean, so we can merge and then in sequence the new publisher, and the RR support for maya


Can't not found writable characteristic

I got this exception: BTException{error: BTError.errorWithMessage, message: can't not found writable characteristic}
Both text and rawData with esc_pos_utils plugin

I also have this issue.


LUA wrappers for JUCE – Automatic conversion is broken

Hi,
I try to build a panel for Korg M1. Since there mainly bulk messages are documented, I need to do some parsing in Lua.
According to the internet lua strings should be used to collect raw binary data (as ASCII strings are involved I'd like to avoid the overhead of converting them to hex and back) such as for construction of SysEx messages.
Fortunately juce::MidiMessage is available as class MidiMessage in Lua. Unfortunately MidiMessage:createSysexMessage does not take string parameters. I tried to implement a corresponding overload and didn't succeed, since the default_converters do not work in LAudio.cpp. The whole source file depends on it. So even a simple call like MidiMessage:masterVolume(0.3) does not work as Lua code.
I intend to make the above mentioned panel OpenSource as an example of a completely opensource panel.

i will check that ASAP, strings should be converted betwenn Lua and JUCE

@keinstein Even if the above is maybe an issue, why don't you just load the full sysex message in a MemoryBlock then handle it with getByte, getRange... as several of us are doing?
This is straightforward and I explained it several times in the old forum (if I well remember ;-) )

I think, I can clarify this issue a little bit, now: Ctrlr converts somehow between Lua strings and JUCE strings, but I tried to convert Lua strings to MemoryBlocks. The current implementation is not binary safe, as it somehow assumes nul terminated strings. On the other hand, Ctrlr assumes lua strings to be hex strings, not binary strings, when it comes to MIDI messages. I could fix the impementation, but I don't know whether JUCE strings are binary safe (functions like strlen are not used without explicit convertion to C strings). In comparison C++ strings are binary safe. std::strung::c_str() just adds a 0 at the end, before returning std::string::data().