Allow using system certificate store for TLS

Allows reqwest to use the system certificate store when validating a TLS certificate e.g. for OIDC.
Fixes #203

Thanks @msiemens, you are right. However, I think the line rustls-tls should be replaced by rustls-tls-native-roots?
Please see:

https://docs.rs/reqwest/latest/reqwest/#optional-features and
https://docs.rs/crate/reqwest/latest/features#rustls-tls-native-roots (which enables rustls)

I've adapted the PR to not use the bundled certificates but only the OS certificates.

I think it better to just rely on the OS CA certificates instead if of bundling CA certificates with ChirpStack. What do you think?

I agree, especially considering that Mozilla's CA certificate collection for instance is updated multiple times a year and using the OS certificates would allow updating the certificates without having to update a running ChirpStack installation.


3.6.x

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 9 committers have signed the CLA.:white_check_mark: mmoayyed:white_check_mark: leleuj:white_check_mark: jtgasper3:x: serac:x: battags:x: Eric Domazlicky:x: fjollberg:x: laszlovandenhoek:x: Jérôme LELEUEric Domazlicky, Jérôme LELEU seem not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Need a way to control sentence duplication during tests

Example: When testing for swap entities, I want to be able to have multiple copies of a sentence with different entities swapped. How do I do this in the config file?
Currently "I live in Boston" -> "I live in Mumbai"
We need a parameter to control and have multiple duplicates if desired: "I live in Boston" -> "I live in Mumbai", "I live in Paris", "I live in New York", "I live in London"
Default should be no duplicates (only 1 version of the sentence)

We need to perform experiments to check whether the number of tests applied to common datasets are enough. If it is too small, then we can create new tests by swapping them with different names.


ansible extension doesn't recognize podman installed on the system

Summary
i enabled "*Execution Environment" , *and selected podman, it throws an
error  'Error: Command failed: command -v podman', But infact
i have podman installed and available in default PATH. (/usr/bin/podman)
Extension version
v2.3.7
VS Code version
Version: 1.78.
Ansible Version
ansible [core 2.13.8]
  config file = /etc/ansible/ansible.cfg
  configured module search path = ['/home/mniranja/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/mniranja/venv38/lib/python3.8/site-packages/ansible
  ansible collection location = /home/mniranja/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/mniranja/venv38/bin/ansible
  python version = 3.8.16 (default, Dec 21 2022, 10:58:32) [GCC 8.5.0 20210514 (Red Hat 8.5.0-17)]
  jinja version = 3.1.2
  libyaml = True

OS / Environment
RHEL 8.8
Relevant log output
No response

Send us the output of command -v podman

From my Bash terminal
(venv) [mniranja@mniranja ~]$ command -v podman
/usr/bin/podman
(venv) [mniranja@mniranja ~]$ echo $PATH
/home/mniranja/venv/bin:/home/mniranja/.local/bin:/home/mniranja/bin:/home/mniranja/.local/bin:/home/mniranja/bin:/home/mniranja/.local/bin:/home/mniranja/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/home/mniranja/go/bin:/home/mniranja/go/bin:/home/mniranja/go/bin
(venv) [mniranja@mniranja ~]$

From vscode terminal
sh-5.1$ echo $PATH
/app/bin:/app/bin:/app/bin:/usr/bin:/home/mniranja/.var/app/com.visualstudio.code/data/node_modules/bin

[476 preload-host-spawn-strategy] Warning: waitpid override ignores groups
sh-5.1$ echo $PATH
/app/bin:/app/bin:/app/bin:/usr/bin:/home/mniranja/.var/app/com.visualstudio.code/data/node_modules/bin
sh-5.1$ command -v podman
sh-5.1$

I have to mention here that vscode was installed using flathub repository

@mrniranjan The /usr/bin in flatpak is coming from the runtime. The host one is accessible via /run/host/usr/bin, however the proper way to invoke commands from the host is using flatpak-spawn --host from within the flatpak sandbox.
Folks, is there a way to change the command the plugin uses to invoke podman so I can configure it properly for the sandboxed environment?

On that point, I'm trying to figure out how to use this in Silverblue.  The flatpak version of vscode includes the command /app/tools/podman/bin/podman-remote, which I can't execute from the ansible extension.


[EPIC] Analytics Feature MVP

As a User, I want to be able to aggregate activity entry data, so I can gain business insights and better improve business processes

MVP
Goals

[ ] Generate tabular data based on attributes in activity entries
[ ] Generate data using fixed fields in activity entries
[ ] View all reports created in the organization

MVP task

[x] #237
[x] #238
[x] #252
[x] Finalize MVP state UI for analytics reports in Figma
[x] #263
[ ] Implement the backend for saving reports generated to prevent the need for regenerating the reports

Stretch
Goals

[ ] Have automated report generation capabilities
[ ] Generate data using custom forms in activity entries
[ ] Export data to CSV files

MVP completed


Phase 0: Add support for ES|QL to Serverless

Add the raw handling of ES|QL request/response in Serverless

Done in:

https://github.com/elastic/elasticsearch-serverless-ruby/pull/79


Add discord-hs

There are some upper bounds in place:
aeson-<IP_ADDRESS> (Adam Bergmark<EMAIL_ADDRESS>@bergmark) is out of bounds for:

[ ] discord-hs-0.2.1 (==1.0.*). Joshua Koike<EMAIL_ADDRESS>@jano017. @jano017. Used by: library

vector-<IP_ADDRESS> is out of bounds for:

[ ] discord-hs-0.2.1 (==0.11.*). Joshua Koike<EMAIL_ADDRESS>@jano017. @jano017. Used by: library

0.2.2 should fix. I thought I had pushed it but apparently I didn't.

Thanks


[Feature] Add Validation Annotations

Problem
I cannot add custom validation class annotations to the generated typescript classes from the prisma.schema
Feature Request
If there is a model that looks like this:
model Organization {
  id    String     @id @default(cuid())
  name  String  @unique
  email String
}

It would be nice to have the ability to add annotations as follows:
model Organization {
  id    String     @id @default(cuid())
  /// @IsNotEmpty()
  name  String  @unique
  /// @IsEmail()
  email String
}

that would create a class like this:
export class CreateOrganizationDto {
  @IsNotEmpty()
  name: string;

  @IsEmail()
  email: string;
}

Yea, this is going to prevent me from being able to use this library.

A few months ago, I forked this repo to add some additional features according to our project needs. One of them was to include those class validation decorators. You may want to have a look and try here: https://www.npmjs.com/package/@brakebein/prisma-generator-nestjs-dto


Meeting recordings owned by person who started recording...

Discovered something interesting... In a recent review meeting, Ted started the recording. Now, the recording is "owned" by him. Previously, because these meetings were part of the Teams channel, they were automatically available to the owners of that channel and they were all in one place.
Because the meeting is scheduled by the bot, each meeting is its own chat channel. As a result, the person who starts the recording owns the recording. We will need to download the recordings and then upload them to a more permanent spot. And also change the expiration of them as well.
The recordings should be owned either by everyone or by the bot, they should not expire, and ideally, they should be automatically moved to a shared and commonly accessible location in the Team's sharepoint. This would be very close to what we have today.

This is very interesting. Thanks @markweitzel
We will need to look into the teams meeting creation and see how we can configure it.


Spacing issue on centerMode and Infinite with slideCount < slidesToShow

I was experiencing an issue when there are less slides available than to show with centerMode and Infinite both set to True. The transform3D was setting the value way too high and slides were being pushed off the screen without the arrows showing, since there aren't enough slides to trigger the arrows. Here are the settings on the JS i am using to init the slider:
$('.slickslider').slick({
	dots: true,
	infinite: true,
	speed: 300,
	adaptiveHeight: true,
	slidesToShow: 7,
	slidesToScroll: 1,
	centerMode: true,
	centerPadding: '40px',
	swipeToSlide: 1,
	prevArrow: '<button type="button" data-role="none" class="slick-prev slick-arrow" aria-label="Previous" role="button"></button>',
	nextArrow: '<button type="button" data-role="none" class="slick-next slick-arrow" aria-label="Next" role="button"></button>',
	responsive: [
		{
			breakpoint: 1200,
			settings: {
				slidesToShow: 5
			}
		},
		{
			breakpoint: 992,
			settings: {
				slidesToShow: 3
			}
		},
		{
			breakpoint: 768,
			settings: {
				slidesToShow: 2
			}
		}
	]
});

I corrected this issue with a small change to one of the functions. The fix for this on my end was to modify the getLeft function on line 1105 to:
       if (_.options.centerMode === true && _.options.infinite === true) {
            if (_.slideCount <= _.options.slidesToShow) {
                _.slideOffset += Math.floor(_.slideWidth * (_.options.slidesToShow - _.slideCount)) / 2;
            } else {
                _.slideOffset += _.slideWidth * Math.floor(_.options.slidesToShow / 2) - _.slideWidth;
            }
        }

Now it is spacing the slides properly and responsively! Hopefully this helps if anyone else is running into this issue!
PS. Including the js and min.js in case someone wants them :)
slickjs.zip

Same problem here. @TonyShark19 thanks. Your fix works. Can you submit a pull request instead of attaching a ZIP file?

@orthes glad it worked! I'm new to GitHub, but I'll try!

@orthes I went to submit a pull request and I saw there was already a change for this part of the code. I tested the new JS files and they are working for me with the committed changes instead of mine. Seems things are alright without this change. Can you test on your end to see if the new code solves it for you as well?


Add support for alts

The bot should prompt the user to type all the alts/ids whose problems they want to ignore in the round

was fixed in #12


ConnectToDeviceAsync unable to connect to Bluetooth devices

Steps to reproduce

Turn on the Bluetooth switch on your phone
2.Connect Bluetooth devices using an APP
3.After the APP is successfully connected, turn off the Bluetooth switch on the phone
4.Turn on the Bluetooth switch of the phone again
5.Reconnect the last connected Bluetooth device using the APP

Expected behavior
If you view 'Adapter. Connected Devices', you will find that a previously connected device already exists and cannot be successfully connected again,After waiting for a period of time, an exception 'the task is cancelled' will be reported

Hi @StevenBase,
I'm the friendly issue checker.
It seems like (75.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!

Gents,
I am re-iterating this issue on Android after an upgrade from 2.1.3 to 3. I am creating a different issue around our observations anyways but it is to confirm that the behavior from 2.1.3 to 3 about ConnecToKnownDevice also has changed entirely, which caused us a lot of headache.

Are you caching the Device object after the first connect and trying to reconnect to that?
Turning Bluetooth off will clear the Android ble cache, so you too should clear/null out your Device reference on disconnect and get a new instance if the Device after a new scan.


🐛 In navbar there is no active tab and onhover and animation missing

Description of the bug
🐛 In navbar there is no active tab and onhover and animation missing
I'm a GSSoC'23 contributor please assign me this issue under gssoc label and level.
Please add screenshots (if applicable)

Add any other context about the problem here
No response
Checklist

[X] I have read the Contributing Guidelines
[X] I have checked the existing issues
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

Hello :wave:
Well spotted, do you want to work on it?

yes

can you please me under gssoc23 label and level tag


Entry points, naming

As it stands both Manim and ManimCommunity have their entry module named manim.py, which is a problem when both are installed and in the environment variables, as there'll be two instances of manim.py to pick from. To keep ease of access I'd suggest something along the lines of renaming this manim.py to manimc.py (or something else) so that code can be quickly run on either installed version, which those developing here will likely want to do.

So here's the thing: we have to find a solution such that it will fix the clash situation for devs, and will not change anything for the end user (for now, at least). The easiest way to do this is to allow our version to be ran in two different ways. In the usual python -m manim.py and also in a new way python -m manim-com.py. If you are a dev, you know you have to use the second one to avoid conflicts. If you are a user, regardless of which version you have, you use the first one.

From trying a simple renaming on my side I can already say there's gonna be a bit more needed. Even if I explicitly run the file from ManimCommunity, when both folder are in the env variables it'll actually use the manimlib from the main Manim, not ManimCommunity. This isn't all that surprising though when looking at manim.py, as it simply uses import manimlib, which will grab the first manimlib it's going to find.

I think the problem is that currently, manim is ran directly from the manim.py file at the top level of the repo. There shouldn't be any .py files at the top level. Instead, the entrypoints should be designated using a setup.py file. All the .py files should go inside manimlib/, and only use local imports. In that way, our version will never try to do import manimlib which will grab the global installation.

numpy seems to do global imports too, unless I'm missing something [1][2].

Huh. That's interesting. I wonder if those are typos?
In that case, numpy would also have problems if there were two versions of numpy installed in the same machine.
Since we are trying to avoid that, I still think the best course of action (at least for now) is to try to import everything locally.

Related: #15. Once that is merged, it'll be easier to work on adding the right entrypoints here.


Bluetooth: Controller: Connection Parameter Update indication timeout

Note
This sample is just to provoke the issue. This is obviously not a real scenario but it's the easiest way to show it.
Describe the bug
When a central device updates connection parameters a few times in a row, the central sends one of the update indications too late. That way, once it is finally sent out, the instant for which the
the new parameters shall be valid lies then in the past. The connection now gets disconnect either with reason 0x08 (timeout) or 0x28 (instant passed).
Devices involved for this sample:
Central:    nRF52840-USB Dongle (nrf52840dongle_nrf52840)     https://docs.zephyrproject.org/latest/boards/arm/nrf52840dongle_nrf52840/doc/index.html
Peripheral: nRF52 DK            (nrf52dk_nrf52832)	      https://docs.zephyrproject.org/latest/boards/arm/nrf52_pca10040/doc/nrf52_pca10040.html

To Reproduce

Build and flash the provided sample to the usb dongle (Scripts for building and viewing RTT output are included)
Hook up the nRF52 DK to a computer and start nRF Connect (v3.6.0)
Load the Bluetooth Low Energy App, select the device and let it start advertising.
Keep the DK close to the nRF dongle, it will now connect/pair and update connection parameters
Both sides will notify about the connection being terminated because of a timeout

Expected behavior
The connection update indication should either be sent in time, or if not possible, the connection update procedure should fail entirely.
Impact
Need to come up with weird workarounds (timeouts etc.) in order to proceed
Logs and console output
RTT Log from central:

Setting new connection params...
on_le_param_updated (0x200009c8): e8:34:60:2b:56:15 (random) interval 16 latency 0 timeout 100
on_le_param_updated (0x200009c8): e8:34:60:2b:56:15 (random) interval 17 latency 0 timeout 500
on_le_param_updated (0x200009c8): e8:34:60:2b:56:15 (random) interval 18 latency 0 timeout 1000
on_le_param_updated (0x200009c8): e8:34:60:2b:56:15 (random) interval 19 latency 0 timeout 2000
Done!
Disconnected: e8:34:60:2b:56:15 (random) (reason 0x08)

Ellisys trace:
Ellisys_trace.zip
nRF52 USB dongle sample code:
nRF52840_Dongle sample.zip

Slave dissappeared for a number events, while master was trying to send an empty packet.
When slave re-appeared the central sends connection update with instant in the past. Looks like an issue with setting the instant when the packet is queued, not when it is first actually sent.

@cvinayak this looks like an issue in the Controller as per @joerchan's analysis.

Yes, the instant is set when the UPDATE_IND PDU is enqueued from ULL to LLL. LLL operating as packet controller, will not parse the PDU and update it. This will have to be vendor specific.
Even if LLL would set the instant on first transmission, if the transmissions are not ack-ed (like consecutive CRC errors in every connecction event), the instant will pass. But, as procedure timeouts are not used for connection update, instant passed could be the correct outcome (and hence, the rationale behind setting the instant when connection update procedure is enqueued).

I was able to reproduce it using the default peripheral sample (see attachment). However, I had to explicitly set CONFIG_BT_CTLR_CONN_PARAM_REQ=n in the prj.conf. Otherwise the peripheral would just send a connection parameter update request after the central was done with it's connection update indications. This behavior keeps the connection alive.
nrf52dk_nrf52832_peripheral.zip

Do you have a sniffer log that you can attach here?

Unfortunatly not, my sniffer setup is unable to log the communication. The last thing I was able to see was the connection request. I'm not sure what I am doing wrong here.

Slave dissappeared for a number events, while master was trying to send an empty packet.
When slave re-appeared the central sends connection update with instant in the past. Looks like an issue with setting the instant when the packet is queued, not when it is first actually sent.

Slave disappearing for a number of events seems to be caused by a bad connection event timing by the master. There is a connection parameter update indication in connection event 27. The new connection parameters are scheduled for connection event 33 and this is exactly when the slave disappears. Connection interval at that time is 20 ms, transmit window size is 1.25 ms and transmit window offset is 0 ms. The distance between connection event 32 and 33 is 21.418 ms (please see attached screenshot), which is bigger than the connection event + transmit window offset + transmit window size. The slave probably emerges again when the receiving window gets big enough (due to window widening). My question is: what is causing the bad timing by the master

?

@cvinayak could you please comment on this?

It appears like the Zephyr controller has sent the conn_update_ind PDU without filling the window offset value of 1.
Could you please recheck with the following in your prj.conf:
CONFIG_BT_CTLR_ADVANCED_FEATURES=y
CONFIG_BT_CTLR_SCHED_ADVANCED=n

Tested the attached sample on a nRF52840DK modified prj file to use UART console (my WIP branch rebased over latest upstream master 27529e0c0d) and do not see any issues (makes me believe this is not a bug in controller source code).
Console output:

nRF sniffer trace (wireshark) file, gh_29636_success_nrf52840dk_nrfconnect.pcapng:
gh_29636_success_nrf52840dk_nrfconnect.zip
Tested the attached sample on nRF52840DK unmodified prj file:
RTT output:

nRF sniffer trace (wireshark) file, gh_29636_success_nrf52840dk_nrfconnect_rtt.pcapng
gh_29636_success_nrf52840dk_nrfconnect_rtt.zip
Tested the attached sample on nRF52840Dongle unmodified prj file:
(no console, as I dont have SWD pinheads soldered, I flashed the hex using nrfconnect desktop's programmer)
nRF sniffer trace (wireshark) file, gh_29636_success_nrf52840dongle_nrfconnect_rtt.pcapng
gh_29636_success_nrf52840dongle_nrfconnect_rtt.zip
I am not able to reproduce the issue on the latest upstream master with my work in progress on top. Please provide details of your zephyr commit hash that reproduces the issue. Also, the dongle revision details (small white sticker on the dongle, mine is PCA10059 1.2.0, 2020.7 ).

Hi,
thanks for the update!
I am on commit https://github.com/zephyrproject-rtos/zephyr/commit/cc4708e3170bfedcc2be33d8dc64c48534a76b0f and the my dongle is PCA10059 1.0.0 2018.34. I flash it using a J-Link programmer.
Because I update my master frequently I just checked again that the issue still occurs and it does:

That being said, when i edit my prj.conf to contain your suggested paramerters (see below), I will never run into a connection timeout.
CONFIG_BT_CTLR_ADVANCED_FEATURES=y
CONFIG_BT_CTLR_SCHED_ADVANCED=n
For me this is an acceptable workaround. If you need anything else from me to find the root cause, just let me know.
Thanks a lot!

Could related to https://github.com/zephyrproject-rtos/zephyr/issues/25440

@Guayusa please verify the fix: https://github.com/zephyrproject-rtos/zephyr/pull/31477

@Guayusa please verify the fix: https://github.com/zephyrproject-rtos/zephyr/pull/31477

I checked out your sample and let it run without the workaround mentioned earlier. I did not face any disconnects anymore.
LGTM!

I checked out your sample and let it run without the workaround mentioned earlier. I did not face any disconnects anymore.
LGTM!

I checked out your branch and let it run without the workaround mentioned earlier. I did not face any disconnects anymore.
LGTM!

@Guayusa Thank you for the testing and fast response.

I checked out your branch and let it run without the workaround mentioned earlier. I did not face any disconnects anymore.
LGTM!

@Guayusa Thank you for the testing and fast response.


Use generation 2 maps in general, 1 for old munis

For disestablished munis, we show the old boundary in yellow (to match the colour of the warning banner), and then load the 2016 boundaries on top of that.

when hovering:

I really like the presentation here

@longhotsummer is this waiting on changes to mapit to work? it isn't working for me locally.

it works now


[Outlook] (log event) Add article

Related to PR https://github.com/OfficeDev/office-js-docs-reference/pull/1203.

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

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-crm.md
:white_check_mark:Succeeded
View

docs/overview/office-add-in-availability.md
:white_check_mark:Succeeded
View

docs/reference/manifest/extensionpoint.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 1de58e6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-crm.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 0926e5a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/mobile-log-crm.md
:bulb:Suggestion
View
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-crm.md

Line 227, Column 115: [Suggestion: preserve-view-not-set - See documentation] Did you mean to link to a specific version? It's usually better not to specify a version, so the link always goes to the canonical version. If you really need to link to a specific version, add &preserve-view=true to the URL: /graph/api/resources/extended-properties-overview?view=graph-rest-1.0. Otherwise, remove the view parameter.

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 b96bb36:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-crm.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 689441e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-crm.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 4b088c6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.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 84f4f18:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.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 060055e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.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

We may need to update Add-ins for Outlook Mobile to call out the MobileLogEventAppointmentAttendee extension point.

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

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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

We may need to update Add-ins for Outlook Mobile to call out the MobileLogEventAppointmentAttendee extension point.

Good catch. Updated.

Docs Build status updates of commit 391072e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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 6bfeded:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

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 0029643:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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 e089437:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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 6431e2b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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

Looks good to me.
-Manbendra

Docs Build status updates of commit 8186f9d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-ios-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-ios-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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 2e9770f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/outlook/mobile-log-appointments.md
:warning:Warning
View
Details

docs/images/outlook-android-log-appointment-details.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-ios-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-ios-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md

Line 254, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 478, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 536, Column 245: [Warning: bookmark-not-found] Cannot find bookmark '#implement-viewing-appointment-notes' in 'outlook/mobile-log-appointments.md'.
Line 536, Column 306: [Warning: bookmark-not-found] Cannot find bookmark '#implement-viewing-appointment-notes-1' in 'outlook/mobile-log-appointments.md'.

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 9cd6686:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/outlook/mobile-log-appointments.md
:warning:Warning
View
Details

docs/images/outlook-android-log-appointment-details.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-ios-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-ios-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.md
:white_check_mark:Succeeded
View

docs/toc.yml
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md

Line 254, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 478, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

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 53706f7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-ios-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-ios-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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 dbeafbf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-ios-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-ios-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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

@samantharamon Approved and ready to merge! Cheers, linda

Docs Build status updates of commit 8251d96:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-ios-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-ios-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/online-meeting.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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 1e73114:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-ios-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-ios-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/online-meeting.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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 a1cfcaf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/images/outlook-android-log-appointment-details.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-android-view-appointment-log.jpg
:white_check_mark:Succeeded
View

docs/images/outlook-ios-log-appointment-details.png
:white_check_mark:Succeeded
View

docs/images/outlook-ios-view-appointment-log.png
:white_check_mark:Succeeded
View

docs/outlook/add-mobile-support.md
:white_check_mark:Succeeded
View

docs/outlook/mobile-log-appointments.md
:white_check_mark:Succeeded
View

docs/outlook/online-meeting.md
:white_check_mark:Succeeded
View

docs/outlook/outlook-mobile-addins.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


"Best practices" documentation

Is your feature request related to a problem? Please describe.
When working with complex designs, it's fairly easy to fall into patterns which are functionally correct (i.e., they will produce the correct geometry) but which will cause problems at a later point. Some examples:

Making many copies of a component when gf.components.array is applicable can slow down rendering
Manually defining wire paths when a bus router or auto-router would work can increase developer toil
Manually lining up subcomponent offsets instead of connecting them with ports is harder to maintain

Describe the solution you'd like
A section on the docs site covering the most common pitfalls and "power user" tools would go a long way towards making gdsfactory more accessible for new users.

Thanks! Any further additions to this doc as more best practices are established would be welcome.


Refactor log messages of crypto module

Purpose
$subject
Check List

[ ] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #18613 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #18613   +/-   ##
=======================================
  Coverage   15.15%   15.15%
=======================================
  Files          48       48
  Lines        1254     1254
  Branches      197      197
=======================================
  Hits          190      190
  Misses       1050     1050
  Partials       14       14

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 a3b6f85...d27bd23. Read the comment docs.


cdh: move kms crate to cdh module

the kms crate is used exclusively by cdh, so we don't need to maintain it as individual crate, which helps with naming conflicts and reduces build complexity.
~note: this currently builds on pr #814~

Oh. Now KBS imports kms as a dependency here as backend impl of KBS. Now if we want to import the denpendency in trustee we need to use confidential-data-hub, which will also import image-rs and a lot of other dependencies.
So probably we'd better move kms crate out to deps as it would be used outside cdh.


SGE - Always casting Dyskrasia (II)

Sage often falls into a state where it just casts Dyskrasia (II) over and over..
even if not a single enemy is nearby or there is even no combat at all.

in the past this was my problem

look for conflict with other plugins.

I mean.. RSR is the one casting. If I disable it, it stops.
And if I re-enable it, it isn't in that state anymore for some time.
I am not sure what you are suggesting?

I had the exact same problem. Enable rsr and running in the city, consatant casting dyskrasia. Culprit was Sloth.

I.. don't use sloth, but even if.. why would RSR cast anything at all ?

What level are you on sage?

But it happens when downsync'd to 60, 80 and 90 too.

Unable to reproduce, tested on level 90 sage out of combat with no enemies near by


Open URL (feature request)

It'd be handy to be able to open a URL if the cursor is located within it, or at least to highlight the URL and perhaps I could then get iTerm to launch it.

I think this can be left to the terminal emulator. For example in iTerm2, you can hold Command and hover over a link to open it.

@zyedidia thanks for the suggestion; two things:

I often like to use the keyboard only.
Your iTerm2 does not work for me when URLs are wrapped. As you can in the image below, only the first part of the URL is underlined (and will be opened when clicked, yielding a 404.)

This iTerm2 issue sounds like my own, but not sure what to do about it.

Changing the iTerm2 option to yes doesn't do anything for me.

It seems the terminal emulator would rather not be able to handle it: for example, how does it know that the whitespace at the beginning of 2nd line in the screenshot (the ruler) is not a part of the wrapped text?
So it seems it should be implemented on the editor level, but rather not in Micro itself but as an external plugin. I think this is exactly a kind of feature to implement in a plugin.

Yeah, this is a good point and should be implemented in the editor at some level.

@zyedidia, ah did not know about the toggle. I imagine I'd have similar problems when using spell checkers which alter the left margin.

Hyperlinks (a.k.a. HTML-like anchors) in terminal emulators proposed a new escape code to open URLs and it is already widely implemented.

Using Wezterm I am able to open links if they are directly in the shell prompt or in Vi (just with a single click without any Ctrl or else) but not in Micro.

I can propose something like foot's terminal approach

I made a plugin for this feature - https://github.com/pjg11/micro-urlopen

Thank you @pjg11 !


Highlight items with particular codes mentioned in the query string

We don't persist these highlighted items.
Merge this before #59.

How do you use this? ?items=0100 doesn't work for me


Added OrangePI 2G IoT

PR Checklist

[ ] No broken links found using link-checker.

Linkchecker
Use the following command to check the broken links.
docker run --rm -it ghcr.io/linkchecker/linkchecker --check-extern http://<IP_ADDRESS>:4000

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.2 out of 3 committers have signed the CLA.:white_check_mark: samson0v:white_check_mark: imbeacon:x: msvitelskaYou have signed the CLA already but the status is still pending? Let us recheck it.


Initial Commit of SP

Added the Playbook, Connector and Scenario Record

All things look good from a development perspective.
Please add SP documentation in next PR


Small refactoring Core and SoC Simulation

Cool!  Will it be SPI or QSPI)?

SPI, then I can reuse the design to create a QSPI later, which is a bit more complicated to implement. Adding the SPI interface will make the SoC able to communicate with sensors. I have some sensors at home and will test it.


Doesn't work strapi 3.6.0

(node:5024) UnhandledPromiseRejectionWarning: ValidationError: [0] must be a `object` type, but the final value was: `[
  {
    "section": "\"plugins\"",
    "displayName": "\"Access the Navigation\"",
    "uid": "\"read\"",
    "pluginName": "\"navigation\""
  },
  {
    "section": "\"plugins\"",
    "displayName": "\"Ability to change the Navigation\"",
    "uid": "\"update\"",
    "pluginName": "\"navigation\""
  }
]`.
at validateRegisterProviderAction

seems like you can change the bootstrap.js action registration to
  actionProvider.register(actions[0]);
  actionProvider.register(actions[1]);
``
to fix it ?

Hi @davidsielert ,
New release 1.0.1 provides compatibility with 3.6.0 version of Strapi.


Nix package available

Just wanted to mention that I've written way-cooler nix package definition. So it is now available to NixOS users and those who use Nix package manager.

Hey that's sweet, thanks for doing that. I'll add that to the README. However, I'm afraid I haven't used nix before so I wouldn't know if there are any special instructions I have to say. Feel free to send a patch clarifying the wording if necessary.

Oh, also is there some way I can notify/update the package when a new version of Way Cooler comes out? I have access to the AUR package, and I know how to update it and I would like to make sure they can stay in sync.

@Timidger, thanks for adding info to README. There is no special instructions, it installs just like any other application.
For new versions:
Short answer: the easiest way I see for you is to open a new issue at NixOS/nixpkgs repository and mention package maintainers, currently it's me.
The reason behind that is the way how nix packages are defined, it requires a accumulated sha256 checksum of all it's Cargo dependencies. In NixOS to calculate it, you just make a build of package with fake checksum and system will calculate new one for you. I don't know how one could calculate in on his own without using Nix package manager.

Ok, we'll cross that bridge when we come to it (next version will be 0.6.0, if it wasn't obvious from the milestones on the github page). When I release it I'll open an issue/PR in that repo and @mention you.


Not Opening on real device

Been experiencing issue of opening epub on IOS device on an emulator the it easily works but when on a real device it does not open any help is highly appreciated

please see the installation steps in specific Info.plist section
https://github.com/victorsoares96/epubjs-react-native?tab=readme-ov-file#installation

i am using this versions
"@epubjs-react-native/core": "1.4.0-beta.45",
"@epubjs-react-native/file-system": "^1.1.2",
"react-native": "0.72.12",
"react-native-webview": "^13.8.5",
"react-native-gesture-handler": "^2.16.0",
and i add LSSupportsOpeningDocumentsInPlace
 this to info.plist but experiencing issue of opening epub on IOS real device (stuck in loading 0%) but not in ios simulators

try run npx pod-install in your ios directory again after add LSSupportsOpeningDocumentsInPlace key

and use @epubjs-react-native/core: "1.4.1

Is this version have injectjavascript function? Also when i try npx pod install my system ask me a path . So do u have any idea on which path should i give

Yeah, this version have injectJs and contains the fix for this issue.. about pod install you can run npx pod-install ios inside root of your react native project, the first argument after npx pod-install is a path where project ios files are located

I'm developing with expo and facing the same issue on iOS.

I'm developing with expo and facing the same issue on iOS. It works fine when the src is a remote file but not when it's local.

check if you use the latest version(1.4.1) and see the installation steps in specific Info.plist section
https://github.com/victorsoares96/epubjs-react-native?tab=readme-ov-file#installation

Try to add key mentioned above in expo app.json, see more in expo docs:
{
"ios": {
"infoPlist": {
"LSSupportsOpeningDocumentsInPlace": true
}
}
}
https://docs.expo.dev/guides/permissions/#ios

And if you use expo managed project with expo-document-picker try to use this:
const { assets } = await DocumentPicker.getDocumentAsync({ copyToCacheDirectory: false });

Adding LSSupportsOpeningDocumentsInPlace to info.plist and setting copyToCacheDirectory to false on iOS worked. Thanks.

awesome! i'll close this issue, the author can reopen if need


No cursor: pointer in most places

There is no "hand" cursor when hovering on reactions, servers on the right side, users on the right side, channels inside servers, channels options, buttons on the bar below, inside the settings menu, etc...

Works just fine, thanks 👍


In preview: Using an HSM Code Signing Cert, CI/CD fails

This is due to a missing mandatory settings.json parameter.
In the Sign step of CI/CD I receive this error:
Secrets: {"licenseFileUrl":"***","insiderSasToken":"***","codeSignCertificateUrl":"","codeSignCertificatePassword":"","keyVaultCertificateUrl":"","keyVaultCertificatePassword":"","keyVaultClientId":"","gitHubPackagesContext":"","applicationInsightsConnectionString":""}
    artifactCacheKey:
    containerName: bc5822555729
    _azureCredentialsJson: ***
    _timestampService: http://timestamp.digicert.com
    _digestAlgorithm: SHA256
    _pathToFiles: ./.buildartifacts/Apps/*.app
    _parentTelemetryScopeJson:
Error: Unexpected error when running action. Error Message: Cannot process command because of one or more missing mandatory parameters: settingsJson., StackTrace: at <ScriptBlock>, D:\a\_temp\197b8bd8-df1e-[41](https://github.com/BMI-Software/OfficeProducts-AppSource/actions/runs/5822555729/job/15793900820#step:9:42)94-a21f-3f81[44](https://github.com/BMI-Software/OfficeProducts-AppSource/actions/runs/5822555729/job/15793900820#step:9:45)8729df.ps1: line 4 <- at <ScriptBlock>, <No file>: line 1
Error: Process completed with exit code 1.

Since I am using an HSM Cert, providing a proper keyVaultCodesignCertificateName value in .AL-Go/settings.json should be all that is required.
This was working just fine for several weeks.  All of our projects began to fail simultaneously, starting roughly 20 hours ago.
I'm not sure if this is a duplicate of #652

What version of AL-Go are you running?
preview?
Did you upgrade AL-Go system Files ~20 hours ago?

For now you have two options really

Revert the PR which updated the AL-Go System files ~20 hours ago
Wait for the PR I created above to be merged in and deployed to preview - will happen tomorrow morning european timezone.

What version of AL-Go are you running? AL-Go for GitHub,d15c25e25c4b0033da9f99970e3a420e231f7fbc
preview? Yes
Did you upgrade AL-Go system Files ~20 hours ago? Yes

Ok, thanks Freddy.  It's currently late here in the US.  I'll first try the update in the morning.  If that doesn't work, then ill revert the PR and give that a go.

You will need to update AL-Go System Files, before it works (after we submit a fix) - then it will work.

New preview should be deployed now - you should be able to update and sign

Thank you Freddy.  I can confirm this issue has been resolved!


Change test script to run on MacOS

When using cwd in withCreateProcess, absolute paths should be used to ensure portability. See doc for cmdspec :: CmdSpec. See also haskell/process#87

Thanks for the contribution!


Server Error - Function getBody() on null

Hi,
I'm new to Grav so apologies for my lack of technical knowledge of it's inner workings.
I've recently installed the FreshDesk plugin. I've added it to a modular page using the built in Form.md (that comes with Antimatter).
However, once i've added the shortcode and try to submit a ticket, it fails with:
Server Error
0 - Call to member function getBody() on Null.
It also appears to break my other contact form with this error:
Server Error
0 - Freshdesk "subject" is required.
Could you please help resolve this issue?
Thanks in advance.

Hey @DYNSOL, I can't reproduce this. Can you please share your code? (the .md file of the page containing the form, as well as the template you're using) Thanks!

@DYNSOL Gentle bump :)

Closing for now, feel free to reopen with repro steps.


How to download H5 files?

Dear Author, I read this paper and want to test this model on my small Sentinel-2 dataset. However, I  failed to download these H5 weights files. There are some warnings like that "This repository is over its data quota." when I use git Bash and LFS to download these files. Is there other ways to download these weight files?

Or you can upload these data to Google Drive, is it possible?

Or could send me the single weight file "voting/unet_16f_2conv_762/train_output/model_unet_Voting_final_weights.h5" to my Google Email<EMAIL_ADDRESS>please, I really need it

We just updated our repository and added some scripts to help anyone who want to download the weights. Inside the src/utils directory you can run:
python download_weights.py
python unzip_download_weights.py


Update React Bootstrap package

Updating from beta 9 to beta 11 to fix issues with overlay triggers & popovers

Good fix @daviddyess and @JosefBud !

@daviddyess gets all the credit for this one, I'm only a mere vessel


bypassing -- Your connection is not private error

Is there a programatic way to get past this screen.  This will be another big issue for other developers.

does "get past this screen" means ignoring security warning?

Yes!  😄

Sorry for confusing language!

I don't have a site that can test this, not sure if any of the security / SSL related switches below can help, which can be triggered during launch time. https://peter.sh/experiments/chromium-command-line-switches/

@kensoh thank you for your advice.
@garris Seeing the site mentioned by @kensoh, I found the switch that helps to resolve the problem. --ignore-certificate-errors might be your help.

Great -- I will try adding that to chrome flags.  Thank you!

Yes.  I can confirm that both methods eliminate the security wall.
This is the BEST option...
chromy.chain()
   .ignoreCertificateErrors()
   ...

Adding this also works...
--ignore-certificate-errors

but  if you also enable the "window" option the following warning appears (does not appear in a screenshot if the window option is false)

Thanks for addressing this!


[Bug] yarn build exits with code 0 when getRoutes fail

Environment
npx envinfo --system --npmPackages react* --binaries --npmGlobalPackages react* --browsers

npx: installed 1 in 2.466s

  System:
    OS: macOS 10.14.2
    CPU: (8) x64 Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz
    Memory: 244.29 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 10.15.0 - ~/.nvm/versions/node/v10.15.0/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.15.0/bin/npm
  Browsers:
    Chrome: 72.0.3626.119
    Firefox: 64.0.2
    Safari: 12.0.2
  npmPackages:
    react: ^16.6.3 => 16.7.0
    react-dom: ^16.6.3 => 16.7.0
    react-hot-loader: ^4.3.12 => 4.6.3
    react-static: ^6.0.18 => 6.1.5
  npmGlobalPackages:
    react-static: 6.3.3

Steps to Reproduce the problem
$ nvm use node
Now using node v10.15.0 (npm v6.4.1)
$ react-static --version
6.3.3
$ react-static create --name=broken
# select basic template

# modify `getRoutes` in static.config.js to break the build
# throw "broken-build"

$ yarn build
yarn run v1.13.0
$ react-static build

=> Info: No 'siteRoot' is defined in 'static.config.js'. This is suggested for absolute urls and a sitemap.xml to be automatically generated.

=> Cleaning dist...
=> [✓] Dist cleaned
=> Building Routes...
  Error: broken-build

✨  Done in 3.73s.
$ echo $?
0

Expected Behavior
return 1

Duplicate of #946


dubbo广播模式调用有bug

[ ] I have searched the issues of this repository and believe that this is not a duplicate.
[ ] I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.3
Operating System version: win7
Java version: jdk8

Steps to reproduce this issue
consumer c1, 广播调用下面三个接dubbo接口方法：
productor p1 执行结果p11
productor p2 执行结果抛出异常RemoteAccessException
productor p3 执行结果抛出异常IllegalArgumentException
消费者c1广播调用后，最终的取值是p1, p2, p3 的结果？
很有可能取得是生产者p1的结果
Pls. provide [GitHub address] to reproduce this issue.
生产者p2或者p3的结果

What do you expected from the above steps？
Actual Result
很有可能取得是生产者p1的结果
Just put your stack trace here!

我试着通过修改下面的方法，修改了这个bug

我觉得可以提前抛出异常，没有必要等到最后抛出异常

https://github.com/apache/dubbo/issues/7173#issuecomment-773759592
我觉得还是要最后抛异常，若是某个服务报错就直接抛异常，后续服务就收不到广播通知，失去了广播的意义了。我理解的广播是并不关心结果的，主要是要通知各个服务。

Let’s discuss this issue:
In the broadcast mode, when a node has a problem, do you need to continue to notify other nodes in the future?
When a node is abnormal, then notify other nodes, such as broadcast notification to update the cache. In this case, this notification is not guaranteed for consistency. Assuming that there are n nodes, n-1 have been notified, and there is no node left Update, so on the whole, this notification is problematic. Therefore, throwing exceptions in advance and throwing exceptions at the end are both unreliable in terms of results. It is better to report errors in advance to reduce resource occupation.

   consumer通知所有provider全部失败，这种极端情况下仍采用全部通知后再抛异常这种策略，确实会导致consumer资源浪费的问题。但是考虑到另外一种场景，provider处理能力不一样可能部分调用存在超时情况，亦或是网络原因导致部分失败部分成功。这样都不能单纯的说是consumer端的这个通知有问题。
    所以我觉的应给这个广播模式添加策略选择，一是出错就结束，二是不管报错与否都要全部通知，三是使用一个阈值来控制，超过阈值就不再通知。
    我觉得使用阈值比较合理，通过阈值我们也可以设置-1让它出错就不再继续调用，设置任意0~100的数表示报错百分比到达这个值就不再继续调用

@dkisser 这个确实是一个问题，可能由于网络状况导致调用失败，但是 provider 端已处理成功。加阈值控制我觉得可行。@AlbumenJ 你的意见了？

I think it is reasonable to add a threshold for broadcast cluster.
There are still some issues to consider:

We need to ensure forward adaptability, so that users no need to worry about inconsistent behaviors due to upgrading to the new version.
Is the threshold corresponding to a percentage or an absolute value. Such as 20 is means 20 percent of all providers or just 20 providers.
Shall we notify users when an error occurs if they already specify a threshold

I agree with you.
there is another issue that needs to be considered:
it is more reasonable to add this threshold to that position. Because for other modes, such as failover, this parameter is not needed, it is only required in broadcast mode.

Threshold represent for a percentage, For example, 20  stand for 20 percent of all providers.Compatibility issues is easy to solve, wo can use 0 for the default threshold , in this way if exception occured ,it will throws it as the old version did.

By the way, is it appropriate to put this threshold parameter on the reference? After all, this parameter is only used by broadcast cluster. Are there other more suitable places?

&READY-TO-CLOSE&

close #7173 via #7174


dash clear live stream playback issue

Hi,
We are trying to play a unencrypted dash live stream from envivio encoder but we are getting assertion  failed errors.
mpd is as follows.
<MPD xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"     xmlns="urn:mpeg:dash:schema:mpd:2011" xsi:schemaLocation="urn:mpeg:dash:schema:mpd:2011     DASH-MPD.xsd" type="dynamic" minimumUpdatePeriod="PT10.000S" minBufferTime="PT5.000S"     maxSegmentDuration="PT10.080S" availabilityStartTime="2015-08-01T15:24:12Z"     timeShiftBufferDepth="PT60.000S" profiles="urn:mpeg:dash:profile:isoff-live:2011">
<Period id="0" start="PT0S">
<AdaptationSet mimeType="video/mp4" segmentAlignment="true" startWithSAP="1"     maxWidth="720" maxHeight="576" maxFrameRate="25" par="16:9">
<SegmentTemplate timescale="90000" initialization="$RepresentationID$/Header.m4s" media="$RepresentationID$/$Time$.m4s" presentationTimeOffset="676091987">
<SegmentTimeline>
<S t="676099187" d="900000" r="5"/>
</SegmentTimeline>
</SegmentTemplate>
<Representation id="video1" width="720" height="576" frameRate="25" sar="64:45" scanType="progressive" bandwidth="1500000" codecs="avc1.64001E"/>
</AdaptationSet>
<AdaptationSet mimeType="audio/mp4" lang="en" segmentAlignment="true" startWithSAP="1">
<SegmentTemplate timescale="90000" initialization="$RepresentationID$/Header.m4s" media="$RepresentationID$/$Time$.m4s" presentationTimeOffset="676091987">
<SegmentTimeline>
<S t="676100881" d="898560"/>
<S t="676999441" d="904320"/>
<S t="677903761" d="898560" r="2"/>
<S t="680599441" d="904320"/>
</SegmentTimeline>
</SegmentTemplate>
<Representation id="audio1" audioSamplingRate="16000" bandwidth="96000" codecs="mp4a.40.2">
<AudioChannelConfiguration schemeIdUri="urn:mpeg:dash:23003:3:audio_channel_configuration:2011" value="2"/>
</Representation>
</AdaptationSet>
</Period>
</MPD>

And we are getting the following error on the shaka player.

video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>970032 latestAvailableSegmentEndTime 5179.632011111111
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>970032 latestAvailableSegmentEndTime 5179.573188888889
Starting each stream from 5164.593189108234
Timestamp correction -5119.493188111111
Assertion failed:
video.currentTime (45.100000888889554) should be within the stream limits {"start":5119.94301121983,"end":5119.94301121983}
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>970032 latestAvailableSegmentEndTime 5179.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>970032 latestAvailableSegmentEndTime 5179.632011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Player error CustomEvent {detail: Error: The browser failed to decode the media content.
at shaka.player.Player.onError_ (http://1…, srcElement: null, target: s…a.p…r.Player, currentTarget: s…a.p…r.Player}bubbles: truecancelBubble: falsecancelable: falsecurrentTarget: shaka.player.PlayerdefaultPrevented: falsedetail: Error: The browser failed to decode the media content.
at shaka.player.Player.onError_ (http://<IP_ADDRESS>/shaka-player-master/lib/player/player.js:403:15)eventPhase: 0path: Array[0]returnValue: truesrcElement: nulltarget: shaka.player.PlayertimeStamp:<PHONE_NUMBER>170type: "error"proto: CustomEvent
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5189.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5189.616011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5199.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5199.600011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5209.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5209.584011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5219.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5219.632011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>970032 latestAvailableSegmentEndTime 5229.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>970032 latestAvailableSegmentEndTime 5229.616011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5239.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5239.600011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>629425 latestAvailableSegmentEndTime 5249.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>629425 latestAvailableSegmentEndTime 5249.584011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5259.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5259.632011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5269.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime<PHONE_NUMBER>485016 latestAvailableSegmentEndTime 5269.616011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:
Updating manifest...
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 866 latestAvailableSegmentEndTime 5279.573188888889
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 866 latestAvailableSegmentEndTime 5279.600011111111
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Updated SegmentIndex 2: 0 -> 6 SegmentReference(s).
Updated SegmentIndex 3: 0 -> 6 SegmentReference(s).
video/mp4; codecs="avc1.64001E" is supported
audio/mp4; codecs="mp4a.40.2" is supported
Manifest updated!
Assertion failed:

Http headers are given below.
curl -I http://<IP_ADDRESS>/dash/test1/manifest.mpd
HTTP/1.1 200 OK
Content-Length: 0
Server: Halo Origin Server
Content-Type: text/xml
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Origin,Content-Type,Access-Control-Allow-Origin,Range,Accept
Access-Control-Expose-Headers: Access-Control-Allow-Origin, Content-Length, Content-Type, Date, Range, Server, Transfer-Encoding
Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
Date: Sat, 01 Aug 2015 15:37:07 GMT
Connection: keep-alive
Do we need to change anything?
Regards,
Randeep

Looks like its the issue with time. its either trying to play from the past or from future. Can someone help me identifying this.

What does this actually says
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 3876.003000020981 latestAvailableSegmentEndTime 16023.052288888888
@availabilityStartTime seems to be inaccurate; some segments may not be available yet: currentPresentationTime 3876.003000020981 latestAvailableSegmentEndTime 16023.104544444444
Is the player trying to play the segments which is not generated yet? or the ones which were too old?

Thanks for the report we'll take a look.

I believe there may be an issue with how the player handles the presentationTimeOffset attribute for live content with SegmentTemplate + SegmentTimeline.

Does the content playback in 1.3.x?
Are you able to host any content that uses presentationTimeOffset to a public location?

@randeeppr We are still waiting for your feedback on this.

Is this still an issue for you?
Does the content play in 1.3.x?
Are you able to share sample content with us that triggers this bug for you?  If not publicly, then a private email will suffice.

Hi Joey,
It is solved. We were using Envivio encoder for the live stream.  Envivio support has changed something and its working now.
Thank you.

We have found that we do, in fact, have a bug in Shaka Player around our handling of presentationTimeOffset, specifically for live streams.  I've updated the tags and title to reflect this, and I'm reopening the issue until we can publish a fix.


[dv/xbar] Do not tie all reset to one source

Description
In current xbar testbench:
https://cs.opensource.google/opentitan/opentitan/+/master:hw/top_earlgrey/ip/xbar_main/dv/autogen/tb__xbar_connect.sv;l=22?q=TODO&ss=opentitan%2Fopentitan:hw%2Ftop_earlgrey%2Fip%2Fxbar_main%2Fdv%2F
tb__xbar_connect.sv, all resets in xbar are tied to one reset source. Ideally these resets can come from different reset domains.

The current modeling actually corresponds to what is happening on the chip level. There are different resets for the different clock domains, but they all go back to the same parent reset in the same reset domain. For details see this comment https://github.com/lowRISC/opentitan/issues/15729#issuecomment-2161239016.
I am thus closing the issue as not planned.


KAFKA-9076: support consumer offset sync across clusters in MM 2.0

In order to make the Kafka consumer and stream application migrate from source to target cluster
transparently and conveniently, e.g. in event of source cluster failure, a background task is proposed to periodically sync the consumer offsets from the source to target cluster, so that when the consumer and stream applications switch to the target cluster, they will resume to consume from where they left off at source cluster.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-545%3A+support+automated+consumer+offset+sync+across+clusters+in+MM+2.0

@ryannedolan revised the pr, please take your time for another pass of review. Thanks

@ryannedolan do you suggest to a new connector, like "GroupOffsetSyncConnector" or an existing Connector?
Also do you suggest to do the actual consumer offset sync job as a scheduled task in Connector (like scheduler.scheduleRepeatingDelayed(this::refreshConsumerGroups, internval), or in a new "GroupOffsetSyncTask" that extends SourceTask? Previously I think in your previous comments, you suggested to run the sync job across Tasks instead of syncing all groups in a Connector?

do you suggest...

I was thinking we'd add a Scheduler to MirrorCheckpointTask (not the Connector) and periodically write offsets from there. MirrorCheckpointTask already has an OffsetSyncStore, which lets you transform offsets for any group assigned to the Task. So you just need to loop thru the assigned groups, transform their offsets, and write them downstream.
This is very close to what you have now -- just that we should do it periodically (in a Scheduler), not part of the poll() loop.
I don't think we should create a new Connector or Task, since all the info we need (OffsetSyncStore, group assignment) is already in MirrorCheckpointTask.

@ryannedolan thanks for your valuable and concrete feedback. I did the change that you may expect and please take another review when you have time. Thanks

@ryannedolan thanks for another set of review feedback, updated the pr based on your latest comments

Can I upvote so this ticet gets prioritized :)

Hi @ryannedolan @mimaison , I updated this PR with simple unit test and would like to get your initial feedback. If the proposed approach looks reasonable, I will be adding more unit tests. Thanks for your comments

Thanks @ning2008wisc for the update. I'll try to take another look but it might be worth bumping the KIP Vote as it's still missing votes

@mimaison thanks for your attention, I am wondering what do you mean by "bumping the KIP Vote".

I meant to reply to the Vote thread of this KIP and ask committers to review and vote

@ning2008wisc I was testing this PR locally, correct me if I'm wrong, it only sync CG that already exist in the target cluster. When new CG appear in the source cluster the sync doesn't propagate them to the target cluster?
If not, wouldn't it be better to sync the CG also?

@thspinto thanks so much for your feedback. It indeed does not consider the new consumer group. I just uploaded a new version that should work for new consumer group at source cluster. please go ahead and let me you your feedback. Thanks

@thspinto @ning2008wisc i am trying this , but i do not see the consumer offsets being populated on the target side, my consumer group is not dead i am polling for messages every 5 seconds on the source cluster. Could you please tell me how do i go about debugging this?

Could you post your configuration file @bseenu?

Hi @bseenu , it will be very helpful to elaborate the operational sequence of your testing case? e.g. which cluster your consumer initially consume from? Did you switch your consumer from primary to backup cluster? What message your consumer consumed before and after the cluster switch? Thanks

Sorry false alarm, my consumer was having enable.auto.commit set to false , it started working after i made it true. Thanks

@ning2008wisc what happens in a situation where i have a single consumer group subscribing to multiple topics . Let's say we have two sites - Site A and Site B and three topics - topic A, topic B and topic C. And multiple consumers are consuming from site A and if we move consumption of topic A from site A to site B. Will the committed offsets of topics B and C continue to get updated for that consumer group on site B?

@ning2008wisc what happens in a situation where i have a single consumer group subscribing to multiple topics . Let's say we have two sites - Site A and Site B and three topics - topic A, topic B and topic C. And multiple consumers are consuming from site A and if we move consumption of topic A from site A to site B. Will the committed offsets of topics B and C continue to get updated for that consumer group on site B?

From here I'd say that as soon as the consumer group starts consuming from site B, the offsets from the same consumer group from site A won't be synced anymore. Independent of the topics.

@thspinto Thanks, I tried to test it today. And see the case where consumer group not existing at the target site works fine, But if it exists but has no active members does not work.
I see that we are covering cases of DEAD and EMPTY , the consumer group state existing at target site may be some other state?

hi @bseenu @thspinto I updated the PR to handle both cases: (1) new consumer (2) new topic/partition in existing consumer. Please go ahead if you want to test it out sooner. Meanwhile I am writing some integration tests as well to test both cases. Thanks for your feedback

@ryannedolan @mimaison I added the Integration tests for testing this automated consumer offset sync in MM 2.0. When available, I am appreciated for your first pass of review. Thanks

Hello @mimaison thanks for your comments. I have addressed them in the latest push and please take another review. Thanks

bump for attention @mimaison ^ given that https://issues.apache.org/jira/browse/KAFKA-9076 is slipped to the next release (2.7.0) and some people may be already testing/using this feature, I would hope if it is possible to revisit this PR soon so that it can formally part of Kafka. Thanks

ok to test

@mimaison thanks so much for your fast response :) I have addressed your above 3 comments and please take the final review pass

retest this please

ok to test

unrelated test failures:
 kafka.api.SaslGssapiSslEndToEndAuthorizationTest > testProduceConsumeWithWildcardAcls FAILED
org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest > testReplication FAILED (though in the same file that got changed, but testReplication is not involved this PR)
kafka.api.PlaintextConsumerTest > testLowMaxFetchSizeForRequestAndPartition FAILED
org.apache.kafka.streams.integration.EosIntegrationTest > shouldNotViolateEosIfOneTaskFailsWithState[exactly_once] FAILED

retest this please

ok to test

Some of the failures look related:
18:04:25 org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest > testReplication FAILED
18:04:25     java.lang.RuntimeException: Could not find enough records. found 0, expected 100
18:04:25         at org.apache.kafka.connect.util.clusters.EmbeddedKafkaCluster.consume(EmbeddedKafkaCluster.java:435)
18:04:25         at org.apache.kafka.connect.mirror.MirrorConnectorsIntegrationTest.testReplication(MirrorConnectorsIntegrationTest.java:221)

Let's retest

ok to test

seems unrelated test failed:
kafka.api.PlaintextConsumerTest > testLowMaxFetchSizeForRequestAndPartition FAILED

@mimaison If the one failed test is not relevant, are we ready to merge, or anything I can do? Thanks

Huge thanks to all reviewers and committers for providing valuable comments and testing results


This syncs zones, both creation deletion and changes, it's pretty trivial to handle so it should not contains or create that many bugs -if any (wishful thinking)

Why does it says it fails, it succes when i compile it

There was an error publishing the mod, but not building it. Everything seemed to build fine.


Sleep more aggressively in some threads

The logger and lru maintainer threads both adjust how long they sleep
based on how busy they are. This adjustment should be exponential, to more quickly adjust to workloads.
The logger thread in particular would only adjust 50 microseconds at a
time, and was capped at 100 milliseconds of sleep, causing many
unnecessary wakeups on an otherwise idle dev machine. Adjust this cap to 1 second.

I'm giving this some thought. The logger thread should definitely have a higher max wait, but I'm worried about the wait time increasing too quickly since that's especially bad for the LRU thread.
Thanks!

Yeah this is the right thing to do.. I updated your change for the newer code, as slab classes are individually scheduled now.
it'll go out in the next release.


Adding a like button.

I was going through the project and found the following issues:
1]There is no like button for the song that is been played.
2]Notting is been displayed when I click on liked song tab in the nav bar.
Can you please assign this enhancement to me so that I can start working on it?

ok. go for it.


Build both MacOs, and linux

Fixes #3
by using Setup PostgreSQL for Linux/macOS/Windows for running PostgreSQL service on both ubuntu-latest and macos-latest.

Hey @hfhbd,
My pleasure! I find this a super interesting endeavour, and seems like a good point for me to contribute a bit to the SqlDelight Postgres efforts. I am having some issues building locally on my M1 machine, do you perhaps have any idea? This would be great so I can debug locally, instead of having to run builds on my repo's Github Actions 😅
I am seeing the following issue, but Googling hasn't yield any results after install brew install libpq. I've tried all different kind of brew link and setting the recommended environment and path option from brew but without any change in the result.
ld.lld: error: undefined symbol: PQsetdbLogin
>>> referenced by out
>>>               /var/folders/qs/9sb020z91_z1_f50v18bnmf00000gn/T/konan_temp7434751582350192226/result.o:(libpq_PQsetdbLogin_wrapper5)
>>> did you mean: _PQsetdbLogin
>>> defined in: /opt/homebrew/opt/libpq/lib/libpq.a

The row number 0 is out of range 0..-1 is also what I've seen on my CI setup, but not sure yet if it's something wrong yet with the introduced Github Action or a bug we're seeing now in contrast to the previous CI setup 🤔
Googling that error turned up it's related to incorrect libpq code, but it's curious that you didn't run into it before...
Since I cannot build locally I've not been able to test against a docker-compose postgres server.
There are other options to run Postgres on MacOs that we can try, but I hoped to use this simpler action to not introduce more complex scripts such as this: https://gist.github.com/jaredh159/634285e52456fefc9f04fb2b4bd3af28

Hey @nomisRev
I have a M1 mac too and yes, I have the same errors, but only sometimes. I don't know if you need a clean build... Did you install libpq with the correct linker and compiler env? homebrew usually echoes the config after installing libpq.
https://github.com/hfhbd/postgres-native-sqldelight/blob/0a33a34173c82b3182c921033fdb47e8786c68b3/postgres-native-sqldelight-driver/src/nativeInterop/cinterop/libpq.def#L7
Locally I just use docker: docker run  -e POSTGRES_PASSWORD=password -p 5432:5432 postgres to test the driver. I get this error locally too: row number 0 is out of range 0..-1, but the test and the code do work.

I mean this:
If you need to have libpq first in your PATH, run:
  echo 'export PATH="/home/linuxbrew/.linuxbrew/opt/libpq/bin:$PATH"' >> /home/runner/.bash_profile
For compilers to find libpq you may need to set:
  export LDFLAGS="-L/home/linuxbrew/.linuxbrew/opt/libpq/lib"
  export CPPFLAGS="-I/home/linuxbrew/.linuxbrew/opt/libpq/include"

Hmm strange. I have following in at the bottom of my.zprofile.
export PATH="/opt/homebrew/opt/libpq/bin:$PATH"
export LDFLAGS="-L/opt/homebrew/opt/libpq/lib"
export CPPFLAGS="-I/opt/homebrew/opt/libpq/include"

and it seems to match what you have in postgres-native-sqldelight/postgres-native-sqldelight-driver/src/nativeInterop/cinterop/libpq.def

The test wrongCredentials failed. I guess, the new action setup does not reject wrong credentials.

Hm, I have this in my .zshrc:
export PATH="/opt/homebrew/opt/libpq/bin:$PATH"

Okay, I think I got it to work. Some thoughts:

I can run the tests from IDEA but running ./gradlew test doesn't run the test. So I assume ./gradlew build doesn't either, but running ./gradlew :testing:macosArm64Test does, so maybe tests are currently not running on CI since we run ./gradlew assemble and ./gradlew build.

Running ./gradlew build doesn't work locally, so perhaps we should document in the README.MD or CONTRIBUTIONS.MD how to setup your machine for this project, and what command you need to run for which machine you're building on. Alternatively, we can perhaps dynamically only enable the targets for the platform you're building on. I.e. I cannot build linuxX64 or macosX64 on my Arm64 machine.

I'm happy to create PRs with the relevant changes depending on your thoughts ☺

🤯 Thanks for the investigation. Indeed, I only run macosArm64Test locally... Interesting, building the arm artifacts on macosX64 works (the artifacts are published and works on arm)
But at least on ubuntu-latest, which uses linuxX64, .gradlew build does work, otherwise, the wrong credential test won't fail :D
Feel free to add it to the README.md (or I can take it too).
But in the end, this is a Kotlin error, so one of us should create a youtrack ticket.

I created a ticket for the wrong rejected credentials.
Until this bug is fixed, let's keep the current behavior and test linux only.

I will add a short description of how to set up your machine and which tests do work.
@nomisRev Do you want to create the youtrack ticket? Otherwise, I can take it too.

Interesting, building the arm artifacts on macosX64 works (the artifacts are published and works on arm)

It seems this works, but not the other way around. At least on my aarch64 machine :/

But in the end, this is a Kotlin error, so one of us should create a YouTrack ticket.

Okay, I think I found what the bug is with ./gradlew build in the Kotlin Gradle Plugin. At least for me, could you perhaps verify this before we create a ticket on YT?
When I run ./gradlew build on my Mac M1 it runs the test the first time, but if they FAILED they're cached and won't run again unless you clean or --rerun-tasks so this results in a false positive.

I can create the YouTrack issue. Thanks for looking into this with me @hfhbd 🙏 I now also figured out how to setup CI and local dev for my own project, and can continue testing this driver in a "real-life" project 🙌

Okay, I think I found what the bug is with ./gradlew build in the Kotlin Gradle Plugin. At least for me, could you perhaps verify this before we create a ticket on YT?

When I run ./gradlew build on my Mac M1 it runs the test the first time, but if they FAILED they're cached and won't run again unless you clean or --rerun-tasks so this results in a false positive.

What do you mean?
If I run ./gradlew clean ./gradlew build it fails on M1 mac because of X64 linking problems. Running ./gradlew build again still fails.

Sorry, I was talking about a separate issue that I am experiencing when only having macosArm64 configured. I temporarily disabled the other targets locally investigating the issues with ./gradlew build.
I created two separate YouTrack issues:
https://youtrack.jetbrains.com/issue/KT-54505/Build-macosX64-from-macosArm64
https://youtrack.jetbrains.com/issue/KT-54506/Incorrect-cached-macosArm64Test-task-resulting-in-false-positive


[Bug] labelLayout.draggable didn't work

Version
5.4.3
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=line-smooth&code=PYBwLglsB2AEC8sDeAoWsAeBBDEDOAXMmurGAJ4gCmRA5AMYCGYVA5sAE7m0A0J6AE2aMiAbVoBZGL1i0AKgFcqM2gHUqAlXIAWClQDEOEFQGVmphdFoBdEgF8-6cjnxFUpMpRqyAbowA2SrT2jrB4VEZUhLCi_MQegsJiABwATAAMPLAAnADMqVnZ6QCMhbkALFnFqUVVubmZsMX56dahHhTUdP4Q0MrtpHgAtsDAYNpEYBxKA-j-jABGVP5ucR542sAA7pPTVLOwDmuw80v-ADKM5MAKYKsJpAIcjKysi_7eUzPHRx52JLY7ABuIA
Steps to Reproduce
Look here
Current Behavior

labels do not respond to dragging

Expected Behavior

labels react to dragging

Environment
- OS: Windows 10
- Browser: Chrome, Opera
- Framework:

Any additional comments?
No response

Apparently draggable is effective only when x or y are set.
Demo Code


Robert Longson: Watch hacker-list.com

Robert Longson requests the watch of the watch_keyword hacker-list\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

hacker-list\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Ollie in Charcoal HQ